Just a note to you guys out there implementing Enhancement Package 3.
Basically this applies to anything imported using SPAM/SAINT.
If you run in to errors that stop the import process in any of the phases, just restart the import. Most of these are timing problems or miscellaneous quirks that are corrected automatically when you retry.
Hope this helps...
Tuesday, December 16, 2008
Monday, December 15, 2008
Syntax error in program SAPFGIDB in step XPRA Enhancement Package 3...
When performing the Enhancement Package 3 for ERP 6.0 upgrade, during step XPRA we ran into the following error message:
Error in the ABAP Application ProgramThe current ABAP program "RGICGLU1" had to be terminated because it has come across a statement that unfortunately cannot be executed.The following syntax error occurred in program "SAPFGIDB " in include "FGIDBF26" inline 240:"No component exists with the name "WRITE_SI_FOR_BCF". ."
After doing a lot of digging I found a reference to "WRITE_SI_FOR_BCF" in SAP Note 1153947.
The problem is, all of the changes listed in the note had already been applied to our system through support package 14 for SAP_APPL. It seems the upgrade will cause these changes, particularly steps 4 and 5 in the solution in Note 1153947.
After manually re-implementing steps 4 and 5, the upgrade finished successfully.
I hope this helps...
Error in the ABAP Application ProgramThe current ABAP program "RGICGLU1" had to be terminated because it has come across a statement that unfortunately cannot be executed.The following syntax error occurred in program "SAPFGIDB " in include "FGIDBF26" inline 240:"No component exists with the name "WRITE_SI_FOR_BCF". ."
After doing a lot of digging I found a reference to "WRITE_SI_FOR_BCF" in SAP Note 1153947.
The problem is, all of the changes listed in the note had already been applied to our system through support package 14 for SAP_APPL. It seems the upgrade will cause these changes, particularly steps 4 and 5 in the solution in Note 1153947.
After manually re-implementing steps 4 and 5, the upgrade finished successfully.
I hope this helps...
Tuesday, December 9, 2008
Error during Upgrade to Enhancement Pack 3 for ERP 6.0...
When Upgrading to Enhancement Package 3 for ERP 6.0, you may run into an error during the DD Activation Phase for EA_APPL. The objects that my upgrade kept failing on were the table EMMA_BPC and the view V_EMMA_BPC. The problem is that the view is built with a field that no longer exists in the source table. A quick consistency check in SE11 will tell you that.
The solution is to register V_EMMA_BPC, remove the erroneous field (CLASSJOB), and activate both the view and the table.
Then just restart your upgrade from where you left off.
You have no idea how much of a headache this was causing me the past few days.
UPDATE: This may occur on several different views on tables changed by Enhancement Pack 3. I recently ran into this same problem with view J_1AVEBRCH which had 2 erroneous fields.
Hope this helps...
The solution is to register V_EMMA_BPC, remove the erroneous field (CLASSJOB), and activate both the view and the table.
Then just restart your upgrade from where you left off.
You have no idea how much of a headache this was causing me the past few days.
UPDATE: This may occur on several different views on tables changed by Enhancement Pack 3. I recently ran into this same problem with view J_1AVEBRCH which had 2 erroneous fields.
Hope this helps...
Subscribe to:
Posts (Atom)