Detail screen should be uneditable while MM01/MM02

Dear Gurus,
While creating new material or in change mode, in QM View, in that inspection setup tab, while assigning different inspection type, details information screen is in editable mode, i want that screen to be only in display mode.
Please guide.
thanks in advance
kailash thakkar

Hi
It is possible to control through monitoring authorization objects. For MM01 - Do not provide authorization for Inspection Setup
Use QA08 for inspection setup where you can control authorization limited to selection of inspection type and not to tamper with controls
Regards
Atul

Similar Messages

  • ALV Grid Details Screen Editable

    Hi All,
    I have requirement to Edit the ALV grid.
    ie I have ALV grid , after selecting (highlighting a line ), the user will go to the details screen, i need to be the details screen
    should be editable. Please give info about this.
    Thanks
    aRs

    My problem is if you put details screen also displayed in horizontal way. I need to display the fields in vertical order.and it should editable
    If you press details icon the grid, you see the selected records displays like the following , but i need to editable
    eg.
    Number     :  XXXXXX
    Desc        :   XXXXXXXXXXXXXXXXX
    Name        :  XXXXXXXXXXXXXXXXX
    Thanks
    aRs

  • Additional custom field on mm01/mm02 screen

    hi all,
    I need to create an additional custom field on mm01/mm02 screen.
    value entered in this field will be updated in the database.
    Kindly give pointer to the user exit/ screen where i can create the custom field.
    thanks in advance

    Hi Manish,
    Do the following process step by step as specified in the following link.[http://www.****************/Tutorials/ExitsBADIs/MM/MM01.htm]
    But in this link while you are at the 11th step
    select your required view.
    and do the rest as usual.
    This is at the configuration level u can add your customer fields.
    I dont think there are any exits available that can fulfill your requirement as the same requirement is fulfilled at the customization level.
    Thanks.

  • Screen-Exit MM01/MM02/MM03 - Problems when I try to retrieve the data saved

    Hi guys,
    I created a Screen-Exit in the Accounting View of MM01/MM02/MM03 because I need to insert data into the fields of an Append Structure of the table MBEW, that I created.
    So, I can insert the data through an User-Exit. I Export to the Memory the data from my Screen-Exit and I modify the Fields content of MBEW inside of this User-Exit.
    I need to select these data and show it, because the selection is not automatic. I don't know if it could be automatic.
    Inside of the Screen-Exit there are some tables available, but they are empty and I can't retrieve the data because I don't have
    the Material Number nor other data of MBEW. When I run MM02, for example, the User-Exit is not started and so
    I can't export the data to the Memory and after that to select the data. This User-Exit is only started when I save the data...
    I found not any BADI too...
    Please, could someone help me?? How I could solve this question?
    Thanks a lot!
    Regards,
    Marcos Fernando Dotta

    Hello Marcos,
    Please see OSS note 44410 - Integrating cust. - specific fields in matl master.
    Kind Regards,
    Rae Ellen Woytowiez
    Link:  [https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=44410]

  • WBSE Layout Detail Screens - Error while Client Copy

    Hi
    I have 4 Project Profiles like P1,P2,P3,P4.
    I customized the WBSE Layout Details with 05 TABs for P1.
    I included them in a TR & tried to make a client copy.
    End result in the Target client is 09 TABS for P4 profile (actual intention is 05 TABS for P1 Profile as mentioned above)
    This is very strange & I am not able to trace from where system picked up ... 
    1. Entirely different Project Profile
    2. How 9 TABs have come instead of 5 TABs
    Still,
    Source Client shows entries for 5 TABs for P1 Profile
    Target Client shows entries for 9 TABs for P4 Profile.
    regards

    Hi Rafi,
    TR is created following the automatic TR prompt while configuring only (similar to other standard configs).
    I didnot know the point that "TR created from IMG for WBSE Detail Screens will not work".
    But I made out the differences in "TCSCR" table entries (got this table from TR details) in the Source & Target clients.
    There is a key number field "0002" which is the reason for mismatch in table "TCSCR" in both the clients.
    I searched the help but did not get any value add.
    What can be the solution now?
    regards

  • Error in adding custom fields to mm01/mm02/mm03 trx

    Hello People,
    To add my custom fields in the basic view tab of MM01 transaction, i have performed the following steps:-
    1. Inserted the append structure in MARA table with the required fields.
    2. Copied function group 'MGD1' to 'ZMGD1' and then set the layout of screen '0001' as per my requirement.
    3. Then i made changes in spro as
         SPRO->Logistics-General->Material Master->Configuring the material master->define structure of data screens for each screen sequence and inserted my program name( of function group 'ZMGD1') and screen number(0001) in 21(Std ind.(short) tab pages)->7(Basic Data 1)->8(sequence).
    Now, if i click on SPRO option (view data screen), then i can see my fields added in basic data view...
    but when i execute 'MM01/MM02/MM03' trx  there my added fields do not appear....
    Does anyone know where i am missing out??
    Please suggest...
    Thanks in advance..
    Rgds,
    Abhi

    Here are some notes I have from when I recently added a new screen/subscreen to Material Master transactions.  Hopefully this information will help you.
    This guide should be used in conjunction with OSS note 44410 and IMG notes Logistics->Logistics Material Master->Material->Configure Customized Material Master.
    Online Maintenance.
    1. Add fields to append structure ZAEMARA.
    Use data dictionary maintenance u2013 SE11
    2. Generate table MARA.
    3. Add fields to view MARU and generate.
    Use data dictionary maintenance u2013 SE11.
    4. Create new sub-screen or add new fields to screen SAPLYMM1 9001.
    Use Screen Painter u2013 SE51.
    Change flow logic to add fields to field: statement and to add any validation required. Generate screen.
    If this is the first time additional data has been added to material master it will be necessary to create a new function group and associated programs. See Configure Customised Material Master paragraph Requirements.
    5. If new sub-screen, add to Customer main screen.
    Transaction OMT3.
    Double click on u2018Std industry sequenceu2019.
    Choose customer screen and Details.
    Change the first occurrence of 0001 (blank screen) to new screen number.
    Save.
    Back arrow.
    Click on Transport button and choose required transport.
    6. To include in 'Copy with Reference' processing - MM01, add new MARA fields to table T130F. (in each client)
    Use Transaction SM31. (make a copy of another ZZ field by typing over existing name).
    Add to transport manually:- R3TR TABU T130F + individual keys
    7. Test Material create, change, display.

  • Adding new field in MM01/MM02/MM03

    Hi All,
    I have a requirement to add a checkbox in MM01 costing2 tab page. I have done the basic configurations like adding a new field in MARC with Append Structure, creating Function group (for subscreen) in SPRO and assigning the same to the respective screen (2902) for Costing2 tab page.
    I am facing a problem that when i check the newly created checkbox in Costing2 tab page while creating new material. Once the material is successfully created, it is not reflecting in the MARC table for the same created Material,
    can anybody guide me to meet the desired requirement.
    Note : while running MM02 TCode the respective value to the newly created checkbox should retrieved from database table and if any change made to that should also be reflected back to MARC.
    Kindly help me in this regard
    Regards
    Babu

    USE set parameter id in the standard EXIT

  • Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

    Good day to all of you!
    I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
    In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
    I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
    MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
    1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
    2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
    PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
    All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
    Any help, pls?
    Good day and thank you!

    Hi Alex,
    In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
    http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
    and
    Just read the OSS note mentioned earlier.
    Symptom
    You want to integrate customer-specific fields in material master maintenance.
    Other terms
    SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001 
    Solution
    To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
          1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as  the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
          2. Enhancing online maintenance in customized material master maintenance:
          Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
          In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
          If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F): 
          Application examples for standard field selection:
          The field is mandatory and is to be flagged with a "?".
          The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
          The following data is required for each field:
                a) Field name        (T130F-FNAME)
                b) Field selection group (T130F-FGRUP)
                Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
                You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
                Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
                c) Maintenance status (T130F-PSTAT)
                List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
                d) Reference        (T130F-KZREF)
                This indicator must be set if the field from the reference material should be proposed during creation with reference.
    Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
    You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
    In addition, you must not add new standard fields to table T130F.
          3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
          Add the fields to central field table T130F (see above).
          Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
          Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
          For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
          If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
          Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
          As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
                a) Add the customer-specific fields to include CI_MMH1.
                The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
                Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in  table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
                b) Activate include CI_MMH1.
                c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
                d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
    Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
    In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
    Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
    If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
    If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
    To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
    check this link. It may helps you to solve your issue.
    Thanks
    Sravan

  • Stop Navigating from Basicdata1 tab to Basic data2 tab in MM01/MM02

    HI,
    In MM01/MM02 after giving the 1st screen details and selecting basic data1 and basic data2 .
    And navigating to the second screen there in Material Grp field is not a mandatory and if user does not provide any MATGRP it can navigate to the Basic data2 tab.
    But now reqmt is to check the material grp is blank or old matrieal grp is entered. If user provides an old materila grp or blank in the field it should not navigate the user from Basic data1 to Basic data2 and should prompt an error.
    Could anyone help me in achieveing  this functioanlity.
    Thanks.

    Closed.

  • How to restrict a User to access only 2-3 views in MM01/MM02 ???

    Hi,
    Can anyone tell me how can I restrict a User to access only 2-3 views in MM01/MM02 and also the User should not be allowed to change the View selection by clicking on the Select Views button ?.
    Regards,
    Lucky

    Hi Prashant,
    Can this only be done through changes in Authorization Objects ? Is not there any setting which can be done in SPRO for this ?
    Hi Sheshagiri,
    I could not exactly understand how the access to MM Views can be restricted to User through TCode OMT3B i.e. in SSeq. 01 and Screen 07 ? Subscreen 2154 is for Mat. Groups ? Please explain your answer in detail.
    Regards,
    Lucky

  • Post-generating 3-level master-detail-detail screens

    Hi all,
    for a consulting project, I had to create several three-level master-detail screens using JHeadstart. For the JHS demo app, this would mean for example that a location page contained a list of departments at the location and underneath it a list of employees working at the currently selected department.
    From what I have learned so far using JHS, this is not supported by the wizards and should be done by post-generation changes. This forum has a few topics mentioning the problem and possible solutions, but most of the time just fragments of the complete solution/approach. As I had to create several of these 3-level detail screens, I tried to uniformly document them, providing the 7-step guide as outlined below. I only started working with JHS recently, so please let me know where I take a long way round or where my approach is not appropriate at all :o)
    NOTE1: Terminology-wise, for the example given above, I will call the departments the 2nd level detail and employees the 3rd level detail, while locations are the first level masters. I hope this is not too confusing ;o)
    NOTE2: the example code is not guaranteed to work with the JHSdemo. I just changed the names of variables and classes from my own application to the familiar entities of the demo.
    STEP 1: Generate plain MD screens for the first and second level entities (table-form) using the JHS application generator and make sure all generated features you want in your page are OK. Afterwards, switch off the UIX generation in your application structure file. If you want multiple entities at the third detail level,
    STEP 2: Add the functional contents of the generated 3rd level detail UIX page to the main master UIX page, right underneath the 2nd level detail-table but still inside the <header> entity of this 2nd level detail. (I'm not too sure whether this really matters, but at least the indentation looks nice). What I call "functional contents" is the <header> entity containing the 3rd level detail table.
    STEP 3: Edit the java file of the 3rd level view object, adding a variable storing the identifier (primary key) of the currently selected 2nd level detail row. If you haven't used the java file before, generate it by doubleclicking the view object and checking the generate view object box in the Java screen.
    private String $selectedDeptID;
    public void setSelectedDeptID(String id) {
    $selectedDeptID = id;
    STEP 4: Edit the java file of your application module (in the model layer) and add a method for updating the view objects search queries like the example below:
    public void updateEmployeeView(String deptID) {
    // fetch the view object instance
    EmployeeViewImpl view = (EmployeeViewImpl)this.getEmployeeView1();
    // register the currently selected departments ID
    view.setSelectedDeptID(deptID);
    // re-execute the view objects query
    view.executeQuery();
    // reset the selected ID
    view.setSelectedDeptID(null);
    STEP 5: Create a java class for handling the event when a user selects a different 2nd level detail row.
    package view;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpSession;
    import oracle.adf.controller.struts.actions.DataActionContext;
    import oracle.adf.model.BindingContext;
    import oracle.adf.model.bc4j.DCJboDataControl;
    import oracle.adf.model.binding.DCDataControl;
    import oracle.adf.model.binding.DCUtil;
    import oracle.cabo.servlet.BajaContext;
    import oracle.cabo.servlet.Page;
    import oracle.cabo.servlet.event.EventResult;
    import oracle.cabo.servlet.event.PageEvent;
    import oracle.cabo.servlet.ui.data.PageEventFlattenedDataSet;
    import oracle.cabo.ui.data.DataObject;
    import oracle.cabo.ui.data.DataSet;
    import oracle.cabo.ui.beans.table.SelectionUtils;
    import oracle.jbo.ApplicationModule;
    * USER-DEFINED EVENT-HANDLING CLASS
    * this class is triggered after the user selects another row in the Department
    * table/form in the Locations.uix screen. It derives the ID (pk) of the
    * selected row and launches the AppModule method to update the view objects
    * select queries with the selected DeptID.
    public class RowSelector
    * private variable holding the name of the DataControl module for this
    * Application Module
    private static final String DATACONTROLNAME = "AppModule" + "DataControl";
    * private variable holding the name of the table/form object in the uix page
    * from which we want to derive the selected row data.
    private static final String TABLEFORMNAME = "DepartmentsView2";
    * private variable holding the name of the form field holding the database
    * ID (pk) of a row in the ${TABLEFORMNAME} table/form
    private static final String IDFIELDNAME = "Dept_ID";
    * This method fetches the ID of the user-selected row in the DepartmentsView2
    * table/form in the Locations.uix form.
    * Afterwards, it fires the ApplicationModule method for updating the view objects
    public static EventResult doSelectionEvent(BajaContext bc, Page page, PageEvent event)
    try {
    // create a new FlattenedDataSet for the table name
    DataSet tableInputs = new PageEventFlattenedDataSet(event, TABLEFORMNAME);
    // fetch the UI table index from the DataSet (NOT the pk from the db)
    int index = SelectionUtils.getSelectedIndex(tableInputs);
    // fetch the DataObject representing all the input elements on the current table row.
    DataObject row = tableInputs.getItem(index);
    // fetch the value of the input field holding the ID (pk) of the selected department row
    Object value = row.selectValue(null, IDFIELDNAME);
    if (value != null) {
    // tell the AppModule to update the appropriate view object(s)
    getAppModuleImpl(bc.getServletRequest()).updateEmployeeView(value);
    // quick and dirty exception handling. not too many exceptions possible due to
    // hard-coded field/table/module names. anyway, taking no action at all is not
    // that bad an option for a demo ;o)
    } catch (Exception e)
    e.printStackTrace();
    return null;
    * method for fetching the active Application Module
    public static AppModuleImpl getAppModuleImpl(HttpServletRequest request)
    BindingContext ctx = DCUtil.getBindingContext(request);
    DCDataControl dc = ctx.findDataControl(DATACONTROLNAME);
    AppModuleImpl service = (AppModuleImpl)dc.getDataProvider();
    return service;
    STEP 6: Override the executeQueryForCollection method in your view object java file to make sure it uses the selected 2nd level detail rows ID for the bound variable specifying the 3rd level select query. Otherwise, the select query for the 3rd level detail set appears to use the ID of the first 2nd level detail row selected for the currently selected 1st level master. In the example below, no other bound variables are used in the view object, otherwise, the indexing might have to be adjusted.
    protected void executeQueryForCollection(Object qc, Object params[], int noUserParams) {
    if ($selectedDeptID != null) params[0] = $uur;
    super.executeQueryForCollection(qc, params, noUserParams);
    STEP 7: In the Locations.uix page, set a primaryClientAction for the radio select input in the 2nd level detail screen. This action should fire an event (fe 'userChoseDepartment') and refresh the 3rd level detail tables using the partial refresh options in the primaryClientAction dialog window. Afterwards, add an event handler to the bottom of your Locations.uix page, linking the event specified before to the doSelectionEvent in the RowSelector class.
    So, that's how it worked for me. I hope it does the same for you and please do post any comments or remarks if problems arise or simplifications are possible. The more remarks or bugs appear in the above code, the more the JHS team is hinted to enable auto-generated 3rd level detail screens :-D
    Cheers,
    benjamin

    Benjamin,
    Thank you for sharing your expreinces with us!
    A few remarks:
    1. With JHeadstart 10.1.2.1 you can generate unlimited master-detail levels in the same page when using UIX and table-layout for the detail groups This feature is implemented usin g UIX table detail disclosure: when you click on the "show" link in a row in of the level 2 detail table, you will see in the detail disclosure area the level 3 detail table.
    There is a screen shot of this feature in the JHeadstart Developers Guide for 10.1.2.1, chapter 3, section "Creating Table Pages". You can now download the dev guide from the JHeadstart Product Center:
    http://www.oracle.com/technology/consulting/9iservices/jheadstart.html
    2. You have a lot of steps related to synchronizing the level 3 ViewObject with the level 2 ViewObject. You can leave all this work to ADF Business Components, by adding the l;evel 3 ViewObject as a nested usage to the level 2 ViewObject in your application module data model.
    Ths would save you the work you aredoing in steps 3 to 6.
    Steven Davelaar,
    JHeadstart Team.

  • Navigation via button in agentry editor details screen -SAP Round Manager

    Guys,
    I am looking to open a details screen from a details screen via a button or an image on click .Please suggest the right way to do that .Please follow the attached figure for your reference .
    Tags edited by: Michael Appleby

    My requirement is - I have a field with extra information(Called LongText) about a measuring point and while user is reading a point there should be an option for them to read the extra information(not compulsory) like the below information icon.
    Now on click on this icon one screen should open where the LongText field will be mapped ,So user can read the extra information and act accordingly .So for this I have added one button on 'Reading Point ' screen to fire one action to open another screen for LongText but it's not working .
    Hope make sense to you !!

  • SAP Work Manager customization - adding a new field to equipment details screen (Syclo Agentry)

    Hi Experts,
    I am trying to add a field (NAME1) on the Equipment details screen under work orders in work manager 5.3 application.
    I have performed the following steps, but I am getting an error while connecting to the application.
    1) Create extension for Equipment class to add a new field.
    2) added the new field (Name1) as the property to the standard object Equipment.
    3) Added the field on the screen.
    4) Added the field (name1) to the complex table ctEquipment.
    5) Added the JAR file to Agentry.ini file.
    6) Changed the Class mapping for parameter "Equipment" under group "SAPOBJECT" to point it to the custom (Extended) class.
    7) Changed the class mapping for complex table parameter "ctEquipment" under group "CT_SAPOBJECT" to point it to the custom class.
    8) after publishing the changes and re-starting the server, I get following error.
    the log file generated (message.log) also has the same description.
    What am I missing here? Any help would be really appreciated.

    Hi Emanuel,
    Thanks for looking into this issue.
    I have performed the following steps as suggested by you, still it doesn't seem to work and gives the same error.
    Below are the changes done on the ECC Side.
    1) Copied the standard equipment class /SYCLO_CL_PM_EQUIPMENT1_DO to custom class ZSYCLO_CL_PM_EQUIPMENT1_DO. Changes made in the GET Method to get custom equipment related data
    2) Modified the standard equipment structure /SYCLO/PM_EQUI_STR by adding one custom field
    3) Configured this custom class as the object handler in the equipment mobile data object
    4) Configured this custom class as the object handler for the equipment complex table
    5) We are still using the standard BAPI Wrapper itself for getting the equipment data and the added field is reflected in the BAPI Wrapper table parameter
    Is there something we are missing?

  • When i plug in my ipod touch to charge it starts with the battery with the little bolt under it then it goes to the apple logo screen and after a while it flashes white and just shuts off and restarts the process. Whats wrong and how do i fix it?

    when i plug in my ipod touch it goes to the battery witht he bolt under it the goes to the apple logo screen and after a while it will flash white like its trying to go to the lock screen but just restarts and restarts the process and keeps doing it. What should i do? Is there any way to fix it?

    See if you missed anything here:
    - iOS: Not responding or does not turn on
    - Also try DFU mode after try recovery mode
    How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
    - If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
    - Try on another computer
    - If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
    Apple Retail Store - Genius Bar       

  • How to activate the new fields on material master(MM01/MM02/MM03) for existing Materials

    Hi,
    We have a requirement to add  some custom fields as a new tab in additional data option(Descriptions, Unit of measure, etc.) in Basic data of Material master (MM01/MM02/MM03). I have successfully added and these custom fields and they are not part of standard(MARA, MARC) but a custom table and the updates are also done in custom table.
    For new materials, I can see the new tab in additional data screens of basic data view and I could successfully create/change/display using MM01/MM02/MM03. However I cannot see the new tab/fields for existing materials in the system in all 3 tcodes (MM01/MM02/MM03). This is not a main view in material master so that I can extend it by MM01.
    Is there any setting or mass generation program I have top perform so that I can see and maintain these new fields for existing materials. Appreciate any leads or help on this.
    Thanks,
    Harry

    Hello Harry,
    Goto t.code SPRO ---> Display IMG --->  Logistics - General --> Material master --> Configuring the material master --> Create program for customized screens
    Use the above path and create the screen and assign it to the sequence using the below link as reference.
    **************** - Tips - Implementing screen exits for MM01/MM02/MM03
    Regards,
    Thanga

Maybe you are looking for