Customer Enhancement Tabs to be made mandatory

Hello
I have WBS Customet enhancement tab wherein I want to make them madatory, and system should give error while saving.
Can anyone help me?
Deepak M Pitale

Also, If you want to go with user-exit option then check the following exits:
1. CNEX0009 -- EXIT_SAPLCOMK_001
      Use this exit while processing materials from the network orders.
2. CNEX0011 -- EXIT_SAPLCOMK_002
      With this user exit, you can modify the quantity of the BOM items which are exploded at the BOM explosion
in the network screens.
      This exit will export STPOX_TAB table which is the structure of the BOM items.
3. CNEX0014 -- EXIT_SAPLCN10_001
      The user exit can be activated when you want to transfer BOM items from external systems.
      If the exit is active then the indicator for the takeover of external data in the initial screen of the interface like
CN33 should be set active.
      In return, a table with the extended structure of the BOM items (STPOX) is expected.
4. CNEX0015 -- EXIT_SAPLCN10_002
      This exit can be used to change BOM data for BOM transfer.
      If this user exit is called, then a function module is called after the BOM explosion. This function module
receives a structure with fields from the initial screen (RCNIP01) as well as the table of selected Bill of
materials items (STPOX).
      The changed table can be returned to the calling program for further processing.
5. CNEX0026 -- EXIT_SAPLCOMK_005
      This user exit is used to check if there are any changes done to the material component in the component
overview screen or the details screen of the material component.
      Please note that this user exit is called only during the change in component overview screen or
component detail screen.  In other words this exit cannot be called if for an example the network order header
changes which involved in the material component change during release or scheduling etc.,
6. CNEX0034 -- EXIT_SAPLCN10_003
      This user exit is used to check if a new assignment is allowed for the network activity during BOM transfer
to PS (CN33).
7. CNEX0035 -- EXIT_SAPLCN10_004
      This user exit is used to check if a change to an existing assignment is allowed for the network activity
during BOM transfer to PS (CN33).
8. CNEX0036 -- EXIT_SAPLCN10_005
      This user exit is used to check if any existing assignment can be deleted during BOM transfer to PS
(CN33).
9. CNEX0037 -- EXIT_SAPLCOMK_011
      This user exit can be called during creation of new material component to the network activity.
10. CNEX0038 -- EXIT_SAPLCOMK_012
      This user exit can be called during change of material component.
11. CNEX0038 -- EXIT_SAPLCOMK_013
      This user exit can be called during deletion of material component.
12. CNEX0040 -- Source determination of the network
      This user exit is used to activate the source determination of the network.
13. CNEX0041 -- EXIT_SAPLCOZF_004
               -- EXIT_SAPLCOZF_005
      This exit is used to influence the date of price simulation when you specify a Purchasing Info Record for an
activity/element or for a component.
14. CNEX0042 -- EXIT_SAPLCN10_006
      This user exit is used to control the generation of preliminary requirements for the top level BOM item
during multi-level BOM explosion.
Regards
Saurabh

