Solution : https://service.sap.com/sap/support/notes/942540 (SAP Service marketplace login required)
Summary :
When performing a system copy of a BW system, the import of the SAPDFACT package may fail due to improper handling of primary keys for F-fact tables. Symptoms include BCP Commit failures or DbSlEndModify errors in the R3load logs. The prerequisite to address this issue involves generating custom SQL files using the SMIGR_CREATE_DDL report, as outlined in note 771209. These generated SQL files should then be manually placed in the target system’s directory to guide table and index creation correctly. To resolve import errors, execute the described steps: regenerate and rerun the SAPDFACT import after dropping all affected tables using generated SQL scripts. This process ensures the correct table configurations are applied, mitigating key duplication issues.
Key words :
str <export directory>/db/ddlmss, directory <export directory>/db/<dbsys>, <export directory>/db/mss, bw systems differs slightly, <export directory>/data/sapdfact, import duplicate key errors, mentioned bcp-errors, r3load log shows, tablesstart query analyser, running r3load -ctf
Related Notes :
| 771209 | NetWeaver 04: System copy (supplementary note) |