Pricing - VOFM requirements

Hi,
I have a requirement routine assigned to 10 differentcondition types in the pricing procedure. Now there is a need for adding an additional check which has to be added in the same routine for 3-4 specific condition types in that. When I put the code its getting executed for all the 10 condition types against which the routine is assgined. So here i want to find out each time the current condition type also for which the rouitne is executing.But in the run time, i couldnt find any work area of variable which provided the current condition type which is calling the routine. the itab tkomv is available, but it contains all the condition types..
Anyone has an idea how to solve this ?
Thanks,
Dinu.

Copy your requirement into a new requirement and configure the new requirement in pricing to those 4 pricing conditions where you need this additional check. Just so that you do not double maintain the code call the original requirement from the new requirement, check return code and perform only addtional validations in the new requirement. This way any modifications made to the original requirements would also apply for new requirement. Better way of doing things rather than figuring out via code when do go with validations.
Thanks

Similar Messages

Pricing Condition: VOFM (requirements & Formulas)

Scenario:When we go to transaction VOFM and go to Requirements--->Pricing in the Menu we see all the routine numbers. One of the routine number in that system is 621.
I need to copy it and create a new one with the same code and add some more logic. How do I do that.

Hi,
you cant copy a routine just like that, what you can do is create a new routine requrest for access key becuase routine names will be in SAP namespace.
Copy your code and rememebr to activate it otherwise the routine will not appear in the procedure.
Regards,
Krishnakumar

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.

VOFM-requirements, data transfer, formulas

Hi experts,
I am now learning how to create pricing procedure. The part that remains still unclear to me is the requirement part. I tried to find some documentation of it but failed. I want to a systematical understanding about how pricing procedure works with the requirement, which conventions the requirement (VOFM: also data transfer,formulas) has, and how can I create my own requirement, data transfer and formulas.
Does anyone know any good documentation on subject?
Thank you in advance.
Best regards,
Fan

Hi Prasad ,
thank you very much for your reply.
This is indeed what I need. However, this is only the VOFM part 1. Do you have the link to part 2, 3, 4? I think there will be four parts of this documentation. Each specifies one subject regarding VOFM: copying requirements, data transfer,
requirements, and formulas.
Best regards,
Fan
Edited by: Fan Mou on Oct 23, 2009 5:19 PM

Pricing Procedure Requirment

Dear guru's,
                my client requirment is as follows.
               we have Two materials one is Service and other is Trading Material.Here service material is not collected any VAT Tax. Where as Trading Material needs to calculate VAT Tax.But these Two Materials are in one Sales Area.Document Type is one only.
              Now is there any way to use Two Pricing Procedures for One Sales Area and One Sales Document Type.
             kindly anybody guide.
Thank you
suribabu

Hello,
This is very normal scenario...
Say you are Selling a Air Conditioner & also charging Rs. 1,500 for Installation. Here you need to charge VAT on A/c but there would be no VAT (instead it would be Service Tax) on Installation (Service Item)
As you will have two seperate LIne Item in Sales Order, Maintain different Tax classification ('0' in case of Service) for Material & Service.
Also in Material master of Service, in Sales view there would be Tax Classification indicators. Maintain '0' for the VAT condition type.
Another option, if in the Key Combination of your VAT Condition Record if there is Material code, then dont maintain VAT Condition for Service Item. Thus it will not at all appear in the Sales Order.
Hope this helps...
Thanks,
Jignesh Mehta

MM pricing - help required ?

