SAP S/4EWM2023-ECC6 - Transfer Master Data using IDoc

CLICK here to view the Presentation

SAP QM - Late Characteristics Creation for Process Quality Control in PP Production Order

 
CLICK here to view the Presentation

Q&A in Class (2025-04-30) S43000

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Classic vs S/4 FIORI Technical Object creation for SAP Plant Maintenance. 

Answer: The FIORI "UX" App "Create Technical Object" is a combined "UX" App to Create either Functional Location or Equipment and therefore combining the classic transaction code of IL01 and IE01. Besides layout changes of the look and feel in the FIORI interface via "Create Technical Object" FIORI App, there is really not much difference comparing this App to IL01 or IE01. 

See link 

https://froggysap.blogspot.com/2024/11/sap-pm-create-technical-objects-s4hana.html

Another FIORI App for Technical Objects perhaps worth reviewing is the "Find Technical Object" FIORI App ID "F2072"

See the link below for a demonstration of this App:

https://docs.google.com/presentation/FindTechnicalObjectFIORIApp/

Some of the key features this App are:

• List Display FL and EQ plus download to Excel.
• Display Installation information for the Technical Object in the Hierarchy.
• Perform Installation and Dismantling.
• Shows details of related Notification and Order for the Technical Object of FL an EQ.
• etc.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Advanced features of "AI" (Artificial Intelligence) in S/4HANA 2023 Plant Maintenance ? 

Answer: Predictive maintenance continually assesses equipment health in real time, helping the maintenance organization to maximize uptime and therefore equipment and/or functional location performance. There is a "Predictive Modeling" tool announce by SAP recently (only via FIORI App) but unfortunately we do not have access to activate it for simulation. Nevertheless, to be really able to use such a "Modeling" tool, the Equipment or FL must be IOT-powered; meaning sensors embedded in equipment to collect data and predict potential failures, allowing for proactive maintenance and minimizing downtime. Hopefully, SAP soon will provide a course content and access to this kind of advanced App to provide knowledge transfer to consultants and the customer. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Option for EAM Deployment from ECC to S/4HANA ? 

Answer: The ways in which how the PM module will be deployed from ECC to S/4HANA system is of the following: 

• On-Premise : On-premise solutions involve resources being deployed within the organization's own infrastructure. The Organization will need both IT (BTS team) as well as Software support teams internally as the SAP software is installed and maintenance within the premises of the Organization. The organization can then flexibly customize the SAP system to their process requirement either using internal teams or SAP partners. 
• Cloud (Private) : Private Cloud service is still managed by a 3rd party but it is dedicated for a single Organization. The SAP software is access via Cloud, while some Customization is still possible but depending on licensing agreement with SAP. 
• Cloud (Public) : using Cloud service whereby it is shared by multiple organizations, often time this kind of license are for organizations with "super lean" IT and support whereby most if not all SAP support is by the Cloud service organization. Usually standard use of the SAP system is expected with limited or no Customizations. This approach is generally acceptable for organizations with lean IT and smaller organizations which prefer to use "Standard" SAP. Implementation time line is usually the shortest for such as approach. 
• Mobile: Setting up of Mobile infrastructure is desirable if there is an intention to use tablet devices for Job Card deployment from Maintenance Orders to the Technicians via FIORI login via Mobile Devices. The "Simplification Maintenance" Scenario for Mobile solutioning allows Technician to perform confirmation via their Mobile Devices. 

It is important to note that as the PM or EAM module is not the only SAP component implemented in a S/4HANA migration from ECC, for a mid size to large organization, it is likely for a Deployment with either On-Premise with Mobile or even Hybrid with On-Premise, Private Cloud and Mobile architecture as a Deployment option. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is SAP BTP in S/4HANA ?

Answer: There are always 2 sides of SAP ie: the Application side and the Technical side. While the Application side (often where Application Consultants works are associated with) are the SAP software areas like FICO, MM, SD, PP, HR etc.

1. Basis: The Technical side of SAP ensure that everything should work the way it should, and during the R2 and R3 SAP versions are usually referred to as Basis (often the job function of Basis Consultants). SAP Basis is technological foundation and system administration component for running SAP
2. Netweaver: SAP NetWeaver, originally developed by TopTier Software in 1997 and acquired by SAP in 2001, was first released in 2004. The TopTier Software develops the portal technology that would become the foundation of SAP NetWeaver. SAP Basis is the foundation of SAP NetWeaver, with Basis evolving into the Web Application Server (WAS) and becoming a mandatory requirement for installing any NetWeaver component. NetWeaver encompasses various functionalities, including Portal, Business Intelligence, and Process Integration, building upon the capabilities of the previous Basis. I'd like to call Netweaver the Basis++ as Netweaver builds on top of the SAP Basis. 
3. BTP: Perhaps the one of the best differentiating statement on Netweaver vs BTP is that SAP NetWeaver is the on-premise foundation for SAP applications, while SAP Business Technology Platform (BTP), formerly SAP Cloud Platform, is its cloud counterpart. SAP Business Technology Platform (SAP BTP) was introduced in January 2021. SAP BTP was introduced as part of the SAP strategy to unify its portfolio and cloud offerings under a single platform. I'd like to call BTP as NetWeaver++ as BTP enhanced on top of SAP NetWeaver. 

SAP will continue to add new components to its BTP platform but the most recent (or one of the most recent SAP release) introduce BTP to consist or 5 components (or 5 Pillars): 

