Troubleshooting
Problem
SAP OData jobs are failing during execution with the following error message:
“Internal error occurred: SCAPI error: Column <column_name> not found in SAP Metadata Columns. Please check the Column name”
Symptom
When executing SAP OData jobs, the jobs fail unexpectedly due to a metadata validation error. This occurs when one or more expected columns are missing from the SAP columns metadata definitions retrieved at runtime. The issue is reflected in the job logs with the following error message:
com.ibm.connect.api.SCAPIException CDICO9999E: Internal error occurred: SCAPI error: Column Userid not found in SAP Metadata Columns. Please check the Column name.
This indicates that the connector is unable to locate the specified column within the SAP metadata structure, causing the job to fail.
The failures have been observed due to the following reasons:
- SAP OData older jobs failing during execution:
After applying APAR fixes DT261430 and DT260532, older SAP OData jobs (created prior to these fixes) are failing at runtime during metadata validation. - Metadata created without using the IMAM tool:
If customers manually create or modify metadata columns without using the recommended IMAM tool, the resulting mismatch between job definitions and SAP metadata causes validation errors at runtime.
Cause
This issue occurs due to changes in the metadata validation within the SAP OData Jobs. The connector now enforces strict validation by ensuring that the job's defined columns metadata match the SAP columns metadata retrieved at runtime. Jobs fail when discrepancies or mismatches are detected.
The problem typically arises in the following scenarios:
- SAP OData older jobs failing during execution: SAP OData older jobs, created before the APAR fixes DT261430 and DT260532 (implemented enhanced metadata validation), may not align with the updated validation rules. These jobs often follow outdated metadata naming patterns or lack proper structure, causing mismatches between the job design and the SAP metadata during runtime validation
- Metadata created without using the IMAM tool: When customers manually create or modify metadata definitions without using the IMAM tool, it increases the risk of inconsistencies in columns metadata. The IMAM tool ensures that metadata is accurately imported and structured according to the connector’s expectations. Without it, manually defined metadata might not correctly match SAP’s metadata schema, leading to validation errors during job execution.
Resolving The Problem
To resolve this issue, you can follow either of the below methods:
- Re-import the metadata using IMAM (Infosphere Metadata Asset Manager):
This will fetch the latest metadata definitions directly from SAP, ensuring they are aligned with the updated validation rules. - Manually update the column names:
Rename the columns in your job design to follow the format:
EntitySetName__ColumnName (for example: UserDetails__Userid).
This ensures that the job’s column definitions properly match the SAP metadata structure during validation.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
28 April 2025
UID
ibm17231041