Similar Messages

  • Want to change customer enhancement tab name in CJ20N

    Hi Friends
    As per our requirement, we have created customer enhancement tab in CJ20N (project definition level).
    It shows the name as cust.enhancement, but as per our requirement we want to change the tab name.
    But we are not able to change that.
    if anybody come accross this type of scenario, kindly let me know.
    Thanks
    Gowrishankar
    Edited by: gowrishankar p on Mar 30, 2010 1:26 PM
    Edited by: gowrishankar p on Mar 31, 2010 9:39 AM

    Hi mithilesh,
    we can do it. but it may need access key. Find out the screen number and program name.
    Go to se51 and input the program name and screen number then select Layout ->display.
    click on that tab, move change mode then give the text what do you want.
    Give Points if useful.
    Regards,
    Jogesh.Mutyala

  • How to change enhancement tab name iw33 transaction

    Hi,
    I have created one custom enhancement tab in iw33 transaction,but i have to change name for enhancement tab.
    Can you pls suggest me.
    Best Regards,
    Babu

    Hi
    There is a OSS note 1340615 for the same.
    I just copied the same from market place.
    Follow the steps to make the change if the changes can't be downloaded auotomatically.
    1. Start the transaction SE51.
    2. Give program as SAPLCOIH and screen as 1100. Select the radio button (option) 'Element List'.
    3. Click on the change button.
    4. In general attr. for the field 'BTN_PLUS_CUK' change the column 'Vislg' from the value '10' to '13'
    5. Save and activate.
    6. Go back to initial screen of the SE51 transaction.
    7. Give program as SAPLCOIH and screen as 1205. Select the radio button (option) 'Element List'.
    8. Click on the change button.
    9. In general attr. for the field 'BTN_VGD5' change the column 'Vislg' from the value '10' to '13'
    10. Save and activate.
    Shiva

  • How to Update EKPO table with enhancement at header level-customer data tab

    Experts,
    I have a requirement where I had to create a new button in the 'customer data' tab(header) in the ME21N/ME22N Transaction and once it gets clicked a table control will appear and in that all the line items with item no, material and plant and an additional check box will display, and once any one checks the check box against the item/material in the table control the item data with additional z fields (already created the zfields in EKPO Table) should get updated.
    Displaying Table control and item data on the click of button was successful, but once you check the check box against the item and save the PO it is not updating the z-fields in the EKPO table.
    I have implemented all the user exits , badis but no results. 
    Once you check the box in the table control against each item in the header part (Table control is in header part (customer tab)) the line item EKPO table with z fields should get updated.
    Any Clues/ideas will be appreciated.
    Thanks in advance,
    Kalikonda.

    Hi,
    Can you please share the remedy for above issue, recently we have same issue in our system.
    or please send me any supportive doc. for the below mail
    Looking forward for your positive response.
    Thanks
    Mohan
    ([email protected])

  • PO Custom Data tab size incorrect after EHP4 installation

    Hello,
    We have previously enlarged the size of the custom data tab on PO transaction ME23N (via modification) in order to accommodate a comprehensive overview of the many custom fields we have. The screen we changed is as follows:
    Program: SAPLMEGUI
    Screen: 1227
    Original size:
    - Lines/columns Occupied 5 / 100
    Mainten. 5 / 100
    Modified size:
    - Lines/columns Occupied 23 / 160
    Mainten. 23 / 160
    It worked out fine in our ECC6.0 Release 700 (SP17).
    Recently we upgraded to Release 701 (SP03). We have made the same modification to the same screen as mentioned above. However, the screen was not resized as we had expected. Its size stays as 5/100. So the user has to scroll through a very short subscreen in order to see all custom fields.
    Have anyone of you experienced this ( or any UI related issues)  after installing enhancement pack 4 of ECC 6?
    Any of your suggestions are appreciated.

    Sap has provide a sample in OSS [ Note 407975 - MM06E005: Collective note: Examples for implementation|https://service.sap.com/sap/support/notes/407975] - compare with yours
    Regards,
    Raymond

  • In PS field RESBD-GPREIS cannot be made mandatory but can in PM

    The feild RESBD-GPREIS can be made mandatory in PM but it does not take effect in PS and the field is not available in PS config.  I have tried
    SPRO>IMG>Project Systems>Structures>Operative Structures>Networks>User interface settings --> Define field selection for networks --> Field selection :Network:Details -->
    without luck.   Has anyone been able to make Price mandatory for Purchasing tab in PS?   We can make external processing using AFVGD-PREIS

    In general in Web Dynpro ABAP, setting the required property on the UI doesn't actually do anything except visibily mark the UI element with the required symbol (the red * next to the label).  Unlike classic dynpro, this property doesn't cause a runtime check to see if the field has a value or produce an error message.  This must be added within the application logic.  There is a helper method cl_wd_dynamic_tool=>check_mandatory_attr_on_view.
    That said, I can't comment specifically about this SRM framework.  It would be something application specific that sits above the WD framework.  Perhaps it has this dynamic call already built in and this situation is an error.  Or it could be the case that the SRM tool is just exposing all the UI element properties and you would have to use the Enhancement Framework to extend the view logic to acutally perform a mandator check.

  • To change a field to edit ,which is in customer fields tab of an item in crmd_order transaction.

    Hi All,
    My requirement is to change a "field to edit" which is in "customer fields tab" of an item in "crmd_order" transaction.
    Please find the screen shot.
    Please help me with this issue

    Use easy enhancement workbench
    The Easy Enhancement Workbench is a development tool with which SAP applications (called Business Objects in the following document) can be extended in a simple manner.
    Customer enhancements to a Business Object are defined via wizards. The Workbench then does all development work for the user; databank tables, screens and application logic are created automatically. Finally the customer enhancement is included in the SAP standard.
    This also allows users without ABAP knowledge the simple possibility of extending the SAP standard.
    An extension created using the Easy Enhancement Workbench does not differ technically from one created manually. In both cases transportable ABAP objects are created and the same Customer Exits, Business Transaction Events or BAdIs are implemented
    You need to use EEWB feature to achieve the same.
    Tutorial
    http://www.scribd.com/doc/6755615/Eewb-Steps
    http://help.sap.com/saphelp_crm50/helpdata/en/9f/a19c921f0911d6b1d500508b6b8b11/frameset.htm
    In addtion check this note
    Note 484597 - Customer enhancement of CRM applications
    a guide is attached to it for telling u steps
    Hope query is solved
    Regards
    Prakhar

  • Error in Variable in Customer Enhancement

    Message  : Error Variable in Customer Enhancement YQVMTD
    I need To Create Customer Exit For Variable based on 0P_FPER (Fiscal Year Period).The user has to enter a value for Fiscal year/Period(0P_FPER).If the user is entering Current month(eg:July 2009) then the report should display Previous Month(eg:June 2009) .If user is entering months other than current month (eg: April 2009)  then the report should display April 2009 Data only.
    Special Case: If the System Date is Jan 2009(That is if Current Month is Jan 2009) then the report should display Dec 2008 Data.
    This is the exit in CMOD for the customer exit variable u2018YQVMTDu2019.  This variable in not ready for input.
    DATA :
                curfiscper TYPE /bi0/oifiscper,
          Curperiod(3) TYPE n,
          Curfiscyear(4) TYPE n,
      When u2018YQVMTDu2019.
       IF i_step = 2.
         READ TABLE i_t_var_range WITH KEY
         vnam = '0P_FPER'
         iobjnm = '0FISCPER'
          INTO l_s_var_range.
        if sy-subrc = 0.
             Concatenate sy-datum0(4) '0' sy-datum4(2) into curfiscper.
             If l_s_var_range-low = curfiscper.
                Curperiod = l_s_var_range-low+4(3).
                If Curperiod = '001'.
                   Curfiscyear = l_s_var_range-low(4).
                   Curfiscyear =  Curfiscyear - 1.
                   Concatenate Curfiscyear '012' into l_s_var_range-low .
                Else.
                   Curperiod = Curperiod - 1.
                   Concatenate l_s_var_range- low(4) curperiod into l_s_var_range-low. 
                EndIf.
              Else.
                 l_s_var_range-low = l_s_var_range-low.
             EndIf.
        l_s_range-sign = 'I'.
        l_s_range-opt = ' EQ '.
        APPEND l_s_range TO e_t_range.
        EndIf.
      EndIf.
    When i execute the query i am getting the following error:
    Error Variable in Customer Enhancement YQVMTD
    Diagnosis
    This internal error is a deliberate termination, since a program status has arisen, that is not allowed to occur.
    The error has arisen for variable YQVMTD in the customer enhancement .
    Procedure
    Please check your customer enhancement.
    Procedure for System Administration
      Notification Number BRAIN 649
    Please have a look into this and suggest me whether i need to change anything in the code in the exit.

    Hi Rathy,
       Yes I made the change at all places.
    When 'YQVMTD'.
    IF i_step = 2.
    LOOP AT I_T_VAR_range INTO l_s_var_range WHERE vnam = '0P_FPER'.
    Concatenate sy-datum0(4) '0' sy-datum4(2) into curfiscper.
    If l_s_var_range-low = curfiscper.
    Curperiod = l_s_var_range-low+4(3).
    If Curperiod = '001'.
    Curfiscyear = l_s_var_range-low(4).
    Curfiscyear = Curfiscyear - 1.
    Concatenate Curfiscyear '012' into l_s_range-low .
    Else.
    Curperiod = Curperiod - 1.
    Concatenate l_s_var_range-low(4) curperiod into l_s_range-low.
    EndIf.
    Else.
    l_s_range-low = l_s_var_range-low.
    EndIf.
    l_s_range-sign = 'I'.
    l_s_range-opt = ' EQ '.
    APPEND l_s_range TO e_t_range.
    Endloop.
    EndIf.

  • Movtement type 101: Reason for movement made mandatory

    We have made reason for movement made mandatory for movement type 101.
    Now, we go for posting 'Service Entry Sheet', system does not allow it to post.
    While posting service entry sheet, can we enter 'Reason for movement'.
    Regards,

    Hi Rajan,
    You can set "reason for movement" field to either required entry or
    optional entry in customizing for the transaction MIGO. You can do this
    here in the IMG:
    -> Materials Management
    -> Inventory Management and Physical Inventory
      -> Settings for Enjoy Transactions
       -> Settings for Goods Movements (MIGO)
        -> Field Selection per Mvt Type
    Select the entry for movement type 101 and field GRUNG, set to
    required' and save.
    regards,
    Ramana

  • Customer Data tab

    Hi All,
    We have added a customer data tab in PO header using enhancement MM06E005. We also added a push button in this tab. Our requirement is to call a zprogram once the user presses this push button. Is it possible?
    Regards,
    Sibin

    Hi , you add pushbuton in one of this screen
    and you should handle pressing this button in PAI module of screen
    PROCESS AFTER INPUT.
      MODULE user_command_0010.
    MODULE user_command_0010 INPUT.
      save_ok = ok_code .
      CLEAR ok_code .
      CASE  save_ok.
        WHEN 'XXX'.    "  code of tour button
            submit zprorgam with ... and return .
           WHEN OTHERS.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0010

  • How to create Customer data TAB in PO -ME23N

    Can anyone tell me how to add 'Customer data' TAB in the PO heade TABSTRIP. I have to add it in the header besides 'Status' TAB.
    I know an enhancement 'MM06E005' which is used for this purpose.
    Thanks
    SMS

    Hi
    see this sample doc and do it accordingly
    by creating a project in CMOD and assigning the Enhancment MM06E005  and writing the code in the respective screen
    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
    Regards
    Anji

  • Using MEREQ001 u2013 Checking error for data in customer data tab.

    Hi Guys,
    I have implemented MEREQ001 enhancement to add custom field in CUSTOMER DATA tab at item level. I want to validate the custom fields for error and display RED dot in front of the line item number when user press SAVE button.
    I am using EXIT_SAPLMEREQ_005 for validating the custom field when user press SAVE button.
    Is this the correct exit for this requirement.
    Can somebody share to code to display the RED dot in front of the line item which has error in custom fields?
    Thanks in advance.

    I think it's right
    U need to tranfer the message to exporting parameter or raise an error message

  • What is "Customer Fields" Tab in the CHaRM

    Hi All,
    can any one explain what is the "Customer Filelds" tab in the Change Request for?
    It is found under the Transaction Data button  of the Change request ticket.
    Thanks in advance.
    Regards,
    Pradeep L

    Pradeep ,
    This tab is used for creating additional customer fields
    note
    Note 816456 - Customer enhancements for CRM business object types
    Regards
    Prakhar

  • Custom Enhancement

    Hi All,
         I have a custom enhancement implementation.Though the Enhancement is active the code associated with the enhancement is not getting executed.
    Should the the Enhancement implementation necessarily be assigned to a switch for it to get executed.Please clarify.
    Regards,
    Roopa
    Edited by: Roopa R  on Jun 18, 2008 1:36 PM

    Hi Roopa,
    All the standard SAP Enhancements are seen in SMOD. Here we will be viewing all the components for the particular packages.
    After picking up the correct one that suits to our requirement we will go to CMOD, and create a ZXXX  customer project there. After that you will be importing the particular exit and click on the components tab respectively.
    For knowing that whether your enhancement is active or not you will be clicking on the function module exits and insert a break point over there. Inside the function module exits there will be includes. In that includes you will writing your code.
    For Ex: EXIT_SAPMM06E_006  in that include write     break username , by this that particular exit gets triggered for your ID only. Similarly you will be ruuning your transaction by giving some input details, so by this you will be checking for the exits.
    In the same way for BADI's also to find a exact BADI you will be creating an implementation on the interface tab there you will be finding number of methods. Inside the methods you will putting a break point and activate them.
    Then you will run your transaction.
    Cheers,
    Swamy Kunche

  • VERSION "completed" check box to be made mandatory

    Sir,
    I want to make version "completed" check box to be  now made mandatory.
    right now reason and text is made mandatory
    regards
    amey

    When you create a requisition or an external purchasing document (such as a PO), the system automatically creates an initial version (version 0). From this time on, changes and newly entered data are documented in the current version that is valid in each case.
    In the case of requisitions, one version is generated per requisition item (at item level). In the case of external purchasing documents, one version is generated per document (at header level).
    Once all necessary data has been entered for the purchase requisition, the version must be completed. Only then can:
    ●     The purchase requisition be released or converted into a follow-on document
    If a requisition is subject to an overall release procedure, the versions of all requisition items must be completed in order for the requisition to be released and converted.
    ●     The external purchasing document be released or outputted (printed out or transmitted as a fax or EDI message etc.)
    You complete a version by setting the Completed indicator in the version data. The processor of a purchase requisition or external purchasing document thereby explicitly indicates that he or she has now made all changes desired at the time.
    You can specify that version 0 is to be completed automatically in Customizing for Purchasing. To do so, set the Version 0 OK indicator under Version Management ® Set Up Version Management.

Maybe you are looking for