Upgrade to ECC6.0 problem

Question

Hi all,
Currently, I'm upgrading R/3 4.7 ext 2.00 to ECC 6.0.
In the Final Step before complete the SAPup needed me
to revise this
UPGRADEPHASE XPRAS_UPG
1PEPU203X> Messages extracted from log file "SAPR700ZE1.UG1" <
  Long text:
    Cause
      During the upgrade, a message relevant for postprocessing was written
      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.
A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"
UPGRADEPHASE JOB_RDDNTPUR
1PEPU203X> Messages extracted from log file "RDDNTPUR.UG1" <
  Long text: see above
3PETG447 Table and runtime object "RFIDPTFCATAG" 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 created
      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 "RFIDPTFIELDAG" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "RFIDPTPOSTAG" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "RFIDPTPOSTAG_T" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "RFIDPTPRENTCLC" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "RFIDPTPRENTVAL" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "RFIDPTPRPERTYP" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "T811MESS" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "TFARSIMONTH" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "TISLMONTH" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "TIVBE44" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "TIVBECTYP" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "TIVBECTYPT" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "TIVBEKOFI" exist without DDIC reference ("Transp. table")
  Long text: see above
3PETG447 Table and runtime object "TIVBEOBJ" exist without DDIC reference ("Transp. table")
  Long text: see above
Any help would be appreciate.
Rapheephan

Answer 1

Dear Rapheephan
I search AGS Global message as same as your problem.
this is rely from AGS.
but there is still no confirmation to solve this problem by this rely
Please re-review SAP Note 69455 specifically section 3. Upgrade behavior
and section 4. Combination with Add-ons for resolution.
This section explains your error messages and how it can be remedied
post upgrade. As stated in the note:
3.  Upgrade behaviour
During system upgrade the addon ST-A/PI gets lost just like standard
coding ("passive deletion"). No restrictions on upgrade target
releases or similar. Choose "Passive deletion" whenever the upgrade
asks you about ST-A/PI. You do not need the files of ST-A/PI for the
target release during the upgrade. You do not need to update an old
ST-A/PI prior to an upgrade.
4.  Combination with other add-ons
After upgrade you may find messages like 'Table /SSF/.. exists
without DDIC reference' concerning service tool tables in the
CHK_POSTUP phase or in DB02. These are harmless and most easily
solved by implementing ST-A/PI on the new release. Then run report
RTCCTOOL and follow the recommendation 'Procedure after upgrade'
(takes 2 clicks from inside the tool).
Combination with other add-ons
All combinations of ST-A/PI with all other addons are released. No
conflicts with any other support package or addon.
To prevent any possibility of conflicts or interference with
productive transactions, ST-A/PI objects are in independent separate
namespaces /SSF/+/SSA/ (transaction codes ST12-ST14 and report
source RTCCTOOL are the only exception to this rule).
Best Regards
JangHyun.