Parameters in Function-Exit

Hi all,
I am using one Function-exit to read two screen fields and to pass a default value to another field. But in the function-exit there is no parameter for first field but i have parameters for second field and for the field which i need to export a value.
Please explain how can read the value in the first field.
Thanks,
Subhani.

Using field symbol i read the value of the first screen filed

Similar Messages

How to write BDC in Function exit (user exit )

Hi champs,
I am trying to write one bdc code in a function exit but it is giving me the error:
" Incorrect nesting: Before the statement "FORM", the structure
introduced by "FUNCTION" must be concluded with "ENDFUNCTION". -
The code which i have written is
**& Include           ZXMRCU01
data: begin of it_imptt occurs 0,
        POINT like imptt-point,
        MRMIN like imptt-MRMIN,
        MRMAX like imptt-MRMAX,
      end of it_imptt.
Internal table to store BDC screens   *
and field values                      *
DATA: BEGIN OF it_BDCDATA OCCURS 0.
        INCLUDE STRUCTURE BDCDATA.
DATA: END OF it_BDCDATA.
select point
       MRMIN
       MRMAX from imptt into it_imptt
       for all entries in imrg_ins
       where point = imrg_ins-point.
endselect.
read table imrg_ins with key point = it_imptt-point.
if imrg_ins-readg < it_imptt-mrmin
     or imrg_ins-readg > it_imptt-mrmax.
perform bdc_dynpro      using 'SAPLIQS0' '0100'.
perform bdc_field       using 'BDC_CURSOR'
                                'RIWO00-QMART'.
perform bdc_field       using 'BDC_OKCODE'
                                '/00'.
perform bdc_field       using 'RIWO00-QMART'
                                        'M1'.
perform bdc_dynpro      using 'SAPLIQS0' '7200'.
perform bdc_field       using 'BDC_OKCODE'
                                '=BUCH'.
perform bdc_field       using 'VIQMEL-QMTXT'
                                        'test desc1'.
call transaction 'IW21'
                        using it_BDCDATA
                          Mode 'A'
                            update 'S'.
REFRESH it_BDCDATA.
endif.
**&      Form bdc_dynpro
      text ---- Taking 2 parameters Screen Name & Screen Number.
FORM BDC_DYNPRO USING SCREEN_NAME SCREEN_NUMBER.
CLEAR it_BDCDATA.
it_BDCDATA-PROGRAM = SCREEN_NAME.
it_BDCDATA-DYNPRO = SCREEN_NUMBER.
it_BDCDATA-DYNBEGIN = 'X'.
APPEND it_BDCDATA.
ENDFORM.                    "bdc_dynpro
**&      Form bdc_field
      text---- Taking 2 parameters Field Name & Field Number.
FORM BDC_FIELD USING FNAME FVAL.
CLEAR it_BDCDATA.
it_BDCDATA-FNAM = FNAME.
it_BDCDATA-FVAL = FVAL.
APPEND it_BDCDATA.
ENDFORM.                    "bdc_field
Is there any different way of writing bdc in user exit?

<b>FUNCTION.</b>
**& Include ZXMRCU01
data: begin of it_imptt occurs 0,
POINT like imptt-point,
MRMIN like imptt-MRMIN,
MRMAX like imptt-MRMAX,
end of it_imptt.
Internal table to store BDC screens *
and field values *
DATA: BEGIN OF it_BDCDATA OCCURS 0.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF it_BDCDATA.
select point
MRMIN
MRMAX from imptt into it_imptt
for all entries in imrg_ins
where point = imrg_ins-point.
endselect.
read table imrg_ins with key point = it_imptt-point.
if imrg_ins-readg < it_imptt-mrmin
or imrg_ins-readg > it_imptt-mrmax.
perform bdc_dynpro using 'SAPLIQS0' '0100'.
perform bdc_field using 'BDC_CURSOR'
'RIWO00-QMART'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'RIWO00-QMART'
'M1'.
perform bdc_dynpro using 'SAPLIQS0' '7200'.
perform bdc_field using 'BDC_OKCODE'
'=BUCH'.
perform bdc_field using 'VIQMEL-QMTXT'
'test desc1'.
call transaction 'IW21'
using it_BDCDATA
Mode 'A'
update 'S'.
REFRESH it_BDCDATA.
endif.
<b>ENDFUNCTION.</b>
**& Form bdc_dynpro
text ---- Taking 2 parameters Screen Name & Screen Number.
FORM BDC_DYNPRO USING SCREEN_NAME SCREEN_NUMBER.
CLEAR it_BDCDATA.
it_BDCDATA-PROGRAM = SCREEN_NAME.
it_BDCDATA-DYNPRO = SCREEN_NUMBER.
it_BDCDATA-DYNBEGIN = 'X'.
APPEND it_BDCDATA.
ENDFORM. "bdc_dynpro
**& Form bdc_field
text---- Taking 2 parameters Field Name & Field Number.
FORM BDC_FIELD USING FNAME FVAL.
CLEAR it_BDCDATA.
it_BDCDATA-FNAM = FNAME.
it_BDCDATA-FVAL = FVAL.
APPEND it_BDCDATA.
ENDFORM. "bdc_field
Regards
Peram

