Condition Type issue

Hi,
i have assigned 3 vendors to one customer master , 1 vendor to another customer master & No vendor assigned to another customer
Vendor partner functions Z1, Z2,Z3
i have created 3 condition Types ZCO1, ZCO2,ZCO3 as a commission Percentage and also i maintained in pricing procedure determination
I maintained the condition record with combination Customer / Vendor 1, Customer / Vendor 2 , Customer / Vendor 3 for 3 vendor like that if 2 vendor for another customer 2 times etc..,
But my problem is if i mentioned the condition type is mandatory in pricing procedure at the time of sales order system will pick automatically if u maintained condition record
But in the above case one customer doesn't have any vendor
My requirement is my commission percentage is fixed for each and every customer & with out entering the condition type manually is there any solution to pick the condition if don't maintain the condition type Required and Manually
please guide me how to solve my issue

Hi Prasanna,
System will consider your condition type as automatic if you have set some access sequence to it. So, it will look into access sequence and fetch the record.
Manual entry setting inside the condition type will allow you to change the value determined (automatically / manually) inside the sales order whereas mandatory option in the pricing procedure will make the system to check the values for the condition type determined / entered before saving the sales order. If there is no value either determined / entered manual (incase of manual condition type), system will set an incompletion log during pricing.
Please let me know if this clarifies your doubt.
Regards,
P Gomatheeswaran

Similar Messages

PO Condition Type Issue

Hi All,
I have encounter a PO condition type issue, hope to get someone to enlighten me.
I have create both cuztomize condition type ZOT2 AND ZOT3.
With config in Control data 1
Cond. Class - A Discount or Surcharge
Calculat. type - B Fixed Amount
Cond. category - B Delivery cost
Group Condition
Select for Group cond. & RoundDiffComp
GrpCond.routine - 1 Overall Document
ZOT2 in header condition should be divided into item via value.
ZOT3 in header condition should be divided into item via quantity.
Both condition type havemanually enter with value 300
In the test PO I have created 3 materials:-
Material     Quantity     Net Price     Item Net
A     100     1,615.00     161,500.00
B     100          16.15         1,615.00
C     1000          16.15       16,150.00
In the Item view calculation for both condition type as stated below:-
ZOT2 - 270.27 : 2.70 : 27.03 (Ratios base on Value 100:1:10)
ZOT3 - 270.27 : 2.70 : 27.03 (Rations base on Quantity 1:1:10) the amount result should be 25: 25: 250 but the result I get from the system for condition type ZOT3 is the same as ZOT2.
Please advise how to reticfy the configuration. Thank you.

Eugenia Foong Pui Mun wrote:
Hi Shiva,
>
> I have try to config with the info you have suggested, but it does not seem to get the expected result.
Hi Eugenia...
I tested scenario with values you have mentioned. It works perfect both ways. Pls follow this....
1. Pls avert the changes I had suggested in my prev reply for changing the condition types. (group condition active, round diff condition & group cond routine, keep them as they are)
2. While you enter value in header with condition type ZOT2. the value gets properly distribute by the ratio 100:1:10 and thats perfect......Now
3. While you enter the values for condition type ZOT3 in the header...Pls note that your Total Qty is 1200 and the total condition value is 300 this means per unit qty the value is 300/1200 =0.25...
Now while you enter the values for ZOT3 in the header, enter 300 in the Amount column and 1200 in the Per column, meaning that the total of 300 shoud be divided into 1200 units irrespective of quantities per Line Item
Now check the results and you will have the distribution ratio 1:1:100
NB:For ZOT3 (Qty base) to work the UoM for all the line items must be similar
Pls check and revert
Regards
Shiva
Edited by: Shivaspatil on Nov 24, 2011 12:42 PM

Tax condition types issue in sales order

