Description
This program is a special utility for data transmission pursuant to §301SGB V in Germany and is not required in any other country.
With EDI pursuant to §301, several business transactions can betransferred in one message (separated by the service segments UNH andUNT). This contradicts the transaction concept of a message with theresult that effective error handling (troubleshooting) is no longerpossible. For this reason, SAP has decided N O T to support thiserrored logic in the standard EDI interface. Messages of this type arenot generated in SAP nor are they intercepted by the standard interface.
This program was created to import inbound files containing severaltransactions in one message. The program analyzes the original fileaccordingly. If it detects several transactions in one message, the fileis copied (extension '.bak'). The system then attempts to create anEDI-compatible file from this copy.
A corresponding message group (UNG - UNE) is created from each message(UNH - UNT) in the original file. This group contains all of thebusiness transactions in the original file as a separate message withinthe group.
If an error occurs, the backup copy is still available. The condition ofthe original file is then undefined.
Once the program has been executed successfully, the EDI-compatible fileis stored under the orginal name (in the same directory). The backupcopy (original format) is not deleted.
Despite the fact that a backup copy is created, we strongly recommendthat you copy the original file to a different directory before youexecute this program to prevent any data from being lost.

Precondition

• To execute this program, you require the authorization S_PROGRAM with
the action SUBMIT for the authorization group specified in the reportattributes.

• The order file for the file in question must be located in the same
directory.

• The files or the directory must be readable and writeable (for the
system user, usually c31adm or similar).

• The file must be a regular reception file for a correctly configured
data collection point in the system. This information is required tocreate the file with the correct character set.

Output
A brief log is output on the screen. Please also note any messagesdisplayed in the status bar at the bottom of your screen.
If an error occurs, the backup copy is retained. The status of theoriginal file is then undefined.
After the program has run successfully, an EDI-compatible file is storedunder the original name (in the same directory). The backup copy isretained (original format).

Example
Assuming that the original file has the following structure: all UN*segments and all GVF business transactions are listed, 'UNH1' is thefirst UNH segment in the file and GVF3 (3rd business transaction) iswritten to the entire file. Indentations are only intended to illustratethe hierarchy structure. The dots '...' represent information for thepreceding object:
UNB...
UNH1...GVF1...GVF2...GVF3...UNT1...
UNH2...GVF4...UNT2...
UNH3...GVF5...GVF6...UNT3...
UNZ...
The following EDI-compatible file is then created from this file:
UNB...
UNG1...
UNH1...GVF1...UNT1...
UNH2...GVF2...UNT2...
UNH3...GVF3...UNT3...
UNE1...
UNG2...
UNH4...GVF4...UNT4...
UNE2...
UNG3...
UNH5...GVF5...UNT5...
UNH6...GVF6...UNT6...
UNE3...
UNZ...