Condition Pre step in pricing- condition not determined

Hi,
Iam having an issue in my system. There is a condition type ZTFR (output tax condition) which is not determined in sales order. The access seq with this condition is MWST. There are two accesses in this mwst seq as follows
access seq=mwst
first access 06--departure country/dest country/material group--
standard requirement 8 is assigned to this access
2nd access 10-- departure country/dest country----
standard requirement 8 is assigned to this access
I have seen the standard req 8. The code for include LV61A008( req 8) consists of two parts--one pre step and the other normal exprt/import check...... the pre-step part checks that departure/destinaton country is not nil and both are not equal. the 2nd part checks the same for dept/dest country but also checks whether vat of customer is maintained or not and european tax indicator is set.
In my case only vat no is not maintained and all other conditions like dept ctry/dest ctry amd EU indicators are mainatined both for dept/dest country.
the issue is the condition ZTFR is not determined in sales order. Pls note that there is no VAt no maaintained in customer masterv since our customer does not have the same.
system says the follwowing on doing pricing analysis.
1) access 6 not made since req 8 not met. may be because vat no not maintained as wriiten in requirment 8
2) access 10 not made since condition record not found----
the system also gives message that "No condition record was found in the condition preliminary step for this condition using the document data"........... in this Iam not able to understand why the system has not given a message during pricing analysis that requirement not met. Rather the system said that no condition record found for preliminary step ??
what is meant by condition pre step ? and what is happening ? in the first access, system says req 8 not met whereas in 2nd access record not found but issue is same requiement 8 is assigned to acess 6 and access 10.
regds

Hi,
Did you solved this error? Can you tell me the way to solve? I met same error.
Plz

Similar Messages

Pricing Conditions and how the pricing date is determined

Hi all,
Small question, i ahve some pricing conditions that use the Serives Rendered date and others that use the Pricing Date from an order, how is the condition decided on what date it uses?
Hope i have expplained this ok, if not and you need more info let me know.
Regards
Steve

Hi
There is a difference between Service Rendered Data and Pricing Date.
Normally Freight Conditions are maintained on Service Rendered Date so the freight will be picked on the basis of date on which the Actual Delivery done, whereas Pricing date is used for other conditions so that price will be based on the date on which the document created and the Pricing Date maintained in that.
In the same way there is a Billing Date which came in Invoice so price will be based on the date of Invoicing.
If you maintain the record in VK11 and test a cycle you will be able to find the difference easily.
Regards
Amitesh

How to get xkomv-kwert (condition value) from a pricing condition ZZP1

Hi experts,
   I have a pricing condition zcust that I need to modify in the sales order.   The calculation of ZCUST is dependent on the condition value in another price condition ZZP1.   The price for ZZP1 is a fixed amount of $6 which is split among line items in the order.    In sapmv45A, when the code hits userexit_save_document_prepare, the value of xkomv-kwert (condition value) exist.   In other user-exits in sapm45A, I was unable to find xkomv-kwert. My question is: How can I find the value of xkomv-kwert as i don't know how ZZP1 is calculated ?? There is no routine attached to ZZP1.
    THE ZCUST has a routine 993 which is similar to 3.   Here in program saplv61A, i was trying to get xkomv-kwert for ZZP1 but unable to get any data.   Can anyone suggest where i can get the data (xkomv-kwert) for ZZP1 in saplv61a ?
I looked at userexit_xkomv_bewerten_end in saplv61a but it does not help.
XKomv-kbetr always has data.    If i have ZZP1 data, then i can modify ZCUST.
Many thanks.
Joyce

Hi Jelena,
In VOFM, it is Formula/Condition Base Value for routine 993.   In Pricing Procedure, it falls in column "Base Type" for 993.
Let's see if i can simplify this: In a sales order with 2 line items:
               prices                    Amt                      Condition Value (USD)
Line 10     ZS1   sell price     2.30                                 1150
                 ZPP1 charge        6.36                                 3.40 (note the distribution **)
                 ZL1                      3                                      3
                ZR1 %                  1.000%                            11.50
                ZR2                      0.01                                   5
                Suggested price = 2.35                             1172.90
                  ZCUST               2.34                                1170
                  total price            2.34                               1170
Note: The ZCUST price is wrong. It is missing the ZPP1 charge which is 3.40. Zcust should be 1170 + 3.40 = 1173.40
Line 20     ZS1   sell price     25                                 1000
                 ZPP1 charge        6.36                                 2.96 (note the distribution **)
                 ZL1                      3                                      3
                ZR1 %                  1.000%                            10
                ZR2                      0.01                                   0.6
                Suggested price = 25.41                              1016.56
                  ZCUST                   25.34                           1013.60 (should be 1013.60 + 2.96)
               Total price                25.34                            1013.60