Hello all,
i require your help for pricing procedure.   refer the below pricing - conditions 1 nad 2 are related to cost of a material while 3 and 4 are related to freight. Also suppose condition 2 and 4 are manual.
now the requirement is - when you post GR, only 800+150 = 950 (actual cost) should get loaded on BSX ie.inventory a/c. but total cost 1200 should get loaded on GR/IR which i want to pay to internal vendor (plant vendor). also, condition 2 and 4 should get accrued to some G/L account.
can i configure this scenario in std SAP ? if yes, how? or do I need some enhancement ?
1.Actual price          800          BSX
2.Internal cost           200          Accrual
1+2=                               1000
3.Freight                               150          BSX
4.Internal freight cost          50          Accrual
3+4=                                200
123+4=                                1200          GR/IR
Waiting for your reply ASAP,
Thanks in Advance,
P

HI,
For condition 2 and 4 , maintin the Accruals and seperate Accopunt Key.
Click Accruals in Condition type and maintian the subtotal as 5 against that condition , so that the value will be added on to the material cost.
Regards,
Andra

Pricing Procedure Requirement

Hi All
In third party scenario our requirement is "PO Net Price should be Sales Gross Price". Is there a way to bring the pricing from PO to SO automatically.
Please guide me through.
Regards
JK

Hi Jagadish,
You maintain the conditon records through ME2k and with the help of the abaper , you can achieve this.
Cheers
Kris

VOFM requirement creation help

I'm trying to create a new requirement to be used for billing document output. The requirement is, only invoices 1 day older than current date is to be outputted. Using transaction VOFM output control, I've created a new requirement for application type V3.
I needed some guidance into coding this. My plan is to assign this new requirement to the access sequence I've created, so this requirement must always be met.
Very simple psuedo code:
if ( current date - document date != 1 )
then sy-subrc = 4
The problem I'm facing is that I don't know how to get the document date, since this program is running separately. If I could somehow get the invoice number that is currently being processed for output, then all is well.
please advise,
thanks in advance,
Mo

Hi
You need to add (by append structure) the document date in the structure KOMKBV3
Max
Edited by: max bianchi on Jan 11, 2011 4:04 PM

SAP Basis Security in Sales order pricing - Help required

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

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

Pricing Details Required for Sales order Item

Hi Gurus,
I have a requirement to get pricing details of sales order line item to be displayed on smart form.
Please let me know the tables which i need to refer to get the pricing details. Please let me know how I can link those tables from VBAK or VBAP.
OR
Please let me know if there is any function modules to get the pricing details of sales order header / item
Regards
Avi

Hi,
Check with the below table
Table : VBRK, VBRP, VBFA, KONV tables.
In VBRK and VBRP you can link with VBELN field. In VBFA table you can link with VBELV fireld.
Regards
Thiru

VOFM(Requirements Output Control)

Hi all,
We have custom output type configured which has to be displayed alone when a invoice is created for particular customer....All this part is done...but now i need to create a form routine and a requirement which wud be assigned to this output type which would display only this output type(Zxyz) say and should'nt display other standard output types like RD01 and other output types in the invoice outptut messages.....
How to create a routine is my first question for output control.
How to right a code in the routine which wud have only ZXYZ output type in the output message for particular Invoices.....

Hi,
Create a routine and assign the VOFM routine to all the other output types in the procedure except for the new one..
You can create the routine in the transaction VOFM..
In the VOFM routine have this logic.
If KOMKBV3-kunag = 'my specific customer'.
sy-subrc = 4.
ELSE.
sy-subrc = 0.
ENDIF.
Hope this helps..
Thanks
Naren

Oracle VM Sizing and pricing support required

Dear All,
Good morning,
I have a scenario in one of my projects where i have Servers in Intel platform and it goes like below.
Development environment_
1. Application server - 4 core
2. Databse server - 4 core
3. Weblogic Server - 4 core
Total 12 core for development environment.
PRoduction_
1. Application server - 2 server 4core each - 8 core
2. Weblogic server - 2 server 4 core each - 8 core
3. DB server - 2 servers 4 core each with RAC - 8 core
4. Oracle HTTP server - 2 servers 4 core each - 8 core
Total 32 cores in production.
Test_
1. Application server - 4 core
2. Databse server - 4 core
3. Weblogic Server - 4 core
Total 12 cores in Test.
Processors are Intel E5- 2600 series .
for all of the above environments i have suggested Redhat Linux.
now i do have the task of virtualizing this environment and i would like to go with Oracle VM. Could you please help me in sizing it properly and what will be the pricing for this.
i do need to have 3 years support.
Regards,
Binoy

