Do you have any question about this error?
Message type: E = Error
Message class: FTR_COMS -
Message number: 089
Message text: &1 leg &2: Fixing date and contract price must not both be filled
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.
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.
FTR_COMS089
- &1 leg &2: Fixing date and contract price must not both be filled ?The SAP error message FTR_COMS089 indicates that there is a conflict in the data entry for a financial transaction, specifically related to a contract in the context of financial instruments. The message states: "Fixing date and contract price must not both be filled," which means that both the fixing date and the contract price fields have been populated, which is not allowed.
Cause:
This error typically occurs in the following scenarios:
- Data Entry Error: Both the fixing date and contract price fields have been filled in the transaction entry screen, which is against the business logic defined in the system.
- Configuration Issue: The system may be configured in such a way that it expects either a fixing date or a contract price, but not both, for the specific type of financial transaction being processed.
- Business Process Requirement: The business process may dictate that only one of these fields should be used to avoid ambiguity in pricing or valuation.
Solution:
To resolve this error, you can take the following steps:
- Review the Input Fields: Check the transaction entry screen where the error occurred. Ensure that either the fixing date or the contract price is filled, but not both. Remove the value from one of the fields.
- Consult Documentation: Refer to the relevant SAP documentation or user manuals for the specific financial transaction you are working with to understand the requirements for filling in these fields.
- Check Configuration: If you have access to configuration settings, verify if there are any specific rules or settings that dictate the behavior of these fields. Adjust them if necessary, but this should be done with caution and ideally by a qualified SAP consultant.
- Test the Changes: After making the necessary adjustments, try to save or process the transaction again to see if the error persists.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who can provide deeper insights into the configuration and business logic of your SAP system.
Get instant SAP help. Start your 7-day free trial now.
FTR_COMS088
Average &1: Crcy of DCS ID &2 not equal to crcy of DCS ID &3 of the flow
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FTR_COMS087
Field &1 of COMMODITYCONDITION is empty, &1 of COMMODITYSWAP was used
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FTR_COMS090
Side category 'Not Specified' only possible in case of manual entry
What causes this issue? Side category <ZK>Not Specified </>is not permitted since <ZK>Swap Symmetrie</> or <ZK>Multiple...
FTR_COMS091
For this combination, side category 'Not Specified' is not permitted
What causes this issue? After you have enabled <LS>Swap Symmetry</> or <LS>Multiple Flow Generation</>, you have selected <...
Click on this link to search all SAP messages.