Sync users from s/4 hana to IAS and vice versa for UUID sync

 

Connect Identity Authentication service to On-Premise System

In SAP S/4HANA, user name is usually used to access the system and user name is unique. In BTP, email is used to access the system and email address is unique for each user. When configuring SSO between BTP and S/4HANA system, we need a common identifier across the landscape. Usually, email or Global User ID(UUID) are used to uniquely identify a user. For Task Center integration, only Global User ID is supported. The UUID is automatically generated for every newly created, imported or provisioned user in the Identity Authentication Service. So, We need to connect the Identity Authentication Service to the SAP S/4HANA system to update the Global User ID in SAP S/4HANA system. When updating the UUID from IAS to S/4HANA, the email address is used to map the users. So, the users must have email address maintained in transaction code SU01.

Firstly, we need to sync the users from the S/4HANA to IAS, if user with same email address exist in the IAS, the login name will be updated in IAS. If the user does not exist in the IAS, the user will be created in the IAS.

Then, we need to sync the Global User ID(UUID) to S/4HANA system.

Reference: https://help.sap.com/docs/SUPPORT_CONTENT/fioritech/5129990827.html

Change SAP Transport Request Number Range

 Sometimes we may require to set up new number range for the TR's created in SAP ABAP System:

Ex: Normally TR's are created strating from:DEVK900000, curent numberrunning may be DEVK902500.

You may need to start from a new number for some reason. Ex you need to start from DEVK910000.

run below command in DB level: below command is to run in hana db with schema SAPABAP1.

update SAPABAP1.E070L set TRKORR = 'DEVK910000' WHERE LASTNUM=’TRKORR’;

Referencenote: 1674286 - How to modify CTS transport number range (ABAP)

What is SAP Fiori Catalogs, Groups, spaces & Pages

Catalogs

• Purpose: 

  Catalogs are containers for Fiori app tiles. They are technical or business-oriented and are used to manage and organize tiles. 
• Types: 

  They can be technical (containing many tiles) or business-oriented (used for specific business roles). 
• Assignment: 

  Business catalogs are assigned to business roles, which determines which apps a user can see. 

Groups

• Purpose: Historically, groups were used to organize tiles for users on the Fiori launchpad. 
• Status: SAP is phasing out groups in favor of spaces and pages. 
• Content: They contained tiles that were available to the user. 

Spaces

• Purpose: Spaces are the modern, primary way to organize content on the Fiori launchpad, replacing groups. 
• Structure: A space is a container that holds one or more pages. 
• Assignment: Spaces are assigned to business roles. 
• User Experience: They offer a more focused "day-in-the-life" approach compared to groups, providing a cleaner, simpler view of essential starting points. 

Pages

• Purpose: Pages are individual screens within a space that display apps as tiles. 
• Structure: Pages can have single or multiple sections that further organize tiles. 
• Content: They are created from catalogs and contain a collection of apps for a specific business purpose. 
• Assignment: Pages are assigned to spaces. 

 

Fiori Inital setup task list

 In S/4 hana below are the list of tasks to run for inital fiori activation:

SAP_BASIS_ACTIVATE_ICF_NODES :below are the services required

/sap/public/bc/its/mimes

/sap/public/icf_info

/sap/bw/ina

/sap/bw/mime

/sap/bc/ui2/nwbc

/sap/bc/nwbc

/sap/bc/apc/sap/webgui_services

/sap/bc/gui/sap/its/webgui

/sap/public/bc/ur

/sap/public/bc/uics

/sap/public/bc/icons

/sap/public/bc/icons_rtl

/sap/public/bc/webicons

/sap/public/bc/pictograms

/sap/public/bc/webdynpro

/sap/public/bc/icf/systemloginjs

SAP_ESH_INITIAL_SETUP_WRK_CLIENT

Component: EAAPPLH and select all models

SAP_BW_SETUP_INITIAL_S4HANA

SAP_GW_FIORI_ERP_ONE_CLNT_SETUP

SAP_FIORI_FOUNDATION_S4

SAP_FIORI_CONTENT_ACTIVATION

SAP_BR_ADMINISTRATOR

Publish OData V4 service groups in sap fiori

 To publish v4 Odata service groups:

goto: /n/IWFND/V4_ADMIN

theb search for service

select and click on publish service group.

s/4 Hana Public cloud Use full app names

APP NAME                         -         Description(USE)

Display Authorization Trace - like SU53 in onpremise.

Display Security Audit Log -  If we want check security audit log
IAM Information System - It works something like SUIM
Display Authorization Trace - To capture the authorization trace.
Monitor Email Transmission - Display all outgoing email requests & Send a test email to check
Monitor User Sessions - To monitor all active users session, you can delete if you want.
Monitor Email Transmissions - Like SOST in On-premise

Embedded BW activation in S/4 hana

 To Activate Embedded BW in S/4 hana use belw notes:

Check notes:

2636754 - Configuration steps for embedded Analytics in ABAP based Applications

2289865 - Configuration steps for SAP S/4HANA Analytics

2303900 - Latest Information about BW Setup in S/4HANA Systems

Setup: 

Run se37 to setup BW client:

RS_MANDT_UNIQUE_SET – to set the client

RS_MANDT_UNIQUE_GET – to view existing client

Run the task in STC01: 

AFter setup we are facnig error:  Data source XXX was not found in system <SID> from  Analysis for office.

When we execute the same query from RSRT once, then it is working from Analysis for office.

We need to run the RSA1, first time it will ask to activate, so activate it. No wall queries are started working

also check the rfc in SBGRFCCONF. The client should be correct client.