Scribd
Upload
444 views3 pages

Open Period Balances

The document describes an issue where the XLABAOPE module for open period balances was failing with an ORA-06550 error when run by the SYSADMIN user. The cause was that this module should not be run from the SYSADMIN responsibility. The solution is to disable the subscription for the open period business event for SYSADMIN and recreate two Oracle packages to resolve the issue. After applying the solution, requests to open period balances would no longer be run by SYSADMIN.

Uploaded by

Yadev Bascor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
444 views3 pages

Open Period Balances

The document describes an issue where the XLABAOPE module for open period balances was failing with an ORA-06550 error when run by the SYSADMIN user. The cause was that this module should not be run from the SYSADMIN responsibility. The solution is to disable the subscription for the open period business event for SYSADMIN and recreate two Oracle packages to resolve the issue. After applying the solution, requests to open period balances would no longer be run by SYSADMIN.

Uploaded by

Yadev Bascor
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

XLABAOPE Open Period Balances Error ORA06550 in FDPSTP when requestor was

SYSADMIN (Doc ID 1616495.1)

To
Bottom

In this Document
Symptoms
Cause
Solution

APPLIES TO:
Oracle Cost Management - Version 12.1.3 and later
Information in this document applies to any platform.

SYMPTOMS
On : 12.1.3 version, Subledger Accounting
When attempting to execute XLABAOPE module: Open Period Balances
under responsibility / requestor SYSADMIN,
the following error occurs:
ERROR
----------------------ORACLE error 6550 in FDPSTP
Cause: FDPSTP failed due to ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to
'OPEN_PERIOD_SRS'

STEPS

----------------------The issue can be reproduced at will with the following steps:


1. User opened a specific month period
2. Noticed that the XLABAOPE module: Open Period Balances was being
launched thru requestor SYSADMIN.
3. The concurrent request failed with error.

CAUSE
This program XLABAOPE should not be submitted from SYSADMIN
responsibility. This
program should be either submitted from GL responsibility or any other
Subledger responsibilities (like Payables, Receivables etc). So suggest
customer to remove this concurrent program from the request group of
SYSADMIN
responsibility.
This issue was described in:
BUG 11056002 - AFTER UPGRADING FROM R12.1.2 TO R12.1.3
CONCURRENT PROGRAM OPEN PERIOD BALANCES
.

SOLUTION
To Implement the solution, please see the following details:
1. Search for business event "oracle.apps.gl.CloseProcess.period.open"
2, Click on Subscription icon for this business event.
3, Check whether the subscription status is "Disabled".
If the status is not disabled update the subscription and set the status to
Disabled.
4. Execute the following commands to recreate the package at the SQL
prompt.
a. SQL> @xlabacom.pkh
b. SQL> @xlabacom.pkb
To verify the solution:
- Tried to open a new period in GL.
- Navigate to System Admin responsibility > View all requests> checked
specific requests and looked for all requests that start with Open%Period%
.
Now , you do not see the Open period Balances request run by requestor
SYSADMIN

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy