on 03-28-2008 2:53 PM
Hi
As per client requirement I am using Shipping Point for Pricing, (Appended KOMP structure added shipping pt feild)
But while creating Sales Order firist I am entering Material, then user will enter Plant, So system is not identifing Shipping pt and Condition record is not accessing. If we enter Material & Shipping Pt Condition record is accessing. but it is not possible to user to enter both at a time
(Plant will be determined at the time of Sales Order we can't give at Customer Master).
Is there any solution
Plz guide me
prasad
Mainatin Shipping Point Determination - Shipping Condition of customer / Loading group of Material/Plant and the shipping Point in SPRO-IMG- LE-SHIPPING-BASIC SHIPPING FUNCTIONS-
You mentioned that Plant will be determined during Order Processing and is it going to be different than the plant mainatined in the shipping point determination. If thats the case then we will have to maintain for all combinations in the Shipping point determination.
Regards
SAI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
May be you can address the requirement during the Document save.
Else there is a very long process of - create a condition table with customer-material-shipping point
Then add this table as the first one in all the required access sequences- exclusive indicator checked.
then it will default into your order processing. But thats a very lengthy process and if shipping point is not in the allowed fields - u will have to add it to the field catalog. Adding new field to field catalog-
I shall give an example. But you should first identify the field for Profit Center (Design ID) and then do as follows:
For example if you want to use field PSTYV (Sales document item category) that is included in structure KOMP (Pricing Communication Item) as a key for a condition table.
When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
Prerequisites:
For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG (Allowed Fields for Condition Structures).
To solve the problem, proceed as follows:
1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, ZZ - sales document item category and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
Component Component type
ZZPSTYV ZZPSTYV
Save, check and activate the change you made.
3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
4. Call up Transaction SPRO. Navigate to Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control and execute Define Condition Tables. Choose Conditions: Allowed fields and include ZZPSTYV as a new entry.
5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.For header fields, use structure
KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
For more information, see Transaction SPRO via the path Sales and Distribution -> System Modifications -> Create New Fields (Using Condition
Technique) -> New Fields for Pricing and Note 21040.
Hope this is helpful
rgds
Sai
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.