How To Fix BK173 - No currency was given for the activity price.

SAP Error Message - Details

• Message type: E = Error

• Message class: BK - Create, Display, Reverse Controlling Document

• Message number: 173

• Message text: No currency was given for the activity price.

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 BK173 - No currency was given for the activity price. ?

  The SAP error message BK173 ("No currency was given for the activity price") typically occurs in the context of controlling (CO) when you are trying to post an activity price or when you are working with cost centers, internal orders, or other controlling objects that require a currency specification.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Missing Currency Information: The activity price you are trying to enter does not have an associated currency defined in the system.
  Configuration Issues: The controlling area or the relevant master data (like cost centers or internal orders) may not have the currency set up correctly.
  Data Entry Errors: The user may have forgotten to enter the currency when inputting the activity price.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Activity Price Configuration:
  
  Go to the configuration settings for the activity types in the controlling area.
  Ensure that the activity price is defined with a currency. You can do this by navigating to the relevant configuration path in SPRO (SAP Reference IMG).
  
  
  
  Verify Master Data:
  
  Check the master data for the cost center or internal order you are working with. Ensure that the currency is correctly defined.
  You can do this by using transaction codes like KS03 (Display Cost Center) or KO03 (Display Internal Order).
  
  
  
  Enter Currency:
  
  If you are entering data manually, ensure that you specify the currency when entering the activity price. This is often done in the relevant transaction screen.
  
  
  
  Check Controlling Area Settings:
  
  Ensure that the controlling area has a currency defined. You can check this in the controlling area settings in SPRO.
  
  
  
  Review User Input:
  
  If the error occurs during data entry, double-check the input fields to ensure that all required fields, including currency, are filled out correctly.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  KS01: Create Cost Center
  KS02: Change Cost Center
  KS03: Display Cost Center
  KO01: Create Internal Order
  KO02: Change Internal Order
  KO03: Display Internal Order
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on configuring activity types and managing currencies in controlling.
  
  
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to this error message.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the problem persists, consider reaching out to your SAP support team for further assistance.