External system accesing Function module

hi all,
I have some questions regarding connection of SAP with some external systems. So here it is:
External system e.g. TIBCO is accessing SAP's Function Module e.g. Z_CA_CRM_INV_DETAILED, is there any way i can see in Debug mode a moment the external system calls this function module and import parameter values?
Thank u all, and please refer me to a category in this forum if this question wouldn't be appropriate for ABAP general,
thanx in advance,
Maja

hi,
my problem is that i can't change existing function module as it's cross client..
exactly where should i put that breakpoint? in Utilities/breakpoint? there is only set/delete... none options for external breakpoint...
so it seems like i have a smaller version...

Similar Messages

  • System error Function Module

    When I execute transaction /SAPAPO/CPP. Then when we select locgical system as WCD320 and executing. The below error.
    System error Function module
    "CIF_ERROR_LOG_OPERATE_NEW" not fo for call in
    system WCD320
    Above issue is only coming in development but quality and production working fine. It is giving error some where in the program error during remote call. what is the exact problem please suggest me.
    please help me out.

    Hello Venkat,
    Are your workiong for PMI? WCD and WCQ is upgraded to ECC 6, WCP is still in 5.0. I am the contact for P1 for interfaces...:)
    Edited by: Naresh Reddy K on Jun 7, 2010 4:09 PM

  • Third party system call function module/BAPI through RFC to update Z table

    Dear Friends,
    We have a third party system which directly inserts a Z table in SAP through its programming, which is an auditing issue.
    We want the third party system should call function module/BAPI through RFC so that the Z table gets updated.
    waiting for inputs..
    Thanks,
    Kumar

    if third party system is capable of making Remote Function call, then writing a Function module & making it remote enable is not difficult task in ABAP.
    You may have to prepare specifications first to decide if third party system is going to Read, insert, update, delete records from Zee table.

  • Changing Password across the RFC systems needed Functional Module

    Hi All,
                 Could anybody pleaese tell me is there any function module to change the password across the RFC destinations.
    Marks will be given immediately.,
    J

    Have a look at the bapi's
    BAPI_EMPLOYEET_CHANGEPASSWORD.
    Type in BAPIPASSWOR to look at the complete suite.
    J

  • How to exit the execution in middle of a function module

    Hi Fox,
    I have a function which sometime needs more than 10 minutes to deliver a result.
    This is not acceptable thus this function will be given a time-out value in a second format after which the function should be stopped or killed. Do you have an idea how to do it. The function has to process a lot  of records within a table, so maybe a solution with a counter
    Cheers!
    Kami

    CALL FUNCTION func DESTINATION 'NONE' ...
    The destination NONE refers to the calling system. Function
    modules called with are executed in the system of the calling program, but in their own program context.
    As you know RFC uses dialog work process and the timeout for dialog work process will be in the range of 10 -15 mins not beyond that , so once the time the function module gets killed !!!
    I m sure about this process because i did a similary requirement like yours.
    Thanks.

  • How to add a created Z function module to the existing list in WE21

    Hi all,
    There is some existing function modules ( like EDI_PATH_CREATE_CLIENT_DOCNUM ) in WE21 in the function module field.
    here, i need to create one Z function module as per user requirement & want to add to that list.  is it possible???
    actually, i want the file name format is like
       " Document Number_YYYYMMDDHHMMSS.xml  ". but existing function modules are not giving this format.do anybody give any idea.
    correct answers will be rewarded.
    Thanks & Regards

    HI Pabitra,
       Yes, can always change the existing fm and add it with message type as follows pls note step 7 and step 8. (for inbound it is we42 and for outbound it is we41 )
    Basic IDOCs have supplied by SAP with standard structure. (Segments). You can extend them with your own segments.
    IDOCs does have unique number. They contain control, data, and status records.
    Useful Transaction Codes:
    WEDI : IDoc Menu
    WE02 : IDoc List (can enter IDoc number to select on)
    WE05 : IDoc List
    WE19 : Transaction WE19 can be used to test the IDoc
    WE30 : IDoc Type Development: Initial Screen
    WE31: Development Segments: Initial Screen
    WE60 : Documentation for IDoc Types. This allows you to view the IDoc you have created.
    WE81 : Display View ‘EDI: Logical Message Types’: Overview
    WE82: Display View ‘Message Types and Assignment to IDoc Types’: Overview
    WE21 - Creation of POrt
    WE20 - Partner Profile creation
    SALE - ALE (Application Linking and Enabling) settings
    For Outbound ALE Configurations: (Example)
    IDoc definitions and necessary ALE configurations settings for the outbound .
    Create Idoc segments – Transaction WE31.
    Create Idoc type – Transaction WE30.
    Create Message Type – Transaction WE81.
    Assign Message Type to Idoc type – Transaction WE82.
    Create a distribution Model - Transaction BD64
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    for creating a IDOC
    see the below steps for outbound processing IDOCS..
    2.1 Outbound Interface
    PROCESS DIAGRAM
    Outbound Interface
    1. Analyse Hierarchy Levels
    2. Create New segment
    3. Create New IDoc Type
    4. Create New Message Type
    5. Link Message with IDoc Type
    6. Create an entry in EDP13 via transactions WE20 and BD64
    7. Populate the Custom IDoc via ABAP Program
    7b Error Handling
    7c. Send Status Email
    8. Test the Population of the Custom IDoc
    Step 1 – Analyse Hierarchy Levels:
    Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
    Navigate to transaction code WEDI
    Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
    Step 2 – Create a new segment:
    via wedi : Development - IDOC Segments or Transaction code WE31.
    • Enter segment name and click on Create.
    The? name of the segment type must start with Z1 , and have a maximum of eight characters.
    • Enter description and enter the relevant field names and data elements.
    The segment should represent a structure in the program so for? each field in the segment a field name and a data element must be defined.
    • Save the segment and enter Person Responsible and Processing Person .
    • Go to Edit and Set Release.
    • Repeat this procedure for each new Segment in the IDOC.
    Step 3 – Create a new IDOC Type
    via wedi Development - IDOC Types or Transaction WE30.
    • Enter segment name (starting with Z), click on Basic Type and then Create.
    • Create as new, enter Person Responsible and Processing Person and enter description.
    • On ‘Create Basic Type’ screen decide where segments should be inserted and go to Edit/Create Segment.
    • Complete relevant fields in the Maintain Attributes screen:
    • From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
    • The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
    • The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
    • Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a ‘Child’.
    • When IDOC created return to initial screen. Go to Edit and Set Release.
    • Go to Transaction WE60 to view the IDoc Type you have created.
    Step 4 – Create new Message Type
    via wedi Development - Message Types or Transaction WE81.
    • Display/Change and click on New Entries
    • Create a new Message Type and Save.
    Step 5 – Link Message Type to IDOC Type
    via wedi Development - IDOC Type/Message or Transaction WE82.
    • Display/Change and then click on New Entries.
    • Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
    Step 6 – Create an entry in EDP13 via transactions WE20 and BD64.
    The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
    • WE20 – Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
    • BD64 – Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to ‘Environment’ on Menu and click on Generate Partner Profiles and generate (not save) profile.
    Step 7 – Populate the custom IDOC via ABAP Program
    See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
    • Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
    • The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
    - PERFORM populate_Control_structure USING c_mestyp
    c_SEGMENT_type1.
    • The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
    - PERFORM transfer_Parent_data_to_seg.
    • The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
    - PERFORM master_idoc_distribute.
    • NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
    • The ALE Layer handles the sending of the IDOC to the receiving system.
    • Error Handling (see Step 7b).
    • Commit work.
    Project SpecificStep 7b – Error Handling
    • Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
    • Declare a structure of type ‘MCMAILOBJ’ for sending instructions.
    • Enter values for the internal table based on structure ‘MCMAILOBJ’
    • For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module ‘MC_SEND_MAIL’.
    • Enter values in the following parameters: -
    MS_MAIL_SENDMODE = ‘B’ (Batch Mode)
    MS_MAIL_TITLE = 'Mail Title'
    MS_MAIL_DESCRIPTION = ‘Error description’ (e.g. MATNR not given)
    MS_MAIL_RECEIVER = ‘Name of Receiver’ (To be determined)
    MS_MAIL_EXPRESS = ‘E’ (Express Delivery)
    MS_MAIL_DLINAME = Leave Blank
    MS_MAIL_LANGU = 'E' (Language)
    MS_MAIL_FUNKOBJ_NAME = Leave Blank
    TABLES
    MS_MAIL_CONT = I_MCMAILOBJ
    Note:
    It has to be determined separately for each interface how these errors and mail notifications are to be grouped – dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
    When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
    <b>Step 7
    (Transaction WE57)
    Assign the custom function module to the IDoc type and the message type.
    Set function module to type ‘F’ and direction ‘2’ for inbound.
    Step 8
    (Transaction WE42)
    Create a new process code and assign it to the function module. The process code determines how the incoming IDoc is to be processed in SAP.</b>
    Step 9
    (Transaction BD67)
    Assign the function module to the process code created above. Got to ‘New Entries’ and enter the process code and the function module name.
    Step 10
    (Transaction WE20 and Transaction BD64)
    Create a partner profile for your message and ensure that in transaction WE20 the process code is the one that points to your function module. (See step 6 of creating Outbound Idocs).
    Step 11
    Ensure that error handling functionality is present.
    If u still have doubt, i can send u the print screen doc -  hope this helps u
    <b>Reward pts if found usefull :)</b>
    regards
    Sathish

  • Function Module RSTC_BIRS_DELETE_OLD_DATA

    After re-installing technical business content; we tried to load data in newly installed info cubes. During this process, an update task has been blocked on my name which was Deleting old statistical data from BI 7.0 system. Function module "RSTC_BIRS_DELETE_OLD_DATA" is called in update mode and it is taking lot of time deleting data, BW statistical information, from 4 database tables(rsddstatheader, rsddstatevdata, rsddstatdm, rsddstatinfo ).
    On table rsddstatinfo system is taking long time to perform delete data, in update task. I have found out OSS note 1487003 which talks about how to improve performance of function module RSTC_BIRS_DELETE_OLD_DATA. But I would like to know why this function module is called in first place.
    Thanks,
    Nitesh Shelar

    Hi, Amit,
    Thanks for the reply.
    I tried it. But I got an error saying "Access via 'NULL' object reference not possible". My code is like below. Would you please look at it and see where is wrong? Thank you!
    TABLES: pa9001.
    DATA:
            ls_return              TYPE TABLE OF bapireturn1,
            msg                    TYPE REF TO  IF_HRPA_MESSAGE_HANDLER ,
            is_ok                  TYPE BOOLE_D,
            ls_9001                TYPE pskey.
    DATA:   BEGIN of lt_pa9001 Occurs 0.
              INCLUDE structure pa9001.
    DATA:   END OF lt_pa9001.
    START-OF-SELECTION.
        SELECT * FROM pa9001 INTO lt_pa9001
           WHERE ztitlety = 'CONTRACT'
             AND begda = '20060701'
             AND endda = '20060630'
             AND aedtm = '20070313'
             AND uname = 'MYANG1'.
         IF sy-subrc = 0.
    *      MOVE-CORRESPONDING pa9001 to ls_9001.
        MOVE lt_pa9001-pernr to ls_9001-pernr.
        ls_9001-infty = '9001'.
        MOVE lt_pa9001-begda to ls_9001-begda.
        move lt_pa9001-endda to ls_9001-endda.
        move lt_pa9001-seqnr to ls_9001-seqnr.
         ENDIF.
    ENDSELECT.
    *     MOVE lt_pa9001-pernr to ls_9001-pernr.
    *     MOVE lt_pa9001-begda to ls_9001-begda.
    *     move lt_pa9001-endda to ls_9001-endda.
    *     move lt_pa9001-aedtm to ls_9001-aedtm.
    *     move lt_pa9001-uname to ls_9001-uname.
    *     move lt_pa9001-subty to ls_9001-subty.
    *     move lt_pa9001-seqnr to ls_9001-seqnr.
    *       ls_9001-pernr = lt_pa9001-pernr.
    *       ls_9001-begda = lt_pa9001-begda.
          CALL FUNCTION 'HR_ECM_DELETE_INFOTYPE'
            EXPORTING
              pskey                 = ls_9001
              MESSAGE_HANDLER       = msg
            IMPORTING
              IS_OK                 = is_ok.

  • THrough dynpro i am not able to debug backend function module

    Hi,
    In my scenario i am uploading one file through dynpro application and store it at backend(sap r/3). In this scenario first i copy file from ep application server to r/3 application server and then send file dms server where i store that file. I make function module which copy file from ep application server and send it r/3 application server and further it store it dms server.
    I checked with function module it was working fine in backend but when i am call fm in my application it would not work,
    I could not able to debugg it also.
    Please provide if i miss any thing .
    Regards,
    Gurprit Bhatia

    Have you fulfilled following list:
    1. Enbable remote debugging(external breakpoint) on function module
    2. Use same UserID that enables debugging and used in JCo Connection.
    3. Keep open the SAP GUI screen
    4. Run your application, it will take you to SAP GUI screen when breakpoint found.
    Thats all, hope this will help.
    Jawed Ali
    Edited by: Jawed Ali on Aug 27, 2008 10:42 AM

  • Function module RSAOU_BWBC_GET not found

    hi guys i have a ODS in my BWD systems , everything works fine, loading is correct, i have moved it to my testing environment and sense then, the transfer rules are inactive when i try to active them i get this error
    With Remote Function Call to system EBQCLNT900 error Function module "RSAOU_BWBC_GET" not found.  occurred.
    I have checked both r/3 systems, the function module doesnu2019t exist. I have checked both BW systems and the function module does exist and is active.
    If this was an issue with QAS. Then DEV shouldnu2019t also load any data in BWD, and in BWD everything works fine.
    I have checked the connections and its all fine.
    Any suggestions?

    HI,
    Seems like some connectivity issue or something related to transfer rules mismatch with the data source.Its not exaclty what BW is lloking for.
    Can you just do a check if the connection is happening properly between the systems.
    Also can you verify the data source in the source system in quality is OK and is same as development.
    can try to transport the data source again and then do a replication again and transport the transfer rules again.
    Thanks
    Aeet

  • Function Module required to convert the date coming from external system

    Hi Friends,
       I need a Function Module that would convert the incoming date from external sytem in format YYYYMMDD to the SAP system in DDMMYYYY. The External system data type for the date is Numberic. Please suggest any FM if you know.I found out many in SAP but didn't find for this requirement

    Wait a minute.  I am definetely missing something here.  You want to convert from an external format YYYYMMDD to SAP's internal format?  SAP's internal format is YYYYMMDD.
    All you should have to do is move you external date directly to your internal date.
    data: date1(8) type c value '20051225'. "Format YYYYMMDD
    data: date2 type sy-datum. "Format (YYYYMMDD)
    write: / date2.
    When you write out date2 it will be in whatever format your user profile has. 
    If you want to force the date format independent of your user profile settings during the write statement:
    write: / date2 DDMMYY.
    Message was edited by: Thomas Jung

  • Commit Function Module for External System ?

    Hi Gurus,
    I am using RFC - RFC_UPDATE_TAXES_DOC to post documents into External System.
    After I post those documents how to execute Commit fucntion in the external system.
    My Try:
    Will I be able to commit using BAPI_TRANSACTION_COMMIT -
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' DESTINATION gc_external_system.
    Many Thanks,
    Madan

    Yes.
    It should work, b'coz BAPI_TRANSACTION_COMMIT is itself a RFC func module.
    Regards,
    Subramnaian

  • Function module to create a CS order from external system

    Hello,
    i´m setting up a prototype for customers service (CS).
    My goal is to create the CS order automatically from a external system where i have all the required data.
    Is there a function module or something in SAP ERP which i can use to create the CS order in background?
    Thank you.
    Best regards
    Manfred

    Hello Amit,
    the requirement is the following:
    we have a SAP CRM System where we create Servicetickets.
    This tickets contain the following data which are also from interest for the CS Order:
    - Customer data
    - Equipment
    - Shorttext
    The goal is to create as follow up for the SAP CRM Serviceticket not a SAP CRM Serviceorder but a CS Order in ERP.
    All data which can be used from the ticket should be used - all further data should the user add to the CS Order manually.
    Thank you for your ideas.
    Best regards
    Manfred

  • How to debug a RFC function module remotely from another R/3 system?

    Hi experts,
       I have RFC function module in one R/3 system. I am calling this from another R/3 system that is cross apps (Xapps).
       This function module is Synchronous.
      Is it possible to debug this function module from cross apps?
      Can somebody give me the steps?
    Thanks & Regards
    Gopal

    Hi Shree,
       Can you explain it bit more?
       Do I have to call the function  module with "IN BACKGROUND TASK"?
       Or is it that I have to just put external breakpoint in the function module?
       Please help
    Thanks
    Gopa

  • How to call function module/ class method of another system.

    Suppose now i am working in System A. And i need to check the system Status of System B, System C, System D....
    my design is to provide an interface. and each system realize the interface individually.now my question is how cani call the interface, because they are in different systems.
    of course i know about the host name, port and logon information over these systems.
    who can give my some suggestions or other solutions.
    thanks in advance.
    Johnney.

    Hello,
    If u want to call a FM of the other system then that FM should be a RFC enable on one.
    <b>CALL FUNCTION func DESTINATION dest.</b>
    Effect
    Executes the function module from an external source (as a Remote Function Call or RFC); dest can be a literal or a variable.
    Depending on the specified destination, the function module is executed in another R/3 or R/2 System. Externally callable function modules must be flagged as such in the Function Builder (of the target system).
    Since each destination defines its own program context, further calls to the same or different function modules with the same destination can access the local memory (global data) of these function modules.
    To maintain existing destinations, choose Tools -> Administration, Administration -> Network -> RFC destinations
    Note
    Under certain circumstances, an RFC may trigger a database commit. For this reason, RFCs must not be used between pairs of SQL statements that open and close a database cursor (such as SELECT... ENDSELECT).
    Vasanth

  • No entries in Define conversion group and external function module setting.

    Hi all,
    After active bussiness function SAP Oil & Gas, my system have a problem in SPRO.
    SPRO --> IMG --> Industry solution Oil & Gas (Downstream) --> HPM --> QCI configuration --> Define conversion group and external function module setting.
    Problem appear: Has no entries in there!
    Please, help me! Thank you so much!
    Tks & best regards,
    DatHT

    Dat,
    There are few entries normally delivered by SAP and which are good for a regular implementation. It is possible that those are not copied over from the reference client. Second option is to check the BC set (if) available for this activity and pull those in. Check the SAP reference client first, most likely that has entries which you can copy over to your regular client.
    Regards,

Maybe you are looking for