EDI Post Processor Service
The following table provides an overview of the EDI Post Processor service:
- System name
- EDIPostProcessorType
- Graphical Process Modeler (GPM) categories
- All Services, EDI
- Description
- Handles deferred sequence checking and acknowledgement processing of X12 interchanges, as well as duplicate control number checking. It is called if the inbound envelopes require sequence checking. If sequence checking is not required, acknowledgement processing is done by the X12 Deenvelope service.
- Business usage
- Its processing is done in parallel with EDI translation, thereby improving system performance.
- Usage example
- The X12 Deenvelope service determines that an inbound purchase order matches envelope definitions which specify that sequence checking should be performed. The service continues to process the inbound purchase order, performing all required compliance checks except for the sequence check, and puts the inbound interchange in a sequence check queue. The EDI Post Processor service runs after the X12 Deenvelope service completes and picks up all interchanges from the sequence check queue. It performs the sequence check, generates any acknowledgements that are necessary, and invokes the specified business processes to handle the purchase order.
- Preconfigured?
- No
- Requires third party files?
- No
- Platform availability
- All supported application platforms.
- Related services
- This service is intended to be used in conjunction with the X12 Deenvelope service.
- Application requirements
- No
- Initiates business processes?
- Yes
- Invocation
- Runs only by the X12DeenvelopeUnified business process.
- Returned status values
- Success – The service will return success if it processes all queued interchanges without finding compliance errors.
- Error – The service will return error when it encounters non-compliant data and envelope definitions are set to not allow non-compliance.
Document Tracking Levels and Performance
You can boost EDI performance in the IBM® Sterling B2B Integrator by using the TRACKING_LEVEL parameter to adjust the tracking level for business processes.
You set the default global settings for the TRACKING_LEVEL parameter in the enveloping.properties file. However, these global settings can be overridden for certain EDI-related services by using the BPML-only TRACKING_LEVEL parameter. This enables you to obtain maximum EDI performance in some business processes and maximum search and tracking functionality in others. This parameter can be set for the following services:
Inbound Services
- CII Deenvelope service
- EDIFACT Deenvelope service
- EDI Post Processor service
- X12 Deenvelope service
- Generic Deenvelope service
Outbound Services
- EDI Encoder service
- CII Envelope service
- EDIFACT Envelope service
- Envelope Generic service
- X12 Envelope service
This performance boost is done at the expense of Tracking and Search functionality. The tracking level setting affects the following EDI functionality:
- EDI Correlation Search
- EDI Document Tracking
- EDI Reporting
The TRACKING_LEVEL parameter is not available in the IBM Sterling B2B Integrator service configuration or in the GPM. It must be added manually to the BPML. Use the TRACKING_LEVEL parameter with one of the following settings:
- Setting
- Description
- none
- Provides the largest EDI performance boost with the least tracking and search functionality. EDI Correlation Search, EDI Document Tracking and EDI Reporting are nonfunctional.
- basic
- Provides an EDI performance boost while also providing search functionality. EDI Correlation Search is functional. EDI Document Tracking and EDI Reporting are nonfunctional.
- full
- Default setting. Provides the lowest EDI performance with the highest search and tracking functionality. EDI Correlation Search, EDI Document Tracking and EDI Reporting are fully functional.