Ansicht
Dokumentation

RV_VENDOR_HIERARCHY - Edit Vendor Hierarchy

ROGBILLS - Synchronize billing plans   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Purpose

You can use this report to display and edit vendor hierarchies.

A vendor hierarchy consists of various hierarchy node assignments. A node consists of a combination of the Vendor and Purchasing Organization fields. Each assignment has a validity period.

The assignment of a lower-level node to a higher-level node must always be unique. A node cannot therefore be assigned to several nodes within a period. You cannot therefore create any network structures.

Vendor hierarchy data is only saved in the LFMH table. Attributes of a hierarchy node (also known as relevance indicators) are recorded in the vendor master data in table LFM1. These relevance indicators are:

• Relevance for pricing

• Relevance for subsequent settlement

During assignment processing, the system transfers the relevance indicators from table LFM1 and records them redundantly in table LFMH. If the attributes of a node in the vendor master data change, these can be updated before or during hierarchy maintenance. However, you cannot change the attributes during hierarchy maintenance.

Prerequisites

You can make settings for the following activities in the Customizing settings for Purchasing (MM):

• Vendor Hierarchy

• Define Vendor Hierarchy Categories

• Define Partner Determination for Hierarchy Categories

• Assign Account Groups

• Assign Purchasing Organization

• Assign Hierarchy Category per Order Document Type

• Partner Determination

• Assign Partner Schemas to Document Types

If you have maintained the settings consistently and the hierarchy has been created, the system checks whether the vendor appears in the pricing hierarchy defined for the current purchase order document type when the order is placed. If this is the case, the path with all higher-level nodes for the vendors and all its relevance indicators is copied into the order. Individual nodes with the hierarchy partner roles (starting from the initial partner role for the hierarchy category) are copied into the order as partners. The path is displayed on the Partner screen in the order. You must define enough hierarchy partner roles so that all higher-level nodes are copied.

Hierarchy partner roles are only designed to be transferred into an order. Since these functions are not used in the vendor master, they should not be included in the partner determination procedures for vendor master data. The system determines the first node for which the relevance indicator was selected from the hierarchy nodes path transferred. If hierarchy conditions are available for these nodes, they are observed during pricing or during subsequent settlement.

Selection

1. Specify the hierarchy category on the selection screen. The hierarchy category defines the usage category for a vendor hierarchy. Hierarchies of different categories have no relationship with one another. Whilst an assignment in a hierarchy of a specific category is unique, it can occur in a hierarchy with a different category.
2. Enter the validity date for the vendor hierarchy. The system proposes the current date automatically. The system selects all assignments that are valid on this date. If a date in the past is selected, assignments that are valid on this date are displayed but cannot be changed.
3. You can restrict the selection further by entering a specific vendor and/or purchasing organization. The system then displays all hierarchies that match the selection requirements. Select this type of selection if an extremely large number of data records are available for a hierarchy category and you want to improve system performance.

Output

The vendor hierarchy is displayed using the ALV Tree Control. Various functions are available to you here:

• You can change the validity period.

• You can change existing assignments using Drag and Drop or the menu.

• You can create new assignments.

• You can reassign and remove nodes or sub-hierarchies.

• You can access the vendor master data directly and display or change the data for a hierarchy node.

• If errors occur when the hierarchy data is read, you can view these in the application log.

For more information on working with the ALV Control, see the SAP Library under SAP NetWeaver → Application Platform → ABAP Technology → UI Technology → Controls and Control Framework for SAP GUI → SAP List Viewer (BC-SRV-ALV).

Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 5772 Date: 20240601 Time: 044253     sap01-206 ( 102 ms )