Programme SAP MMXPRA06 - Adapt Material Master Field Attributes

Description
This converter program updates certain entries in the material masterfield table.
The maintenance status and field group, amongst others, are defined inthis table for each material master field. You access this table inMaterial Master Customizing by choosing Material -> Fieldselection -> Assign fields to field groups.
The converter program makes the following changes:

  • Status D (MRP) is assigned to field MARC-RGEKZ (backflush).

  • Field group 48 is assigned to field MARC-PRCTR. However, this is only
  • the case if you have not yet changed the previous standard field group89.
    In addition, the following changes are made since, owing to theconfigurability of screens in 3.0, the assignment of fields tomaintenance statuses has to be revised with regard to the maintenancestatuses suitable for a field.
    • Some MARA fields of a general character should be assigned all
    • maintenance statuses:
      Field,,Old
      ,,status
      MARA-BISMT,, K
      MARA-PRDHA,, K
      MARA-MATKL,, KELV
      MARA-NTGEW,, KLV
      MARA-SPART,, VKB
      MARA-XCHPF,, ALES
      • Many MARA fields, which did not previously have status "K", should be
      • given this status in addition since status "K" has the secondaryattribute "General data".
        Field,,Old,,New
        ,,status,,status
        MARA-STOFF,, LS,,-> KLS
        MARA-BEHVO,, L,,-> KL like MARA-TEMPB, MARA-RAUBE
        MARA-BSTME,, E,,-> KE like MARA-EKWSL, MARA-VABME
        MARA-ERGEI,, V,,-> KV like associated fields
        MARA-GEWTO,, V,,-> KV like MARA-VOLTO
        MARA-ETIAR,, L,,-> KL like MARA-ETIFO
        MARA-QMPUR,, Q,,-> KQ
        MARA-TRAGR,, V,,-> KV
        MARA-WESCH,, L,,-> KL
        • Some MARA fields, which so far only had status "K" since, for technical
        • reasons, they previously existed only on the Engineering/Design screen,should additionally be given the correct status:
          Field,,Old,,New
          ,,status,,status
          KNA1-NAME1,, K,,-> KV (Sales screens could not formerly
          MARA-KUNNR,, K,,-> KV cope with pure MARA data)
          Note: MAW1 fields should be given all maintenance statuses.
          • Some MARC fields are general plant fields and should be given all
          • maintenance statuses except K and C (pure MARA statuses):
            Field,,Old
            ,,status
            MARC-AUSME,, LSFQA
            MARC-INSMK,, EQA
            MARC-KZKRI,, EA
            MARC-MMSTA,, DEAFQ
            MARC-PRCTR,, S still missing
            MARC-SERNP,, S still missing
            MARC-XCHPF,, ALES
            MARC-XMCNG,, X, Z still missing
            • In addition, all field names assigned to a frame are deleted from the
            • material master field table since empty frames are automatically nolonger displayed (new Basis functionality) as of 3.0.
              Frame fields previously contained in the material master field table:
              MARC023008
              MARC025003
              TEXT020002
              TEXT020003
              TEXT020101
              TEXT021603
              TEXT023008
              TEXT025003
              TEXT026003
              TEXT026102
              TEXT027502
              TEXT029508
              Moreover, in the material master field table, field selection group 54is set to hidden for the entry for field reference MM03. (In thestandard system, this is already the case for MM01, MM02, MMVH, andMMVV.)

              Output
              A log with success or error messages is issued. This log may contain theerror message "Maintenance status overflow". This error message canoccur if, while making modifications, you have defined your ownmaintenance statuses in addition to those defined in the standard SAPsystem.
              It may then not be possible to fully assign the new maintenance statusessince you may specify a maximum of 15 maintenance statuses for eachfield. In this case, no data is converted for the field concerned in therespective client.
              Take a look at the current maintenance statuses of the fields concernedand, where appropriate, extend these maintenance statuses yourself. Youneed make no further response to these errors during updating.