Documentation

Goods issue based goods receipt

1. Classic intra-stock transfer order process

Information regarding the classical intra-stock transfer with stock transport orders is
available in the standard SAP documentation:
http://help.sap.com/saphelp_erp2005/helpdata/en/4d/2b90dc43ad11d189410000e829fbbd
/content.htm

Quick overview:

2. Deficit of the classic stock transport order process with batch

managed / split valuated materials
The documentation about split valuation can be found here:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/47/61017149f011d1894c0000e829fbb
d/frameset.htm
When processing stock transport orders for batch split valuated materials, a valuation type
has to be entered in step 1) when creating the stock transport order.
Issue: The receiving plant is not aware of the valuation type that will be issued by the
supplying plant. Batch split in outbound delivery for several valuation types is not possible.
 Requirement: Valuation type should be maintained at the time of the goods issue in the
outbound delivery. This would also allow batch split in order to be able to post a goods issue
with several valuation types for one stock transport order item.

3. Goods issue based goods receipt process

The goods issue based goods receipt (GI based GR) process allows to save a stock transport
order for items with batch managed split valuated materials without entering a valuation
type. The valuation type must be entered at the time of the goods issue when posting the
outbound delivery using transaction VL02N.

1) Stock transport order creation

For the stock transport order creation a new checkbox in ME21 and ME21N is provided called
GI-based GR on tab Delivery. This new checkbox is right beside the input field Valuation
type:

As soon as the checkbox GI-based GR is set, its no longer possible to enter a valuation type.
The field will be grayed out:

If you entered a valuation type and set the checkbox afterwards, the entry in field valuation
type will be deleted. Its only possible to either enter a valuation type or to set the GI-based
GR checkbox.
It is possible to mix items with and without GI-based GR indicator in the stock transport
order.

2) Outbound delivery processing

The outbound delivery will be created with transaction VL10B with reference to the stock
transport order as usual. The difference for split valuated delivery items where the GI-based
GR checkbox is set is that there is no valuation type available. If the valuation type is entered
in the stock transport order, its not possible to change that entry in the outbound delivery as
it is taken over from the stock transport order.

3) Goods Issue processing

 In order to be able to post the goods issue (using movement type 641) it is necessary to enter
a valuation type for the items where GI-based GR is set in the STO.

4) Goods receipt processing

The goods receipt must be posted with reference to the goods issue. This is mandatory in the
GI-based GR process in order to ensure data consistency.
This can be done by posting the goods receipt with reference to the outbound delivery with
transaction MIGO (Goods receipt -> Outbound Delivery) or transaction MB0A.
Alternatively the goods receipt can be posted with reference to an inbound delivery which
was created with reference to the outbound delivery in case a confirmation was set for the
STO item.
If the goods receipt is posted via BAPI or IDOCS it must be ensured that the correct deliveries
are provided as input parameters. The stock unit, valuation type, quantity and unit of
measure must be equal to the values in the outbound delivery.

If the prerequisites for the goods receipt are not met, the user will receive the error message
M7-469.

4. Inbound delivery processing

If the STO item has a confirmation control key provided or the goods receipt goes into a
decentralized storage location (EWM, WM) then an inbound delivery processing is
mandatory.
Its not possible to create an inbound delivery for GI-based GR STO items using the manual
entry transactions VL31N, VL34N, VL60 and VL64. The users will receive the error message
M6-002 when trying to create the inbound delivery manually for these items.
Inbound deliveries for these types of STOs can only created using the message type SPED in
the outbound delivery. The inbound delivery will then be created out of the outbound
delivery with proper reference.
For the items of an inbound delivery with GI-based GR indicator its not possible to change
the valuation type and the quantity / stock unit to ensure that the goods receipt is posted
based on the goods issue. This limitation is mandatory in order to ensure data persistency
and consistency! Please do not make customer specific adjustments under this restriction as
it could cause data inconsistencies that cant be handled under support conditions.

5. Exceptions / Process limitations in a nutshell

In order to ensure data consistency and not to affect already existing functionality its
obligatory to introduce some process limitations.
Prior using the new process, please ensure that you took these limitations into account and
can handle them properly.

1) Stock transfer only with same valuation type

The valuation type cannot be changed in this process. Its only possible to transfer the goods
within the same valuation type. This means that the valuation type of the supplying plant is
the same as in the receiving plant.
2) Inbound delivery creation only via SPED
The Inbound deliveries can only be created with reference to the outbound delivery with
message type SPED. During the goods issue posting with reference to the outbound delivery
a corresponding inbound delivery can be created. Users who are trying to create an inbound
delivery manually will receive error message M6-002.

3) Changes in Inbound delivery

The stock unit, valuation type, quantity and stock unit of measure that will be goods
receipted must be equal to the stock unit, valuation type, quantity and stock unit of measure
that have been goods issued from the supplying plant. This is necessary to ensure data
consistency. Because the value booking in the receiving plant already happens with the 641
GI and the quantity booking happens with the 101 GR. Therefore these fields are grayed out
for items where GI-based GR is checked.

4) Return transfer processing not possible

Once the GI-based GR indicator is set in the purchase order, the item the return indicator
cannot be set anymore. You can either check the return or the GR-based GI indicator.
Advanced Returns Management process wont work either. During a return process the
returned batches and valuation types should already be known as they are getting returned.

5) Creation of the stock transport orders with ME21N only

The classic transaction ME27 was not enhanced for this newly introduced process, thus
ME21N must be used.

6) Stock determination during GI posting not possible

Its not supported, as the determined valuation types from shipping, as explained by note
483888, cannot be updated in the delivery. Therefore during the goods receipt the
information about the valuation type is not available which then leads correctly to error
message M7469.