Issues Applying BSP 8.0.2.0.2 Patch 23590264 (Doc ID 2173845.1)

Last updated on OCTOBER 20, 2016

Applies to:

Oracle Financial Services Balance Sheet Planning - Version 8.0.2.0.2 and later
Information in this document applies to any platform.

Goal

Question 1: While applying Oracle Financial Services Balance Sheet Planning (BSP) 8.0.2.0.2 <Patch 23590264>, the following message appeared when executing "dm_bsp_procs_funcs_custom2.sql" script in Step 10.  The following warnings against all BSP initialized schemas.

SP2-0806: Function created with compilation warnings
SP2-0806: Function created with compilation warnings
SP2-0806: Function created with compilation warnings
SP2-0806: Function created with compilation warnings
SP2-0806: Function created with compilation warnings
SP2-0804: Procedure created with compilation warnings
SP2-0804: Procedure created with compilation warnings
SP2-0804: Procedure created with compilation warnings
SP2-0804: Procedure created with compilation warnings
SP2-0804: Procedure created with compilation warnings
SP2-0804: Procedure created with compilation warnings
SP2-0804: Procedure created with compilation warnings

Show errors give additional details:

SQL> show errors;
Errors for PROCEDURE PR_BSP_POPULATE_PRICING_MARGIN:

Invalid Objects
LINE/COL ERROR
437/2 PLW-07206: analysis suggests that the assignment to 'LV_STAGE_CD' may be unnecessary
482/13 PLW-07202: bind type would result in conversion away from column type
482/31 PLW-07202: bind type would result in conversion away from column type
490/13 PLW-07202: bind type would result in conversion away from column type
490/31 PLW-07202: bind type would result in conversion away from column type
500/7 PLW-06009: procedure "PR_BSP_POPULATE_PRICING_MARGIN" OTHERS hand ler does not end in RAISE or RAISE_APPLICATION_ERROR
591/40 PLW-07202: bind type would result in conversion away from column type
591/52 PLW-07202: bind type would result in conversion away from column type
591/65 PLW-07202: bind type would result in conversion away from column type
591/74 PLW-07202: bind type would result in conversion away from column type
782/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
784/45 PLW-07204: conversion away from column type may result in sub-opt imal query plan
786/42 PLW-07204: conversion away from column type may result in sub-opt imal query plan
787/43 PLW-07204: conversion away from column type may result in sub-opt imal query plan
798/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
800/45 PLW-07204: conversion away from column type may result in sub-opt imal query plan
802/42 PLW-07204: conversion away from column type may result in sub-opt imal query plan
803/43 PLW-07204: conversion away from column type may result in sub-opt imal query plan
817/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
829/51 PLW-07204: conversion away from column type may result in sub-opt imal query plan
849/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
869/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
942/41 PLW-07204: conversion away from column type may result in sub-opt imal query plan
951/41 PLW-07204: conversion away from column type may result in sub-opt imal query plan
966/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
978/51 PLW-07204: conversion away from column type may result in sub-opt imal query plan
998/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
1018/48 PLW-07204: conversion away from column type may result in sub-opt imal query plan
1100/9 PLW-06009: procedure "PR_BSP_POPULATE_PRICING_MARGIN" OTHERS hand ler does not end in RAISE or RAISE_APPLICATION_ERROR
1132/7 PLW-06009: procedure "PR_BSP_POPULATE_PRICING_MARGIN" OTHERS hand ler does not end in RAISE or RAISE_APPLICATION_ERROR

Can the above be ignored?
 
Question 2: Custom financial element (FE)s were deleted when applying 8.0.2.0.2 patch in Step 13:

It seems that this is the step that causes this issue:
==============================================
Step 13. Pre-requisites:: please execute step 12(vii) if you haven't executed yet. Once you have executed 12(vii), please follow the below steps based on the bsp application type (Std,C1 and C2)
(a) If BSP Initialized language is "English", then do the below steps,

(i) Copy " $EPM_ORACLE_HOME/bsp/bsplcm/BSP_Account.xml" file To "$MIDDLEWARE_HOME/user_projects/epmsystem1/import_export//HP-/resource/Global
Artifacts/Common Dimensions/Standard Dimensions" and after copying BSP_Account.xml, rename it to Account.xml. Please delete existing Account.csv from the same folder before renaming BSP_Account.xml.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms