Posting Change for Stocks

In SAP Extended Warehouse Management (SAP EWM), a posting change is a change in the stock key of a quant. A posting change is always documented by a goods movement document. It can be accompanied by a warehouse task if the changed stock is to be moved to another bin.

For more information about quants, see Quant.

Typical posting changes are as follows:

Change of stock type. This is the most common posting change.
Examples
- Change from unrestricted-use stock (F2) to blocked stock (B6) or scrap stock (S6)
- Change from quality-inspection stock (Q4, Q3) to unrestricted-use stock (F2, F1)
- Change from unrestricted-use stock in putaway (F1) to unrestricted-use stock in the warehouse (F2) during the putaway process
- Change from customer-returns stock (R7, R8) to unrestricted-use stock (F1, F2)
- Change from unrestricted-use stock in the warehouse (F2) to unrestricted-use stock in production (P2) in the production supply process
Change of product or batch number
Change of stock usage and owner, for example, from vendor-consignment stock to your own stock
Change of sales order stock or project stock, for example, to another sales order, to another WBS element, or to normal stock
Change of document reference, for example, from normal stock to a delivery-related stock in the picking process

There are a number of procedures to handle posting changes available in SAP EWM.

For posting changes triggered in SAP ERP, there must be an outbound delivery in SAP ERP and a posting change delivery in SAP EWM.

For posting changes triggered in SAP EWM, you can work with or without posting change deliveries.

The following table illustrates the different procedures available for posting changes in SAP EWM:

Procedure	Transaction at Start of Procedure	Outbound Delivery Exists in SAP ERP	Posting Change Delivery Exists in SAP EWM	Immediate Goods Movement Allowed	Goods Movement after Warehouse Task Allowed	Goods Movement before Warehouse Task Allowed
Planned posting change triggered in SAP ERP	`MIGO` or `VL_MOVE`	X	X	X	X	X
Planned posting change triggered in SAP EWM	`/SCWM/IM_PC` or `/SCWM/POST`	No	X	X	X	X
Direct posting change or warehouse task	`/SCWM/POST`	No	No	X	No	X
Automatic posting change upon warehouse task confirmation	`/SCWM/TO_CONF` or `RF`	No	No	No	X	No

For more information about these procedures, see the following:

Integration

If your warehouse is integrated with SAP ERP, the following restrictions apply:

In the warehouse, you can perform only the posting changes that are allowed in SAP ERP.
All posting changes except changes in the document reference of the stock are communicated to SAP ERP.
If an outbound delivery exists for a posting change in SAP ERP, the posting change is communicated to SAP ERP as a delivery message.

If no outbound delivery exists for the posting change, the posting change is communicated to SAP ERP as a goods movement message.

Features

Delivery Documents for Posting Changes

You can plan a posting change by creating an outbound delivery in SAP ERP or a posting change delivery in SAP EWM. For posting change deliveries, you cannot trigger the goods movement manually. The system always posts the posting change automatically, either when the posting change delivery is created or when the warehouse task is confirmed.

For more information about posting change deliveries in SAP EWM, see Warehouse Request of the Posting Change Type.

Goods Movement Document for Posting Changes

A goods movement document is a document similar to a warehouse task except that it always contains two items for each posting change – one item for the source stock key and one item for the destination stock key.

You can display goods movement documents for posting changes using transaction /SCWM/TO_DISP or in the warehouse management monitor under Start of the navigation path Documents Next navigation step Warehouse Task End of the navigation path or Documents All Movements for Product . Goods movement documents have the warehouse process category 7.

Note Note

The warehouse management monitor node Start of the navigation path Documents Next navigation step Posting Changes End of the navigation path displays the posting change deliveries. It does not display the goods movement documents for posting changes.

End of the note.

Posting Change with Immediate Goods Movement

If a quant is not moved to another bin for the posting change, the posting change can be posted immediately without creating a warehouse task. However this is only possible if the system is able to find the quant.

For example, the system cannot find a quant under the following conditions:

The bin is not specified in the posting change delivery and several quants exist
The available quantities are managed at bin level or are batch-neutral

If the system cannot find the quant, you must create warehouse tasks for the posting change.

Mixed Storage after a Posting Change

If a posting change with immediate goods movement affects only a partial quantity in a handling unit (HU) or in a bin, it results in two quants on the bin or on the HU. This means that you must allow mixed storage in the storage type. If you do not want to store different products or different batches on the same bin or HU, you can allow a more specific mixed storage like the mixed storage of different stock types of the same product or batch.

It you do not allow mixed storage on a storage type, you must create warehouse tasks for the posting change and post the posting change when the warehouse task is confirmed, that is, goods movement after warehouse task.

Posting Change with Warehouse Task

You can create warehouse tasks to move the changed stock to another bin. For example, you use different storage types for unrestricted-use stock and quality-inspection stock or for vendor-consignment stock and own stock.

In this case, the system creates the following documents:

A warehouse task to move the stock
A goods movement document for the posting change

Depending on the process type settings, the goods movement for the posting change can be posted before or after the warehouse task.

Note Note

The system cannot post a posting change after the warehouse task for warehouse tasks created without posting change deliveries with transaction /SCWM/POST. In this transaction, the system always posts the posting change first.

For posting change deliveries, the posting change can be posted before or after the warehouse task. However the system can post a posting change before the warehouse task only if the system can find the stock. If the system cannot find the stock, you must create the warehouse tasks first.

End of the note.

If you use warehouse tasks to execute posting changes, all warehouse task functions, such as the use of warehouse orders, radio frequency, or warehouse task printing, are available.

Automatic Posting Change upon Warehouse Task Confirmation

In some SAP EWM processes, the system automatically triggers posting changes when a warehouse task is confirmed. In this case, the posting change always takes place after the warehouse task is confirmed.

Business Add-Ins for Posting Change

You can implement the following Business Add-Ins (BAdIs):

Stock Checks for Goods Movement (/SCWM/EX_CORE_GM_STOCK)
Allows you to prevent some posting changes in your warehouse, for example, you do not allow a change of product number in your warehouse.
Stock Type Determination for Transfer Postings (/SCWM/EX_CORE_GM_CAT)
Allows you to determine the destination stock type in the case of automatic posting change upon warehouse task confirmation.
Delivery-specific BAdIs that allow you to implement checks for warehouse requests of the posting change type