Pricing Conditions Class CL_COND_DATACONTAINER

Hi,
Has anyone come across this class for maintaining pricing conditions. What are the inputs we are supposed
to provide so that we create a condition record,update or delete a condition record. Sample code will also be help ful
Any help will be appriciated.
regards sami.

Hi,
I share the same opinion as Lakshman.
basically you are paying him advance for tooling charges or we can consider it like this as vendor has asked for money before the delivery of goods, so he has send you the invocie.
if your requirement is to reflect tooling charges, then you require to have the condition made.
pay him advance, during LIV amount will be setoff.
many times it happens that we raise a PO, but before goods are received vendors sends invocies requesting for some payment release for portion of work he has done. it is then treated as invoice.
if it is regular practice, then it is a process. proceed as lakshman has suggested.
Regards
Rajesh

Similar Messages

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

2 pricing conditions in PP

Hi everyone,
This is a RETURNS scenario.
We create a Credit Memo Request (Sales Order type: CR) when the customer calls in for a Return and we make another Sales Order (Sales Order Type: RE) when the goods actually come in. A credit memo is created against the CR initially and later a billing doc. is created against deliv. made from the RE order.
Now the requirement is to have 2 pricing conditions in PP of the CR order. Say ZR00 and ZR01, where ZR01 = -(ZR00). This is coz' ZR00 is posted to the sales account and ZR01 to Accrual account. When RE is created the -ve price in Accruals account from the CR is cleared.
Now standard SAP allows only one pricing condition in a PP, any ideas on getting around this?
Temporarily I have made ZR01 a 100% discount....but I knw thats not the way to go about it.
Any help is appreciated
regards

Hi,
Maintain a single Price Condition Type, say ZR00, in your PP.
In T. Code: V/06, maintain Field: Plus/ minus as "Blank" for Condition amount as both: Negative (a Discount) or Positive (a Surcharge), or whether both positive and negative amounts are possible.
{Condition Class: B - Prices}
In T. Code: V/08, insert your condition type: ZR00 and maintain other column entries as, for example, Column: Account Key as "ERL - Revenue"; Column: R as "Checked for Mandatory, if reqd." etc..
You may insert other condition types, based upon Condition Type: ZR00, in subsequent rows, such as "Material", "Customer Discount", "Customer/ Material" or Tax Conditions etc..
In Acct Determination, T. Code: VKOA, Maintain G/L accts. for "Cust Grp./ Mat. Grp/ Acct Key" and maintain Provision Acct, next to G/L Acct for account determination takes place in the billing document with the field, relevant for accrual.
Rest will be assured from FI-Consultant as maintain G/L accts and postings is FI-job.
There is no need of maintaining 2- Condition Types in PP, at all.
Best Regards,
Amit.
NOTE: Hope, I have understood the problem and answered to your query, up to some extent.

Problem with pricing condition type in case of proforma invoicing

Hello All,
the problem is related to a pricing condition type in case of proforma invoice where the details are as follows -
Name of Condition Type - ZADC - Add 10% on Cost                                         Access seq.   Z038 Diff
                                                                                Plus/minus    A Positive
Cond. class - A Discount or surcharge
Calculat.type - A Percentage
Cond.category - Blank
Manual entries      D Not possible to process manually
Amount / Percent - Checked
Item Condition - checked
Scale Basis - Quantity
Currency Conversion - Checked
Quantity Conversion - Checked
This condition type has been kept as statistical in the pricing procedure. Still in the proforma invoice the condition type is not getting reflected automatically , whenever I am updating with " carry out new pricing " option the condition type is getting populated.In case of other commercial invoices this very condition type is getting populated automatically without any updates.Along with this point to be noted is that the Condition type in which the actual costi is captured has been kept active.
What more needs to be configured or what are the changes to be done to populate the condition type automatically as statistical during the time of proforma invoicing?
Thanks & Regards
Priyanka Mitra

Hi,
Kindly do the pricing analysis and check whether you have the following error such as
Inactive condition type because of subsequent price,
Regards,
Ravi

Custom Pricing Conditions not working for a PO in SRM