You can see the ZCUST is calculated incorrectly. The routine calculate zcust as $1170 and $1013.60 for each item which did not include the distribution amount of ZPP1 ($3.40 and $2.96).
When i debug the routine, the xkomv-kwert is zero.   I am trying to get $3.40 and $2.96 so i can add to to zcust in the routine.
Am trying to determine in saplv61A at which include that i can see #3.40 and $2.96 for both line items in xkomv-kwert.
Then maybe i can modify the routine or saplv61A so it shows the correct zcust price after entering the 2 line items in the sales order create (VA01) ?     Can you pls suggest ?
If i make the changes in USEREXIT_SAVE_DOCUMENT_PREPARE, then user cannot see the correct zcust until the order is saved. This would be too late to know the zcust price ahead of time.
Pls view in the Edit mode... i see my texts have been compressed.
Many thanks
Joyce
Edited by: Joyce Chan on Jul 9, 2009 10:24 PM
Edited by: Joyce Chan on Jul 9, 2009 10:25 PM

Pricing procedure not determined

HI
When i tried to create sales order with sales area lg11/lg/lg.I am getting the error that pricing procedure is not determined,because no entry with keys lg11/lg/lg 'a' 'v' exists in table 683v.
I am not able to move further. Can u pls help me.
Thanks&Regards
Prasad.G

Hi,
This is nothing but the problem in pricing determination.
Go to OVKK.
And maintain the required entries for your sales organisation, distribution channel, division, customer pricing procedure , document pricing procedure and the required pricing procedure that you want to get triggered when once enter this sales area with the other combinations.
Customer pricing procedure comes from customer master data .(sales area data sales tab) and document pricing procedure comes fromthe controls of order document(VOV8)
Mohan
Award points if it adds information.

Pre defined set types are not determined in CAtegory

Hi all,
when i try to create a category for a service product for SLA, the pre defined set types are not getting populated for me.
I have created a new hierarchy, assigned to product and product type.....
but still when i create a category the list of predefined some of the predefined set types are not getting displayed.
Can anyone help this issue.
kindly advice in this regard.
Thanks,
Subhashini.

Hi,
Thanks for the reply.
I have assigned the product type service in the category.
This is the only custom category available. only one std category has this set types. other than that nothing is there in the system.
is there any services that has to be activated or any authorization that is missing for me...
nut i have sap_all...could not able to trace out the problem.
kindly guide.
thanks,
Subhashini.

Condition Type 0K07 not determined

Hi All,
I have defined two conditions records for 0K05 ( Customer/Material discount) and 0k07( Customer Discount).
In Sales Order in Conditions only 0K05 condition is calculating , but 0K07 is not determined.
in Pricing Procedure definition both the condition types are present.
Thanks,
Nagesh

Hi,
Have u maintained condition record for condition type 0k07 in BP??
Thanks & Regards,
Anirban

Pricing condition- Header

Hi,
I have a problem with a pricing condition. It is a the moment both a header and item condition but my customer want it to be only a header condition.
I can not get this to work as it is a condition that is an automatic freight condition with different stages depending on the value in the order. There are an access sequence connected to the condition and according to that the item condition can not be removed.
Is there anyone else who know how it could be possible to solve this? I want a condition to be automatic with stages depending on the order value and I only want to have the condition on header level.
Thanks for the help,
Ulrika Nilsson

Please go to the pricing procedure screen (VOK0 transaction) You will see different pricing steps within the pricing procedure. Also you will see a column "Reqt" associated with each pricing condition.
Identify the pricing condition type for automatic freight conditions and add a custom requirement" say for instance 699. Prior to this activity go to VOFM transaction -> Requirements -> Pricing and create a new routine 699. (may need access key)
Once this routine is created and saved, 2 form routines will be created. Add the following sy-subrc statements as shown below and activate the program. Make sure the routines are added to the transport.
FORM KOBED_699. "Header Pricing
sy-subrc = 0. "successful
ENDFORM.
FORM KOBEV_699. "Item Pricing.
sy-subrc = 4. "not successful
ENDFORM.

Copy the pricing conditions from Sales Order to Delivery

Hi all,
I have to send the princing conditions from the delivery trough Idoc.
That's the reason why I need the princing conditions in the delivery. But I can't redetermine the pricing procedure in the delivery creation. I need to copy the pricing conditions from order to delivery.
Because if there is any manual modification of a condition in the sales order, If I redeterminate the pricing procedure in the delivery, I would lost the changes.
Anybody knows any User Exit or anyway to copy the pricing conditions from SO to Delivery?
Thanks in advance

I think pricing will not determine in delivery, if any shipmentchanges will copy to delivery, not standard pricing.
Logically, when you create delivery by that time your pricing need to finsh, no changes, so send pricing infor from order to customer, as its standard process in any client.

Use of conditino category in pricing condition type

Hi,
Can anybody please guide about the exact use of condition category in the pricing condition type. In text it is mentioned that it is used for grouping of similar condition types but what exactly is the requriement for this? Does it have any control function like the feild condition class has( like for example grouping in this is used in redeterminations etc) ?
Please guide about the use of this feild and if maintained or not maintained then how will it matter?

