The Advanced Variant Configuration screen does not open in classic SAPGUI transactions (e.g. Sales Order processing) and shows an error page or an empty screen or an error message that some requests were not successful in case the S/4HANA embedded Fiori deployment option is used, which means S/4HANA backend and Fiori frontend server system are the same.
Another issue is that a logon page comes up in SAPGUI for Windows when opening the Advanced Variant Configuration screen in case the S/4HANA embedded Fiori deployment option is used.
The reason for the issue in the Advanced Variant Configuration screen is that an origin URL parameter is added to the OData requests sent to the SAP Gateway system, which is prohibited by SAP Gateway in the Co-Deployment scenario.
The logon page issue happens because in SAPGUI for Windows, the SSO logon cannot be established the same way as when accessing the system via Fiori Launchpad and embedded SAPGUI for HTML; instead, a ticket-based logon using special capabilities of the SAPGUI HTML Viewer control is used.
Refer the Notes: 2916536-2916536 – SSO and OData Issue Fix for Advanced Variant Configuration
There are few new BOM Transactions in S4 Hana (onPrem) as listed below
CS11H Display BOM level by level-SAP HANA
CS12H Display multilevel BOM – SAP HANA
CS13H Display Summarized BOM – SAP HANA
These Transactions use the CS_BOM_EXPL_MAT_V2_HANA and not the classical Function module. SAP Has done Time consumption between classical and S4 Hana and concludes When the Data set or the complexity of the BOM is more then only the Improved Performance can be noticed.
Curious about the details? Dive into the comprehensive time comparison study at https://me.sap.com/notes/0002469718
If you’ve had hands-on experience with these transactions or the function module, I would love to hear your insights! Drop a comment below and share your thoughts
The below are the list of New apps that have been released in SAP S/4 Hana 2023 in the Manufacturing LOB
⚡ Historical Buffer Performance –
is a new app using which you can view the historical data for your buffer stock related to the time-dependent buffer level charts within a specified time period (for example, last month). The visualization and analytical capabilities helps the production planner to gain an insight into the historical buffer performance for a material.
⚡Manage Material Coverage(F0251A) –
With this app, you can display and analyze coverage issues that exist for selected materials. For each material that you select, you can display a stock / requirements list including material shortage information, which helps you determine shortages that can cause disruptions to production or to the fulfillment of customer demands. You can also take actions directly from the app, for example, start an MRP run or edit MRP elements to resolve coverage issues
⚡Evaluate Capacity is a new app using which you can better visualize capacity situation of work centers within a plant. You can group work centers based on work center group and visualize the utilization on the group level. The visualization and analytical capabilities helps in understanding and managing the impact of capacity situation.
⚡My Area of Responsibility – Work Center Person Responsible
With this new app, you can define your area of responsibility by selecting the respective combinations of plant and work center person responsible. In the Mass maintenance of work center capacities app, only those work center capacities are displayed in the worklist that fulfill your selection criteria.
Once when you open the link then , this will provide you all the information.
As you enter the migration object , 1st you need to apply the filter in the top portion for the version and the language. As SAP is continously releasing new objects in subsequent releases , you need to ensure which exact version you are working on.
Also Note the SAP DMC has been introduced only from 1909 so make sure you are on version above 1909 to use this DMC features.
Once you have selected the correct Version then you will see the list of the all the migration objects .. Here you can filter with the migration object and you can also filter based on the Object type- if it is master data or the transaction data. The important attention is to be given to the available migration approach if it can be done through the File/Staging table or direct transfer. Also note DMC is widely used on ERP / EWM / AFS so kindly make sure you are checking the releavant application here. Filter can also be applied on the components.
With this information provided now you will be able to identify the migratoin object with approach. This should help you to plan your data migration approach of the Project.
Do leave your comments/ query.As we are continiously learning i will update if there is any correction or any topics to be covered.
In the Previous post , we saw about the SAP DMC introduction, In this post we will see the pre-requisities for migrating the data from the existing ECC System.
Do kindly review the previous post before you start on this Post.
There are many SAP projects which are now on the verse of migration. And SAP DMC till 1909 has offered only the below methods for migration
1)Transfer data using files
Download template file for relevant migration object
Populate file with relevant business data
Upload file to the SAP S/4HANA migration cockpit
2)Transfer data using Staging Tables
Staging Tables are created automatically (in an SAP HANA DB schema)
Populate Staging Tables with business data
Transfer data from Staging Tables to target SAP S/4HANA system
SAP Has provided this Transfer data directly from SAP System (new with SAP S/4HANA 1909).
Transfer data from SAP ERP source system to target SAP S/4HANA system
Access source system through RFC connection
Supports data migration scenarios from other applications for example, from SAP Apparel and Footwear (SAP AFS) to SAP S/4 Fashionand Vertical Business, SAP Extended WarehouseManagement (SAP EWM) to Decentralized EWM
You want to migrate data from an SAP ECC 6.0 system or an to an SAP S/4HANA On-Premise system using Migration Cockpit,then one of the below Prerequisitie is to have DMIS installed in the ECC system.
The Below notes gives detailed information of the Complete Pre-Requisites.
2973957 – SAP S/4HANA Migration Cockpit: Composite Note for Transfer Data Directly from SAP System – SAP ERP or SAP AFS to SAP S/4HANA
SAP DMC Stands for the SAP Data Migration Cockpit. SAP is Sunsetting the support of LSMW and other upload tools in the Hana Envirornment.
Earlier the Data migration was done using the LTMC. SAP offered the features of migrating or uploading the data for the S4 hana system with the predefined objects like Materail master, BOM , Routing etc.
It has options to Upload the data using files or staging tables this was available in the S4 Hana version 1909.
But From S4 Hana (OP) 2020, it is strongly bringing the SAP DMC is the only source ( Same as LTMC) but the addittional feature here is we can directly connect the ECC system to S4 Hana system through this SAP DMC and perform the required data migration.
This also provides features to do the Mapping ( Transformation) in case if there is any changes in the master data, etc if the costcenter is changed then we can provide the source vs target and which help to create the new cost center in the S4 Hana system.
The intent of this post is to bring awareness on this tool and further topics will be detailed in the subsequent Posts.
More details about this SAP DMC is available in this link https://www.sap.com/documents/2017/07/26113ac0-c47c-0010-82c7-eda71af511fa.html and also keep watching this space for more updates on this topic
You will be surprised to know that with single T.code we will be able to get the list of all reports across all modules in SAP. Watch this video to find it and also how to use it.
When we start the MRP live in S4 hana, we may notice some of the materials are not being planned by MRP live. during such instances it is good to check with the given report to find the reasons for not planned.
