SAP Basis Security in Sales order pricing - Help required

Hi,
My requirement goes like this:
The ability to view cost and margin should be restricted
The ability to add discounts and update price should be restricted
Sales Directors, Sales Managers, Revenue Recognition and members of the Sales Ops team will be allowed to view cost and margin
Sales Directors will have the ability to add controlled discounts (i.e. up to a pre-defined % value)
Sales Ops will have the ability to add discounts without restriction
Sales Ops will have the ability to maintain price overrides
These are governed by Condition types such as PR00 etc., can you control it by using Authorization objects in sales order Item Condition tab for the particular USER?
In T.code: V/06
For E.., EK01/EK02, double click on it....You can find a sub screen "Changes which can be made". There u can enable whatever required by tick marking ...e.g., amount, value, delete etc.,
Pricing procedure will be normally designed for a sales AREA and group of customers/Documents.
Condition type values are stored in the form of condition record by using T.code: VK11. It is stored in table KONV and KONP.
So, actually client needs like:
Some users should NOT be allowed to change the price/discount.
Also some are to shown in DISPLAY mode only.
Some can add some conditions types too.
Is it possible through SAP BASIS security?
I am waiting for your valuable suggestions.
Regards,
Anbu

Yes it is possible to restrict authorizations for condition types using authroization objects. Some user exits need to be used to meet the requirement. Refer OSS Note 105621 which gives a detailed procedure for customizing Authorization check for the condition screen.
Regards,
GSL.

