Inside the VOFM Program - SAPtech Solutions

1 Inside the VOFMP rogramTechnicalSolutionGuideThe Smith Consulting Group, Box 703 Flanders, NJ and R/3are the trademarks or registered trademarks of SAP AG in Germany and in several other 2005 The Smith Consulting Group, Inc. All Rights the vofm Program11/25/2005 Page2of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights structure of a vofm Indicator Indicator Codes contained in the vofm Custom Routine Range Determination by Group Name Determination by Group Include Name Determination by Group Class Determination by Group Include and Form Names Determined in the vofm Include of the Active the TFRM Include of the Short Program the vofm Program11/25/2005 Page3of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc.

2 All Rights many SAP specialists have used and created vofm routines in R/3, fewunderstand how these routines are technically implemented within the various programsand function groups in which they purpose of this paper is to provide a technical explanation of how the vofm transaction works. It is assumed that the reader has a working knowledge of the vofm transaction and ABAP programming. The screen shots and data in this document weretaken from an R/3 structure of a vofm routineVOFM routines are ABAP FORM routines and they exist in a wide variety of programsand function groups.

3 The routines are organized by a group code and there are manygroup codesavailable in the system. Each routine is contained in a unique ABAP includefile. These include files are then included in a parent include file. Finally, the parent include file is included in the main Program or function group. While this design mayseem complicated, it allows the generation, activation and deactivation of these routinesto occur without modifying the main Program . When a routine is created, a new includeis created and the associated parent include is updated.

4 Activation and deactivationmodify the parent include by adding or removing the include file that contains the vofm Program11/25/2005 Page4of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights Indicator CodeVOFM routines are organized using the Group Indicator Code. The vofm Program usesthe group indicator to determine the Program include and subroutine names when itdynamically creates these objects. The assignment of these names is hard coded in theprogram. The valid group indicator codes are defined in data base domain GRPZE usinga value GRPZEI nside the vofm Program11/25/2005 Page5of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc.

5 All Rights Indicator Codes contained in the vofm ProgramThe following table contains the group indicator codes that are hard coded in the vofm Program . This list may be different depending on the release and does not correspondexactly to the domain value requirements in the orderADATData transfer in the orderCASBC opying requirements for sales activitiesCASCData transfer for sales activitiesCHBEB atch search strategiesCHMVS tock requirementsCHRGB atch requirementsEXKOE xport requirementsFBEDC opying requirements in the billing documentFDATData transfer in the billing documentFOFUS ubsequent functionsLBEDC opying requirements in the deliveryLDATData transfer in the deliveryLST1 Info

6 Blocks for RV reportingLST1 Info blocks for RV reportingMCA1 Work item requirements (MCA = Activity)MCA2 Work item formulas (MCA = Activity)MCB1 Stock control requirementsMCB2 Stock control formulasMCE1 PURCHIS RequirementsMCE2 PURCHIS formulasMCF1 SFIS requirementsMCF2 SFIS formulasMCI1PM requirementsMCI2PM formulasMCL1WS requirements in LISMCL2WS requirements in LISMCQ1 QMIS requirementsMCQ2 QMIS formulasMCT1 TIS requirementsMCT2 TIS formulasMCU1 UIS requirementsMCU2 UIS forms (Utility Information System)MCV1 SIS requirementsMCV2 SIS formulasMCW1 RIS requirementsInside the vofm Program11/25/2005 Page6of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc.

7 All Rights formulasMCZ1 External data requirementsMCZ2 External data formulaPBEDP ricing requirementsPBEFM aterial determination requirementsPBEKA ccount determination requirementsPBELM aterial listing requirementsPBENO utput control requirementsPBNAFree goods requirementsPBWVR equirements for pricingPFRAP ricing formulas: Condition basisPFRMP ricing formulas: Condition valuePFRSP ricing formulas: Scale basisPNATPRUNPSTKS tructure of scale key for pricingREAKA rchiving for ordersREKAA rchiving for sales activitiesRELKA rchiving for deliveriesRERKA rchiving for billing documentsRISKRisk management (form of payment guarantee)TBEDC opying requirements for textsTDATData transfer involving textsTNAMText names for word processingTRAUData transfer transportTXNMText names for copying modules (out of date)

8 VCAUA uthorization requirements for payment cardsVFCLM ulti-dimensional scalesVKMPC redit check requirementsVSELData transfer for shipping unitsInside the vofm Program11/25/2005 Page7of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights MaintenanceSince vofm routines are named after the transaction, most people access the routinesusing the vofm transaction. Unfortunately, vofm only provides access to a subset ofthe routines available. An alternative is transaction VOFN, which provides access to allroutines in all VOFNVOFN is executed by group indicator (the screen refers to it as Class).

9 Inside the vofm Program11/25/2005 Page8of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights the group indicator is selected, the detailscreen looks and functions like the vofm detail screen. It is actually the same Program . The following example displays all of theroutines in the MCV1 class (SIS Requirement Routines). Inside the vofm Program11/25/2005 Page9of36 Technical Solution GuideCopyright 2005 The Smith Consulting Group, Inc. All Rights Custom RoutinesWhen implementing custom vofm routines, aquestion frequently asked is what routinenumbers should be used.

10 The answer is that it depends on thegroupindicator. The tableina subsequentsection denotes the starting customer range for each group indicator(Customer Include column). The selection of an appropriate routine number is importantbecause it determines the include file naming convention as well as the developmentclass used when creating the routine. The customer routine ranges are hard coded in theprogram. The following screen shotsdetail how it Routine RangesThe following screen shot is from the global data section of the Program . There are threepossible starting customer ranges defined (USER_GRPNO_FIRST1,USER_GRPNO_FIRST2 and USER_GRPNO_FIRST3).