Requirement: Synchronous posting from EWM2S4 are generally required because of following reasons.

• Avoid hanging queue from EWM2S4
  
• Avoid stock inconsistencies between EWM & S4
  
• Real time storage location extension during posting from /SCWM/ADGI( GM code=04, NWLO from EWM to non-EWM storage location).

Logic of Synchronous Posting from EWM2S4: Activation at warehouse level( SPRO–>Extended Warehouse Management–>Interfaces–>Goods Movements–>Activate Synchronous Goods Movement Posting)

/SCWM/CL_ERP_GOODSMVT_SYNC_S4 is the maintain service class for synchronous posting from EWM2S4.

Two important methods play a pivotal role for synchronous posting

/SCWM/IF_ERP_GOODSMVT_SYNC~SIMULATE_POSTING–> This method checks the corresponding S4 Data like sufficient stock availability or even master data extension like ‘material is extended to storage location or nor in real time to avoid hanging queues and display of error at ‘UI Level’ at 10 EWM relevant transaction.

IS_GM_CODE_ALLOWED: This is the main method displaying the EWM relevant transaction meant for Synchronous posting from EWM to S4. There are total relevant processes, the blog will highlight the /SCWM/ADGI synchronous capability only from EWM to S4.

Below example is moving a Material from EWM managed to IM managed storage location using /SCWM/ADGI, GM Code=4)

System does the real time storage location extension check instead of posting and creating a hanging queue( If No Auto Sloc creation is enable in 411 Mvt type in S4).

The class /SCWM/CL_ERP_GOODSMVT_SYNC_S4 with method /SCWM/IF_ERP_GOODSMVT_SYNC~SIMULATE_POSTING performs all relevant synchronous posting simulation before posting goods movement. In below example, a real time stock availability check is performed during a Material movement from EWM to IM managed storage location.

Similarly all relevant synchronous posting can be conducted from EWM2S4 with below transaction as well which are mentioned

• Difference analyzer(/SCWM/DIFF_ANALYZER)
  
• Difference analyzer(/DIFF_ANA_CAT_CHG)- Stock category change during posting.
  
• Initial Stock upload( /SCWM/ISU)
  
• Posting change ( /SCWM/POST )
  
• /Unplanned Goods Issue( /SCWM/RGI_SCRAP)- /SCWM/ADGI
  
• Stock type change report( R_STOCK_TYPE_CHANGE )
  
• monitor posting change via ‘BBD/SLED Overview’—>MON_DDATES_PC’,
  
• monitor posting change via ‘Physical Stock–> ‘MON_PHYSTO_PC’,
  
• Consumption against PMR- ‘MFG_GI’,
  
• Goods Movement Kanban Staging task Wbse to PSA- TO_KANBAN’,

All relevant information replicated is based on my personal experience and insight. Relevant tests have been performed in S/4 HANA 2023 FPS02 system.

The post Which Synchronous Posting is enabled from EWM to S4 & relevant Service Class for posting appeared first on ERP Q&A.

The purpose of this blog post is to show the configuration steps needed to perform printer determination based on warehouse door during inbound receiving.

Scenario: Lets take an example of a warehouse which has two inbound doors DOR1 and DOR2. Both have a unique printer attached to them. DOR1 is linked to printer YEP1_17 and DOR2 is linked to printer LP01.

Configuration:

1) Define Print Profiles for Delivery Processing:

SPRO IMG > EWM > Goods Receipt Process > Inbound Delivery > Print > Define Print Profiles for Delivery Processing

2) Define Print Profile Determination for Goods Receipt Process

SPRO IMG > EWM > Goods Receipt Process > Inbound Delivery > Print > Define Print Profile Determination for Goods Receipt Process

3) Activate PPF /SCWM/PDI_01_UNLOAD_LIST_PRINT (Transaction SPPFCADM)

4) Setup condition record to trigger printing upon inbound delivery creation in EWM (Transaction /SCWM/DLVPPFC)

5) Ensure that the printer in transaction SPPFCADM -> Condition Configuration (Transportable Conditions) is cleared. This is mandatory to inform the system to determine printer based on configuration

Testing:

1) Inbound Delivery received at door DOR1. PPF action is triggered upon inbound delivery creation and spool generated for printer YEP1_17

2) Inbound Delivery received at door DOR2. PPF action is triggered upon inbound delivery creation and spool generated for printer LP01

Note: – The above scenario has been executed on S4 Hana embedded EWM 2022 sandbox.

