ODI SAP LKM MANUAL_UPLOAD_ABAP_CODE=1 Generates Wrong ABAP Indentation
(Doc ID 2087196.1)
Last updated on JUNE 16, 2022
Applies to:
Oracle Data Integrator - Version 12.1.2.0.0 and laterInformation in this document applies to any platform.
Symptoms
When an Oracle Data Integrator (ODI) mapping using a SAP Loading Knowledge Module (LKM) is executed with MANUAL_UPLOAD_ABAP_CODE=1, the generated ABAP code in ABAP file generated in temporary directory contains the wrong indentation:
REPORT ZODI_AC8VCGRWHRFKBUTG.
PARAMETER: IV_DELI TYPE CHAR3.
PARAMETER: IV_FILE TYPE CHAR255 LOWER CASE.
PARAMETER: IV_USER TYPE CHAR35 LOWER CASE.
PARAMETER: IV_PWD TYPE CHAR35 LOWER CASE.
PARAMETER: IV_HOST TYPE CHAR35.
PARAMETER: IV_HASH TYPE CHAR35.
PARAMETER: IV_PATH TYPE CHAR35 LOWER CASE.
PARAMETER: IV_MAXC TYPE SYTABIX.
PARAMETER: IV_FETC TYPE SYTABIX.
DATA : RETURN TYPE TABLE of BAPIRETURN
WITH HEADER LINE.
DATA : ET_FILE_RETURN TYPE TABLE of BAPIRET2
WITH HEADER LINE.
DATA: it_odivar TYPE zodi_cond,
wa_odi TYPE zodi_cond_str,
lv_dyn_var TYPE string,
lv_var TYPE int4 VALUE 2,
lv_line1 TYPE line,
lv_low TYPE syindex,
lv_high TYPE syindex,
lv_new TYPE sytabix,
lv_mod TYPE sytabix,
lv_string TYPE STRING.
DATA: IV_DELIMITER TYPE CHAR3,
IV_FILENAME TYPE CHAR255,
IV_HASHVALUE TYPE CHAR35,
IV_MAX_ROW_CNT TYPE SYTABIX,
IV_FETCH_BATCH_SIZE TYPE SYTABIX.
SELECT-OPTIONS:
IT_COND FOR lv_line1 NO INTERVALS.
FIELD-SYMBOLS: <fs> TYPE any,
<ps> TYPE any.
************************
*Final Type declarations
************************
TYPES : BEGIN OF ty_final,
This is a sample from a correct ABAP code uploaded when using automatic upload:
DATA: it_odivar TYPE zodi_cond,
wa_odi TYPE zodi_cond_str,
lv_dyn_var TYPE string,
lv_var TYPE int4 VALUE 2,
lv_line1 TYPE line,
lv_low TYPE syindex,
lv_high TYPE syindex,
lv_new TYPE sytabix,
lv_mod TYPE sytabix,
lv_string TYPE STRING.
.
DATA: IV_DELIMITER TYPE CHAR3,
IV_FILENAME TYPE CHAR255,
IV_HASHVALUE TYPE CHAR35,
IV_MAX_ROW_CNT TYPE SYTABIX,
IV_FETCH_BATCH_SIZE TYPE SYTABIX.
.
SELECT-OPTIONS:
IT_COND FOR lv_line1 NO INTERVALS.
FIELD-SYMBOLS: <fs> TYPE any,
<ps> TYPE any.
************************
*Final Type declarations
************************
TYPES : BEGIN OF ty_final,
Please note that the ABAP comments in the first snippet start at column 2, but ABAP comments must start in column 1 (as shown in the ABAP code generated for automatic upload.)
This leads to ABAP syntax errors.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |