Copy the function module

Hi,
can you suggest me how can i copy the function group.
for example:Zfun_01  having 10 objects and i need all the objects to Zfun_02 function group.
I tried from SE80 but I didnt get copied.
Thanks,
Sriiii.

Hi
Check the below thread the same issue is discussed
Re: Function-Group
Regards
Pavan

Similar Messages

  • Problem in copying the function module.

    Hi All,
    I have to Copy the standard function modules "FI_ITEMS_DISPLAY" and "ITEM_DERIVE_FIELDS".
    The Function group for both of above FM is "FI_ITEMS".
    What i did is I went to SE80 ,I copied down the Function Group 'FI_ITEMS' to 'ZFI_ITEMS'.
    later on i copied the standard function modules 'FI_ITEMS_DISPLAY' and 'ITEM_DERIVE_FIELDS'
    to the 'ZFI_ITEMS_DISPLAY' and 'ZITEM_DERIVE_FIELDS' resp.in the same function group 'ZFI_ITEMS'.
    Then i made some changes to these copied modules (I did change the structure of it_items from RFPOSXEXT to ZRFPOSXEXT in ZFI_ITEM_ITEM_DISPLAY,and same change in ZITEM_DERIVE_FIELDS but for the parameter s_item).
    And finally i activated these FM..and it got activated also.
    But later on when i used these FM in my report...error occured saying that -
      "The name of the function module to be called is "ZITEM_DERIVE_FIELDS".
    but "ZITEM_DERIVE_FIELDS" cannot be found in its function group. "
        hence i thought of activating the function group ZFI_ITEMS,which was inactive before to this...but when i tried activatin this FM it was giving hell lot of errors showing conflict occured at diffrent places,I think just because of the change (structure of IT_ITEM chnged from RFPOSEXT to customised ZZRFPOSXEXT).
    I am helpless in removing all this errors ...
    Can anybody suggest where did i go wrong?
    And what is the right way to copy the function module.?
    If possible reply me ASAP.
    Thanx in advance.

    Hello Sanjay,
    First, delete your new function group and
    Do like this:
    1. copy FI_ITEMS_DISPLAY to zFI_ITEMS_DISPLAY from Se37. here you find a button on the application toolbar to do it. It also asks about the Function group. GIve the FG as
    ZFI_ITEMS.
    Activate all the related objects
    2. same for the other FM. Use the same FG. and activate the related objects.
    Regards,
    Naimesh

  • Copy the Function Module one server to another server

    Hi Guy's,
    Please help me How to copy the Function module from one server to another server.
    Present requirement is like this, copy the FM from DRH-100 to NRH-100.
    Thanks and Regards,
    Sai

    if it is a zfm, u might have assigned a TR when cretaing this FM.so u need to relese this TR to the desired system.contact ur BASIS for the transport lanscape.
    if it is a standard FM, u better copy this FM to a ZFM and make it as RFC enabled if it is not RFC enabled and call this ZFM from the system in which want to call this FM by giving the logical system id in the destination while calling this FM.

  • Error while copy the function module

    Hi,
    When am copying the some standard FM into my z function module and when am checking the syntex error it throwing the error "REPORT/PROGRAM statement missing, or program type is I (INCLUDE).".
    Can you suggest.

    Hi All,
    Thanks for your help.
    Finally i did by my own.
    the problem is we need to activate their mail program and all include which we can see in goto>main program.
    Amit.

  • Client copy Locked function module

    HI,
    I'm trying to make a client from client 400 to 420.
    The problem is that the function module is locked by the current user (the same running the client copy); Then when It can't deletes the FM it states that it already exists:
    "G_GLDB_POSTING_A already exists (include LGIVAU01)"
    Afterwards the job gets cancelled due to a system exception ERROR_MESSAGE
    The weird part is that it just happens for this client 420. There is also a copy from 400 to 410 and it works without a problem.
    Any help would be greatly appreciated.

    Hi,
    You can check the client copy lock from SCC4 also, but it really matters if your client copy finished or not.
    If you still see the client copy lock there then it seems your client copy is not finished properly. Try to login your new client 420 and start deletion using SCC5 and after that you can start/schedule new client copy during weekends.
    Regards,
    Manish

  • WBS copy via function module "K_PLAN_TO_PLAN_COPY"

    Hi Experts
    anybody please advise whether WBS copy to other via function module "K_PLAN_TO_PLAN_COPY"
    is possible or not in below situation.
    Currently we faced some issue when WBS satus is "TECO", we can not
    copy WBS to another WBS (we want to copy whole wbs into others) by
    function module "K_PLAN_TO_PLAN_COPY".
    So we just change system status from TECO to REL then copy wbs to other,
    however, we could face another issue with this way of copying. (since we
    have to change wbs status, it could cause conflict against other project)
    We want to copy wbs without changing wbs status via function module "K_PLAN_TO_PLAN_COPY".
    Can it be possible? if yes, please advise how to, (settings/conditions/something like that)
    Thank you.
    Satoru

    Hi Satoru,
    The Function Module K_PLAN_TO_PLAN_COPY is not released for customers and therefore it is not intended to be used in customer specific programs or enhancements. For further details, please have a look SAP Note 109533.
    Sorry for not having better news.
    BR,
    Enrique

  • Error in copy of function module  FIEB_PASSWORD_ENCRYPT as a Z FM

    Hi Gurus,
    I want to make a copy of function module  FIEB_PASSWORD_ENCRYPT as a Z FM.
    but after coping standard FM when i am trying to activete it ,it is showing one error
    *form decrypt_password does not exist.*
    if possible give me the solution step by step.
    Regards,
    Susheel Joshi

    do something susheel,
    create an empty function group:ZFIEB_PASSWORD.
    Now in the attribute of your ZFM, just add this name (ZFIEB_PASSWORD)in the FUNCTION GROUP section.
    in the main program of this FG-- (ZFIEB_PASSWORD)i, copy the includes given in function group:FIEB_PASSWORD.
    Add these codes:
    *   System-defined Include-files.                                 *
      INCLUDE LFIEB_PASSWORDTOP.                 " Global Data
      INCLUDE LFIEB_PASSWORDUXX.                 " Function Modules
    *   User-defined Include-files (if necessary).                    *
    * INCLUDE LFIEB_PASSWORDF...                 " Subprograms
    * INCLUDE LFIEB_PASSWORDO...                 " PBO-Modules
    * INCLUDE LFIEB_PASSWORDI...                 " PAI-Modules
    INCLUDE LFIEB_PASSWORDF01.
    the intension is to copy all the includes from this pool.
    you should be able to do it now
    ags.n
    Edited by: ags on Oct 30, 2009 3:19 PM

  • Problem with i_buffer_active in the function module

    i_buffer_active in the function module "REUSE_ALV_FIELDCATALOG_MERGE"  
    hi folks,
    i am using this  function module "REUSE_ALV_FIELDCATALOG_MERGE" to develop a field catalog....but teh problem is that when i use this i_buffer_active and if a assign value 'X' to that parameter .......teh entire structure is not getting copied in to teh field catalog ...........and when i comment the line i_buffer active ........teh entire structure i sgetting copied ..........so can u guys please with ur valuable suggestion, the program name is RFITEMAP

    Hi!
    Check out the program BCALV_TEST_BUFFER.
    Regards
    Tamá

  • Copy Standard Function modules  to Z Function modules

    Hello,
    I have a requirement like , I need have a typical requirement where i need to copy few function modules in the same function group , in  this regard i copied 4 function module and calling performs with the program name , but i am unable to achive the requirement , Function module is getting Dump,
    Can any one explain the standarded function modules and place it in Z function group. or is it possible to include standard function group in to Z function group ?
    How to get reslove ?  please guide ...
    Thanks In Advance.
    With Best Regards
    Naganjaneyulu.P.V

    Hi Naganjaneyulu,
    If you copy it will be similar to Standard. But you can modify those FMs as you like which will not be possible in standard. Also if you solely copy the FM, If that FM consists or depends on the screens or Includes which are present in the Function Group then there will be syntax errors and shortdumps. The Reason for your short dump might be this.
    If you are still not happy with this approach, Kindly paste the standard FM that you are trying to clone and the short dump that you are encountering.
    Thanks,
    Sai

  • What is the function module used to send an email

    hi
    what is the function module used to send an email

    Hello,
    Try this, It will help you. Sure.
    Regards,
    Rakesh.
    CLASS cl_abap_char_utilities DEFINITION LOAD.
      CONSTANTS:
      con_tab TYPE c VALUE cl_abap_char_utilities=>horizontal_tab,
      con_cret TYPE c VALUE cl_abap_char_utilities=>cr_lf.
      TYPES: BEGIN OF typ_item,
             asno(10) TYPE c,
             matnr TYPE mseg-matnr,
             maktx TYPE makt-maktx,
             menge TYPE mseg-menge,
             meins TYPE mseg-meins,
             END OF typ_item.
      DATA: wrk_menge(17) TYPE c.
      DATA: sum_srno TYPE i VALUE 0.
      DATA: wrk_srno TYPE n.
    *Internal tables
      DATA: it_std_objhdr  TYPE TABLE OF solisti1.
      DATA: it_std_objcnt  TYPE TABLE OF solisti1.
      DATA: it_std_rcvlst  TYPE TABLE OF somlreci1.
      DATA: it_std_objtxt  TYPE TABLE OF solisti1..
      DATA: it_std_objpack TYPE TABLE OF sopcklsti1 .
      DATA: it_std_cntbin  TYPE TABLE OF solisti1.
      DATA: it_std_items TYPE TABLE OF typ_item.
      DATA: is_items LIKE LINE OF it_std_items.
    *  DATA: it_attachment LIKE solisti1 OCCURS 0 WITH HEADER LINE.
    *  DATA: wa_attachment TYPE solisti1.
    * Internal structures
      DATA: is_docdata LIKE sodocchgi1.
      DATA: is_objhdr  LIKE LINE OF it_std_objhdr.
      DATA: is_objcnt  LIKE LINE OF it_std_objcnt.
      DATA: is_rcvlst  LIKE LINE OF it_std_rcvlst.
      DATA: is_objtxt  LIKE LINE OF it_std_objtxt.
      DATA: is_objpack LIKE LINE OF it_std_objpack.
      DATA: is_cntbin  LIKE LINE OF it_std_cntbin.
    *Work variables
      DATA: wrk_lines TYPE i.
      is_docdata-obj_descr = 'Movement of parts to processor'.
    *Cover letter of the mail
      is_objtxt = 'Dear Sir,'.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = ' '.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = text-001.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = text-002.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = text-003.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = ' '.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = 'Thanks n Regards,'.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = ' '.
      APPEND is_objtxt TO it_std_objtxt.
      is_objtxt = 'abc MOTORS'.
      APPEND is_objtxt TO it_std_objtxt.
    * Write Packing List (Main)
      DESCRIBE TABLE it_std_objtxt LINES wrk_lines.
      READ TABLE it_std_objtxt INTO is_objtxt INDEX wrk_lines.
      is_docdata-doc_size = ( wrk_lines - 1 ) * 255 + STRLEN( is_objtxt ).
      CLEAR is_objpack-transf_bin.
      is_objpack-head_start = 1.
      is_objpack-head_num   = 0.
      is_objpack-body_start = 1.
      is_objpack-body_num   = wrk_lines.
      is_objpack-doc_type   = 'RAW'.
      APPEND is_objpack TO it_std_objpack.
      BREAK-POINT.
    *loop for selecting the data into contents bin//// Excel.
      CONCATENATE 'SRNO' 'ASN no:' 'PARTNO' 'PART DESCRIPTION'
                  'QUANTITY' 'UNIT' INTO is_cntbin
      SEPARATED BY con_tab.
      CONCATENATE con_cret is_cntbin INTO is_cntbin.
      APPEND is_cntbin TO it_std_cntbin.
      LOOP AT it_std_items INTO is_items.
        sum_srno = sum_srno + 1.
        wrk_menge = is_items-menge.
        wrk_srno  = sum_srno.
        CONCATENATE wrk_srno is_items-asno is_items-matnr is_items-maktx
        wrk_menge is_items-meins
        INTO is_cntbin SEPARATED BY con_tab.
        CONCATENATE con_cret is_cntbin INTO is_cntbin.
        APPEND is_cntbin TO it_std_cntbin.
      ENDLOOP.
    *To be implemented later
    *  CONCATENATE 'EBELN' 'EBELP' 'AEDAT' 'MATNR'
    *  INTO it_attach SEPARATED BY con_tab.
    *  CONCATENATE con_cret it_attach INTO it_attach.
    *  APPEND it_attach.
    *  LOOP AT it_ekpo INTO wa_charekpo.
    *    CONCATENATE wa_charekpo-ebeln wa_charekpo-ebelp
    *    wa_charekpo-aedat wa_charekpo-matnr
    *    INTO it_attach SEPARATED BY con_tab.
    *    CONCATENATE con_cret it_attach INTO it_attach.
    *    APPEND it_attach.
    *  ENDLOOP.
    *ENDFORM. " BUILD_XLS_DATA_TABLE
      DESCRIBE TABLE it_std_cntbin LINES wrk_lines.
      READ TABLE it_std_cntbin INTO is_cntbin INDEX wrk_lines.
      is_objpack-doc_size   = ( wrk_lines - 1 ) * 255 +
                               STRLEN( is_cntbin ).
      is_objpack-transf_bin = 'X'.
      is_objpack-head_start = 1.
      is_objpack-head_num   = 0.
      is_objpack-body_start = 1.
      is_objpack-body_num   = wrk_lines.
      is_objpack-doc_type   = 'XLS'.
      is_objpack-obj_name   = 'Document File'.
      is_objpack-obj_descr  = 'Document File'.
      APPEND is_objpack TO it_std_objpack.
    *Start of testing code
      IF sy-uname = 'DEVELOPER'.
        is_rcvlst-receiver = sy-uname.
        is_rcvlst-rec_type = 'B'.
        is_rcvlst-express  = 'X'.
        APPEND is_rcvlst TO it_std_rcvlst.
        CLEAR is_rcvlst.
      ENDIF.
    *End of testing code
    *Creating the recepient list
      is_rcvlst-receiver = '[email protected]'.
      is_rcvlst-rec_type = 'U'.
      is_rcvlst-express  = 'X'.
      is_rcvlst-com_type = 'INT'.
      APPEND is_rcvlst TO it_std_rcvlst.
      is_rcvlst-receiver = '[email protected]'.
      is_rcvlst-copy     = 'X'.
      is_rcvlst-rec_type = 'U'.
      is_rcvlst-express  = 'X'.
      is_rcvlst-com_type = 'INT'.
      APPEND is_rcvlst TO it_std_rcvlst.
      BREAK-POINT.
      CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
        EXPORTING
          document_data                    = is_docdata
       put_in_outbox                    = 'X'
       commit_work                      = 'X'
    * IMPORTING
    *   SENT_TO_ALL                      =
    *   NEW_OBJECT_ID                    =
        TABLES
          packing_list                     = it_std_objpack
    *   OBJECT_HEADER                    =
       contents_bin                     = it_std_cntbin
       contents_txt                     = it_std_objtxt
    *   CONTENTS_HEX                     =
    *   OBJECT_PARA                      =
    *   OBJECT_PARB                      =
          receivers                        = it_std_rcvlst
    * EXCEPTIONS
    *   TOO_MANY_RECEIVERS               = 1
    *   DOCUMENT_NOT_SENT                = 2
    *   DOCUMENT_TYPE_NOT_EXIST          = 3
    *   OPERATION_NO_AUTHORIZATION       = 4
    *   PARAMETER_ERROR                  = 5
    *   X_ERROR                          = 6
    *   ENQUEUE_ERROR                    = 7
    *   OTHERS                           = 8
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      COMMIT WORK.

  • Error during generation of the function module..need help urgently

    Hello everyone,
                            m trying to generate data source in BWDevelopment.
    After mapping all the BW fields to Source Object elements I click on Generate DataSource(for UD Connect) so following error comes
    'An error occurred in step 1 during generation of the function module'
    RFC connection is fine, error free and extractor is also fine.
    Where could be the problem?
    Thanks & Regards,
    Priyanka

    Hello everybody,
                             my problem is solved.For the UDConnect, whatever DATA SOURCES you create gets registered in a FUNCTION MODULE which has a capacity of only 99 enties, so to increase it implement the SAP NOTE 876340 - UDC Error available on SERVICE MARKET PLACE.
    This problem occurs with BW version 3.5 level 17 or below.
    Regards,
    Priyanka
    Edited by: Priyanka Joshi on Jun 10, 2008 11:03 AM

  • Jobs to run the function modules to extract the generic extarctors

    Gurus,
    I have a Datasource 'ZCMS_PP_TRAN' with extract structure 'ZBW_ST_CMSD_PP'. The extract structure is populated using the function module Z_BW_GET_CMSD_PP.
    But how do I schedule this FM or in general, are they run using std programs?
    Thanks,
    Simmi

    Hi Simmi,
       what ever it may be the DS(i mean Business Content DS, Generic DS).... these will extract the Data using Dynamic Function Calls(not always). Comming to Generic DS using FM, this will be called using Dynamic Function Module.
    In RSA3 or while extracting data from BW, you will pass request number, Update Mode, debugging option, selection fields, BW source System ID, DS Name.
    Based on these details system will extract the underlying extract structure and function module(or table/view/infoset).
    No job(Job created from BW while extracting data in the source system BI_requestid) created for Generic DS while extracting data in SAP.
    For Queue Delta, Background job will be created, it will move the data to Delta Queue.
    i will update the thread with related function modules. Try to debugg in RSA3, you could find all the information.
    all the best.
    Nagesh.

  • Not able to use Commit after the function module STATUS_OBJECT_CREATE

    I am using function module   STATUS_OBJECT_CREATE
       CALL FUNCTION 'STATUS_OBJECT_CREATE'
              EXPORTING
               CHGKZ         = 'X'
               CLIENT        = SY-MANDT
                OBJNR         = LV_OBJNR3
                OBTYP         = 'IWE'
                STSMA         = 'ZS_RE_01'
              IMPORTING
                OBJNR         = LV_OBJNR3.
                STONR                        = LV_STONR.
            IF SY-SUBRC = 0.
                COMMIT WORK.
            ENDIF.
    i am getting error after the COMMIT WORK .
    I am not getting any issue in the function module .after the function module i am using the COMMIT WORK and i am getting the following error message
    Category               ABAP Programming Error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    ABAP Program           SAPLBSVU
    Application Component  CA-GTF-TS-SMT
    Date and Time          03/17/2014 07:01:29
    |Short text                                                                                        |
    |    The ABAP/4 Open SQL array insert results in duplicate database records.                       |
    |What happened?                                                                                    |
    |    Error in the ABAP Application Program                                                         |
    |                                                                                                  |
    |    The current ABAP program "SAPLBSVU" had to be terminated because it has                       |
    |    come across a statement that unfortunately cannot be executed.                                |
    |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                                                                                    |
    |    An exception occurred that is explained in detail below.                                      |
    |    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught                 |
    |     in                                                                                           |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING                    |
    |     clause.                                                                                      |
    |    Since the caller of the procedure could not have anticipated that the                         |
    |    exception would occur, the current program is terminated.                                     |
    |    The reason for the exception is:                                                              |
    |    If you use an ABAP/4 Open SQL array insert to insert a record in                              |
    |    the database and that record already exists with the same key,                                |
    |    this results in a termination.                                                                |
    |                                                                                                  |
    |    (With an ABAP/4 Open SQL single record insert in the same error                               |
    |    situation, processing does not terminate, but SY-SUBRC is set to 4.)                          |
    |How to correct the error                                                                          |
    |    Use an ABAP/4 Open SQL array insert only if you are sure that none of                         |
    |    the records passed already exists in the database.                                            |
    |                                                                                                  |
    |    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:                                                                                     |
    |                                                                                                  |
    |    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"                                              |
    |    "SAPLBSVU" or "LBSVUU01"                                                                      |
    |    "STATUS_UPDATE"                                                                               |
    |                                                                                                  |
    |    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.                                                           |
    |                                                                                                  |
    |    The exception must either be prevented, caught within proedure                                |
    |    "STATUS_UPDATE" "(FUNCTION)", or its possible occurrence must be declared in                  |
    |     the                                                                                          |
    |    RAISING clause of the procedure.                                                              |
    |    To prevent the exception, note the following:                                                 |
    |System environment                                                                                |
    |    SAP Release..... 702                                                                          |
    |    SAP Basis Level. 0010                                                                         |
    |                                                                                                  |
    |    Application server... "sds6ci"                                                                |
    |    Network address...... "11.224.101.53"                                                         |
    |    Operating system..... "Linux"                                                                 |
    |    Release.............. "2.6.18-194.el5"                                                        |
    |    Hardware type........ "x86_64"                                                                |
    |    Character length.... 16 Bits                                                                  |
    |    Pointer length....... 64 Bits                                                                 |
    |    Work process number.. 17                                                                      |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                                  |
    |    Database server... "gctsdb01lds.hsi.hugh"                                                     |
    |    Database type..... "ORACLE"                                                                   |
    |    Database name..... "DS6"                                                                      |
    |    Database user ID.. "SAPDS4"                                                                   |
    |                                                                                                  |
    |    Terminal.......... "GCTEMP02VDI"                                                              |
    |                                                                                                  |
    |    Char.set.... "C"                                                                              |
    |                                                                                                  |
    |    SAP kernel....... 720                                                                         |
    |    created (date)... "Sep 14 2013 05:28:14"                                                      |
    |    create on........ "Linux GNU SLES-9 x86_64 cc4.1.2 use-pr130820"                              |
    |    Database version. "OCI_102, 10.2.0.5.0, V2, default"                                          |
    |                                                                                                  |
    |    Patch level. 500                                                                              |
    |    Patch text.. " "                                                                              |
    |                                                                                                  |
    |    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"               |
    |    SAP database version. 720                                                                     |
    |    Operating system..... "Linux 2.6, Linux 3"                                                    |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 1317248                                                                              |
    |    EM...... 0                                                                                    |
    |    Heap.... 0                                                                                    |
    |    Page.... 0                                                                                    |
    |    MM Used. 1242912                                                                              |
    |    MM Free. 53400                                                                                |
    |User and Transaction                                                                              |
    |    Client.............. 160                                                                      |
    |    User................ "DV018458"                                                               |
    |    Language key........ "E"                                                                      |
    |    Transaction......... "SE38 "                                                                  |
    |    Transaction ID...... "5323C30FC9364665E10000000BE06533"                                       |
    |                                                                                                  |
    |    EPP Whole Context ID.... "002655EE0F241ED3ABB7D81260A28C44"                                   |
    |    EPP Connection ID....... 00000000000000000000000000000000                                     |
    |    EPP Caller Counter...... 0                                                                    |
    |                                                                                                  |
    |    Program............. "SAPLBSVU"                                                               |
    |    Screen.............. "RSM13000 3000"                                                          |
    |    Screen Line......... 2                                                                        |
    |    Debugger Active..... "none"                                                                   |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "SAPLBSVU" - in "STATUS_UPDATE".                     |
    |    The main program was "RSM13000 ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 60                                  |
    |    of the (Include) program "LBSVUU01".                                                          |
    |    The program "SAPLBSVU" was started in the update system.                                      |
    |    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in                   |
    |    procedure "STATUS_UPDATE" "(FUNCTION)", but it was neither handled locally nor                |
    |     declared                                                                                     |
    |    in the RAISING clause of its signature.                                                       |
    |                                                                                                  |
    |    The procedure is in program "SAPLBSVU "; its source code begins in line                       |
    |    1 of the (Include program "LBSVUU01 ".                                                        |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                   |
    |   30|  LOOP AT jsto_upd WHERE chgkz = 'X'.                                                       |
    |   31|    CHECK: jsto_upd-chgnr > '000',                                                          |
    |   32|           jsto_upd-stsma NE jsto_upd-stsma_old.                                            |
    |   33|    CLEAR jcdo_tab.                                                                         |
    |   34|    MOVE-CORRESPONDING jsto_upd TO jcdo_tab.                                                |
    |   35|    MOVE-CORRESPONDING chdat    TO jcdo_tab.                                                |
    |   36|    jcdo_tab-stsma_new = jsto_upd-stsma.                                                    |
    |   37|    APPEND jcdo_tab.                                                                        |
    |   38|  ENDLOOP.                                                                                  |
    |   39|* Änderungen zu Einzelstatus (Insert)                                                       |
    |   40|  LOOP AT jest_ins WHERE chgkz = 'X'.                                                       |
    |   41|    CHECK jest_ins-chgnr > '000'.                                                           |
    |   42|    CLEAR jcds_tab.                                                                         |
    |   43|    MOVE-CORRESPONDING jest_ins TO jcds_tab.                                                |
    |   44|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   45|    jcds_tab-chind = 'I'.                                                                   |
    |   46|    APPEND jcds_tab.                                                                        |
    |   47|  ENDLOOP.                                                                                  |
    |   48|* Änderungen zu Einzelstatus (Update)                                                       |
    |   49|  LOOP AT jest_upd WHERE chgkz = 'X'.                                                       |
    |   50|    CHECK jest_upd-chgnr > '000'.                                                           |
    |   51|    CLEAR jcds_tab.                                                                         |
    |   52|    MOVE-CORRESPONDING jest_upd TO jcds_tab.                                                |
    |   53|    MOVE-CORRESPONDING chdat    TO jcds_tab.                                                |
    |   54|    jcds_tab-chind = 'U'.                                                                   |
    |   55|    APPEND jcds_tab.                                                                        |
    |   56|  ENDLOOP.                                                                                  |
    |   57|* Verbuchung Statusobjekte                                                                  |
    |   58|  DESCRIBE TABLE jsto_ins LINES sy-tabix.                                                   |
    |   59|  IF sy-tabix > 0.                                                                          |
    |>>>>>|    INSERT jsto CLIENT SPECIFIED                                                            |
    |   61|                FROM TABLE jsto_ins.                                                        |
    |   62|  ENDIF.                                                                                    |
    |   63|  DESCRIBE TABLE jsto_upd LINES sy-tabix.                                                   |
    |   64|  IF sy-tabix > 0.                                                                          |
    |   65|    field-symbols <fs_jsto_line> like jsto_upd.                                             |
    |   66|    loop at jsto_upd assigning <fs_jsto_line>.                                              |
    |   67|      IF <fs_jsto_line>-chgnr = '000'.                                                      |
    |   68|        <fs_jsto_line>-chgnr = '999'.                                                       |
    |   69|      ENDIF.                                                                                |
    |   70|* on change of status profile delete user status related to old profile                     |
    |   71|      IF <fs_jsto_line>-STSMA NE <fs_jsto_line>-STSMA_OLD.                                  |
    |   72|        DELETE FROM JEST CLIENT SPECIFIED WHERE                                             |
    |   73|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   74|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   75|               STAT  LIKE 'E%'.                                                             |
    |   76|        DELETE FROM JCDS CLIENT SPECIFIED WHERE                                             |
    |   77|               MANDT = <fs_jsto_line>-MANDT AND                                             |
    |   78|               OBJNR = <fs_jsto_line>-OBJNR AND                                             |
    |   79|               STAT  LIKE 'E%'.                                                             |

    i tried with out using commmit but it is not creating Status.
    When i see the function module help and they are trying to COMMIT
    FU STATUS_OBJECT_CREATE
    Short Text
    Create Status Object
    Functionality
    The function module generates a status object.
    Take the object number from the object number management (function modules OBJECT_NUMNBER_GET_xx).
    If no object number is given, the module takes a temporary object number that must be replaced later (function module STATUS_OBJECT_SWITCH_NUMBER).
    Example
    Creating an internal order with number 100123 (object type "ORC") for status profile "STATSCHEM" with final object number
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        objnr = objektnummer
        obtyp = 'ORC'
        stsma = 'STATSCHEM'.
    commit work.
    Creating the same order with a temporary object number
    data: objectkey like ionra.
    * TBO00-REFSTRUCT for object type 'OR' is 'IONRA'
    objectkey-aufnr = '100123'.
    call function 'STATUS_OBJECT_CREATE'
      exporting
        i_objectkey = objectkey
        obtyp       = 'ORC'
        stsma       = 'STATSCHEM'.
      importing
        objnr       = objektnummer.
    call function 'OBJECT_NUMBER_GET_OR'
      exporting
        aufnr = '100123'
      importing objnr = objektnummer_neu.
    call function 'STATUS_OBJECT_SWITCH_NUMBER'
      exporting
        objnr_old = objektnummer
        objnr_new = objektnummer_neu.
    commit work.
    Notes

  • How to create a secondary list of alv grid inside the function module

    Hi All,
    My requirement is to create a RFC function module to display the alv grid of one table.
    i have created that.
    while clicking on the records of the alv it should open the secondary list of another table.
    My problem is it is not fetching the records of the internal table of the primary list since it is created inside the function module(FUNCTION...ENDFUNCTION).
    pls help me on this.
    Thanks in Advance.

    hi,
    READ TABLE sel_sheet INTO wa_sheet INDEX rs_selfield-tabindex.
    here sel_sheet is the internal table for the primary list..
    i called the function module "reuse_lav_grid_display" inside Function...Endfunction.
    so when i am using  READ TABLE sel_sheet INTO wa_sheet INDEX rs_selfield-tabindex.
    inside the user command perform therecords in this internal table is not populating..
    pls help me on this.
    thanks in advance.

  • Error while using the function module..pack_handling_unit_dlvry

    Hi all...
    while using the function module pack_handling_unit_dlvry,
    we need to pass the handling unit number as per the functionality we require.
    but the mandatory field for the function module is the handling unit number in the form of bar code..
    so how to use this function module..
    All the useful answers will be regarded..
    Regards,
    Saroja.

    Have you tried using BAPI BAPI_HU_CREATE. Also view Function Module Documentation on its usage.

Maybe you are looking for

  • Goods Receipt and Subcontract/Service confirmation

    Dear SAP Guru, I have one scenario to map. Some waste will be generated because of nature of FG production and processing of this waste will be carried out within factory premises by sub-contractor. As material issued will be waste, no weighing of ma

  • Function module  VS RFC

    any body can help me to know the difference between function module and remote function module...?

  • Screen Exit in Header Level in ME51N

    Hi, Are there any screen exits in header level in ME51N screen? I need to call a BSP upon the click of a button and when the user selects a line item from there, it has to fall as a line item in the PR screen. Need your help on this. Thanks and Regar

  • Are all prices in my local currency?

    I'm in New Zealand, and Vanity Fair magazine in particular is $8.29 per edition. I want to know if this is my local currency or US dollar? As it's about a 3rd of what I will pay for the actual magazine, it's awfully cheap! Thanks

  • Photoshop Touch Up for Android Available in the Playstore - Now!

    if your looking for a great tool to Touch up your Photo's have a look at this app from Adobe..  B33