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

Similar Messages

Header Pricing Condition (SD)

Hello,
We have a header pricing condition type both applicable to header and line items. When manually putting an amount on the header, it automatically distributes the amount on the line items proportionally.
When running in batch or IDoc via requirement routines (or any VOFM routines), how can I populate the header amount so that it will distribute the amount automatically also on the line items?
I normally do this on the line item level by modifying XKWERT on a requirement routine but I cannot get it to to work when the target is a header pricing condition.
Please help me if you have any ideas.
Thanks in advance,
John

which include? i think you forgot to include the name of the include

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.

Change header pricing condition in sales order

Hi,
I have an requirement in VA01 and VA02 to automatically edit one header pricing condition. The user can able to change the value of that condition type in header not in items . Does anyone know what user exit I can use for this requirement.
Thanks

Hi Sunil,
Plealse find below 2 methods to change header pricing conditions in sales order.
1.Goto SE38, give prog name as MV45AFZZ and in that write logic under USEREXIT_PRICING_PREPARE_TKOMK . (OR)
2) The same can be done by creating a Alt Calculation type routine through VOFM and writng the logic in the routine, which will then be assigned to the pricing procedure in the condition type which will automatically calculate the condition.
Try with the options mentioned above..
Regards,
KK

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?

Header Pricing conditions in BAPI function module

I am using BAPI function module BAPI_SALESDOCU_CREATEFROMDATA1 to create sales orders through program.
It is working fine with item level pricing conditions.
But my requirement is ... I need to update few pricing conditon types in item level and one in header level.
Could you please help me where I need to pass header pricing conditions. Please help me.
        CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
          EXPORTING
            SALESDOCUMENT             = SALESDOCUMENT
            SALES_HEADER_IN           = SALES_HEADER_IN
          SALES_HEADER_INX          =
          SENDER                    =
            BINARY_RELATIONSHIPTYPE   = 'VORL'
          INT_NUMBER_ASSIGNMENT     = ' '
          IMPORTING
            SALESDOCUMENT_EX          = SALESDOCUMENT_EX
          TABLES
            RETURN                    = RETURN
            SALES_ITEMS_IN            = SALES_ITEMS_IN
          SALES_ITEMS_INX           =
            SALES_PARTNERS            = SALES_PARTNERS
            SALES_SCHEDULES_IN        = SALES_SCHEDULES_IN
          SALES_SCHEDULES_INX       =
            SALES_CONDITIONS_IN       = SALES_CONDITIONS_IN.
          SALES_CFGS_REF            =
          SALES_CFGS_INST           =
          SALES_CFGS_PART_OF        =
          SALES_CFGS_VALUE          =
          SALES_CFGS_BLOB           =
          SALES_CCARD               =
          KEY_TABLE                 =
Thanks in advance.
Raghu

If the correct configuration allows for manual entry of the condition type you want to populate, You can map your value using
' ORDER_CONDITIONS_IN' . If item level map line number, cond step number of the condition type in your pricing procedure, your condition type you are using, condition value you are sending into the system, currency, and cond unit. If it is a header condition, then send in 000000 as the item number.   You can also consider using BAPI_SALESORDER_CREATEFROMDAT2

Freight pricing condition types

Hello Experts,
I have this one business scenario to be addressed.
There are 3 line items in the sales order, there is a freight condition type in every line item, Now, when i am creating a delivery document, only the least freight value should go to the delivery document,
For instance: in sales order 3 line items, in line 10, freight is 10$, in line 20 it is 20$ and line 30 it is 30 $
so,only 10 $ should go to delivery
I have build this logic, hope this works, but I need some expert advise.
Pass the values of the freight item condition types to a sub-total and store it in there. Create a header freight condition type and write a routine in the calculation type to fetch the least value from the sub-total and put it in the header condition.
Then thru copy control pass on this header value to the delivery document.
The question thats hitting me is, will the header frieght condition get updated in the run time with the least value from the item condition types.
Please let me know if you have any other work-around.
Thanks to all in advance,
Beatle

Hi Beatle
As per your example, if least value should go to delivery then you need to assign new requirement to the freight condition type in the pricing procedure You have to assign the same requirement to all freight condition types in the pricing procedure.The header freight condition type will get updated provided the requirement that you are assigning is correct.So make sure that in the requirement the logic that you are giving and writing is correct.
Regards
Srinath

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

