Custom user exit

can we develop our own User Exit

Hi,
Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
Regards

Similar Messages

Differnce Between Customer & User Exits

Pls tell me
What are various types of exits?
with Regards,
Manmeet singh

Hi Manmeet,
Differnce Between Customer & User Exits
In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.
There are the following types of user exit:
User exits that use INCLUDEs -
These are customer enhancements that are called directly in the program.
User exits that use tables -
These are used and managed using Customizing.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
· They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
· They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
User Exits:
User exits allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors in the enhancement process.
Types of Exits.
1)MENU EXITS
2)FUNCTION EXITS
3)TABLE EXITS
4)SCREEN EXITS
5)KEYWORD EXITS
6)FIELD EXITS
Menu Exits
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.
Function Module Exits
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.
screen exits:
http://help.sap.com/saphelp_erp2005/helpdata/en/94/bef83770798b76e10000009b38f842/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/13/1f2d1a831a43be8a43ecd14170bf1c/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
Function Module Exits
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.
Screen exits:
http://help.sap.com/saphelp_erp2005/helpdata/en/94/bef83770798b76e10000009b38f842/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/13/1f2d1a831a43be8a43ecd14170bf1c/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
Regards,
Priyanka.

Questions about authorization variable customer user exit

Dear all,
To reduce the authorization maintenance effort, I found from the web that we can use authorization variable with customer user exit RSR00001.
When I use the transaction CMOD to display the maintain the user exit RSR00001, the user exit does not found. I would like to know how can I use thie user-exit?
My SAP version is R/3 4.7
The information of authorization variable from web is as follow:
http://help.sap.com/saphelp_nw04/helpdata/en/6d/58f438114ee836e10000000a114084/frameset.htm
Would anyone have some ideas to solve my questions?
Many thanks
Sunny
Edited by: LI Sunny on Aug 3, 2010 12:08 PM

Dear Bala Duvvuri,
Firstly, many thanks of your reply.
Actually, what I want to do is to call some user-exit when performing authorization checking. I want to add some logic to the authorization checking and the user exit can be called automatically when performing authorization checking.
I mainly use this checking in the FI module.
Are there any ways I can perform this checking?
One more findings, I have another machine containing SAP XI, I can search the user exit RSR00001. but it doesn't exit in SAP R/3 4.7. Is it version issue or my SAP R/3 4.7 doesn't contain the BI module?
Many Thanks again.
Sunny

Block the customer user EXIT

dear sap gurus
is there any user exit can enable us to block the customer (XD05) when using a specific document type
EXAMPLE:When using a document type X trigger transaction (XD05)

Hi,
Donot use call transaction in any of the user exits or badis
I will give you an idea but not the source code. Find a suitable exit or badi for transaction F-02 or FBZG ( as per your requirement ) . In the exit use class CMD_EI_API method MAINTAIN_BAPI and populate the values as required
for blocking/unblocking customer. Thiswill only get executed when a commit work is invoked by the transaction.

IPC Pricing with AP 7.00 Database Access/Call function module user-exit

