Skip to Content
0
Former Member
Jan 14, 2008 at 11:53 AM

error in upgrade from 4.6 to ecc 6.0

73 Views

Hi all,

We are upgrading from SAP 4.6 c to ecc 6.0 anr we are getting the following messages

UPGRADEPHASE XPRAS_UPG

1PEPU203X> Messages extracted from log file "SAPR700WG4.ORD" < Long text:

Cause

During the upgrade, a message relevant for postprocessing was writte to a log file. This message is not dealt with until the end of the entire upgrade. The upgrade continues.

System Response

The upgrade stops in phase CHK_POSTUP. To create the reference to the original log file, this message is generated by R3up.

What to do

Note the messages following this message and proceed according to the instructions.

A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_CONFIRM" must still be migrated

A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_UPDATE" must still be migrated

A2PESEEF_BADI 103 BAdI implementation "ZWORKORDER_UPDATE" must still be migrated

1PEPU203X> Messages extracted from log file "SAPR700ZG1.ORD" < Long text: see above

A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"

UPGRADEPHASE JOB_RDDNTPUR

1PEPU203X> Messages extracted from log file "RDDNTPUR.ORD" < Long text: see above

3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")

Long text:

Cause

A runtime object was found for a table which is unknown in the ABAP Dictionary. The table contains data, which is why, as a precaution, the runtime object was not deleted. Since there is a runtime object, this means the table was once create in the ABAP Dictionary. The fact that the table can no longer be found in the ABAP Dictionary could be due to the following reasons:

It is a customer-specific table which was created when the correction system was switched off.

Depending on the history of your system, there may also be SAP tables which were not deleted completely, or for which only the runtime object was delivered without the related definition in the ABAP Dictionary

System Response

What to do

RESET N1

Customer-specific tables

If it is a customer-specific table, and you still need the data, try to restore the table in the ABAP Dictionary.

Note the specified table type

when you do this (transparent table, pool table, and so on). The table may still, for example, be contained in the version database.

You can access version management through the menu "Utilities" in the in the ABAP Dictionary (transaction SE11).

You may also still have a copy of the system that still contains the table definition. You can also display the runtime object and create the table according to the field names, types and lengths specified in the definition. You can display the runtime object in the menu "Extras" of the database utility (transaction SE14).

Tables in the SAP namespace

Search for notes on these tables in OSS using the key words RDDNTPUR and TG447.

3PETG447 Table and runtime object "STGLTRAN" exist without DDIC reference ("Transp. table")

Long text: see above

3PETG447 Table and runtime object "STSLEVNTSV" exist without DDIC reference ("Transp. table")

Long text: see above

3PETG447 Table and runtime object "STSLTOBJSV" exist without DDIC reference ("Transp. table")

Long text: see above

3PETG447 Table and runtime object "STSLTRANSV" exist without DDIC reference ("Transp. table")

Long text: see above

3PETG447 Table and runtime object "TIBAN_ACTIVE" exist without DDIC reference ("Transp. table")

Long text: see above

3PETG447 Table and runtime object "ZPH_RESS_STATUS" exist without DDIC reference ("Transp. table")

Long text: see above

Please suggest what to be done in these cases.

Thanks