Hi Experts,
We are on SRM 5.0, ECC 6.0 , Extended Classic Scenario.
We configured the pricing conditions in SRM . We defined the our custom pricing condition types as below
Condition type      --- Condition Class       --- Calculation Type
Frieght(%)            ---       Prices                ---      Percentage
Frieght Value       ---        Prices                --- Fixed Amount
We also defined the Calculation Schema.
But when we try to define the pricing conditions in SRM during PO creation\change , the standard pricing condition types work but when we input the above defined custom pricing condition type, the value entered gets cleared. Pricing Overview is not calculating the values of the custom Pricing condition types.
Please assist as where i have gone wrong. Do I need to run any standard report for pricing or do i have to implement any BADI.
Thanks,
Addy.

Hi Sanjeev,
I have run SM52 and VMC is active with 4 VM's .
Please suggest.
Thanks,
Addy.
Edited by: Addy1209 on Nov 18, 2010 4:28 PM

How to set required for group of condition type in the same condition class

Hello,
we have a group of condition type with the same condition class B, the last one have been set, and all of others will be inactive.
but we don't set any required for all the condition types in pricing control, so if user don't set any of them, the sales order or billing is still saved. that is a risk.How can i fix it? Thanks.
Sophie

Hello,
incompletion log is not available in invoices.
You have different options:
- activate a validation in FI when the Billing document is released into accounting, so that te release into accounting is not allowed if the invoice amount is zero;
- define a subtotal in the pricing procedure as sum of the pricing conditions of your group, then develop a custom routine to be assigned in the formula "CalType" (field T683S-KOFRM) where an error should be raised if the amount of the subtotal is zero (use as an example formula 48);
Best regards,
Andrea

Pricing condition type is inactive in pricing procedure

hi,
We have two base price in our pricing procedure ,
fixed -pr00
and wight wise.-pr01
both have condition class-B
while doing VA01 conditon type is showing as inactive(-Y-inactive because of subsequent price.
Please need ur help

Thanks for your early reply,my client do not want to make the !st conditiontype (PR00) as discount and surcharge.
let me elabrate the pricing procedure more detail.. we have two pricing procedure for export sales.
1-export sales -zabexp
2-Deemed export sales-zadexp
pricing procedure -zabexp
condition type                                     from      to      manual       required
proo(base price)                                      -            -         -                   -
pr01 (base price weight wise )                -           -           -                   -
it is runing well in zabexp. but the same setting is not running in zadexp.
Need Help.

Pricing condition question

Hi Gurus,
I need your help
1) Want to configure a pricing condition which can be used only in a purchase order, but NOT in a contract/outline agreement. Is it possible? If yes, then how?
2) Want to configure a pricing condition which when added in a purchase order, will Not add the corresponding charges against the cost of material, but instead will get posted to a seperate G/L account. What special I have to do for it's configuration?
I do Not want to add a seperate line in the PO with a NLAG material accounting for those charges. The business wants the charges as a pricing condition (since we have the flexibility to put a different Vendor in a condition type )
Thanks,
Kumar

Hi,
1.Why you want a condition which can be used only in a purchase order, but NOT in a contract/outline agreement? What is the real business requirement!
2.For Not to add the corresponding charges against the cost of material,follow the steps:
Create a condition type (copied from standard FRB1 or FRA1 or FRC1 condition type ) in M/06 t.code & select check box of "accrual" selected in control data-2 & the Cond.category must be B(Delivery Cost) in control data-1 .
And
In the schema (M/08), keep an accounting key & an accrual key for that condition type
In OBYC only assign G/L account (separate) for accrual key with chart of account, valuation modifier & valuation class.
Now create PO( during saving PO, you can see net value not included amount in that condition type in PO & assign as needed by you separate vendor to that condition type)
Go for MIGO & do GR and see all accounting entries with a separate entries for separate G/L account
For more check link:
http://wiki.sdn.sap.com/wiki/display/ERPLO/PostingplanneddeliverycosttoNon-inventoryaccount
Regards,
Biju K