Hi experts,
we are running SAP ECO on SAP ECC 6.0 with IPC Pricing AP 7.00 running in the VMC.
I'm facing a new requirement. In an user-exit for requirements the access to the ABAP database is needed.
(I know that the SAP recommendation is, don't have access to database. But we need this functionality)
In ABAP it looks like:
select single * from a590
      into     LH_674_a590
      where    kappl = 'V'
      and      kschl = 'ZSPR'
      and      kunnr = komk-kunnr
      and      matnr = komp-matnr
      and      datbi >= komk-prsdt
      and      datab =< komk-prsdt.
Is there a possibility to implement the same SELECT in the Java-User-Exit?
Is there maybe the alternative to call a function module instead?
The database exits on the same application server on which the VMC runs.
If there is a possiblity can anyone provide me with sample coding or give an advice where to find samle coding?
I would prefer to call a functions module.
Thanks in adcance
Karl-Wilhelm

Hi Shanto & Sumit,
Thanks for the inputs.
as per my understanding of the log
java.lang.IncompatibleClassChangeError: com.sap.leasing.pricing.tools.LeasingPricingTools: method getPricingConditionByConditionTypeName(Lcom/sap/spe/pricing/transactiondata/userexit/IPricingItemUserExit;Ljava/lang/String;)Lcom/sap/spe/pricing/transa ctiondata/IPricingCondition; used to be stati
error is thrown by the SAP standard user exit and because of which execution is failing in customer user exits and surprisingly we have not made any changes in both of them.
this was working earlier before upload.could this be because of the jar packaging.
how i can download the standard user exit com.sap.leasing.pricing.tools.LeasingPricingTools from crm
for further investigation.
Thanks,
Siddharth

Sales Order - user exit at item level

I am new in writing user-exits. Pls do share your exp !
When creating a sales order I encounter error, system says "Enter batch number".
We basically create batch when doing GoodsReceive for Production Orders. At this time the Material Revision is copied as Batch into MCHB table.
For example:
Material ABC has the below,
Rev    Batch
A        A
B        B
C        blank
If I create a SO for part ABC for Rev C, it does not allow me becos batch does not exists. But my SO should be allowed to be copy C into the batch field in VBAP.
Pls let me know if we must create custom user-exit rather than modifying std.SAP user-exit for Sales Order processing (MV45AFZZ).
Is there any contraints using the batch field in SO? As I came to know that the problem is when creating a Purchase Order it allows to enter free text in batch field but SO doesnt allow. Is't?
Is there any standard way to config the system such that SO will bypass the existence checking of the batch
Pls share !
Pri

Hi, but inplace of Batch we only enter the Revision of the material. Becos rev-batch relationship is 1-1, meaning is rev is A, the batch will be A too.
We just use the batch field to represent the revision
Rev    Batch
A        A
B        B
C        blank
I can enter A in SO item batch field because system check that batch A exists
I can enter B in SO item batch field because system check that batch B exists
But I cant enter C in SO item batch field because system check that batch C doesnt exist
Wondering how the system might know the batch is actually my revision. Not sure if I use User EXIT to move C into VBAP-CHARG, will it give me error message because it will find out that there is no C batch
Your views !

BADI/User exit for MIGO fi postings

Hello Experts,
I have one requirement regarding at the time of MIGO accounting entry is generating based on the OBYC settings,now the client want along with this entry, want to create one more FI document through background,In the background we will give the debit g/l and credit g/l.That means at the time of MIGO two FI documents has to generate one is with OBYC setting gl's and second FI entry is from programe hard coded gl's.
For this requirement has any BADI/USER Exit.I appriciate your valuable inputs.
Regards,
Nivas.

Hi,
May I know why you need two accounting documents?
You may refer the similar thread: BADI / Exit required for MIGO for posting FI document
And about the number ranges - I would suggest a custom number range object and a different number range for these additional documents.
Also refer the doc: Methods to find Customer/User Exit's & BADi's for a Transaction Code!
Regards,
AKPT

SAP ISU - User exits at the end of move-in process

Hi,
We have a requirement to send some outbound messages on completion of Move-in process in SAP ISU system. And send some outbound message on completion of Reverse Move-in process.
I tried to find the customer/user exit in transaction EC50E and EC53E, all i could find is user exits during the process. I need something at the end of process.
At the moment all I can do is use the events raised when these process are completed (Ex: MOVEINDOC.Created) and start a workflow to send outbound messages. But i would want to know if there are any exits available at the end of the processess as I dont want to create a workflow just for one activity.
Any inputs will be appreciated.
Many Thanks,
Anand

very old item - closed

Code Review of User Exits with Code Inspector

Hi,
We are using Code Inspector(Tcode - SCI) for checking the quality of ABAP Codes. It is working fine for all custom programs. But when we are checking the code of User Exits i: e MV50AFZ1 or ZXM06U22 then it checks the std SAP program (SAPMV50A) or (SAPLXM06) for these exits in place of checking that particular Exit only . How the customer/User Exits can be checked using Code Inspector. Pls advice.

Hi there!
Today, I stumbled over the same problem: Defining an Include for user exits leads to a check of the surrounding function group from SAP which I don't want to correct at all.
Is there a nice an elegant way of filtering out the SAP modules from checking? If not, the only way to get around this seems to be building an own implementation of the Code Inspector integration into CTS.
Thanks, Markus

User Exit issue after upgrade from 4.6c to ECC 6.0

Hi Experts,
After upgrade we are facing some issues regarding user exit. In 4.6c we have implemented several user exit to do customization in several module like SD,FI and HR. But after upgrade it has been identified that SAP has already provided this functionality in ECC 6.0. Now our problem is when this transactions are called or executed control is going to both custom and standard code. Which took long time to execute and causing performance issue.
Is there any ways to identify which are the functionality SAP has provided in ECC 6.0 so that we can delete our custom user exits.

Hi
List all the user exits which you have modified and check in OSS notes you will get the OSS note with all the details what functionality has been changed. Based on this you can delete or retain the user exits which ever you want.
Regards,
JB

Can the user exit EXIT_SAPMM07M_004 be called from an FM exit in my code?

Hi ,
When I create a Goods Receipt by tx MB1C , an MM adapter(FM user exit) is kicked off in my workspace creating documents wrt to that goods receipt.However if a batch does not exist during MB1C , it says that a batch would be created.But when i do a save , the user exit is kicked off before it returns to the SAP code to create a batch.As a result no MM documents are created in my workspace.Now I want that the batch be created while in my user exit and I want to implement the customer user exit EXIT_SAPMM07M_004(for copying the batch characteristics) .Is it possible to call this exit from my code?Kindly suggest.

> When I create a Goods Receipt by tx MB1C , an MM adapter(FM user exit) is kicked off in my workspace creating documents wrt to that goods receipt.However if a batch does not exist during MB1C , it says that a batch would be created.But when i do a save , the user exit is kicked off before it returns to the SAP code to create a batch.As a result no MM documents are created in my workspace.Now I want that the batch be created while in my user exit and I want to implement the customer user exit EXIT_SAPMM07M_004(for copying the batch characteristics) .Is it possible to call this exit from my code?Kindly suggest.
Can you call the user exit? - Yes ofcourse.... but why dont you just add the same code that is in your exit instead of calling the user exit?
User exits are developed and called from appropriate places where sap can take the changes and apply to the transaction. there is no restriction on calling the user exit (atleast programmatically) but you need to think 100 times before you call the user exit.
For example, you want to call user exit 'A' in your program because you want to use the code in this user exit in your program '1'. Why dont you just write the code in program '1' with what is in user exit 'A' ?
Calling user exit in your program does not really helps. Better find out different ways. once again, user exits are embedded in sap business applications and remember they are not independent FM's as you think
Good luck

Include or sub-routine in user-exit

Hi all,
i want to put a sub-routine in my customer user-exit (CMOD).but i can not put the subroutine.
can i put a subroutine or include statement in a user exit?
correct answers will be rewarded.
Thanks
pabi

You can make subroutine calls inside a User exit, only if the exit is part of a function pool. All the subroutines can be placed in an include in the function pool & can be called with a Perform Statement from the User Exit.
~Suresh

Brief about enhancements and user exits

hai,
can any one tell me what are enhancements and user exits in sap sd,
their signifcance & configuration
regards
sriram

hi,
an example of user exit
In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the Target *** Qty required and the Target *** Date for a specific customer who was not sending *** Qty Received by him.
So for that specific customer we used the search term and added the same in the Data 4 field of the IDOC under segment E1EDK09.
There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating *** Issued and then find out the difference from Target *** Qty and get *** Qty Received for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
<b>User exits in SD</b>
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Pl reward if helpful.
Thanks
Sadhu Kishore

User exit info

will someone guide me on usage of USER-EXIT ,
FUNCTION-EXIT & how to use them ? what all things i
have to do initially ? what transaction i have to use
for starting these EXITS?

USER EXITS->
User exits (Function module exits) are exits developed by SAP.
The exit is implementerd as a call to a functionmodule.
The code for the function module is writeen 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>
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
CUSTOMER EXITS-> t-code CMOD.
As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.
Among others, this enhancement technique has the advantage of
being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,
customer, and so on)
instead of a two-level landscape (SAP, customer) as with the customer exits.
You can create definitions and implementations of business add-ins at any level of the system landscape.
To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
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
Look at the below link, it will solve your Prblem
http://www.sap-img.com/abap/what-is-user-exits.htm
Re: what is the difference between User exit and customer exit
the following links give u a clear picture abt customer & user exits
User-Exit For MIGO_GR
This will surely help:
examples of user exits in SD and MM module
Reward points if useful
Regards,
Nageswar

