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

SAP Blog

Kayıtlı Üye
Katılım
22 Ara 2017
Mesajlar
1,759
Tepki puanı
7
Puanları
6
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:

e0aad0b5b1f94a358778e7be1b7fb637~tplv-tt-shrink:640:0.image


518eb08ff0e84429868083e806f2a80c~tplv-tt-shrink:640:0.image


29d9071dd7614e58b25512715be406b7~tplv-tt-shrink:640:0.image


d4c8969289ba4d428864b60210060da7~tplv-tt-shrink:640:0.image




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

3153ff44f6d4488789916d1d73c706f8~tplv-tt-shrink:640:0.image


c5fb39d210f1435c8b5a3ea305b8c9ef~tplv-tt-shrink:640:0.image


3f0b2779294b43d2aa62f5f3971aed67~tplv-tt-shrink:640:0.image



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,

741a3857c0494aa1a67b478fbdf2cf08~tplv-tt-shrink:640:0.image



See the ABAP code and the comments,

7a4dfd4d11f74ea8bb33f65143a42bf7~tplv-tt-shrink:640:0.image



If requirement=1,

6ab92d5c533742ab922b8239a669e505~tplv-tt-shrink:640:0.image



See the ABAP code and related comments,

f784d980528f435bb563426f01a23c6b~tplv-tt-shrink:640:0.image



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.

3a80bda2043f4501886feedafee56358~tplv-tt-shrink:640:0.image


8f987c02119b43f481d09280c9417f31~tplv-tt-shrink:640:0.image





4, Maintain the condition record for output type SPED.


Transaction code:VV21/VV22/VV23

8fd584df11e046e8a384f905e973640f~tplv-tt-shrink:640:0.image


d9b6689ada96459e98bd753ff1f17b66~tplv-tt-shrink:640:0.image



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.

77bc428939eb40bab3cab667c5d128f5~tplv-tt-shrink:640:0.image


39bcae08a54b42b4b963e96babf7f437~tplv-tt-shrink:640:0.image



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





6, The definition of purchase order confirmation control key.

11d83b04a2a64282a98293626985b02d~tplv-tt-shrink:640:0.image



Here I created a new confirmation control key Z004,

18d5e81f2ec64fdb9da312276c8a1df7~tplv-tt-shrink:640:0.image


eb8250fb9c9546299dfd085b0e6a4ea3~tplv-tt-shrink:640:0.image



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.



40a65cb7ae3749dba88def9b36d92d39~tplv-tt-shrink:640:0.image



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.

5f71c8e306094665ba714307ac9fae3c~tplv-tt-shrink:640:0.image



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

2862842101ec41dbb9bed341376ae766~tplv-tt-shrink:640:0.image



Success!

7202f57b975843d8a1cba4949a0a029e~tplv-tt-shrink:640:0.image



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

8b31c415b8c543d6905a07956532ada2~tplv-tt-shrink:640:0.image



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,

bd1eb44d4e1c4e31a8ac4b0aef2fdd5e~tplv-tt-shrink:640:0.image



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

78113c27c3044070a47bd67b78d50c75~tplv-tt-shrink:640:0.image



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,

545186fe872944a284b22cd90b97340a~tplv-tt-shrink:640:0.image


b93cc7bda54046a4a3a74e7f38db64dc~tplv-tt-shrink:640:0.image



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.

Okumaya devam et...
 
Üst