Skip to Content
author's profile photo Former Member
Former Member

Multimapping doesn't work in BPM

Hello,

I've constructed two mapping 1:1 and multimapping N:1 for two messages to transform them in two inbound IDOC . I put this process in BPM. When I test these mappings in MM and IM editors all are ok. But if i try to test the end-to-end through BPM i can get only one IDOC (mapping 1:1) with data.

The second IDOC(N:1) has empty segments only without combined data!

In BPM I use Fork to receive two messages. The Fork Step has two branches, two transformation steps(1:1 and N:1), two Send Steps(for two Idocs) accordingly. There is a correlation between two fields of two messages.

Perhaps one message leaves BPM before fullfilling N:1 mapping ? I confused.

Please help me to resolve this problem.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 04:10 PM

    Hi Igor.

    Are you using any correlations?

    If you are, then check if you are using the correct fields for correlation. I feel that could the problem.

    Make sure you are using the correct correlation.

    Correlations:

    We use a correlation to assign messages that belong together to the same process instance. A correlation joins messages that have the same value for one or more XML elements. A correlation is therefore a loose coupling of messages: at design time, it enables you to define which message a receive step must wait for, without knowing the message ID.

    Correlating Objects:

    A correlation enables you to identify objects that belong together, for example, a quotation and the relevant sales order. This involves correlating the objects by using one or more common elements, for example, the quotation number. When you define a Workflow, you can specify the object that the Workflow must wait for, without having to enter the ID of the object.

    Check this blog for further information on Correlations.

    /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi

    Regards,

    Hari.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hey Igor.

      Good to hear that your scenario is working fine now.

      It is not recommended to put the transformation and the send steps inside the fork as it sometimes hinders some of the send/transformation steps that are provided. It is always better to have all the transformation and send steps outside the fork and the block steps.

      Regards,

      Hari.

  • Posted on Nov 30, 2007 at 03:09 PM

    please go through the blog

    /people/narendra.jain/blog/2005/12/30/various-multi-mappings-and-optimizing-their-implementation-in-integration-processes-bpm-in-xi

    /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure

    with regards

    gabriel

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you. I've read these blogs but they describe 1:N multimapping.

      There is some differences.

      I can add the information. In SXMB_MONI_BPE I don't see the second message for N:1 multimapping.

      Does it happen because the second message is used for 1:1 mapping in the first branch of Fork and cann't use in the second branch for N:1 mapping??

      I feell that I must add something in my BPM. But WHAT?

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.