Pricing Condition during upgrade

Hi,
During our SAP upgrade we are experiencing an issue related to PO pricing conditions. How can we bring over PO pricing conditions in open POs from 4.7 system to 6.0. We are using several custom condition types.
If anybody have an experience like this please share with me for resolving this issue.
Thanks
John K. T.

Hi John,
check the following steps:
1. maintain Z-table for Conversion from old and new conditions
2. Include this table in extraction program (ABAPer'll do this)3.
3. Check the extracted data for accuracy
Now your file is ready with new conditions and new data as per your ECC6 system
4. Then upload this flat file by uploading program.
Revert where you are facing issues? What process you are following?
Umakanth R

Similar Messages

Copying STO PO pricing condition to Billing During Billing creation

Hi,
MM and SD pricing conditions are not similar.
And I cant use Copy PO Basic price in billing Document
I was advised to try USEREXIT_PRICING_PREPARE_TKOMP or USEREXIT_PRICING_PREPARE_TKOMK.
How do I copy the Pricing condition from the STO PO to Billing during billing creation?
Is there an FM i can use to extract the pricing condition given the STO PO?
thanks,
NC

Hi
If the option of Raghavendra doesn't work for you (parameters in copy rule for invoice), try with VOFM subroutines (Condition formula for alternative calculation type) in the pricing procedure. Surely it will be slower, but it must work. How? You have in KOMP the values for VGBEL and VGPOS with the delivery number and item. So, seach the PO number in the same way. When you have the PO number, with the value of field KNUMV search the value of condition in table KONV.
I hope this helps you
Regards
Eduardo
PD: I forgot. The userexits that you mention is to populate KOMP/KOMK for customer fields. See SAP Note 531835 - Using field PSTYV in the condition access for futher information.
Edited by: E_Hinojosa on May 16, 2011 9:21 AM

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

User exit to copy Manual pricing conditions with in sales documents

Hi all,
I have a situation where i have to copy the manual pricing conditions from inquiry to quotation.
Problem: From VA21 when I try to do the same using the tab "create with reference" the document is being copied but the manually set pricing condition in the inquiry is not being copied into quotation. This is because in the copy controls the pricing type is set to 'B' which means "carry out new pricing". I can change it to 'C' or 'D' so that it copies manual pricing but i am not allowed to do so because other sales orgs in the company has a problem if i do so. Only our perticular sales org needs this config. I cannot even create another item catogory specific to this plant because it is against the rules of the company. So I am looking for a user exit in which i can change this pricing type during runtime so that i can plug in some code specific to this sales org to copy manual pricing. I have found one from the SAP note 24832 (MV61AFZA). It doesn't work as i think its obsolte. Can anyone suggest me a better way of solving this issue. Any quick response is appreciated.
Thanks,
Giridhar.

Hi
The following EXITS may help you
Exit Name              Description
SDTRM001            Reschedule schedule lines without a new ATP check
V45A0002            Predefine sold-to party in sales document
V45A0003            Collector for customer function modulpool MV45A
V45A0004            Copy packing proposal
V45E0001            Update the purchase order from the sales order
V45E0002            Data transfer in procurement elements (PRreq., assembly)
V45L0001            SD component supplier processing (customer enhancements)
V45P0001            SD customer function for cross-company code sales
V45S0001            Update sales document from configuration
V45S0003            MRP-relevance for incomplete configuration
V45S0004            Effectivity type in sales order
V45W0001            SD Service Management: Forward Contract Data to Item
V46H0001            SD Customer functions for resource-related billing
V60F0001            SD Billing plan (customer enhancement) diff. to billing plan
V45A0001            Determine alternative materials for product selection
Regards
PRabhu

How to Maintain the Pricing Condition Records in CRM

Hi
I am new to the CRM
How to maintain the pricing condition records in crm for the particular condition type?
as we do in SD(VK11)
Thanks

Hi Binu,
First of all, you could maintain pricing conditions in the following places:
1. In General Condition Maintenance (GCM)
2. At the product maintenance level
3. At the 'Price agreement' tab of Contracts
4. As manual conditions during order processing at item level
Now, if you want to maintain conditions using GCM, you first have to maintain a condition maintenance group in the customizing where in you can assign condition table and condition type for different counter values. I am assuming that you have done this activity successfully.
When you run the transaction '/SAPCND/GCM', for application 'CRM', your condition maintenance group name and context 'GCM', you will be initially taken to a screen where in you'll have an item area which would be blank and then condition fields would be displayed in a tree on the left.
Here, select the field 'Condition type' and click on icon 'Select records'. You would get a dialog prompting you to enter condition type. Here you can specifiy the condition type for which you want to maintain/view condition records.
If no condition records are available, item area would be left blank. Here, you can choose a condition type using the standard F4 help. Depending on condition types that are assigned to condition maintenance group, different condition types would be displayed in the F4-help using which you can maintain condition records.
Hope this helps.
Regards,
Pavithra
**PS: Please reward points if this helps.

Disck Space not enough during upgrade CUCM 9.1(2)SU1 to 9.1(2)SU2a

Hi,
I face an issues during upgrade my current CUCM 9.1(2)SU1 to 9.1(2)SU2a, it show with this error message "There is not enough disk space in the common partition to perform the upgrade, for steps to resolve this condition please refer to CUCM 9.1(1) release notes or view defect CSCuc63312 in bug toolkit on Cisco.com". I had check the bug id and got 2 way to do it:-
1. reduce the amount of traces on the system, but I not ready want to do this
2. install a COP file name: ciscocm.free_common_space_v1.0.cop.sgn
If I select option 2, will it have any risk? Is it mean 9.1(2) - inactive version will be clear out from disk space or it will clear out 2 version - active and inactive version from disk space?
I need have some advice on this before I perform.
Thanks.

Hi,
As per the following link
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91_chapter_011.html
You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version."
Additionally, regarding the first option, if you do not want to reduce the tracing levels you can still delete some old traces using RTMT which gives you an option of deleting the traces from the server as well as transferring / downloading them to your pc simultaneously by checking the 'delete from server' option on last page of log file collection option.
HTH
Manish

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 VPRS

Hi guys,
I'm receiving the following error in a Standard Sales Order: OR against pricing condition: VPRS - Error in quantity/value determination.
I believe I have to set this up either in the payment terms table OBB8 or against the material. Could anyone give me a walkthrough of the steps required to set this up please?
Points awarded for helpful responses.
Many Thanks,
Philip Johannesen

Hi,
Some more info for routine 4 which must be assigned to VPRS in pricing procedure.
An order is placed that contains both stockable and non-stock items. Non-stock items are represented in the sales order with the item category TAX. TAX has been configured so that the cost is not determined during pricing of that item in the sales order. Stockable items have been configured to determine costs so that the net sales price can be compared against the cost price. Requirement '4' is assigned to the cost condition type in the pricing procedure so that the cost price is only accessed if the item category is relevant for cost determination
Regards,
Amrish Purohit

Crm_order_maintain ,changing pricing condition value at item level

Hi,
I am trying to change the pricing condition value at item level while creating sales order through CRM_ORDER_MAINTAIN.
I am not able to change the condition value.
Code is below.
 wa_inputfields-ref_guid = wa_orderi-guid.
 wa_inputfields-ref_kind = 'B'.
 wa_inputfields-objectname = 'PRIDOC'.
 wa_fieldname-fieldname = 'KBETR'.
 append wa_fieldname to wa_inputfields-FIELD_NAMES.
 wa_fieldname-fieldname = 'KMEIN'.
 append wa_fieldname to wa_inputfields-FIELD_NAMES.
 wa_fieldname-fieldname = 'KPEIN'.
 append wa_fieldname to wa_inputfields-FIELD_NAMES.
 wa_fieldname-fieldname = 'KSCHL'.
 append wa_fieldname to wa_inputfields-FIELD_NAMES.
 wa_fieldname-fieldname = 'WAERS'.
 append wa_fieldname to wa_inputfields-FIELD_NAMES.
 INSERT wa_inputfields INTO TABLE it_inputfields.
wa_pricing_add-KSCHL = 'ZP06'.
wa_pricing_add-WAERS = 'USD'.
wa_pricing_add-KBETR = '10'.
wa_pricing_add-KPEIN = '1'.
wa_pricing_add-KMEIN = 'ST'.
INSERT wa_pricing_add INTO table it_pricing_add .
wa_pricing-REF_GUID = wa_orderi-guid.
wa_pricing-REF_KIND = 'B'.
wa_pricing-PRICING_TYPE = 'A'.
wa_pricing-COND_ADD = it_pricing_add.
wa_pricing-PRICING_PROCEDURE = 'ZVDSP'.
append wa_pricing to it_pricing.
Can you tell me how to overwrite the condition value while creating sales order using crm_order_maintain.?
Regards,
Indhra.E

Hello Indhra,
Check the CT_INPUT_FIELDS table, in the OBJECTNAME field you will find all the tables that are filled during the function call. Check those tables mentioned in the OBJECTNAME to look for any pricing related data.
When your order is in change mode and you activate debug just before you make the change, the CRM_ORDER_MAINTAIN FM call contains data only relevant for the change you just made. In other words, you need to fill exactly the same tables as CRMD_ORDER does.
E.g. You just change the pricing procedure and you see in debug that 5 tables are filled, you must do exactly the same in your code! It's quite anoying but you're using a low-level API FM that can handle ANY transaction type in CRM!
Check it, it works!!
Reward points if useful!
Regards,
Joost

Maintain Excise defaults for pricing condition in TAXINN procedure

Hi all,
I post this message as I'm customizing CIN part for creation and calculation of excise invoice. I have read lot of post but i'm a bit confused about right procedure to adopt. I try to explain:
I'm doing a stardard sales flow (sales order -> delivery -> commercial invoice -> excise invoice) and the only method I have found to flow excise values in excise invoice is to insert pricing conditions in India -> Basic settings -> Determination of excise duty -> Maintain excise defaults for TAXINN procedure.
In this table I have insert pricing conditions I use in my SD pricing schemas (in this case I use a copy of JINFAC). I have insert pricing conditions corresponding to BED % and BED total, and also CESS % and total and S&HCESS % and total.
If I remove pricing condition from this table, corresponing value in excise invoice, when I create it, become 0.
My dubt is if is correct to populate with table to flow excise values in excise invoice. I ask it as I have read differents approach and differents customizing settings applied in similar situations. In particular, I have found documentation in which, for TAXINN procedure, is recommended to leave blank "excise defaults" (with exception of CVD condition). What is the right method to use?
There is one right procedure or, as it seems reading posts, someone have to do his "proper CIN customizing" based on results that have to obtain?
Thanks in advance for any contribute that can help to clarify this situation.
Regards
Gianpaolo

Hi all,
I think to have found solution to my dubt.
If I use "condition based Excise determination" I have to insert records with pricing schema (if is a copy of standard J* schema, like ZINFAC that is a copy of JINFAC) and excise pricing conditions in the transaction below:
India -> Basic settings -> Determination of excise duty -> Condition-based Excise determination -> Classify condition type
To determine value in excise invoice seems that program check before table in transaction described before. If in this table don't find records for pricing schema-excise pricing condition the program check also table in transaction below:
India -> Basic settings -> Determination of excise duty -> Maintain excise defaults
If during this second check find excise pricing conditions insert, can determine equally the values of excise in excise invoice.
This is the result of my checks. I hope this could be useful for other people with similar problem.

MM - Purchasing Information Record/Pricing Condition

Hello MM world,
I'm taking this opportunity to log an issue I can't find an answer for and I would appreciate to know if someone out there would share his/her knowledge with me.
So here's the question:
I'm trying to determine an additional pricing condition type (discount) during the creation of a purchasing info record (me11). The default PB00 gross price condition type is automatically proposed. Attached to that condition type, you can indicate a pricing schema/procedure that has what they refer to as condition supplements. The condition supplements pricing schema looks like an ordinary pricing procedure, however, SAP has confirmed that condition technique or access sequence determination does not work within the info record due to conflicting validity period between the info record and the additional pricing condition types. So, what I am wanting to do is write both a requirement and alternative condition routine for the ZPIR condition to calculate the discount amount. This will work fine, however we can only hit the routines IF the ZPIR condition supplement is automatically proposed. If the condition type is presented, we can hit the routines without a problem..the challenge is, we cannot figure out how to automatically propose the condition supplements, in our case ZPIR, without clicking the icon during create.
So, what I am wondering is if it is possible to write something in the requirement or alt condition routine attached to PB00 to programmatically add ZPIR to the info record, which would then invoke the requirement and alt condition routine that would determine the discount value.
Or is there anything else we can do to make this work?
Thanks a lot, I appreciate any input.
Mo

Hi Mo Arabat,
Looks good .Once agarin check up your configuration throug this link.
http://www.sap-img.com/materials/steps-for-mm-pricing-procedures.htm
Cheers
Hareesha k

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o In rounding rule 'B', values are always rounded down:
   1045.9 -> 1045 LIT
   1045.1 -> 1045 LIT
   In this example, the currency of the condition rate is Italian Lira.
   The Italian Lira does not have any places after the point.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

Transport Pricing Conditions

Hi
I've maintained the pricing conditions in CRM 5.0 for all the products. I wish to transport these confition records from one client to another on the same system ID. Is there any report or transaction available for transporting the condition records from one client to another?
Urgent help required.
Thanks
Avineesh

hi
In SPRO > MM > Purchasing > Conditions > Define Price Determination Process > Define Schema Determination > Determine Schema for Stock Transport Orders > Here assign Calculation Schema "RM2000" i.e. Stock Transfer Document to Schema Grp Pur. Org, STO Type (For e.g. UB) and Supplying Plant.
Calculation Schema "RM2000" has condition type P101 which will pick up the MAP of supplying plant automatically during creation of STO in ME21N ("Conditions" Tab).
You can create new freight / delivery cost conditions in M/06 and assign in pricing procedure "RM2000" in M/08 and also assign the Accrual Key to this and do the Account Determination for this Accrual Key in OBYC
At the time of PGI, following accounting entry will get generated;
Stock A/c - Dr - 110 INR (Receiving Plant)
Stock A/c - Cr - 100 INR (Supplying Plant)
Freight Clearing A/c - Cr - 10 INR (Supplying Plant)
reagrds
kunal

Duplicate Pricing Conditions

Hi everyone,
When we create a sales order (VA01) with reference to an existing order, the pricing conditions in the document are getting duplicated.
Even forcing a pricing update (via the conditions tab) does not get rid of the duplicate condiations.
Does anyone have experience with a similar issue?
Any ideas on how to isolate where the duplicates are being generated would be appreciated.
Thanks,
- Suresh

I would check analysis from the pricing screen to see how your conditions were determined (based on what keys/tables). Another place to loock at - access sequence for your conditons, does it have multiple accesses and EXCLUSIVE checkbox non-selected ? Also, I would check requirements in the access sequence.
Do you have any code which tweaks XKOMV during order processing - it may cause problems as well.

Pricing Condition during upgrade

Similar Messages

Maybe you are looking for