How To Fix COND_SSCUI009 - Consulte el texto explicativo antes de modificar el campo &1.


SAP Error Message - Details

  • Message type: E = Error

  • Message class: COND_SSCUI - Message Class for Condition Technique SSC UIs

  • Message number: 009

  • Message text: Consulte el texto explicativo antes de modificar el campo &1.

  • Show details Hide details
  • ¿Qué causa este problema?

    Changing the value of &V1& for a condition type may influence existing
    documents. You should consider the following points:
    If you change the value defined in this field and prices in existing
    documents are recalculated, the value of the condition may change. This
    could lead to a different price, discount, surcharge, tax, and so on.
    The following requirements must be fulfilled for the price of an
    existing document to change:
    The condition type is part of a pricing procedure.
    This pricing procedure is used in an existing document.
    A repricing of this document has been triggered.
    The determined value of a condition needs to be different before and
    after the repricing.

    El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.

    For the following fields, please consider the consequences of changing a
    value. The stated examples make no claims for completeness and do not
    include all cases that may influence the pricing result and may need to
    be considered.
    Access Sequence
    Access sequences define sets of business attributes for which the system
    determines condition values. If you change the access sequence, the
    system will determine other condition records. The system will either
    find new records containing different values or it may no longer find
    previously used records, if the new access sequence doesn?t contain
    accesses that were part of the original sequence.
    Condition Class
    Condition classes classify condition types, e.g. prices, surcharges or
    discounts. The system handles condition classes differently during price
    determination. For example, a pricing procedure may contain only one
    active condition type of condition class Price. A condition of condition
    class Price deactivates preceding conditions of condition class Price.
    Changing the condition class may therefore lead to a different pricing
    result. This change takes effect when a new price determination is made.
    Calculation Type for Condition
    The determined condition amount may change its meaning in the price
    calculation. For example, it may change from a fixed to a percentage
    value. Ensure that the settings of the pricing procedures and the master
    data that use the condition type are consistent. Also ensure that they
    are consistent for any base formulas, from/to steps, and so on. The
    change takes effect when a new price determination is made).
    Condition Category (Examples: Tax, Freight, Price, Cost)
    Changing the condition category will affect the point in time of
    redetermination changes (for example, taxes are usually redetermined
    during billing). The change takes effect when a new price determination
    is made. Account keys can also depend logically but not technically on
    the condition category. The system will continue to post to the same
    accounts although logically they may have changed from Cost to Freight.
    Rounding Rule
    If you change the rounding rule, for example from rounding up to
    commercial or vice versa, this may lead to different pricing results in
    existing documents should a price recalculation be triggered.
    Structure Condition
    If you select the structure condition value <LS>Cumulation Condition</>,
    you must adjust the step in which you use the cumulation condition in
    all pricing procedures as follows:
    To the <LS>Alt. Calculation Type </>field, you either assign the SAP
    standard formula <LB>0000036</> or a customer-defined formula.
    You select the <LS>Statistics </>indicator.
    If you select the structure condition value <LS>Duplication Condition</>
    , no follow-up action is necessary.
    If you remove the structure condition value <LS>Cumulation Condition</>,
    in the pricing procedures that used the cumulation condition, you can
    unassign the SAP standard formula <LB>0000036 </>(or a customer-defined
    formula) and deselect the <LB>Statistics </>indicator.
    Group Condition
    For group condition, the value that is used to determine the scale level
    can be a cumulation of different document line items. This may influence
    the condition value. Make sure that the formulas used in corresponding
    pricing procedures are suitable for group conditions. For non-scale
    conditions, amounts that are entered at header level are distributed
    across all items.
    Routine Number for Creating Group Key
    This field determines how the scale basis for a group condition is
    calculated and how it may influence the condition value. This also
    affects recalculation (and not only redetermination).
    Manual Entries
    This flag controls whether a user can enter a condition manually in a
    business document. In addition, it specifies whether the system
    prioritizes manual or automatic conditions. Any change may lead to
    different pricing results, if manual and automatic conditions of the
    same type are used to calculate the pricing result of a document item.
    The change will also affect existing documents, if pricing results are
    recalculated.
    Reference Condition Type
    If you change the reference condition, the system will determine an
    alternative different condition record. This in turn might change the
    pricing result. The change comes into effect when a new price
    determination is made. Ensure that a condition record exists for the new
    reference condition.
    Reference Application
    If the reference application is changed, a different condition record is
    determined, which might change the pricing result.
    Condition Update
    Condition update determines whether limit values are relevant to
    pricing. For example, if the flag is removed, a potential maximum limit
    for the base value is not considered.
    Scale Basis Indicator
    The scale basis indicator determines the scale on which a measure is
    based (for example, quantity, volume, and so on). This may change the
    condition value. Check if the scale base indicator is consistent with
    the used scale base formula. Also, check if the from/to step range is
    correct.
    Scale Type
    The scale type determines how a scale is calculated and may change the
    value of the condition. Check if scale type is consistent with the used
    scale base formula. The change from or to "D - graduated-to interval
    scale" must not be made for conditions that have already been used in
    existing documents. This may lead to incorrect results should the
    quantity change.
    Formula for Scale Base Value
    Determines how the scale base value is calculated, which may influence
    which scale level is used. Please check if the from/to step range is
    correct.
    Scale Unit
    Determines which unit is used for scale determination for volume or
    weight group conditions. This may change the value of the condition. A
    pricing error will occur if the corresponding conversion factor has not
    been maintained for the selected scale unit.
    Currency Conversion
    Changing this value might lead to a different pricing result since you
    are changing the point in time of the currency conversion. Note: The
    change also affects existing documents, if a repricing is carried out.
    Quantity Conversion
    Changing this value leads to the use a different conversion logic and
    hence possibly to a different result, if the sales quantity unit is
    equal to the condition quantity unit. Note: The change also affects
    existing documents, if a repricing is carried out.
    Pricing Date
    This fields controls the date used for the search for valid condition
    records. The use of a different date may lead to different conditions
    being found in a document. Note: Changing this flag will affect also
    existing documents, if a redetermination of condition records is carried
    out
    Condition is Relevant for Accrual (for example, Freight)
    Indicates if the system posts the amounts resulting from this condition
    to financial accounting as accruals. The condition is always
    statistical, and the accruals account must be defined. The system
    ignores this indicator if, in the pricing procedure that you select, you
    also select the <LS>Relevant for Account Determination </>indicator.
    Condition for Intercompany Billing
    Indicates that the condition is a internal costing condition. The
    condition may be handled differently in billing processes and may change
    the result of affected documents. Usually intercompany billing
    conditions have requirement "22 - Inter-company". Please keep in mind
    that intercompany billing conditions are redetermined with repricing
    type "G - Copy pricing elements unchanged and redetermine taxes".

    Respuesta del sistema

    ¿Cómo arreglar este error?

    Procedimiento para Administradoras de Sistemas


    Extracto de mensaje de error del sistema SAP. Copyright SAP SE.


Smart SAP Assistant

  • ¿Cuál es la causa y la solución del error de SAP COND_SSCUI009 - Consulte el texto explicativo antes de modificar el campo &1. ?




    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Mensajes de error de SAP relacionados

Haga clic en los enlaces a continuación para ver los siguientes mensajes relacionados:

Haga clic en este enlace para buscar todos los mensajes de SAP.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker