How to Determine Sales Price with Shipping Point in SAP
Introduction
Determining the sales price based on the shipping point in SAP can be challenging since the shipping point is an item-level field, whereas standard pricing structures often reference header-level fields. If you are encountering the error message "access not made" in the shipping point field in sales order pricing analysis, this guide will help you resolve the issue.By following the steps below, you can configure your condition tables, access sequences, and pricing procedures correctly to include the shipping point in sales price determination.
Understanding the Problem
When setting up pricing conditions, you might want to use the shipping point as a key field along with sales organization, distribution channel, and ship-to party. You may have already:- Created a condition table with the required key fields
- Configured the access sequence
- Maintained the condition type and pricing procedure
Why Does This Happen?
- The shipping point field (VSTEL) exists at the item level in SAP but is not available in header-level structures (KOMK).
- The default pricing logic does not recognize the shipping point field for sales price determination.
Solution Approach
To resolve this issue, you need to:- Enhance the structure KOMP to include shipping point.
- Modify the user exit MV45AFZZ to populate the field correctly.
- Create a new condition table with the modified structure.
- Complete the pricing configuration using access sequence and pricing procedure.
Step 1: Append the Structure KOMP
Since the shipping point (VSTEL) is at the item level, you need to extend the structure KOMP to include it.How to Do This?
- Open SE11 (Data Dictionary).
- Modify the table KOMPAZ (this is the include for KOMP).
- Append a new component:
- Field name: ZZVSTEL
- Component type: VSTEL
- Save and activate the changes.
Step 2: Modify User Exit MV45AFZZ
The field ZZVSTEL you just created needs to be filled with the shipping point data. To do this, modify the user exit MV45AFZZ.How to Modify the User Exit?
- Open SE38 (ABAP Editor) and navigate to the include MV45AFZZ.
- Locate the FORM USEREXIT_PRICING_PREPARE_TKOMP.
- Add the following ABAP code:
- Save and generate the changes.
tkomp-zzvstel = vbap-vstel.
Why Is This Step Necessary?
This ensures that the shipping point (VSTEL) at the item level is correctly mapped to the pricing structure (TKOMP).Step 3: Create a New Condition Table
Now that the field ZZVSTEL is available, create a new condition table that includes it.How to Do This?
- Go to Transaction Code V/03 to create a condition table.
- Add the necessary key fields (Sales Org, Distribution Channel, Ship-to Party, and Shipping Point (ZZVSTEL)).
- First, maintain ZZVSTEL in "Condition: Allowed Fields" to make it selectable.
- When selecting the shipping point field, use the Technical View to confirm whether ZZVSTEL or VSTEL is available.
- Save the condition table.
Step 4: Complete Pricing Configuration
After successfully adding the new field and condition table, proceed with the final pricing setup.- Access Sequence (V/07):
- Add the new condition table to your access sequence.
- Ensure that the correct field (ZZVSTEL) is used in the field mapping.
- Condition Type (V/06):
- Link the access sequence to the relevant condition type.
- Pricing Procedure (V/08):
- Include the condition type in the pricing procedure.
Step 5: Test Your Configuration
- Create a new sales order (VA01).
- Enter an item with the relevant shipping point.
- Check the pricing analysis (Shift + F6) to confirm that the shipping point is being considered for pricing.
Expected Outcome:
- The sales order should display the correct price based on the shipping point.
- No more "access not made" errors should appear in the pricing analysis.
Frequently Asked Questions (FAQs)
1. Why is my shipping point not appearing in the pricing analysis?
Ensure that:- You appended ZZVSTEL correctly to KOMP.
- The user exit MV45AFZZ is properly modified and activated.
- The new condition table includes the correct field.
2. Can I use the standard VSTEL field instead of creating ZZVSTEL?
No, because VSTEL is not available in KOMP by default. You must append a new field like ZZVSTEL to use it in pricing.3. Will this customization affect standard SAP functionality?
No, as long as you follow best practices and do not overwrite existing standard structures.4. How can I debug if the pricing condition is still not working?
Use Transaction Code V/05 to analyze condition records and V/06 to check access sequences. You can also place breakpoints in MV45AFZZ and debug the pricing logic.5. Do I need ABAP programming knowledge for this?
Basic ABAP knowledge is helpful, but you can collaborate with an SAP developer for modifying user exits and appending structures.6. Can this setup be transported to another SAP system?
Yes, include all changes (structures, exits, condition tables) in a transport request to move them to another environment.Conclusion
By following this guide, you can successfully determine the sales price using the shipping point in SAP. The key steps involve enhancing KOMP, modifying MV45AFZZ, creating a new condition table, and configuring the pricing procedure properly.This customization ensures that the shipping point is recognized in sales order pricing, eliminating the "access not made" error and allowing for more precise price determination.
For further troubleshooting, consult an SAP pricing
expert or check SAP Notes related to pricing conditions.
