PROD GLA Integration Guideline - MOM Integration

Source document: IP016_PROD-GLA-Integration-Guideline.pdf
Original PDF section: 8.3 GLA and MOM communication
Version: 1
Effective date: 01-Jan-2022

1 GLA and MOM communication
2 Preservation notes

1 GLA and MOM communication

1.1 Overview

GLA-to-MOM interface is described in this section.

MOM-to-GLA interface does not exist, and there is no plan to develop it.

GLA talks to Palletizer, and Palletizer talks to MOM, only for factories where we still have Palletizers.

The source document also asks to provide information concerning SAP-GLA interfacing, which will be active after MOM implementation.

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

1.2 Validated Pallet data interface

GLA provides pallet data to MOM as soon as the pallet is built and validated by TPM.

The following information is provided by GLA to MOM:

Field description	Data type	Length	O/M	Description
`PlantCode`	`Varchar`	10	O	The factory id as used in SAP, e.g. `DEP1`, `TRP1`, etc
`BatchNumber`	`Varchar`	10	M	The batch number of the pallet to create
`SSCCcode`	`Varchar`	20	M	The SSCC of the pallet to create. Can be empty, in which case there should be 20 spaces and the SSCC can be updated through the T&T pallet information association process. This is dependent on the fully automated or semi-automated solution. Note: The second last digit in the SSCC represents the tracking indicator. This enables the system reading this file to know if the pallet is tracked or not
`WorkOrder`	`Varchar`	8	O	The production order number of the pallet to create. Can be empty, in which case there should be 8 spaces. This value is padded on the left with spaces
`PalletCounter`	`Numeric`	6	O	The sequential number of the pallet to create
`PalletType`	`Nvchar`	3	M	Three characters representing the pallet type using SAP coding. Example: `EUR` for Euro, `IND` for Industrial Pallets
`NumberOfCase`	`Int`		M	Number of master cases on the pallet
`MaterialNumber`	`Varchar`	8	M	SKU number of the work order
`EPCcodes`	`Varchar`	Max	M	Provides master case codes in an array format. See example below
`ErrorCode`	`Int`		M	Error or success code of TPM and Palletizer communication
`PalletBuildStatus`	`Int`		M	If the pallet was built automatically or manually to use the correct vehicle for pick up. Value `0`: Pallet built automatically. Value `1`: Pallet built manually

Example array format for EPCcodes:

{
  "EPCcodes": [
    "011460043993295310127346602100006124014046760",
    "011460043993295310127346602100006224014046760",
    "011460043993295310127346602100006324014046760",
    "011460043993295310127346602100006424014046760",
    "011460043993295310127346602100006524014046760"
  ]
}

1.3 New Pallet Created in GLA

Note: The original PDF contains a flowchart. The visual layout cannot be fully preserved in Markdown. The OCR-extracted text was low quality, so the available text is preserved below as an OCR note.

Start
New Pallet
GLA
New SSCC
Created
Pallet Contains
Any Errors
Error Code
Update
No
Is TFD?
Yes
Pallet info
Send to TPM
All codes are
validated?
No
Yes
Is Pallet Printed
Validate
MOM
Stop

1.4 Existing Pallet Reworked

Note: The original PDF contains a flowchart. The visual layout cannot be fully preserved in Markdown. The OCR-extracted text was low quality, so the available text is preserved below as an OCR note.

Start
Existing Pallet
Reworked
Is TFD?
Delete Existing
SSCC & Create
New SSCC
Pallet info
Send to TPM
No
All cases are
validated?
Is Pallet Printed
Error Code
Update
Pallet info Send to
MOM
Stop

1.5 TPM Status Change Interface GLA to MOM

GLA provides TPM status change information to MOM.

GLA will run a new interface with the TPM system every 300 seconds to check the TPM status.

If TPM becomes unreachable, GLA will trigger this GLA-to-MOM TPM status interface to notify MOM.

Whenever GLA detects that TPM is running again, the interface will be triggered to notify MOM.

The interface execution data will be logged in the GLA database, in the InterfaceRunLog table.

The JSON format is explained below.

TPM status values:

TPM is Enabled
TPM is Disabled

Request JSON format:

{
  "LocationID": "RUP1",
  "MessageDateTime": "2019-10-04T08:15:01.000",
  "ErrorCode": 51003,
  "TPMAlive": 1
}

MOM response JSON format:

{
  "StatusCode": 200,
  "ResponseDateTime": "2019-10-04T08:15:01.000"
}

Status codes:

Status code	Meaning
`200`	Success
`500`	Failed

1.6 TPM Alive Check GLA to TPM Interface

A new interface has been developed between GLA and TPM systems to check if the TPM system is running.

GLA will log the TPM state changes in its database.

A new field can be added into the SAPInterfaceConfiguration table to store the TPM state.

Request JSON format:

{
  "LocationID": "RUP1",
  "MessageDateTime": "2019-10-04T08:15:01.000"
}

TPM response JSON format:

{
  "StatusCode": 200,
  "ResponseDateTime": "2019-10-04T08:15:01.000"
}

If TPM does not respond, GLA will treat it as TPM unavailable and trigger the TPM status change interface to MOM.

Contents​

1 GLA and MOM communication​

1.1 Overview​

1.2 Validated Pallet data interface​

1.3 New Pallet Created in GLA​

1.4 Existing Pallet Reworked​

1.5 TPM Status Change Interface GLA to MOM​

1.6 TPM Alive Check GLA to TPM Interface​

Contents