Want to see 5 desimals in pricing condition

Hi All,
The line item vlaue in sales order (KONV-KBETR) has been maintatined as 35.00 USD.
Now our customer is requesting to get the facility of storing this value as 35.12345 USD.
The decimals should be in 5 digits.
But the field KONV-KBETR is having 2 decimals.
How to resolve this issue, so that we can provide user to store condition values with 5 decimals values...
Its lilttle urgent........
Your help will be apprciated...
Regards
Krishna

Hi,
You want to have 5 digits after the decimal point for the field
KONV-KBETR.
You declare one variable of type p(packed) and put  decimals 5.
eg:
data : num1 type p decimals 5.
Then put the value of field KONV-KBETR into that variable.
You will get your requires result.
If it is helpful reward me with the points.
Thanks and Regards.
Mayuresh..

Similar Messages

  • Purchase Order Pricing Condition and Withholding Tax

    Hi
    We have investigated Extended Withholding Tax functionality, which appears to be FI specific.
    The problem is that we want to have the Purchase Order pricing conditions reflect that some amount is being withheld for tax purposes.
    At invoice time, the vendor would invoice for the entire amount (i guess) (ie. 100$) but we would pay the vendor only 80$ and 20$ would go to a withholding tax account...or something like this would happen ...
    I have some pricing config knowledge...but limited
    Can anyone tell me
    a) if this is possible?
    b) any hints on how to go about this?
    Also noticed a 'withholding tax code' field on MEK1 - Create Condition Records. .... which appears as display only depending on how i configure my condition type - haven't figured out how to use this field or what is means...
    Thank-you !!!

    Hi,
    If you are using the standard PO Print then check in M/08 and check for that Condition Type whether Print Indicator is "X"? If it is is Z-Print Program then take help of ABAPer.

  • Function module to change the value for pricing condition type

    Hello experts,
    I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
    I used many function modules but none are working.
    Please kindly suggest a function module that will change the value for a condition type .
    I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
    Thank you.
    CLEAR PRCD_COND.
         SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                              KSCHL = COND_TY.
      IF SY-SUBRC = 0.
    *    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
    *    CLEAR L_COND_CHG-KBETR.
        L_COND_CHG-STUNR = PRCD_COND-STUNR.
        L_COND_CHG-KBETR = COND_PRC.
    *    L_COND_CHG-KSCHL = COND_TY.
        INSERT L_COND_CHG INTO TABLE T_COND_CHG.
    L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
    L_ITEM_GUID = WA_ORDERADM_I-GUID.
    INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
    INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
        CALL FUNCTION 'CRM_ORDER_READ'
         EXPORTING
           IT_HEADER_GUID                    = HEAD_GUID
           IT_ITEM_GUID                      = ITEM_GUID
         IMPORTING
           ET_ORDERADM_H                     = LT_ORDERADM_H
           ET_ORDERADM_I                     = LT_ORDERADM_I
           ET_PRIDOC                         = IT_PRIDOC_RD
           ET_DOC_FLOW                       = T_DOC_FLOW
    *     CHANGING
    *       CV_LOG_HANDLE                     =
    *     EXCEPTIONS
    *       DOCUMENT_NOT_FOUND                = 1
    *       ERROR_OCCURRED                    = 2
    *       DOCUMENT_LOCKED                   = 3
    *       NO_CHANGE_AUTHORITY               = 4
    *       NO_DISPLAY_AUTHORITY              = 5
    *       NO_CHANGE_ALLOWED                 = 6
    *       OTHERS                            = 7
        IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
    INSERT L_PRI_COND INTO TABLE PRI_COND.
    LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
    MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
    L_PRIDOC_CHG-PRIC_COND = PRI_COND.
    L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
    L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
    INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
    ENDLOOP.
    LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
    MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
    INSERT L_HEADER INTO TABLE HEADER.
    ENDLOOP.
    LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
    MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
    INSERT L_ITEM INTO TABLE ITEM.
    ENDLOOP.
    L_FIELD-FIELDNAME = 'STUNR'.
    INSERT L_FIELD INTO TABLE FIELD.
    L_FIELD-FIELDNAME = 'KBETR'.
    L_FIELD-CHANGEABLE = 'X'.
    INSERT L_FIELD INTO TABLE FIELD.
    L_INPUT-FIELD_NAMES = FIELD.
    L_INPUT-REF_KIND = 'E'.
    L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
    L_INPUT-OBJECTNAME = 'PRIDOC'.
    INSERT L_INPUT INTO TABLE INPUT.
        CALL FUNCTION 'CRM_ORDER_MAINTAIN'
         EXPORTING
           IT_PRIDOC                     = PRIDOC_CHG
         IMPORTING
           ET_EXCEPTION                  = EXCEPT
         CHANGING
           CT_INPUT_FIELDS               = INPUT.
        IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    REFRESH EXCEPT.
    CALL FUNCTION 'CRM_ORDER_SAVE'
      EXPORTING
        IT_OBJECTS_TO_SAVE         = HEAD_GUID
    *   IV_UPDATE_TASK_LOCAL       = FALSE
    *   IV_SAVE_FRAME_LOG          = FALSE
    *   IV_NO_BDOC_SEND            = FALSE
    *   IT_ACTIVE_SWITCH           =
    IMPORTING
       ET_SAVED_OBJECTS           = SAVED
       ET_EXCEPTION               = EXCEPT
       ET_OBJECTS_NOT_SAVED       = UNSAVED
    * CHANGING
    *   CV_LOG_HANDLE              =
    * EXCEPTIONS
    *   DOCUMENT_NOT_SAVED         = 1
    *   OTHERS                     = 2
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    COMMIT WORK AND WAIT.

    Hi,,
    To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
    Alternatively u can use this function module.
    CRM_STATUS_DATA_SAVE_DB
    BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
    Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

  • PO printing Tax - Pricing Conditions

    Hi Friends
    In Purchase order,
    I want to know table which links tax code , pricing condition , tax precent.
    Basically I want to calculate amount for each pricing conditions for a tax code.
    Pankaj

    Hi Pankaj,
    Table TSTL has all the details. It has all the tax related condition types for each country.
    In addition to above to get tax values you can use the following function: Its for sales order but hence please check the structures used for PO.
    CALL FUNCTION 'RV_PRICE_PRINT_ITEM'
          EXPORTING
            comm_head_i = komk
            comm_item_i = komp
            language    = nast-spras
          IMPORTING
            comm_head_e = komk
            comm_item_e = komp
          TABLES
            tkomv       = tkomv
            tkomvd      = tkomvd.
    Read the table tkomv with the conditino type from TSTL for the country and that will be your tax value.
    Please reward if  helpful.
    Regards,
    Shahu

  • Needa a Table to see the Pricing Conditions.

    I want to know the Table which should give countries for which a Pricing condition is activated.
    Thanks you very much in advance for the help.

    Hi,
    You can get all the CONDITION RECORDS for pricing in A000 Table.
    Depending on your Access sequence the CONDITION RECORDS tables will vary like A000, A001, A002, A003...
    If you want the Table for the Pricing procedure attached to the SALES AREA then check that in the table T683
    Please check that and revert back.
    regards,
    santosh

  • Want to disable the pricing conditions in VA02

    Hi,
    When we create or change the Sales Order from VA01/VA02 with refrenced to contract always.
    It copies the pricing conditions from Contract.
    We are using PR00 pricing conditions.
    In Sales order it is Write mode. But we need to disable that, so no one will make changes in the PR00 conditions.
    I need to do this by Authorization. As soon as I give change Autho for SO document then any one can change PR00 also.
    Pls suggest.
    Points will be rewarded.
    Thanks

    Hi Kaleeswaran,
    Yes, it has disabled the conditions.
    But the same has been disabled in va42 and va22 also.
    I want to disable the same only for Order (VA02).
    Pls help.
    Thanks

  • I want to block a ertain pricing condition after a certain date, is it poss

    Hi
    i want to block a Certain pricing condition after a certain date, is it possible?..
    Regards
    Tanmoy

    HI
    It is possible to control it in Info record in the conditions details for the condition tyep PB00, similarly if you have any condition reord for PB00 or any other condition in place  of it  in MEK1 then also it can be blocked with the validity period. You can control the conditions with access sequence only in any of these two places.
    Regards

  • BASIS : want to disable the pricing conditions in VA02

    Hi,
    When we create or change the Sales Order from VA01/VA02 with refrenced to contract always.
    It copies the pricing conditions from Contract.
    We are using PR00 pricing conditions.
    In Sales order it is Write mode. But we need to disable that, so no one will make changes in the PR00 conditions.
    I need to do this by Authorization. As soon as I give change Autho for SO document then any one can change PR00 also.
    Pls suggest.
    Points will be rewarded.
    Thanks

    Hi,
    Find authorization objects which are associated with tcode va02, the activity value of perticular object which is related to pricing condition (PR00) can be set to 03 for display.
    Try and revert.
    Rgds,
    - gaurav

  • Pricing Condition in scheduling agreement

    Hi Gurus,
    I'm working with scheduling agreements and I figured that whenever I create scheduling agreements, pricing condition PB00 gets defaulted to the scheduling agreement,
    Can you guys be kind enough to tell me what configuration is driving this?? How can we make changes to the config settings so that I can have a condition type of my choice assinged to the scheduling agreenment??
    More over I have a requirement to have a tiered pricing in scheduling agreement. I do know that this is driven by SCALES in SAP however as per my requirements I need to have SCALES per formulas. In the condition type configuration we do have a field for SCALES where we can assign the formulas but whenever I click on this field a screen pops up with some ROUTINES.
    Can someone tell me how can I define the ROUTINES and the ABAP formula for this ROUTINE so that I can have my tiered pricing conditions accomplished??
    Any feedback on this will be highly appreciated!!
    Thanks folks,
    Dhaval Joshi

    Hi Ramesh,
    Thanks for the heads up. I looked at the config for the schema dtermination and I see that the pricing procedure RM0002 has not been assinged to any vendor POrg schema in this configuration.
    I then looked at the config for the condition type PB00 --> pricing procedure RM0002 has been assigned to the condition type PB00 and since we don't have any entries maintained for RM0002 in the schema determination config I was just wondering if this is what is influencing the automatic proposal of the condition type PB00 in my scheduling agreement.
    Also can you please tell me what is a difference between a Purchasing Document (BIG) and Purchasing Document (Small) in the schema determination config.
    All I wanted to accomlish here is my teired pricing to work when I assign scales on the condition type in the scheduling agreement ( not in the PIR)
    What currently happening in my case is ....
    Example: Scale From 1 pc - 100.00 USD
    from 50 pc - 90.00 USD
    from 100 pc - 80.00 USD
    Target quant. 100 pc
    schedule lines 30 pc
    20 pc
    The problem is  that the goods receipt of 30 pc is valuated at the price 80.00 USD It always takes a lowest price on the scale.
    I've tried looking for OSS notes and also looked enough on the forums but I could not get any resolution to this question.
    I would appreciate if I could get any heads up from your side.
    Cheers,
    Dhaval

  • Pricing condition question

    Hi Gurus,
    I need your help
    1) Want to configure a pricing condition which can be used only in a purchase order, but NOT in a contract/outline agreement. Is it possible? If yes, then how?
    2) Want to configure a pricing condition which when added in a purchase order, will Not add the corresponding charges against the cost of material, but instead will get posted to a seperate G/L account. What special I have to do for it's configuration?
    I do Not want to add a seperate line in the PO with a NLAG material accounting for those charges. The business wants the charges as a pricing condition (since we have the flexibility to put a different Vendor in a condition type )
    Thanks,
    Kumar

    Hi,
    1.Why you want a condition which can be used only in a purchase order, but NOT in a contract/outline agreement? What is the real business requirement!
    2.For Not to add the corresponding charges against the cost of material,follow the steps:
    Create a condition type (copied from standard FRB1 or FRA1 or FRC1 condition type ) in M/06 t.code & select check box of "accrual" selected in control data-2 & the Cond.category must be B(Delivery Cost) in control data-1 .
    And
    In the schema (M/08), keep an accounting key & an accrual key for that condition type
    In OBYC only assign G/L account (separate) for accrual key with chart of account, valuation modifier & valuation class.
    Now create PO( during saving PO, you can see net value not included amount in that condition type  in PO & assign as needed by you separate vendor to that condition type)
    Go for MIGO & do GR and see all accounting entries with a separate entries for separate G/L account
    For more check link:
    http://wiki.sdn.sap.com/wiki/display/ERPLO/PostingplanneddeliverycosttoNon-inventoryaccount
    Regards,
    Biju K

  • Duplicate pricing conditions due to contract supplements

    Hi all,
    <br><br>
    We want our pricing conditions to appear automatically on a normal purchase order and on a purchase order with reference to contract, but they should only be on the purchase order once. We're experiencing difficulties since the condition is fetched and displayed twice (once coming from the condition supplement via the contract and a second time via the standard purchasing procedure).
    <br><br>
    Let me sketch the scenario.
    <br><br>
    We have two procedures used for purchasing:<br>
    - procedure ZM0000 as standard purchasing procedure<br>
    - procedure ZM000S as contract supplements procedure
    <br><br>
    Both procedures contain conditions ZA00, ZR01, ZR02, ZR03, ZR04, ZR05 and these conditions are not indicated as a manual condition.
    <br><br>
    For condition type ZA00 the pricing procedure ZM000S is defined so that condition supplements can be added in the purhcase contract. There is also an Access Sequence for this condition to prevent it from appearing twice on a purchase order with reference to a purchase contract.
    <br><br>
    When we create a normal purchase order, we get all conditions from the ZM0000 procedure without any problem.
    But when we create a purchase order with reference to a contract with condition ZA00 and condition supplements ZR01, ZR02, ZR03, ZR04, ZR05; then we see these ZRxx condition appearing twice instead of once.<br>
    It's displayed once coming from the ZM0000 procedure and a second time due to the ZM000S procedure.
    <br><br>
    I've had a look at the standard procedures, at sap notes and searched on the forums and can't find a feasible solution for this.
    <br><br>
    One way it is commonly solved is to make the ZRxx conditions a manual condition but that means the user will have to add these conditions manually to the purchase order. When we're talking about 50 or more conditions then it becomes a cumbersome to add all these conditions (if required) manually one by one for each purchase order that the user creates --> not feasible.
    <br><br>
    I guess another solution would be to create an access sequence for all ZRxx conditions based on purchase order type and then create condition records for all ZRxx conditions for the purchase documents without reference to a contract. That way the condition will be displayed once (from the condition record) on a normal purchase order and once (from the contract, since the condition record can't be found) in case of a purchase order with reference to a contract. When we're talking about 50 or more conditions and more then 2 document types, then maintaining all these condition records is quite some task --> not really feasible, not the prefered solution.
    <br><br>
    As an alternative to SAP standard we've found the following enhancement point in LV61AA11 where we could possibly delete the "duplicate" condition from KONV if the condition origin (KONV-KHERK) is not equal to "Condition supplement" (F) in case of purchase document type that references to a contract... but this is not the prefered solution.
    <br><br>
    <span style="font-family: Lucida Console">-----<br>
    get pricing result from database table<br>
    ENHANCEMENT-SECTION     KONV_EINLESEN_02 SPOTS ES_SAPLV61A.<br>
      select * into table hkomv<br>
               from konv<br>
               where knumv = komk-knumv<br>
               order by primary key.<br>
    END-ENHANCEMENT-SECTION.<br>
    </span>
    <br><br>
    Also, it's not a feasible solution to put a requirements formula on all these ZRxx condition because we're talking about more then 50 conditions.
    <br><br>
    Does anyone know a solution to this problem?<br>
    How can we make sure the condition is displayed only once? (be it on the standard purchase document or on the purchase document with reference to the contract)<br>
    Is there a standard approach for this?
    <br><br>
    Thanks in advance for your time.
    Edited by: Kevin Coquel on Apr 15, 2010 3:34 PM

    Bernhard, <br />
    Thank you, but as I mentioned in my starting post, this is not feasible as this is concerning over 50 conditions (some of which already have other requirements formulas). <br />
    Using requirement routine for all is an option we want to avoid at all costs.<br />
    It would mean we need to have edit our existing requirement routines to also include routine 15 (as you can only have one requirement routine per condition in a pricing procedure).<br />
    <br />
    Hardik, <br />
    Thank you for pointing us to EXIT_SAPMM06E_013.<br />
    Preferably we would like to solve this using SAP standard before turning to ABAP development.<br />
    <br />
    I'm a bit surprised not being able to find a SAP standard solution to this problem. Since it's not possible to define a different pricing procedure per purchasing document type I would expect a) there is a way to avoid duplicate conditions (coming from the contract supplements) when you're in a purchase document with reference to a contract and b) that the conditions will appear by default in a normal purchase document (instead of having to add them manually one by one when you use "Manual" in the pricing procedure).

  • Help with pricing condition??

    Hi Guyz,
    I have a requirement with my client, the want to supply material to an external customer at an intercompany price(ZPR9). So whenever a sales order is created for this specific customer it should pull the price from Intercompany price(ZPR9).  I have a option to create new pricing procedure and new pricing condition but this condition should pick up the price from ZPR9 so that we don't have to define the price manually like we do in PR00.
    I can't able to assign ZPR9 to my new pricing procedure because ZPR9 is use for intercompany and this customer doesn not belong to any of our company code.So the situation is i have to define new pricing procedure and new pricing condition but this condition should pull the price from ZPR9.
    when I see the details of ZPR9(condition type) its condition category is assigned as 'Y' which is customer reserve Y. I am not sure what this is.So could you plz advice how to handle this whole scenario. Appreciate your help.
    thanks
    Mohammed.

    mohammed,
    This type of requirement is hard to handle and if you do it in a wrong way, whoever support this process later will have a hard time.
    Anyway, I think one of the twisted ways of doing this is to use Alternative Culculation routine and put the logic to get the condition right out of price condition table (A*) of ZPR9. This is not flexible at all because this involves hard coding, so I do not recommend this.
    The message I can get from your client is "We don't want to maintain the same condition here and there," but sometimes they have to deal with it, because the nature of the condition type is very different from business point of view.
    Having said that, in order for them to have easier way to create the condition, maybe you can develop a custom ABAP to copy ZPR9 condition into the new condition you might be creating, and either have them run the program every time they update ZPR9 or schedule the job.
    Hope this helps.
    Akio

  • Pricing Condition type triggering based on other condition type

    Hello sir,
    There are some pricing condition types in our system.
    Based on condition records you can trigger one condition type based on other    condition type.
    For eg: PR00 condition type is there and amount is  suppose 1000rs and other condition type is JBED and we made a condition record and put it some percentage so as soon as we some value in PR00 ,JBED condition type is automatically manipulating the value on the base condition record.
    Now i want other than condition record can we trigger one condition type based on other condition type through defining user routine under requirement.
    Suppose we have condition type ABC and some amount i have given and other condition type DEF , i want that amount of DEF condition type should automatically come from the Condition type and it should manipulate according to my routine .
    eg  Condition type    Amount
           ABC                  1000
           DEF                    40
      The value 40 should come as 4% of 1000.
    I am not maintaing any condition record and i want that this should trigger through some requirement created by me.
    i created my routine no 905 and i putted the code inside it.
      if komtl-kschl = 'DEF'.
      komv-kbetr  =   ( komv-kbetr * 4) / 100.
    endif.
    Now problem is that this code is getting trigger when i m giving value in DEF condition type then it is showing 4 % of it.
    But i want as soon as i give value for the condition type ABC and some value 1000
    then after pressing enter , one condition type DEF should automatically come with value 40 that too in display mode ,not in change mode.
    Please suggestions and solutions regarding this matter , I will be grateful to you.
    Manish

    hi
    In V/06 in the calculation type you can see the entries for "D-gross weight" & "E-net weight"
    For the required condition type select the calculation type as gross weight or net weight. Save it.
    In MM01 - create material master, here in BASIC DATA 1 SCREEN you have fields for gross weight & net weight.
    Maintain the condition record in VK11 for the required condition type.
    You can also maintain the scales as required like u said
    1 to 10 kgs -  100 rupees,
    11 to 25 kgs - 1000 rupees.
    Another way could be
    The BEST practice to do it is, use of VOFM routine for price calculation (VOFM-->Formulae).
    Take help from ABAPer and write a routine such that
    if weight = 1 - 10
    price = 100.
    else if weight > 8.
    price = 1000.
    else
    price = 100.
    end if
    but the maintainnance of routine is big problem as u might be having many records
    Hope this will help you
    Vishal

  • Changing Pricing Condition from VF02

    Hi,
    I'm an ABAPer, for a development purpose I'm trying to change the Pricing Condition data from VF02.But I have found that the Update button at the bottom is disabled.Looking for solution so that I can change the Pricing Procedure.
    Thanks in advance.
    Sarbajit Majumdar.

    Dear Sarabjit,
    If you want to change the price which is coming in the order you need to change its condition record, for this kindly follow the following steps:
    1-     First go to the Analysis Tab on VF02 and check which pricing procedure is maintained over there.
    2-     Then check the condition type you want to change the records for, click on the extension icon before the Condition type you will get the access sequence which is maintained for the Condition type.
    3-     Click on the access sequence and see on the right side of the screen on which basis the condition records are maintained for it.
    4-     The condition record may appear like customer/material/plant.
    5-     Now use T Code VK12, on the initial screen it will ask for Condition Type, enter the condition type and press enter for which you want to change the value.
    6-     The system will ask for the key combination of the condition type which you will get from the step 3 & 4.
    7-     In the next screen it will ask for the values of key combination which are present on the analysis view(step 3 & 4)
    8-     Once you enter these data and press f8(execute) you will reach to the next screen where you can change the condition record for the condition type.
    Regards,
    Ashu

  • Pricing condition- Header

    Hi,
    I have a problem with a pricing condition. It is a the moment both a header and item condition but my customer want it to be only a header condition.
    I can not get this to work as it is a condition that is an automatic freight condition with different stages depending on the value in the order. There are an access sequence connected to the condition and according to that the item condition can not be removed.
    Is there anyone else who know how it could be possible to solve this? I want a condition to be automatic with stages depending on the order value and I only want to have the condition on header level.
    Thanks for the help,
    Ulrika Nilsson

    Please go to the pricing procedure screen (VOK0 transaction) You will see different pricing steps within the pricing procedure. Also you will see a column "Reqt" associated with each pricing condition.
    Identify the pricing condition type for automatic freight conditions and add a custom requirement" say for instance 699. Prior to this activity go to VOFM transaction -> Requirements -> Pricing and create a new routine 699. (may need access key)
    Once this routine is created and saved, 2 form routines will be created. Add the following sy-subrc statements as shown below and activate the program. Make sure the routines are added to the transport.
    FORM KOBED_699. "Header Pricing
    sy-subrc = 0. "successful
    ENDFORM.
    FORM KOBEV_699. "Item Pricing.
    sy-subrc = 4. "not successful
    ENDFORM.

Maybe you are looking for