on 09-21-2010 3:41 PM
Hi all,
we have 2 interfaces which uses same Idoc type, message type & Partner No.Only Process code is going to different according to the posting logic.
How can we differentiate both while posting idocs to not mess up each other .
Regards
one possibility in in the message mapping validate the process code and complete the EDI_DC40 segment with the propers values. so in one scenario you determinate the receiver.
take alook to this blog: /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
Edited by: Rodrigo Alejandro Pertierra on Sep 24, 2010 12:29 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess you might not be able to use the same IDOC for two different interfaces in PI. PI would not allow two receiver deteminations for the same IDOC type. You would have build some logic in the PI mapping so that the target messages are created as needed.
VJ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vamsi,
when you have two sender interfaces,then i dont think it will be a problem.
Based on which sender interface is triggered, the corresponding mapping gets executed and send the data to the R/3 system.
u can use the same channel and also the same interafce in the receiver side.
Thanks,
Hemanth.
> How can we differentiate both while posting idocs to not mess up each other .
What do you mean with "not mess up"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it inbound or outbound with respect to R3. If inbound to R3 then you can configure your partner profiles accordingly. You can use different Message Functions there in your partner profile.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
Say example:
Interface 1 is invoice coming from legacy system to SAP and i have to use AAA.BBB Idoc
Interfaces 2 is accrual coming from legacy system to SAP and i have to use AAA.BBB Idoc
So i am creating partner No with LS_LEGACY and with 2 inbound entries one for each.
Even though i am using the same Idoc types but inside those the process codes are different because they are different in posting logic.
Issue:
From XI perspective i can't differentiate them saying like Invoice interface should execute the entry in the partner profile with invoice process code and accrual interface with accrual process code.
My Idea is to design like this...
Using the Message Code option, While creating partner profile give the MESCODE and in Mapping provide the same MESCODE.
So that even thought i am using the same partner No with same message type & basis types for 2 scenarios, the right interface will trigger the right process code based on the MESCODE mentioned in mapping by carrying the control record values
Please let me know ur views
Regards
as i sugguest before,you can define the IDoc for two diferents profiles. once you define it, you can dynamic define the IDoc destination configuring the EDI_DC40 sengment in the message mapping. by this way you use the same IDoc and MT for 2 interfaces. plase refer to my previous post-
also i found additional information:
2. How do I use 'Apply Control Record Values from Payload' parameter with the IDOC adapter?
See notes:
a) 728792 - how the fields in the control record get set.
b) 792333 for an overview of how to convert partners in the IDoc adapter.
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
Edited by: Rodrigo Alejandro Pertierra on Sep 27, 2010 11:13 AM
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.