PROD GLA Integration Guideline - Gate Integration

Source document: IP016_PROD-GLA-Integration-Guideline.pdf
Original PDF section: 8.2 GLA-GATE integration
Version: 1
Effective date: 01-Jan-2022

1 Integration with Gate system
2 Preservation notes

1 Integration with Gate system

1.1 Overview

This section describes the integration between GLA and Gate.

The integration is used to transfer work order related information from GLA to Gate and to support pack UID availability handling.

Note: The source PDF content is under original section 8.2. In this split Markdown file, the chapter numbering starts from 1.

1.2 GLA to Gate work order transfer

GLA transfers work order information to Gate so that Gate can use the relevant production and tracking data.

The transferred data may include production order, SKU, batch, plant, line, and tracking-related values.

Typical work order transfer fields:

Field	Description	Notes
`WorkOrderID`	Production work order number	Used as the main work order reference
`SAP_PO`	SAP production order number	May be the same value as `WorkOrderID` depending on implementation
`SAP_SKUNumber`	JTI SKU number	Material or SKU identifier
`SAP_BatchNumber`	Batch number	Batch linked to the work order
`SAP_PlantCode`	Plant code	Factory or plant identifier
`SAP_MakePack`	Production line or work center	Used to identify the line where production is executed
`SAP_TTProdIdent`	T&T production identifier	Used to determine tracking relevance
`SAP_IsTrackingRelevant`	Tracking relevance flag	Indicates whether master case tracking applies
`SAP_IsCartonTrackingRequired`	Carton tracking flag	Indicates whether carton-level tracking applies
`SAP_IsPackTrackingRequired`	Pack tracking flag	Indicates whether pack-level tracking applies

Formatting note: The original PDF section contains interface details that may be represented as tables or structured data. Technical fields are wrapped in backticks to avoid Markdown or MDX formatting issues.

1.3 Pack UID availability

Pack UID availability is used to determine whether pack-level unique identifiers are available for the relevant production process.

Typical pack UID availability data:

Field	Description	Notes
`PlantCode`	Plant or factory code	Identifies the source location
`LineCode`	Production line code	Identifies the production line
`WorkOrderID`	Work order number	Links UID availability to the work order
`MaterialNumber`	SKU or material number	Identifies the produced material
`BatchNumber`	Batch number	Links availability to the production batch
`PackUIDAvailable`	Pack UID availability indicator	Indicates whether pack UIDs are available
`MessageDateTime`	Message date and time	Timestamp for the availability status

Example JSON-style representation:

{
  "PlantCode": "Plant code",
  "LineCode": "Production line code",
  "WorkOrderID": "Production order number",
  "MaterialNumber": "SKU or material number",
  "BatchNumber": "Batch number",
  "PackUIDAvailable": true,
  "MessageDateTime": "YYYY-MM-DDTHH:mm:ss"
}

MDX safety note: JSON braces {} are kept inside fenced code blocks to avoid JSX parsing issues in Docusaurus.

1.4 Data handling

GLA should provide Gate with the relevant work order and tracking information required for the Gate-side process.

Recommended handling points:

Work order data should be transferred after the work order information is available in GLA
Tracking flags should be derived from the SAP work order data already imported into GLA
Pack UID availability should be communicated using a clear availability indicator
Messages should include enough identifiers to correlate the status with the correct plant, line, work order, SKU, and batch
Interface activity should be logged for troubleshooting

1.5 Error and retry handling

If the Gate interface fails, GLA should log the failure and follow the configured retry or support process.

Typical error handling information:

Field	Description
`ErrorCode`	Error code returned by Gate or generated by GLA
`ErrorMessage`	Error message text
`MessageDateTime`	Request timestamp
`ResponseDateTime`	Response timestamp, if available
`WorkOrderID`	Work order involved in the failed transfer
`PlantCode`	Plant where the issue occurred
`LineCode`	Production line where the issue occurred

Example error response structure:

{
  "StatusCode": 500,
  "ResponseDateTime": "YYYY-MM-DDTHH:mm:ss",
  "ErrorCode": "Gate error code",
  "ErrorMessage": "Gate error message"
}

If the Gate system is unavailable, the interface should be retried according to the local GLA interface scheduler configuration.

Contents​

1 Integration with Gate system​

1.1 Overview​

1.2 GLA to Gate work order transfer​

1.3 Pack UID availability​

1.4 Data handling​

1.5 Error and retry handling​

Contents