EDI Message Control Working part two

The present post is in continuation with previous post EDI Message Control how it works part one and going through it give a sort of feeling of continuation.

After the output proposal process is complete, the list of proposed outputs displays on the output control screen of an application, as shown in figure below. The output control screen is usually available at the header level, but in some cases it is available at other levels. For example, with sales orders, it is available at the sales order header and at the sales order item level.

To reach the output control screen of an application, we have to follow the following steps.

Go to the application document with which you are working (a sales order, purchase order, delivery, or billing document).

1. Look for Extras, Output or Header, Output or Header, Messages on the menu, depending on the application area. At the line−item level, you look for Item, Output.

2. The initial status of these outputs is 0 (not processed), displayed as an icon with a yellow light. After the output has been successfully issued it is in status 1 (successfully processed), displayed as a green light icon.

The user entering the application document can carry out the following editing operations.

1. Delete proposed outputs.
2. Change timing.
3. Select new outputs from the list. The same output cannot be listed twice in status 0.
4. Copy a previously processed output for reprocessing.

If the output medium is 6 (EDI) for an output, the partner number in the proposed output is validated against a partner profile entry. If an entry does not exist in the partner profile table, you cannot save the output.

Output Processing

When the final selection of the output is complete, you can save the application document. A record for each proposed output is saved in the NAST table with the following values.

1. Application ID ·
2. Application document key (prefixed with zeros if fewer than 10 characters) ·
3. Output type ·
4. Output medium ·
5. Output timing ·
6. Status code with value 0 (not processed) ·

We can view a complete list of fields in the NAST table via transaction SE11.

The RSNAST00 program processes entries in the NAST table. This program is started immediately for NAST entries whose timing is set to immediate. For other NAST entries, you must schedule this program. The selection list for this program allows you to specify various parameters.

After RSNAST00 selects a record for processing, it checks the TNAPR table for the processing program associated with an output medium. For EDI, a standard routine, EDI_PROCESSING, exists in the RSNASTED program.

The EDI_PROCESSING routine reads the Message control record in the partner profile and determines the process code. The process code points to a function module. The function module has a standard interface for its input and output parameters. One of the input parameters is the NAST record.

This function module then has all the information necessary to read the application document data and formats the document for the message to be generated, using the IDoc format. The output parameters of the function module are the IDoc data and the control record.

The EDI_PROCESSING program creates a physical IDoc from the data passed back to it from the function module. Then the IDoc is ready for the ALE service layer, where it goes through version change, filtering, and conversion, and is subsequently sent to the operating system through a file port.

Related Posts

EDI Message control configuration and part two
Maintaining partner profiles in EDI
EDI in bound parameters over view
Control table in message control
SAP ABAP SAMPLE CODE ALV SIMPLE REPORT