SAP Knowledge Base Article - Preview

2567171 - Runtime errors "SAPSQL_PARSE_ERROR" occurs in ABAP Program "CL_AGSCCL_LAST_USAGE_MIG======CP", SAP Solution Manager 7.2

Symptom

In transaction ST22, the following dump is found:

Category               ABAP Programming Error
Runtime Errors         SAPSQL_PARSE_ERROR
Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS
ABAP Program           CL_AGSCCL_LAST_USAGE_MIG======CP

Short Text
    An error has occurred while parsing a dynamic entry.

What happened?
    Error in the ABAP Application Program

    The current ABAP program "CL_AGSCCL_LAST_USAGE_MIG======CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.

Error analysis
    An exception has occurred which is explained in more detail below. The
    exception is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS' and was not
     caught in procedure
    "_FETCH_INCL_USAGE" "(METHOD)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated this
    exception, the current program was terminated.
    The reason for the exception is:
    The current ABAP program attempted to execute an Open SQL statement
    containing a dynamic entry. The parser returned the following error: "Field
     "A_SID" is unknown. It is neither in one of the specified tables nor defined
     by a "DATA" statement. "DATA" statement."

Information on where terminated
    The termination occurred in ABAP program "CL_AGSCCL_LAST_USAGE_MIG======CP",
     in "_FETCH_INCL_USAGE". The main program
    was "AGSCCL_LAST_USAGE_MIG".

    In the source code, the termination point is in line 2 of (Include)
    program "CL_AGSCCL_LAST_USAGE_MIG======CM011".
    Program "CL_AGSCCL_LAST_USAGE_MIG======CP" was started as a background job.

    Job name....... SM_CCLM:LUSG_MIG_SKC
    Job initiator.. SOLMAN_BTC
    Job number...... 00242100
    The termination is due to exception "CX_SY_DYNAMIC_OSQL_SEMANTICS" occurring
     in procedure "_FETCH_INCL_USAGE" "(METHOD)".
    This exception was not handled locally or declared in the RAISING
    clause in the procedure's signature however.
    The procedure is in program "CL_AGSCCL_LAST_USAGE_MIG======CP". The source
     code begins in line 1 of
    (include) program "CL_AGSCCL_LAST_USAGE_MIG======CM011".


Read more...

Environment

SAP Solution Manager 7.2

Product

SAP Solution Manager 7.2

Keywords

CL_AGSCCL_LAST_USAGE_MIG, "_FETCH_INCL_USAGE",CX_SY_DYNAMIC_OSQL_SEMANTICS, migration job, SM_CCLM:LUSG_MIG,SAPSQL_PARSE_ERROR, ST22. , KBA , SV-SMG-CCM , Custom Code Management , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.