Pricing: Condition type for advance "ZADV" can be enterted twice

Hello,
I have defined condition type for advance as ZADV in pricing procedure.
Issue: Now teh end user is able to enter the advance conditype types "ZADV" in the sales order, is it any way possible that it should not allow the condition type to be entered twice.
Regards
Suvin.S

HI,
Issue: Now teh end user is able to enter the advance conditype types "ZADV" in the sales order, is it any way possible that it should not allow the condition type to be entered twice.
1*.Suppose Condition type ZADV having Condition Class "Discount or Surcharge " system will allow to enter manually second time also*
2. Suppose Condition Type ZADV is mandatory to few customer and also customers then do the some changes in the condition Type under the Tab "Changes which Can be made " we can find out the Manual Entries fields in that try to mentioned "D - Not possible to process manually "
Regards,
Prasanna
Edited by: prasanna_sap on Sep 6, 2011 8:35 AM

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.

Intercompany Billling - pricing conditions are getting redetermined

Dear friends,
I have one issue of Pricing conditions being redetermined in the Intercompany Billig Document.
Whatever values I maintain in the sales order should follow to Intercompany Invoice. For eg PI01 value maintained in the slaes order is 782.15 INR. It will be same in the Invoice (F2). But when i create the Intercompany Invoice the value is something else i mean it is getting determined from the condition record of PI01. Same is the case with other Intercomopany Discount cond types.
Addtional Info:- I have checked the copy control settings between LF and IV. For the item cat TAN Pricing type is G.
Please suggest what can be done to resolve this.
Best Regards,
Vishi

