Do you have any question about this error?
Message type: E = Error
Message class: FKKINV - Invoicing in Contract Accounts Receivable and Payable
Message number: 679
Message text: Event 2641 provides inconsistent data for the card payment
<DS:FU.FKK_SAMPLE_2641>Event 2641</> provides formally incorrect data
for processing card payments.
The error is error number &V1& from the following error list:
Card &V2& &V3& is invalid
No card data was found.
Card data is incomplete or inconsistent.
Assignment of card data to open items is formally incorrect.
A new payment card supplement is supposed to be created for card &V2&
&V3& (for instance, postauthorization). Card data is nonetheless
inconsistent.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE NA_SYSADMIN1 OBJECT DOKU ID TXINCLUDE FICA_NA_OSS OBJECT DOCU ID TX
Error message extract from SAP system. Copyright SAP SE.
FKKINV679
- Event 2641 provides inconsistent data for the card payment ?The SAP error message FKKINV679, specifically related to Event 2641, indicates that there is inconsistent data for a card payment in the context of the SAP Convergent Charging or SAP Convergent Invoicing modules. This error typically arises when there are discrepancies in the data associated with a payment transaction, which can prevent the system from processing the payment correctly.
Causes:
- Data Mismatch: There may be inconsistencies between the payment data and the invoice data, such as mismatched amounts, currencies, or payment methods.
- Incomplete Data: Required fields for the card payment may be missing or incorrectly filled out.
- Configuration Issues: Incorrect configuration settings in the payment processing or invoicing modules can lead to inconsistencies.
- Transaction Errors: Errors during the transaction process, such as network issues or timeouts, can result in incomplete or corrupted data.
- Duplicate Transactions: If a payment is attempted multiple times, it may lead to conflicts in the data being processed.
Solutions:
- Data Verification: Check the payment and invoice data for consistency. Ensure that all relevant fields are correctly filled and match across the system.
- Review Configuration: Verify the configuration settings for payment processing in SAP. Ensure that all necessary parameters are correctly set up.
- Transaction Logs: Review transaction logs to identify any errors or issues that occurred during the payment process. This can help pinpoint the source of the inconsistency.
- Reprocess Payment: If the payment was not processed correctly, attempt to reprocess the payment after correcting any identified issues.
- Consult Documentation: Refer to SAP documentation or support notes related to FKKINV679 for specific guidance on resolving this error.
- Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They can provide insights based on the specific configuration and version of your SAP system.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FKKINV678
Statistical tax amount in local currency not correct (&1)
What causes this issue? The sales/purchase tax amounts in the general ledger items do not match the total of the statistical tax data in the business...
FKKINV677
Statistical tax amount in transaction currency not correct (&1)
What causes this issue? The sales/purchase tax amounts in the general ledger items do not match the total of the statistical tax data in the business...
FKKINV680
Max. no. of preliminary invoices reached. Invoicing to be aborted
What causes this issue? You want to create a preliminary invoice to replace existing preliminary invoice &v3&. However, the configuration of ...
FKKINV681
Key for determining invoice form &1 is unknown
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.