Ansicht
Dokumentation

RNCEDIRECREATEFILE - IS-H: Recreate all Messages of an EDI File

RFUMSV00 - Advance Return for Tax on Sales/Purchases   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Title

Recreate All Messages of an EDI Outbound File

Purpose

This program is used if you want/have to recreate all messages of an EDI file, which has already been sent, without processing application data. This is usually only necessary following errors situations that cannot be resolved any other way.

This program recreates these messages based on the current database status. The messages that are recreated do not refer to any files. When they are ready to be sent, the system takes them into account during the next file creation (like all other messages that are ready to be sent).

It is not possible to create exactly the same file in this way because usually there will be a number of new messages available by the time of the next file creation. If you do want to reconstruct an old file just as it was, you must use the create message file program (RNC30101) in the relevant processing mode.

Integration

Prerequisites

All messages of a file must still be contained in the EDI status management table NC301S with their file reference. The file management record does not have to still exist as such, but you should only delete it (if you must delete it at all) after the messages have been recreated.

Check this using program RNC301U2 by selecting the messages sent with the data collection point and the corresponding collection point related sequence file number. Exactly those messages that you select in this way are recreated with this program. Before executing the program ensure that the file number and messages are correct. Recreation cannot be reversed.

Depending on the errors which made it necessary to recreate messages, you must satisfy the following requirements:

• Existing messages that have already been stored in EDI management with file reference should be retained. This means in particular that the recipient does not expect the file with the same sequence number.

In this case, the messages of a file must all have the status "sent and not acknowledged" or "errored, rejected". Only these status can prevent old messages from being deleted when messages are recreated. The correct status in this situation is "errored, rejected". You should set this status (using program RNC301U6) if you have not already done so.

• Existing messages which have already been stored in EDI management with data reference should no longer exist when messages have been recreated. The file with the sequence number used last time in particular should be transmitted again.

In this case, you should set all messages of a file to the status "never sent and incomplete or errored". This status ensures that when messages are recreated, the old messages will be deleted. The file reference will also disappear. Before you remove a file management record you should be absolutely sure that no more messages exist which refer to this file.

If this is the case after you have recreated messages, then you probably selected and recreated the wrong file. Contact SAP immediately before other inconsistencies are caused. Do not create any more files until the reason for this has been established.

Features

Messages are recreated based on the current database status. This may mean that messages do not look the same as when they were originally sent.

In particular, this can lead to communication problems if the partner has accepted and imported further files in the meantime despite this file being refused. This is an incorrect response in the communication procedure and causes sequential problems that can rarely be solved.

Selection

Enter all selection parameters. Make absolutely sure that you have entered the correct data collection point specific file number (program RNC301U2).

Standard Variants

Output

The system outputs the number of messages that were recreated.

Activities

The messages themselves are created in the next run of the message formatting program (program RNC30100).

Example

BAL Application Log Documentation   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4660 Date: 20240520 Time: 095421     sap01-206 ( 95 ms )