Add fields on Bonus buy screen

Hello,
We need to add two fields on the bonus buy screen (VBK1, also change and display). Does anyone know if it is possible to add own fields either on the header level or item level?
Best Regards,
Ann-Sofie Svensson

Hi All,
THanks for the input. it was really helpful.
I have added two columns in at the ouptput and used exit EXIT_SAPLV60P_012 for passing the data to these new fields.
Only one query left.....
Addition of two fields on the selection screen of VF24.
I know that we can copy the program and do that.....in that case the logic i tried for above mentioned solved requirement was not required .i would have been done that in Zprogram........but i want it to be on std tcode & screen.
Please suggest.
Thanks
RK

Similar Messages

Add field in Z* tcode screen

Dear All
How to add new field in Z* tcode screen
Regards
Suresh

Dear all
ys01 tcode our development tcode how will add new field in this tcode
Regards
Suresh

Need to add field in the standard screen

Hi
As per my requirementn we have to add one field in the Material master(MM01/MM02). Mentioned path below.
MM01/MM02)--> MRP1 tab --> in the MRP areas > click on MRP AREAS button>Pop will come with MRP AREA --> double cleck on entry > MRP area screen will appear> In general data tab> MRP group field is availble> Beside that i have to add one field.
Program Name--> SAPLMD_MGD1
Screen --> 0030
As it is separate pop kind screen not sure whether we can add or not. Please let me know if there is any chance to add the field with procedure.
Regards
Raj.

hi
For this you have to find the screen EXITS.
GOTO MM01->click on SYSTEM->then STATUS mow click on the program and find our the package name.
NOW GOTO -> se84 ->click on ENHANCEMENT-> give the package name here and EXECUTE you find all the EXITs.
hope this helps
Regards
Ritesh

Add field 'ebeln' in selection-screen of FBL1N transaction

Hi Experts,
Is there a way to display the field 'ebeln' in transaction FBL1N for certain document types and company code only..?
I have already tried this steps below..But the problem is, this changes below is applicable to all document types.
1. Trans. SE36, indicate logical database KDF. <- Logical database for FBL1N transaction
2. Details > Selection views
3. Update the standard SAP view
4. Select table BSIK
5. Include field ebeln.
Regards,
Ekitzv

Dear,
Please kindly note that field BSEG-EBELN is not possible for being shown
with a value in FBL1N (and FBL5N).
Since Release 3.0, several purchase orders can be offset in one invoice.
As a result, different purchasing document numbers (BSEG-EBELN) can be
contained in the different G/L account line items..
As a result, it is no longer possible to enter a unique purchasing
document number in the customer/vendor line item.Field BSEG-EBELN is not
filled in the vendor line item and therefore cannot be displayed in the
line item display for customers/vendors.
You could reference note 152335 to find a more detailed explanation and
possible solution of the issue.
It is only possible to view the purchase order number(EBELN) in FBL3N.
As a workaround, you may branch from vendor line item display to
'Document overview' and you will see the PO number for the respective
accounting document in other G/L account line items.
What You are doing is to insert the field EBELN into the Dynamic selection of the FBL1N but this does not mean to have it available into the FBL1N layout.
I hope the System behaviour is clerer.
Mauri

Use of enhancement to add field in screen

