Skip to Content
0
Former Member
Jul 28, 2008 at 07:28 PM

MSS: Approve working time Program " " not found error

17 Views

Hi,

I am able to enter working time and release in ESS. CAT2, CAT4 and CAT6 are also working fine. Im using the Approve Time sheet data iView in MSS to approve working time. Im not sure if I did all the required configuration in IMG Approve working time.But when I click the iView I get a Java exception as shown below. Pl find the ST22 dump also. Can you please let me know

1. What could be the problem.

2.What are minimum configuration to be done in IMG Approve working time.

com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Program not found., error key: RFC_ERROR_SYSTEM_FAILURE

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)

at com.sap.xss.hr.cat.approve.blc.FcCatApprove.rfcExecute(FcCatApprove.java:307)

at com.sap.xss.hr.cat.approve.blc.FcCatApprove.init(FcCatApprove.java:276)

at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApprove.init(InternalFcCatApprove.java:200)

at com.sap.xss.hr.cat.approve.blc.FcCatApproveInterface.onInit(FcCatApproveInterface.java:136)

at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApproveInterface.onInit(InternalFcCatApproveInterface.java:133)

at com.sap.xss.hr.cat.approve.blc.wdp.InternalFcCatApproveInterface$External.onInit(InternalFcCatApproveInterface.java:313)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)

at com.sap.xss.hr.cat.approve.vac.dd.VcCatApproveDrillDownList.onInit(VcCatApproveDrillDownList.java:

ST22 dump

-


Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not

caught in

procedure "BUILD_TABLE_STRUCTURE" "(METHOD)", nor was it propagated by a

RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

On account of a branch in the program

(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)

or a transaction call, another ABAP/4 program

is to be loaded, namely " ".

However, program " " does not exist in the library.

Possible reasons:

a) Wrong program name specified in an external PERFORM or

SUBMIT or, when defining a new transaction, a new

dialog module or a new function module.

b) Transport error

Regards

Srini