COPA Charcteristic group for assignment screen --KE4G/ FBCJ

Hi,
We have Account based COPA. I have created one Charcteristic group and have assigned this group to Business Transactions  which are RFBU, RFBV,RFIG,RKU2(T code KE4G).  In entry aid,only cost center and profit center is required in Profitability segment being real cost object while posting any revenues. (SD module is not implemented).
In invoice posting (T code FB70) user has to first specify Cost center and has to click on Prof seg tab being real cost object . Here the profit center  gets automatically picked up as it is defined in Cost center master.
Now the problem is , in Tocde FBCJ, (Cash receipts) if I select business transaction type "other Receipts" and use the same GL of revenue which I use in FB70, system is not deriving Profit center automatically even if  I am specifying cost center first and clicking on Prof seg tab
What could be the problem? Do i need to add any other Business transaction in Tcode KE4G or any setting is required in FI.
Request for the help.
regards,
makrand

Hi
I dont know why in FBCJ it should behave differently...
Can you try the below steps and see if PC gets derived from CC in FBCJ
1. Try to post the entry just be entering a CC..
2. System would give an error that real object is required for posting
3. Convert this error into warning in OBA5...
4. Now try to repost the doc right from start in FBCJ
Once the doc gets posted, check if PC is derived or not... Ofcourse, you can do this only in a test client
Regards
Ajay M

