Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 468
Message text: No foreign payment for creditor & in company code &
The transaction for creditor &V1& in <GL:company_code>company code</>
&V2& does not trigger a notifiable foreign payment.
Entering additional data relating to foreign payments therefore makes
little sense.
The entry of new data is refused. If the message appears in display or
change mode, the system setting or the creditor master record have
probably been changed.
Look into the matter. If necessary, contact your system administrator.
If you have already entered data, you should
delete it if this is still possible according to the processing status
restore the creditor master record
Error message extract from SAP system. Copyright SAP SE.
MN468
- No foreign payment for creditor & in company code & ?The SAP error message MN468 "No foreign payment for creditor & in company code &" typically occurs when you are trying to process a foreign payment for a vendor (creditor) in a specific company code, but the system cannot find the necessary configuration or data to allow for that transaction. Here are some potential causes, solutions, and related information for this error:
Causes:
- Missing Configuration: The company code may not be set up to handle foreign payments. This could be due to missing settings in the payment configuration or in the vendor master data.
- Vendor Master Data: The vendor may not be set up correctly for foreign currency transactions. This includes missing currency information or incorrect payment terms.
- Currency Settings: The currency used for the payment may not be allowed for the specified company code or vendor.
- Payment Method: The payment method being used may not support foreign payments.
- Transaction Type: The transaction type may not be configured to allow foreign payments.
Solutions:
Check Vendor Master Data:
- Go to the vendor master record (transaction code
XK03
orFK03
) and ensure that the vendor is set up for foreign currency transactions. Check the currency field and ensure it is correctly populated.Review Company Code Configuration:
- Check the company code settings in the configuration (transaction code
OBY6
) to ensure that it is set up to handle foreign currency transactions. Look for settings related to foreign payments.Payment Method Configuration:
- Review the payment method configuration (transaction code
FBZP
) to ensure that the payment method being used allows for foreign payments. Make sure that the payment method is correctly assigned to the vendor.Currency Settings:
- Ensure that the currency used for the payment is valid for the company code and that the necessary exchange rates are maintained in the system (transaction code
OB08
).Check Transaction Type:
- Verify that the transaction type being used for the payment is configured to allow foreign payments. This may involve checking the payment program settings.
Consult Documentation:
- Review SAP documentation or consult with your SAP support team for specific configuration steps related to foreign payments.
Related Information:
FBZP
(Payment Program), XK03
(Display Vendor), and OB08
(Exchange Rate).If the issue persists after checking these areas, it may be beneficial to engage with your SAP support team or consult with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MN467
Document currency missing
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN466
Function not defined for rebate arrangements of type &
What causes this issue? It is not possible to perform this function for <GL:arrangement>rebate arrangement</> &V4&. The arrangem...
MN469
No foreign payment for debtor & in company code &
What causes this issue? The transaction for debtor &V1& in <GL:company_code>company code</> &V2& does not trigger a notif...
MN470
Settlement documents already exist for a condition record
What causes this issue? Settlement documents already exist for a condition record.How to fix this error? The system issues an error message and will...
Click on this link to search all SAP messages.