ORDERS Idoc splitting into two

[former_member1275317]

Hi,

I have requiremnt where i need to Split Orders idoc into messages.

1. Orders XML file 2.XML file only with control record fields.

i have seen all the discssion on this and deceiced to implement the scenario as per

/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible blog. But the problem is need to use two message types on the target side.. for splitting the message..

ORDERS and Contrlo record Fields message type... i can't change the standard idoc..

Can i add the Control record fields to Standard IDOC in any way.... like exporting file...if so..

tell me whether the Idoc will split into two messaged or not....

Regards,

Deep

[Former Member · Accepted solution]

Hi,

If you are using IDOC adapter in receiver then you can not use multimapping(in blog) concept.Idoc adapter not support this functionality.

Regards,

Prakasu.M

Edited by: prakasu on May 15, 2009 4:34 PM

[Former Member]

Hi,

You can certainly create 2 files as you require. If you follow the steps correctly in the blog that you have mentioned in your post.

You wont need to change anything in standard, you simply need to create 2 message types and add these 2 message types in the multi mapping and do the necessary field and structure mapping in the graphical mappind editor.

Source---Target

IDoc-------> XML file 1 ( message type with idoc data n control record )

-

---

> XML file 2 ( message type with idoc control record only )

Don't forget to use enhanced interface mapping.

In moniroting you will only see a single entry with sub documents for each of the message types, but when

files are written there will be 2 files.

regards,

Advait

[former_member1275317]

Advait...

Thanks for ur reply... I have done as per ur explanation.. bt here is a problem..

Whenever we adding 2 messages on target side.. Source side sturcture automatically getting changed..

Messages.... 1-1

<Message1>...1-1

<ORDERS05> ...1-1

...................... but incoming idoc is standard we cannot change structure...

However in this mapping Orders05 sttucture getting changed...if we go for mulitmapping...

so how to get rid off this ORDERS05 structure...

Regards,

Deep..

[Former Member]

Hi,

There is no need to change anything.The tag automaticaly generate at the time of (multimapping).But runtime it will accept only ORDERS05 structure only.

Regards,

Prakasu.M

[Former Member]

Hi Sandeep,

Those extra tags are ok, they are created on both the source and target side, nothing to worry about them, they are created at runtime as rightly said by Prakasu. And you don't have to bother about changing the ORDERS05 structure at all.

So you can continue with your scenario as it is.

regards,

Advait

[Former Member]

Hi Sandeep,

can u bit clear abt ur requirement?

Like IDOC is at sender side and u want to split IDoc into 2 files (xml message and control message)..

if this is a case then u need to have 2 message types at target side.

Regards,

Manisha

[former_member1275317]

Madan,

Thanks for ur reply...Changing of IDOC structure by importing and adding fields thats fine...

My doubt is in the mentioned blog target msg type was created one.. here i need to take with ORDERS idoc(ED in our case). I need to split the IDOC everytime when it triggers based on RCVPRN field value.. this value is always so there should be 2 values everytime.

Does it split into two message ( ORDERS XML and Control Record XML)

Prakasu,

IDOC is on Source side...

Manisha,

Thanks for ur reply... I'm asking question as per mentioned blog in my msg..

I do have the interface with two message mappings which is running fine.. just i want to change the scenario..

Regards,

Deep.

[Former Member]

Hi Sandeep,

if ur saying tht u want to add 2 messages at target side and generate only one target file..

I guess then tht is not possible...it will generate 1 file only.

Regards,

Manisha

[madanmohan_agrawal]

>>I do have the interface with two message mappings which is running fine.. just i want to change the >>scenario..

Perfect!!

I think there is no other way to implement the same. You have done the right thing.

Regards,

Madan Agrawal

[former_member200962]

My doubt is in the mentioned blog target msg type was created one.. here i need to take with ORDERS idoc(ED in our case). I need to split the IDOC everytime when it triggers based on RCVPRN field value.. this value is always so there should be 2 values everytime.

you will need to duplicate the IDOC at the target side to achieve this...if you are successful in doing the 0...unbounded thing for your IDOC....

1) Duplicating:

Duplicating is not Multimapping.....Multimapping is what you saw in the blog and duplicating is right-clicking on the node and choosing Duplicate Subtree....no two messages will be created in this process (duplicating).....

2) Multimapping:

it is used to create two (or more) different messages at the target end...

Does it split into two message ( ORDERS XML and Control Record XML)

No it wont split the IDOC into two messages.....

So if your requirement is to have only one target message with seperate IDOC nodes..having ORDERS and Control data individually...then go for duplication method...apply the condition for RCVPRN to generate the nodes...

If your req is to have two different messages at the target then use multimapping apply the condition for RCVPRN to generate the two different messages.....

Hope it helps...

Regards,

Abhishek.

[madanmohan_agrawal]

>>i can't change the standard idoc

open standard IDOC --> export it as XSD --> change it --> import it as an ED in IR and use it in MI.

>>tell me whether the Idoc will split into two messaged or not....

Yes it is possible. During your change in XSD file put the occurances as Unbounded.

regards,

Madan Agrawal