Similar Messages

  • How to get the screen groups for the screen field which are on selectionscn

    hiiii Experts,
                   How to know the screen groups for the screen field which are on selection screen.
    Thanks and regards,
    kasyap

         NAME                                             PNPABKRS-LOW
            GROUP1                                             SEL
            GROUP2                                             DBS
            GROUP3                                             LOW
            GROUP4                                             180
    to get this use this:
    AT SELECTION-SCREEN OUTPUT.
      LOOP AT SCREEN.
        if screen-name CS 'ABKRS'.
          BREAK-POINT.
        endif.
      ENDLOOP.

  • Assign COPA Char Group to PR/PO screen

    Hi,
    I want to assign COPA screen to appear during PR/PO creation. I have assigned the business transaction RMBA, RMBE & RMBL in the 'assignment of char group for assg screen' (KE4G). But, still during PR/PO creation, the COPA screen does not appear in it.
    Is there something that I must do before this changes take effect?
    TQ.

    already got the answer.
    need to set the PSG as optional entry in PR/PO config (OME9).

  • Someone has a tutorial for creating screen exit?

    I have a development and I do not know how to create screen exit.
    Case Someone has a tutorial for creating screen exit please help me
    Thank you
    <b><i>Wagner Duarte
    Consultant - SAP ABAP</i></b>

    hI
    Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
    1. Go to the screen>System>Status-->Program (Double
    click this program. It will take you to the program.
    2. Now, Goto-->Object Directory Entry.
    3. Make a note the package name.
    4. Now run the transactions SMOD, press F4 and enter the
    above noted package, press enter.
    5. It will display list of Exits.
    6. Now go back to the initial screen SMOD.
    7. Specify the exit name here and select the radio button
    Components.
    8. It will display four group boxes one for FM, second
    for Fcodes, thrid for Screen areas and last for
    includes.
    9. Goto transaction CMOD, create a new project, and
    click the button "Enhancement assignments" and
    specify your enhancements that you got in SMOD.
    10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
    Have a look at below link It will definately help you to undestand the same.
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    check these links.
    http://help.sap.com/saphelp_46c/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
    http://www.allsaplinks.com/screen_exit.html
    USER EXITS
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
    How to implement screen exit for a SAP standard transaction
    Introduction
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen – where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen – so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool – including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton ‘SAP Applications’. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest – for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number – 20 characters
    Location 2 – 15 Characters.
    Model no – 20 characters
    Location 2 should start with ‘L’.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be ‘CUST’ (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with ‘L’ will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_002’, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_003’, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done – otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to ‘Components’.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field “Location 2”, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything – the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder ‘Tab page titles’.
    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
    Original Source: ittoolbox.com
    Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
    1. Go to the screen>System>Status-->Program (Double
    click this program. It will take you to the program.
    2. Now, Goto-->Object Directory Entry.
    3. Make a note the package name.
    4. Now run the transactions SMOD, press F4 and enter the
    above noted package, press enter.
    5. It will display list of Exits.
    6. Now go back to the initial screen SMOD.
    7. Specify the exit name here and select the radio button
    Components.
    8. It will display four group boxes one for FM, second
    for Fcodes, thrid for Screen areas and last for
    includes.
    9. Goto transaction CMOD, create a new project, and
    click the button "Enhancement assignments" and
    specify your enhancements that you got in SMOD.
    10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
    and you just go through these links also
    Screen exit
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    screen-exits
    Check the following link.
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all

  • How can I assign a period (instead of B) in Keynote for blank screen so I can use a Logitech R800 presenter? An option in next version?

    I have recently bought a Logitech R800 presenter which works very well with Keynote on a MacBook Pro. The start/stop presentation key does not work but that can be easily fixed by assigning F5 to "Start presentation" for Keynote in the keyboard system preferences. The remaining issue is that the blank screen button sends a period (".") which works as a prompt for a blank screen in PowerPoint, but in Keynote it causes the slideshow to end. Keynote uses the letter "B" for blank screen.
    How can I assign a period (instead of B) in Keynote for blank screen? Some sort of work around would be very useful as I often use blank screen in my presentations and much prefer Keynote to PowerPoint.
    Perhaps it will be an option in next version of Keynote?
    Thanks

    As far as I know you can not change these keystrokes without changing the Program files. I am sure it is possible there, but I have no idea where to even start to tell you where to find it.
    Your best bet it to go to the Keynote Menu>Provide Keynote Feedback and let Apple know you would like the option to change them.

  • Adding new field in SC Account Assignment Screen (only for information)

    Hi guys,
    we have a requirement, to <b>show</b> additional fields within the account assignment screen. The contents should only be displayed as information for the user. It is not necessary, respectively not wanted to save this data within SRM or the Backend-System.
    2 questions:
    a) Is it necessary to expand the item-structure of the SC (INCL_EEW_PD_ITEM_CSF_SC) AND to expand the accounting structure (INCL_EEW_PD_ACC_CSF) for this fields?
    b) Is it sufficient, that the INCL_EEW*-structures of the PO-/billing-document etc. are <b>NOT</b> expanded with the additional fields to avoid the saving? In OSS-Note 458591 it is mentioned, that it is necessary to expand the CI-COBL-structure within the Backend-System.
    Thanks in advance with best regards.
    Bernd
    ps. We are using SRM 4.0.

    Hi
    <b>We have done this several times, in our past previous SRM implemenatations.</b>
    a) Yes. You need to expand the item structure at the Shopping cart level to display your Custom fields in the We bapage. As Per OSS Note - 672960, you can see the details. For display purpose, at least these custom fields must be created in the standard include structures [e.g., INCL_EEW_PD_ACC_CSF, etc ].
    b) Yes, no need to expand any other SAP Include structure, incase you don't want the field contents to be saved in backend system (incase of Purchase Order / Purchase Req).
    <u>Please see the follwoing links, which deal with the similar requirements, you have asked for in detail with code and other relevant details -></u>
    Re: Item Field Appearing In Account Assignment Field
    Re: Control Busniess Area Field in Account Assignment..
    Re: Add new account assignment field
    Re: Account assignment category not passed into Target Objects Badi
    Re: Add customer fields in Shopping cart and purchase order
    Re: Hiding CUF fields in SC Basic data
    displaying custom fields on shopping cart
    Custom Fields in Cost Assignment Tab
    How to add the custom field in SRM EBP shopping cart?
    Add customer fields in Shopping cart and purchase order
    Hope this will definitely help. Do let me know, incase you face any issues.
    Regards
    - Atul

  • Automatically assign a BP Grouping for a BP Role

    Hi, everyone!
    I would like to automatically assign an specific Grouping range for a BP when creating it in an specific Role.  Now, the user has to select each them separately and sometimes makes mistakes because he selects a wrong Grouping for the Role he is selecting.
    Can this be done?  I will appreciate a lot your help.
    Thanks in advance.
    Adolfo Garay

    Thank you very much, Javier! I will try to explore this.  By any chance, do you have any example that could help me to do this?
    Anyone else have some examples that can be useful for this case?
    Regards,
    Adolfo

  • Boundary Group for site assignment, shall I add My "Management Point" as a "Site System Server" in "References"

    Hi,
    We have an flat singel site.
    Boundary Group for site assignment, shall I add My "Management Point" as a "Site System Server" in "References"
    /SaiTech

    Yes - if it's also a DP?
    The servers are added as content location servers for this boundary group. Only servers that have a distribution point or state migration point installed on them are available.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Display Assignment Field for Mulitple Account Assignment Screen in MIRO

    Hi Members,
    I'm hoping someone may have the answer to a question concerning the transaction MIRO-posting an invoice.
    The issue occurs in MIRO on the Purchase Order tab. I have a validation rule which requires a value in the assignment field before the document can be posted. When multiple account assignment functionality is used to allocate the charges, there is no assignment field available. How can I configure the assignment field (ZUONR) to be present in this area?
    Your responses are appreciated.
    KF

    Thank you for your response.
    What is call point 2? Would this specify that the substitution rule would only apply to the multiple account assignment screen?
    If that is the case, this might provide one option.
    However, if it applies to the entire MIRO transaction, that will not be possible because we use the text field and the assignment field for other purposes in the transaction.
    Do we have any other options?
    KF

  • Field Status Group for Special G/L Indicators

    Could you define different field status group for special G/L indicators? My problem is I am using two different special G/L indicators but their recon accounts are assigned with the same field status group. I used the same posting keys as well.  But when it comes to general posting, they have different screen numbers.  One SAPMF05A 303 and the other one is SAPMF05A 304.  How did this happen?

    Hi Noel,
    As you have defined Field Status Group for 2 different SPL GL Indicators then it will create 2 different screens only as it wont consider the reconciliation account.
    Regards
    andrew

  • Field Exit for VA11 screen ?

    Hello Abapers,
                         I need ur help to find out the field exit available for VA11 screen.
    How to find the field exit wht is the procedure?
    Thks

    Hi Venkateswar,
    First you check this link once.,
    http://www.****************/Tutorials/ExitsBADIs/MK01/FieldExit.htm
    Field exits are frozen on the 4.6C maintenance level and are not further developed. This means that the existing functionality is kept with all restrictions (see also the last item below). Existing exits can be further used and are called at runtime as usual.
    Existing exits can be maintained using program RSMODPRF (run the program using transaction SE38). Activation of the field exits and assignment of the dynpros can also be carried out using program RSMODPRF. For this purpose, the program must be started without parameters (input fields remain blank).
    If required, new field exits can be created using program
    RSMODPRF (see the program documentation).
    Please find below the step by step procedure for field exit :-
    There are eight steps to creating a field exit:
    Step 1: Determine Data Element
    Step 2: Go To Field Exit Transaction
    Step 3: Create Field Exit
    Step 4: Create Function Module
    Step 5: Code Function Module
    Step 6: Activate Function Module
    Step 7: Assign Program/Screen
    Step 8: Activate Field Exit
    Step 1: Determine Data Element
    Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
    An easy way to determine the data element associated to a particular screen field is to:
    Go the appropriate screen.
    Position the cursor in the appropriate field.
    Press ‘F1’ for field-level help.
    Click on the ‘Technical info’ pushbutton (or press ‘F9’) on the help dialog box.
    On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
    Step 2: Go To Field Exit Transaction
    The transaction to create field exits is CMOD.
    You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
    From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
    After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
    NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
    Step 3: Create Field Exit
    From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
    After choosing this menu path, a dialog box will prompt you for the appropriate data element .
    Enter the data element name and click the ‘Continue’ pushbutton.
    Now, you will be able to create the function module associated to the data element’s field exit.
    Step 4: Create Function Module
    You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the ‘Continue’ pushbutton.
    In the ‘Function module’ field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
    FIELD_EXIT_<data element>
    You can add an identifier (an underscore followed by a single character ).
    The first function module for a data element’s field exit must be created without an identifier.
    To create the function module, click on the ‘Create’ pushbutton, choose menu path Function module -> Create, or press ‘F5’.
    After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing ‘Enter’, you will be able to go ahead and create the function module.
    Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
    Step 5: Code Function Module
    From the function module’s attributes screen, click on the ‘Source code’ pushbutton or choose the Goto -> Function module menu path to the code of the function module.
    Here you will add your desired functionality for the field exit.
    Remember that field exit’s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
    You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
    Step 6: Activate Function Module
    After coding the function module, you must remember to activate it.
    Use the Function module -> Activate menu path to activate the function module.
    At this point, you can return to the field exit transaction.
    You should be able to 'green arrow' back to this transaction.
    When you return to the field exit transaction, you will see an entry for the newly created field exit.
    At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
    Also, the field exit will not be triggered yet because it is inactive.
    Step 7: Assign Program/Screen
    This step is only needed if you want to make a field exit local.
    To make a field exit local, select the field exit and click on the ‘Assign prog./screen’ pushbutton.
    In the dialog box , indicate the appropriate program name and screen number.
    This information indicates that the field exit is local to the specified screen in the specified program.
    In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the ‘Fld. Exit’ field.
    If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
    If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
    Step 8: Activate Field Exit
    The field exit must be active for it to be triggered by the system.
    Activate the field exit by choosing the Field exit -> Activate menu path.
    After assigning the field exit to a change request, its status will change to ‘Active’ and it will be triggered automatically on the appropriate screen(s).
    NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
    Please reward points if helpful.
    Cheers,
    Swamy Kunche

  • Mandatory field in COPA characteristic group not checked

    Hello,
    I have customized a COPA characteristic group in KEPA transaction entering the product as a mandatory characteristic.
    Then I have posted a document in FBD9 taking a reference document that does nor have filled the product and the system does not show an error and the document is posted without the mandatory field.
    How could I solve this problem?
    Thank you very much
    Regards

    Hi
    Did you assign this char group in KE4G against your Busn Trans or in KEVG2 against record type B?
    If yes, and still it is not reading it, then refer note 115500.. you may need to apply this note
    Regards
    Ajay M

  • SHD0 transaction - Set Variant Group for VA01

    Hi Guru,
    please can you help us fixing Variant Group for VA01 transaction, only for specific user?
    We created a standard variant in SHD0 for VA01 tansaction and we assigned this variant to specific user group.
    Problem is that for these users in the group, standard variant is not imported into Sales Order (no screen settings are imported).
    If we assign the same Standard Variant into Order Type it works perfectly.
    Can you help us using this variant also for specific user (Variant Group)?
    Thank you very much
    Kind Regards
    Andrea

    Please do you have any news?
    Thank you very much
    Kind Regards
    Andrea

  • Screen exit for RF screen LM61

    Hi all,
       I have created a screen exit SAPLXLHU 1765 for the dummy RF screen SAPLLMOB 1765.
      The new screen has to be part of the XLHU function group, as the screen to be modified is for packing by delivery through the RF transaction LM61.
      I have saved this new screen as a local object. and now I am unable to change it or move it into a workbench request by changing the dev class. Even if I delete the screen and create it again it directly saves it as a local object without promting for the development class.
    Is there any other way to assign this to the request.
    Thanks in advance
    Sheetal.

    Hi Sheetal,
    Very interesting, I to am working on a similar enhancement for an RF screen in SAPLXLRF (not SAPLXLHU but the concept is the same). I also saved the enhancement screen as a local object to allow testing but can no longer add it to a development package or transport. Even if I delete and recreate the screen, it still ends up as local.
    I do not need to transport the enhancement screen as yet but will in future. I was thinking of raising a customer message with SAP to see if they could help.
    Let me know if you manage to find a solution.
    Regards
    Che

  • How we create Schema group for every vendor?

    If we have multiple vendors/transporters, how you configure pricing procedure for each vendor what is the process of creating Schema group for every vendor?
    Thanks in advance
    Suresh

    hi suresh,
    you create Pricing procedure, and then you create Vendor schema group; and purchasing schea group.
    for your scenario you will create N number of vendor schema groups.
    follow this menu path:
    spro --> materials management --> purchasing --> conditions --> define price determination process --> Define schema determination --> define caluculation schema for standard purchase orders -->
    in that screen:
    you maintain entries in the combination of
    purchasing org schema group  -- vendor schema group -- pricing procedure.
    for your scenario, you maintain N number of vendor schema groups and assign it to procing procedure.
    hope this may help you,
    Regards
    srinivas

Maybe you are looking for