How to bring the custom function module in WE42?

Hi,
I have created a custom function module to post a custom idoc.
Process code has been created thro WE42 and WE57 is done.
Still I am not able to see the custom function module in the list (WE42) in order to assign it to process code.
May i know the reason for this?
Thanks.
Thiyagu

What makes you think that it should be visible in WE42? There is no F4-value help for this and you haven't added it manually yet, right.
In WE42 you can manually add entries, so that's what I would do.

Similar Messages

How to write the custom Function Module to trigger the Alert.

Hi all,
I have developed a custom alert category in Tx - alrtcatdef. Now i want to trigger it from my custom function module. what should i do or what is the procedure to trigger the alert from my custom function module.
Arul Jothi

hi arul,
try this program.
RSALERTTEST.
check out this link...
<a href="/people/ginger.gatling/blog/2005/12/02/innovative-ways-to-use-alerts:///people/ginger.gatling/blog/2005/12/02/innovative-ways-to-use-alerts
regs,
jaga

How to create a custom function module with the records in SAP R/3?

Hi All,
How to create a custom function module with the records in SAP R/3? Using RFC Adapter I have to fetch the custom function module records.
Regards
Sara

Hi
goto se37...here u need to create a function group... then u need to create a function module. inside assign import/export parameters. assign tables/exceptions. activate the same. now write ur code within the function module
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db98fc35c111d1829f0000e829fbfe/content.htm
Look at the below SAP HELP links, These links will show you the way to create a Function Module
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db98fc35c111d1829f0000e829fbfe/content.htm

How to create the INBOUND Function Module for INBOUND IDOCs

Hi Friends,
Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
which are recieved from XI Server ?
I am working in SAP-ISU
Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
We have a Standard INBOUND FUNCTION MODULE
IDOC_INPUT_ISU_MR_UPLOAD
which Uploads the Meter Reading Results.
I copied the Same function Module into ZIDOC_INPUT_
and working on it.
Can any one suggest me, whether i am going in correct way or not.
In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
Can I Use the Same BAPI
BAPI_MTRREADDOC_UPLOAD
to Update the below fields,
EABL-SERNR
EABL-ZWNUMMER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS
EABL-ADATTATS
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Kindly Suggest me,
Thanks in Advance,
Ganesh

Hello Ganesh
I think you are going completely astray with you z-function module for IDoc processing.
If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
EABL-SERNR => BAPIEABLU-SERIALNO
EABL-ZWNUMMER =>REGISTER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS => ACTUALMRTIME
EABL-ADATTATS => ACTUALMRDATE
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
- BAPI_TE_EABL
- BAPI_TE_EOSB
Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
Regards
Uwe

How to copy the standarad function module

hi,
      i wants to copy the standard function module which are not rfc enabled. for that one i copied standard one and modified the attributes to rfc enabled. but it was giving the errors "You can only use LIKE and TYPE to specify types in RFC",
how can i solve my problem. pls help me.

Hi mukka,
1. In that FM, while after copying to Z,
2. there is a second parameter in IMPORT
WITH_TEXT
3. in the column of Associated type,
    it will be blank.
give some data element like CHAR30
   and also give type
4. Then it will not give the error.
regards,
amit m.

How to find the Obsolete function module in ECC 6.0

Hi Guys,
How we can find the all obsolete function in ECC 6.0, is any T-code to finding the obsolete function modules, or any other way to find.
Could you please help me.
Thanks,
Gourisankar.

Hi Gouri,
If you are looking at determining whether a single FM is obsolete or not is by this method:
Go to FM in SE37 -> Goto Attributes Tab -> General Data section -> look above the Edit Lock field ... where SAP places the release status and date of the FM, if the FM is obsolete, the text Function Obsolete appears
This is one way of finding out one FM @ a time
However if you want to check on a mass scale, I dont have a SAP system here hence cant confirm, however, all FMs are stored in TFDIR database table. Please scroll through the fields of the DB table to check whether any field relates to release status or the like. If it does, then from SE16, you can put the value corresponding to "Obsolete" in the field and run to check all FMs.
Cheers,
Aditya