Hi,
It serves some purposes.
1. It is used for the classification of condition types. During implementations, consultants classify the condition types into condition categories (Prices, Discounts, Taxes) and later use these categories to print the value of condition types in the forms. Coding based on condition categories reduces the effort instead of hardcoding on the condition type.
2. They also have some inbuilt property for some of the condition types like VPRS, SKTO etc where the categories are important for the behaviour the condition type, the way they are expected to behave.
3. Some of the condition categories will be applicable only for some specific processes and not for all the processes. for example e during downpayment.
But the complete function of this field can be only learned over a period of time when we implement new functionalities for the business.

Error in BDOC while uploading the pricing condition record to ECC from CRM

Hi all,
I have created a condition record for ECC pricing condition type (I have maintained all settings required for maintaining ECC condition type in CRM 7.0) in CRM 7.0. But theis condition record is not uploaded to ECC. I have checked BDOC, it is showing with error status for BDOC type "CND_M_SUP". The errors are as below.
1. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
Message no. CND_MAST064
2. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
Message no. CND_MAST064
3. Service that caused the error: CND_MAST_INT_DEEP_MB_TO_SBDOC
Message no. SMO8047Diagnosis
A service caused/ reported an error.
Can some one help me in fixing this issue please.
Thanks in advance,
JM
Edited by: JM on Sep 7, 2010 4:46 PM

Hi,
sBDOCs are not used in ECC to CRM or CRM to ECC data replication scenario. You can either ignore the error or disable mobile bridge.
Regards
Prasenjit

Value of Manual Pricing Condition is becoming zero while saving.

My clientu2019s pricing calculation requirement is complex. Here I am mentioning :-
We have one pricing condition type YPR4 which is header as well as item condition. Value will come only from condition record . So, we maintained access sequence in the configuration. Beside this we maintained u2018Manual entries u2018 in the configuration as u2018Not possible to process manuallyu2019. Condition record for this pricing condition type we maintain for line items.
We have another pricing condition type Y255 which is also Item condition as well as header condition. For this pricing condition value ( header level) can come from condition records if record exist , or , if condition record is not there or if user wants, user can enter value in header level of the sales order. For getting this functionality we maintained access sequence and u2018Manual Entryu2019 in the condition type configuration we have maintained as u2018No Limitationu2019.
In the line item level Y255 will come only if YPR4 is there for that item. The total value of the Y255 in the header will need to be distributed in the line items accordingly as per existence of YPR4 in the line item.
Issue:
Now the issue is that, when there no condition record for Y255 and when we are entering the value of Y255 manually in the header, the value of Y255 is becoming zero when we are moving from one screen to another screen in the same sales order , or when we are saving the sales order..
Can anybody suggest what we need to do so that manually entered value of Y255 remains in the sales order after moving to another screen or after saving the sales order ?

Hi ,
Please check the pricing routines funcationality which is assigned to both condition types.check the requirement and alt.cal. type routines of Y225 condition , on what basis condition record is updating manully entry as well as picking value from condition records.

Configuration enabling goods receipt of purchasing pricing condition

Hi Gurus,
a) If I check the "Accruals" flag for a pricing condition, then only, that pricing condition will create a delivery costs goods receipt, while we receive the purchase order having that condition type......is it correct?
b) Is any other configuration change critical for a condition type to generate it's goods receipt?
Thanks,
Kumar

Hi Kumar,
Just check your condition type in tcode M/06 whether all the below mentioned parameters are correct..
In control data 1 -
Cond. class - A (Discount or surcharge)
Calculat.type - A (Percentage)
Cond.category - B (Delivery costs)
Plus/minus - A (Positive)
Thanks

Pricing procedure not determind

Hi Gurus,
I was creating a Sales order but i cannont save the sales order and getting a error message as
Pricing procedure not determined.
Please help.
Thanks,
Dardo

Hi Dardo
Check in OVAZ wheather the sales document type is assigned to the sales area or not . But , after creation of sales order if you are getting this error Pricing procedure not determined. then go to OVKK and maintain the data sales area + Cupp + Dupp =Pricing procedure and then check, if you are still getting error then maintain sales area + Cupp + - = Pricing procedure
Regards
Srinath

Urgent:pricing condition not determined in sales order

HI,
i have defined a pricing condition for a material . when i am creating a sales order the pricing condition is not determined;

hi
You must have done all the pricing related settings like access sequence, determination, condition type. Please cross check them once again. Also see if the condition record is picked up properly , is it bypassing ?
If every thing is fine, check the item category of that material and see if in business data of that item category Pricing is activated !!
regards
swapnil

Pricing condition records should not be picked up

Hi,
I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
Do I have to use any Userexits, if so which one?
Regards,
Abhishek

As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
To configure new Document Pricing Procedure:
IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
Pricing Procedure Determination:
In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. 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.
Pricing Procedure Configuration:
In SD, the steps to configure Pricing procedure are as under:
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

Condition Pre step in pricing- condition not determined

Similar Messages

Maybe you are looking for