MOPZ has issues calculating stack XML file in SOLUTION MANAGER

Hello,
We have a SOLUTION MANAGER system on NW 7.0 EHP1 SP stack level at initial support stack (ISS).
Recently we upgraded all our R/3 systems to ECC6.0 EHP4 SPS04 and now we are trying to upgrade the stack level to EHP4 SPS07. So we are trying to get a XML file from MOPZ but no luck.
The backend system has all the correct data updated in SMSY and all looks fine but while we try to calculate the stack for EHP4 SPS07 it ends with error like below mentioned.
Please look into the errors and throw some light if anyone has come across the same.
Error details:
System Messages
Type Message Text
Error The Installation/Upgrade Package for Add-on EA-APP L rel. 600 is not available
Error ABAP queue check failed
But the backend system has EA-APPL level at 604, we do not know why it is looking for installation/upgrade package for
EA-APPL 600.
Regards,
Yoganand.V

hi
can you check the sap note
1. Note 1277035 - Solution Manager: EHP4 product data missing
might be this could be the reason for your issue
or
check the thread already discussed the same and the solution also provided
[EHP4 upgrade error on SAPK-603DHINEAPS|EHP4 upgrade error on SAPK-603DHINEAPS]
////////////////It seems that there is a small bug in teh software vector for EA-PS.
Essentially, SAINT prevents you from going forward because it thinks that you don't have the correct version of EA-PS installed.
The solution for this is described in OSS Note: 1143022
"To import EA-PS in a system that already has the level EA-APPL 604, load the attached file ACP_EAPS.SAR into your system (SPAM-> Support Package -> Load Packages -> from Frontend) before you start the import using SAPehpi. Otherwise, an error may occur in the queue calculation, which can be solved by reloading the ACP"////////////////////////
check and update
Jansi

Similar Messages

XML File in Solution Manager

How to Generate XML file in solution manager for EHP5 upgrade

Hello,
You can find links to many interesting documents and also some troubleshooting guides at https://wiki.sdn.sap.com/wiki/display/SM/Maintenance+Optimizer
Best regards,
Miguel Ariñ

EHP4 - Stack XML file related issue

Hi,
I have the following two issues from DSWP tcode (or solution_manager):
1. From DSWP code -> Change Management -> Maintenance Optimizer, New
Maintenance Transaction and i select the ERP system , then i select the radio button Enhancement Package Installation after which it is showing a drop down from where i can
select EHP4 installation and second drop down i can select support
stack 03. But if i do the same thing again by coming out and going back
in on the same day it is showing only support stack 01, Next day again
for one time it is showing.. --- Why is it like this ?
2. Also after selecting the EHP4 version, support stack 03 it log's on
to the ERP system and it comes out with lot of components from
which if i select some of them and deselect some of them as per our
need, it continues to next screen and confirms the file from download
manager and also the XML file gets's created but unfortunately the XML
file contains all components including the one we deselect because of
which we ended up in doing all shown components last week. We
are in a stage of applying another technical usage and the xml is
created with all the components again. Any idea how to avoid this ?
Thanks,
Murali.

Hi,
The problem might be configuration of your system in SMSY transaction ...Because if some componenets you have selected there will come as selected by default...
Moreover go to SAP Note 1134872 - Maintenance Optimizer: FAQ for Stack Delta Files and related sap note to this note which contains problems related to MOPZ and stack xml file..
Thanks
Sunny

RPT_MOPZ_COPY_STACK_XML shows SC version differs for JAVA and DUAL-Stack xml files

Hi All,
I am using the report/program RPT_MOPZ_COPY_STACK_XML to copy the stack xml file I used from a previous upgraded system. Systems are identical. However, report shows below..
"Software Component Version KRNL64UC7.20 [01200615320200013056] differs between <System1> and <System2>"
and
Software Component Version SAPJVM6.1 [01200615320200012982] differs between <System1> and <System2>"
However, this is not the case when checked, it's strange that this particular component has the same version between the two systems, but the report says they differs in version.
Please help check how to resolve the issue.
SAP notes mentioned in below KBA were already obsolete. Solution Manager system just upgraded to 7.1 SP11.
1711612 - RPT_MOPZ_COPY_STACK_XML Report Troubleshooting.
We would appreciate your response for us to resolve this issue. Thanks.
Regards,
Philip

