Problem in Copying Pricing Condition Type

Hi All,
This problem is regarding copying pricing condition type in Sales Order. The problem is given below with an example -
Qty of Material A - 10 PC.
Condi Type   Amount Currency   Per UOM Condition value Currency
ZP06             100         INR          1     PC      1000.00             INR
ZP07                2         INR          1      PC         20.00             INR
ZP08               98        INR          1      PC        980.00             INR      Statistical
ZP01               98        INR          1      PC        980.00             INR      Mandatory with ERL A/c Key Active
The condition types ZP06 & ZP07 have access sequence maintained for them and ZP08 has been derived deducting ZP07 from ZP06.
I want the above mentioned scenario where the values of Condition Type ZP08 which is a Statistical Condi Type will be copied exactly & entirely to condition type ZP01 where It will remain active alongwith posting key ERL.
I have tried copying it by 100 % copy but the value is getting changed as 100% instead of 98 INR.
Considering the above scenario please suggest some soluitons.
Thanks & Regards
Priyanka

Hi Tarpan,
First of all thanks for checking my post.
In the problem I am not looking for the value of ZP08 to be maintained manually.I want the system to copy the exact details of ZP08 to ZP01 entirely where the condition type ZP01 will remain active alongwith the posting key ERL.
I have tried copying the condition type ZP08 by using 100% copy of condition type but in ZP01 the resultant value becomes 100% in place of 98 INR.
Please suggest some solutions.
Thanks & Regards
Priyanka

Similar Messages

Problems in New Pricing Condition type

Dear SDN'ers!
Please help me to know if this is doable. Here is my requirement
If a line items qualifies for the per title unit minimum, but not the per order minimum no discount will be applied and vice versa, if a line item qualifies for the order unit minimum but not the per title unit minimum no meet comp discount will be applied.
Two new condition types will be configured say
ZCN1 - Group Condition say for e.g. 100 per order
ZCN2 - Item level condition say e.g. 10 per line item
Individually this is working when the order meets group condition ZCN1,i.e. 100 items and if line item meets ZCN2 i.e. 10 items the discount is applied. Currently the customer is getting the discount either way.
In simple words for each line item to qualify for discount it should meet both ZCN1 AND ZCN2, otherwise no discount order or item level discount should be applied.
I tried in USEREXIT_PRICING_PREPARE_TKOMP and USEREXIT_SAVE_DOCUMENT_PREPARE in MV45AFZZ.
Since its working individually, I added check condition to see if XKOMV-KBETR value is not equal 0 for both ZCN1 OR ZCN2. If either of this is zero then it would have failed in one of the condition either order level or item level.
I have to modify the XKOMV-KBETR value for ZCN1 & ZCN2 to zero i.e. no discount. It displays correctly in the screen but it doesn't update the database. When i go to KONV and check the value its still showing the old discount.
Appreciate any help
Regards,
Badri

Hi Badrinath,
Please try pricing requirements in VOFM.
T/code VOFM> Requirements> Pricing > you can copy Standard routine (Price Change)> Write your own logic .
Hope this may help you.
Lanka

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

Copy pricing conditions from R/3 to CRM

Hello,
I am using Function Module CRM_ORDER_MAINTAIN to copy pricing conditions from R/3 sales order to CRM complaint document.
I am fetching R/3 conditions with the help of RFC call to R/3 and then passing these condition records to the FM CRM_ORDER_MAINTAIN.
I am populating the importing parameter - IT_PRIDOC of this FM. And filling following internal table of this importing parameter:PRIC_COND, COND_ADD, COND_CHANGE and COND_DELETE.
I am not sure if filling table PRIC_COND would be needed.
Could you please guide me about the exact use of these tables? Do you have any documentation for this function module?
Many thanks in advance,
Sandhya.

Dear Sandhya,
I am facing the same problem.
Could you please explain me (in case you finally implemented this), how you did it?
Thanks in advance.
Regards,
Yolanda

Pricing Condition type triggering based on other condition type

Hello sir,
There are some pricing condition types in our system.
Based on condition records you can trigger one condition type based on other    condition type.
For eg: PR00 condition type is there and amount is suppose 1000rs and other condition type is JBED and we made a condition record and put it some percentage so as soon as we some value in PR00 ,JBED condition type is automatically manipulating the value on the base condition record.
Now i want other than condition record can we trigger one condition type based on other condition type through defining user routine under requirement.
Suppose we have condition type ABC and some amount i have given and other condition type DEF , i want that amount of DEF condition type should automatically come from the Condition type and it should manipulate according to my routine .
eg Condition type    Amount
       ABC                  1000
       DEF                    40
The value 40 should come as 4% of 1000.
I am not maintaing any condition record and i want that this should trigger through some requirement created by me.
i created my routine no 905 and i putted the code inside it.
if komtl-kschl = 'DEF'.
komv-kbetr =   ( komv-kbetr * 4) / 100.
endif.
Now problem is that this code is getting trigger when i m giving value in DEF condition type then it is showing 4 % of it.
But i want as soon as i give value for the condition type ABC and some value 1000
then after pressing enter , one condition type DEF should automatically come with value 40 that too in display mode ,not in change mode.
Please suggestions and solutions regarding this matter , I will be grateful to you.
Manish

