Formulae activation in VOFM

HI Experts,
I have added 2 formulae in VOFM=> formulas=>Condition value for conditional sub totals.
I Have activated them in VOFM(Check box).
Still these formulae are not getting triggered. Is there any thing more that i need to do for activating the same?
I did execute the program "RV80HGEN" also.
***Help ful suggestions will be rewarded.
Thanks,
Mohammed.

hi
refer to the following documentation
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'.
hope it will clear all ur doubts
u can refer to the link as well given below
http://www.sapprofessionals.org/?q=vofm_requirement_and_formulas_for_sap_sd_pricing
regards
ravish
plz reward if helpful

Similar Messages

Activating a VOFM Routine

Hi Folks,
I have made a VOFM routine in data tranfer->Sales activities.I have activated the program and also the entry in "Maintain:Data transport sales activities" But still i am getting an error "No frame work was found for the Include RV44A601".I have no idea which configuration is missing now please help.I have also tried using SAP program RV80HGEN first and then Standard SAP program SDINVOFM used to identify and repair missing table entries in the VOFM control tables TFRM and TFRMT but in vain..:(
Attached are the screenshots.
Error:
Activated Program and Entry:
Thanks in Advance.

Abhishek,
There is no need to activate the standard programs like SAPLV43A or RV**NNN program separately when you are creating a custom routine.Once you register the Custom Routine in SAP Service Market Place you will get the SCCR key so that you can proceed with the coding.Once the coding you can activate the routine using RV80HGEN.This will activate the routine.To cross check whether the routine has got activated or not you can check if there is an entry with your custom routine program name in the corresponding RV**NNN program.This is only for confirmation and there is no need to separately activate other standard programs or transport these program along with your custom routine.
Running RV80HGEN will take care of activating the routine.The same activity needs to be done again once the TR is imported in the target client.
If you want to run RV80HGEN automatically ( instead of performing it as a cut over activity once the TR is imported to target client ) you can tag RV80HGEN as XPRA along with your custom routine in the TR and get this imported to target client.XPRA will set RV80HGEN for execution once the TR is imported to the target client.
You can refer to SAP Notes 86161 and 327220 for more info.
K.Kiran.

Routine is not activated in VOFM - Output Control for Inventory Mangmt.

Hi Guys,
I wrote an enhancement routine for invemtroy mangmt. in VOFM tcode.
Even though I actiavte the code, still the routine active box is not checked in VOFM.
I also run the program RV80HGEN to genarate the routine.. still Active box not checked in VOFM.
Anything else I need to do ?
Cheers

Hi,
I think you may need to regenerate the VOFM routines.
Please check the SAP NOTE: SAP Note Number: 406054
Solution
Start the report RV80HGEN to include the used program in the carrier include of the calling application.
If this doesn't work, could you please kindly let us know more detail on what you coded in the routine?
Cheers,
Edited by: NI SHILIANG on Mar 17, 2010 7:31 AM

Would RV80HGEN turn on the 'Active' indicator in VOFM

Hi Guru, does any body know if RV80HGEN will turn on the 'Active indicator' in VOFM? Or does it only generate the codes for all routines marked as 'ACTIVE' in VOFM?
When we do the transport from test to QA, newly created routines are "INACTIVE" in QA even the active flag is turned on in test client when the transport is created. All the help documents stated we need to use RV80HGEN to active/generate the new routine, but it does not turn on the 'ACTIVE' set in VOFM, table TFRM in our case.
Any advice is appreciated.

Found out our issue was due to a missing transport. Issue solved

VOFM - Requirements

Hi Folks,
I am working on requirements.
I am a bit new to this process.I wud like to have some detailed info on the same.Please clarify the below mentioned.
1.I've seen Requirements in VOFM only for some areas..like output control,pricing,material determination etc. what is the working mechanism of this? How is it different from USER EXITS?
2.The same piece of code appears twice in the same requirement under to differnet form definitions,namely form KOMBD and KOMBV ? why this is required twice?
3.why do we need to run RV80HGEN after creating a requirement?
4.From where the number series starts for newly defined routines apart from standard requirements?
5.If we want to modify the standard exist what are the precaution to take? what i heard is ..once we give the access key for it...there is some icons apper on tool bar like INSERT DELETE etc..
Your help is appreciated.
Thanks
Raja

Hello Raja,
As indicated only for the following as indicated number range is allowed for rest it is 600-999.
Name Number
Subsequent functions 900 - 999
Group key routines 50 - 99
Data transfer routines f. texts 50 - 99
all other group indicators 600 - 999

I am attaching another note which deals with VOFM problem. Keep this with u as it will prove useful.
 SAP Note 327220
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 subareas:
 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. <<<result value assignment
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.
2.7 FAQs: Possible causes of errors and problems
This chapter deals with the most frequent errors and problems that occur when using the VOFM function and its objects. If problems arise for which this note provides no explanation or solution, create an OSS message on component CA-GTF-BS-VOFM and send it to the SAP Support.
(01) Question/problem:
 During the order processing, in the shipping, LIS, billing and so on a program termination with error message: PERFORM_NOT_FOUND occurs when you call a VOFM object. This symptom can occur for all users of VOFM objects.
(01) Answer:
 The used VOFMobject is not known in the main program of the calling program and thus cannot be addressed. Details on the call method of VOFMobjects are described in section 2.4 of this note. Note 28683 describes how to correct this error.
(02) Question/problem:
 Even though report RV80HGEN was executed, the VOFMobject is not registered in the object carrier. Why?
(02) Answer:
 During the setup of the object carriers via RV80HGEN the system includes only VOFMobjects which have set the 'active indicator' (refer to section 2.3.2). If the active indicator for the corresponding object is not set, the RV80HGEN does not process the VOFMobject. Solution: Set the active indicator for the respective object and start the RV80HGEN again.
(03) Question/problem:
 The syntax check in the ABAP form routine of an VOFM object displays syntax errors.
(03) Answer:
 Note the explanations on the work method of the syntax check in Note 393012. In addition, the restrictions of the SAP maintenance responsibility to customer-specific VOFM objects (described in section 1.3) apply.
(04) Question/problem:
 When you create/change VOFM objects the system requires an SSCRregistration key, even though the VOFM is within the 'customer namespace'.
(04) Answer:
 Refer to the explanations given in section 2.2. 1 'Registration'.
(05) Question/problem:
 In which namespace can I create customer-specific VOFM objects? Or: Which routine numbers are reserved for customers?
(05) Answer:
 Refer to Note 356737, in addition refer to the explanations in section 2.2 'Namespaces'.
(06) Question/problem:
 Is it possible to assign VOFM objects to own development classes?
(06) Answer:
 No. Refer also to section 2.2.1
(07) Question/problem:
 When you create a VOFM object the system displays information message TR 015 'Object can only be created in SAP development class'.
(07) Answer:
 This is no error. Refer to section 2.2.1. and the answer to question number 5.
(08) Question/problem:
 How can I transport VOFM objects via the Change and Transport System ?
(08) Answer:
 The steps necessary for a successful transport are described in detail in Note 22808.
(09) Question/problem:
 The used transport request does not contain an entry for the VOFM object carrier in the object list (for example RV61ANNN, FV45ANNN ...)
(09) Answer:
 The object carriers must not be transported. Instead, a setup of a current object carrier suitable for this system is required in the target system. For details refer to Note 22808, step 5 as well as section 2.4.1 and 2.5 of this note.
(10) Question/problem:
 How are VOFM objects deleted? And can deletions of VOFM objects also be transported?
(10) Answer:
 You should delete VOFM objects only via the editing interface of the VOFM function. Only this way it is ensured that all subobjects (ABAP form routine, TFRM and TFRMT table entries) are completely removed.
 You can also transport the deletion youmade into an additional system. For that purpose, the setup of an object list in a transport request analog to the creation (refer to Note 22808) is required.
 During the deletion of objects the system deletes the object in the source system. At the time of the export the export program (R3trans) notes that the object does not exist any more. In this case the system enters a "D" into the 'Object function' field in the corresponding entry in the object list of the transport request.
 The deletion of table entries is made analog to the deletion of objects. First delete the keys in the source system. Then specify the deleted keys in the request. At the time of the export the transport program notes that the specified keys do not exist any more and deletes them in the target system. If you combine the object list of the transport request manually, you must set the object function of the individual entries correspondingly. To do that, proceed as described in the F1 help of the 'Object function' field.
(11) Question/problem:
 During the creation of VOFMobjects the system requires a transport request which contains a task of the 'Repair' category. The system displays message TK 181 'Repair &1 may only contain repaired objects'.
(11) Answer
 This problem is caused by a program error. Implement the corrections of Note 326560 or Note 385067 depending on your release.
(12) Question/problem:
 During the creation the system displays message TK 112 'Edit objects separately since they belong to different original systems'.
(12) Answer:
 This problem is caused by a program error. Implement the corrections of Note 326560 or Note 385067 depending on your release.
(13) Question/problem:
 When you create or activate VOFM objects the system displays message: 'Report/PROGRAM statement is missing or program type is INCLUDE?'.
(13) Answer:
 This problem is caused by a program error. Implement the corrections of Note 326560 or Note 385067 depending on your release.
(14) Question/problem:
 Why does the system generate VOFM objects with source system 'SAP'?
(14) Answer:
 Design. The entire VOFM logic depends extremely on basis functions like transport, object directory entries, generation and so on. Because VOFM objects are inserted in SAP standard development classes, these receive ID 'SAP' for source system during the generation process. This cannot be avoided and does not affect the VOFM function.
(15) Question/problem
 The system does not insert report RV80HGEN automatically as XPRA into the object list of a transport request.
(15) Answer
 Whether the system inserts report RV80HGEN automatically into the object list of the transport request depends on the release you use. For Releases 4.0A to 4.6B the system generates a corresponding entry, provided that all corrections for the VOFM function exist in the system. As of Release 4.6C the basis function of the 'Change & Transport System' (CTS) does not support the automatic insertion of objects of the 'XPRA' category into an object list any more. If you want an automatic registration of the transported routines in the target system, proceed as described in Note 22808, step 5.
(16) Question/problem:
 During the activation of VOFM objectsa termination occurs or the system requires a registration key for additional VOFM objects, even if they were not changed.
(16) Answer:
 There are inconsistent VOFM objects in the system (refer also to section 2.3.), that means table TFRMcontains entries for which no include with corresponding ABAP form routine exist.
 If the termination occurs for VOFM objectsfrom the SAP namespace, this is normally due to a delivery error as described, for example, in Notes 395600 and 0403705. Check whether already a corresponding note exists for the affected VOFMobject. If not, contact the SAP Support.
 If the problem occurs for customer-specific routines, the inconsistency is mostly due to a handling or transport error. For example the deletion of VOFMincludes via Transaction SE38has the effect that the system does delete the form routine and the corresponding include, however the system does not delete the entries in tables TFRM and TFRMT. Inconsistencies can also occur due to incomplete or incorrect object lists in transport requests. You can make a correction by newly creating the same object via the VOFM interface or be deletion analog to the method described in Note 395600.
(17) Question/problem:
 During the import of Support Packages or during the system upgrade, customer-specific VOFM objects were overwritten or are missing completely.
(17) Answer:
 First, check whether the missing VOFMobjects are really missing and if yes, whether all or only certain subobjects do not exist anymore (refer to section 2.3). if the VOFMobject is completely there, generally only a new setup of the object carriers is required. Read section 2.5 'Activation, generation and RV80HGEN' to learn which options exist for this purpose.
 If there is indeed a VOFM object but ifthe source code of the ABAP form routine does not correspond to the customer-specific, this is a delivery error. However, you can reconstruct the customer-specific source code with the version management. Proceed as follows: call the ABAP Editor for the affected objects by using Transaction SE38. Afterwards branch into menu 'UTILITIES' -> 'VERSIONS' -> 'VERSION MANAGEMENT'. Deselect the version delivered by SAP and select your original, customer-specific version instead. Choose 'RETRIEVE' to restore this version.
 Delivery errors of this type are documented by notes. If there is no corresponding note for the overwritten object in the OSS, contact the SAP Support.
(18) Question/problem:
 In the display of the Object Navigator (Transaction SE80) the system does not display newly created VOFM objects. On the other hand, it can also occur that deleted VOFM objects are still contained in the Object Navigator.
(18) Answer:
 The Object Navigator displays an obsolete status (refer also to Note 15447). Choose button 'Refresh object list' above the tree structure in order to correct this inconsistency.
(19) Question/problem:
 Is it possible to delete VOFM objects delivered by SAP in the standard?
(19) Answer:
 Yes. However, because of separate number ranges for VOFM objects SAP does not recommend a deletion of SAP standard objects.
(20) Question/problem:
 Which maintenance responsibility has SAP for customer-specific VOFM objects?
(20) Answer:
 None. Refer to the explanations in section '1. 3 A frank word on the "source code responsibility"'. According to Note 381348 this includes also VOFMobjects whose creation wasbased on notes of the 'Consulting' or 'Workaround for missing function' category.
(21) Question/problem:
 Where can I get help, if my customer-specific VOFM object does not work as expected?
(21) Answer:
 If you need support during the implementation of customer-specific VOFM objects you can contact the SAP Remote Consulting. Please understand that SAP cannot check VOFM objectswithin the framework of the normal support.

Service Tax Payable Transfer - Incorrect Amounts

Dear all
I am facing the following issue while using S_AC0_52000644 - Tax Reports -> General -> Deferred Tax -> Deferred Tax Transfer (New) for transfer of Service Tax(Output) from Interim to Payable accounts -
The accounting entry that is generated at the time of Billing document is as below -
Customer                        110,300.00
Domestic Sales                          100,000.00-
Output Service Tax Interim Basic     10,000.00-
Output Service Tax ECS Interim     200.00-
Output Service Tax H & ECS Interim     100.00-
Hence, ideally the service tax that should be transferred from Interim to Final Payable should be Rs 10000, Rs 200 and Rs 100. However, when i execute the transfer program, the amounts that are getting transferred are not correct, the base amount gets changed. In the present case for e.g for Output Service Tax Interim Basic, the base amount is displayed as 109,510.22 and the tax amount as 10,142.65.
We are using TAXINJ and have maintained the 2 tax codes i.e deferred and final. The tax rates are maintained at the tax code level in FTXP and the rates are 10%, 2% and 1%.
Any help on this issue will be highly appreciated.
Thanks
Hrishi

Hi:
        Please see the OSS Note 921634 - Service tax India: Transfer from Interim to Final account to rectify the issue. There seems an issue with your routine assignment and activation in VOFM (ask SD Guy). Also check in FTXP if this tax code has more than one line item. If there are then deactivate the one not required. Another way to avoid this issue is to go to FS00 and in the control tab, select indicator "posting without tax code allowed" ..
Regards
Edited by: Atif Farooq on Sep 30, 2011 7:16 PM

New SD copy routines

Hello,
I have created 2 new routines, 900 and 901, in VOFM but when I go to transaction VTAA to assign them they do not show up as available in the drop down. They are active in VOFM. Is there a step I am missing?
Thank you,
JR

did you activate main program ?
Check this PDF..for creating a new VOFM copying requirement.
http://saptechsolutions.com/pdf/VOFMCopyRequirementRoutines.pdf
Regards,
Maha

Vofm fomula routin activation error.

i have complete a formula via tc:'VOFM', and i would like to active the routin, but get error message" Report/Program statement missing, or program type is i (include)". what can i do?

Hi,
You have to create the routine via VOFM, an include will automatically be created in the required main include/program. Put you your codes in the routine/form activate it. then got back to VOFM :
- select routine
- Click on EDIT and activate
This will activate your codes and routine.
Regrads,
Dev.

VOFM routines activation

Hi Sap Guru's,
As per my client requirement, I have maintained new routine in VOFM by using below navigation:
routine names are 902 & 903 & their includes are RV64A902 & RV64A903.
Now, when we move the changes to quality server then the routines are showing in VOFM but in standard program RV64ANNN it’s not
available. (so when we run sales order then the includes 902 & 903 is not triggering)
So I ran the standard program RV80HGEN. (to activate VOFM routines)
Then the routine names are populated into standard program RV64ANNN. (when we run sales order then the includes 902 & 903 is triggering & its working as expected)
But same changes we moved to production server, so if I will run the same standard program RV80HGEN in production environment then all other
customized routines also activating including my 902 & 903 routines.
So please suggest me, how can I will overcome the situation.
I have to activate my routines 902 & 903 only in production server.
Thanks in advance.
BR,
Shabareesh

Hello,
but still I don't understand your perplexity:
In order to avoid all confusions, we have planned to do below steps:
Capture our routines in new TR with standard program RV64ANNN (Development server)
Then we will move the changes to QAS server & check the result
If result would be fine, then we will move the TR to PRD.
this should be the standard and "best-practice" approach for any kind of change.
Request you to confirm on above point or we will go ahead to run RV80HGEN program directly in PRD.
When you transport a newly created routine, you always need to run program RV80HGEN to be sure that it's correctly and completely activated. But it won't do any harm. Unless you moved to Production environment a routine that you don't want to activate: but this is not the correct and advisable approach.
Best regards,
Andrea

VOFM, RV45C901 Activation

Hi all,
I've created a custom data transfer routine (RV45C901). The problem is I get a short dump in our production system whenever I try to run it. We encountered this in QA and I reactivated a bunch of stuff (I don't remember what order and what objects) but eventually got it to work.
In our production box I was going to try to deactivate and reactivate it in VOFM but it has status "not modifiable". So in development I created a new transport where I deactivated and reactivated the routine in VOFM. This still didn't work.
Any ideas? Are there specific steps to take? How can this be avoided in the future?
Thanks!

