Ansicht
Dokumentation

RMLFMH00 - Supplier Hierarchy

Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.

Use

This report lets you display or maintain vendor hierarchies during list processing. You can call up the report as follows:

• Directly

• With the display transaction MKH2

• With the maintenance transaction MKH1

A vendor hierarchy consists of hierarchy nodes that are assigned to each other. A node consists of a combination of vendor and purchasing organization. Each assignment has a validity period.

The assignment of a lower-level node to a higher-level node must always be unique. This means that you cannot assign a node to more than one node at a time. Therefore you cannot build network structures.

Vendor hierarchy data is saved exclusively in the table LFMH. Attributes (also referred to as relevancy indicators) for a hierarchy node exist in the vendor master data in the table LFM1. These relevancy indicators are:

• Relevancy to price determination indicator

• Relevancy to subsequent settlement indicator

During assignment maintenance, the relevancy indicators are transferred from table LFM1 and stored redundantly in table LFMH (performance). If the attributes for a node in the vendor master data change, you can update the attributes before or during hierarchy maintenance. You cannot maintain the attributes directly in hierarchy maintenance.

On the selection screen, you enter the vendor hierarchy category and a validity date. The hierarchy category confirms the intended purpose for a vendor hierarchy. Hierarchies with different categories are not related. Although an assignment in a hierarchy with a certain category is unique to that category, it can occur in a hierarchy with another category. The current day's date is displayed as the default validity date for selection. All assignments are selected that are valid on the day. If you choose a date from the past as validity date, the assignments that were valid on that day are selected for display only and cannot be changed.

You can choose to have hierarchy nodes or assignments displayed with vendors' names or with validity periods. To achieve a better overview, you can restrict the display to the first three levels.

During assignment maintenance you can:

• Change the validity period

• Change the existing assignment (Choose Assignment details)

• Create a new assignment

• Choose one of the following to process nodes or sub-trees:

• Cut

• Assign to higher-level node

• Assign to lower-level node

• Reassign

• Delete

• Display or maintain vendor master data

Here you can change the vendor master data for a hierarchy node

Prerequisites

In Customizing for Purchasing (MM), you maintain settings in the following activities:

• Vendor Hierarchy

• Define hierarchy categories

• Define partner determination and hierarchy partner functions

• Assign account groups

• Assign purchasing organizations

• Assign one hierarchy category relevant for price determination for each order document type

• Partner Determination

• Define the use of hierarchy partner functions in partner schemas for purchasing documents

If you maintain the settings consistently and the hierarchy is built, the system checks during ordering whether the vendor occurs in the price determination hierarchy defined for the current order document type. If it does, then the path for all the vendor's higher-level nodes together with all the relevancy indicators is transferred to the order. Individual nodes with their hierarchy partner functions (starting from the initial partner function of the hierarchy category) are stored as partners in the order. This path is displayed on the Partner screen of the order. You must define enough hierarchy partner functions for all higher-level nodes to be transferred.

These hierarchy partner functions are intended exclusively for transfer to an order. Because these functions are not used in the vendor master, do not include them in the partner schemas for vendor master data. From this transferred hierarchy nodes path, the first node is determined for which the relevance indicator is set. If hierarchy conditions exist for these nodes, they are taken into account during price determination or subsequent settlement.

Features

Activities

Example

CPI1466 during Backup   General Material Data  
This documentation is copyright by SAP AG.

Length: 5904 Date: 20240520 Time: 051225     sap01-206 ( 105 ms )