Skip to Content
Technical Articles
Author's profile photo DICKSON JIN

Output type SPED trigger inbound delivery after PGI for inter-company STO’s outbound delivery

Inter-company purchasing is a very common business scenario in many SAP projects. In project practice, inter-company STO (or cross-company STO) is used to realize this process.


Different projects have different practices:

– In some projects, one-step transfer is adopted, that is, after the issue company post goods issues by VL02N, the receiving company automatically completes the goods receipt posting.

– In some projects, two-step transfer is adopted, that is, the issue company first performs goods issue posting, and then the receiving company performs goods receipt posting separately.

-In some projects, inbound delivery needs to be created on the receiving side. Through system settings, SAP can automatically trigger the inbound delivery document in this scenario after the goods issue posted by the issue company.


I wrote this blog to explain how to use the SAP standard output type SPED, to realize the function of automatically triggering the inbound delivery after the goods issue of outbound delivery is posted.



The main steps are as follows:


1, The output type SPED was defined here:

2, Output type SPED was assigned to output determination procedure V10000.

The requirement of the output type SPED can be 408 or 1. (I tested, those two values are both OK, can trigger the inbound delivery document successfully after goods issue posting for the outbound delivery document.)


Requirement = 408,

See the ABAP code and the comments,

If requirement=1,

See the ABAP code and related comments,

Remember that for the requirement 408/1, the inbound delivery will be triggered AFTER goods issue posting for outbound delivery.

3, The Output Procedure V10000 was assigned delivery type NLCC.


4, Maintain the condition record for output type SPED.

Transaction code:VV21/VV22/VV23

Be careful that the value of the field Partner cannot be empty in this condition record, see above screen.

5,Assign goods receiving point for receiving plant/storage location combination.

We need to assign shipping point for all receiving plant/storage location combination.



6, The definition of purchase order confirmation control key.

Here I created a new confirmation control key Z004,

Make sure that the check box GR-Relevant and GR Assignment Key are both selected.

7, Now we can create a inter-company STO document to see the effect.


STO#4500000759. The stock of material 555 will be transferred from plant NMI1 to plant NM03, they belong to different company code.

VL10B to create a outbound delivery for this STO,DN#80000781.

VL02N to pick and post goods issue for this outbound delivery,


Now let me to check the output record for this outbound delivery using VL03N,

There is output record for output type SPED. See above screen.



Now let us check the STO item details, see the confirmation tab by transaction code ME23N,

Inbound delivery 180000182 was triggered successfully,the batch number picked in outbound delivery also was copied into this inbound delivery,

Remark: there is a pre-condition if output type SPED to trigger inbound delivery document. It is that the inter-company STO should be a two-step transfer. In below configuration,

For the issue plant/receiving plant combination, do NOT select the checkbox ‘One Step’. Otherwise when we conduct PGI for outbound delivery, SAP will pop up error message to say: No goods receipt possible for purchase order ####. When I tested, I have ever meet this error message when PGI by VL02N.

Hope this blog can help you.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Dominik Tylczynski
      Dominik Tylczynski

      That is a very nice explanation of SPED functionality!

      When we use SPED, we should also used SPER with requirement 409. SPER deletes an inbound delivery when a goods issue against an outbound delivery is cancelled. This way we get a full process.

      Author's profile photo DICKSON JIN
      Blog Post Author

      Dear Moninik,


      Today I tested this ,but got error msg:


      Inbound delivery 180000189 is not deleted yet; Cancellation not possible.


      See the detailed message:



      Inbound delivery 180000189 is not deleted yet; Cancellation not possible

      Message no. VLA076


      The outbound delivery is part of a 2-step stock transfer. The goods issue cannot be cancelled until the following inbound delivery 180000189 has been deleted.

      System Response

      It is not possible to cancel the goods issue.


      Call the change transaction for the inbound delivery 180000189 and delete the document.

      If the inbound delivery contains handling units, they must first be deleted if Handling Unit Management is not active in your system. If Handling Unit Management is active, you must undo the assignment of the handling units to the inbound delivery in the packing transaction before the document can be deleted. In this step, the handling units are reassigned to the previous outbound delivery.





      Author's profile photo DICKSON JIN
      Blog Post Author

      Dear  Dominik,


      Thanks a lot for your comments.


      I will test if the output type SPER works well as you mentioned.

      Author's profile photo Maxime Dere
      Maxime Dere

      Great blog and well detailed.

      It is also worth mentionning that when you are doing that process, you will be able to find the linked Inbound delivery from Fiori App My Inbound Delivery Monitor (VL06I), General Inbound Delivery List (VL06IF) or via Transaction Code VL06IF by inputing the Outbound delivery number (with leading 0 or *) in the field "External Delivery ID"



      Author's profile photo GERARDO LOPEZ SCHEKAIBAN

      Hello DICKSON,

      Inbound delivery, for intracompany STO, is created with External Delivery ID field empty, instead of having the outbound delivery number, do you know what can be missing? for plant to plant STOs is getting populated correctly. Thank you.