Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 426
Message text: Billing document type & for sales document & not defined
Billing document type &V1& does not exist in the system. However, it
has been assigned to partial or final settlement accounting via the
sales document type &V2& of rebate arrangement &V3& ("subsequent
settlement").
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Create billing document type &V1& or change the assignment of
arrangement type to sales document type or sales document type to
billing document type (sales-order-related billing document type).
INCLUDE 'NA_CUST_MAINTAIN' OBJECT DOKU ID TX
<DS:SIMG.SIMG_CFMENUOLSDVOFA>Define billing document types</>
<DS:SIMG.SIMG_CFMENUOLSDVOV8>Define sales document types</>
<DS:SIMG.SIMG_CFMENUOLMEOMHD>Define rebate arrangement types for
subsequent settlement</>
ENDIF
Error message extract from SAP system. Copyright SAP SE.
MN426
- Billing document type & for sales document & not defined ?The SAP error message MN426 typically indicates that there is an issue with the configuration of billing document types in relation to sales document types. This error occurs when the system cannot find a valid mapping between the specified billing document type and the sales document type in the configuration settings.
Cause:
- Missing Configuration: The billing document type is not defined for the specific sales document type in the system.
- Incorrect Settings: There may be incorrect or incomplete settings in the configuration of billing types.
- Custom Development: If there are custom developments or modifications, they may not have been properly aligned with the standard configurations.
Solution:
To resolve the MN426 error, follow these steps:
Check Configuration:
- Go to the SAP Customizing Implementation Guide (SPRO).
- Navigate to Sales and Distribution > Billing > Billing Documents > Define Billing Types.
- Ensure that the billing document type you are trying to use is correctly defined and linked to the appropriate sales document type.
Define Billing Document Types:
- If the billing document type is missing, you will need to create it.
- Ensure that the billing type is assigned to the correct sales document type.
Assign Billing Types to Sales Document Types:
- In the same configuration area, check the assignment of billing types to sales document types.
- Make sure that the sales document type you are using is linked to the billing document type.
Check for Customizations:
- If there are any customizations or enhancements, review them to ensure they do not interfere with the standard billing document type assignments.
Testing:
- After making the necessary changes, test the process again to ensure that the error is resolved.
Related Information:
SPRO
for configuration, VA01
for creating sales orders, and VF01
for creating billing documents.By following these steps, you should be able to resolve the MN426 error and ensure that your billing document types are correctly configured in relation to your sales document types.
Get instant SAP help. Start your 7-day free trial now.
MN425
Sales document type & not defined or faulty
What causes this issue? Sales document type &V1& does not exist in the system or is not allowed for "subsequent settlement" (end-of...
MN424
Copying control for sales doc. type & for billing doc. type & faulty
What causes this issue? The copying control facility for sales document type &V1& for billing document type &V2& at item level (item ...
MN427
Sales organization, distribution channel, or division missing
What causes this issue? You should check the organizational data for sales organization &V1&, distribution channel &V2&, division &am...
MN428
Organizational data: debtor missing for rebate arrangement &
What causes this issue? The organizational data for the debtor for rebate arrangement &V1& is missing. Apart from a program bug, another poss...
Click on this link to search all SAP messages.