/UI2/FLC

/UI2/FLC reads all launchpad content in the selected development packages and returns it as one ALV list, with errors and warnings next to the objects they concern. It serves two purposes:

• Troubleshooting: standard content problems, each with a test ID and a suggested place to fix it.
• Analysis: which catalogs exist per area, which tiles and target mappings no role uses, which application types a catalog references.

For a given user, the report can also show whether the content sits in a PFCG role assigned to that user. /UI2/FLC is a content inventory with built-in consistency rules, not a single-user navigation test.

Information rows carry test IDs starting with INFO. Errors in the TM and AP groups are the ones that break navigation for users, so /UI2/FLC results are best read from those groups first.

Alder Manufacturing transports a new purchasing catalog and wants to check it before go-live:

1. Start /UI2/FLC in the system that holds the launchpad content.
2. Select the adaptation layer: Configuration (client-independent), Customizing (layered) to see whether customizing overwrites configuration, or Customizing (only).
3. Filter by catalog ID or development package; select Include Subpackages for a structure package.
4. Optionally enter a user and select Restrict to Assigned Roles.
5. Run the report and switch to a predefined layout that shows only errors.
6. Fix each error where the table suggests, then run /UI2/FLC again.

Running the same selection before and after a transport makes /UI2/FLC a simple quality gate for launchpad content.

Yes, in recent releases. The ABAP platform 2025 documentation marks content checks with /UI2/FLC as deprecated and points to two tools instead; the 2023 documentation carries no such note.

• Launchpad content manager (/UI2/FLPCM_CUST): displays issues while loading catalogs, such as unresolved references and differences between configuration and customizing scope.
• Launchpad content aggregator (/UI2/FLPCA, or /UI2/FLPCA_USER per user): lists the content of roles, including tiles, target mappings, OData services and ICF services.

For pages, /UI2/CHECK_PAGE_REFS finds broken tile and target mapping references, and /UI2/FLC1 finds orphaned catalogs and groups. Teams on older releases can keep using /UI2/FLC, but new runbooks should be built on its successors.