How To Fix /ACCGO/OIJ_NOM_API060 - API supports only ACM specific pegging types

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/OIJ_NOM_API -

• Message number: 060

• Message text: API supports only ACM specific pegging types

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/OIJ_NOM_API060 - API supports only ACM specific pegging types ?

  The SAP error message /ACCGO/OIJ_NOM_API060 API supports only ACM specific pegging types typically occurs in the context of the SAP Oil and Gas (OIJ) module, particularly when dealing with Nomination APIs. This error indicates that the API you are trying to use is restricted to specific pegging types that are related to the ACM (Asset and Contract Management) functionality within the SAP system.
  
  Cause:
  
  Incorrect Pegging Type: The error is usually triggered when the pegging type being used in the API call is not one of the ACM-specific types that the API supports.
  
  Configuration Issues: There may be a misconfiguration in the system that leads to the use of unsupported pegging types.
  Version Compatibility: The API might be expecting a certain version of the data or configuration that is not being met.
  
  
  Solution:
  
  Check Pegging Types: Review the documentation for the API to ensure that you are using a valid ACM-specific pegging type. Make sure that