About field exits
Hi Gurus,
i have a problem, in MM01(Basic data1) there is field called Prod.hierarchy(dataelement is prodh_d), for this data element how to create Field Exits and how to assign to MM01 Tcode.
the code part i have to write is
1. To validate MARA-PRDHA field length (field exit can handle this). the field length should be 18 char.
2.Copy the value of MARA-PRDHA to MVKE-PRODH (the code of the field exit above, you can do field-symbol technique to transfer value from mara-prhda to mvke-prodh).
plz. do the needfull information with all the steps ASAP.
Thanks & Regards,
Sudheer.
You can create a field exit to the data element by running the report RSMODPRF.
You will then have to assign the the program name & screen No. (In this case the program name & screen No. in MM01 transaction.)
You will have to write a field exit for MARA-PRDHA and within that ensure that the field length is 18char.( The input value you read should be of 18 char).
You can read the screen field value by using the fn. module to read the screen values & put that value inside MVKE-PRODH. This can be written in another exit.
Important Things to Note.
1.You cannot debug a field exit.
2. Assign the correct program name & screen no. to activate the field exit.
3. This is written at data element level.
Hope this helps...
Let me know if you need any further details.
Regards
Deepu.
Reward Points if it helps.
Similar Messages
-
Official documentation from SAP about field exits as obsolete
Hi all,
I want to know if there is any official SAP documentation about the support of field exits. Because, I herad some time ago that they are obsolete and its use is not recomended from 4.6C onwards.
Regards,
EricCheck OSS note 29377.
-
I have created a function module 'FIELD_EXIT_ABREX'.Can I use other field value in this Function Module?How to implement it?
Hi,
Firstly decide the scope : Global or Local to screen.
Global Field Exits are trigerred from all Screens whereas for Screen specific needs the screen to be specified when we go for activating it....
Run program RSMODPRF and specify the field ...
Note : Screen name & data element may be different...so u have to specify Data Element & not Screen field name. Just to remind as this is common pitfall.
Now as u said 'FIELD_EXIT_ABREX' as the Func module created. This gets the screen value of field ABREX in variable INPUT of the Func Mod 'FIELD_EXIT_ABREX' and after processing u can return value throu variable OUTPUT.
You can write u r validations in the FM and do whatever. Just remember the value are lost as soon as this Field Exit is triggerred Again
I hope this should help you for further wwork and any other specific issue do post back ... we'll see dude.
<b>Do reward if this was useful and adds to u r knowledge / solves issue</b>
Regards, -
Hi all.
With a Field-exit we can only check a field, or also modify the field?
ThanksHi,
you can check and modify also.
Field and screen exit..
regards
vijay -
Documentation about Screen, Menu and Field Exits
Hi all!!
I need some documentation about Screen, Menu and Field Exits.
I´m very interested specially on steps by steps.
My mail is [email protected]
Helpful posts will be rewarded.
Thanks in advance and regards,
Manuel.<b>Types of Exits </b>
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
<b>Menu Exits</b>
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
<b>Screen Exits</b>
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
<b>Function Module Exits </b>
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
CASE okcode.
WHEN 'BACK OR EXIT'.
CASE sy-dynnr.
WHEN '100'.
SET SCREEN 0.
LEAVE SCREEN.
WHEN '200'.
**** Note that you can write any code that satisfy your needs. ****
**** But in this case, this was wrote as a sample code for reference sake. ****
**** And you can test it. ****
SET SCREEN 100.
LEAVE SCREEN.
ENDCASE.
ENDCASE.
reward points if it is usefull..
Girish -
Field Exit for customer master data
hi
i want to execute a check every time that we create a new customer
this check should check that the field "VAT REG.." is field and not blank
please your advice what is the best practice for this issue, field exit? badi? or is there any other way recommended
i think that there is option to use field exit but i don't know which field exit and how to do it
many thanksHi Meir,
You go to SE84, and enter the enhancement I provided. Then, you activate the user-exit and write your own code. You can consult your ABAP team, if you are not sure about implementing user-exit.
Regards,
Eli -
Need a document for field exit....urgent
Can any one please send a document for field exit or have a simple document on how to work on a field exit with screen shots. pls send it ...its urgent
Thanks and regards
Nandha kumar RHi,
A field exit is a type of user exit.
A user exit is a hook where you can inject your own add-on functionality or behavior to SAPs standard business applications without having to modify the original applications.
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
CASE okcode.
WHEN 'BACK OR EXIT'.
CASE sy-dynnr.
WHEN '100'.
SET SCREEN 0.
LEAVE SCREEN.
WHEN '200'.
Note that you can write any code that satisfy your needs. ****
But in this case, this was wrote as a sample code for reference sake. ****
And you can test it. ****
SET SCREEN 100.
LEAVE SCREEN.
ENDCASE.
ENDCASE.
Field exits (SMOD/CMOD) Questions and Answers
1. Field exit was created with CMOD, but is not processed when calling the screen.
- Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
- Set profile parameter abap/fieldexit to YES and restart the system.
- After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
- Do not work on different application servers since there may be some delay before the field exit is activated.
- The profile parameter must be set on all or none of the application servers.
- If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen
number (take care with subscreens).
- Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit use the name of the data element and not the field name.
- After transport, field exits are marked as active but will not be processed.
Tip: First try deactivating the field exit once more and then afterwards, activate it again.
2. How is performance affected by setting abap/fieldexit?
- If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an
update. The user should not notice any difference because screen generation is very fast.
3. Can you read the contents of other screen fields in the field exit?
- In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them
available to other field exits. Note here that field exits are always called and not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
4. How does the field exit behave on step loop fields ?
- After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system
variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
5. Can field exits be debugged ?
- No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
6. What can you do if the field contents are no longer transported to to ABAP/4.
- Check whether a value is assigned to the field OUTPUT.
7. When is the field exit called if a conversion exit is attached to the
data element ?
- The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the
ABAP/4 program also receives it.
8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@)
- This is an error in the kernel which no longer occurs as of 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
9. Field exit is not visible in CMOD, although created.
- If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_. This
function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix,
the data element is not displayed in CMOD.
10. Field exit is not executed although it is active.
- Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an
extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is
invisible.
- Field exits can only be executed for fields that are directly related tothe dictionary. If the relation is indirect, i.e. via an ABAP declaration ( LIKE ), no field exit can be executed.
11. Field exits on check buttons do not work
- Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on
them.
12. Field exits do not work on selection screens
SAP Field Exits
From 4.6c onwards, Field exits will no more be supported by SAP. They removed the function of field exit but they had given lot of flexibility through userexit.
However, if you still required it, here is how to activate it :-
First called up transaction CMOD.
Then called up transaction PRFB.
or
Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank). If required, new field exits can be created using program RSMODPRF (see the program documentation).
REFER THIS LINK ALSO.
defining screen fields using FIELD-SYMBOL
Thanks,
Shankar -
Is it possible to work with Field Exits in R/3 Enterp. Basis 6.20???
How could I work with them?
Yes you can.
SE 38 --> Prog RSMODPRF
http://www.sapdevelopment.co.uk/enhance/fexits.htm
But Have a look at OSS note 29377 as well:
Symptom
Problems and questions concerning field exits
Other terms
FAQ, Q+A, SMOD/CMOD, field exits
Reason and Prerequisites
Note
Field exits are frozen on the 4.6C maintenance level and are not further developed. This means that the existing functionality is kept with all restrictions (see also the last item below). Existing exits can be further used and are called at runtime as usual.
Existing exits can be maintained using program RSMODPRF (run the
program using transaction SE38). Activation of the field exits and
assignment of the dynpros can also be carried out using program
RSMODPRF. For this purpose, the program must be started without
parameters (input fields remain blank).
If required, new field exits can be created using program
RSMODPRF (see the program documentation).
Solution
1. Field exit was created with CMOD, but is not processed when calling the screen.
Since the field exit is not processed until PAI, an action must be triggered on the screen (Return, Save, ...).
Set profile parameter abap/fieldexit to YES and restart the system.
After activating the function module FIELD_EXIT... and the field exit, leave the transaction on whose screen the field exit is to be executed. The screen is not generated until the transaction is started.
Do not work on different application servers since there may be some delay before the field exit is activated.
The profile parameter must be set on all or none of the application servers.
If the field exit is to only be active on specific screens, check whether you chose the correct program and the correct screen number (take care with subscreens).
Generate the screen on which the exit should be active using SE51. It is possible that it was not correctly generated. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with SE38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
Using SE51 -> Field list, check that the screen field does have a reference to a data element. In the name of the field exit, use the name of the data element and not the field name.
After transport, field exits are marked as active but will not be processed. Tip: First try deactivating the field exit once more and then activate it again.
2. How is performance affected by setting abap/fieldexit?
If a screen is generated and the profile parameter is set, a check is run on 2 tables (TDDIR, TDDIRS) to see whether a field exit must be generated for the respective field. In practice, the screen load is not generated until the screen is selected after an update. The user should not notice any difference because screen generation is very fast.
3. Can you read the contents of other screen fields in the field exit?
In principle, every field exit can store its value in the global variables of the function group (TOP) and hence make them available to other field exits. Note here that field exits are always called, not only if an entry is made in the field or if the field is empty. In addition, it is not possible to make any assumptions about the order in which the field exits will be called in the future.
4. How does the field exit behave on step loop fields ?
After the user has entered data, the field exit is called in PAI as often as there are visible fields in the step loop. The system variable SY-STEPL is incremented each time. If a new value is assigned to the field, it is displayed in the module between LOOP and ENDLOOP. This module is also called once for each visible step loop line.
5. Can field exits be debugged ?
No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variables to the file system using TRANSFER... . These can then be analysed there.
6. What can you do if the field contents are no longer transported to ABAP/4?
Check whether a value is assigned to the field OUTPUT.
7. When is the field exit called if a conversion exit is attached to the data element?
The field exit is called after the conversion exit. This means that the INPUT field receives the data in the same format as the ABAP/4 program receives it.
8. Although a global field exit is inactive, a function module is called which does not exist (for example FIELD_EXIT_PROGRAMM_@). This can lead to an ABAP dump error when function module FIELD_EXIT_<data element name> is called.
This is an error in the kernel which no longer occurs as of Release 3.0C. As a temporary measure, it is useful to assign a program and a screen which do not exist to the field exit and then activate the field exit.
Due to performance reasons, the active/inactive indicator is stored in the screenload. This can cause inconsistencies between Source and Load. Generate the affected screen with se51. If you want to be sure that all screens that use the data element are regenerated, you can transfer Report rsmodfdg from the correction instructions and start it with se38. The Report uses the affected data element as the input parameter and regenerates all screens that use the data element.
9. Field exit is not visible in CMOD, although created.
If you want to create a field exit for a data element, a function module is proposed with the name FIELD_EXIT_<data_element>. This function module must exist for the field exit to work. If you do not create this function module, but do create one with a suffix, the data element is not displayed in CMOD.
10. Field exit is not executed although it is active.
Fields which do not have the 'Input field' attribute usually do not trigger a field exit. The field exit is designed to allow an extended input check. It is therefore only called for input fields - even if they are not ready for input at runtime of the application by LOOP AT SCREEN.
This rule does not apply, however, if the field is located within a steploop. Here the field will be always activated, even if it is invisible.
Field exits can only be executed for fields that are directly related to the dictionary. If the relation is indirect, i.e. via an ABAP declaration (<fieldname> LIKE <dictionary element>), no field exit can be executed.
11. Field exits do not work on selection screens.
Results from the previous item since ABAP-internal fields and never the original Dictionary fields are used on selection screens.
12. Field exists do not work on check buttons.
Field exits are only intended for input fields. As check buttons count as graphical elements, you cannot install field exits on them.
13. How can all screens that use a data element be generated?
If you want to be sure that all screens that use a specific data element are regenerated, you can transfer Report rsmodfdg from the correction instructions into a customer report (e.g. zsmodfdg). The Report regenerates all screens. In this way, you can ensure that active field exits refer to screens and that inactive exits cannot be called on any screen. The Report uses the affected data element as the input parameter. The affected data element is in the name of the exit: FIELD_EXIT_<data element name>.
14. Restriction of usage
Field exit technology was developed for input fields on dynpros and cannot be used for other/new dynpro elements. This means that this technology does not offer support for the new ScreenPainter elements such as graphical elements (e.g. checkbuttons, radiobuttons, dropdown listboxes), controls (except for table controls which are supported like a step loop), or selection screens.
Erwan -
Want to know about User exit in detail
Hi ALL,
I M NEW TO sap ABAP. I WANT TO KNOW ABOUT USER EXIT IN DETAIL. PLS DO THE NEEDFUL . If there are eny document regarding this pls mail to this id [email protected]
thanks and regards
NandhaHi Nanda,
Welcome to SDN,
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
User exits are used when the flow for a particular transaction has to take some other route other then the normal flow. this can be the case when you have to attach some additional functionality lik u need a customised screen, or new functionality (using a functional module). based on these things user exits can be classified as screen exits, function module exits, field exits( not used anymore). hope this gives some help on userexits.
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..
For More information on Exits, check these links
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 -
Hi Folks.
I have a question about user exit, or field exit. The question is that if is possible to fill a field with a value, depending on a value entered by the user within the same transaction.
Thanks for your help.
Regards,
Gilberto LiThe field Exit have only INPUT and OUTPUT, but u can validate using another values.
U can:
<b>1- Use the values in that Screen ( Using function GET_DYNP_VALUE)</b>
example:
DATA: l_vkorg TYPE STRING.
CALL FUNCTION 'GET_DYNP_VALUE'
EXPORTING
I_FIELD = 'RMMG1-VKORG'
I_REPID = 'SAPLMGD1'
I_DYNNR = '1004'
CHANGING
O_VALUE = l_vkorg.
<b>2- Use Parametes ID:</b>
example:
DATAL l_matnr TYPE MARA-Matnr.
GET PARAMETER ID 'MAT' FIELD l_matnr
<b>3- Get Data from tables using SELECT with any of the values that u can get in options 1 or 2.</b>
Example:
DATA:
l_matnr TYPE MARA-matnr,
l_mtart TYPE MARA-mtart.
IF INPUT is INITIAL.
GET PARAMETER ID 'MAT' FIELD l_matnr.
SELECT SINGLE MTART
INTO l_mtart
FROM MARA
WHERE MATNR = l_matnr.
Now I have the value l_mtart to validate.
IF l_mtart = 'Z001'
ENDIF.
Greetings -
Acessing global structure values in field exit function
Hi Friends,
I have created field exit on sold to party field while creating sales order. But inside of that field exit
i need to put one query on basis of sold to party and sales organization and division. But that field exit function having only one import parameter that is sold to party but from where i can fetch sales organization and division . How can i refer global program values. Can i use assign statememnt for that. Please help me.
Thanks a lot in advance.Hello
the original article about this topic can be found here:
[SAP User Exits and the People Who Love Them|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/208811b0-00b2-2910-c5ac-dd2c7c50c8e8]
Regards
Uwe -
Hi there!.
My customer is asking me to upgrade from 4.6c to ECC 6.0 their field-exits. But I've reading about Enhancement Framework, and for validations made for Field Exits, I would need a SAP Source Key Code to modify the SAP Object and implement the online validations in the screen SAPLCOMD Dynpro 3170.
Has someone tried to work with this new technology ? what could I do for Upgrade this Field Exits?..
Thank you very much for any help!.
AntonioHello,
There was a recent discussion onthis topic. Here's the link.
How to reduce input field length
Apart from the name of the Standard Report, I hope you'll find something else of use , too.
Regards,
Anand Mandalika. -
Are Field Exits Not Recommended ?
Hi everybody
I saw recently a post wich comments that Field-Exits are not more recommended and supported by SAP.
It's that true ? Why are these not recommended ?
where can i see informatión about that ? so i could justify their use or not.
Thanks for help.
Regards
FrankHi Frank,
Its not that you cannot use field exits now. Whatever was delivered by SAP will be supported but no further development will take place on enhancing field exits by SAP. See OSS note 29377. It will clear all your doubts.
It says -
Note
Field exits are frozen on the 4.6C maintenance level and are not further
developed. This means that the existing functionality is kept with all
restrictions (see also the last item below). Existing exits can be
further used and are called at runtime as usual.
Existing exits can be maintained using program RSMODPRF (run the
program using transaction SE38). Activation of the field exits and
assignment of the dynpros can also be carried out using program
RSMODPRF. For this purpose, the program must be started without
parameters (input fields remain blank).
If required, new field exits can be created using program
RSMODPRF (see the program documentation).
14. Restriction of usage
o Field exit technology was developed for input fields on dynpros
and cannot be used for other/new dynpro elements. This means that
this technology does not offer support for the new ScreenPainter
elements such as graphical elements (e.g. checkbuttons,
radiobuttons, dropdown listboxes), controls (except for table
controls which are supported like a step loop), or selection
screens.
Cheers. -
Hi Gurus,
i have a problem, in MM01(Basic data1) there is field called Prod.hierarchy(dataelement is prodh_d), for this data element how to create Field Exits and how to assign to MM01 Tcode.
the code part i have to write is
1. To validate MARA-PRDHA field length (field exit can handle this). the field length should be 18 char.
2.Copy the value of MARA-PRDHA to MVKE-PRODH (the code of the field exit above, you can do field-symbol technique to transfer value from mara-prhda to mvke-prodh).
plz. do the needfull information with all the steps ASAP.
Thanks & Regards,
Sudheer.Hi sudheer,
I didn;t get your question..
Do you want to add a field to the standard screen basic data 1 and have a screen exit to handle that field?
If this is the case check out SAP note 44410 .It talks about intergrating customer-specific fields in the material master maintenance.
Award points if useful.
Regards
Parag -
I would like to know about conversion exits.
i would like to know about conversion exits.
Hi,
Under Domain of a data element of a field, Output Characterestics field 'Convers. routine' is used to create conversion routines, system will do the data changes with in these routines while storing the data into table and retriving the data from table.
Ex: if coversion routine is defined as 'ALPHA' for a standard domain , with this value system will create two function modules.
CONVERSION_EXIT_ALPHA_INPUT
CONVERSION_EXIT_ALPHA_OUTPUT
you can also create your own conversion routines by defining the value in this field. i have defined conversion routine to convert NUMC type data to DEC type data with 'ZCNV'.system will generate two FM's. you need to write the code in those FM's according to your logic.
see the code for this :
CONVERSION_EXIT_ZCNV_INPUT
FUNCTION CONVERSION_EXIT_ZCNV_INPUT.
""Local interface:
*" IMPORTING
*" VALUE(INPUT)
*" EXPORTING
*" VALUE(OUTPUT)
DATA : ws_output type numc10.
ws_output = input.
output = ws_output.
ENDFUNCTION.
CONVERSION_EXIT_ZCNV_OUTPUT
FUNCTION CONVERSION_EXIT_ZCNV_OUTPUT.
""Local interface:
*" IMPORTING
*" REFERENCE(INPUT)
*" EXPORTING
*" REFERENCE(OUTPUT)
data : ws_value type dec12.
ws_value = input.
WRITE: ws_value TO output DECIMALS 0.
ENDFUNCTION.
Thanks & Regards,
Sunil
Maybe you are looking for
-
Is it possible to use old Apple Flat Panel Display (62 watt power adapter) with a MacBookPro 13" Mid-2012 laptop? Would like to use larger screen when working at home. I have a mini display port to VGA cable and have tried to hook up the old displa
-
AFP only works for Active Directory "Domain Admins"
I have purchased a new XServe to add to our Active Directory domain as a member server. It all seems to work right except that only users in AD who are members of the "Domain Admins" group seem to function properly under AFP. The Mac Clients can conn
-
SamplesApp from BEA Weblogic Workshop :handling data, binary Flow
Hi, Everything is fine if I want to upload an image, but I would like to upload another kind of file in a database, PDF for example, how I can access it after uploading and saving in a database? Are amy examples about this? Any help is appreciated. T
-
I have Photoshop Elements (Version 6.1.0.250) on my PC and I'm trying to install the updates (Elements 9.0.3 Update & Photoshop Camera RAW 6.5) but they keep failing continuously. What can I do?
-
I need to install software on a computer without a dvd drive. Where can I find the download for the student edition?