SAP Note 22808 - Transferring formulas

Symptom:

Formulas and requirements created in the source system with Transaction VOFM do not arrive in the target system.

Cause and prerequisites

Transport connection cannot be implemented at all before Release 4.0A. After that it can be partly implemented.

Solution

As of Release 4.0, changes to VOFM objects (change/creation) are automatically transferred to a transport order. As a result of this, the steps 1 to 4 described below are not applicable as of Release 4.0A. However, step 5 must still be carried out.
In case of deletions, all steps have to be carried out depending on the release (< 4.6C) and maintenance level, if required.

Please proceed as follows to transfer a formula:

Step 1: Enter the formula to be transported in a correction request.
You get the name of the formula for the entry in the correction by calling the editor for maintaining the ABAP/4 program code of this formula.

You can enter R3TR PROG or LIMU REPO ( = name of the formula, 8 characters)

Example : Formula > Condition base value 601
When calling the editor, you will find the name of ABAP/4 program code in the header line: RV63A601.

The entry in the correction is ------------------------------
PgmID Obj Object name Function ObjStatus
R3TR PROG RV63A601
Step 2: Transport the corresponding entries of tables TFRM and TFRMT into the target system.

Example : Formula > Condition base value 601

The entry in the correction is ------------------------------
PgmID Obj Object name Function ObjStatus
R3TR TABU TFRM K
R3TR TABU TFRMT K
Fill the key on the 2nd detail screen as follows (you can skip the 1st detail screen simply by double-clicking):


Key field list (for table TFRM) ------------------------------------------ Field description Category Item Value
Group indicator C 1 PFRA
FORM routine N 2 601


Key field list (for table TFRMT) ------------------------------------------ Field description Category Item Value
Language C 1 D
Group indicator C 2 PFRA
FORM routine N 3 601


The following entries are possible for the group indicators:


PFRA Formulas for pricing: Condition base value
PFRM Formulas for pricing: Condition value
PFRS Pricing formulas: Scale basis
PBED Pricing requirements
PBEK Account determination requirements
PBEL Material listing requirements
PBEN Output control requirements
PSTK Structure of scale key for pricing
FDAT Data transfer in the billing document
FBED Copying requirements in the billing document
ABED Copying requirements in the order
ADAT Data transfer in the order
LDAT Data transfer in the delivery
TBED Copying requirements for texts
TDAT Data transfer involving texts
LBED Copying requirements in the delivery
CASB Copying requirements for sales activities
CASC Data transfer for sales activities
LST1 Info blocks for RV reporting
MCV1 Requirements SIS
MCV2 Formulas SIS
MCE1 Requirements Purch.Info.System
MCE2 Formulas Purch.Info.System
MCF1 Requirements PPIS
MCF2 Formulas PPIS
MCB1 Requirements stock control
MCB2 Formulas stock control
MCQ1 Requirements DMS
MCQ2 Formulas DMS
MCI1 Requirements PM
MCI2 Formulas PM
VSEL Data transfer for shipping units
CHRG Batch requirements
CHBE Batch search strategies
EXKO Export requirements
TXNM Text name for copying modules
TNAM Text name for online word processing
FOFU Subsequent functions

Step 3: Release the correction and the corresponding transfer order for the target system.


Step 4: Please check the transport log of the transfer order.


Step 5: Start report RV80HGEN in the target system. All formulas indicated as being "active" in TFRM are activated for the application programs.
If you do not want to start this report in the target system manually, you can also transfer report RV80HGEN as the XPRA to the transport order in the source system (workbench organizer, SE09). The corresponding entries are:

• PgmID = 'R3TR'

• Obj = 'XPRA'

• Object name = 'RV80HGEN'
  
  CAUTION: There is no check for the existence of a formula that is indicated as active, that is: if the relevant ABAP/4 program code is missing, cancellations can occur when calling the individual applications (syntax error, because the Include was not found).
  ACTION: Deactivate the corresponding formula and delete this formula using Transaction VOFM.