1. SAP BTP for Data Management offers a wide range of data management options (previously the BI component of NetWeaver) are offered by SAP BTP, including:
• Data Warehousing: Storage and analysis of vast amounts of data are made possible by the cloud-based data warehouse offered by SAP BTP.
• Data lakes: Regardless of the type or structure of your data, SAP BTP offers a cloud-based data lake that can be used to store it all.
• Data Visualization: Dashboards, reports, and charts are just a few of the tools available in SAP BTP for visualizing data.
2. SAP BTP for Application Development is for the creation of applications, SAP BTP offers a range of tools and services, including:
• Cloud based IDE: SAP BTP offers an IDE in the cloud that may be used to create apps in a number of different programming languages.
• Code Repository: SAP BTP offers a repository for managing and storing code.
• CI/CD Pipeline : The build, test, and deployment of apps can all be automated using the CI/CD pipeline offered by SAP BTP.
3. SAP BTP for Application Integration offers several integration capabilities are offered by SAP BTP, including:
• API management: SAP BTP offers a platform for the creation, administration, and security of APIs. In the context of SAP systems, APIs (Application Programming Interfaces) like RESTful APIs using OData are generally considered more modern and flexible than BAPIs (Business Application Programming Interfaces) which use RFC (Remote Function Call).
• Event-driven architecture: SAP BTP offers an event-driven architecture that can be used to integrate apps without a shared data model.
• Microservices: To help developers create scalable, loosely linked systems, SAP BTP offers a microservices architecture.
4. SAP BTP and Intelligent Technologies uses a range of clever technologies, such as:
• Artificial intelligence (AI): SAP BTP offers a range of AI features, such as computer vision, natural language processing, and machine learning.
• Machine learning (ML): SAP BTP offers a range of ML features, such as fraud detection, predictive analytics, and consumer segmentation.
• Internet Of Things(IoT): Data collecting, data analysis, and predictive maintenance are just a few of the Internet of Things (IoT) features offered by SAP BTP.
5. SAP BTP and Analytics offers a number of analytics features, such as:
• Data Mining: Finding patterns and insights in data is a process known as data mining. To extract insights from your data, SAP BTP offers a range of data mining tools and methods.
• Predictive analytics: Utilizing data to make predictions about the future is known as predictive analytics. To predict consumer behavior, fraud, and other outcomes, SAP BTP offers a number of predictive analytics tools and approaches.
• Business intelligence: Business intelligence (BI) is the process of using data to enhance decision-making. To visualize data, produce reports, and build dashboards, SAP BTP offers a number of BI tools and methodologies.

So, is BTP an SAP Product, not really! BUT since the SAP Business Technology Platform (BTP) is an amalgamation of existing and new SAP cloud services, note the following points: 

• While not strictly mandatory for all S/4HANA implementations, SAP Business Technology Platform (BTP) is highly recommended and often essential for extending and integrating S/4HANA Cloud solutions, especially for side-by-side extensions and connecting to other systems.
• SAP BTP is a key platform for building and deploying applications that extend the functionality of S/4HANA Cloud, allowing for customization and integration without altering the core S/4HANA system. 

See the following links: 

https://www.youtube.com/watch/What is SAP BTP/

https://www.youtube.com/Understanding BTP/

https://www.youtube.com/SAP BTP is the Choice/

https://www.youtube.com/SAP BTP vs S/4HANA/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: The Classic Technical Objects transaction code in S/4HANA (similar to ECC)

Answer: The above transaction codes are still valid in S/4HANA2023 similar to its availability in ECC EhP8. One can conclude that in a technical upgrade, the transaction codes for Technical Object creation, change, or display and reporting (list display) are the same in ECC to S/4HANA. AND although there are some FIORI Apps available for some (not all) of the Technical Objects above, the "UX" (User Experience) may not be as impressive as other modules (like in MM and SD). 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What are difference in Enterprise Structure of the Plant Maintenance module comparing ECC and S/4AHANA ? 

As at ECC Ehp8 vs S/4HANA 2023 for Plant Maintenance, there isn't any difference of Enterprise Structure of 

• Maintenance Planning Plant
• Maintenance Plant

The functionality is the same from ECC to S/4 where the Logistics Plant (for MM, PP, SD) can immediately be used as a Maintenance Plant primarily as the (1) Location for the Technical Object of FL and EQ, (2) Maintenance Work Center, and (3) Spare Parts Storage. In this respect, usually this Enterprise Structure mapping for ECC to S/4HANA upgrade is "easy" unless there is a need to "revamp" the Enterprise Structure when implementing S/4HANA. 

The Maintenance Planning Plant (ECC and S/4 the same) will have to be explicitly assigned (see blog post link below), The use of the Planning Plant is for Maintenance Task List header, Maintenance Plan as well as the Header of the Maintenance Order. In this respect, Planning Plant is for "Planning" along with the Planner Group" and the Maintenance Plant is for "Execution" for assignment of the Work Center, representing as "Main Work Center" and Spare Parts issuance. 

Answer: See link 

https://froggysap.blogspot.com/HowToCreatePlanningPlant/

https://froggysap.blogspot.com/HowToCreateMaintenancePlant/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: the IBAU BOM, what is it ? 

The IBAU Material Type (ECC and S./4HANA the same functionality) is often used to represent the Header of the Material BOM to assign with Spare Parts, where the Header (IBAU BOM) is then assigned as a Construction Type to the FL or EQ. This is especially true when the Header BOM is not to be procured or inventoried; it is to be used like a "Phantom" to link the Spare parts to the Functional Location and Equipment master. Creation of the IBAU Material is easy as it only need the Basic data view with the Material code, Description, and UOM.

Answer: see link for configuration of IBAU material type and application demo for IBAU Material BOM. 

https://docs.google.com/presentation/IBAUConfiguration&DemoIBAUBOM/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

SAP MM - Self-Service Purchase Requisition using Catalog Item

 

CLICK here to view the Presentation

Question no 4045 : Valid Receivers for Production Order Settlement

