Best Of
Re: oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key
Hello,
The message indicates that two or more objects have the same unique identifier (primary key is the unique identifier). So the unique identifier is not unique any more and Oracle doesn't know which to use. The solution is to rename the objects until each has its own distinct name.
In your case, it seems that the unique identifier is 20003, UPL_PARAM_500226, US
If 20003 is the application id, then these are likely custom objects, perhaps someone made a copy and saved it with the same identifier as the original. You may be able to find them and rename them so they are all unique. If these are standard objects, you should log an SR and ask Oracle to help fix duplicated standard objects.
Regards,
J
Re: When can we expect a patch for Ireland on the Auto-Enrolment Retirement Savings Scheme
Hi Mariana,
Any updates on this one?
Regards,
Bernard
Re: When can we expect a patch for Ireland on the Auto-Enrolment Retirement Savings Scheme
Hi Mariana ,
Is there any update on the Patch above ?
Thanks & Regards
Srihari.
Re: PeopleSoft error - File: E:\PT858P19B_2203300501-retail\peopletools\src\pssys\msgget.cppSQL error.
Hello Mandla,
Please add this variable in your psprcs.cfg file in the given section:-
[Database Options]
OracleUseLobLocators=0
Using PSADMIN, reconfigure process scheduler server.
Clean CACHE & IPC resources.
Retest your issue.
This Table is having Long field and if field into which this is copied is not Long then problem has been reported in the past.
Thanks,
Akash
Re: AWE - how to Pushback the transaction to originator for making changes. how to do this?
Hi - Refer below document.
E-AWE: How Would Pushback Functionality Work On First Approval in Approval Chain (Doc ID 1575795.1)
Excerpt from document…
No, it is not possible for current Approver to Pushback the Voucher to the original Approver. In the scenario described, the Step is still the first Step in the Approval Process, so there is no where to Push Back the transaction. Had the Approval process been further along, assigned to next Approver, Pushback may have been feasible.
The only way to reassign back to original Approver is via the Monitor Approvals page, logged in as the User with the Admin Role on the VoucherApproval Process Definition.
This works as designed.
-Velu
Re: Rename the field conditionally
Hi NadeemAlhamdan,
Please use Page and Field Configurator provides the flexibility to configure fields and pages, in any component, without having to customize delivered application pages or fields.
Thanks,
Bhuvana
Re: G40R : demand scheduling execution in 9.2
Dear User_31RO3,
I actually split your follow up question into a new thread:
I provided the following answer to your question:
The R47171 knows to process firm or planned demand based on the setup in the P40R21 (Demand Cross Reference). The customer will send in demand type/period in the F47173 data, which is cross referenced with the setup in the P40R21. We change the demand type/period to values that are used in E1 for the R40R010 to determine if a sales order (firm) should be created or a forecast (planned) would be created.
Thank you,
Michael
