Using Field determined in a Condition in another Condition for a pricing procedure

Hi Gurus,
I have a scenario in a pricing procedure as follows:
Cond type ZABC : Determines field HIENR because of the Processing type marked as B for determination based on a field KUNNR ..
I want to use the HIENR determined in the previous access in a subsequent condition type for processing. I want to know if there is any way to do this without coding.
Cond type ZPQR: HIENR is passed as a mandatory field for processing access.

Hello Santosh,
These are two different condition types with two different access sequences. In the pricing procedure, ZPQR follows ZABC, now, i want to use the HIENR determined in access for ZABC as a variable in access for ZPQR .
HIENR >> determined from Access ZABC >> Conditon type ZABC
HIENR should be populated into table ABC table for ZABC access sequence.
HIENR passed as a variable to Access ZPQR >> Condition type ZPQR.
Is there a way to do this without addind code??

Similar Messages

Condition Type not displaying on the pricing procedure

Hello We are copying a sales order contract with reference to a sales order but we want a condition on the contract pricing procedure to be determined. Now I know I could redetermine pricing by selecting these option but we can't do that as there could be a year difference so we need the old pricing. B Carry out new pricing C Copy manual pricing elements and redetermine the others e.g. Sales Order Pricing Procedure XXXX Conditions ZPR0 Conditions ZHD1 Create Contract with reference to sales order Contract Pricing Procedure yyyyy Conditions ZPR0 Conditions ZHD1 Conditions ZNEW In the analysis the condition ZNEW has the "Condition without condition record (not relevant)" As I mention in new pricing it appears

Hi Roy,
Trust you are doing good,
I have gone through the question which you have asked but its not clear what do you want to exactly do.
Pricing Procedure XXXX Conditions ZPR0 Conditions ZHD1 Create Contract with reference to sales order Contract Pricing Procedure yyyyy Conditions
Here you talking about two different pricing procedures..or you talking in terms of pricing values.
Please highlight.
Thank you,
Regards
SRT

Condition PR00 not appeared in customized pricing procedure

Hi Gurus
I have customized Pricing Procedure RVAA01 to ZVAA01.
ZVAA01 is already consists of PR00 & PB00 condition types.
I have also maintained the condition record (VK11) for the sales orgDist. ch material+customer combination.
But Billing doesn't show the PR00 condition at all.
How to fix this issue.
Regards
RG

hi R G ,
Please whether the system is using the same pricing procedure for billing document that of the sales order- (i am assuming that in sales order it is populating the conditon typwe pr00)by going to the condtions tab in vf01
if yes it should flow check in ovkk what is the pricing procedue that is allocated to the combination of sales areadoppcupp(cust pric proc.),
here dopp(doc pric proc) of sales order and bill should be same like A
upadate me with the above findings so that i can propse the other solution
revert if helpful
Mohit Singh

Tax Condition type : Account keys in SD Pricing procedure .

Dear SAP Gurus,
In the configuration of the taxes (Service, Ecess & H & Ecess)
The tax codes are defiined and the condition type JXX has been defined with the account keys .
Then the taxes are automatically posted to the accounts .
But in the SD pricing procedue for the same condition type the account key defined is EXD .
But where is this account key going to post the value of the condition type JXX ..
Please explain the use of the account key in the Tax Conditon types in the pricing procedure.
regards,
Amlan Sarkar.

Hi,
The account keys ERL , ERS, DIFF which are related to revenue and sales deduction in your pricing procedure are defined in transaction VKOA. Here the account key, chart of accounts, your sales organization and G/L accnt combination are maintained.
Whereas all the tax codes G/L accounts get picked from transaction OB40 , So in your pricing procedure where ever you see tax account keys, make sure you go to OB40, input your tax code and then you will see all the G/L accounts against each respective account key. This is nothing but the calculation of tax on sales / purchases.
Hope this will solve your query.
If it does, please dont forget to reward points for contribution.
Regards
Ravi

Statistical Condition not appearing in Rebate Specific Pricing procedure

Hi,
We had recently implemented Rebate Billing in SAP and for the credit notes I had created a new pricing procedure and marked it as 'Special PP' for rebate at Pricing procedure level.
I am calculating Discount and providing Tax in Rebate Credit Memo.
My India Tax JIVC and JIVP are based on some statistical conditions ZATS and ZSEB, although I am getting the Tax Condition in the document but for the statistical condition, it says "Condition record exists, but has not been set".
Kindly suggest what is that I am missing.
Regards,
Naveen

Pls check the validity of your condition type as per the pricing date of the conditon type. The condition record should be valid on the pricing date of the c.type.
This should solve your problem.
Reward if this helps.

Using Field symbol to fetch data from another program