please explain me how to add fields in standard transaction screen by using enhancement 6 in version 6.0 ?

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 u2013 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 u2013 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 u2013 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 u2018SAP Applicationsu2019. 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 u2013 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 u2013 20 characters
Location 2 u2013 15 Characters.
Model no u2013 20 characters
Location 2 should start with u2018Lu2019.
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 u2018CUSTu2019 (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 u2018Lu2019 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 u2018EXIT_SAPLAIST_002u2019, 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 u2018EXIT_SAPLAIST_003u2019, 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 u2013 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 u2018Enhancement Assignmentsu2019 in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to u2018Componentsu2019.
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 u201CLocation 2u201D, 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 u2013 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 u2018Generalu2019 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 u20181000u2019 and click on folder u2018General Assignment of Layoutu2019.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout u2018SAPu2019 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 u2018SAPu2019 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 u2018Tab page titlesu2019.
You want to put your custom fields in the tab page u201CGeneralu201D. 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 u201CGeneralu201D are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with u201CUu201D 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 themu2026save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
I hope you read it all
Thanks and Regards
Santosh K.

Adding field in the selection-screen of a zprogram

hi gurus,
i have to add field in the selection-screen of oppurtunities. in database i have a field salesvalues, some of oppurtunity guids have this field value. first i need to add in selection-screen in this alv report. and fetch the data from ztable into required field . if the input fields of the salesvalues field id filled, then filter the global guids(from global table which had the guid values already) with this guids related to salesvalues. and if one single guid mathes to 2 values of salesvalues then concatenate 2 values with comma and display in single field. if select-options are blank then fetch all opportunity guids which have salesvalues. pls give solution.

Hi Srini,
Thanks for your Reply
I have kept 01 against the field BSEG-AUGDT and selected the preselect check box also.
But still that field is not visible in the dynamic selection screen.
Thanks
Ajay.D

Add Parameters in FBL3N Selection Screen

Hi Experts,
Would it be possible to add parameters in FBL3N selection screen?
We would like to add Purchase Order, Delivery Order and Year/Month.
Thanks in advance!

Hi
BET 1650 will add fields in the Output screen.. it wont help you to add Selection Parameters
I have not come across any standard way of enhancing the FBL reports.. You can copy the program and make a Z of the same... I did it for FBL1N and FBL5N to get the Profit center in the vendor/customer line item
Br, Ajay M

Additional Fields in F-28 Screen

Dear Friends
Our client needs additional fields in F-28 screen to capture some business information like the cheque is from which bank and branch, town, challan number etc..... For this we need to go for Field exits. Can I know
1. Is it possible to add fields for F-28 screen for my requirement.
2. If Yes, how is it going to be done with minimal effort.
Request your help.
Brahma

Hi Brahmam,
Feild exit is put on a particular feild not to create additional feilds for a screen. For eg if you want a validation for assignment feild say you are capturing cheque # and you want it to be ony 6 digits then you can go for feild exit.
If you are using F-26 you can capture all the above feilds mentioned by you by way of IMG configuration. Let me know if you can use F-26 instead of F-28.
Regards
Santosh Hegde

Me21n - account assign - is it possible to add field ?

me21n -> account assign - is it possible to add field ?
is there any standart exit ?
i know about the optin to add fields in my own screen
( MM06E005 ) .
i need it becouse i can't inforce ( display message )
the user to insert value in my own subscreen .

hi
I have the same requirement of adding a new field in account assignment. Please let me know if you are done with that or you have any infor regarding user-exit/BADI.
Thanks
Alok

Add fields in KOB2 & KSB2 report in selection screen as well as output

Dear All,
I have an issue in which i have to add fields in KOB2 & KSB2 report.
i need to add below fields to KSB2 report.
1) Internal order
2) Vendor
3) Purchasing group
I also need to add profit centre in selection screen for KSB2
Similarly for KOB2 i need to add below fields
1) Cost centre
2) Vendor
3) Purchasing group
I also need to add cost centre as input for KOB2 report.
I have gone through note 325546 "CO line item reports: Creating a user-defined field" which can be helpful.
However i am not sure as to how do i add fields in input screen as required.
Other alternative is to create a Z report however when i try and copy the report both KOB2 & KSB2 call same report "RKAEP000".
I am not able to get as to how do i differentiate the call of different screens when ZKOB2 is called or when ZKSB2 is called.
I could identify " c_item_group" field having different values however i couldnot get a proper logic as to how correct screen can be called based on input
Please suggest .
Thanks,
Ronak

Hi Raymond,
The note 747588 is good as soon as you are adding fields from the same table only.
When I have added additional table into KAEP_SCOVP selection view below COVP (just because the extra fields I need are not in COVP) they will show up in KOB1 as selection criteria, but not getting saved.
Any idea if any ABAP should be regenerated or what extra steps are required when adding more tables into Selection View?
Thank you!

How to Add a new fields in the selection screen of LDB.

Hi All,
I want to add a new fields in the selection screen of LDB & then i need to select the data for that fields.
So could you please tell me for that where i need to add the code for selecting the data.
Thanks
Roli

