cancel
Showing results for 
Search instead for 
Did you mean: 

File to IDoc - How to proceed further?

prasad_ulagappan2
Contributor
0 Kudos

Hi everybody,

Consider the following scenario,

<Header>

<Transaction>

<Meterpoint>

<Address></Address>

<Asset>

<Meter></Meter>

<Conversion></Conversion>

<Register></Register>

</Asset>

</Meterpoint>

</Transaction>

</Header>

This is the structure of one IDOC.

My Source structure can contain multiple <meterpoint> and multiple <transaction>.

I have to post one IDOC for each meterpoint per transaction.

For example, a transaction can contain 4 meterpoints, then I have to post 4 IDOCs for that transaction alone.

And this applies for each transaction that are present in the source structure.

My Queries are,

1. How to proceed for posting the IDOCs for this kind of scenario?

Is it possible to do it with message mapping itself or we need a java mapping/XSLT mapping?

2. How can I do content conversion for a complex structure like this.

Any help will be highly appreciated.

Regards,

Prasad U

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member185751
Contributor
0 Kudos

Hi Prasad,

"Outbound Packaging of IDocs" feature is available from SP11 only. Check OSS note 778890.

Regards,

Sridhar

Former Member
0 Kudos

Hi Prasad,

I feel with XSLT you can quickly develop your mapping as follows.

<Header>

<xsl:for-each select="Input/Transaction/MeterPoint">

<Transaction>

<Meterpoint>

<your idoc mapping here>

</Meterpoint>

</Transaction>

</xsl:for-each>

</Header>

You can do message mapping also. But you have to change the idoc occurrence setting to 0 to unbound.

Instead of posting IDoc one by one, collect your IDoc into packets and send to SAP.

Thanks,

Sasi

Former Member
0 Kudos

Prasad

Its a scenario of 1:N mapping(multimapping)..Do a root mapping from <Meterpoint> to IDoc root tag and use multimapping to convert target 0..unbounded in the message tab(of message mapping).

Now use ccBPM to call the IDoc for every looped message in your target.

Regards

Sriram V.