The post Printer Determination based on warehouse door during EWM Inbound Receiving appeared first on ERP Q&A.

You can use the Advanced Returns Management component in SAP ERP with SAP Extended Warehouse Management (SAP EWM) to manage returns items on storage bin level. The inspection of returns items is fully supported by the Quality Management (QM) component of SAP EWM. This integration improves the efficiency and transparency of the returns process.

In this blog I would like to compare 2 scenarios of ARM integration with EWM in comparing with Customer Returns process without ARM as listed below.

• Customer Returns Process without ARM
  
• ARM integration with EWM Process – Inspection occurs in ERP
  
• ARM integration with EWM Process – Inspection occurs in EWM

The testing version is S/4 HANA 2020 – EWM Decentralized.

Process Flow

Explain ERP Storage Location maps with EWM Warehouse Avail.Grp

Before we get into detail of each process, let’s have a look of current mapping between SAP ERP Storage Location and Warehouse Availability Grp & Stock Type as below.

We manage returns stock in ERP Sloc RETR firstly after receiving, upon inspection decision we will transfer stock to normal Sloc GRCV or Scrapping Sloc SCRP. And in EWM we have mapping Stock type for each Sloc. Try to keep the process simple so we only have 1 Stock type (F4/F9) per Avail.Grp for Returns & Scrapping.

Customer Returns Process without ARM

In this scenario, we assume that Inspection will be manage outside SAP and decision to change stock type after Inspection have to be done manually.

ARM integration with EWM – Inspection occurs in ERP

In this scenario, Inspection happens in ERP and inspection result is sent from ERP to EWM.

ARM integration with EWM – Inspection occurs in EWM

In this scenario, Inspection happens in EWM and inspection result is sent from EWM to ERP.

Testing

Because the limitation of my current EWM system setting, I can only describe the testing for scenario ARM – Inspection occurs in EWM with 2 Cases: Inspection Decision Accepted & Inspection Decision Rejected/Scrapping.

The testing for scenario ARM integration with EWM – Inspection occurs in ERP – You can reference to another blog that I attach the link in the Reference part.

Prerequisites

You have made the following settings in Customizing for Extended Warehouse Management:

• You have separated the posting of a decision and follow-up action and canceled an inspection under Cross-Process Settings -> Quality Management Basics -> Warehouse-Dependent Activation for Inspection Object Types.
• You have made the basic settings for inspection rule (master data) creation under Cross-Process Settings -> Quality Management -> Settings for Inspection Rules.
• You have defined a code group MSRDEC with assignment of allowed decision and follow-up codes (this has to be synchronized with SAP ERP) under Cross-Process Settings -> Result.
• You have set up QM for the sending and receiving locations under Cross-Process Settings -> Quality Management.
• You have maintain QM Inspection Rule under Q-Inspection Returns Tcode /SCWM/QRSETUP

ARM – Inspection occurs in EWM Process Flow Testing

Step 1: ERP Create Returns Sales Order

Tcode: VA01

Returns Sales Order is created with Follow-Up Action is “Receive into Plant” and Refund Control “Standard by credit memo request”.

Step 2: ERP Outbound Delivery is created.

Tcode: VL10A

Outbound Delivery is created reference to Returns Sales Order, and receiving Sloc is RETR – Returns.

ERP – Check Customer Returns Overview – Tcode MSR_TRC_C

At this stage when Return Delivery is created, you can see Delivery number is updated in the Returns Steps and marked as Green – Completed, next step is GR marked blue as not yet process.

Step 3: EWM Inbound Delivery is replicated, Post GR

Tcode: /SCWM/PRDI

EWM Inbound Delivery is replicated and stock supposed to be posted in F4 – Returns stock type and keep in QI-ZONE.

Post GR and GR status is completed.

ERP – Check Returns Overview

After GR posted in EWM, it sends update to ERP and Goods receipt movement is created and marked as Green – Completed, next step is Inspection.

Display GR Document, it’s posted with Mvt653 and to Sloc RETR.

Step 4: EWM Inspection

Tcode: /SCWM/QINSP

There are 2 Items in Delivery, I will set Item 10 – Material A as Inspection pass and Item 20 – Material B as Inspection fail, then we can compare the difference.

Item 10 – Perform Inspection Decision: Accept – Quality check passed.

First step to create new HU because current HU is the dummy one. Then choose the Decision as 0001 – OK, Accepted; and assign Dest. HU as new created HU.