Hi
welcome to SDN forum
If you are designing your own LDB with your own tables you can define tree structure and then the selection screen for the tables
if you wants to modify the std LDB of SAp means take the access key and to modify that code
if you add the extra field you have to modify the where conditions in the code also
see the doc
A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
LDB offers an easy-to-use selection screens. You can modify the pre-generated selection screen to your needs. It offers check functions to check whether user input is complete, correct, and plausible. It offers reasonable data selections. It contains central authorization checks for data base accesses. Enhancements such as improved performance immediately apply to all report programs that use the logical database.
Less coding s required to retrieve data compared to normal internel tables.
Tables used LDB are in hierarchial structure.
Mainly we used LDBs in HR Abap Programming.
Where all tables are highly inter related so LDBs can optimize the performance there.
Check this Document. All abt LDB's
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2flibrary%2fabap%2fabap-code-samples%2fldb+browser.doc
GO THROUGH LINKS -
http://www.sap-basis-abap.com/saptab.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9bfa35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm
/people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases
Re: **LDB**
www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_Logical_Database_FAQ.html
www.sap-img.com/abap/abap-interview-question.htm
www.sap-img.com/abap/quick-note-on-design-of-secondary-database-indexes-and-logical-databases.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db9bb935c111d1829f0000e829fbfe/content.htm
Gothru the blog which provides info on LDB's:
/people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases
Sample code
TABLES: SPFLI,
SFLIGHT,
SBOOK,
SCARR.
START-OF-SELECTION.
GET SPFLI.
WRITE:/ SPFLI: , SPFLI-CARRID, SPFLI-CONNID,
SPFLI-AIRPFROM, SPFLI-AIRPTO.
GET SFLIGHT.
WRITE:/ SFLIGHT: , SFLIGHT-CARRID, SFLIGHT-CONNID, SFLIGHT-FLDATE.
GET SBOOK.
WRITE:/ SBOOK: , SBOOK-CARRID, SBOOK-CONNID,
SBOOK-FLDATE, SBOOK-BOOKID.
GET SFLIGHT LATE.
WRITE:/ GET SFLIGHT LATE: , SFLIGHT-FLDATE.
Regards
anji

How to add fields in custom infotype and update its screens

Hi Experts
I want to enhance a custom infotype ( Add some new fields, and add special function on its screen). This custom infotype is created in previous release. is there any way to add fields in infotype? and let system automatcailly modify corresponding screens to add new fields

Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the u2018Employee Infotypeu2019 radio button.
4) Select the u2018PS Structure Infotypeu2019.
5) Click on Createu2026 A separate table maintenance window appearsu2026
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on u2018Allu2019 push button. It takes a few moments.
10) Click on u2018Technical Characteristicsu2019. Infotype list screen appears
11) Click on u2018Changeu2019(pencil) button
12) Select your Infotype and click on u2018Detailu2019 (magnifying glass) button
13) Give u2018T591Au2019 as subtype table
14) Give u2018T591Su2019 as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on u2018Infotype Characteristicsu2019 u2026 Infotype list screen appears
18) Click on u2018Changeu2019 (pencil) button
19) Click on u2018New Entriesu2019
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotypeu2019s infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirementu2026
25) In the PM01 initial screenu2026Select u2018Screenu2019 radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select u2018Layout Editoru2019 and click u2018Changeu2019.
27) Screen default layout appearsu2026here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Donu2019t forget to u2018Activate at every level
i think u have to select CI_INCLUDE while enhanceing the Standrad Infotype

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

How to add new fields in message creation screen

Hi All,
My requirement is to add another 2 fields in the message creation screen.
Also I found this link is bit useful.
Add custom fields to Support Message
Can anyone share the detailed procedure to add a field in the message screen.
Thanks in Advance.
Regards
Narasingam. B

Hello,
I think of something like:
First, you create extension, with transaction WE30.
Then, reduce your idoc, your extension should also be proposed.
Do not forget to add this extension in outbound we82, and/or we57 in inbound, and WE20, and find BTE or exit to populate extension.
regards.
F.S.

How to Add field to Selection screen of Tx. FBL5N

Hi All,
In Tx. FBL5N, there is a field Customer number (on Customer selection screen).
In addition to the above we need to add field Customer name in Selection screen.
How do we go about it ?
PS :- We have found steps to add fields to FBL5N output. But, we dont want it on output, we want to add it on Selection screen.
Regards,
Ashish

Hi,
Only certain table fields are allowed in dynamic selection, please see this sap note for detail :
Sap Note 310886 - Line items: Dynamic selections ignored
Permitted tables:
SKA1: all fields
SKB1: all fields
BSIS: all fields
So BKPF-CPUDT field is not allowed for dynamic selection.
check this thread Add new Fields to Dynamic Selection FBL5n
Or
Enhancing Selection Views in the dynamic selection of some SAP transactions like FB03, FBL3N, FBL5N
This enhancing related to SAP OSS Note: 188663 and 832997
Requirement: The business requires the Doc. Header Text be added in the dynamic selection in SAP transactions FB03
■Execute Transaction code SE36. Click F4. Enter the SAP table name wherein you think the field could be found. In this case the SAP table is BKPF and the logical database is BRF
■From the initial screen of SE36, Choose from the path EXTRAS >> Selection Views
■Copy Selection View u201CSAPu201D to u201CCUSu201D
■Change the selection views u201CCUSu201D
■In the right corner, double click your table BKPF.
■In the right corner, check whether what functional groups does your field belong. If it is 01 then input it beside your field name.
■Then Save it afterwards.
Prabhudas

Add fields on Bonus buy screen

Similar Messages

Maybe you are looking for