Do you have any question about this error?
Message type: E = Error
Message class: RQ - Messages for Cash Management and Forecast
Message number: 390
Message text: No payment method can be determined for &1 / &2/ &3
No payment method can be determined, either because the 'Payment
Method' parameter is full or the payment method can be determined via
view V_T018Z.
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.
RQ390
- No payment method can be determined for &1 / &2/ &3 ?The SAP error message RQ390 ("No payment method can be determined for &1 / &2 / &3") typically occurs in the context of payment processing in SAP, particularly when trying to execute a payment run or when processing invoices. The error indicates that the system is unable to determine a valid payment method for the specified document or transaction.
Causes:
- Missing Payment Method Configuration: The payment method may not be configured for the company code or the specific vendor/customer.
- Incorrect Payment Method Assignment: The payment method may not be assigned to the vendor or customer master data.
- Payment Method Not Allowed: The payment method may not be allowed for the specific transaction type or document.
- Missing Bank Details: The vendor or customer may not have the necessary bank details maintained in their master data.
- Document Type Restrictions: Certain document types may have restrictions on which payment methods can be used.
- Country-Specific Settings: Payment methods can be country-specific, and the settings may not be correctly configured for the relevant country.
Solutions:
Check Payment Method Configuration:
- Go to the configuration settings for payment methods in SAP (Transaction code: OBPM1 for payment methods by company code).
- Ensure that the payment method is correctly configured for the relevant company code.
Verify Vendor/Customer Master Data:
- Check the vendor or customer master data (Transaction codes: XK03 for vendors, XD03 for customers).
- Ensure that the payment method is assigned in the master data and that the necessary bank details are maintained.
Review Payment Method Assignment:
- Ensure that the payment method is assigned to the relevant document type and that it is allowed for the transaction you are processing.
Check for Document Type Restrictions:
- Review the settings for the document type being processed to ensure that the payment method is allowed.
Country-Specific Settings:
- If applicable, check the country-specific settings for payment methods to ensure they are correctly configured.
Test Payment Run:
- After making the necessary changes, perform a test payment run to see if the issue is resolved.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed information on payment methods and configuration.
SAP Notes: Check for any relevant SAP Notes that may address specific issues related to payment methods and error RQ390.
By following these steps, you should be able to identify and resolve the cause of the RQ390 error in SAP.
Get instant SAP help. Start your 7-day free trial now.
RQ389
Payment method &1 missing in T042E for company code &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RQ388
Level &1 belongs to deb/cred items. No line items found.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RQ391
Freuquency in days too small to set to previous day off/working day
What causes this issue? If a value less than 3 days is specified, then the parameters 'Set to previous Friday/working day instead of skipping...
RQ392
&1 individual records are missing - read long text
What causes this issue? &V1& line items could not be created as the chosen daily frequency is too low to skip a weekend or a series of non-wo...
Click on this link to search all SAP messages.