Server Error - When Upgraded to SP3 in SPM 3.0

[Former Member]

Hi All,

We upgraded our SPM 3.0 to SP3 and since than we are unable to launch the potral. We are getting Server error. On the Java end there is a strange log related to Fiscal variant ( Below is the exact log ). The master Query 0ASA_MP01_Q1002 works fine in BEX analyzer.

Any help would be greatly appreciated.

1. com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent

WARNING RSUOM (069): Target quantity not found

WARNING RSUOM (065): No quantity conversion possible

ERROR FGV (002): Fiscal year variant WK is not maintained for calendar year 2006

  MSGV1: WK

  MSGV2: 2006

ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

#2.0^H#2013 10 04 18:03:11:713#0-100#Error#com.sap.poa.sbc.bui.bi#

#XAP-SBC-BUI-JAV#sap.com/poa~sbc~bui~server~adapter~nw~eap#C0000A01399400C70000001D00002B80#368865850000000004#sap.com/xapps~analytics~opm~eap#com.sap.poa.sbc.bui.bi#MBPATIL#19##115289BF2D2711E39320000015FC723A#c716aee82b9f11e39ef7000015fc723a#c716aee82b9f11e39ef7000015fc723a#0#Thread[HTTP Worker [@426958117],5,Dedicated_Application_Thread]#Plain##

Termination message sent

WARNING RSUOM (069): Target quantity not found

WARNING RSUOM (065): No quantity conversion possible

ERROR FGV (002): Fiscal year variant WK is not maintained for calendar year 2006

  MSGV1: WK

  MSGV2: 2006

ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION#

[Former Member]

Hi Manjunath,

We are experiencing similar problem.  Did your problem get fixed? Our error message is as follows:

WARNING RSUOM (069): Target quantity not found

WARNING RSUOM (065): No quantity conversion possible

ERROR FGV (002): Fiscal year variant Z1 is not maintained for calendar year 2099

  MSGV1: Z1

  MSGV2: 2099

ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

Thanks,

Mani Chinnaiah

[Former Member]

Hi Mani,

Yeah we were able to fix this issue, its simple but took a lot of effort to figure out what was going wrong.

The solution is

Go to transaction RSRHIERARCHYVIRT

Go to Virtual Time Hierarchies.

Look for fiscal year Z1. It would have been turned on. Turn it off and try running SPM. It works for sure.

Please let me know if you need more details.

Thanks

Manjunath

[Former Member]

Hi Patil,

1. Please make sure that both ABAP and JAVA stacks are upgraded as per the SAP Note 1882819.     Choose one of the alternatives and make sure all the component's version are as per the note.

2. Also, the User logging in SPM UI should also have BEx Web Analyzer access and should be able     to execute the query - 0ASA_MP01_Q1002 in portal.

3. Make sure UOM master data is loaded.

4, If your source system is ECC, make sure the Date properties - yyyymmdd for all the Objects while loading Transactional data through SPM UI - data manager

Let me know if this helps.

Thanks,

AG

[bidisha_tripathi]

can you delete the precalc cache from backend and the browser cache also

function module to be used is OPM_DM_PRECALC_DELETE, OPM_DM_PRECALC_CLEAR, OPM_DM_PRECALC_ENDCLEAR and check the uppercase/lowercase checkbox.

reactivate the query.

check the UOM dso has all the units and corrosponding material.

check fiscal year for 2006 as the error says you have data for 2006 and fincal variant WK from ECC and you may not have defined WK in your bw system(check this in  SPRO customizing)

Hope this will help.Else raise issue with SAP.

Regards,

bidisha