File->different type of mesages->split->IDOCs

[Former Member]

team,

I am working on the above scenario using BPM. I got it working without BPM using Enhanced Interface determination and now trying to get it going with BPM to compare the performance.

1. File has multiple batch records, based on the data in the batch records two different messages (bulk AP and AR messages ) needed to be generated.

2. These bulk AP and AR messages need to be split into individual messages and mapped to IDOCs for being posted into ECC as AP and AR IDOCs.

I want to use BPM to split the file into multiple messages ( of differt types - AR and AP).Mapping into IDOC would be done outside BPM.

My BPM has

1. Receive step ( message received form the file content conversion )

2. Transformation step with I:N mapping with AP and AR as target message types

3. A fork without end condition

4. A Block in each of the branches of folk

5. A Send step in each of the blocks

My question is whether it is okay to use a folk after transformation step for handling two different interfaces coming out of transformation step.

I am able to see two different messages in the workflow log after the transformation step, but can’t see them in the SXMB_MONI. And so the mapping to IDOC is not happening. The config also seem to be okay .

[Former Member · Accepted solution]

I want to do IDOC mapping outside BPM and use BPM just for splitting the message. I have defined interface mapping for IP+IDOC in the config alomg with rest of the config.

The M1 and M2 are bulk messages. I thought I should use a ParForEach ( or for Each)block with a send inside to generate individuaul messages.This is working when I have only one bulk message generated from 1:n transformation. When I have two interfaces generated from 1:n transformation, I am struggling.

I am going to use two blocks next two each other with sends inside and see what happens

Correct me if this theory is wrong

[Former Member · Accepted solution]

Hi,

Yes. This would work.

Two Blocks , B1,B2.

B1 has send step S1 which sends message type S1.

B2 has send step S2 which sends message type S2.

Each of these blocks are configured as "par for each".

The mapping of idocs would be taken care at the interface determination level.

Regards,

Smitha.

[Former Member]

Yes it worked. Removed the fork and inserted two blocks next to each other. The IDOCs are also getting posted. Thanks Samita.

[Former Member]

Hi,

I don't think you need to have a fork in the BPM at all.

Once the multimapping happens, you would have 2 messages. M1 and M2.

After the multimapping, have two transformation steps T1 and T2.

In T1, map M1 to idoc1 and in T2, map M2 to idoc2.

Next, have 2 send steps S1,S2

S1 sends idoc1

S2 sends idoc2.

Regards,

Smitha.

[Former Member]

No. I am still struggling.

The scenario is very similar to the one in

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

The difference is my target messages are 0…unbounded and I need to get individual messages out. I have included a receiver determinination step in both the Fork branches.It still doesn't work.In the workflow log, the inout message is not entering the blocks at all

[Former Member]

Did you solved your prolem ?

If not send me an e-mail with the screen shot of the Integration Process to

sandro point garofano @ techedge.it

Regards,

Sandro