Order template -runtime error

Hello Time.
When i open some order templates from the search result it is giving run time error.
It is not happening for all order templates.? Any one can help me with any clues.
I also want to know.
1.How the order template is stored in backend.
2. how we can differentiate between normal order and order template.
3.Will search result for order template show all order templates in the system?. What is the filthater criteria for that?.
4. What are the function modules involved in this?.
Regards,
Shanto Aloor

Hello Denis,
The below is the run time error i am getting.
java.lang.NullPointerException: It was tried to rebuild the connection because of invalidity. It is not allowed because the connection type is not JCoConnectionStateless. You may also check the user authorizations.
     at com.sap.isa.core.eai.sp.jco.BackendBusinessObjectBaseSAP.getDefaultJCoConnection(BackendBusinessObjectBaseSAP.java:55)
     at com.sap.isa.backend.crm.SalesDocumentStatusCRM.readDocumentStatus(SalesDocumentStatusCRM.java:1086)
     at com.sap.isa.backend.crm.order.OrderStatusCRM.readOrderStatus(OrderStatusCRM.java:59)
     at com.sap.isa.businessobject.order.OrderStatus.readOrderStatus(OrderStatus.java:432)
     at com.sap.isa.isacore.action.order.DocumentStatusDetailPrepareBaseAction.isaPerform(DocumentStatusDetailPrepareBaseAction.java:270)
     at com.sap.isa.isacore.action.IsaCoreBaseAction.isaPerform(IsaCoreBaseAction.java:378)
     at com.sap.isa.isacore.action.IsaCoreBaseAction.isaPerform(IsaCoreBaseAction.java:418)
     at com.sap.isa.isacore.action.IsaCoreBaseAction.ecomPerform(IsaCoreBaseAction.java:344)
     at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:375)
     at com.sap.isa.core.BaseAction.execute(BaseAction.java:212)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:692)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:409)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source)
     at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176
Regards,
Shanto Aloor