Note the Inspection Type before making Decision is A.

Save the inspection decision and you can see Inspection Type changed to C now. You can mark Completed Process Step for HU if storage processes related.

EWM – Stock Overview: Material A is updated as F1 – Goods in Putaway.

ERP – Check Returns Overview

Inspection result is sent from EWM to ERP and updated in Returns Steps. Here Inspection result and Transfer Posting are marked Green – Completed. Next step in ERP is to create Credit Memo.

Display ERP Inspection, Follow up Activity is “Transfer to Free Available Stock”.

Display Transfer Posting, it transfers from Sloc RETR to GRCV.

Item 20 – Perform Inspection Decision: Reject/ Scrapping – Quality check failed.

First step to create new HU, then choose the Decision as 0003 – Scrapping and assign Dest. HU as new created HU. Note that Inspection Type change from A to C after Save Inspection result.

EWM Stock Overview, stock type is changed F4 -> F9.

ERP – Check Returns Overview

Inspection result is sent from EWM to ERP and updated in Returns Steps. Here Inspection result and Transfer Posting are marked Green – Completed.

Display ERP Inspection, Follow up Activity is “Transfer to Specified Stock”.

Display Transfer Posting, it transfers from Sloc RETR to SCRP.

Step 5: EWM Create Warehouse Task for Putaway & Confirm WT

This step is managed in EWM to finish EWM putaway step and has no impact to further Credit Memo step in Returns process in ERP, means Credit Memo step can happen in parallel.

Create WT as Follow-On Function in Inbound Delivery and confirm WT as normal.

EWM – Stock Overview: After Putaway Material A to Normal Rack, Stock type change F1 -> F2; Putaway Material B to Clearing Zone for scrapping, Stock type has no chance.

Step 6: ERP Process Credit Memo & Payment

Those steps belong to Accounting department which I don’t get in detail. Statuses are updated in Returns Overview as well.

The post EWM – ARM Advanced Returns Management integration with EWM appeared first on ERP Q&A.

How we are going to achieve this? What are the options available.

To achieve the above requirement, following steps needs to be followed

1. Storage type configuration

2. WPT configuration

3. Put away strategies

4. Product Master

5. Testing

1. Storage type config in which destination should not be determined

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Master Data – Define Storage Types

In storage type in the put away control section select WT GENERIC as 2-Only Storage Type, that means when-ever our put away strategy search for the storage type, section and bin it will search till storage type only so that user can put away the material what ever the bin he wants to put away in that particular Z030 Storage type.

2. WPT config for put away

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Cross Process Settings – Warehouse Task – Define Warehouse Process Type

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Cross Process Settings – Warehouse Task – Determine Warehouse Process Type

3. Put away strategies

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Define Put away Control Indicator

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Define Storage Type Search Sequence for Put away

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Assign Storage Types to Storage Type Search Sequence

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Goods Receipt Process – Strategies – Storage Type Search – Specify Storage Type Search Sequence for Put away

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Master Data – Activity Areas – Define Activity Areas

IMG Path: SCM Extended Warehouse Management – Extended Warehouse Management – Master Data – Activity Areas – Assign Storage Bins to Activity Areas

4. Product Master (/N/SCWM/MAT1)

5. Testing:

1. Create Purchase order (ME21N)

2. Create Inbound Delivery (VL31N)

3. /N/SCWM/PRDI

Unloading and GR in /N/SCWM/RFUI

Hit Enter

click on F3-New HU

Scan the destination bin and hit Enter

Put away by HU in /N/SCWM/RFUI

Hit Enter

You can see in the above picture; the destination storage bin is blank. User Enter storage bin where he wants to Put away.

Put away is done.

The post Determine Storage bin Blank while Put away-SAP EWM appeared first on ERP Q&A.

Serial number profile plays a important role in the warehouse to track the material by serial number

The purpose of this blog is to configure the serialization for the material at Document level, Warehouse level and Inventory management level

In EWM serial number are maintained at three levels.

1. Serial numbers for document items: Serial number requirement only at document level either in inbound ‘or’ out bound. Very useful for customer return process.

2. Serial numbers at the warehouse level: Serial numbers are required for all goods receipt/issue and are maintained at the warehouse level. Visibility only at warehouse level, not at storage bin level.

3. Serial numbers in IM: Storage bin level visibility available and serial number become a quant parameter. Required to use serial number for every movement in warehouse

Configuration:

