Resending Private Process Messages

Business level Acks sent to partner: ACK_TO_TP

This state is resendable if the partner requested a Business level Acknowledgment, for example, TA1, 997 for X12

Message from partner: EDI_LOGGED_TO_FILE

When the Log Raw EDI Request to File feature is enabled for inbound, you can resend messages previously sent from your partner to yourself as if it was resent by the partner. BusinessConnect Container Edition reprocesses the resent message.

The Log Raw EDI segment should be enabled on the trading host for inbound.

Message from partner: EDI_TXN_FROM_TP

Same as EDI_LOGGED_TO_FILE except that you can send individual transactions instead of the whole interchange.

To use this resendable state, you must enable Log Raw EDI Segments to File and Include Envelope Segments at the Transaction level, and provide a value for Store Location value on the trading partner side for the inbound.

New request from back-end private process: RECEIVED_FROM_PP

BusinessConnect Container Edition validates and converts payloads as appropriate and uses the primary transport to resend messages to the partner.

InitiatorResponse to private process: RESPONSE_TO_PP

BusinessConnect Container Edition can resend these private process messages to JMS.

ResponderRequest to private process: REQUEST_TO_PP

BusinessConnect Container Edition can resend these private process messages to JMS.

ACK ACCEPTED

The transaction that is sent out has received a positive business acknowledgment that was requested and was successfully completed with no EDI validation errors.

This status can/cannot happen depending on the acknowledgment that was expected and the acknowledgment that was created by the Trading Partner.

ACK ACCEPTED WITH ERRORS

The transaction has received a negative business acknowledgment and was not successfully completed with no EDI validation errors by the partner. This status means that the transaction was accepted, but errors were noted in the transaction.

This status can/cannot happen depending on the acknowledgment that was expected and the acknowledgment that was created by the trading partner. The actual error condition is defined in the acknowledgment description and in the ack code that was sent by the partner.

ACK PENDING

The transaction is waiting for a business acknowledgment from the partner.

This status can/cannot happen depending on the acknowledgment that was expected and the acknowledgment that was created by the trading partner.

ACK REJECTED ERROR

The transaction has received a negative business acknowledgment and was rejected due to EDI validation errors by the partner.

This status can or cannot happen, depending on the acknowledgment that was expected and the acknowledgment that was created by the trading partner. This transaction cannot be reconciled after this error.

ACK TIMEOUT ERROR

The transaction is waiting for the business ack and has not received within the timeout interval. The transaction cannot be reconciled after this error.

ANY

Any transaction that occurred.

ANY ERROR

Any error that occurred.

ANY PENDING

Any transaction that is pending.

CANCELED

The transaction was scheduled and later deleted from the message queue log.

COMPLETED

The individual summary rows are completed and no further audit trail is pending. It also means that the transaction has completed successfully if there were no acks were expected.

COMPLETED WITH ERRORS

DENIED

The transaction cannot be accepted by this partner due to partner/transaction level security being enabled and the message that was received does not follow the security agreement that was agreed between the partners.

ERROR

There were general errors during the processing of the transaction.

ERROR ACK CREATION

There were errors encountered during the creation of the acknowledgment on inbound. This can be due to missing guidelines.

ERROR ACK RECONCILIATION

There were problems in reconciling the business acks with the transactions that were sent out. The problems can be several: ack codes are not correct, database problem in retrieving the original ack option that was expected, and so on.

ERROR CONFIGURATION

There were problems in identifying the partner and cannot retrieve the business agreement.

ERROR PARSING

There were problems encountered in parsing the EDI document due to syntactic errors in the document.

ERROR SECURITY

There were errors encountered in digitally signing/authenticating or encrypting/decrypting the EDI document due to bad/wrong public or private keys.

ERROR TRANSPORT

The transaction could not be sent due to problems contacting the partner through the transport that was configured to be sent.

ERROR VALIDATION

Indicates there were errors in the EDI validation. Can be used to search for transactions with only the ERROR VALIDATION status.

INFO VALIDATION

Indicates that the EDI document has some informational category of errors which do not cause the transaction to be rejected. Can be used to search for transactions with only the INFO VALIDATION status. Used by HIPAA users only.

PENDING

The transaction has not yet completed all required states.

RECEIPT PENDING

Indicates that the transaction that was sent is waiting for a transport level receipt from the partner. Business acknowledgments cannot be reconciled even if they are received before the receipt is received. Only occurs when AS1 or AS2 transport is used.

SCHEDULED

The transactions are scheduled to be sent to the partner.