To trace with HTTP watch while checking fiori, please install HTTP watch from link:
http://www.httpwatch.com/download/
Reference note: 1558903 - How To Trace a Portal Scenario Using HttpWatch
==========================================================================
To Activate Job Repository in S/4 hana, we have to perform below steps:
In Section-1, i will provide direct steps, with out going to more deails, for more deails you can follow section-2:
Section-1: This steps should perform in all client in system like 000, 100 & 200.
1. check whether SAP_SYSTEM user exists or not, if not create user type system and with SAP_ALL profile. you can also user differnt user than SAP_SYSTEM, but recommed to use this user.
2. run /nSJOBREPO_STEPUSER tcode and assign user SAP_SYSTEM
3. Run report: R_JR_UTIL_1 and activate job repository, if already active also, just deactivate and activate once. So that job R_JR_BTCJOBS_GENERATOR will get scheduled.
after job R_JR_BTCJOBS_GENERATOR run only, the default jobs will get scheduled.
===============
Section-2
Below is the detailed procudure to activate:
By default, the SAP S/4HANA technical job repository expects the user SAP_SYSTEM in the clients ADMIN (=000) and BUSINESS or, if this is not available, the user DDIC. If neither SAP_SYSTEM nor DDIC exists in a client (or if these users do not have the required authorizations), the technical job repository cannot schedule any jobs in this client.
In this case, enter a user that should be used to execute the technical jobs in the client for each individual client.
As of SAP S/4HANA 1610, transaction SJOBREPO_STEPUSER exists for this purpose. It is used to create a suitable user and assign this user to the job repository in the current client. As of SAP S/4HANA 1709, this transaction can be called using a button in the menu bar of transaction SJOBREPO.
Goto Transaction: /nSJOBREPO_STEPUSER
So we will assign that user.
If the job R_JR_BTCJOBS_GENERATOR not exist in any client, just run report R_JR_UTIL_1 deactivate and activate job repository, it will crate a new job in the logged in client.
Reference Notes:
3236399 - FAQ - Technical Job Repository (SJOBREPO)
2190119 - Background information about SAP S/4HANA technical job repository
Values in My User Defaults is blank in My Purchase Requisitions New app
While creating a purchase requisition, the following needs to be done to have values in My User Defaults:
Default Settings is used to view and edit selected default settings of the purchase requisitions created by the user.
Reference note: 3497486
========================================================================
User IDs not found in "Default Settings for Users" App
In Manage Workforce APP, No work agreements exist for the users that are facing the error. Thus, are not appearing in the user selection(F4 help). A valid workagreement should exist for that particular CB user
Reference note: 3320061
=========================================================================
While accessing Migrate your Data Fiori app, you will not find the create Option:
Your client global setting is notmofiable in SE06
Your client might be not modifiable state in scc4
Your client might set as test or production in SCC4.
=======================================================================
if we did sap_all client copy , we need to run the SAP_ESH_ADJUST_AFTER_CLIENT_COPY
=======================================================================
Error ESH_ADM_MSG312 "the execution of the URL according to the whitelist is not possible" occurs when run ESH-COCKPIT
For the root cause solution, please check the SAP Notes:
853878 - HTTP WhiteList Check (security)
2578665 - How to maintain the table HTTP_WHITELIST
As the workaround, the enterprise cockpit can be opened from t-cd=ESH_DASHBOARD -> Menu -> Administraton -> ES-Cockpit.
2626107 - How to execute task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT
========================================================================
In SAP S/4HANA Cloud, public edition, you need to deploy scope items in both the customizing and development tenants, but they are not deployed separately in the sense of independent activations. Instead, the customizing tenant acts as the initial system where you define the scope and make initial configurations. The development tenant is then activated to mirror the customizing tenant, allowing for development and testing of changes before they are transported to the customizing tenant or potentially to a test/production environment.
In SAP S/4HANA Cloud public, custom roles are primarily created and managed within the Customizing Tenant, which is the primary workspace for business process configuration and key user extensibility. While the Development Tenant is used for ABAP development, including developer extensibility, custom roles are generally not created there.
The customizing tenant uses customizing requests and software collections for moving configurations, while the development tenant uses workbench requests. This ensures a clear separation of concerns.
some more glance on TR's created during deployment:
https://community.sap.com/t5/enterprise-resource-planning-q-a/deployment-of-organizational-structure-from-development-tenant/qaq-p/14015683#:~:text=Accepted%20Solutions%20(1)-,Accepted%20Solutions%20(1),learning%20page%20and%20the%20KBA:
On the other hand, when you deploy your CBC configurations to the Development Tenant, there is no transports created for you to release/export these configurations to the Test Tenant and Production Tenant. This is a kind of hard guardrail to prevent you from moving development org configurations to the T and P tenants. From Development Tenant, you can only create and export development transports (ABAP codes) to the downstream tenants.
