MVIEW:MMS – Material View Values

The values can be read directly from the data base or the current, eventually changed values, depending on the option „use changed data".

General information

The data with the handler MVIEW:MMS is generally maintained using the standard function module MATERIAL_MAINTAIN_DARK, for exceptions see the following sections. For more information, see the corresponding function module documentation.

MRP profile (MARC-DISPR / MDMA-DISPR)

• If a new MRP profile is assigned to a plant view or an MRP area, the values from the profile are merged into the data.

• Values that have the selection Only default value in the MRP profile are only used if this value has not yet been set and is not set by another record from the ProMaterialData Definitions within the same grouping.

• Values that have NOT been marked as Default value only in the MRP profile are always used. They overwrite a record from the ProMaterialData Definitions in the same group.

Notes for material short texts (MAKT)

• For filters, only the fields MAKTX (entered material short text) and MAKTG (material short text in capital letters) are supported.

• Only SPRAS and MAKTX can be set as dependent values.

• When reading, the language must be specified in filter field 3. If the value * is entered as language, the logon language of the respective executing user is used.

• When writing (setting the dependent values), the language and text must be specified as a pair for the same grouping, as for other tables.

• If only missing languages are to be set with an initial value (for example, a mark that the text is missing, which can then be searched for), you can use a filter in the activation to check whether the corresponding language is empty.

Notes for inspection type-material-dependent parameters (QMAT)

• When reading, the test type must be specified in filter field 3.

• When writing (setting the dependent values), the plant and the inspection type must be specified as a pair for the same grouping as in other tables.

• This data is maintained using the SAP BAPI interface QAALE_DISTRIBUTE_QMAT_POST. For more information, see the corresponding function module documentation.

• The standard values are preset from the corresponding Customizing table (TQ34).

Hints for MRP areas (MDMA)

• MRP areas are available if activated on the system.

• The plant for the MDMA area must always be specified.

• MRP profiles are supported (see above)

• Forecast profiles are supported, but must contain all mandatory fields for the forecast data. If no forecast profile is specified, no forecast data is created.

• MRP areas can only be written, MDMA cannot be used as a filter.

Hints for long texts (LTX1)

Long texts can only be written, LTX1 cannot be used as a filter. Long texts are written either line by line or as complete texts.

Single lines:

There must always be exactly one HEAD record for each long text.

• In this record, the long text type, necessary key fields and optionally whether the text is to be added to an existing text must be entered.

• A search help is available for LTX1 / HEAD in the "Set value" field.

• For the plant note (NOTE), either the plant or the Special Values <MM> must be specified. Note that NOTE can only be written together with other plant data (restriction SAP).

• For the sales text (VERT), the sales organization and distribution channel or the Special Values <MM> must be specified. Note that VERT can only be written together with other sales data (restriction SAP).

• The APPEND control is ignored if the "Only if Initial" option is selected.

• The values to be set cannot be maintained language-dependently. Different value groups must be used for several languages.

One LINE record must be entered for each text line.

• The text lines are entered in "Set value".

  • You can specify any number of lines, but you must assign all lines and the HEAD record to the same grouping.

  • The run number determines the sequence of the text lines.

  • An optional SAP text format can be specified in target field 3. Without the standard format * is used.

  • Special Values can be used in the text.

Example:

Open

Complete texts:

• Complete texts are always read from a source. Currently supported is REFMAT and MATNR.

  • REFMAT reads the textes from a defined reference material. See <REFMAT(...)> and <REFMAT>.

  • MATNR reads the textes from a existing plant view (NOTE) or sales view (VERT) from the material currently processed.

  • For each line with target field 1 = LTX1 and target field 2 = TEXT, the complete text is copied according to the "Set value".

  • A search help is available for record LTX1 / TEXT in the "Set value" field.

  • "Set value" is divided into two parts, separated by ;

    • Part One - target

      • Defines which text of the material master is to be written.

      • Uses the same syntax as described in "HEAD" (see above).

      • APPEND is not supported here.

      • For the language and the organization keys * can also be used, see below.

    • Part Two - source

      • As noted above, only REFMAT and MATNR is supported as source:

        • After the key REFMAT, you can optionally specify the organizational keys for reading separated with /.

        • After the key MATNR, the organization keys for reading separated with / are required. Exception see below.

        • The language used to read the long text from the reference material is always used according to the target definition.

        • The following applies to REFMAT:

          • If * is specified in the target for the organizational key, * is also used for the source, see below.

        • If you do not specify an organizational key:

          • For REFMAT, the organizational keys currently stored for the reference material are used. See REFMAT:MMS – Access to data of a reference material.

          • For MATNR, when creating a new view using transaction MM01, the keys specified under “Copy from” when entering the organization levels are used. Without such keys, no text to copy can be determined.

          • For any other usage of MATNR (create view by MMS, MMS Widget, API) the source views (plant key / sales organization and distribution channel) must be specified.

  • Use of * in language or organizational key

    • If you use * in the language or in the organizational key, all existing texts are read and written.

    • If the value * is used in the target, * is always also used in the reference material.

    • It is only * supported and no partial masks.

    • If no text is found for the parameters in the source, no (empty) text is created in the target.

Example for REFMAT

Open

• Sequence number 1: The basic data text is copied from the reference material to the target in all existing languages.

• Sequence number 2: The plant note in the user language is copied from stored plant of reference material to plant 0001 of the target material .

• Sequence number 3: All existing sales texts in all existing languages are copied.

Example for MATNR

The material memo in all languages is copied from the current material from plant 0001 to the target plant to be maintained.