EA-FINSERV 600 to 604

[Former Member]

Hi Guys,

I am trying to upgrade EA-FINSERV 600 to EA-FINSERV 604.

Burt when i m going to SAINT i can see the EA-FIN 603 and EA-FINSER 604 upgrade package but XML button is missing.

Stack configuration buttion is there but when i click it displays no xml found in solution manager.

I created new transaction in MOPZ but i am unable to find EA-FINSER for selection.

I have already upgraded the system to EHP4 but somehow EA-FINSERV was left on 600.

Please guide me on how to proceed.

Regards

Abhishek

[Former Member]

Hello Abhishek,

If this is the reason that you cannt upgrade EA_FINSERV without using XML then I think you need to use EHPI installer again using only one component(ie generated stack.xml file).

But before going to that I will suggest to raise an OSS message regarding the same ,see if there is any option to do it.

Thanks & Regards

Amit Barnawal

[Former Member]

Hi,

Using EHPI will take alot of time.

My question is if its working for QAS why is it not working for PRD.

I assume that it is not mandatory to upgrade EA-FINSER using EHPI only.

Since by clicking Stack configurationbutton system is unable to fetch XML from SOLMAN in PRD and same works in QAS system. There must be some issue between the PRD and SOLMAN.

Could some one guide me on how verfiy if same setting are maintained between PRD and SOLMAN as are between QAS and SOLMAN.

Regards

Abhishek

[Former Member]

Got solution from SAP.

Changed the entries in BCOS_CUST table.

Regards

[Former Member]

Dear Abhishek,

Stack file seems okay.

You have copied the file using root thats why owner is root:root,

You can change the owner as <SID>adm:sapsys and then proceed.

Thanks & Regards

Amit Barnawal

[Former Member]

Hi,

But i am still not getting the STACK XML button on SAINT screen.

There is only on STACK CONFIGURATION(fetch from solman) button.

I just checked my QAS system. When i clicked on stack configuration button it gave me a pop for EHP4 stack file.

So i think something is missing between my PRD and SOLMAN.

Please advice how to proceed.

Regards

Abhishek

Edited by: abhishek sharma on Dec 15, 2011 11:42 AM

[Former Member]

Dear Abhishek,

Why dont you download the EA_FINSERV 604 sar file from service market place and put it in /EPS/in

After that uncar it using SAPCAR and .PAT files will be genrated.

Using SAINT load that package and try to upgrade.

It might help.

Thanks & Regards,

Amit Barnawal

[Former Member]

Hi,

Under Saint screen i can see EA-FINSER603 and EA-FINSER604 as upgrade package type.

When i click on continue i get message these components should be upgrade using XML only.

As i have mentioned earlier for QAS system Stack configuration button pops a screen giving a option for EHp4 upgrade but same is not happening in PRD system

Regards

Abhishek.

[Former Member]

Dear Abhishek,

After copying the xml file in /EPS/in of production

give 777 permission to <SID>adm user and after that you perform saint upgrade.

you can open the stack.xml file directly and read the contents in that.

If EA-FINSERV 604 is present there then its right xml file.

Use link : http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b14f0c-b9af-2e10-ba83-f05ebcfbc...

This link provides how to generate stack.xml file, you have to select the components accordingly.

Thanks & Regards,

Amit Barnawal

[Former Member]

Dear Abhishek,

After copying the xml file in /EPS/in of production

give 777 permission to <SID>adm user and after that you perform saint upgrade.

you can open the stack.xml file directly and read the contents in that.

If EA-FINSERV 604 is present there then its right xml file.

Thanks & Regards,

Amit Barnawal

[Former Member]

Hi,

I have given 777 to STACK file but owner are root:root.

Here is stack file overview:

