SAP Knowledge Base Article - Public

3781003 - Short dump occurs when choosing "Copy" in Batch Determination dialog in MIGO although no batch was found

Symptom

When performing a goods movement in MIGO, Batch Determination is executed.

If Batch Determination does not find any suitable batch, the result list is empty.

If the user chooses Copy despite no batch being returned, the system terminates with the following short dump:

  • Category                         ABAP programming error
    Runtime Errors                ASSERTION_FAILED
    ABAP: Program                SAPLCLFM
    Application Component     CA-CL-CL

This behavior can occur after upgrading to SAP S/4HANA Cloud Public Edition CE 2608.

Environment

SAP S/4HANA Cloud Public Edition 2608

Reproducing the Issue

  1. Open the MIGO app/transaction.
  2. Create a goods movement (for example, Goods Receipt or Goods Issue) for a batch-managed material.
  3. Click on 'Stock Determ.' or 'Stock Determ. For all' option.
  4. Execute Batch Determination using selection criteria that do not return any eligible batch.
    • The result list is empty.
  5. Choose Copy.
  6. Dump occurs.

Cause

During Batch Determination, classification data (selection criteria) is temporarily created for the material document.

Under specific circumstances, when Batch Determination does not return a suitable batch and the user selects Copy, inconsistent classification data may be generated.

As of CE 2608, the correction delivered with SAP Note 3747995 prevents inconsistent classification data from being saved to the database. Instead of allowing the inconsistent data to be persisted, the system terminates processing with a short dump.

Therefore, the short dump is a consequence of the newly introduced consistency protection detecting an invalid situation that previously could result in inconsistent database entries.

Resolution

If Batch Determination returns no suitable batch, do not choose Copy.

Instead:

  1. Choose Back to leave the Batch Determination dialog.
  2. Enter a batch manually, if required.
  3. Alternatively, adjust the Batch Determination criteria so that a valid batch can be determined.

This avoids the creation of inconsistent classification data and prevents the short dump.

A permanent correction is currently being developed.

See Also

Note 3747995 - Extend CUOB_CHECK_OBJECT_TEMP_KEY for MSEG

Keywords

MIGO, Batch Determination, Copy, Back, DBSQL_DUPLICATE_KEY_ERROR, INOB, CLF_HDR, Classification, CUOBJ_CH, MATDOC, MSEG, CE2608, 3747995, LCLFMF24, 37, INSERT_CLASSIFICATION, ASSERTION_FAILED, SAPLCLFM , KBA , LO-BM-BD-2CL , Batch Determination (Public Cloud) , LO-BM-2CL , Batch Management (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition 2608