hi
In V/06 in the calculation type you can see the entries for "D-gross weight" & "E-net weight"
For the required condition type select the calculation type as gross weight or net weight. Save it.
In MM01 - create material master, here in BASIC DATA 1 SCREEN you have fields for gross weight & net weight.
Maintain the condition record in VK11 for the required condition type.
You can also maintain the scales as required like u said
1 to 10 kgs - 100 rupees,
11 to 25 kgs - 1000 rupees.
Another way could be
The BEST practice to do it is, use of VOFM routine for price calculation (VOFM-->Formulae).
Take help from ABAPer and write a routine such that
if weight = 1 - 10
price = 100.
else if weight > 8.
price = 1000.
else
price = 100.
end if
but the maintainnance of routine is big problem as u might be having many records
Hope this will help you
Vishal

Additional Pricing Condition Type Determination in Returns Oder

Hi Guys
I am working on Returns Sales Process, but I have stuck in pricing?
The thing is I have to determine the additional condition type based on transaction type .i.e. returns order when I create the returns order with ref. to sales order the pricing condition types which is present in the sales order has been copied but the additional condition type is not determined automatically?
I have created the 2 pricing procedure one of sales order and other for returns order.
Can anybody help me out?
Thanks advance

Hi,
All you have done is right. just assign the other pricing proceduere which you created for the document re.
To the combination of sales orgdistribution chaneldivision + cpp( in customer master)+ dpp( for the document re )
So now when you create with the re doument you will automatically get that pricing procedure.
hope this solves.
regrds\
preetham

Header pricing condition types

Hi,
In a purchase order header pricing condition types are appearing twice .
Ex: JCDB    254
      JCDB     20
      JCV1    345
      JCV1     30.
first condition type (ex: JCDB 254) is calculated on net price
second cond type (ex: JCDB 20) is calculated on handling charge.
Only for this particular PO we face this problem.
How the pricing condition types are calculating twice?
regards,
sathya

If I am not mistaken, this is a Purchasing question.
Please post to correct forum.
Regards

How to change exchange rate type for specific pricing condition type

Hello every one,
I have a requirement for billing ie VF01.
currently all the exchange rate are being calculated with exchange rate type 'M' by default.
but now client want it should calculate exchange rate with type 'E' for two pricing condition type for all others it should calculate with type 'M'
Please any body can help me with the exit and code which i can use.
I have checked exits SDVFX008.
but how to change exchange rate with type 'E' only for two conditions.
as changing exchange rate at document header will change exchange rate for all condition type.

You need to assign KOMK-KURST = 'E', for those two condition types. If it had been item number specific, you could have used USEREXIT_PRICING_PREPARE_TKOMK(RV60AFZZ).
Do one thing, put a breakpoint on FM 'PRICING' and then do selective runtime analysis.
Check whether any user exit/BADI/ explicit enhancement are available when condition types are processed in a loop. If nothing is available, try implicit enhancement.
Link to refer for selective runtime analysis - Runtime Analysis for VOFM
Also try with VOFM requirements ( not sure whether changing KOMK-KURST is permissable in requirement as normally we only set sy-subrc values to suppress/allow condition types ). Don't forget to assign requirements against condition types in pricing procedure.

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Table to link FI document number, line item and pricing condition type

Hi,
I am looking for tables to link the FI document number, line item and PO pricing condition type.
Appreciate any help on this.
Thanks.

For any PO in ME23n in which Goods receipt has happened, you can check in the itemdetails->Po history tab in ME23n.
Here you will find the material document number. Just click on the material document, it will take you to anpther screen here you will find a button for FI document.
Click that button for FI document. In PO history istelf you can see the Condition types.
Hope this helps.

Copy Pricing Conditions from Sales Order to Billing

Hi,
Is there anyway to copy pricing conditions for item level from Sales Order to Billing Document at the time of creation of Billing Document.
Thanks

This question is not on topic for the Web Dynpro ABAP forum and has been locked.

Table for existing PO/Sch.Agg pricing condition types

Hi Experts,
Which table will have PO / Sch.Aggrement - pricing condition types with values as maintained in PO (like freight / P&F etc). I have the input of PO/Sch.Agg ref, plant, vendor & material.
We have created Z condition types for freight/ P&F and using the same in PO/Sch.Agg.
Thanks,
Jeeva

HI,
Same status.
In table EKKO also field "Doc. condition no." is updating for PO only, which is same as we find in EKKI. For Sch.Agg it it not updating the Doc.Condition no and remains blank.
Any way i have gone thro a different route. since I am looking for delivery condition for a completed GR, I can pick the conditions from EKBZ table.
Thanks.
Jeeva.

Sales Order Pricing - Condition Type:PR00 inactive

Hi
In Sales Order Item level pricing, condition type PR00 become inactive. It shows reason : Inactive via formulae of incorrect.
Sales Order is partially delivered & billed. For remaining deliveries, system not allowing for billing, showing sales order is incomplete.
Condition Type PR00 maintained manually. Order quantity changed several times.
Please guide me on this.
Regards
Uma

