Resolution:
/*There is no current Documentation available in Users Guide on the Message Types.

Here is a short description of each:
/*ReceiptInfoFromTradingPartner:*/
======================
This activity would be triggered when a AS1/AS2 receipt is received by
BC-EDI within the specified configured time period. This receipt is a transport level acknowledgement that the TradingPartner has received the message with full integrity and no errors were encountered with respect to the security of the message. This receipt does not acknowledge that the message has been validated/converted by the Conversion Engine.

/*ReceiptErrorFromTradingPartner:
=========================*/
This activity would be triggered when a AS1/AS2 receipt is received by
BC-EDI within the specified configured time period. This receipt is a transport level acknowledgement that the TradingPartner has received the message but errors were encountered while trying to decrypt, verify or decompress the message that was sent to the Trading Partner.  No Business Level acknowledgement is exchanged since the transport level receipt had failures.

/*ReceiptTimeoutErrorAdvisory:
=====================*/
This activity would be triggered when a AS1/AS2 receipt is not received
by BC-EDI within the specified configured time period. Normally this would occur, if an
AS1/AS2 message has been sent to the Trading Partner, but no transport level acknowledgement was received within the configured time period to receive the receipt. Any receipt received for this message after the timeout would not be processed.

/*AckTimeoutErrorAdvisory:*/
------------------------------

This activity would be triggered if the Business Level Acknowledgement (For EDIFACT, it is CONTRL) is not reached within the specified time as mentioned for the transaction that was sent to the trading partner. This Timeout advisory would be sent out only if an ack is expected and can be disabled by Trading Partner configuration.

*/InboundInterchangeLoggedToFile:/*
-----------------------------------

This activity would be triggered on Inbound after a document's Interchange boundary is identified and ready to be sent to the conversion engine. This activity is published only when EDI conversion and processing is enabled. This activity receives the interchange control information in the activity along with the TP Information. This activity is always published and cannot be disabled.

/*SecurityErrorAdvisory:*/
-----------------------

This activity would be triggered only from an incoming/outgoing secured message from/to either AS1 or AS2 transport is received/sent. Whenever the private key or the public certificate date has already expired, this activity would receive a message informing of the PKI expiry and would stop the Business Message to be processed. This
activity is always triggered and only on a PKI key/cert expiry.

/*SecurityWarningAdvisory:*/
--------------------------

This activity would be triggered only from an incoming/outgoing secured message from/to either AS1 or AS2 transport is received/sent. Whenever the private key or the public certificate date is about to  expire, this activity would receive a message informing of the PKI expiry and would continue the Business Message to be processed. This activity is always triggered and only on a PKI key/cert expiry about to happen. Default date to expiry check is 30 days and is configurable in the EDI.cfg file.


/*TransactionAckFromTradingPartner:*/
------------------------------------
This activity is triggered when a Initiator Acknowledgement message is sent by BusinessConnect as a result of reconciled transaction when a functional acknowledgement 997 or CONTRL is received from the Trading Partner. This would be triggered only if the outgoing transaction is expected to reconcile. If the Trading Partner does not expect a ack, this activity would not be triggered.

/*TransactionAckToTradingPartner:*/
-----------------------------------
This activity is triggered when a Responder Acknowledgement message is sent by BusinessConnect as a result of acknowledging the incoming EDI document received from the Trading Partner. This activity is triggered after successfully sending the functional acknowledgement 997 or CONTRL is sent to the Trading Partner.


/*ValidationErrorAdvisory:*/
--------------------------
This activity is triggered whenever a Validation Error occurs in the EDI document validation/conversion process. This can occur either in the EDI to XML conversion or in the XML to EDI conversion. There is detailed transaction error information published in this activity on where the error has occurred and the cause of the error.

Document on MiscMessages BusinessWorks can receive from BusinessConnect EDI.