Do you have any question about this error?
Message type: E = Error
Message class: 1G - BKK: Konditionen
Message number: 628
Message text: The corresponding basis condition does not have a condition item
You have created a markup condition, which references a basis condition
for which a condition header has been created, but no position exists.
Create a condition position for the basis condition first.
Error message extract from SAP system. Copyright SAP SE.
1G628
- The corresponding basis condition does not have a condition item ?The SAP error message 1G628 ("The corresponding basis condition does not have a condition item") typically occurs in the context of pricing conditions in sales documents, purchase orders, or other transactions where condition records are used. This error indicates that the system is unable to find a corresponding condition item for a basis condition that is expected to have one.
Cause:
- Missing Condition Records: The most common cause is that the condition record for the specified basis condition is missing or not maintained in the system.
- Incorrect Condition Type: The condition type may not be correctly configured or may not be relevant for the transaction type you are working with.
- Inconsistent Data: There may be inconsistencies in the data setup, such as missing master data (e.g., customer, material) that is required for the condition record to be valid.
- Pricing Procedure Issues: The pricing procedure assigned to the document may not be set up correctly, leading to missing condition items.
Solution:
Check Condition Records:
- Go to the transaction code VK13 (Display Condition) or VK11 (Create Condition) to check if the condition records for the relevant condition type are maintained.
- Ensure that the condition records are valid for the specific combination of key fields (e.g., customer, material, sales organization).
Review Pricing Procedure:
- Check the pricing procedure assigned to the document type in the configuration (transaction code V/08).
- Ensure that the pricing procedure includes the necessary condition types and that they are correctly sequenced.
Verify Master Data:
- Ensure that all relevant master data (customers, materials, etc.) is correctly maintained and that there are no missing entries that could affect the pricing conditions.
Check for Inactive Condition Types:
- Sometimes, condition types may be inactive or not allowed for certain transactions. Verify that the condition type is active and applicable.
Consult with Configuration Team:
- If you are unable to resolve the issue, consult with your SAP configuration team or a functional consultant who can help analyze the pricing procedure and condition records in detail.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement the necessary corrections to resolve it.
Get instant SAP help. Start your 7-day free trial now.
1G627
Fiscal year start could not be found for bank area &1
What causes this issue? The system could not find a fiscal year for the bank area by using the company code and the fiscal year variants.System Respo...
1G626
Valid-From date is set to fiscal year start &1
What causes this issue? You want to retroactively change conditions after the start of the fiscal year. This is not allowed according to the basic se...
1G629
Create a condition for an account balanced by &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
1G630
Condition category &1 already has a condition until &2
What causes this issue? Create a new condition header for a condition category. Note that there is already a condition header for the condition categ...
Click on this link to search all SAP messages.