How To Fix /ACCGO/DGR068 - Schedule name version not fetched from BRF+

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/DGR -

• Message number: 068

• Message text: Schedule name version not fetched from BRF+

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 /ACCGO/DGR068 - Schedule name version not fetched from BRF+ ?

  The SAP error message /ACCGO/DGR068 Schedule name version not fetched from BRF+ typically indicates an issue with the Business Rule Framework (BRF+) configuration in the context of the SAP system, particularly when dealing with the Financial Accounting (FI) or Controlling (CO) modules.
  Cause:
  
  
  BRF+ Configuration Issues: The error often arises when the system is unable to retrieve the necessary schedule name or version from the BRF+ application. This could be due to:
  
  Missing or incorrect configuration in BRF+.
  The specific rule set or decision table not being activated or published.
  Issues with the transport of BRF+ objects between different environments (e.g., Development to Production).
  
  
  
  Authorization Issues: The user executing the transaction may not have the necessary authorizations to access the BRF+ rules or decision tables.
  
  
  Data Consistency Issues: There may be inconsistencies in the data or settings related to the schedules in the BRF+.
  
  
  Solution:
  
  
  Check BRF+ Configuration:
  
  Ensure that the relevant BRF+ rules, decision tables, and applications are correctly configured and activated.
  Verify that the schedule name and version exist in the BRF+ application.
  
  
  
  Authorization Check:
  
  Confirm that the user has the necessary authorizations to access BRF+ objects. This can be done by checking the user roles and authorizations in the SAP system.
  
  
  
  Transport Issues:
  
  If the issue arose after a transport, check if all necessary BRF+ objects were included in the transport request and that they were successfully imported into the target system.
  
  
  
  Debugging:
  
  If the above steps do not resolve the issue, consider debugging the process to identify where the failure occurs. This may involve checking the logs in BRF+ or using transaction codes like SLG1 to view application logs.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to BRF+ and the specific error message for any additional troubleshooting steps or patches that may be required.
  
  
  
  Related Information:
  
  Transaction Codes: You may find it useful to use transaction codes like BRF+ (to access the BRF+ workbench) or SLG1 (to view application logs) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or fixes related to this error message. You can search for the error message or related keywords in the SAP Support Portal.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If the problem persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.