name></archives></software-component><software-component><caption>EA-FINSERV 604</caption><ppms-number>01200314690200006718</ppms-number><runtime-type>ABAP</runtime-type><name>EA-FINSERV</name><version>604</version><vendor>sap.com</vendor><support-package><caption>SP 01 for EA-FINSERV 604</caption><name>SAPK-60401INEAFINSRV</name><vendor>sap.com</vendor><ppms-number>01200314691100044119</ppms-number><sp-level>0001</sp-level><patch-level>0</patch-level><archives><archive-name abap-delivery-transport="SAPK-60401INEAFINSRV">K-60401INEAFINSRV.SAR</archive-name></archives></support-package><support-package><caption>SP 02 for EA-FINSERV 604</caption><name>SAPK-60402INEAFINSRV</name><vendor>sap.com</vendor><ppms-number>01200314691100046415</ppms-number><sp-level>0002</sp-level><patch-level>0</patch-level><archives><archive-name abap-delivery-transport="SAPK-60402INEAFINSRV">K-60402INEAFINSRV.SAR</archive-name></archives></support-package><support-package><caption>SP 03 for EA-FINSERV 604</caption><name>SAPK-60403INEAFINSRV</name><vendor>sap.com</vendor><ppms-number>01200615321100052444</ppms-number><sp-level>0003</sp-level><patch-level>0</patch-level><archives><archive-name abap-delivery-transport="SAPK-60403INEAFINSRV">K-60403INEAFINSRV.SAR</archive-name></archives></support-package><support-package><caption>SP 04 for EA-FINSERV 604</caption><name>SAPK-60404INEAFINSRV</name><vendor>sap.com</vendor><ppms-number>01200314691100050324</ppms-number><sp-level>0004</sp-level><patch-level>0</patch-level><archives><archive-name abap-delivery-transport="SAPK-60404INEAFINSRV">K-60404INEAFINSRV.SAR</archive-name></archives></support-package><support-package><caption>SP 05 for EA-FINSERV 604</caption><name>SAPK-60405INEAFINSRV</name><vendor>sap.com</vendor><ppms-number>01200615321100057806</ppms-number><sp-level>0005</sp-level><patch-level>0</patch-level><archives><archive-name abap-delivery-transport="SAPK-60405INEAFINSRV">K-60405INEAFINSRV.SAR</archive-name></archives></support-package><support-package><caption>SP 06 for EA-FINSERV 604</caption><name>SAPK-60406INEAFINSRV</name><vendor>sap.com</vendor><ppms-number>01200314691100055254</ppms-number><sp-level>0006</sp-level><patch-level>0</patch-level><archives><archive-name abap-delivery-transport="SAPK-60406INEAFINSRV">K-60406INEAFINSRV.SAR</archive-name></archives></support-package><support-package><caption>SP 07 for EA-FINSERV 604</caption><name>SAPK-60407INEAFINSRV</name><vendor>sap.com</vendor><ppms-number>01200314691100057151</ppms-number><sp-level>0007</sp-level><patch-level>0</patch-level><archives><archive-name abap-delivery-transport="SAPK-60407INEAFINSRV">K-60407INEAFINSRV.SAR</archive-name></archives></support-package><archives><archive-name abap-delivery-transport="SAPK-604DHINEAFINSRV">K-604DHINEAFINSRV.SAR</archive-name></archives><archives><archive-name abap-delivery-transport="EA-FINSERV604">EA-FINSERV604.SAR</archive-name></archives></software-component><software-component><caption>SAP_BS_FOUNDATION 701</caption><ppms-number>01200314690200007512</ppms-number><runtime-type>ABAP</runtime-type><name>SAP_BS_FND</name><version>701</version><vendor>sap.com</vendor><archives><archive-name abap-delivery-transport="SAP_BS_FND701">SAP_BS_FND701.SAR</archive-name></archives></software-component><software-component><caption>EA-FINSERV 603</caption><ppms-number>01200615320200009214</ppms-number><runtime-type>ABAP</runtime-type><name>EA-FINSERV</name><version>603</version><vendor>sap.com</vendor><archives><archive-name abap-delivery-transport="SAPK-603DHINEAFINSRV">K-603DHINEAFINSRV.SAR</

[Former Member]

Hello Abhishek,

Can you please check EPS/in of your production system and confirm that .xml file is present over there.

If not then it might be saved in your solution manager /EPS/in.

Copy that file in /EPS/in of production system.

then retry.

Thanks & Regards,

Amit Barnawal

[sunny_pahuja2]

What is SPAM/SAINT version ?

Thanks

Sunny

[Former Member]

