How To Fix MDGBP163 - Relationship cannot be processed due to time dependency

SAP Error Message - Details

• Message type: E = Error

• Message class: MDGBP - Master Data Governance: Business Partner specific messages

• Message number: 163

• Message text: Relationship cannot be processed due to time dependency

What causes this issue?

You want to add the relationship &v1& between business partners &v2& and
&v3& to an MDG change request. This is not possible because the MDG
data model BP does not support time dependency for business partner
relationships. However, because you provided a valid-to date &v4&,
active time dependency is required to prevent the valid-to date from
getting lost.

System Response

The system skips the current relationship and doesn't add it to the
change request.

How to fix this error?

In MDG 9.0 or higher, you can enable the time dependency feature for
business partner relationships.
If you are working with an earlier MDG version, or if you don't want to
enable this feature, change the valid-to date for this record in your
source system to 9999/12/31. This will make the record time-independent,
and the relationship can be added to the change request.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDGBP163 - Relationship cannot be processed due to time dependency ?

  The SAP error message MDGBP163, which states "Relationship cannot be processed due to time dependency," typically occurs in the context of Material Requirements Planning (MRP) or when dealing with master data relationships in SAP, such as those between materials, BOMs (Bill of Materials), or routing.
  
  Cause:
  The error is generally caused by one of the following issues:
  
  
  Time Dependency: The relationship you are trying to process has time-dependent data that is not valid for the period you are working in. For example, if a BOM or routing is valid only for a specific date range, and you are trying to access it outside that range, this error may occur.
  
  
  Missing Validity Period: The data you are trying to use may not have a defined validity period, or the validity period may not cover the date you are trying to process.
  
  
  Incorrect Configuration: There may be configuration issues in the MRP settings or in the master