Serial Number Profile: Two independent serial number profiles are required in ERP, one is for logical execution system (LES) and other one is for EWM integration.

LES relevant serial number profile maintained in material master ‘Sales General/Plant view’. EWM relevant serial number profile maintained in ‘WM Execution view

ERP settings:

LES Serial number profile.

IMG-Logistics Execution-Shipping-Basic Shipping Functions-Serial Numbers-Determine Serial Number Profiles

EWM relevant serial number profile:

Img- Integration with Other SAP Components- Extended Warehouse Management – Additional Material Attributes- Attribute Values for Additional Material Master Fields- Define Serial Number Profile

1) Serialization at document level

Create a Material: 5066399

Under ‘Sales/General Plant’ View – Under ‘WM Execution’ view

2) Serialization at warehouse level

Create a Material: 5066400

Under ‘Sales/General Plant’ View – Under ‘WM Execution’ view

3) Serialization at Inventory Management level

Create a Material: 5066405

Under ‘Sales/General Plant’ View – Under ‘WM Execution’ view

EWM Settings

Define serial number profile: IMG- SCM Extended Warehouse Management- Extended Warehouse Management- Master Data-Product- Define Serial Number Profiles-Define Warehouse Number Independent Serial Number Profiles

1) Document level

2) Warehouse level

3) Inventory Management level

IMG- SCM Extended Warehouse Management- Extended Warehouse Management- Master Data-Product- Define Serial Number Profile-Define Warehouse Number-Dependent Serial Number Profiles

Note: if both WHN dependent and WHN independent serial number profiles assigned for any WHN, system prioritize WHN dependent serial number

1) Document Level

2) Warehouse level

3) Inventory Management level

IMG- SCM Extended Warehouse Management- Extended Warehouse Management- Master Data-Product- Define Serial Number Profiles Serial Numbers:

Settings for Warehouse Number

Do the CIF and then maintain at Warehouse Level in Product Master

1) Document level-5066399

Check the storage tab in warehouse level product master whether serial no profile is displayed or not

2) Warehouse level-5066400

Check the storage tab in warehouse level product master whether serial no profile is displayed or not

3) Inventory Management level-5066405

Check the storage tab in warehouse level product master whether serial no profile is displayed or not

1) Test Scenario for Document level:

We have created purchase order for the material 5066399

Create inbound delivery with T-code vl31n and distribute the delivery to wms

At EWM Tcode:/N/SCWM/PRDI

Check At item level serial no req A:doc level is automatically triggering or not

In IBD, if we are not entering the serial numbers then at the time of task confirmation error message will come.

Click on inbound delivery at header level-follow on functions-Create a warehouse task

Confirm the warehouse order

Check the monitor

Go to stock and bin check the physical stock for the material 5066399

Go to inbound delivery-inbound delivery item-give the product and serial number then click on execute

Here the product and serial number is available in 1000003762

2) Test Scenario for Serialization at warehouse level:

We have created purchase order for the material 5066400

Create inbound delivery with T-code vl31n and distribute the delivery to wms

Here serial numbers should be given at the time of inbound delivery creation

Go to extras at the header level select the serial numbers and assign the numbers and save it.

Go to EWM System inbound delivery Tcode:/N/SCWM/PRDI

Check At item level serial no req B:Warehouse level is automatically triggering or not

Here automatically serial numbers will be displayed

Click on inbound delivery-follow on functions-Create a warehouse task

Confirm the warehouse order

To check go to monitor

Go to stock and bin check the physical stock for the material 5066400

To check serial number go to stock and bin-click on serial number on warehouse level-enter product -click on execute

We can see serial numbers at warehouse level

3) Test Scenario for Inventory Management level:

Create a Purchase order for the material 5066405

Create inbound delivery with T-code vl31n and distribute the delivery to wms

Go to EWM System inbound delivery Tcode:/N/SCWM/PRDI

Check At item level serial no req C:Inventory Management level is automatically triggering or not

In IBD, if we are not entering the serial numbers then at the time of task confirmation error message will come.

Click on inbound delivery-follow on functions-Create a warehouse task

Confirm the warehouse order

Go to monitor

Go to stock and bin check the physical stock for the material and provide storage bin and click on

execute

Here, serial number tracking possible at storage bins level

The post Configuration of Serial Number Management in SAP EWM appeared first on ERP Q&A.

