Summary
During order processing, shipping, LIS, billing, etc. an abnormal termination occurs when the system calls up an VOFM routine (external Perform). The error message: PERFORM_NOT_FOUND is displayed.
This symptom can affect all users of VOFM objects.
SDINVOFM, TFRM, TFRMT, VOFM, SAPMV80H, RV80HGEN, AKTIVIEREN_ALLE, formulas, conditions, data transport routine, copy routine, data transfer
Cause and prerequisitesThe called routine is not included in the calling program (= the Include line is missing in the respective Include carrier).
There is no entry for this routine in tables TFRM and TFRMT.
Thus routine is not active and cannot be used.
The respective ABAP does not exist in the system.
RESET N1
Start report RV80HGEN to include the used program into the carrier include. If the program continues to abend after the report has run, continue with the solution mentioned under 2.
Start report SDINVOFM using Transaction SE38. Further information on how to proceed can be found in the program documentation of this report!
Report SDINVOFM is delivered as part of the standard system as of Release 3.0B. For releases before 3.0B, you must copy the report from SAPSERV3 using FTP. The file is called /dist/permanent/Note.0028683.
The respective transfer order is called P30K049593.
Documentation on report SDINVOFM
The report enables you to directly create TFRM and TFRMT entries without having to detour to transaction VOFM. In particular, this procedure does NOT generate any new ABAP code which means that any ABAP code that already exists will NOT be overwritten!! The tables are only updated once the test mode has been deactivated!
The following list gives an overview of the classes that can be accessed via VOFM; column "SAP" contains the name of the standard Include carrier and column "Customer" contains the name of the customer's Include carrier. This list gives you the respective classes for a routine (see the example).
* Class SAP Customer
* ------------------------------------------------
* Copying requirements
abed lv45cnnn rv45bnnn
lbed fv50bnnn rv50bnnn
fbed lv60annn rv60bnnn
casb lv43annn rv43annn
tbed lv45tnnn rv45tnnn
* Data transports
adat fv45cnnn rv45cnnn
ldat fv50cnnn rv50cnnn
fdat fv60cnnn rv60cnnn
casc fv44annn rv44annn
tdat lv45tenn rv45tenn
vsel fv51annn rv51annn
* Text names
tnam lv70tnnn rv70tnnn
txnm fv46tnnn rv46tnnn
* Requirements
pbed lv61annn rv61annn
pbef lv61dnnn rv61dnnn
pben lv61bnnn rv61bnnn
pbek lv61cnnn rv61cnnn
pbel lv61gnnn rv61gnnn
* Batches
chbe l080mnnn r080mnnn
chrg lv01fnnn rv01fnnn
* Execution requirements
exko lv52ennn rv52ennn
* Follow-up functions
fofu lv07annn rv07accc
* Formulas
pfrs fv62annn rv62annn
pfra fv63annn rv63annn
pfrm fv64annn rv64annn
prun fv13annn rv13znnn
pstk fv65annn rv65annn
* IS-OIL-DS
OICA (carrier:SAPLV61A)fv69annn rv69annn < MAP
OIAA (carrier:SAPLMBGB) fv70annn rv70annn < Exchange
* Reporting
lst1 rv77snnn rv77unnn
* VIS
mcv1 sapfmcvf rmcvunnn
mcv2 sapfmcvf rmcvunnn
mce1 sapfmcef rmceunnn
mce2 sapfmcef rmceunnn
mcf1 sapfmcff rmcfunnn
mcf2 sapfmcff rmcfunnn
mcb1 sapfmcbf rmcbunnn
mcb2 sapfmcbf rmcbunnn
* QM
mcq1 sapfmcqf rmcqunnn
mcq2 sapfmcqf rmcqunnn
mci1 sapfmcif rmciunnn
mci2 sapfmcif rmciunnn
Note: The classes for the class areas SIS and QM can be read directly from the names of the routines; for example routine FMCB1402 belongs to the class MCB1.
If you want log texts, they contain information on whether TFRM / TFRMT entries and the corresponding ABAP exist in the system or not.
Example:
**********************************************************************
*** Example 1 *
**********************************************************************
A customer problem contains the error message:
PERFORM_NOT_FOUND: Program LV45C001 not found.
You can determine class ABED for LV45C001 (nnn = 001) from the list.
Program SDINVOFM is started with this class.
First run: the program runs in test mode
=====================================================================
Test mode is activated; Tables TFRM and TFRMT will not be updated.
Start parameters for Report SDINVOFM:
------------------------------------
Class ABED
Routine Number 1
Routines - short text
x Test mode
x Output log texts
Log texts from Report SDINVOFM:
------------------------------------
TFRM - Entry for Number 001 (Class ABED) : missing.
TFRMT - Entry for Number 001 (Class ABED, Language D): exists.
ABAP - Routine for Number 001 (Class ABED) : exists.
Interpretation of the Log:
-------------------------
The TFRM entry for this routine is obviously missing: an error may have occured during a transport.
2nd Run: The Program runs in production mode:
===================================================================
Start parameters for Report SDINVOFM:
------------------------------------
Class ABED
Routine Number 1
Routines - short text
_ Test mode
_ Output log texts
If the program is started with these parameters, the TFRM entry is created for class = ABED, Routine number = 1. At the same time, you branch to the respective VOFM Detail screen for this class.
CAUTION:
You still have to activate the routine;
Path: Edit -> Activate.
**********************************************************************
*** Example 2 *
**********************************************************************
As in example 1, but in the first run the log contains the note:
ABAP - Routine for number 001 (Class ABED) : missing.
In this case, please continue with Report SDCLVOFM.
Start parameters for Report SDCLVOFM:
------------------------------------
Class ABED
x Change mode
You once again branch to the Detail screen of VOFM for class ABED.
Caution:
You still have to activate the routine.
Path: Edit -> activate all.
Header Data
| Release Status: | |
| Released on: | 16.05.2001 22:00:00 |
| Priority: | |
| Responsible: | Gabriele Weyerhaeuser |
| Category: | |
| Primary Component: | CA-GTF-BS-VOFM |
| Secondary Components: | IS-OIL-DS |
| SD-BF |
Affected Releases
|
Related Notes
Attributes
|
Action Log
|
1379
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
