Error on Screen Exit

Good day experts,
I would like to seek your help after I exhausted all possible solutions I knew in my mind and some research I did on net.
I am working right now in tcode, WB21, WB22, WB23 --Trading Contract...
My requirement is.
a. Add 5 additional fields/columns in tables WBGT/ WBHK/ WBHI (SAP standard trans table) and;
b. Add subscreens on the header and on the items. On the header screen, add 5 input fields. While on the item screen, add 20 input fields.
c. In this input fields, once the user saves it, it will be saved on the fields/columns added on the table, WBGT/ WBHK/ WBHI.
With this, I have found an enhancement which corresponds to my requirement. The enhancement is LWB2B001. This has three (3) FM exits and two (2) Screen Exits. I have successfully added the screens for the header and for the item. Now, I successfully added also the input fields in each subscreen, on the header and on the items. On the header, I can navigate from one tab to another.
My problem is on the item screen. Once I click it for the first time, it is ok. But when I click the other tab, an error now occurs.
The error message differs when I used different data samples. Here are the error messages
1. Entry 002 does not exist in TB2BK (check entry).
2. Item type for item 00001/material 8347841 could not be determined.
I hope I will hear some advises/solution to solve my problem. Thank you very much in advace.
Edited by: levis 501 on Jun 24, 2010 3:04 PM
Edited by: levis 501 on Jun 24, 2010 3:05 PM

Hi Toni,
First, append structures to this standard tables WBGT/ WBHK/ WBHI. The structures must corresponds to your screenfields. Use SE11 to append structures to this standard tables.
Second, after appending the structures, use the necessary exits. As far as I recall, we used a userexit I mentioned above. Also I implemented BADI WB2_ADDITIONAL_DATA to pass values from standard transactions like WB22.
I think these are the only thing that we did to implement such. Sorry but I can't give you the full detail now as I did this project almost three years now.
Regards,
Levi

Similar Messages

Runtime error in MIRO while using User/Screen exit

Hello,
I have implemented an exit in ABAP for MIRO which when transported to Quality server through runtime error.
I have used EXIT (SMOD) : LFDCB001 which contains FM -> EXIT_SAPLFDCB_001 and include -> ZXM08U31. In this exit I have written my code to disable Inv. Party field. This field exist in Details Tab in Miro Transaction.
Location of the field: MIRO -> Details (tab) -> Inv. Party (Field)
Code written in include ZXM08U31 is:
LOOP AT SCREEN.
IF screen-name = 'INVFO-LIFRE'.
    screen-input = 0.
    MODIFY SCREEN.
ENDIF.
ENDLOOP.
This exit is assigned to a project in CMOD and I tested the same in Development system. It is working perfectly.
Now I transported the TR (Includes program ZXM08U31 and Customer enhancement projects ZMIRO). Now when I run MIRO in quality server it triggers the my logic and then through runtime error.
Runtime error says:
Short text
    Dynpro does not exist
Error analysis
    The system attempted to use dynpro 0400 in program "SAPLXM08".
    This dynpro does not exist.
I agree that screen 400 does not exists in program for MIRO but it does not exists in development system as well. So if the runtime error is valid in QEC server then why not in DEV server. And when it can run successfully in DEV server why cant it run in QEC server.
Hope I have explained all the things in detail.
Please provide me the solution since user can bombard anytime for the MIRO dump everytime in QEC.
Regards,
Harjeet Grover

Hi Harjeet,
Reason of your Dump is that the enhancement "LFDCB001" which you used contains one Function module exit "EXIT_SAPLFDCB_001" and another one screen exit in calling screen "SAPLFDCB" number 0150.
So when you activate your project these above mentioned both components were activated.
So when you execute transaction SAP looks for called screen "SAPLXM08" No-0400 but as you havn't created and program go for DUMP.
Solution - Just Create called screen "SAPLXM08" No-0400 and activate.
Thanks,
Vijay

Problem in transporting MIGO BADI screen exit?