How to trigger inbound custom function module?

Hello Experts,
Could someone help me with my dilemma?
I have created a custom process code which is linked to a custom function module for processing inbound IDocs. I have tested the function module successfully and I have set up the partner profile accordingly. The IDocs are coming in but get stuck at status "64". My function module never gets triggered even though in the partner profile it is set up to be triggered immediately. Any idea what I am missing?
Thanks,
Marlin

Hi marlin ,
just go for these checks and let us know the status ..
1.Check here .
Bd51 assignment of Inbound function module. Present or not
Check here .
2.Bd67 assignment of process code to inbound function module /present or not.
3.
Check here.
In the object for the message type u need to give the BUS object as the application object.
like bus2032
4.
Now place a break-point in ur function module and run it in debugging mode ..
Now check whether this one is getting into ur function module , next check the status record of the document number .
regards,
vijay.
take an idoc , populate it from we19 and then there call the function module in debugging mode in back ground ..
we'll see if this is actually picking the Fm or not.
Message was edited by: Vijay

How to find the existing function module is used in another function module

Hi all,
I created a function module and the same one is called from another function module.
When I tried to find where the first function module is used using Where-used List , I am getting the message "function module not found in selected areas" .
Please guide me what is other method to find whether the function module is used in another one.
Thanks,
Vengal Rao.

hi,
Go to UTILITIES-> Update Navigation index.
or go to fucntion group and Generate the Funtion group once.
it will detect all fucntion modules under that function group.
regards,
Rama

How could we assign customized function module to the object

Hi Experts,
How could we assign z made function module to the object type.
for instance, i have prepared one z function module and want to assign segment builder.
Please help in this regard
Thanks
Mahesh Babu

Hi Thiru,
Standard Transaction Codes, have their own Function Modules for generating Outbound/Indbound Idocs. Where these Function Modules will be configured to a particular Process Codes.
For E.g for PO's
Process code : ME10 - IDOC_OUTPUT_ORDERS - for creation
In case if its a Z Function Module, It depends on the case how you use IDOC types. either directly through Z Program or through Inbound/Outbound Process codes with respective Function modules.
Regards,
Anbalagan

How to use the alv function module

hi all,
        can any one help me out how to use reuse_alv_block_list_append function module, what parameters shall i pass to it, so that i get top of page and end of page events and report data in two blocks, can any one tell how can i didvide the data into block, at a particular line

hi,
this is my simple alv blockedlist programme.go through it.it will definrtley help u.
REPORT z50870alv_blocked.
TYPE-POOLS : slis.
*&      structure declaration
TYPES : BEGIN OF st_ekko,
          ebeln TYPE ekko-ebeln,    "Purchasing Document Number
          bstyp TYPE ekko-bstyp,    "Purchasing Document Category
          bsart TYPE ekko-bsart,    "Purchasing Document Type
          aedat TYPE ekko-aedat,    "record created on
          ernam TYPE ekko-ernam,    "Person who Created the Object
        END OF st_ekko.
TYPES : BEGIN OF st_ekpo,
          ebeln TYPE ekko-ebeln,
          ebelp TYPE ekpo-ebelp,    "Item Number of Purchasing Document
          ematn TYPE ekpo-ematn,    "Material number
          matkl TYPE ekpo-matkl,    "Material group
          netpr TYPE ekpo-netpr,    "Net price in purchasing document
        END OF st_ekpo.
*&      internal table and work area declaration
DATA : it_ekpo       TYPE STANDARD TABLE OF st_ekpo,
       it_ekko       TYPE STANDARD TABLE OF st_ekko,
       it_fieldcat1 TYPE slis_t_fieldcat_alv,
       wa_fieldcat1 TYPE slis_fieldcat_alv,
       it_fieldcat2 TYPE slis_t_fieldcat_alv,
       wa_fieldcat2 TYPE slis_fieldcat_alv,
       it_events     Type slis_t_event,
       wa_layout     TYPE slis_layout_alv.
