BW migration error

[Former Member]

Hi Guys,

During a BW 3.5/oracle TEST migration, I am getting errors in database export. SAPAPPL1 and SAPAAPL2 fails because there are a lot of tables that exist only in ABAP dictionary but are missing from database.

Our developers did not create these in the databases. I have changed the TSK file to ignore these and continued withour errors but what si the right solution for these?

The table below are few examples

/BI0/0100000001 E ign

D /BI0/0100000011 E ign

D /BI0/0100000014 E ign

D /BI0/0100000016 E ign

D /BI0/0100000017 E ign

D /BI0/0100000018 E ign

D /BI0/0100000019 E ign

D /BI0/0100000029 E ign

D /BI0/0100000031 E ign

D /BI0/0100000039 E ign

D /BI0/0100000113 E ok

D /BI0/0100000115 E ign

D /BI0/0100000117 E ign

[Former Member]

I will ask them if they want to do that.

Thanks.

Message was edited by:

cyrus brocha

[Former Member]

Our BW guys say they dont want these tables in the database.

Thats why I did it.

Should I still create them in the database?

[david_malinconici2]

He should delete them in the ABAP dictionary.

There is no reason for having such tables defined in DDIC and not existing in database.

Additionally, even if you perform the export using ignore, the tables will be still created empty during import.

[Former Member]

I ran the SAP_DROP_TMP_TABLES report and some of these tables still exist only in ABAP dictionary and export fails due to it.

I checked with our BW developers and they dont need these tables in the database. So, I just set these table to "ign" in the TSK files and continued with the export.

I couldnt delete these tables using SE14 with delete database table option as it says table doesnt exist. In se11 also, I cant see these tables.

So skipping them in the export seemed the right solution.

Any Comments would be appreciated.

Thanks

Cyrus

[david_malinconici2]

Hi Cyrus,

you have to create those tables in database with SE14, not delete them.

Doing so R3load will export them with an empty content and everything will be run without modifying the task files.

David

[david_malinconici2]

You have two solution:

- run the report SAP_DROP_TMPTABLES in order to delete the temporary objects /BI0/01*

- create the object in database from SE14.

Regards,

David

[andreas_herzog]

or....

-> check your R3szchk.log and find entries reporting something similar to: "<b>table xyz not in DB</b>"

-> if found delete the corresponding entries in the *.STR files (for example SAPAPPL1.STR) - all lines belonging to that table entry...

GreetZ, AH