Select from local (tmp) Table in Function - Table not found

Hi,
I want to create a cursor which selects from a Table which does not exist in database.
I create this table as local table (how is it called? nested table?).
Not shown in the code but I want to fill this local table later.
After filled my cursor is going to use this filled table.
When try to run I get the error Table or View does not exist at the "FROM TempTab_var T1;" of my cursor.
This is my simplified code:
CREATE OR REPLACE FUNCTION PC_RL_MTA_PMT
RETURN PC_RL_MTA_TYPE_PMT
IS
result_out PC_RL_MTA_TYPE_PMT;
  TYPE TempTab_record_type IS RECORD
    (ID int);
  TYPE TempTab_type IS TABLE OF TempTab_record_type
          INDEX BY BINARY_INTEGER;
  TempTab_var TempTab_type;
  CURSOR TempCursor3_var IS
    SELECT    ID AS ID_var
    FROM    TempTab_var T1;
BEGIN
RETURN result_out;
END PC_RL_MTA_PMT;
Any Ideas whats wrong?
Thanks very much in advance.

And a further example from my library of examples, just to help you out...
SQL> CREATE OR REPLACE TYPE num_descript AS OBJECT(num number, descript varchar2(30))
  2  /
Type created.
SQL> CREATE OR REPLACE TYPE tbl_num_descript AS TABLE OF num_descript
  2  /
Type created.
SQL> CREATE OR REPLACE PACKAGE reftest AS
  2    FUNCTION pipedata(p_choice number) RETURN tbl_num_descript PIPELINED;
  3  END;
  4  /
Package created.
SQL> CREATE OR REPLACE PACKAGE BODY reftest AS
  2    FUNCTION pipedata(p_choice number) RETURN tbl_num_descript PIPELINED IS
  3      v_obj num_descript := num_descript(NULL,NULL);
  4      v_rc  sys_refcursor;
  5    BEGIN
  6      IF p_choice = 1 THEN
  7        OPEN v_rc FOR SELECT empno as num, ename as descript FROM emp;
  8      ELSIF p_choice = 2 THEN
  9        OPEN v_rc FOR SELECT deptno as num, dname as descript FROM dept;
10      END IF;
11      LOOP
12        FETCH v_rc INTO v_obj.num, v_obj.descript;
13        EXIT WHEN v_rc%NOTFOUND;
14        PIPE ROW(v_obj);
15      END LOOP;
16      CLOSE v_rc;
17      RETURN;
18    END;
19  END;
20  /
Package body created.
SQL> select * from table(reftest.pipedata(1));
       NUM DESCRIPT
      7369 SMITH
      7499 ALLEN
      7521 WARD
      7566 JONES
      7654 MARTIN
      7698 BLAKE
      7782 CLARK
      7788 SCOTT
      7839 KING
      7844 TURNER
      7876 ADAMS
      7900 JAMES
      7902 FORD
      7934 MILLER
14 rows selected.
SQL> select * from table(reftest.pipedata(2));
       NUM DESCRIPT
        10 ACCOUNTING
        20 RESEARCH
        30 SALES
        40 OPERATIONS