Hi Jansi, Divyanshu,
Both system have the same patch levels.
Here the situation, SYS1 is where we generated the stack xml file. Afterwards, used that stack file to upgrade SYS1.
Now we built SYS2, ensuring it has the same components version with the un-upgraded version of SYS1, so yes they have same patch number for same components, for this issue, kernel and jvm.
Thus, instead of running MOPZ for SYS2, we used RPT_MOPZ_COPY_STACK_XML to convert the stack file of SYS1 to be used for SYS2.
This is where we encountered below messages, when performing the copy.
"Software Component Version KRNL64UC7.20 [01200615320200013056] differs between <System1> and <System2>"
and
Software Component Version SAPJVM6.1 [01200615320200012982] differs between <System1> and <System2>"
We previously used SOLMAN 7.0 SP23, and the report is working fine there. Then recently, solman was upgraded to 7.1 SP11, and now the report is not working with the above issue.
We would appreciate if you could share actions on how we can fix the issue.
Regards,
Philip

Twicking Stack.XML file

Hello Experts,
We are doing the ECC6 EHP4 upgrade in our system. As per the process we generated Stack.XML first from our Solution manager for our test system and we used it for very first EHP4 installation on our test system. EHP4 was successfully installed. Now we are repeating the exact same EHP4 installation in to our next system which has different SID, Host etc.
Is it possible to just update the existing Stack.XML file and replace new host and SID of the next system in it, rather than re doign all Solution Manager steps just to generate new Stack.XML for next system ?
Thanks,
Harshal

