BPM Concern: Total message processing time too large

[Former Member]

Hello Experts,

I have implemented a BPM scenario with a fork step. MDM is the sender system and ECC is the final reciever system.

Branch 1 of Fork step: Processes Message type 1(DEBMAS); includes transformation step(ABAP mapping) and Send step (RFc call to ECC)

Branch 2 of Fork step: Processes Message type 2(ADRMAS); includes transformation step(ABAP mapping) and Send step (RFc call to ECC)

the messages are proccessed as required but the only concern is the total time reuired for the final message to be posted to ECC system. This scenario using the above design takes more thean 5 mins to post the message to ECC; which the end user will not accept.

Is this due to the parallel processing using fork step? Is there any alternative method of implementing this with minimum processing time?

Thanks in advance,

Elizabeth.

[udo_martens]

Hi,

a general rule for a better bpm performance is to put the mappings outside. So, if it is possible, you should try to put the ABAP mapping behind the process.

Regards,

Udo

[former_member207622]

Yes we can reduce the total throughput , Can you explain why ABAP mapping is used ? I mean can we avoid that

because it is used twice in parallel procesing taking a toll on server

Do we have any message dependency ?

Regards

Ninad

[Former Member]

Hi Ninad,

Begore the ABAP mapping step, there is a send step (sends DEBMAS/ADRMAS to ECC).

ABAP mapping reads the message Id generated for the above message and the retrieves the PI IDoc number and its details from PI SXMB_MONI backend tables. This is then required to be given as input to Send step (RFC call to ECC to get ECC IDoc acknowledgment based on PI IDOC number).

~Elizabeth.