Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 268
Message text: Income is not to be determined (subsequent settlement)
The credit memo document you are processing is a settlement document
created during the process of settlement accounting for a condition
record within the framework of the "subsequent (end-of-period rebate)
settlement" functionality.
For the function you require, the system attempted to determine the
settled incomes and any provision amount from the document.
The system determines the accounts defined in Customizing for the
debit/credit indicator on the basis of
the company code, and
the account key defined in settlement schema &V1& for condition type
&V2&.
However, no line of the credit memo document has one of the two
combinations of account and debit/credit indicator. It was therefore
not possible to determine the settled income from the credit memo
document.
It is not possible to process the credit memo document with the current
configuration of the account determination facility.
Please contact your R/3 system administrator.
The cause of this error will normally be due to a change made to the
account determination facility in Customizing since the date of
document creation.
To cancel this document, the account determination facility must be
restored to its status at the time of document creation. You will find
information on the accounts posted using the function "Display
document".
The rebate arrangement involved is &V3&. The condition record has the
(internal) number &V4&.
Error message extract from SAP system. Copyright SAP SE.
MN268
- Income is not to be determined (subsequent settlement) ?The SAP error message MN268, which states "Income is not to be determined (subsequent settlement)," typically occurs in the context of the settlement process in SAP, particularly when dealing with internal orders, projects, or cost centers. This error indicates that the system is unable to calculate or determine the income for a particular settlement due to various reasons. Causes of Error MN268 Missing or Incorrect Settlement Rules: The settlement rules for the order or project may not be properly defined or may be missing. This can prevent the system from determining how to allocate costs and revenues. Incorrect Configuration: The configuration settings for the settlement process may not be set up correctly. This includes settings related to the settlement profile, allocation structure, or the characteristics of the cost objects. No Revenue Data: There may be no revenue data available for the period in question. If there are no postings that can be settled, the
Get instant SAP help. Sign up for our Free Essentials Plan.
MN267
Document data faulty (internal error)
What causes this issue? Invalid document data has been passed on to function module &V1&.System Response The system issues an error message ...
MN266
No default value for document type assigned to transaction &
What causes this issue? The default value may also be needed for automatic processes (such as credit memos within the framework of "subsequent s...
MN269
Trans./event type & from PO history is not allowed (internal error)
What causes this issue? The function module &V4& ("subsequent settlement", Purchasing) was invoked with inadmissible data. The func...
MN270
Supplier business volume (final settlement) cannot be determined
What causes this issue? Calculation rule &V1& determines the way in which the supplier business volume is used for the purposes of final sett...
Click on this link to search all SAP messages.