Hi,

I had copied the XML to EPS/in for PRD.

SPAM and saint version is 7.01/42.

What should be the permission on stack in EPS/in.Currently its -rw-rr.

@Sunny: Could you please provide me steps for generating correct XML so that i can verify that i am not doing something wrong.

Regards

Abhishek

[Former Member]

Hi,

Its strange that you have upgraded your system leaving EA-FINSERV on 600 release.

upgrade using SAINT is not supported by SAP. You have to use EHPi for it. The message that you are getting above is correct.

[Former Member]

Hi,

Thanks for the reply.

I know it is not recommended by SAP but it is possible through SAINT.

I just want to know the method.

Regards

Abhishek

[Former Member]

check this link

[Former Member]

Hello Abhishek,

Please choose category like "enhancement...." and try in MOPZ. You should be able to find that and generate XML file. You can upgrade through SAINT with XML file.

Thanks,

Siva Kumar

[Former Member]

HI,

I created a new Solution and added my PRD system to it.

Then in mopz i selected EHP4 stack and just continued till the stack file generation came.

I checked on stack detail that EA-FINSER is 604.

But when i go to SAINT in my PRD i clicked on EA-FINSERV.i can see EA-FINSER603 and EA-FINSERV604 ( upgrade)

But when i click on stack configuration i get message no stack file found in MOPZ.

Please advice how to proceed.

Regards

Abhishek

[Former Member]

Did you Save the XML and supply in SAINT as usual procedure ?

[Former Member]

Hi,

I have saved it.

But under Log i am seeing message that procedure container contains no objects for implementation.

Regards

Abhishek

[Former Member]

Make sure XML file has the FINSERV component that you trying to upgrade ?

[Former Member]

Hello Abhishek,

Please place that XML file under .../EPS/in and click on tab "Stack XML file" from SAINT to upload and continue.

Please try that let us know if you still having problems.

Thanks,

Siva Kumar

[Former Member]

Hi,

Here is what i am doing.

1.)Create a new transaction. select solution and then check my PRD system.

2.)Select EHP

3) Select the file. EHP4 for ERP6.0 stack 07.I have checked the stack detail it show EA-FINserv 604.

4) Under technical usage i am not selecting anything.( I cant find EA-FINSERV)

after these i just continue till screen where i get XML is pushed in EPS/in

Then i login to my PRD system and execute SAINT.

5)There i select EAFINSERV component and select Continue.

6)On next screen i can see EA-FINSERV 603 and 604 as upgrade package type.

But i cant find the XML button only Stack configuration button is there. when i click on stack configuration i get message "There are no stack configuration XML available in mopz"

Please advice where i m doing wrong.

Regards

Abhishek

[sunny_pahuja2]

Hi,

First, in order to download EA-FINSERV packages, you need to select technical usage Financial Services in mopz then only you will get packages of EA-FINSERV.

Please make sure you login in client 000.

Thanks

Sunny

[Former Member]

Hello Abhishek,

I am with Sunny. You won't see that component until you choose technical usage as "Financial Services" in maintenance optimizer.

Thanks,

Siva Kumar

[Former Member]

Hi,

I selected the financial services as technical usage type.

I reached the screen where it says stack file exported to EPS/in. i completed the the transaction.

I logged on to 000 in PRD system. Executed Saint and selected EA-FINSER component and click continue.

On next screen i could see EA-FINSER 603 and EA-FINSER 604 as upgrade package type.I selected both and click on stack configuration (since stack XML button is missing) and i got pop up error message sayin no configuration stack file found in MOPZ.

Please advice how to proceed.

Regards

Abhishek

Edited by: abhishek sharma on Dec 15, 2011 9:02 AM

[Former Member]

Did you verify whether stackXML file exists now in EPS/in or not ?

Otherwise you also try to copy that stackXML from Solman EPS/in to PRD EPS/in as well, with good permissions.

Thanks

[Former Member]

Hello Abhishek,

I reached the screen where it says stack file exported to EPS/in. i completed the the transaction.

- XML file is saved under ../EPS/in in solution manager system. Please move that file into ../EPS/in in target system where you are deploying this component.

Thanks,

Siva Kumar