4.1.8 Pre-built EDI X12 solution components
LANSA Composer is supplied with a limited number of pre-built transformation maps, staging database tables and export and import processors and document viewers for selected EDI X12 transactions.
These pre-built components may serve as a pro-forma solution for those transactions, but more especially as examples of a completed solution upon which you might base a solution for other types of transaction documents used by your organization.
The EDI X12 transactions and the associated pre-built components are listed below:
|
X12 Transaction Type |
Inbound and/or Outbound Maps |
Import and/or Export Processors and Document viewers |
Staging Database Tables Supplied |
|
810 |
O810_4010 |
n/a |
Yes (EDI810*) |
|
850 |
I850_4010 |
EDI850IMP |
Yes (EDI850*) |
|
855 |
O855_4010 |
n/a |
Yes (EDI855*) |
|
997 |
I997_4010 |
EDI997EXP |
Yes (EDI997*) |
For more information on the types of components mentioned above and the role they play in the transaction document processing framework, please refer to:
4.1.7 Transformation Maps for Transaction Document Processing
Source code for the pre-built export and import processors and document viewers mentioned above is included in the LANSA Composer development package. For information on finding and installing the LANSA Composer development package, please refer to Before you begin your Custom Activity .
Note the supplied import and export processors read from or write to sample application database tables installed with LANSA Composer. If you wish to adapt these supplied components for use with your own application, you will, at the least, have to replace the import and export processors with ones that reference your own application database.