Implement pricing conditions GAU1 and GAU2

Question

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

Answer 1

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