Topic Covered -

• EWM Embedded System Development Progress
• Warehouse Number Creation and Assignment
• Supply Chain Unit Master Data Creation
• Creating Business Partner as Custodian
• SAP EWM Custodian and Ship-to Party
• Warehouse Number Range Setup Discussed
• S/4HANA and EWM Integration Setup
• EWM System Configuration and Batch Management
• Data Flow Between S/4 and EWM
• S/4 and EWM Integration Setup

Summary

Ewm Embedded System Development Progress

In the meeting, PLN discussed the ongoing development of the Ewm embedded system, focusing on the interface between the two systems. PLN also explained the company's structure, including its manufacturing plants in California and Dallas, and its corporate office in New York. The discussion also covered the creation of a dummy warehouse and the mapping of Ewm warehouse numbers. PLN emphasized the importance of supply chain in it, custodian, default party entitled, and ship to party in the warehouse number creation process. PLN also mentioned the need to create a business partner as a custodian and the importance of assigning a supply chain in it. The conversation ended with PLN logging into the SAP system to demonstrate the configurations.

Warehouse Number Creation and Assignment

PLN discussed the process of creating a warehouse number and assigning it in the SAP system. He emphasized the importance of using a best practice system, either 1710 or 001, and the need to create a new request number for each warehouse. PLN also explained the role of the supply chain in it and the custodian default party in the warehouse setup. He demonstrated how to create a supply chain using the transaction SCU and how to assign it to a warehouse. PLN also mentioned the importance of defining business attributes for the supply chain to avoid errors in delivery. He concluded by explaining how to create a new supply chain using the transaction SCU and how to assign it to a warehouse.

Supply Chain Unit Master Data Creation

PLN explains how to create and manage supply chain unit master data, emphasizing that this data must be created separately in development, quality, and production systems as it cannot be transported between them. He demonstrates how to set up a business partner as a custodian, starting with creating a business partner using transaction BP and selecting the appropriate business grouping. PLN notes that coordination with MM team is important for determining the correct business partner configurations and functions. He also explains that the supply chain unit provides geographical location information for warehouse numbers and is essential for creating deliveries.

Creating Business Partner as Custodian

PLN discussed the process of creating a business partner as a custodian. PLN explained that the custodian's address and warehouse number usually remain the same, unless specified otherwise. PLN also mentioned that the language should be English, and the custodian's phone number and email address are not necessary. PLN then demonstrated how to extend the business partner to a supplier, using the role of 'Flv Ngs supplier' or 'accounting'. PLN also explained the importance of selecting the correct purchasing organization and the process of creating a vendor. PLN emphasized that the process is the same for any person to be created, and that the business partner number and vendor number will be the same. PLN also mentioned that the account grouping under business grouping will be explained later. PLN concluded by stating that the process is not mandatory, but can be done for practice purposes.

SAP EWM Custodian and Ship-to Party

PLN explains how to create and configure a custodian and ship-to party in SAP EWM, which is a one-time setup activity for each system environment. The custodian is created as a business partner with a plant assignment and acts as a warehouse representative, while the ship-to party is configured to handle delivery addresses and packing information. Sridhar asks about grouping flexibility for custodians, and PLN confirms there are no specific requirements but advises checking what grouping is used in the actual project. The session concludes with copying warehouse customizing settings from the best practice system (001) to their warehouse number (997) to reduce configuration effort.

Warehouse Number Range Setup Discussed

The team discusses setting up number ranges for various warehouse operations in EWM. PLN explains that number ranges need to be created for warehouse tasks, documents, waves, warehouse orders, consolidation groups, value-added services (VAS), and physical inventory. They set up specific number ranges for warehouse 997, ensuring the ranges are large enough to accommodate tasks for many years without running out. PLN emphasizes that while different warehouses can have different number ranges, they can also share the same ranges as the system links each number to its specific warehouse. The number ranges are assigned to the warehouse number along with a factory calendar setting, which should match the country where the warehouse operates.

S/4hana and EWM Integration Setup

The discussion covers the integration setup between S/4HANA and Extended Warehouse Management (EWM) systems. PLN explains that the basis team needs to enable several technical parameters including RFC settings, logical systems, and business systems. The integration process involves mapping dummy warehouse numbers between S/4 and EWM, assigning storage locations to availability groups (with one availability group per storage location), and configuring basic EWM linkage settings. PLN emphasizes that while this is demonstrated in an embedded system, the same process applies to decentralized landscapes.

EWM System Configuration and Batch Management

The discussion covers the setup of extended warehouse management (EWM) system configuration. The speaker explains that deliveries from the S/4 system should be immediately distributed to the EWM system, but only after being checked for data accuracy. They discuss batch management functionality, which is particularly important for industries like pharmaceuticals and food manufacturing, where products are produced in batches with unique identifiers for traceability. The speaker also covers goods receipt from EWM for production integration, queued and serialized communication between systems, and delivery change permissions, emphasizing that careful consideration is needed when allowing delivery changes after processing has begun in the warehouse.

Data Flow Between S4 and EWM

PLN discussed the data flow between the S4 and EWM systems, emphasizing the importance of understanding the roles of each system. PLN explained that the S4 system is the sender and the EWM system is the receiver, and that the data flow between them is crucial for efficient operations. PLN also highlighted the need for a detailed log of any errors or issues that may arise during the data flow process. PLN further discussed the importance of enabling the connection test feature in the quality system, but not in the production system, as it could impact performance. PLN also explained the process of checking the connection between the S4 and EWM systems using the SM59 transaction. PLN concluded by emphasizing the need for a dedicated team to monitor and clear the queues in the system on a daily basis.

S4 and EWM Integration Setup

PLN discussed the integration setup between the S4 and EWM systems, emphasizing the importance of understanding the technical aspects. He explained the process of creating a material in the S4 system and extending it to the EWM system, highlighting the role of the business system grouping. PLN also demonstrated how to generate a distribution model to ensure that deliveries, outbound deliveries, and manufacturing orders are distributed from the S4 system to the EWM system. He shared a document detailing the steps to be followed for the ERP to EWM integration setup. PLN also clarified the concept of 'no aggregation' for system communication with single queues, explaining that it ensures each delivery creates a separate queue. The team agreed to continue discussing the topics in the next session.