*&      data declaration
DATA : v_ebeln TYPE ekko-ebeln.
*&      selection-screen
SELECTION-SCREEN BEGIN OF BLOCK a WITH FRAME TITLE text-000.
SELECT-OPTIONS : so_ebeln FOR v_ebeln.
SELECTION-SCREEN END OF BLOCK a.
*&      At-selection-screen
at selection-screen on so_ebeln.
perform validate_ebeln.
*&      start-of-selection
START-OF-SELECTION.
PERFORM data_retrieval.
*&      end-of-selection
END-OF-SELECTION.
PERFORM initialize_alv_block.
PERFORM build_fieldcatalog1.
PERFORM build_fieldcatalog2.
PERFORM build_layout.
PERFORM get_events .
PERFORM append_ekkodata_to_alv_block.
PERFORM append_ekpodata_to_alv_block.
PERFORM display_blocked_alv.
*&     FORM initialize_alv_block
FORM initialize_alv_block.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'
EXPORTING
    i_callback_program             = sy-repid.
endform.
*&     FORM validate_ebeln
form validate_ebeln.
select ebeln
   from ekko
   into table it_ekko
   where ebeln in so_ebeln.
if sy-subrc ne 0.
    message text-003 type 'W'.
endif.
endform.
*&     FORM data_retrieval
FORM data_retrieval.
SELECT ebeln bstyp bsart aedat ernam
    FROM ekko
    INTO TABLE it_ekko
    WHERE ebeln IN so_ebeln.
if sy-subrc ne 0.
   message text-001 type 'I'.
endif.
SELECT ebeln ebelp ematn matkl netpr
    FROM ekpo
    INTO TABLE it_ekpo
    WHERE ebeln IN so_ebeln.
if sy-subrc ne 0.
   message text-002 type 'I'.
endif.
endform.
*&      Form build_fieldcatalog1
FORM build_fieldcatalog1.
wa_fieldcat1-fieldname   = 'EBELN'.
wa_fieldcat1-seltext_l   = 'PURCHASE ORDER'.
wa_fieldcat1-col_pos     = 0.
APPEND wa_fieldcat1 TO it_fieldcat1.
wa_fieldcat1-fieldname   = 'BSTYP'.
wa_fieldcat1-seltext_l   = 'DOCUMENT CATEGORY'.
wa_fieldcat1-col_pos     = 1.
APPEND wa_fieldcat1 TO it_fieldcat1.
wa_fieldcat1-fieldname   = 'BSART'.
wa_fieldcat1-seltext_l   = 'DOCUMENT TYPE'.
wa_fieldcat1-col_pos     = 2.
APPEND wa_fieldcat1 TO it_fieldcat1.
wa_fieldcat1-fieldname   = 'AEDAT'.
wa_fieldcat1-seltext_l   = 'DATE'.
wa_fieldcat1-col_pos     = 3.
APPEND wa_fieldcat1 TO it_fieldcat1.
wa_fieldcat1-fieldname   = 'ERNAM'.
wa_fieldcat1-seltext_l   = 'NAME'.
wa_fieldcat1-col_pos     = 4.
APPEND wa_fieldcat1 TO it_fieldcat1.
ENDFORM.                    "build_fieldcatalog
*&      Form build_fieldcatalog2
FORM build_fieldcatalog2.
wa_fieldcat2-fieldname   = 'EBELN'.
wa_fieldcat2-seltext_l   = 'PURCHASE ORDER'.
wa_fieldcat2-col_pos     = 0.
APPEND wa_fieldcat2 TO it_fieldcat2.
wa_fieldcat2-fieldname   = 'EBELP'.
wa_fieldcat2-seltext_l   = 'ITEM NUMBER'.
wa_fieldcat2-col_pos     = 1.
APPEND wa_fieldcat2 TO it_fieldcat2.
wa_fieldcat2-fieldname   = 'EMATN'.
wa_fieldcat2-seltext_l   = 'MATERIAL TYPE'.
wa_fieldcat2-col_pos     = 2.
APPEND wa_fieldcat2 TO it_fieldcat2.
wa_fieldcat2-fieldname   = 'MATKL'.
wa_fieldcat2-seltext_l   = 'MATERIAL GROUP'.
wa_fieldcat2-col_pos     = 3.
APPEND wa_fieldcat2 TO it_fieldcat2.
wa_fieldcat2-fieldname   = 'NETPR'.
wa_fieldcat2-seltext_l   = 'NET PRICE'.
wa_fieldcat2-col_pos     = 4.
wa_fieldcat2-do_sum      = 'X'.
APPEND wa_fieldcat2 TO it_fieldcat2.
ENDFORM.                    "build_fieldcatalog
*&      form build_layout.
FORM build_layout.
wa_layout-zebra ='X'.
wa_layout-no_vline = 'X'.
wa_layout-no_hline = 'X'.
wa_layout-colwidth_optimize = 'X'.
wa_layout-window_titlebar = 'PURCHASE ORDER HEADER AND ITEM DETAILS'.
ENDFORM.                    "build_layout
*&      form append_ekkodata_to_alv_block
FORM append_ekkodata_to_alv_block.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
    is_layout                        = wa_layout
    it_fieldcat                      = it_fieldcat1
    i_tabname                        ='it_ekko'
    it_events                        = it_events[]
