How Catalogue Processes Batch Files

Documents sent by batch interface to Catalogue go through the following process:

1	OpenText picks up the inbound EDI document from the OpenText electronic mailbox.

2	OpenText checks file integrity against the EDI standards.

3	The EDI document is validated for EDI qualifiers, mandatory segments and elements, field lengths, and so on.

If your administrator has not selected the option (during the account set-up process) that prevents functional acknowledgements (FAs) from being generated, one of the following occurs:

If the document passes EDI validation, you will receive a positive FA (997 or CNTRL) message to acknowledge receipt of the document. The process continues with Step 4.

If the document fails EDI validation, you will receive a negative FA message. The errors will not appear in Error Processing (EP). You must resend a corrected standards-compliant EDI document that Catalogue will be able to process.

Note: Control numbers must be unique. If a duplicate control number is found, the entire EDI document will be ignored. The corrected document must be sent with a new control number.

4	The files are queued and processed in FIFO order (first files in are the first files out).

5	Within the EDI document, Catalogue processes each valid ST group as a separate transaction. OpenText translates each transaction into a series of qXML functions.

qXML is the OpenText-designed implementation of XML, a document format created to load data into Catalogue. Within qXML, the original EDI is structured as "functions" (actions, records, or business tasks). Successful translation depends on the correct use of EDI mapping as detailed in the OpenText Active Catalogue 832 Batch Guide for Vendors and the OpenText Active Catalogue 888 Batch Guide for Vendors.

Note: EDI documents containing errors that prevent translation into qXML appear in EP. You can use EP to locate the error in the EDI document. You must then fix the errors and resend the EDI document.

6

Catalogue attempts to validate the functions. This includes running business rule validations, data validations, and compliance checks for each item. The system stops processing a specific function when it encounters the first error in that function. Catalogue continues processing subsequent functions.

This process results in one of the following:

No errors—Successful data maintenance for that item.

Errors—The errors are sent to Error Processing (EP). No data maintenance takes place for that item. You can correct the errors online through EP and resubmit the error document.

7	Catalogue sends you a separate email for each EDI document that contains errors. It includes a hyperlink to the browser interface where you can troubleshoot the errors.

The email can be recognized by its subject line:

"OpenText Active Catalogue error report (control number: DocumentControlNumber)."

See the example below. The email includes the number of qXML functions (translated from EDI) that were rejected and a summary of the errors.

The email is sent to the primary contact email address for your account (Account > Account Details on the Account Details tab in the Contact panel). Be sure that this email address is valid.

Example

Subject: OpenText Active Catalogue error report (control number: DocumentControlNumber)

 

One or more errors occurred while processing your input file. Please login to the OpenText Active Catalogue User Interface to review and manage these errors.

(https://catalogue.gxs.com)

 

Control number: DocumentControlNumber

Date: May 6, 2007

Time: 5:27:38 AM

Number of errors: 360

 

Error Count Description

-20505 23 Failed to get existing item attributes; error code=-20505

-20505 15 Item Number not found

-20511 3 Duplicate item number302

-90034 1 Item number already exists

-20510 318 Specified Selection Code or Product not found. It may have been deleted by
another user.

 

8	You can use Error Processing in the browser interface to view and manage errors. See the section, “Strategies for Correcting Errors.�

Note: Any errors displayed in Error Processing are automatically purged from Catalogue after 60 days.

21.2 release. Online Help last updated March 6, 2021 OpenText Active Catalogue Browser Interface User Guide for Vendors PDF

Copyright © 2021 Open Text. All rights reserved. Trademarks owned by Open Text.