2013 Aug 19 7:34 AM
Hello everyone,
I'm struggling with Model View Distribution issue.
In a scenario where I wanted to send Material Master IDOC from client 500 to client 600, I created Model View in client 500 (BD64) and distributed it to client 600. It worked just fine.
But right now I'm working on a scenario, where I'm supposed to create PO on client 500, and as a result SO should be created on the same client. The problem is I tried creating Model View in client 500 (BD64).
But I'm getting error "Client and server must be different."
Does it mean we should not create Model View when IDOC is transferred to the same client?
Please help,
Desperately waiting for reply.
2013 Aug 19 7:50 AM
Hi,
BD64 model views you need to create only for master data distribution from one client/system to another, like material master, cost center, etc.
In your scenario you probably have to use message output in PO or SO to trigger the sender idoc.
Just wake the settings for output and input within WE20 directly.
In case you use logical system you can maintain the input and output for orders within the same partner number.
Regards
Michael
Hello everyone,
I'm struggling with Model View Distribution issue.
In a scenario where I wanted to send Material Master IDOC from client 500 to client 600, I created Model View in client 500 (BD64) and distributed it to client 600. It worked just fine.
But right now I'm working on a scenario, where I'm supposed to create PO on client 500, and as a result SO should be created on the same client. The problem is I tried creating Model View in client 500 (BD64).
But I'm getting error "Client and server must be different."
Does it mean we should not create Model View when IDOC is transferred to the same client?
Please help,
Desperately waiting for reply.
2013 Aug 19 7:44 AM
Hi Nikhil,
Use a BADI/exit to create a SO on creating the PO.
BR,
Shankar.
2013 Aug 19 7:50 AM
Hi,
BD64 model views you need to create only for master data distribution from one client/system to another, like material master, cost center, etc.
In your scenario you probably have to use message output in PO or SO to trigger the sender idoc.
Just wake the settings for output and input within WE20 directly.
In case you use logical system you can maintain the input and output for orders within the same partner number.
Regards
Michael
2013 Aug 19 8:01 AM
actually the error is correct as you want to use different client so you should use the other client as receiver client
2013 Aug 19 8:20 AM
Hey Raman, I want to use the same client as sender and receiver.
2013 Aug 19 8:20 AM
Hi Michael,
Don't we have to do Bd64 configuration when triggering IDOcs from PO/SO using message control ? Actually these things confuse me a bit , It would be very helpful if you can elaborate this. Thanks in advance.
BR,
Shankar.
2013 Aug 19 8:26 AM
Hello Michael Brauns,
Thanks for your input. I have used NEU as message output in PO to trigger the idoc outbound process. I can see the IDoc created also. But not sure what will make this PO to SO?
Please see this link I have posted, http://scn.sap.com/thread/3406892
2013 Aug 19 9:54 AM
Define an inbound in WE20 of your logical system for message type ORDERS and process code ORDE.
Double click on ORDE and you can see the function module name which will be processed for SD input.
It should be IDOC_INPUT_ORDERS. Within this FM (SE37) you can find some customer exits.
Search for string customer-function.
2013 Aug 19 12:32 PM
Hi Shankar.,
no you don't need BD64 in this case. Basically you need BD64 for ALE master data distribution scenarios. In this case it is an EDI scenario which is normally built to collaborate between different business partners (customer and vendor).
But you can use it also in the same client. So it is considered some sort of intercompany process.
You have to make sure that the SO is assigned to a valid sales organisation.
/Michael
2013 Aug 19 1:53 PM
2013 Sep 01 8:30 AM
Hey Michael Brauns,
thanks a lot for your response, after a lot of study I finally got answer to my own question. Following link I found really helpful.
http://scn.sap.com/docs/DOC-45574
And one thing i would like to mention is no exit or enhancement is needed for this.
Regards,
Nikhil GHadge.