cancel
Showing results for 
Search instead for 
Did you mean: 

Scenario-- One Idoc--> Two files has to generate.

Former Member
0 Kudos

Hi All,

I got the scenario where i need to generate two files ( 1 with header data and 1 with item data) for single idoc FIDCC1.

Is it possible to acheive this?

Please suggest me how to appraoch this scenario?

Thanks.

Regards

Seema.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

<b>Design Time</b>

<i>Interface Objects</i>

create 2 data types one for header and one for data

create 2 message types one for header and one for data

create 2 Interfaces (outbound) one for header and one for data

<i>Mapping Objects</i>

In message mapping, there are 3 tabs Design, Test and Messages...

Go to Messages and select source as your IDoc and in target

Messages select two message types.. (data and header)

Then design Interface mapping..

<b>Configuration Time</b>

Same as IDoc to single file...

but you need have two receiver agreement...

In interface determination go for extended option...

Hope this helps

Regards,

Ramesh P

Former Member
0 Kudos

Hi,

BPM is not required. The steps i gave you will do it fine and one more thing i forgot is pointed out by Prateek.

<i>>>>>Create 2 communication channels. 2 receiver agreements</i>

Regards,

Ramesh P

Former Member
0 Kudos

Hi Ramesh,

I also felt the same.

But in receiver agreement i can give

1 Sending BS

1 Receiving BS

1 Message Interface(outbound)..

1 commu channel.

If i want to create another receiver agreement for 2 comm. channel.

It is not taking because "Object already exists"

So even if i create 2 Comm. channels.i cannot create 2 RX agreements beacause of

1 Sending BS

1 Receiving BS

1 Message Interface(outbound)..

Please suggest me.

Regards

Seema.

prateek
Active Contributor
0 Kudos

<i>If i want to create another receiver agreement for 2 comm. channel.

It is not taking because "Object already exists" </i>

U cant create more than 1 <b>receiver determination</b>

However u can create more than one <b>receiver agreement</b>

Regards,

Prateek

Former Member
0 Kudos

Hi Reddy,

This is very much possible, having more than one receiver agreement with different interfaces.

<b>Receiver agreement...</b>

Sender_BSystem | Receiver_Bsystem | <Interface for your header> | Namespace

Sender_BSystem | Receiver_Bsystem | <Interface for your data> | Namespace

Regards,

Ramesh P

Former Member
0 Kudos

Sorry.. worng msg.

Thanks.

Seema.

Message was edited by:

reddy seema

Former Member
0 Kudos

Hi,

>>>>><i>But here iam having only one Rx System and only one outbound Message interface. That's why it is not allowing me to create 2nd receiver agreement for 2nd commu channel.

And it is displaying as " Object already exists"</i>

Yes, exactly you are right.

In your case you have to create one interface for header and one interface for data and both outbound.

Regards,

Ramesh P

prateek
Active Contributor
0 Kudos

<i>it is not allowing me to create 2nd receiver agreement for 2nd commu channel.</i>

U may always create any number of communication channels under the busines system or business service.

[Please reward each helpful answer]

Regards,

Prateek

Former Member
0 Kudos

Thanks Rajesh,Ramesh and Preteek.

Im following the below steps.

File type : 2 DATA TYPES (Header, Item)

Msg Type: 2 Message Type (Header Msg, Item Msg)

Msg Interface: 2 Messgae interfaces (Category Inbound, Mode assynchronous).

Message Mapping:

You can do a multi mapping (1:N).

Else

Perform 2 message mapping

a) with IDOC TO Header Msg

b) Between IDOC to Item Msg.

Perform 2 Interface Mapping

IDOC-> HEADER INTERFACE

'IDOC -> ITEM INTERFACE.

ID:

Import Both the Business Systems

1) Define 2 Communication channel for File Business Systems. (one for Header, other one for Item).

2) Define 1 Receiver Determination

3) Define 2 Interface Determination

4) Define 2 receiver Agreements as we have 2 communication channel.

Hope it will works..

<b>

Rewarded the points.</b>

If i get get any doubts while developing .. i will disturb u guys again.

Thank You.

-Seema.

Answers (3)

Answers (3)

Former Member
0 Kudos

SOURCE IDOC TARGET 2 FILES NO BPM .

IR:

FOR FILE / LEGACY APPLICATION :

File type : 2 DATA TYPES (Header, Item)

Msg Type: 2 Message Type (Header Msg, Item Msg)

Msg Interface: 2 Messgae interfaces (Category Inbound, Mode assynchronous).

Message Mapping:

You can do a multi mapping (1:N).

Else

Perform 2 message mapping

a) with IDOC TO Header Msg

b) Between IDOC to Item Msg.

Perform 2 Interface Mapping

IDOC-> HEADER INTERFACE

'IDOC -> ITEM INTERFACE.

ID:

Import Both the Business Systems

1) Define 2 Communication channel for File Business Systems. (one for Header, other one for Item).

2) Define 1 Receiver Determination

3) Define 2 Interface Determination

4) Define 2 receiver Agreements as we have 2 communication channel.

Hope you got it.Any errors please post.

Cheers,

<b>*RAJ*

*REWARD POINTS IF FOUND USEFULL*</b>

prateek
Active Contributor
0 Kudos

<i>Is it possible to acheive this?</i>.

yes

<i>Please suggest me how to appraoch this scenario?</i>

Do the mapping of header of idoc to first file structure and mapping of the item details to other file structure. Then do the receiver dtermination

Regards,

Prateek

Former Member
0 Kudos

Hi,

Problem is only one sending system and one receiving system.

If i create

IR:

-


2 data types

2 Msg types

2 Msg inter

1 Msg Mapping.

1 IM

Will the file splits once we do like above ?Since we are using only one communication channel.. how can it will create 2 files?

Regards

Seema.

Former Member
0 Kudos

One more point is i should not use BRM .

Please suggest me.

prateek
Active Contributor
0 Kudos

Create 2 communication channels. 2 receiver agreements

U may use this

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

Regards,

Prateek

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

it's possible in standard - you can create two receivers in receiver determination

Regards,

michal