In SAP Cost Object Controlling for Production Orders, which of the following determination factors for "Valid Receivers" for Production Order Settlement ?

(more than one answers)

A. Costing Variant.
B. Valuation Variant.
C. Production Order Type.
D. Planning Plant.
E. Settlement Profile.

Answer: C, E

The Order Type (Plant independent) is assigned with a Settlement Profile and the configuration of the Settlement Profile determines the Valid Receivers.

SAP S/4EWM with ECC6 - Setup and Execute Physical Inventory "Ad-hoc PI (storage bin specific)"

CLICK here to view the Presentation

SAP SCM-EWM - Setup Value-Added Services (Oiling and Repack Materials before Storage) for Inbound

CLICK here to view Presentation

SAP MM - BRF+ Out Management for PO with Channel EMAIL and PRINT

 CLICK here to view the Presentation

Q&A in Class (2025-04-22) EWM110

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What are the configuration steps of interface between ERP and EWM?

Answer: Configuring the EWM interface involves setting up the communication and integration between SAP EWM and other SAP systems (like ERP) or external systems. This typically includes defining logical systems, setting up RFC destinations, defining queues for data transfer, and generating distribution models. Additionally, configuring EWM parameters, defining warehouse structure, and creating master data like storage types, bins, and activity areas is crucial. 

Here's a more detailed breakdown of the configuration steps:

1. Basic System Setup & Integration.
• Define Logical Systems and Assign to Clients: Establish logical systems (both ERP and EWM) and assign them to their respective clients. 
• Define RFC Destination: Configure the RFC destination in ERP for EWM to communicate with the ERP system. 
• Set Up qRFC and Queues: Define queues for data transfer between ERP and EWM, ensuring the proper flow of data. 
• Generate Distribution Model: Create a distribution model to specify which data objects and attributes should be transferred between systems. 
• Configure EWM-Specific Parameters: Set up EWM-specific parameters eg: Supply Chain Unit, Plant integration to Business Partners for "Default Entitled Party to Dispose"
2. Warehouse Structure and Master Data:
• Define Warehouse Number: Create and assign warehouse numbers in both ERP and EWM, ensuring consistency. 
• Activate EWM deployment scenario: Embedded or Distributed or External EWM. 
• Define Plant, Storage Location, and Shipping Point: Define these elements in ERP and map them to EWM locations. 
• Create Storage Types, Storage Sections, and Storage Bin Types: Define the organizational structure within the warehouse in EWM. 
• Create Storage Bins: Define the physical storage locations within the warehouse using a program, template, or upload. 
• Define Activity Areas: Define the areas where specific warehouse activities (like put-away, retrieval) can occur. 
• Create Master Data (Material, Customers, Vendors): Transfer material master data, customers, and vendors from ERP to EWM using Core Interface (CIF) or ALE IDOC (BD10, BD20) depending on system and SAP version.  
• Create EWM Work Centers: Define EWM work centers for Warehouse Inspection, Deconsolidation, Packing, Value-Added Service etc in Warehouse steps. 
• Define Availability Group usually with nomenclature of "Plant/SLoc", assign it to Location-Independent Stock Type in EWM like "FF" (Unrestricted) or "QQ" (QI stock type). Also assign the Availability Group to Sub-stock type of "F1" (at Dock), "F2" (available for use).
• "SPCW/RD00" - "F1" - "FF" assign to Plant SPCW and SLoc RD00
• "SPCW/RD00" - "F2" - "FF" assign to Plant SPCW and SLoc AF00
3. EWM-Specific Configuration:
• Create and Mapping of EWM Inbound/Outbound Documents of different Category (for Inbound, Outbound, Posting Changes) to LE Inbound/Outbound Documents. 
• Create and Mapping the Item Type in EWM Inbound/Outbound Documents to the Item Category of the LE Inbound/Outbound Documents.  
• Define PPF Actions for the Header and Item Type EWM Document or Print and Process Control if necessary. 
• Define Warehouse Process Types: Define the different types of warehouse processes (e.g., inbound, outbound, internal movements). 
• Configure Process-Oriented Storage Control (POSC): Define how storage processes are controlled, including external storage steps and process definitions. 
• Configure Storage type Determination Strategies for Putaway and Removal Strategy. 
• Configure Storage section Determination Strategies for Putaway and Removal Strategy. 
• Configure Bin Sorting parameters and perform Bin Sorting. 
• Define Putaway and Replenishment Strategies: Determine how goods are stored and replenished within the warehouse. 
4. Configure RF:
• To configure Radio Frequency (RF) for SAP Extended Warehouse Management (EWM), you'll need to define the RF framework, create presentation devices, configure RF menus, assign users to RF profiles, and integrate with SAP ITS Mobile.
• Navigate to SPRO -> SCM Extended Warehouse Management -> Mobile Data Entry -> RF Framework -> Define RF Framework Parameters.
• Activate the RF framework for the required warehouse.
• Define Presentation Devices:
• Presentation Profiles: These define the appearance of the RF screens, including text size, layout, and more.
• Presentation Device Maintenance: Define presentation devices to connect to SAP through a browser or a device that supports SAP Console. 
• Configure RF Menu:
• Navigate to SPRO -> SCM Extended Warehouse Management -> Mobile Data Entry -> RF Framework -> Define RF Menu. 
• Define the menu structure and functions available on the RF devices. 
5. Configure Material Flow System (MFS):
• If using MFS, configure the interfaces, communication channels, and other relevant settings. 
• Set Up Integration with Other Systems:
• Configure integration with other SAP systems like Transportation Management (TM) or Production Planning (PP). 
6. Testing and Validation:
• Test Data Transfer: Ensure that data is transferred successfully between ERP and EWM. 
• Use EWM Monitors: Tool - Queue to check if Message Arrival and troubleshoot the Log to identify issues of the Queue to address missing configurations accordingly. 
• Test Warehouse Processes: Verify that warehouse processes (e.g., inbound, outbound, internal movements) work as expected. 
• Validate Master Data: Ensure that master data (e.g., materials, storage bins) is correctly maintained in EWM. 