Similar Messages

  • New operating concern - order settlemement - runtime error KE499

    Hello all,
    we created a new operating concern 8000 and changed to the operating concern in KEBC.
    Now when we try to do an order settlement in KO88, it is working for new orders created after the operating concern change, but for old orders, we do get a runtime error KE499:
    Profitability segment number 0000183221 does not exist in operating concern 8000!
    Appearently this is caused by the operating concern change, because the old orders are still "connected" to our old operating conern 2000.
    Now I was wondering, is there a transaction to fix this, something that would transfer the values for the order from the old operating concern to the new one?
    Thanks
    Anne

    Hi,
    I am also getting the exact same error while running CO88 for settlement of production orders, The note recommended above deals with inconsistencies in the sales data. We had changed the assignment of the operating concerna and now we are facing the error where we are not available to pass even one settlemsnt of the production order. I cannot go and individually delete the orders and have to run settlement as a mass transaction.
    Please advise innwhat to do.
    Ariel

  • Custom Purchase Order template causes Error while generating PDF

    The standard XSLFO works, my custom one errors:
    History of the world:
    1) I downloaded the XML Publisher thing for Word, installed it no problems
    2) Downloaded the XML data definition for the Standard Purchase Order from XML Publisher Administrator
    3) Created a blank word document and created the purchase order layout from scratch using the XML Publisher plug-in
    4) Previewed it as a PDF in word - it looked fine (well, it was a start)
    5) Exported the XSLFO
    6) In XML Publisher created a new template and uploaded the XSLFO
    7) Assigned the new template to the document in Purchasing
    All good... the new template is defintately the one being used by the PO Output for Communication program. The problem of course is that it throws a useless error message :) - namely:
    PoPrintingUtil.getBlobPDF(input,input) - After initializing the FOProcessor
    PoPrintingUtil.getBlobPDF(input,input) - After setting the i/o stream and output format
    PoPrintingUtil.getBlobPDF(input,input) - Error while generating the PDForacle.apps.xdo.XDOException
    genDoc() : Exceptionjava.lang.Exception: Error while generating PDF :null
    java.lang.Exception: Error while generating PDF :null
    java.lang.Exception: Error while generating PDF :null
         at oracle.apps.po.communicate.PoGenerateDocument.genDoc(PoGenerateDocument.java:2011)
         at oracle.apps.po.communicate.PoGenerateDocumentCP.runProgram(PoGenerateDocumentCP.java:421)
         at oracle.apps.fnd.cp.request.Run.main(Run.java:148)
    When I run POXPOPDF in Debug I get:
    getArchiveOn(): APPROVE
    After calling genDocThu May 18 12:50:05 EST 2006
    Adding the blob to vector
    java.lang.NullPointerException
    java.lang.NullPointerException
         at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89)
         at oracle.apps.po.communicate.PoGenerateDocumentCP.runProgram(PoGenerateDocumentCP.java:304)
         at oracle.apps.fnd.cp.request.Run.main(Run.java:148)
    I know no one can magically fix this for me (I wish!) but does anyone have any suggestions on what to do next? I have no conditional formatting or any other more complex functionality, just a really boring PO layout with a logo.
    Any suggestions welcome, in the meantime I will keep trawling through Metalink in search of a clue ;)
    Thanks
    Jo

    Hi Jo,
    The first version for which the Template Builder was released is 5.0
    Well, I guess I am one of the few who has a backported 4.5 version of the template builder. I did that for testing exactly your case. I just replaced our xdocore.jar file with the 4.5 version and it worked. The core.jar is not easily available. The files are part of the 4.5 patch, but I think it is too much work to get them out.
    However, I would strongly recommend to upgrade to a later version of XML Publisher. We made huge improvements, since 4.5 - performance, translation, RTF template capabilities....
    I just checked the process of converting an RTF template to FO and uploading it to EBS with 5.6.2 and it still worked. So it seems you can go straight to the latest version.
    Hope that helps,
    Klaus

  • Order template Error

    Hi
    When we try to retieve the created order template its giving the follwoing errors
    Thanks in advance
    at com.sap.isa.backend.db.SalesDocumentDB.getIpcItemProperties(SalesDocumentDB.java:999) at com.sap.isa.backend.db.SalesDocumentDB.createIPCItems(SalesDocumentDB.java:868) at com.sap.isa.backend.db.SalesDocumentDB.recoverItemsDB(SalesDocumentDB.java:3252) at com.sap.isa.backend.db.order.OrderTemplateStatusDB.recoverFromBackend(OrderTemplateStatusDB.java:549) at com.sap.isa.backend.db.order.OrderTemplateStatusDB.readOrderStatus(OrderTemplateStatusDB.java:172) at com.sap.isa.businessobject.order.OrderStatus.readOrderStatus(OrderStatus.java:419) at com.sap.isa.isacore.action.order.DocumentStatusDetailPrepareBaseAction.isaPerform(DocumentStatusDetailPrepareBaseAction.java:269) at com.sap.isa.isacore.action.IsaCoreBaseAction.isaPerform(IsaCoreBaseAction.java:377) at com.sap.isa.isacore.action.IsaCoreBaseAction.isaPerform(IsaCoreBaseAction.java:417) at com.sap.isa.isacore.action.IsaCoreBaseAction.ecomPerform(IsaCoreBaseAction.java:343) at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:353) at com.sap.isa.core.BaseAction.execute(BaseAction.java:211) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:674) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62) at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source) at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    seems problem with some IPC configuration. To make sure the same try changing the Shopadmin settings use LIST PRICE and restart application then look into that issue very closely. this may help you.

  • RunTime Error while saving a Sales Order

    Hi All,
    When i am saving a Sales Order, the system is throwing a Runtime Error.
    The ABAP Code in the Runtime Error screen as follows.
              select * from (t681-kotab) appending table <cond_tab>
                     up to 1 rows
                     where kappl  = se_kappl
                     and   kschl  = se_kschl
                     and   datbi >= se_date
                     and   datab <= se_date
                     and   (coding_tab).
    Till these days, there was no such error while saving a Sales Order.
    How to resolve this issue?
    Regards
    Pavan

    Hi,
    The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
    select * from (t681-kotab) appending table <cond_tab>
    up to 1 rows
    where kappl = se_kappl
    and kschl = se_kschl
    and datbi >= se_date
    and datab <= se_date
    and (coding_tab).
    The reason could be is someone has screwed up the entries in T681 table. Check that out.
    Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
    Let me know if you are still stuck up.
    If you can send me the ST22 dump of the run time error, i might be able to help you more  on this.
    Hope this helps.
    Thanks,
    Balaji

  • WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR

    hi to all experts,
    whenever i try to delete a particular sale order im getting a runtime error
    stating that
    Short text
        Screen: Illegal message
    What happened?
        The current screen processing action was terminated since a situat
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the cur
        screen.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT
    SourceCde
                  message e001(zm) WITH text-335 ltab-kunnr text-334.
                else.
                  if ktab-jkunnr <> ltab-kunnr.
                    ktab-jkunnr = ltab-kunnr.
                    jobsitecode = ltab-kunnr.
                    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                    EXPORTING
                      input  = jobsitecode
                      IMPORTING
                      output = jobsitecode.
                    SELECT SINGLE * FROM kna1 WHERE kunnr = jobsitecode.
                    IF sy-subrc = 0.
                      ktab-jname1 = kna1-name1.
                      ktab-jstras = kna1-stras.
                    ENDIF.
                    chg_flg = 'X'.
                  endif.
                endif.
              else.
                message e001(zm) WITH text-336.
    * Validation for relationship between Sold-to Party and Ship-to Party
    *          if ktab-ckunnr+0(4) NE ktab-jkunnr+0(4).
    *            message e001(zm) WITH text-335 ktab-jkunnr text-337 ktab-ckunnr.
    *          endif.
              custcode1 = ktab-ckunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = custcode1
                IMPORTING
                  output = custcode1.
              jobsitecode1 = ktab-jkunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = jobsitecode1
                IMPORTING
                  output = jobsitecode1.
              SELECT SINGLE * FROM knvp
              WHERE kunnr = custcode1
                AND vkorg = vbak-vkorg
                AND vtweg = vbak-vtweg
                AND spart = vbak-spart
                AND parvw = 'WE'
    Error analysis
        The program attempted to issue a " " message during "Exit Command"
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT

    Hi,
    Seems there is some problem with the user exit USEREXIT_SAVE_DOCUMENT..
    Put a breakpoint and see.
    Regards,
    Nagaraj

  • WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"

    Hi Experts,
    While deleting a sales order giving run time error.  PFB runtime error details.
    If you know any OSS message, please let m know. I tried, but there is no luck.
    Short text
        Screen: Illegal message
    What happened?
        The current screen processing action was terminated since a situation
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the current
        screen.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator.
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    How to correct the error
        The program must be modified to correct the error.
        The modification must be made in "Exit Command" processing.
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
        after the short dump. Then choose "System->List->Save->Local File
        (Unconverted)".
    Source Code Extract
    Line  SourceCde
        1 *---------------------------------------------------------------------*
        2 *       FORM YVBEP_LESEN                                              *
        3 *---------------------------------------------------------------------*
        4 *       Lesen der Tabelle YVBEP (nicht sortiert)                      *
        5 *---------------------------------------------------------------------*
        6 FORM YVBEP_LESEN USING US_POSNR
        7                        US_ETENR
        8               CHANGING CH_TABIX.
        9
       10   YVBEP = SPACE.
       11   YVBEP-MANDT = VBAK-MANDT.
       12   YVBEP-VBELN = VBAK-VBELN.
       13   YVBEP-POSNR = US_POSNR.
       14   YVBEP-ETENR = US_ETENR.
       15   READ TABLE YVBEP.
       16   IF SY-SUBRC > 0.
       17     MESSAGE E506 WITH US_POSNR US_ETENR.
       18   ENDIF.
    >>>>>   CH_TABIX = SY-TABIX.
       20
       21 ENDFORM.
    Could you please help on this issue.
    Thanks
    Srinu

    Hi Srinu,
    it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
    It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
    If only a single order causes this issue, maybe something was wrong during an update.
    If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
    If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
    Regards,
    Klaus

  • Getting Runtime Error 6 Overflow when Running a BI Publisher Template

    Hi,
    I have a requirement to in a template where i am filling the table with empty lines if the no of lines in the template per page are less then the specified no of lines per page.
    It is working when the data is for 4 suppliers when the data is huge ie: 40 suppliers the template is showing Runtime Error 6 Overflow.
    can anyone please guide on this,if needed i will mail the template and the xml.
    Best Regards,
    Mahi

    Hi ,
    I am also getting the same error. When i am trying to print 6 lines per page in xml publiesher report, it is working fine but if i am trying to print 7 lines or more, then it is going into Runtime Error 6 Overflow. Can you suggest something on this?
    Regards
    Sachin

  • Portal Runtime Error: Unable to parse template

    Hi!
    I integrated SAP BW system with SAP Portal. All the connection tests (Sap Web AS connection, ITS connection, Connection Test for connectors) run successfully.
    I also installed a BI add on u201CBI Administratoru201D on Portal and performed all the steps on SAP BI system.
    When I try to access one of the functions of BI Administrator I get Portal Runtime Exception on all the windows in Portal (bellow, in the middle, etc.).
    BI System Selection  
    Portal runtime error.
    An exception occurred while processing your request. Send the exception ID to your portal administrator.
    Exception ID: 12:26_20/01/09_0013_21754250
    Refer to the log file for details about this exception.
    I have looked into log file for Portal and detected the following error text:
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException:
    Exception in SAP Application Integrator occured: Unable to parse template &\#39;&lt;System.Access.WAS.protocol&gt;://&lt;System.Access.WAS.hostname&gt;
    /sap/bw/BEx?sap-client=&lt;System.client&gt;&amp;sap-language=&lt;Request.Language&gt;&amp;accessibility=&lt;User.Accessibility
    [SAP_BOOL]&gt;&amp;style_sheet=&lt;LAF.StylesheetUrl[url_ENCODE]&gt;&amp;&lt;TrayInformation[IF_true PROCESS_RECURSIVE]&gt;&amp;&lt;Authentication&gt;&amp;&lt;Report&gt;&amp;&lt;BusinessParameters&gt;&\#39;; the problem occured at position 82. Cannot process expression &lt;System.client&gt; because Invalid System Attribute:
    System:    &amp;\#39;SAP_LocalSystem&amp;\#39;,
    Attribute: &amp;\#39;client&amp;\#39;.
    Question:
    How can I correct this error?
    Any helpful information will be very appreciated!
    Axel

    Hi Alex,
    It seems that the iview (of the type Application intergrator) cannot read or interperet the "client" parameter from your system object.
    I can also see that the systemobject-alias that is reffered to is "SAP_LocalSystem".
    Find the System Object called SAP_BW and see if all settings to connect to the backend are correct.
    In addition in the iview try to set the system-alias from SAP_LocalSystem to SAP_BW and retry.
    Good Luck.
    Benjamin

  • While creating Sales order in Va01 runtime error

    Hi friends,
    While i am creating sales order in VA01 i am getting runtime error
    Thanks in advance
    venuprasad

    This could be due to some recent code changes in SAPMV45A...may be some user exits...
    The Dump which is obtained can be analysed by an ABAP person and could lead you tot he right issue.
    Hope this helps
    Regards
    Biju

  • Runtime Error - Order Status

    Hi friends,
    Pls check below the runtime error description ,which I'm getting when releasing the Order - PM.
    Pls advise, What happ'd and how to fix it.
    Regards
    Sankar.
    Runtime Errors MESSAGE_TYPE_X
    Date and Time 31.03.2008 13:16:08
    Short text 
    The current application triggered a termination with a short dump. 
    What happened? 
    The current application program detected a situation which really 
    should not occur. Therefore, a termination with a short dump was 
    triggered on purpose by the key word MESSAGE (type X). 
    What can you do? 
    Note down which actions and inputs caused the error. 
    To process the problem further, contact you SAP system 
    administrator. 
    Using Transaction ST22 for ABAP Dump Analysis, you can look 
    at and manage termination messages, and you can also 
    keep them for a long time. 
    Error analysis 
    Short text of error message: 
    Unable to read RFC destination WORKFLOW_LOCAL_250 
    Long text of error message: 
    Technical information about the message: 
    Message class....... "SWF_RUN" 
    Number.............. 617 
    Variable 1.......... "WORKFLOW_LOCAL_250" 
    Variable 2.......... "RFC_READ_DESTINATION_TYPE" 
    Variable 3.......... "DESTINATION_NOT_EXIST" 
    Variable 4.......... " " 
    How to correct the error 
    Probably the only way to eliminate the error is to correct the program. 
    If the error occures in a non-modified SAP program, you may be able to 
    find an interim solution in an SAP Note. 
    If you have access to SAP Notes, carry out a search with the following 
    keywords: 
    "MESSAGE_TYPE_X" " " 
    "CL_SWF_RUN_WIM_LOCAL==========CP" or "CL_SWF_RUN_WIM_LOCAL==========CM088" 
    "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER" 
    If you cannot solve the problem yourself and want to send an error 
    notification to SAP, include the following information: 
    1. The description of the current problem (short dump) 
    To save the description, choose "System->List->Save->Local File 
    (Unconverted)". 
    2. Corresponding system log 
    Display the system log by calling transaction SM21. 
    Restrict the time interval to 10 minutes before and five minutes 
    after the short dump. Then choose "System->List->Save->Local File 
    (Unconverted)". 
    3. If the problem occurs in a problem of your own or a modified SAP 
    program: The source code of the program 
    In the editor, choose "Utilities->More 
    Utilities->Upload/Download->Download". 
    4. Details about the conditions under which the error occurred or which 
    actions and input led to the error. 
    System environment 
    SAP-Release 700 
    Application server... "SILDEV" 
    Network address...... "192.168.255.70" 
    Operating system..... "Windows NT" 
    Release.............. "5.2" 
    Hardware type........ "4x IA64 Level 3" 
    Character length.... 16 Bits 
    Pointer length....... 64 Bits 
    Work process number.. 2 
    Shortdump setting.... "full" 
    Database server... "SILDEV" 
    Database type..... "MSSQL" 
    Database name..... "DEV" 
    Database user ID.. "dev" 
    Char.set.... "C" 
    SAP kernel....... 700 
    created (date)... "Mar 3 2008 03:55:37" 
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10" 
    Database version. "SQL_Server_8.00 " 
    Patch level. 150 
    Patch text.. " " 
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194" 
    SAP database version. 700 
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows 
    NT 6.0" 
    Memory consumption 
    Roll.... 16192 
    EM...... 8379680 
    Heap.... 0 
    Page.... 16384 
    MM Used. 4889280 
    MM Free. 3487552 
    User and Transaction 
    Client.............. 250 
    User................ "PM5CHARL" 
    Language Key........ "E" 
    Transaction......... " " 
    Transactions ID..... "49F6FEDCA000F177897B0017A4ABF059" 
    Program............. "CL_SWF_RUN_WIM_LOCAL==========CP" 
    Screen.............. "SAPMSSY1 3004" 
    Screen Line......... 2 
    Information on caller of Remote Function Call (RFC): 
    System.............. "DEV" 
    Database Release.... 700 
    Kernel Release...... 700 
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) 
    Call Type........... "synchron and transactional (emode 0, imode 0)" 
    Inbound TID.........." " 
    Inbound Queue Name..." " 
    Outbound TID........."C0A8FF46013847F096C00004" 
    Outbound Queue Name.." " 
    Client.............. 250 
    User................ "PM5CHARL" 
    Transaction......... " " 
    Call Program........."SAPLERFC" 
    Function Module..... "ARFC_DEST_SHIP" 
    Call Destination.... "NONE" 
    Source Server....... "SILDEV_DEV_00" 
    Source IP Address... "192.168.255.70" 
    Additional information on RFC logon: 
    Trusted Relationship " " 
    Logon Return Code... 0 
    Trusted Return Code. 0 
    Note: For releases < 4.0, information on the RFC caller are often 
    only partially available. 
    Information on where terminated 
    Termination occurred in the ABAP program "CL_SWF_RUN_WIM_LOCAL==========CP" - 
    in "IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER". 
    The main program was "SAPMSSY1 ". 
    In the source code you have the termination point in line 10 
    of the (Include) program "CL_SWF_RUN_WIM_LOCAL==========CM088". 
    Source Code Extract 
    Line  SourceCde 
    1 METHOD if_swf_run_wim_utl_internal~get_system_user . 
    2 DATA: l_excp TYPE REF TO cx_swf_run_wim. 
    3  
    4 TRY. 
    5 IF me->m_int_state-system_user IS INITIAL. 
    6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
    7 ENDIF. 
    8 re_user = me->m_int_state-system_user. 
    9 CATCH cx_swf_run_wim INTO l_excp. 
    >>>>> MESSAGE ID l_excp->t100_msg-msgid 
    11 TYPE 'X' 
    12 NUMBER l_excp->t100_msg-msgno 
    13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2 
    14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4. 
    15 ENDTRY. 
    16  
    17 ENDMETHOD. " 
    Contents of system fields 
    Name  Val. 
    SY-SUBRC 0 
    SY-INDEX 2 
    SY-TABIX 1 
    SY-DBCNT 0 
    SY-FDPOS 1 
    SY-LSIND 0 
    SY-PAGNO 0 
    SY-LINNO 1 
    SY-COLNO 1 
    SY-PFKEY  
    SY-UCOMM  
    SY-TITLE CPIC and RFC Control 
    SY-MSGTY X 
    SY-MSGID SWF_RUN 
    SY-MSGNO 617 
    SY-MSGV1 WORKFLOW_LOCAL_250 
    SY-MSGV2 RFC_READ_DESTINATION_TYPE 
    SY-MSGV3 DESTINATION_NOT_EXIST 
    SY-MSGV4  
    SY-MODNO 0 
    SY-DATUM 20080331 
    SY-UZEIT 131608 
    SY-XPROG SAPMSSY1 
    SY-XFORM XAB_READ 
    Active Calls/Events 
    No. Ty. Program Include Line 
    Name 
    26 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM088 10 
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER 
    25 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM00J 5 
    CL_SWF_UTL_MAIL=>GET_OWNER 
    24 METHOD CL_SWF_UTL_MAIL===============CP CL_SWF_UTL_MAIL===============CM002 37 
    CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND 
    23 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0IE 38 
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL 
    22 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM021 7 
    CL_SWF_RUN_WIM_STATE=>DYN_SEND_ERROR_REPAIR_MAIL 
    21 METHOD CL_SWF_RUN_WIM_STATE==========CP CL_SWF_RUN_WIM_STATE==========CM01V 12 
    CL_SWF_RUN_WIM_STATE=>EXECUTE_STATE_TRANSITION 
    20 METHOD CL_SWF_RUN_WIM_STATE_FLOW=====CP CL_SWF_RUN_WIM_STATE_FLOW=====CM004 2 
    CL_SWF_RUN_WIM_STATE_FLOW=>IF_SWF_RUN_WIM_STATE~EXECUTE_STATE_TRANSITION 
    19 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM09A 72 
    CL_SWF_RUN_WIM_LOCAL=>SET_STATUS_INTERNAL 
    18 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM0H3 16 
    CL_SWF_RUN_WIM_LOCAL=>_SET_STATUS 
    17 METHOD CL_SWF_RUN_WIM_LOCAL==========CP CL_SWF_RUN_WIM_LOCAL==========CM04P 7 
    CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SET_STATUS 
    16 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM011 12 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>SET_WORKITEM_STATUS_ERROR 
    15 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM01A 81 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXCEPTION_RESULT 
    14 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM00R 93 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>HANDLE_EXECUTION_RESULT 
    13 METHOD CL_SWF_RUN_WIM_EXECUTION_MGR==CP CL_SWF_RUN_WIM_EXECUTION_MGR==CM008 144 
    CL_SWF_RUN_WIM_EXECUTION_MGR=>START_EXECUTION 
    12 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM016 42 
    CL_SWF_RUN_WORKFLOW_START=>START_WORKITEM 
    11 METHOD CL_SWF_RUN_WORKFLOW_START=====CP CL_SWF_RUN_WORKFLOW_START=====CM002 33 
    CL_SWF_RUN_WORKFLOW_START=>EXECUTE 
    10 FUNCTION SAPLSWW_SRV LSWW_SRVU13 135 
    SWW_WI_CREATE_VIA_EVENT_INTERN 
    9 FUNCTION SAPLSWW_SRV LSWW_SRVU11 64 
    SWW_WI_CREATE_VIA_EVENT 
    8 FORM SAPLSWW_SRV LSWW_SRVU11 1 
    SWW_WI_CREATE_VIA_EVENT 
    7 FORM SAPMSSY1 SAPMSSY1 271 
    XAB_RUN_DRIVER 
    6 FUNCTION SAPLSXAB LSXABU01 9 
    RFC_RUN_XAB_DRIVER 
    5 FUNCTION SAPLERFC LERFCU01 115 
    ARFC_EXECUTE 
    4 FUNCTION SAPLERFC LERFCU02 386 
    ARFC_DEST_SHIP 
    3 FORM SAPLERFC LERFCU02 1 
    ARFC_DEST_SHIP 
    2 FORM SAPMSSY1 SAPMSSY1 85 
    REMOTE_FUNCTION_CALL 
    1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30 
    %_RFC_START 
    Chosen variables 
    Name 
    Val. 
    No. 26 Ty. METHOD 
    Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER 
    RE_USER 
    222222222222 
    000000000000 
    000000000000 
    000000000000 
    L_EXCP 
    B0004000 
    90006000 
    SY-MSGID 
    SWF_RUN 
    55455542222222222222 
    376F25E0000000000000 
    00000000000000000000 
    00000000000000000000 
    L_EXCP->T100_MSG-MSGID 
    SWF_RUN 
    55455542222222222222 
    376F25E0000000000000 
    00000000000000000000 
    00000000000000000000 
    SWFCO_WIM_WI_FORWARD 
    SWW_WI_FORWARD 
    555554544554542222222222222222 
    377F79F6F271240000000000000000 
    000000000000000000000000000000 
    000000000000000000000000000000 
    SY-MSGNO 
    617 
    333 
    617 
    000 
    000 
    L_EXCP->T100_MSG+40(6) 
    617 
    333 
    617 
    000 
    000 
    SY-MSGV1 
    WORKFLOW_LOCAL_250 
    54544445544444533322222222222222222222222222222222 
    7F2B6CF7FCF31CF25000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+48(100) 
    WORKFLOW_LOCAL_250 
    54544445544444533322222222222222222222222222222222 
    7F2B6CF7FCF31CF25000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    SY-MSGV2 
    RFC_READ_DESTINATION_TYPE 
    54455444544554445444555542222222222222222222222222 
    263F2514F45349E149FEF49050000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+148(100) 
    RFC_READ_DESTINATION_TYPE 
    54455444544554445444555542222222222222222222222222 
    263F2514F45349E149FEF49050000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    SY-MSGV3 
    DESTINATION_NOT_EXIST 
    44554445444544554545522222222222222222222222222222 
    45349E149FEFEF4F5893400000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+248(100) 
    DESTINATION_NOT_EXIST 
    44554445444544554545522222222222222222222222222222 
    45349E149FEFEF4F5893400000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    SY-MSGV4 
    22222222222222222222222222222222222222222222222222 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    L_EXCP->T100_MSG+348(100) 
    22222222222222222222222222222222222222222222222222 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    %_DUMMY$$ 
    2222 
    0000 
    0000 
    0000 
    No. 25 Ty. METHOD 
    Name CL_SWF_UTL_MAIL=>GET_OWNER 
    RE_OWNER 
    %_DUMMY$$ 
    2222 
    0000 
    0000 
    0000 
    ME->M_OWNER 
    %_VIASELSCR 


    ME 
    A0005000 
    E0001000 
    L_WORKITEM 
    60009000 
    3000C000 
    SY-REPID 
    CL_SWF_UTL_MAIL===============CP 
    4455545554544443333333333333334522222222 
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    No. 24 Ty. METHOD 
    Name CL_SWF_UTL_MAIL=>IF_SWF_UTL_MAIL~SEND 
    EX_SENT_TO_ALL 




    EX_MAIL_OBJECT 
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SYST-REPID 
    CL_SWF_UTL_MAIL===============CP 
    4455545554544443333333333333334522222222 
    3CF376F54CFD19CDDDDDDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    ME 
    A0005000 
    E0001000 
    OBJECT_HD_CHANGE-ACNAM 
    SWW_WI_DISPLAY_FOR_MAIL 
    555554544554455445544442222222222222222222222222222222 
    377F79F4930C19F6F2FD19C0000000000000000000000000000000 
    000000000000000000000000000000000000000000000000000000 
    000000000000000000000000000000000000000000000000000000 
    OBJPARB 
    Table IT_7581x570 
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJPARB 
    Table reference: 224 
    TABH+ 0(20) = E06D6DEFF9060000000000000000000000000000 
    TABH+ 20(20) = E0000000F6020000010000003A020000FFFFFFFF 
    TABH+ 40(16) = 042A0200600B000010000000C1248401 
    store = 0xE06D6DEFF9060000 
    ext1 = 0x0000000000000000 
    shmId = 0 (0x00000000) 
    id = 224 (0xE0000000) 
    label = 758 (0xF6020000) 
    fill = 1 (0x01000000) 
    leng = 570 (0x3A020000) 
    loop = -1 (0xFFFFFFFF) 
    xtyp = TYPE#000046 
    occu = 16 (0x10000000) 
    access = 1 (ItAccessStandard) 
    idxKind = 0 (ItIndexNone) 
    uniKind = 2 (ItUniqueNon) 
    keyKind = 1 (default) 
    cmpMode = 2 (cmpSingleMcmpR) 
    occu0 = 1 
    groupCntl = 0 
    rfc = 0 
    unShareable = 0 
    mightBeShared = 1 
    sharedWithShmTab = 0 
    isShmLockId = 0 
    gcKind = 0 
    isUsed = 1 
    isCtfyAble = 1 
    >>>>> Shareable Table Header Data <<<<< 
    tabi = 0x80095FEFF9060000 
    pgHook = 0x0000000000000000 
    idxPtr = 0x0000000000000000 
    shmTabhSet = 0x0000000000000000 
    id = 540 (0x1C020000) 
    refCount = 0 (0x00000000) 
    tstRefCount = 0 (0x00000000) 
    lineAdmin = 16 (0x10000000) 
    lineAlloc = 16 (0x10000000) 
    shmVersId = 0 (0x00000000) 
    shmRefCount = 1 (0x01000000) 
    >>>>> 1st level extension part <<<<< 
    regHook = Not allocated 
    collHook = Not allocated 
    ext2 = Not allocated 
    >>>>> 2nd level extension part <<<<< 
    tabhBack = Not allocated 
    delta_head = Not allocated 
    pb_func = Not allocated 
    pb_handle = Not allocated 
    OBJECT_HD_CHANGE-OBJDES 
    Workflow 405090 set to status ERROR 
    56766667233333327672762776777245545222222222222222 
    7F2B6CF70405090035404F03414530522F2000000000000000 
    00000000000000000000000000000000000000000000000000 
    00000000000000000000000000000000000000000000000000 
    %_FSREG_001 
    OBJCONT 
    Table IT_7609x510 
    \CLASS=CL_SWF_UTL_MAIL\METHOD=IF_SWF_UTL_MAIL~SEND\DATA=OBJCONT 
    Table reference: 225 
    TABH+ 0(20) = 106F6DEFF9060000000000000000000000000000 
    TABH+ 20(20) = E1000000F802000009000000FE010000FFFFFFFF 
    TABH+ 40(16) = 042A0200300B000010000000C1248401 
    store = 0x106F6DEFF9060000 
    ext1 = 0x0000000000000000 
    shmId = 0 (0x00000000) 
    id = 225 (0xE1000000) 
    label = 760 (0xF8020000) 
    fill = 9 (0x09000000) 
    leng = 510 (0xFE010000) 
    loop = -1 (0xFFFFFFFF) 
    xtyp = TYPE#000045 
    occu = 16 (0x10000000) 
    access = 1 (ItAccessStandard) 
    idxKind = 0 (ItIndexNone) 
    uniKind = 2 (ItUniqueNon) 
    keyKind = 1 (default) 
    cmpMode = 2 (cmpSingleMcmpR) 
    occu0 = 1 
    groupCntl = 0 
    rfc = 0 
    unShareable = 0 
    mightBeShared = 1 
    sharedWithShmTab = 0 
    isShmLockId = 0 
    gcKind = 0 
    isUsed = 1 
    isCtfyAble = 1 
    >>>>> Shareable Table Header Data <<<<< 
    tabi = 0x402D5FEFF9060000 
    pgHook = 0x0000000000000000 
    idxPtr = 0x0000000000000000 
    shmTabhSet = 0x0000000000000000 
    id = 541 (0x1D020000) 
    refCount = 0 (0x00000000) 
    tstRefCount = 0 (0x00000000) 
    lineAdmin = 16 (0x10000000) 
    lineAlloc = 16 (0x10000000) 
    shmVersId = 0 (0x00000000) 
    shmRefCount = 1 (0x01000000) 
    >>>>> 1st level extension part <<<<< 
    regHook = Not allocated 
    collHook = Not allocated 
    ext2 = Not allocated 
    >>>>> 2nd level extension part <<<<< 
    tabhBack = Not allocated 
    delta_head = Not allocated 
    pb_func = Not allocated 
    pb_handle = Not allocated 
    OWNER 
    222222222222 
    000000000000 
    000000000000 
    000000000000 
    SENDER 
    222222222222 
    000000000000 
    000000000000 
    000000000000 
    SY-SUBRC 

    0000 
    0000 
    SWFCO_MAIL_ERROR_NOTIFY 
    0002 
    3333 
    0002 
    0000 
    0000 
    OBJECT_HD_CHANGE 
    E ERRORMESSAGEWorkflow 405090 set to status ERROR 00000000000000 F F S
    4222222222245545445544456766667233333327672762776777245545222222222222222233333333333333242425
    50000000000522F2D5331757F2B6CF70405090035404F03414530522F2000000000000000000000000000000060603
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    OBJECT_TYPE 
    RAW 
    545 
    217 
    000 
    000 
    SWFCO_OBJTYPE_BOR 
    BO 
    44 
    2F 
    00 
    00 
    No. 23 Ty. METHOD 
    Name CL_SWF_RUN_WIM_LOCAL=>IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL 
    LT_AGENTS 
    Table IT_7521x28 
    \CLASS=CL_SWF_RUN_WIM_LOCAL\METHOD=IF_SWF_RUN_WIM_INTERNAL~SEND_ERROR_REPAIR_MAIL\DATA=LT_AGEN
    Table reference: 207 
    TABH+ 0(20) = 806B6DEFF9060000000000000000000000000000 
    TABH+ 20(20) = CF000000F0020000010000001C000000FFFFFFFF 
    TABH+ 40(16) = 04180100E006000010000000C1248401 
    store = 0x806B6DEFF9060000 
    ext1 = 0x0000000000000000 
    shmId = 0 (0x00000000) 
    id = 207 (0xCF000000) 
    label = 752 (0xF0020000) 
    fill = 1 (0x01000000) 
    leng = 28 (0x1C000000) 
    loop = -1 (0xFFFFFFFF) 
    xtyp = TYPE#000022 
    occu = 16 (0x10000000) 
    access = 1 (ItAccessStandard) 
    idxKind = 0 (ItIndexNone) 
    uniKind = 2 (ItUniqueNon) 
    keyKind = 1 (default) 
    cmpMode = 2 (cmpSingleMcmpR) 
    occu0 = 1 
    groupCntl = 0 
    rfc = 0 
    unShareable = 0 
    mightBeShared = 1 
    sharedWithShmTab = 0 
    isShmLockId = 0 
    gcKind = 0 
    isUsed = 1 
    isCtfyAble = 1 
    >>>>> Shareable Table Header Data <<<<< 
    tabi = 0xA0696DEFF9060000 
    pgHook = 0x0000000000000000 
    idxPtr = 0x0000000000000000 
    shmTabhSet = 0x0000000000000000 
    id = 537 (0x19020000) 
    refCount = 1 (0x01000000) 
    tstRefCount = 0 (0x00000000) 
    lineAdmin = 16 (0x10000000) 
    lineAlloc = 16 (0x10000000) 
    shmVersId = 0 (0x00000000) 
    shmRefCount = 2 (0x02000000) 
    >>>>> 1st level extension part <<<<< 
    regHook = Not allocated 
    collHook = Not allocated 
    ext2 = Not allocated 
    >>>>> 2nd level extension part <<<<< 
    tabhBack = Not allocated 
    delta_head = Not allocated 
    pb_func = Not allocated 
    pb_handle = Not allocated 
    SYST-REPID 
    CL_SWF_RUN_WIM_LOCAL==========CP 
    4455545554554454444433333333334522222222 
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD+840(28) 
    WS20000014 
    55333333332222 
    73200000140000 
    00000000000000 
    00000000000000 
    SY-REPID 
    CL_SWF_RUN_WIM_LOCAL==========CP 
    4455545554554454444433333333334522222222 
    3CF376F25EF79DFCF31CDDDDDDDDDD3000000000 
    0000000000000000000000000000000000000000 
    0000000000000000000000000000000000000000 
    FUNCNAME 
    SWW_WI_DISPLAY_FOR_MAIL 
    555554544554455445544442222222 
    377F79F4930C19F6F2FD19C0000000 
    000000000000000000000000000000 
    000000000000000000000000000000 
    SWFCO_WI_REMOTE 





    PARAMETER-NAME 
    WI_ID 
    54544 
    79F94 
    00000 
    00000 
    SWFCO_CALLBACK_AGENTS 
    CALLBACKAGENTS 
    54444444454444552222222222222222 
    F31CC213BF175E430000000000000000 
    00000000000000000000000000000000 
    00000000000000000000000000000000 
    PARAMETER-VALUE 
    000000405090 
    333333333333 
    000000405090 
    000000000000 
    000000000000 
    ME->IF_SWF_RUN_WIM_INTERNAL~M_SWW_WIHEAD-WI_ID 
    000000405090 
    333333333333 
    000000405090 
    000000000000 
    000000000000 
    PARAMETER 
    807020C0 
    7080A050 
    00000000 
    00100010 
    LS_MAILOBJ 
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

    Hi Sankar,
    Clearly RFC destination WORKFLOW_LOCAL_250 doesnot exist. But please don't create it directly using Sm59.
    Log into client 250 and go to transaction SWU3. Here you will get option for creating RFC destination making use of user WF-BATCH. In case there is workflow expert in your project take his help.
    Once this is done this dump should not come.
    Regards.
    Ruchit.

  • Error adding new function in order template

    Hi,
    When i am trying to add a new function to order Template under /contolData/Functions/ form data dictonary
    I am getting error :
    Element with same name exist.The following nodes can not be added to the order.
    (no namespace):/ControlData/Functions/MyNewFunction
    (no namespace):/ControlData/Functions/MyNewFunction/componentKey
    Thanks
    Harman

    Hi Harman,
    You might need to be more specific before I can help you. What have you done, and which step you run into the error? I supopse you have created a new "function" Order Component, and created the required Control Data nodes in Data Dictionary (what have you added?), right? So, when you go into the Order Template tab of the new Order Component (which would be empty since it was newly created), and you try to "select from Dictionary" the corresponding ControlData for the function (e.g. /ControlData/Functions/MyNewFunction), that such an error occurs?
    Have you assigned a process for this Order Component? Studio does not allow adding control data to it unless a process is assigned.
    Btw, you should define a namespace for your Order Components (and other orchestration entities). The OSM server uses namespace to locate these entities among cartridges.
    Cheers,
    Daniel Ho
    Product Management -- OSM

  • Runtime Error in CRM_EVENT_PUBLISH_OW while Sales Order Creation

    Hi,
    I am getting run time error when I try to copy the sales order from Existing one and Save it. ( in WEB UI)
    I am getting this error in the Function Module : CRM_EVENT_PUBLISH_OW
    Code Extract :
    IF ( iv_obj_name IS INITIAL ) OR
        ( iv_guid_hi IS INITIAL ) OR
        ( iv_kind_hi IS INITIAL ) OR
        ( iv_event IS INITIAL ).
    -- Fehlerhafte oder unvollständige Parameterübergabe bei Aufruf &1 ---*
       MESSAGE x028(crm_ssc) WITH 'FU CRM_EVENT_PUBLISH_OW'.
    ENDIF.
    Please help me, how can I solve this runtime error.
    Thanks,
    Sandeep

    Hi,
        The Event Publish itself might not be responsible for the error. Whenever you make a change in the order, the change is "published" in order to check if the change is acceptable to other objects of the order. You will have to analyze what might be possibly affected when you made the change or have to do a lot of debugging....
    Regards,
    Arun Prakash

  • Runtime error in sales order creation

    Hai,When I am trying to create sales order one run time error is occured.The error is CALL_TRANSACTION_NOT_FOUND  TRANSACTION "%_GS" IS UNKNOWN.TRANSACTION "%_GS" IS NOT LISTED IN TABLE OF T.CODES.CURRENT ABAP PROGRAMME HAD TO BE TERMINATED BECAUSE ONE OF THE STATEMENT COULD NOT BE EXICUTED.THE CURRENT ABAP/4 SAPMV80Z PROGRAMME USES CALL TRANSCTION TO CALL THE  TRANSACTION"%_GS".TABLE TSTC CONTAINS NO ENTRY FOR"%_GS".THIS COULD BE DUE TO PROGRAMME ERROR.

    Hi,
    Did you call the correct transaction?
    Non-Catchable Exceptions
    Cause: Transaction is unknown
    Runtime Error: CALL_TRANSACTION_NOT_FOUND
    More info
    http://www.s001.org/ABAP-Hlp/abapcall_transaction.htm
    Cheers
    Wiparat

  • Runtime error while creating sales order in VA01

    Dear all,
    In our develpment server(ecc 6.0),while creating sales order in VA01 for a sales area, when ever entering material number and quantity and press enter, it is giving error and taking to Runtime error long text showing syntax error in program RK2LSFOC
    application patch level for both production and development is same.
    can any one suggest the solution please

    Please note the error details
    Runtime Errors         SYNTAX_ERROR
    Date and Time          07.01.2010 17:43:06
    Short text
    Syntax error in program "RK2LSFOC ".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLKEAK" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RK2LSFOC " in include "RK2LSFOC
    " in
    line 128:
    "No component exists with the name "KWBRUM". ."
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP* "
    Error in the ABAP Application Program
    The current ABAP program "SAPLKEAK" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "RK2LSFOC ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    The following syntax error was found in the program RK2LSFOC :
    "No component exists with the name "KWBRUM". ."
    |    " "

Maybe you are looking for

  • Footer not coming end of the page in BI Publisher

    Hi All, I am developing a report in which the footer output is not coming end of the page after the tabular output per group Completion. There is a tabular group and free form group which output coming accourding to number of lines in tabular output

  • How to load external photo gallery in swf file

    hello! i've been using flash catalyst beta to create a simple 100% flash portfolio site. you can view the test here: http://remgriff.110mb.com/ my problem is that i want to link a button from the portfolio page to an external swf file (or html, both

  • HT201210 Why can't I restore my iPad?

    Ok, so long story short, I NEED to restore my iPad to update it to iOS 6. Then this happens in order: When I open up iTunes, before I even get to click on my iPad, it says: "The software on the iPad '**** iPad' has expired and must be updated to a ne

  • Email Invoice as PDF

    Hi folks, I'm trying to send a sapscript/smartform invoice as a PDF attached to an email.  I've been reading a number of posting on this topic but it is still unclear to me how to get this to work.  (R/3 4.7) I need to setup a new output type with tr

  • How do you find which model iPhone you are using?

    Help me find on the iphone what model it is