How to read data from a function exit

Hi friends,
I have a requirement, where in i am creating a screen exit for ME51N.I am using MEREQ001 enhancement for this.It is working fine, but i am to get data in to this so as to write any code.For that i am using the function exit EXIT_SAPLMEREQ_001 in that same enhancement(thought of doing export and import).
But the data is declared in this way..
REFERENCE(IM_REQ_ITEM) TYPE REF TO IF_PURCHASE_REQUISITION_ITEM
so now it is having a method GET_DATA in which i have all the parameters required.
can anyone please tell me how to read this data...
Regards,
Thoufique.

thats ok friends..i got the solution.
Regards,
Thoufique

Function exits doubt

hi gurus,
I want to know about modifications on fm of enhancements.
suppose i have taken EXIT_SAPMIWO0_020 function exit for iw21 tcode.
in this i have seen *--- Move I_VIQMEL to exporting parameter E_VIQMEL
this syntax along with include zxqqmu20.
so how to use it.
i hered that there will be some modification structures to use above syntax.
how to find them .
kindly sugest me.
thanks to all,
padmaja.

To implement this exit you have to create a project in CMOD and activate this exit. Then you just double click on statement include zxqqmu20. This will give you a warning that ZX includes are resereved for enhancements which you are doing, so just confirm the warning and the include is created.
Within that include you can access all the import parameter of the function module and can also pass data to the export parameters of the function module. Implement your functionality within the include.
Hope that explains it,
Michael

FORM EXITS Vs FUNCTION EXITS

Hi folks
I am a little confused on FORM EXITS& FUNCTION EXITS...can anyone provide me what exactly is the differnce between these two. How we go about using these two in various scenarioes.
Thanks in advance.
Regards
Ram

Hi
There are 4 types of exits
like FUNCTIOn MODULE, MENU,FIELD and SCREEN exits
What is this form exits?
see the doc
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
How to implement screen exit for a SAP standard transaction HOT
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
Reward points for useful Answers
Regards
Anji

Re : creation of Function exit for Zfield

Can we create function exit for zfields similar to function exit for std field in SAP . If yes , How...?
Thanks in advance.

Hi Jhunu,
Try creating a field exit for the data element and see how it goes..
Run program RSMODPRF -> give the data element name and create a function module...There will be 2 parameters ...importing input and exporting output....write code accordingly
After activating the function module ...run the program again without entering the data element name
Select the required check box -> go to the top menu ->field exit -> activate
Let me know if it works out since we haven't tried it on a custom field yet
Hope it helps
Regards
Byju

How to log input parameters for Function Modules?

Hi,
I need to create a Logging system to trace input parameters for function modules.
The log functionality could be done by developing a class method or a function module (For example 'write_log'), and calling it within each function module that I want to log. The 'write_log' code should be independent from the interface of the Function Module that I want to log.
For example, I'd like to write a function/class method that can log both these functions modules:
Function DummyA
   Input parameters: A1 type char10, A2 type char10.
Function DummyB
   Input parameters: B1 type char20, B2 type char20, B3 type char20, B4 type Z_MYSTRUCTURE
Now the questions...
- Is there a "standard SAP" function that provide this functionality?
- If not, is there a system variable in which I can access runtime all parameters name, type and value for a particular function module?
- If not, how can I loop at Input parameters in a way that is independent from the function module interface?
Thank you in advance for helping!