Hi Friends,
I am bit lost with the following issue. I have searched sdn and other SAP forums for this. There were similar issues discussed but they didnu2019t solve my issue. There was exactly similar issue but it was unanswered. So I am posting the issue here to get some inputs.
This is the Indian tax scenario. I have configured pricing procedure where I have JVAT and JCST. If the company is selling to customer in the same state where company is located letu2019s say region 05 JCST 2% applicable. If the customer is outside region 05 then 5% JVAT should applicable.
=> In the pricing procedure it was like
150 0 JVAT
160 0 JCST
Both will be calculate on the gross value.
=> I have created two new tax classifications for customer master.
JCST   2   Tax liable outside region 05
JVAT 3    Tax liable inside region 05
So in the customer master I have both JCST and JVAT. I have created a customer with region 05 and in customer master under Billing document tab I have entries like below
Country    Name   Tax Category   Name   Tax classification Description
IN              India        JCST                IN: CST              2                  Tax liable outside region 05
IN              India        JVAT               IN: VAT              0                  Tax Exempt
=> I have created condition record for JCST with the following key combination
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 05
TaxClass1-Cust. -- 2
TaxCl.Mat u2013 1
Amount u2013 2 percentage
Tax code u2013 A1 (TAXINN A1 2% Output tax)
=> With the above condition records maintained for JCST and maintaining tax classification as 2 for JCST and 0 for JVAT, I assume in Sales order SAP should calculate tax JCST 2 percentage. But in sales order SAP is not considering JCST and JVAT. For JVAT it makes sense as it does not have condition records. But I didnu2019t get the reason for not getting JCST. When I checked analysis and click on JCST condition type it says condition record is missing. Surprisingly when I click on the access details it shows u201CTaxClass1-Cust. as 0u201D it didnu2019t show as 2 as maintained in the customer master.
When I change the Tax classification for JVAT from 0 to 1 or from 0 to 3 in the customer master, in the analysis when I click on access details for JCST it shows tax classification maintained for JVAT that is as 1 or 3 so it seems SAP is not considering JCST in customer master at all. Why is that so?
The access (condition table) for JCST and JVAT are same.
Any inputs?

Hai SAP_2006,
We are also having similar requirement and inform the USER to maintain
In our customer master we gave like
Customer master:
Sales area data
Billing documents
JTX1     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX2     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX3     Tax Jurisdict.Code d     1     Full Tax 12.5%
JTX4     Tax Jurisdict.Code d     1     Full Tax 12.5%
To get LST we maintain
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 05
TaxClass1-Cust. -- 1
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A2 (TAXINN A1 12.5% Output tax)
To get CST
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 06
TaxClass1-Cust. -- 1
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A2 (TAXINN A2 12.5% Output tax)
In case if they want CST 2%, then user has to go
Sales order header Biiling
Alt tax Classification : Shouls change the Blank to 2 in the 1 box out of 4.
for that we maintained condition record as
Country u2013 IN
Region of dlv. Plant u2013 05
Region u2013 06
TaxClass1-Cust. -- 2
TaxCl.Mat u2013 1
Amount u2013 12.5 percentage
Tax code u2013 A3 (TAXINN A3 2% Output tax)
This doesn't require to change customer master regularly and default system finds LST or CST 12.5 unless they change to 2% system will not change automatic. So CST 2% Vs CSTfull tax risk is also avoided.
Regards,
Mani

Pricing condition type Issue YPR0--- ZPR1

Hi All,
WE have a pricing issue, for example we have a condition type YPR0 and we use a pricing procedure which i will call ZME600, we are basically creating a new condition type to be called ZPR1 to replace YPR0, now in the copy control, delivery document to billing, for item category YBHP, the price type setting is ''G ''which means copy pricing elements unchanged and redetermine taxes, if we use this option, when we upload new price list, create a billing document, it will change the price on all open sales orders rather than keep the original price, so option is, change the pricing type setting to a ''D'' which basically copies all pricing elements unchanged, will this be a better solution? what happens when we start using new condition type ZPR1 to replace YPRO, the system will no longer recognise YPR0, if there any options to work around this, some have suggested linking YPR0 to ZPR1 in the pricing procedure??

Hi,
Please check V/06 conditiontype functionlality of tht condition type. There it might have been activated for both header level and item level. that is the reason it is printing in both levels. Please do needful setting there..
Regards
Sankar

Pricing condition type issue

Hi gurus,
i have a problem with pricing conditon type. The problem is the Conditon type which i am working as header condition and this condion in header coming correctly. Now the question the same conditon coming in item also why so. one morehting this condition type coming twice in the detail screen. Why so.
thanks & Regards
Ponts will awarded

Hi,
Please check V/06 conditiontype functionlality of tht condition type. There it might have been activated for both header level and item level. that is the reason it is printing in both levels. Please do needful setting there..
Regards
Sankar

Excise duty condition type and Purchase Order Print Issue

Dear Friends,
We have a issue related to Purchase order print out.
We are maintaining TAXINN.
We have implemented CIN and we are maintaining Excise Conditions i.e. Basic Excise in JMOP
In FV11 we are maintaining values for JMOP with plant and material Group combination.
In Purchase Order Tax calculation is happening correctly.
But issue is to find the value of taxes for Purchase Order Print.
We are using function module CALCULATE_TAX_FROM_NET_AMOUNT
and passing values of Company Code, Country, Currency, and Base amount to get the entries in condition types.
But we are not getting any entry even after passing the values.
How we can get these values in JMOP.
Regards
Kant