By following these steps, you can effectively configure the EWM interface to integrate with other SAP systems; However, it is important to note that SAP updates in its new SAP versions of simplified and/or additional steps to the configuration that will be applied to obsolesce and new functionalities.

See the following link for steps overview: 

https://froggysap.blogspot.com/2024/07/distributed-extended-warehouse.html

Also check the following resources: 

https://help.sap.com/doc/How To Integrate EWM and in SAP S/4HANA

https://help.sap.com/doc/en-US/EWM950_Master_Guide.pdf

https://community.sap.com/sap-s4-hana-embedded-ewm-configuration-blog-step-by-step-guide/

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the meaning of Custodian, Party Entitled to Dispose, and Ship-from Party ?

Answer: All of the 3 objects are created as Business Partner which represents the Plant (or Company) with the following attributes:

• Custodian: The custodian is the entity that has direct physical control over the stock. This could be a specific plant or warehouse, and the warehouse itself can be a custodian, according to SAP Community.
• Party Entitled to Dispose: The party entitled to dispose is the entity that has the right to sell, transfer, or otherwise dispose of the stock. This can be different from the owner or custodian.
• Ship-from Party: Usually to represent as the Delivery Plant. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the purpose of Activity Area in SAP EWM ?

Answer: In SAP EWM, an activity area serves as a logical subdivision of a warehouse, used to group storage bins that are managed together for specific warehouse activities. It allows for defining activity-
dependent bin sorting, which optimize the execution of warehouse tasks like putaway or picking.

Here are characteristics and usages of Activity Area:

• Logical Subdivision: Activity areas help divide a warehouse into sections, each dedicated to specific warehouse operations, such as picking, putaway, inventory counting, or replenishment. 
• Activity-Dependent Bin Sorting: Within an activity area, you can create bin sorting that are specific to the activities performed there. This allows EWM to prioritize bins based on the type of task being executed. 
• Optimizing Warehouse Tasks: By defining activity areas and their corresponding bin sorting, EWM can efficiently assign warehouse tasks to specific bins within the appropriate area, leading to streamlined warehouse operations. 
• Flexibility: Activity areas can span across one or multiple storage bins, and they can also encompass bins from the same or different storage types. 
• Storage Bin Assignment: Storage bins are assigned to activity areas, ensuring that warehouse tasks are directed to the appropriate areas and bins for optimal efficiency. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the purpose of the XYZ Coordinates in SAP EWM Storage Bin definition ? 

Answer: The following summary points on the EWM Bin XYZ Coordinates:

• The XYZ coordinates of the Bin Structure can be represented in a a three-dimensional map. User can determine the XYZ coordinates of the warehouse storage bins by overlaying the warehouse diagram onto a map and measuring the location of the storage bins according to the XYZ coordinates of the map. 
• SAP allows the mapping using the Metric measurement (M or Meter). 
• If the company have an AutoCAD blueprint of the warehouse and all of the shelving/storage bins then the relative distance between aisles, stacks, levels, and bins specified by units of measure can be mapped in a 3D view of the warehouse via the X, Y, X Coordinates.
• With the proper setup of the relative XYZ coordinates of the EWM bins, users can view the warehouse using /SCWM/GWL t-code (the Graphical Warehouse Layout (GWL) display two-dimension layout of your warehouse).
• The X, Y, and Z coordinates specified for the Bins can then be used in the travel path calculations for labor management because the distance calculations are based on relative differences between the points.
• In order to calculate the travel time based on the travel distance, the average speed of the resource assigned is used in the standard formula (time = distance/speed) (albeit using average speed of the resources in the warehouse) via t-code /SCWM/TDC_SETUP (Travel Distance Calculation transaction). 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is a suitable method to upload initial stocks in the EWM system ? 

Answer: The following are some guidelines for t-code /SCWM/ISU or Program /SCWM/R_INITIALSTOCKUPLOAD.

1. Prepare the CSV File:
• Structure: The CSV file needs to be structured according to the /SCWM/S_STOCK_UPLOAD_EXT structure, as mentioned in the SAP documentation.
• Fields: The CSV file should include columns for:
• Warehouse Number
• Material Number
• Quantity
• Storage Bin
• Handling Unit (HU) - if applicable
• Other relevant details (e.g., Batch, Stock Type).
• Format: The CSV file should be saved in a local format.
2. Use Transaction /SCWM/ISU:Access: Navigate to the transaction code /SCWM/ISU.
• Upload: Browse and select the prepared CSV file.
• Check Data: Review the uploaded data to ensure accuracy.
• Execute: Click the "Execute" button to initiate the stock data transfer.
• Logs: A log will provide confirmation that the HU is created for the material and the material document is posted.
3. Using Report /SCWM/R_INITIALSTOCKUPLOAD (Alternative Method):
• Access: Navigate to the report /SCWM/R_INITIALSTOCKUPLOAD.
• Upload: You can either upload a local CSV file or a file from an application server.
• Process: The report will process the data in a similar manner to the /SCWM/ISU transaction.
4. SAP Note 974852: Refer to SAP Note 974852 for guidance on building the stock upload CSV file. 

More resources for data migration: 

https://help.sap.com/docs/Data Migration from LE-WM to EWM/

https://blog.sap-press.com/how-to-deploy-or-migrate-to-sap-stock-room-management/

https://blog.sap-press.com/migrating-from-sap-wm-to-embedded-ewm-in-sap-s/4hana

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the purpose of the SCU (Supply Chain Unit) in the EWM system ?

Answer: In SAP EWM, a Supply Chain Unit (SCU) represents a physical or organizational entity involved in logistics processes. 

It can be a 

• warehouse
• a goods receipt office
• a shipping office
• or any other location where goods are handled

The purpose of a SCU is also to represent a specific geographical location and maintain its associated logistical functions within EWM. 

As in the above pictorial example

• A Plant SPCW contain raw material storage locations of RD00 and RD01 which is linked to a EWM warehouse E100, the warehouse address is at the East Road with Gate 1 entered the Yard for the Goods Receipt Docking. A SCU (Supply Chain Unit) created also as E100 will be set using the East Road Gate 1 address with the Warehouse having activity attributes as a Warehouse and Goods Receipt Office. The Geo Data for SCU E100 is X1 Longitude and Latitude. 
• The same Plant SPCW also contain finished product storage locations of AF00 and AF01 which is linked to another EWM warehouse of E101, but this warehouse address although the SAME but the exit gate for Outbound Delivery is via Gate 2 on the West Road. AND the SCU (Supply Chain Unit) will be created as E101 (same as the EWM warehouse E101) but will be assigned with activity attributes as a Warehouse and Shipping Office. The Geo Data for SCU E101 is X2 Longitude and Latitude. 
• One Business Partner as SPCW code same as Plant code SPCW is created to be assigned to the Plant SPCW and also contain attributes as Custodian, Party Entitled to Disposal, and Ship-to Party AND the Single BP is assigned to both SCU E100 and SCU E101; as regardless of either Warehouse, the stock responsibilities of the raw materials SLoc at RD00 or RD01 OR finished goods SLoc at AF00 or AF01 are to ONE Plant SPCW. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

SAP SCM-EWM - Analyzing Process-Oriented Storage Control for an Outbound Delivery Scenario (for Packing 2 HU into 1 HU)

CLICK here to view Presentation

Question no 4044 : Production Order activities before Release

In SAP Production Planning & Execution, which of the following are possible activities in a Production Order before it is Released ?

(more than one answers)

A. Costing calculation
B. Scheduling
C. Capacity determination
D. BOM and Routing determination
E. Reservation created for Components.
.

Answer: A, B, C, D, E

S/4 Embedded EWM - Goods Receipt for Purchase Order before Putaway to Final Storage

CLICK here to view the Presentation

Question no 4043 : NAST Message Output Printer Determination Source

In SAP Material Management, Purchasing Document Output Determination's Printer setting can be from which of the following ?

I. Purchasing Organization
II. Condition Record
III. Purchasing Document item level Purchasing Group
IV. Purchasing Document header Purchasing Group
V. Plant
VI. User default

(only one answer)

A. II, IV, VI
B. III, IV, VI
C. II, III, V, VI
D. I, II, VI
E. I, II, IV, VI
.

Answer: A

SAP SD and TM - Considerations and Arguments for Good Business Practice for Inco Terms treatment

The question of Good Business Practice (not Best Practice) for Split SD and TM Billing Documents by INCO Terms. 

Incoterms and Their Impact:

• Incoterms specify the business agreement between the buyer and the seller at which the responsibility for goods, risks, and costs transfer from the seller to the buyer.
• They agreed Incoterms influence the way goods are transported and handled, but don't dictate how a company's internal systems should process orders for deliveries.
• Incoterms are part of the contract of sale, and they don't cover all aspects of a sale especially in international trade scenarios. 

Split criteria for "SD Outbound Deliveries" based on Incoterms:

• No, there isn't a Standardized split criteria for SAP Outbound Deliveries based solely on Incoterms. 
• While Incoterms define the responsibility for costs and risks associated with international trade, they don't dictate how a company should manage internal processes like delivery splits. 
• Delivery splits, in systems like SAP, are determined by various factors including 
• Shipping Conditions
• Plant
• Shipping Point
• Other internal parameters.

Split criteria for "SD Billing Documents" with reference to SD Sales Order and/or Outbound Deliveries based on Incoterms:

• From the Accounting perspective, it is generally a Best Practice to split Outbound Delivery to SD Billing by Incoterms, as different Incoterms can result in different cost responsibilities between the buyer and the seller. This ensures accurate billing based on the agreed terms of sale and avoids potential disputes or misunderstanding. 
• AND in my opinion, the same principles applied when creating Billing document for the Freight Orders. 
• Considerations: 
• Incoterms Define Responsibility: Incoterms (International Commercial Terms) are standardized trade terms that define the obligations, risks, and costs associated with the delivery of goods between a buyer and a seller.
• Varied Cost Structures: Different Incoterms assign different responsibilities for costs like transportation, insurance, and customs clearance. For example, in some Incoterms, the seller is responsible for costs up to the point of delivery, while in others, the buyer takes on the costs.
• Accurate Billing: Splitting outbound delivery to billing by Incoterms ensures that the invoice accurately reflects the agreed-upon cost allocation. This helps avoid situations where one party is overcharged or undercharged for costs that should have been borne by the other.
• Clear Transaction: By aligning the billing with the Incoterms, you create a clear record of which costs are included in the price and which are separate, improving transparency and reducing the potential for disputes.

Split criteria for "TM Freight Units" based on Incoterms:

