How To Fix KE777 - You must specify a company code if the company code currency is used

KE777 - Overview

• Message type: E = Error

• Message class: KE -

• Message number: 777

• Message text: You must specify a company code if the company code currency is used

What causes this issue?

You have added the characteristic "Currency type" (field PALEDGER) to a
summarization level. If the currency type is specified as "10" (company
code currency) or with an asterisk ("*"), you also need to use the
field "Company code" (BUKRS) in the summarization level.
<ZH>Note:</>
The field "Company code" is not required if you specified currency type
"B0" (operating concern currency).

System Response

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

How to fix this error?

First add the field "Company code" to your summarization level. Then
add the currency type.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KE777 - You must specify a company code if the company code currency is used ?

  The SAP error message KE777 indicates that a company code must be specified when the company code currency is being used in a transaction. This error typically arises in the context of controlling (CO) module transactions, particularly when dealing with cost centers, internal orders, or profit centers.
  
  Cause:
  The error occurs when:
  
  A transaction is being processed that requires a company code, but the company code is not specified.
  The system is set up to use company code currency, which necessitates the identification of a specific company code for proper financial reporting and analysis.
  
  
  Solution:
  To resolve the KE777 error, you can take the following steps:
  
  
  Specify the Company Code: Ensure that you are entering a valid company code in the relevant field of the transaction. This is usually done in the header or initial screen of the transaction.
  
  
  Check Configuration: If you are consistently encountering this error, check the configuration settings in the controlling area to ensure