Pricing procedure print field

hi,
in v/08 pricing procedure what is the use of print indicator
.1 Where the condition line gets printed is it in printout
2 condition line means is it value & cindition type
Pl suggest

Hi,
Print ID for condition lines
Controls issue of condition lines when printing documents such as order confirmations or invoices.
In releases previous to 4.0, the following print indicators are available :
' ' : Condition line is not printed
'X' : Condition line is printed at item level
'S' : Condition line is printed in totals block
The following standard logic is set out for these printing indicators:
Item POS of the last condition line is determined with 'X'.
All condition lines that contain an item smaller than POS in the pricing procedure are only printed if print indicators 'X' or 'S' are set.
All condition lines that contain an item larger than POS in the pricing procedure, that come before the first tax condition line and which have a non-statistical VAT condition, receive printing indicator 'S'. The same applies for condition lines that contain an item larger than POS in the pricing procedure, that come after the first tax condition line and an active non-statistical VAT condition.
Condition lines that represent a tax condition type are always printed in totals blocks with print indicator 'S' (set internally or externally).
Condition lines that represent a condition type that is not a tax condition type are only printed with print indicator 'S' (set externally or internally) if the condition value of the condition line is not zero. Condition lines that do not represent a condition type (i.e. subtotals) are only printed with print indicator 'S' or 'X' (set externally or internally) if the condition value of the condition line is different from the condition value of the previous condition line in the pricing procedure.
To provide a better overview of this process, 8 more print parameters are available as of Release 4.0. These print indicators cannot, however be mixed with the three previous print indicators ' ', 'X' and 'S' in the pricing procedure. This means that the new indicators are only taken into account if a no condition lines in the pricing procedure contain printing indicators 'X' or 'S'.
The new printing indicators have the following settings, and corresponding influence on processing.
regards,
US

Similar Messages

  • Re: Pricing Procedure -Print option

    Hi
    In Pricing Procedure - Print option what is the difference between X ,S and A.
    Regards
    Debasish

    Dear Debashish,
    I am sure you read the F1 help. but still would like to put my view in hope that it will resolve your problem.
    As per my understanding of the explanation given there goes, these field follow a standard logic, which is already mentioned in F1 help. I will try to elaborate the same. and sure will make more sense.
    if you leave it blank,
    Point 1 : System will consider all the pricing conditions (e.g PR00 ),etc available in pricing and at the end of these conditions last condition will be determined with "X"
    point 2 : all the condition values which are smaller than pricing (e.g PR00 value )will only be printed if the print field is marked either with "X"  or "S"
    Point 3 : all the conditions which are greater than the pricing condition (e.g PR00) and are coming before the tax conditions the field will be automatically marked as "S" ( which is nothing but for totals of few conditins )
    Poiint 4: all the tax conditions are always marked with "S"
    Point 5 : if  you want to mark the field "s" it should fullfill criteria as
                             A) condition types which are non zero
                             B) are not tax conditions also,
                 condition lines in pricing procedure which are not condition types e.g sub totals, you can mark the field as "X" or "S" but they will get printed only if the condition line has different value than the earlier condition line.
    Please also read the next explanation given in F1 help will be useful.
    Please close the thread if answered.
    Regards,
    Paresh

  • Pricing procedure Print ID

    Hi friends,
    There is print field in pricing procedure called "a". If the Condition Type = 0 would it still be printed? If not is there a nother oppetunity to see "0" on the print?
    Thanks.

    Hello,
    This is the explanation as I have found it a couple of times:
    Controls issue of condition lines when printing documents such as order confirmations or invoices.
    Use
    In releases previous to 4.0, the following print indicators are available :
    o   ' ' : Condition line is not printed
    o   'X' : Condition line is printed at item level
    o   'S' : Condition line is printed in totals block
    The following standard logic is set out for these printing indicators:
    -     Item POS of the last condition line is determined with 'X'.
    -     All condition lines that contain an item smaller than POS in the pricing procedure are only printed if print indicators 'X' or 'S' are set.
    -     All condition lines that contain an item larger than POS in the pricing procedure, that come before the first tax condition line and which have a non-statistical VAT condition, receive printing indicator 'S'. The same applies for condition lines that contain an item larger than POS in the pricing procedure, that come after the first tax condition line and an active non-statistical VAT condition.
    -     Condition lines that represent a tax condition type are always printed in totals blocks with print indicator 'S' (set internally or externally).
    -     Condition lines that represent a condition type that is not a tax condition type are only printed with print indicator 'S' (set externally or internally) if the condition value of the condition line is not zero. Condition lines that do not represent a condition type (i.e. subtotals) are only printed with print indicator 'S' or 'X' (set externally or internally) if the condition value of the condition line is different from the condition value of the previous condition line in the pricing procedure.
    To provide a better overview of this process, 8 more print parameters are available as of Release 4.0. These print indicators cannot, however be mixed with the three previous print indicators ' ', 'X' and 'S' in the pricing procedure. This means that the new indicators are only taken into account if a no condition lines in the pricing procedure contain printing indicators 'X' or 'S'.
    The new printing indicators have the following settings, and corresponding influence on processing.
    -   'A' : in total: general
    -   'B' : in total: if value <> zero
    -   'C' : in total: if value <> value of predecessor
    -   'D' : in total: if value <> zero and value <> value of predecessor
    -   'a' : at item : general
    -   'b' : at item : if value <> zero
    -   'c' : at item : if value <> value of predecessor
    -   'd' : at item : if value <> zero and value <> value of predecessor
    Trust this helps.
    Regards,
    Jan Pel

  • What is the meaning of this column in the pricing  procedure?

    Dear Gurus,
    What is the meaning of this column in the pricing procedure?
    thanks..

    subtotal field : Subtotal field is used to pass the value to some other field in PO .
    for ex: using value 9 you pass the value to field komp-brtwr. so that this can be used in  any other routine in the pricing procedure.
    requirement field: if there is a scenario that condition type should come in pricing on some condition like vendor country is india. in that case use create the requirment and attached this requirement.in this requirment you put logic and set the sy-subrc value 4 or 0.

  • Getting Pricing Procedure Name  CRM_COND_COM_BADI- item

    Is there any function module that I can call to get the Pricing Pricedure name used in the order. I want to determine the same in the CRM_COND_COM_BADI - ITEM_COMMUNICATION_STRUCTURE.  So What I have is the irem GUID.
    Thanks,
    Ravi

    Hi Shanto,
                    Thanks for the response.
    But which structure from this FM has the pricing procedure name? can you give me more details to the field and the structure level because I cehceked the structures from this function module and it does have pricing conditions details but I could not find the Pricing procedure name field.
    I might be missing it so it would be great if you could get me the field level deails.
    Ravi

  • How to replicate a new pricing procedure from SAP ERP?

    Dear Experts,
    I have set up a new pricing procedure in the ERP backend and I would like to replicate this to SAP CRM.
    A replication using object DNL_CUST_CNDALL has been executed once in the past.
    What would be the best way for me to download the new pricing procedure without overwritting any of the existing pricing settings in SAP CRM?
    Thanks,
    Dan

    Hello Dan,
    The views in CRM pricing customizing do not allow to change the pricing procedures, condition types and access sequences that have been downloaded from the ERP system. You will see a field in customizing Source System with value A indicating that these were not created originally in CRM and the view does not go to edit mode.
    In case a i.e. condition type had been created originally in CRM with the same name as a condition type that exists in the ERP the download of the adapter object will not delete the condition type that was created in CRM.
    Therefore it is safe to execute the initial download of the adapter object DNL_CUST_CNDALL without filtering. If you have many pricing procedures in the ERP and you do not want to transfer its customizing to CRM you can create your own adapter object by copying the content of DNL_CUST_CNDALL ( to be on the safe side and keep the original) and then add a filter in your adapter object ,for example in pricing procedures using field KALSM of table T683S, including all the pricing procedures that must be transferred to CRM u2013 those that were transferred in the past and the one that you want to transfer now .However this filter is optional, most SAP customers do not change the standard filters.
    The usual options are:
    -- Download only DNL_CUST_CNDALL (or a Z object that was created based on DNL_CUST_CNDALL) which contains client dependent and also  independent customizing ( i.e access sequences, condition tables).  Condition tables may be generated too and it can take longer, maybe up to 45 minutes or so.
    -- If you have made changes only to pricing procedure(s) or condition types u2013 client dependent customizing--  it will be enough if you download only DNL_CUST_PRC. As there is no generation of condition tables the download will be faster.
    But you must consider that you should not download both adapter objects at the same time ( overlapping times), as part of the content being downloaded is the same and the database will be inconsistent. This can cause errors in pricing, not a severe issue, as it can be solved by a new download of  DNL_CUST_CNDALL, but an issue that causes trouble as it is sometimes difficult to determine the root cause of the problem. So if you for whatever reason ( i.e. additional changes in a condition type) download both adapter objects you should always check R3AM1 and download the second object when the download of the first one has finished ( green light in transaction R3AM1)
    Best Regards
    Luis Rivera

  • Condition type field when Define Pricing Procedure Determination

    Hello Gurus,
        there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
    Many thanks,
    Frank Zhang

    Here is are the details of various fields while configuring pricing procedure.
    A. STEP
    This indicates the number of step-in the procedure.
    B. COUNTER
    This is used to show a second ministep
    C. CONDITION TYPE
    This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
    D. DESCRIPTION
    This forms the description of the condition type.
    E. FROM
    This is used to define the progression of the calculation and range of subtotals
    F. TO
    This is used to define the progression of the calculation and range of subtotals
    G. MANUAL
    This function enables to allow the condition type to be entered manually also apart from automatic pickup.
    H. MANDATORY
    This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
    I. STATISTICS
    This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
    J. PRINT
    The activation of this function will enable the printing of the values and conditions to the document.
    K. SUBTOTAL
    A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
    L. REQUIRMENT KEY
    This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
    M. ALTERNATE CALCULATION TYPE
    This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
    N. ALTERNATE CONDITION BASE VALUE.
    The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
    O. ACCOUNTS KEY
    The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
    PR00- ERL
    K007/KA00- ERS.
    KF00- ERFu2026u2026u2026u2026.& so On.
    P. ACCRUAL KEY.
    The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
    Kalpesh

  • Value Field in COPA doesn't updated in Pricing Procedure

    Dear SAP Experts,
    I have a problem about Value Field in COPA.
    Why the Value Field in COPA that have been assigned to Transfer of Billing Document for Statistical Condition Type doesn't updated in Pricing Procedure (SD) when Billing Posting?
    Any suggestion will be appreciated.
    Thank You
    Regards,
    Kursteilnehmer

    HI
    in pricing procedure SD consultant are creating the pricing condition rules wher these keys are purley belongs to revenue keys .the conditions wich are taken consideration these are all belongs to finding profit margin.
    coming to CO-PA the main objective of copa is analysig the profitability of particular segment .wher as in  CO-PA the most happend flow from sd saide . so wat ever conditions are taking in pricing procedure its compulsary add co-pa valu fields .to take the reports.
    even though in FI-SD interface levele this pricing is taking greater place to flow the values with the help accounting keys.
    coming to stastical condistion co-pa is real cost object

  • Using Field determined in a Condition in another Condition for a pricing procedure

    Hi Gurus,
    I have a scenario in a pricing procedure as follows:
    Cond type ZABC : Determines field HIENR because of the Processing type marked as B for determination based on a field KUNNR ..
    I want to use the HIENR determined in the previous access in a subsequent condition type for processing. I want to know if there is any way to do this without coding.
    Cond type ZPQR: HIENR is passed as a mandatory field for processing access.

    Hello Santosh,
    These are two different condition types with two different access sequences. In the pricing procedure, ZPQR follows ZABC, now, i want to use the HIENR determined in access for ZABC as a variable in access for ZPQR .
    HIENR >> determined from Access ZABC >> Conditon type ZABC
    HIENR should be populated into table ABC table for ZABC access sequence.
    HIENR passed as a variable to Access ZPQR >> Condition type ZPQR.
    Is there a way to do this without addind code??

  • Use of subtotal field in pricing procedure?

    Hi Gurus,
    what is the use of subtotal field in pricing procedure?
    thanks..

    Hi,
    Please see the note 1022966   FAQ for the 'Subto' column (KZWIW) in the pricing procedure.           
    Subtotals (net price, effective price) are created in the case of time-independent conditions.
    SAP recommends working with time-dependent conditions for quotations and scheduling agreements.
    For time-dependent conditions (for example, price maintained in contract    
    and scheduling agreement), supplementary pricing schema is used. Reason     
    is that when condition maintenance is called for contracts and schedule     
    agreements, system refers to supplementary pricing procedure for            
    calculating subtotals.
    Regards,
    Edit

  • Ask help about detail explaination on "subtotal" field in pricing procedure

    Hi, everybody:
       I wanna get detail explanation about "subtotal" field in pricing procedure configuration. I have caught basic thoery on this field usage. However, I'm unclear on its option items, for exapmle, Dcopy value to XWORKD, Ecopy value to XWORKF and so on. I can't find where these kinds of objects are stored and in which suituation we have to select one of them in configuration.
      Another question is how the standard programe uses KOMP to store condition results and transfer them to relative modules, for example, A--carry over price to KOMP-CMPRE.
       Hoping get answer or some documents from you on this issue. If you have reference documents sent to me, please send to my e-mail box: [email protected]
      Tks!
    Justin

    dear justin
    Sub-total:     
    The value of this field determines where the value of the sub-total is gong to be stored in data base
    Sub-total – 1     : KOMP – KZWI-1
    Sub-total - 2     : KOMP – KZWI-2
    rewards if it helps
    siva

  • Please explain the implication print ID in pricing procedure

    F1 help for Print Id in pricing procedure is confusing, can someone explain me please

    Hi,
    Print ID for condition lines
    Controls issue of condition lines when printing documents such as order confirmations or invoices.
    Use
    In releases previous to 4.0, the following print indicators are available :
    ' ' : Condition line is not printed
    'X' : Condition line is printed at item level
    'S' : Condition line is printed in totals block
    The following standard logic is set out for these printing indicators:
    Item POS of the last condition line is determined with 'X'.
    All condition lines that contain an item smaller than POS in the pricing procedure are only printed if print indicators 'X' or 'S' are set.
    All condition lines that contain an item larger than POS in the pricing procedure, that come before the first tax condition line and which have a non-statistical VAT condition, receive printing indicator 'S'. The same applies for condition lines that contain an item larger than POS in the pricing procedure, that come after the first tax condition line and an active non-statistical VAT condition.
    Condition lines that represent a tax condition type are always printed in totals blocks with print indicator 'S' (set internally or externally).
    Condition lines that represent a condition type that is not a tax condition type are only printed with print indicator 'S' (set externally or internally) if the condition value of the condition line is not zero. Condition lines that do not represent a condition type (i.e. subtotals) are only printed with print indicator 'S' or 'X' (set externally or internally) if the condition value of the condition line is different from the condition value of the previous condition line in the pricing procedure.
    To provide a better overview of this process, 8 more print parameters are available as of Release 4.0. These print indicators cannot, however be mixed with the three previous print indicators ' ', 'X' and 'S' in the pricing procedure. This means that the new indicators are only taken into account if a no condition lines in the pricing procedure contain printing indicators 'X' or 'S'.
    Kapil

  • Maping custom field for Freignt to ECC Pricing Procedure

    Hi,
    We have a custom field in SRM to store FREIGHT which is to be mapped to a condition type in ECC pricing procedure.
    Can anyone help in giving a solution to the same?
    Regards,

    Hi Brian,
    Thanks for your help.  I have resolved this, and the information that you provided was helpfutul.
    I had to create a function module in ECC, modeled after the SAP provided sample FM SAMPLE_INTERFACE_DE_BALE.   In addition to this, I had to configure entries in the standard SAP tables TBE24 and TBE34 (event DE_BALE), so that my new function module  would be  called. 
    Duane.

  • Pricing Procedure: requriement routine and mandatory field

    Hi,
    In pricing procedure, which setting has higher proirty between logic included in requirement routine or mandatory field configuration?
    I have a condition type to store list price (copy of PR00), and it is configured as mandatory.
    However, I want to include a requirement routine saying that 'Only for a specific order type and sales organization, set this condition type PR00 as optional.
    That way I can set this PR00 as possible to override the amount.
    Any ideas?
    Thank you in advance.
    Pinkytak

    I agree with all other solutions, but pricing anyway is very flexible to have to make routines.
    If you want just to overwrite the amount, mandatory or not has little to do. Just allow manual changes in the condition type properties.
    But if i understood your requirement correctly, i propose,  you let the mandatory condition type run normally, and  in certain sales type you insert another one, which with condition exclusion, will "deactivate" the mandatory one. In that way, you'll keep the initial one for reporting and statistical reasons.
    If you come back with your business requirement (not the technical one) i'm confident that we'll come up with better solutions.
    Regards
    Agis
    Edited by: Agis Katsafouros on Apr 20, 2010 1:50 PM

  • Pricing procedure field importence(ovkk)

    hello experts
    in (ovkk) pricing procedure determination what is the importent of condition type
    while determining pricing we are not specifing condition type.when can we use condition type in ovkk
    advance thanks

    Hi Friend,
    Please find the below link
    pricing procedure determination
    Thanks
    Dasaradha

Maybe you are looking for