Urgent: USER exit for W2 Box 13 of Tax reporter 4.7

Hi,
I am working on tax reporter version 4.7 and while printing the W2 forms saw that the Box 13 (selection of Statutory employee or Retirment plan or third party sick pay ) is not ticked. I worked in one of the clients on ECC 6.0 last year whom had a custom user exit for this same box 13 of W2 which used to get ticked on W2 form depending on the logic in that user exit.
I suggested to this present client that an user exit needs to be written, they asked me to write functional specs for the user exit, can someone help me in writing the functional specs for this W2 form Box 13 selection of Tax reporter on 4.7. what do I need to specify and how do i need to write the functional specs reflecting the logic of this Box 13 of W2 form in tax reporter. Please help me guys, its very urgent.
I apprecite your answers.
Thank you so much
Tony

Hi Oscar Romero,
Sorry its an typo error. second range should be 001.2006 to 007.2006.
1. I want to know how to create Multiple Interval(Range) value variable? - I have used selection option and created variable. Is it correct?
2. Pls find my coding.
when 'ZFISCYAC'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZFYPEROP'. ---> Value entered is 001.2005 - 012.2006
CLEAR L_S_RANGE.
L_S_RANGE-LOW = LOC_VAR_RANGE-LOW(4).
L_S_RANGE-LOW4(3) = LOC_VAR_RANGE-LOW4(3).
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZSCENAR'. -
> Value entered 20060804, 20060705.
*concatenate LOC_VAR_RANGE-LOW(4) '0' LOC_VAR_RANGE-LOW+4(2)
*into L_S_RANGE-high.
L_S_RANGE-high = LOC_VAR_RANGE-LOW(4).
L_S_RANGE-high+4(1) = '0'.
L_S_RANGE-high5(2) = LOC_VAR_RANGE-LOW4(2).
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'BT'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDLOOP.
ENDLOOP.
ENDIF.
Final range should be for 20060804, "ZFISCAY" should be from 001.2005 to 008.2006
For 20060705 range should be 001.2005 to 007.2006.
*Coding for Filling variable "Fiscal year/Period Plan Multiple values
when 'ZFISCYPL'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZSCENAR'.
CLEAR L_S_RANGE.
L_S_RANGE-LOW = LOC_VAR_RANGE-LOW(4).
L_S_RANGE-LOW+4(2) = '00'.
L_S_RANGE-LOW6(1) = LOC_VAR_RANGE-LOW4(2) + 01.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGE
WHERE VNAM = 'ZFYPEROP'.
L_S_RANGE-HIGH = LOC_VAR_RANGE-high(4).
L_S_RANGE-HIGH4(3) = LOC_VAR_RANGE-high4(3).
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'BT'.
APPEND L_S_RANGE TO E_T_RANGE.
ENDLOOP.
ENDLOOP.
ENDIF.
With same variable values entered as above plan value for variable "ZFISCPL" should be of range 009.2006 to 012.2006 for 20060804
Range should be 008.2006 to 012.2006 for 20060705.
Hope this is clear.
Pls answer very urgent.
Thanks.
Bhuvana.

Custom user exit

Similar Messages

Maybe you are looking for