Using Object Dependencies with Reference Characteristics

Objective

After completing this lesson, you will be able to use Object Dependencies with Reference Characteristics in the High Level Configuration.

Object Dependencies with Reference Characteristics

In the object dependency, you can process any information from the current sales order. Therefore, you need the corresponding reference characteristics.

This figure shows you an example of object dependencies with Reference Characteristics. A Sales Order is created and a customer entered. Whenever a special customer is entered another characteristic value in characteristic evaluation is set. In detail a Read Information from the Sales Order is used.

For constraints, the reference characteristics must be included in the variant class (characteristic with interface display without display).

Name of the table field using:

→ F1 Help

→ Technical Info

This figure shows a write information. In this case the value of the field weight (structure VCSD_UPDATE) is calculated depending on customers request.

You can also use individual fields of the sales order item directly using object dependencies. These are:

  • Gross and Net Weight + Unit

  • Volume + Unit

  • Cumulated order quantity + sales unit

  • Numerator + Denominator for Conversion from Sales Unit to SKU

  • Target Quantity + Target Unit of Measure

  • Numerator + Denominator for Conversion of ToU to SKU

  • Short Text

With:

  • SKU (stockkeeping unit)

  • ToU (target unit of measure)

You require reference characteristics with reference to the structure VCSD_UPDATE.

For constraints, the reference characteristics must also be included in the variant class (characteristic with interface display without display).

Name of the table field using:

  • F1 Help
  • Technical Info

This figure shows tables for Reference Characteristics with Write Access: SDCOM, MMCOM, VCSD_UPDATE, STOP, PLPO, PLFH, PLFL, ESLL, SCREEN_DEP.

In table SDCOM, in the VKOND field, you maintain variant conditions that are used to determine surcharges and discounts during characteristic value assignment. This is done by referring to these fields in object dependencies using reference characteristics or by creating the link in characteristic maintenance.

In purchasing, the field VKOND of the table MMCOM is used for the maintenance of variant conditions.

Not all fields can be changed in table PLPO. Structure PLPO_CFMOD defines which fields these are. In the same way as table PLPO, you can work with table ESSL in sample service specifications.

This figure shows tables for Reference Characteristics with Read Access only: VBAK, VBAP, VBKD, MAEPV, MAAPV, VEDA, (VBPA_AG, VBADR_AG), (VBPA_WE, VBADR_WE), (VBPA_RE, VBADR_RE), (VBPA_RG, VBADR_RG), MARA, MARC and MAKT.

You can refer to the sales order tables listed in the graphic in reference characteristics. However, you can only have read-only access to these table fields in object dependencies. The field values can't be changed using object dependencies. Other tables of the sales order that you can also access in read mode are the address data of the contract partners in VBADR_AG, VBADR_WE, VBADR_RE, and VBADR_RG.

With:

STPOB = Document table

STPO MDSP = View of BOM items and material master for BPLA

POSVID = iPPE – Variant

PAMODD = Duration of an activity-resource relationship

In the configuration of material variants, you can access the material master tables MARA, MARC, and MAKT in read mode.

SCREEN_DEP

You can override settings in the Characteristic definition via structure SCREEN_DEP.

This figure explains the possibility to Override Settings in Characteristic Definition via Structure SCREEN_DEP. The following options are available: Hide characteristic / Characteristic ready for input, manual value assignment possible / Characteristics only in display, no manual value assignment / Reset dynamically Set Parameters.

The next figure shows you an example: SCREEN_DEP-NO_INPUT.

This figure shows how to override settings in Characteristic Definition via Structure SCREEN_DEP. SCREEN_DEP-NO_INPUT could be an example.

How to Use Object Dependencies with Reference Characteristics in the High-Level Configuration

The weight of the lifting structure T-FCLB## in the sales document must be adjusted depending on the configuration with regard to mass height and fork length.

To do this, you must first check the existence of the required object characteristics. These reference characteristics must be assigned to the VC model in a suitable form.

A corresponding procedure must be created and tested.

Log in to track your progress & complete quizzes