REP-56098: wrong system name
i don't know why this error appears when any users request a specific report, if a users request another reports it's executed ok. what can i do , and where i can find a help about errors in reports server�
What is the report name?
How you are calling the report? (meaning from where u r calling this report)
Ansqwers to these questions would help to understand the problem clearly
Similar Messages
-
Reg: Table name where logical system name will store in R/3 and CRM..
Hi
We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
RegardsHi,
In CRM: look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
Hope this helps.
Thanks,
Karuna. -
Custom Prompt sometimes shows wrong Machine Name
I set up a custom command prompt in my .bash_profile to show the machine name. Sometimes it works, sometimes it doesn't.
The command:
export PS1='\[\033[0;32m\]\h \W\$ \[\033[0m\]'
Sometimes it shows
lud610wxp-sales rfreedman$
Sometimes it shows
qaimac rfreedman$
This is correct
I see the same behavior on other systems although the wrong machine name is different.If you're on a network, the hostname for the prompt is set by performing a reverse DNS lookup of your IP address. Often an old entry will be listed in the reverse DNS table before the current one, and its name will be used instead of the correct one. You can manually edit /etc/hostconfig if this bothers you, but it generally does not affect anything because forward DNS queries will be correct.
-
Client no in SAP Business System name.
Hello All,
I am currently working on naming for the SAP PI objects.
In my previous SAP PI implementations I used naming like SIDCLNTNO ( f.e. DPECLNT110 ) and SAP Recommends that as well. However we faced problem while pointing the different client to SAP PI sometimes in quality. For example my business system name is XXXCLNT110 in QA. But as they want to do some performance testing they wanted to point it to 900 client. At that time technically we can point it but logically it becomes wrong as scenario is still refering to 110 client (XXXCLNT110 ).
So in my new project I am thinking of keeping business system name client independent. i.e. SAPERP_DEV. Let me know your views regarding the same ?
Thanks & Regards,
Dijesh Tanna.Hi Dijesh ,
But as they want to do some performance testing they wanted to point it to 900 client. At that time technically we can point it but logically it becomes wrong as scenario is still refering to 110 client (XXXCLNT110 ).
---> for me "performance checking " is related to "technical settings" only !!!
It's the client No. which depicts the purpose of system like test ,Dev, Sandbox,....not other way !!! so logically also "SAPERP_DEV" is not correct ...In this fashion you will be tight coupling the business system name with the business context !!! and the solution will not be scalable !!
Consider a case where new ERP systems coming into the landscape
will you name it SAPERP_DEV1...SAPERP_DEV2.......
Hope my sincere views you would find useful !!
Regards , -
Hi Friends,
I want to print logical system id and system name.
I am trying with sy-name , no result.
ThanksHi,
this is wrong forum, ask this into ABAP forum.
The system name you can fetch from view V_TBDLS, and for system id try SY-ID.
Regards,
Sarvesh -
Probem after changing the system name of EP 6.0 SP9
Hi,
I have changed the system name of the EP 6.0 SP9 system and restarted it and after I again shifted back to the old system name and restarted the system.
Now the j2ee engine is not coming up ...
I am placing the developer trace.
Pl. suggest what might have went wrong.
Thanks & Regards
Mrutyunjay
trc file: "E:\usr\sap\D01\JC00\work\dev_jcontrol", trc level: 1, release: "640"
node name : jcontrol
pid : 5552
system name : D01
system nr. : 00
started at : Mon Dec 19 11:14:46 2005
arguments :
arg[00] : E:\usr\sap\D01\JC00\j2ee\os_libs\jcontrol.exe
arg[01] : pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
JStartupReadInstanceProperties: read instance properties [E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties;E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties]
-> ms host : portald
-> ms port : 3601
-> OS libs : E:\usr\sap\D01\JC00\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> files [01] : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : portald
-> ms port : 3601
-> os libs : E:\usr\sap\D01\JC00\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9391400 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9391450 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID9391400 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] ID9391450 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] sdm : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
[Thr 2144] Mon Dec 19 11:14:46 2005
[Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 2144] [Node: bootstrap] java home is set by profile parameter
Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [bootstrap]
-> node name : bootstrap
-> node type : bootstrap
-> java path : c:\j2sdk1.4.2_08
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 128M
-> root path : E:\usr\sap\D01\JC00\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0093914
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_bootstrap
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=bootstrap
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] Mon Dec 19 11:14:52 2005
[Thr 2144] JControlExecuteBootstrap: read instance values after global bootstrap
JStartupReadInstanceProperties: read instance properties [E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties;E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties]
-> ms host : portald
-> ms port : 3601
-> OS libs : E:\usr\sap\D01\JC00\j2ee\os_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
[Thr 2144] JControlExecuteBootstrap: enumerate the nodes after global bootstrap
Used property files
-> files [00] : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> files [01] : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : portald
-> ms port : 3601
-> os libs : E:\usr\sap\D01\JC00\j2ee\os_libs
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
-> [00] bootstrap : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9391400 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9391450 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID9391400 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [01] ID9391450 : E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> [02] sdm : E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
[Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9391400]
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] [Node: dispatcher bootstrap] java home is set by profile parameter
Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [bootstrap_ID9391400]
-> node name : dispatcher bootstrap
-> node type : bootstrap
-> java path : c:\j2sdk1.4.2_08
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 170M
-> root path : E:\usr\sap\D01\JC00\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009391400
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_bootstrap
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=bootstrap_ID9391400
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap_ID9391400.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap_ID9391400.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap_ID9391400
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] Mon Dec 19 11:14:58 2005
[Thr 2144] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID9391450]
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] [Node: server0 bootstrap] java home is set by profile parameter
Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [bootstrap_ID9391450]
-> node name : server0 bootstrap
-> node type : bootstrap
-> java path : c:\j2sdk1.4.2_08
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 1024M
-> root path : E:\usr\sap\D01\JC00\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID009391450
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_bootstrap
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=bootstrap_ID9391450
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_bootstrap_ID9391450.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_bootstrap_ID9391450.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_bootstrap_ID9391450
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] Mon Dec 19 11:15:05 2005
[Thr 2144] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 1424] JControlRequestFunc: Thread 1424 started as listener thread for np messages.
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] [Node: dispatcher] java home is set by profile parameter
Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID9391400]
-> node name : dispatcher
-> node type : dispatcher
-> java path : c:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1 -XX:NewSize=28m -XX:MaxNewSize=28m -XX:+DisableExplicitGC -Drdbms.driverLocation=D:/oracle/D01/920/jdbc/lib/classes12.jar -Dsys.global.dir=E:/usr/sap/D01/SYS/global/
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 170M
-> root path : E:\usr\sap\D01\JC00\j2ee\cluster\dispatcher
-> class path : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 60000
-> shutdown timeout: 120000
[Thr 2144] INFO: Invalid property value [JLaunchParameters/]
[Thr 2144] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx512M [jstartxx.c 2282]
[Thr 2144] [Node: server0] java home is set by profile parameter
Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [ID9391450]
-> node name : server0
-> node type : server
-> java path : c:\j2sdk1.4.2_08
-> java parameters : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:PrintGCDetails -XX:PrintGCTimeStamps -XX:UseParNewGC -XX:MaxNewSize=85M -XX:NewSize=85M -XX:DisableExplicitGC -XX:MaxPermSize=192M -XX:PermSize=192M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Drdbms.driverLocation=D:/oracle/D01/920/jdbc/lib/classes12.jar -Dsys.global.dir=E:/usr/sap/D01/SYS/global/
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> init heap size : 512M
-> root path : E:\usr\sap\D01\JC00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class : com.sap.engine.boot.Start
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout: 120000
[Thr 2144] [Node: SDM] java home is set by profile parameter
Java Home: c:\j2sdk1.4.2_08
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> java path : c:\j2sdk1.4.2_08
-> java parameters :
-> java vm version : 1.4.2_08-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 128M
-> root path : E:\usr\sap\D01\JC00\SDM\program
-> class path : E:\usr\sap\D01\JC00\SDM\program\bin\SDM.jar
-> OS libs path : E:\usr\sap\D01\JC00\j2ee\os_libs
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : E:\usr\sap\D01\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=E:\usr\sap/D01/JC00/SDM/program
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout: 120000
[Thr 2144] JControlMSConnect: attached to message server (portald/3601)
[Thr 892] JControlMSMessageFunc: Thread 892 started as listener thread for ms messages.
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_dispatcher
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391400
-> arg[05] = -nodeId=0
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_dispatcher.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process dispatcher started (PID:1432)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:1436)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_sdm
-> arg[03] = -file=E:\usr\sap\D01\JC00\SDM\program\config\sdm_jstartup.properties
-> arg[04] = -nodeName=sdm
-> arg[05] = -nodeId=2
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_sdm.out
-> arg[08] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_sdm.out
-> arg[09] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process SDM started (PID:1452)
[Thr 892] Mon Dec 19 11:15:35 2005
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 892] JControlMSMessageFunc: receive command:6, argument:1213679940 from Message Server
[Thr 2144] Mon Dec 19 11:16:00 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:1436) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (1)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:4092)
[Thr 2144] Mon Dec 19 11:16:40 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:4092) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (2)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:5456)
[Thr 2144] Mon Dec 19 11:17:25 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:5456) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (3)
JStartupStartJLaunch: program = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = E:\usr\sap\D01\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> arg[02] = -DSAPINFO=D01_00_server
-> arg[03] = -file=E:\usr\sap\D01\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=ID9391450
-> arg[05] = -nodeId=1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_5552
-> arg[07] = -jvmOutFile=E:\usr\sap\D01\JC00\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\D01\JC00\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\D01\JC00\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\D01\SYS\profile\D01_JC00_portald
-> lib path = PATH=c:\j2sdk1.4.2_08\jre\bin\server;c:\j2sdk1.4.2_08\jre\bin;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
-> exe path = PATH=c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\JC00\j2ee\os_libs;D:\oracle\D01\920\jre\1.4.2\bin\client;D:\oracle\D01\920\jre\1.4.2\bin;D:\oracle\D01\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\j2sdk1.4.2_08\bin;E:\usr\sap\D01\SCS01\exe;E:\usr\sap\D01\JC00\exe;E:\usr\sap\D01\SYS\exe\run
[Thr 2144] JControlICheckProcessList: process server0 started (PID:4948)
[Thr 2144] Mon Dec 19 11:18:10 2005
[Thr 2144] JControlICheckProcessList: process server0 (pid:4948) died (RUN-FLAG)
[Thr 2144] JControlIResetProcess: reset process server0
[Thr 2144] JControlIResetProcess: [server0] not running -> increase error count (4)Dear Ashutosh,
Thanks for guiding us to correct location.
What we identified is we connected portal to the LDAP
of EP 5.0 while migrating the content.After migration we
have formatted the 5.0 system.
Now that portal is connected to that LDAP which is
not existing the problem is coming.
Is there any way through CONFIGURATION tool I can remove
that connectivity to LDAP?
I am trying to configure LDAP again on the same server
but before to that if some one can hint me how to
remove the LDAP configuration from the Portal I would
be very much thankful..
regards
Mrutyunjay -
Dear Support Team,
Every time i tried to logon Icloud its gives me wrong user name or password and at the end it show me error " This Apple ID is valid but is not an ICloud Account" then how can i use one account for same Apple ID and ICloud?
ThanksIt is not possible to create a new iCloud account using a Windows machine. You must create the account using a Mac (10.7.5 or more) or an IOS device (iPhone etc). Once that is done you can sign into and use the account on your Windows machine.
-
Logical system name for acknowledgement in BPM
Hi,
I have a szenario:
IDOC --> BPM --> MAIL
Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
"Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
What can I do?
Possible Solution 1:
I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
Possible Solution 2:
I can enter an existing logical system name in the "adapter specific attributes".
BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
Is Solution 1) a common way?
Thanx
Regards
Wolfgang HummelHi,
there are many ways:
some for aleaud are described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
>>>>Is Solution 1) a common way?
no this is not good a good idea
BTW
you can also supress aleaud raport IDX_NOALE
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a> -
Logical System Name Not appearing in the Business System
Hi,
Initially we had created a Technical system with Client 700 without a "Logical System Name" in SLD. hence the 'logical system name' in 'business system' was also Blank.
Now, since we are implementing the IDOC to file scenario; we need to maintain the "Logical System Name" in the client and which in turn should reflect in our Business System in SLD.
Though we maintained the Logical System Name in the Technical System --> Client --> Logical System Name; we are unable to see the same(Logical System Name) in Business System ('Integration' tab)
Please also note that Business System is of the ROLE: Integration server.
When we go to business system in SLD ---Integrtaion tab ---Logical System Name -- is still blank.
Can anyone please help us to update the 'Logical system name' in Business System in SLD?
Regards,
RehanHi Sunil,
I followed your link till
Bussiness System -> select your bussiness System -> in Below pane u will find Details of your bussiness system ->amongs the various tabs available select Integration Tab->U will See option for technical system beside that u will see option for change ->click this ->u will be taken to Logical system ->there u define u r logical syatem name and then save the entries.
When I clicked the option chnage ---> "Change Associated Technical System" appeared, It didn't take me to Logical system.
But in turn I clicked hyperlink corresponding to Technical systems, it took me to technical system --> clients tab --I have entered the Logical system name.
When I go back to Business system again its not showing the Logical system name in Integration tab.
regards,
rehan -
IDOC sender: Error in Logical system name?
Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
SowkhyaHi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya -
Logical system name in business system (SLD)
Hi,
While creating business system in SLD what should give for the logical system name?
Should the logical system name exists in ABAP stack or the new one?
Thanks.Hi,
If you are creating the BS for SAP R/3 in SLD means we have to give the LS name which we had in SAP R/3( goto SALE and take the LS from there)
Goto Assign LS-----take the client which you are using for SAP R/3 and take the LS name assigned to that Client
Regards
Seshagiri -
Logical system name to be updated while client copy--URGENT HELP REQUIRED
Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe -
Sun would like your help with the "System Name Already In Use" error
A couple of users have reported getting an erroneous "System Name Already in Use" error when re-registering a system after a fresh Solaris re-install. We'd like your help in tracking down this problem.
The scenario is this:
* Install Solaris 10 and register with updatemanager,
* Wipe out the installation and re-install Solaris.
* re-register with updatemanager.
The system erroneously reports that the system name is already in use. It is supposed to detect a duplicate registration of the same system.
We have not been able to reproduce this error in our lab.
If this has happened to you, would you let us know at [email protected]?
Here are the things that we would like to ask of you:
* If you run "updatemanager -debug" if will create a log file /tmp/basicreg<timestamp>.log.
* Details on the exact hardware you have (make/model/configuration).
* Details on the steps you took to get to the bad state. REALLY detailed!
Thanks!
Based on what we know now, we believe you can work around the issue by either:
* Changing the host name and re-registering.
* Creating a different user account and registering the host to that account.
Some previously-posted workarounds are known NOT to work:
* Wait 24 hours and try again.
* Do some "ccr" incantations and try again.Hi,
Can you drop me an email as i am a sun employee and i will be able to check if the swup frontline team have received any support cases on this issue and then we can work with you directly to resolve the issue.
Scott Wallace -
I tried to share a photo using e-mail and when i set up my gmail account I typed in the wrong user name and password.
Now I can't send a photo because i get an error message saying the user name and password do not match.
How do i save a new gmail user name and password??iPhoto Menu ->
Preferences ->
Accounts ->
Delete and recreate your email settings.
Alternatively, use Apple's Mail for the job. It has Templates too - and more of them. -
Logical System and Logical System Name
Hi,
I would like to create the following and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
Creating a port(I suppose I need to do this on the R3. What are the steps involved)
Create a Partner ProfileHi Sonia,
For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
just go through the following steps and Configure ALE :-
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Ashwin M
Reward If helpful
Maybe you are looking for
-
Using one PC for two different iphone
My wife and I got the Iphone3GS recently. But, we just shared a PC at home. Are there any method to syn our materials on the same PC with different account?
-
Status tab problem in PO header
Hi Gurus, I am working in R3 version 4.6. We create a PO with condition type NAVS (Non-deduct.Input Tax) and tax indicator N3. The system shows in tab status the net value (without tax) referred to u201Corderedu201D field and the same for u201Cstill
-
Disable the email client selection prompt for forms
Hello, I am wondering if you might help me. When hitting the "email to" button in a pdf form, by default the select email client window pops up. I have been searching in vain (sofar) to prevent this window from appearing in the first place (at first
-
Help with importing .pdf's - flattening
Hello folks, I just upgraded to Win7 and did a complete reinstall. I have CS2 that is working fine, however, when I place a .pdf, it automatically flattens. Many customers send .pdf's that I place into a template, however, sometimes flattening will
-
Hi plz help I have made presentation in flash cs4. I have one main file Index & loading rest all the files through LoadMovie. I want to convert my presentation into AVI for video but when i export it in avi so it converts in AVI but its not taking th