Dear Reader,
During the SWPM (Software Provisioning Manager) export phase, you may encounter situations where certain tables exist in the ABAP Dictionary but not in the database.
This discrepancy can cause export packages to fail, resulting in export errors.
Example Error in Package Log
When such inconsistencies occur, the export log (e.g., <package-name>.log) will contain error messages similar to the following:
——————————————————————————————————————————————————–
A3EEEXP 008 Task failed with error: (EXP) DbSIExeRead failed with dbrc=103
A3EEEXP 008 (EXP) SQL error = 942
A2EETSK 007 Finished export for object “RSJOBMESSAGEHDLR” of type “table” with error in 0.00 sec #
——————————————————————————————————————————————————–
Identifying Failed Tables
To identify all failed tables within a specific package, open the corresponding <package-name>.TSK file.
Entries for failed tables will typically appear in the following format:
———————————————-
D RSJOBMESSAGEHDLR E err
———————————————-
Verifying Tables in ABAP Dictionary
Once the failed tables are identified, you can verify their existence in the ABAP Dictionary using transaction SE14.
Resolution
If the table is missing in the database but exists in the ABAP Dictionary, you can create the table.
Once created, rerun the export process for the affected package.
Reverse Scenario
In some cases, the situation may be reversed — tables exist in the database but not in the ABAP Dictionary.
In such cases, these tables are ignored during the export process:
They are not included in any .STR file.They are not exported by SWPM.
This behavior is expected and does not require corrective action.
Thanks for reading !! Please feel free to add your thoughts.
Dear Reader,During the SWPM (Software Provisioning Manager) export phase, you may encounter situations where certain tables exist in the ABAP Dictionary but not in the database.This discrepancy can cause export packages to fail, resulting in export errors.Example Error in Package LogWhen such inconsistencies occur, the export log (e.g., <package-name>.log) will contain error messages similar to the following:——————————————————————————————————————————————————–A3EEEXP 008 Task failed with error: (EXP) DbSIExeRead failed with dbrc=103A3EEEXP 008 (EXP) SQL error = 942A2EETSK 007 Finished export for object “RSJOBMESSAGEHDLR” of type “table” with error in 0.00 sec #——————————————————————————————————————————————————–Identifying Failed TablesTo identify all failed tables within a specific package, open the corresponding <package-name>.TSK file.Entries for failed tables will typically appear in the following format:———————————————-D RSJOBMESSAGEHDLR E err———————————————-Verifying Tables in ABAP DictionaryOnce the failed tables are identified, you can verify their existence in the ABAP Dictionary using transaction SE14.ResolutionIf the table is missing in the database but exists in the ABAP Dictionary, you can create the table.Once created, rerun the export process for the affected package.Reverse ScenarioIn some cases, the situation may be reversed — tables exist in the database but not in the ABAP Dictionary.In such cases, these tables are ignored during the export process:They are not included in any .STR file.They are not exported by SWPM.This behavior is expected and does not require corrective action.Thanks for reading !! Please feel free to add your thoughts. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
