cancel
Showing results for 
Search instead for 
Did you mean: 

File to idoc scenario

Former Member
0 Kudos

Hi experts,

I am making File to Idoc Scenario.

In my file there are two records for ORDERS05 message type, When I am sending the same from file, only it is creating First record here,

When I am checking the Occurance of IDOC Segment of ORDERS05, it is showing 1:1,

How I can send multiple entries in this Segment of Message type ORDERS05 ?

Please help,

Regards,

Study SAP

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi just create the external definition (XSD) of IDOC and there just change the occurrence of IDOC from 1:1 to 0...unbounded. Thats it.

To be be more clear, when you copy the IDOC xsd on your local machine then only change the occurrence and then import it undr external definition. I hope you got my point.

Regards,

Sarvesh

Former Member
0 Kudos

Hi,

As correctly said by sharvesh first export the strucutre and using XML spy or Stylo studio change the occurance of root node from 1..1 to 1...unbounded and then import the strucutre in external definition and use it.

Thnx

Chirag

Former Member
0 Kudos

Thanks for reply,

I have completed the steps as per your given idea.

When we are sending the data we are receiving the error

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>

<SAP:Stack>Unable to interpret IDoc interface test_idoc</SAP:Stack>

In sxmb_moni.

It is for my idoc name as when we are importing external definition for XSD Schema, we are giving the name for that "test_idoc", This idoc is not available at our R/3 system.

When we are creating Receiver Determination, we are giving "test_Idoc" in place of ORDERS.ORDERS05.

This error is for that.

Please help me to remove this error.

Regards,

Study SAP

former_member859847
Active Contributor
0 Kudos

Hi,

Please disable the field which has attribute.

attribute are mandotory fields.

otherwise please assigh constant time being.

u will not get that error.

regards

mahesh.

turmoll
Active Contributor
0 Kudos

Hi,

Is "test_idoc" your new message interface created based on enhanced external definition?

Have you created new interface mapping and new message mapping (1-many)?

Regards,

Jakub

Former Member
0 Kudos

Yes Jakub,

I have created one Message interface for that External Definition,

I have created new interface and message mapping also for the same.

The problem is only for IDOC receiver part, because "test_idoc" is not an idoc at R/3 system. So idoc adapter is not identifying the same. Also this interface is not an idoc.

Regards,

Study SAP

turmoll
Active Contributor
0 Kudos

Hi,

I was wrong. You shouldn't' have created a new message interface.

After you upload a new external definition you can use it in the message mapping directly!

Regards,

Jakub

Former Member
0 Kudos

Hi,

Yes, I am using that "External Definition" directly for mapping purpose.

But the error message is same.

Regards,

Study SAP

turmoll
Active Contributor
0 Kudos

to sum up:

1. import IDoc to IR and export IDoc Schema to file

2. do the enhancement of maxOccurs in exported file

3. import enhanced schema as External Definition

4. use enhanced External Def. in Message Mapping

5. create Interface Mapping but use not External Definition but IDOC!

Regards,

Jakub

Former Member
0 Kudos

Help Please, it is urgent.

Former Member
0 Kudos

Hi,

Go to you External Definition and open the test_idoc sxd and press the F7 button to check if there is any error in it.

Secondly, go to message mapping and select the Test Tab and test you mapping here first.

Rest of the configuration as you did seems to be correct.

Regards,

Sarvesh

Former Member
0 Kudos

GREAT.............................

It is working fine,

Thanks to all of you epsecially JAKUB.

Regards,

Study SAP

Answers (1)

Answers (1)

turmoll
Active Contributor
0 Kudos

Hi,

All you need: [XI: IDOC bundling - the "trick" with the occurance change|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2762] [original link is broken] [original link is broken] [original link is broken];

Regards,

Jakub