I have a requirement where i need to fetch value of a field from one of the function pool so i have written a sample progam to check the logic but its doest seems to work its giving dump.
Basically i want to know how to use <programname><fieldname> with fieldsymbol.
REPORT ztest1.
DATA test(25) VALUE 'ggg'.
submit ztest.
report ztest.
constants: lv_memory(25) type c value '(ZTEST1)TEST'.
field-symbols: <fs2> type char25 .
assign (lv_memory) to <fs2>.
write : <fs2>.
I am getting same field symbol assignment dump

Hi Rahul,
You can use this concept in between the FUNCTION MODULES where both are
under same FUNCTION GROUP ( as both the FM's have same global memory area ).
And also if you are calling an FM or method from your program ,you can have the data of the calling program in that called FM or METHOD.
Hope this may help you.
Regards,
Smart Varghese

Varient condition is not picked in the pricing procedure.

Dear Friends,
I am creating a sales order where, I am getting a message that VA00 condition is not determined. I analyze the pricing,and find out that the condition record is not determined by the system. Message number is 106. I already maintained the condition record for VA00.
Thanks,
Abhishek Kumar

Hi,
Only if you have created the variant and assigned the same in VK11 then the system will fetch that during pricing
otherwise for VA00 manual entries has a priority so you can add the condtion type manually and give the value to it manually.

Condition type field when Define Pricing Procedure Determination

Hello Gurus,
there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
Many thanks,
Frank Zhang

Here is are the details of various fields while configuring pricing procedure.
A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERFu2026u2026u2026u2026.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
Kalpesh

Pricing Procedure Determination - Condition type

Hello,
Would like to know the use of maintaining condition type while maintaing the pricing procedure determination in OVKK transaction.In what way it would help?
For standard procdeure RVAA01, standard condition type PR00 is maintained - May I know what impact it carries?
Thanks.

hi collins,
this is to inform you that,
this condition types you will set in pricing procedure in a sequence like.
BASE PRICE
DISCOUNTS
+
FRIEGHT
+
TAX
gives raise to your final price
in this sequence only you will arrange the pricing conditions in pricing procedure
hope this clears your issue
balajia

Condition type is missing in Pricing Procedure determination

Hi experts,
We have a problem with Pricing Condition type in CRM.
We have created a Transction in CRM as a follow up for the Transaction which is replicated from ECC to CRM the pricing procedure has been determined. But the net value is "0".
when I checked in the conditions tab page "the condition type is missing" I checked Pricing Procedure the condition type is very much there. Then I checked for access sequence for that Condition type "Access sequence is also maintained.
Then I checked copy controls for the Source and Target Item categories, for copy conditions the indicator is set up as "copy conditions,Redetermine taxes" then I changed it to "Copy all conditions".
But still it is not happening.
Can any please help me in this regard? Did I miss any configuration?
Any help will be rewarded with points.
Regards,
Frederick.

Hi Fredrick,
This requirement must be assigned in your Pricing Procedure for condition type VKPO.
The system first checks whether the requirement is fulfilled and than only execute that condition type.
Requirements are nothing but Java Routines, which check for some condition before executing a condition type.
For this Go to path
IMG: CRM-> Basic Functions-> Pricing-> Define settings for Pricing-> Create Pricing Procedure.
Choose your pricing procedure here. Here for the condition type VKPO requirement 41 must be assigned in column REQ. The requirements are coded in JAVA in SAP CRM.
If this Pricing Procedure has been downloaded from SAP R/3, u can check in R/3 itself (Tcode: V/08) what the requirement is meant for, but choosing F1 and than the path for customizing.
Regards,
Shalini Chauhan
Edited by: Shalini Chauhan on Apr 29, 2008 2:43 PM

Pricing requirement: condition to be in(active) linked to another condition

Hi,
I have created 2 new conditions type YR05 and YR06 in pricing procedure.
I would like that the second one (YR06) is considered as active only if amount of condition type YR05 is different from 0. (KOMV-KEBTR and KOMV-KWERT different from 0)
Could you please advise how I should handle it as I am not so familiar with requirements and Condition base value.
In addition, I created an additional line in pricing procedure to sum the amount (condition value) of these 2 conditions (to be printed on the billing document).
Any idea of the code to put in requirement and calculation type ?
Thanks for help,
Brgds,
VM

Hi,
In pricing procedure, you can put a subtotal for YPR5 (like D for XWORKD).
Then, in new routine (basis or formula), you can check if XWORKD <> ' '.
If yes, xkomv-kinak = ' ', if no, xkomv-kinak = 'X'.
This is just an idea.
Regards,
Lionel

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.

CRM 2007 - Pricing procedure could not be determined

Hi Gurus
We starting an implementation of CRM 2007.
For my Service Ticket transaction we are receiving the message "Pricing procedure could not be determined". We do not need any Pricing as this is purely a service orientated call centre and pricing has no impact on the services we provide.
We're using the dummy service product "INVESTIGATION".
I've tried modifying the customizing to use a Pricing Procedure but this has failed to work.
Is there config which will prevent this error from showing up in the first place.
Maximum points for a speedy response.
Many Thanks
Panduranga

Hi Vishant
I checked the following
1. Assign the sales area of your sold to party a customer pricing procedure.
    In transaction BP for my customer in role "Consumer" data is as follows:
    Sales Org - Defined
    Dist Channel - Defined
    Billing Tab
            Cust Pric Procedure: Standard
2. Assign your transection a document pricing procedure.
     Transaction has Leading Category "Service Process" is not possible to assign a document pricing procedure. Unless you know of another way?
3. for document pricing procedure, customer pricing procedure and sales area data, define the pricing procedure to be used.
    Under SPRO - IMG - Customer Relationship Management -
              Basic Functions - Pricing - Pricing in the Business
              Transaction - Determine Pricing Procedure.
    Sales Org, Dist Channel, Division, Doc Procedure (S - Service Process), Cust Pric Procedure (Standard), Procedure ((0CRMBP) used this as it only has one condition)
4. in product master data, define the values of condition types being used in the pricing procedure (if you dont need the prices, you can just define them as zero).
Added conditions to the Product
Unfortunately I'm still receiving the same error, can you assist further?
Regards,
Panduranga

Pricing procedure(Condition technique)

Hi All
Can someone provide me all the configuration steps in pricing procedure in MM...

Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
Highlight it and double click the Control icon in the LHS screen.
We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
The detail description of each column is given below.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence specified by the counter.
Condition Type:
It represents pricing element in pricing procedure as a base price, discount, freight and tax.
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Ex.: PR00 - Price
K004 - Material Discount
K005 - Customer/Material Discount
K007 - Customer Discount.
Description:
System copies description of condition type from its description (V/06).
From and To:
1.From: This can be used as a base to the condition type for calculating further value.
1.{+}From and To: + The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we un-check the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
It is used only for information purposes only.
This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
This is commonly used for condition types
SKTO - Cash Discount
VPRS - Cost (Moving average price/Standard Price).
Print:
The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
If the same fields are used to store different condition amounts, the system totals the individual amounts.
These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
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.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used instead of standard formulas.
For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11 - Profit Margin.
If new routines are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
And we assign the application type.
AltCBV - Alternative formula for condition base value:
Formula for determining the condition basis as an alternative to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
ERB Rebate sales deduct.
ERF Freight revenue
ERL Revenue
ERS Sales deductions
ERU Rebate accruals
For Ex.,
For all Price condition types like PR00 etc. we assign ERL - Revenue.
For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
or
Hi,
Pricing Procedure in MM
The steps are:
SPRO->MM->Purchasing->Conditions->Define Price dertermination process
1. Define Condition Table:
2.Define Acces Sequence,
3.Define Condition Type,
4.Define Claculatin Schema,
5.Assign Calulation Schema,Acces Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organisation,
8.Assign Schema Group Of Vendor to Purchasing Organisation,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organisation and Calculation Schema.
10.Assign Vendor to Schema Group Of Vendor (XK02)
11.Maintain Condition record(MEK1)
Edited by: MANI ROOPA SD/MM on Apr 17, 2008 8:44 AM

New Condition Table in Tax Pricing Procedure

Hi Friends,
Have u ever created new table for TAX Pricing Procedure and assigned the same to acess sequence.
We are using TAXINN.
Scenario is given below:
We receive material directly & some times we asked 1st vendor to send the material to another vendor without receiving into our factory. 1st case it will be cenvatable & in 2nd case it is non cenvatable (2nd vendor who receives material will claim)
Presently we are using condition table of Plant / vendor / Material. To meet above requirement we want to make a table with Plant / Material / Vendor / Storage location combination.
We maintain "Storage location" in filed catalogue VOK0 & then maintain in KOMPAZ appendix structure, so that it update KOMP & KOMK tables accordingly. When we are creating new table with storage location, we are getting error i.e. "storage location" field is not updated in KOMP & KOMK tables.
Can any one guide me how to proceed ? Is there any other method for solving this ?
Regards,
Sai Krishna

46C: You should do it the other way around: first update structure KOMPAZ with field LGORT, then add it to the field catalog in VOK0.
You will then need to code these exits:
USEREXIT_PRICING_PREPARE_TKOMP and/or USEREXIT_PRICING_PREPARE_TKOMK to fill in the storage location field. If you add new fields to the catalog, you need to supply the values as well. The userexits are available in MV45AFZZ.

Using Field determined in a Condition in another Condition for a pricing procedure

Similar Messages

Maybe you are looking for