Add field to standard program

Hi experts,
   how can v add a field to the standard program..it is asking access key..
Thx in advance.
Neelima.N

Hi,
What you can do is find an USER-EXIT or a BAdi (business add-ins) for the standard program.
It is not avisable to change standard code as if you go for an upgrade then all the user-defined code will be lost.
But using the above approach the user-defined code will be replaced/lost.
Hope this solves your problem.
Thanks & Regards,
Tarun Gambhir

Similar Messages

  • Need to add field to standard program.

    Hi all
    I need to add a field to standard program whic is from the Ztable.  How do I do it and where should i add the field. 
    Plz help.
    Regrds
    Mona

    My queries is I need to create a ztable and using that ztable field I need to get data. I need to change the output of the standard program that output shud have that field.
    for eg. Company code specific data. this company code field i need to have in program output that means i need to use this ztable in standard program.
    If not clear plz tell me
    mona Please respond to the same thread.
    so everyone could answer for your query.
    if it is a report program copy it as a Zprogram.
    create a ztable in se11 .
    add fields and data entries finish all those work there.
    and in the copied std pgm
    add select-options: s_new_f1 for ztable-f1.
    or u can also use parameters: p_f1 type ztable-f1.
    under : at selection-screen output.
    <perform select query operation for the new ztable.>
    select singe * from table ztable wa_ztable where f1 = p_f1.
    so that the new field willl also come along with the standard output.
    Please check this

  • Add selection screen field in standard program

    Hi Friends,
    I have a requirement to add a language selection screen field in standard programs (RFSUSA00, RFITEMGL, RFIDPL11, RFBELJ10_NACC, RFIDPL06, RAGITT_ALV01 , RFASLD15 , S_PL0_86000028 , RFCASH00 , RFIDPL18).
    This is such that when I select the appropriate language the output should get printed in that paticular language. Can someone help me with how to do this?
    Regards,
    Dikshitha

    Hi Dixitha,
    Use implicit enhancement option.
    Desplay the report in se38.
    In Menu, go to Edit > Enhancement Operations > Show Implicit Enhancement Options.
    The system will show you lines (in color) where you can add your enhancement.
    This function will allow you to add business rules, substitute fields, do extra calculations, and other unique, non-standard requirements.
    Reddy

  • Add fields to Standard Purchase Order

    How can I change the standard order data definition. I need to add some fields that are not in the standard po definition.
    Must i add fields to po_headers_xml.
    But i think I also have to change the .xsd file. But how can I change them ?

    Nike,
    That is indeed the way of working but what I find strange is when you download the Standard Purchase order XSL-FO.
    You see that Oracle uses Boilerplate messages to fill up the labels on there PO
    print.
    These messages are hard coded in the procedure for generating the xml that is
    used for filling up the data of the database.
    For my customer it is useful to change the messages (labels) in the database
    and not in the template. Now why does the standard PO support this. It is build
    up with boilerplate messages ! And why can you not use these way of programming
    for your custom messages. Or will be this supported in the future?
    Maybe it is usefull to build up the part where the messages are selected in the
    PO_COMMUNICATION_PVT.POXMLGEN not hard coded but dynamicly. So you can set up
    which messages are used.Alse the part wich language the xml is generated based
    upon the language of the supplier. So that you can do View > Document in PO
    summary screen with the language of the supplier.
    These are the problems I have, it seems logical to me that the way the standard
    PO is presented, it also can be used in customisations.
    But these customisations are not supported.

  • Hiding Fields in Standard Program :  RFITEMAR ,LDB : DDF

    Hi Experts,
    Am using standard program : RFITEMAR ,as per my requirement i dont need
    to display all the fields in the standard selection screen,i juss want to hide the fields which
    i dont want to dispaly in the selection, as there are some dependencies i dont want keep that code in active state.
    can anyone pls help me/suggest me with my logic/guidance would be helpful and very much appreciated.
    Regards,
    Ashok.

    Hi Marcin,
    Thnaks for your response.
    SHDO Tcode is used for Transcation Varient which is used to hide the fields
    or display additioal fields in sales order.
    According to my requirement i copied the standard program into a custom program
    thats where am tryig to implement changes.am not sure wether that would fulfill my requirement.
    do let me if know any solution /guidance would be helpful and appreciated.
    Regards,
    Ashok.

  • Assign search help for a screen field in standard program?

    Hi All,
    Is there any other way to assign search help to a standard SAP screen field? (to be precise i want to assign search help to Recipient field in table control of components tab in transaction IW32/IW31)
    I know we can do this by assigning search help through screen painter (by changing standard program, which is my last option).
    Any advice/help will be greatly appreciated.

    Hi,
    I think you will find solution in below <b>threads</b>:
    Re: Search Help for standard field
    How to assign a search help
    Search help for Standard SAP field
    <b>Reward if helpful</b>
    Rgds,

  • Add fields to payment program

    Hi Gurus,
    I have a question regarding the rffo* classic payment program. I wanted to add more fields in the file that is going to be generated. However i am not able to find out how to do it like should i extend the reguh and regup tables or i should use a exit where in i call add the new fields. please help required ..
    rgds
    Edited by: SAPgopi on Apr 21, 2011 11:15 PM

    Hi Amir,
    The program documentation for the report RFZALI20 contains technical instructions for enhancing the output options.
    As mentioned in the same, the ABAP dictionary structures REGUH_LST (header information) and REGUP_LST (line item information) contain the output fields provided by program RFZALI20. You can modify these fields to suit your requirements using the CI_INCLUDES CI_REGUH_LST and CI_REGUP_LST.
    Also you can refer to consulting note 895843, which discusses on listing the payment request and the ordered payment amount in report RFZALI20. You can use this note as your guide and take hints from this to achieve your Business requirement.
    Hope this helps.
    Kind Regards
    Soumya

  • Without EEWB Is it Possible to add field to standard tab

    Hi Experts!
    Without EEWB and enhancing Screen Is it Possible to adding field to standard tab. Any body can help out in this.
    URGENT
    Thanks
    vikram.c

    Yes it is possible, but we are talking a modification of SAP standard here. Also the effort needed will be at least 10 times higher than using EEWB as you have to reprogram all generated code / screen helps that SAP provides. Moreover these fields are then still not exchanged with the interfaces / BDocs etc which will be also some more days of work. There is no usable documentation on this - at least not by SAP and I am not aware of another one. It is much easier to create an EEWB enhancement and then move the fields from one tab to another.
    Doing this all by hand is like adding a second processor to an existing motherboard for more performance compared to exchanging the existing one with one of higher specifications.This is possible, but requires a) more work/time/material b) more experience c) you lose warranty d) in the end you do not know for sure what the outcome will be
    Regards, Kai

  • Add field in standard ALV report.

    Hi friends,
    In SAP standard ALV report, t.code- S_ALR_87012050, user wants the vendor to include information about source document - vendor number, vendor name, invoice number, original document number of the transaction in the case of payroll being capitalized.
    I tell me weather this information is already present in the report or I have to create Z report for adding this information and how do I proceed to add new fields in the created Z program.
    Please help me.
    Thanks in advance,
    Saya

    HI Saya,
    Check in the ALV output whether these fields are already there and not displaying in the ALV output, if the fields are not at all printing in the ALV output,then copy the Program to Z program and change it.
    write the Code to add the new fields to the internal table and change the Field catalaog to come your fields in the ALV output then print it
    Regards
    SUdheer

  • Add fields to standard Report for T-code-S_PL0_86000028-Financial Statement

    Hi Sap Gurus,
    The standard trial balance report does not generate the trial balance report with the parked documents, since the parked documents do not update the posted documents tables.
    now i have to add that colum next to the normal items column and display Parked Document data.
    so please suggest me which is the best way to do it.
    1. Either copying the standard to Z prog and do it
    2. Or enhance in any point in the standard Report.
    this report seems to have dynamic programs in it so confused how to start on.
    Tr code is: S_PL0_86000028

    Hi Sagar,
    Adding a New field is a new requirement. Its a new developement and it would be good idea to
    go ahead and develope a Z-program.
    Using Enahancement- there is high possibility of affecting the functionality...
    Regards,
    Kittu

  • How to add field to standard screen of PNP

    hello masters, tell me one thing:
    - it is possible to add a field that isn't part of PNP logical database to the standard screen PNP.
    Could someone help me?
    regards and thanks in advance
    Mário

    Hi Mario,
    I don't know anything about SAP HCM, but: If you work with SE80, you can see the logical database in the object tree. Right-mouse-click to copy the logical database to custom name. Modify as you need. Use.
    Regards,
    Clemens
    P.S.: Before I tried I was always afraid of logical databases.Copying is a lot easier than expected.

  • Want to add field in standard table control - me21n , me22n , me23n

    Dear All ,
    I have come across a situation where I want to add a field in a standard table control .
    But how to proceed for tht I am not getting .
    In the standad transation me22n in the ITEM  OVERVIEW table control I want to add Curreny field in the table control structure
    i.e MEPO1211 I have append the field in MEPO1211_DATA it is even visible in run time in the structure but not visible in table control and in table control settings also.
    How can I add one more column or some standard procedure to do that. Please suggest .
    Thanks & Regards
    Aryan

    hi,
    If you don't want to access key...then only option is ,you have to search USER Exit or BADi (Try using BADI ME_GUI_PO_CUST) for me22n transaction......to adding the field.
    Regards
    Gaurav

  • BDT add fields to standard SAP tabel on BP screen

    With this email I would like to report a problem I have with the BDT to show extra fields on a table control in the businesspartner masterdata. I hope you can help me and tell me what I am doing wrong or why I cannot show these new fields.
    The SAP Module is FS-CS (Commissions). On the businesspartner there is a tab screen with contractdetails. We want to add two new Z-fields to the table control and we have added these fields to an append structure in the CACS_CTRTBU table. I have put the extra fields to a new fieldgroup and put the fieldgroups on a new view added the view on a new section, defined a new screen and finally added the screen to a new screen sequence. The original screen has now been replaced with the new screen with the extra fields.
    In the screenpainter I defined a new screen for the new view by copying the original function group of the original screen together with all functionmodules. I added the new fields of the newly defined fieldgroup to this screen.
    I registered the new functionmodules for the events ISSTA, ISDAT and ISDST in customizing for the new defined application.
    Within the programme there is a structure used called CACS_S_BUPA1. I have added the 2 new field also to this structure.
    If I look in my sourcecode in the PBO then I see that the internal table has stored the values of the new fields together with the values of the original fields.
    Still if the screen comes up, the values for the new field are not shown and the old(orignal fields) are shown. The new headers and colomns in the table control for the new fields are visible.
    Do you have any idea what the problem might be ?
    Kind regards,
    Peter Jonker

    Thanks for your reply, the tip of the fieldgroup has helped me and my colleague who also had a BDT problem, his problem was that changes on fieldgroup level were not saved. Once he changed to the range 6xx with his fieldgroup the problem was solved.
    My problem has been solved too, although I am not sure if it had anything to do with changing the range of the fieldgroups, it probably did.
    I had done the whole designing from scratch again, but this time using fieldgroups in the range 6xx. Now it works fine.
    Strange thing is that in the SAP Help it says to use fieldgroups in the range 600- 799, while the 7xx range will give you problems. The 900 range, as you suggested, also gave problems. In our case the 6xx range was the right one to use

  • 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.

  • CEWB - add Columns to standard Table control using enhancement

    hi,
    there is a table control in CEWB where i want to add a field from table STPO. Is this possible to add fields to standard tble control. If yes, what is the method? Enhncement or i read somewhere GUIXT. Whats that?
    Any help will be really appreciated.
    I hv got some list of BADIs, but none of them re triggering in the "Component assignment" screen:
    EWB_SELECTION
    CEWB_TSK_MENU_INTERN
    CEWB_TSK_MENU_EXTERN
    CEWB_OPR_MENU_INTERN
    CEWB_OPR_MENU_EXTERN
    CEWB_COM_MENU_INTERN
    CEWB_COM_MENU_EXTERN
    CEWB_CHA_MENU_INTERN
    CEWB_CHA_MENU_EXTERN
    CEWB_MST_MENU_INTERN
    CEWB_MST_MENU_EXTERN
    CEWB_GEN_MENU_INTERN
    CEWB_TSK_UPDATE
    CEWB_TSK_SCREENS
    ags.
    Edited by: ags on Jan 20, 2012 7:11 PM

    hi,
    I am able to do this using SAP GUIXT scripts. But since I am new to this Script would like to get some advice on it like is it best practice to use this technique in such situations? Also how do i make this change universl, like how should i deliver this develoipment to the customer nd other users? what kind of settings need to be done.
    Any hint will be really helpul.
    Thanks in advance.
    Ags.

Maybe you are looking for