Best Of
Re: Advisor Webcast for Applications Unlimited: Enabling Modernization with Artificial Intelligence
Was there an answer to @Matheshwaran V - PeopleSoft Delivery Architect question above? We run Peoplesoft onprem.
Re: Error while approving Journal
Does the multiledger responsibility have access to the ledger that the journal notification is for? If not, then something is defaulting to that responsibility (as opposed to choosing the responsibility for you based on the access it has).
Re: Error while approving Journal
Hi,
The reported issue might be reproduced via below steps:
- User selects a notification (Belongs to Ledger A).
- Click on link "Enter/Review Journals".
- User gets an option of selecting a responsibility.
- User selects "Responsibility 1"
- Journal Opens in Oracle Forms.
- User then navigates to open another notification which Belongs to Ledger B
- Click on link "Enter/Review Journals"
- Pick a responsibility 2 ;
However the system tries to use the responsibility1 from cache to open the Journal using Responsibility 1
and gives error message: "APP-FND-01347: You no longer have access to the specific information requested in this screen."
In this case, use a responsibility that has access to a single Ledger when you click on the Workflow Notification for the Journal Batch Approval.
Or
Enable Internet Explorer Options “Delete Browsing History On Delete”
Logout and login back.
Regards,
Phanendra.
Re: DrillDown query result is not as displayed on DrillDown web page
Hi,
This query is of the SLA table data.. as the issue is specific to a specific source I would suggest engaging the Cost Management community to see why the query does not return the data your expecting. It could be some security or profile setting that is set specific to that application.
Thank you,
Greg
Re: WEBADI document creation issue
Hi, Thanks for sharing the screenshot.
Please follow steps from below note and see if issue is getting resolved here.
Web Applications Desktop Integrator - Download Of WebADI Document Is Stuck Or Hangs At 'Do not close this window until processing completes' (Doc ID 752760.1)
Thank you !!
Re: Full Package increase the Tablespace
Hello @2011
So you see an increase in tablespace utilization. May Iask what tablespace?
Also you could look in package build kernel log if you see anything like this:
OCI0000179 - Error - ORA-01653: unable to extend table <tablespace>.<table_name> by <x> in tablespace <tablespace>
If this error is encountered, set the tablespace to autoextend.
But a general rule I would go through so you have autoextend turned on, to not encounter any issues if you have an Oracle Database. Your DBA would be able to identify tablespaces that is running out of space to make sure autoextend is on and you dont need to drop anything.
Sincere regards
Johan
Re: Full Package increase the Tablespace
Hi
The following documents can help in archiving and purging to reduce tablespace . It also has information on freeing up disk space as well
E1: ENV: Archive and Purging within JD Edwards EnterpriseOne (Doc ID 1082128.1) E1: ENV: OS: How To Housekeep JDE Objects For More Free Disk Space? (Doc ID 1345177.1)
Regards,
Prabhu
Re: why redo and undo logs are required during flashback of database? aren't flashback logs enough?
Hi,
In Oracle, Flashback Database relies primarily on flashback logs, but redo logs and undo are still required because flashback is not a standalone mechanism—it integrates with Oracle's recovery and transaction management architecture.
Flashback Database = Flashback Logs (physical rewind) + Redo (roll forward committed changes) + Undo (rollback uncommitted transactions). Flashback logs alone can restore block versions.Redo and undo ensure logical consistency at the target point-in-time.
Without redo/undo:
Database would be physically correct at SCN but transactionally inconsistent.
You could end up with partially applied or uncommitted transactions.
Thanks,
Mahesh
Re: why redo and undo logs are required during flashback of database? aren't flashback logs enough?
Physically correct → The database files and blocks are not corrupted; they look like they existed at that SCN.
Transactionally inconsistent → Some transactions were only partially done or uncommitted, so the data does not reflect a clean, committed state.
Thanks,
Mahesh
Re: Full package build is failing after Deployment server OS upgrade to 2022
Thank you JohanR for your recommendations. I have just put this value in registry. Restarted the Server. Submitting a full build now to see how it goes. Will keep you updated.
On Windows the key registry DWORD:
HKLM\SYSTEM\CurrentControlSet\Services\TcpIp\Parameters\KeepAliveTime = 900000
Default is 7200000
Thanks
Jitendra


