Do you have any question about this error?
Message type: E = Error
Message class: FICO1 -
Message number: 205
Message text: Absolute markup and relative markup are not possible at same time
You attempted to create an absolute markup condition and a relative
markup condition for the same condition type &V1& with the same currency
and with overlapping validity periods from &V2& to &V3&.
A condition type can only have either absolute markup conditions or
relative markup conditions.
Absolute and relative markup conditions in one validity period are also
overlapping if one of the two conditions is cross-currency and the other
was defined for a specific currency.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Change the validity period of the markup conditions so that their
validity periods do not overlap. Specify a <DS><DS:DE.FICO_DVALIDTO>
valid-to date</></> if required.
Error message extract from SAP system. Copyright SAP SE.
FICO1205
- Absolute markup and relative markup are not possible at same time ?The SAP error message FICO1205, which states "Absolute markup and relative markup are not possible at the same time," typically occurs in the context of pricing and cost calculations in SAP, particularly within the Financial Accounting (FI) and Controlling (CO) modules. This error arises when there is a conflict in the pricing configuration where both absolute and relative markup methods are being applied simultaneously, which is not allowed.
Cause:
- Configuration Conflict: The error usually indicates that the system is trying to apply both absolute and relative markup methods to the same pricing condition. This can happen if the pricing procedure is incorrectly configured or if there are conflicting settings in the condition records.
- Condition Records: If condition records for pricing are set up in a way that both absolute and relative markups are defined for the same item or service, the system will not be able to process the pricing correctly.
- Master Data Issues: Sometimes, the issue can stem from the master data setup, such as the material master or vendor master, where conflicting pricing information is defined.
Solution:
Review Pricing Procedure: Check the pricing procedure assigned to the relevant transaction. Ensure that it is configured to use either absolute or relative markup, but not both. You can do this by navigating to the configuration settings in SPRO:
- SPRO > Financial Accounting > Accounts Receivable and Accounts Payable > Business Transactions > Sales and Distribution > Pricing > Define Pricing Procedures.
Check Condition Records: Review the condition records for the pricing conditions involved. Ensure that you do not have both absolute and relative markup conditions defined for the same item. You can do this using transaction codes like VK11 (Create Condition) or VK12 (Change Condition).
Adjust Master Data: If the issue is related to master data, review the relevant master records (e.g., material master, vendor master) to ensure that the pricing information is consistent and does not conflict.
Consult Documentation: Refer to SAP documentation or help files for detailed information on how to configure pricing procedures and condition records correctly.
Testing: After making the necessary adjustments, perform tests to ensure that the error does not occur again. Create a test transaction to verify that the pricing is calculated correctly without triggering the error.
Related Information:
By following these steps, you should be able to resolve the FICO1205 error and ensure that your pricing configuration is set up correctly.
Get instant SAP help. Start your 7-day free trial now.
FICO1204
&1: Capitalization is not possible for unit-quoted interest
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FICO1203
You must enter a currency for differentiation category &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FICO1206
Release: Valid-from date cannot be changed to date before &1
What causes this issue? The date of last use from when the condition component was created or changed (validity period) has been exceeded. You can ne...
FICO1207
Condition determination not allowed for scaled/interval condition
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.