Reference
- Differences in enveloping, de-enveloping, and transformation behavior in Sterling B2B Integrator and SPE
If you customarily use Sterling B2B Integrator, you might see the following differences in your enveloping, de-enveloping, or transformation operations when you use SPE. - SPE Deenveloping Service
The SPE Deenveloping Service parses an inbound, enveloped EDI payload, checks the document for compliance, and extracts the transaction sets that it contains for further processing. In addition, Sterling B2B Integrator users can pass any parameters into SPE , and therefore benefit from the Sterling B2B Integrator visibility functionality. This visibility functionality includes information on what SPE is attempting to do (envelope, de-envelope, transform, or run a driver), and whether the action succeeded or failed. Also, every event includes tracking information that can be passed in by the application that hosts SPE . - SPE Transformation Service
The SPE Transformation Service takes document input from the primary document and uses a provided map to transform the document into another format. In addition, Sterling B2B Integrator users can pass any parameters into Standards Processing Engine, and therefore benefit from the Sterling B2B Integrator visibility functionality. This visibility functionality includes information on what SPE is attempting to do (envelope, de-envelope, transform, or run a driver), and whether the action succeeded or failed. Also, every event includes tracking information that can be passed in by the application that hosts SPE. - SPE Enveloping Service
The SPE Enveloping Service applies a standard-specific envelope to the transaction set messages that it receives as input. In addition, Sterling B2B Integrator users can pass any parameters into SPE, and therefore benefit from the Sterling B2B Integrator visibility functionality. This visibility functionality includes information on what SPE is attempting to do (envelope, de-envelope, transform, or run a driver), and whether the action succeeded or failed. Also, every event includes tracking information that can be passed in by the application that hosts SPE.