1. What is the purpose of automatic inbound delivery creation
for stock transfers?
Answer:
If you use stock transfers according to the two-step
procedure, you must post the goods receipt separately in the receiving plant
after posting the goods issue of the replenishment delivery from the delivering
plant. In the standard process, you use a goods receipt transaction of
inventory management for this posting (for example, transaction MIGO
"Goods Receipt for Replenishment Delivery"). However, replenishment
delivery data is ignored in goods receipt posting using inventory management,
for example:
Quantities
Serial numbers
Batches
Handling units (HUs)
However, if you use automatic inbound delivery creation for
two-step stock transfers, this data is copied from the outbound delivery to the
inbound delivery, which you can use to post the goods receipt in the receiving
plant. The automatically created inbound delivery saves you from entering the
actual quantities manually and, in addition, provides an preview of the
expected goods receipt in the receiving plant.
Automatic inbound delivery creation is mandatory if the
receiving plant is managed using a decentralized Warehouse Management system
(WMS) or an Extended Warehouse Management (EWM) system; in this case, the
inbound delivery is required as a communication document for the decentralized
system. Automatic inbound delivery creation is also required if Handling Unit
Management (HUM) is activated for the receiving storage location. In this case,
the inbound delivery serves as a reference document for the HUs that are
transferred by the preceding replenishment delivery.
2. What is the process flow of the stock transfer process
like when you use automatic inbound delivery creation?
Answer:
The stock transport order and the subsequent outbound
delivery are created and processed using standard transactions. The outbound
delivery is picked, packed as and when required and then goods issued posted.
An output condition works in goods issue posting and ensures that the special
output SPED is added to the header outputs of the delivery. The output SPED
generates the inbound delivery during processing in the background. Processing
can take place either using immediate processing or using reports for output
issue.
You then carry out putaway and goods receipt posting using
the inbound delivery.
If the receiving plant is managed using a decentralized
Warehouse Management system or an Extended Warehouse Management system, after
creation, the inbound delivery is automatically distributed to this system.
Putaway and goods receipt posting then take place in the decentralized system.
The inbound delivery is updated in the document flow of the
outbound delivery. In addition, the external delivery number of the inbound
delivery (LIFEX) refers to the outbound delivery. Therefore, you can use the
search help "E: External delivery number of vendor" in transaction
VL32N or VL33N to determine the inbound delivery belonging to the outbound
delivery if you know the outbound delivery number. Add the prefix "*"
to the delivery number to ignore potential leading zeros of the outbound
delivery number during the search.
3. When is the function "Automatic inbound delivery
creation for stock transfers" available (as of which release)?
Answer:
You can use the function as of ERP Release 6.00 in the
standard system. If you use an ERP release lower than 6.00, a consulting
solution is available for the automation of inbound delivery creation (see Note
497287).
4. What data is copied to the automatically created inbound
delivery?
Answer:
The automatically created inbound delivery is based on
outbound delivery data and the underlying stock transport order. Therefore, it
receives a purchase order reference; however, it copies the data relevant for
logistical processing from the outbound delivery, in particular
Materials
Quantities
Batches and batch splits
Serial numbers
Handling units (HUs)
Header and item texts
If a receiving storage location is specified in the stock
transport order, it is transferred to the inbound delivery. If it is not
specified, the receiving storage location is determined according to the
standard storage location determination rules.
5. How is the function set up?
Answer:
See Note 965176 for a detailed description about the steps
required to set up the function. Using the procedure described in Note 1095322,
you can delay automatic inbound delivery creation and make it dependent on the
planned delivery date in the receiving plant.
6. How can inbound delivery creation be controlled depending
on certain criteria?
Answer:
Since inbound delivery creation is triggered using a delivery
output, you can use the output determination options to control inbound
delivery creation based on specific criteria. In the standard system, the
delivery type is used to control whether the output SPED is relevant; however,
you can use any other criteria using the condition technique. For example, you
can change the access sequence in the definition of the output type SPED. If
inbound delivery creation depends on complex criteria, you can also use your
own condition routine. In this case, use standard condition routine 408
(include LV61B408) for the template. For more information about the configuration
of output determination, call transaction SPRO and go to "Logistics
Execution" -> "Shipping" -> "Basic Shipping
Functions" -> "Output Control". If you want to influence the
time of inbound delivery creation, proceed as described in Note 1095322.
7. What must be noted if handling units (HUs) are used?
Answer:
If there are HUs in the outbound delivery for the stock
transport order, these can pass over to the subsequent inbound delivery during
the goods issue. However, the HUss are only transferred from the outbound
delivery if either the lean HU status update or unique number assignment are
active for HUs. You can find the relevant settings in the Implementation Guide
under "Logistics Execution -> Service Parts Management (SPM) ->
Cross-Process Settings -> Handling Unit Management -> Set Lean HU Status
Update in Non-unique HU Numbering Scenario". You should only activate
unique numbering if you want to use HUM, otherwise you should use lean HU
status update. If lean HU status update is active, the status and the history
of the handling units are updated, but there is no check to see if the HU
number is unique.
If you use cross-delivery HUs (as they can be created in
EWM), they can also be transferred from the outbound delivery to the inbound
delivery if the receiving warehouse is also managed by an EWM system. Note
however that this process does not work if you have activated unique number
assignment for HUs. You cannot use both HUM and cross-delivery HUs in ERP.
When you use batch splits with handling units, note that HUs
can only be reassigned from the outbound delivery to the inbound delivery when
the batch split items are themselves packed. You cannot use the "Pack
accumulated batches / movement type item" indicator (TVLP-CHHPV) in the item
category of the delivery together with the two-step transfer scenario via the
output SPED. In this case, the system displays error message HUFUNCTIONS191
"Handling unit &1 is already assigned to outbound delivery
&2" when you create the inbound delivery.
8. How do you know which inbound delivery was created by the
system?
Answer:
The inbound delivery created appears in the document flow of
the outbound delivery. In the inbound delivery, you recognize the assigned
outbound delivery by the external delivery number that corresponds to the
number of the outbound delivery You find this information in the inbound
delivery dialog (transaction VL33N) on the tab page "Header" ->
"Administration".
9. What must you check if the inbound delivery was not
created automatically?
Answer:
First check whether the inbound delivery exists by displaying
the document flow of the replenishment delivery. If the inbound delivery does
not exist, check the assignment of the output SPED to the header outputs of the
outbound delivery (menu: "Extras" -> "Delivery Output"
-> "Header").
If the output does not appear there, the condition record is
usually missing. Therefore, use transaction VV22 to check whether a condition
record exists for the condition SPED and the delivery type of the outbound
delivery. Create the missing condition record if required. As an exception, you
can also assign the output SPED to the outbound delivery and save the delivery.
The output is then either processed immediately according to the default
settings of the output type SPED or it can be processed using standard reports,
for example, using transaction VL71.
If the system rejects the manual assignment of the output
SPED for the outbound delivery, assign the appropriate output determination
procedure to the delivery type as described in Note 965176.
If the output appears but is still unprocessed (yellow
traffic light), you can start processing using a standard report a standard
report, for example, using the report RSNAST00 or transaction VL71.
If the output appears and is incorrect (red traffic light),
you can release the processing log of output processing for error analysis. You
can use transaction VL71 for output postprocessing (processing mode 3).
10. What must you do if the inbound delivery created cannot
be goods receipt posted?
Answer:
If the goods receipt for the inbound delivery cannot be
posted, the appropriate confirmation control key is usually missing in the
stock transport order. Therefore, check whether a confirmation control key was
assigned to the items of the stock transport order (item tab page
"Confirmations" in transaction ME23N). Make sure that the goods
receipt relevance and goods receipt assignment are activated for the chosen
confirmation control key. The corresponding settings are available in the
Implementation Guide (IMG) under "Materials Management" ->
"Purchasing" -> "Basic Functions" ->
"Confirmations" -> "Set Up Confirmation Control".
11. Can you create the inbound delivery manually with regard
to the stock transport order?
Answer:
You can use a procedure described in Notes 421276 and 490865
to manually create the inbound delivery with regard to the stock transport
order. You can continue to use this procedure but it is not advised since a
whole host of restrictions occur as a result, particularly due to the missing
data transfer from the outbound delivery. For detailed information about these
restrictions, see the notes mentioned above.
If the inbound delivery for the stock transport order was not
created using message control and a subsequent creation is required, you can
implement the report
Z_IBDLV_CREATE_FROM_OBDLV
from the correction instructions in your system and execute
it. The report requires you to enter the outbound delivery number and generates
the inbound delivery if the corresponding prerequisites exist. A log is output
in the case of errors.
12. Can you delete the automatically created inbound delivery
again?
Answer:
You can delete the automatically created inbound delivery
again after you have deleted the HUs of the inbound delivery or the assignment
of the HUs for the inbound delivery. Note 1083602 is a prerequisite if you want
to reassign the HUs to the outbound delivery in this step to facilitate the
regeneration of the inbound delivery or the goods issue reversal of the
outbound delivery. Support Packages SAPKH60011 and SAPKH60201 contain the
corrections from Note 1083602 or they are found as standard in SAP_APPL 6.03
(ERP 6.00 with Enhancement Package 3).
13. How can you reverse the goods issue of a replenishment
delivery if an inbound delivery was already created for it?
Answer:
Before the goods issue of the replenishment delivery can be
reversed, the subsequent inbound delivery must first be deleted. Note 1083602
describes the required procedure, particularly if you are using HUM.
If you use an Extended Warehouse Management system (EWM) in
the delivering and receiving plant, you can use the delivery output SPER to
automatically request the deletion of the inbound delivery. In this case, no
further manual steps are required. The output SPER must be assigned to the
output determination procedure of the delivery along with condition routine
409.
14. Can you create the inbound delivery for the outbound
delivery repeatedly?
Answer:
Usually, it is not useful to create the inbound delivery
repeatedly since, for example, the HUs and the serial numbers from the outbound
delivery can only be passed on to one inbound delivery. In addition, the stock
in transit created during the goods issue for the replenishment delivery can be
goods receipt posted only once. However, as an exception, you can create
another inbound delivery by carrying out repeat processing of the output SPED
after you delete the outbound delivery created previously or set the quantities
of this outbound delivery to zero. The report
Z_IBDLV_CREATE_FROM_OBDLV
also enables you to create another inbound delivery. In this
case, the prerequisites are not checked.
Before you create another inbound delivery, you must check
whether the inbound delivery exists using the document flow of the outbound
delivery or by searching for the inbound delivery using the outbound delivery
number as an external delivery identification. Note 1312812 provides additional
information.
15. Which restrictions apply if, instead of the outbound
delivery message SPED, the shipping notification IDoc DESADV is used to create
the inbound delivery?
Answer:
If you use the shipping notification IDoc DESADV to transfer
the outbound delivery information to the receiving warehouse, you cannot use
cross-delivery handling units in this process. Neither outbound processing and
inbound processing of the IDoc nor the message itself (basis type DELVRY03 or
higher) are prepared for the transfer of the corresponding HU attributes.