EDI Transaction Control

EDI Transaction Control allows you to display the list of inbound and Outbound EDI Transactions, with the option to drill down to view the detail of each EDI Transaction. 

The primary use of EDI Transaction Control is to view the status of EDI Transactions and to reset transactions in Error following the resolution of the original reason for EDI Processing failure. 

To display the EDI Transaction Control, perform the following:

• From the main "ECS/integrated email" panel click on the drop down menu "e-commerce",  select "EDI" then select "EDI Transaction Control" .

• The "EDI Transaction Control" window will now be displayed, listing all EDI Transactions:

       

• The options for Event Filter and Status Filter enables the user to configure which EDI Transactions are listed. Clicking on the Event Filter drop down prompt will display all the EDI Trading Partner Events that have been previously defined. Clicking on the Status Filter drop down prompt will display all the possible Status codes. Selecting "*ALL" will display all records .  

• Selecting an individual Transaction and clicking Delete will physically delete the Transaction Control record (File: IEXC) and all associated EDI Transaction detail records (File: IEYT)

• Selecting an individual Transaction and clicking Reset will reset the status of the transaction in error, ready to be processed again.  Note: Only Transactions in an Error status (ERR) can be reset. 

• Clicking the Refresh button will update the EDI Transaction Control Panel with any changes.  

• Selecting an individual Transaction and clicking Display (or double clicking) will display the detail of the EDI Transaction Control record. The following panel should be displayed: 

• The EDI Transaction Control Detail panel is an information panel, displaying the full details of the individual transaction control record:

• Transaction Ref is the Unique transaction identifier that is automatically assigned by the ECS/EDI Processor. The format is the processing date/time stamp followed by a sequential counter (YYMMDDHHMMSSxxx)

• Direction can be Inbound or Outbound.

• Event Id is the associated EDI Trading Partner Event Id that this Transaction relates to.

• The Trading Partner name relates to the EDI Trading Partner linked to this Transaction.

• The Sender Id contains the Trading Partner Identifier of the sender of the EDI transaction The Sender Id is a mandatory entry and may be required by the Business Application when mapping EDI data.  

• The Receiver Id contains the Trading Partner Identifier of the receiver of the EDI transaction. The Receiver Id is a mandatory entry and may be required by the Business Application when mapping EDI data.   

• The Protocol contains the form of communications used for sending Outbound EDI Interchanges. The Protocol is used by external communications applications  to determine how the EDI interchange file should be transmitted to the Trading Partner.  

• The Input Path is only used for Inbound Transactions and contains the full path of where the input EDI Interchange was selected from.

• The Output Path is used for Inbound and Outbound Transactions and contains the full path of where the EDI file was placed following processing. 

• The Application Reference can be populated by the Outbound Application Mapping program (ie. Order or Invoice number) to provide a user friendly link between the EDI Messages and Business Application data. Application Reference is only used for Outbound Transactions. The field XCAREF on IEXC (50AN) requires populating by the relevant application integration mapping program for this to be displayed.

• The Original Transaction Reference is used for Outbound XML Transactions only and stores the original application transaction reference generated by the Business Application mapping program. The original Transaction Reference is automatically replaced with the unique Identifier conforming to the ECS/XML Processor standards.

• The Last update User, Date and Time of the related EDI Transaction Control record is displayed. 

