Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: VY - Messages for freight processing
Message number: 142
Message text: Pricing procedure &1 does not contain a calculation base diff.from ' '
The costing sheet &V1& only contains condition types that have
calculation base &V1&. This means that no shipment cost sub-items can
be created.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you want to work with the pricing procedure, maintain a condition
type for the pricing procedure that contains a calculation base.
Maintain the <DS:SIMG.SIMG_CFMENUOLSDT_08>pricing procedure</>.
Error message extract from SAP system. Copyright SAP SE.
VY142
- Pricing procedure &1 does not contain a calculation base diff.from ' ' ?The SAP error message VY142 indicates that the pricing procedure you are using does not contain a calculation base that is different from a blank value. This typically occurs during the pricing determination process in sales documents, such as sales orders or quotations.
Cause:
- Missing Calculation Base: The pricing procedure defined for the sales document does not have a calculation base defined for the relevant condition type. This means that the system cannot determine how to calculate the price for that condition type.
- Incorrect Configuration: The pricing procedure may not be correctly configured in the system. This could be due to missing entries in the pricing procedure or incorrect assignment of condition types.
- Condition Type Settings: The condition type may not be set up to use a calculation base, or the calculation base may not be defined properly in the condition type settings.
Solution:
Check Pricing Procedure:
- Go to the transaction code
V/08
to display the pricing procedure.- Verify that the pricing procedure assigned to the sales document contains the necessary condition types with appropriate calculation bases.
Review Condition Types:
- Use transaction code
V/06
to check the condition types used in the pricing procedure.- Ensure that the condition types have a valid calculation base defined. You can do this by checking the "Calculation Base" field in the condition type configuration.
Assign Correct Pricing Procedure:
- Ensure that the correct pricing procedure is assigned to the sales area (Sales Organization, Distribution Channel, Division) in the configuration settings.
- You can check this in transaction code
OVKK
(Assign Pricing Procedure to Sales Area).Test Pricing:
- After making the necessary changes, create a new sales document to test if the pricing is calculated correctly without the error.
Consult Documentation:
- If you are unsure about the configuration, refer to SAP documentation or consult with your SAP functional consultant for guidance on setting up pricing procedures and condition types.
Related Information:
V/08
: Maintain Pricing ProceduresV/06
: Maintain Condition TypesOVKK
: Assign Pricing Procedure to Sales AreaBy following these steps, you should be able to resolve the VY142 error and ensure that your pricing procedure is correctly configured to handle the necessary calculations.
Get instant SAP help. Sign up for our Free Essentials Plan.
VY141
Condition type &3: Access seq. &1 and calculation base &2 inconsistent
What causes this issue? The condition tables stored in the <DS:DE.KOZGF>access sequence</> &V1& contain fields that are not known...
VY140
Shipment costs &1 not saved because they contain no items
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
VY143
Field &3 of access sequence &2 could not be checked
What causes this issue? The field &V3& for access sequence &V2& was not checked by the system. No checking rule has been stored for t...
VY144
Condition type &1: Field &3 of access sequence &2 was not checked
What causes this issue? For condition type &V1&, the field &V3& in access sequence &V2& was not checked by the system. No che...
Click on this link to search all SAP messages.