Nowadays, SAP S/4 HANA is taking up rapidly, many companies face the challenges while deciding right SAP EWM solution for their businesses. This blog carries the functional information between SAP S/4 HANA EWM deployment options and will help you to decide right EWM solution which depends on enterprise structure, current system landscape, future automation plan and cost etc.

Objective:

The objective of this blog is to get clear understanding of SAP S/4 HANA EWM deployment options to Customer’s, Consultant’s, and partner. Also, this article contains few important point’s which are needs to take into consideration while choosing the EWM deployment option. All the information is based on latest releases of SAP S/4 HANA EWM.

Deployment Options:

EWM can be used in two different deployment modes of SAP S/4HANA systems:

Embedded EWM on SAP S/4HANA

Decentralized EWM on SAP S/4 HANA

1. Embedded EWM on SAP S/4 HANA:

Which integrates only with the local ERP storage locations, is available in two license versions:

i. Basic EWM: SAP offers the Basic EWM application component with default S/4 Hana license.
ii. Advance EWM: To avail the advance functionalities additional licensing required.

Benefits with SAP S/4 HANA Embedded EWM

• Embedded EWM reduced data replication as Business Partner data, Material Master Data, Batch Master Data does not need to be replicated. It can be directly access from S/4 HANA ERP.
  
• Core Interface (CIF)is not required to be used anymore.
  
• Transactional data like Purchase Order data or production order data can be read directly.
  
• Elimination of the use of additional documents like outbound delivery.
  
• SAP S/4 Hana ERP and SAP EWM can run on same landscape.
  
• It has simplified system structure compared to decentralized option.
  
• Embedded S/4 HANA EWM reduce the total cost as the license of basic EWM functionality is included in the SAP S/4HANA ERP license.

Data Transfer between SAP S/4 HANA & Embedded EWM

Main functionality difference between Basic EWM and Advance EWM.

Limitations with SAP S/4HANA Embedded EWM.

• With this option, it is not possible to integrate with storage locations in other SAP ERP systems.
  
• The solution is not very adaptable with multiple warehouses or with large MFS system traffic.
  
• It cannot keep operational in case of ERP system down.

2. Decentralized EWM on SAP S/4 HANA:

With this deployment option, SAP EWM is deployed on a separate server platform and connected to SAP S/4 HANA system using RFC’s and CIF. Decentralized EWM on SAP S/4HANA is released for integration with SAP ERP system and SAP S/4HANA system (with ERP role).

Decentralized EWM cannot integrate to local ERP storage locations but can integrate to ERP storage locations of other clients or other systems, is available in one license version.

Decentralized EWM system can handle a higher volume of transactions and since this is on a different instance, system performance of other processes is not impacted.

This deployment option is highly capable to handle high performing material flow systems, big size warehouses and other automation.

Benefits with SAP S/4 HANA Decentralized EWM.

• It has ability to handle big size volume of transactions.
  
• It can keep operational even if the ERP system is down.
  
• It has ability to handle the multiple warehouses on same landscape.
  
• It has better ability to support automatic warehouses (Integration with MFS, ASRS)
  
• Both systems can be upgraded without impacting each other.
  
• It can connect to multiple ERP systems.

Data Transfer between SAP ERP & Decentralized EWM.

While implementing SAP EWM customers’ needs to know which SAP EWM deployment option should be chosen and why? It can be decided on some of the questions mentioned below.

• What is total volume of transactions data at present in all warehouses?
  
• What will be the total volume of transactions will be increased in future?
  
• How many warehouses are at present on system and what is future expansion plan?
  
• What is effect of total cost?
  
• What is cost of investment?
  
• What is present level of warehouse automation?
  
• What is future warehouse automation plan?
  
• What is future plan about system upgrade?
  
• Is existing IT infrastructure capable to handle Embedded EWM?

The post SAP Extended Warehouse Management (EWM) deployment options with S/4 HANA appeared first on ERP Q&A.

Sample Business scenario:

To make the inbound process smooth we have the requirement to use vendor SSCC labels to avoid printing labels and in case the pallets are not labelled, then SAP EWM should print the SSCC labels for scanning. To receive Vendor SSCC labels the vendor labels should be also have GS1 standard SSCC labels with ]C1 prefix.

Process Flow:

SAP EWM configuration:

1. SSCC HU number ranges-

Path: SPRO>SCM Extended Warehouse Management>Extended Warehouse Management>Cross-Process Settings>Handling Units>External Identification>SSCC Generation Acc. to EAN128>Define Number Range Object for SSCC