Similar Messages

  • Control Sales order Pricing Date with Delivery GI Date

    Is it possible to have a control that ensures the Actual GI date in a delivery is not more than a number of days from the sales order pricing date?

    Hi,
    To have restriction in actual GI date in transaction VL01N . Please find the user exit for VL01N , you can use one which are marked as bold . Kindly take the help of abaper to put the validation or logic as required.
    V02V0001   - Sales area determination for stock transport order 
    V02V0002   - User exit for storage location determination 
    V02V0003   - User exit for gate + matl staging area determination 
    V02V0004   - User Exit for Staging Area Determination (Item) 
    V50PSTAT  - Delivery: Item Status Calculation 
    V50Q0001   - Delivery Monitor: User Exits for Filling Display Fields
    V50R0001    -  Collective processing for delivery creation 
    V50R0002    - Collective processing for delivery creation 
    V50R0004    - Calculation of Stock for POs for Shipping Due Date List
    V50S0001    - User Exits for Delivery Processing 
    V53C0001    - Rough workload calculation in time per item 
    V53C0002    - W&S: RWE enhancement - shipping material type/time slot
    V53W0001   - User exits for creating picking waves 
    VMDE0001  - Shipping Interface: Error Handling - Inbound IDoc 
    VMDE0002  - Shipping Interface: Message PICKSD (Picking, Outbound) 
    VMDE0003  - Shipping Interface: Message SDPICK (Picking, Inbound) 
    VMDE0004  - Shipping Interface: Message SDPACK (Packing, Inbound) 
    Hope this will help you to resolve your issue!!!!
    Regards,
    Krishna O

  • User exists sales order pricing

    How to find out SALES ORDER PRICING USER EXISTS already predefined
    Thanks
    munna

    Hi,
    Check below link for all user Exists in SD.
    https://wiki.sdn.sap.com/wiki/display/ERPLO/SDUserexits
    User Exits for Price Determination
    Routine      - Module pool or function group - Include  - Description
    USEREXIT_PRICING_PREPARE_TKOMK      SAPLV60A      RV60AFZZ      This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document. This user exit is described in detail in the "New fields in pricing" section.
    USEREXIT_PRICING_PREPARE_TKOMP      SAPLV60A      RV60AFZZ      This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing. This user exit is described in detail in the "New fields in pricing" section.
    USEREXIT_FIELD_MODIFICATION      SAPMV61A      MV61AFZA      You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals. This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_KZWI      SAPMV61A      MV61AFZB      You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_KOPF      SAPMV61A      MV61AFZB      You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_LEER      SAPMV61A      MV61AFZB      You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_PRICING_CHECK      SAPMV61      MV61AFZA      You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
    USEREXIT_PRICING_RULE      SAPLV61A      RV61AFZA      In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
    USEREXIT_CHANGE_PRICING_RULE      SAPMV61A      MV61AFZA      You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
    USEREXIT_XKOMV_BEWERTEN_INIT      SAPLV61A      RV61AFZB      This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
    USEREXIT_XKOMV_BEWERTEN_END      SAPLV61A      RV61AFZB      Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
    USEREXIT_XKOMV_ERGAENZEN      SAPLV61A      RV61AFZB      In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
    USEREXIT_XKOMV_ERGAENZEN_MANU      SAPLV61A      RV61AFZB      You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
    USEREXIT_XKOMV_FUELLEN      SAPLV61A      RV61AFZB      This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
    USEREXIT_XKOMV_FUELLEN_O_KONP      SAPLV61A      RV61AFZB      This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
    USEREXIT_PRICING_COPY      SAPLV61A      RV61AFZA      You can change the KONV fields for copied price components.
    Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been converted from a full screen to a subscreen. The full screen is included in the SAPMV61A module pool, the subscreen, however, in program SAPLV69A. Therefore, instead of MV61AFZA and MV61AFZB, the user exits in LV69AFZZ should be used. For reference, see OSS note 313569.
    Best regards,
    Anupa

  • SAP Certification Exam for sales order management

    Hello All,
    I am an SAP SD Consultant with 5 yrs of experience. My experience spans across different areas in SD which includes integration experience as well.
    Off late i decided to appear for a certification exam & found the same in SAP website. SAP is offering the following certification exam as it relates to SO Management
    "SAP Certified Application Professional - Sales Order Management with SAP ERP 6.0"
    Can somebody advice/sugges me on if i can prepare for this exam on my own based on my work experiece or is it better to go to a centre which offers a certification training. I would appreciate any suggestions/comments
    Thanks,
    Vinay

    Hi Vekat,
    Having knowledge is good but certification comes in different way. There will be questions from SAP materials and it might be just one line from the PDFs.
    Its good to go thru the SAP materials applicable for this certification which can help you to prepare for it in a better way.
    If you donot have these materials then you may go thru e-learnings/classroom trainings either from SAP Eduction or from its affiliated institutions.
    Regards,
    Subhash

  • Sales Order Pricing User Exit Problem

    Hi,
    I am facing a problem related to coding in Sales Order pricing user exits. Scenario is as mentioned below:
    Based on Material Entered and Sold To in Sales Order, auto determination of a manual pricing condition happens. For doing this, coding has been done in USEREXIT_PRICING_PREPARE_TKOMP by changing XKOMV table. Auto determination of the manual price is happening properly.
    From Sales Overview Screen when user goes to the Conditions tab, Net Value is not getting calculated. When we navigate away to Schedule line tab and then come back to COnditions tab, Net Value is automatically getting calculated.
    AM i missing something in the coding part? As the data is getting populated automatically I guess some piece of code needs to be triggered. Can anyone shed some light into this.
    Thanks in advance,
    thunderans.

    Prabhu: After filling in XKOMV structure, I am calling FM PRICING. On doing this, the Sales Pricing is getting calculated but even then net value of order at header i.e VBAK-NETWR is not getting populated when we are in Sales Overview screen. When, I am getting into Conditions tab and coming back to Sales Overview screen, Net value is getting populated correctly. This portion of everything not getting populated at the same time is bothering me. The pricing conditon that I am  filling is a manual pricing condition.
    I put a breakpoint after FM PRICING which correctly populates XKOMV structure. How do I properly update Order Net Value in Sales Overview screen wihtout having to navigate to any other tab?
    Nicklas: I am looping at Order line within the user exit USEREXIT_PRICING_PREPARE_TKOMP and determining price. Once all line items are processed, I am using the FM PRICING for calculating Sales Prices.
    J@Y: Request to send me a bit more details into your approach.

  • Country of Delivering Plant is not showing in Sales Order Pricing Analysis

    Hello All,
    I have created a new condition table with the field Country of Delivering Plant (KOMK-WKCOU).
    But in the sales order pricing analysis this field is not fetching the country of the plant (it is showing the Yellow color exclamation icon).
    This is  a standard field, I am not able to understand why it is not fetching this field.
    I have used the same field for tax condtions in my previous projects as well, there it worked well. 
    Even I have activated the KOMK structure in SE11 also, but still the same problem.
    Can anybody tell me how to resolve this issue.
    Thanks & Regards,
    Sreehari.

    Rightly suggested by Shiva.
    As plant determines at item level.
    So, instead of KOMK-WKCOU, field should append in KOMP.
    FYI, for checking any inconsistency in condition table, you can use TCode VK+C.
    Regards
    JP

  • Excise CIN amounts not updated in TAX field in Sales Order Pricing

    Hi,
    I am not getting the Excise Amount [CIN] i.e BED + ECS + SHE Cess in Tax field of Sales Order Pricing Procedure. only Sales Tax amount is showing.
    Plz let me know, where did I go wrong in the Configuration.
    Thanx in advance.
    with best regards
    Jabbar

    Abdul,
    What you have said is correct with regards to condition record creation, excise rate picking and its calculation.
    On clicking the "analysis" button in pricing screen (Sales item details --> condition -->) try to analyse for each condition type
    we can resolve it
    Check within the condition type whether you have entered condition category = D, it must be like this
    Cond. class   =  D Taxes
    Calculat.type  = A Percentage
    Cond.category = D Tax
    In Pricing Procedure Activate "Statistical" Indicator, it will definitely appear in the tax field.
    Regards
    Sathya

  • Sales order pricing conditions

    Can any one let me know what are the tables that are updated while working with sales order pricing conditions .......      r sales order conditions

    Hi Ali,
    VBRK     Billing document :header data
    VBRP     Billing document :Item data
    KONH      Conditions header
    KONP     Conditions items
    KONV     Procedure ( billing doc or sales order)
    KOND     Conditions (data)
    These tables will give sufficient information on Sales order pricing and its billing conditions etc.
    best regards
    Ramakrishna

  • Video Tutorials for SAP Basis & Security

    Hi,
    Is Any CBT Nuggets/Video Tutorials are also available for SAP Basis & Security???
    please provide me the link if it is available

    Saurabh,
    You cannot expect A to Z of SAP Basis and Security tutorials in videos. May be you can find some basic to important information.
    Refer to the links though
    www.youtube.com/watch?v=OT4PQarbT0k
    www.learnsap.com/config/basis.html
    http://sapdownloads.blogspot.com/.../sap-basis-training-for-beginners.html
    Just google it, you will find loads of information.
    Good Luck
    Regards,
    Arjun

  • Sales order and delivery requirement

    Hi,
    I have never worked real time on TOR and availibility check. I need help on clarification on the concept.
    1) The sales order transfers the requirement to MRP. So in the sap system there is a standard  requirement type/class 41 for the same. I need to know why there is a requirement type/class for sales order related delivery (011- delivery req type/class) ?
    In sales order related delivery, only availibility check is controlled(thru delivery item category) since the requirements are already transferred from sales order. so why the 011 delivery requirement ?
    2)The requirement type is determined through sales order item categoryMRP type.for the same combination of item categorymrp type, do one has to assign both the sales order and delivery requirment. I.e. suppose sales item category is ZTOR and mrp type is PD. so do one has to necessarity configure the follwoing
    ZTOR+PD=041(SALES ORDER REQ TYP) and 041 assigned to 041 req class
    ZTOR+PD=011 (DELIVERY REQ TYPE) and 011 assigned to 011 req class
    regds

    hi,
    please go in to class details you will find various indicators, related to costing, accounting etc.
    kapil

  • How to identify Sale Order costing is required for Items in Sales Order

    Howstandard cos estimate*w to identify Sale Order costing is required for Items in Sales Order?
    On which criteria we can conclude Sale Order Costing is reqd ?
    ? * means what and wat is the purpose and how to chk for the Item in Sales Order, either it is required or not**.

    Hi Dharamveer,
    The best way is to make the order qty is equal to the quantity delivered. This way, when some one looks at this order in future - they think that the order was for X and the delivery was for X qty is completed. They will not know the background of the issue unless they go through change log. Even in change log, they see that the Ord qty was adjusted, but may not understand why?
    The good practice is to make order qty equal to already delivered qty.
    Create a new line for the remaining qty and reject the same with appropriate reason for rejection. This way, any one can understand the background , the reason for rejection easily. Hope it helps !

  • PRICING Procedure in SAP for an Incomming Sales Order IDOC

    Hi Friends,
    Here is a situation what we have and what we intend to do.
    We would be getting a Sales Order IDOC and when it hits the SAP..it comes with
    -Material, Qty and Price per material
    -Total Freight
    -Total Tax
    i.e the Pricing conditions are not maintained in SAP at all..we would just get the IDOC externally and the SAP needs to read the material, Qty at line item,
    take the total freight as it comes, and total Tax as it comes in the Idoc.
    My thoughts were to have all the Conditons PR00 (ZR00), KF00 (ZF00), UTXJ (ZTXJ) . ZR00 to set as Manual condition. ZF00 as header Freight and Manual condition, ZTXJ as header condition and Manual.
    I therefore was trying to figure out the best way to set the pricing procedure.
    Please let me know if I am on right track if not which is the way I need to set.
    Thank you
    Ravi

    HI Ravi,
    I think your issue is solved now...so for the benefit of SDN members....can you share the solution..as I am also working on the same requirement !!
    Thanks in advance
    Mayank

  • Sale order- Pricing -Access Sequence

    Hi Gurus,
    While creating Sale order, the price is picked from the Pricing procedure and Condition records maintained.
    In PR00- Material price and Customer-Material special price is maintained in VK11.
    So the system picks Customer Material combination price and the same we can see in the Item level conditions-Analysis for pricing and can also see it fetched record from where.
    So for this Client wants in the following way: POPUP MESSAGE
    At Sale order Warning Message that Price is taken from Which List- Normal Price List or Special Price List for Customer and Material combination
    Is there some way to do this?
    Thanks in Advance.
    Best Regards
    Sri

    Hi,
    U have to take ABAPER HELP  No doubt please use this input if tis use full .
    User Exits For Price Determination
    USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)
    This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.
    This user exit is described in detail in the "New fields in pricing" section.
    USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
    This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.
    This user exit is described in detail in the "New fields in pricing" section.
    USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
    You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)
    You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)
    You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)
    You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
    This user exit is also used in order processing.
    USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)
    You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
    USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)
    In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
    USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)
    You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
    USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)
    This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
    USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)
    Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
    USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)
    In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
    USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)
    You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
    USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)
    This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
    USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)
    This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
    USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)
    You can change the KONV fields for copied price components
    With best regards,
    venkataswamy.y

  • Restrict Formula Calls in Sales Order Pricing

    Hi All,
    I have created a pricing conditon formula to get the price for the real time contract price from a third party Contract management system through a RFC call, and assigned the formula to a condition type.
    In this formula, if there was an error i am exporting the error message to a memory and importing the value from that memory to set a billing block in the user exit SAVE_PREPARE_DOCUMENT (MV45AFZZ).
    The problem i am facing is that the formula is getting called many times uncessarily for eg. when you click pricing etc
    and not necessarily updates the price all times. Actually the price is not updated when called from the following routine and is basically because of the following code.
    Form: xkomv_bewerten.
    IF xkomv-kofrm NE 0 AND wertformel EQ space AND komp-kposn NE 0.* rettkomv = xkomv*.
    xkwert = xkomv-kwert. frm_kondi_wert-nr = xkomv-kofrm. PERFORM (frm_kondi_wert) IN PROGRAM saplv61a IF FOUND. xkomv = rettkomv.
    ENDIF.
    During Change Sales Order, because of this even a billing block is set before, it is getting cleared without updating the price.
    Can somone help me with this?
    Thanks.
    Martin

    I coded  this logic in a 906 pricing routine... and I did not have any problem bcoz of multiple hits... SAP is taking care of when to update values as per the calculations I am doing here....
    if I remember right SAPLV61A is the main program which will be included with all sorts of code related to routines..
    * Call the RFC wrapper in a new task
      CALL FUNCTION 'ZTEST'
        STARTING NEW TASK taskname
        DESTINATION 'NONE'
        PERFORMING ret ON END OF TASK
        EXPORTING
          comm_head_i           = wa_komk_i
          comm_item_i           = wa_komp_i
        EXCEPTIONS
          communication_failure = 1
          system_failure        = 2
          resource_failure      = 3.
      IF sy-subrc EQ 0.
        WAIT UP TO 1 SECONDS.
      ENDIF.
    * Get the values from the RFC shared memory export
      CONCATENATE 'ZTESTVPRS' sy-uname INTO memid1.
      IMPORT lt_komp = comm_item_e
      FROM SHARED BUFFER indx(st) ID memid1.
      wa_komp_o = comm_item_e.
      IF sy-subrc EQ 0.
        DELETE FROM SHARED BUFFER indx(st) ID memid1.
      ENDIF.
    * Get the Header level from RFC shared memory
      CONCATENATE 'ZTESTVPRS_H' sy-uname INTO memid2.
      IMPORT lt_komk = comm_head_e
      FROM SHARED BUFFER indx(st) ID memid2.
      wa_komk_o = comm_head_e.
      IF sy-subrc EQ 0.
        DELETE FROM SHARED BUFFER indx(st) ID memid2.
      ENDIF.

  • Rebate base on the sales order no.

    I want to create the rebate base on the previous sales order,the key combinaiton is customer and sales order number.I had used the field of sales order number is AUBEL,and I had also maintained alll the configuraiton and master data for this rebate. But the billing could not capture the rebate. I have check the analysis, the message display the condition record is missing ,the sales document is the currently SO.I do not understand why it could not capture the SO no. which I had maintained in the rebate.Does anyone have some suggest for this issue?Thank you in advance.
    Best regards
    Emma

    Hi
    Rebate conditions comes into effect only when you will create a Billing document, you can not find them in Sales order.
    THis beacuse of "Requirement 24" assigned to the Rebate condition types in the Pricing Procedure.
    It is logical also.
    Suppose, you are working with Material Rebate.
    Customer has ordered for 100 units, but subsequently he has requested you do deliver only 50 units with reference to his order.
    So, you will bill him for 50 units only.
    Now, if you have set the Rebate on Sales order, then system will calculate the Rebate accrual on Sales order quantity, which is wrong.
    Billing quantity is the right quntity for which customer is eligible for Rebate.
    That is why in SAP, it has been set like this.
    Beside this when you want to work on Rebate, you need to activate Rebate in three places
    - Sales organisatio
    - Payer
    - Billing document type  (NOT Sales document type).
    Beside this , your Sold-to-party and Payer may be different, whereas you have made the condition record for Sold-to-party and Sales order combination.
    Rebate condition record must be create within the Rebate Agreement specifying the Rebate rate and Accrual rate.
    It is not created by VK11.
    These are few possiblities for which Rebate is not featuring in your Billing document.

Maybe you are looking for