on 03-17-2015 8:11 AM
Hi Group
In our shipment cost pricing procedure some conditions may be set as inactive due to subsequent conditions. For the inactive conditions indicator is set as Y...i.e KINAK=Y(Inactive because of subsequent price). This works as intended.
However when conditions are transferred to SD billing, inactive conditions in shipment cost document are transferred/copied as active conditions and KINAK is not equal to Y.
This inflates the shipment cost in billing.
Any thoughts on what might be wrong here..
Many thanks
A
Hi,
I am not sure I understand when you say with standard config shipment cost cannot be pulled into billing. We relied on this a lot : http://help.sap.com/saphelp_45b/helpdata/en/5f/e411bb044411d2bf5d0000e8a7386f/frameset.htm
Here is some condition configuration info
Application | Condition type | Condition class | Calculation type | Condition category | Manual entries | Group condition | Header condition | Item condition | Group cond.routine | Scale formula | Plus/ minus | Amount/ percent | Value | Qty relation | Calculation type | Delete | Calculation Base | Matrix maint. | TextDetermProcedure | Text ID |
F | Cond1 | B | B | F | X | X | X | 0 | 0 | X | X | X | X | X | B | |||||
V | Cond1 | A | T | F | C | X | X | 0 | 0 | X | 02 | 0001 | ||||||||
F | Cond2 | B | T | F | X | X | X | 0 | 0 | X | B | 1 | ||||||||
V | Cond2 | A | T | F | X | X | 0 | 0 | X | X | 02 | 0001 |
Also this is what I see upon clicking cond1 which is inactive in shipment cost and active in billing
Double clicking condition 1 in Shipment cost pricing shows below | |||||
Condition class B Prices | |||||
Calculat.type B Fixed amount | |||||
Condit.category F Freight | |||||
Cond.control A Adjust for quantity variance | |||||
Condit.origin A Automatic pricing | |||||
Inactive Y Inactive because of subsequent | |||||
Group condition Yes |
Double clicking condtion 1 in Billing shows below | |||
Price Source F | |||
Condition class A Discount or surcharge | |||
Calculat.type B Fixed amount | |||
Condit.category F Freight | |||
Cond.control E Condition value and basis fix | |||
Condit.origin A Automatic pricing | |||
Group condition Yes | |||
Statistical Yes |
Pl do let me know if further information is required.
Thanks for your time
A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhijit,
I am sorry, but I have to say that this process works as designed.
The price source functionality, maintained in copy control, will copy
the condition records from the shipment cost document if the condition
type was also maintained in the pricing procedure of the invoice.
In the invoice you have a different pricing procedure and according to
this pricing procedure it will be determined again in the invoice, where
the inactive flags (here KINAK = 'Y') have to be placed.
In the invoice there is no reason to determine the KINAK = 'Y' for
condition type Cond1.
One possible solution could be to maintain an exclusion group for pricing
procedure in billing, if you want to inactivate condition type Cond1.
The condition group funtionality can be found in customizing:
SPRO: Sales and Distribution
-> Basic Functions
-> Pricing
-> Condition Exclusion
-> Condition Exclusion For Groups Of Conditions
Regards,
Alex
Hi Alex,
Thank you for your reply. After evaluating we feel condition exclusion would not work when shipment involves legs/stages.
E.g. Delivery contains only a single item. Shipment has 2 stages and hence pricing will be carried out for both stages.
For 1st stage ... Con1 Inactive Value 100 Cond class-B
Con2 Active Value 50 Cond class-B
Con3 Active Value 10 Cond class-A
For 2nd stage ... Con1 Active Value 200 Cond class-B
Con2 No record found
Con3 Active Value 20 Cond class-A
In billing we expect the same to appear as the solution as claimed by SAP is Stable but we get as below which is wrong first line below is active
Con1 Active Value 100 Cond class-B
Con1 Active Value 200 Cond class-B
Con2 Active Value 50 Cond class-B
Con3 Active Value 10 Cond class-A
Con3 Active Value 20 Cond class-A
Total shipment cost overstated by 100.
If condition exclusion is used then the result would be as below and 2nd line would be set inactive incorrectly.
Con1 Inactive Value 100 Cond class-B
Con1 Inactive Value 200 Cond class-B
Con2 Active Value 50 Cond class-B
Con3 Active Value 10 Cond class-A
Con3 Active Value 20 Cond class-A
Total shipment cost understated by 200
So even this solution is not working.
Is there any other approach to the scenario mentioned above?
Thanks
Abhijit
Hi Abhijith,
In this case, which condition value you consider for shipment cost..? the value which ever is lower or the value which ever is higher..?
Do you always have a fixed rule for this?
If so, condition exclusion will work, you have to chose the correct exclusion procedure option in that (example " the least favourable ').
Regards
Jobi
Hi Jobi,
We do not have a preference based on value (like least/most favorable). As explained in the example earlier, we have a few conditions with condition class B-prices. If there more than one condition of this type in pricing then system activates only the latest condition and de-activates other which is irrespective of value.
It would have been much simpler for me to work with condition exclusion had business process used least/most favorable condition but that is not the case.
Thanks
Abhijit
Hi Abhijit,
In such case, I'm afraid that the standard condition exclusion function cannot fulfill your requirement.
You may have to consider to implement your own logic in the userexit to affect xkomv-kinak for the relevant shipment cost condition.
You can have a try with USEREXIT_XKOMV_BEWERTEN_END(RV61AFZB).
Regards,
Alex
From your post, it is very difficult to understand the issue. You also need to explain what configuration / Condition Class you have for shipment cost condition type and pricing condition type. Also with the standard configuration, you cannot fetch the shipment cost to billing document. There should be some user exit in place which you have to find out what logic is written there.
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
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.