Describing the Customer Hierarchy and Master Agreement

Objectives

After completing this lesson, you will be able to:
  • Explain the customer hierarchy with master agreement
  • Explain Customizing for Master Agreement in SOM

Customer Hierarchy with Master Agreement

Example of a hierarchy.

Customer Hierarchy Key:

A prerequisite to use a customer hierarchy in a master agreement is that the node ID, which represents the customer hierarchy key, exists.

The key Node ID is a short representation of the full key of a customer hierarchy, which consists of the customer node:

  • Sales Organization
  • Distribution Channel
  • Division
  • Start of Validity

Create Master Agreement with Customer Hierarchy:

  1. Assign a Customer Hierarchy as Authorized Partner to your Master Agreement.
  2. Search for your Customer Hierarchy by selecting the search help in Authorized Partner.
  3. Select your setup Customer Hierarchy.
  4. Hierarchy is assigned as authorized Partner.
  5. After saving your Master Agreement, the Hierarchy is copied to the Contract Accounts Receivable and Payable (FI-CA) Master Agreement.

Create a Call off:

  1. As authorized contract partners, you can choose the hierarchy and the assigned partners.
  2. The selected partners are copied to the order/quotation.

Customizing for Master Agreement in SOM

The image shows the navigation path in SAP to define the transaction type for a Master Agreement, which is PRMA, and to access general settings and BAdIs for Master Agreement. The path is Service → Transactions → Basic Settings → Define Transaction Types and Service → Transactions → Settings for Master Agreement.
The image shows instructions for defining target document types for subscription orders and solution quotations in reference to a master agreement, along with a screenshot of the Created Document Type with Reference to Master Agreement settings in a software interface. The screenshot lists Subscription Order and A Solution Quotation as document types for transaction types PRVO and SRVP, respectively.

Customizing Target Document Type for a Call-Off:

You can create a subscription order and solution quotations with reference to an existing master agreement. To do so, you must define the target document type to be created if a certain master agreement is used.

  • Space – Subscription Order
  • A – Solution Quotation

Service → Transactions → Settings for Master Agreement → Define Target Document Type

Authorized Partner Validation Rule:

On Master Agreement item level, you have to assign Authorized Partners. Authorized partners act as partners in the call-off objects.

Partner validation Rules are predefined in customizing and used as a Filter for a BAdI Implementation. The default implementation is uses the filter SPACE.

You can find the corresponding setting in Implementation Guide (IMG): Service → Transactions → Settings for Master Agreement.

BADI for Date Determination: The default implementation is using the contract start date for the check.

You can use Business Add-In (BAdI) CRM_PRVMA_DATE_DETERMINE to check which date shall be used for checking the validity of a subscription order / solution quotation with reference to a master agreement item.

The date must be within the validity period defined in the master agreement item referenced. If the check fails, the system creates an error message.

Enhancement Spot ES_CRM_PRVMA_API

BAdI Definition CRM_PRVMA_DATE_DETERMINE

Default Implementation CL_CRM_PRVMA_DATE_DETERM_DFL

Replication to Contract Accounts Receivable and Payable (FI-CA): IMG: Service → Transaction → Data Exchange in Service.

Replication of Master Agreement between Service and FI-CA is done via Data Exchange. Custom specific logic can be implemented. In addition, you can use BADI Data Exchange CRMS4_MAGR_DATA_EXCH to enrich data during exchange.

The image shows the SAP IMG path for defining partner validation rules for provider master agreements, along with a screenshot of the Change View 'Partner Validation Rule for Provider Master Agreement' interface. It also includes details about the enhancement spot, BAdI definition, and default implementation for partner validation.

Master Agreement – BAdI Date Determination

You can use BAdI CRM_PRVMA_DATE_DETERMINE to check which date shall be used for checking the validity of a subscription order / solution quotation with reference to a master agreement item. The date must be within the validity period defined in the master agreement item referenced. If the check fails, the system creates an error message.

Enhancement Spot ES_CRM_PRVMA_API

BAdI Definition CRM_PRVMA_DATE_DETERMINE

Default Implementation CL_CRM_PRVMA_DATE_DETERM_DFL

The default implementation is using the contract start date for the check.

The image shows the SAP configuration path for defining custom handler classes for forward and backward data exchange in the Service module, along with a customization view for data exchange settings. It highlights the replication of Master Agreement between Service and FI-CA using Data Exchange and mentions the use of BADI Data Exchange CRMS4_MAGR_DATA_EXCH for data enrichment.

Create a Master Agreement

ExerciseStart Exercise

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn