Requirements in pricing

Dear Gurus
in our scenario we have TAX caliculation on MRP in some cases and on Stokist price in other cases
and further, whenevr it is Tax on MRP even the Free goods are considered for Tax caliculation.
unlike this If it is tax on PTS free goods are exempted for TAX caliculation.
we have defined different condition types for all above. we have called requirement '2' (Item with pricig') agaist Tax conditoion 'JLST' in pricing procedure. whre as for ZVAT(MRP based TAX condition) type no requirement has been called.
but now we need ZVAT(MRP based TAX condition) to neglect Free goods in (Chattisgud state).
can some body tell how can we make this condition behave in two ways
Regards,
Jim

If you are using a same document type for free goods then you are left with the item category to pick up a specific Tax Code which will have a 0% rate which can automate the process. You need to add an access in the access sequence which you are using for ZVAT where you need to have an item category as one of the parameter. Since item category is not in the standard pricing field catalog so you need to have the following enhancement:
a. Call the ABAP Dictionary (transaction SE11) and create the data type ZZPSTYV. Select PSTYV as the domain. As the short description, you can use 'ZZ - Sales Document Item Category' (for example) and as the field labels, you can use the field labels of the data type PSTYV. Save, check and activate your entries.
b. In the ABAP Dictionary (transaction SE11), enter the structure KOMPAZ, switch to change mode and make the following entries:
Component Component type
ZZPSTYV ZZPSTYV
Save, check and activate the change.
c. Note: Due to the changes in the structure KOMPAZ, the field ZZPSTYV is now known in the structures KOMG and KOMP because the structure KOMPAZ is included in both structures.
d. Call transaction SPRO. Go to 'Sales and Distribution > Basic Functions > Pricing > Pricing Control' and execute 'Define Condition Tables'. Select 'Conditions: Allowed fields' and enter ZZPSTYV as a new entry.
e. Note: When you create the condition table Axxx, you can now use the field ZZPSTYV as a key field.
f. Populate the new field you defined by including the following source code line in the user exit USEREXIT_PRICING_PREPARE_TKOMP:
MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
In order processing, the user exit is available in the include MV45AFZZ, and in billing document processing, it is available in the include RV60AFZZ.

Similar Messages

Requirement in pricing procedure

whta is the use requirement in pricing procedure? gurus please explain me briefly?

Hi Durga,
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
o Go to T.Code: VOFM. - Maintain Requirements & Formulas
o Click on the "Requirements" in the top menu and then click on "pricing".
o We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
o And we assign the application type like V - Sales/Distribution etc.
Hope this info has been useful.
Rgds,
Aram K.

Requirment---In Pricing Procedure

Hi,
Please explain what is meant by Requirement in Pricing Procedure.
Explain specifically about 6 and 17 requirement(Cond.exclusion <>'X' and Cash disc.in purch. respectively)
Will reward.
Regards

Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing".
We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.

Requirement for Pricing - When region is AR

Hi Gurus!
I have done this before so wanted to get some help on this "Requirement for pricing". I need to create a new Pricing requirement . Basically a new condition table A123 has been created for Access Sequence ZSDR and I was asked to create a new requirement for pricing for sme which teh SD people would fill the requirement number that I create in that. This required for a partcular region "AR', which I believe is that when the region is 'AR' this prcing requiremnt should folow. I am not sure at all as how to go about and would require you help if someone has done tihs type of thing before.
The details that I ahve been given are as follows:
Key conbination : Sales org/ material group 4/Customer
Below are the required fields for this transaction
Sales Org u2013 CA03
Material Group u2013 ZTR
Valid On u2013 defaults to todayu2019s date
Customer
I need to create a new Pricing requirement with this. Could someone please help me out with this?
Thanks,

I have been able to create a new requirement under the pricing and numbered it 927. Then I activate it and after that I ran the program RV80HGEN to activate all the routines. It says there is no main program for the routine RV61A927. I even checked the include program RV61ANNN and it does show my new routine there but above that it does not show in the Function tgroup that it exists. Is there a way I can activate it or include it so that it gets attached to the main program?
Thanks

Do Intel iMacs Require High-Priced UPSs?

I'm in the market for a UPS for my new iMac. I've never used one before, but I've experienced enough power glitches to now "graduate" from my trusty old surge suppressors.
In the past, I've leaned towards APC surge suppressors, so I decided I'd look into APC UPSs. In doing my homework, I came across a rather interesting, and potentially disturbing, thread
(see <http://forums.macworld.com/thread/100654?start=0&tstart=0>). Essentially (if it's correct), when selecting a UPS, one can't simply go by the power ratings in the specs of our
Macs (they end up "understating" (in effect) the size of the UPS you will need). More of a concern, however, is the possibility that the Intel Macs may be a bit "too quick" for any of the
"standard" UPS models (i.e., those based on the lower-cost, offline-technology designs, usually employed by UPS manufacturers for the home-computer/small-office market),
and require one of the "premium" models (i.e., those based on the higher-cost—often,
significantly higher-cost—line-interactive or online technologies).
Has anyone had any experience that would support or refute this?

You all seem to be calling upon your previous experience with APC products. And while I agree that experience is a great teacher, I’m not so sure how much of the experience you are relating is really relevant (i.e., the use of APC UPSs with recent-vintage Intel Macs). Quite frankly, I’m also not sure whether enough time has elapsed for the alleged issues raised by the APC tech to actually become issues for a lot of Mac users.
So, was the tech “full of it,” and simply trying to “sell” the APC customer—who had contacted APC for tech support regarding his 3-month old UPS—or was the tech honestly trying to help the customer? And if the latter, did he know what he was talking about?
My own experience with APC (limited as it is) combined with what I’ve seen and heard other folks say about the company, and the company’s overall reputation in the marketplace suggest that the tech probably was not trying to get the customer to needlessly buy a more-expensive unit. That leaves us with the question: Did he know what he was talking about?
The tech made 2 specific clams: One relating to power requirements, the other to transfer-time requirements. Everyone here seems to be focusing on power requirements, so let’s try to pass judgment on that first.
_Power Requirements_. The tech made the following statement:
+Apple uses Power Factor Corrected power supplies in their computers. When we+
+size a UPS for a computer with a Power Factor Corrected power supply, we+
+multiply the watts by 1.25. So, for the purposes of choosing a UPS for your+
+Mac, we would use a wattage of 280W x 1.25 = 350W. This would exceed the+
+watt capacity of the BE550R which can handle a load of 330W. I will place a+
+link here to a document that describes Power Factor Corrected power+
supplies.
He then provided the following link to a document located in the APC Knowledge Base:
<http://nam-en.apc.com/cgi-bin/namen.cfg/php/enduser/std_adp.php?p_faqid=8883&p_created=1193079387&p_sid=JU8cSF2j& p_accessibility=0&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd1 9jbnQ9NCZwX3Byb2RzPTAmcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2 VhcmNoX25sJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9cGZj&p_li=&ptopview=1>.
The document certainly seems to be “authoritative” in its discussion of “power factor corrected” power supplies and the Government’s updated Energy Star requirement (Energy Star 4.0, which took effect in July 2007—see <http://www.energystar.gov/ia/partners/fed_agencies/estar40.pdf>) that such power supplies be used in computers (e.g., desktops, notebooks, workstations, game consoles, and servers). So unless the document is wrong, or unless the tech is wrong about Apple’s compliance with Energy Star 4.0, it appears that the tech’s statement regarding the BE550R’s ability to handle the potential load of the customer’s post-July 2007 24” iMac is correct.
_Transfer-Time Requirements_. The tech claimed that Intel Macs require a transfer time of 4-5 milliseconds but that the APC Back-UPS series (which includes the BE550R) has transfer rates of 8-10 milliseconds. He indicated that this mismatch may very well have been a contributing factor to the sudden spurt of daily shutdowns that the customer had experienced. He put it this way:
+However, there is another consideration. Macs are more sensitive to power+
+fluctuations than comparably sized PC's are. My assumption, based on the+
+information provided, is that the BE550R may have been having very brief+
+transfers to battery caused by harmonic distortion in the input power. This+
+type of distortion is common and is not normally a problem. But, when your+
+UPS transferred to battery, one of two things probably occurred. Either the+
+overload issue caused your Mac to shutdown or the transfer time from on-line+
+to battery caused the Mac to shutdown. The BE550R, being a Back-UPS ES, has+
+a transfer time of around 8 - 10 milliseconds. The BR units have a transfer+
+time of 4 - 5 milliseconds. We have noticed that Macs need a quicker+
+transfer time than this. For this reason, we now recommend a Smart-UPS for+
+all Macs. Our UPS configurator is being updated to reflect this+
+recommendation. A Smart-UPS has a transfer time of 2 - 4 milliseconds which+
+works well with Macs. So, to make a long story short, we would recommend an+
+SUA750 for your Mac.+
He was clearly somewhat more tentative about this transfer-time requirement than he was about the power requirement. And I have yet to see any changes made to the APC website to reflect these new “requirements.” Nevertheless, his presentation seems “reasonable,” and certainly doesn’t come across as a “sales job.” From a user perspective, I just hope it’s a matter of a thoughtful tech pointing to a technically possible issue that may never be of real practical concern.

Pricing - VOFM requirements

Hi,
I have a requirement routine assigned to 10 differentcondition types in the pricing procedure. Now there is a need for adding an additional check which has to be added in the same routine for 3-4 specific condition types in that. When I put the code its getting executed for all the 10 condition types against which the routine is assgined. So here i want to find out each time the current condition type also for which the rouitne is executing.But in the run time, i couldnt find any work area of variable which provided the current condition type which is calling the routine. the itab tkomv is available, but it contains all the condition types..
Anyone has an idea how to solve this ?
Thanks,
Dinu.

Copy your requirement into a new requirement and configure the new requirement in pricing to those 4 pricing conditions where you need this additional check. Just so that you do not double maintain the code call the original requirement from the new requirement, check return code and perform only addtional validations in the new requirement. This way any modifications made to the original requirements would also apply for new requirement. Better way of doing things rather than figuring out via code when do go with validations.
Thanks

2 pricing procedures for the same sales area

Hi Gurus.,
              My client requirement is the client requires 2 pricing procedures for the combination of Same sales areaDEocument Pricing procedurecustomer pricing procedure in OVKK
He doesnt want to use new sales area or new document pricing procedure or new customer pricing procedure,I know that in standard SAP it is not possible.
Can any of the gurus throw some light on this.Some work around is required here,So can u please say the required changes in Standard functionality.
Thanks & Regards
Narayana
Message was edited by:
        manam narayana
Message was edited by:
        manam narayana
Message was edited by:
        manam narayana

Hi Gurus.,
               First of all thank you very much for giving me so tremendous response, But my client requirement is,
              He has one customer and for that customer when raising an order ,for some orders Tax shouldnot caliculate and for some orders Tax should be caliculated,
        For example : If he gives price 100,Then the base price should be 100,For some orders he gives price as 130 rs which is inclusive of tax like 110 should be the base price and 20 rs tax should get caliculated
           So i have tried in the pricing procedures and we have standard pricing procedure RVAA01 & RVAB01 ,In which RVAB01 is the price inclusive of tax procedure,We can assighn different pricing procedures if any of the combination in OVKK is changed,But he dont want to change the combination in OVKK.
        So client asks now when he raise an order he decides how the price should be caliculated, i.e the price may be he give price or price inclusive tax,of which the pricing procedure should automatically split the tax and price accordingly,He is asking in the way like when we raise a sales order we should do like a pop up box should appear asking which pricing procedure should be selected,So on selecting the pricing procedure the order should caliculate based on the selected pricing procedure
Thanks & Regards
Narayana

Pricing procedure mm Packing and forwarding to be calculated on Basic price

Hi experts
we are having one pricing procedure where in details are as follows.
basic price                                                 100
excise                                                           12.36
total                                                             112.36
P & F 2 % 0n (112.36)                                   2.24
total                                                             114.60
Vat 5 % 0n (114.60)                                       5.73
Grand total                                                   120.33
Now we require new pricing procedure wherein Packing & forwarding to be calculated on basic price & not on basic + excise
so can we change in same pricing procedure or we have to create new ?
Can you elaborate with the configuration steps ? Any changes required in Tax procedure also or not ?
Thanks in advance
regards

Hi,
No need you can add the condition type to the pricing procedure at spro--mm---purchasing--pricing procedure ---calculation schema with proper calculation to get the percentage on base price and add to the total .
Regards,

Pricing procedure execution...

Hi Folks,
How SAP reads the pricing procedure..
Example
Con.Type      Requirement        Routine
ZSAA            601                     901
ZSAB            602                     902
Doubt 1: -Is system reads this pricing procedure line by line or coulmn by column?, In the debug we noticed it goes column by colmun? why?
Doubt 2: - I want to know the value found for ZSAA during the execution of 602 requirement. Example scenario is if ZSAA is more than 100$ don't execute ZSAB.

Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.

How to Avoid Duplicate Pricing Condition Types In Sales Order and Billing

Hi SAP Gurus
I have a requirement in Pricing (Sales and Distribution). We have issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
I want make them inactive duplicated Condition type in Sales order and Billing Documents.
Please advice me how to make inactive status to duplicated Condition types
Thanks in Advance.
Ravikanth

Hi
You can use Exclusion Group
You can define 2 Groups and include 1 condition type in each
and define exlusion procedure
A   Best condition between condition types
B   Best condition within the condition type
C   Best condition between the two exclusion groups
D   Exclusive
E   Least favorable within the condition type
F   Least favorable betweent the two exclusion groups
you can use Exclusive to set your condition type or as per your requirement
Regards
Jitesh

Pricing Condition type controls- Formula and condition records

Hello experts
I have one question in pricing.
Is it possible to determine the value of a single condition type by means of the maintained condition records vs a formula depending on the scenario?
Eg- In my case for the requirement is:-
If in my sales order the item category is X or Y then i need to use the condition records to determine the value of the condition type say ZCON but if the item category is Z then i need to use a custom formula?
Can this scenario be achieved using only one condition type with the appropriate formula or do i have to maintain separate condition types to achieve it?
Thanks for your inputs.

I believe it can be achieved with the single condition type. Since the routine assigned in the Requirement in pricing procedure controls the system's access to condition records...create a new VOFM routine which should check the item category and if satisfied, the condition records will be accessed.
If the requirement fails and a value is not determined, the routine in the alternate calculation type should handle the calculation (based on PR00 value etc.,) and determining the value for this condition type. If not possible this way, should be able to handle this requirement through a userexit.
Your condition type should be configured allowing both automatic and manual entries.
This is just a wild guess.

Pls help in MM Pricing procedure?

Dear Gurus,
clients wants to implement one new condition type "exmn" to sto pricing proc "xm1000".their requirement is as below:
Additional condition is required to implement minimum excise tax calculation:
"exmn" - Excise Tax Minimum
Condition exmn should not be mandatory as the same pricing procedures are being used for Lithuania, Latvia and Estonia, but minimum excise tax calculation rule is not applicable for Lithuania.
System should check, if minimum excise tax is required (if it was defined).
If the result of the standart excise tax calculation is lower than minimum excise tax rate, then "exmn" is applicable for the product and condition "exmn" will be used.
kindly guide me...is ROUTINE required in pricing procedure?
Pls help..

Pls look into this issue gurus and provide ur valuable suggestions..

Pricing condition table and condition type question

hi guys,
We can use same condition table in pricing for multiple condition types.I am wondering how system knows which condition records should be applicable for which condition type in the same table.
I know the structure KOMV has those details,but thats used during the run time.
Do we have database table which preserve this relation /link ? Please help.
I also would like to know the tables / fields /structures which can be used at run time for defining requirements in pricing procedures.
Thanks
Dona

Hi,
Condition types are assigned with access sequences.
These are the determining sequences in order to select which condition table is to be selected for that particular scenario.
Generally the access sequences are tested to the condition records on their priority basis.
pricing procedure
condition type
access sequence
condition table
selection records.
hope this would help you understand the concept.
regards,
Siddharth.

Dectivate pricing condition for sales order not service order.

Hi,
We are on ECC6.0 and CRM5.0
I need to add new condition type to the existing pricing procedure.It should be activtaed only for service orders and not for sales order.I can achive this by adding new requirement in pricing procedure to limit this condition type based on order type.
Example: if KOMK-AUART eq ORDER_TYPE.
sy-subrc = 0.
But I don't want to do this,because I would need to change this requirement everytime I add new service order type.
Is there any field in Pricing structure KOMK bu using which we can achieve this. ?
Please suggest any other idea by which I can achieve this
Thanks
Dona

Currently ,we have one pricing procedures for both the scenarios...
We control if the perticular condition type to be active or not by writing a requirement which checks the order types.
This has been done this way because we built the pricing procedure in ECC and tranfer it to CRM.Also we donot have service orders in ECC.
any further alternatives guys..

Pricing for Domestic , imports and service

We have following scenarios:
Domestic purocurement.
1. Purchase of Consumables, Excise duty credit taken (Cenvetable)
2. Purchase of Spares, Excise duty credit taken (Cenvetable)
3. Purchase of Services, Service tax credit taken.
4. Purchase of Consumables, NO Excise duty credit
5. Purchase of Spares, NO Excise duty credit
Imports.
1. Purchase of Consumables, Import duty credit taken (Cenvetable)
2. Purchase of Spares, Import duty credit taken (Cenvetable)
3. Purchase of Consumables, NO Import duty credit
4. Purchase of Spares, NO Import duty credit
I am thinking to have a pricing Procedure for Domestic, one for Imports and one for Services.
could you please explain procedure as i go correct or not

Hi,
Note required three Pricing Procedures ieu2026u2026 Domestic, Imports and Services as two Pricing Procedures is enough as per your above procurement processes u2026ieu2026 Domestic, Imports .You can have a condition type for service and insert in both procedure which triggers ONLY when material not there in purchasing document.
Regarding CENVAT credit or adding to inventory A/C, you can very well controlled with individual tax code creation with separate condition type for each ( like for example: JMIP: BED inventoried and JMOP-BED Setoff) by using tax procedure( TAXINN or TAXINJ).
Refer link:
http://wiki.sdn.sap.com/wiki/display/ERPLO/DifferencebetweenTAXINJandTAXINN
Regards,
Biju K

Requirements in pricing

Similar Messages

Maybe you are looking for