4.1.1 Overview of the Transaction Document Processing Framework
LANSA Composer provides a ready-made framework solution for transaction document processing. The framework can very quickly be modified and extended to:
- Handle specific types of transaction documents
- Take account of processing requirements specific to the customer's trading and processing environment.
This framework encompasses supplied LANSA Composer definitions and features working together to provide a near ready-to-use transaction document processing solution.
Document types and standards
LANSA Composer provides support for and definitions that describe certain characteristics of transaction documents such that inbound and outbound document processing can recognize them, validate them and invoke the appropriate processing sequence to further process them.
A core set of and definitions are supplied with LANSA Composer for the document types most commonly used, but you can extend these with your own definitions according to your organizations requirements and trading relationships.
For more information on creating or modifying and definitions, please refer to:
4.1.3 Document Types and Document Standards
Trading Partners
The use of Trading Partner definitions and features is central to the operation of the supplied transaction document processing framework. Trading Partner definitions provide links to directories, configurations and transformation maps used to process transaction documents. In addition, the Trading Partner Data Interchange attributes provide additional values used in transaction document processing. For more information refer to: 4.1.4 Trading Partner support for Transaction Document Processing.
Activities
Of course, transaction document processing solutions can and do make use of any or all of the supplied LANSA Composer Activities.
However, there is a subset of Activities supplied with LANSA Composer that are very specifically intended for and associated with the transaction document processing framework. These are listed in:
4.1.5 Activities for Transaction Document Processing
Processing Sequences
A core part of the transaction document processing framework is the set of processing sequences that have been pre-built and supplied with LANSA Composer for this purpose. These are listed and further described in:
4.1.6 Processing Sequences for Transaction Document Processing
Transformation Maps
Transformation maps are almost always an integral part of a transaction document processing solution. The pre-built processing sequences that are central to the transaction document processing framework assume a particular pattern for the transformation maps that it invokes and LANSA Composer supplies "model" transformation maps that match this pattern. For more information refer to:
4.1.7 Transformation Maps for Transaction Document Processing
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. For more information, refer to:
4.1.8 Pre-built EDI X12 solution components
Application program interfaces (APIs)
LANSA Composer allows you to extend the transaction document processing framework in several ways by providing application program interfaces (APIs) in the forms of ancestor components for your own LANSA components and by providing callable LANSA interfaces. These interfaces allow you to provide extended support for specific transaction types and to better integrate the solution into your own applications. For more information, refer to:
4.1.9 Application program interfaces (APIs)