Unable to update the header Pricing Condition of Customer Quotation

Hi Friends,
I am trying to change the Customer Quotaion using the 'BAPI_CUSTOMERQUOTATION_CHANGE'.
I am able to update the Header details and item details,but When it comes to pricing Conditions the Following errors I am getting
000000: Operations with Conditions of type F not allowed(ZZHD).
as it is a Header pricing Condition, I am passing Item number as 000000,even I tried to Comment and see,but the same issue.
Following is are the pricing Condition details that I am passing to BAPI.
CLEAR: wa_quote_condition_in,
         wa_quote_condition_inx.
wa_quote_condition_in-itm_number        = '000000'.
wa_quote_condition_inx-itm_number       = '000000'.
wa_quote_condition_in-COND_COUNT     = '01'.
wa_quote_condition_inx-COND_COUNT    = '01'.
wa_quote_condition_in-cond_type            = 'ZZHD'.
wa_quote_condition_inx-cond_type         = 'ZZHD'.
    wa_quote_condition_inx-updateflag      = 'U'.
lv_zzhd = ( ls_nd_payment-transport_charg / 10 ).
wa_quote_condition_in-cond_value     = lv_zzhd.
wa_quote_condition_inx-cond_value    = 'X'.
APPEND: wa_quote_condition_in TO it_quote_condition_in,
          wa_quote_condition_inx TO it_quote_condition_inx.
CLEAR: wa_quote_condition_in,
         wa_quote_condition_inx.
Please help in tracing the above issue.
Regards,
Xavier.P
Edited by: Xavier on Sep 7, 2011 10:59 AM
Edited by: Xavier on Sep 7, 2011 11:00 AM

Hi prasad,
Please find the you will find 'condition type paramter in the structers bapicond, bapicondx.
data :it_quote_condition_in    TYPE TABLE OF bapicond,
         wa_quote_condition_in    TYPE bapicond,
         it_quote_condition_inx   TYPE TABLE OF bapicondx,
         wa_quote_condition_inx   TYPE bapicondx.
CALL FUNCTION 'BAPI_CUSTOMERQUOTATION_CHANGE'
    EXPORTING
      salesdocument                = ls_nd_payment-vbeln
      quotation_header_in          = wa_header
      quotation_header_inx         = wa_header_inx
     simulation                   = 'X'
BEHAVE_WHEN_ERROR            =
INT_NUMBER_ASSIGNMENT        =
   logic_switch                 = wa_logic_switch
NO_STATUS_BUF_INIT           = ' '
    TABLES
      return                       = it_bapiret2
      quotation_item_in            = it_order_items
      quotation_item_inx           = it_order_items_inx
     partners                     = it_partners
PARTNERCHANGES               =
PARTNERADDRESSES             =
      conditions_in                = it_quote_condition_in
      conditions_inx               = it_quote_condition_inx
QUOTATION_CFGS_REF           =
QUOTATION_CFGS_INST          =
QUOTATION_CFGS_PART_OF       =
QUOTATION_CFGS_VALUE         =
QUOTATION_CFGS_BLOB          =
QUOTATION_CFGS_VK            =
QUOTATION_CFGS_REFINST       =
    schedule_lines               = it_order_schedule
    schedule_linesx              = it_order_schedule_inx
   quotation_text               = it_texts
QUOTATION_KEYS               =
EXTENSIONIN                  =
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
Regards,
Xavier.P

User exit to add header pricing condition in sales order

Hi experts,
I have an urgent requirement in VA01/VA02 to automatically add a header pricing condition and rate (Kanban charges) for a certain type of Sales order (Kanban Sales order). Does anyone know what user exit I can use for this requirement? Also, the additional header pricing condition should be included in the net value for the item.
Thanks!

HI Leo
To add a condition price for a condition type, this has to be assigned in the pricing procedure. For each condition type in a pricing procedure, we will have access sequences. If we follow this approch, the price is automatically extracted basing on the access sequences when condition records are maintained. For this, no coding is required and everything can be done by configuration by Functional consultant.
Naren is right to point out on the same.
If you need to change the price for a particular condition which already exists, you can go by pricing routines. Go through transaction VOFM for the same.
I advice you to discuss with your functional consultant and understand the requirement and then go for modifying accordingly.
Kind Regards
Eswar

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

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]

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

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.

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.

Header pricing condition types

Similar Messages

Maybe you are looking for