Using RB00 condition type for Price Adjustment

Hi,
I have to do a price adjustment due to some rounding issues in the pricing of my sales order.(Using standard Pricing Procedure RVAA01). I am thinking of using manual condition type RB00 at Item level that can accept both positive and negative values depending on the situation.
If the calculated value>expected value then the user will enter negative RB00 value manually and
if the calculated value<expected value then the user will enter positive RB00 value manually.
The account key is however different in standard Pricing procedure for RB00 and it is ERS and for standard Base Price (PR00) it is ERL.
So, my question is that does that make any difference if I maintain condition records in VKOA for RB00 same as PR00?

Hi
If you are looking for rounding then you round the decimals by not maintaining any decimals.But if it is a price adjustment then your approach is correct
If it is VK11 then there is no need to maintain condition record for RB00 as it is a manual condition type at item level
If you are talking to maintain revenue account determination VKOA then you have to maintain as whenever you give discount then it will hit some G/L account .So you should assign a G/L account also
Regards
Srinath

Similar Messages

Not possible to determine a condition type for the price in ME49

Hi,
While saving the price in ME49 i.e. comparision of Quotation i am getting below error:
Not possible to determine a condition type for the price
Message no. 06657
Diagnosis
When it attempted to generate the time-dependent conditions for the price you entered, the system was unable to determine a condition type. Price determination is therefore not possible.
Procedure
Contact your system administrator.
The latter can maintain the calculation schema assigned to the purchasing document using the Implementation Guide (IMG).
Utsav

Hi Utsav,
You can refer to the following link. it might be useful to you
RFQ price
Thanks
Nisha

V-41 tcode error :Table 304 is not defined for use with condition type PR00

Hi All,
I am trying to create a BDC using the transaction V-41.
The first screen has fields:
ConditionType and Table, where I have to fill values ZPM1 and 800 respectively.
But as soon as I enter the tcode v-41 and say enter, the above mentioned fields are already having the values 'PR00' and ' 304'. Normally if you take an example fo t-code VA02, all fields are blank.
Then an error message is displayed:
Table 304 is not defined for use with condition type PR00
This behaviour is not allowing me to use the BDC feature.
Please advise me on why this is happening. What are the possible solutions I can use to clear these values programmatically?
Can anything be done via customizing?
Regards,
Namita.

Dear ILHAN ,
Well the problem you are facing is having the following solution:
Table 304 is not defined for use with condition type PR00
Message no. VK024
Diagnosis
The selected condition type does not fit in the condition table, that is the basis for the condition record. Alternatively the selected condition type is not included in the condition types that were selected on the selection screen or that are defined in the variant of the standard selection report.
Procedure
Úse F4 help to choose a valid condition type.
If this does not give you the required condition type, check in Customizing for condition types and the related access sequences.
In the condition maintenance also check Customizing for the selection report (pricing report), that you have selected in the navigation tree, using the standard condition table as a reference.
I hope this helps.
It has worked for me.
I gave it a try and what I am getting using the transaction V-41 is create Price condition (PR00) : Fast Entry.
Please award points if you find it useful.
Regards,
Rakesh

Condition type for fee - no change of moving price or balance sheet account

Hi, hope you can help me.
We need a new condition type for a kind of fee which has to be paid to the vendor and used in the purchase order.
This is a condition type which
- has to be part of the invoice
- has to be posted as a kind of accrual
- must not! change the price of the material or the balance sheet account
If we use freight conditions the moving price is changed.
Because it is dependent on the material (and therefore a condition record works great) we can't or better don't want to use a second position in the purchase order.
Does anybody have a solution for this one?
PC

Thanks for the answer!
This is what I already tried, but it still changes the balance sheet account and the moving average price.
This is what I customized:
Condition ZXYZ
Cond. class A
Calculat.type C
Cond.category B
Item condition yes, delelte, amount/percent and Qte relation yes
Scale base C
Accruals yes
In the Calculation Schema it's defined just before the Actual Price, with Statistical-checkbox marked and Account key ZE1, Account key - accruals / provisions ZE2.
Do you have any idea what I have to change or what else to try?
Thanks a lot!

