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.

Enveloping

If you customarily use Sterling B2B Integrator, you might see the following differences in your transformation operation when you use SPE.

Scenario Behavior or result that is seen with EDI enveloping in Sterling B2B Integrator Behavior or result that is seen with SPEEnveloping in SPE
An EDI input document is missing. Advanced status is reported as Expected Document Not Found. Advanced status is reported as No Documents to envelope..
An EDI input document is missing. The process data <Prev_NotSuccess_Adv_Status>Expected Document Not Found</Prev_NotSuccess_Adv_Status> is passed. The process data <Prev_NotSuccess_Adv_Status>No Documents to envelope.</Prev_NotSuccess_Adv_Status> is passed.
A mandatory block is missing in an input document. Advanced status is reported as All translated documents to process are empty.  
Correlation check results are viewed in the UI. Three document correlations are displayed: two for the primary or input document and the other for the enveloped document. The additional correlation for the primary or input document is the result of the X12EnvelopeUnified process, which takes place in Sterling B2B Integrator only.

The X12EnvelopeUnified process also results in an additional record in the document table.

 Two document correlations are displayed: one for the primary or input document and the other for the enveloped document.
Enveloping is done in deferred mode. The EDI_DOCUMENT_STATE table retains records for documents in "waiting to be enveloped' status after those documents are processed.
Action required: Remove records from the database.
SPE_EDI_DOCUMENT_STATE table records are deleted after documents in the status "waiting to be enveloped" are processed.

De-enveloping

If you customarily use Sterling B2B Integrator, you might see the following differences in your de-enveloping operation you use SPE.

Scenario Behavior or result that is seen with EDI de-enveloping in Sterling B2B Integrator Behavior or result that is seen with SPEDeenveloping in SPE
An EDI input document is missing. Advanced status is reported as Expected Document Not Found. Advanced status is reported as No Documents to deenvelope..
An EDI input document is missing. The process data <Prev_NotSuccess_Adv_Status>Expected Document Not Found</Prev_NotSuccess_Adv_Status> is passed. The process data <Prev_NotSuccess_Adv_Status>No Documents to deenvelope.</Prev_NotSuccess_Adv_Status> is passed.
Inbound document is missing a Transaction Set ID Code. A Service Configuration Error is reported in Status. An error is reported in Status.
Inbound document is missing a Transaction Set ID Code. The Status Report reads: No matching ST envelope was found. Interchange not processed. Please configure the appropriate inbound EDI envelopes and restart this business process. The Status Report reads: Resource X12-0:
No matching ST envelope was found. Interchange not processed. Please configure the appropriate inbound envelopes and reprocess this data.
ISA06 - SenderID is invalid in input A Service Configuration Error is reported in Status. An error is reported in Status.
ISA06 - SenderID is invalid in input The Status Report reads: No matching ISA envelope was found. Interchange not processed. Please configure the appropriate inbound EDI envelopes and restart this business process. The Status Report reads: Resource X12-0:
No matching ISA envelope was found. Interchange not processed. Please configure the appropriate inbound envelopes and reprocess this data.
Correlation check results are viewed in the UI. Five correlation records are displayed: 1 EDIDeenvelope document, 3 X12DeenvelopeUnified documents, and 1 FSA document.

The additional correlation is the result of the X12EnvelopeUnified process, which takes place in Sterling B2B Integrator only.

 Four correlation records are displayed: 3 SPEDeenvelope documents and 1 FSA document.
Documents are out of sequence. Out-of-sequence documents go to the EDI Sequence Check queue of Sterling B2B Integrator and can be seen in the EDI Sequence Check Queue section of the Sterling B2B Integrator UI. Out-of-sequence documents go to the EDI Sequence Check queue of SPE and can be seen in the EDI Sequence Check Queue under control numbers in the SPE UI.
Documents have duplicate control numbers. Control number history is maintained in Sterling B2B Integrator to identify documents with duplicate control numbers. Control number history is maintained in SPE for identifying documents with duplicate control numbers.
Reconciliation reports that originate from document acknowledgements differ.
  • Reconciliation does not show State or Status for Interchange/Group ack reconciliation details.
  • Message Level Acknowledgment Reconciliation details shows status 7.
  • Reconciliation reports are generally configured to be viewed in the Correlation Viewer.
  • Reconciliation shows State or Status for Interchange/Group/Message level ack reconciliation details.
  • Reconciliation reports are viewed as status reports.
  • Message Level Acknowledgment Reconciliation details shows status ACCEPTED.

Transformation

If you customarily use Sterling B2B Integrator, you might see the following differences in your transformation operation when you use SPE.

Scenario Behavior or result that is seen with EDI Transformation in Sterling B2B Integrator Behavior or result that is seen with SPETransformation in SPE
Map location is invalid. Not applicable.
  • Status shows a Service Configuration Error.
  • Advanced Status includes the invalid file path for the map server.
  • Status Report includes the invalid file path for the map server.
  • Process Data shows a message similar to this example: <Prev_NotSuccess_Adv_Status>Invalid filepath for Map Server Location: filepath/compiled_map_name.txo</Prev_NotSuccess_Adv_Status>
Correlations are displayed in the CORRELATION_SET table.

The parameters that display differ between Sterling B2B Integrator and SPE .
These parameters display in Sterling B2B Integrator only:
StandardVersionID
MessageFormat
Standard
TransactionControlNumber
Level
Direction
TransactionSetID
TransactionSenderID
TransactionReceiverID
TransactionCount
TransactionEnvelopeName
TransactionComplianceStatus
Common parameters: These parameters are common to both products:
TRACKINGID
Status
DocumentSize
TransactionDateTime/TranslationDateTime
These parameters display in Sterling B2B Integrator only:
TrackingType
Map
MapVersion
Common parameters: These parameters are common to both products:
TRACKINGID
Status
DocumentSize
TransactionDateTime/TranslationDateTime
Correlations are displayed in the CORRELATION_SET table. The number of documents in the DOCUMENT table increases by 2. The number of documents in the DOCUMENT table increases by 3.