Good to hear that, so what all i need is just to change the
Hostname, SID and installation number in it ?
or
anything else as well ? How should i keep the new file name as it contains some numbers in the file name
(e.g. SMSDXML_<SID>_<DATE&TIME>.<ID> (SMSDXML_ECB_20100121000340.255) ?
Thanks,
Harshal

Cannot generate stack.xml file

Greetings,
We are not able to generated stack.xml file in /usr/sap/trans/EPS/in
We have tried in /n/tmwflow/mopz_stack.
MOPZ is configured we are able to approve support patches
This xml file is required to upgrade the ECC_DIMP from 600 to 605
Please advice
R..../-

Wrote to SAP. Got the below mentioned reply from them
Please make sure that in transaction SMSY, in the Header Data tab for
the system you want to upgrade, both ERP 6 and EHP5 for ERP 6 are added
as product versions and also active. Information about why this is
needed can be found in note 1464712.
Please don't forget to choose a relevant product instance for ERP 6.
After this is done, please enter the system in an ERP 6 logical
component. Please add the new ERP 6 logical component to another
solution, and please proceed to opening the Maintenance Optimizer
transaction from the solution with the ERP 6 logical component.
The option to choose should be 'Enhancement Package install'.
The technical usage to choose is Discrete Ind.& Mill Products.
If somehow you are not able to choose technical usage Discrete Ind.&
Mill Products in the technical usage screen in Maintenance Optimizer:
please check note 1324838 for the required product instances of ERP 6
in SMSY.

Error while generating stack.xml file in solman

Hi All,
I am unable to generate a stack.xml file in solman, below is the error.
Also, how to select a patch for Java stack JVM in solman. Please help me.
Thanks,
Dheeraj

Hi Kartik,
Thanks for the info.
I am trying to upgrade SAP JVM from 6.1.49 to 6.1.64,
I tried by manually downloading the file and upload it through SUM it was not successful.
Now I am trying with stack.xml and some product instance are not installed.
Any suggestions??
Regards,
Dheeraj

TS1192 'Could not read the iPhoto Library. The library at [file path] has a corrupted AlbumData.xml file.'

Got this msh from Piasa...any ideas? 'Could not read the iPhoto Library. The library at [file path] has a corrupted AlbumData.xml file.'

Contact Adobe support - that is not an iPhoto message - in general Piasa has no ability to access the iPhoto library - there have been hacks but often they do not worka nd can cause problems
You need to user either Picasa or iPHoto - using both on the same photos is problematic
LN

Stack.xml file

Hi,
Currently we have NW7.0 SR3 (ABAPJAVA), Now we are planning to upgarde to EHP1 through ehp1 tool. how i can generate stack.xml file for (ABAPJAVA) stack without solution manager. Kindly help me
Regards,
Sampath.

Hi,
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/swdc/sps/index.do?pvnr=01200615320900001250&u=&session_id=saS000427859520110124070001SID%3aANON%3apwdf4962_OW1_01%3aBkxYmOjMQn50g5RGGRAOjSdi_oZwuReU3be5uAej-ATT
Check here.
You have NW 7.0 as source and EHP1 is present in target.
Regards,
Nirmal.K

Error while Importing ResourceObject xml file in Deployment Manager

Hi Everyone,
I am getting this error while doing Import of HRPeopleSoftResourceObjects.xml ( A Resource Object xml file) in Deployment Manager. I am doing this step for Authoritative(Trusted Source) Reconciliation.
Error Says:- Attribute not present in EntityDefination of User :: ExpectedReturnDate.
ExpectedReturnDate is a UDF (Customize) field. I did Metadata and Sandbox import for this field to create this attribute in OIM. I can see this attribute on User Details screen as well as in User Table in OIM. So, ideally this error should not popup. I have to do this import for Reconciliation.
I pulled and checked all the xml files like(UserEO.xml.xml, userEO.xml.xml, userVO.xml, UserVO.xml.xml) from oracle.iam.console.identity.self-service.ear_V2.0_metadata1 and found ExpectedReturnDate field is available.
I am using: OIM Version - Oracle 11g Release 2
Database version - 11.2.0
Weblogic version - 10.3
Please let me know how to resolve this error.
Appreciate your response and support!
Warm Regards
Vijay Kumar

Appreciate your response Kevin!
I saw your response today. What you have suggested in your post make perfect sense to me.
Yesterday, I was able to create Reconciliation profile successfully. No idea how it worked so, didn't updated my post.
I tried to re-import the UDF, noticed ExpectedReturnDate attribute has little icon in fornt of it on deployment manager screen which says on mouse over "new field". No idea why as I didn't delete it from anywhere, perhaps it didn't get imported properly previously. I stepped ahead and clicked the import button on deployment manager but failed as it was throwing an exception which says udf_usr_expectedReturnDate is available in usr table. That makes sense to me as this column got created in usr table in OIM because of previous import and I didn't delete it either. This raised couple of doubts more as, along with this attribute there were other attributes in the same metadata xml file which were part of previous import and their respective columns were already created in usr table. Then why message poped-up for this field in particular? Anyway I went ahead with the import process.
Now I stopped all the server (Admin, SOA and OIM) and restarted them again and performed the same steps as mentioned above and this time it worked as expected. UDF file got imported successfully.
After this I went to Design Console verified all the fields and created the Reconciliation Profile. I checked OIM database and found RA_ProfileName recon tables got created.
As per your comment, Today I checked the RECON_USER_OLDSTATE table but this table is empty.
Still I have couple of doubts, if Reconciliation Profile got created it should create the xml file under metadata direcectory(in my case path should be: /apps/Oracle/Middleware/Oracle_IDM1/server/metadata/db). Please correct me if I am wrong? I hope it should be physical file not a logical file.
Once again thanks for your response!
Warm Regards
Vijay Kumar

Error while importing xml file in calc manager

Hi All,
I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
-Kamran

Hi All,
I am having trouble in importing the xml file for calc manager. I have used the rules migrator utility to convert the .rle file into XML. Now when I import this xml file in the calc manager it gives me the following error- "An invalid application 'XML file name' was found on object Main_Global". Please let me know how should I import the xml file in calc manager and get it deployed. Thakns in advance for the help.
-Kamran

Problem with Stack XML file

Hello,
We have an ECC 6 system with EHP 4 SPS 5 and we watn to install a new Technical Usage (IS-OIL, IS-PRA and IS-UT)
In order to do that I have to supply an xml file created by the MOPZ.
I created a new MOPZ transaction, in the phaze "Update Options" I selected : Enhancement Package Installation,
Afterwards I selected in Target Enhancment package stack : SAP ERP Enhanecment Package 4 on NW7.01 - SP Stack 05
We do not want to upgrade the Stack to a latter one.
I have selected Oil & Gas with Utilities and continued.
The Sack XML that was created contained SAP-APPL, SAP-BASIS and SAP-ABA in patch level 8. we do not want to upgrade these components.
Is there a way to install a new Technical Usage without upgrading these components?
and if there is how can I create XML file suited for this situation?
Please Advice,
Zvi Gilinsky

Hello,
There is an equivalence of Support Package levels between EHP stacks and baseline ERP 6 stacks. Note 1064635 has a list of these equivalences.
In any case, stack 5 for EHP4 of ERP should include stack 5 of NW 701.
By your description it looks like you are having a Maintenance Optimizer issue. What is the Maintenance Optimizer stack level?
Best regards,
Miguel Ariñ

Can't convert stack XML file using report RPT_MOPZ_COPY_STACK for upgrade

Hello Colleagues/ SAP Experts,
Here is a background. 2 weeks ago, we have generated an XML stack file using MOPZ in solman 7.1 for the following systems (P6D which is DEV,
P6Q which is quality, P6R which is regression and P1P which is production). We were at our technical cutover rehearsal phase and the system that we were rehearsing was P6R. But AFTER our technical cutover, a new java component, which is seeburger as2 adapter, was installed in P1P, PRODUCTION. Thus, the landscape of P1P has changed as a new component was introduced and we believe that the generated XML file 2 weeks ago will no longer be valid for P1P. Instead of generating another xml file thru mopz for P1P, we would like to use report RPT_MOPZ_COPY_STACK_XML to convert the XML file OF P6R to map it toP1P. I have uploaded P6R XML and the target is P1P. So as you can see, P6R XML (source) --> P1P target.
Actions already done are the following:
1) Fulfilled and followed the resolution in note: 1711612
RPT_MOPZ_COPY_STACK_XML Report Troubleshooting
2) SAP-OSS is working in SM59
Basically, program RPT_MOPZ_COPY_STACK does not convert the Regression system's xml to the target, which is production. Kindly see attached screenshot. *the screenshot shows only 1 component in error but upon clicking the 'next difference' button, it will still show other components. I have checked my lmdb settings, will there be workaround for the issue?
Regards,
Meinard

