During the implementation of a Support Package queue, using either transaction SPAM or the SUM tool (Software Update Manager), an error "field is specified twice" in phase DDIC_ACTIVATION (ACT_UPG or ACT_TRANS) and it is not possible to continue with the procedure. Check the examples:
- In the activation logs, something similar to the following example should appear:
Field A3_ZIP in table J1G_XML_BADI_HEADER is specified twice. Field KURRZONE in table J_1GNAHTM is specified twice.
Field KURRREGI in table J_1GNFTXT is specified twice. Field TABO in table J1G_XML_BADI_ITEM is specified twice. Table J1G_XML_BADI_HEADER could not be activated
Table J1G_XML_BADI_ITEM could not be activated
Table J_1GNAHTM could not be activated
- When running SPAM/SAINT, an error similar to the following:
By checking the package logs, information like the following can be found:
- In more complex scenarios:
- SAP Netweaver ABAP Release Independent.
- Upgrade Tools for ABAP.
dictionary, activation, error, field, object, 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 , KBA , BC-DWB-DIC-AC , Activation Prog., Conversion Prog., DB-Utility, MC, SPDD , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-UPG-OCS-SPA , Support package tools for ABAP , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.