• The EDI Transaction Control Status can be one these possible options, RDY, ERR, FIN, UIP, PIP, UNP, CRT. The definition of the status codes differs according to the transaction direction: 

  • Inbound  Transactions:

    • UIP - Unpack in Profgress. The ECS/EDI Processor has successfully received the Inbound Interchange file and it is being unpacked into individual messages and Validated. This status code is assigned by the ECS/EDI Processor.

    • UNP - Unpacked. The ECS/EDI Processor has successfully unpacked the Interchange into Inbound Message files and the data is ready for database conversion. 

    • RDY - Ready. The ECS/EDI Processor has successfully processed the Inbound XML document and the data is ready to be mapped to the Business Application. This status code is assigned by the ECS/XML Processor.

    • FIN - Finished. The data has been successfully mapped to the Business Application. The update of this status code is the responsibility of the custom business application mapping program. 

    • ERR - Error. The ECS/EDI Processor has failed to process the Inbound EDI transaction and has emailed an Error report to the designated EDI Event Administrator. This status code is normally assigned by the ECS/EDI Processor but can also be used by the custom mapping program to report application integration issues.

  • Outbound Transactions:

    • RDY - Ready. The data has been successfully mapped from the Business Application by the custom mapping program to the ECS/EDI Transaction database. (Files: IEXC & IEYT). The Transaction is ready for the ECS/EDI Processor convert the data from AS/400 database format to EDI Message format. The update of the status code to "RDY"  is the responsibility of the custom business application mapping program.

    • CRT - EDI Message Created. The ECS/EDI Processor has successfully generated the Outbound EDI Message and it is now ready for EDI Validation and Packing into an EDI Interchange file. This status code is assigned by the ECS/EDI Processor.

    • PIP - Pack In Progress. The ECS/EDI Processor is validating the individual EDI Messages and packing the Messages into  EDI Interchanges. The messages are grouped by Trading Partner. This status code is assigned by the ECS/EDI Processor.

    • FIN -  The ECS/EDI Processor has successfully validated the EDI Messages, packed the messages into EDI Interchange file(s) and placed the file in the located indicated within the Outbound Path ready for Transmission. This status code is assigned by the ECS/EDI Processor.

    • ERR - Error. The ECS/EDI Processor has failed to process the Outbound EDI transaction and has emailed an Error report to the designated EDI Event Administrator. This status code is normally assigned by the ECS/EDI Processor but can also be used by the custom mapping program to report application integration issues.

• The EDI Std/Msg/Ver displays the EDI Standard Set, Message Id, Message Version and Syntax Set associated with this EDI Message. These values are used by the ECS/EDI Processor to validate the content of the EDI Message.

EDI Transaction Control - Error Reset 

The ECS/EDI Processor validates Inbound and Outbound  Message content against the predefined EDI Standards database and Syntax Set. EDI Transactions will be placed into an Error Status ("ERR") if there is a problem with EDI Message and the error report will be automatically emailed to the designated EDI Trading Partner Event Administrator. Once the reason for the error has been rectified it is normal to attempt to reprocess the transaction in Error. This can be performed within the EDI Transaction Control detail panel.

The following is an example of the detail view of a transaction in Error, note the Error Reset command button in the bottom left hand corner, which is only displayed for EDI Transactions in Error.

Clicking the Error Reset command will change the status of the EDI Transaction record to a status ready to be processed the next time the ECS/EDI Processor is executed.

Diagnosing the problem with the EDI Message should be performed with the following aids: 

• Summary of Error message on Transaction Control detail panel. 
• Detailed email error report, automatically emailed to the EDI Trading Partner Event Administrator. 
• Viewing the EDI Message in Error. 

The above example shows that there is an Invalid character in the EDI Message as described by message "Invalid Character found in EDI Message. Character ^ not valid."

The content of the EDI Message in Error can be displayed by clicking on the Display button to display the following: 

The error is clearly identifiable in the second "NAD" segment, which contains the character ^ which is not listed in the Permitted Character set for the associated Syntax Set. 

This error could be resolved by configuring an Outbound Character Replacement for the associated Syntax Set to automatically replace the ^ character with and valid character to prevent this error occurring with future transactions.  

  <<<<< Back to ECS/EDI Menu <<<<< 

Copyright © 1998-2003 Electronic Commerce Solutions All rights reserved.

ECS/integrated email & ECS/ie are trademarks of Electronic Commerce Solutions, Ltd. Other brand names and product names used in this document are the trademarks and trade names of their respective holders and may be registered.