• While not explicitly a Best Practice in the strictest sense, splitting freight units by Incoterms can be a valuable strategy for better clarity and management of international trade shipments. It helps to clearly define responsibilities and risks, potentially streamlining logistics and reducing disputes. 
• Hence, to split/combine outbound deliveries items with different Inco Terms into Freight Units each having the same Inco Terms can be a Good Business Practice for clarity especially when managing international trade shipments.
• However, the specific benefits and drawbacks depend on the context, including the specific Incoterms used and the complexity of the shipment.
• Benefits of splitting by Incoterms:
• Clearer responsibility: Incoterms outline who is responsible for different aspects of the shipment (e.g., arranging transport, paying for insurance, handling customs clearance). Splitting freight units based on these responsibilities can make it easier to track and manage those responsibilities.
• Improved risk management: By understanding when and where the risk of loss or damage transfers from the seller to the buyer (as defined by the Incoterm), you can better allocate insurance coverage and manage potential claims.
• Easier cost tracking: Incoterms specify who is responsible for different costs (e.g., freight, insurance, customs duties). Splitting freight units can help in accurately tracking and allocating these costs.
• Streamlined logistics: By clearly defining responsibilities, you can streamline the logistics process and reduce the potential for delays or misunderstandings.
• Reduced disputes: When responsibilities and risks are clearly defined, there is less chance for disputes about who is responsible for what, or who should pay for what.
• Potential drawbacks:
• Increased complexity: Splitting freight units by Incoterm can add a layer of complexity to the overall shipment management process.
• Administrative overhead: More freight units generally require more administrative effort to create, track, and manage.
• May not always be necessary: If the shipment is simple and the Incoterm is well understood by all parties, splitting by Incoterm might not be necessary.
• Potential for misunderstandings: If the Incoterms are not clearly defined or understood, splitting freight units based on them can actually increase the risk of misunderstandings and disputes.
• When it's a good idea:
• Complex shipments: For shipments involving multiple modes of transport, multiple parties, or complex customs procedures, splitting by Incoterm can be beneficial.
• When there are potential risks: If there is a higher risk of damage or loss, or if the Incoterms involve more complex risk transfer points, splitting by Incoterm can help clarify responsibilities.
• When there are multiple parties involved: If the shipment involves multiple buyers, sellers, or other parties, splitting by Incoterm can help clarify their individual responsibilities.  
• In summary:
• Splitting freight units by Incoterms can be a valuable strategy for international trade, but it's not a one-size-fits-all solution. It's important to consider the specific circumstances of the shipment, the complexity of the Incoterms used, and the capabilities of all parties involved. By carefully considering these factors, you can determine if splitting by Incoterm will be a beneficial approach for your specific situation.
• Based on the above arguments; although not mandatory, but as with regards to process harmonization of business process in Freight Units creations for a variety of Outbound Deliveries scenarios; in my opinion is a "Good Business Practice" and "Good System Practice" to Split/Combine Freight Units by Inco Terms. 
• With Freight Units Split/Combine by Inc Terms then there is also a ONE-to-ONE relationship when Charges are Calculated an Billing Document is created to the Customer.
• The same Considerations argued for "Best Practice to split Outbound Delivery to SD Billing by Incoterms" can therefore be applied to why Freight Units "should" also be split by Incoterms.  

SAP SD - aATP Feature Overview (S/4HANA 2023)

 
Click here to view the Presentation

Q&A in Class (2025-04-09) S4QM1

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: As per requested is the presentation of the Production Parts Approval (PPAP) flow for S4HANA QM.

Answer: Production Part Approval Process (PPAP) includes a set of standard processes that ensures the production process of a material meets your requirements. 

• An essential part is the first article inspection (FAI).
• You enable PPAP in the Manage Quality Info Records app. There you can specify for a material that a first article inspection should take place at goods receipt for one or several purchase order items.

See the following Presentation:
https://docs.google.com/presentation/d/1M7UmZZgfau_rFRWo7jJx0_uR8yYSQSKeUF5IESVNta8/edit?usp=sharing

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Review of the FIORI App RR and UD.

Answer:

See the following presentation:  
https://docs.google.com/presentation/d/1OfztDazkHpRgv-Wc0BBzXdy0KuInDWjW4qmAzzK2Axg/edit?usp=sharing

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: 8D process review.

Answer: In the context of SAP S/4HANA Quality Management (QM), the "8D" refers to the Eight Disciplines problem-solving methodology. This methodology is used to address and resolve internal quality issues within SAP S/4HANA, providing a structured approach to identify, analyze, and resolve problems, while preventing recurrence. 

Here's a breakdown of the 8D methodology within SAP S/4HANA QM:

1. Purpose and Scope:

• The 8D methodology is a standardized approach for problem-solving within SAP S/4HANA QM. 
• It helps in identifying, correcting, and eliminating recurring problems. 
• It is used for both internal and external problem-solving, including those involving suppliers, according to the SAP Community. 

2. 8D Steps in SAP S/4HANA QM:

The 8D methodology in SAP S/4HANA QM involves the following 8 steps, which are implemented through specific apps and functionalities within the system:

1. D1: Form a Team: A team is formed to address the problem.
2. D2: Define and Describe the Problem: The problem is clearly defined and described.
3. D3: Containment: Temporary measures are taken to prevent further occurrences of the problem.
4. D4: Root Cause Analysis: The underlying reasons for the problem are identified.
5. D5: Identify Potential Corrective Actions: Possible solutions to address the root cause are explored.
6. D6: Select and Implement Corrective Actions: The chosen corrective actions are implemented and verified.
7. D7: Preventative Actions: Measures are taken to prevent similar problems from occurring in the future.
8. D8: Final Actions: The team documents the results, learns from the process, and ensures follow-up actions are taken.

See the following link to presentation:

https://docs.google.com/presentation/d/1tuFZfn8Mz1-SEQYwB_w_xpe37pG0gC8U2iMVdRvrF-w/edit?usp=sharing

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Q&A in Class (2025-04-09) S4QM1

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is PPAP (Production Parts Approval) in SAP?

