on 04-12-2011 12:08 PM
Is BPM a must to implement two-action scenario?
e.g.
ME -
sending 3A4 Request --> Partner A
ME <------sending 3A4 Confirmation -- Partner A
Without BPM,
1. can the adapter alert when no 3A4 confirmation receipt?
another example:
Partner A --Sending 3A4 Reqeust --> ME
Partner A <--Sending 3A4 confirmation -- ME
without BPM
1. how to map the conversation id from 3A4 request to 3A4 confirmation?
Thanks.
Philip
Hi,
PIP 3A4 of version V02.02 encompasses two business action messages, u201CPurchase Order Request Actionu201D and u201CPurchase Order Confirmation Actionu201D. These will correspond to abstract Message Interfaces as follows:
http://sap.com/xi/RosettaNet/PIP3A4_V0202, PurchaseOrderRequestAction
http://sap.com/xi/RosettaNet/PIP3A4_V0202, PurchaseOrderConfirmationAction
If you use Alternate Interface Namespace:
http://sap.com/xi/RosettaNet/V0202, PIP3A4
For two action RNIF, have a look into below SAP Documentation.
http://help.sap.com/saphelp_nw04/helpdata/en/f0/7098403de08368e10000000a1550b0/content.htm
Regards
Aashish Sinha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Philip,
We have the same requirement,. The conversation id of the order request should be present in the order confirmation. Will it be handled automatically by the adapter (two action asynchronous request & two action asynchronous response ) or do we need any settings in the bpm to make it work. Please help us in resolving the issue .. thanking you in advance ..
Regards,
Aju
HI Philip,
what is your scenario.. which adapter you are using on sender and receiver side..? explain your scenario and requirement?
Need of BPM depends on above details..?
try to put specific question and this allow us to provide good solution..
Thanks,
Bhupesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bhupesh,
I have two scenarios here.
Scenarios 1:
Adapters: RNIF & IDOCS
1. SAP ECC send IDOC to SAP PI
2. SAP PI transform IDOC into PIP
3. SAP PI send PIP with RNIF Adapter to Partner A
4. Partner A response with confirmation PIP to SAP PI
5. SAP PI receive confirmation PIP via RNIF adapter
6. SAP PI transform confirmation PIP into IDOC
7. SAP PI send IDOC to SAP ECC
Scenarios 2:
Adapters: RNIF & IDOC
1. Partner A send PIP to SAP PI
2. SAP PI receive PIP via RNIF Adapter
branch 1:
a. SAP PI transform PIP into IDOC
b. SAP PI send IDOC to ECC
branch 2:
a. SAP PI transform PIP into confirmation PIP
b. SAP PI send PIP via RNIF adapter to Partner
Philip
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
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.