ECRTP is a data transformation engine, which analyzes, transforms, and routes messages. ECRTP includes map files, trading partner database, and log files.
Map files contain the business rules and logic that define the relationships between incoming and outgoing data.
Trading partner database contains information that route messages between trading partners and to select the specific map that should be run.
Log files maintain an audit trail of the transaction processing.
This table identifies documentation specific to ECRTP 4.2.
Title |
Description |
Location |
|---|---|---|
ECRTP Reference Guide |
Intended for map developers, this document tells you how to use ECRTP to analyze, transform, and route messages. |
ecrtprg.pdf in \doc folder of your install directory. |
ECRTP Installation Key |
Includes the product key you need to install ECRTP. |
Print only |
CR |
Description |
|---|---|
308309 |
Problem: When running ECRTP the error message when missing an ST is confusing.� Resolution: ECRTP has been updated to correctly report an error when the ST is missing. |
351165 |
Problem: The behavior of 4.0.5 ECRTP on AIX was different from 4.0.5 ECRTP on other platforms and 4.0.3 on all platforms. There are two errors related to this problem. Incorrect error messages were generated and invalid null values were output instead of spaces. � Resolution: The problem was caused by a local variable not being initialized correctly. The local variable was identified and is now initialized correctly. |
351951 |
Problem: ECRTP did not correctly check for minimum length errors for decimal data types. The definition of the decimal datatype says, “The length of a decimal type data element does not include the optional leading sign or decimal point”. Thus '.294' will be an invalid value if the minimum length of the element is 4. ECRTP caught this error on all other decimal data types except for Real Number. � Resolution: Fixed. Minimum length requirements for the Real Number data type is now computed correctly. |
354659 |
Problem: When there is mixture of good and bad ST/SE segments in the input EDI file, one extra bad SE segment was generated and written into the good.edi file. This extra bad SE segment belongs to one ST/SE section and should only be written into the bad.edi file.� Resolution: ECRTP's logic was changed to determine whether the current segment will be written into output stream or not. |
354659 |
Problem: When there are mixtures of good and bad ST/SE segments in the input EDI file, one extra bad SE segment was generated and written into the good.edi file. This extra bad SE segment belongs to one ST/SE section and should only be written into the bad.edi file. � Resolution: ECRTP's logic was changed to determine whether the current segment will be written into output stream or not. |
355941 |
Problem: Running supplied inbound map and input file, no CLM1101 data is used, however invalid error: “(1297) ERROR: Value- is not found in Table- Causes.XRF” is reported. � Resolution: ECRTP will process the entire segment looking for data. This includes running cross-reference tables when encountered. In order to avoid the error above, a blank entry should be added to the cross-reference table. Once this is done, the error will no longer be received. It is recommended that a blank entry be added to cross-reference tables in which this error (in this case) is not wanted. |
356592 |
Problem: A change was made that disallowed Trade Agreement routing in EC Gateway. � Resolution: Fixed. Now both Trade Partner and Trade Agreement routing work through EC Gateway. |
ECRTP uses KeyFields and LinkFields to process outbound user files. Some customers requested additional information to explain why a record remains in the buffer even if a KeyField/LinkField break was hit when reading it. The record remains in memory by design.
For example, if ECRTP processes a purchase order file and a line item file, RTP reads a purchase order number, and then starts to read line items from the line item file. When RTP reads a line item record that does not share the same link field with the purchase order, the program breaks, but keeps the line item record in memory. Processing of the line item record occurs after RTP reads a new purchase order that matches the line item record's link field.
ECRTP has a limitation of 2GB on the maximum file size it can process.
