Header level pricing condition error

Hi Friends,
In a PO, I have 5 line items. I am giving freight condition type at header level for the entire po as Rs. 500. But the system calculates the freight charge as 500*5=2500. The freight condition type FRB1 is a fixed charge condition type.
The client wants the absolute freight charge should be for the entire PO.
Please advice how to solve this issue.
Thanks & Regards
Satya

Hi,
the scales have nothing to do with this, they just allow different prices to be stored for different quantities.
But have you had a look at the "qty relevant" flag on the condition type?
Please do check the flags that are set, these do control the calculation.
Also make sure that you are using a condition type that has the "header conditions" flag set on. If you choose one that has only the item condition set on this may not be correct.
FRB1 (the one that you said that you are using) is an ITEM condition and should not be added to the header.
Steve B

Similar Messages

Header level Pricing condition

Hi guys
I have a header condition type which is calculated based on some values from line items but the header conditions should be always be calculated in barrels but my line items can have products in different units like kegs, barrels. What I need to do so that value in my header conditions is calculated in barrels.
Regards
Javed

My header condition = ZPR0
Item condition = ZPR1
My header condition ZPR0 = sum all ZPR1 and give me total price per barrel.
Example
I have the following 3 products on my quotation
Material      qty     Unit     price          total
A001     60     K1     30/K1      1800 gbp
A002     5     barrels      70/barrels 350 gbp
Now total zpr0 = 1800 + 350 = 2150 gbp but I want this to be calculated per barrel
So my required value for ZPR0 should be 1800/185= 9.729 GBP per barrel
1 K1 = 3 barrels
Please let me know what should I do to get this done.

Header level pricing is not triggered

Hi
I am facing problem when I change some line item data on my sales transaction then header level pricing is not triggered though system triggers line item pricing and all the line item condition types are calculated but header condition types are not calculated.
Would you please let me know how can I trigger my header level pricing.
Regards
Javed

Hi Javed,
As I understood your problem, the item level condition types are calculated and condition records are fetched while the header level conditions are not calculated. This is a strange thing because the pricing procedure associated with the document will have condition types marked relevant for header and item level. Depending on these and the formulae associated with the condition types in the pricing procedure, IPC calculates the condition values and are summed up as different items at the header level.
I would suggest you to to switch on the debugging parameter for your user id and try to debug to check condition types failing at the header level.
Regards,
Pavithra
**PS : Please reward points if you find this useful.

Item level pricing condition record is not getting recognized

Hi,
In our scenario we have to maintain the additional charges based on Plant. For this purpose I have created the condition table 900 which contains the following fields
Sales Org/Dist Chal/Divi./Plant
I have maintained the condition record for the table, Which has been downloaded to CRM successfully.
When I create the order in CRM price of the product is getting recognized where as additional charges condition records are not getting recognized.
When I check the Access I found that header level data .i.e. sales org/dist chal / divion has been recognized and plant has not been recognized that values are like this 00000000000000000000000000
I have checked the plant it has been downloaded successfully to CRM
So, can anybody help me out?
Thanks

Hi,
Check in the access sequnce exclusive indicator activation, it might be selected to the previous Condition Tables, if it is selected than system will not check further available/maintained condition reocrds.
Regards
Naren..

PO header level excise condition in MIGO are wrong

Hello ,
While doing goods receipt
Item excise Codition values are as follow
BED = 959.71
ECS = 19.24
SECESS = 9.62
But at header level it is showing as ( divide by 100)
BED = 9.59
ECS = 0.19
SECess = 0.09
Please help to resolve this issue

Hello,
have u used any calculation type ? if yes then remove that first.Please check in Tax procedure.
regards,
sujit

Pricing condition error

Hi,
In pricing when I am trying to enter a percentage based k007 type condition.... for a particular customer...........it is showing this error
I want to enter 1.000 % for 100 uni
1.000- exceeds the limit 2.000- for condition type k007
message no. VK038

Hi Erik
i know its very late , but today i came across the same situation , and found the solution its not upper and lover limit , its a Customization ,
t -code: OVB2 ,
and in this t code u restrict the value of condition type ,

Middleware-Pricing condition error while downloading pricing objects

Dear all,
I am encountering an error after i replicated the pricing objects from R/3 to CRM. Below is the description of that error as seen in T-code SLG1
There is no entry in the object directory (TADIR) for R3TR TTYP /1CR/RCBCUS503_T
Please provide me with some pointers to resolve this issue.
Thanks & Regards
Yogesh

Hi Yogesh,
I am facing exactly the same problem,
How did you solve it?
Any comments gurus?

Clearing Sales Tax at Header Level in an Order