Why do you want to calculate the taxes during the PO Print when you are getting correct values in PO itself?
Modify your print program with pulling values directly from EKPO/ EKKO Tables and display it to Spool.
check with ur ABAP Person

Condition type price issue

Hello,
I have a item level condition type ZMAT. This condition type will be applicable when you order a material XXX with qty 5 and there will be 10% discount. Suppose we create an order with material XXX and qty 3, still this condition type ZMAT is appearing in condition tab with amount the discount amount as ZERO.
I don't want to appear this condition type in case if the material XXX is having qty less then 5 in an order. Please help me how to fix this issue.
Thanks,
Shreekant

In your pricing routine, check if qty is less than 5 then set sy-subrc = 4.

Issue in using custom discount condition type in pricing agreement at Service Contract line item level

Hello
We are facing an issue while using a Z discount condition type in price agreement at service contract line item level.
A Z Condition type has been created in ECC and assigned to the pricing procedure. This pricing procedure is downloaded in CRM and determined in the service contract.
A condition maintenance group using this Z condition type is created in CRM and assigned to service contract item category.
Condition records are created in CRM for this condition type/condition maintenance group for specific products along with sales org and discount percentage.
But when the price agreement(using this condition type) is used at the item level of a service contract, the system throws errors (related to product/unit of measure and sales org, even though no issues seem to be there)and thus the price agreement is not allowed to be used.
If anyone has worked on such kind of scenario, please get in touch, I will share more details for the same.
Regards
Ankit Arora

Dear Ankit,
Once the pricing procedure is downloaded, please maintain the document pricing procedure at service contract header level, and maintain the customer pricing procedure at business partner sales area billing data.
In spro, maintain the pricing procedure for the combination of sales area, document pricing procedure, customer pricing procedure.
Please crosscheck whether the condition table is active or not.
Regards,
Maddy

Issues with Service Tax Condition Type.

Hi All,
Where in IMG do you define Region. When I am trying to create a condition record for the Condition Type ZSRT Service Tax under the access sequence, Country Plant Region Material.the system throws the following error SDC SAP System Message Workprocess restarted session terminated. Please advise what needs to be done.
Kind Regards
Atul Keshav

I dont think the issue is because of some missing IMG configuration but because of some kernel patch updation which is basis related. You may have a look at a Note 1375494 - SAP system does not start after applying SAP kernel patch and consult with your Basis team.
thanks
G. Lakshmipathi

Decimal issue in condition type

