Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 261
Message text: Category & of purchasing document & not allowed
The updating of supplier business volumes within the framework of
<DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</> is
only defined for purchasing documents belonging to categories 'F'
(purchas order) or 'L' (scheduling agreement). However, document &V2&
belongs to category &V1&.
No supplier business volume could be updated for purchasing document
&V2&.
Contact your system administrator. This situation is probably due to a
program error.
The error occurred in function module &V3&.
Error message extract from SAP system. Copyright SAP SE.
MN261
- Category & of purchasing document & not allowed ?The SAP error message MN261, which states "Category & of purchasing document & not allowed," typically occurs in the context of purchasing documents such as purchase orders or purchase requisitions. This error indicates that the document category being used is not permitted for the specific transaction or configuration in the system.
Cause: Incorrect Document Category: The purchasing document category (e.g., standard purchase order, contract, etc.) being used is not allowed for the specific transaction or configuration.
Configuration Issues: The configuration settings in the SAP system may not allow the use of certain document categories for specific purchasing processes. User Authorizations: The user may not have the necessary authorizations to create or modify documents of that category. Document Type Settings: The document type settings in the purchasing configuration may not be set up correctly to allow the specified category.
Solution: Check Document Category: Verify that the document category you are trying to use is valid for the transaction
Get instant SAP help. Sign up for our Free Essentials Plan.
MN260
Condition class & of condition record not allowed
What causes this issue? A program or function module within the subsequent settlement functionality has been called up with a condition record that d...
MN259
Settlement indicator not set for item &1 of document &2
What causes this issue? The indicator "Settlement" exists for each item in a document. This indicates whether the item is relevant for subs...
MN262
Overflow in statistics update, subsequent settlement, Purchasing
What causes this issue? What causes this issue? An overflow has occurred during the process of updating the business volume subject to rebate settlem...
MN263
Short text for material & does not exist in language &
What causes this issue? Subsequent settlement accounting for the condition record (internal number &V3&) and thus for rebate arrangement &...
Click on this link to search all SAP messages.