How To Fix FRE368 - Material &1, plant &2: Change pointer for LFRHY/MRPPP was not created.

FRE368 - Overview

• Message type: E = Error

• Message class: FRE - F&R CON R/3 - Messages

• Message number: 368

• Message text: Material &1, plant &2: Change pointer for LFRHY/MRPPP was not created.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FRE368 - Material &1, plant &2: Change pointer for LFRHY/MRPPP was not created. ?

  The SAP error message FRE368 indicates that a change pointer for a specific material and plant combination was not created for the LFRHY (Logistics) or MRPPP (Material Requirements Planning) process. This error typically arises in the context of change pointers, which are used in SAP to track changes to master data and trigger subsequent processing.
  
  Cause:
  
  Change Pointer Not Activated: The change pointer functionality may not be activated for the specific material type or plant.
  Incorrect Configuration: There may be configuration issues in the change pointer settings for the relevant application area.
  Material Status: The material may be in a status that prevents change pointers from being created (e.g., blocked or inactive).
  Data Inconsistencies: There could be inconsistencies in the master data that prevent the creation of change pointers.
  Missing Customizing: The necessary customizing settings for change pointers might not be properly set up in the system.
  
  
  Solution:
  
  
  Check Change Pointer Activation:
  
  Go to transaction SPRO and navigate to