Sign in

B2BCloud Prod Issue Notifications

  • Updated

The following notifications are part of a CIC system check process that monitors for certain conditions and then provides early warning through email.

  • Received and Unwrapped Messages Exist
  • Active or Stopped Processes Exist
  • Received Only Connection Exist

Received and UnWrapped Messages

This often indicates that CIC has received the data but is unable to proceed. Reasons for this error often include:

Missing Route or Binding

This common error will cause a job to fail during processing. A log may contain this message (partial):

The Inbound EDI Router was unable to find matching Inbound EDI Routes.
Number of matching Inbound EDI Routes: 0
Number of associated Process Bindings: 0

This occurs when the process can’t find an EDI Route (pointing to Trading Partner) or a Process Binding (pointing to BP& Ruleset).  A modification to your current setup or a new partner configuration would need to be completed before the data can be reprocessed.

Recommended troubleshooting steps (in CIC Studio)

  1. Confirm that all trading partner resources (Project, objects, etc.) have been setup and deployed.
  2. Check that the correct EDI Route object is being used for the correct trading partner.
  3. Check that envelope values in the EDI document match the envelope values as defined in the EDI Route object.
  4. Check that there is an associated Process Binding in the EDI Route. This defines the Business Process that will be used for the received EDI document. If this is not set up correctly (or at all), then processing will not complete.

Related Info

Duplicate Interchange

An error scenario may be when a trading partner’s document has been marked as Duplicate and not translated into your application files.  A connection marked as duplicate indicates that Interchange Change Control Number had been received previously from the same trading partner.  This does not mean the data inside the interchange is actually the same.  Both Interchanges may have been received at the same time.

Recommended actions

  1. The customer would need to confirm this is an actual duplicate. Contact the trading partner to see if they intended to send a duplicate document.
  2. If the data is the same and is a duplicate, then nothing else needs to be done.
  3. If it is not a duplicate, the customer may need to reprocess the one marked DUPLICATE. They should contact Support for assistance in reprocessing data.

Related Info

Invalid EDI Data

Consider these examples:

  1. An EDI message failed during processing.  The error was caused by invalid EDI data and/or the data not matching the current mapping setup.  The data and/or mapping must be corrected and the message reprocessed.  The error is an invalid EDI value (ITC) in element L1102.

    Invalid content for ID type element.  Segment "Message area '1', Segment 'L11 occurrence 1', Element at position '2'", element "128".  Content is "ITC".

  2. The length of a L1101  element is 33 but the maximum length is 30.  The data must be corrected and reprocessed. The trading partner should perform the above actions.

    Invalid maximum length Message area '1', Segment 'L11 occurrence 2', Element at position '1'.  This length is 33.  Maximum length is 30.

  3. The failed messages failed to process because the provided data did not meet X12 EDI standards. In this example, the provided code "DM" is invalid for the W1305 element.  The data must be corrected and reprocessed. The trading partner should perform the above actions.

    Invalid content for ID type element.  Segment "Message area '2', Loop start 'W07', Segment 'W13', Element at position '5'", element "853".  Content is "DM".

  4. The document failed to process because of a missing mandatory element, which is W0602, in this example.  The data must be corrected and reprocessed. The trading partner should perform the above actions.

    Missing mandatory item Message area '1', Segment 'W06', Element at position '2'.

Active or Stopped Processes Exist

Active jobs may simply be a long running process with a large amount of data still processing. There may be no need for any action, other than to be aware and observe.

Job status in active process appear like this in CIC Cockpit.

However, this can also indicate jobs that have timed out or failed but the status has not updated. In this case the job should be investigated for problems, and reprocessed when corrected.

Note: Active jobs notifications are only sent when a job has been running more than 20 minutes.

Stopped

A stopped process usually occurs when a Business Process has been manually stopped; any jobs that may have been queued up to run (from the process) would also stop.

Received Only Connection Exist

This indicates a connection has received EDI data but has yet to be processed. Generally, the causes for this status may include:

  • Data has been received but there are other processes running, and the queue is backed up; the connection is waiting to process.  This can occur when a Trading Partner sends many connections at once, causing a backlog.
  • A process containing multiple connections either stops or is manually stopped. There may be queued-up connections that have been received, but their statuses do not update to a Canceled status, remaining at Received Only. This is shown in the CIC Studio Auditor below.

    In many cases, these connections could be reprocessed from the Received only status, and may not need to be resent by the Trading Partner.

Related articles

Comments

0 comments

Please sign in to leave a comment.