MRP area- settings are missing in material master

Dear All,
       I am working on MRP area. As I was going through the SAP library, it was given that the some settings are need to be done in MRP 4 view for the perticular storage locations. But I am unable to find those settings in material masters, without which I can't proceed further. Kindly guide me. I am using ECC 6.0.
      Dear Rupesh Brahmankar, heartiest congratulations for achieving the milestone. Keep up the good work.
Regards
SmanS

Dear SAP Consultant,
Pls check whether MRP is activated for your material master thru Tcode OMS2.
This can be activated by selecting MRP under user departments in detail screen of material type in Tcode OMS2.
Regards,
Abhee.

Similar Messages

  • Standard  Radio Button Tabs missing in Material Master

    Dear Experets,
    We have Upgraded from 4.5 to Ecc 6.0. We are finding an issue in Material Master.
    When we create a material with the required selected Views and maintaing the datas like Basic Data and other Views, we usually have standard Radio button Tab to shift over from one View to another View. I am not able to find those Views either in Creation of Material Master, Or Change or Display ?
    Can any one suggest on this? Is there any Patch is missing or any configuration setting has to be carried out ?
    Please Suggest your valuable inputs.
    Best Regards
    Javeed
    Edited by: JAVEED AHAMED on Apr 29, 2010 10:40 AM

    Hi,
    Check sap note 107404.
    Regards
    Ankur

  • Material Group field is Missing in Material Master - Purchasing view ?

    Hai Experts,
                      I want to configure to bring back Material Group field is Missing in Material Master - Purchasing view.  It is mandatory to Create & save a master. I cant save a master in sandbox. Need Help..

    I make all field as Optional & Create master successfully.. Thanks.. I even verfied in J1ID Master for assesable value &  Chapter ID Combination.. But in Cenvat Determination Field,  How i can set Default Indicator for Modvat "tick" & how can i set Excise Intimation Date also.
    I checked Material Master in mm03 [ Display].
    I clicked More & Pre Vals. option in  Foreign Trade Import.
    For More, It shows this error.
    Record 21 MORE  does not exist in table T133E
    Message no. M3748
    For Pre vals., It shows this error.
    Record 21 J1PR  does not exist in table T133E
    Message no. M3748
    Kindly guide me..
    Thanks & Regards
    Swetha

  • Backflushing field is missing in material master MRP2

    Dear experts,
    We're are configuring the logistics system for the 1st time.
    The field "Backflushing" is not active in material master, MRP2, although in OMS9 there are no "hidden" indicators for the reference field group 74.
    Could you give any hint, which other relevant settings might be missing in our case?
    Many thanks in advance.

    problem solved.

  • Tax code missing in material master

    Hi Gurus,
    When I try to create a outbound delivery system displays message u201CMaterial not defined for sales from Indiau201D, the long text of message says that tax codes are not maintained in material master.
    But in material master sales view I am unable to maintain values (no values in possible entries option F4).
    Please advice.
    Regards,
    Prasad svs

    you have an entry there for India in your sales org data of Material master, but this entry is without tax code, correct?
    Or don't you even have a line for India there?
    In case 1) create the tax classfication in IMG > SD > basic data > taxes > tax relevance of master data
    If case 2) allocate the sales organisation to you India plant in IMg > Enterprise structure > Allocation > Sales org to plant

  • How to delete MRP view data after create in Material master data ?

    Hi all ,
          After user  create a useless MRP view data in Material master data , how to remove it ?

    Hi
    Material master once created cannot be deleted.Only thing u can do is to mark it for deletion
    Go to Logistics > Materials management > Material master > Material > Flag for deletion > Immediately.
    Give the necessary data that is needed for the view you want to delete.
    Press and flag the view you want to delete.
    Now the view is flagged for deletion. This means that it's use is limited and it will be cleaned up or really deleted at the next clean up of the system.
    regards
    Anand

  • Future standards missing from material master

    Hi All,
    I have an issue with ckr1 t/r.
    when i run ckr1 t\r in test run and in future standards cost estimate mode by giving i/ps for comany code plant and material.
    when i look into mm03 t\r, i am getting zero's in future standards.
    As per my analysis the future data might be deleted. if itz correct ( future standards data deletion)  how can i know the data was deleted and when it was deleted. if data was not deleted then what will be the reason to getting zeros in future standards.
    Thanks & Regards
    Krishna

    It's all about the table KEKO.
    these are the Key fields
    Reference Object  - don't know this field, it is always "0" when I look
    Cost Estimate Number - Product Costing  - system assigned number
    Costing Type  -  01 for product costing (18 for Sales order costing
    Costing Date (Key) 
    Costing Version
    Valuation Variant in Costing
    Costs Entered Manually in Additive or Automatic Cost Est.
    Notice that STATUS is not part of the key combination
    Status KA = costed without error
    Status VO = marked without error - this will show in the Future Cost estimate fileld of Costing 2
    Status FR = released without error and is is the current cost estimate filed of Costing 2 - it is also the standard price
    If a cost estimate for material 1234 is created (CK11n) with no errors for:
    Nov 1 2010
    version 1
    valuation variant Z01
    and saved KEKO shows the status KA for this key combination (serveral more tables are involved that hold the values, but KEKO is the key)
    When this cost estimate MARKED without error to be the NEXT standard cost (CK24) the status in KEKO becomes VO
    and you will see it as the FUTURE cost estimate on Costing 2 (This VO status is in KEKO until released or overwritten  or deleted)
    When this material cost is RELEASED on Nov 1 (without error) the status in KEKO becomes FR and you see is as the Current Cost estimate in Costing 2.
    NOW  IF SOMEONE creates a new cost estiomate on OCT 31 2010 (CK11n) for :
    Material:  1234
    Nov 1 2010
    version 1
    valuation variant Z01
    (notice this is the same key as before)
    AND SAVES it, KEKO will overwrite the VO Status date and save the new KA status data.
    The VO status and its information is now gone.
    Depending on the precise sequence of steps and timing - the value may or may not be visible in Costing 2,  But in the KEKO table and the tables that hold the values, the VO status record no longer exists.
    If the new cost estimate created and saved was meant to be the new standard, it should be MARKED so it can be in Costing 2 and so it can be released.
    If the new cost estimate was an effort to see the Nov 1 cost (I know people who use CK11n to create a cost rather than use CK13n to display a saved cost) and it is "accidently"saved - this is an issue. 
    I do a great deal of CK11n work, but my work is never meant to be released as inventory values.  Therefor I use different versions ( version 50, 51 52 etc) and that makes a different key combination and a new record is created in KEKO, and the VO record still exists.
    I hope that I have answered your question.
    Althea

  • Plant specific fields in the material master for product move

    Hi, SAP gurus,
    My scenario is we are moving a existing product in US plant to Brazil plant. What are the fields in the material master that are specific to a plant that will change. For ex MRP controller will change from plant to plant. Like that can anybody please provide me a list of fields that i need to be looking at?
    Thank you
    Anusha

    Hi Anusha,
    First of all, list down all your materials those you want to extend to new plant.
    a) Secondly, pay attention to those fields you will find "filled" in those materials at plant level.
    b) MARC comes handy for you to analyse which fields are at plant level.
    Intersection of fields with values between a and b are the ones you need to work out.
    Good luck,
    Regards

  • During LTP material master values need to be modified

    Hi ,
    We are implementing LTP process in company. while  LTP Run it pick the MRP1234 values for Simulative order creation. We have requirement to change the MRP1234 only during LTP run. Were as the MRP run will run with normal material master(MRP1234) values.
    The values need to be changed are during LTP run are MRP group , Lox size etc., '''

    Thank you.. Almedia and köller..
      We are already using this badi  MD_MRP_PARAMETERS. We are facing the following problem
    For example
    header               ATEST
    component            BCOMP
    We need to switch off the bulk indicator and phantom for the component.
    We  are using the above bapi its manipulation only the header (ATEST) material master data but in LTP run during creation of header simulative planned. Component simulative dep requirement values are copied from material master. In this above bapi we are manipulating only header values.
    When the next loop during component simulative planned order generation time the above parameters(bulk and phantom) are copied from component simulative dep requirement. Hence the switching of bulk indicator and phantom assembly is not working during ltp using this badi. This problem is happening for multi level components too.
    Is there any suggestion for this issue..

  • Material master tables

    Hi,
    how can I understand what views are opened for materials using material master tables ?
    Regards

    Go to the MARA table - Execute with the material you want to see.
    Check the maintenance status field (PSTAT) and that will show the views created for that material.
    Work scheduling     A
    Accounting             B
    Classification          C
    MRP                        D
    Purchasing                E
    Production resources/tools F
    Costing                     G
    Basic data                K
    Storage                     L
    Forecasting                P
    Quality management   Q
    Warehouse management S
    Sales                            V
    Plant stocks                     X
    Storage location stocks Z

  • Material master -sales text / purchase order text

    Dear MM experts,
    we are maintaining materials sales text & purchase order text while creating material master.
    sales text is required for our customers quotations & purchase order text is required for our Vendors Purchase orders.
    I have an issue, where sales text in material master is limited to 6.5 inch length, but need 7.5 inch length, where I can set this page length. Also i wanted to have same font characteristics to be changed from exiting font size and font style to required, how to do this?
    pl help &  how the above can be changed from default settings to flexible settings with regard to material master.
    thanks  in advance
    regards
    Srihari

    from http://help.sap.com/saphelp_erp2005/helpdata/en/f4/b49e8c453611d189710000e8322d00/content.htm
    Text Entry Area 
    Type your text into the text entry lines. You can type continuously: SAPscript fills your text using a line length of 72 characters as soon as you choose ENTER or a function.
    To enter text in the line editor continuously, the checkbox Automatic tab at field end must be marked. For more information on setting automatic tabbing, see Setting Automatic Tabbing and Entering Text.
    Note that the line editoru2019s text filling has no influence on the final appearance of the text. Your text is formatted no earlier than at the time it is displayed or printed. For more information, see Previewing and Printing SAPscript Documents.

  • Archiving material master

    Hello Friends,
    I have put deletion flag for material by MM06 & tried to execute SARA transaction, however While doing archving, iam getting the following errors in the SM37 job log after write step, please let me know how to resolve th same:
    1. MARC:  production order exists
    2. MARC:  use in product group exists
    3. MBEW:  plant is assigned to the valuation area
    4. MARA:  Dependent material master data still exists
    5.50026991526002R ROLLBACK carried out
    6.MARD:  error deleting table MARD
    Thanks,
    Kumar

    Hi Kumar,
    If a purchase order, Open production order or any other Dependency exists for the material, Material master record cannot be archived and deleted at a given organizational level, the reason will be given in the log the log also contains technical data. check all dependencies for the materials and up on clearing them  flag the materials for deletion first and then Archive them.
    Ref the links:
    http://www.sap-img.com/bc003.htm
    http://help.sap.com/saphelp_46c/helpdata/en/ff/515e5449d811d182b80000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_46c/helpdata/en/8d/3e59bc462a11d189000000e8323d3a/frameset.htm
    Pavan

  • Creation of a Material Master

    Hi guys,
        Can any one help me in creating a Material master
        pls do send me the steps that are involved in
        creating a Material master
    Thanku
    Jino

    Check the BAPI BAPI_MATERIAL_SAVEDATA
    Check the below sample code.
    REPORT YGECICI MESSAGE-ID 00
    No Standard Page Heading
    Line-Size 200
    Line-Count 65.
    *TO CREATE MATERIAL USING BAPI.
    STRUCTURE DECLARATIONS *
    TABLES: BAPIMATHEAD, “Headerdata
    BAPI_MARA, “Clientdata
    BAPI_MARAX, “Clientdatax
    BAPI_MARC, “Plantdata
    BAPI_MARCX, “Plantdatax
    BAPI_MAKT, “Material description
    BAPI_MBEW, “VALUATION DATA
    BAPI_MBEWX,
    BAPI_MARM,
    BAPI_MARMX,
    bapi_mean,
    BAPIRET2. “Return messages
    DATA:V_FILE TYPE STRING. “input data file
    DATA:
    BEGIN OF LSMW_MATERIAL_MASTER,
    MATNR(018) TYPE C, “Material number
    MTART(004) TYPE C, “Material type
    MBRSH(001) TYPE C, “Industry sector
    WERKS(004) TYPE C, “Plant
    MAKTX(040) TYPE C, “Material description
    DISMM(002) TYPE C, “Extra Field Added In the Program as itsrequired
    MEINS(003) TYPE C, “Base unit of measure
    MATKL(009) TYPE C, “Material group
    SPART(002) TYPE C, “Division
    LABOR(003) TYPE C, “Lab/office
    PRDHA(018) TYPE C, “Product hierarchy
    MSTAE(002) TYPE C, “X-plant matl status
    MTPOS_MARA(004) TYPE C, “Gen item cat group
    BRGEW(017) TYPE C, “Gross weight
    GEWEI(003) TYPE C, “Weight unit
    NTGEW(017) TYPE C, “Net weight
    GROES(032) TYPE C, “Size/Dimensions
    MAGRV(004) TYPE C, “Matl grp pack matls
    BISMT(018) TYPE C, “Old material number
    WRKST(048) TYPE C, “Basic material
    PROFL(003) TYPE C, “DG indicator profile
    KZUMW(001) TYPE C, “Environmentally rlvt
    BSTME(003) TYPE C, “Order unit
    VABME(001) TYPE C,
    EKGRP(003) TYPE C, “Purchasing group
    XCHPF(001) TYPE C, “Batch management
    EKWSL(004) TYPE C, “Purchasing key value
    WEBAZ(003) TYPE C, “GR processing time
    MFRPN(040) TYPE C, “Manufacturer part number
    MFRNR(010) TYPE C, “Manufacturer number
    VPRSV(001) TYPE C, “Price control indicator
    STPRS(015) TYPE C, “Standard price
    BWPRH(014) TYPE C, “Commercial price1
    BKLAS(004) TYPE C, “Valuation class
    bwkey(004) type c,
    END OF LSMW_MATERIAL_MASTER.
    INTERNAL TABLE DECLARATIONS *
    *to store the input data
    DATA:
    BEGIN OF it_matmaster OCCURS 0.
    INCLUDE STRUCTURE LSMW_MATERIAL_MASTER.
    DATA:
    END OF it_matmaster.
    *for material description
    DATA:BEGIN OF IT_MATERIALDESC OCCURS 0.
    INCLUDE STRUCTURE BAPI_MAKT .
    DATA:END OF IT_MATERIALDESC.
    *FOR gross wt
    data: begin of it_uom occurs 0.
    include structure BAPI_MARM.
    data:end of it_uom.
    DATA: BEGIN OF IT_UOMX OCCURS 0.
    INCLUDE STRUCTURE BAPI_MARMX.
    DATA:END OF IT_UOMX.
    data:begin of it_mean occurs 0.
    include structure bapi_mean.
    data:end of it_mean.
    DATA:BEGIN OF IT_MLTX OCCURS 0.
    INCLUDE STRUCTURE BAPI_MLTX.
    DATA:END OF IT_MLTX.
    *to return messages
    DATA:BEGIN OF IT_RETURN OCCURS 0.
    INCLUDE STRUCTURE BAPIRET2.
    DATA:END OF IT_RETURN.
    SELECTION SCREEN *
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-002.
    PARAMETERS:P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK B1 .
    AT SELECTION SCREEN *
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
    CALL FUNCTION ‘F4_FILENAME’
    EXPORTING
    PROGRAM_NAME = SYST-CPROG
    DYNPRO_NUMBER = SYST-DYNNR
    FIELD_NAME = ‘P_FILE’
    IMPORTING
    FILE_NAME = P_FILE.
    TO UPLOAD THE DATA *
    START-OF-SELECTION.
    V_FILE = P_FILE.
    CALL FUNCTION ‘GUI_UPLOAD’
    EXPORTING
    filename = V_FILE
    FILETYPE = ‘ASC’
    HAS_FIELD_SEPARATOR = ‘X’
    HEADER_LENGTH = 0
    READ_BY_LINE = ‘X’
    DAT_MODE = ‘ ‘
    IMPORTING
    FILELENGTH =
    HEADER =
    tables
    data_tab = IT_MATMASTER
    EXCEPTIONS
    FILE_OPEN_ERROR = 1
    FILE_READ_ERROR = 2
    NO_BATCH = 3
    GUI_REFUSE_FILETRANSFER = 4
    INVALID_TYPE = 5
    NO_AUTHORITY = 6
    UNKNOWN_ERROR = 7
    BAD_DATA_FORMAT = 8
    HEADER_NOT_ALLOWED = 9
    SEPARATOR_NOT_ALLOWED = 10
    HEADER_TOO_LONG = 11
    UNKNOWN_DP_ERROR = 12
    ACCESS_DENIED = 13
    DP_OUT_OF_MEMORY = 14
    DISK_FULL = 15
    DP_TIMEOUT = 16
    OTHERS = 17
    IF sy-subrc 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    *ELSE.
    *DELETE IT_MATMASTER INDEX 1.
    ENDIF.
    DATA POPULATIONS *
    LOOP AT IT_MATMASTER.
    *HEADER DATA
    BAPIMATHEAD-MATERIAL = IT_MATMASTER-MATNR.
    BAPIMATHEAD-IND_SECTOR = IT_MATMASTER-Mbrsh.
    BAPIMATHEAD-MATL_TYPE = IT_MATMASTER-Mtart.
    BAPIMATHEAD-BASIC_VIEW = ‘X’.
    BAPIMATHEAD-PURCHASE_VIEW = ‘X’.
    BAPIMATHEAD-ACCOUNT_VIEW = ‘X’.
    *CLIENTDATA
    BAPI_MARA-MATL_GROUP = IT_MATMASTER-MATKL.
    BAPI_MARA-DIVISION = IT_MATMASTER-SPART.
    BAPI_MARA-DSN_OFFICE = IT_MATMASTER-LABOR.
    BAPI_MARA-PROD_HIER = IT_MATMASTER-PRDHA.
    BAPI_MARA-PUR_STATUS = IT_MATMASTER-MSTAE.
    BAPI_MARA-ITEM_CAT = IT_MATMASTER-MTPOS_MARA.
    BAPI_MARA-NET_WEIGHT = IT_MATMASTER-NTGEW.
    BAPI_MARA-PO_UNIT = ‘KG’.
    BAPI_MARA-UNIT_OF_WT_ISO = ‘KG’.
    BAPI_MARA-UNIT_OF_WT = ‘KG’.
    BAPI_MARA-PACK_VO_UN = ‘KG’.
    BAPI_MARA-BASE_UOM_ISO = ‘KG’.
    bapi_mara-size_dim = it_matmaster-groes.
    BAPI_MARA-MAT_GRP_SM = IT_MATMASTER-MAGRV.
    BAPI_MARA-OLD_MAT_NO = IT_MATMASTER-BISMT.
    BAPI_MARA-BASE_UOM = IT_MATMASTER-MEINS.
    BAPI_MARA-BASIC_MATL = IT_MATMASTER-WRKST.
    BAPI_MARA-HAZMATPROF = IT_MATMASTER-PROFL.
    BAPI_MARA-ENVT_RLVT = IT_MATMASTER-KZUMW.
    BAPI_MARA-PO_UNIT = IT_MATMASTER-BSTME.
    BAPI_MARA-VAR_ORD_UN = IT_MATMASTER-VABME.
    BAPI_MARA-PUR_VALKEY = IT_MATMASTER-EKWSL.
    BAPI_MARA-MANU_MAT = IT_MATMASTER-MFRPN.
    BAPI_MARA-MFR_NO = IT_MATMASTER-MFRNR.
    BAPI_MARAX-MATL_GROUP = ‘X’.
    BAPI_MARAX-DIVISION = ‘X’.
    BAPI_MARAX-DSN_OFFICE = ‘X’.
    BAPI_MARAX-PROD_HIER = ‘X’.
    BAPI_MARAX-PUR_STATUS = ‘X’.
    BAPI_MARAX-ITEM_CAT = ‘X’.
    BAPI_MARAX-NET_WEIGHT = ‘X’.
    BAPI_MARAX-UNIT_OF_WT = ‘X’.
    BAPI_MARAX-UNIT_OF_WT_ISO = ‘X’.
    bapi_maraX-size_dim = ‘X’.
    BAPI_MARAX-MAT_GRP_SM = ‘X’.
    BAPI_MARAX-OLD_MAT_NO = ‘X’.
    BAPI_MARAX-BASE_UOM = ‘X’.
    BAPI_MARAX-BASE_UOM_ISO = ‘X’.
    BAPI_MARAX-BASIC_MATL = ‘X’.
    BAPI_MARAX-MFR_NO = ‘X’.
    BAPI_MARAX-HAZMATPROF = ‘X’.
    BAPI_MARAX-ENVT_RLVT = ‘X’.
    BAPI_MARAX-PO_UNIT = ‘X’.
    BAPI_MARAX-PACK_VO_UN = ‘X’.
    BAPI_MARAX-VAR_ORD_UN = ‘X’.
    BAPI_MARAX-PUR_VALKEY = ‘X’.
    BAPI_MARAX-MANU_MAT = ‘X’.
    BAPI_MARAX-MFR_NO = ‘X’.
    *PLANT DATA
    BAPI_MARC-PLANT = IT_MATMASTER-WERKS.
    BAPI_MARC-PUR_GROUP = IT_MATMASTER-EKGRP.
    BAPI_MARC-BATCH_MGMT = IT_MATMASTER-XCHPF.
    BAPI_MARC-GR_PR_TIME = IT_MATMASTER-WEBAZ.
    BAPI_MARCX-PLANT = IT_MATMASTER-WERKS.
    BAPI_MARCX-PUR_GROUP = ‘X’.
    BAPI_MARCX-BATCH_MGMT = ‘X’.
    BAPI_MARCX-GR_PR_TIME = ‘X’.
    *VALUATION DATA
    BAPI_MBEW-PRICE_CTRL = IT_MATMASTER-VPRSV.
    BAPI_MBEW-STD_PRICE = IT_MATMASTER-STPRS.
    BAPI_MBEW-COMMPRICE1 = IT_MATMASTER-BWPRH.
    BAPI_MBEW-VAL_AREA = IT_MATMASTER-BWKEY.
    BAPI_MBEW-VAL_CLASS = IT_MATMASTER-BKLAS.
    BAPI_MBEWX-PRICE_CTRL = ‘X’.
    BAPI_MBEWX-STD_PRICE = ‘X’.
    BAPI_MBEWX-COMMPRICE1 = ‘X’.
    BAPI_MBEWX-VAL_AREA = IT_MATMASTER-BWKEY.
    BAPI_MBEWX-VAL_CLASS = ‘X’.
    IT_MATERIALDESC-LANGU = ‘EN’.
    IT_MATERIALDESC-MATL_DESC = IT_MATMASTER-MAKTX.
    append IT_materialdesc.
    IT_UOM-GROSS_WT = IT_MATMASTER-BRGEW.
    IT_UOM-ALT_UNIT = ‘KG’.
    IT_UOM-ALT_UNIT_ISO = ‘KG’.
    IT_UOM-UNIT_OF_WT = IT_MATMASTER-GEWEI.
    APPEND IT_UOM.
    IT_UOMX-GROSS_WT = ‘X’.
    IT_UOMX-ALT_UNIT = ‘KG’.
    IT_UOMX-ALT_UNIT_ISO = ‘KG’.
    IT_UOMX-UNIT_OF_WT = ‘X’.
    APPEND IT_UOMX.
    it_mean-unit = ‘KD3′.
    append it_mean.
    it_mltx-langu = ‘E’.
    it_mltx-text_name = it_matmaster-matnr.
    APPEND IT_MLTX.
    CALL FUNCTION ‘BAPI_MATERIAL_SAVEDATA’
    EXPORTING
    headdata = BAPIMATHEAD
    CLIENTDATA = BAPI_MARA
    CLIENTDATAX = BAPI_MARAx
    PLANTDATA = BAPI_MARc
    PLANTDATAX = BAPI_MARcx
    FORECASTPARAMETERS =
    FORECASTPARAMETERSX =
    PLANNINGDATA =
    PLANNINGDATAX =
    STORAGELOCATIONDATA =
    STORAGELOCATIONDATAX =
    VALUATIONDATA = BAPI_MBEW
    VALUATIONDATAX = BAPI_MBEWX
    WAREHOUSENUMBERDATA =
    WAREHOUSENUMBERDATAX =
    SALESDATA =
    SALESDATAX =
    STORAGETYPEDATA =
    STORAGETYPEDATAX =
    FLAG_ONLINE = ‘ ‘
    FLAG_CAD_CALL = ‘ ‘
    IMPORTING
    RETURN = IT_RETURN
    TABLES
    MATERIALDESCRIPTION = IT_MATERIALDESC
    UNITSOFMEASURE = IT_UOM
    UNITSOFMEASUREX = IT_UOMX
    INTERNATIONALARTNOS = it_mean
    MATERIALLONGTEXT = IT_MLTX
    TAXCLASSIFICATIONS =
    RETURNMESSAGES =
    PRTDATA =
    PRTDATAX =
    EXTENSIONIN =
    EXTENSIONINX =
    read table it_return with key TYPE = ‘S’.
    if sy-subrc = 0.
    CALL FUNCTION ‘BAPI_TRANSACTION_COMMIT’
    EXPORTING
    WAIT =
    IMPORTING
    RETURN =
    *else.
    *CALL FUNCTION ‘BAPI_TRANSACTION_ROLLBACK’
    IMPORTING
    RETURN =
    endif.
    WRITE:/ IT_RETURN-TYPE,
    2 IT_RETURN-ID,
    22 IT_RETURN-NUMBER,
    25 IT_RETURN-MESSAGE.
    IT_RETURN-LOG_NO,
    IT_RETURN-LOG_MSG_NO,
    IT_RETURN-MESSAGE_V1,
    IT_RETURN-MESSAGE_V2,
    IT_RETURN-MESSAGE_V3,
    IT_RETURN-MESSAGE_V4,
    IT_RETURN-PARAMETER,
    IT_RETURN-ROW,
    IT_RETURN-FIELD,
    IT_RETURN-SYSTEM.
    ENDLOOP.
    Reward points..

  • Material Master - Error M3 826 Maintenance status of field ... to screen

    Hi Experts of the Material Master,
    I am getting the error M3 826 "Maintenance status of field MARA-BEHVO does not correspond to status of screen K" when all screens are selected in the Create Material Master transaction.
    Here is my situation: I have added the fields MARA-BEHVO and MARA-TEMPB both of status L (Storage) to a screen called "Phys. Characteristics", which has status K (Basic data).
    This produces  the error message above in standard SAP. I didn't want to change the customizing of the screen to allow L, because this screen is also used by other material types.
    I had to copy the screen MGD1 2701 (Phys. Characteristics) to my custom program for Material Master screens anyhow, as the number of fields and their descriptions had to be adjusted.
    The program was created using the activity "Create Program for User Subscreens" in SPRO.
    in the coding of ZMGD1 screen 2701 I have added this code behind the standard module FELDAUSWAHL to manipulate the standard logic that would blend out L fields on a K screen.
    LOOP AT SCREEN.
    *   Material Type
        IF mara-mtart = 'ZPNT'.
    *     Screen-Names of the 3 fields
          IF screen-name = 'MARA-TEMPB' OR
             screen-name = 'MARA-BEHVO'.
            screen-active      = 1.
            screen-invisible   = 0.
            screen-output      = 1.
    *       Change or Create transaction
            IF sy-tcode = 'JP27' OR sy-tcode = 'JP28'.
              screen-input       = 1.
              screen-required    = 1.
            ENDIF. "transaction code JP27 or JP28
            MODIFY SCREEN.
          ENDIF. "screen-name
        ENDIF. "Material Type ZPNT
      ENDLOOP.
    It all works fine when only a number of screens (but including the modified) screens are selected for creation.
    But it fails with the message above on the modified screen when all screens are selected.
    Any ideas?
    Ralf

    from the message, it appears that ZZKUNNR is a custom field attached to your MARA table. So, it is your System specific.  I don't see ZZKUNNR available in MARA.  If you look at the transaction code OMT3B (configuration for material master data screens), you can find K - Basic Data Screen in Maintenance Status field.
    You may look in this area to fix your issue. Because yours is a custom field, its tough to analyse further.
    Reward points, if it helps!
    Regards

  • Object ID for PO long text for BDC of material master

    Hi all,
    we are working on BDC of material master:
       I have given some technical specifications in the P O text view of Material Master, i want to assign an object id for this long text , how to assign an object id for the long text?
    regards,
    urendra

    Hi
       thanku for quick response,,,  i had checked the textid,
       my problem was resolved, i have awarded some points
    thank u
    regards,
    urendra

Maybe you are looking for