check this sample code. here i am capturing only parameters (import) values. you can extend this to capture tables, changin, etc.
FUNCTION y_test_fm.
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(PARAM1) TYPE CHAR10
*"     REFERENCE(PARAM2) TYPE CHAR10
*"     REFERENCE(PARAM3) TYPE CHAR10
DATA: ep TYPE STANDARD TABLE OF rsexp ,
        ip TYPE STANDARD TABLE OF rsimp ,
        tp TYPE STANDARD TABLE OF rstbl ,
        el TYPE STANDARD TABLE OF rsexc ,
        vals TYPE tihttpnvp ,
        wa_vals TYPE ihttpnvp ,
        wa_ip TYPE rsimp .
FIELD-SYMBOLS: <temp> TYPE ANY .
CALL FUNCTION 'FUNCTION_IMPORT_INTERFACE'
    EXPORTING
      funcname                 = 'Y_TEST_FM'
*   INACTIVE_VERSION         = ' '
*   WITH_ENHANCEMENTS        = 'X'
*   IGNORE_SWITCHES          = ' '
* IMPORTING
*   GLOBAL_FLAG              =
*   REMOTE_CALL              =
*   UPDATE_TASK              =
*   EXCEPTION_CLASSES        =
    TABLES
      exception_list           = el
      export_parameter         = ep
      import_parameter         = ip
*   CHANGING_PARAMETER       =
      tables_parameter         = tp
*   P_DOCU                   =
*   ENHA_EXP_PARAMETER       =
*   ENHA_IMP_PARAMETER       =
*   ENHA_CHA_PARAMETER       =
*   ENHA_TBL_PARAMETER       =
*   ENHA_DOCU                =
   EXCEPTIONS
     error_message            = 1
     function_not_found       = 2
     invalid_name             = 3
     OTHERS                   = 4
IF sy-subrc = 0.
    LOOP AT ip INTO wa_ip .
      MOVE: wa_ip-parameter TO wa_vals-name .
      ASSIGN (wa_vals-name) TO <temp> .
      IF <temp> IS ASSIGNED .
        wa_vals-value = <temp> .
      ENDIF .
      APPEND wa_vals TO vals .
    ENDLOOP .
ENDIF.
ENDFUNCTION.

How to use the variables of Function exit in the include program

i have a problem of using the variables of a function exit in the include program..
If i use those variables there will be an error indicating 'Field FEBVW_IN is unknown. It is neither in one of the specified tables nor defined by a DATA statement'. Please help... Below is the code of the function exit:
FUNCTION EXIT_SAPLIEDP_202.
""Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(IDOC_CONTROL_INDEX)
*"     VALUE(IDOC_DATA_INDEX)
*"     VALUE(FEBVW_IN) LIKE FEBVW STRUCTURE FEBVW
*"     VALUE(FEBKO_IN) LIKE FEBKO STRUCTURE FEBKO
*"     VALUE(FEBEP_IN) LIKE FEBEP STRUCTURE FEBEP
*"     VALUE(FEBRE_IN) LIKE FEBRE STRUCTURE FEBRE
*"     VALUE(FEBPI_IN) LIKE FEBPI STRUCTURE FEBPI
*" EXPORTING
*"     VALUE(I_FIMSG) LIKE FIMSG STRUCTURE FIMSG
*"     VALUE(FEBVW_OUT) LIKE FEBVW STRUCTURE FEBVW
*"     VALUE(FEBKO_OUT) LIKE FEBKO STRUCTURE FEBKO
*"     VALUE(FEBEP_OUT) LIKE FEBEP STRUCTURE FEBEP
*"     VALUE(FEBRE_OUT) LIKE FEBRE STRUCTURE FEBRE
*"     VALUE(FEBPI_OUT) LIKE FEBPI STRUCTURE FEBPI
*" TABLES
*"      IDOC_CONTROL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_AVIP STRUCTURE AVIP OPTIONAL
*"      IDOC_AVIR STRUCTURE AVIR OPTIONAL
*"      IDOC_AVIT STRUCTURE AVIT OPTIONAL
*" CHANGING
*"     REFERENCE(IDOC_AVIK) TYPE AVIK OPTIONAL
*" EXCEPTIONS
*"      PROC_ERROR
INCLUDE ZXF08U10.
Here is the code for the include program.
INCLUDE ZXF08U10
MOVE febvw_in TO febvw_out.

