Best Of
Re: Issues Using Type Ahead/Smart Prompt - Is there a Bug Related to Type Ahead/Smart Prompt on 8.62?
I can replicate in PUM56 tools 8.62.13 The key, I believe, is to have Autocomplete DISABLED and Smart Prompt ENABLED. It seems to me there are also other issues with Smart Prompt, but if you have both Autocomplete and Smart Prompt disabled or enabled, this issue does not occur. You have to have the Smart Prompt show values, which isn't always happening, for the issue to occur too.
Re: ips local repo create
Your approach is broadly correct, but use one repository service instance and the same port throughout.
Also verify the downloaded repository content covers your installed SRU 71.
Download all repository ZIP parts for the required release, plus its Repository Installation Guide containing the script, README and digests.
For a repository supporting SRU 71, include the Solaris 11.4 GA content and the installed SRU 71 content.
If you plan an upgrade, also include the target SRU content.
Follow the download README’s assembly requirements; GA content alone does not provide SRU 71.
See minimum repository content: (https://docs.oracle.com/cd/E37838_01/html/E60982/repobestpractice.html).
Run these commands as root, assuming the datasets do not already exist and sufficient space is available:
zfs create -o mountpoint=/export/repoSolaris11 -o atime=off rpool/export/repoSolaris11
zfs create -o mountpoint=/export/iso rpool/export/iso
mkdir -p /export/iso/GA /export/iso/SRU71
Keep each release’s ZIP parts, installation script and matching digest file together in its own download directory.
Assemble GA first, then add SRU 71 to the same repository:
cd /export/iso/GAchmod +x install-repo.ksh./install-repo.ksh -d /export/repoSolaris11 -c -v
cd /export/iso/SRU71chmod +x install-repo.ksh./install-repo.ksh -d /export/repoSolaris11 -c -v
pkgrepo info -s /export/repoSolaris11pkgrepo list -s /export/repoSolaris11 entirepkg list -Hv entire
The -c option checks download digests; -v verifies the assembled repository. Confirm the repository lists the exact installed entire version.
Your original sequence mixes the named solaris instance with the default instance, and ports 80 and 8081.
Use the named instance consistently. The following assumes solaris does not already exist and port 8081 is available:
svccfg -s application/pkg/server add solaris
svccfg -s application/pkg/server:solaris setprop pkg/inst_root=/export/repoSolaris11
svccfg -s application/pkg/server:solaris setprop pkg/readonly=true
svccfg -s application/pkg/server:solaris setprop pkg/port=8081
svcadm refresh application/pkg/server:solarissvcadm enable application/pkg/server:solaris
svcs application/pkg/server:solarispkgrepo list -s http://localhost:8081/ entire
If the instance is not online, check:
svcs -xvL application/pkg/server:solaris
After repository verification succeeds:
pkg set-publisher -g http://localhost:8081/ solarispkg publisher solaris
This adds an origin; it does not remove existing origins.
For other servers, replace localhost with the repository server’s reachable hostname or IP address.
Hope that helps.
Re: ilom password is unknown
Powering on the T8-2 may boot Solaris, but it does not bypass the ILOM login or automatically give you access to the Solaris console.
The SER MGT port connects to ILOM. To open the host console, first authenticate to ILOM, then run:
start /HOST/console
You can then see Solaris console output and its login prompt if Solaris boots successfully.
See Oracle’s T8 console procedure: (https://docs.oracle.com/cd/E79179_01/html/E82092/z40001381388942.html).
If Solaris starts and its network is available, you may log in directly through Solaris SSH using valid Solaris credentials. That provides OS access but does not recover ILOM access.
For console access, recover the ILOM account using the documented physical-presence procedure.
ILOM operates while AC power is connected, independently of whether the host is powered on.
A host reboot or factory reset is not required for password recovery.
See T8 user accounts: (https://docs.oracle.com/cd/E79179_01/html/E82092/grvdn.html) and ILOM operation (https://docs.oracle.com/cd/E79179_01/html/E82092/z40001381388892.html).
Before powering on an evacuated server, confirm its saved configuration will not start guests already running on the other server.
Hope that helps.
Re: JN21831
Hello,
Your assertion is correct, JN21831 is for 2026 and is available on the update center for download
Thanks
FrankD
Re: Seperate early october pre-1099 patch
Thanks Alicia, also patch 40092406 is release now, any idea when is the next patch for 1099 is going to be released approximately sometime in early november like last year
Re: Does anyone have a workaround for Bug 40068664?
Hello David,
Greetings!
Our Campus Solutions Development team is actively working on this issue with high priority and is currently preparing a PeopleSoft Release Patch (PRP) to address the reported compilation error.
Please log a Service Request (SR) with Oracle Support to receive regular updates on the progress and availability of the patch.
We will share the patch details as soon as they become available.
Thank you for your patience and understanding.
Thanks & Regards,
Akhilesh
Re: How can we prevent the overwriting of Rec and revenue account in distributions for AR Transaction
Hi
If Transaction is Incomplete, user can override the accounts.
You can do a Forms Personalization to stop users from changing the accounts.
Best Regards,
Bharat
Re: Advisor Webcast: JDE E1 - Changing Date Patterns in General Accounting & Fixed Assets - 24-Mar-2021
Questions and Answers from the live webcast and listed below:
Q:Can an old batch still be posted if it was not posted before the process?
A: If the batch has the Fiscal Year and Period Number as per the old date pattern an error will occur: Invalid Period Number and/or Fiscal Year
Running R099103 will realign the GL part of the batch so the batch may post. You will need to verify the re-aligned period is open and may need to run the repost and annual close reports and other verifications may also be required (e.g. if this was a Fixed Assets batch for a FY for which the F1202 records were deleted)
Q: Are there any reports to re-align Period Numbers in other modules?
A: No. R099103 is designed to re-align F0911 only and there is no similar UBE or process for Account Payable or Account Receivable and so on.
Q: Can the Date Pattern in R12851 be used instead of this process?
A: There is a functionality in Life Year Rules (R12851) that allows User Defined Depreciation (R12855) to calculate depreciation based on a different Date Pattern.
When considering this functionality, make sure to review how the data is entered in F0911 and F1202 and its limitations (e.g. for running R12910).
Q: What is the best approach in targeting the change all the following at the same time
- Fiscal Year start/end;
- Fiscal Year Structure (from 13 period to 12 periods in 5-4-4 format)).
No duplicate years as short Fiscal Year is to be introduced.
How does this impact depreciation (straight line spread equally over the period of the asset life)? What are the options to ensure assets do not fully depreciate too soon / too late?
A: A short year should not be used for Fixed Assets. New Date Patterns must be set up back to the oldest Asset’s start depreciation date.
If the Normal Number Of Periods is also changed, review the Asset's Life Months.
Q:What is the impact on Enhanced Estate Management Module? Payment Profile & Accounting Profile would've been prepopulated already based on the original date pattern. Any gotchas there?
A: The webcast only addresses General Accounting and Fixed Assets. All other systems should be reviewed before making the change. For more information on each system, issues need to be discussed in the corresponding Community / Support group
Q: If you have 40 companies, can you change the date pattern for just one company?
A: Yes. If other companies are going to remain on the old Date Pattern, new Date Patterns (including short year if required) should be created for the Company that is changing the Date Pattern, making sure to leave the Date Patterns of the other Companies untouched.
Q: If we have a no duplicate year change where new fiscal year start is Jan 1 2021 but we have already posted data into periods in 2021 (i.e real January, etc).
Depreciation is run in Summary mode so no F0911 records.
What would you recommend for redoing the Depreciation for those months in 2021? Would we need to void the GL batches?
A: In Fixed Assets, when changing Date Patterns, User Defined Depreciation (R12855) should not be run past the time period of the close on the old date.
If business wants to void the G/L batches, this may not solve the issue completely as it will not affect Fixed Assets if depreciation was run in Summary mode.
If the Accumulated Depreciation and Depreciation Expense accounts have only been modified by depreciation batches then you may consider clearing the F1202 postings using SQL along with voiding the depreciation batch.
This solution should be thoroughly tested in a Test Environment before applying to Production.
Q: What is the recommendation for those other tables (i.e. F0411, F03B11, F4311, etc.)? SQL update?
Do you recommend that they be updated to ensure data integrity?
There is no standard requirement to update F0411, F03B11, etc. However, each process should be reviewed and if such a need exists, then SQL is the option for updating these tables as there is no standard UBE (like R099103 for F0911).
Make sure to test thoroughly before applying to Production.
Q: If the new date pattern includes a short year which has already past.
For instance June 1, 2020 through December 31, 2020. Will fixed assets have an issue when running Depreciation in January 2021 and later?
Assume 12 periods on old and new pattern - went from Fiscal to Calendar.
A: If the new Date Pattern includes a Short Year, User Defined Depreciation (R12855) may not calculate depreciation as expected since for each year it will calculate using the Normal Number of Periods (CALD) from Company Names & Numbers (P0010).