Explorer Version for MDM 5.5 SP06

Hi,
I was wondering if MDM 5.5 SP06 supports any other internet explorer version than IE6?
I found a note (1422355) regarding 7.1 where support for IE 8 is mentioned, but nothing about the 5.5 version.
I think the PAM mentions IE6, but I just want to make sure, since there are so many hotfixes
Best Regards
Olof

Hello Olof
Sorry i don't have "Portal Business Package" guide for SAP MDM 5.5 SP5
But As i told you early.
if you look at that guide ( for SAP MDM 5.5 sp6) (Page 10):
https://websmp201.sap-ag.de/~sapidb/011000358700001119502007E
"...Browser Recommendation: Any browser supported by EP 6.0 or EP 7.0..."
Do you have "Portal Business Package" for SAP MDM 5.5 SP5 guide for supported browsers search?
and you can ask your Portal consultant or found in TEP10 which kind of browsers aresupported.
Regards
Kanstantsin Chernichenka
Edited by: Kanstantsin Chernichenka on Mar 29, 2011 3:39 PM

Similar Messages

Internet Explorer versions for 5.1.9

We have a system that is running Business Objects 5.1.9.
We need to update to Internet Explorer version 7 from 6.
I have searched all over for the relevant documenation without success.
Can anyone help point in the direction of the documentation.
We need to understand if there will be any issues but are short of development environments to test it.
Thanks.

More specifically this link:
http://www.mirrorservice.org/sites/browsers.evolt.org/browsers/ie/mac/5.1.7_Clas sic/InternetExplorer517EN.bin
However, I would highly recommend using Wamcom Mozilla instead. You can stop popup advertisements, and it is much better support of many newer websites than Internet Explorer on Mac OS 9. It can be found here:
http://www.wiwi.uni-frankfurt.de/wamcom/20030723/wamcom-131-macos9-20030723.sit
Using it though, I'd close the left sidebar for most optimized speed.

How do I initialize the ItemDetails screen when first presented for MDM WD

Hello everyone!
Iu2019m new to the world of netweaver ce and webdynpro for MDM and need a little help with what Iu2019m sure is a basic code problem for most of you. Please help if you can! I am a developer for MDM 7.1 sp06. We are now experimenting with Enterprise Portal using NetWeaver CE 7.2. I have create and deployed an application using NetWeaver Design Studio 7.2. I have also created some screens in the WD Configuration Manager for MDM.
The 2 interface views I have configured are u201CSEARCHu201D and u201CITEMDETAILSu201D. u201CITEMDETAILSu201D was limited to ADD/CREATE new items in MDM using the WD Configuration Manager options.
When I created the WD application in NWDS I also created a link with buttons between the 2 screens/views. When I then deploy my application and I press the button to go from my u201CSEARCHu201D screen/view to the u201CITEMDETAILSu201D ADD screen/view, All I see is a u201CCREATEu201D button and no other fields.
I expected to see every field without values in them just as I do when I u201CPREVIEWu201D the screen in the WD Configuration Manager . If I continue and press the u201CCREATEu201D button on the the u201CITEMDETAILSu201D view, The screen the then presented as I expected with all fields showing but without any values populated in them. I donu2019t want the user to have to press the create button the first time they are presented with this screen.
Can anyone tell me or give me a sample of code that will initialize the itemDetails view just as it is seen when previewed in the WD Configuration Manager?
Thank you
Steve

Thanks for the reply but I dont have any problem calling the ItemDetailsInterface. My problem is when I call the ItemDetailsInterface the screen that is presented has no data other than the buttons. I would like the ItemDetailsinterface to display exactly as it does when I preview the screen in WD configuration manager.
What I expect to see is... a screen showing all the buttons plus all the ItemDetails Fields but with the fields initilized as null. this would then allow my user to input the fields needed to create a new record. As it works now... when the user is sent to the ItemDetails view... all they see is the "Cancel" and "Create" button. They have to press the "Create" button 1 time inorder to present the screen a second time but this time witlh all fields presented.
I believe I have to set the "LeadSelection" or the "internalID" to -1 the first time thru the ItemDetails "DoInit" section. So far, no luck.