Hi,
I have a requirement to not charge any tax on an order if the credit card used on the order is a government credit card. Currently I have implemented this logic in USEREXIT_SAVE_DOCUMENT_PREPARE. I am able to clear out the sales tax at the line level but this change does not reflect at the header level. I have to manually click on update pricing to zero out the tax displayed at the header level. I could not find a variable to tap into header level pricing condition and tax value field.
I would greatly appreciate if any one can give me some pointers on where to look for header level data for tax. Also, is there any better user exit to implement this functionality.
Folliwing is the code I am using to clear out line item level tax:
          LOOP AT XKOMV INTO WA_XKOMV WHERE KSCHL EQ 'UTXJ'.    "GET THE TAX CONDITION
              CLEAR WA_XKOMV-KWERT.                               "Set the TAX to 0
              CLEAR WA_XKOMV-KAWRT.
              CLEAR WA_XKOMV-KBETR.
              MODIFY TABLE XKOMV FROM WA_XKOMV
                TRANSPORTING KWERT KAWRT KBETR.
          ENDLOOP.
          LOOP AT XVBAP INTO WA_XVBAP.    "GET THE TAX VALUE
              CLEAR WA_XVBAP-MWSBP.                               "Set the TAX to 0
              MODIFY TABLE XVBAP FROM WA_XVBAP
                TRANSPORTING MWSBP.
          ENDLOOP.
Thanks,
Paresh

Hi,
In the case of sales cycle, All the item level taxes are summirised and come to the header level. So we can't find the conditions at header level for taxes. Check the user exit , because, the values are already moved to the header level structure and then you are clearing the item level taxes. I hope thats why the changes are not reflected in header level.
Regards,

Pricing Condition Values in Sales order

Hi Guru's
Where the Header level Pricing condition Values stored in Sales Document?
Thanks and Regards
Srinivas Kapuganti

Hi srinivas
Generally the values are stored at the following tables :
KOMK - header data is stored
KOMP - Item data is stored
You can check these tables through SE11 or SE16
Regards
Srinath

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

Implement pricing conditions GAU1 and GAU2

Dear All,
I want to implement pricing procedure for precious metals.
Anyone who has implemeneted the procedure at their end please guide me towards the same .
In PO I am getting following error in condition type GAU1 Inactive status as "X" and message as " Inactive via formulae of incorrect "
Please help
Thanks
Garima