Hi All,
Present Calculation`s
Our SAP system in Sales Order
Mat - xxxx   Qty 12, Price 4,08 with 7,5 % discount
                   7,5% -    0,306
                  Net price -3,774
Calculation - 12 (Qty)*3,774=45,288         It gives 45,29 for invoice amount
Requirement :
customer calculation with 2 decimals
Price       4,08
7,5%        0,31
Net Price   3,77
Should calculate   12(Qty)*3,77=45,24
customer compares 45,24 with 45,29 and gets a difference of 5 cent hence he is not accepting the invoices because of the differences.
How can we make the decimal 0,306 to reach 0,31?
Note : In condition type the rounding rule commericail.We tried all the options but did not yield results. Your help i highly appreciated

Dear Friend,
One option is rounding rule in Condition Type, which is somethimg you have already tried. Just make sure that for all Condition Type mentioned here, the rounding rule is Commercial.
Now the real issue in you case is not Round Rule, but is is realted to Decimal Places.
You can set Decimal places at OY04 (IMG - SAP NetWeaver - General Settings - Currencies - Set Decimal Places for Currencies)
Here you will have to set the Decimal Places to 2 against Currency type (INR incase of India).
But please note that this setting is applicable on Currency & will have impact on all the places where the said Currency is used in system.
Hope this helps...
Thanks,
Jignesh Mehta

Condition type decimal point issue in pricing

Hi
I have a import pricing Procedure as shown
The condition types JEDB and JSED were calculated on 0.16 EUR,
Like JEDB 2% of 0.16EUR= 0.0032
and JSED 1% of 0.16EUR= 0.0016
it is taking the first two digits of the value, ie 0.00 only
Please confirm how to come with the corrected values,
Thanks,

Yes it is intended for TM but you can do the manual changes as recommended in the note and for technical coding, you can copy that logic. Else, have a look at this note:-
Note 38881 - Pricing with different decimal places
G. Lakshmipathi

Currency conversion issue for condition type

Hello,
I am creating two invoice document.
1. Customs Invoice (ZCDS)
2. Inter company invoice.(IVA)
both the invoices should be similar. Same pricing procedure is used to create both the documents but in Customs invoice YUMU condition type is not getting converted whereas in IVA the condition type is getting converted. Can anyone tell me the possible reason for this?
ZCDS
IVA
Regards,
Jagjeet

Hi Jagjeet,
For IVA invoice type -(For condition type- YUMU)
Below highlighted part of code is changing KSTEU from 'E' to 'C' for IVA invoice using std prog RVIVAUFT.
For ZCDS Invoice Type -(For condition type- YUMU)
Program RVIVAUFT is not called since ZCDS is not trigerried using Output type unlike IVA.
Hence KSTEU is not getting updated from 'E' to 'C' in case of ZCDS.
To solve your problem write code in User exit - userexit_pricing_copy to change konv-ksteu to 'C' for YUMU condition type at runtime.This will definately solve your problem.This will ensure you get correct/same condition value for IVA and ZCDS...:)
Regards,
Vikas Mulay.

Issue regarding condition pricing date as system date for some condition types in sales order

Hi
I have already created a sales order on 30.04.2014. Today I am adding new line item to sales order in VA02 transaction. in this order new line items condition pricing date for conditions JEX2,JECX should show as 12.06.2014. But currently it is showing as 30.04.2014. I need condition pricing date as system date for above conditions.
Regards
prashant

Hi
When I am changing pricing date VBKD-PRSDT in sales order header . It is changing the condition pricing date for all. Sales order is created on 04.06.2014. I have added line item 150 on 14.06.2014.
After adding line item 150 , there I have changed the pricing date as 14.06.2014. in sales A tab of item 150. But still it is taking from Sales order header date as 04.06.2014 for all conditions. But my requirement is for line item it should take as system date for some conditions like JEX2,JECX& JA1Y but for other conditions it will take as Order creation date. Please suggest. I have also attached screen shot below. please go through it.
Regards
PK
Sales order header change mode VA02
Here pricing date VBKD-PRSDT = 04.06.2016
Item change mode
I have added new line item 150 on 14.06.2014
Changed the condition pricing date to 14.06.2014 & saved
After saving I have gone to Va02 screen of line item 150
& there I have gone to condition pricing date field from item condition tab
for JEX2 condition type but still here condition pricing date is showing as
04.06.2014 as below.
Condition pricing date
My requirement is like this
For some particular conditions like JEX2 condition pricing date will take as system
date instead sales order creation date when I will add a new item 150 on
14.06.2014.but for other conditions it will show as order creation date for the
same line item 150 .

Issue with new Condition type..

Hi,
I want to create a Condition Type for VAT %, where we can insert value like...
5% on 60% of Basic Price OR
3% on 70% of Basic Price OR
1% on 80% of Basic Price
Note: - We have try with New Tax code and it's working... But through it, we require mew Tax code as per change condition..
That's why we require a Condition Type for variable %...
Please guide...

Hi,
You can do this through two ways.
Option 1
Add new condition type in tax procedure and Make access sequence say with doc type and tax code.
So for old PO's make the variable condition as 100% and for the new ones you need to create that many tax codes.
Option 2:
Write a routine for alternate base that is to be attached in tax procedure. Make a condition type in MM pricing procedure that is statistical and calculates value on base price. Read this base price in the routine. So with this you will not make that many tax codes.
Regards
Sangeeta

Creation of New Condition Type

Hello SAP Folks,
I have one issue related to pricing. See the case is i have to produce an extra cost in the Sales Order which is actually depended
upon the net price. This condition type is percentage based and calculation works in the following way:
Let the new condition type be Z123 and Net price be PR00.
So for year variation 1-2 year, the condition type Z123 will be 1.5 times of PR00
2-3 year, the condition type Z123 will be 2.0 times of PR00
3-5 year, the condition type Z123 will be 3.0 times of PR00
Can anyone throw light on how to configure this condition type ???
Regards,
Sarthak

Hi,
For Z123 Condition type make (V/06)
Cond. class A Discount or surcharge
Calculat.type A Percentage
Plus/minus A Positive
and all other settings are same as Discount condition Type
For making Z123 customize an Discont Condition Type (EX:K004,)
Then while creating the condition record give the percentage as 150% 1-2 yearin valid from and to date,
give the percentage as 200% 2-3 yearin valid from and to date, give the percentage as 300% 3-4 yearin valid from and to date, and save the record. (VK11)
In the pricing procedure For step z123 condition type from which you want the % that is step of PR00 should be mentioned in the FROM and TO column.(V/08)
This will result as per your requirement

Condition Type issue

Similar Messages

Maybe you are looking for