Assuming the company is using EAN128 which means it has a unique ILN Basis number (International Location Number) or else you must request ILN number from UCC or EAN International.

2. SSCC Generation for each Warehouse-

Path: SPRO>SCM Extended Warehouse Management>Extended Warehouse Management>Cross-Process Settings>Handling Units>External Identification>SSCC Generation Acc. to EAN128> Maintain SSCC Generation for Each Warehouse Number

You define an SSCC using a basis number of an International Location Number (ILN) and a number from the number range object. The total length of these two numbers must be 17 characters.

Example, for warehouse number 0001, you entered a basis number of ILN 11234567 and chose to begin with this number. You are using the internal number range interval 01 from the number range object /SCWM/SSCC. This generates the number 123456789.

Your SSCC is 112345671234567890. The system assigns 0 as the check digit.

Note: The field HUIDENT in table /SCWM/HUHDR is having value of 20 CHAR, therefore system adds zeros in prefix while saving in database.

3. Maintain Bar code specification.

Path: SPRO>SCM Extended Warehouse Management>Extended Warehouse Management> Mobile Data Entry> Maintain Bar Code Specification

Assigning the AI type to Warehouse

SAP EWM Transactional details:

1. Let us check the ‘Receive HU by Delivery’ option

If we see the logical transaction and step using Ctrl+shift+F1

2. Open the screen painter,

Check the screen field for HU

Note: In RF configuration, we can see the validation profile for field VLENR the barcode translation FM is /SCWM/RF_EAN128_SPLIT_VALID for RH**** logical transactions

For this step RHUSL we have the PAI FM- /SCWM/RF_REHU_HU_SEL_PAI

In this FM- we have the barcode decode perform being called

If we check this FM in SE37, we can find standard decode FM- /SCWM/EAN128_DECODE

3. According to GS1-128/EAN128 configuration for decoding the barcode system needs prefix ]C1

To enable ]C1 in MC33 Zebra device we can use the below settings in default profile and DW DW Demo profile:

MC33 Device:

Profile: DW Demo

Device settings:

Data wedge > barcode input main settings>Configure scanner setting> scan params>barcode input > code id type > code id type aim

Note: GS1 128/EAN 128 have the prefix ‘]C1’ this is different than Code 128 barcode which have the prefix ‘]C0’. Hence while building barcode please use correct barcode type.

4. Scan an external GS1 128 1D Barcode-

(00)123456788000077123(15)210831

Where (00) identifier is for SSCC and (15) is for Best before date

Scanner adds prefix ‘]C1’ in the string

In debugging mode,

we can see the IT_BARCODE field is populated with the scanned barcode string with ]C1 prefix

And the FM decodes the values of SSCC and BBD

The decoded GS1 SSCC number shows in HU field in RF.

The post GS1-128 Barcode Understanding and Technical Details appeared first on ERP Q&A.

Consider a case where a storage type contains products with UOM as Boxes, cases, Pallets and EA.

Boxes, Cases & Pallets- Alternative UOM AUoM

EA- Smallest UOM as Base Unit of Measure BUoM

Customer places order in BUoM, however, the picker in Warehouse has to have the flexibility to pick in Alternative UOM.

Example, if customer places an order of 290 EA, EWM should create 3 WTS.

1 Pallet for 200 Ea, 1 Box for 50 EA and 40 EA, 3 Task.

These can be done through packaging specification also( I will not talk of SUoM), only the packaging specification will be explored.

To achieve this, create a 3 level Pack speck.

A condition record of type 0WHT should be created having product and supply chain unit combination.

Assign the operative UOM at all the 3 levels.

Let the Warehouse process type for picking should be intelligent enough to conduct rounding.

Customer order of 290 EA, OBD of 290 EA, with above settings, system should create 3 WT

Check EWM WT:

RFUI helps picker in alternative UOM.

No quantity classification was used in source storage type, the Storage type will have stock in EA but picking can happen in AUOM as per Pack spec Operative UOM

Note: As per SAP KBA 2745415 – AUoM during Warehouse Task creation:

The system takes the AUoM of the available quantity when creating a WT. The system also tries to determine which AUoM is best suited for WT execution. If a quantity equivalent to a whole pallet is to be removed, the system creates a WT with the AUoM for a pallet. The system decides whether to use another AUoM for the WT according to the quantity for the WT or to the quantity classification that is maintained in the WT’s source storage type and in the product master.

