Do you have any question about this error?
Message type: E = Error
Message class: KK -
Message number: 319
Message text: Planning currency does not exist
The planning currency in which a unit cost estimate is created does not
exist. This means, for example, that you are trying to plan in
transaction currency, but the key for this currency is missing.
This can occur if the switch allowing planning in all currencies was
changed from 'Not allowed' to 'Allowed' in the control data for the CO
area settings.
If planning was already carried out without currencies, that is, only
in CO area currency, this can no longer be changed as unit costing does
not know the missing currencies.
You can no longer change the unit cost estimate.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
KK319
- Planning currency does not exist ?The SAP error message KK319: Planning currency does not exist typically occurs in the context of controlling (CO) and profitability analysis (CO-PA) when you are trying to perform planning activities, such as creating or updating planning data, and the system cannot find the specified planning currency for the relevant controlling area or the specific planning version.
Causes:
- Missing Planning Currency Configuration: The planning currency may not be defined for the controlling area or the specific planning version you are using.
- Incorrect Settings in Master Data: The master data for the cost center, internal order, or profitability segment may not have the correct currency settings.
- Inconsistent Currency Settings: There may be inconsistencies between the company code currency, controlling area currency, and planning currency.
- Version Not Defined: The planning version you are trying to use may not be defined correctly or may not have been activated.
Solutions:
Check Planning Currency Configuration:
- Go to the configuration settings for your controlling area (Transaction Code: OX19).
- Ensure that the planning currency is defined and is consistent with the company code currency and controlling area currency.
Verify Master Data:
- Check the master data for the relevant cost centers, internal orders, or profitability segments to ensure that they have the correct currency settings.
- You can use Transaction Codes like KS03 (Display Cost Center) or KO03 (Display Internal Order) to check the details.
Review Planning Version:
- Ensure that the planning version you are using is correctly defined and activated. You can check this in the planning version settings (Transaction Code: OKKP).
- Make sure that the version is set up to allow planning in the desired currency.
Currency Translation:
- If you are working with multiple currencies, ensure that the necessary currency translation settings are in place. This may involve setting up exchange rates if you are planning in a currency different from the local currency.
Consult Documentation:
- Review SAP documentation or help resources for specific guidance on planning currencies and related settings.
Related Information:
Transaction Codes:
SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
User Roles and Authorizations: Ensure that the user has the necessary authorizations to access the planning functions and the relevant data.
By following these steps, you should be able to identify the cause of the KK319 error and implement the necessary solutions to resolve it.
Get instant SAP help. Start your 7-day free trial now.
KK318
Costing type & is not in table TCK01
What causes this issue? The costing control tables were changed. Costing type &v1& is stored in control table TCK03 under costing variant &am...
KK317
Costing variant & does not exist for the reference object
What causes this issue? Cost estimates for the reference object you edited may not be assigned to costing variant &v1&.System Response The s...
KK320
No cost estimate exists for base planning object &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
KK326
Error when determining partner number
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.