Funds Management Ver 4.7

[deepa_khatri]

Hi everybody,

I wanted to know some patches are required for Funds Management Module in Ver 4.7 because i had maintained basic configuration for Fund management after that in several areas errors started coming like while doing Reversal using FB08 dump is coming...in sales deriveries error is coming so please let me know if some Partches which needs to be in Ver 4.7

Thanks

Deepa

[iklovski · Accepted solution]

Hi,

Of course, there were several updates for the PSM-FM in 4.7 and I have no idea what package do you have. You'd better address your question directly to SAP-OSS. Otherwise, specify what problem exactly do you have.

Regards,

Eli

[deepa_khatri · Accepted solution]

Thanks Eli,

Im getting dump or errors in some areas .These are coming after the configuration of FM.

As for example while doing doc reversal FB08 following dump is comming

Runtime errors CALL_FUNCTION_NOT_FOUND

Exception CX_SY_DYN_CALL_ILLEGAL_FUNC

Occurred on 22.07.2009 at 16:19:03

-

---

Function module "FMREAS_GET_DPR_ACCOUNT" not found.

-

---

What happened?

-

---

The function module "FMREAS_GET_DPR_ACCOUNT" was called, but cannot be

found in the Function Library.

Error in ABAP application program.

The current ABAP program "SAPLFMRI_CORE" had to be terminated because one of

the

statements could not be executed.

This is probably due to an error in the ABAP program.

-

---

What can you do?

-

---

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

-

---

Error analysis

-

---

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',

was neither

caught nor passed along using a RAISING clause, in the procedure

"FM_DOCUMENT_FM_ASSIGNMENT_GET" "(FUNCTION)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

The program "SAPLFMRI_CORE" contains a CALL FUNCTION statement. The name

of the function module to be called is "FMREAS_GET_DPR_ACCOUNT".

No function module exists with the name "FMREAS_GET_DPR_ACCOUNT".

All function modules are stored in the Function Library (SE37).

Possible reasons:

a) Wrong name specified. Particular attention should be paid

to upper/lower case and underscores ("_")

b) Transport error

c) If an enqueue/dequeue module has been used, the lock object

may not have been activated (ABAP Dictionary)

may not have been activated (ABAP Dictionary).

-

---

How to correct the error

-

---

The exception must either be prevented, caught within the procedure

"FM_DOCUMENT_FM_ASSIGNMENT_GET"

"(FUNCTION)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Check the last transports to the R/3 System.

Is the program "SAPLFMRI_CORE" currently being changed?

If an enqueue/dequeue module is involved, is the activation

of the lock object missing in the ABAP/4 Dictionary?

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC

"SAPLFMRI_CORE" or "LFMRI_COREU04"

"FM_DOCUMENT_FM_ASSIGNMENT_GET"

-

---

Function modules with names similar to "FMREAS_GET_DPR_ACCOUNT":

FM_GET_CASH_ACCOUNT

FMR_DERIVE_ACCOUNT

FDBA_GET_DIFFERENCE_ACCOUNT

FI_GL_ACCOUNT_FAST_GET

FM_DC_ACCOUNT_ASSGMT_TEXT_GET

FM_OPEN_ITEM_GET_CUR_ACCOUNT

FIAA_GL_ACCOUNTS_GET

FM3R_GET_POSIT_FROM_ACCOUNT

FM_ACCOUNT_ASSIGNMENT_GET

FM_ACCOUNT_GET_COBL

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

-

---

System environment

-

---

SAP Release.............. "620"

Application server....... "sam_dev"

Network address.......... "172.16.1.51"

Operating system......... "AIX"

Release.................. "5.1"

Hardware type............ "0051495A4C00"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 0

Short dump setting....... "full"

Database server.......... "sam_dev"

Database type............ "ORACLE"

Database name............ "DEV"

Database owner........... "SAPDEV"

Character set............ "en_US.ISO8859-1"

SAP kernel............... "640"

Created on............... "Oct 29 2006 20:42:11"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "OCI_920 "

Patch level.............. "155"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"

-

---

User, transaction...

-

---

Client.............. 200

User................ "FINTL"

Language key........ "E"

Transaction......... "FB08 "

Program............. "SAPLFMRI_CORE"

Screen.............. "SAPMF05A 0105"

Screen line......... 43

-

---

Information on where terminated

-

---

The termination occurred in the ABAP program "SAPLFMRI_CORE" in

"FM_DOCUMENT_FM_ASSIGNMENT_GET".

The main program was "SAPMF05A ".

The termination occurred in line 27 of the source code of the (Include)

program "LFMRI_COREU04"

of the source code of program "LFMRI_COREU04" (when calling the editor 270).

Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"

occurred in the

procedure "FM_DOCUMENT_FM_ASSIGNMENT_GET" "(FUNCTION)" but was not handled

locally, not declared in the

RAISING clause of the procedure.

The procedure is in the program "SAPLFMRI_CORE ". Its source code starts in

line 5

of the (Include) program "LFMRI_CORE$04 ".

-

---

Source code extract

-

---

000010 function fm_document_fm_assignment_get.

000020 *"----

---

000030 ""Lokale Schnittstelle:

000040 *" IMPORTING

000050 *" REFERENCE(I_BUDAT) TYPE BKPF-BUDAT

000060 *" REFERENCE(I_BELNR) TYPE BKPF-BELNR

000070 *" REFERENCE(I_GJAHR) TYPE BKPF-GJAHR

000080 *" REFERENCE(I_BUKRS) TYPE BKPF-BUKRS

000090 *" REFERENCE(I_BUZEI) TYPE BSEG-BUZEI OPTIONAL

000100 *" CHANGING

000110 *" REFERENCE(C_FIPOS) TYPE BSEG-FIPOS

000120 *" REFERENCE(C_FISTL) TYPE BSEG-FISTL

000130 *" REFERENCE(C_GEBER) TYPE BSEG-GEBER OPTIONAL

000140 *" REFERENCE(C_FKBER_LONG) TYPE BSEG-FKBER_LONG OPTIONAL

000150 *" REFERENCE(C_GRANT_NBR) TYPE BSEG-GRANT_NBR OPTIONAL

000160 *" REFERENCE(C_MEASURE) TYPE BSEG-MEASURE OPTIONAL

000170 *"----

---

000180 data:

000190 l_flg_isps_not_active type c.

000200

000210 *----- Nur Aufrufen wenn IS-PS aktiv ist

000220 call function 'FM00_CHECK_ISPS'

000230 importing

000240 e_flg_isps_not_active = l_flg_isps_not_active.

000250 check l_flg_isps_not_active is initial.

000260

-

---

> call function 'FMREAS_GET_DPR_ACCOUNT'

000280 exporting

000290 i_budat = i_budat

000300 i_belnr = i_belnr

000310 i_gjahr = i_gjahr

000320 i_bukrs = i_bukrs

000330 i_buzei = i_buzei

000340 changing

000350 c_fipos = c_fipos

000360 c_fistl = c_fistl

000370 c_geber = c_geber

000380 c_fkber_long = c_fkber_long

000390 c_grant_nbr = c_grant_nbr

000400 c_measure = c_measure.

000410 endfunction.

thanks

Deepa

[iklovski · Accepted solution]

Hi,

Implement notes 689885 and 918477 to solve this issue.

Regards,

Eli