Hi all,
I have implemented MB_MIGO_BADI for screen-exit of the MIGO.
Whem transporting I am getting an error that
Table ZMIGO_BADI_EX_SCREEN_FIELD could not be activated
(E- Routine EXPAND (Table ZMIGO_BADI_EX_SCREEN_FIELD could not be expanded) )
Table Type ZTY_T_EXTDATA could not be activated
(E- Row type ZMIGO_BADI_EX_SCREEN_FIELD is not active or does not exist ) .
But this row type is in the same request number and activated also ?
I am unable to identify the reason. Please help me to solve this problem?
Thanks,
Vamshi

Hi,
Go to se80 and display the program name which you might have given in methof IF_EX_MB_MIGO_BADI~PBO_DETAIL and activate the screen which you have created,
Thanks,
Shailaja Ainala.

Problem with Screen EXITS.

Hi,
I need to to some enhancements to my std screen for T.code IE03.
I found screen exits and Function exits for that .
I create the subscreen in screen exit and linking to the functional exit,
Whem i am activiting it raises the error
"Incorrect nesting Before the Statement module structure introduced by function must be conclude by endfunction."
Can any one suggest the solution for this problem.
Points will be awarded.
regards,
Jayasimha

The Problem can be due to incorrect closing of syntex.. either in function module or in PBO or PAI module. i.e you might have started by saying function but endfunction is missing or same goes for PBO / PAI module do check it and let us know
No Rewards Pz..

Problem activating a project with screen-exit