Recommendation for MDM monitoring tool

Dear all
We are using MDM 5.5 Sp06 on HP Unix. What should we use as an monitoring tool?
CCMS and SMD is not supported for the above combination.
Please suggest. Thanks in advance.
Regards
Ravi

Thanks Markus for the reply.
SMD is not supported for MDM 5.5 sp06 on HP UNIX platform. We got this confirmed in one of the SAP OSS message also.
since MDM 5.5 SP06 P4 we are supporting CCMS heartbeat again. The documentation is almost finished and waits for last rework - will be provided soon
We are not using P4, but if you can share the documentation or provide the link, it will help a lot.
Just to re-confirm CCMS heartbeat is supported for SP06 P4 on HP Unix. Can you please confirm this?
Thanks in Advance-
Ravi

Server and client version for configuring/developing offline kapsel apps

Hi all.
I am planning to develop an offline Kapsel app.
I have two questions.
Q1.I have installed SP05 version for SMP server and SP06 version as SMP client. Is this configuration sufficient to begin with?
Q2. Is a delta token enabled SAP ABAP service mandatory for developing an offline app?
Need your help on this.
Thanks.

Hi Daniel Van Leeuwen ,Jitendra Kansal
I am using SAP Netweaver Gateway services instead of Integration Gateway.
I am now able to read the data when online, but get an error when I try to open the Offline store.
Does this have to do anything with the Netweaver Gateway?
The server log is as below.
#2.0#2015-04-23 07:25:11.9#+0:00#INFO####Offline#1429708585665001#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########450###<47> Synchronization failed#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072043#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at org.apache.olingo.odata2.api.ep.EntityProvider.readMetadata(EntityProvider.java:809)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072044#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at com.sap.odata.offline.scripts.ODataSyncHandler.prepareMetadata(ODataSyncHandler.java:358)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072045#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at com.sap.odata.offline.scripts.ODataSyncHandler.doHandleUploadData(ODataSyncHandler.java:209)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072046#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at com.sap.odata.offline.scripts.ODataSyncHandler$1.call(ODataSyncHandler.java:174)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072047#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at com.sap.odata.offline.smp.MLSMPFactory.executeWithContext(MLSMPFactory.java:156)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072048#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at com.sap.odata.offline.scripts.ODataSyncHandler.handle_UploadData(ODataSyncHandler.java:179)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072049#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at sun.reflect.GeneratedMethodAccessor423.invoke(Unknown Source)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072050#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072051#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at java.lang.reflect.Method.invoke(Method.java:606)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072052#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at ianywhere.ml.script.MethodInfo.invoke(MethodInfo.java:11826)#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072053#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] '#
#2.0#2015-04-23 07:25:11.021#+0:00#ERROR#RequestResponse#200##Offline#1429708585072054#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10225] Failure occurred while executing user supplied code in the server#
#2.0#2015-04-23 07:25:11.021#+0:00#INFO#RequestResponse#200##Offline#1429708585072055#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> end_upload <connection> (no script)#
#2.0#2015-04-23 07:25:11.021#+0:00#INFO#RequestResponse#200##Offline#1429708585072056#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> end_publication <connection> (no script)#
#2.0#2015-04-23 07:25:11.021#+0:00#INFO#RequestResponse#200##Offline#1429708585072057#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> end_synchronization <connection> (no script)#
#2.0#2015-04-23 07:25:11.005#+0:00#DEBUG#RequestResponse#200##Offline#1429708585072033#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.SessionLogger:debug#username#######447###ML_SCRIPT Exit handle_UploadData: remoteID=127d6d6a-e9e6-11e4-8000-d25ebbb51773#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072034#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] Exception thrown in method: 'public void com.sap.odata.offline.scripts.ODataSyncHandler.handle_UploadData(ianywhere.ml.script.UploadData) throws java.lang.Exception'. Error description: 'java.lang.IndexOutOfBoundsException: Index: 0, Size: 0'.#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072035#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] Stack trace: 'java.lang.IndexOutOfBoundsException: Index: 0, Size: 0#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072036#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at java.util.ArrayList.rangeCheck(ArrayList.java:604)#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072037#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at java.util.ArrayList.get(ArrayList.java:382)#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072038#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at org.apache.olingo.odata2.core.ep.consumer.XmlMetadataConsumer.readAssociation(XmlMetadataConsumer.java:427)#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072039#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at org.apache.olingo.odata2.core.ep.consumer.XmlMetadataConsumer.readSchema(XmlMetadataConsumer.java:152)#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072040#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at org.apache.olingo.odata2.core.ep.consumer.XmlMetadataConsumer.readMetadata(XmlMetadataConsumer.java:102)#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072041#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at org.apache.olingo.odata2.core.edm.provider.EdmxProvider.parse(EdmxProvider.java:51)#
#2.0#2015-04-23 07:25:11.005#+0:00#ERROR#RequestResponse#200##Offline#1429708585072042#127d6d6b-e9e6-11e4-8000-d25ebbb51773#com.mycompany.app#com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged#username#######447###<47> [-10158] 	at org.apache.olingo.odata2.core.ep.ProviderFacadeImpl.readMetadata(ProviderFacadeImpl.java:225)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072001#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> Table #1: LODATA_SYS_PROPERTIES, 3 columns#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072002#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> propertyID integer NOT NULL PRIMARY KEY#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072003#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> longValue bigint#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072004#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> stringValue long varchar#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072005#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> Table 'LODATA_SYS_PROPERTIES' is referenced by publication 'LODATA_DATA_PUBLICATION'#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072006#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> Table #2: LODATA_SYS_REQUESTS, 4 columns#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072007#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> requestName varchar(128) NOT NULL PRIMARY KEY#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072008#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> definingRequest long varchar NOT NULL#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072009#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> deltaLink long varchar#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072010#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> refreshSubset bit NOT NULL#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072011#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> Table 'LODATA_SYS_REQUESTS' is referenced by publication 'LODATA_DATA_PUBLICATION'#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072012#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> Table #3: LODATA_SYS_COMMAND, 3 columns#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072013#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> ID integer NOT NULL PRIMARY KEY#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072014#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> commandID tinyint NOT NULL#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072015#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> argument long varchar#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072016#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> Table 'LODATA_SYS_COMMAND' is referenced by publication 'LODATA_DATA_PUBLICATION'#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072017#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> authenticate_user <connection> (no script)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072018#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> authenticate_user_hashed <connection> (no script)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072019#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> authenticate_parameters <connection> (no script)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072020#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> modify_user <connection> (no script)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072021#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> begin_synchronization <connection> (no script)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072022#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> begin_publication <connection> (no script)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072023#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> begin_upload <connection> (no script)#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072024#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> handle_UploadData <connection>#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072025#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########447###<47> com.sap.odata.offline.scripts.ODataSyncHandler.handle_UploadData#
#2.0#2015-04-23 07:25:10.88#+0:00#DEBUG####Offline#1429708585072026#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.SessionLogger:debug########447###ML_SCRIPT Enter handle_UploadData: remoteID=127d6d6a-e9e6-11e4-8000-d25ebbb51773#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072027#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.SessionLogger:info########447###Starting delta refresh#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072028#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.SessionLogger:info########447###Store version: 0#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072029#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.SessionLogger:info########447###Service root: http://xxxx.xxx.xx.com:80/com.mycompany.app#
#2.0#2015-04-23 07:25:10.88#+0:00#DEBUG####Offline#1429708585072030#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.odata.offline.smp.MLODataSMPConfig:getApplications########447###getApplications()#
#2.0#2015-04-23 07:25:10.88#+0:00#DEBUG####Offline#1429708585072031#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.odata.offline.smp.MLODataSMPConfig:getApplications########447###...getApplications()#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708585072032#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.SessionLogger:info########447###Sending HTTP GET "http://xxxx.xxx.xx.com:80/com.mycompany.app/$metadata"#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429708722954016#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########420###<47> Network protocol version check completed#
#2.0#2015-04-23 07:25:10.88#+0:00#INFO####Offline#1429709254451016#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########430###<47> Request from "UL 16.5.1413" for: remote ID: 127d6d6a-e9e6-11e4-8000-d25ebbb51773, user name: ml_odata_user_01, version: ODATA_TO_ML#
#2.0#2015-04-23 07:25:10.281#+0:00#INFO####Offline#1429773910281000#127d6d6b-e9e6-11e4-8000-d25ebbb51773##com.sap.mobile.platform.server.mobilink.NativeLogger:doMessageLogged########409###<47> Request from "UL 16.5.1413"#
Request your help on this

