What is customer's modification concept in Call function??

Following is the definition of CALL CUSTOMER-FUNCTION <func>...
It is similar to CALL FUNCTION. The function modules must be programmed and activated within the <b>customer's modification concept</b>.
Here,I am not able to understand what is meant by :  CALL CUSTOMER-FUNCTION ??

It is nothing but one type of Enhancement(user exit) like thing to write out code with respect to that program.
We use user exits in different ways from CMOD, SMOD etc
for certain programs, with in the program SAP has provided this type type of CUSTOMER FUNCTION '001'.
double click on the '001' and create your own include and write the related code in that for your requirement.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
• They do not affect standard SAP source code
When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.
• They do not affect software updates
When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You can find more information about locating applications with pre-defined exits in Locating Applications that have Exits
CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.

Similar Messages

  • Lock inheritance with "CALL FUNCTION func IN BACKGROUND TASK"

    I see that the "SAP Lock concept" documentation states that for locks obtained with _scope = '3', all UPDATE tasks (spawned via "CALL FUNCTION func IN UPDATE TASK" inherit the lock (which is released only once all such update tasks and the calling process have requested a DEQUEUE).
    What should happen when instead, I use "CALL FUNCTION func IN BACKGROUND TASK" (for doing the update in a queue)? Are the locks inherited here as well?
    Cheers!

    Hopefully not, as a background task may be executed late. While update tasks are to be executed quickly (if not, administrators should review the system configuration, like increasing the number of UPD workprocesses).
    Solution: In the background task, redo the locks, as if it was a background job.

  • Call Function'BAPI_USER_CHANGE' starting new task 'TEST'

    Hi All,
    I have problem with starting new task statement, I am using one FM after that am using starting new task 'TEST'
    statement but its not working in one system its working fine in other systems, Please help me who this works.
    Thanks in Advance.
    Eg: Call Function'BAPI_USER_CHANGE' starting new task 'TEST'
    Regar

    Thanks Lqueiroz  ,
    Now again i am getting a DUMP by saying ,
    "An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "At least one entry could not be "
    on the called page."
    so what can be the reason for this
    call function 'ZRFC_PER_DIEM' starting new task lc_taskid performing subr on end of task
            exporting
              h_guid      = it_header_guid_n
              request_obj = lt_requested_objects_n.
          wait up to '1' seconds.
          read table gt_scl into ls_scl index 1.
          p_transaction_per_diem =  ls_scl-value.
          read table gt_scl into ls_scl index 2.
          transaction_currency_code = ls_scl-value.
      form subr   using task_id type clike.
      data: p_transaction_per_diem  type  char13,
            transaction_currency_code type  char3.
      receive results from function 'ZRFC_PER_DIEM'
                               tables
                                value = gt_scl.
    So basically i am getting dumo when receive statenment is running , by giving above dump.
    Regards
    PG

  • What is Customer Exist?

    Dear All,
    What is Customer Exist?
    What is Different Between User Exist & Customer Exist?
    Regards,
    Dharmesh

    Hi ,
    <b>Customer Exits :</b>
           Pre-planned enhancement to the standard SAP system.
    SAP anticipates potential customer requests not already implemented in the standard system by predefining them as 'empty modification modules'. Customers fill these modules with their own logic according to their own requirements.
    SAP creates customer exits with transaction <b>SMOD</b>. From these customer exits, customers then use transaction <b>CMOD</b> to choose the enhancements they want to process, assign them to enhancement projects, edit the components, and activate the relevant projects.
    Using customer exits guarantees upwards compatibility. This is because jumps to exits are predefined in the standard software and the validity of the call interface are both retained, even in future release upgrades.
    <b>Difference Between User-exits and Customer-exits</b>
    1. USER EXITS are FORMS and are called by SAP standard programs using PERFORM.
                CUSTOMER EXITS are FUNCTIONS so they are called using CALL FUNCTION (or more exactly CALL CUSTOMER FUNCTION).
    2. Inside the form (user exit) you can read and change almost any global data from host program.
                 Inside a function (customer exit) you can only acces your import/export/changing/tables parameters.
    3.User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent.
                  Customer exits are more restrictive but you are sure any change you can make to any parameters will never lead to inconsistency.
    4.User-exit doesn’t have any classification.
                   In customer-exit we have function-module exit , screen exit , menu exit.
    5.User Exits are Basically designed For SD module.
                  Customer Exits are available for MM,SD,FI,HR…..Basically designed for all modules.
    6. User-exits can be written only using access-key.
                  No need of access key to write a customer exit.
    7.With user-exits the code , the developer has written will not be there for next version unless modification assistance tool is used.
                 Customer-exits are not wiped during upgradation.
    thanks  and regards,
    kunal.

  • I would like to know how to contact someone in Verizon corporate to file a complaint.  I have received the absolute WORST customer service over the last week from this company! The customer service agents promise to call me back and then never do.  The la

    Verizon Wireless has the absolute worst customer service I have ever received.  The in store reps are unprofessional and spend more time texting and taking personal cell phone calls than in helping customers.  They are not at all knowledgeable and even state they do not know what they are doing.  When you call customer service you get jerked around and passed from one person to the next with no one knowing how to fix my billing issue.  I have received NO call backs that were promised and the latest person I spoke to was incredibly rude.  Sanita from Sacramento refused to even give me her last name or the last name of her Manager Nick so that I could follow up.  I am incredibly disappointed at how poorly I have been treated.  I will make sure to tell everyone I know about this experience and as soon as my contract has expired I WILL be leaving Verizon services after 10 years with the company!!

    This is a customer to customer forum, so this is not the place.
    What is going on with your account? maybe we can help you.

  • Customer Communication Preferences - Do Not Call & Do Not Email

    Oracle leverages Siebel CRM to develop an effective solution to address the Do Not Call and Email Permissible Use requirements. The application uses the Contacts functionality to manage communication preferences, which when defined, centrally synchronizes all contact records that share the same phone number and email address. Additionally, the relevant information is masked so Oracle employees cannot accidentally reach out to the contact. Therefore, the solution ensures that we are compliant with regulations, enables us to respect individuals' communication preferences and provides an audit trail of changes to their preferences.
    I am working on R12.1.2 and my customer want this feature to be implemented on our Oracle Application.
    My customer asked to implement this my seeing a blog post on Oracle Blogs
    Here is the URL: http://blogs.oracle.com/crm/entry/crm_at_oracle_series_do_not_ca
    This is the only hit I found on internet.
    did you guys ever worked on this kind of requirement ??
    would you guys please help me on how to implement this requirement?
    Thanks,
    Versatile!

    railman wrote:
    What ever happened to the "Do not call lists"??
    I get calls continually from a 616 area code to "lower my credit card interest rate".  It is a scam trying to get credit card numbers.
      I block the numbers on my account but within a few day to a week there is another call from 616 area code with the same scam.  How do I get rid of these for good !??!
    If you asked to be removed they hang up, if you question what credit card they are calling about they hang up, if you question anything about their service other than being willing to submit your card number they hang up.
    BUT, within a few days they call back on a different number, always 616 area code and usually the same exchange and no matter what you do you can't get rid of them unless you block the current number.  HELP!!!
    You can report them at donotcall.gov but it probably won't help.  The people dom't seem to care about breaking the law.

  • What's up with these unwanted, unsolicited calls?

    Beginning yesterday morning, I've gotten four calls from area codes within California.  I do not recognize the numbers, and I have no contacts in these areas.
    (All mobile numbers on this post has been deleted to comply with VZW Community ToS)
    Message was edited by: Verizon Moderator

    All my phone numbers have been on the DNC registry since 2007; I have current confirmations.
    It is apparent to me that Verizon has no interest in dealing with this problem; I am still NOT convinced that my personal information was not leaked or otherwise compromised by Verizon.  Your assurance that you do not release personal information to third parties is of little comfort to me; Verizon, like any other organization, has in its employ dishonest and/or incompetent people.
    Date: Mon, 13 Aug 2012 14:33:29 -0600
    From:
    To:
    Subject: Re: What's up with these unwanted, unsolicited calls? - Re: What's up with these unwanted, unsolicited calls?
                                                                                    Re: What's up with these unwanted, unsolicited calls?
        created by Verizon Wireless Customer Support in My Bill - View the full discussion
        I know unwanted calls be a pain in the neck CSwa! I recommend adding your number to the Do Not Call list and taking advantage of our free call and message blocking feature.
    Please be assured we do not release any of our valued customers' personal information to third parties. I have included a helpful link below for your reference.
    bit.ly/KQCmRY
    Sincerely,
    JonathanK_VZW
    VZW Support
    Follow Us on Twitter@VZWSupport
    >Post edited to remove personal email addresses
    Message was edited by: Verizon Moderator

  • What  is CUSTOMER MATERIAL INFORMATION RECORD ?

    Dear SAP Gurus
    What  is CUSTOMER MATERIAL INFORMATION RECORD ?
    Regards
    SA

    SA
    The Information relating to a material that applies only to a specific customer  is called as CUSTOMER MATERIAL INFORMATION.This is a description of your material by the customer and you record this customer specific information in the customer material info record.
    Regards
    VIVEK

  • Call function and call customer function

    Hi
    Can anybody let me know what is the difference between CALL FUNCTION AND CALL CUSTOMER- FUNCTION .
    i know call customer- function is used while we r working on user exits .
    but is their any specific reason of difference ...
    Thanks

    CALL CUSTOMER-FUNCTION function_exit parameter_list.
    Effect
    This statement can be used in programs delivered by SAP. It includes the function module exit specified in function_exit . The function module exit is a customer exit. In an SAP program, it enables you to call a function module provided by SAP and implemented by the customer.
    The indicator function_exit must be a three-digit text field literal. A function module exit is specified by SAP using the transaction SMOD and can be activated using the transaction CMOD in customer systems.
    Specifications by SAP
    An empty or partly implemented function module must be assigned to the function module exit using the transaction SMOD. The name of the function module consists of EXIT_, the program name, which contains the statement CALL CUSTOMER-FUNCTION, and the three-digit indicator in function_exit. The interface of the function module is completely defined by SAP.
    Activation in the customer system
    The transaction CMOD enables the customer to implement the source code of the function module within an enhancement project and to activate the function module exit. If the function module exit is not activated, the statement CALL CUSTOMER-FUNCTION is ignored. If the function module is activated, the corresponding function module is called in the same way as the general function module call.
    Syntax and meaning of the parameter_list for the assignment of the actual parameters to formal parameters and for the exception handling are the same as in a general function module call. It is not possible to dynamically fill the interface.
    CALL FUNCTION func
    Syntax
    CALL FUNCTION func { parameter_list
                       | parameter_tables }.
    Effect
    This statement calls the function module specified in func. The identifier func must be a character-type data object, which contains the name of a function module in uppercase letters during the statement execution. Each function module of an SAP system has a unique name, which is why you need not specify the function group.
    Use additions parameter_list or parameter_tables (as of release 6.10) to statically or dynamically assign actual parameters to the formal parameters of the function module and return values to the non-class-based exceptions.
    Note
    If the name of a function module is specified by a constant or as a literal, the extended syntax check can check the statement.
    Exceptions
    Catchable Exceptions
    CX_SY_DYN_CALL_ILLEGAL_FUNC
    Cause: The called function is known but not active.
    Runtime Error: CALL_FUNCTION_NOT_ACTIVE
    Cause: The called function is unknown.
    Runtime Error: CALL_FUNCTION_NOT_FOUND
    CX_SY_DYN_CALL_ILLEGAL_TYPE
    Cause: The type of the actual parameter does not fulfill the requirements of the function interface.
    Runtime Error: CALL_FUNCTION_CONFLICT_GEN_TYP
    Cause: The actual parameter does not have the length expected by the function.
    Runtime Error: CALL_FUNCTION_CONFLICT_LENG
    Cause: The actual parameter does not have the type expected by the function.
    Runtime Error: CALL_FUNCTION_CONFLICT_TYPE
    Cause: Only those functions can be called in the update task that are intended for it.
    Runtime Error: CALL_FUNCTION_NO_VB
    Cause: An actual parameter does not fulfill the alignment requirements of the respective formal parameter.
    Runtime Error: CALL_FUNCTION_WRONG_ALIGNMENT
    CX_SY_DYN_CALL_PARAM_MISSING
    Cause: The function expects a parameter, which has not been passed by the caller.
    Runtime Error: CALL_FUNCTION_PARM_MISSING
    CX_SY_DYN_CALL_PARAM_NOT_FOUND
    Cause: The caller has passed a parameter, which is not known to the function.
    Runtime Error: CALL_FUNCTION_PARM_UNKNOWN
    plz reward points if it helps

  • What is custom IDoc ?

    Hi Friend,
    plz help me about Custom IDoc and how to configure ?
    Thanking you.
    Subash

    Hi Subash,
    Aim: Transfer the data from one system to another using user customized IDOC.
    Sender System: 
    Server: 172.25.8.185
    Client: 200
    Data from Z table: zsach1 
    ReceiverSystem:
    Server: 172.25.9.198
    Client: 800
    Data from Z table: zsach1 
    Data is fetched from Z table on the sender system and inserted it in the Z table of Receiver system using ALE/IDOC. 
    Settings on the Sender End 
    Table Creation T – Code SE11. The table contains data that is to be sent to Receiver. 
    ALE Configuration 
    T-Code – SALE 
    Defining Logical System 
    200 is our sender
    800 is our receiver 
    Assigning Client to Logical System 
    200 is our sender
    800 is our receiver 
    Defining Target System for RFC Calls (Tcode – SM59)
    Click on R/3 Connections and then Create TAB 
    Step 1 
    Step 2 
    Save and test the connection. 
    Defining Port 
    The sender system is connected to the receiver system through this Port.
    Defining Partner Profiles 
    The partner for client 200(Sender) is the client 800 (Receiver) 
    Since this is a sender we have to define only Outbound Parameters in this case.
    Here you can see the Message type is Z message type.  
    2.                   Maintaining Distribution Model ( TCode BD64 ) 
    Create new Distribution Model 
    Add Message Type 
    Now Distribute this Model View  
    Distribute it from Edit &#61664; Model View &#61664; Distribute
    Defining the Z Segment type
    Tcode – WE31 
    Defining the Basic Type
    T Code WE30 
    Click on New 
    This will take you to next screen as follows 
    Here you have connected the basic type to the segment type.
    Enter again and this will take you to screen as follows  
    This shows the relation between the basic and the segment types. 
    Next you need to make the entry of the segment in the system table.
    Tcode : WE81 
    Next is the following entry which is required. 
    Here you are specifying the message type and the basic type and the release version. 
    This is all about the configuration you need to do on the sender side.
    Now on the sender side you also need a program that will fetch the required data, couple it in the IDOC format and post it. 
    Here is a small piece of code that could be useful.
    *& Report  ZSACH_CUST_IDOC                                             *
    report  zsach_cust_idoc                         .
    parameters :            p_logsys like tbdlst-logsys.
    data : gen_segment like edidd-segnam value 'ZSACH'.
    data : control_dat like edidc,
          gen_data like z1hdr .
    tables :zsach1.
    data: begin of inttab occurs 0,
            lname type z1hdr-lname,
            fname type z1hdr-fname,
          end of inttab.
    data :
          int_edidd like edidd occurs 0 with header line,
          int_edidc like edidc occurs 0 with header line.
    select * from zsach1 into corresponding fields of table inttab.
    if sy-subrc ne 0.
      message 'no data' type 'I'.
      exit.
    endif.
    control_dat-mestyp = 'ZSACH'.
    control_dat-idoctp = 'ZSACH'.
    control_dat-rcvprt = 'LS'.
    control_dat-rcvprn =  p_logsys.
    loop at inttab.
      gen_data-lname = inttab-lname.
      gen_data-fname = inttab-fname.
    GEN_DATA-SSN = INTTAB-SSN.
    GEN_DATA-DOB = INTTAB-DOB.
      int_edidd-segnam = gen_segment.
      int_edidd-sdata = gen_data.
      append int_edidd.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
      exporting
        master_idoc_control                  = control_dat
      OBJ_TYPE                             = ''
      CHNUM                                = ''
      tables
        communication_idoc_control           = int_edidc
        master_idoc_data                     = int_edidd
    exceptions
       error_in_idoc_control                = 1
       error_writing_idoc_status            = 2
       error_in_idoc_data                   = 3
       sending_logical_system_unknown       = 4
       others                               = 5
    if sy-subrc <> 0.
      message id sy-msgid type sy-msgty number sy-msgno.
    else.
      loop at int_edidc.
        write :/ 'IDOC GENERATED',int_edidc-docnum.
      endloop.
      commit work.
    endif.
    Settings on the receiver side. 
    The ALE configuration is same as we did it on the sender side. Please refer to earlier pages. 
    The receiver specific differences are mentioned below. 
    T-Code – SALE 
    200 is our sender
    800 is our receiver 
    Steps  
    Defining Logical System (Same as sender)
    Assigning Client to Logical System (Same as sender)
    Defining Target System for RFC Calls (Tcode – SM59) (Same as sender)
    Defining Port(Same as sender) 
    Defining Partner Profiles – Here we are accepting the data from Sender system. Hence we need to configure it as Inbound. 
    Click on the   sign above to go to next screen. 
    Here the message type is to be created again as it was created on the sender side.
    The following steps are repeated, as done on the sender side, on the receiver end 
    Tcode WE30
    Tcode WE31
    Tcode WE82
    Tcode WE81
    Here on the receiver end, we need to specify a process code at the time of defining the partner profile.
    Process code is something that has the logic defined about what to be done after receiving the IDOC. 
    In our case, on receipt of the IDOC, we are updating the Z Table. i.e Inserting the data from the IDOC into the Z Table. 
    Creating a Process Code
    Tcode – WE42  
    The logic associated is coded in the Function Module which is specified in the Identification Field above. 
    Also the processing type is selected as Processing by Function Module as above. 
    The function Module is specified in the following screen. 
    To have your function Module in the above drop down list, the entry is to be made using the following transaction 
    TCode – BD51 
    Once the entry is done here, the function module appears in the drop down list in the previous stage.
    Also it is important to make the following entry
    Tcode WE57 
    Function Module will look something as below: 
    Source Code
    function z_idoc_input_sach .
    ""Local interface:
    *"  IMPORTING
    *"     VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
    *"     VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
    *"     VALUE(NO_APPLICATION_LOG) LIKE  SY-DATAR OPTIONAL
    *"     VALUE(MASSSAVEINFOS) LIKE  MASSSAVINF STRUCTURE  MASSSAVINF
    *"       OPTIONAL
    *"  EXPORTING
    *"     VALUE(WORKFLOW_RESULT) LIKE  BDWF_PARAM-RESULT
    *"     VALUE(APPLICATION_VARIABLE) LIKE  BDWF_PARAM-APPL_VAR
    *"     VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
    *"     VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
    *"  TABLES
    *"      IDOC_CONTRL STRUCTURE  EDIDC
    *"      IDOC_DATA STRUCTURE  EDIDD
    *"      IDOC_STATUS STRUCTURE  BDIDOCSTAT
    *"      RETURN_VARIABLES STRUCTURE  BDWFRETVAR
    *"      SERIALIZATION_INFO STRUCTURE  BDI_SER
    *"  EXCEPTIONS
    *"      WRONG_FUNCTION_CALLED
      include mbdconwf.
      data : it_emp_data like zsach1 occurs 0 with header line.
      data : gen_data like zsach1 .
      workflow_result = c_wf_result_ok.
    data : counter type int4.
    select count( * ) from zsach1 into counter.
    counter = counter + 1.
      loop at idoc_contrl.
        if idoc_contrl-mestyp ne 'ZSACH'.
          raise wrong_function_called.
        endif.
        clear gen_data.
        refresh it_emp_data.
        loop at idoc_data where docnum eq idoc_contrl-docnum.
          if idoc_data-segnam = 'ZSACH'.
            gen_data = idoc_data-sdata.
              it_emp_data-mandt = counter.
              it_emp_data-lname = gen_data-lname.
              it_emp_data-fname = gen_data-fname.
              counter = counter + 1.
            append it_emp_data.
          else.
            message 'ERROR' type 'I'.
          endif.
        endloop.
      endloop.
    insert zsach1 from table it_emp_data.
    call function 'EDI_DOCUMENT_OPEN_FOR_EDIT'
      exporting
        document_number               = idoc_data-docnum
      importing
        idoc_control                  = idoc_contrl
      tables
        idoc_data                     = idoc_data
      exceptions
        document_foreign_lock         = 1
        document_not_exist            = 2
        document_not_open             = 3
        status_is_unable_for_changing = 4
        others                        = 5.
    call function 'EDI_CHANGE_DATA_SEGMENTS'
      tables
        idoc_changed_data_range = idoc_data
      exceptions
        idoc_not_open           = 1
        data_record_not_exist   = 2
        others                  = 3.
    data t_itab_edids40 like edi_ds40 occurs 0 with header line.
    clear t_itab_edids40.
    t_itab_edids40-docnum      = idoc_data-docnum.
    t_itab_edids40-status      = '51'.
    t_itab_edids40-repid       = sy-repid.
    t_itab_edids40-tabnam      = 'EDI_DS'.
    t_itab_edids40-mandt       = sy-mandt.
    t_itab_edids40-stamqu      = 'SAP'.
    t_itab_edids40-stamid      = 'B1'.
    t_itab_edids40-stamno      = '999'.
    t_itab_edids40-stapa1      = 'Sold to changed to '.
    *t_itab_edids40-stapa2      = t_new_kunnr.
    t_itab_edids40-logdat      = sy-datum.
    t_itab_edids40-logtim      = sy-uzeit.
    append t_itab_edids40.
    call function 'EDI_DOCUMENT_CLOSE_EDIT'
      exporting
        document_number  = idoc_data-docnum
        do_commit        = 'X'
        do_update        = 'X'
        write_all_status = 'X'
      tables
        status_records   = t_itab_edids40
      exceptions
        idoc_not_open    = 1
        db_error         = 2
        others           = 3.
    endfunction.
    Running the Application 
    Sender system
    Execute the program we created earlier 
    Checking the IDOC 
    T Code WE02 
    Checking the data on the Receiver end 
    Tcode: WE02 
    The IDOC has arrived here 
    Checking the Data  
    Double click on the IDOC  
    Checking the Database 
    This way, the data has come to the receiver end successfully. 
    Thanks&Regards,
    Phani.
    CHECK URL:http://www.****************/Tutorials/ALE/DataDistributeCustomIDOC/page6.htm

  • What is the use of CALL FUNCTION MODULE - AT BACKGROUND TASK?

    Hi experts,
    I found Call functional module in background task will make the FM run at the next commit work as some people said. So I have some questions:
    1 if we use COMMIT WORK commend, the pending FM will be called? If there are several FMs called at background task, what is the sequence of them? How many conditions will trigger the running of these FMs?
    2 Where can I find the log of this pending FMs? In SAP library, it says there are 2 tables. But I checked these tables and can only find the FM name and user of it. And I can not understand content of these tables. It seems one is for the main information of FM, and the other is for the data of the FM, maybe the parameters.
    3 If I call a FM in this way, Can I canncel it before the next commit work in some way?
    Finally, thanks for reading and help.

    HI,
    When the COMMIT WORK statement is executed, the function modules registered for the current SAP-LUW are started in the order in which they were registered. ROLLBACK WORK deletes all previous registrations for the current SAP-LUW.
    If the specified destination is not available when COMMIT WORK is executed, an executable program called RSARFCSE is started in background processing. By default, this tries to start the function modules registered for a SAP-LUW in their destination every 15 minutes and up to 30 times. These parameters can be changed in the transaction SM59. If the destination does not become available within the defined time, it is recorded in the database table ARFCSDATA as the entry "CPICERR". The entry in the database table ARFCSSTATE is deleted after a standard period of eight days

  • What is customizing request?

    what is customizing request?
    regards,
    phani.

    Hi Phani..
    Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
    Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
    Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
    You can see good details on this thread:
    Re: customising and workbench request
    and if you need any extra information just have a look in these
    http://help.sap.com/saphelp_sm40/helpdata/en/b5/90cd3a21873650e10000000a11402f/content.htm
    http://web.mit.edu/ist/org/admincomputing/dev/qa_tr_faq_production.shtml
    http://help.sap.com/saphelp_nw04/helpdata/en/3b/dfba3692dc635ce10000009b38f839/content.htm
    http://www.planetsap.com/cts.htm
    http://www.sapbrain.com/TOOLS/CTS/CTS.html
    If it helps Reward with points
    Regards Rk
    Message was edited by:
            Rk Pasupuleti

  • What's the phone number I should call for help with my iPhone and ihome dock?

    What's the phone number I should call for help with my iPhone and ihome dock?

    http://www.ihomeaudio.com/support/

  • What is the syntax for calling function from class file by jsp

    does anyone here knows what is the syntax of how to call a function from java class file by javascript code or any way to call it?
    and where should i put the calling function code? because the function is called depend on the user click.
    for example
    <%=pc.functionName(a,b)%>
    for the variable a and b, how can i get the value from html textbox and put it in a and b...
    urgent needed...
    thx

    Jsp's are executed before the Html forms are created and loaded. Dont try to use a java code function calling on a javascript click. You'll have to explicitly redirect it into a servlet where in you can call the function you want.
    Well! another way could be using AJAX. That seems to be powerfull enough and it might also serve your purpose.
    Hope this helps

  • What's needed to qRFC enable (and call) a function module?

    Hi people,
    I have a function module that I want to call using qRFC. However, I'm not sure how to go about this. What i can find in documentation is the following:
    - function module needs to be RFC enabled (of course)
    - function module needs to be called in update task
    However, I have the feeling there should be more to it than just this. Can anyone point me in the right direction?
    Thanks,
    R

    I guess you will have to make use of the following function modules to define the queue name:
    TRFC_SET_QUEUE_NAME
    TRFC_SET_QUEUE_RECEIVER_LIST (inbound queue)
    TRFC_SET_QUEUE_NAME_LIST (outbound queue)
    Also, the call would be like
    call function u2019Z_QRFC_FUNCTIONu2019
    destination 'DESTINIATION'
    in background task  ( as separate unit )
    exporting ...
    tables ...
    etc...
    Also, you can check this link
    http://help.sap.com/saphelp_nw04s/helpdata/en/62/73241e03337442b1bc1932c2ff8196/content.htm
    Hope this helps.

Maybe you are looking for

  • Sometimes volume keys or spaces don't work

    Hi all, A couple of months ago my macbook fell to the floor (something like 30-40cm fall). It didn't broke but the unibody frame got a bit dented by the zone it hit the floor (one of the battery corners). From then on, I have noticed that, from time

  • Error when inserting into table - Undefined Variable

    DB = Oracle 10.2.0.1 WEBSERV = Apache 2.0.55 LANG = PHP5 I have created (or more accurately, copied) a php script to insert data into one of my database tables when I press submit. The code is as follows (my connect string works fine and its included

  • Credit Memo to transfer AUC balance to WBS Element

    We have implemented Project Systems in a limited way and now need to transfer the current AUC balances into project WBS Elements.   The plan is to issue credit memo's from the AUC to a clearing account then mark the balance with a WBS Element.  When

  • How to call a form with dabble clicking on a record with one time where

    Hi All, How to call a form with dabble clicking on a record with one time where clause. I mean when i dabble click on the current record i want to call another form with details of the record with onetime where clause. Can anyone help me in this rega

  • OWB 10gR2 - some enhancement requests

    Hi, I've been working with OWB 10gR2 for approximately a week now, and I've come across a few (minor) bugs, as well as a list of enhancements that I think would make the tool better. I'd like to surface these in this forum so they can be either disag