Profit Center - Additional Fields and Screen Exits

Hi,
I would like to add in new fields in Profit Center (KE51). Is it possible for Profit Center creation and if so, how to determine Screen Exit for this transaction.

Dear!
It is possible to add field at the master data screen of Profit Center ( KE51) by using the Customer Enhancement ( CMOD/SMOD-screen exit/field exit).
Please visit the following link
http://www.sapbrain.com/TUTORIALS/TECHNICAL/user_exits_tutorial.html
http://www.erpgenie.com/abap/fieldexits.htm
Please reward me point as way of thanks
null
Message was edited by:
Muhammad Siddique

Similar Messages

Regarding field and screen exits

Hi,
     plz. send me the step-by-step procedure to create Field and Screen exit.

Screen Exits:
Screen exits are provided by SAP to allow the programmer to add his own sub screen in the already available standard SAP screen. The standard screen will have a sub screen area defined especially for this purpose. The call to this sub screen will also be present already in the standard code.
For example, there is an enhancement RVEXAKK1 available for foreign trade transactions.
As you see in the above screen in screen areas block the calling screen, its number, sub screen area and the called screen with its number are defined. Here the main screen 101 in program SAPMV86E is having a sub screen area ZUSATZ and the screen 100 from program SAPLXAKK will be the sub screen for that area.
It is mandatory for the called screen to be in a function group that starts with X. Here the function group is XAKK.
Also, if you see the above enhancement, it also has two FM exits. These two FM exits will be used to pass data to & from the sub screen. These FM calls will be in PBO & PAI modules of the main screen. These FMs are also part of the above said function group.
And the function group will not have that sub screen 100 defined. The programmer can create his own screen with the number 100(or whatever is called).
Calling of the sub screen.
sub screen call     in PBO of main screen 101          this module has the FM exit call
Sub screen call in PAI block of main screen          this module has FM exit call
Create the screen 101 in program SAPLXAKK from transaction CMOD.
Double click here to create the screen
Once screen creation is done, use the two FM exits present in the enhancement to pass data to the sub screen and get data from the sub screen.
Field Exits
1. Field exit was created with CMOD, but is not processed when calling the screen.
   o Since the field exit is not processed until PAI, an action must be
      triggered on the screen (Return, Save, ...).
   o Set profile parameter abap/fieldexit to YES and restart the
      system. Setting the profile can be done by a BASIS person.
o     To check if the parameter is set or not use transaction RZ10.
   o 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.
   o Do not work on different application servers since there may be
      some delay before the field exit is activated.
   o The profile parameter must be set on all or none of the
      application servers.
   o 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).
   o 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.
   o 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.

Field and screen exit..

Hi I am used function moduel user exit many times but I am not sure about the concept of field exit and screen exit.
Can someone elaborate it by giving an example..
Thanks.

Hi Tushar Shah
·        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
Add screen layouts to applications. SAP creates screen exits by placing special subscreen areas on a standard screen and calling a customer subscreen from the standard screens flow logic.
·        Function Module Exits
Add functions to 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 programs. These calls have the following syntax: CALL CUSTOMER-FUNCTION 001.
From Release 4.5A, you can change field texts on screens and add data element documentation using the Modification Assistant.
Just have a look at following Link>:
http://help.sap.com/saphelp_erp2005/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
regards,
Vijay Raheja

Profit center mandatory field in sales order !

Hi All !
How to make profit center mandatory field in sale order can any body let me know...
Thanks & Rgds
Naveen

Hi
You can either Transaction variant SHD0/User exit
Refer below<a href="http://www.sap-img.com/sap-sd/supressing-fields-in-sale-order.htm">Fields in Sale Order</a>
help required: how to makes sales office field mandatory, in inquiry and qu
Re: supress some fiels in sales order? user exit?
Message was edited by:
SHESAGIRI.G

Profit Center Master Data - Validation - User Exit

Hi,
I need to add few validation to the profit center master data. If there is any user exit that I can use or is there any validation like OB28 (we have for financial accounting document) that can be used.
Please help me out.
Regards,
Binay Agarwal

We are on version 4.6C. Requirement is that while creating profit center, two fields, Budget Holder and CC Board Member field should be updated via some valid user id that exist in SAP.
This user id would be used in work flow. This fields are free field and would accept anydata. But subsequent processes would be hindered. Same thing has been implemented for Cost center and we were able to get hold of user exit but I am struggling to find the same for profit center.
As far as I am aware there might not be any user exit for KE51 tcode. Now only point is is there any other way (like validation) which can be setup before the data us saved so that we have control over the data being saved in these two fields.
Regards,
Binay Agarwal

Menu Exits and Screen Exits

hi everyone,
can you send me some examples on menu exits and screen exits.
thank you.
preetham