A2a file MDM 5.5 SP06

HI,
Please guide me where i can download sample a2a file for MDM 5.5 SP06
Regards
Subhash

Hi,
you can find DEMO repository here:
SAP NetWeaver - Demo Model;jsessionid=%28J2EE3414900%29ID1355369050DB11065073906383630678End#section21
Hope this help you.
Best Regards,
Vito

Right versions of Java for Internet Explorer 8,8,19 versions for BO 4.1

Hi,
Can any body guide me on the right version of Java(Internet Explorer version 8,9,10) for BI Launch Pad 4.1 SP6?

Hi,
If there is enough time to validate SP06 against MS Windows 10, and if the enterprise market demands it (i.e. our maintained customer-base) then it would certainly be considered.
However, Win 10 isn't out yet, and if SP06 comes out in only few months.. then the timelines aren't favourable.
Realistically, we don't anticipate enterprise organisations to be adopting Win 10 as soon as it comes out.. It's a fringe requirement. But that said, our SPs are designed to offer additional PAM support, so let's see.
Regards,
H

BO Explorer Accelerated Version for BWA with BO Enterprise 4.0.2 ????

Dear all,
we are currently running a complete BO Enterprise 4.0.2 landscape, including BO Explorer 4 (non accelerated version).
What we would like to add in addition(!), is an installation of BO Explorer (accelerated version of a dedicated blade) which directly accesses the data in our BWA, but which makes use of the already existing BOE landscape (including CMS, SAP authentication, etc.)
I checked all documentation on the service.sap.com, etc. and I have to say that I'm a little bit lost about the versions and the naming.
- There was once a version which was called SAP BO Explorer (blade) 2.0 and in the installation/master guide there was a dedicated part how to connect the new BO Explorer to the BO Enterprise and how to establish a connection between the BO Explorer and the BWA (so exactly what we from my general understanding need to do).
Unfortunately this guide was always based on the BOE XI3.2 version and NOT on the current 4.0.2 version
- The successor of SAP BO Explorer (blade) 2.0 is now called SBOP EXPLORER PACKAGE 4.0 (as I can read in service.sap.com), but when I check /instguides for "explorer", I can again read the following:
SAP BusinessObjects Explorer, accelerated version comprises the following software packages and components:
SAP BusinessObjects Explorer (blade) 2.0
SAP NetWeaver BW Accelerator 7.2
SAP BusinessObjects Accelerator (blade) 1.0
SAP BusinessObjects Data Services
SAP BusinessObjects Accelerator Index Designer
SAP NetWeaver Business Warehouse (optional)
And now I'm lost. Does it mean that the latest installable blade edition is still SAP BusinessObjects Explorer (blade) 2.0, even when we are running BO Enterprise 4.0.2 ???? If so, is there any major difference between the XI3.2 version from the (blade) 2.0 installation/master guide and version 4.0.2 (except that I do not need the SAP integration stuff anymore)?! Is there an installation guide for BO Enterprise 4.0.2?
And last but not least, which version is the version which I can find under /swdc
SBOP EXPLORER ACCELERATED VERSION -> SBOP EXPLORER PACKAGE -> SBOP EXPLORER PACKAGE 4.0
It seems to me that this is the NON ACCELERATED version - so not the blade edition which is going directly to the BWA...
OR
Having the new BO Explorer Version 4 available does not at all require a special blade installation anymore?!? I simply need
- BWA720 and need to perform the following steps:
To connect SAP BusinessObjects Explorer with a designated SAP NetWeaver BW Accelerator via the CMC administration page:
1. Stop the Explorer servers.
2. Logon to the BusinessObjects Enterprise CMC.
3. Navigate to Manage > Applications.
4. Right-click Explorer and click Properties.
5. Within Advanced Configuration: type the host and port values of the designated BWA.
For example:
com.businessobjects.datadiscovery.dataprovider.trex.host=<mybwaserver>
com.businessobjects.datadiscovery.dataprovider.trex.port=3<TREX_instance_number>16
Who can help me with this?
Thanks,
Andreas
Edited by: Andreas Freistedt on Jan 28, 2012 10:07 PM

