How To Fix GM063 - No origin exists in area & / & and controlling area &

SAP Error Message - Details

• Message type: E = Error

• Message class: GM - Combination manager

• Message number: 063

• Message text: No origin exists in area & / & and controlling area &

What causes this issue?

No origin exists in area &V1& to &V2& and controlling area &V3&.

System Response

The function selected cannot be performed.

How to fix this error?

Create the required origins in controlling area &V3& in the product
cost accounting configuration menu.
<DS:TRAN.OKZ1>Execute function</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GM063 - No origin exists in area & / & and controlling area & ?

  The SAP error message GM063 ("No origin exists in area & / & and controlling area &") typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with the integration of the General Ledger (FI) and the Controlling area. This error indicates that the system cannot find a valid origin for a transaction in the specified area and controlling area.
  Cause:
  
  Missing Configuration: The error often arises when there is a missing or incorrect configuration in the controlling area or the related master data. This could include missing cost centers, internal orders, or other relevant master data.
  Incorrect Assignment: The assignment of the controlling area to the company code or the assignment of the cost elements may not be set up correctly.
  Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the master data tables that are required for the transaction to be processed.
  Transaction Type: The transaction type being used may not be valid for the specified controlling area or may not have been set up correctly.
  
  Solution:
  
  Check Configuration: Verify the configuration settings in the controlling area. Ensure that the controlling area is correctly assigned to the company code and that all necessary settings are in place.
  Review Master Data: Check the relevant master data (e.g., cost centers, internal orders) to ensure that they exist and are correctly configured for the controlling area in question.
  Validate Transaction Type: Ensure that the transaction type being used is valid for the controlling area and that it has been set up correctly in the system.
  Use Transaction Codes: Utilize transaction codes such as OKB9 (for cost element accounting) or KSV5 (for cost center accounting) to review and adjust the settings as necessary.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on the configuration of the controlling area and related master data.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OKB9, KSV5, KSB1, and KOB1 for managing cost elements and cost centers.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide specific solutions or workarounds.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to access and modify the relevant data in the controlling area.
  Testing: After making changes, perform testing to ensure that the error does not reoccur and that transactions can be processed successfully.
  
  If the issue persists after checking these areas, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.