Study guide
11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages
Key Takeaways Explain This Topic AI
A business catalog in a role grants access to apps; a launchpad space and its pages in the same role make the tiles appear automatically.
Customers own their business roles; SAP templates (security roles starting with SAP_BR_) should be copied, not changed.
Technical catalogs hold original tiles and target mappings and are maintained with the Launchpad App Manager; business catalogs hold references and are maintained with the Launchpad Content Manager.
Groups are deprecated since SAP S/4HANA 2021; spaces and pages are maintained with the Manage Launchpad Spaces and Manage Launchpad Pages apps.
Last updated: October 2026
Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages
A sales user who cannot see the Create Sales Orders tile is a common problem in projects and in practice systems. The S4C03 unit Creating Users and Defining Authorizations explains the chain from user to app: user master record, business role, business catalog, and launchpad space and page.
Business Roles and Who Owns Them
A business role represents a job, such as an internal sales representative. SAP delivers hundreds of business role templates; their security roles start with SAP_BR_ . A template contains the SAP Fiori and classic apps of the job, the navigation between them, markings for supported devices, a default launchpad layout (groups or spaces and pages), and the matching security role. Copy a template instead of editing it, or build a role from scratch.
Customers own their business roles. Role administrators work with the line-of-business experts, review the roles after each upgrade (deprecated and new roles), maintain spaces and pages, remove the access of the external project team after the project, and apply the rule of least privilege . The course advises against giving this job to the security administrator, the functional or Basis consultant, the UI designer or developer, or the project manager, because none of them focuses on the end-to-end user experience or stays with the system long enough.
The Authorization Chain
Object Contains Notes
Business user One or more business roles Employees are ideally replicated from the HR system of record, for example SAP SuccessFactors Employee Central
Business role One or more business catalogs and launchpad spaces Created with role maintenance ( PFCG )
Business catalog References to tiles and target mappings Can mix SAP Fiori apps, Web Dynpro apps, SAP GUI transactions, and WebClient apps; its content is a subset of the technical catalogs
Technical catalog Original tiles and target mappings (launchpad app descriptors) Managing it requires the role SAP_FLP_ADMIN
Space and page Pages with sections of tiles or links Control the display, not the authorization
In short: the catalog in a role grants access to the app and brings its authorizations into the role; the space and page in the role make the tile appear automatically. A tile on a page whose app is not in any of the user's catalogs is not displayed. In addition, the OData services of each app must be activated, individually or with task lists.
Standard roles for people who configure and extend the system include Administrator , Analytics Expert , Business Process Specialist , and several Configuration Expert roles. Administrators set up the launchpad and its content, end users personalize it, and developers can extend the launchpad UI through APIs.
Users
Users are created as user master records with SU01 ; at a minimum, the last name and a password are required. Users log on with a user name and password or with single sign-on. The user master record grants access to the SAP S/4HANA application only, not to the SAP HANA database or the operating system; the application reaches SAP HANA through a technical user. To use the launchpad, a user needs the SAP Fiori foundation user role from Rapid Activation (section 11.3) plus the catalogs, and usually the spaces, of their job.
- Setting Up Launchpad Content
- Three Configuration Layers
Cross-client configuration layer (SAP Fiori administrator): technical catalogs.
Client-specific customizing layer (SAP Fiori administrator): business catalogs, spaces, and pages. Content changed here is decoupled from the configuration layer.
Personalization layer (end users): users can add, remove, and rearrange tiles they already have access to, but they cannot give themselves access.
For new implementations, SAP sets up the launchpad for one client per system, with sample apps, as part of the standard services; partners enable the apps for the customer's processes. For conversions, partners set up the launchpad with Rapid Activation.
Tools (SAP S/4HANA 2021 and Later)
- Object Recommended Tool
- Technical catalogs SAP Fiori launchpad App Manager ( /UI2/FLPAM ), the successor of the mass maintenance tool
Business catalogs Launchpad Content Manager : /UI2/FLPCM_CONF (configuration layer) and /UI2/FLPCM_CUST (customizing layer)
- Spaces Manage Launchpad Spaces app (F4834)
- Pages Manage Launchpad Pages app (F4512)
- Roles Role maintenance ( PFCG )
- Groups (deprecated since SAP S/4HANA 2021) SAP Fiori Launchpad Designer only
The Launchpad Designer ( /UI2/FLPD_CONF , /UI2/FLPD_CUST ) is not deprecated and is still needed when settings should apply only to a subset of users in a client, but it does not distinguish technical from business catalogs, so administrators must keep originals and references apart themselves. KPIs and reports are maintained with Manage KPIs and Reports (F2814), which replaced the SAP Smart Business tools in SAP S/4HANA 1909.
Recommended Procedure
Create a business catalog , preferably by copying an SAP business catalog, which keeps the target mappings needed for app-to-app navigation. Do not change SAP catalogs directly. Apps delivered only in technical catalogs (mainly SAP GUI for HTML apps) are added as references.
Create a business role in PFCG and assign the catalog on the Menu tab ( Insert Node → SAP Fiori Launchpad → Launchpad Catalog ). The catalog's authorization objects are added to the role and maintained on the Authorizations tab.
Create a space with at least one page , and assign the space to the role ( Launchpad Space ) before adding tiles. Pages are assigned only through their space.
Add the apps to the page. Apps from catalogs that are not in the same role are flagged "Out of Context" , a warning that users may not see them.
Further recommendations: keep originals in technical catalogs and references in business catalogs, work in one scope at a time, and keep a catalog below 100 apps to avoid performance problems at design time. About 300 new SAP Fiori apps arrive with each release, which is why the Content Manager offers mass maintenance and where-used lists (which roles use a catalog, which catalogs contain an app). The role SAP_FLP_ADMIN contains the catalogs SAP_BASIS_BC_UI_FLA and SAP_BASIS_BC_UI_FLD and the space SAP_BASIS_SP_UI_FLP for these tools.
Tip
If a sales user can start an app through search but does not see its tile, the catalog is assigned but the space or page is missing. If the tile is on the page but stays hidden, the catalog is missing from the user's roles.