Dear Vishi,
D: Copy pricing elements unchanged. The system
1. Copies the pricing elements unchanged with automatically determined or manually entered surcharges and discounts from the reference document (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity
2. Does not redetermine the taxes
*G: Copy pricing elements unchanged and redetermine taxes. The system
redetermines the following condition types:
1. Taxes (condition class D)
2. Rebate (condition class C)
3. Intercompany billing conditions (condition category I)
4. Invoice list conditions (condition category R)
5. Condition types with condition category L
6. Cost conditions (condition category G)
7. Cash discount conditions (condition category E)
8. All other condition types are treated as for pricing type D.
Why you want to redetermine taxes.
Regards
Amit

Can idoc COND_A04 be used to update/delete existing pricing conditions?

Hi all,
I am designing an interface from an external pricing system to SAP, and am currently looking at the COND_A04 idoc as a mechanism to load the prices into SAP. In testing I've found that this idoc creates pricing conditions very nicely, but I'm wondering if the idoc can also be used to change existing pricing conditons or mark existing pricing conditions for deletion. Has anyone ever done this with COND_A04?
I tried deleting an existing condition by populating E1KONH-KNUMH with the condtion record number of the existing condition, and populating E1KONP-LOEVM_KO (deletion indicator) with an 'X'. Instead of marking the existing condition with the deletion flag, what this did was create a new condition record (same validity period and price) that is marked for deletion. While functionally this does in fact delete the price (the previous condition is 'overlapped' by the new condition and therefore ignored going forward), it doesn't seem like a clean solution and the resulting change history is very confusing.
Are there are fields on the idoc that can be set to perform a true change or deletion, vs. simply creating a new condition record??? Any ideas will be most appreciated!
Thanks,
Allison

There could be numerous reasons for the IDoc failure because the message that you are getting is too generic. Btw, Is this the only message you get, check if there are more than 1 status 51 in your IDoc to get some more information.
Also see the longtext of the message by double clicking on the status message, probably you will get a more comprehensive reason for the failure.
If nothing of the above helps, try to see the message number and class and see where it is used in the posting program and put a break point at the spot where this message is triggered.
regards,
Advait

ECS: New Pricing condition for purchase order on item level

Hello Experts,
we use SRM 5.0 with the extend classic scenario.
We customized a new pricing condition (absolute discount), which we want to use in a purchase order and added it to the calculation schema.
condition type:
Application     BBP
Source system LOCAL
Usage           PR
Condition Type ZRBT
Access Seq.     01CT
Condition class       discount
Calculat. Type    fixed amount
Condit.category
Rounding rule commercial
manual has priority
item level
delete
amount/percent
UoM
Scale Base Type   quantity
Check stat             none
Max. No. Dimens    no scales
We see the condition type and can choose it in the transaction which is used to create a po.
But when we choose it from the drop-down box it isn't added to the calculation.
Regards,
Sven

Hello Sven,
Thank you very much for posting the OSS note solution for your issue.
I had similar issue and finally was able to resolve it after reading your post.
regards
Vinod

Header Pricing Condition -- Can I attach rotuine..

Hi,
I want to attach routine for the header pricing condition (instead of manual) to fetch the price from ztable then the price
has to be equally distribute to item level/
Is this possible? can i attach a rotuine to Header condition?
Laxman

Hi,
The price for this Header condition is stored in classification field of material master.
Example..
We created charactersitc called deductables,and
attached this characterstic to the class of material. finally we given value of 100 usd in the material master classification tab.
So when I attach a routine (say 602) to ZDED (header discount condition), it has to go to the material master and find this 100 usd and equally distribute to all line item.
My direct questions is
Is SAP header condition will work if I attach a routine (altenative calcualtion type)?
If yes, once i identify the value of 100 USD how to pass to header level condition rate?
Need advice

Coprying rule-Pricing Condition records

Hi,
When copying the condition records, it gave the message "*Copying is incomplete because no rules have been defined."Can anybody pls. guide as to how to define copying rule for pricing condition.
Regards

Prerequisites for Copying
The following general prerequisites apply to copying condition records:
If the condition tables differ between the source and target condition records, then:
Only one field may differ between the two condition tables
The condition tables must contain the same number of fields
If the condition types differ between the source and target condition records, then each condition type must have the same calculation rule, scale type, condition class, and plus/minus indicator.
Copying Rules
Copying rules determine which condition types and condition tables you can use for copying between source and target condition records. The rules are defined in Customizing for Sales and must meet the prerequisites listed above. The standard R/3 System contains standard copying rules. If required, your system administrator can modify the standard copying rules or add new ones to meet your requirements. During processing, you can select from alternative copying rules, depending on what you are trying to copy.
Examples of Different Copying Scenarios
The following three scenarios describe how you can copy condition records.
Scenario 1: Same condition types/same condition tables
You offer a special discount to a particular price group (a group of customers defined in the customer master record). You want to make this discount available to other price groups by copying pricing details from the existing record. In this type of copying, the condition types (K020) and the condition tables (table 20) are identical for both source and target condition records. The only thing that varies in this case is the value of one of the key fields (the Price group field).
Scenario 2: Same condition types/different condition tables
The access sequences for a particular condition type can be defined in Customizing for Sales so that it accesses more than one condition table. This means condition records with the same condition type can have different keys. You can also copy condition records where the condition type is the same but the condition tables are different. Say you offer a material-specific discount to a particular price group (condition type K032, condition table 32). You can copy this material discount and create a new condition record for a specific customer (condition type K032, condition table 5).
Scenario 3: Different condition types/different condition tables
You can also copy condition records even when both condition types and condition tables are different. Say you offer a special discount to a particular price group (condition type K020, condition table 20) as you did in the first scenario. Here, however, you want to copy this condition record not to another price group but to a new customer-specific discount (condition type K007, condition table 7). In this case, both condition types and condition tables are different.
Copying Process
You can call up the copy function from the Edit menu in any of the following condition record screens:
Creating
Creating with reference
Changing
Overview
There are several typical scenarios for using the copying function. You may want to copy an existing condition record into a number of new condition records. In this case, you use the change condition record function. Alternatively, you may want to create a new condition record and copy it to other records all in one step. In this case, you use the create condition record function. In both cases, you can change the copied data before you save the new condition records.
Note:
If the existing rules not suited to ur requirment , u have to contact Abapers to write the routines for ur requirement.
Hope it is useful
REWARD POINTS IF USEFUL...

Pricing Conditions Class CL_COND_DATACONTAINER

Similar Messages

Maybe you are looking for