Skip to Content

1. Trigger the IDOC sending using tcode R3AS

/wp-content/uploads/2013/12/clipboard1_344353.png

Choose the receiver destination site from f4 help:

/wp-content/uploads/2013/12/clipboard2_344363.png

Click f8 to execute the sending.

/wp-content/uploads/2013/12/clipboard3_344364.png

2. Launch tcode SMQ2 to check inbound QRFC queue, you should find one entry for our R3AS run in step1.

/wp-content/uploads/2013/12/clipboard4_344366.png

Double click on it:

/wp-content/uploads/2013/12/clipboard5_344367.png

Then double click it again, choose the entry for FM BAPI_CRM_SAVE and click debug icon:

/wp-content/uploads/2013/12/clipboard6_344368.png

3. Now debugger window automatically pops up:

/wp-content/uploads/2013/12/clipboard7_344369.png

Adapter module COM_MAP_BAPIMTCS_TO_PRODUCT will be called.

/wp-content/uploads/2013/12/clipboard8_344371.png

/wp-content/uploads/2013/12/clipboard9_344372.png

/wp-content/uploads/2013/12/clipboard10_344373.png

Middleware framework class will be called:

/wp-content/uploads/2013/12/clipboard11_344374.png

/wp-content/uploads/2013/12/clipboard12_344378.png

/wp-content/uploads/2013/12/clipboard13_344379.png

These above three function modules will be executed one by one. The first one is for message replication and the second for master data management and we are only interested in the last one for IDOC sending.

/wp-content/uploads/2013/12/clipboard14_344380.png

/wp-content/uploads/2013/12/clipboard15_344381.png

Function module CRMXIF_ADP_OUTBOUND will be called:

/wp-content/uploads/2013/12/clipboard16_344382.png

/wp-content/uploads/2013/12/clipboard17_344383.png

/wp-content/uploads/2013/12/clipboard18_344384.png

Variable ls_data_mapped contains the product data to be sent:

/wp-content/uploads/2013/12/clipboard19_344385.png

/wp-content/uploads/2013/12/clipboard20_344386.png

Get the ALE function module name:

/wp-content/uploads/2013/12/clipboard21_344393.png

The real sending occurs in function module MASTER_IDOC_DISTRIBUTE. After execution the IDOC document number will be stored in variable idoc_comm.

/wp-content/uploads/2013/12/clipboard22_344394.png

The variable IDOC_DATA contains the formatted data to be sent:

/wp-content/uploads/2013/12/clipboard23_344395.png

write down the document number 214003

/wp-content/uploads/2013/12/clipboard25_344402.png

And have a look at it in tcode WE05:

/wp-content/uploads/2013/12/clipboard26_344403.png

It is in error status 29

/wp-content/uploads/2013/12/clipboard27_344404.png

Error code 29 means the receiver of IDoc is its own logical system

/wp-content/uploads/2013/12/clipboard28_344405.png

So we can check via tcode SMOEAC against the IDOC receiver site. And yes, the configuration there is wrong, since currently we are triggering IDOC send right in QDD, and we should not set it again as receiver site.

/wp-content/uploads/2013/12/clipboard29_344406.png

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply