Glossary

 

AI	See Translation.
AI Bridge	See Translation Instance
AI Session Number	See Translation Session Number.
Application Reference	An application identifier used in file or message routing, assigned by GXS during the implementation process. Application Reference IDs might identify a particular system, process, recipient, or data type. The value might also be blank, such as for inbound data moving from the GXS network into the first Managed Services routing cycle. This identifier is usually unique to a specific process, data type, or trading partner.
AS2	A data transport protocol designed to provide secure and reliable file transfer over the Internet. AS2 communication activity is reported on the Managed Services Dashboard.
CFTP Bridge	Connect-Out FTP Bridge. A Managed Services connection point that can use standard FTP connections to pass data to (or pull data from) a remote host.
Client Address	See Partner Address.
Communication Type	The communications protocol, standard, or interface used to submit the transaction to the Trading Grid.
Control Number	Interchange Control Number of the data coming in or going out. It is a number assigned by EDI systems to various structural levels of an EDI file for the purpose of verifying data integrity.
COS Bridge	Connect-Out Service Bridge. A Managed Services connection point that can pass task parameters to a user's program, UNIX shell script task, or NT command file.
Created Date and Time	Date and time that the transaction was created.
Delinquent Acknowledgment	See Late Acknowledgment.
Delivered Report	A scheduled report extract or a standard Managed Services report generated on a scheduled basis.
Direction	Direction (inbound or outbound) of data movement from the perspective of the GXS customer (associated with the My Address field), not the customer’s partner (associated with Partner Address).
Document	An electronic business document, typically in EDI format.
Document Type	A code in EDI that identifies a specific type of EDI document, for example, 810 or INVOIC. In this field in Search, enter the identifier of a document type to return only documents of that type. To search for documents of multiple types, separate the types with commas.
EDI	Electronic Data Interchange. A standardized data structure for exchanging business documents electronically.
Enterprise	See Managed Services platform.
Extended events	Events that occur outside of GXS which the customer publishes to GXS. For example, your backend system might detect that a file failed to reconcile and reports that information to GXS.
Extracted	Status or event type in some implementations. Indicates that the trading partner extracted the document from the mailbox or interconnect.
File	A data file moving through the Managed Services environment.
Functional Group	Refers to a structural level of an ANSI X12 EDI-formatted file that contains a document (or documents) of a particular document type. GXS Ref Num - a unique number created by the Managed Services platform to track EDI interchanges, EDI documents, and files.
Functional Group Control Number	A number assigned by EDI systems to the functional group header and trailer segments of an EDI file for the purpose of verifying data integrity. Typically applies only to ANSI X12 formatted data.
Functional Group Type	A two-digit code found in the group header segment of an ANSI X12 EDI-formatted file that identifies the type of business document it contains.
Group	See Functional Group
GXS Ref No.	A unique number created by the Managed Services platform to track: Transmission files — preceded by F- EDI interchanges — preceded by I- EDI groups EDI documents — preceded by D- XML documents — preceded by U- Trading Grid Messaging Service transactions On the Search page, the GXS Ref Num is a quick way to access lifecycle processing information.
ICS (Interchange Services)	Former name of a GXS value-added network service that manages the electronic exchange of business documents between trading partners. ICS might appear in an error message.
IFTP	A file transfer protocol with enhanced scripting used to create automated, robust and reliable File Transfer Protocol operations.  IFTP communication activity is reported on the Managed Services Dashboard.
ILOG Number	Input Log Number, assigned by the Trading Grid for tracking purposes and uniquely identifies a file transmitted by the Sender. An ILOG is an 11-digit number, based on the combination of the month, day, Greenwich Mean Time, and the decimal fraction of the hour.
Inbound data	Data being received by your company.
Input File(s)	The file(s) that are used as the source data during a translation session.
Interchange	Refers to an EDI-formatted file.
Interchange Control Number	A number assigned by EDI systems to the interchange header and trailer segments of an EDI file for the purpose of verifying data integrity.
Interconnect Name	The name of a third-party VAN, for example, between your company and GXS in the file routing process.
Late Acknowledgment	An EDI acknowledgment which has not been returned in the period of time designated in the acknowledgment tracking rule, usually 24 hours.
Lifecycle	A sequential history of data activity at various processing points on the Managed Services platform.
Mailbag ID	References an interconnect service (for example, a third-party VAN). Value must be numeric.
Mailbox	GXS mailbox identifier.
Managed Services Dashboard	High level view of communication and data tracking, enabling management by exception.
Managed Services Platform	The routing application used to manage the flow of data between managed Services clients, their trading partners, and various processing points in between.
Model	A file used during translation that defines the structure of a file and mapping rules for its data content.
My Address	Your EDI or GXS routing address.
My Functional Group Address	Your EDI functional group address; applies only to the ANSI X12 standard.
Organization Report	See Delivered Report
Outbound data	Data sent by your company to a Trading Partner.
Output File(s)	The file(s) that are created as a result of a translation session.
Partner Address	The EDI or GXS routing addresses of your Trading Partner.
Partner Name	The company name of your business partner, as it is defined in Active Documents. On the Search page, you can enter a partial name and the system displays a drop-down selection list that matches the value you entered.
Primary Key (and Value)	The type and value of a document identifier assigned by the sender to identify a particular documentsuch as Purchase Order Number. On the Search page, if you enter a partial key, the system displays a list of key types beginning with the same character(s). Click one to select it. Then, in the Value field, enter the identifier value to use for the selected key. In the Value field, you can type a partial value ending in an asterisk (*) for the system to return any documents with the selected key value that begins with those characters. Some Managed Services clients might have keys defined at the file level.
Production/Test Flag	This is a field/flag in the EDI interchange header for ANSI X12.  This field indicates if a transaction is test or production.  Users can send test transactions on the production system to Trading Partners, and this flag distinguishes which transactions are test and which are production.  You should work with your Trading Partner in deciding how to use this flag.
Receiver	The recipient ID in a Managed Services routing cycle. For data processed as EDI, the recipient ID is typically an EDI address. For non-EDI file types, the recipient ID represents a routing ID.
Reference #	See GXS Ref No.
Scheduled Report	A set of search parameters set up to extract Managed Services data on a daily, weekly, or monthly basis. The term also applies to Standard Managed Services reports that are scheduled.
Secondary Key (and Value)	The type and value of a secondary document identifier assigned by the sender to identify a particular document such as Trading Partner. On the Search page, if you enter a partial key, the system displays a list of key types beginning with the same character(s). Click one to select it. Then, in the Value field, enter the identifier value to use for the selected key. In the Value field, you can type a partial value ending in an asterisk (*) for the system to return any documents with the selected key value that begins with those characters. Some Managed Services clients might have keys defined at the file level.
Sender	The originator ID in a Managed Services routing cycle. For data processed as EDI, the originator ID is typically an EDI address. For non-EDI file types, the originator ID represents a routing ID.
Sender Reference	A number or alphanumeric value referencing the file in the routing process. The value is assigned by a process in the routing cycle.
Session #	The number assigned to uniquely identify a specific translation instance.
Standard	The format and version number for the type EDI data contained in the data file, for example, ANSI (5020), EDIFACT (00.A) or Tradacoms.
Standard Reports	A set of pre-defined reports available through the Managed Services reporting tool.
Status	In Search, a drop-down list of possible statuses to search, based on the platform, level of tracking, and configuration. Status searches can apply to inbound and outbound transactions. In Managed Services, at the file level you can search the following statuses: With Errors Without Errors With Negative Alerts (last status alert was for an error or an event that did not occur within a specified time period for the event type) Without Negative Alerts (last status alert for file was for an event that occurred within the specified time period for the event type) In Managed Services, at the document level, you can search the following statuses, depending on your service subscription: Acknowledged Not Acknowledged In other implementations, you might also be able to search for files with the following Status: Extracted (picked up by trading partner) Unextracted (not picked up by trading partner) Rejected (by GXS) Rejected from Interconnect Incomplete (incomplete itineraries, which are GXS instructions for processing a document) In any implementation, leave All selected to not search based on a specific status.
Time Frame	Date criteria based on when GXS processed the document, whereas Invoice Date Range is based on the content of the actual invoice document. From the selection list, select the type of date search: Specific Date Range — Use calendar icons to select From and To dates. Enter the time using a 24-hour clock, i.e., enter values from 00:00 to 23:59. Last No. of days — Enter the desired number of days back from the current date, e.g., 10, 15, etc. Relative Time Range — Select the days and times in the From and To fields. None — Search all available records.
Translation	The GXS data transformation process used in translating data between data formats. Data is translated from any format to another format. Many Managed Services customers use the system to translate between their in-house data formats and standard EDI (Electronic Data Interchange) formats.
Translation Instance	Identifies which Application Integrator translation instance processed the transaction.  There is one or more than one translation instance, depending on the implementation.
Translation Session Number	A number assigned to each translation process.
UDF	User-defined file format.
Unextracted	Status or event type in some implementations. Indicates that the trading partner has not extracted the document from the mailbox or interconnect.
User ID	The email address that you use to log in to Trading Grid Online.
User Report	See Delivered Report
XML/UDF	Refers to document-level processing for data in either XML structure or a user-defined format to enhance search. The XML structure might follow a defined standard, such as RosettaNet, or an in-house data format.

 

16.2 release. Updated October 23, 2016 Trading Grid Online User Guide PDF

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