Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

 Community  Topics  Answers  Blogs  Events  Programs  Resources  What's

 Community  Topics  Answers  Blogs  Events  Programs  Resources  What's New    Home  Community  Blogs  Ask a Question  Write a Blog Post  Login / Sign-up Product Information Yunus Yucesoy Posted onAugust 27, 2019 13 minute read Basic Settings for SAP EWM in SAP S/4HANA 1809 FollowRSS feedLike 18 Likes 18,296 Views 5 Comments This blog post is updated version of previous blog post Basic Settings for SAP EWM in SAP S/4HANA 1709, please check previous blog post for SAP S/4HANA 1709 and 1610. This blog post is not valid for Decentralized EWM on SAP S/4HANA Use Cases 1. If you use a SAP S/4HANA 1809 system with Best Practice activated but without using the SAP Extended Warehouse Management for S/4HANA, and you want to add the Best Practice for the SAP EWM in SAP S/4HANA to an existing plant, this blog lists all the required Best Practice Org data and guides you to expedite the Basic Settings process so that you don’t need to research for the input data. 2. If you use a SAP S/4HANA 1809 system, and you want to add the SAP EWM in SAP S/4HANA to a new or an existing plant, you replace the Best Practice Org Structure in this blog with your own and complete the basic settings by following the example. 1 Basic Settings for SAP EWM in SAP S/4HANA SAP provides a copy of “Getting Started Guide – Basic Settings for SAP EWM in SAP S/4HANA” in the attachment of SAP Note 2668150 – SAP S/4HANA 1809: Release information and restrictions for EWM in SAP S/4HANA SAP Note has file “BasicSettings_EWMinS4_V01.pdf”. This blog provides step-by-step screenshots based on the guide and the Best Practice Org structure. SAP EWM in SAP S/4HANA Best Practices SAP EWM in SAP S/4HANA provides the following 11 scope items in the Best Practice content, and this blog shows the basic settings needed for these Best Practices. For each scope item, more functional related configurations are needed. Refer to rapid.sap.com for the required Building Blocks for each scope item. Scope Item Description License 1FS Basic Warehouse Inbound Processing from Supplier Basic 1FU Initial Stock Upload for Warehouse Basic 1FW Physical Inventory in Warehouse Basic 1FY Replenishment in Warehouse Basic 1G0 Scrapping in Warehouse Basic 1G2 Basic Warehouse Outbound Processing to Customer Basic 1V5 Warehouse Inbound Processing from Supplier with Batch Management Basic 1V7 Warehouse Outbound Processing to Customer with Batch Management Basic 1V9 Basic Warehouse Inbound Processing from Supplier with Quality Management Basic 1VB Production Integration – Component Consumption and Receipt in Warehouse Basic 1VD Advanced Warehouse Outbound Processing to Customer Advance 2 Configuration of qRFC Communication 2.1 Background Information About System Landscape Settings The system landscape entities in the following table is based on a single SAP S/4HANA sandbox system, which has system ID BES and Client 300. If you need to setup the system landscape for a distributed system landscape, e.g., with customizing, test, and production system, see Section 2.1 in the guide pdf file. System Landscape Entity Example Comments RFC Destination BESCLNT300 Exists in your SAP S/4HANA system already, see Section 2.2 below Logical Systems BESCLNT300 Exists in your SAP S/4HANA system and assigned to Client 300 already Dummy Logical System BESEWM300 To be created by the Implementation Tool for System Connection, see Section 2.4. Business System Group BG1 BG1 To be created by the Implementation Tool for System Connection, see Section 2.4. Business System S4H_001 BES_300 To be created by the Implementation Tool for System Connection, see Section 2.4. 2.2 Technical Prerequisites for qRFC Communication The RFC Destination and RFC Connection BESCLNT300 should be in the existing SAP S/4HANA system already. You need to test the RFC Connection to confirm that the connection is working via transaction SM59 by clicking on the Connection Test button. 2.3 Creating Dummy Logical System Manually The Dummy Logical System for EWM will be created automatically by the “Implementation Tool for System Connection” in Section 2.4. 2.4 Configuring qRFC Communication and Client Settings You use this procedure to configure the following data with the help of the “Implementation Tool for System Connection” in SAP EWM in SAP S/4HANA:  System landscape settings for qRFC communication. · Basic number ranges (on client level) in SAP EWM including packaging specifications and shipping and receiving activities · Warehouse-independent basic settings using BC Set activation within the tool You follow the following steps to use the “Implementation Tool for System Connection”. 1. In Customizing for Extended Warehouse Management, choose Interfaces → ERP Integration → Tool-Based ERP Integration → Implementation Tool for System Connection, click on the IMG node execution icon. 2. The following pop-up window opens. 3. Select “Display Quick Help” to display input field information. 4. Enter a Data Set name (W001) and its Description (W001). The system uses the name of the data set to store your data input. 5. Select an existing transport Request/Task or create a new one to store all the configurations made during the Activation step. 6. Click on the “Next >” button to go to Step 2 “Use Cases”, and select the “Configuration EWM in the current system” radio button. 7. Click on the “Next >” button to go to Step 3 “System Settings”, review the system proposed entries, and enter new values if the fields are blank. 8. Click on the “Next >” button to go to Step 4 “Number Ranges”, if you need to setup your own number ranges, select “Skip creation of number ranges”. The number ranges will be created by the system in this blog. 9. Click on the “Next >” button to go to Step 5 “Activation”. Enter the Request/Task, and click on “Activate” button. You could export the details of the activation content by clicking the Export button. 10. The activation is executed in the background. 11. Click on the “Next >” button to go to Step 6 “Activation Logs” after the completion of Activation. Check the logs for any error messages. The same log could be found in transaction SLG1 under object /SCWM/WME and sub-object IMPL_TOOL. 12. You have successfully executed the Implementation Tool for System Connection. 3 Warehouse Creation and Integration into the Enterprise Structure 3.1 Background Information About Warehouse Integration The Best Practices for US Localization version for SAP EWM in SAP S/4HANA requires the following org structure. For other country localization, replace the 17 prefix by your country number. For example, instead of Plant 1809 for US, use 1010 for Germany, 2910 for Canada, 1310 for China, 3010 for Australia, etc. Org. Master Data Value Master Data Description Comments Company Code 0001 Company Code 0001 S/4HANA Object Org. Master Data Value Master Data Description Comments Purchasing Organization 0001 Purch. Org. 0001 S/4HANA Object Plant PL01 Plant 1 US (or your description) S/4HANA Object Storage Location ROD EWM ROD S/4HANA Object Storage Location AFS EWM AFS S/4HANA Object ERP Warehouse Number W01 W01 WM Warehouse for EWM (or your description) S/4HANA Object Receiving Point 0001 Shipping Point 0001 S/4HANA Object Supply Chain Unit SCU-W001 SCU Warehouse W001 EWM Specific Objects in S/4HANA EWM Warehouse Number W001 EWM W001 EWM Specific Objects in S/4HANA Custodian BPW001VC BPW001VC S/4HANA Object Entitled to Dispose BPW001VC BPW001VC S/4HANA Object Goods Receipt SCU-W001 SCU for Warehouse W001 EWM Specific Org. Master Data Value Master Data Description Comments Office Objects in S/4HANA Shipping Office SCU-W001 SCU for Warehouse 0001 EWM Specific Objects in S/4HANA 3.2 Prerequisites for Warehouse Integration Plant PL01 should have been already created in your system and an active material ledger for the valuation area has been assigned to Plant PL01. If your plant doesn’t exist, create it and set active material ledger for your plant, see Section 3.2 in file “BasicSettings_EWMinS4_V01.pdf”. You have to perform the following manual configuration before you could use the automated configuration tool in Section 3.4. 1. Create storage locations AFS and ROD in plant PL01. Customizing Path: Enterprise Structure → Definition → Materials Management → Maintain storage location. 2. Create a business partner BPW001VC with predefined roles FLCU00 (FI Customer) and FLCU01 (Customer)Transaction BP Select create Organization icon, and enter name, Country, Language, and Save To add the FLCU00 BP role under the change mode, select the FLCU00 BP role, enter address, and Save. To add the FLCU01 BP role, under Change mode, select the FLCU01 BP role and save. You need to link the customer BPW001VC to Plant PL01 via Customizing Path: Materials Management → Purchasing → Purchase Order → Set up Stock Transport Order → Define Shipping Data for Plants. Enter BPW001VC in the Customer No. – Plant field. 3. Add FLVN00 (FI Vendor) and FLVN01 (Vendor) to BPW001VC Use transaction Code BP to change BPW001VC. Add FLVN00 BP role to Business Partner BPW001VC, and save. Add FLVN01 BP role to Business Partner BPW001VC, and save.You need to link BPW001VC as the supplier to Plant PL01. In the BP transaction change mode, select the FLVN01 Supplier role, under the uploads/Management/ ewm-guide.pdf