Hi,
Try to run the program RV80HGEN to generate the VOFM routines..
In future when you are transporting the VOFM routine..Manually add a entry in the CR with the following data in the object list..
R3TR XPRA RV80HGEN
If you give this the program RV80HGEN will run once the transport is complete..
Hope this helps..
Thanks,
Naren

VOFM routine - NO frame work

Hi all,
    By posting an inbound idoc we are creatin a purchase order and post goods issue for the purchase order.
    When a purchase order is getting created an entry is getting updated in NAST table which trigger the idoc ORDERS05.
    This idoc triggering should happen only when the Post goods issue is successful.
    Now for this am creating a routine in vofm. 903. Inside the routine am looping at XNAST table and checking for condition
    and making the sy-subrc as 4. i activated the include and routine. i executed the program RV80HGEN.
    But when i try to create a break point there it says.."No framework program was found for include RV61B903"
This routine is related with output Control...kindly help..
   What am I doing wrong here.
   Regards
   Sridevi S
Edited by: Sridevi Sivanandam on Jan 7, 2011 7:45 AM
Edited by: Sridevi Sivanandam on Jan 7, 2011 7:47 AM

You can try testing this by:
- assign your output type and put there dispatch time = '1'
- setup breakpoint
- execute program RSNAST00 for your PO/output type
This way you should be able to debug output triggering.
Regards,
Dominik Modrzejewski

