Refurbishment process in SAP PM

Dear Master,
Can anybody help me understand the process of refurbishment in SAP PM?
I hope there might be some document for that.
Please guide me through.
Thanks in advance.

Dear Chinta,
Sorry I can't give you any documentation, but let me give you a little explanation about refurbishment.
Refurbishment is a process to repair our  repairable spare part, then return that spare part back to the equipment, or to warehouse.
1. Warehouse make a good receipt 'other' for the repairable spare part, (spare part is received at warehouse)
2. Make a refurbishment order (IW81). We can repair the sparepart by our technician, or by external service
3. Make a good issue to refurbishment order
4. Repair faulty spare
5. Perform good receipt with reference to refurbishment order.
6. Order close
Hope this can help.
Regards

Similar Messages

  • Problem in refurbishment processing while creating GR.

    Dear experts,
    I'm working on refurbishment processing. I have done all the steps as below:
    I have a material for equipment for which I have 3 valuation types:
    C1 - New items
    C2 - Repaired Items
    C3 - Damaged Items.
    1. Equipment creation with serial number allocating the valuation type C1 installed at a F/L
    2. I have 2 no.s of the same in stock with the valuation type C1.
    Now I got a problem with equipment which is installed and needs to send it to the vendor for repair. I have changed the valuation type to C3 of the equipment in serial number data, and dismantled using t code IE4N with movement type 202. After that I have issued one material (equipment) from stock to the same cost center and then went to change mode of the equipment (IE02) in structure tab I have mentioned the F/L.
    Now I have created a Refurbishment order for the damaged equipment, mentioning from valuation C3 to valuation C2 in the order. I have mentioned the Service number, qyt and price in the External screen of the Operations tab. Released the order. I got PR. (I have mentioned only services for the PR, no materials). I have created the PO w.r.t the PR from the refurbishment order.
    After that the vendor has completed the services and returned the material (equipment), for that I'm following the GR w.r.t refurbishment order i.e, IW8W. I have entered the Order number then enter. There in the new screen it shows,
    Change charge / valuation type+Post GR. this is having tick by defualt.
    Posting date: 28.05.2009
    Document date28.05.2009
    Valuation type C2 in gray mode
    Plant 1250 in gray mode
    stor. location 1040 optional entry
    Then I have ticked the box for Deliv. Compl
    Here I am not finding the material number or serial number.
    In the bottom of the screen it shows the header
    Serial number   Material number     Materail doc number     Batch/Valuation Type
    The headers are showing but no data under the header. While saving the document it gives error message as below:
    Select serial numbers
    Message no. CMFU106
    But there is no data of serial number to select. I have tried the same in IDES, there it is showing only Material numbe no serial number, but allowing to save the document. (the screen is bit different that of Devl. server, in IDES the header as I mentioned above is not appearing, just below the order number the Material number is displaying.)
    Please help me in solving this issue.
    Rgrds,
    Praveen

    Pithan,
    I dont understand why new serial number is created while creating RO? That equipment is already having aserail number and was in use. Now that equipment is damaged and sending for repair to vendor.
    While creating RO it takes the serail number of that equipment (here I have one serial number to one equipment and one material with several serail numbers).
    If that is the case then how it has accepted the GR through MIGO?
    In the document itself SAP mentioned the you need to choose the serial number of the damaged equiupment while creating the RO. It will not be created while creating RO.
    When I try to create and release RO it gives error message as below:
    Automatic serial number assignment for refurbishment is not advisable
    Message no. IW832
    Diagnosis
    The material 700000236 is assigned to the serial number profile. For the serialization operation affected here, automatic serialization is configured in Customizing (value 04)
    System Response
    The setting is not supported in the refurbishment.
    Procedure
    Maintain the serial numbers manually.
    Regards,
    Praveen

  • Movement types for material movements in refurbishment process

    Hi,
    I require some clarification about the movement types to be used when posting material movements in the standard refurbishment process.
    I am mentioning the standard refurbishment process below. Please correct me if I am wrong or if I missed anything.
    1) Dismantle a defective spare part from the machine.
    2) Take this defective spare to a storage location for unserviceable stock. (Materials movement-post GR)
    3) Withdraw a new or repaired spare for the above material. (Materials movement-post GI)
    4) Install the the above new or repaired spare to the machine.
    5) Repair the defective spare.
    Now I am confused and what I require to know is that for steps 2 and 3 what transaction to use for goods movement and what standard movement types are recommended for this GR and GI?
    Thanks and regards,
    Abhijit Dutta

    Abhijit Dutta
    The standard Refurbishment process does not involve the initial move into the warehouse/stock. That is part of the standard maintenance processes.
    The Refurbishment takes defective item from the warehouse (goods issue), repairs them, and returns the, back to stock (goods receipt). Usually these items are valuated stock.
    [SAP Help|http://help.sap.com/erp2005_ehp_04/helpdata/EN/5b/ae3bf14b8611d182ba0000e829fbfe/frameset.htm]
    PeteA

  • Implementation of refurbishment process

    I want to implement this refurbishment process in already implemented site which does not have this process .
    Kindly advice me other than process what is to be done in the project .
    What is exactly do in mm do we need to upload all mm data again or only refurbished material to be uploaded .
    then what from finance side & pm side in project
    kindly help me friends
    chandrashekhar

    hi chandrashekar,
    you can look in to this web site <b>http://help.sap.com/saphelp_46c/helpdata/en/fe/67f9609d6f11d189b60000e829fbbd/frameset.htm</b>
    regards
    thyagarajan

  • Return from Vendor in Refurbishment Process

    Hi
    Need help in understanding the below Steps Refurbishment Scenario u2013
    We want to send the defective Material to a external Vendor for Repair, we can Issue the Material under valuation class u201CDEFECTu201D Thro MB1B Mvt Type 541 . However while taking back thro Mvt type 542 it is not possible to take it in valuation class u201CREFURu201D .
    Kindly guide how to map the process.
    Regards
    Sameer

    Hi
    Thanks for providing the links for subcontracting process .
    I have two Queries pls guide -
    1) Is standard SAP PM Refurbishment Process is not supporting the process of external repair of spares ( Which is a common industry practise ) . Due to this we need to have two processes for repair one for internal repair Refurbishment Process & another for external repair Subcontracting Process.
    2) As this "Subcontracting indicator " in PM Order Process is available for ECC6 - EHP4 --- we are not in that so how we can map the process of external repair in SAP PM .
    Reagrds
    Sameer
    Edited by: Saxena Sameer on Oct 13, 2011 1:36 PM

  • Alternate solution for Refurbishment Process without split valuation

    Hi Experts,
    We are implementing SAP PM module. We want any alternate method for Refurbishment process ( Internally processed inside the plant) without activating the split valuation . Is it possible ? If possible, please suggest the process .
    Thanks in Advance.
    VT

    No suggestion received, I am closing this.
    regards
    VT

  • What is the speciality of Refurbishment Process

      Hi Guru's
      Please let me know the details of Refurbishment Process.
    I can use a preventive or breakdown maintenance, but why should an organization go for Refurbishment.
    What are the advantages.

    There are many threads & many help links available in google. Please do some search.
    You can refer SAP help links of the desired topic.

  • Refurbishment Process Flow

    Hi,
    I am in implementation of PM/CS module, my client requirement is configure refurbishment process,
    any body tell me how refurbishment process flows in SAP PM/CS.
    I need t-codes of this process.
    Kapil

    One more useful link
    [Steps in Refurbishment Process|http://www.sap-img.com/plant/the-steps-regarding-refurbishment-order.htm]
    *Edited below*
    Key Configuration setting:
    Indicate Order Types for Refurbishment Processing
    T Codes:
    IW21 -->                 If the Refurbishment Order is supported by a job request by the Customer
    IW31 -->                In case there is no IW21 in the process.
    IW41 -->                Confirming (Partial quantities or full quantity  DLV status)
    MB1B, MIGO -->          Transfer C3 Material (to be refurbished) between storage Locations
    MB11 -->                To take the C3 Material  into the Refurbishment Order
    IW8W -->                 Repaired material transfers from Order to Inspection Lot (as C2)
    QA32 -->                 Material Inspection and Transfer to Storage Location Unrestricted Stock
    TECO -->                       Technical Completetion
    Regards....
    Edited by: K Jogeswara Rao on Jun 29, 2010 9:14 AM

  • User is getting email delivery failure when processing via SAP as it tries to send an email to a user who have left the company

    Hi Experts,
    I need to remove a name on a group list in Outlook as the user is getting email delivery failure when processing via SAP (He sends the invoice for approval and emails get sent to different users for approval.) One of those users has left the company and so the user gets a email delivery failure error.
    How do I remove this user who is no longer with the company?
    The user is saying: When I approve an invoice in SAP it sends an email notification through outlook. One of those users is no longer with the company so it cannot deliver the notification, and in return send a delivery failure (in outlook). I am approving the invoices from my SAP Workplace inbox.
    How do we know what group the email is going to?
    Please let me know if you have seen this issue before. Greatly appreciate your help.
    Thanks,
    Asad

    Hi,
    Please check whether you are using a custom z program for sending emails of approved invoices to users. If yes then either the user email ids are hardcoded in the program else a ztable is maintained for them.

  • Problem in Refurbishment processing while doing GR.

    Dear experts,
    I'm working on refurbishment processing.
    I have done all the steps as below:
    I have a material for equipment for which I have 3 valuation types:
    C1 - New items
    C2 - Repaired Items
    C3 - Damaged Items.
    1. Equipment creation with serial number allocating the valuation type C1 installed at a F/L
    2. I have 2 no.s of the same in stock with the valuation type C1.
    Now I got a problem with equipment which is installed and needs to send it to the vendor for repair.
    I have changed the valuation type to C3 of the equipment in serial number data, and dismantled using t code IE4N with movement type 202.
    After that I have issued one material (equipment) from stock to the same cost center and then went to change mode of the equipment (IE02) in structure tab I have mentioned the F/L.
    Now I have created a Refurbishment order for the damaged equipment, mentioning from valuation C3 to valuation C2 in the order.
    I have mentioned the Service number, qyt and price in the External screen of the Operations tab. Released the order. I got PR. (I have mentioned only services for the PR, no materials)
    I have created the PO w.r.t the PR from the refurbishment order.
    After that the vendor has completed the services and returned the material (equipment), for tha I'm following the GR w.r.t refurbishment order i.e, IW8W.
    I have entered the Order number then enter.
    There in the new screen it shows,
    Change charge / valuation type+Post GR. this is having tick bydefualt.
    Posting date: 28.05.2009
    Document date28.05.2009
    Valuation type C2 in gray mode
    Plant 1250 in gray mode
    stor. location 1040 optinal entry
    Then I have ticed the box for Deliv. Compl
    Here I am not finding the material nuber or serial number.
    In the bottom of the screen it shhows the header
    Serila number        Material number       Materaildoc number    Batch/Valuation Type
    The headers are showing but no data under the header.
    While saving the document it gives error message as below:
    Select serial numbers
    Message no. CMFU106
    But there is no data of serial number to select.
    I have tried the same in IDES, there it is showing only Material numbe no serial number, but allowing to save the document. (the screen is bit different that of Devl. server, in IDES the header as I mentioned above is not appearing, just below the order number the Material number is displaying.)
    Can any one please help me in solving this error message?
    I am following the steps correctly? If not please tell me where I'm doing wrong?
    Thanks in Advance,
    Regards,
    Praveen.

    Dear Experts,
    I was able to complete the process through MIGO.
    I have changed the valuation type of the serial number master through IQ02 from C3 to C2. Then I have done the GR w.r.t the order. Now it has posted the document.
    There were some errors while doing this, like some settings missing in OBYC for GBB. That also I have rectified then it allowed for the GR.
    Surprisingly, it not allowing to post through IW8W where everything will change automatically, like Valuation type from C3 to C2 etc...
    I am not able to understand why this is not happening?
    The steps I followed would be work around.
    Can some please help me out ?
    Regards,
    Praveen.

  • System Refresh Process of SAP Web AS 6.20 in BW env

    We are in the process to refresh our BQA system from the offline backup copy of BPR(Production server). We did it number of times in 4.6 R/3 server successfully in past. We used the oracle backup/restore method for refresh process in R/3. The same oracle backup/restore method we used for BW refresh. But this method is not able to change the schema name in tablespace (in BQA system, tablespace are like PSAPBQAFACT and in BP1 , it is PSAPBP1FACT). Seems to me this is not the right method to refresh SAP Web AS 6.20 and above systems.
    Could anyone pls suggest the right documents or if someone has the procedure for refresh process of SAP Web AS 6.20, pls confirm.

    Hi Reiner! Thanks for your reply!
    - I want to create a secure connection between the .NET client and the SAP Web AS 6.20 Web Service, and HTTPS would be great. Is there any documentation regarding this issue?
    - No, I don't want to provide the result of a Web Service as a Web Service. Maybe I was quite unclear... :/ What I meant was:
    I want my Web Service to return a table (the result comes in the structure of a table). How do I define the Out-parameter in transaction se37 to accomplish this? Right now the best solution I got was to construct an array of strings (like the ZZVALUES int array in the example) where each position of the array, is a string that has the various fields of the table i want to return concatenated.
    I'm able to retrieve the array in Visual Studio .NET 2003 client, and separate the fields (to fill a table again with them). If I could just return the table from SAP and receive it in .NET would be much more simpler.
    Thanks again.

  • Jstart.exe process in sap mmc is not getting started

    Hi,
    The jstart.exe process of sap mmc (management console/server) is not getting started.
    The status for this process is "starting the processes". Need help!
    The developer trace is as follows :
    trc file: "dev_jstart.7668", trc level: 1, release: "720"
    trc file: "dev_jstart.new", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7668
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 10:03:13 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F Mon Oct 08 10:03:13 2012
    F  ********************************************************************************
    F  Java environment properties (C:\usr\sap\SV1\J02\work\jstart.jvm)
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F  ********************************************************************************
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 7652] MtxInit: 30002 0 2
    trc file: "dev_jstart", trc level: 1, release: "720"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi

    F [Thr 7652] Mon Oct 08 10:03:14 2012
    F  [Thr 7652] *** LOG => connected to Enqueue Server.
    F  [Thr 7652] *** LOG => connected to Message Server.
    F  [Thr 7652] *** LOG => Starting run level 1.
    F  ********************************************************************************
    F  Java process [deployment] properties:
    F    section name     : deployment
    F    config file      : C:\usr\sap\SV1\J02\exe\startup.properties
    F    node name        : Deploy_offline
    F    home directory   : C:\usr\sap\SV1\J02\j2ee\cluster
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 1.

    F Mon Oct 08 10:03:15 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=0
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -hostvm
    F    arg[ 4] = -nodeName=deployment
    F    arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
    F    arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_deployment
    F    arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_deployment.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_deployment.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_deployment.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process Deploy_offline started with pid 7968
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process deployment started (pid 7968).

    F [Thr 7652] Mon Oct 08 10:03:19 2012
    F  [Thr 7652] *** LOG => Process deployment stopping (pid 7968).

    F [Thr 6972] Mon Oct 08 10:03:19 2012
    F  [Thr 6972] *** LOG => Signal 13 SIGCHLD.
    F  [Thr 7652] *** LOG => Process deployment stopped (pid 7968).
    F  [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Run level 1 completed.
    F  [Thr 7652] *** LOG => Starting run level 2.
    F  ********************************************************************************
    F  Java process [bootstrap] properties:
    F    section name     : bootstrap
    F    config file      : C:\usr\sap\SV1\J02\exe\startup.properties
    F    node name        : Instance_bootstrap
    F    home directory   : C:\usr\sap\SV1\J02\j2ee\cluster
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 2.

    F Mon Oct 08 10:03:20 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=0
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -hostvm
    F    arg[ 4] = -nodeName=bootstrap
    F    arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
    F    arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_bootstrap
    F    arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_bootstrap.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_bootstrap.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_bootstrap.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process Instance_bootstrap started with pid 7952
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process bootstrap started (pid 7952).

    F [Thr 7652] Mon Oct 08 10:03:47 2012
    F  [Thr 7652] *** LOG => Process bootstrap running (pid 7952).
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).

    F [Thr 7652] Mon Oct 08 10:04:10 2012
    F  [Thr 7652] *** LOG => Process bootstrap stopping (pid 7952).

    F [Thr 4436] Mon Oct 08 10:04:10 2012
    F  [Thr 4436] *** LOG => Signal 13 SIGCHLD.
    F  [Thr 7652] *** LOG => Process bootstrap stopped (pid 7952).
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Run level 2 completed.
    F  [Thr 7652] *** LOG => Starting run level 3.
    F  ********************************************************************************
    F  Java process [debugproxy] properties:
    F    section name     : debugproxy
    F    config file      : C:\usr\sap\SV1\J02\exe\dproxy.properties
    F    node name        : Debug_Proxy
    F    home directory   : C:\usr\sap\SV1\J02/j2ee/rdbg.proxy
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  ********************************************************************************
    F  ICM process [icm] properties:
    F    section name     : icm
    F    config file      : C:\usr\sap\SV1\J02\exe\icm.properties
    F    node name        : ICM
    F    home directory   : C:\usr\sap\SV1\J02\work
    F    shutdown timeout : 122000 ms
    F    exit timeout     : 7000 ms
    F  ********************************************************************************
    F  ********************************************************************************
    F  Java process [server0] properties:
    F    section name     : ID24836450
    F    config file      : C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
    F    node name        : server0
    F    home directory   : .
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : true
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 0.
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\icman.EXE
    F    arg[ 1] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 2] = -nodeId=1
    F    arg[ 3] = -f
    F    arg[ 4] = C:\usr\sap\SV1\J02\work\\dev_icm
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_icm.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_icm.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process ICM started with pid 7336
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process icm started (pid 7336).

    F [Thr 7652] Mon Oct 08 10:04:12 2012
    F  [Thr 7652] *** LOG => Process icm running (pid 7336).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 1.

    F Mon Oct 08 10:04:16 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=2
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -DSAPINFO=SV1_02_server0
    F    arg[ 4] = -hostvm
    F    arg[ 5] = -nodeName=ID24836450
    F    arg[ 6] = -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
    F    arg[ 7] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 8] = -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
    F    arg[ 9] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_server0.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_server0.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process server0 started with pid 7616
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process server0 started (pid 7616).

    Hi Ravi,
    Thanks for your quick response.
    Where do I find the default trace for this?
    The server0 process status is "Waiting to start". The developer trace for server0 is as follows :
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7616
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 10:04:17 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out

    F Mon Oct 08 10:04:17 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 7280] MtxInit: 10002 0 2
    I  [Thr 7280] MPI: dynamic quotas disabled.
    I  [Thr 7280] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 7280] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 7280] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 7280] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 7280] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 7280] CCMS: CCMS Monitoring Initialization finished, rc=0.

    F Mon Oct 08 10:04:17 2012
    F  ********************************************************************************
    F  SAP Java VM arguments:
    F    arg[ 0] = vfprintf
    F    arg[ 1] = abort
    F    arg[ 2] = exit
    F    arg[ 3] = -XmonGcCallback
    F    arg[ 4] = -XdebugStateChangeCallback
    F    arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=7616
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 7364] *** LOG => SfCJavaVm: abort hook is called.

    F [Thr 7280] Mon Oct 08 12:28:13 2012
    F  [Thr 7280] *** LOG => Command STOP 0 {}.
    F  [Thr 7280] *** LOG => Result for STOP 0 {}: 0 ok, 00000000.

    F [Thr 7280] Mon Oct 08 12:28:33 2012
    F  [Thr 7280] *** LOG => Command DUMP_THREADS 0 {}.

    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:28:33 2012

    J  ================================================================================
    F  [Thr 7280] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.

    M [Thr 684] Mon Oct 08 12:28:33 2012
    M  [Thr 684] CCMS: CCMS Monitoring Cleanup finished successfully.
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        5508
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 12:28:34 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out

    F Mon Oct 08 12:28:34 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 500] MtxInit: 10002 0 2
    I  [Thr 500] MPI: dynamic quotas disabled.
    I  [Thr 500] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 500] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 500] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 500] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 500] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 500] CCMS: CCMS Monitoring Initialization finished, rc=0.

    F Mon Oct 08 12:28:34 2012
    F  ********************************************************************************
    F  SAP Java VM arguments:
    F    arg[ 0] = vfprintf
    F    arg[ 1] = abort
    F    arg[ 2] = exit
    F    arg[ 3] = -XmonGcCallback
    F    arg[ 4] = -XdebugStateChangeCallback
    F    arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=5508
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 4136] *** LOG => SfCJavaVm: abort hook is called.

    F [Thr 500] Mon Oct 08 12:29:02 2012
    F  [Thr 500] *** LOG => Command DUMP_THREADS 0 {}.

    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:29:02 2012

    J  ================================================================================
    F  [Thr 500] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.

    M [Thr 5068] Mon Oct 08 12:29:02 2012
    M  [Thr 5068] CCMS: CCMS Monitoring Cleanup finished successfully.
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7704
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 12:29:17 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out

    F Mon Oct 08 12:29:17 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 4980] MtxInit: 10002 0 2
    I  [Thr 4980] MPI: dynamic quotas disabled.
    I  [Thr 4980] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 4980] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 4980] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 4980] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 4980] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 4980] CCMS: CCMS Monitoring Initialization finished, rc=0.

    F Mon Oct 08 12:29:17 2012
    F  ********************************************************************************
    F  SAP Java VM arguments:
    F    arg[ 0] = vfprintf
    F    arg[ 1] = abort
    F    arg[ 2] = exit
    F    arg[ 3] = -XmonGcCallback
    F    arg[ 4] = -XdebugStateChangeCallback
    F    arg[ 5] = -DSAPJStartVersion=720, patch 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=7704
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 4736] *** LOG => SfCJavaVm: abort hook is called.

  • How to map different Retail store business processes in SAP

    Hi
    In our stores( Retail Business) there are two sales sections, In the first section we have Point  of Sales systems, here we placed our materials in racks, after confirming and creating sales order customer collects pick list and goes to the location to pick the products. Here customer Invoice will be created before delivery.
    In second sales section normally order fulfillment will take place. Customer visit this section and select products and places an order. But the delivery will be at a later date. We receive some down payment from customer and we create sales order with scheduled delivery. while delivering the products we create delivery note and it will be sent to customer, Our driver will carry the delivery note along with products to the customer and take customer signature on the delivery note. In this second process we are creating Invoice after delivery only.
    Could any body suggest me how can we map these two processes in SAP?
    Your suggestions will be highly appreciated.
    Thanks and Regards

    Hello,
    Check out these links, as they would be useful:
    1. http://www.sap.com/industries/retail/businessprocesses/index.epx
    2. http://help.sap.com/bp_retailv1500/Retail_NL/documentation/RET_Solution_Scope_EN_NL.doc
    3. http://204.154.71.138/pdf/8560/Serving_the_Needs_of_Food_Retailers.pdf
    Regards,
    Gauravjit.
    reward points if the links are useful

  • Clearing process in SAP

    Dear Experts,
    I am quiet confused about this clearing process in SAP.
    For example a cash discount in SAP is posted with the following entry
    01 Cust a/c 15000
    40 Cash disc a/c 3000
    50 Sales or revenue a/c 18000.
    The above open item in the customer account is cleared when payment is recieved from the customer. How the G/l and cash discount account are cleared. I know tcode F-03 clears a g/l account manually when there are debit and credit line items which balance to zero . In what cases the above tcode is used?
    Appreciate if you can explain me.
    Rgds
    Komal

    Hello,
    There is no rule that each account needs to open item managed and cleared completely. There are number of accounts, you cannot maintain as open item managed. By default your customer and vendor accounts are created as open item managed.
    If every account cleared completely, then at the end of the year, you will not have any balances in your Trial Balance. In your case, for example the balances like like cash discount and sales will go to your profit and loss account and the profit or less for the financial year will be discovered.
    Let us take your example itself:
    Customer A/c Dr 15000
    Discount A/c Dr   3000
    Sales Account Cr 18000
    Now think that you have received payment from customer
    Bank A/c Dr. 15000
    Customer A/c 15000
    Presuming that you do not have any other transactions for the year.
    Your P&L Account (You have a profit of 15,000 = 18000-3000) have profit of 15000 and which will be moved to Liabilities side of your Balances sheet and against which you have 15000 bank balance.
    Hope this information clarifies your doubts.
    Regards,
    Ravi

  • Letter of Credit Process in SAP

    Hi Guru's
    Can any one send me or explain me  the letter of credit process in SAP or sales cycle?
    please send step by step configuration or documentation on the above process.
    my mail id is [email protected]
    Suitable points will be rewarded.
    thanking you in advance for your kind help.
    Thanks n Regards
    Toshniwal

    Hi,
    Please find the Letter of credit details
    The configuration is as follows - OVFD, Define and assign payment guarantee, OBYN,OBYH, and OBYK. It is properly working.
    I made all the required transaction VX11N, VXA2, F-36, F-34, F-20
    Letter of Credit: A letter issued by a bank to obtain payment for goods. When a letter of credit is confirmed, the advising bank guarantees payment only if all stipulations in the letter of credit are conformed to exactly.
    1.The importer first request a quote for merchandise. This may or may not include transportation and insurance costs.
    2.The importer prepares a purchase order based on the offer received from the exporter.
    3.The exporter creates a proforma invoice and sends it to importer.
    4.The importer opens a letter of credit with the opening bank in the country of import.
    5.The opening bank sends the letter of credit to the advising bank in the exporters country.
    6.The advising bank advises the exporter that a letter of credit has been opened in his favor.
    7.The exporter ships the merchandise in accordance with the terms stipulated in the LOC.
    8.The exporter gives the documents proving that the shipment was made in conformance with the LOC to the advising bank.
    9.The advising bank pays the exporter based on the documents received.
    10.The advising bank transfers the documents to the opening bank and receives payment.
    11.The opening bank gives the document to the importer.
    12.The importer calculates the duty rates, file the declaration with customs and pays the customs duties within the time frame required by law.
    Hope this will be useful
    Reward points if helpful to you.
    Bye
    Anil

Maybe you are looking for