–> If the product has a packaging specification, the system uses the AUoM from the packaging level which fits the WT. If there is no packaging specification, the system attempts to determine an AUoM by checking the product master for the AUoM’s conversion factors.

Operative UOM

To know more about the potential usage of Operative UOM from Packaging specification, adding few excerpts from a legendary book SAP EWM Architecture and Programming by Peter Zoellner, Robert Halm, Danila Schapler & Karen Schulze, SAP press, page no 339.

Note: If in warehouse there are many products which are using same packaging structures, you dont need to create packaging specification for each.

You can reduce the number of packaging specifications for products by creating a packaging specification for one product and entering this product as the reference product in the product master data (packaging data) of all similar products.

For this you need to add field PAK_REFMATID Ref.Product GUID /SCWM/DE_REFMATID RAW Ref.Prod Ref.Product Reference Product and encapsulate in access sequence. You can customize 0WHT to ZWHT.

This is how Pack spec functionality can be leveraged to pick in Alternative UOM which is very critical in picking process without maintaining any quantity classification in source storage type

The post Picking in Alternative UOM: The hidden power of Packaging Specification appeared first on ERP Q&A.

Basic knowledge of CIF configuration in ERP and transfer master data through CIF using BTEs.

CIF Customizing in the ERP system

The Core Interface is an interface that enable data exchange between an ERP and EWM system.

We can transfer custom data to the EWM system through enhancement.

Prerequisite:

Below are the steps for basic configuration required in ERP before activate BTE.

Define Logical system:

Logical system is a Unique ID within SAP system that Identifies partner communication system.

Configuration Path:

SPRO -> Integration with other SAP Components -> Advanced planning and optimization -> Basic setting for setting up the system landscape -> Name logical system name (Transaction code BD54)

Enter the Logical system name and description.

Under same above path, assigning logical system to Client and we have options while transfer for client specific objects like Automatic recording of changes and No changes allowed.

Assign logical system to Client: Transaction code SCC4

Identify the SAP system release under system status and assign to logical system.

Specify SAP SCM Release: Transaction Code NDV2

Once assignment successfully, Set up RFC Destination for logical system for communication between source and target system.

Setup RFC Destination: Transaction Code SM59

Assign logical system of ERP and Logical system of EWM for transfer master data.

Assign RFC Destination to Various Application: CFC7

once assignment of both logical system, assign Queue type to logical system like below.

Set Target System and Queue Type: CFC1

Set user parameter for distribution of master data to target system.

Set User Parameter: Transaction code CFC2

CIF Customization in the SCM System

Same above settings follow in SCM System

Initial creation of master data

Once you have created the master data like material master, Vendor , Customer in ERP.

Below are two procedures for making the transfer:

• Periodic transfer using background proc
  
• Online transfer using Business Transfer Events (BTEs)

The main difference between BTEs and Change pointer is need creation batch job for process. The system is auto activated message types for BTEs once you activate the BTEs

I’m focused on Online transfer using Business Transfer Events

Below are the configure steps for BTEs

1. Activate BTEs for CIF Integration: Transaction BF11

Set indicator for ND-APO Application below

2. Optionally, check and delete old and inactive version of the integration model through report RIMODDEL or Transaction Code CFM7

Enter the logical system and execute report. Select the entry and click on delete button.

3. Create a new version of the corresponding integration model using report RIMODGEN

Transaction Code: CFM1.

Enter Model Name, Logical System and APO Application.

Choose check box in below image like if we want transfer material data to EWM.

Check the Material check box and left side you can provide materials and execute. Once you execute the report, Model will be generate for transfer.

Automatically distributed once created or change master data in ERP, we have to create Variants with same of materials, Vendors and customers as per requirement. the saved variant will be utilize in standard table following step.

Created different variants like: EWM_MAT , EWM_CUS

4. Activate the new version (Report RIMODAC2), Set the radio button Activate new version

Transaction Code: CFM2

Enter Model Name, Logical System and APO Application.

The system automatically sets the old version inactivated. The system is not transferring all the data in the new version to the target system. Only differences between old and new(delta info) are transferred.

5. Run the transaction CFC9 to call the Change Target System Independent Settings in CIF

Once time settings only.

Under Change transfer master data, Choose BTE immediately

6. Use transaction SM30, Call Table CIFIMODGEN

maintain the Connection points for material, customer etc with Program RIMODGEN with respective variant created in CFM1.

Insert the data Connection Point for material like MAT_INS, Program RIMODGEN and Variant which is created above step.

