Do you have any question about this error?
Message type: E = Error
Message class: RESCSP - Settlement Participation
Message number: 018
Message text: SCS receivables pstg terms of AP contract &1 cond.type &2 are different
In contract &V1&, there are several different posting terms for the
advance payment condition type &V2&. However, service charge settlement
requires one unique posting term. This situation can occur, for
instance, if the advance payment condition type is used multiple times
with a different condition purpose within the same time period. This is
the case, for example, when subsidizers are used. In such cases, the
system is not able to determine if it should post to the master tenant
or to the subsidizer.
The settlement uses the standard posting term SPACE.
If you want to use a different posting term, then assign it as the
"posting term for service charge settlement" to all affected conditions.
The "posting term for service charge settlement" was not available in
earlier releases. Therefore, in those releases, the only possible
solution was an implementation of the BAdI BADI_RE_SC_CR. If you have an
implementation of this kind that specifies the posting term in cases
where the posting term is not unique, you can suppress this error
message.
INCLUDE RECA_CUSTOMIZED_MESSAGE_INFO OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
RESCSP018
- SCS receivables pstg terms of AP contract &1 cond.type &2 are different ?The SAP error message RESCSP018 indicates that there is a discrepancy between the posting terms of accounts receivable (AR) and accounts payable (AP) for a specific contract and condition type. This typically occurs in scenarios involving contract management or when dealing with financial transactions that involve both receivables and payables.
Cause:
The error arises when the system detects that the terms of the receivables (SCS) do not match the terms defined in the accounts payable contract for the specified condition type. This can happen due to:
- Configuration Issues: The configuration settings for the condition types in the accounts payable and receivables modules may not be aligned.
- Data Entry Errors: Incorrect data entry when creating or modifying contracts or condition types.
- Contract Changes: Changes made to the contract terms that have not been reflected in the corresponding receivables or payables settings.
- Inconsistent Master Data: Differences in master data settings for the vendor and customer involved in the transaction.
Solution:
To resolve the RESCSP018 error, you can take the following steps:
Check Configuration:
- Review the configuration settings for the condition types in both the accounts receivable and accounts payable modules. Ensure that they are consistent and aligned.
Verify Contract Terms:
- Go to the contract in question and verify the posting terms for both receivables and payables. Ensure that they match for the specified condition type.
Review Master Data:
- Check the master data for the vendor and customer involved in the transaction. Ensure that the terms of payment and other relevant settings are consistent.
Adjust Data Entry:
- If the error is due to incorrect data entry, correct the entries in the relevant contracts or transactions.
Consult Documentation:
- Refer to SAP documentation or help resources for specific guidance on the condition types and their configuration.
Testing:
- After making the necessary adjustments, perform a test transaction to ensure that the error no longer occurs.
Related Information:
ME33K
(Display Contract), ME32K
(Change Contract), or VK11
(Create Condition) to review and modify the relevant data.By following these steps, you should be able to identify and resolve the cause of the RESCSP018 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
RESCSP017
Time period of exception was changed from &3 to &4
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
RESCSP016
Exception &1 begins before the contract
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RESCSP019
SC key &1 is not defined and was assigned to condition type &2
What causes this issue? In assigning the service charge key to condition type, a service charge key was specified that is not defined. The system iss...
RESCSP020
Condition type &1 was assigned to SC key &2 that is not defined
What causes this issue? In the assignment of the condition type to service charge group/key, a service charge key was specified that is not defined.S...
Click on this link to search all SAP messages.