Key Date a Customer Exit and Variant use
Hello,
I have a query and it includes time dependent data. The key date uses a variable that is filled with the current date in a customer exit. Works nicely when the query is executed. However, if I save a variant with various values for variables on the starting/selection screen, the date is saved as a constant date and not dynamic based on the current date so that when the variant is selected to be used on a different day, the key date is the date the variant was saved and not the current date. This can be handled in R/3 ABAP report variants but I've not found a way to do it in BEx. Any help?
Thanks,
Diane
Hi,
If you are running on BI 7.0 you can maintain variants with the below code. make data sy-datum instead of user input.
You can also chect the document. It also contains a method for bw 3.5 variants.
You can schedule this program in a process chain or make variations of this as needed.
[How To
Troubleshoot Information Broadcasting (BEx Workbooks)|http://www.sapadvisors.com/resources/HowtoInformationBroadcasting.pdf]
*& Report Z_MASS_VARIANT_MAINTENANCE *
*& Program to mass update BEx Variants within SAP NetWeaver 2004s *
REPORT Z_MASS_VARIANT_MAINTENANCE.
parameter variable like RSRVARIANT-VARI.
parameter vname like RSRVARIANT-VNAM.
parameter sign_01 like RSRVARIANT-SIGN.
parameter opt_01 like RSRVARIANT-OPT.
parameter low_01 like RSRVARIANT-LOW.
parameter high_01 like RSRVARIANT-HIGH.
tables: RSRVARIANT.
select * from RSRVARIANT.
if rsrvariant-VARI = variable AND rsrvariant-vnam = vname.
rsrvariant-SIGN = sign_01.
rsrvariant-OPT = opt_01.
rsrvariant-LOW = low_01.
rsrvariant-HIGH = high_01.
elseif rsrvariant-vnam = vname.
rsrvariant-SIGN = sign_01.
rsrvariant-OPT = opt_01.
rsrvariant-LOW = low_01.
rsrvariant-HIGH = high_01.
endif.
update rsrvariant.
if sy-subrc <> 0. insert rsrvariant. endif.
endselect.
regards,
Similar Messages
-
Difference between user exit/Function exit / Customer exit and BADI
Hi Guys,
I am confused with the types of exits-user exit/Function exit / Customer exit and BADI.
Can you tell me the difference between the different exits/Enhancements?
Classify the following:
what is the one which is shown in SMOD under enhancements? There are 3 sections in that - Function module, Screen and includes.
What is the one which are called using -
Call Customer-Function 001?
Regards,
Guruhi,
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.
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).
advantages of enhancements
Do not affect standard SAP source code
Do not affect software upgrades
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.
Various types of customer exits
Menu exits
Screen exits
Function module exits
Keyword exits
Menu exit
Adding items to the pulldown menus in standard R/3 applications .
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.
Function module exit
Adding functionality to R/3 applications. Function module exits play a role in both menu and screen exits.
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
Hope this helps, Do reward. -
Diff b/w "Customer exits" and "User-exit"
Hi,
What is the difference b/w customer exits and user-exit and also please explain me what are the various types of customer and user-exits.
Thanks in advance.
RamanaHi,
Types of Exits
There are several different types of customer exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
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.
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.
Screen Exits
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.
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 pulldown 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.
<b>User exits:</b>
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-code-samples/userexits%20in%20a%20transaction.doc
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
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
http://www.easymarketplace.de/userexit.php
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
Check out these links too...
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
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
USER EXITS
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
****Reward points if helpful.
All the best -
Difference between customer exit and user exit?
hi experts
difference between customer exit and user exit?These r the main differences between user exits and customer exits
1) user exits r subroutines where as customer exits r function modules
2) user exits r not upgraded where as customer exits r will upgrade
3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
4) customer exits r reusable where as user exits r not reusable.
Also:
1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
Please go through the following link which will help you understand the exits in a much better way:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
http://sap.niraj.tripod.com/id21.html
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.sap-img.com/ab038.htm
User Exits.
http://www.erpgenie.com/sap/abap/code/abap26.htm
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
customer exits
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
Menu Exit.
http://www.sappoint.com/abap/spmp.pdf
http://www.sappoint.com/abap/userexit.pdf
http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
1. Previously there were only user-exits.
2. Then came the concept of customer-exits.
3. user exits were nothing but subroutines
FORM/PERFORM
called from standard programs.
4. The FORM defintion was placed inside
an empty include file.
5. So It was called EVERYTIME.
and we need to MODIFY/REPAIR the
standard include .
6. Then it came with concept of customer-exit
7. It consists of calling a FUNCTION MODULE,
which is called only if
the user-exit is ACTIVATED (other wise not called)
In this case, the code in put inside
a pre-defined Z include.
8. Functionality of both is same, howerver
we can note the following important differences
a) Customer exit is called only if activated.
(hence, it does not waste resources)
b) in customer exit, REPAIR does not happen
to the standard include.
Exits are basically the hooks whcih SAP has provided to add your own code.
User Exits: These are provided only SD module .
They are Empty subroutines with naming like USEREXIT_.
We need to have Access key to implement them.
Customer Exits: These are enhancement techniques.
There are defined in SMOD and implemented in CMOD.
Types of Customer exits: Function exit, Screen Exit, Menu exit.
User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
Customer Exit,
Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
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
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
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
reward points if found useful
regards
palak -
What is the difference between customer exits and user exits?
hello friends,
what is the difference between customer exits and user exits?Hi
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
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. *-- Mani
The following document is about exits in SAP :-
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 user 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.
Types of Exits
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.
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.
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.
Screen Exits
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.
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.
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'.
SET SCREEN 100.
LEAVE SCREEN.
ENDCASE.
ENDCASE. -
How to find out the customer exit and sap exit variables created provider?
Hi all,
How to identify what are all the customer exit and sap exit variables are been created for an info provider. is there any tables which allow us to find out.
thanxs
harithaHello haritha,
SAP Exit and Customer Exit variables are created for Characteristics and not for individual InfoProviders.
So whenever the characteristic is used in the InfoProvider, by selection the appropriate variable the exit can be called.
So the same Exit can be in one or more InfoProviders.
Hope it helps.
Thanks,
Chandran -
Data Replication Between Sqlserver and Oracle11g using materialized view.
I have Sqlserver 2005 as my source and oracle11g as my target.I need to populate the target daily with change data from source.
for that we have created a dblink between sqlserver and oracle and replicated that table as a Materialized view in Oracle.
problem we are getting here is Fast refresh option is not available.each day it will pick full data from the source.
is there any way to use Fast refresh in this scenario??
Thanks in advance.
Regards,
Balaram.Pl do not post duplicates - Data Replication Between Sqlserver and Oracle11g using materialized view.
-
Difference between customer exits and user exits
difference between customer exits and user exits
Hi,
USER EXITS->
1. Introduction:
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
Regards
Kiran Sure -
BW Master Data for Customer Exit Variable Reference
Good day Experts,
I have several queries that I would like to remove the hard coding of values on to prevent yearly maintenance. In these queries there are two conditions each condition is on different key figures that is amount by year. The query is only to report on data that for the two amounts (separated by year) is greater than the specified values. I want to change the condition so the value is no longer hard coded so the query will role automatically as the time period changes. The year amount values that the condition will need to reference are not currently stored in our BW system. I would like to create master data that is maintained directly in the BW system for the amounts that a variable for the condition in the query can then access.
I know it can be set up as master data and then referenced through a customer exit variable but when I set up the master data if I do the Amount as a key figure I cannot maintain the key figure value for the master data manually in BW, if I set the Amount up as a numeric characteristic then I canu2019t directly use a decimal. Am I missing something in the key figure setup then referencing the key figure as an attribute of the year value or do I need to do it as a characteristic and use a conversion routine or something for data manipulation?
Can someone please give me some guidance to what the best way to do this is?
The data necessary master data for storage in BW is the YEAR and a single dollar value:
For Example:
Year Amount
2009 101.50
2008 207.80
2007 807.40I figured out that I can use an amount in the master data and maintain the amount manually as long as I use the amount with a currency instead of setting the currency in the key figure.
-
Is there a list of open items at key date per customer?
Hello,
In FBL5N you can get a list of open items for a customer at some specific date.
I'm looking for a summarized list that would give me a list of sums of open items for some customer per day, so I would see for example for one month what was the sum of open items for this customer on each day.
Is there already some similar report in SAP?
Thanks and best regards,
DavidHi,
I still don't think we understand each other.
If I run FBL5N I have option to select:
- Items that are or were open at the key date are displayed on one date
- All items posted on the posting date specified fromde date1 to date2.
- Items that were cleared at the clearing date specified
I would like a list of all items from option 1 (Items that are or were open at the key date are displayed on one date) so items that are or were STILL open and not yet cleared on one date, but not just for one date but for more days.
If I use your suggestion I get what items opened or cleared on one day not how many items were still open on particular day.
So a list of how many opened items were there at the day, and notjust items that were opened on that day but also all previous items that were not yet cleared at that day. -
Concatination of Two dates in customer exit Variable
HI Expert ,
I am writting customer Exit Variable to get Records from user entered Dates .
Eg. In Variable Screen of Bex report i have 2 Variable LYDate & TY Date both of them are As "Mutiple Single Value" & "Mendetory".
If we give LYDATE and TYDATE Date range as,
LYDate - 01/2013 - 06/2013
TYDate - 01/2014 - 12/2014
So I need ABAP Code which will get Value Range from 01/2013 from LYDATE and 12/2014 From TY DATE . So Query will Get data for 01/2013 TO 12/2014 (2 Years Data).
ZCALYEAR (Cusomer Exit) = LYDATE (01/2013) TO TY DATE(12/2104).
Please provide step by step ABAP Code to Achiev above issue. Points for Sure...
Thanks,
GBHi,
Some code like this will solve your issue:
CASE I_VNAM.
WHEN 'NEWVARIABLE'.
IF I_STEP = 2.
READ TABLE I_T_VAR_RANGE INTO LOC_VAR_RANGE WITH KEY VNAM = 'LYDate'.
If sy-subrc =0.
CONCATENATE LOC_VAR_RANGE-LOW(4) INTO L_S_RANGE-LOW.
READ TABLE I_T_VAR_RANGE INTO LOC_VAR_RANGE WITH KEY VNAM = 'TYDate'.
If sy-subrc =0.
CONCATENATE LOC_VAR_RANGE-HIGH(4) INTO L_S_RANGE-HIGH.
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'EQ'.
APPEND L_S_RANGE TO E_T_RANGE.
endif.
endif.
endif.
endcase.
Regards
Yasemin...
Just realized that you need the year. Message was edited by: Yasemin ULUTURK -
Derive 0OBJ_CURR from 0COST_CENTER master data in customer exit
Hi,
I'm having trouble with the syntax in the following case:
I'm trying to create a customer exit variable for reporting which is reading the cost center value from cost center variable (ZIPCC) and then using that value to determine the home currency of that cost center by reading the 0OBJ_CURR field from cost center master data.
The code is as follows:
DATA D1 Like 0OBJ_CURR.
remark: Object currency is unit. How to declare units?
WHEN 'ZIPCUR'.
if I_STEP = 2.
loop at i_t_var_range into lt where vnam = 'ZIPCC'.
Select single OBJ_CURR into D1 from /BI0/PCOSTCENTER where COSTCENTER = i_t_var_range-low.
remark: I'm having also trouble with the selection of OBJ_CURR.
clear l_s_range.
l_s_range-low = D1.
l_s_range-sign = 'I'.
l_s_range-opt = 'EQ'.
append l_s_range to e_t_range.
endloop.
endif.Found the answer, to bad i cannot give points to myself :-P
In the ABAP i use the E_T_RANGE output structure.
That structure has several fields (sign, opt, low, high).
In my ABAP i stored the same value in the low and high field.
This should work fine for normal (flat) characteristic values.
However, because i use a hierachy i should enter the 0HIER_NODE value in the high field.
For details see: SAP NOTE: 912473
Regards -
Difference b/w Customer exits and User Exits
Hi,
Can anybody explain diff b/w user exits and customer exits .
How to find out and Impement the coding ..
Thanks Advance
Rohan.AHi Rohan,
Check this matter , this may be helpful to you.
<b>CUSTOMER EXITS</b>
The 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 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.
<b>User exits :</b>
1. Introduction
2. How to find user exits
3. Using Project management of SAP Enhancements
1. Introduction:
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>
Example:
The program for transaction VA01 Create salesorder is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION i program
SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
Hope this is helpful.
Reward all the helpful answers.
Regards -
RSCRM: Query date with customer exit variable
Hi All,
Is there any way to run the RSCRM transaction with a query with a customer exit variable for a date characteristic?
The issue is that the query ran ok but the variable is not being updated when the RSCRM query is running with a background job or a process chain.
Thanks in advance
EVI do not think you can select Customer Exit variable, if you see the type is selected to Char Value Variables and it is not editable.
It would be suggested to go for Customer Exit procesing type for your text variable.
Cheers,
Neel. -
Need logic to find Year to Date for customer exit variable
Hi to all,
I am creating customer exit variable for query .
query should display data according to current system year from jan till current system date.
here senario is like that user never enter year and query will automatically will fetch the data according to current year starting from jan to current system date.
example.
current year 2010 and today is system date is sep 29 2010, so query will display data from jan 2010 to current data sep 29 2010.
please can any one provide me logic for that.
any code .
regards
pavneet ranaHi,
You need to create the characteristic customer exit variable of type select-options. Restrict your keyfigure based on this variable.
In the logic in CMOD,
write as below
i_step =2.
case i_vnam.
When 'exit variable'.
temp = sy-datum+0(4).
concatenate temp '0101' into temp1.
l_s_range-low= temp1.
l_s_range-sign = 'I'.
l_s_range-opt = 'BT'.
l_s_range-high= sy-datum.
append APPEND l_s_range TO e_t_range.
endcase.
For any further help on customer exit based variable, please refer below article.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f119d9-922d-2c10-88af-8c016638bd90?quicklink=index&overridelayout=true
Edited by: Rahul K Rai on Sep 29, 2010 3:09 PM
Maybe you are looking for
-
I HAVE iTUNES v 10.6x installed on my Macbook Pro - been using for quite awhile without issues. All Updates to iTunes have gone just fine. I also use Parallels Desktop with Windows XP Pro installed on it and within that Windows installation on this
-
Can't update Apps. Wants me to verify old Apple ID that no longer exists.
This is really annoying. . . I go to update my apps in my iPad & iPhone but when I go "Update All" it asks me to sign in with my old Apple ID (that email address no longer exists). Even if I put in the old password associated with that old ID it tel
-
XLR - Incoming Payment - Open Balance field not found
I'm trying to build an aged debtors report in XLR and the last piece I need is the Open Balance (ORCT.OpneBal) on an Incoming Payment that was made on account. I've not been able to find this field in XLR. Does anyone know if its available from insid
-
How do put and image in front of HTTP in the address bar? Thanks
-
Hello skype community I run a small web design company and searching for a skype number in Europe Tell me best location to get number for us 1- We live in India 2- We need number in Europe 3- We need it in location that all Europeans client feel fre