Dear Anbu,
long time ago since I did the initial configuration.
When I remember right, there was an additional parameter in one of the *ini files on the Trex Server, but when I searched I was not able to find any additional parameter - so I guess there is none.
One thing that I remember is, that we had to use the IP-adress on the BO server configuration instead the server name, as otherwiese the BO server was not able to reach the BWA (but his might be due to our internal configuration).
Regards,
Andreas

Installation prerequisites for MDM 5.5

Hi all,
Is it possible to download MDM 5.5 sp06?
If yes,what are the prerequisites for that?
What configuration should maintained in my desktop?
how much space will it take in my computer memory?
Regards,
Vijay

Hi Vijaybabu,
The hardware requirements for installing the MDM.
Hardware Requirements -- See MDM 5.5 - Sizing Guide at service.sap.com/installMDM
Operating Systems -- See Product Availability Matrix (PAM) on SAP Service Marketplace at
service.sap.com/pam -> SAP NETWEAVER-> SAP MDM
Minimum Database -- Versions
MaxDB 7.7.01
IBM DB2 8.2
IBM DB2 for z/OS 8 in New Function Mode
IBM DB2 for i5/OS V5R4
Oracle 9i: 9.2.0.7
Oracle 10g: 10.2
MS SQL 8 SP3
Software to be installed along with the SAP MDM.
Client software for the DBMS you want to use.
MS XML Parser 4.0 with SP 2 or higher (available for free download from Microsoft)
MS MDAC u2013 Version 2.7 or higher (available for free download from Microsoft).
MS Access® (Office 2000, Office XP, Office 2003) and/or MS Excel® (Office 2000, Office XP, Office 2003)
Adobe Acrobat® Reader Version 4.0 or higher
Adobe Acrobat® Standard or Professional Version 4.0 or higher
Adobe Photoshop® version CS2
Adobe InDesign® versions CS2 or CS3
Oracle Provider for OLEDB
MS Visio® 2003 standard
Hope this inforamtion helps you.
Cheers
Santosh.