Dear Umasankar
Check in VK12 for the material whether the From To Date is maintained for current period.
Also go to V/08 and check your pricing procedure whether any invalid account key is defined.
Thanks
G. Lakshmipathi

Pricing condition type not working

Hi all,
A pricing condition type is present which is supposed to make the netvalue to zero after the order reason is changed to rejection using va02. But even after the order reason is changed to rejection and we tried to genrate new pricing document, the netvalue is not becoming zero. How can I debug this? The condition type is not determined by using condition records.
Thanks in advance.

Hi Smith
This should be working in the following ways.
1) Order Reason/Rejection Reason being a field in the Key combination with 100% Discount triggering Zero Net Value
if this the case, then you should check in Condition Analysis wheather the value has conrrectly flown in the condition table , if not why it has not flown in to the condition table (It could be missing value in the condition record or a prblem in the field catalogue user exit- you need to take Developer's help as suggested by others)
2) Using a Requirement and changing the Net Value Zero without any condition table field.
If so, put a break point in the requirement and check why this has not been successful in this scenario.
I hope the replies would help you to some extent in solviing the issue.
Thanks
Subbu

Function module to change the value for pricing condition type

Hello experts,
I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
I used many function modules but none are working.
Please kindly suggest a function module that will change the value for a condition type .
I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
Thank you.
CLEAR PRCD_COND.
     SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                          KSCHL = COND_TY.
IF SY-SUBRC = 0.
*    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
*    CLEAR L_COND_CHG-KBETR.
    L_COND_CHG-STUNR = PRCD_COND-STUNR.
    L_COND_CHG-KBETR = COND_PRC.
*    L_COND_CHG-KSCHL = COND_TY.
    INSERT L_COND_CHG INTO TABLE T_COND_CHG.
L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
L_ITEM_GUID = WA_ORDERADM_I-GUID.
INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
    CALL FUNCTION 'CRM_ORDER_READ'
     EXPORTING
       IT_HEADER_GUID                    = HEAD_GUID
       IT_ITEM_GUID                      = ITEM_GUID
     IMPORTING
       ET_ORDERADM_H                     = LT_ORDERADM_H
       ET_ORDERADM_I                     = LT_ORDERADM_I
       ET_PRIDOC                         = IT_PRIDOC_RD
       ET_DOC_FLOW                       = T_DOC_FLOW
*     CHANGING
*       CV_LOG_HANDLE                     =
*     EXCEPTIONS
*       DOCUMENT_NOT_FOUND                = 1
*       ERROR_OCCURRED                    = 2
*       DOCUMENT_LOCKED                   = 3
*       NO_CHANGE_AUTHORITY               = 4
*       NO_DISPLAY_AUTHORITY              = 5
*       NO_CHANGE_ALLOWED                 = 6
*       OTHERS                            = 7
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
INSERT L_PRI_COND INTO TABLE PRI_COND.
LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
L_PRIDOC_CHG-PRIC_COND = PRI_COND.
L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
ENDLOOP.
LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
INSERT L_HEADER INTO TABLE HEADER.
ENDLOOP.
LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
INSERT L_ITEM INTO TABLE ITEM.
ENDLOOP.
L_FIELD-FIELDNAME = 'STUNR'.
INSERT L_FIELD INTO TABLE FIELD.
L_FIELD-FIELDNAME = 'KBETR'.
L_FIELD-CHANGEABLE = 'X'.
INSERT L_FIELD INTO TABLE FIELD.
L_INPUT-FIELD_NAMES = FIELD.
L_INPUT-REF_KIND = 'E'.
L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
L_INPUT-OBJECTNAME = 'PRIDOC'.
INSERT L_INPUT INTO TABLE INPUT.
    CALL FUNCTION 'CRM_ORDER_MAINTAIN'
     EXPORTING
       IT_PRIDOC                     = PRIDOC_CHG
     IMPORTING
       ET_EXCEPTION                  = EXCEPT
     CHANGING
       CT_INPUT_FIELDS               = INPUT.
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
REFRESH EXCEPT.
CALL FUNCTION 'CRM_ORDER_SAVE'
EXPORTING
    IT_OBJECTS_TO_SAVE         = HEAD_GUID
*   IV_UPDATE_TASK_LOCAL       = FALSE
*   IV_SAVE_FRAME_LOG          = FALSE
*   IV_NO_BDOC_SEND            = FALSE
*   IT_ACTIVE_SWITCH           =
IMPORTING
   ET_SAVED_OBJECTS           = SAVED
   ET_EXCEPTION               = EXCEPT
   ET_OBJECTS_NOT_SAVED       = UNSAVED
* CHANGING
*   CV_LOG_HANDLE              =
* EXCEPTIONS
*   DOCUMENT_NOT_SAVED         = 1
*   OTHERS                     = 2
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK AND WAIT.

Hi,,
To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
Alternatively u can use this function module.
CRM_STATUS_DATA_SAVE_DB
BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

Problem in Copying Pricing Condition Type

Similar Messages

Maybe you are looking for