Output generation using condition type for deliveries - emailing output

Hi,
I have created a specific output type using a condition type functionality. The output generates when delivery picking is complete. I need the output to be in email format. However I require the email to send to a specific address, distinct from the email address defined for the ship-to. Which is the best transmission medium to use? Is there any way an external email address can be defined within a condition record? Can an email address be used for the transmission type 7 Simple Mail?
Regards,
Gary

Good Morning,
If you want to send an external e-mail use the medium 5. If you want to
send a mail with SAPoffice than you can not use an e-mail address.
Instead you should use the name of the user (partner who receives the
output).
The medium '7' means internal mail, It was designed for internal use
for that reason you can set up the execution parameters in order to
run directly the transaction.
Another solution could be to reate several partner roles, each partner
with one own email-adress; run output determination several times,
each time with different partner (and email-adress). Although this
increases the amount of master data that has to be maintained.
If you have acess to OSS notes, please refer to the following:
960088     FAQ: Sending SD messages externally
454893     CHECKLISTSD: Sales document output as an e-mail
152474     Testing fax and e-mail
I hope you find this information very helpful and hopefully it will solve your problem.
Regards,
Martina McElwain
SD - Forum Moderator

Which Access sequence will use for sales tax condition type for TAXINN

hi.,
which Access sequence will use for sales tax condition type for TAXINN procedure.pls give one example (Access sequence) and give fields.
Because i couldnot create the condition record,the system not accepted for tax indicator.
Regards.,
lakshmanan

We also got the same problem with our client and escalated it to SAP.
they advised to use the access sequence JIND which consists of condition tables in the order given below
Step Condn Table
10 354
20 355
30 40
Attach this to your condition types.
Rewards if it helps.
Regards,
Anbu

Condition types for Material

Hi,
I have got a scenario where the customer is going to maintain "Z" condition types for a material(1 for sales price and 1 for purchase price). I can read the correct price for this material at the Sales Order maintenance and PO maintenance using some standard function modules
SALES_CONDITION_READ/ME_PO_PRICE_SIMULATION.
as these condition types are maintained in the pricing schema and hence are returned in the correctly.
I have problem when I try to read the purchasing price for this condition type(material) while creating the sales order. Here I have only the material information to read the price. Can anybody suggest how I can read the correct purchase price while creating the sales order.
Thanks in advance.
Best Regards
Malthi

HI Malthi
I would recommend you use BAPI: BAPI_SALESORDER_SIMULATE. This will give you the conditions how the sales order is going to look when itz created.
This BAPI is mainly used for:
1. Checking ATP Qunatities
2. Conditions/Prices
Hope this helps.
Kind Regards
Eswar

