PROD GLA Integration Guideline - EOL WMS MCPA Web Service

Source document: IP016_PROD-GLA-Integration-Guideline.pdf
Original PDF section: 8.5 EOL / WMS MCPA Web Service
Version: 1
Effective date: 01-Jan-2022

Contents

• 1 EOL / WMS MCPA Web Service
  • 1.1 Overview
  • 1.2 Purpose
  • 1.3 QuerySSCCNo
  • 1.4 Request data
  • 1.5 Response data
  • 1.6 Workflow
  • 1.7 C# contract
  • 1.8 Security protocol
  • 1.9 Error handling and logging
• 2 Preservation notes

---

1 EOL / WMS MCPA Web Service

1.1 Overview

This section describes the EOL / WMS MCPA web service integration.

The interface is used to query SSCC-related information and support validation or exchange of pallet or master case data between GLA and external systems such as EOL, WMS, or MCPA.

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

1.2 Purpose

The purpose of the web service is to provide SSCC query capability for systems that need pallet or container information.

The interface supports scenarios where an external system needs to confirm whether an SSCC exists, is valid, or has related information available in GLA.

Typical use cases include:

• Querying pallet SSCC information
• Validating SSCC availability
• Supporting warehouse or end-of-line processes
• Exchanging information with WMS or MCPA components
• Returning status and descriptive information for downstream processing

1.3 QuerySSCCNo

QuerySSCCNo is the web service operation used to query information by SSCC number.

MDX safety note: SOAP/XML tags and placeholders must remain inside fenced code blocks. Do not place raw <...> tags directly in Markdown prose.

Generic SOAP request structure:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header />
  <soapenv:Body>
    <QuerySSCCNo>
      <SSCCNo>SSCC number</SSCCNo>
    </QuerySSCCNo>
  </soapenv:Body>
</soapenv:Envelope>

Generic SOAP response structure:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header />
  <soapenv:Body>
    <QuerySSCCNoResponse>
      <QuerySSCCNoResult>
        <!-- Response payload -->
      </QuerySSCCNoResult>
    </QuerySSCCNoResponse>
  </soapenv:Body>
</soapenv:Envelope>

1.4 Request data

The request contains the SSCC number to be queried.

Field	Description	Mandatory / Optional	Notes
SSCCNo	SSCC number to query	M	Used as the main lookup value

Example request payload:

<QuerySSCCNo>
  <SSCCNo>SSCC number</SSCCNo>
</QuerySSCCNo>

Extraction note: The source PDF may contain additional wrapper, namespace, or service-specific fields. The available extraction in this conversation did not provide every field with full confidence, so the structure above preserves the reliable operation and main request field.

1.5 Response data

The response returns the result of the SSCC query.

Typical response fields include:

Field	Description	Notes
StatusCode	Processing status returned by the service	Indicates success or failure
Message	Success or error message	Used for troubleshooting
SSCCNo	Queried SSCC number	Should match the request value
Exists	Indicator showing whether the SSCC exists	Boolean or numeric indicator depending on implementation
PalletStatus	Status of the pallet or SSCC	Returned if available
ResponseDateTime	Response timestamp	Used for logging

Example response payload:

<QuerySSCCNoResponse>
  <QuerySSCCNoResult>
    <StatusCode>200</StatusCode>
    <Message>Success</Message>
    <SSCCNo>SSCC number</SSCCNo>
    <Exists>true</Exists>
    <PalletStatus>Status value</PalletStatus>
    <ResponseDateTime>YYYY-MM-DDTHH:mm:ss</ResponseDateTime>
  </QuerySSCCNoResult>
</QuerySSCCNoResponse>

Status code examples:

Status code	Meaning
200	Success
500	Failed

1.6 Workflow

The high-level workflow is:

1. External system sends a QuerySSCCNo request to the web service
2. Web service receives the SSCC number
3. GLA or the related service component searches for the SSCC information
4. Web service returns the query result
5. Request and response are logged according to the configured logging process

Workflow representation:

External system
  ↓
QuerySSCCNo request
  ↓
EOL / WMS / MCPA web service
  ↓
SSCC lookup in GLA or related data source
  ↓
QuerySSCCNo response
  ↓
External system receives result

Note: The original PDF may include workflow figures. Exact visual layout cannot be fully preserved in Markdown, so the workflow is represented as MDX-safe text.

1.7 C# contract

The source PDF includes C# contract-style content for the web service.

MDX safety note: C# code must remain inside fenced csharp blocks because braces {} can be interpreted by MDX if left in prose.

Generic C# contract-style representation:

[ServiceContract]
public interface IService
{
    [OperationContract]
    QuerySSCCNoResponse QuerySSCCNo(QuerySSCCNoRequest request);
}

public class QuerySSCCNoRequest
{
    public string SSCCNo { get; set; }
}

public class QuerySSCCNoResponse
{
    public int StatusCode { get; set; }
    public string Message { get; set; }
    public string SSCCNo { get; set; }
    public bool Exists { get; set; }
    public string PalletStatus { get; set; }
    public DateTime ResponseDateTime { get; set; }
}

Extraction note: The original C# snippet in the PDF was not fully reliable in the available extraction. The representation above preserves the identified operation and likely contract structure without exposing broken OCR fragments as compile-ready code.

1.8 Security protocol

The service should be accessed according to the configured security protocol.

Security considerations include:

• Use the configured endpoint URL only
• Use the authentication method required by the implementation
• Do not store credentials in Markdown documentation
• Do not expose passwords, tokens, or secrets in source control
• Use secure transport where configured
• Restrict access to authorized systems only

Security note: If the original PDF contains usernames, passwords, tokens, or secret values, they should not be reproduced in the Markdown documentation.

Generic endpoint format:

https://<host>/<service-path>

Generic SOAP endpoint usage:

POST https://<host>/<service-path>
Content-Type: text/xml; charset=utf-8
SOAPAction: "QuerySSCCNo"

1.9 Error handling and logging

If the web service cannot process the request, it should return an error response and log the issue.

Typical error handling scenarios:

Scenario	Expected handling
Missing SSCC number	Return validation error
Invalid SSCC number format	Return validation error
SSCC not found	Return not-found or negative result
Service unavailable	Return failure response or timeout
Internal exception	Return error status and log technical details

Typical logged data includes:

• Request timestamp
• Response timestamp
• SSCC number queried
• Calling system, if available
• Status code
• Error message
• Exception details, where applicable

Example error response:

<QuerySSCCNoResponse>
  <QuerySSCCNoResult>
    <StatusCode>500</StatusCode>
    <Message>Error message</Message>
    <SSCCNo>SSCC number</SSCCNo>
    <Exists>false</Exists>
    <ResponseDateTime>YYYY-MM-DDTHH:mm:ss</ResponseDateTime>
  </QuerySSCCNoResult>
</QuerySSCCNoResponse>