Versions Compared

Version Old Version 9 New Version Current
Changes made by

Christian Gradolf

Christian Gradolf

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Value Handler

Filter-/
Target Field 1

Filter-/
Target Field 2

Filter field 3

MVIEW:MMS

Table

Field

On following tables only used for reading access (filter):

  • MAKT: Filter field 3 = language acc. to SAP format (single-digit). See also below.

  • QMAT: Filter field 3 = Inspection type for which the value shall be read.


CLAS

Characteristic name

[class type, default = 001][/class name]
Both values are optional. The class name is only required, if characteristic values are locally defined for a class and the external value should be read.

Info

If the class name contains one of the special characters # or /, then this character must be used together with the escape character #. Example:

Class name: RED/BLUE
To be entered in MMS Customizing as: RED#/BLUE

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

...

  • 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.

...

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 value 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 value 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.

...

  • 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 valuesValues can be used in the text.

Example:

...

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

    • REFMAT reads the textes from a defined reference material. See also <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 materialREFMAT: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.

...