Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Fusion Material master feed not working for Brampton (0384)

Former Member

‎2014 Jul 14 1:40 PM

0 Kudos
111

0384 is not picked up in the auto job and works fine when I trigger manually.

Below is a snapshot of all four RECEIVER ID populated on the
IDOC. Each reflects a 3PL DC, you can see entries for 1001 (Ontario), 4974 (Orchard),
5589 (Calgary) and 5684 (Columbus). I don’t see an entry for Brampton (0384).

I triggered manually today to send a material into Brampton. All automated feeds for
Canadian materials must include the below listed Receiver ID.

Where need to check the issue.




 
 
 
 
 
 
 
 
 
 
 
 




3 REPLIES 3

Former Member

‎2014 Jul 14 1:41 PM

0 Kudos
81

inbound idoc issue.

thanga_prakash
Active Contributor
In response to Former Member

‎2014 Jul 15 6:03 AM

0 Kudos
81

Hello Venu,

The image was not attached properly in your question.

Can you please elaborate on the issue.

Regards,

TP

thanga_prakash
Active Contributor

‎2014 Jul 15 6:08 AM

0 Kudos
81

If the problem is with the inbound idoc processing.

Go to WE20 transaction, respective partner profile --> Inbound parameters  ---> message type and display.

Under the Inbound options tab, double click on process code, the function module mentioned in Identification is used to process the inbound idoc.

Place a break point inside the function module, recreate the idoc using the transaction WE19 and debug the code to find it.

Regards,

TP