ITPub博客

首页 > 数字化转型 > ERP > IDoc DESADV trigger inbound delivery after PGI for inter-company STO's outbound

IDoc DESADV trigger inbound delivery after PGI for inter-company STO's outbound

原创 ERP 作者:dicksonjyl560101 时间:2021-11-23 10:52:41 0 删除 编辑

IDoc DESADV trigger inbound delivery after PGI for inter-company STO's outbound delivery


In the inter-company purchase (inter-company stock transfer) process, a common solution is to automatically trigger the inbound delivery document of the receive company after the issue company completes the goods issue posting. In addition to using the SAP standard output type SPED, it can also be implemented through IDoc.


This blog describes how to realize this function through IDoc.


It mainly consists of the following steps:

1, Create a new output type for outbound delivery.

T.Code – V/34,or using below configuration menu,

Here I created a new output type ZZIB,

Access sequence Z001,

The value of the field Transm.Medium is 6 (EDI).

The program is RSNASTED.

The form routine is EDI_PROCESSING

In the partner functions, create a new entry:6/SH, see above screen.

2,Assign the output type to output determination procedure V10000.

Requirement should be set as 1, means the output will be triggered after PGI for the outbound delivery.

3, Maintain the condition record for the output type.

Transaction code: VV21/VV22.

The partner specified here should be maintained in tcode WE20.

4,Define confirmation control key .

5, The outbound IDoc setting.

5.1), IDoc type – DELVRY03

Tools > ALE > ALE Development > IDoc > IDoc Type Development > IDoc Types

T.Code – WE30

5.2), Message Type – DESADV

Tools > ALE > ALE Development > IDoc > IDoc Type Development >Logical Messages

T.Code – WE81.

5.3),  Process Code – DELV

Tools > ALE > ALE Development > IDoc > Outbound Processing > Define Process Code

T.Code – WE41.

Function Module –  IDOC_OUTPUT_DELVRY.

5.4), Maintain the partner profile for outbound parameter.

SPRO > Materials Management > Purchasing > Messages > EDI > Set Up Partner Profile

T.Code – WE20.

Partner Type – KU (Customer)

Partner Role – SH

Receiver Port: A000000002

RFC Destination:

6, Inbound IDOC setting

IDoc type – DELVRY01

Message Type – DESADV

Process Code – DELS

Tools > ALE > ALE Development > IDoc > Inbound Processing > Define Process Code

T.Code – WE42

Function Module – IDOC_INPUT_DESADV1,

Maintain the partner profile for inbound parameter.

Tcode WE20. Partner Type – LS (Logical system)

7, The definition of Logical system by code SALE or by tcode BD54.

The assignment between logical system and SAP client.

Note: Currently I did this testing in CLIENT 100 system.

8, Create document and to see the effect.

STO#4500000768,

VL10B created an outbound delivery 80000784,

The PGI was done for this outbound delivery,

Check the output for this outbound delivery, IDoc triggered successfully.

The Inbound delivery was triggered successfully.

2021-11


来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/29829936/viewspace-2843599/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论
行万里路,读万卷书,阅无数人。 吃货一枚,爱吃湘菜,粤菜与杭帮菜,尝遍天下美食。 摄影爱好者,游遍名川大山,江河胡海,赏遍人间春色。 爱看电影,尤其是国产大片,好莱坞大片。英文名:Dickson Jin, 网名:风一样的BOY。精通SAP供应链咨询。2017年开始研习人工智能。

注册时间:2014-08-27

  • 博文量
    2569
  • 访问量
    4137124