cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from SAP 4.6C with AFS 3.0B to ECC 6.06 with AFS 6.6

0 Kudos

Hi All,

We are trying to upgrade our system from SAP 4.6c with AFS 3.0B to ECC 6.06 with AFS 6.6. We are struck with an error in the extraction phase (PREP_INIT/ADDON_SPEC1).

The error message refers to OSS Note 817898 and it is already implemented in the system.

The phase is struck saying Upgrade pre-requisites is not met for AFS and the upgrade cannot continue further.

Any suggestions are highly appreciated.

Thanks and Regards

Madhav

Accepted Solutions (1)

Accepted Solutions (1)

CharlesChen
Employee
Employee
0 Kudos

Hi Madhav,

So what's the error information reported in log files?

And the stack file was generated with AFS 6.6 for your target system, right?

It will be easier to understand the issue if you can upload the error log files and the stack file.

Best regards,

Charles

0 Kudos

Hi Charles,

Greetings. This issue occurs after PREP_INIT/UCMIG_DECISION phase. There are some prep checks done by the tool and it returns error saying

Upgrade pre-requisites for AFS are not met

You cannot continue with Prepare, resp. upgrade

See note 817898 for details!

We have applied this note and as per the note the report /AFS/CONVCHK_DOM_ZAEHK is returning a warning message because of data size in tables KONV (no conv) and RSEG

Please find the log files along with stack file attached herewith.

Have a nice day

Thanks and Regards

Madhav

0 Kudos

Hi All,

For the benefit of all users using this forum, the issue has been solved by SAP Product development team.

Technically as our system is IS_AFS, the solution provided by the support team is very specific to our landscape.

And to assist the support team, we made sure that OSS Note 817898 is applied and the table J_3ADUSR is populated with an entry. After this the support team was able to fix our issue.

Hope this helps someone having similar problem.

Thanks and Regards

Madhav

Former Member
0 Kudos

Hi Guys,

We are also in the process of upgrading 4.6c with AFS 3.0B to ERP6 EHP6 and same issue occurred.

SAP has logged into the system and done those changes of the table entries which are more than 2 character long to 2 character. After that we ran the report and it has resulted Green.

Then we restarted SUM tool from the scratch and facing the same issue in that phase.

Could you please let us know what we are still missing?

To let you know that the data element type DZAEHK is having NUMC Length 3.

Errors are as below

Former Member
0 Kudos

Upgrade prerequisites for AFS not met. You cannot continue with the Prepare, resp. Upgrade. See note 817898 for details! SAPup.log CURRENTPHASE # Cannot execute module 'PREP_IMPORT' because 'PREP_INIT' is not successfull! # Cannot execute module 'PREP_OQ_UNITTESTS' because 'PREP_IMPORT' is not successfull! # Cannot execute module 'PREP_PARSETUP' because 'PREP_IMPORT' is not successfull!

Former Member
0 Kudos

Another log after running SUM tool 4 ETQ010 Date & Time: 20160920141940  2 ETQ102 Finished execution of 1 process(es). 2 ETQ108 Analyzing logs for errors. 3 ETQ114 Analyzed 1 log files. 2 ETQ399 Requested task ID is 'AFSCHK'. 3 ETQ399 Generated TQL file 'SQLDBSCRIPT.TQL' with 1 SQL statements, log file 'SQLDBSCRIPT.OUT'. 4 ETQ276 Executing SQL-script "SQLDBSCRIPT.TQL" 3 ETQ120 20160920141940: PID 8508 execute 'E:\usr\sap\SBX\SUM\abap\bin_nuc\SAPuptool execdb ..\var\SQLDBSCRIPT.TQL', output written to 'E:\usr\sap\SBX\SUM\abap\log\SQLSTMTSTD.OUT'. 3 ETQ123 20160920141940: PID 8508 exited with status 0 (time 0.000 real) 3 ETQ399 Reading SQL output from 'SQLDBSCRIPT.OUT'. 4 ETQ205 Module state set to error. 1 ETQ207 Executing post-phase DB specific actions 0/1. 4 ETQ010 Date & Time: 20160920141940  1 ETQ202 Upgrade phase "ADDON_SPEC1" completed successfully ("20160920141940") Log:/logs/SQLDBSCRIPT.OUT 1 ETQ000 ================================================== 1 ETQ399 Executing SQL script '..\var\SQLDBSCRIPT.TQL'. 2 ETQ399 Connecting to database 'mss'. 3 ETQ398 SQL: SELECT APPLSZ FROM J_3ADUSR WHERE APPLSZ = 'OK' 4 ETQ010 Date & Time: 20160920141940  4 ETQ394 "OK" 1 ETQ000 ================================================== 4 ETQ010 Date & Time: 20160920141940  1 ETQ003 exit code: "0" Thanks and Regards Vanga Reddy

0 Kudos

Hi Vanga Reddy,

Greetings. Request to check the table J_3ADUSR entries after the error is rectified. And also, if the table is populated with the required entries, the phase can only be skipped by SUM with help of SAP development team. We were told that this issue will be fixed in latest SUM releases.

Would it be possible to let us know which SUM version you are using now

Thanks and Regards

Madhav

Former Member
0 Kudos

Hi Madhav,

Thank you so much for your reply.

As you said there is an entry in J_3ADUSR table with

APPSLZ = OK

NPROG = /AFS/CONV_DOM_ZAEHK

This table has been populated with these entries after we completed the one of the table entries from 3 to 2 character which are in error due to the fact that they used 3 character.

We also raised very high message and SAP is looking into it and AFS team has advised all these steps as per the note and even after that we are still facing this error in SUM phase.

Now, I think SUM tool experts are looking into it to skip this phase which is kind of bug in SUM.

We are using the latest SUM tool that is SUM10 SP17 (PL10).

Thank you so much again and let me know how the SAP guys skipped this SUM step to go forward.

Regards

Vanga Reddy

0 Kudos

Hi Vanga Reddy,

Normally this will be skipped by updating SUMup_par file with some entries. But to do this, they will have to coordinate with SAP AFS development team too. Hence, I suggest we should wait for them to give you the reply directly.

And also, I hope you are doing CUUC within the same project. Wish you good luck.

Thanks and Regards

Madhav

0 Kudos

Hi Vanga Reddy,

Any further update from SAP on that issue ? Were you able to proceed further

Thanks and Regards

Madhav

Former Member
0 Kudos

Hi Madhav,

Thanks for your reply.

I am still waiting for SAP to connect and update.

I will update you once they provide the solution.

Regards

Vanga Reddy

Former Member
0 Kudos

Hi Madhav,

Good morning.

SAP has provided the skip par file as you mentioned and the upgrade is progressing from that stage onwards.

Appreciated your response for this issue.

Regards

Vanga Reddy

rishan_ahamad
Explorer
0 Kudos

Hi Vanga Reddy,

That is great to hear. There will be one more phase, where you might need help from SAP to skip.

I would request to keep the ticket open so that they will be able to help you.

And also, our environment was MS SQL Server with SAP... If it is SQL, you should set collation before you upgrade to latest releases of SQL (just thought it would be useful). Please ignore if you are on other environment.

Thanks and Regards

Madhav

Former Member
0 Kudos

Hi Madhav,

We kept open the ticket till the end of the upgrade.

Yes, we are on Windows2003 with MSSQL2000 copied to Windows 2008 R2/SQL 2008 R2.

While copying it self I took care of all the required steps such SQL Collation, Kernel Patches and so.

I will keep you update.

Regards

Vanga Reddy

Answers (0)