MS Visio 2007 for MDM Workflow

Hi,
We are working on MDM SP06 patch 2.
Just want to know whether MS Visio 2007 version is compatible for MDM workflow since only 2003 products work fine with MDM .Has anyone tried this out?
Please suggest
Regards
Nisha

Hi,
Just now went back to Master Guide of MDM SP06 it says That MDM doesnt support Microsoft 2007.
What version of MDM are u on?
Regards
Nisha

MDM 5.5 SP06 Support on SRM 7.0

Hi
We are using SRM 3.0 (EBP 4.0) with requisite catalog to maintain the catalog
We are going to upgrade SRM to SRM 7.0 and would like to use our existing MDM 5.5 SP06 lanscape (It is being currently used to maintain our company Product Master)
Can someone tell me that the latest SRM version 7.0 can use existing MDM Landscape without any issue
We have very small size of Catalog which we are using with SRM 3.0
Thanks in advance
Thanks
Deelip

Hey Deepali,
I informed you about best practice and SAP's recommendations.
My thoughts on WHY SAP RECOMMENDS SEPARATE LANDSCAPE FOR SRM-MDM CATALOG are as follows:
1. Version strategy of SRM-MDM Catalog is different from MDM Product version strategy. And from my experience what i have seen, compatible package of SRM-MDM Catalog is released with in 1-2 month of release of normal MDM. You may face a situation that a new version of MDM is available but SRM-MDM Catalog version compatible to this MDM version is not released..
For example, As of now, MDM 7.1 SP05 is the latest version, but latest version SRM-MDM Catalog version is based on MDM 7.1 SP04 and as of now MDM 7.1 SP05 is not yet supported for SRM MDM Catalog.
2. if You face any compatibility problem or issue in SRM-MDM Catalog and have to upgrade MDM patch to fix it, then it will disturb your other master data object processes too.
3. SRM-MDM Catalog UI should be compatible to MDM Server Version and is based on a specific MDM Release. You may face a situation that SRM-MDM Catalog package not exactly matching your MDM Server version.
Please check the version mapping note for SRM-MDM Catalog 2.0 and MDM 5.5. this will explain this point in a better way..
SAP Note 1083126 - Version mapping SRM-MDM Catalog 2.0 to SAP MDM 5.5
But, on the other side, i don't see any technical restriction in using SRM-MDM Catalog with other Master data objects (* if you can get SRM-MDM Catalog package matching to your MDM server version)
So, you can also use same MDM server in above case.
Hope this will clearify things more...Revert if any further question...
Best Regards,
Shiv

