Skip to Content
author's profile photo Former Member
Former Member

File to multiple IDOCS

Hi,

I need to set up the following activity. Can any of you please help me out.

File to IDoc Mappings

It is likely the names below will be used, except where for the beginning of the name (Z???). All of the below message types are built on the basic IDoc type ZSSV_GENERIC_IDOC.

There are some fields that will be required to be mapped inbound to SAP, that will not be contained in the input file from AMES. These fields will be required in XI to have something mapped to them. In other tests, I have used constants to map these fields. These fields for the ZSSV_GENERIC_IDOC basic IDoc type are:

ZSSV_GENERIC_IDOC

IDOC

BEGIN (only field under IDOC) = ?

EDI_DC40 (only listing required fields below, there are others)

SEGMENT = ?

TABNAM (table name) = ?

DIRECT (direction) = ?

IDOCTYP (IDoc type) = ?

MESTYP (message type) = ?

SNDPOR (sender port) = ?

SNDPRT (sender partner type) = ?

SNDPRN (sender partner number) = ?

RCVPOR (receiver port) = ?

RCVPRN (receiver partner number) = ?

Z1SSV_ITEMS_SUMMARY

SEGMENT = ? use counter starting at 1 in XI

Z1SSV_ITEMS

SEGMENT = ? use counter starting at 2 in XI

BLOB (this is talked about below and will be from the input file)

For the fields listed above, I have entered examples of what they have been set to in other mappings.

BEGIN – ?

SEGMENT (EDI_DC40) – ?

TABNAME – EDI_DC40

DIRECT – 02 (this represents inbound to SAP, 01 is outbound)

IDOCTYP – ZSSV_GENERIC_IDOC

MESTYP – This will be based on the incoming message types that are used, see list below.

SNDPOR – AMES (this would need to be what is defined in SAP as a logical system to use this)

SNDPRT – LS (this represents Logical System)

SNDPRN – AMES (this could be the same as SNDPOR)

RCVPOR – This will be based on C, Q, and P systems (SAPCAC, SAPQAC, and SAPPAC)

RCVPRN – This will be based on C, Q, and P systems, same as RCVPOR

SEGMENT (Z1SSV_ITEMS_SUMMARY) –?

SEGMENT (Z1SSV_ITEMS) –?

Z???_AMES2_COMP_SERIAL_UPD

Z1SSV_ITEMS_SUMMARY -This will not be used inbound to SAP

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. The data for this field will be copied directly from the file that is sent from AMES. Each line in the input file will be written to Z1SSV_ITEMS. If this input file contains 5 lines, we will write to 5 Z1SSV_ITEMS entries, each will have its own BLOB field. Whatever is in the file on each line will be written in each BLOB field. There will be no transformations or mappings on this data. In this example, the final IDOC for this file would have 1 blank entry for Z1SSV_ITEMS_SUMMARY and 5 Z1SSV_ITEMS entries, each with one BLOB.

Z???_AMES2_DELIVERY

Z1SSV_ITEMS_SUMMARY -This will not be used inbound to SAP

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. The data for this field will be copied directly from the file that is sent from AMES. Each line in the input file will be written to Z1SSV_ITEMS. If this input file contains 5 lines, we will write to 5 Z1SSV_ITEMS entries, each will have its own BLOB field. Whatever is in the file on each line will be written in each BLOB field. There will be no transformations or mappings on this data. In this example, the final IDOC for this file would have 1 blank entry for Z1SSV_ITEMS_SUMMARY and 5 Z1SSV_ITEMS entries, each with one BLOB.

Z???_AMES2_PRODORD_CONF

Z1SSV_ITEMS_SUMMARY -This will not be used inbound to SAP

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. The data for this field will be copied directly from the file that is sent from AMES. Each line in the input file will be written to Z1SSV_ITEMS. If this input file contains 5 lines, we will write to 5 Z1SSV_ITEMS entries, each will have its own BLOB field. Whatever is in the file on each line will be written in each BLOB field. There will be no transformations or mappings on this data. In this example, the final IDOC for this file would have 1 blank entry for Z1SSV_ITEMS_SUMMARY and 5 Z1SSV_ITEMS entries, each with one BLOB.

Z???_AMES2_QNOTE

Z1SSV_ITEMS_SUMMARY -This will not be used inbound to SAP

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. The data for this field will be copied directly from the file that is sent from AMES. Each line in the input file will be written to Z1SSV_ITEMS. If this input file contains 5 lines, we will write to 5 Z1SSV_ITEMS entries, each will have its own BLOB field. Whatever is in the file on each line will be written in each BLOB field. There will be no transformations or mappings on this data. In this example, the final IDOC for this file would have 1 blank entry for Z1SSV_ITEMS_SUMMARY and 5 Z1SSV_ITEMS entries, each with one BLOB.

Z???_AMES2_REMORD_CONF

Z1SSV_ITEMS_SUMMARY -This will not be used inbound to SAP

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. The data for this field will be copied directly from the file that is sent from AMES. Each line in the input file will be written to Z1SSV_ITEMS. If this input file contains 5 lines, we will write to 5 Z1SSV_ITEMS entries, each will have its own BLOB field. Whatever is in the file on each line will be written in each BLOB field. There will be no transformations or mappings on this data. In this example, the final IDOC for this file would have 1 blank entry for Z1SSV_ITEMS_SUMMARY and 5 Z1SSV_ITEMS entries, each with one BLOB.

Z???_AMES2_TRANSORD

Z1SSV_ITEMS_SUMMARY -This will not be used inbound to SAP

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. The data for this field will be copied directly from the file that is sent from AMES. Each line in the input file will be written to Z1SSV_ITEMS. If this input file contains 5 lines, we will write to 5 Z1SSV_ITEMS entries, each will have its own BLOB field. Whatever is in the file on each line will be written in each BLOB field. There will be no transformations or mappings on this data. In this example, the final IDOC for this file would have 1 blank entry for Z1SSV_ITEMS_SUMMARY and 5 Z1SSV_ITEMS entries, each with one BLOB.

Z???_AMES2_TRKNUMERRORS

Z1SSV_ITEMS_SUMMARY -This will not be used inbound to SAP

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. The data for this field will be copied directly from the file that is sent from AMES. Each line in the input file will be written to Z1SSV_ITEMS. If this input file contains 5 lines, we will write to 5 Z1SSV_ITEMS entries, each will have its own BLOB field. Whatever is in the file on each line will be written in each BLOB field. There will be no transformations or mappings on this data. In this example, the final IDOC for this file would have 1 blank entry for Z1SSV_ITEMS_SUMMARY and 5 Z1SSV_ITEMS entries, each with one BLOB.

Thanks and Regards,

Manoj

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Mar 05, 2007 at 09:23 AM

    Hi,

    You need to popoulate the IDoc Conteol Record EDI_DC40. Disable this Segment in your mapping in the grpahical mapping edtory.

    The values for the Idoc control record will be filled directly in the runtime from the SLD.

    Regards

    Bhavesh

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.