Freight based on order value before tax

Similar  to the post regarding freight charges which are conditional on shipping address ( which looked as if customisation was the only route) , is there an easy way to implement an order value cut-off point on freight charges. ( i.e. orders below a certain amount are charged at a flat fee but above this limit are free )
I'd presume that this would have to be set per shipping type it if could be done out of the box.
If it requires custom code what steps would be involved how much of the checkout process would have to be re-built and is this a relatively straightforward customisation or one likely to be plagued with problems for someone who is not experienced in this area?
Thanks in advance,
Geoff

Maybe I'm not sure, but i think that it's standard functionality,
in expenses -> shipping
edit shipping type
on general:
Basis - price (means value to be honest) charge type: flat charge
on definition:
Lower Rate     Upper Rate     Charge     Effective Date     Expiration Date     
     0.00      1000      £6.00      2009-Feb-24      3000-Apr-01 
regards
Greg.

Similar Messages

  • Free Goods  based on order value

    Hello,
    We would like to setup a new promo - if your order exceeds $X, get a specified material for free.
    Is it possible to setup and how?
    Thank you for all your help!
    Mila.

    Yes. This scenario is very much possible, although I haven't tried.
    Refer the following SDN thread, which discussed of a similar sort requirement:
    - Exclusive Free Goods Based on Value irrespective of the material.
    In case of any further information or clarification or face any difficulty in applying the same, please do revert.
    Regards
    JP

  • How to get the freight based on the order value

    Hi Folks,
    I have a scenario..if the total order value is less than 2000/- the freight cost will be beared by the customer and if the total order value is more than 2000/- then the company will bear the freight cost. We are using two condition types for freight calculation for this scenario. What can be the way to get this?
    useful suggestions will be awarded points.
    Sunanda.p

    Hi
    SUNANDA.P
    U can achieve this by using scale in yr freight condition. Select yr freight condition and go to Tcode V/06 there u will find SCALE TAB -
    scale basis,  u select " B ". Now maintain condition scale value 2001 then freight rate will be e.g. 500 rs.
    In VK11u can go to scale by pressing F2.
    Try and this will help you
    Thx.
    Dwarkesh

  • Update a list item based sort order of created by column value

    HI
    using powershell script how to sort a list column before update a list  item.
    here i created a document library and uploaded some documents and update ProcessNo column based sort order of created column
    value.
    Add-PSSnapin Microsoft.SharePoint.PowerShell -EA SilentlyContinue
    $webURL = "http://tspmcwfe:91" $listName = "Courts"
    Get the SPWeb object and save it to a variable
    $web = Get-SPWeb $webURL
    $list = $web.Lists[$listName] 
    $items = $list.items
    Go through all items
    foreach($item in $items)
    $item["ProcessNo"] = 1
    $item.Update()
    $web.Dispose()

    Hi,
    According to your description, my understanding is that you want to sort the list items order before updating items using PowerShell.
    I suggest you can use the Sort-Object command to sort the list items.
    Here are some detailed articles for your reference:
    Better SharePoint Lists and List Items in PowerShell
    Sort-Object
    Thanks
    Best Regards
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • FREIGHT AFTER ED AND BEFORE TAX (CST/VAT)

    Hi Friends,
    We need the freight to be calculated after Excise duty and before Tax ( CST/VAT). For example
    Basic Value = 100
    ED 10% = 10
    ECS 2% = .2
    SECS 1% = .1
    10.3
    Freight = 10
    120.3
    CST 3% = 3.60
    Total Value = 123.90
    In our case Freight is calculation after TAX. But we need to calculation of CST/VAT includes freight.
    Kindly suggest how to make changes in pricing procedure.
    I created one condition in pricing procedure for freight, but the same is not transferring to tax procedure for calculation. I also created one condition in tax procedure. But value is not passing to tax procedure.
    Knidly give the solution at the earliest.
    Regards,
    Shital Deshpande

    Check in tax procedure(OBQ3) whether freight condition(Z*) is included after ed subtotal ?
    Whether you maintained condition record(FV11) for lumpsum Z* freight condition ?

  • Sales order value based invoicing

    Hi ,
    Present setting is that Invoicing is done based on the quantity, is it possible that I can do the invoicing based on sales order value.
    2) How to control that Invoicing value and quantity  should not exceed the sales order quantity and value.
    Regards

    Hi
    most of conditions used in sales pricing get copied directly from order to invoice, only freight and delivery charges are aded up while generation of invoice.
    So functionally  if you can estimate freight or delivery charge value in sales order ,you can always maintian routine to be triggered in pricing procedure while invoice generation  to indicate whether  invoice  freight value is exceeding either the individual freight value for sales order  or compare total sale order value  with total invoice value.
    You can set error message if value exceeds than allowed condition value and so the transaction will not be saved.
    Alternatively Condition types AMIZ,AMIW can also be used to have a control through estimation.
    Create appropriate pricing routines with the help of ABAP developer and apply to condition value. Use statistical condition types for control of conditions.and I think what you are trying to achieve can be done.
    Regards
    Mandar

  • Freight calculation on minimum order value

    Forum,
    I am wondering if it is possible for Freight to be calculated on an AR Order based on an order's minimum order value. i.e. If an order with a value of <£50 then £5 Freight is applied.
    I cannot see a standard way of doing this, can this be confirmed?
    Regards,
    Juan

    Hi Juan,
    There is no standard way for it. You can try FMS.
    Thanks,
    Gordon

  • Tax as percentage of totaL  order value

    Hi,
    In pricing i have a scenarios where the tax is calculated on the total sales order value.
    If order has 2 items
    10 mat1    net value 5000
    20 mat2 net value 40000
    The tax should be 1 per of 90000 ie RS 900
    The client does not want it enter it manually and want to use condition records.
    Best regards
    Jatinder

    Hi
    As per my knowledge tax is always calculated on the nett value of the sales order which is in line with your requirement
    Make sure that in your pricing procedure that you are not giving from and to for that tax condition tye
    Suppose in your PP you have a PR00 at step 10 ( first condition type)
    Say a customer discount K007 at step 20
    Say a material discount K020  at step 30
    Material price is Rs100 and customer discount is 5 % thae it is 95 rupees and than a material discount another 5 % then the nett price becomes Rs 90
    Now you want tax MWST to be 1 % on this Rs 90 that is 90 paise or .9 rs then in your PP mwst should be in step 40 without from and to and with its requirements and other things
    You have to maintain condition record for MWST as 1 % for your domestic key combination
    Regards
    Raja

  • Pricing discount based on daily order value

    Dear All.
    Any ideas on how to handle a scenario where a discount could be given if the customer meets a daily minimum order value?
    Not sales order minimum order value, but if the cumulative order quantity across all sales orders for a customer in a given day meets the threshold they would then receive the discount.
    Example:
    mm/dd/yyyy (threshold = $100)
    order 1 - 40, under threshold.
    order 2 - 50, under threshold.
    order 3 - 30, meets threshold.  Gets discount.
    all remaining orders for the day get the discount.

    Devon
    1) My suggestion would be to include the threshold  by date in a custom Infostructure ( S500+)  in flexible planning- MC93.
    2) Also activate Infostructure S001 for customer analysis to update synchronously.
    3) Now include a Pricing Requirement  against the discount condition to compare the value in S001 with SXXX and  apply it only when the threshold is crossed.
    4) Maintain Discount rate  in a (dummy) condition record, but you may need a alt. Cond. Base value formula also.
    Hope this helps.

  • Cancelling order discounts when below Customer's Minimum Order value

    I've been reading what I can find about discount conditions etc and am slightly confused as all the examples seem to relate to item line situations. We need to have a setup where all possible discounts are cancelled if the order total value is less than a given minimum order value (or threshold) related to that particular customer - and not based upon any line item value.
    We do not use Minimum Order Value as per the SAP examples given i.e. orders not accepted below the MOV and therefore surcharges added. As mentioned we use a threshold value for most customers under which discounts do not apply.
    Because of this we cannot automatically email or fax acknowledgements, and we have a massive time consuming checking operation for orders added to ensure mistakes are not made i.e. discounts applied incorrectly before the acknowledgements are sent out.
    Can anyone advise as to where I can find the path to getting a solution to this problem.
    Thanks
    Jim Jackson
    Edited by: Jim Jackson on Feb 20, 2009 9:11 AM

    I understant AMIW is Header condtion type - statistical- and has the MOV value for the specified customer.
    Maintain AMIW as Header / Line condition type.( T Code V/06)
    Create the condition reocord for AMIW with EXCLUSIVE Indicator X.(VK11)
    Then create a requirement for all the discount condition types, if the total order value = or > AMIW value then do not check the exclusion indicator( KOMP - KZNEP), ELSE check the exclusion indicator.
    ( T Code VOFM)
    During order save - automatically repirce the order in Userexit_save_document_prepare or userexit_save_document.
    If there is a partial delivery, during Invoicing if the copy control(delivery to Invoice) has carry out new pricing B, the above setting might fail. Maintain the copy control setting to copy pricing elements unchanged and redetermine taxes OR try to determine the condition values in the invoice from the order.
    Hope this helps.
    Thanks
    Sai

  • Mini. order value

    Hi,
    I have one requirement that order should not be less than 1 lakh.  For this i maintained AMIW in pricing procedure at the end after the Grand total field  and maintained the condition record in VK11 to the condition type AMIW.
    So, when i create the sales order  with less than 1 lakh system is saving the order.  am i missing anything in the configuration.  Plz help me.
    Regards
    Rajesh.

    Hello,
    If the condition type AMIW is in your pricing procedure, the set the condition type. It will work as follows:
    You specify a minimum order value of Rs100000/-.
    During sales order processing, the net value (after discounts and freight, before taxes) of an incoming order is 95000/-.
    During pricing, the system determines that the net value falls below the minimum order value and calculates a minimum-order-value surcharge. In this example, the surcharge equals 5000/-.
    The minimum order value and the surcharge appear as separate lines in the pricing screen. The minimum value is for information purposes only, and does not affect pricing. The system automatically adjusts the net value of the order (before taxes) to the minimum value allowed.
    Prase

  • Requirement Standard SAP Report on Total Purchase Order Value

    Dear Friends,
    Could u please suggest is there any standard SAP report. Requirement has given belwo.
    I required if we have account assignment  Category A as one of inputs, we will get the reqd output  " Total Purcchase order value."
    Note 1) Total Purchase Order Value means - Basic price + taxes + Charges (Freight + Other charges - Discounts etc)
    Note 2) My requirement standard SAP report only.
    Thanks and regrds,
    Vijay Kumar TVN

    Hi,
    T code : ME80FN
    Select :Edit->Dynamic selections>Purchasing document item> Acct. assignment cat.>select A(f4)->execute
    select Material no., PO Number in program selections
    Hope it shall resolve your query....
    regards
    rahul

  • FM for BACK Order Value ....check

    Dear All,
    Is there any FM which gives the Back Order Value...based on input Material...
    Regards,

    Hello Diego,
    just with SM37 test FM and you will be able to enter new or change existing values in organization structure.
    For Input parameters you should use one of USER_ID_P or ORGUNIT_ID_P depending if you want to change attributes for user or org unit. REPLACE_P is if you want to replace existing value of the attribute. (We need to use this filed if we want to change cost centre, even if the value was empty before).
    In Table IT_ATTR_P field ATTR_ID is for field name of attribute that you want to change (i.e. CNT), VALUE_LOGS is for system for where attribute value is, VALUE is for attribute value, DFT_FLAG is if you want that value is defaulted for attribute.
    There are also some other less relevant fields, but they are the same like in attributes visible through ppoma_bbp.
    Also it is possible to maintain extended attributes on the same way.
    HTH
    Gordan

  • Discount on Total Order Value

    Hi everybody ,
    We need the Discount to be calculated automatically on the Total Order Value.
    Its a promotion.
    Useful suggestions will be rewarded.
    Thanks
    Kartik

    Hi pls follow the procedure below, Hope it will help u out
    VOFM: ON PRICING
    This note is an explanation of function "Maintain: Requirements and Formulas", which is also known as "VOFM".
    By using descriptions and examples, this note explains how the VOFM function works in the R/3 Standard System, which objects are related to it and which restrictions exist.
    Chapter 2.7 explains possible causes of errors and solutions for problems with the VOFM function.
    To provide a good overview, this note is subdivided into the following sub areas:
    1. General information
    1.1 Definition of terms
    1.2 Application areas
    1.3 A frank word on the "source code responsibility"
    2. Technology
    2.1 Introduction
    2.2 Namespaces
    2.2.1 SSCR object registration
    2.3 Structure of a VOFM object
    2.3.1 Include file with ABAP form routine
    2.3.2 Table entries in TFRM and TFRMT
    2.4 Calling VOFM objects
    2.4.1 VOFM object carrier
    2.5 Activation, generation and RV80HGEN
    2.6 Transport
    2.7 FAQs: Possible causes of errors and problems
    Technical field names are displayed in angle brackets [].
    Note that this note only explains the mode of operation of the VOFM in an R/3 Standard Core System.
    For R/3 industry solutions or Add-Ons the VOFM function displays a different behavior in subareas, however, this is not dealt with in this note.
    Additional key words
    VOFM, SAPMV80H, TFRM, TFRMT, RV80HGEN, XPRA, formulas, requirements, data transport routine, copy routine, data transfer.
    Cause and prerequisites
    1. General information
    1.1 Definition of terms
    Depending on the business processes used it may be necessary to influence the standard behavior of R/3 applications. For that purpose the VOFM function provides a corresponding environment in order to be able to develop and manage customer-specific logic simply.
    The system stores the objects generated via the VOFM in the Customizing of the respective application area
    (Pricing, message determination and so on) and its programs call the objects correspondingly.
    Also SAP delivers certain functions in the form of VOFM objects.
    Consequently, the VOFM is an exit technology as explained in more detail in Note 381348.
    1.2 Application areas
    Typical VOFM objects are requirements, formulas and data transfer routines.
    These are used in processes of the purchase order, the delivery, billing, price determination, material determination, message determination, the free goods, the pricing and of others.
    In the entries of the R/3 core menu of Transaction VOFM you can find a precise overview of the supported application areas.
    1.3 A frank word on the "source code responsibility"
    As in user exits, in VOFM objects are many fields and tables available. Thus, the use of VOFM objects is very versatile and consequently also very critical under certain circumstances. For the use of "customer-specific" VOFM objects the statements in Note 381348 regarding the responsibility for customer enhancements (Maintenance responsibility, problems during the upgrade and so on) apply. Read this note carefully before you decide on the use of customer-specific VOFM objects.
    Errors and data inconsistencies that are caused by improper application or implementation of VOFM objects are not processed by the SAP Support but exclusively within the framework of the Consulting that has to be purchased separately.
    2. Technology
    2.1 Introduction
    A VOFM object is uniquely defined via characteristics "group indicator" [GRPZE] and "group number" [GRPNO].
    Here the group indicator, technically represented by a character field of length 4, is the logical connection to the calling environment.
    Examples:
    ABED copying requirement in the order
    ADAT data transfer in the order
    PBED requirements pricing
    CASC Data transfer for sales activities
    PBEK requirements account determination
    CHRG requirements batches
    REAK archiving for orders
    VFCL Multi-dimensional scales
    You can find all defined group indicators in the allowed values of the "GRPZE" domain in the ABAP Dictionary (Transaction SE11).
    The group number can have a value from 1 to 999.
    Exceptions are group indicators "PSTK" (= group key routine pricing) and "TDAT" (= data transfer for texts). For these the system can only assign group numbers from 1 to 99.
    2.2 Namespaces
    The VOFM has separate number ranges in order to distinguish VOFM objects delivered by SAP from customer-specific VOFM objects. These number ranges are often also called "VOFM namespaces".
    However, note that this is not a "real namespace" that is protected by corresponding entries in system table "TRESC" (= reserved names for Customizing tables and Customizing objects).
    Instead, only the VOFM logic itself does the definition and check of the number ranges.
    The following list displays the customer number ranges sorted according to group indicators:
    Indicator     Name     Number range customer
    FOFU     Subsequent functions     900 - 999
    PSTK     Group key routines     50 - 99
    TDAT     Data transfer routines f. texts     50 - 99
    all other group indicators           600 - 999
    In Note 356737 you can find more information on the available VOFM number ranges.
    2.2.1 SSCR object registration
    VOFM objects are subject to SSCR registration (= SAP Software Change Registration).
    The reason for that is the necessity that every VOFM object is physically assigned to that SAP development class, from whose programs a corresponding jump into the VOFM object later occurs.
    If you use the VOFM interface the system makes the assignment automatically. An assignment of customer-specific development classes is not possible.
    2.3 Structure of a VOFM object
    A VOFM object consists of the following parts:
    Include file with ABAP form routine
    TFRM table entry
    TFRMT table entry
    2.3.1 Include file with ABAP form routine
    In the ABAP form routine the desired function is programmed.
    Example pricing value formula number 001:
    Include name : FV64A001
    Form routine : FRM_KONDI_WERT_001
    Implementation: * * Profit margin considering rebate agreements
    form frm_kondi_wert_001.
    xkwert = komp-kzwi3 - komp-wavwr.
    endform.
    Dependending on the selected group indicator, the group number and the system type (SAP or customer system), the system assigns and generates the include name and form routine name automatically.
    For this reason, standard routines delivered by SAP generally have a different structure of the include name than customer-specific routines.
    Example:
    SAP standard value formula for the pricing
    => prefix FV64A + object number with 3 places from 'SAP namespace'
    => for example FV64A001
    Customer-specific value formula for the pricing
    => prefix RV64A + object number with 3 places from 'customer namespace'
    => for example RV64A905
    2.3.2 Table entries in TFRM and TFRMT
    The entries in tables TFRM and TFRMT belonging to a VOFM object are used for the status management and assignment. The system always analyzes them if the user calls Transaction VOFM or if a generation operation occurs (for details refer to section 2.5).
    The system generates exactly one TFRM table entry per VOFM OBjekt. In this TFRM entry the following information is stored:
    Group indicator     GRPZE
    Group number     GRPNO
    Routine 'active' indicator     AKTIV_TFRM
    Application     KAPPL
    Date of the last generation     GNDAT
    Time of the last generation     GNZEI
    Examples:
    GRPZE     GRPNE     AKTIV_TFRM     KAPPL     GNDAT     GNZEI
    PBED     001     X     V     06 13 2001     09 06 39
    TDAT     001     X           06 13 2001     09 06 39
    CHRG     003     X           06 13 2001     09 06 39
    The meaning of group indicators and group numbers has already been dealt with.
    The 'active indicator' controls whether a VOFM object is 'active' or 'inactive'. Active VOFM objects have characteristic value AKTIV_TFRM = 'X', inactive objects have characteristic value AKTIV_TFRM = initial.
    VOFM objects flagged as 'active' are 'known' to the calling program logic, that means they were included in the main program of the 'calling program' and can thus be addressed and
    processed during the runtime.
    You cannot delete VOFM objects that are still 'active'. In this case you have to reset the active indicator manually before.
    The content of the 'Application' field serves to filter the relevant VOFM objects in various display functions and Customizing functions.
    Example: Condition value formula 010 'Relevant Price'. This formula has characteristic value 'MS' for the 'Application' field (= External Services Management purchasing). Therefore the object is not open for selection in the input help during the maintenance of pricing procedure SD (Transaction V/08), because this is a Customizing transaction assigned to application 'V' (= Sales and Distribution).
    Storing an application key is optional.
    The generation date and the generation time record the time of the last registration of the VOFM object (the object carrier, refer to section 2.4.1).
    In addition to the respective TFRM entry a VOFM object can have 'n' entries in table TFRMT. The entries are used for the storage of language-dependent object descriptions, which are structured as follows:
    - Language key [SPRAS]
    - Group indicator [GRPZE]
    - Group number [GRPNO]
    - Description [BEZEI]
    Examples:
    SPRAS     GRPZE     GRPNO     BEZEI
    D     PBED     001     Regulierer abweich
    E     PBED     001     Different payer
    The system supplies the language key automatically with the logon language of the user during the creation of a new VOFM object.
    The length of the object description is limited to 20 characters.
    Important! A VOFM object is only consistent if both the Include file with ABAP form routine and a corresponding TFRM table entry exist. Entries in table TFRMT are optional.
    2.4 Calling VOFM objects
    As mentioned above, VOFM objects are called directly by the application logic of R/3 standard programs. Technically this is implemented by ABAP statement 'PERFORM ... IN PROGRAM'. With the aid of this statement you can specify both the name of the subroutine and the main program dynamically (during the runtime).
    Example: Call of a condition value formula from the pricing
    if xkomv-kofrm ne 0. <<< formula reference existing?
    xkwert = xkomv-kwert. <<< act. value in work variable
    frm_kondi_wert-nr = xkomv-kofrm. <<< set up object names
    perform (frm_kondi_wert) in program saplv61a if found. <<<CALL
    xkomv-kwert = xkwert. <<
    endif.
    In the example above the subroutine is determined by the contents of variable 'FRM_KONDI_WERT'; the main program, which is to be searched for the form routine, is SAPLV61A.
    If the called routine is not known in the main program, a program termination with the title 'PERFORM_NOT_FOUND' occurs.
    Therefore some users of the VOFM technology call ABAP statement 'PERFORM ... IN PROGRAM' together with the addition 'IF FOUND', which has the effect that a jump into the form routine is only executed if this in fact exists in the main program. This does indeed prevent a program termination, however, the result of the overall process may deviate from the
    result expected by the user, because in this case the system does not execute the source code implemented in the VOFM object.
    2.4.1 VOFM 'object carrier'
    Object carriers are required to make a VOFM object 'known' in the main program of the calling program (refer to section 2.4). The object carrier is integrated in the main program of the calling program as an independent include (for example SAPLV61A, SAPMV45A and so on).
    Example: Inclusion of object carriers for word processing in SD
    documents; Program 'SAPLV45T'
    System-defined Include-files. *
    INCLUDE LV45TTOP. "Global Data
    INCLUDE LV45TDEF.
    INCLUDE LV45TUXX. "Function Modules
    INCLUDE LV45TNNN. <<< 'carrier' copy requirements for texts
    INCLUDE LV45TENN. <<< 'carrier' copy routines for texts
    Every active VOFM object (for an explanation on the active indicator refer to section 2.3.2) must be registered in the 'carrier'.
    The system writes standard VOFM objects delivered by SAP directly into the 'carrier', VOFM objects from the number range reserved for customers (refer to section 2.2 'Namespaces') are sorted into a 'sub-include' included in the carrier.
    Exactly one carrier exists per group indicator. The names of all defined object carriers are hard-coded in program MV80HF0A, form routine 'AKTIVIEREN_TRAEGER_SETZEN'.
    Here the names of the sub-include for customer-specific VOFM objects belonging to the main carrier are also defined.
    Example: Carrier object 'FV63ANNN' for the registration of condition basis formulas in the pricing (Program SAPLV61A)
    FV63ANNN
    <<< main
    carrier-include
    |-INCLUDE RV63ANNN. "User-Routinen <<< sub-include customer objects
    | |- INCLUDE RV63A910. "Customer specific
    | |- INCLUDE RV63A911. "Customer specific
    | |- INCLUDE RV63A912. "Customer specific
    | |- ...
    |- INCLUDE FV63A001. "Volume
    |- INCLUDE FV63A002. "Net value
    |- INCLUDE FV63A003. "Net Price
    |- INCLUDE FV63A004. "Net Value Plus Tax
    |- INCLUDE FV63A005. "KZWI1
    |- ...
    Because the content of the VOFM object carriers is automatically created source code, you should avoid manual changes to them.
    SAP notes, which suggest manual changes to the object carriers, are therefore also incorrect. However, if you nevertheless receive such a note to solve a problem, contact the SAP
    Support with a reference to this note.
    2.5 Activation, generation and RV80HGEN
    The 'activation' is the inclusion of an VOFM object in an object carrier. A 'deactivation' results in the removal of the VOFM object from the object carrier.
    The overall process for the creation of a current object carrier is often called 'generation'.
    Generally the activation or generation fall into three types.
    - Individual activation
    - Collective activation
    - Generation of object carriers via report RV80HGEN
    The 'individual activation' causes the registration of an individual VOFM object in the corresponding object carrier. Which object carrier is relevant is determined with the aid of the group indicator and the group number. In addition to the entry of the VOFM object in the object carrier the system writes the date and time of the generation into table TFRM (refer also to section 2.3.2).
    You can start the individual activation only manually. It is always always executed when a user selects a line within the VOFM editing interfaces and afterwards selects activity
    'Activate' from the 'Edit' menu.
    The 'collective activation' causes the registration of all VOFM objects that belong to a certain group indicator. Analog to the individual activation the system determines the relevant object carrier automatically and writes date and time into table TFRM. The 'collective activation' is a process which you can start also only manually. For this purpose, choose activity
    'Activate all' from the 'Edit' menu.
    During the generation via report RV80HGEN the system sets up the object carriers of all defined group indicators again. However, the system includes only those VOFM objects that have set the 'active' indicator in the corresponding TFRM table entry. Nonactive VOFM objects are not included in object carriers during the generation via report RV80HGEN.
    Due to the quantity of the data to be processed,
    the generation via RV80HGEN can take between 0,5 and >5 minutes (depending on the system and the constellation).
    Because the RV80HGEN is defined as 'XPRA', it is executed automatically during a system upgrade.
    You can also use this XPRA feature for the transport of VOFM objects in order to implement an automatic update of the object carriers after the import of VOFM objects into the target system (section 2.6 provides more details on the transport).
    Both the collective activation and the activation via report RV80HGEN technically revert to the program components of the individual activation. For the separate control of the individual activation types form routine AKTIVIEREN_EINZELN (Include MV80HF0A) has a 'USING' parameter, which can have the following characteristic values:
    'E' Activate individually
    'A' Activate all (= collective activation)
    ' ' Deactivate individually
    During the generation via RV80HGEN the system executes a collective activation for every group indicator sequentially, that means a call of form routine
    AKTIVIEREN_EINZELN with characteristic value 'A'.
    2.6 Transport
    If you want to transfer VOFM objects from one system (= source) into another system (= target), this is generally made with an object transport.
    As of Release 4.0, the VOFM function has a connection to the SAP 'Change and Transport System' (CTS) in order to simplify the transfer process for the user.
    By the transport connection the system automatically adds newly created or changed VOFM objects to the object list of a transport request which was selected by the user before.
    All steps necessary for the execution of a VOFM transport are described in detail in Note 22808 'Transferring formulas'. Note that steps 1-4 are only needed
    if the VOFM maintenance environment providesno automatic connection to the transport system or if you want to combine a transport request manually. In any case you must execute step 5, regardless of how the transport request was created.
    In addition to Note 22808, Note 385067 contains an overview for releases >= 4.6C regarding which sorts of tasks and object entries are required in a
    transport request (depending on the activity carried out (create/change/activate/deactivate/delete)) in order to transport a VOFM object successfully.

  • User exit for pricing to calculate net sales value and tax at billing level

    Hi,
    Can anyone give the solution for below thing.
    I have written the code for to calculate the net sale a value and tax value based on condition types YTN1 & YTN2 and with pricing procedure "ZXTNIC"  under   user exit "userexit_field_modification"  in include program LV69AFZZ
    Calculation as per below
    FD:
    The user exit will run on the values of the line item and the header of the pricing conditions
    The user exit will subtract the current net value from the value of the conditions YTN1 & YTN2, also the Tax value will be added to the value of the conditions YTN1 & YTN2.
    Need the Net value = 8,032 and not 8,882  " here 8832 value is before calculation
    This value will be calculated as follows = Current Net u2013 YTN1 u2013 YTN2 = 8,882 u2013 0,773 u2013 0,077 = 8,032
    Need the Tax value = 2,395 and not 1,545  " here 1545 value is before calculation.
    This value will be calculated as follows = Current Tax + YTN1 + YTN2 =     1,545 + 0,773 + 0, 077 = 2,395
    When i will execute the VF01 transaction there in initial screen values are not updating automatically.Once we will select item line and  then clicking on " item pricing condition" icon i.e., item level , then only the values are updating both in item level and header level.
    But when we will execute the VF02 and VF03 the values are updating automatically as per condition.
    So please suggest me is there any exit for this requirement.
    Regards,
    Jayaram

    Hi,
    You should implement your logic in VOFM Copying routine for billing document.
    Regards
    Prasenjit

Maybe you are looking for