Hi Preetham,
In older versions MENU Exits approached through Transaction CMOD by creating
PROJECTS and activating the project and assigning Program to that
Transaction Codes. For MENU Exits, Transaction Codes will be starting with
"+" sign and with default text "NODE TEXT NOT FOUND" for which you can
assign your Report or Dialog Program etc., (for Eg:- +DW4 MENU Exits
Transaction available in TOOLS --> ABAP Workbench --> Utilities --> <Node
Text Not found>).
Procedure for Creating MENU Exits.
1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
Line.
2) In Area Menu Paramenter type 'S000' (S triple Zero)
3) Then Press Change Icon in Application Tool Bar. Then It may ask for
Access Key [or] it may display "Specify Processing mode" window. If it ask
for the Access Key Check for the availability of OSS Note and apply to open
Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
Processing mode" window with Three Push Button. In which select "Change" and
proceed further.
4) Then it will display "Information" window with the following information
"Caution : The Original Language of the structure is German (editing lang. :
English) ". Then press "Enter Key to proceed further.
5) Then you will get into "Edit Area Menu S000".
6) for eg:- Expand Tools Menu.
7) Then Press ABAP Workbench <Icon>.
8) Then you will get into ABAP Workbench Menu Tree.
9) Then Expand Utilities Menu.
10) In the last line you will find one MENU EXIT Provision to include your
own menu. "Node Text Not Found" This text can be change by double Clicking
that. There you can find the T.Code. Here for Eg:- "+DW4".
11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
the T.Code "+DW4".
12) Then Save with Change Request Number and come out of Transaction SE43.
13) Then Goto Transaction SE93.
14) Then type T.Code "+DW4" and press Create.
15) Then proceed further to create transaction called "+DW4".
I hope this could help you in Creating Menu Exit...
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
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.
the tcode is cmod...
1.From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
2.Choose Edit component.
3.Choose the screen exit and double click on it
4.Create your subscreen using the Screen Painter.
5.Design your screen to be added to the standard screen and activate the particular screen and return back to the flow logic .
6.Choose the PAI and PBO to write down the logic.
7.Generate your screen and choose Back (the green arrow) to return to the Project management transaction.
8.Go to the transaction ME22 to view the customer defined screen exit.
9.Enter the purchase order number and press Enter.
10.Go to the menu header --> Details.
11.Purchase number is visible on the standard screen
check the foll link,
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
also refer
MEnu Exit
http://www.sap-img.com/abap/what-is-user-exits.htm
Creating menu exits
http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm
For screen exits.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
chech these links for user exists its usefull
http://www.allsaplinks.com/user_exit.html
Re: Screen exit
user exit and customer exit
http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapab013.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
MENU
refer
MEnu Exit
just refer to the link below for step by step procedure with screen shots
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
Check this link:
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen

How to add profit center in fbl5n selection screen

how to add profit center in fbl5n selection screen
and
it is save to copy ddf from sap to cus
wll it affect anything else

When you are on selection screen of FBL5N, press (Shift + F4) DYNAMIC SELECTIONS, there you will see a Dynamic selection screen along with your normal FBL5N selection screen, you will find Profit Centre ther, if you don't find Profit Centre in Dynamic Selection Screen you can add the same from the list on the left, search for profit centre, place your cursor on Profit centre and press the Arrow Button(Copy Selected) on top of the list. Now you will find Prfit Centre in Dynamic selection screen, fill the field with values and press save, that's it.....
Reward points if useful, get back in case of query...
Cheers!!!

How can i add field to screen exit ?

ver 4.7
trans. me21n
add field in screen exit .
i implement screen exit MM06E005->SAPMM06E->0111
in the layout i try to add field by pressing
button in the toolbar ( dictionary field window ) ,
but when i press "save" in me21n ,
i get message "No data changed".
i choose in the dialog window
field from structure "ci_ekpodb" , field that i already
been add .
thanks .

Hi
You have to implement the exit to import/export the data into/from screen-exit:
EXIT_SAPMM06E_016 and EXIT_SAPMM06E_018
Max

Profit center group field in profit center

When i create a profit center in ke51 system asking profit center group filed is required. but i donot required filed i need optional field where can i put that.

Hi
Is there a specific reason why you do not want to enter the Profit Center group field? Is it because you do not know them as of now and you want to update later?
The basic rule is the profit centers need to be assigned to a hierarchy.
Karthik
Edited by: Karthik Coneru on Mar 17, 2009 6:16 PM

User Exit and screen Exit

hi everyone,
For custom field creation and linking the existing system fields with my custom fields i like to know about User Exit and screen Exit. Kindly give me the suggestion.
Thanks & Regards
R.Vijai

