Kontakt

Ansicht
Dokumentation

RNC301I2 - IS-H EDI: Inbound Messages, Manual Postprocessing

RNC301I2 - IS-H EDI: Inbound Messages, Manual Postprocessing

CPI1466 during Backup   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Description

EDI Worklist

This worklist is used to postprocess the EDI messages imported by the RNC301I0 program (data import program).
Two types of message are of significance here:

  1. Errored messages that could not be imported.
  2. Messages that cannot be postprocessed automatically by IS-H and must be checked by an administrator, for example, ZAHL, MBEG.

In addition to specifying the worklist displayed, you can also further restrict the messages displayed using certain selection criteria.

Do not forget to save your work from time to time to limit the size of the internal change management tables and ensure optimum system performance.

Requirements

To execute this program, you need the authorization S_PROGRAM with the action SUBMIT for the authorization group specified in the report attributes.

The authorization N_EINR_REP is also required for the institutions in question and the report. If this authorization is not available for certain institutions, the relevant data cannot be output or changed.

Output

The program functions with two modes:

  1. File mode
  2. Message mode

File mode:

In this mode, the system displays the files for which an error occurred early on during the import, thus preventing any messages from being extracted from the file. The files and the corresponding messages are simply displayed. No further processing is possible. Please correct the file to be imported, and then repeat the import operation.

Message mode:

Only one message is displayed at a time.
Any errors that have occurred are also displayed.
The contents of the segments are also displayed field by field.

Functions of the work list:

  1. You can jump between the individual messages with the arrow keys.
  2. By positioning the cursor on the field content of the segments displayed and then executing the Replace function, you can change the contents of a field.
  3. You can change the status of the message.
    Please note, however, that changing the status of a message can have further consequences. The following status values are possible:
    1. Completed (ok, processing successfully completed)
      If you choose this status, any existing error messages as well as the individual segments for returning data (NC301W) and error confirmations that have not yet been sent are deleted. Following this, the message can only be displayed with RNC301U2 (and no longer with RNC301I2).
    2. External error
      You can only choose this status if at least one external error has been detected. The individual segments for returning data are stored in NC301W. An EDI order is generated automatically and sends an error message confirmation to the original sender the next time the messages are formatted.
    3. Internal error (manual or automatic processing)
      You should choose automatic processing if the system set the status of the message to "internal error, manual processing" and the detected error was only a temporary problem (locking problem or missing Cutomizing entry). If the problem is resolved, you can then trigger processing with the report RNC301I1. You should do this straight away, and then check whether processing has been successful. If this is not the case, you have to set the status of the message and file to "New, received", and then upload the message again.
      You should choose manual processing if you cannot correct the error straight away. In this case, you should inform the administrator responsible who must then check whether an error is actually present in the data record (the status is then changed to "external error") or whether the information contained in the message can be evaluated in IS-H (the status can then be set to "completed").
    4. For processing
      This status indicates that the message was imported correctly but a technical method for updating the data in a transaction (for example, for ZAHL) has not been implemented. In this case, please notify the financial accounting department accordingly. You can then set the status to "completed".
  4. You can add any errors that you detect in the received data using the error codes specified by the EDI update, if possible.
    Please also specify the errored segment and the number of the affected field. If the error is on the sender side, also specify the status 01 (external error).
  5. Errors that have been corrected can be deleted.
  6. You can display the case overview (case monitor) to view all of the messages for a particular case.
  7. You can display the case list.
  8. You can branch to the insurance provider transaction.
  9. With messages relating to insurance verification or medical grounds, you can call the relevant transaction by double-clicking the message.
  10. You can view the long text of an error message (providing that one has been defined) by double-clicking the message.
  11. With particular procedures which use a hold date for transmitting messages, you can unlock these messages for transmission by choosing Unlock messages on hold.

Example






Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 5649 Date: 20240531 Time: 041046     sap01-206 ( 101 ms )