How to call routine and pass data to routine in vofm

Hi Experts,
I need to update KBETR and KWERT values present in 'Conditions Tab' in Purchase Order (ME21N/ME22N).
I have created a new customer tab in which we enter amount field and percentage filed. When user enters some value in this and clicks on 'Conditions Tab', calculation has to be done and the calculated value has to be appeared across a specific condition type.as i am new to abap i dont know how to create routine and pass data to routine in vofm from customised tab in me21n .
Thank's in advance

Hello Rajendra,
You can get plenty of forums in SCN related to it. Follow below steps to create VOFM routine.
Go to VOFM Transaction Code
1. On the Menu Select required Application i.e Pricing
2. Enter any Number in between 600 to 999 for Custom Developments.
3. On entering Pop Screen appears ask for Access Key(We have to remember that Every New Routine needs an Access Key)
4. Once the Access Key is received we can do modification.
5. Enter the Routine Number ,description and insert the Access Key
6. Now the ABAP Editor will open and required code can be copied from Standard SAP Routine and Custom Code Can be developed.
7. Once the coding is completed we have to Activate the Routine
8. Select the Routine and Go to Edit – Activate
9. Ensure that Active check box is ticked upon Activation of the Routine.
10. Double click on the routine will enter into ABAP Editor, we have to generate the Routine
11. Go to Program and select Generate
12.A screen pops up with the related Main Programs and select all required main programs wherever the Routine is being called.
13. Once the Routine is Generated and Activated, We need to configure the Routine in the config.
** Important SAP note: 156230.
Check the below document too.
http://www.scribd.com/doc/35056841/How-to-create-Requirement-Routines
Regards,
Thanga