XI Business content for MDM - Syntax error in IDOC adapter

Hi mates,
I'm trying out the Master Data Harmonization scenario for Vendor data with R/3 as the client system. I'm using SAP delivered XI Business content for MDM. The mapping program is generating ADRMAS and CREMAS IDocs but the IDOC adapter reports that there is a syntax error in ADRMAS IDOC. Find below the details.
<i><SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Segment 'E1BPAD1VL', segmentnumber '000001' not correct in structure ADRMAS02</SAP:Stack>
<SAP:Retry>M</SAP:Retry></i>
Generated ADRMAS IDOC is
<i> <?xml version="1.0" encoding="utf 8" ?>
<ADRMAS02>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1" />
<E1ADRMAS>
<OBJ_TYPE>LFA1</OBJ_TYPE>
<OBJ_ID>0000500140</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Swift Transportation</NAME>
<COUNTRY>US</COUNTRY>
<COUNTRYISO>US</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<SORT1>SWIFT TRANSPORTATION</SORT1>
<TIME_ZONE>CST</TIME_ZONE>
<E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
</E1BPAD1VL1>
</E1BPAD1VL>
</E1ADRMAS>
</IDOC>
</ADRMAS02></i>
Strangely, the control record is blank. I looked at the XSLT program, it is coded that way. I do not understand the reason. Is the error pointing to the control record?
Look at the code sample from XSLT mapping program
<xsl:for-each select="IDOC/*/E1ADRMAS">
     <IDOC BEGIN="1">
     
          <EDI_DC40 SEGMENT="1"/>
          <xsl:apply-templates select="."/>
     </IDOC>
</xsl:for-each>
How can an IDOC w/o control record be posted?
Did anyone come across this error? Whats wrong/missing?
I appreciate ur inputs.
thx in adv
praveen

Moorthy,
I tried reloading the IDOC metadata from IDX2. Still I get the same error.
Regd, IDOC w/o control record, can u elaborate on "dynamic value while posting IDOCs". From where, XI message SOAP header with Business System replaced by corresponding logical system names?
Thanks
Praveen

I am attempting to upgrade from Adobe Premier Elements 9 to Adobe Premier Elements 13 after using 13's trial version for a few weeks. I am unable to find where and how to do this without losing the project I have been working on. Please help?

I am attempting to upgrade from Adobe Premier Elements 9 to Adobe Premier Elements 13 after using 13's trial version for a few weeks. I am unable to find where and how to do this without losing the project I have been working on. Please help?

Vere Clarke
Premiere Elements 9.0/9.0.1 and Premiere Elements 13 are standalone products.
So, you can have both on the same computer, but only open one for your work.
The classical recommendation is to finish a project in the version in which it was created since there
is no guarantee that a project from an earlier version will open in the later version. Probably will, but
no guarantees. And, when you do explore this, do it from a copy of the earlier version project. Once you
take the earlier version project into a later version one, you cannot go back to edit the later version edited
project in the earlier version program.
If you have both versions (9 and 13) on the same computer and you have not moved, deleted, renamed any of the version 9's files/folders,
right click the saved closed Premiere Elements 9.0/9.0.1 project file, select Open With, and then Adobe Premiere Elements 13.
(Your 9.0/9.0.1 saved closed project file should be found in Libraries/Documents/Adobe/Premiere Elements/9.0.)
Please review and consider. If any questions or need clarification, please do not hesitate to let me know.
Thank you.
ATR

I bought the Mac version of Premiere Elements, can I get the Windows version for free or cheap with my serial number?

I bought the Mac version of Premiere Elements, can I get the Windows version for free or cheap with my serial number? I'm about to migrate back to PC soon and I'd love to not have to buy the program again since I just bought it. Under my order history though it only shows it for Mac so I wanted to make sure.

ihavea4
The boxed packaging is not sold by Adobe direct. If you want to explore that type of purchase which offers the perk of a Windows and a Mac installation disc, you need to purchase from an authorized reseller who is not going to offer you "upgraded pricing". The seller would be its own entity with its own pricing and own return/refund policy. Sometimes the authorized reseller price may be less than the Adobe"upgraded pricing".
Did you purchase your Premiere Elements 13 Mac from Adobe direct and are within 30 days of purchase? If so, you can contact Adobe Chat Orders to ask for return/refund. And, then you can explore the authorized resellers for pricing and availability of the box packaging. Maybe check out the pricing all around before making any final decisions.
Please review and consider.
Thank you.
ATR

Javascript in web.show_doc not works in explorer version 6

Hi ,
I've requirements to open form B from form A using URL not call_form (the config parameters are not the same), but when I open form B using web.show_document I end up having the new form opened in a oversized web browser which also shows standard button and address bar.
To avoid that I tried using the examples I found on OTN, see below:
I try to run this examples found in OTN but they not work in Explorer version 6.
1) WHEN_BUTTON_PRESSED trigger contains:
begin
WEB.SHOW_DOCUMENT ('javascript:window.open("http://www.google.com","","fullscreen=no,titlebar=no,location=no,toolbar=no,menubar=no,status=no,resizable=yes");self.close()','_blank');
end;
2)POST_FORM trigger contains
web.show_document('Javascript:window.close()','_self');
Both do nothing and when I exit the form I get an empty black window, this is not acceptable in a production environment.
The POST-FORM trigger worked well with the pervious release of window explorer.
Thanks for your help

Hi Frank,
Many thanks,
the when-Button-pressed trigger of my Exit button contains the following code:
DECLARE
url_txt varchar2(1000);
BEGIN url_txt := 'http://servername/closing_window.htm';
WEB.SHOW_DOCUMENT(url_txt,'_self');
END;
The closing_window.htm is a simple page:
<html>
<HEAD>
<body onLoad="window.close();">
</html>
</HEAD>
Data in my form are already committed when I exit it.
How to commit is maybe an issue, in fact if I commit before calling the web.show_document the browser is not closed and a black window appears.
Thanks

Explorer Version for MDM 5.5 SP06

Similar Messages

Maybe you are looking for