MM-PUR default scales for condition types for service (ME31K

Hi,
We have faced the following problem:
The business case was, to have default scales for certain condition types for a service for a purchasing contract.
We didn't find it in SAP, so we wrote an OSS. SAP answered that it's not possible now, nor in the future.
So we decided to look around in SAP, and found out that it was half possible.
I've abused the exit USEREXIT_XKOMV_BEWERTEN_INIT of program RV61AFZB.
In this exit I provide the internal table staffel for program SAPMV13A with the correct information (via ASSIGN ('(SAPMV13A)STAFFEL[]') to <staffel>.)
In this way, if a user adds a service, this exit will get reached and the scales are filled. If the user then clicks on conditions and then double clicks the condition type with the scales, all the default scales are shown to the user. If you then click on save, the next screen is the service screen, if you then click on save again, all the date is stored in the database. (bit of a work around, but this works)
However, I can't figure out how to save the scales data, when you only add a service and then push the save button without viewing the conditions. Quite logically actually because I'm skipping two whole screens with pbo and pai modules, in these modules internal converting takes place.
Has anyone encountered this problem before and how did you solve it then ?
Alternatively what is the SAP standard way to add pricing condition scales on condition types of a service of a purchasing contract? As you know there is no BAPI yet to change/create a purchasing contract.
I was thinking, to add the scales by updating the tables directly via ABAP, I know that's not a clean way to do it, although it isn't too risky.
Kind regards, Rob Dielemans

Dear Rob,
Is this solution properly working for you?
I think my problem is similar: purchasing outline agreement (contract) refuses to apply relevant scale prices in the item line. Always uses the first price - without considering order quantity depencies.
Regards,
Tamás
Edited by: Tamas Szabo on Mar 31, 2009 3:50 PM

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
In rounding rule 'B', values are always rounded down:
1045.9 -> 1045 LIT
1045.1 -> 1045 LIT
In this example, the currency of the condition rate is Italian Lira. The Italian Lira does not have any places after the point.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Using Cumulative Condition Type KUMU

Dear SAP Gurus
I have a requirement here that when a packaged item is sold with some accessories, the order confirmation and billing output should only showed the total price on the main item. We are not using sales bom for this purpose.
For example in SAP order entry screen:
Line 1      Main item   net price $100
Line 2      accessory   net price $ 20
But on billing output to show:
Line 1      Main item   net price $120.00
Line 2      accessory   net price $    0.00
I am planning to use KUMU condition type to capture all the total net price of the 2 items into line 1.
Is it normal for KUMU to be determined at the sub items as well ?
Any ideas on how we could control the output print logic ? i.e to print only the KUMU condition type on main item if it exist.
Thanks

Hi friend,
As per my information KUMU is a cumulative condition. If you have sales BOM and if you carry pricing for the sub items and if you want to display the main item in the invoice with the price. This condition can be used to cumulate the sub item price and display it at the main item level.
I think this might be given you a idea of this condition type
As pe my knowledge...
The standard system condition type KUMU facilitate us to display the total of the net values of an item and all the sub-items belonging to that item.
Line: -
Constraints OF KUMU cumulative condition type -
Cumulative conditions cannot be used as header conditions and processed manually.
When we copy a S O (sales Order) to a billing doc, the condition rate and the condition value of a cumulative condition is Freez. This means that the condition is not redetermined when it is copied regardless of the pricing type. The net value of the total is not redetermined even if the individual net values have changed.
as already suggested KUMU condition is used as item condition.This is a statistical condition and alternative calculation type is 36.The item should be higher level item and prices of all lower level items assigned to this higher level item are cumulated.
Regards,
Rajeev Sharma

List of sales condition types for a material

Hi,
I have a material and maintained pricing and discount condition types for that material. I guess VK33 helps to view what condition types maintained for that material.
However when I tried VK33 and selected the material from the conditions from the node on the left hand side and entered the sales org, dist. channel and material and executed after I clicked on the display icon on the condition type, Sales org, Dchl material no conditions are displayed.
Please let me know how I can view the list of sales condition maintained for a specific material.
Thanks.

Hi Giri,
Thanks for the response.
In VK13 I should enter the condition type then I can hit condition information so that the details of all records maintained for a specific condition type will only be displayed but not for other condition types.
In V/LD, I am getting the list only for individual prices. If I insert 17 u2013 Discounts and surcharges by customer or 18 u2013 Discounts and surcharges by material, I am unable to get the list. Is it anything because of the u2018release statusu2019? We had not checked the u2018release statusu2019 field for the tables assigned to access sequence for the condition types.
As per the requirement business wants to view the list of u201CDiscounts and surcharges by customer/materialu201D. I think this is possible if I run the report provided by inserting values 17 or 18 but the unable to view the list. Any config settings required to activate?
Please let me know how to view the list of condition types.
Thanks

New Condition type for pricing

Hi,
I have a requirement wherein I want to create new condition type for add on cost of material with manaual entry . this condition is to be given in inforecord.
How to proceed? also, this contion type to be inserted in pricing schema??

Dear Smitha,
You may ask what is the condition type?
For example:
- discounts, surcharges or tax taxes add to net price
- delivery costs, cash discounts add to effective price
Discounts or surcharges may be percentage based, quantity dependent, or absolute.
Best Regards,
ian, Wong Loke Foong

Z condition type for surcharge need to be displayed in billing doc only.

Hi ,
I am having going to create condition type for surcharge, this condition type need to be diplayed only in billing doc.condition value should be calculated based weight of the material in delivery doc and scales in condition record.
scales values are as below:
Access key:
sales org/dis channel/ route /sales unit(KG)
DE10/02/DETX1/   1 Kilo   =   30 u20AC
skales:
DE10/02/DETX1 / 31 Kilo = 35 u20AC
DE10/02/DETX1/ 41 Kilo =   40u20AC
DE10/02/DETX1/ 51 Kilo =   45u20AC
then for 52 Kilo we have price for these item with 52 Kilo = 45 u20AC
where exactly need to do the config and development changes for displaying in condition type in billing doc only.
Thanks in advance.
Regards,
RAM

In the Pricing Procedure , maintain requirement as 24 against the Z Condition type.Now it will reflect the value only in Billing Document.
Best Regards,
Ankur

Condition type for deduction in service purchase order

Hi All,
Our client has scenario where in transport service Purchase order, client wants to deduct some part of amount as a security fund.
E.g client takes transport service from vendor amounting Rs. 1000 and client deducts Rs. 10 as a security fund so payment to vendor is Rs. 990. This deduction amount should go to separate GL.
Kindly let me know how can we map this scenario? I guess we can do this with the help of condition type but dont know from where to start and what will be the nature of condition type.
Thanks in advance.
Regards,
Nisha.

Hi
What client is going to do with security deposit? Do they settle over a period of time?
Based on that you can do the config setting.
Case 1) Retaining of security deposit.
If client is not paying back and wants to keep the security deposit. They Wants to have track record of the same. Then you can use Z condition type by copying R002 discount using M/06 and assign GL in OBYC for that condition type.
Case 2) paying back security:
Create Z condition type by copying any freight condition and assign GL in OBYC
While creating PO use condition type.
While repayment of security deposit FI will use same GL as Db and vendor account as Cr using F-44.
Rgs