Answer: Production Part Approval Process (PPAP) includes a set of standard processes that ensures the production process of a material meets your requirements. 

• An essential part is the first article inspection (FAI).
• You enable PPAP in the Manage Quality Info Records app. There you can specify for a material that a first article inspection should take place at goods receipt for one or several purchase order items.

See the following Presentation:
https://docs.google.com/presentation/d/1M7UmZZgfau_rFRWo7jJx0_uR8yYSQSKeUF5IESVNta8/edit?usp=sharing

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: S/4HANA RR and UD using FIORI App.

Answer: See the following Presentation:

https://docs.google.com/presentation/d/1OfztDazkHpRgv-Wc0BBzXdy0KuInDWjW4qmAzzK2Axg/edit?usp=sharing

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: How is 8D Methodology implemented in SAP S/4HANA?

Answer: In SAP S/4HANA, 8D problem-solving is a structured methodology used to identify, correct, and eliminate recurring quality issues. It provides a systematic approach to problem-solving, guiding users through eight distinct phases. This approach is particularly helpful in identifying root causes, implementing interim fixes, and developing permanent solutions to prevent future recurrences. 

Here's a breakdown of the 8D methodology in SAP S/4HANA:

1. 1. D0: Plan: This initial phase involves planning the problem-solving process, including defining the scope, setting objectives, and identifying resources. 
2. 2. D1: Use a Team: A cross-functional team is formed, bringing together individuals with relevant expertise to collaborate on the problem. 
3. 3. D2: Define and Describe the Problem: The problem is clearly defined, specifying the who, what, where, when, and how of the issue. 
4. 4. D3: Develop Interim Containment Plan: Temporary measures are implemented to contain the problem and prevent further damage. 
5. 5. D4: Identify and Verify Root Causes: The team investigates the underlying causes of the problem using various root cause analysis techniques. 
6. 6. D5: Develop and Implement Corrective Actions: Permanent solutions are designed and implemented to address the identified root causes. 
7. 7. D6: Verify Corrective Actions: The effectiveness of the implemented solutions is verified to ensure that the problem has been resolved. 
8. 8. D7: Prevent Recurrence: Preventive actions are put in place to avoid future recurrences of the problem. 
9. 9. D8: Recognize the Team: The team is recognized for their efforts and the successful resolution of the problem.

See the following:
https://docs.google.com/presentation/d/1tuFZfn8Mz1-SEQYwB_w_xpe37pG0gC8U2iMVdRvrF-w/edit?usp=sharing

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Q&A in Class (2025-04-10) EWM100

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Depict the process flow again for WT to SLoc RD00 and then to SLoc AF00.

Answer: The EWM inbound delivery process in SAP typically starts with a purchase order being created in the ECC system, which then triggers the creation of an inbound delivery document in EWM. EWM uses this inbound delivery document as a request document for warehouse operations like putaway and staging. The process involves creating warehouse tasks based on the inbound delivery to perform the following flow:

• Unloading from "DOOR" to "GR-ZONE" (SLoc RD00 in MM).
• Move from "GR-ZONE" to "EWM Execution Bins" (for EWM Work Center further processing like Packing, Deconsolidation, Oiling, EWM QM or EWM with External QM etc).
• Move from "EWM Execution Bins" to "Final Storage" (SLoc AF00 in MM).

You can see a pictorial and SAP steps flow in the following Blog Posts: 

https://froggysap.blogspot.com/2025/04/sap-scm-ewm-process-flow-of-ewm-inbound.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question no 4042 : NAST Message Determination Printer Determination

In Material Management as at S/4 1909, which of the following is TRUE about the following Parameter set in the Picture for NAST ? 

(more than one answers)

A. Always select the Printer assigned to the Purchasing Group

B. If Printer not found in the Purchasing Group, then select Printer assigned to the Condition Record of "NEU"

C. If Printer not found in "NEU" Condition Record and no Printer found in the Purchasing Group, then select Printer default at the User Master.

D. If Printer not found in "NEU" Condition Record then select Printer assigned to the Purchasing Group.

E. If Printer not found in "NEU" Condition Record and no Printer found in the Purchasing Group, then no Message can be determined in the Purchase Order

Answer: D, E

In the Configuration screen above, Printer Parameter can be set to Purchasing Group or User Parameter:

If it is set to Purchasing Group:

. 1st try to find Printer in the Condition Record of "NEU"

. 2nd if Printer not assigned to the Condition Record, then select Printer assigned to the Purchasing Group (Header Pur Group)

. 3rd if no Printer is assigned to the Purchasing Group then no Message can be determined

If it is set to User Parameter:

. 1st try to find Printer in the Condition Record of "NEU"

. 2nd if Printer not assigned to the Condition Record, then select Printer assigned to User

. 3rd if no Printer is assigned to the User then no Message can be determined

SAP Technical - Migration Cockpit (First Look of Upload Equipment Master)

CLICK here to view the Presentation

Q&A in Class (2025-04-07) S4SD1

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the Inco term recommendation when using TM for MM Inbound Delivery & SD Outbound Delivery?

Answer: The following is as at S/4HANA 2023:

