Do you have any question about this error?
Message type: E = Error
Message class: F0 - FI batch program messages
Message number: 413
Message text: Payment & contains different hedging contract numbers
Line items were processed in payment &V1& &V2&&V3& which contain
different contract numbers for hedging contracts.
According to the requirements for the &V4& format, only one contract
number can be entered for a payment order.
None of the hedging contract numbers entered in the line items in
payment &V1& &V2&&V3& were transferred to the data medium.
If you require contract numbers to be transferred to the data medium,
proceed as follows:
First reset the clearing items and reverse clearing document &V1& &V2&.
<DS:TRAN.FBRA>Reset cleared items</>
ELSE
Payment order &V3& has been generated. You must delete this.
<DS:REPO.RFPYORDD>Deletion report for payment orders</>
ENDIF
Then change the configuration of the payment program. Select the field
"Single payment for marked item" under <ZH>Payment methods->In company
code</>.
<DS:TRAN.FBZP>Payment program configuration</>
You must also enter the the payment method explicitly in the item.
<DS:TRAN.FB09>Change line item</>
If necessary, change the document change rules beforehand so that the
relevant fields are ready for input when the document is changed.
<DS:TRAN.OB32>Define document change rules</>
Execute another payment run to clear the changed open items and then
generate the data medium.
<DS:TRAN.F110>Automatic payment transactions</>
Error message extract from SAP system. Copyright SAP SE.
F0413
- Payment & contains different hedging contract numbers ?The SAP error message F0413, which states "Payment & contains different hedging contract numbers," typically occurs in the context of financial transactions involving hedging contracts. This error indicates that the payment document you are trying to process includes multiple hedging contracts that are not compatible or cannot be processed together.
Cause:
- Multiple Hedging Contracts: The payment document references multiple hedging contracts that are not aligned or are from different sources, which is not allowed in the current configuration.
- Configuration Issues: There may be configuration settings in the SAP system that do not allow for the processing of payments that involve multiple hedging contracts.
- Data Entry Errors: Incorrect data entry during the creation of the payment document or the hedging contracts may lead to this error.
- Inconsistent Contract Types: The hedging contracts may be of different types or categories, which the system does not allow to be processed together.
Solution:
- Review Payment Document: Check the payment document to ensure that it only references a single hedging contract. If multiple contracts are included, separate them into different payment documents.
- Check Hedging Contracts: Verify the hedging contracts involved in the payment. Ensure they are compatible and belong to the same category or type.
- Configuration Review: Consult with your SAP configuration team to review the settings related to hedging contracts and payments. Adjustments may be needed to allow for the processing of multiple contracts if that is a requirement.
- Data Correction: If the error is due to incorrect data entry, correct the entries in the payment document or the hedging contracts.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on handling hedging contracts and payments.
Related Information:
If the issue persists after following these steps, it may be beneficial to engage with SAP support or a consultant who specializes in financial transactions within SAP.
Get instant SAP help. Start your 7-day free trial now.
F0412
Payment &1 &2: Due date &3 changed to &4
What causes this issue? The direct debiting system in Finland makes the following specifications for the due date of a bank collection order. The due...
F0411
Company code & and payment method &: Service code has not been maintained
What causes this issue? The service code for direct debiting has not been maintained or has been maintained incorrectly for payment method &V2&am...
F0414
Payment method &2 in company code &1: Customer no. maintained incorrectly
What causes this issue? The customer number was entered incorrectly or not maintained in the form data for payment method &V2& in company cod...
F0415
Payment method &2 in company code &1: Customer no. is too long
What causes this issue? The customer number maintained in the form data for payment method &V2& in company code &V1& is too long.Syst...
Click on this link to search all SAP messages.