on 02-20-2010 12:53 AM
Hi,
Am new to BPM. Followed Krishnamoorthy's wonderful blog : Walkthrough with BPM and was able to make it to work.
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
but it did not have transformation step : it was a simple file to file without transform.
If i want to introduce transform ,what all changes I need to make in design and config?
Please suggest.
Thank you.
Edited by: pi_question on Feb 20, 2010 1:58 AM
hi,
Insert an Transformation step between Receive and Send step, and in the Properties windows, Give Operation Mapping, sender and receiver Service interface as given in this blog:
/people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
Also check:
http://help.sap.com/saphelp_nw04/helpdata/en/27/db283fd0ca8443e10000000a114084/content.htm
https://www.sdn.sap.com/irj/scn/weblogs?blog=/cs/junior/view/wlg/9918
Thanks,
Mayank
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ok this covers design , how abt config?
Actually i did similar steps, but I only see my file being picked but integration process does not seem to kick off. Iniitally i created a bpm which worked but was from krishnamoorthy's walkthrough blog. Now i inserted transform step as u mentioned and i guess my steps were similar as in the blog you sent. Somehow maybe i did something not correct.
Thank you.
Edited by: pi_question on Feb 20, 2010 6:58 AM
for conf part also follow step 2 in the the same blog:
/people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
Step 2: Integration Directory: Configuration
Create the configuration scenario, assign the Business system, created the communication channels of type File for Sender and Receiver, and create Sender Agreement.
Create two Receiver Determinations-
1) File Sender ->BPM ( No Mapping)
2) BPM->File Receiver ( No Mapping)
Create the Receiver Agreement.
Save and activate all.
Now Design and Development is done.
For monitoring BPM, check this blog:
/people/shabarish.vijayakumar/blog/2005/12/07/transformation-error-and-still-stuck
in SXMB_MONi, got to your message search for PE click on it and check out, you will see the steps also there in next window.
so is no interface det needed?
Interface Determination is one of the mandatory steps in ID.
However when you include a Transformation Step in a BPM, then the only difference will be that the corresponding Interface Determination may not have a Mapping in it.
Including mapping in the Interface Determination (instead of Transformation Step) is a good option, as this increases the performance of the BPM. Now your BPM to work, you should make sure that the Message Interfaces refered should be accurate.
was just wondering if ichange bpm in IR and import again in ID ,do i need to do something else also to trigger this process?
Importing the BPM again in ID is not necessary....you should save --> activate --> check return code of BPM in SXI_CACHE (it should be 0).....if you still feel that the new changes are not getting reflected then re-import the BPM.
Note that re-importing the BPM means re-creating the (BPM-involved) ID objects
or is it just like we trigge any interface through sender adapter ?
yes, the triggering is the same.....just pass some message through the sender channel (if any) and then if everything is configured correctly then the BPM will receive the message.
Regards,
Abhishek.
Hi,
The number of objects same,just add Trasformation step between Receive and send,then it ask specify operation mapping in Trasaformation step,add operation mapping in that,
you have to use Source abs,target abs interfase as source and taget,then only interface mapping will appear in Trasformation step.
Remoce opration mapping in Interface determination,it will work.
Regards,
Raj
if possible could u tell the number of MI /Design objects an ID objects for doing a scneario like : recv - transform - send
Sender --> BPM:
1) Outbound Async MI
2) Abstract Async MI (message type of 1 and 2 will be the same since there is no mapping in Interface Determination)
3) Sender Agreement...since source is FILE
4) Interface Determination (without mapping)
5) Receiver Determination
6) Sender Channel (FILE) ..... no receiver channel.
BPM --> Receiver:
1) Abstract Async MI
2) Inbound Async MI (message type of 1 and 2 will be the same, if there is no mapping in Interface Determination)
3) Receiver Agreement, Receiver Channel
4) Interface Determination
5) Receiver Determination
Steps remain the same, just the addition of mapping now happens in the Transformation Step.
Regards,
Abhishek.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.