Sometimes you will get this error message when checking include code in exits even though there is really no error - it happens because the include does not realise it is in the function due to the navigation index being out of date.
Try activating the code - it may work even though the check said there were errors.
You can also get this issue when trying to drill down on the field in the include to view its structure.
Andrew

What are the input parameters for Function Module

Dear Experts,
I want to generate a Sales Tax returns report,those fields are not available in my existing Datasources.
For that i want to write a Generic Datasource with Function Module.
audat
bukrs
vkorg
vtweg
spart
aurat
auart
netwr
mwsbp
kschl zedp(consition type)
kschl zvat(condition type)
ksch zcst(condition type)
matkl material group
Here what are the Input parameters for Function Module.
Thanks in Advance.
Srinivasan.

Srinivasan-
For creating a Generic extractor based on a FM, you first of all need to know what is going to be your structure.. i.e. what all fields you need to pull from what all tables. A functional consultant may help you identify the exact DB tables.
Once you know them, hand over the requirement and the pdf mentioned by Krishna to the ABAP guy, he would be able to take this up further.
Also decide 1st whether you would be using a full load or delta. There is a slight difference in the way they are built.
Let me know how it goes.
-Bhushan.

Need of Changing Parameters in Function Module

Hi All,
Why we need sepearte Import and Export parameters in Function Module if the Changing Parameters
acts as both import and export parameters.
What is the use of using Changing Parametrs in Function Module.
Thanks in advance.
Sundaresan

Hi,
EXPORT PARAMETERS: When u r passing some value to the function, and the parameter will not be changed in the function, we use export parameter. Example: u pass parameter (a : 10) to a function, even after the function has been executed, value of a will be 10 only.
IMPORT PARAMETER: When u require some value back from the function. u do not provide any initial value to the function. Example : u pass a parameter (b: <blank>) to the function, function returns the same import parameter as (b : 20).
CHANGING PARAMETER: When u pass some value to the function and that function may change that value inside function, then changing parameters are used. Example: u pass parameter ( c: 30) to the function as changing parameter and function modifies this variable and return ( c: 50).
Reward points if helpful.
Thanks & Regards
- Rishika Bawa

Activating only one function-exit in a multiple function-exit in CMOD

Dear All,
I am using customer-exit for doing validation in PO during saving. I am using EXIT EXIT_SAPMM06E_012 under enhancement
MM06E005. The code is working fine. The problem is that when I am activating the screen all the components under that enhancements are getting activated. There are 10 function-exits, 6 screen-exits and 2 incude tables. I have not added any new screen or done custom include. I only want to activate EXIT_SAPMM06E_012, rest I want to deactivate. It is giving a dump in production server when we are trying to create a contract as it is looking for a screen 0211 which we have not created.
Regards
D. Mallick

am using customer-exit for doing validation in PO during saving. I am using EXIT EXIT_SAPMM06E_012 under enhancement
MM06E005. The code is working fine. The problem is that when I am activating the screen all the components under that enhancements are getting activated. There are 10 function-exits, 6 screen-exits and 2 incude tables. I have not added any new screen or done custom include. I only want to activate EXIT_SAPMM06E_012, rest I want to deactivate. It is giving a dump in production server when we are trying to create a contract as it is looking for a screen 0211 which we have not created.
HI ,
You can activate only one function exit EXIT_SAPMM06E_012, But you must and should create below empty screen and active Using SE51.
SAPLXM06                       0101
SAPLXM06                       0111
SAPLXM06                       0201
SAPLXM06                       0211
SAPLXM06                       0301
SAPLXM06                       0311
Thanks & Regards
Sudheer Madisetty

Difference between Import and Export parameters in Function Module

Hi All,
I am unclear about the import and export parameters, when i create a function module. Can anyone explain abt this. However when i call the function module in any program the import parameters in Function module are displayed as exporting in program amd the export parameters as importing.
Any help on this would be appericiated.
Shejal.

