Do you have any question about this error?
Message type: E = Error
Message class: EDEREG_INV - Error Messages for Payment Management in a Deregulated Env.
Message number: 728
Message text: Cannot create aggregated posting for special cases
The system can not create the aggregated posting of the incoming bill
for one of the following reasons:
The maximum permitted amount for the relevant special cases was not
transferred to the posting run for the aggregated incoming bill.
The current special case requires the tax lines to be created in a
specific way. A new tax line must be created that corresponds to the
existing ones but that only refers to a tax base amount and not to a tax
amount. The tax base amount &V1& in the tax correction line exceeds the
maximum permitted amount of &V2&.
For <DS:FU.ISU_SAMPLE_R212>event R212</>:
Either no maximum permitted amount was transferred to the posting run
for the aggregated incoming bill or
A maximum permitted amount was transferred but the amount is not
sufficient
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The system cannot execute posting in this case. This can be for theINCLUDE NA_SYSADMIN1 OBJECT DOKU ID TX
For <DS:FU.ISU_SAMPLE_R212>event R212</>, a clearing lock and a maximum
permitted limit for special cases during tax posting can be transferred
for the posting run for the aggregated bill.
Define a customer function module for event R212 or enhance the existing
one and transfer a clearing lock and the maximum permitted amount to the
posting run for the aggregated bill.
<ZU>Note on Maximum Permitted Amounts for Special Cases During Tax
Posting:</>
Based on the currency, the maximum amount should take rounding
differences into account. If the tax base amount in the additional tax
line exceeds the possible rounding differences, create a problem
message. For example, for the currency EURO, do not select a maximum
amount that is higher than 0,10 EUR.
You can maintain the clearing lock in Customizing. Execute the
<DS:SIMG._FICABFDP_TFK000S>Define Lock Reasons for Posting Locks</> IMG
activity.
If you have to create a new customer module for event R212, define it in
the <DS:SIMG._FICA_TFKFBC>Define Customer-Specific Function Modules</>
activity.
You can only clear the document once the clearing lock has been removed
from all document items. You can only remove the clearing lock from all
document items if the document has been checked accordingly and found to
be correct.
Error message extract from SAP system. Copyright SAP SE.
EDEREG_INV728
- Cannot create aggregated posting for special cases ?The SAP error message EDEREG_INV728 ("Cannot create aggregated posting for special cases") typically occurs in the context of the SAP system when dealing with invoice verification and posting processes, particularly in the area of special cases such as partial invoices, credit memos, or other exceptions.
Cause:
The error can arise due to several reasons, including:
- Incorrect Configuration: The system may not be configured correctly for handling special cases in invoice processing.
- Data Inconsistencies: There may be inconsistencies in the data being processed, such as missing or incorrect information in the invoice or related documents.
- Posting Rules: The posting rules for aggregated postings may not be set up to handle the specific type of transaction being processed.
- Special Cases Handling: The system may not support the specific type of special case being attempted, leading to the inability to create an aggregated posting.
Solution:
To resolve the error, consider the following steps:
Check Configuration: Review the configuration settings related to invoice verification and special cases in the SAP system. Ensure that the settings are appropriate for the types of transactions being processed.
Validate Data: Ensure that all necessary data for the invoice or transaction is complete and accurate. Check for missing fields or incorrect entries that could lead to processing issues.
Review Posting Rules: Examine the posting rules in the system to ensure they are set up to handle the specific special case you are working with. Adjust the rules if necessary.
Consult Documentation: Refer to SAP documentation or notes related to the error message EDEREG_INV728 for any specific guidance or updates that may address the issue.
Test with Different Scenarios: If possible, test the posting process with different scenarios to identify if the issue is isolated to specific cases or if it is a broader problem.
Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights or patches that can resolve the issue.
Related Information:
By following these steps, you should be able to diagnose and resolve the EDEREG_INV728 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
EDEREG_INV727
Use other selection parameters
The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Procedure for System Adminis...
EDEREG_INV726
No lines exist for internal reference number &1
What causes this issue? The internal reference number (INT_LINE_REF_NO) is used to reference a different document line. However, the system cannot fi...
EDEREG_INV729
The system settings do not allow the down payment process
What causes this issue? System settings do not permit posting budget billing amounts as down payments on incoming invoices for the sender/receiver pa...
EDEREG_INV730
No tax number defined for posting area &1
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.