IT_SORT                          = IT_SORT
I_TEXT                           = ' '
TABLES
    t_outtab                         = it_ekko
EXCEPTIONS
   PROGRAM_ERROR                    = 1
   MAXIMUM_OF_APPENDS_REACHED       = 2
   OTHERS                           = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.
*&      form append_ekpodata_to_alv_block
FORM append_ekpodata_to_alv_block.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
    is_layout                        = wa_layout
    it_fieldcat                      = it_fieldcat2
    i_tabname                        ='it_ekpo'
    it_events                        = it_events[]
IT_SORT                          = IT_SORT
I_TEXT                           = ' '
TABLES
    t_outtab                         = it_ekpo
EXCEPTIONS
   PROGRAM_ERROR                    = 1
   MAXIMUM_OF_APPENDS_REACHED       = 2
   OTHERS                           = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.
*&      FORM display_blocked_alv.
FORM display_blocked_alv.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'.
endform.
*&      Form GET_EVENTS
FORM get_events .
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      i_list_type     = 2
    IMPORTING
      et_events       = it_events[]
    EXCEPTIONS
      list_type_wrong = 1
      OTHERS          = 2.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " GET_EVENTS\
regards,
pavan t.

HOw to find the BAPI function module

Hi all,
I have a field called IEVER in table EIKP.
How to find the related BAPI function module and BAPI structure for this filed.
Thanks in advance
KP

Hi KP,
can you tell us the name of the transaction in which you saw this field?
If it is in PO Creation or Change you can probably look at the bapis
BAPI_PO_CREATE or BAPI_PO_CHANGE
Regards,
Ravi

How to reset the Calculate_tax_item function module

Hi expert,
I am using calculate_tax_item function module for calculating tax for purchase order in item wise. If the purchase order having only one item means its showing result correctly...but if the purchase order having two item means it takes 1st item also after i refreshed that internal table... i don't know how to reset that function module but option is there to reset...its not working after i gave reset = 'X'. Guide me to solve this issue...
Regards,
Rathish

Hi,
Refer the below link
http://wiki.sdn.sap.com/wiki/display/Snippets/FunctionModuletoCalculateTaxinPurchaseorderbasedoncondition+type

Error in Custom Function Module