Actually i haven't worked on metal prices...but once i had faced same type of error in my freight condition types...SAP responded with some solutions which i am posting...please see whether these are useful or not:
(1) Condition row is inactive
The condition type (group condition or item condition) is listed with or without a pricing result in the condition row on the condition screen for the subitem. However, the condition value is ignored. On the condition details screen (double-click on the condition row), an indicator is set for 'Inactive'.
(1.1) Inactive indicator 'A condition exclusion item'
You have selected an exclusion procedure at subitem level for your freight cost price determination schema. The condition type with inactive status 'A' was excluded using this procedure in favor of another condition type (set as inactive).
Check: In favor of which condition type or condition exclusion group was the condition type in question excluded?
=> Use Customizing transaction T_32 to determine the condition exclusion group to which the relevant condition type was assigned and use Customizing transaction TOK8 to determine the exclusion procedure assigned to the price determination schema.
(1.2) 'K - Inactive due to calculation basis/shipping material type'
An automatically determined or manually created condition type is set as inactive (inactive indicator 'K'), even though a valid condition record was found according to the analysis.
Check 1: Do all handling units in the subitems belong to a 'material group for packaging materials' that is assigned to this particular packaging material type in Customizing? The calculation base of the condition type refers to handling units (calculation bases C, E or F) and, in Customizing (transaction T_06), a packaging material type (synonym: shipping material type field T685A-VHART) was specified for the condition type?
=> Material numbers are assigned to 'material groups for packaging materials' in the material master (transaction MM02). 'Material groups for packaging materials' are assigned to packaging material types in Customizing: Transaction VHZU or IMG -> Logistics General -> Handling Unit Management -> Basics -> Define Allowed Packaging Materials
Check 2: Was a valid condition record for this condition type found in all subitems for the calculation base used?
=> Extend the condition pricing data (transaction TK11) so that valid condition records can be found for all subitems. If necessary, use a price 0.
Check 3: Was the condition type only created manually for individual subitems?
=> Usually, manual conditions must be created for the calculation base in all subitems, with the value 0 if necessary. If changes were also permitted at header level for an item condition (in Customizing transaction T_06), you can automatically create identical entries in all subitems of the calculation base by creating the condition at header level. You can then adjust these templates (with the value 0 if required) at subitem level.
Notes: For background information and options for 'Inactive K', see also note 318775. For the system response in the case of manual changes to freight conditions, see consulting note 773038.
(1.3) Inactive 'L - Condition exclusion header or inactive at header level'
The condition type could not be evaluated as a group condition or was excluded as part of a header exclusion because of another condition type.
Check 1: Could the condition group be evaluated at all?
=> On the condition screen of the header conditions (enter '=kkon' in the command field), check whether different subgroups have been created for the condition type. If this is the case, several condition rows will be displayed for the same condition type. Also check the Check the scale input values in the individual condition display (double-click on the condition row).
Since neither the price determination analysis nor the condition record display is available at header level, you must check the price table for the condition type using a subitem: Is there also a valid scale level for each scale input value? The lowest scale level is often missing in from-scales and the highest conceivable scale level is often missing in to-scales. For example, a to-scale of 'to 30 TO' cannot evaluate any shipments with 31 tons. You therefore need to extend this scale to 'to 99999 TO'.
Check 2: Did you select an exclusion procedure for your freight cost price determination schema at header level?
=> Use Customizing transaction TOK8 to check whether the indicator 'A - header exclusion' was entered in the relevant column for the exclusion procedure that is assigned to the price determination schema. If this is the case, the group condition inactive status 'L' may have been excluded in favor of another group condition type using this exclusion (set as inactive).
Use Customizing transaction T_32 to determine the condition exclusion group to which the condition type in question was assigned and use Customizing transaction TOK8 to determine the condition type or condition exclusion group in favor of which the group condition type in question could have been excluded.
Check 3: Are you using your own scale or condition formula for a multi-dimensional group condition?
=> You may try to analyze the import parameter KOMK or KOMP for a group condition in this formula. However, these parameters are not filled in group processing: '...The components komk and komp are initial during processing of group conditions...' ('i - Formulas' button on the 'Scales for Conditions' detailed screen in Customizing transaction T_06).
The inactive indicator KINAK is set by default to 'T' for group processing (inactive at header level) and is converted to the more general 'L' by the subsequent price determination.
(1.4) 'X - Inactive via formulae or incorrect'
If an error occurs during processing of multi-dimensional conditions (for example, during conversion to scale units or in a customer-specific formulas for scale bases), the condition is usually set to inactive status 'X'.
Check: Are all formulas used in connection with this condition (condition base formula, scale base formula, condition value formula) error-free?
(1.5) 'Y - Inactive because of subsequent price'
According to the price determination logic in SD, there can only ever be one valid price in a pricing procedure. All other conditions are surcharges or discounts in some shape or form. Accordingly, the last, valid pricing condition (valid condition record and not equal to zero) always applies. All pricing conditions in the schema with a lower level number are set to inactive status 'Y inactive because of subsequent price'.
Check: If the required pricing condition was unintentionally set to inactive status 'Y' by a subsequent pricing condition, you must decide (using an exclusion procedure, if required) which of the pricing conditions is varied. All pricing conditions with inactive indicator 'Y' are included in the exclusion procedure.
Regards,
Indranil

Issue in maintaining the freight condition in SRM pricing conditions

Hi All,
We have maintained the freight condition in SRM pricing conditions But when a buyer try to add the freight condition it does not give any field to add the value.We want the freight condition at the header level.
Let me know if there is any service needs to be activated or we have to activate any business function to enable this.
Please find the attached document to check the settings and actual issue while entering the freight condition.
This is urgent and please provide your suggestion to avoid this issue.
Thanks,
Ankur

Hi Anil,
Its not a standard functionality to get the Header level price condition in SRM PO . I got to know that we need to implement note 1898304 for SRM 7.13 SP01 and activate a Business function.Can anyone let me know how it used to handle in previous versions.
Thanks,
Ankur

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

T code/ report to list all material sales pricing condition with deletion i

I create sales org/ material level pricing conditions in VK11. Some unwanted material pricing conditions are with Deletion indicator active. Iu2019m looking for a report to list all material sales pricing condition with deletion indicator active.
Please advice me on this.

Hi Goto v/ld and select 16 which stands for individual prices, and then populate sales organization, distribution channel, customer ,material numbers,etc...and tick "Cond.marked for deletion" check box in "list screen" tab which is the most important, execute you will be able to see all material pricing condition even though it had been deleted.

How can I have the pricing conditions at the item and header level of the d

How can I have the pricing conditions at the item and header level of the delivery? There exist "condition" tabs both the header and the item level of the delivery but the contents of the tabs are empty. I'll be happy if you can help me. Thanks in advance....

Hi
If you want to have the pricing procedure at delivery level then you need to assign a pricing procedure at delivery level also
Just go through the path to maintain the pricing procedure at delivery level.
IMG -> Logistics execution -> Shipping -> Basic Shipping Functions -> Pricing -> Pricing Procedure. for Delivery.
But can you be more clear if the above one is not your query ?
Regards
Srinath

Header level pricing condition error

Similar Messages

Maybe you are looking for