System Error u0096 Restart is Not Possible!

Hi guys,
I have a sync scenario that calls an http service. When the http service is not available (down) the message in the monitor has a sys error status and the restart is not possible. With an identical scenario, but async, the status is also system error but Manual Restart is possible.
My question is: this is a typical behavior for sync http scenarios? I would like to be able to restart this message, is it possible?
Thanks in advance,
Ricardo.

Hi Michal
Thanks for your quick response.
I’m using these sync calls under a BPM and I found a way to reprocess this messages in system error. So, in Message Monitor open the PE and over the task in error (ex. send step) open the work item and go to “EDIT” menu, in EDIT menu press “change” and you will see on the left side “Services for Administration” and something like “reprocess after error, press the execute button and the sync calls is restarted.
I believe without BPM is not possible restart sync calls, but with BPM it is
Thanks Michal.
Regards,
Ricardo.
Message was edited by: Ricardo  Quintino
Message was edited by: Ricardo  Quintino

Similar Messages

  • System error and restart not possible

    Hi
    I have developed the Proxy to SOAP scenario and it used to work normally as designed, But suddenly it started giving the System error and restart not possible,
    I see the following error in the Runtime work bench on the Receiver CC
    SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
    Can anyone let me know what the error is
    Thanks
    PR

    Hii
    If this channel was in working state earlier, then this error would mean that the receiver webserver hosting the webservice has some problem. You may contact the receiver system for checking out if they have problem at their end and if they agree resend the messages and it should pass through.
    It may be problem with certificates even.
    Best Regards

  • Set Message in BPM to System Error - Manual Restart Possible ?

    Hello,
    I'm working on a scenario where two idocs are merged in a BPM. The next step is sending the message in a synchronous RFC (BAPI) to a SAP R/3. Is it possible to set the merged message to the message status 'System Error - Manual Restart Possible' in the SXMB_MONI, when the BAPI returns an Error message?
    When it's not possible, is there an othe possibility to sent the message again, without involving the source system?
    Thanks in advance
    Matthias

    Hi,
    It would be better i think if you use the concept of raising an exception in your response mapping
    please refer:
    /people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
    /people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping
    in the response mapping you can check the condition for the responce code from RFC.
    Ranjit

  • URGENT: system error - Maual restart possible

    Hi Experts,
    I'm facing a problem in Xi prodoction. Both inbound and outbound are throwing system error - Maual restart possible. The user is restarting manually in order to post the invoice.
    Basically this is retail project, from POS s/w to Xi to SAP R/3. The scenario is file to idoc(inbound) and idoc to file (outbound).
    The error is :
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Interface Determination
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="PERSIST">MESSAGE_NOT_FOUND</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>XML message not found</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The acknowledgement error is :
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have gone throw the sdn post and blogs but i'm uable to trace the problem.
    Kindly suggest me ASAP as this is business critical and posting have been stoped.
    Regards,
    Pawan

    Hi,
    Please find the interface determination trace. Hope this will help you to provide some suggestion.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Interface Determination
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">User: XIBGUSER</Trace>
      <Trace level="1" type="T">Language: E</Trace>
      <Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
      <Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
      <Trace level="2" type="T">Tunneling needed?</Trace>
      <Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
      <Trace level="3" type="T">Sender Interface</Trace>
      <Trace level="3" type="T">WP_PLU.WP_PLU03 urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="1" type="T">Syntax-Check-Flag X</Trace>
      <Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
      <Trace level="1" type="T">Queueid</Trace>
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
      <Trace level="1" type="T">Get the Metadata for port SAPRT2</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
      <Trace level="2" type="T">Port : SAPRT2</Trace>
      <Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
      <Trace level="2" type="T">Cimtyp :</Trace>
      <Trace level="2" type="T">RFCDest :</Trace>
      <Trace level="2" type="T">Release : 700</Trace>
      <Trace level="2" type="T">Version : 3</Trace>
      <Trace level="2" type="T">Direct : 1</Trace>
      <Trace level="2" type="T">SAPREL : 700</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
      <Trace level="2" type="T">Port : SAPRT2</Trace>
      <Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
      <Trace level="2" type="T">Cimtyp :</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">Create XML-Control Record</Trace>
      <Trace level="2" type="T">Create XML-Data Records</Trace>
      <Trace level="3" type="T">Create data Record E1WPA01</Trace>
      <Trace level="3" type="T">Create data Record E1WPA02</Trace>
      <Trace level="3" type="T">Create data Record E1WPA03</Trace>
      <Trace level="3" type="T">Create data Record E1WPA04</Trace>
      <Trace level="3" type="T">Create data Record E1WPA05</Trace>
      <Trace level="3" type="T">Create data Record E1WPA01</Trace>
      <Trace level="3" type="T">Create data Record E1WPA02</Trace>
      <Trace level="3" type="T">Create data Record E1WPA03</Trace>
      <Trace level="3" type="T">Create data Record E1WPA04</Trace>
      <Trace level="3" type="T">Create data Record E1WPA05</Trace>
      <Trace level="3" type="T">Create data Record E1WPA01</Trace>
      <Trace level="3" type="T">Create data Record E1WPA02</Trace>
      <Trace level="3" type="T">Create data Record E1WPA03</Trace>
      <Trace level="3" type="T">Create data Record E1WPA04</Trace>
      <Trace level="3" type="T">Create data Record E1WPA05</Trace>
      <Trace level="3" type="T">Create data Record E1WPA01</Trace>
      <Trace level="3" type="T">Create data Record E1WPA02</Trace>
      <Trace level="3" type="T">Create data Record E1WPA03</Trace>
      <Trace level="3" type="T">Create data Record E1WPA04</Trace>
      <Trace level="3" type="T">Create data Record E1WPA05</Trace>
      </Trace>
      <Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
      <Trace level="2" type="T">Set Sender Routing-object</Trace>
      <Trace level="1" type="T">Set Receiver Routing-object</Trace>
      <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
      <Trace level="3" type="T">Getting type of XMB...</Trace>
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
      <Trace level="3" type="T">No triggers found. OK.</Trace>
      </Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="3" type="T">system-ID = XIP</Trace>
      <Trace level="3" type="T">client = 600</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIBGUSER</Trace>
      <Trace level="1" type="Timestamp">2008-03-27T06:35:02Z UTC-7</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTI0001</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0001</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = DCFBC7EA238100F1B64A00145EDC94EF</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">OK.</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface WP_PLU.WP_PLU03*</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="1" type="T">no interface found</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = XIP</Trace>
      <Trace level="3" type="T">client = 600</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIBGUSER</Trace>
      <Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - e_solutionsPOS</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 2</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 001</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) e_solutionsPOS WP_PLU.WP_PLU03</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: WP_PLU.WP_PLU03</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-03-27T06:35:03Z UTC-7 End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
    Thanks,
    Pavan

  • Notifications of XI-mgs in status 'System Error - Manual Restart Possible'

    Dear colleagues,
    I'm using a simple communication channel of type 'GeneratedReceiverChannel_XI' in order to push XML-messages from the intergration engine into the ABAP-Backend using an ABAP server proxy. Many of these messages, however, show an error status in the XI-monitor (Notifications of XI-mgs in status 'System Error - Manual Restart Possible'). The indication of the system error is OK, since the XML-parser correctly detects a character in a field which shall be mapped to a field of type 'DEC' in the ABAP backend.
    Is there any possibility to configure some type of alerting in the ABAP-backend to track especially the appearence of XML-messages in the XI-monitor with status 'System Error'?
    Thanks a lot and kind regards
    Stefan

    HI,
    As its mentioned in above postes, you can configure the Alert notification in XI which can give you the alerts about this kind of errors.
    If the exception is raised after reaching to ABAP backend R/3 Side, then you may trace it in t-code SXMB_MONI of R/3.
    Refer -- ALERT MANAGMENT
    http://help.sap.com/saphelp_nw04/helpdata/en/3f/81023cfa699508e10000000a11402f/content.htm
    Thanks
    Swarup

  • Document Contains Errors. Approval is not Possible.

    I have a SC approval that errored out when coming back to SRM. We run RBBP_OFFLINE_EVAL program periodically throughout the day to pick up offline approvals from users. In the spool list, I see this message:
    Document Contains Errors. Approval is not Possible. And the system gives me the WI ID, SC # and the object type BUS2121.
    I've never seen such an error before. The document here...is it referring to the approval email itself? We instruct our users to not edit the approval email in any way. They just have to click on the approval link and click on Send in Outlook. I don't know if the document it's referring to is the SC or the approval email.
    Can anyone help?
    SN

    Hi,
    You are right. This error is the issue. To answer your other question why this message was not raised earlier;the problem could be that at the time of sc creation, there might be sufficient budget. But because your shopping cart was in approval for some time, it is possible that some more shopping carts have been raised with the same WBS and got approved. This would reduce the overall budget available. When the shopping cart is approved, one more check is done by the system and this time there was no sufficient budget.Hence the error is displayed. Only option for you now would be to ask FI people to increase budget or resubmit the cart by changing the value of the shopping cart.
    Regards,
    Sanjeev

  • System error: Default TXJCD is not filled in the table T001

    Hi friends,
    Can anyone help me out in this scenario? We are facing a peculiar problem.
    We are in a upgrade project from 4.5b to ECC 6.0.Client is not maintaining any tax codes i.e they are maintaining it outside SAP.The problem is when ever the billing document is released to accounting(VF02) in ECC 6.0 it is showing  this error “System error: Default TXJCD is not filled in the table T001”.But this is working fine in 4.5b.
    Are there any basic changes regarding TAX JURISDICTION CODE is concerned from upgrade. Please provide.
    Thanks in advance,
    Yoga

    Hi Yoga,
    Probably, the program is showing error message FF799, please maintain transaction OBCL with a default tax jurisdiction code.
    The tax jurisdiction code should be maintained at state level only and
    corresponds to the tax jurisdiction code structure maintained in table
    TTXD. For example, if your structure is 2-3-4-1. Then your default
    code should be XX00000000. I suspect that the settings in transaction
    OBCL are incorrect and hence the FF799 error, when shipping from a US
    plant to a foreign ship-to customer (non-US).
    Addional info concerning the Tax Interface for standard methods for
    US taxes you can find at  -   http://www.saplabs.com/projects/tax/
    Documentation: Tax Interface Configuration Guide for release 4.6x
    Please have a look at attached notes 112609 and 385127.
    Here is the explaination that the process for tax-exempt transactions
    has been changed.
    Other notes you may need for OBCL :
    -> 0627091   Message FF749 with billing data transfer
    -> 0608159   Error FS791 during billing data transfer
    -> 0380158   Jurisdiction code for export business transaction
    -> 0419124   Export billing document with tax jurisdictions
    I hope this information helps you,.
    Regards,
    Paulo

  • Java system error: Server repository could not create function template

    Hi, Our BI person is trying to  publish/broadcast a query to the PRODCTION  portal, she gets the below error message.  I am
    attaching the defaulttracelog file
    "Java system error: Server repository could not create function template for RSRD_X_PRODUCE_PROXY caused by: com.sap.mw.jco.JCO$Exception: (103)"
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[./log/defaultTrace.trc]/>
    <!PATTERN[defaultTrace.trc]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[UTF8]/>
    <!FILESET[8, 20, 10485760]/>
    <!PREVIOUSFILE[defaultTrace.7.trc]/>
    <!NEXTFILE[defaultTrace.9.trc]/>
    <!LOGHEADER[END]/>
    #1.5 #002264F9350800600000022F000019C000048E9B91EF3AB3#1282698726384#com.sap.security.core.persistence#sap.com/irj#com.sap.security.core.persistence#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". ##An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #1#Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner '127.0.0.1:sapgw00' not reached
    TIME        Tue Aug 24 21:12:06 201
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2823
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       10061
    ERRNO TEXT  WSAECONNREFUSED: Connection refused
    COUNTER     56
    #1.5 #002264F93508006000000230000019C000048E9B91EF47C8#1282698726384#com.sap.engine.services.monitor.mbeans.Monitor#sap.com/irj#com.sap.engine.services.monitor.mbeans.Monitor#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!#
    #1.5 #002264F93508006000000231000019C000048E9B91EF4CD5#1282698726384#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!
         at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:63)
         at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.unregisterMBean(MBeanServerSecurityWrapper.java:395)
         at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java:1327)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java:258)
         at com.sap.engine.services.monitor.mbeans.Monitor.unregister(Monitor.java:106)
         at com.sap.engine.library.monitor.impl0.AbstractMonitorNode.remove(AbstractMonitorNode.java:154)
         at com.sap.engine.library.monitor.impl0.MonitorObjectFactory.uninstallMonitorNode(MonitorObjectFactory.java:483)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:595)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
         at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:568)
         at com.sap.engine.services.monitor.server.ApplicationLifeCycleImpl.applicationStopped(ApplicationLifeCycleImpl.java:52)
         at com.sap.engine.services.monitor.deployment.MonitorDeploymentContainer.commitStop(MonitorDeploymentContainer.java:630)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:244)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:290)
         at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:278)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.stopApplicationLocalAndWait(DeployServiceImpl.java:4569)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopApplicationLocalAndWait(DeployCommunicatorImpl.java:628)
         at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime$2.run(SAPJ2EEPortalRuntime.java:602)
         at java.security.AccessController.doPrivileged(Native Method)
         at java.lang.ClassLoader$NativeLibrary.load(Native Method)
         at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1482)
         at java.lang.Runtime.load0(Runtime.java:737)
         at java.lang.System.load(System.java:811)
         at com.sapportals.wcm.service.fsmount.FSMountService.loadDLL(FSMountService.java:736)
         at com.sapportals.wcm.service.fsmount.FSMountService.<clinit>(FSMountService.java:796)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertGS(CmConfigurationProvider.java:637)
         at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertServiceConfig(CmConfigurationProvider.java:601)
         at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.readConfiguration(CmConfigurationProvider.java:205)
         at com.sapportals.wcm.crt.CrtSystemImpl.createComponentManager(CrtSystemImpl.java:108)
         at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:202)
         at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
         at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    #1.5 #002264F93508005C0000042300002CF00004939AAEE9AEB7#1288192475655#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#J2EE_GUEST#0##n/a##c7d00e00e1dc11dfa36d002264f93508#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###setting initial ACL on /reporting_backend/reports/System Administration/CM Store/cm.crawlcontent - com.sap.security.api.NoSuchRoleException: Role with uniqueName system_admin_role not found!
         at com.sap.security.core.imp.RoleFactory.getRoleByUniqueName(RoleFactory.java:1783)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getRoles(RPRepositoryManager.java:1474)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.syncReportResources(RPRepositoryManager.java:1334)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.initBackend(RPRepositoryManager.java:489)
         at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getResource(RPRepositoryManager.java:581)
         at com.sapportals.wcm.repository.RMAdapter.getResource(RMAdapter.java:228)
         at com.sapportals.wcm.repository.runtime.CmAdapter.findResource(CmAdapter.java:1349)
         at com.sapportals.wcm.repository.runtime.CmAdapter.findManagerAndResource(CmAdapter.java:1322)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:979)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
         at com.sapportals.wcm.service.reporting.ReportingService.localConfigure(ReportingService.java:294)
         at com.sapportals.wcm.service.reporting.ReportingService.startUpImpl(ReportingService.java:74)
         at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
         at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
         at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
         at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
         at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
         at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
         at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
         at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
         at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
         at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
         at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
         at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
         at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
         at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)

    Go to visual admin -> server -> services -> JCO RFC provider.
    Check the RFC that connects to the BI Abap.
    Its reporting the J2EE_GUEST user in the SAP with the system nr 00.
    Is this BI java portal?
    Is the java portal a addon to Abap or having seperate SID?
    Check the connection definitions are correct and the gateway is running.

  • -9041:system error(BD Index is not accessing)

    hi all,
    -9041:system error(BD Index is not accessing),
    i am not able to import the software component from SLD to IR.
    Thanks & regards,
    subba reddy

    solved my problem.
    thanks,
    subba reddy

  • I want to upgrade the software (currently I have Mac OS X 10.6.4) but when the mac is downloading the new version i get an error message and is not possible get the most updated software: Mac OS X 10.6.8 or either the most recent itunes why?!?!?!

    I want to upgrade the software (currently I have Mac OS X 10.6.4) but when the mac is downloading the new version i get an error message and is not possible get the most updated software: Mac OS X 10.6.8 or either the most recent itunes why?!?!?!

    Then you either have a network problem or a hardware problem or a corrupted hard drive. You might try:
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    You can also try downloading from another computer on a different network connection.

  • ABUMN-error "Posting transaction is not possible (Value date not allowed)"

    Hi,
    When we are trying to transfer asset within company code thru Tcode ABUMN, we are getting a error as
    "Posting transaction is not possible (Value date not allowed)"
    What actually we are doing is we are trying to transfer the previous year asset for example say 01.04.2007 assets on today.
    the Parameters are as below
    Document date :26.03.2008
    Posting Date :26.03.2008
    Asset value date is 01.04.2007.
    Then the system is throwing an error and not alloing to post the previous year transfers.
    Can any one help me out.
    Cheers
    Sri

    Hi,
    I think, if you give old asset value date, system will give you the error.  This may be because, you are trying to transfer the assets with old values, means in your examble the dep. from the 01.04.2007 to 29.02.2008 whould have been charged.
    So, give the current year date means any date from 01.01.2008 to till date.
    If you read F1 help for the value date column, it states,
    Asset value date
    The asset value date is the value date for Asset Accounting. It can deviate from the posting and document date and be in posting periods already closed for Financial Accounting. However, the posting year and asset value date year must be the same.
    Since the asset value date can have a direct influence on the amount of depreciation, the system creates a default value when it can. You can specify in Customizing how the the default asset value date is  determined by the system.
    Hope it helps
    Saravanan.A

  • FBV1 error - Transaction Type 030 not possible

    Hi SAP experts,
    I am currently facing an issue while in FBV1 (via batch input)
    It displays error message Transaction Type 030 not possible (posting to affiliated company), however, the asset group that it belongs to can only be Type 030  (Acquisition in group area only).
    How can this be fixed?
    Is there another TType that is similar to 030 ?
    Any help is welcome
    Regards
    Roger

    Hi,
    check SAPNET note 127650.
    Best regards

  • PO System error - Vendor's address not maintanence !

    Dear friends,
    Our user created a PO , system reproted "vendor's address not maintanence", We checked Vendor's information, not error on that Vendor No.
    Brgds
    WangYong

    If he is, ONE-TIME Vendor..
    You have to enter address, manually in Purchase Order.
    Even if you maintain it in Vendor Master Data.

  • Error with IBAN Generation not possible

    hello
    In transaction XK01, when I create a vendor in bank details I have an error when I add the IBAN. This vendor is Spanish.
    If I create directly the IBAN I have this message : " Generation not possible". Why.
    But if I create this supplier by entering the first :
    - County,
    - Bank key
    - Bank account
    - CK
    The iban be generated without errors.
    I set this bank in FI01.
    Could you help me.
    Best regards

    hi, I am using ECC500 and I just  follow following instructions.
    It is working fine.
    Cheers
    >
    SAP Note 503182:
    >Solution
    >    1. Copy function module SAMPLE_INTERFACE_00003030
    >  from SAMPLE_INTERFACE_00003030
    >    to CONVERT_BANK_ACCOUNT_2_IBAN_ES
    >      Function group: IBAN
    >      2. Copy function module SAMPLE_INTERFACE_00003040
    >      from SAMPLE_INTERFACE_00003040
    >      to CONVERT_IBAN_2_BANK_ACCOUNT_ES
    >     Function group: IBAN
       >   3. Implement the attached source code corrections.
        >  4. BTE setting:
       >   Transaction: FIBF
      >    Settings -> P/S function modules
        >  Create the following entries:
         > Event      Country    Function module
          >00003030   ES        CONVERT_BANK_ACCOUNT_2_IBAN_ES
         > 00003040  ES         CONVERT_IBAN_2_BANK_ACCOUNT_ES

  • Download error on creative cloud. not possible to download new items

    hi i am unable to download new apps to my creative cloud .
    i have a full membership.
    it keeps on saying download error on the apps page.
    what can i do ?

    what do you mean ?
    i am not a pro ?
    please explain safe mode with networking.
    thank you

Maybe you are looking for