Screen Exit MIRO

Hi
    I have used as BADI MRM_ITEM_CUSTFIELDS to design custom tab. I have written code in METHOD....ENDMETHOD which is triggering. I am getting value in screen field variable through debugging. But not appearing in screen field.
   But if i pass hard coded value for screen field in PBO, its populating in screen field. I have used SET PARAMETER ID,  IMPORT &  EXPORT values to store the value in PBO. But its not working.

Hi
data: l_zsdper type zsdper,
        l_ebeln type ebeln,
       wa_drseg like line of it_drseg,
       mmcr_drseg type drseg.
" IT_drseg is an intenal table  which is an importing parameter.
loop at it_drseg into wa_drseg.
l_ebeln = wa_drseg-ebeln.
endloop.
select single zsdper
            from ekko
             into l_zsdper
           where ebeln eq l_ebeln.
if sy-subrc eq 0.
move l_zsdper to mmcr_drseg-zsdper.
" mmcr_drseg-zsdper is my screen field which is getting value throhgh debugging.
endif.
in PBO " If i pass hard code value, its displaying in screen.
move 15 to mmcr_drseg-zsdper.

Similar Messages

  • Runtime error in MIRO while using User/Screen exit

    Hello,
    I have implemented an exit in ABAP for MIRO which when transported to Quality server through runtime error.
    I have used EXIT (SMOD) : LFDCB001 which contains FM -> EXIT_SAPLFDCB_001 and include -> ZXM08U31. In this exit I have written my code to disable Inv. Party field. This field exist in Details Tab in Miro Transaction.
    Location of the field: MIRO -> Details (tab) -> Inv. Party (Field)
    Code written in include ZXM08U31 is:
    LOOP AT SCREEN.
      IF screen-name = 'INVFO-LIFRE'.
        screen-input = 0.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
    This exit is assigned to a project in CMOD and I tested the same in Development system. It is working perfectly.
    Now I transported the TR (Includes program ZXM08U31 and Customer enhancement projects ZMIRO). Now when I run MIRO in quality server it triggers the my logic and then through runtime error.
    Runtime error says:
    Short text
        Dynpro does not exist
    Error analysis
        The system attempted to use dynpro 0400 in program "SAPLXM08".
        This dynpro does not exist.
    I agree that screen 400 does not exists in program for MIRO but it does not exists in development system as well. So if the runtime error is valid in QEC server then why not in DEV server. And when it can run successfully in DEV server why cant it run in QEC server.
    Hope I have explained all the things in detail.
    Please provide me the solution since user can bombard anytime for the MIRO dump everytime in QEC.
    Regards,
    Harjeet Grover

    Hi Harjeet,
    Reason of your Dump is that the enhancement "LFDCB001" which you used contains one Function module exit "EXIT_SAPLFDCB_001" and another one screen exit in calling screen  "SAPLFDCB" number 0150.
    So when you activate your project these above mentioned both components were activated.
    So when you execute transaction SAP looks for called screen "SAPLXM08" No-0400 but as you havn't created and program go for DUMP.
    Solution - Just Create called screen  "SAPLXM08" No-0400 and activate.
    Thanks,
    Vijay

  • Field/Screen Exit for MIRO

    Hi Friends,
    The client requirement is to fix an Exit to disable or inactive the field INVFO-LIFRE or to put the INVFO-LIFRE field (invoice party in Details tab) as display mode where the user not able to change it while posting invouces in MIRO.
    I've tried by program screen enhancement in 'SAPLFDCB' but i couldn't able to fix it since the screen name of INVFO-LIFRE is not showing/coming while posting MIRO (checked in debugging mode).
    Instead of fixing error message through BADI/USER EXIT, is there any way to make field/screen exit to disable or inactive the filed??
    Please advise.
    Thanks & regards
    Sankar.

    Hi,
    Check the below link.
    [Screen exit for MIRO transaction;
    [Re: steps to create field exit;
    Regards
    Sunil

  • Screen exit problem MIRO

    Hi,
    I can't find screen exits on MIRO. My requirement is to display popup but i can't use field-exit and i need create a screen exit . Please let me know the screen-exit for the same. Regards
    Bye

    Hi Marcos,
    Please make a habit of searching in SCN first. On this topic, you will find lot of material. As you are new to the SCN, therefore for your help, refer to the following links:
    User exit in Standard transaction
    Screen Exit
    Hope this will help you...

  • Screen EXIT for MIRO

    Hi ,
    I want to add two extra field in the Item Level of MIRO transaction .Is it possible to add two more field in the Item Level .
    I got one SCREEN EXIT -
    LMR1M001 , But that is in Header Level .I want at the Item Level .
    Please reply me .

    Hi,
    Check these Badi's
    BADI     SAPLSADR-LSADRU04     ADDR_PRINTFORM_SHORT
    BADI     LMR1MF79                     BADI_ENJ_ALT_ADR
    BADI     SAPLMR1M                     BADI_ENJ_ALT_ADR
    BADI     SAPLFDCB                     BADI_ENJ_ALT_ADR
    BADI     SAPLFACS-LFACSU15     FAGL_PERIOD_CHECK
    BADI     SAPLFACS-LFACSU42     FI_TRANS_DATE_DERIVE
    BADI     SAPLMRMC-LMRMCU21     INVOICE_UPDATE
    BADI     LMR1MI2G                     MR_CIN_LMR1MI2G
    BADI     SAPLMR1M                     MR_CIN_LMR1MI2G
    BADI     LMR1MI10                                     MR_CIN_LMR1MI2G
    BADI     LMR1MI1N                     MR_CIN_LMR1MI2G_SEL
    BADI     SAPLMR1M                     MR_CIN_LMR1MI2G_SEL
    BADI     LMR1MI10                                     MR_CIN_LMR1MI2G_SEL

  • Urgent - screen exits

    HI ,
    in miro transaction while posting document ,whenever we select g/l account in next screen instead of assignment field data we need to put corresponding po data
    HOw can i do this?
    reg

    hi
    here r the ways to find out the screen exits for a tcode
    1. go to the transaction you are workin on.
    2. go to system --> status and there you'l find your package name.
    3. now go to SE81 --> info systems --> enhancements --> customer exits --> enhancements and give your package name there.
    now you'l get your screen exit here.
    or
    Finding the Exits of a TCode:
    1) Goto Program of Tcode and get the Package of that program.
    2) Now go to SMOD(TCode) in enhancements press f4.
    3) now click on information and give the package u will find all the enhancements. Check the component of enhancement where u will find the function Module of exits.
    If u find it useful mark the points
    SIRI

  • How to find out a screen exit

    hi seniors
    can any one tell me abt screen exit n thier search.
    pls hurry
    points will be rewarded
    offer valid for today only.
    Sameer

    hi,
    How to Find a Screen Exit in a Given SAP Standard T-code
    Program
    REPORT YSMOD2 .
    TABLES: MODSAP, MODACT, TSTC.
    PARAMETERS: INPUT1 LIKE TSTC-TCODE DEFAULT ' ',
                INPUT2 LIKE MODSAP-TYP DEFAULT ' '.
    DATA: SEARCH1(6),
          SEARCH2(3),
          SEARCH3 LIKE MODSAP-MEMBER.
    DATA : FIRST_ROW VALUE 'Y'.
    CONCATENATE: '%' INPUT1 '%' INTO SEARCH1,
    '%' INPUT2 INTO SEARCH2.
    SELECT * FROM TSTC WHERE TCODE LIKE SEARCH1.
    FIRST_ROW = 'Y'.
    CHECK TSTC-PGMNA NE SPACE.
    CONCATENATE '%' TSTC-PGMNA '%' INTO SEARCH3.
    SELECT * FROM MODSAP WHERE TYP LIKE SEARCH2
    AND MEMBER LIKE SEARCH3.
    SELECT SINGLE * FROM MODACT WHERE MEMBER = MODSAP-NAME.
    IF FIRST_ROW EQ 'Y'.
       WRITE: /0 TSTC-TCODE, 6 TSTC-PGMNA, 16 MODSAP-NAME, 32 MODSAP-TYP,
              45 MODSAP-MEMBER, 70 MODACT-NAME.
       FIRST_ROW = 'N'.
    ELSE.
       WRITE: /16 MODSAP-NAME, 32 MODSAP-TYP, 45 MODSAP-MEMBER, 70 MODACT-NAME. 
    ENDIF.
    CLEAR : MODSAP, MODACT.
    ENDSELECT.
    IF SY-SUBRC NE 0.
       WRITE : /0 TSTC-TCODE, 6 TSTC-PGMNA, 30 'No exits found'.
    ENDIF.
    CLEAR TSTC.
    ENDSELECT.
    END-OF-SELECTION.
    CLEAR: SEARCH1, SEARCH2, SEARCH3.
    Regards
    Sudheer

  • Creation of sales order- screen exit

    Hi all,
    I have a requirement like while creation of sales order need to develop one screen field in additional data B.i developed that field. and now while creation of sales order it will save in vbak table. now the problem is that screen field will be enable in that particular sales order type only otherwise it will be disable. how to do this. screen exit.

    Hi
    See SAP Note 209278 - Display of customer-specific fields in sales doc
    Check also, SAP Note 302497 - Additional cust. fields not displayed in 'Additional data B' and SAP Note 386694 - Additional data not displayed in screen 8459 and 8309
    Regards
    Eduardo

  • Screen-exit for profit center creation - transaction KE51.

    Hi All,
    Background: The client has the requirement of importing profit centre master data from legacy system into SAP ECC system. Few of the legacy data could not be filled into existing sap fields, hence the requirement has been to populate the data into custom fields.
    The client also has the requirement, that the same fields are required during online entry. For this we need to enhance the profit centre creation screen (transaction code KE51) with two additional custom fields.
    Requirement: To enhance profit centre creation screen with custom fields. Screen-exit for KE51 transaction.
    Pre-work: Program SAPLRKPM in SAP ECC system is the main program. It does not have any screen or sub screen area for custom fields addition. Debugged the program to check for screen-exits, found none.
    Below user-exits are not either screen-exits or cannot be used for enhancing profit center screen.
    PCA00001  EC-PCA: Document changes for data transfer
    PCA00002  Profit Center Accounting: derivation of representative mat.
    PCA00003  Derive Partner Profit Center for External Deliveries
    PCA00004  Check valuation for invoice verification with transfer price
    PCA00005  Check valuation for invoice verification with transfer price
    PCASELEK  EC-PCA: Selection criteria for data transfer
    Solution required for: Could anyone please let me know if it is possible to enhance the profit center creation screen. If yes, please provide the names of the screen-exit/  badi exit.
    (Just a thought, modifying the standard seems to be the only solution, this should be the last option and i agree, please provide your inputs.)
    Thanks in advance.
    Warm Regards,
    Goutham.

    Thank you Manohar for the response.
    The requirement is to display custom fields on standard sap screen and there are no screen-exits. So, i suppose the standard screen has to be modified.
    Could you please provide brief explanation on
    May be you should consider maintaining custom mapping table instead of going for chaning standard.
    With Regards,
    Goutham.

  • Screen exit/BADI for adding custom field in IW31/IW32

    Hi all,
    The requirement is to add the permit field in the Header component of IW31. Searched SDN and found user exit IWO10018 for the same which includes a screen exit.
    The activation of the same is adding a tab in the screen while user wants the field under header Component tab.
    How this can be done. Any suggestion.
    Thanks
    anya

    Hi,
      You can perform append structure to add your custom field(s)in VBAP table. Next step, go to SE51 (Screen Painter)to modify SAP Program SAPMV45A Screen number 4459 for Additional data A or Screen number 8459 for Additional data B to add your append structure custom fields.
    Once the above steps done, you can place your logic to populate custom fields in include program MV45AFZZ. i.e USEREXIT_MOVE_FIELD_TO_VBAP.
    At the end, please ensure all program and screen are activated. Hope this will help.
    Regards
    Kiran Sure

  • How can i add field to screen exit ?

    ver 4.7
    trans.  me21n
    add field in screen exit .
    i implement screen exit MM06E005->SAPMM06E->0111
    in the layout i try to add field  by pressing
    button in the toolbar ( dictionary field window ) ,
    but when i press "save" in me21n  ,
    i get message "No data changed".
    i choose in the dialog window
    field from structure "ci_ekpodb" , field that i already
    been add  .
    thanks .

    Hi
    You have to implement the exit to import/export the data into/from screen-exit:
    EXIT_SAPMM06E_016 and EXIT_SAPMM06E_018
    Max

  • Fields not greyed out in display mode in screen exit

    Hi all,
    i am working on an screen exit for CJ02 transaction. the values in the customer subscreen are getting updated in database and even it is reflecting in fields when viewed again. the problem is that in display mode (CJ03) the fields are still editable. though there is no save button, but the fields should be greyed out.
    i have tried to modify screen using LOOP AT SCREEN in the function exit provided in PBO.....but it is not picking the subscreen.
    please provide any solution as soon as possible.
    thanks in advance

    In the PBO in your screen exit:
    IF sy-tcode EQ 'CJ03'.
    LOOP AT SCREEN .
    if screen-name 'your field'
    screen-input = 0.
    screen-output = 1.
    MODIFY SCREEN.
    ENDIF.
    endif.
    what enhancement are you using?
    bye

  • Add one column to the screen exits

    Hi All
        I am doing Screen Exits,
    here i have to add one column to the screen
    and it have to retrive the data from the specified fields
    anyone plz give me the solution.

    Hi
    which screen exit?
    Max

  • Problem in  transporting MIGO BADI screen exit?

    Hi all,
    I have implemented MB_MIGO_BADI for screen-exit of the MIGO.
    Whem transporting I am getting an error that                                                                               
    Table ZMIGO_BADI_EX_SCREEN_FIELD could not be activated                      
    (E- Routine EXPAND (Table ZMIGO_BADI_EX_SCREEN_FIELD could not be expanded) )
    Table Type ZTY_T_EXTDATA could not be activated                              
    (E- Row type ZMIGO_BADI_EX_SCREEN_FIELD is not active or does not exist ) .    
    But this row type is in the same request number and activated also ?
    I am unable to identify the reason. Please help me to solve this problem?
    Thanks,
    Vamshi

    Hi,
    Go to se80 and display the program name which you might have given in methof IF_EX_MB_MIGO_BADI~PBO_DETAIL and activate the screen which you have created,
    Thanks,
    Shailaja Ainala.

  • Screen - exits - step by step simple examples

    hi ,
    i am new to user exits.
    pls help me by giving step by step example for creating a subscreen with 2 fields , and incorporate with some standard sap transactions.
    there are many who discussed the same topic in the forum ,but i find confusing.
    *so please don't give me the links, take standard transaction and provide me step by step .
    Thank you.
    regards
    Sree

    hi,
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen u2013 where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen u2013 so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool u2013 including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton u2018SAP Applicationsu2019. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest u2013 for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number u2013 20 characters
    Location 2 u2013 15 Characters.
    Model no u2013 20 characters
    Location 2 should start with u2018Lu2019.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be u2018CUSTu2019 (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with u2018Lu2019 will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module u2018EXIT_SAPLAIST_002u2019, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module u2018EXIT_SAPLAIST_003u2019, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done u2013 otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton u2018Enhancement Assignmentsu2019 in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to u2018Componentsu2019.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field u201CLocation 2u201D, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything u2013 the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page u2018Generalu2019 of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class u20181000u2019 and click on folder u2018General Assignment of Layoutu2019.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout u2018SAPu2019 cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout u2018SAPu2019 to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder u2018Tab page titlesu2019.
    You want to put your custom fields in the tab page u201CGeneralu201D. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page u201CGeneralu201D are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with u201CUu201D padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themu2026save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.

Maybe you are looking for

  • Is there any standard report available to show cost prices from infor recor

    Hi Can any one tell help me is there any possiblility to make a report showing cost prices from info-records on purchasing org. level incl. prices scales? We need a report showing the following: Supplier no. Supplier name Material no. Material name P

  • Playlists in folders not in same order on iPod as in iTunes

    I use iTunes version 11.01 on Mac system 10.6.8. I have iPod classic 2.0.4 I have created playlist folders which contain playlists in certain order. When I synch iPod, the order within playlist folder changes as follows: Playlists names containing nu

  • "result too large" error when accessing files

    Hi, I'm attempting to make a backup copy of one of my folders (using tar from shell). For several files, I got "Read error at byte 0, reading 1224 bytes: Result too large" error message. It seems those files are unreadable. Whatever application attem

  • Strange AFP behaviour

    A sharepoint on an 18 TB xsan, reshared on an MDC failover via AFP, SMB and NFS. Mounted via SMB and NFS, all movies (qt, mpg, avi, etc) open and play on my local machine. Via AFP, the majority of these movies result in QuickTime Player returning the

  • Takes out of alignment within track

    I'm using Logic Express 8. I recorded a vocal track a couple of days ago. When I went to comp the takes today, some of the takes were no longer aligned with the piano. The ones that were off were consecutive and appear to be off by the exact same amo