This is a user-to-user forum.
No one from Oracle is expected to respond to forum posts.
Any reply you receive here might have false, inaccurate, or incomplete information.
Pricing is specific to each and every individual circumstance and can possibly change depending on where you are in the world.
You will need to contact the company directly and that will permit you to get official information.
Start here:
http://www.oracle.com/us/corporate/contact/global-070511.html

Pricing details required urgently

Hi,
i am struggling with the software pricing for a customer.
any Help in pin pointing the best pricing strategy for the below details (preferably in Singaporean dollars) would be highly appreciated...
Thanks and regards
Dwai
Each box is a system x 3650 [ 2 cpu s - each dual processor]
and customer owns licenses for oracle App Server.
Note :
With the below breakdown add 2 processor license for Oracle BAM on windows 2000 server
[2 boxes]Oracle Http Server [2 Hosts]
[2 boxes]
Db-
Oracle 10.2.0.3 RAC DB for SOA Suite
Oracle 10.2.0.3 RAC DB for OID
[2 boxes]
Oracle SOA Suite 10.1.3.3 Advanced Install + Sensor Edge Server+ Oracle AS Service Registry [4 hosts]
Components are as follows:
Oracle ESB [DT and RT] - Oracle SOA Suite 10.1.3.3 Advanced
Oracle BPEL PM - Oracle SOA Suite 10.1.3.3 Advanced
Oracle WSM - Oracle SOA Suite 10.1.3.3 Advanced
Oracle AS [patched 10.1.3.3] - Oracle SOA Suite 10.1.3.3 Advanced
Oracle Sensor Edge Server [Companion CD]
Oracle Business rules - Oracle SOA Suite 10.1.3.3 Advanced
Oracle HWF - Oracle SOA Suite 10.1.3.3 Advanced
Technology Adapters - Oracle SOA Suite 10.1.3.3 Advanced
Oracle AS Service Registry [Seperate Download] )
[1 Box]
OID release 10.1.4 [2 hosts]
----------------------------------------

I suggest to contact your local Oracle Sales Rep to discuss this issue.

Routines for Delivery Pricing (VOFM)

Hi,
We are writing a pricing routine to change condition values in delivery pricing. However no tables related to delivery line items appear during runtime. None of LIPS, XLIPS, etc. occur during the execution of the routine.
While similiar routines worked for Sales Order pricing (changing XKOMV-KBETR based on XVBAK, XVBAP values), it doesn't seem to work for delivery pricing.
Can someone suggest how to access delivery line items data during the creation of delivery.
Regards,
Murali

Hi Murali,
You can use dynamic assign techniques to access the data which is not available in the routines.
Take a look at this weblog on how to access the data which is not available using dynamic assign.
/people/brad.williams/blog/2005/04/25/userexits--how-do-i-access-inaccessible-data
good luck
Cheers
VJ

US pricing procedure required

Hi all
Can someone provide me a pricing procedure of any US company using jurisdiction method? In case we are not using an external system for calculating taxes, how should the taxes be configured?
The condition type UTXJ uses condition records, but the condition types JR1,JR2,JR3 etc are manual entries. Each one represents a level 1, level 2, level 3 etc. is this the different levels like state, county, city etc? are these values given manually ?
Thanks and Regards
Harish

Check this help link
[Procedures|http://help.sap.com/saphelp_47x200/helpdata/en/05/2ccd37b5264a54e10000009b38f842/frameset.htm]
thanks
G. Lakshmipathi

Pricing - VOFM requirements

Similar Messages

Maybe you are looking for