SAP BW Support pack

BW Experts,
Can anyone tell me what is the recent most SAP BW Support pack? My client is on support pack 19, and they want to upgrade it with the version previous to the most recent one.
Thanks
Ashwin

hi Ashwin,
yes, the note mention the impact.
for steps please find here
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/ff9036e1e4b603e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a7/a7a932845c11d2b421006094b9ea64/frameset.htm
normally this task is done by basis.
hope this helps.
783253
Symptom
Support Package 23 for BW Release 3.1 Content
Other terms
SAPBWNEWS, Support Packages for 3.1 Content, BW 3.10, BW Patches
Solution
This note contains the SAPBWNews for Support Package 23 for BW Release 3.1 Content. It contains a list of all notes that describe the corrections and enhancements in Support Package 23 (SAPKW31023). This note will be updated as soon as further notes are added.
The information is divided into the following areas:
Manual actions that may be required:
Factors you must take into account when you import the Support Package.
Errors that may occur after you import the Support Package
General information:
This Support Package corrects the following errors.
Enhancements delivered with this Support Package
Note 539867 contains further important and necessary information about importing Support Packages for BW 3.1 Content, and this information does not refer to any particular Support Package.
For example, Note 539867 contains the necessary patch level for the basis system and other essential information about importing the Support Packages, as well as information about problems that originate in other systems but may also appear in BW.
Note 539867 also contains the planned Support Package release dates. The note is regularly updated to include the most current information (the last update was on NOV/08/2004).
Therefore, we strongly recommend that you refer to this note before you import the Support Package. To subscribe to the note, refer to the instructions contained in Note 487366.
Support Package 23 for BW 3.1 Content corresponds to the technological level of Support Package 29 for BW 3.0B (SAPBWNews 783251).
Factors you must take into account when you import the Support Package:
After you import the Support Package, remember to restart the application or to use $sync to clear the temporary storage.
If filter value selection takes a long time, refer to Note 912773.
Errors that may occur after you import the Support Package:
Querys on MultiCubes in read mode A. For more information, see Note 896066.
The query shows more rows. For more information, see Note 901097.
The update from the PSA using the 'Update' indicator in the scheduler no longer works for normal master data that is not flexible and text DataSources that were updated using 'PSA only' - Reason: The problem is caused by the correction that is contained in Note 889160, Note 905105 corrects the problem.
A syntax error occurs in class CL_RSMD_CONVERSION, method DROP_TMPTABLES. For more information, see Note 905168.
F4 and authorization: SQL error in SAPLRSDM_F4. For more information, see Note 907337.
This Support Package corrects the following errors:
Enhancements that are delivered with this Support Package:
Refer also to the Documentation Enhancements on the SAP Service Marketplace (http://service.sap.com/bi --> Documentation --> SAP BW 3.x Documentation Enhancements), which describe the enhancements that are delivered with this Support Package.
Enhancements in the area of OLAP technology:
General performance improvements for OLAP. For more information, see Note 825396.
The runtime in the REMOVE_SELDR_0INFOPROV_NEW form is very long. For more information, see Note 887801.
Unnecessary reading of partprovider. For more information, see Note 885733.
The performance in from SAPLRRK0; loc_rechnen has been improved. For more information, see Note 884482.
Problems occur with hierarchy selections in MultiProviders. For more information, see Note 879290.
Query runtime if there are several nested formulas. For more information, see Note 872904.
Information regarding the system component validation:
The Support Package was validated at a specific level of the system components that are available at this time. We therefore recommend that, in parallel to the BW Support Package upgrade, you adjust the system environment to the version of the individual components.
You can find more information in the SAP Support Portal at http://service.sap.com/swdc:
-> Additional Download Information -> SAP Support Package Stacks -> SP Stack Information and Download -> SP Stack SAP BW 3.1 Content

Similar Messages

  • How to flush Delta queue for future SAP upgrades/support pack !

    Guys,
    I'm making documentation regards to " How to flush Delta Queues" in case SAP wanted to upgrade the system or any support pack. Please anyone let me know the effective way to flush out the delta queue in step by step methods. I really appreciate your help.

    1.  Run V3 for associated application(s), this will load any potential delta data to the delta queues.
    2.  Run the delta load for each datasource twice.  The second load will clear the delta repeat data so that there should not be any more data in the delta queues defined with the format of the current datasources.
    Does this help?

  • SAP Basis - Support Packs

    Hi All,
    Can you please guide me how can i revert a Support Packs which is implemented recently.
    Thanks in advance.
    Regards
    Shiv

    Hi Siva,
    >My question was when a SNOTE can be reverted without any backup restore, why cant we revert a >support pack which is a combination of SNOTES?
    Because, that is the way it has been designed by SAP. Sorry, I have no better answer.
    But my opinion is that it must  be considered much to complicated and risky by SAP to try to implement the reversal of Support Packages.
    So the message is : always make a full backup before applying Support Packages !
    Regards,
    Olivier

  • SAP HR Support Pack & Legal Packages

    Dear gurus,
    We are facing some troubles in our implementation Project.
    We create the DEV System, apply SP at client 000, create the dev&cust client 200 and then start with configuration tasks. During the configuration & development phase was applied a new SP Stack at client 000 as SAP recommends. Up to this point everything was good.
    When we has to deliver the productive system for transport the cust & devel, we install the system, apply both SP Stack that was already installed at Dev system at client 000, create the Productive client 400 and import all the transport requests.
    The problem that we found after that was that some data at the productive system in client 400 (i.e. T512Z table entries)  does not exist at the cust&devel client 200 in the development system. Making some analysis we determine that the second SP Stack application at the devel system, creates entires for those tables only in client 000 coz they are client-dependent tables but no at the 200.
    Does anybody knows if there are some post SP Stack application tasks that carry out those entries to the others clients?
    Or anybody can tell me if we do some wrong with the SP Stack Application?
    I hope u can help me with this.
    Thanx in advance,
    regards
    MJ

    No comments

  • Error in JSPM Support Pack update

    Hi,
    i am in the process of doing java support packs form level 9 to 14.
    I am doing 3 at a time
    After the sap-jee support pack got deployed the server0 for j2ee is not starting.
    Pls hlep
    The following is the log of disp_server0
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 7296
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:30:40 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 4660] Tue Jun 17 16:30:40 2008
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 4660] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 4660] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 4660] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 6916] JLaunchRequestFunc: Thread 6916 started as listener thread for np messages.
    [Thr 4836] WaitSyncSemThread: Thread 4836 started as semaphore monitor thread.
    [Thr 4660] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 4660] CPIC (version=700.2006.09.13)
    [Thr 4660] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 4660] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 4660] JLaunchISetDebugMode: set debug mode [no]
    [Thr 6772] JLaunchIStartFunc: Thread 6772 started as Java VM thread.
    [Thr 6772] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=7296
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 6772] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 4752] Tue Jun 17 16:30:41 2008
    [Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 4752] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 4752] JLaunchISetClusterId: set cluster id 13786450
    [Thr 4752] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 4752] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 7688] Tue Jun 17 16:30:52 2008
    [Thr 7688] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 7688] ***********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.*
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
    for additional information and trouble shooting.*
    [Thr 7688] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 4560
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:30:55 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 5300] Tue Jun 17 16:30:55 2008
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 5300] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 5300] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5300] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 7140] JLaunchRequestFunc: Thread 7140 started as listener thread for np messages.
    [Thr 6892] WaitSyncSemThread: Thread 6892 started as semaphore monitor thread.
    [Thr 5300] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5300] CPIC (version=700.2006.09.13)
    [Thr 5300] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 5300] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 5300] JLaunchISetDebugMode: set debug mode [no]
    [Thr 6352] JLaunchIStartFunc: Thread 6352 started as Java VM thread.
    [Thr 6352] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=4560
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 6352] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 5836] Tue Jun 17 16:30:56 2008
    [Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 5836] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 5836] JLaunchISetClusterId: set cluster id 13786450
    [Thr 5836] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 5836] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 6128] Tue Jun 17 16:31:06 2008
    [Thr 6128] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 6128] ***********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.*
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
    for additional information and trouble shooting.*
    [Thr 6128] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 8152
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:31:10 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 6468] Tue Jun 17 16:31:10 2008
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 6468] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 6468] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 6468] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 7576] JLaunchRequestFunc: Thread 7576 started as listener thread for np messages.
    [Thr 7312] WaitSyncSemThread: Thread 7312 started as semaphore monitor thread.
    [Thr 6468] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 6468] CPIC (version=700.2006.09.13)
    [Thr 6468] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 6468] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 6468] JLaunchISetDebugMode: set debug mode [no]
    [Thr 7456] JLaunchIStartFunc: Thread 7456 started as Java VM thread.
    [Thr 7456] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=8152
    -> arg[ 35]: -Djstartup.ownHardwareId=T1648851106
    -> arg[ 36]: -Djstartup.whoami=server
    -> arg[ 37]: -Djstartup.debuggable=no
    -> arg[ 38]: -Xss2m
    -> arg[ 39]: -DSAPINFO=BWD_01_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=3227
    -> arg[ 42]: -DSAPSYSTEM=01
    -> arg[ 43]: -DSAPSYSTEMNAME=BWD
    -> arg[ 44]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 45]: -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=01
    -> arg[ 50]: -DSAPSYSTEMNAME=BWD
    -> arg[ 51]: -DSAPMYNAME=WDBSSAPBWD01_BWD_01
    -> arg[ 52]: -DSAPDBHOST=WDBSSDBBWD01
    -> arg[ 53]: -Dj2ee.dbhost=WDBSSDBBWD01
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 7456] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 7648] Tue Jun 17 16:31:11 2008
    [Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 7648] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 7648] JLaunchISetClusterId: set cluster id 13786450
    [Thr 7648] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 7648] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 7432] Tue Jun 17 16:31:21 2008
    [Thr 7432] JLaunchIExitJava: exit hook is called (rc = -11113)
    *[Thr 7432] ***********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.*
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'*
    for additional information and trouble shooting.*
    [Thr 7432] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "F:\usr\sap\BWD\DVEBMGS01\work\dev_server0", trc level: 1, release: "700"
    node name   : ID13786450
    pid         : 7280
    system name : BWD
    system nr.  : 01
    started at  : Tue Jun 17 16:31:25 2008
    arguments       :
    *       arg[00] : F:\usr\sap\BWD\DVEBMGS01\exe\jlaunch.exe*
    *       arg[01] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[02] : -DSAPINFO=BWD_01_server*
    *       arg[03] : pf=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[04] : -DSAPSTART=1*
    *       arg[05] : -DCONNECT_PORT=3227*
    *       arg[06] : -DSAPSYSTEM=01*
    *       arg[07] : -DSAPSYSTEMNAME=BWD*
    *       arg[08] : -DSAPMYNAME=WDBSSAPBWD01_BWD_01*
    *       arg[09] : -DSAPPROFILE=F:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS01_WDBSSAPBWD01*
    *       arg[10] : -DFRFC_FALLBACK=ON*
    *       arg[11] : -DFRFC_FALLBACK_HOST=localhost*
    [Thr 5400] Tue Jun 17 16:31:25 2008
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.box.number=BWDDVEBMGS01wdbssapbwd01] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.host=WDBSSAPBWD01] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.en.port=3200] [jstartxx.c   841]*
    *[Thr 5400] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c   841]*
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties]
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> OS libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : WDBSSAPBWD01
    -> ms port    : 3900
    -> os libs    : F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID13786400 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID13786450 : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID13786400           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    -> [01] ID13786450           : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\instance.properties
    [Thr 5400] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 5400] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 4264] WaitSyncSemThread: Thread 4264 started as semaphore monitor thread.
    [Thr 4488] JLaunchRequestFunc: Thread 4488 started as listener thread for np messages.
    [Thr 5400] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 5400] CPIC (version=700.2006.09.13)
    [Thr 5400] [Node: server0] java home is set by profile parameter
    *     Java Home: F:\java*
    [Thr 5400] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID13786450]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : F:\java
    -> java parameters    : -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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 -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_16-b05
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 1024M
    -> init heap size     : 1024M
    -> root path          : F:\usr\sap\BWD\DVEBMGS01\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\BWD\DVEBMGS01\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     : F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50121
    -> shutdown timeout   : 120000
    [Thr 5400] JLaunchISetDebugMode: set debug mode [no]
    [Thr 4872] JLaunchIStartFunc: Thread 4872 started as Java VM thread.
    [Thr 4872] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
    *     Java Parameters: -Xss2m*
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -XX:MaxPermSize=256M
    -> arg[  5]: -XX:PermSize=256M
    -> arg[  6]: -XX:NewSize=171M
    -> arg[  7]: -XX:MaxNewSize=171M
    -> arg[  8]: -XX:+DisableExplicitGC
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Xloggc:GC.log
    -> arg[ 11]: -XX:+PrintGCDetails
    -> arg[ 12]: -XX:+PrintGCTimeStamps
    -> arg[ 13]: -Djava.awt.headless=true
    -> arg[ 14]: -Dsun.io.useCanonCaches=false
    -> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 16]: -XX:SurvivorRatio=2
    -> arg[ 17]: -XX:TargetSurvivorRatio=90
    -> arg[ 18]: -Djava.security.policy=./java.policy
    -> arg[ 19]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 23]: -Dstartup.mode=SAFE
    -> arg[ 24]: -Dstartup.action=UPGRADE
    -> arg[ 25]: -Dsys.global.dir=F:\usr\sap\BWD\SYS\global
    -> arg[ 26]: -Dapplication.home=F:\usr\sap\BWD\DVEBMGS01\exe
    -> arg[ 27]: -Djava.class.path=F:\usr\sap\BWD\DVEBMGS01\exe\jstartup.jar;F:\usr\sap\BWD\DVEBMGS01\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 28]: -Djava.library.path=F:\java\jre\bin\server;F:\java\jre\bin;F:\java\bin;F:\usr\sap\BWD\DVEBMGS01\j2ee\os_libs;C:\Perl\site\bin;C:\Perl\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;F:\java\bin;F:\usr\sap\BWD\SYS\exe\uc\NTAMD64
    -> arg[ 29]: -Dmemory.manager=1024M
    -> arg[ 30]: -Xmx1024M
    -> arg[ 31]: -Xms1024M
    -> arg[ 32]: -DLoadBalanceRestricted=no
    -> arg[ 33]: -Djstartup.mode=JCONTROL
    -> arg[ 34]: -Djstartup.ownProcessId=7280

    We installed teh objects through SDM .
    this solved the issue

  • SAP R/3  4.6 B Support pack level for AIX 5.2

    Hi,
    We have upgraded O.S version from AIX 4.3 to AIX 5.2. Here our environment is SAP R/3 4.6B and DB oracle 8.1.7.
    My question: Do we apply any support pack to the system after support pack upgrade. Please find the below support pack level for our current system.
    SAP_BASIS      46B           0054    SAPKB46B54
    SAP_ABA         46B           0054    SAPKA46B54
    SAP_APPL       46B           0054    SAPKH46B54
    SAP_HR           46B           0000        -
    ST-PI            2005_1_46B    0003    SAPKITLQC3
    Please request the feedback.
    Thanks & Regards,
    Narayana Murthy.

    Do we apply any support pack to the system after O.S upgrade ?
    ( Correction for the below posted mail)

  • Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007

    What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
    Regards,
    Rajesh Banka

    >
    Rajesh Banka wrote:
    > What should be the Support Pack level for R/3 4.7 and BW 3.5 with SAP CRM2007?
    >
    > Regards,
    > Rajesh Banka
    Hi Rajesh,
    Please see the note '833438', it explains which pack is required in this scenario.
    "You cannont connect ERP (R/3) releases lower than 4.6C to CRM 5.0.
    All subsequent CRM releases (5.0 or higher) cannot be connected to ERP lower
    than (R/3) 4.6C.
    These types of system landscapes are not supported by SAP.
    If you are using CRM 5.0, you must have implemented Plug-in PI 2004.1
    Support Package 10 and, provided you have Basis Release 620 or higher, you
    must import PI_BASIS 2005.1 in R/3. --> After you have imported these
    plug-ins"
    Thanks,
    Nitin Sharma

  • Latest Support Packs for integration of SAP XI 7.0 and SAP ECC 6.0 Retail

    Hi,
    We are integrating SAP ECC 6.0 for IS-Retail System with SAP XI 7.0. I would like to know what lastest Support Packs should present in both the Systems for proper integration, without any technical errors in future.
    Regards,
    Balaji

    Hi,
    The latest Support Pack for PI 7.0 is now SP 14
    You can confirm this from SAP service market.
    https://service.sap.com/swdc
    Thanks
    Swarup

  • Latest support pack for sap srm 5.0(server 5.5)

    Hi,
    Pls let me know the latest support pack for sap srm 5.0(server 5.5).
    Thanks,
    Manu

    Hi Muthu,
    if we take e.g. note 1302207. This was created a short while ago after SP14 was delivered. It has to be included in the next support package.
    So the entry with SP15 here means that it is included in SP15 if it is released.
    Hope that i could help.
    Best regards,
    Georg

  • SAP Support pack upgrade help!!!

    Dear Experts ,
    Am new into basis  . My environment is ECC6 ehp4 with solman 7.0 ehp1 .
    Right now my existing support pack stack is 19.
    When i check in solman using MOPZ it shows the target stack as 20. when i checked the components in target stack it shows only few application component patches. No Basis & abap patches.
    But i checked individually in service market place patches list . all components including application & technical components 4 more patches has been released.
    1.My doubt is did support pack upgrade should be done using support pack stack only ?.
    2.Abap & basis patches should be implemented separately based on the dependency of patches in Support pack stack ?
    Kindly help me!!!!

    Hello,
    First of all you need to make sure your ECC6.0 system product type as ECC6.0 ERP4 under Product Systems --> SAP ERP Enhancement in SMSY. Once it's done, you need to click on "Read System Data Remote" to refresh ECC system component detail. Then after check MOPZ and you should be able to see the target stack level with all components.
    Thanks,
    Siva Kumar

  • SAP support pack upgrade

    Dear Experts,
    There has been a discussion with my colleagues to discontinue support pack upgrade. But we are not able to reach to any consensus. We would require your opinion on the same.
    Background of the discussion:
    Since we are using SAP-EH&S in highly customized manner, support pack causes more issues rather than improvements. Each time we have to invest lot of efforts while testing the system after support pack is applied. We have to stop all the development work for 2 months.
    I need to know:
    - What are the implications of discontinuing support pack upgrades?
    - SAP will no longer provide support for current SAP-EH&S module after 2020. What possible issues can we face if no support pack upgrade is done? I believe after 2020 other module would be used, so we are looking for only next 5 years or so.
    - Have there been any other module (highly customized) facing similar issues?
    - Do we lose support from SAP if we don’t upgrade the system?
    I tried to approach SAP as well but couldn't get a straight answer.
    Thanks,
    Apoorv Bhargava

    Dear Apoorv
    in regards of:
    What are the implications of discontinuing support pack upgrades?
    => you will never get "legal updates". A support package is not only a "fix"; but sometimes SAP is delivering new solutions based on legal topics. Good example is "SVT". This is shipped with a Support Package only; you should not never ever try to implement the more than 100 OSS notes manually
    => you will never get "error" fixes; yes you can implement one OSS after the other (if neededI but this is the wrong approach
    => if you would like to do "major upgrade" (e.g. SAP 6.0 EnhPack7) you need to go through the whole process; and only by high level SAP releases you will get the "newest" functions
    On the top only by installing SP or Upgrade you will get updates in property tree (only if you buy legal content from SAP the story would be different)
    In regards of:
    Background of the discussion:
    Since we are using SAP-EH&S in highly customized manner, support pack causes more issues rather than improvements. Each time we have to invest lot of efforts while testing the system after support pack is applied. We have to stop all the development work for 2 months.
    Be happy that you only need 2 months; in most cases more than that is needed,
    In regards of:
    SAP will no longer provide support for current SAP-EH&S module after 2020. What possible issues can we face if no support pack upgrade is done? I believe after 2020 other module would be used, so we are looking for only next 5 years or so.
    Anybody has the same situation here. After 2020 clearly SAP must deliver a solution (alternative etc.); (and you can extend maintenance period as well)
    - Have there been any other module (highly customized) facing similar issues? => I am pretty sure that SAP SD, SAP Mm etc. is the same story
    - Do we lose support from SAP if we don’t upgrade the system? = in my opinion no. But if you need to strat OSS the story is always the same: they will come back and ask you to implement SP etc.
    A lot of SAP services exists to help you in your situation. But you can help yourself. One option is;
    a.) create first a "sandbox" with current SAP ERP release and prepare EHS
    b.) then compare your set up to standard set up and list" differencies"
    c.) start of analyzing: what can be done to get "closer" to standard
    d.) start with "quick win" standardization and the generate a list of "subprojects" to take care the other differences so that may be after a short time (may be only one year) you are much closer to SAP standard
    In regards of:
    Since we are using SAP-EH&S in highly customized manner => as long as you are using only customizing you are in "Standard". There should be less problems in update/upgrade; only if you have adpated SAP codings etc. you have a problem.
    C.B.
    PS: may be check as well:Overview: SAP EHS Management in context of Enhancement Package / Support Package

  • How to velify applying support packs SAP R/3 46C

    Hi,
    I'm going to implement multiple support packs to our R/3 46C system.
    Patch level will jump up over 10 levels to the latest level.
    My point is the support packs have too many SAP Notes over 2000 to foresee possible impacts to our application area.....
    Can you give me some hints about that from your experience?
    I guess the impacts are confined to our ADD-ON parts (Namespace of Z, Y...). No inpact for SAP default parts.
    Thank you in advance.
    Y.Shirako

    Hello Yuji, below is the answer to yourt questions.
    - Am I correct in assuming that there will not be big problems once corresponding SAP Notes in "Side-effect reports" are appl
    (No problems will happen if support packs are implemeted with all pre requisites are met. From pre requisite i mean suppose for applying HR components you need some basic level of BASIS, Abap components.)
    - I plan to apply support packs via TCD:SPAM. Which time point should I consider SAPU and SPDD, before or after SPAM...?
    (SPAU and SPDD will come during run of SPAM transaction when components are getting patched. That time you can call ADJUST MODIFICATIONS and later after completion of SPAM activity you can ask application team to do SPAU and SPDD which they will do in terms of transport request)
    Hope it addresses your query.
    Regards, Amber S | ITL

  • Experiences - Applying support packs to enhanced SAP Web Dynpro code

    Just thought I might highlight some experiences we've had with applying support packs for XSS. (Reply if you have your own experiences or a proven better way)
    Firstly, we are using Travel within XSS and have some significant developments to get this working globally.  Rightly or wrongly, we added our own DC's within the ESS application area and need to take this into account during support packs.
    As advised by SAP, we have not directly applied the support pack source code to the modified track, but created a separate SPXX track which we manually need to reaply all of our changes.  It dissapoints me that SAP don't recommend doing what the help.sap.com states, but there must be a reason for this (supposedly the meta data tool not yet available in NW04 will address the main reason).
    In order to get our custom DC's from the old track to the new; I needed to add all non-generated objects to an activity, connect SPXX-1 track to the SPXX track and transport all the way through to the approval stage to get it migrated (the connection can be terminated after this is done).  Again - Less than ideal, especially if you accidentally transport a generated file or miss a file.
    Then for all SAP Web Dynpro changes, we've documented all changes to the nth degree and it's at this point we manually reapply the changes - taking into account any SAP changes that may have occurred.
    I hope SAP promotes doing this a better way soon, but here's a process for anyone else needing to do this.
    Regards,
    Matt

    As you stated the system without the context tab is NetWeaver 7.0.  The context tab and the extra wizards were new features in NetWeaver 7.0 Enhancement Package 1.  Your system would have to be updated to this NetWeaver Enhancement Package level in order to have this functionality.

  • Applying support packs in SAP netweaver 2004s

    Hi,
    I am working on SAP netweaver 2004s and currently our systems are on Support pack 9.
    We want to move to SP12.
    Can I directly apply SP12 or I have to apply SP10, 11 & than SP12.
    SAP has recommended to apply patches after 2 april 2007 using Solution Manager optimizer.
    Solution Manager optimizer can only be used for ABAP stack and for Java stack i need to used JSPM correct me if I am wrong.
    Regards,
    Manish

    Hi
    Yes, you Can I directly apply SP12 and no need to apply SP10, 11 & than SP12.
    <u><b>Procedure to upgrade from SP9 to SP12 by SAPINST method</b></u>
    1.we need to download the patches for SP13 from the following patches
    <b>www.service.sap.com/swdc/support packages</b>
    <u>a. OS independent Patches</u>
    <b>J2EERT12.0l0001982.SAR</b>
    <u>b. Control file for Oracle</u>
    <b>CTRLORA12.020000118.SAR</b>
    <u>c.J2EE DB dependent patches</u>
    <b>J2EERTOS12.020000118.SAR</b>
    <u>d. SAPINST Patches</u>
    <b>SAPINST12.020000118.SAR</b>
    2.Keep all downloaded files in directory say (sappatches).
    Goto cmd prompt -> Specify the location of the downloaded patches i.e., (sappatches)
    Uncar all the patches using command “sapcar –xvf <filename>.sar”.
    When you uncar all these files we will be getting SAPINST_CD folder.
    <u>3.Application of J2EE patches</u>
    Goto ->SAPINST_CD/sapinst/NT/1386/sapinst.exe
    Say Run new installation.
    Specify Central Instance Profile.
    Profiles are located in /usr/sap/<SAPSID>/sys/profile.
    Central Instance Profile is a.<SAPSID>_DVEBMGS<instancenumber>_<HOSTNAME> for an ABAP+JAVA system.
    b.< SAPSID>_JC<instancenumber>_<HOSTNAME> for a standalone JAVA system.
    After successful completion you can check your patch level (SP12) in URL
    <b>http://<hostname>:50000/sap/monitoring/systeminfo</b>
    With regards,
    Kanthi.

  • Proper Plan for SAP Support Pack Upload

    Hi Experts,
    We are going for Support pack upload of SAP at your firm.
    Like to get your suggestions on the Plan we have done for going with the update.
    The Present Level of SAP in our server is very low 8 stacks low approx in both the Development Server and Production Server.
    What is the best way to apply them from the below mentioned plan.
    1. shall we go for 1 stack in Development for the required components then test it for 3-4 days then go for the same stack in Production. So that both the server go sync with each other. This way going till the target stack one by one.
    2. shall we go and upload all 8 stacks for the components required in development first one by one and then test the system for all the errors available and then start with the Production. Will there be a transport problem if the system are not in sync for the so many days.
    Please suggest which one shall be best suited  if any other plan can be used for safe and proper update of Support pack.
    Jitesh

    Hi,
    1. shall we go for 1 stack in Development for the required components then test it for 3-4 days
    then go for the same stack in Production. So that both the server go sync with each other.
    This way going till the target stack one by one.
    If Large Support Stack gape is there, then
    1. I would perform system copy of Existing Development System into another separate New Test Server.
    2. Then , I will generate Side Effect Reports based on the Source-to-Target Support Stack gape. You can request such side effect from SMP at https://service.sap.com/side-effects by selecting the solution and by providing source to target SP level per component.
    3.Refer The required SAP Notes regarding OCS Know problems for the support patches. Apply latest SPAM/SAINT Updates. Apply Latest SAP Kernel patches.
    4. Apply the Required Support Package stack after taking successful offline backup of Database.
    5. Perform SPDD - SPAU adjustment and record it in single/Multiple Change requests.
    6. Ask the function team to check the Functionality in new Upgraded TEST system
    7. After Confirmation from the Functional & Technical Team, Apply the same support package stack in existing real DEVELOPMENT system and move that SPAU-SPDD adjustment request.
    2. shall we go and upload all 8 stacks for the components required in development first one by one
    and then test the system for all the errors available and then start with the Production.
    Will there be a transport problem if the system are not in sync for the so many days.
    The same above steps will be applicable here also. Change Requests Transports are not recommended between the systems which are on different Support Patch Stacks. With the above mentioned steps your downtime as well as Development Holiday will be minimized.
    Regards,
    Bhavik G. Shroff

Maybe you are looking for

  • Doubt in calltransaction in ALV

    Hi, i have doubt in calltransction in alv..In my report am using ALV grid display to display purchase order number , material docu number ..If i click on purchasing docu number it has to call transaction ME23N for the purchase order number that i hav

  • Error while creating Records Center site

    Hi, I am trying to create a Records Center site on my Dev environment from Central Admin. However it throws below error: looking for this correlation ID in ULS logs, I found errors like: 1. Failed to find <ListTemplate> tag corresponding to ID "101",

  • Music playlist track order... iTunes vs ATV 2nd Gen

    Streaming music from my iTunes Library to new 2nd Gen AppleTV: When I attempt to listen to a music playlist from my iTunes library through AppleTV, the track order within the ATV playlist does not match that of the playlist in my iTunes library. The

  • Shall v maintain price control  for material type with plant specific ?

    Hai Guru,                    In OMS2, we change HALB price control [valuation] as V or S.  whether shall v maintain this for plant specific.? Kindly guide With Regards Swetha

  • Views in master data

    Hi, How can I hide/supress/madatory some fileds and tab pages in customer master data and material master data? Pls advise me the t-code or menu path. Regards, Student