Document History

1. Overview

This document describes changes in the 3Keys MDLP connector ABAP part.

2. Description

Inbound message 601 containing SSCC existing in SAP ATTP without objects received but not processed because of validation control – transaction /AIF/ERR contains error message “Failed validation: object (00)SSCC123 is not exist for existing parent SSCC456”.

After parameter /K3T/SCN_ALLOW_EMPTY_SSCC activation runtime error occurs on message processing and captured by AIF framework – transaction /AIF/ERR contains the following error in the Log Messages section:

Error UNCAUGHT_EXCEPTION (1F09B73915F6B645E10000000A11447B) when calling /K3T/RU_AIF_IN_GEN

Line 1 in /K3T/CL_RR_RU_UTILS===========CM00P (/K3T/CL_RR_RU_UTILS===========CP)

An exception with the type CX_SY_RANGE_OUT_OF_BOUN DS was raised, but was not handled locally or decl

ared in a RAISING clause.

An exception of type 'CX_SY_RANGE_OUT_OF_BOUNDS' o ccurred, that was not caught anywhere in the call

hierarchy. It was not handled locally or declared using a RAISING clause.

Line 25 in /K3T/CL_RR_RU_UTILS===========CM00P (/K3T/CL_RR_RU_UTILS===========CP)

Substring access (offset = 14, length = 13) to a d ata object of the size 22 exceeds valid boundaries

.

The sub area access (Offset = 14, Länge = GTH) on a data object of size 22, liese valid boundaries.

Error when calling /K3T/RU_AIF_IN_GEN

As a result, EPCIS event has not been created.

After program code correction inbound message 601 have been processed correctly including aggregation events (aggregation received from MDLP system).

Implementation error.

3. Solution

Import related to the transport request.

3.1 Correction instruction FP04

3.2 Correction instruction FP05

3.3 Correction instruction ATTP 3.0

4. Recommendation

Test inbound SCN processing with parameter /K3T/SCN_ALLOW_EMPTY_SSCC activated.

5. Source code objects