Hi!
Could somebody guide me to activate a project that has the enhancement MM06E005, with many screen-exits?
In this enhancement, has many screen exits and I only implemented the 0101 screen (it's appears in me23n).
When I activated the project, the CMOD activated all the screen-exits and put a flag means that all screen exits is implemented, and I only implemented the 0101 screen.
And the problem is, I send the request with this activated project to production and the transaction ME41 generated a dump cause the screen 0301 not is created (this 0301 screen is in MM06E005 and I'm not use, I'm not implemented, but the CMOD activated).
I was clear with my problem?
Thanks in advanced!!!

Hi,
That is because it checks whether that exit has been implemented or not.
In case it finds no screen it doesn't go and look for it.
My concern is that in Dev if you go and check against that screen which is giving error it should say something like 'there is no screen existing ' or something to that effect but if by mistake when you click it shows a screen then there is an issue.
Also, for the solution, what you can do is deactivate this enhancement project in production and then in Dev also deactivate it. Delete this project and assign it to a new project and then sent it to Production.
I am sure this will solve your issue.
I have also checked in my system and when you activate an enhancement project it put's a 'tick' mark against each screen exit meaning it's implemented even for those which have not been created and we are not experiencing any issue currently in this regard
Hope this helps
Regards
Nishant

Screen Exit / Badi for VF01 in ECC 5.0 Version

Dear experts,
I want to add some customized field(Bill of lading date) to the screen of billing header and the field should be displayed in the screens of t-code VF01 and VF02 always.
I found that the BAdi: BADI_SD_CUST_HEAD
But When I try to create implementation for the Badi. The following error is coming Badi definition BADI_SD_CUST_HEAD is only provided for SAP internal use. Our client using sap ecc 5.0 version.
Is there any screen exit or how to add a popup on the billing screen in user exit rv60afzc . Adding popup enter bill of lading date Causes any problems?
Pleaes give me ur help ASAP. Thanks a lot!

Added zfiled in vbrk table.and user exit Called popup.

Pros and Cons of Customer Specific Screens with Screen Exit????????????????

Hi Experts,
                I am using Screen Exits for Notification.
                I want to know what are the Disadvantages of using screen exits for notification.
                Earlier we had Runtime error because of the Screen Exits used anyway we had rectified the problem. Anyway before going for next Screen Exits please tell me if any problems I would likely to face because of screen exits.
               Thanks in advance.
NArendra

Narendra,
If they are programmed correctly, then you shouldn't have any problems.
However, you may need to create some new ABAP reports.
PeteA

Menu-exits, Function-exits & Screen-exits

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

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

Custom Field using screen exits CS01/CS02/CS03

Dear Experts,
I am using Screen exits to add some text description in CS01/CS02/CS03, my requirement is to add a field 'Product Appearance' with multiple lines for the material description. For this I have created customer field 'ZTEXT1' and appended it to STKO table. Now in screen painter(SE51) i need to add 3-4 lines of type stko-ztext1 because the product desc is of size 300-400 character.
I am not able to create 3-4 lines of type stko-ztext1. Can u plz suggest how can i add 3-4 lines of type stko-ztext1 in SE51.
I am able to create a blank field in SE51 using Edit->Grouping->Step Loop->Define, but while activating it is giving error as "Input/Outpt field STKO-ZTEXT1 and key word are not in the same screen".
Plz suggest.
Regards

Hi Kurtt,
Below are the available user exits :-
PCSD0001 Applications development R/3 BOMS
PCSD0002 BOMs: Customer fields in item
PCSD0003 BOMs: Customer fields in header
PCSD0004 BOM comparison
PCSD0005 BOMs: component check for material items
PCSD0006 Mass changes user exit
PCSD0007 Check changes in STKO
PCSD0008 WBS BOM: Customer-specific explosion for creating
PCSD0009 Order/WBS BOM, determine URL page
PCSD0010 Order/WBS BOM, determine explosion date
PCSD0011 Knowledge-based order BOM, parallel update
PCSD0012 Customer - Mat. number/mat. number during material exchange
PCSD0013 Customer-specific processing of an explosion for BOM browser
PCSD0014 Knowledge-based order BOM: Status
Check which one suits your requirement.
Regards
Abhii

Problem in Screen Exit for me21

Hi,
I have developed Screen Exit in ME21N ..and facing a problem where to write the code...I have a little bit confused with all the function exits...
i used move-corresponding...in the function exit but i am getting errors ..if i am trying to activate the code it is activating...
could you plz help me out guys ..
points will be rewarded..
Regards,
Ravi Ganji

hi,
if u want to add new fields in the transaction, this is sample code for CNEX0006 enhancement.
First create a project in cmod and attach the enhancement CNEX0006 to the project.
1.go to se11 and in the PROJ table u will find ci_proj include , in this add ur custom fields.
2.go to se51 give SAPLXCN1 in the program name with screen number 0600 , create the subscreen and in the layout choose Dict./Program fields and drag and drop in the screen .
3. if u want to write any logic before the screen is displayed do it in PBO.
4. now in the function exit EXIT_SAPLCJWB_002 , go in the INCLUDE ZXCN1U11 and write this logic
move-corresponding sap_proj_imp to proj.
5.4. now in the function exit EXIT_SAPLCJWB_003 , go in the INCLUDE ZXCN1U12. and write this logic
move-corresponding proj to cnci_proj_exp.
Activate the project .
Hope this helps
Regards
Syed

Problem while transporting Screen exit object from DEV to QAS client

Hello All,
I have developed screen exit for tcode 'ME51N' to add customer field in newly added TAB. To grayout that field in display mode, I have added code on the PBO event of that screen. Code for PBO even has been written inside the include. Exit is working fine on development client.
After transporting the exit on QAS client the field graying out functionality in diplay mode is not working eventhough the include which contains the code for PBO even is exist on QAS. Also in flow logic if i double clock on the PBO module event, it says object does not exist, eventhough the include which contains the PBO event code exist in QAS.
Please, help me to understand why the linkage between flow logic PBO event and the include where the PBO code has been written is not getting transported from DEV to QAS.

Hi,
First check the TR log if there is any errors. If no errors, then check if all the objects were properly transported or not.
You might have missed out in transporting the enhancement activation(CMOD).
Try to Rebuild the object list for updating the navigation index. You can do this from SE80=>Rightclick on function group=>More functions=>Rebuild object list.
Thanks,
Vinod.

Field/Screen Exit for MIRO

Hi Friends,
The client requirement is to fix an Exit to disable or inactive the field INVFO-LIFRE or to put the INVFO-LIFRE field (invoice party in Details tab) as display mode where the user not able to change it while posting invouces in MIRO.
I've tried by program screen enhancement in 'SAPLFDCB' but i couldn't able to fix it since the screen name of INVFO-LIFRE is not showing/coming while posting MIRO (checked in debugging mode).
Instead of fixing error message through BADI/USER EXIT, is there any way to make field/screen exit to disable or inactive the filed??
Please advise.
Thanks & regards
Sankar.

Hi,
Check the below link.
[Screen exit for MIRO transaction;
[Re: steps to create field exit;
Regards
Sunil

To add screen exits to a existing transaction ( Purchase order) - ME33k

Hi,
Can anyone tell me whether how to add screen exits to a particular transaction
Transaction - ME33k.
I need to add a screen to the existing transaction, so how do i do that
can any one suggest me the way
i know the BADI which can be used for the same
ME_PROCESS_PO
ME_PROCESS_PO_CUST
GOS_SRV_SELECT
but can anyone suggest me a better so as to how to implement them !
thanks,

Hi
Screen exits are exits that allow you to use a reserved part of the screen (A subscreen) to display or input data. It is determined be SAP where the sub screen will be displayed. The syntax is: CALL CUSTOMER-SUBSCREEN The screen exit is not processed untill the corresponding subscreen has been created in an enhancement project, and the project has been activated. Note: Function codes are only processed in the main screens flow logic You are not allowed to enter a name for the subscreens command field You are not allowed to define GUI stauses You are not allowed to enter a value for Next screen The global data of the program is not available for the subscreen. Data for the subscreen is provided by function modules. These function modules belongs to the same function group as the subscreen Subscreens are edited with transaction CMOD. When you activate a project containg subscreens, the calling screen is regenerated and the subscreen is displayed next time you display the calling screen The developer must create the subscreen and the corresponding PBO and PAI modules How to identify screen exits Look after CALL CUSTOMER-SUBSCREEN in the screenprogram of the screen you want to modify. Use transaction CMOD menu Utillities -> SAP enhancements to search for screen exits MENU EXITS Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu entries in the GUI interface. The developer can add his/her own text and logic for the menu. Function codes for menu exits all start with "+" Example We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will run report ZTEST. Goto transaction SE43 Area Menu Maintenance In Area Menu Paramenter type 'S000' (S triple Zero) Select Change and ignore all the warning screens Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function" Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01 Goto transaction SE93 and create transaction +C01 that calls report ZTEST. Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear. 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_<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 2. How to find user exits Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter. You will now come to a screen that shows the function module exits for the exit. 3. Using Project management of SAP Enhancements We want to create a project to enahance trasnaction VA01 Go to transaction CMOD Create a project called ZVA01 Choose the Enhancement assign radio button and press the Change button In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only be used i 1 project. If the enhancement is allready in use, and error message will be displayed Press Save Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit. Now the function module is displayed. Double click on include ZXVVAU04 in the function module Insert the following code into the include: E_KUNNR = '2155'. Activate the include program. Go back to CMOD and activate the project. Goto transaction VA01 and craete a salesorder. Note that Sold-to-party now automatically is "2155" Please check if the thread given below would be of any help. http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696# http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

Screen exit for VL31N

Hi All,
I have a requirement to add a few custom fields in the standard transaction screen VL31N.Is there any screen exit i can make use of? How do i proceed once i get the Screen exit to add the fields in the screen.
Thanks in advance.
Karthik

HI,
There is no screen exit available for VL31N. the available user exists for this Tcode are :
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of Stock for POs for Shipping Due Date List
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)
Thanks,
Varna

Screen exit example step by step

screen exit example step by step need.

hI
REWARD IF USEFULL
User Exits in FI/CO
by Tami Becker, SAP Platinum Consultant, SAP America, Inc.
Overview
R/3 provides three "customization spots" that allow you to enhance FI/CO features without modifying the standard code. Although often collectively referred to as "user exits," two of the three have different names. SAP Enhancements are used to expand the standard functionality within SAP. Enhancements use function modules and are called from the standard SAP code. Each module in the system has a set of delivered enhancements that help companies expand the standard functionality where they need it. Enhancements were new in release 3.0.
The Open FI Interfaces or Business Transaction Events are also used to expand the standard functionality within SAP. These events are defined in the IMG. Business Transaction Events were new in release 4.0. They are not available for all modules and are not called on all integrated transactions into FI as of release 4.5B. This will change with each release and should be retested.
The older User Exits in FI/CO are "Z" programs that are defined in table T80D for client-dependent user exits, and in table T80I for client-independent user exits. These are also used to expand the standard functionality within the FI/CO modules. These User Exits have been available since the early releases of SAP. All of these FI/CO User Exits are listed in this document in the Configuring User Exits (Older). The list is included because these User Exits are not a part of the Enhancements or Business Transaction Events and do not have an Info System for searching.
Benefits
     Standard SAP functionality can be enhanced without modification to the standard code.
     Upgrades do not erase the functionality and it does not have to be re-transported or re-entered into the system. The enhancements should be thoroughly tested when upgrading to ensure the system will still work as implemented.
Configuring SAP Enhancements
Basic Steps in Configuring an Enhancement
     Find the appropriate Enhancement.
     Enter the ABAP code in the "Z" program within the function module.
     Create a project.
     Add the Enhancement to the project.
     Activate the project.
Example Business Scenario for Enhancements
Company A has a requirement to validate all customer master records created with a U.S. address. The U.S. entity reports on the industry field on the customer master. This is only a U.S. requirement and should not be required for the other countries, so the field status would not work. To accomplish this requirement, Company A will need to set up an Enhancement for the customer master transaction. The necessary steps are detailed below with screenprints. This example was configured in a 4.6C system.
Detailed Steps
1.     Tools   ABAP Workbench   Utilities   Enhancements   Definition   Utilities   List Enhancements
2.     Do not execute this without any parameters! There are too many Enhancements and it will probably time out. Youre searching for a customer master exit. Enter mast in the short text (see Figure 1). Youll start there. Searching for an exit can be tricky, so make sure you try several things before giving up.
3.     Execute the search.
Figure 1. Start Your Search for a Master Exit Here
4.     Look through the list until you find the Enhancement for User exits: Customer Master Data.
5.     Double-click on the enhancement SAPMF02D. This will take you to the details of the Enhancement and list the function modules included in the Enhancement.
6.     To continue, double-click on the function module EXIT_SAPMF02D_001
7.     This will take you to the source code for the function module. Click on the Import tab to review the tables/fields that are available for the Enhancement (see Figure 2).
Figure 2. The Tables That Are Available for the Enhancement
8.     To view the tables/fields that can be changed in the function module, click on the Export and Changing tabs. For this function module, these tabs are empty because you can only validate data. You cannot change any fields in this enhancement.
9.     Return to the Source Code tab.
10.     Scroll down until you see the Include statement in the program. The "Z" program listed after the Include is where your code will be written (see Figure 3).
Figure 3. Your Program Will Begin After the Include Statement
11.      Double-click on the Include. You will be prompted to create the include. Click on Yes to create.
12.      At this point you will be prompted to enter a development class and to create a transport request. If you do not know which development class to use, please contact your technical team.
13.     Enter the following ABAP code into the program (Figure 4):
User exit to ensure that all US customers have a group key
entered on the customer master.
if i_kna1-land1 = 'US' and
i_kna1-brsch = ' '.
message e001(F2).
endif.
Figure 4. The ABAP Code You Need to Enter
14.      Note that the table name matches the table name in the import tab tables.
15.      In this example you are using the standard message class F2 with message number 001. Normally, you will create your own message within your own message class. All customer message classes must begin with a "Z" and are created in transaction SE91.
16.     Save the program.
17.     The next step is to create the project. Go to transaction code CMOD or follow menu path: Tools   ABAP Workbench   Utilities   Enhancements   Project Management.
18.     Enter the project name; begin the name with a "Z."
19.     Click on the Create button.
Figure 5. Click on Create After You Type in the Project Name
20.      Enter in a description for the project.
21.      Click on the Enhancement Assignments button.
22.      You will be prompted to save the enhancement. Click on Yes.
23.      At this point you will be asked for a development class and to create a transport for the project. You may use the same one created when adding the ABAP code to the function module.
24.     Enter the name of the enhancement SAPMF02D (see Figure 6).
Figure 6. Enter the Name of the Enhancement Here
25.     Save the project.
26.     Back out of the enhancement assignment.
27.     Activate the project by hitting the Activate button.
The SAP Enhancement is ready to be tested! Try creating a customer with U.S. as the country and a blank group key. Be sure to test one with a group key to make sure the message is not displayed in error as well.
Configuring Business Transaction Events
Basic Steps in Configuring an Event
     Make sure the application is active for Business Transaction Events.
     Copy the sample interface function module into a "Z" function module.
     Enter the ABAP code into the source code section of the new "Z" function module. You may choose to create a "Z" program to enter the code into and then insert the "Z" program into your function module source code.
     Activate the function module.
     Assign the function module to the event, country and application.
Example Business Scenario for Business Transaction Events
Company A would like to copy the group key field from the vendor master into the allocation field on all the line items within a vendor invoice and payments, including the vendor lines. This requirement assumes only one vendor is posted to in a document.
To accomplish this requirement, Company A will use the Business Transaction Event 1130, Post Document: SAP Internal Field Substitution.
1.     IMG Menu Path: Financial Accounting   Financial Accounting Global Settings   Use Business Transaction Events   Environment   Infosystem (Processes).
2.     Find the correct Business Event. You are updating a field, so you select the Processes Info System instead of the Publish and Subscribe Info System.
3.     Execute the search with the defaults.
4.     Find the correct interface for updating a document: Post Document: SAP- Internal Field Substitution (see Figure 7).
Figure 7. Find the Correct Interface for the Business Event
5.     Put your cursor on the event and click on the Sample Function Module button.
6.     You are now in transaction SE37 Function Builder. This is the function module (sample_process_00001130) you will need to copy into a "Z" name function module for your coding (see Figure 8).
Figure 8. This Is the Function Module You Need to Copy Your "Z" Name Function Module
7.     Click on the Copy button.
8.     Enter the "Z" function module name in the To Function Module field (see Figure 9).
9.     Enter a Function Group. If you need to create a "Z" function group, go to transaction code SE37 and follow menu path: Go to   Function Groups   Create Group. A function group is a logical grouping of function modules, and the ABAP code is generated for function groups. You will be prompted for a development class and transport when creating the function group.
Figure 9. Enter Your "Z" Function Module Name Here
10.     In Function Builder (transaction SE37), enter the new "Z" function module. Click on the Change button.
11.     The system will default into the source code screen where you may enter your ABAP code.
12.     Notice the tables available for the code. Additional tables may be declared if necessary.
13.     Enter the following source code (see Figure 10):
tables: lfa1.
data: z_groupkey like lfa1-konzs.
z_groupkey = ' '.
loop at t_bseg.
check for vendor lines. If one is found, read the vendor master and
retrieve the group key field.
if t_bseg-koart eq 'K'.
select single konzs from lfa1 into z_groupkey
    where lifnr = t_bseg-lifnr.
endif.
Move the group key field into all line items allocation field.
loop at t_bsegsub.
t_bsegsub-zuonr = z_groupkey.
modify t_bsegsub index sy-tabix.
endloop. "t_bsegsub
endloop. "t_bseg
Figure 10. The Screen Where You Enter Your Source Code
14.     Save the function module.
15.     Back out to the main Function Builder screen by clicking on the green arrow button.
16.     Activate the function module by clicking on the Activate button (see Figure 11).
Figure 11. Activate the Function Module from This Screen
17.     Assign the function module to the event in the IMG: Financial Accounting   Financial Accounting Global Settings   Business Transaction Events   Settings   Process Function Modules   of an SAP Appl.
18.     Hit enter past the warning messages that this is SAP data.
19.     Click on the New Entries button.
20.     Enter the process for your interface. In your example it is 00001130.
21.     Enter the country the interface is valid for. If it is valid for all countries, leave this field blank.
22.     Enter the application the interface should be called for. If it should be called for all applications, leave this field blank. Please note that not all integrated transactions are programmed to go through these interfaces! You will need to test to find out!
23.     Enter the new "Z" function module (see Figure 12).
Figure 12. Enter Your New "Z" Function Module Here
24.     Save the settings. At this point you will be prompted for a CTS number for the configuration change.
25.     The Business Transaction Event is complete! You are ready for testing.
Configuring User Exits (Older)
Basic Steps in Configuring an User Exit
     Create a "Z" program for the User Exits and enter the necessary ABAP code.
     Enter the new program name into table T80D.
     Configure the application to call the User Exit.
List of User Exits
     Variable Field Movements
     Substitutions in FI, CO, PCA
     Validations in FI, CO, PCA
     Rollups in SPL
     Fixed Field Movements in SPL
     Cost Center Summarization on Detail Screen
     Sets Formula Variables
Example Business Scenario for User Exits
Company A would like to add a "Z" field in the Special Purpose Ledger to capture a Business Unit field for reporting. They have used all the standard SAP fields such as Business Area and Profit Center. The field will only be used for reporting and is only needed in the Special Purpose Ledger. You created a special ledger table (ZZSPL1) with field Z_BUNIT and need to populate this field based on a combination of G/L account, fund and functional area.
To accomplish this requirement, Company A will use the Variable Field Movement User Exit. To make maintenance easier, table ZZBUSUNIT was created with the G/L account, fund and functional area fields as key fields, and the business unit field as a non-key field. You generated the table maintenance so the table could be updated using transaction SM30. SAP users update the business unit determination rules in table ZZBUSUNIT by entering the G/L account, fund and functional area, and then the business unit that combination should be posting to. The User Exit will read table ZZBUSUNIT using the G/L account, fund and functional area from the posting transaction and determine the business unit. The steps for using the user exit are detailed below. This example was created on a 4.6C system.
1.     Copy the delivered template User Exit program RGIVU000_TEMPLATE into a "Z" program. Follow menu path Tools   ABAP Workbench   Development   ABAP Editor (transaction code SE38). In early releases, the delivered program was RGIVU000.
2.     You will be prompted for a development class and a transport. Please check with the technical team for the correct development class.
3.     At the initial ABAP Editor screen, enter your new "Z" program name, select the Source Code button and click on Change (see Figure 13).
Figure 13. To Enter Your New Code, Select Source Code and Click on the Change Button
4.     Enter the following code in the User Exit (Figure 14):
FORM E01_MVC USING FROM_FIELD TO_FIELD.
to_field = 'CORP'. "Set a default business unit.
read table zzbusunit to determine the business unit field.
select single z_bunit from zzbusunit into to_field
   where hkont = accit_glx-hkont and
    geber = accit_glx-geber and
    fkber = accit_glx-fkber.
ENDFORM.
Figure 14. Enter Your New Code at This Screen.
5.     Activate the program by clicking on the Activate button.
6.     Change the configuration in the User Exit table to point to your new "Z" program.
7.     Follow the IMG menu path: Financial Accounting   Special Purpose Ledger   Basic Settings   User Exits   Maintain Client Specific User Exits.
8.     The entry to maintain is application area GIMV: Variable Field Movement. Enter your "Z" program (see Figure 15).
Figure 15. Enter Your "Z" Program in the Application Area GIMV: Variable Field Movement
9.     Save the changes.
10.     The final configuration step is to assign the User Exit in the variable field movement for your special ledger table. In the IMG: Financial Accounting  Special Purpose Ledger  Basic Settings  Master Data  Maintain Field Movements. Field movements control how the fields in a special ledger table are populated. They can be populated straight from other fields in a posting or through User Exits.
Figure 16. After You Assign the Business Unit Field and the G/L Account, the Exit Field Should Contain U01.
11.     Assign the business unit field as a receiver and the G/L account as the sender. The Exit field should contain U01 (see Figure 16).
12.     The User Exit number U01 calls User Exit E01_MVC form in the "Z" program.
13.     Save the field movement.
14.     You are ready to test your User Exit!

Error on Screen Exit

Similar Messages

Maybe you are looking for