Hello Divyanshu Srivastava / Reagan Benjamin ,
Thank you for your replies. Yes I noticed that a new higher patch for one java component was already present when I have regenerated recently for production using mopz. Anyways, SAP has returned a message wherein they edited the xml file themselves. Most of errors were eliminated only error was kernel versions was not matched. We need to upgrade kernel of our production and test if it works. Hopefully it will. Thanks though at first we did not edit the xml as according to one sap note I read it will not be supported by SAP. Closing this thread now

Issue with uploading XML file from application server into internal table

i Need to fetch the XML file from the application server and place into internal table and i am getting error message while using the functional module   SMUM_XML_PARSE and the error message is "line   1 col   1-unexpected symbol; expected '<', '</', entity reference, character data, CDATA section, processing instruction or comment" and could you please let me know how to resolve this issue?
    TYPES: BEGIN OF T_XML,
             raw(2000) TYPE C,
           END OF T_XML.
DATA:GW_XML_TAB TYPE T_XML.
DATA: GI_XML_TAB TYPE TABLE OF T_XML INITIAL SIZE 0.
DATA:GI_STR TYPE STRING.
data: GV_XML_STRING TYPE XSTRING.
DATA: GI_XML_DATA TYPE TABLE OF SMUM_XMLTB INITIAL SIZE 0.
data:GI_RETURN TYPE STANDARD TABLE OF BAPIRET2.
    OPEN DATASET LV_FILE1 FOR INPUT IN TEXT MODE ENCODING DEFAULT.
    IF SY-SUBRC NE 0.
      MESSAGE 'File does not exist' TYPE 'E'.
    ELSE.
      DO.