Hi,
I am working on implementing General Ledger Business content in financial Accounting.
We had a requirement of creating a Custom Virtual cube similar to 0FIGL_V10. Hence, we had copied the standard function module RS_BCT_FIGL_DATA_GET_VC10 and created a custom function module. Before doing that, we had copied the function group RS_BCT_FIGL and created a custom function group for the custom function module.Both were activated subsequently. Then, we had created a custom virtual cube (ZFIGL_V10) using the custom function module.
The queries on the Standard virtual cube were migrated to ZFIGL_V10 using the RSZC transaction code. when the queries are executed in RSRT, we get an error message "**An exception with the type CX_SY_DYN_CALL_ILLEGAL_FUNC occurred" and the ABAP debugger is started post that error.
Has anyone faced this problem before?could any of you provide some pointers to it.
Regards,
Sainath

You cannot use the standard function module which is used for standard cube for another cube.
You should not change the function module.
Instead you can make a copy of the function module you are using aand use this copy in ur virtual cube which will work in the same way the actual Fm used to work and it will make you perfrom the changes.
Follow the below steps:
1) Goto SE37 and In the top tool bar click on the copy button which is on right side of delete button.
2) in fr FM give the name of the actual FM and in to Fm give the name of the function module you want to copy.
3) Then click on copy.
4) Now open this new function in edit mode and goto the import/export parameters and check. it will have all the same parameters as the actual FM. Here you can make the changes you want.
5) Now use this FM in your virtual cube and it will be working as per your requirement
https://forums.sdn.sap.com/click.jspa?searchID=9605118&messageID=4999763
Hope it Helps
Chetan
@CP..

Regarding the Remote Function Module

hi,
Can any body can provide the brief information regarding the Remote Function Module.
1)How to create the remote function module
2)how it differ from the normal function module
3)any special features about this.
Thanks in advance

Hi
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
check out the following link it might help you
http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf
Function Modules;
Check this matter.
Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.
You can create them from TCode SE37.
Go through the following doc:
Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.
Function Module Interfaces
The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:
Syntax
... [IMPORTING parameters]
[EXPORTING parameters]
[CHANGING parameters]
[TABLES table_parameters]
[{RAISING|EXCEPTIONS} exc1 exc2 ...]
The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.
Interface parameters
The interface parameters are defined on the relevant tab pages in the Function Builder.
IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.
EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.
CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.
TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
Exceptions
The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
Note
For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
RFC is a technology which is used to access a functions (Modules) from
the remote systems.
If a function module is set as remote enabled which can be access from
the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
But Normal function modules can not accessd from the remote system.
Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
CALLING A FUNCTION MODULE:
1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
--> Write the Corresponding FM name --> Hit Enter
2)The appropriate import ,export Parameters will be displayed in ur editor
3)Pass the Values Here.
Also check these links.
http://www.geocities.com/victorav15/sapr3/abapfun.html
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
See the following links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
<b>Reward points for useful Answers</b>
Regards
Anji

ALE custom function module for IDOC_INPUT_COSTCENTER

We are setting up an ALE to update cost centers in our HCM system from our ECC system. In conjunction with the cost center update I need to convert the company code (it's not straight-forward enough to use a conversion rule) so I have created a custom copy of IDOC_INPUT_COSTCENTER and included my conversion logic there.
I have done all of the necessary configuration steps associated with the custom function module; created message type ZCOSMAS, process code ZCOSM, etc. When I execute BD16 it is passing the correct message type and process code to the HCM system but I am getting a status 51 'Function module not allowed: IDOC_INPUT_COSTCENTER'.
I must be missing some piece of configuration in my HCM system that should trigger Z_IDOC_INPUT_COSTCENTER rather than IDOC_INPUT_COSTCENTER. Can anyone tell me what I have missed?
Thanks in advance for any assistance you can provide.
Regards,
Pat
Edited by: Patricia Holland on Dec 22, 2011 2:38 PM

I thought that I had found found my problem in the model view but I was mistaken. I am still getting status 51 'Function module not allowed: IDOC_INPUT_COSTCENTER'.
It should be using Z_IDOC_INPUT_COSTCENTER.
Edited by: Patricia Holland on Dec 22, 2011 3:00 PM

How to bring the custom function module in WE42?

Similar Messages

Maybe you are looking for