Multiple Idoc to File

[Former Member]

Hi,

Can you guide me in configuring the below activity.

IDoc to File Mappings

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

Another special note for moving files to AMES, is that there needs to be an Acknowledgement file written out to the file server where we will be moving the IDoc files. This Acknowledgement file is read by AMES first and all it contains is the number 1. If this file exists, AMES knows that the IDoc file it is associated with has been completely FTP’ed to the server and is not in the middle of being written. A JDPS example of the current File and Acknowledgement File names are included in the message types below. Here is an example of what to expect and what will change (the pieces surrounded by <> are what will be change, the company code depends on China):

Filename - PE00wiprtdet20070105153225.DAT

<company code>wiprtdet<date yyyymmdd><assigned #>.DAT

Acknowledgement Filename - PE00ackwiprtdet20070105153225.DAT

<company code>ackwiprtdet<date yyyymmdd><assigned #>.DAT

These Filenames will be sent with the incoming IDocs.

Z???_AMES2_CARRIER

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>carrier<date yyyymmdd><assigned #>.DAT

<company code>ackcarrier<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_COMP_SERIAL_STATUS

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>cscgstat<date yyyymmdd><assigned #>.DAT

<company code>ackcscgstat<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_DELIVSTATUS

Z1SSV_ITEMS_SUMMARY -

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>delivstat<date yyyymmdd><assigned #>.DAT

<company code>ackdelivstat<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_DELPRODORD

Z1SSV_ITEMS_SUMMARY -

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>deltrknum<date yyyymmdd><assigned #>.DAT

<company code>ackdeltrknum<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_MATCC

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>matcc<date yyyymmdd><assigned #>.DAT

<company code>ackmatcc<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_MATMAS

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>matmas<date yyyymmdd><assigned #>.DAT

<company code>ackmatmas<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_ORD_SEQUENCE

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>ordseq<date yyyymmdd><assigned #>.DAT

<company code>ackordseq<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_PRODORDER

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>prodorder<date yyyymmdd><assigned #>.DAT

<company code>ackprodorder<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_PRODSTATUS

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>prodstat<date yyyymmdd><assigned #>.DAT

<company code>ackprodstat<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_QNOTESTATUS

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>qnotstat<date yyyymmdd><assigned #>.DAT

<company code>ackqnotstat<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_REMORDER

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>remorder<date yyyymmdd><assigned #>.DAT

<company code>ackremorder<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_REMSTATUS

Z1SSV_ITEMS_SUMMARY -

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>remstat<date yyyymmdd><assigned #>.DAT

<company code>ackremstat<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_SERIALNBR

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>snbatch<date yyyymmdd><assigned #>.DAT

<company code>acksnbatch<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_SORDOPT

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>sordopt<date yyyymmdd><assigned #>.DAT

<company code>acksordopt<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_STOCK_TRANS_DELIV

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>stktrans<date yyyymmdd><assigned #>.DAT

<company code>ackstktrans<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_TRKNUM_ERR_STATUS

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>oerrstat<date yyyymmdd><assigned #>.DAT

<company code>ackoerrstat<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_TRORDSTATUS

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>trordstat<date yyyymmdd><assigned #>.DAT

<company code>acktrordstat<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_WIBOMDET

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>wibomdet<date yyyymmdd><assigned #>.DAT

<company code>ackwibomdet<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Z???_AMES2_WIPRTDET

Z1SSV_ITEMS_SUMMARY

This data will not be mapped into the AMES file.

The only piece of this that may be used is the HOST_FILENAME, which would contain the name of the file we want to write out to the AMES server to pick up.

Here is an example of the Filename and Acknowledgement Filename for this message type.

<company code>wiprtdet<date yyyymmdd><assigned #>.DAT

<company code>ackwiprtdet<date yyyymmdd><assigned #>.DAT

Z1SSV_ITEMS

There can be 1 to many entries for this segment and it contains only one field, BLOB. This data from this field will be copied directly to the file created. Each Z1SSV_ITEMS entry will be written to one line in the output file. If this IDoc contains 25 Z1SSV_ITEMS entries, there will be 25 lines in the output file, corresponding to each BLOB entry.

Thanks and Regards,

Manoj

[Former Member]

Hi Manoj,

Yes. We can create a single output file for two or more idocs(of the same type) using BPM.

In the BPM, you need to have a

1. Receive step: To receive the message from the R/3 system.

2. Collect(container): You need to collect idocs for a specified interval(in a maultiline container). You need to use correlation, so that you can collect idocs for a particular type.

3. Transform: To carry out the mapping.

4. Send : to send the message to the receiver.

Interfaces: The source interface should have an occurence of 0..ub and the target interface 1..1

In message mapping: What we need is, multiple idocs in a single file. i.e, a file, having a single header and multiple idocs under it.

So, map the source idoc header to target header(which is of occurence 1..1).

Map the child(of the source header) to a target node (which has occurance of 0..ub).

Also please go through this Blog...

/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm

Regards,

Abhy Thomas