The post Master Data transfer through CIF using BTEs appeared first on ERP Q&A.

Purpose

The purpose of this article to understand INBOUND POSC and how does it work in EWM. In this blog post I will discuss the configuration and master data settings in EWM for one of the Inbound process consisting of multi-step movements.

• In this Inbound POSC Scenario we discuss about Deconsolidation/Re-pack process of a product. Here we received a product packed inside HU from the supplier and before placing the product to final bin, we first take out the product from the HU and re-pack in different HU and placed it in final bin.

Read More: https://www.erpqna.com/sap-s-4hana-cloud-private-edition-extended-warehouse-management-certification-preparation-guide/

CONFIGURATION: –

1.1 Define Process Oriented Storage Control:

In this area, maintain storage process with external steps and process-oriented storage control.

PATH: Spro—Img—SCM EWM—EWM—Cross process setting—Warehouse Task—Define Process Oriented storage control

Here we can use Standard External steps also (IB01, IB02, IB03)

1.2 Define Storage Process:

• After Creating Storage process, we need to assign External process codes to storage process. As shown below-

1.3 Define Process Oriented Storage Control:

PATH: Spro—IMG—SCM EWM—EWM—Cross process setting—Warehouse Task—Define Process oriented storage control

1.4 Define Warehouse Process Type:

PATH: Spro—IMG—SCM EWM—EWM—Cross process setting—Warehouse Task—Define Warehouse Process Type

• Here we define WPT for put away process and assign storage process to it, means sequential multi-step trigger to finish the process.

1.5 Define Control Indicator for Determining Warehouse Process Type:

PATH: Spro—IMG—SCM EWM—EWM—Cross process setting—Warehouse Task—Define Control Indicator for Determining Warehouse Process type.

1.6 Determining Warehouse Process Type:

PATH: Spro—IMG—SCM EWM—EWM—Cross process setting—Warehouse Task—Determine Warehouse Process Type

• Here the system determines the WPT according to Document type, Item type, Delivery priority and Process type determination control indicator.

1.7 Define Storage type for Work center:

PATH: Spro—SCM EWM—EWM—Master Data—Define Storage Type

• Here one Storage type with role “work center” is required to assign work center to execute deconsolidation process.

1.8 Define Work center:

PATH: Spro—SCM EWM—EWM—Master Data—Work Center—Define Work Center

1.9 Create Storage Bin for Work center:

• Storage bin is required to assign for work center, this storage bin create against storage type, which is assigned to work center.

PATH: Sap Easy Access—EWM—Master Data—Storage Bin—Create Storage Bin

2.0 Define Master Data Attributes for Work center:

PATH: Sap Easy Access—EWM—Master Data—Work center—Define Master Data Attributes

TEST CASE

3.1 Create Inbound Delivery:

Transaction: VL31N

• Once Material is packed then click on SAVE button. Inbound deliver is transfers to EWM.

3.2 Maintain Inbound Delivery:

Transaction: /N/SCWM/PRDI

• To view HU detail, click on HU TAB to view the HU details.

• Create Warehouse Task

• Here HU is mandatory to work with POSC. HU Warehouse task creates for Warehouse request (IBD), Where Source is “DOOR” and Destination is “GR-STAGE”

3.3 Check Monitor for WT details:

Transaction: /N/SCWM/MON

• Warehouse monitor provides WT information with reference to inbound delivery.

• Once confirm the WT (UNLOAD), there new WT’s will be created, one is Confirmed WT and other is Waiting WT.

• Once confirm the open WT, HU will be available at deconsolidation work center.

3.4 Deconsolidation at Work Center:

Transaction: /N/SCWM/DCONS

• Now create new HU for transferring the materials from old HU to new HU.

• Now Enter the Source HU, destination HU (new/empty HU) under Deconsolidation Tab & select open WT

• Now, Open WT appear under “Deconsolidation” tab

NOTE: It is possible to change Qty of open WT, system will create a new WT for QTY. Once executed, product will be packed in new HU (Destination HU).

• Until ‘complete HU step ‘for individual HU’s, deconsolidation will not be completed.

• Once after complete HU steps, then only waiting WT will be opened.
  
• Once it is opened click on Confirm WT in Background, as shown below-

• Below you can see Waiting WT status has been confirmed and material has been transferred to Destination storage Bin.

The post Embedded EWM – Inbound POSC (Multi-step movements) appeared first on ERP Q&A.