During an OS/DB migration, we have found that in our SAP SCM system there are 8 /BI0/06* tables and while all are listed in DBDIFF and DDNTT, only 5 exist in the database:
/BI0/0600000001
/BI0/0600000002
/BI0/0600000003
/BI0/0600000004
/BI0/0600000005
/BI0/0600000006 <<< not in ORACLE database
/BI0/0600000007 <<< not in ORACLE database
/BI0/0600000008 <<< not in ORACLE database
When we run the R3load migration the R3ldctl program includes the three tables 6-8 (which are not in the DB) in a SAPAPPL STR package
definition and so the migration tools try to export a table that is not there.
We have run the SMIGR_CREATE_DDL report and this report does NOT include these tables in it's *SQL files.
Is there some safe process to make these tables consistent with what exists in the database pre-migration to make things simpler?