Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 165
Message text: Condition type & not maintained in settlement schema &
To permit settlement accounting to be carried out for a condition
record of condition type &V1&, the condition type must be entered in
settlement schema (calculation schema) &V2&. Among other things, the
system takes the account keys for posting the income and the provision
for accrued income (if active - see Customizing, condition types) from
this entry.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
&WHAT_TO_DO& (system administrator)Error message extract from SAP system. Copyright SAP SE.
MN165
- Condition type & not maintained in settlement schema & ?The SAP error message MN165 indicates that a specific condition type is not maintained in the settlement schema for a particular process. This error typically arises in the context of settlement processes, such as in the case of internal orders, projects, or other cost objects where settlement is required.
Cause:
The error occurs when:
- A condition type that is expected to be used in the settlement process is not defined in the settlement schema.
- The configuration for the settlement schema does not include the necessary condition type, which is required for the calculation of settlement amounts.
Solution:
To resolve the MN165 error, you can follow these steps:
Check the Settlement Schema:
- Go to the transaction code
OKO7
(for internal orders) orCJ20N
(for projects) depending on your context.- Review the settlement schema assigned to the relevant order or project.
Maintain the Condition Type:
- If the condition type is missing, you need to add it to the settlement schema.
- Use transaction code
OKO6
to maintain the settlement schema.- Add the required condition type to the schema. Ensure that the condition type is correctly configured with the necessary settings (e.g., calculation type, percentage, etc.).
Check Configuration:
- Ensure that the condition type is properly defined in the system. You can check this in the configuration settings for condition types (transaction code
V/06
for pricing conditions).- Verify that the condition type is active and correctly set up for the intended use.
Test the Settlement:
- After making the necessary changes, perform a test settlement to ensure that the error no longer occurs.
Consult Documentation:
- If you are unsure about the specific condition type or its configuration, refer to SAP documentation or consult with your SAP functional consultant for guidance.
Related Information:
Transaction Codes:
OKO7
: Display/Change Settlement Profile for Internal OrdersCJ20N
: Project ManagementOKO6
: Maintain Settlement SchemaV/06
: Maintain Pricing ConditionsCondition Types:
SAP Notes:
By following these steps, you should be able to resolve the MN165 error and ensure that your settlement process functions correctly.
Get instant SAP help. Start your 7-day free trial now.
MN164
Price determination error during billing doc. check run (internal error)
What causes this issue? The system could not read the price determination data after the billing document check run. The billing document numbers and...
MN163
An error has occurred during saving of data on business volume comparison
What causes this issue? An error occurred during the storing of the statistical data records for"subsequent settlement" (end-of-period reba...
MN166
Calculation schema & not defined for usage &, application &
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...
MN167
Indicator & for distribution of income not defined
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.