Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 843
Message text: No condition type transferred
External data record &V1& contains no condition type.
However, the field "Condition type" (MCKONAB-KSCHL) is a mandatory-entry
field.
The external data record cannot be taken over.
Please correct the external data file.
If the error did not occur in a test run and you have written to the
actual data (version '000'), you should cancel the external supplier
business volume data update in order to preserve the consistency of the
data.
External data record &V1& has the identifier &V2&.
Error message extract from SAP system. Copyright SAP SE.
MN843
- No condition type transferred ?The SAP error message MN843 "No condition type transferred" typically occurs in the context of pricing or condition records in the SAP system, particularly when dealing with sales documents, purchase orders, or other transactions that involve pricing conditions.
Cause:
The error message MN843 indicates that the system is unable to find a valid condition type for the pricing procedure being used. This can happen due to several reasons:
Missing Condition Type: The condition type that is expected in the pricing procedure is not defined or has not been maintained in the relevant master data (e.g., customer master, material master).
Incorrect Pricing Procedure: The pricing procedure assigned to the document may not be correctly configured or may not include the necessary condition types.
Condition Records Not Created: There may be no condition records created for the specific condition type in the system.
Document Type Issues: The document type being used may not be compatible with the pricing procedure or condition types defined.
Configuration Issues: There may be issues in the configuration of the pricing procedure, such as missing access sequences or incorrect assignment of condition types.
Solution:
To resolve the MN843 error, you can take the following steps:
Check Condition Types:
- Go to the transaction code
V/06
(for sales) orM/06
(for purchasing) to check the condition types defined in the pricing procedure.- Ensure that the required condition types are present and correctly configured.
Review Pricing Procedure:
- Use transaction code
V/08
to review the pricing procedure assigned to the document.- Ensure that the pricing procedure includes the necessary condition types and that they are correctly sequenced.
Create Condition Records:
- If the condition type is missing records, create the necessary condition records using transaction codes like
VK11
(for sales) orMK11
(for purchasing).Check Document Type:
- Verify that the document type being used is compatible with the pricing procedure. You can check this in the configuration settings for the document type.
Consult Configuration:
- If you have access, review the configuration settings in the SPRO transaction to ensure that everything is set up correctly for pricing.
Testing:
- After making the necessary changes, test the transaction again to see if the error persists.
Related Information:
Transaction Codes:
VK11
/ VK12
: Create/Change Condition Records for SalesMK11
/ MK12
: Create/Change Condition Records for PurchasingV/06
: Maintain Condition TypesV/08
: Maintain Pricing ProceduresSPRO
: Access to the SAP Customizing Implementation GuideDocumentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MN842
Data record length of external file & incorrect
What causes this issue? External file &V1& cannot be read, due to an incorrect data record length. The data records in the file &V1& ...
MN841
Internal error in management of messages for rebate arrangement
What causes this issue? The program has run up against several messages that are assigned neither to rebate arrangement &V1& nor to the condi...
MN844
Error cancelling current data record &
What causes this issue? An error occurred during the compilation of the reversal document for the cancellation of the external data record with the e...
MN845
Field & has no price determination relevance for subsequent settlement
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.