TOTAL PO VALUE AT HEADER

Dear all,
             is there any way to show the toal po value(inclusive of deductible & non deductible taxes) at header level.one step ahead to this can we  show the total po value(inclusive of all taxes) in the po header STATUS tab.
             like for ex. in po 2 line items are there with base price 100 &200 respectively with tax code( BEDECESSSECESS+CST)  i.e. 10.3% cst 2% alongwith other condition type like P&F .
             ISSUE-  at header level total po value should come (300316.5) approx it is inclusive of ed+ cst.
                          but in my po only 300+6.5 is coming since cst is working as non deductible tax(through NAVS its coming in pricing) but ed component is missing.
note- we are using taxinn & tax code so don't want to use any condiotion type for ed.
          hope prob is clear to all the sap gurus.
             looking forward to your reply its urjent.
regards---
Ratnesh

Hi,
The Total PO value is sum of PO values of lines items and to get the PO Line item value, go to table EKPO and look for the field EFFWR(Effective value of item).
Let me know if it works.

Similar Messages

  • Contract net value for Header Statistics is not correct

    There is issue with value contract. The net value for Header Statistics is not showing correctly for some contracts. Especially, when we delete the PO line items or reverse all entries (GR and IR) for PO line item.
    Contract has one line with account category ‘U’. The target value is 300,000.00 and total quantity released to date is 160,000. The net value for Header Statistics should be 140,000 but it is showing 600,000 which is over (double) the target value and user cannot release any further PO reference to this contract.
    Earlier I defined net price for line item 300,000 and I changed net price to zero and execute report RM06ENP0 but it doesn’t work.
    Please share your experience and thoughts.
    Thanks,
    Shah.

    Hi Jurgen,
    There are few Purchace orders with multiple line items and each line item for Purchase orders referencing the same line and same contract.
    There is only one Purchase order has two deleted lines against this contract.
    Theses deleted line's net price has changed to zero and there is no PO history.
    Contract released order value is correct as there is only one line, but net price is wrong. and user is getting error for target value is excedeed by $nnn when trying to create purchase order.
    Thanks,
    Shah.

  • Total Amount value not displaying while executing print progrm for PO form.

    Hi All,
               I created the PO form, for this i written a print program.After executing this print program everything s displaying & populating, but only the Total Amount  not displaying r not populating.
              But, if i run the PO n tcode ME23N the Total Amount is displaying, after assigning the form n NACE.
    So help me to get the Total Amount to be displayed n main window, while executing the print program.
    Like this i declared n smartform,                    Total net value excl. tax           &is_ekko-waers& &is_pekko-netwr&......
    The print program as follows,
    report zpo.
    tables: ekko,pekko,ekpo,ekpa,eket,ekkn,ekek,komk,nast.
    data: fm_name type rs38l_fnam.
    data: is_ekko type standard table of ekko with header line.
    data: is_pekko type pekko occurs 0 with header line.
    data: it_ekpa like standard table of ekpa,
          it_ekpo like standard table of ekpo,
          it_pekpo like standard table of pekpo,
          it_eket like standard table of eket,
          it_tkomv like standard table of komv,
          it_ekkn like standard table of ekkn,
          it_ekek like standard table of ekek,
          it_komk like standard table of komk.
    selection-screen: begin of block b1 with frame title text-001.
      parameters: pr_ebeln like ekpo-ebeln obligatory.
    selection-screen: end of block b1.
    select * from ekpo into table it_ekpo where ebeln = pr_ebeln.
    select * from ekko into is_ekko where ebeln = pr_ebeln.
    endselect.

    code as follows,
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        FORMNAME                 = 'ZPURCHASE'
    *   VARIANT                  = ' '
    *   DIRECT_CALL              = ' '
    IMPORTING
        FM_NAME                  = fm_name
    CALL FUNCTION fm_name  "'/1BCDWB/SF00000060'
      EXPORTING
    *   ARCHIVE_INDEX              =
    *   ARCHIVE_INDEX_TAB          =
    *   ARCHIVE_PARAMETERS         =
    *   CONTROL_PARAMETERS         =
    *   MAIL_APPL_OBJ              =
    *   MAIL_RECIPIENT             =
    *   MAIL_SENDER                =
    *   OUTPUT_OPTIONS             =
    *   USER_SETTINGS              = 'X'
        IS_EKKO                    = is_ekko
        IS_PEKKO                   = is_pekko
    *   IS_NAST                    =
    *   IV_FROM_MEM                =
    *   IV_DRUVO                   =
    * IMPORTING
    *   DOCUMENT_OUTPUT_INFO       =
    *   JOB_OUTPUT_INFO            =
    *   JOB_OUTPUT_OPTIONS         =
      TABLES
           it_ekpo                   = it_ekpo
           it_pekpo                  = it_pekpo
           it_ekkn                   = it_ekkn
           it_ekpa                   = it_ekpa
           it_ekek                   = it_ekek
           it_komk                   = it_komk
           it_eket                   = it_eket
           it_tkomv                  = it_tkomv.
    * EXCEPTIONS
    *   FORMATTING_ERROR           = 1
    *   INTERNAL_ERROR             = 2
    *   SEND_ERROR                 = 3
    *   USER_CANCELED              = 4
    *   OTHERS                     = 5
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

  • Vendor Down Payment should not exceed Total PO Value

    Dear All,
    We want to restric the Vendor Down payment to total PO value and system must not allow to post the Down payment more that Total PO value.
    Eg.
    Material value - 1000
    Tax                     100
    Other charges    150
    Total PO Value - 1250/-
    Now when we make down payment to the above vendor against the PO,the system must not allow us to make down payment more then 1250/-.
    Do suggest.
    Regards,

    Hi,
    You need to write validation rule & user exit for checking PO amount with down payment.
    Whenever you post a down payment with reference to PO, in PO header, there is a status tab where you can check the status of PO i.e down pymt made, GR done etc., so write a user exit on that basis.
    Regards
    Anuj

  • Total release values in GOA and ECC contract

    Hi  All
    Contract  query
    i just want to match both ECC and GOA release values .
    What is the table Total  release value stored in SRM and ECC other than EKAB (Item release table)
    i want total release value in both system so that i can compare very easily.
    appreciate your help.
    br
    muthu

    In SRM, the total release value is at header level in table BBP_PDHGP / VAL_PO_E. However, we have experienced occasional situation where this value on header differs from the sum on each item (BBP_PDIGP / VAL_PO_E). SAP wasn't able to offer more explanation than recommending that we write an custom report to synchronize them manually.

  • Need to pass condition values in header of billing...by using bapi

    Dear Gurus,
    I am creating invoice for delivery by using bapi
    BAPI_BILLINGDOC_CREATEMULTIPLE.. ....in this i need to update some condition values in header level..when i am passing those condition values in CONDITIONDATAIN its updating for each individual line item of any invoice and sum of line items of condition values in header...but i need to update only in header and dont wnat to update in item level..
    please help me in this..am very much thankful to you if you can help me
    Thanks in advance
    Regards,
    Rajesh

    Ok, after continuing to search the internet I finally found the extra piece that I was missing that gave me the results I needed. The new expression looks like this:
    =runningvalue(Sum(Max(IIF(LEFT(Fields!JobNum.Value,1)="S" AND Fields!Week1STol.Value<>0, CDBL(Fields!Week1STol.Value), 0),"JobItem"),"JobItem"),SUM, "JobItem")
    In this I wrapped the original expression of Max in both a Sum and a runningvalue both at the JobItem level to get this rollup value. Now when I open the grouping I get the correct running value at each level.
    What this really gives to me is a running total at each of four groupings, even with a "max" value at the detail level. This also allows me to total a max value inline on the report, without needing a hidden row, or report footer.
    Thank you to everyone who looked at this, I hope it helps someone else. If this answer is not clear enough, please don't hesitate to add to the comments and I will try to clarify.
    Thank you, Chad

  • Total Settlement Value field  not getting populated in IW38  Transaction

    Dear all PMCS group Members,
    I have a list of  Maintenance Orders on which  Actual Costs are posted and also periodic settlements done before TECO.  When i list these Maintenance Orders in IW38 transaction the system is bringing in the values in  Total Actual Costs column  but  not the Settlement values in Total settlement column which i need to cross check before i do mass TECO. 
    Your help will be greatly appreciated.
    regards,
    rajaraman.

    Dear Rajaraman,
    You can see the Total Settlement values by using tcode IW38.
    ---> Goto IW38
    ---> Execute the Report for selected Orders
    ---> Click on the Current Tab or Press CTRL+F8
    ---> Select the Column of Total Settlements and Actual Settlements
    ---> Click on the Save Button... it will ask you to enter the Layout... Enter it and hit Enter
    Your Required Fields will be Displayed.
    Regards
    BK

  • Total order value (net) per PO with ME2N (Purchase order List display)

    Hello,
    with ME2N I can see the order value (net) of a PO per item line. Is it also possible to see the the total order value for all item lines in a PO?
    Thanks for coming back to me!
    Sofia

    hi in standard reports that is not possible
    But you can opt for filter in PO no. feild and go for an specific PO and press enter it will show all the line item of that PO then you can apply the Total of all Po line items in net price feild
    Or even while running the report you can go for specific PO no and then execute the report.
    Hope this helps
    Else need to devlop an Z report with help of ABAPER
    Try with the table EKPO and feild RLWRT
    He can solve your purpose
    Regards
    Sujoy
    Edited by: SUJOY on Sep 22, 2008 2:39 PM

  • GL account balance not matching with the total stock value

    Hi,
    The GL account balance is not matching with the total stock value in report RM07MBSTfor stock in transit, Can anyone please let me know, where should, I look into to verify the reason for difference.
    Quick response will be appreciated.
    Thanks & Regards

    I am able to solve this issue. My client has a customized report, which helped me to look into the details of stock in tranisit account. Stock in transit account actually include PPV and TPV alongwith standard cost.

  • In PO printout, how to add a customs also included in the total PO Value?

    Hi all,
                  In PO Printout customs value is not included in total PO value. But it's showing in the customs row, for ex. matrl value 100, customs 20. both are showing in PO Print out. But in PO Print out total value only matrl value is showing(100 not 120). how to correct it. where i have to do settings? can anyone help me in this regard.Thanks in advance.
    Pradeesh

    Pls check the Pricing Calculation schema settings.
    Regards
    TGB

  • How to copy total freight value from pricing procedure to TAXINN procedure

    Dear Experts,
    I want to copy the total freight value from pricing procedure to TAXINN procedure , i think i have to use SUBROUTINE for that but can you guide me what is the routine number and in which coloum i i have to use e.g. requirement, or ALt CAl Typ, or cond Base value ???
    e.g.
    freight condition type (QTY , freight) will enter manually e.g. 100 Rs and material qty 4 so total freight is 400 Rs this value (400 Rs) i want to copy from Pricing procedure to TAXINN
    How can achieve this ????
    Thanks and regards
    Hanumant Nimbalkar

    Hello,
    If you want to calculate VAT above Freight, then in Pricing procedure make the Sub total as blank for Freight confition types.
    And in Tax procedure, make the condition base value as 363 for VAT condition type.
    Make the tax code for 4 % VAT and u'll get the desired result.
    This will solve ur purpose.
    Regards
    Prabhjot Singh Nayyar

  • Total Net Value is picking automatically into one G/l a/c in posting time

    Hi to all,
    i have one critical issuse ,
    here i am doing  new pricing procedure in that i put 4 condition types
    80          ZLLU     Actual user price                                        ERL
    850                       Sub Total                      80         849
    860          ZTCS     Tax collection              850                                   ZTS
    872          ZOT1     Other charges 1                                        ZPK
    880                        Grand Total              850     879
    946          ZGPS     Price+ Tax + other      880                                   ZTS
    955                       Total                       945     954
    PR00       ERL
    ZTCS      ZTS
    ZOT1      ZPK
    ZGPS      ERL for this 4 account keys i have assigned different G/L A/C's but while posting into account's. Total net value of billing is hitting into one G/l A/c (that is ERL). it is not hitting into different G/l A/c's
    how it is possible can any clear by issuse ASAP
    REgards
    Murali

    Hi,
    Check Price procedure which key's assign to each condition.
    Check/Carry out configuration in t-code VKOA.
    ELSE,
    Go to VF02, put invoice number
    Environment >>> Account determination analysis >>> Revenue account,
    Here u will get detailed analysis, which condition is hitting proper G/L.
    Kapil

  • Total ordered value for PO

    HI All,
    Is there any standard report to check total ordered value for PO.
    I checked in ME80AN but its not giving excise value. I need Base + Excise + VAT / CST. (Total Net order value per PO)
    Please suggest.
    Regards
    Mahesh M J

    Dear Mahesh,
    ME81N - Anlysis of order values     -  By Material / By buyer /  By supplier           
                      Totals analysis - ABC analysis  -Analysis using comparison period - Frequency analysis
    Regards
    Anand

  • REPORT-TOTAL GR VALUE MONTHWISE

    Dear Experts,
    Please tell me the t-codes for
    1.viewing the total GR VALUE with respect to particular doc types for a month..

    Hi,
    Me not with system but you can Try with MR51,
    Posting date: To & from
    With Document type & execute.
    Get the report.
    Now select amount field and click the in the SUM icon in application tool bar and now get the total value.
    Regards,
    Biju K

  • 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.

Maybe you are looking for