Best Of
Re: Created an OBS but it isn't showing up in my EPS. What am I doing incorrectly?
In the EPS I added Pipe Fabrication. I was in the Projects node when I did this. I added the responsible manager as pipe fabrication. It added it under the Projects node as a child. I need pipe fabrication to be independent of the other business units but I don't have the option to move Pipe Fab out of the Projects node to be it's own independent node. Pipe Fabrication is a different business unit just like the EP projects node, Module Shop node and the Middle East node.
How do I move the Pipe Fabrication to the left? This is what I did to begin with and I wasn't able to move it over to be it's own node. Then I Googled it and it sounded like I needed to create an OBS so I did. I can see that EP Projects, Module Shop, Resource Forecast Files & Shaw Middle East are all independent, so how do I make Pipe Fabrication independent?
Re: Travel & Expenses - New expense type created, mapping updated, getting as Invalid Exp Type error .
Hi Pere Taule,
Thank you for checking and providing suggestions, changing the effective date as mentioned resolved the issue.
Re: Created an OBS but it isn't showing up in my EPS. What am I doing incorrectly?
In the EPS screen the Pipe Fabrication is not showing up to add a responsible manager to. Is there another place to do this? Pipe Fabrication should be showing up above the Shaw Middle East OBS
I have added the users assigned in the cloud portal.
Re: EBS 12.2 - VA Change to Withholding Tables for Wages Paid after July 1, 2025
Thanks again. I will forward this information to our tech team. Dawn
Re: Can I run the post-install script once for multiple installations of Oracle database patches?
Hi All,
Thank you so much for your answers and comments. My Oracle database patching tasks have been successfully completed on time.
Best Regards
Re: Budget Calendar issue.
Hi,
You can use the 'Amount Type and Boundary' feature of budgets. Refer the user manual, below is an example;
Example 1
You operate under a yearly calendar (Jan-Dec) using monthly periods. You do not want to exceed the total budget for the quarter,
but you do not care if any individual month's budget within the quarter is exceeded. You choose the budgetary control options QTD (Amount Type) and Quarter (Boundary).
You enter a second-quarter transaction for May-93.
The system checks the transaction against the funds available balance as of June-93, the end of the second quarter.
Note: In this example, any available funds from the first quarter of the year would not be available for spending in the second quarter (April-93-May-93-June-93).
You can transfer available funds by creating a budget journal entry transferring budget amounts to the second quarter.
See also:
Budgets and Budgetary Control - Setup and Usage (Doc ID 1928941.1)
Error12 During Funds Checking or Posting. Effects Of Different Amount Types And Boundary Combinations In The Budgetary Control Setup. (Doc ID 1013440.102)
SCENARIO 3 (Amount Type = QTD; Boundary = Quarter)
You operate under a fiscal year calendar (Oct-Sep) using monthly periods. You choose the budgetary control options QTD (Amount Type) and Quarter (Boundary). You enter a transaction for Feb-99. The system checks the transaction against the quarter-to-date funds available balance as of Mar-99. Since you chose a quarter-to-date amount type, you have access to available funds from the beginning of the quarter (Jan-99) through the boundary quarter (Mar-99).
Note: In this Scenario, any available funds from the first quarter of the year would not be available for spending in the second quarter. You can transfer available funds by creating a budget journal entry transferring budget amounts to the second quarter.
Thanks and regards,
Anca
Travel & Expenses - New expense type created, mapping updated, getting as Invalid Exp Type error .
Peoplesoft 9.2
We have created new expense type, expense mapping has been updated with new expense type, when we process credit card files ending up in error stating "Invalid Expense Type. We have verified the set up, effective date, merchant category code all seems to be fine, reloaded the files still getting same error. Did anyone faced this kind of issue, is there a way to get rid of this?
1095C Statement in Self Service - Masked SSNs
The print pdf version of the 1095C statement allows us to truncate/mask SSNs to only show the last 4 digits of the employee/covered dependents' social security number, but the electronic copy of the 1095C statement in the Employee Self Service menu in Oracle EBS 12.2.10 - Advanced Benefits does not. Is there a way to mask the SSNs without customizing the page? Or, even if there was a way to expose the pdf template on this page instead, then we can easily use our customized template - but I don't see that option either. Is anyone else experiencing these issues and if so, if you could share ideas how you're working around them, I'd appreciate it.
Thanks,
Misty
Re: adding different sized disks to an existing disk group (normal redundancy) on an Oracle 19c cluster
You will need to perform the operation via SQL*Plus using the ALTER DISKGROUP command. This error is caused by an intentional Oracle ASM validation check that enforces uniform disk sizes within an existing normal redundancy disk group where all current members are equally sized. The solution is to explicitly instruct ASM to use only a portion of the new disks that matches the size of the existing 4TB disks by adding the SIZE clause to your command. You must specify a size that precisely matches the TOTAL_MB of your current disks (e.g., SIZE 4096G), which will effectively make the new disks appear as 4TB to ASM, thus satisfying the requirement for uniformity. For proper redundancy, it is also critical to add each new disk into its own new failgroup. This specific operation bypasses the ASMCA GUI limitation and allows the disk group to be extended successfully.
FYI: Based on the error message and your description, the issue stems from a specific feature introduced in Oracle ASM version 12.1.0.2. This feature enforces a check that prevents the addition of disks of a different size to a normal or high redundancy disk group if all the existing disks in that group are of an equal size.