Similar Messages

  • Error Function module " " not found in Smartforms

    Hi all,
    Please help me out….
    I created the form using the smartforms, check it and activated it. I can see the unique function module is assigned to the form. I wrote the ABAP program and use function module ‘SSF_FUNCTION_MODULE_NAME’and also define data types.
    when I called the function module fm_name for passing values and tables from program to smartform. This is working perfectly in development server but in production it giving error like Function module " " not found.
    Below I m pasting my code.
    *& Report  ZCASHJOURNAL                                                *
    REPORT  zcashjournal                            .
    TABLES: bseg.
    DATA: FM_NAME TYPE rs38l_fnam.
    DATA:BEGIN OF it_bseg OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg.
    DATA:BEGIN OF it_bseg1 OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg1.
    DATA: gv_amt_in_words TYPE spell,
          gv_word TYPE spell-word,
          gv_decword TYPE spell-decword.
    DATA:BEGIN OF gt_bkpf OCCURS 0.
            INCLUDE STRUCTURE bkpf.
    DATA:END OF gt_bkpf.
    DATA:bktxt TYPE bktxt.
    DATA:waers TYPE waers.
    DATA:belnr TYPE belnr_d.
    DATA:werks TYPE bukrs.
    DATA:desc  TYPE butxt.
    DATA:awkey TYPE awkey.
    DATA:docno TYPE matnr.
    DATA:cajo  TYPE awkey.
    DATA:desc1 TYPE butxt.
    DATA:dmbtr TYPE dmbtr.
    SELECTION-SCREEN BEGIN OF BLOCK b2.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT (15) FOR FIELD s_belnr.
    SELECTION-SCREEN POSITION 28 .
      PARAMETERS : s_belnr TYPE bseg-belnr .
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT (15) FOR FIELD s_werks.
        SELECTION-SCREEN POSITION 28 .
          PARAMETERS: s_werks TYPE werks.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN END OF BLOCK b2.
    SELECT * FROM bkpf
               INTO CORRESPONDING FIELDS OF TABLE gt_bkpf
              WHERE belnr LIKE s_belnr
              AND   bukrs LIKE s_werks.
    IF NOT gt_bkpf[] IS INITIAL.
      SELECT * FROM bseg
          INTO CORRESPONDING FIELDS OF TABLE it_bseg
          FOR ALL ENTRIES IN gt_bkpf
          WHERE bukrs EQ gt_bkpf-bukrs
          AND   belnr EQ gt_bkpf-belnr
          AND   shkzg EQ 'S'.
    ENDIF.
    LOOP AT gt_bkpf.
      bktxt = gt_bkpf-bktxt.
      waers = gt_bkpf-waers.
      belnr = gt_bkpf-belnr.
      werks = gt_bkpf-bukrs.
      awkey = gt_bkpf-awkey.
      docno = awkey+0(10).
      cajo = awkey+10(4).
    ENDLOOP.
    LOOP AT it_bseg.
      dmbtr = it_bseg-dmbtr.
    ENDLOOP.
    IF s_werks EQ '65'.
      desc = 'JCBML - Heavy Equipments'.
    ENDIF.
    IF cajo EQ '0001'.
      desc1 = 'PETTY CASH PLANT II'.
    ENDIF.
    CALL FUNCTION 'SPELL_AMOUNT'
      EXPORTING
        amount    = dmbtr
        currency  = waers
        filler    = space
        language  = sy-langu
      IMPORTING
        in_words  = gv_amt_in_words
      EXCEPTIONS
        not_found = 1
        too_large = 2
        OTHERS    = 3.
    IF sy-subrc EQ 0.
      MOVE : gv_amt_in_words-word TO gv_word,
             gv_amt_in_words-decword TO gv_decword.
    ENDIF.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZCASHRECPT'
    IMPORTING
       FM_NAME                  = FM_NAME
    EXCEPTIONS
       NO_FORM                  = 1
       NO_FUNCTION_MODULE       = 2
       OTHERS                   = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    *CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
            EXPORTING  formname           = 'ZCASHRECPT'
                    variant            = ' '
                    direct_call        = ' '
            IMPORTING  fm_name            = lf_fm_name
            EXCEPTIONS no_form            = 1
                       no_function_module = 2.
    *v_vbeln = S_VBELN-low.
    CALL FUNCTION FM_NAME
      EXPORTING
        bktxt            = bktxt
        waers            = waers
        belnr            = belnr
        werks            = werks
        desc             = desc
        docno            = docno
        cajo             = cajo
        desc1            = desc1
        dmbtr            = dmbtr
        gv_word          = gv_word
      TABLES
        T_ZDEB           = it_bseg
      EXCEPTIONS
        formatting_error = 1
        internal_error   = 2
        send_error       = 3
        user_canceled    = 4
        OTHERS           = 5.
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

    Hi Rakesh,
    Check two things
    1. Program tranpsorted to production without any error in request log.
    2. Smartform tranpsorted to production without any error in request log and without renaming / misspelling it.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
    formname = 'ZCASHRECPT'
    IMPORTING
    FM_NAME = FM_NAME
    EXCEPTIONS
    NO_FORM = 1
    NO_FUNCTION_MODULE = 2
    OTHERS = 3
    IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Also try to uncomment the Message id part and it will show some meaningful message.
    And to check whether actaually fucntion module is generated or not goto smartforms ->Smartform name -> Display -> Environment->Fucntion module name . if this is blank try to retransport smartform.
    Hope that helps.
    Regards
    Kapadia
    ***Assigning points is the way to say thanks in SDN.***

  • ORA-20100: Error occurred while processing: Function 'test' not found.

    this program follow:
    declare
    p xmlparser.Parser;
    xmlbuf varchar2(512);
    xmlpat varchar2(512);
    xmldoc xmldom.DOMDocument;
    xmldocnode xmldom.domnode;
    n xmldom.domnode;
    begin
    xmlbuf:='<emps><emp>odp</emp></emps>';
    xmlpat := 'emps/emp/test()';
    p:=xmlparser.newParser;
    xmlparser.parseBuffer(p,xmlbuf);
    xmldoc:=xmlparser.getDocument(p);
    xmldocnode :=xmldom.makeNode(xmldoc);
    n:=xslprocessor.selectSingleNode(xmldocnode,xmlpat);
    --dbms_output.put_line('value of first selected node is:ok');
    exception
    when others then
    raise;
    end testxml;
    message of error:
    ORA-20100: Error occurred while processing: Function 'test' not found.
    ORA-06512: at line 20.
    please quick reponse.

    Steve,
    Yes it helps. I was able to finally figure this much out, however, in order to get the quotes to get handled right, I had to declare the xsl inline and I had to change (there quite a few, this just being an example) the following line from
    <xsl:when test="normalize-space(string(sub_container_settings/initial_investment)) = ''">10000</xsl:when>
    to
    <xsl:when test="normalize-space(string(sub_container_settings/initial_investment)) = ''''">10000</xsl:when>
    This works, but I would prefer to store the xsl in a CLOB. Neither of these work when I get the document from the clob and call the xmldom.parseClob procedure. The parser fails with an error that the document is not valid.
    Do you have any idea on how to handle the single quotes in this circumstance.

  • Function iFS not found

    Hello All,
    Problem:-
    I am transporting my interface from Dev to QA using CMS transport method. Everything is fine in Dev system even mapping is checked correcetly, but when I am checking the mapping in QA system it it showing the error message in the Message mapping as:-
    Error Message in QA message mapping:-
    The source or target structure has been changed or could not be found in the Integration Repository. The mapping definition contains elements or attributes that do not exist in the changed structure. The relevant entries will be deleted
    Function iFS not found
    Function iFS not found
    In My message mapping i am using IF then else function.
    I created new message mapping in Dev system and also transported again but it is giving the same eror message.
    Chirag

    Few other functions are also missing.
    If functions were present in DEV and are now missing in QA....then i would suggest you compare both the systems in terms of patch....this might be the cause of concern....both should be on the same SP
    Update:
    Check the solution section from this note(specifically for IfS): https://service.sap.com/sap/support/notes/1090369
    and confirm that your QA system abides by them
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Nov 20, 2009 4:14 PM

  • Function Module not found in SRM 7.0 -CRM_ORDERADM_H_SELECT_BUF_M_DB

    Hi Masa/Muthu/Viru ,
    We  have upgraded from SRM 3.0 to SRM 7.0.
    we have copied the ZUS2000113 from Business object BUS2000113 for Contract workflow.
    In SRM 7.0 the above   Function Module not found in SRM 7.0 -CRM_ORDERADM_H_SELECT_BUF_M_DB.
    Can you telll which is the replacement of this FM
    Regards
    G.Ganesh Kumar

    Hello,
    What is the aim of FM name you gave us ?
    What is its function group ?
    With those data, it could be easier to find an existing one with same goal in SRM 7.0 release .
    Regards.
    Laurent.

  • SMQ2 SYSFAIL - Function Module not found

    Hi All,
    When i am trying to push data to cdb i got sysfail - Function module not found error in the smq2. But data inserted in the cdb, the probelm we found was the data object having the dependency cause this error.
    The data was there in the cdb, but no distribution entries found.
    Please help me to resolve the same.
    Regards,
    Ramkumar

    Hi,
    Clear the queue first (delete it), then implement the NOTE 1552255 - 'Parallel load problem for partial association shadow'. Run the report mentioned in the NOTE and  do a delta generation.
    Then on doin a delta load the queues should run successfully.
    regards,
    Anil

  • I have upgrade os 6 on my iphone 4 but now in map application i cant found direction from location to location , message appear direction not found so please tell me solution for that

    i have upgrade os 6 on my iphone 4 but now in map application i cant found direction from location to location , message appear direction not found so please tell me solution for that

    http://support.apple.com/kb/HT3743
    Sorry discussing J/B is in breach of the terms and conditions of thi Apple hosted forum
    Google is probably your best hope

  • Function modules not found....

    Hello,
    I found the following errors in my SDCCN logs, I have googled and also searched in SAP market place and even in SDN but no help. Also the EWA shows the same in Missing Function Module column.Please help in this regards.
    Thanks and Regards,
    Yoganand.V
    Errors:
    1) EWA_MAIN_BUSINESS_HOURS : no matching interface found
        function module not found
        EWA_MAIN_BUSINESS_HOURS : funcname /SDF/MAIN_BUSINESS_HOURS , module 000156
    2) READ_RFC_LIST : # of imp params in funcmod < # of imp params in mod 000152
        READ_RFC_LIST : inconsistency in # of imp params found for mod 000152
        READ_RFC_LIST : non-default imp param IF_ANONYMIZE is not passed to mod 000152
        READ_STAMP : no matching interface found
        function module not found
        READ_STAMP : funcname /BDL/READ_STAMP , module 000153

    Hi,
    EWA_MAIN_BUSINESS_HOURS
    READ_RFC_LIST
    READ_STAMP
    are three new function modules which will be supplied with the next version of ST-PI. The next version of ST-PI is currently scheduled to be released in mid December. For the moment, the only thing to do is to ignore those errors until the next ST-PI becomes available.
    best regards,
    -David.

  • Failed to instantiate file "v4.master" from module "DefaultMasterPage": Source path "v4.master" not found.

    Brand new install of SharePoint 2013. No modifications. Made one collection from the Admin site.
    I attempt to create a sub-site.
    Sorry,
    something went wrong
    Failed to instantiate file
    "v4.master" from module "DefaultMasterPage": Source path "v4.master" not
    found.
    David Jenkins

    Hi David,
    Here is the reference for using ULS log:
    http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx
    Regards,
    Rebecca Tu
    TechNet Community Support

  • TABLE VALUED FUNCTION - PARAMETER NOT WORK

    This is the code i have written
    CREATE FUNCTION GETSQL_GL5203(@FORPERIOD AS CHAR)
    RETURNS TABLE
    AS
    RETURN 
    SELECT-- TOP 1000
     --[GLBranch]
         -- ,[accountno]
     glbranch+ '-'+ accountno AS EMBACC
          ,[PERIOD]
          ,[TOTALBAL]
      FROM [EmbraceData].[dbo].[GLbybranchPERIODBAL  ]
      WHERE LEFT(GLBRANCH,2) <> 'TC'
      AND SUBSTRING (GLBRANCH,3,2) <> '00'
      AND [PERIOD] <> @FORPERIOD --'2015-03' 
    --  ORDER BY GLBRANCH
     -- ,ACCOUNTNO--
      --,[PERIOD]
      GO
    when i call the function  as below it is giving me all the information and ignoring the period selection.   When i am running just the body of the query using '2015-03' as the value on the period it is working fine.
      SELECT * FROM GETSQL_GL5203 ('2015-03') AS LIVE

    You need to provide the size for your function parameter
    Try the below:
    CREATE FUNCTION GETSQL_GL5203(@FORPERIOD AS
    CHAR(20))
    RETURNS TABLE
    AS
    RETURN 
    SELECT-- TOP 1000
     --[GLBranch]
         -- ,[accountno]
     glbranch+ '-'+ accountno AS EMBACC
          ,[PERIOD]
          ,[TOTALBAL]
      FROM [EmbraceData].[dbo].[GLbybranchPERIODBAL  ]
      WHERE LEFT(GLBRANCH,2) <> 'TC'
      AND SUBSTRING (GLBRANCH,3,2) <> '00'
      AND [PERIOD] <> @FORPERIOD --'2015-03' 
    --  ORDER BY GLBRANCH
     -- ,ACCOUNTNO--
      --,[PERIOD]
      GO

  • APEX - Can't "Create" table.  Get "Page Not Found Error"

    I am trying to create a table with Oracle's APEX (at apex.oracle.com). When I run through the wizard and final process asks me to hit "create", the frame should state "table created", but instead it says Page Not Found. I have tried restarting the browser and also moved to another computer to see if it was a settings issue, but still receive this. I have emailed Oracle about it, but have not heard back, so thought I'd try here.
    Thanks for any help in Advance.

    My first name is Tyler
    I sent my question to [email protected]
    My email address is [email protected], I used this when contacting oracle, I also contacted with [email protected]
    I tried creating the table through the wizard with just two columns, 1 number column and 1 varchar2() field. I did not create a pk or any constraints, to see if I could just get a bare minimum table created. Unsuccessfully.
    I tried using the create DDL script in the SQL command window in APEX, this also was unsuccessfull. It seems to hang for a couple of minutes, I assumed it was just taking a bit to execute the DDL. But when it "unhangs", the status window below says it's still "executing sql statment", but it does not do anything after that, it stays there.
    I went and checked if by chance the table had been created, but it hadn't.
    Thanks,
    Tyler

  • G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

    i am getting the dump.
    the fuction module is not presend in ECC 5.0
    Runtime Errors         CALL_FUNCTION_NOT_FOUND                                                     
    Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC                                                 
    Date and Time          04/05/2007 07:13:25                                                         
    ShrtText                                                                               
    Function module "G_G_IDOC_REC_ZZINCOT" not found.                                             
    What happened?                                                                               
    The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be                          
        found in the Function Library.                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLGUIF" had to be terminated because one of the                   
        statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                         
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                      
        and make a note of the actions and input that caused the                                      
        error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                
        You can use transaction ST22 (ABAP Dump Analysis) to view and administer                      
         termination messages, especially those beyond their normal deletion                          
        date.                                                                               
    is especially useful if you want to keep a particular message.                                
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                      
        . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',                
         was neither                                                                               
    caught nor passed along using a RAISING clause, in the procedure                              
         "IDOC_INPUT_GLROLL" "(FUNCTION)"                                                             
    Since the caller of the procedure could not have expected this exception                      
         to occur, the running program was terminated.                                                
        The reason for the exception is:                                                              
        The program "SAPLGUIF" contains a CALL FUNCTION statement. The name                           
        of the function module to be called is "G_G_IDOC_REC_ZZINCOT".                                                                               
    No function module exists with the name "G_G_IDOC_REC_ZZINCOT".                               
        All function modules are stored in the Function Library (SE37).                                                                               
    Possible reasons:                                                                               
    a) Wrong name specified. Particular attention should be paid                                  
           to upper/lower case and underscores ("_")                                                  
        b) Transport error                                                                               
    c) If an enqueue/dequeue module has been used, the lock object                                
           may not have been activated (ABAP Dictionary)                                              
           may not have been activated (ABAP Dictionary).                                             
    How to correct the error                                                                               
    Check the last transports to the R/3 System.                                                  
        Is the program "SAPLGUIF" currently being changed?                                            
        If an enqueue/dequeue module is involved, is the activation                                   
        of the lock object missing in the ABAP/4 Dictionary?                                                                               
    You may able to find an interim solution to the problem                                       
        in the SAP note system. If you have access to the note system yourself,                       
        use the following search criteria:                                                                               
    "CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC                                        
        "SAPLGUIF" or "LGUIFU05"                                                                      
        "IDOC_INPUT_GLROLL"                                                                               
    Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":                                                                               
    G_G_IDOC_REC_COFIT                                                                               
    G_G_IDOC_REC_FILCT                                                                               
    G_G_IDOC_REC_ECMCT                                                                               
    G_G_IDOC_REC_GLPCT                                                                               
    G_G_IDOC_REC_GLT0                                                                               
    G_G_IDOC_REC_SECURE                                                                               
    G_POSTING_ZZINCOT                                                                               
    G_G_IDOC_SEND_COFIT                                                                               
    G_G_IDOC_SEND_ECMCT                                                                               
    G_G_IDOC_SEND_SECURE                                                                               
    If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                                                               
    1. A printout of the problem description (short dump)                                         
           To obtain this, select in the current display "System->List->                              
           Save->Local File (unconverted)".                                                                               
    2. A suitable printout of the system log                                                      
           To obtain this, call the system log through transaction SM21.                              
           Limit the time interval to 10 minutes before and 5 minutes                                 
           after the short dump. In the display, then select the function                             
           "System->List->Save->Local File (unconverted)".                                                                               
    3. If the programs are your own programs or modified SAP programs,                            
           supply the source code.                                                                    
           To do this, select the Editor function "Further Utilities->                                
           Upload/Download->Download".                                                                               
    4. Details regarding the conditions under which the error occurred                            
           or which actions and input led to the error.                                               
        The exception must either be prevented, caught within the procedure                           
         "IDOC_INPUT_GLROLL"                                                                               
    "(FUNCTION)", or declared in the procedure's RAISING clause.                                  
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "d48ix100"                                                          
        Network address.......... "151.162.153.62"                                                    
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "00C65EFD4C00"                                                      
        Character length......... 8 Bits                                                              
        Pointer length........... 64 Bits                                                             
        Work process number...... 2                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "d48ix100"                                                          
        Database type............ "ORACLE"                                                            
        Database name............ "D48"                                                               
        Database owner........... "SAPR3"                                                                               
    Character set............ "en_US.ISO8859-1"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Nov 5 2006 20:46:58"                                               
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "156"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16128                                                               
        EM....................... 8379856                                                             
        Heap..................... 0                                                                   
        Page..................... 16384                                                               
        MM Used.................. 2530176                                                             
        MM Free.................. 1657232                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 010                                                                      
        User................ "OS0730"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "YICUPLD "                                                               
        Program............. "SAPLGUIF"                                                               
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".               
        The main program was "Y21091IRECON ".                                                                               
    The termination occurred in line 65 of the source code of the (Include)                       
         program "LGUIFU05"                                                                               
    of the source code of program "LGUIFU05" (when calling the editor 650).                       
        Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"                 
         occurred in the                                                                               
    procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not                   
         declared in the                                                                               
    RAISING clause of the procedure.                                                              
        The procedure is in the program "SAPLGUIF ". Its source code starts in line 5                 
        of the (Include) program "LGUIF$05 ".                                                         
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    35                                                                               
    36 *Prüfen, ob Customizing richtig eingestellt ist                                             
       37     CHECK EXIT IS INITIAL.                                                                  
       38     PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.                                            
       39                                                                               
    40 *Für Einzelposten neue Belegnummern vergeben                                                
       41     CHECK EXIT IS INITIAL.                                                                  
       42     PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER                                           
       43                                       IDOC_CONTRL-MESTYP.                                   
       44                                                                               
    45 *Füllen der Segmentdaten                                                                    
       46     CHECK EXIT IS INITIAL.                                                                  
       47     CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.                                               
       48                                                                               
    49     LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.                                          
       50       IDOC_SEGMENT = IDOC_DATA.                                                             
       51       APPEND IDOC_SEGMENT.                                                                  
       52     ENDLOOP.                                                                               
    53                                                                               
    54 *Name des zu rufenden Funktionsbausteines ermitteln                                         
       55     ROL_FUNCNAME = 'G_G_IDOC_REC_$'.                                                        
       56     PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.                              
       57                                                                               
    58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen                                        
       59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB                                     
       60     IF NOT E1GLTTF-TAB30 IS INITIAL.                                                        
       61       L_TAB30 = E1GLTTF-TAB30.                                                              
       62     ELSE.                                                                               
    63       L_TAB30 = E1GLTTF-TAB.                                                                
       64     ENDIF.                                                                               
    >>>>>     CALL FUNCTION ROL_FUNCNAME                                                              
       66          EXPORTING                                                                          
       67               MESTYP             = IDOC_CONTRL-MESTYP                                       
       68               DOCNUM             = IDOC_NUMBER                                              
       69               TAB                = L_TAB30                                                  
       70          TABLES                                                                               
    71               IDOC_SEGMENT       = IDOC_SEGMENT                                             
       72               IDOC_STATUS        = IDOC_STATUS                                              
       73               RETURN_VARIABLES   = RETURN_VARIABLES.                                        
       74                                                                               
    75   ENDLOOP.                                                                               
    76                                                                               
    77 *Keine IDOC's empfangen                                                                     
       78   IF SY-SUBRC NE 0.                                                                         
       79     RAISE WF_ERROR_PROCESS.                                                                 
       80   ELSE.                                                                               
    81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind                          
       82     LOOP AT IDOC_STATUS WHERE MSGTY = 'A'                                                   
       83                            OR MSGTY = 'E'.                                                  
       84       EXIT.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 2                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 0                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                           &

    I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
    If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error

  • SourceSet in function (Jscript) not found any Data View

    HI,
    I have the code:
    var = oDB xfa.sourceSet.DataConnection.clone (1);
    oDB.nodes.item (1). query.setAttribute ("text", "CommandType");
    oDB.nodes.item (1). query.select.nodes.item (0). value = "SELECT * FROM vw_products";
    oDB.open ();
    oDB.close ();
    This code works perfectly if I call in initialize the form.
    (form1.Inicial::initialize - (JavaScript, both))
    But the same code does not work if I call a function in Jscript, (Function test {} for example). Not found "sourceSet.DataConnection".
    Any idea what could be? I've tried everything but it only works if i put in initialize the page.

    And a further example from my library of examples, just to help you out...
    SQL> CREATE OR REPLACE TYPE num_descript AS OBJECT(num number, descript varchar2(30))
      2  /
    Type created.
    SQL> CREATE OR REPLACE TYPE tbl_num_descript AS TABLE OF num_descript
      2  /
    Type created.
    SQL> CREATE OR REPLACE PACKAGE reftest AS
      2    FUNCTION pipedata(p_choice number) RETURN tbl_num_descript PIPELINED;
      3  END;
      4  /
    Package created.
    SQL> CREATE OR REPLACE PACKAGE BODY reftest AS
      2    FUNCTION pipedata(p_choice number) RETURN tbl_num_descript PIPELINED IS
      3      v_obj num_descript := num_descript(NULL,NULL);
      4      v_rc  sys_refcursor;
      5    BEGIN
      6      IF p_choice = 1 THEN
      7        OPEN v_rc FOR SELECT empno as num, ename as descript FROM emp;
      8      ELSIF p_choice = 2 THEN
      9        OPEN v_rc FOR SELECT deptno as num, dname as descript FROM dept;
    10      END IF;
    11      LOOP
    12        FETCH v_rc INTO v_obj.num, v_obj.descript;
    13        EXIT WHEN v_rc%NOTFOUND;
    14        PIPE ROW(v_obj);
    15      END LOOP;
    16      CLOSE v_rc;
    17      RETURN;
    18    END;
    19  END;
    20  /
    Package body created.
    SQL> select * from table(reftest.pipedata(1));
           NUM DESCRIPT
          7369 SMITH
          7499 ALLEN
          7521 WARD
          7566 JONES
          7654 MARTIN
          7698 BLAKE
          7782 CLARK
          7788 SCOTT
          7839 KING
          7844 TURNER
          7876 ADAMS
          7900 JAMES
          7902 FORD
          7934 MILLER
    14 rows selected.
    SQL> select * from table(reftest.pipedata(2));
           NUM DESCRIPT
            10 ACCOUNTING
            20 RESEARCH
            30 SALES
            40 OPERATIONS

  • Shared library: function is not found and recognized in header file

    Hello,
    I am trying to use Java methods into LV. I am doing so by creating Java Invocation Interface, usind which I can call Java methods into C++ and then create a shared library that can be called into LV.
    When I am importing my shared library into Labview, I am getting the following error messages:
    The shared library contains 3 function(s). But no function is found and recognized in the header file. The following function(s) cannot be wrapped. If you want to import these functions, please review the warning messages next to the functions below. You will need to fix the problems before you can continue with the wizard.
    jclass invokeJavaClass(JNIEnv* jenv, string className);
    The following symbols are not defined:
    jclass;
    Undefined symbols can prevent the wizard from recognizing functions and parameters. To correct this problem, check the header file to determine if you must add preprocessor definitions. Click the Back button to return to the previous page of the wizard to add a preprocessor definitionsl (for example, "NIAPI_stdcall = __stdcall" or "NIAPIDefined = 1").
    The following header file was not found in the specified header file or one of the referenced header files:
    -  string
    -  iostream
    -  cstring
    -  jni.h
    To fix, click the Back button to go to the previous page and add the header file path to the Include Paths list.
     Please advise.
    Regards,
    H
    Attachments:
    SharedLibError.png ‏51 KB

    Hello Vivek,
    The LabVIEW dll that I am trying to import does not include any third-party device..all my code is fully based on LabVIEW. Maybe this helps you to guess what is happening: once I've parsed the dll' header appears an error
    like this one:
    void
    __cdecl Zdmt(LVBoolean *stop, double P, char channelName[],
        TD1
    *errorIn, TD14 *FFTOptions, TD12 *Calibration, char FileName[],
    int32_t minRecordLength, TD26 *InstrumentHandler, LVRefNum
    sessionRefArray[],
        LVRefNum *queueIN, TD1 *errorOut, LVBoolean
    *averagingDone,
        HWAVES LastRecordFetched, TD24 *Impedance, TD17
    *ColeColeCluster,
        TD18 *FFTcluster, TD5
    *InstrumentHandleOutputCluster, LVRefNum *queueOut,
        int32_t
    *Acquired, TD6 *FreqTimeInfoCluster, double *averagesCompleted,
    int32_t len);
    The following symbols are not defined:
    LVBoolean;
    int32_t; LVRefNum;
    Undefined symbols can prevent the wizard
    from recognizing functions and parameters. To correct this problem,
    check the header file to determine if you must add predefined symbols.
    Click the Back button to return to the previous page of the wizard to
    add a preprocessor definitionsl (for example, "NIAPI_stdcall =
    __stdcall" or "NIAPIDefined = 1").
    The following header file was
    not found in the specified header file or one of the referenced header
    files:
    -  extcode.h
    To fix, click the Back button to go to the
    previous page and add the header file path to the Include Paths list.
    I have replaced the first line #include "extcode.h" of
    the dll header file for #include "C:\Program Files\National
    Instruments\LabVIEW 8.6\cintools\extcode.h" that is the full path where
    the header file is located. However, new libraries seems to be missed:
    -  stdint.h
    -  MacTypes.h
    As far as I know,  Mactypes.h contains basic mac os data types and it doesn't have any relation with stdint.h...
    I have created both of them and stored into the same folder as extcode.h, but then other libraries are missed!!!
    Do you know if it would be possible to create the .dll generating all the header files associated for its data structures???
    And if this is not factible, then what do you suggest me? because I hope to not having to create all the header files until it stops giving me an error!
    thanks for four time,
    ben

  • Smartforms.. Function Module not found.. fm_name when tried in the SE38

    Hi all,
    I created the form using the smartforms, check it and activated it.  I can see the unique function module is assigned to the form.  I wrote the ABAP program and declared the data types, but when I called the function module fm_name, the system is saying that fm does not exits..My program looks like this in short:
    data fm_name type rs38l_fnam.
    parameter: p_form   type tdsfname   default 'zashok01'.
    where Zashok01 is the form name.
    print data
      call function 'SSF_FUNCTION_MODULE_NAME'
           exporting  formname           = p_form
                    variant            = ' '
                    direct_call        = ' '
           importing  fm_name            = fm_name
           exceptions no_form            = 1
                      no_function_module = 2
                      others             = 3.
    now after this, when I am calling the function module fm_name to get the generated FM for the form, the system gives a note that FM does not exits..
    Can anyone find me the result.. Do I need to create a new FM or what??? or is there anything wrong with my codes to assign the name of FM.
    Waiting for your replies..
    Regards,
       -Ashok Hansraj

    hi,
    correct the following things
    1. parameter: p_form type tdsfname default 'ZASHOK01'.
    2. check fm name in Smartform - > Environment - > function module name
    3. copy name of the function module and call from the program like
    CALL FUNCTION '/1BCDWB/SF00000003'
    IMPORTING
      DOCUMENT_OUTPUT_INFO       =
      JOB_OUTPUT_INFO            =
      JOB_OUTPUT_OPTIONS         =
    then replace '/1BCDWB/SF00000003' to fm_name like below
    CALL FUNCTION fm_name
    IMPORTING
      DOCUMENT_OUTPUT_INFO       =
      JOB_OUTPUT_INFO            =
      JOB_OUTPUT_OPTIONS         =
    cheers,
    sasi

Maybe you are looking for

  • Can not attach any files to one of my accounts

    Hello i seem to have problems with attachments. I have 5 e-mail accounts with mail. on 4 of them i can not put attachments. I have to first use the one account which i can add attachment and then change over to the other account any idea

  • Email notifications not being sent - SORRY - WRONG FORUM!  PLEASE DELETE!

    Hello all - I have two Mac Mini Servers - both running 10.6.5 One server is within my LAN and behind an Apple Airport Extreme which is acting as a router. The other server is collocated and has a direct connection to the internet. It is running the s

  • Mapping Problem  ( IDoc to File  )

    Hi, I am working on Idoc to file scenario...My input and output structures like below... Idoc: ZOrderInfo        1----99999     OrderNumber 0---1      ZItem       1----99999      Quantity       0---1 File: Item    OrderNumber  0-1    Quantity        

  • Fixed due date for billing created in a period

    Hi We want the new payment tem that should work in the following way Billing date from 01.01.2008 to 31.03.2008 due date should be 20.04.2008 Billing date from 01.04.2008 to 30.06.2008 due date should be 20.07.2008 Please note that the billing period

  • Activations can not be deactivated?

    Abode support called me after putting in a request to reset my activations and told me two things - it was not possible to reset my activation (I need to create a new account and lose the content on my PC) and the ctrl+shift e will deactivate the dev