1624942 - "Field XXXX in table YYYY is specified twice" error in DDIC_ACTIVATION or ACT_UPG

Error "field is specified twice" occurred in DDIC_ACTIVATION (ACT_UPG or ACT_TRANS) phase during implementation of Support Package queue using transaction SPAM or SUM tool (Software Update Manager). It is not possible to continue this procedure. Check the following examples.

• In the activation logs, an error similar to the following example should be displayed.

Field A3_ZIP in table J1G_XML_BADI_HEADER is specified twice.
Field KURRZONE in table J_1GNAHTM is specified twice.
Field TABO in table J1G_XML_BADI_ITEM is specified twice.
Table J1G_XML_BADI_HEADER could not be activated
Table J_1GNAHTM could not be activated
Table J1G_XML_BADI_ITEM could not be activated

• When running SPAM/SAINT, an error similar to the following will occur.
  
  
  
  By checking the package logs, the following information can be found.
  
  
   
• In more complex scenarios, the following errors can be found in the activation log.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP NetWeaver ABAP Release Independent.
• Upgrade Tools for ABAP.

dictionary, activation, error, field, object, table, SPAM, SAINT, SUM, specified, twice, duplicated, DT, 963, ACT_UPG, ACT_TRANS, HCMT_BSP_PA_FR_R0713, HCMT_BSP_PA_FR_R0016, 3EEDT963 Field, in table, is specified twice, 1EEDT963 Field, The field appears twice in the table check it, MAIN_TRANSEXEC/ACT_TRANS, AGS_BPM_APPMONM_LINE, field specified twice , KBA , BC-DWB-DIC-AC , ABAP Dictionary Activation and Conversion , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-UPG-OCS-SPA , Support package tools for ABAP , Problem