Add a new field in va02,va03 and vf02 & data tran. in these fields VOFM

Hi All,
I have a requirement, I need to add a new field in the sales order header part and even a field in the billing document, once I add this field up in both the documents in the header part i need to create a copy routine using the VOFM transaction,
Can any body help me on what's the procedure to add a field in billing document as i dont find any screen exit for doing it and does the copy routine transfer the data ( Custom Field ) from Sales Order to the Billing Document, if yes can somebody help me with the procedure on how to and code of it.
Regards.

Hi,
The procedure to create the new VOFM.
1. Go to VOFM transaction
2. Page down until you find a new spot on the page to put in the VOFM number and description.
3. Put in the VOFM number and the description of the VOFM.
4. Now the VERY IMPORTANT part of the process. Double click on the VOFM description not the VOFM number to create this as a Development/Correction and not as a repair. If you double click on the number then this copies some existing code and prompts you for a repair.
5. Activate and generate the VOFM routine. Note: Configuration must be setup by the OM team for this step.
for example Go to the routine number that needs to be copied.
Put your cursor on the routine number field that needs to be copied.
Overwrite that number with your new routine number and hit enter.
The new routine will be created as a copy of the old routine and you can modify the new routine as you need it.
Ex.
You have to copy routine 104 to 904
Routine number Description Active
104 Bill.bus.item data X
Put your cursor on 104 and then change it to 904 and hit enter.
904 will be created as a copy of 104 and you can make your changes in 904.
Don't forget to activate it after you are done.
refer the below link
https://forums.sdn.sap.com/click.jspa?searchID=3604222&messageID=994791
Regards