Problem with multiple condition type for VAT &CST

Hi,Gurus,
pl. suggest the procedure for the following problem.we configured seperate pricing procedures for our product material and scrap material.We have configured same condition types for VAT(ie.condition type:ZVAT) and CST(cond type:ZCST), in both pricing procedures. Now We want to maintain seperate condition types for VAT and CST for pricing procedure for Product material and Scrap material. I have created two new condition types for scrap sales ZSCT- cst for scrap and ZSVT-vat for scrap by copying the same from existing conditions ZCST & ZVAT, and the same is included in the scrap pricing procedure. And also maintained OB40,OBCN,OVK1,OVK3,OVK4, FTXP,FV11 and VK11.
now I am facing the following problems.
1. while creating the Material master & customer master, in tax category sub screen all conditions i.e. conditions defined for product material( ZCST,ZVAT) and defined for scrap material (ZSCT, ZSVT) displaying and these are compulsory fields.
2. While creating the sale order for scrap material, system is considering the TAX classes from ZVAT/ ZCST (defined for product material) and taking the condition value from the condition type ZSVT/ ZSCT with the TAX class values of ZVAT/ZCST.
Now I would like to know is there any procedure to assign the Material type and Customer Account group to Tax category.
Thanks & Regards
sam

Hello Sam,
The Access Sequence Assigned to your New Condition types ie, ZSCT and ZSVT are same as the Previous Condition type ZVAT and ZCST.
After Adding new condition type in the Tax category in the Masters you have to take care of the Sequence of the Condition type.
If ZSCT and ZSVT is on the 3rd and 4th number in the masters the Condition table you are using in the access sequence should have fields Taxclassification3-Customer and taxclassification3- material. For ZSCT
Likewise Taxclassification4-Customer and taxclassification4- material. For ZSVT
Please add New Condition table in the access sequence with the required Field
And next when you are maintaining the condition record for say ZSCT you will have to maintain condition record for the condition table which has Taxclassification3-Customer and taxclassification3.
In Document the values will be flown correctly after changing this.
Hope I have Solved your Query.
If any Doubt please revert.
Regards,
Rohit Dongre

Using RB00 condition type for Price Adjustment

Similar Messages

Maybe you are looking for