hi,
this will help you find screen exit for a tcode.
[https://forums.sdn.sap.com/click.jspa?searchID=19171273&messageID=6151259]

Difference between profit center in OKB9 and material master

Hello,
I have a small doubt over here in the profit center point of view.
We have created profit center 1200 and assigned the same in material master. Now while doing PO system threws error message like "Account 5005115 requires an assignment to a CO object Message no. KI235". To eliminate this error i have assigned Cost element(1001125) and Profit center(1200) in TC: OKB9, now system is able to post everything fine.
Here the issue " If i can change profit center in the material master say ex: 1201, system picks from the material master only then why assigned in the OKB9? while doing MIRO system updated in the 1201 profit center".
Could anybody update me why we need to assigned profit center in OKB9 and Material Master?
Thanks
anifi

Hi,
This is about co.code level field status and Transaction level field status. In OKB9 transaction profit center is maintained and it is getting picked up.
As per SAP if any transaction level field status is maintained it will overwrite the co.code level field status.
So, here when you are giving the input of Profit center in the material master itself it is overwritting the co. code level field of profit center. If nothing is given in material master, then by default OKB9 level profit center will be picked up.
Thanks,
Prithwiraj.

Plant and Profit center wise Turnover and gross profit for the Month for s

Hi
We need a report Plant and Profit center wise Turnover and
gross profit for the Month for selected month and GL's
We are using new GL. but our bi system old version.
SAP_BW -- 7 Patch:SAPKW70015
BI_CONT - 703 Patch:SAPKIBIIP7
Do you have any idea or experiences which data source and data target required to full fill this requirement?
Thanks
Ramana P

Hi
You need to check if you really the report Plant wise and if yes, then check if the Accounting Transactions are maintained at Plant Level in your source system i.e. in R3.
Ideally it should be Business area or Functional Area or Controlling area which are maintained in Accounting Transactions. You will also the relevant details for these Characterisitics + Profit Center in the NEW GL Accounting data sources.
Cheers
Umesh

Profit center mandatory field in F-58 and F-48

Hello Experts,
We need to make profit center is mandatory field in the F-58, F-53 and F-48 while posting payment to vendor.
Kindly let us know is there any possibility to make required entry for the same.
Thanks in advance!
Regards,
Ratnam.

Hello Ajay,
Thanks for the replay, I used field Bank accounts field status group only for making profit center mandatory. Problem got solved now.
For Reference key mandatory field, I written validation for Required TCodes but Reference key field is not available in the FBCJ kept pending. The same problem is there in MIRO screen also, we are doing enhancement for fetching Ref1, 2, 3 fields the MIRO screen.
Regards,
Ratnam

SRM PO profit center addition

Hi All;
We have extended classic scenario in our project. So approved & complete shopping carts are automatically converted into PO. Now the client is asking to add profit center for certain type of indirect expenses as they have to be assigned to a profit center. So the question is:-
1) Can we add a field for profit center in shopping cart creation? If yes; how?
2) Can we link the requirement for updation of profit center to any element in shopping cart? If yes; is it a configuration or a BADI?
3) Do we need any configuration on ECC side for this? i.e. while replicating SRM PO to ECC?

Hello,
Regarding your question 1), in template SAPLBBP_PDH_ACC_1000_1 (BBPACCOUNT Internet Service), you can find some comments, like:


          TD(TC_1000-column[j].title);
     end;
and

<! --   `TD()`
`if (T_SCREEN_ACCLIST-PROFIT_CTR[j].disabled)`
            `T_SCREEN_ACCLIST-PROFIT_CTR[j].value`
          `else`
            <input type=text
name="`T_SCREEN_ACCLIST-PROFIT_CTR[j].name`"
value="`T_SCREEN_ACCLIST-PROFIT_CTR[j].value`" maxlength="10" size="10">
          `end` -->
So, if you uncomment this screen control, the profit center will appear in shopping cart screen. This field is displayed beside the "Business area" field.
Regards,
Ricardo

Disabling Profit center in VA01 and VA02

Hi geeks,
I have a requirement where i need to disable the profit center column for some specific sales document types in VA01 and VA02.
Please guide me with the User-exit to complete the requirement.
-Jiyaaaa

Hi Prabhu,
i want to gray out completely without being able to input.
the following is the code i hav written in exit "userexit_field_modification" of the include "MV45AFZZ"
enhancement 1 zprofitcenter_enhancement.    "inactive version
case screen-name.
      when '*VBAP-PRCTR'.
        if sy-tcode = 'VA01' or sy-tcode = 'VA02'.
          screen-input = 0.
          modify screen.
        endif.
    endcase.
*IF ( SCREEN-NAME = 'VBAP-PRCTR' ).
*SCREEN-INPUT = 0.
*ENDIF.
endenhancement.
In debugging,i have checked it is calling this enhancement.but in the output,it is not greying out.
kindly,let me know where iam going wrong.
-jiyaaa

Profit Center - Additional Fields and Screen Exits

Similar Messages

Maybe you are looking for