VOFM problem

I am trying to modificate the net price in VOFM for a purchase order, but i need to know the position of the purchase requisition order that i put in the table control of me21n and when i make a get parameter of BAP parameter i don´t find the data, and i can´t find it in komp, komk, xkomv structure, does anybody how can i get this data in my routine?
thanks in advance

Hi,
The procedure to create the new VOFM.
1. Go to VOFM transaction
2. Page down until you find a new spot on the page to put in the VOFM number and description.
3. Put in the VOFM number and the description of the VOFM.
4. Now the VERY IMPORTANT part of the process. Double click on the VOFM description not the VOFM number to create this as a Development/Correction and not as a repair. If you double click on the number then this copies some existing code and prompts you for a repair.
5. Activate and generate the VOFM routine. Note: Configuration must be setup by the OM team for this step.
for example Go to the routine number that needs to be copied.
Put your cursor on the routine number field that needs to be copied.
Overwrite that number with your new routine number and hit enter.
The new routine will be created as a copy of the old routine and you can modify the new routine as you need it.
Ex.
You have to copy routine 104 to 904
Routine number Description Active
104 Bill.bus.item data X
Put your cursor on 104 and then change it to 904 and hit enter.
904 will be created as a copy of 104 and you can make your changes in 904.
Don't forget to activate it after you are done.
refer the below link
https://forums.sdn.sap.com/click.jspa?searchID=3604222&messageID=994791
Reward points
Regards

Problem in VOFM Urgent.

Hi All,
I have created a routine in VOFM in which i just copied routine of service agent and shipment type.I named it starting with 903.
Now the problem is that my functional consultant tells that when he is going to VT02N and giving a shipment number the forwarding agent should be populated in the shipment screen.But it is not coming now.
So what I want to know is how do i know where the problem is?
i.e how to debug.Also I have activated the routine i created.Anything else i need to do?
Thanks in Advance,
Saket.

Hi ,
I hope the Custom Routine you created is assigned against the Service agent and shipping type , so that it can check the new routine for getting these values.
If so,please put a break point in the routine and check in debugging mode.
Regards,
Savitha.

Formulae activation in VOFM

Similar Messages

Maybe you are looking for