* Transfer the contents from the file to the work area of the internal table
        READ DATASET LV_FILE1 INTO GW_XML_TAB.
        IF SY-SUBRC EQ 0.
          CONDENSE GW_XML_TAB.
*       Append the contents of the work area to the internal table
          APPEND GW_XML_TAB TO GI_XML_TAB.
        ELSE.
          EXIT.
        ENDIF.
      ENDDO.
    ENDIF.
* Close the file after reading the data
    CLOSE DATASET LV_FILE1.
    IF NOT GI_XML_TAB IS INITIAL.
      CONCATENATE LINES OF GI_XML_TAB INTO GI_STR SEPARATED BY SPACE.
    ENDIF.
* The function module is used to convert string to xstring
    CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
      EXPORTING
        TEXT   = GI_STR
      IMPORTING
        BUFFER = GV_XML_STRING
      EXCEPTIONS
        FAILED = 1
        OTHERS = 2.
    IF SY-SUBRC <> 0.
      MESSAGE 'Error in the XML file' TYPE 'E'.
    ENDIF.
ENDIF.
IF GV_SUBRC = 0.
* Convert XML to internal table
    CALL FUNCTION 'SMUM_XML_PARSE'
      EXPORTING
        XML_INPUT = GV_XML_STRING
      TABLES
        XML_TABLE = GI_XML_DATA
        RETURN    = GI_RETURN.
ENDIF.
READ TABLE GI_RETURN TRANSPORTING NO FIELDS WITH KEY TYPE = 'E'.
IF SY-SUBRC EQ 0.
    MESSAGE 'Error converting the input XML file' TYPE 'E'.
ELSE.
    DELETE GI_XML_DATA WHERE TYPE <> 'V'.
    REFRESH GI_RETURN.
ENDIF.

Could you please tel me why the first 8 lines were removed, till <Soap:Body and also added the line <?xml version="1.0" encoding="UTF-8"?> in the beggining .
Becuase there will be lot of XML files will be coming from the Vendor daily and that should be uploaded in the application server and should update in the SAP tables based on the data in the XML file.
what information i need to give to vendor that do not add the first 8 lines in the XML file and add the line in the beggining <?xml version="1.0" encoding="UTF-8"?>   ??????
Is there any other way we can do with out removing the lines?

Facing issue while reading XML file 'LPX-00217: '

Hi Gurus,
I am facing one issue while reading the xml file in the one my 11g database instance. The same file if I ran in another instance then it is working fine for me.
I presume it will be related to NLS character. Please help me in finding out character set.
And the issue where I am getting instance character set is 'US7ASCII', and I am not getting this issue in another instance where the character set is 'UTF8'.
And here is the issue I am getting when I was trying to load that file.
Error Occurred :=ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML
processing
LPX-00217: invalid character 150 (U+0096)
Error at line 1
Pls help me in debugging this issue.
Regards,
Nagendra
Edited by: 838961 on Jul 12, 2011 9:32 PM

Hi,
Pls help me in debugging this issue.There's not much to debug actually.
The US7ASCII charset stores 7-bit characters, but you're trying to insert a value out of range (150). So that's expected behaviour.
There were some "tricks" to allow that on some versions, using NLS settings, but it's definitely not the clean way to do it so I won't develop.
The best thing you have to do is to migrate to character set AL32UTF8, which is fully compliant with XML.

MOPZ has issues calculating stack XML file in SOLUTION MANAGER

Similar Messages

Maybe you are looking for