HI,
Import parameter in FM is the value u provide to FM for processing.
export is the value u get from FM after processing.
when u call a FM in a progam the import parameter will appear as Export bcos u r giving value to the FM.
and u r getting value from FM in import parameter(bcos u r importing).
rgds,
latheesh
Message was edited by: Latheesh Kaduthara

Regarding SHipment function exit

Hi Experts,
I have to update some custom table in the function exit of VT01n transaction code based on some condition.
I have done it using update statement as it is custom table there is no problem.
BUT in the code After that UPDATE statement ,based on some condition i have to through a message which will stop the transactionn.
In that case if i exit from the transaction using exit button in the menu bar, the updated custom table has to roll back.
Can i use ROLL BACK Statement. in the function exit in that case.
If i use that ,does it effect any standard functionality.
Orelse is there any alternative solution for that.
Regards
Ramakrishna L

Hi Ramakrishna,
If u r updating the custom table in the same exit where u r throwing the message , don't use the commit work after updating the table. use it at end of the exit.
Regards,
Srinivas.

Named Parameters in Functions: Possible?

I want to use named parameters to call PL/SQL functions using JDBC, as is best practice and necessary for default values to work. Unfortunatley all the examples I found are for procedures only. Using a positional registerOutParameter with named register / get methods on the CallableStatement does not work, obiviously.
Is there any proper way to use named parameters with functions ? Proper does not include writing wrapper procedures nor turning functions into procedures.

Hi Avi,
as far as I know the return value of a PL/SQL function does not have a name, as oposed to the parameters of a PL/SQL function, which must have a name. One could argue that the return value of a function is called the same as the function itself. I have tried that option but it does not work.
Unfortunatley the method OraclePreparedStatement.registerReturnParameter refers to something else than the return value of a PL/SQL function. Is it possible that the developers of the driver have forgotten something?

Menu-exits, Function-exits & Screen-exits

What is Menu-exits, Function-exits & Screen-exits ? explain

Hi,
Why do you need enhancements ?
The standard applications do not offer some of the functionality you need. The R/3 enchancement concept allows you to add your own functionality to SAP's standard business applications.
What are the different types of enhancements ?
Enhancements using customer exits
Customers' potential requirements which are not included in the standard software are incorporated in the standard as empty modification 'shells'. Customers can then fill these with their own coding. Enhancements can relate to programs, menus and screens. Upward compatibility is assured. In other words, SAP guarantees that the jump from the standard software to the exit and the interface which call the exit will remain valid in future releases.
Enhancements to ABAP/4 Dictionary elements
These are ABAP/4 Dictionary enhancements (creation of table appends), text enhancements (customer-specific key words and documentation for data elements) and field exits (creation of additional coding for data elements).
What is customer development ?
Creating customer-specific objects within the customer name range.
What is SSCR ?
SSCR (SAP Software Change Registration) is a procedure, for registering all manual changes to SAP source coding and SAP Dictionary objects.
What is the difference between modifications and enhancements ?
Modifications mean making changes to the SAP standard functionality.
Enhancements mean adding some functionality to SAP standard functionality.
What are the disadvantages of modification ?
Modifying standard code can lead to errors
Modifications mean more work during software upgrades
What are the advantages of enhancements ?
Do not affect standard SAP source code
Do not affect software upgrades
when do you opt for modification ?
Customer exits are not available for all programs and screens within the R/3 standard applications. You can only use exits if they already exist within the SAP R/3 System . Otherwise you have to opt for modifications .
What are the various types of customer exits ?
Menu exits
Screen exits
Function module exits
Keyword exits
What is a menu exit ?
Adding items to the pulldown menus in standard R/3 applications .
13.What is a screen exit ?
Adding fields to the screens within R/3 applications. SAP creates screen exits by placing special subscreen areas within a standard R/3 screen and calling a customer subscreen from within the standard dynpro's flow logic.
What is a function module exit ?
Adding functionality to R/3 applications. Function module exits play a role in both menu and screen exits.
What is a keyword exit ?
Add documentation to the data elements of key words defined in the ABAP/4 Dictionary. The system displays this documentation whenever a user presses F1 to get online help for a screen field.
How do SAP organizes its exits ?
SAP organizes its exits in packages that are called SAP enhancements. Each SAP enhancement can contain many individual exits
Regards

Parameters in Function-Exit

Similar Messages

Maybe you are looking for