• As at S/4HANA 2023, The Freight Order in the TM module can be at both Header and Item level but you will have to be very careful of the Integration points between SD and TM and How the Sales Department would perform the Billing for the Product to the Customer vs how the Freight Costs are to be billed to the Customer from the TM module.
• In SAP Transportation Management (TM) Freight Order, Incoterms are typically maintained at the header level, although some functionality might exist for item-level Incoterms in specific scenarios or future releases (from SAP help.sap.com Documentation). 
• It is very important to note that some Organizations prefer to "Split Billing" using the Inco Term as a criteria; so that in One Outbound Delivery with different Delivery items that contain different Inco Terms, the Organization to split the Billing of the Delivery items based on the "Inco Term" which result in One Billing Document only have One Inco Term. (In fact, the "Split Billing" based on Inco Term is really a common practice as Incoterm determines which party (buyer or seller) is responsible for various costs (freight, insurance, etc.) and risks, and these responsibilities are reflected in the Billing Header which would make more sense. 
• As this point in time (as at S/4HANA2023 which is the only version available for Simulations), it is probably a better decision to combine Freight Units (from Outbound Delivery items) that contain the same Inco Term to ONE Freight Order, so that the Freight Order itself matches the intended Billing Document for both Product and Transportation Services. 
• However, if there is a desire to still have Item level INCO terms at both Product Billing and TM Freight Order Billing (which from both business and system aspect may not be a good decision), then it must be tested thoroughly; BUT I personally don't recommend.
  SAP's recommendations statement: "While not strictly mandatory, using the same Incoterms for all freight items within a single S/4HANA freight order can simplify the process and reduce potential errors. However, if different freight items have distinct shipping requirements or contractual obligations, using different Incoterms may be necessary."

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: What is the latest Architecture on S/4HANA with Distributed TM and EWM ? 

Answer: It is of course the "Best" architecture to be using both Embedded TM and Embedded EWM systems; however, for larger Multinational Organizations; there are multiple business and technical reasons for having a Distributed Architecture. 

For example, a Customer using an ECC system already integrated to S/4HANA TM, and the Customer is only using the Classic WM (and not the EWM system); the company also outsourcing some of its Warehouse and Transportation activities to 3rd party in a more complex Warehousing scenario. In an effort to migrate from ECC to S/4HANA may face multiple challenges of security, data management and system performance; one of the decision would be:

• Multiple S/4HANA to One-or-More TM system.
• Link One-or-More TM system to One-of-More EWM system.
• The S/4HANA maybe also integration to some existing SAP SCM APO system until future migration to a possible Embedded PPDS and Cloud-based IBP.

See further presentation in the following Link: 

https://froggysap.blogspot.com/2025/03/blog-post_24.html

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: The importance of knowing which Licensing of specific S/4HANA modules signed with SAP (eg S/4HANA EWM)

Answer: With the most recent news just March.2025, SAP announced the classic LE-WM in S/4HANA no longer supported and all customers "must" move to the StRM (Stock Room Management Solution); customer previously using the Cross-Docking, Basic Yard Management, Wave Picking will be able to use them anymore. AND if the customer business must use CD, YM, and Wave Picking; then, the customer must acquire not just the EWM Basic Licensing version BUT the "Advanced EWM" Licensing where only in this version SAP allow to switch on CD, YM, and Wave Picking. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Question: Is the LE-WM 2-Step Picking is still possible in the S/4 StRM option ? 

Answer: 2-step picking can be part of the WAVE Picking feature in SAP LE-WM. First we have to check the features of both: 

WAVE Picking (LE-WM-TFM-CP):

• Definition: Wave picking is an order fulfillment strategy where orders are grouped into "waves" based on factors like due date, order size, or product availability, and then picked simultaneously instead of individually. .
• Purpose: To improve efficiency and reduce idle time by scheduling picking activities around common factors, such as shipping deadlines.    
• SAP: VL35 facilitates the creation of "wave picks," which are essentially work packages for picking, grouping deliveries that are to be processed at roughly the same time. 
• Example: Grouping orders with the same shipping date or destination into a single wave

2-Step Picking: 

• Definition: A picking process divided into two steps: a withdrawal step (collectively picking products for multiple deliveries) and an allocation step (distributing the picked products to individual orders).
• Purpose: To optimize picking processes, especially in warehouses with intermediate storage areas or high racks, by minimizing travel distance and picking operations.
• SAP: Use transaction code LT72 to determine the two-step picking process for a group, and LT0E to create transfer orders for the group.
• Example: Picking all the required quantity of a product for multiple deliveries in the first step, then allocating those products to the specific orders in the second step. 

StRM (Stock room management) allows you to use almost all LE-WM functions except the list below:

• Task & Resource Management (LE-TRM),
• Value Added Service (LE-WM-VAS),
• Yard Management (LE-YM),
• Cross-Docking (LE-WM-CD),
• Wave Management (LE-WM-TFM-CP),
• Decentral Warehouse Management (LE-WM-DWM),
• Warehouse Control Unit Interface (LSR)

The next question to determine is that did SAP park the 2-Step Picking feature under the Wave Management (LE_WM-TFM-CP. 

However it doesn't mean that the transactions will vanish. They are there in S/4HANA and will be there. You are just not entitled to use them in S/4HANA anymore.

You can use the STOCKROOM_COMPLIANCE_CHECK report to check if your usage is within the stock room management limitations 

See SAP note: 

• SAP Notes 2881166 - SAP is not planning to invest in Stock Room management, strategic product for SAP is EWM.
• SAP Notes 2882809 - Scope Compliance Check for Stock Room Management.
• SAP Notes 2270211 - WM is still part of S/4HANA but in a compatibility mode. 
• SAP Notes 2269324. With the compatibility mode SAP allows customers to migrate their existing solutions smoothly into S/4HANA.
• SAP Notes 2577428 - SAP also restricts the usage of components which are in a compatibility mode till 31.12.2025.
• SAP Note 2269324 -  titled "Compatibility Scope Matrix for SAP S/4HANA," provides a detailed overview of the compatibility scope, including information on available alternative functionality, license material numbers, and business impact notes for each compatibility scope item, helping customers plan their transition to SAP S/4HANA. 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------