Join us for a fun and relaxing happy hour at the annual My Oracle Support Monday Mix. This year's gathering is Monday, October 26 from 6:00 to 8:00 p.m. at a new location—Fang Restaurant—a half-block from Moscone Center on Howard Street.
After a busy day at Oracle OpenWorld, take a break and unwind with your peers. Stop by and get to know the Oracle Support Engineers you depend on, as well as key Oracle Support executives and developers over drinks and hors d'oeuvres at Fang—a family owned restaurant known for its exciting and seasonal fare.
Admission is free for Premier Support customers with your Oracle OpenWorld badge.
Have you struggled for a solution to error message 0027 - User Defined Code Error? If so, you're not alone. Customers often log service requests and perform searches to understand and troubleshoot this error.
The challenge with the 0027 - User Defined Code Error which states: “The entered code was not found in the User Defined Codes” is that the Item/Account Number (UITM) or Description (DSC1) field is highlighted and neither field is associated to a user defined code (UDC). Due to this you do not know which UDC is in need of correction.
Troubleshooting Voucher Match (P4314) (Doc ID 1531063.1) provides help with this issue. Section D. Error 0027: User Defined Code Error explains that this issue is new to the A9.2C1 release, and occurs when one of the address book category codes assigned to the supplier is not valid. Document 1531063.1 provides step by step instructions on how to identify and update the UDC table in error so the error is no longer given. The document also contains information about a list of UDC tables that do not contain blank as a valid value. Adding the “blank” value to these tables may also help correct the 0027 error issue from occurring in the future.
Ask Questions, Attend a 10-minute Briefing, Get Entered for Prizes
Visit us October 26–28 in the Moscone West Exhibition Hall, booth 3361 for answers to your toughest support questions. Senior support engineers will be on hand spanning all major Oracle product areas, from systems and database products to middleware, applications, and Oracle Cloud.
While there, take advantage of our 10-minute mini-briefings for tips on maintaining, supporting, and upgrading Oracle products. All mini-briefing attendees are entered to win on-the-spot prizes.
More than 500 experts from across Support Services will be on hand at Oracle OpenWorld from October 25–29 to share tips and tools for adopting and optimizing Oracle technology.
Take advantage of 50+ sessions to gain valuable insights into getting the most out of your hardware and software. Learn best practices and customer examples from Oracle Consulting, and develop sharper strategies that drive innovation and create value to meet today's changing business requirements.
It is fall and most of us are dreaming of that steamy pumpkin pie and apple cider. It is also toward the end of the calendar year so it is time to clean up payroll data for end of year. This process is similar to deep cleaning your house. We all know that if we pick things up daily, then when the deep cleaning time occurs, there is less work to be done. The same is true with cleaning payroll data prior to the end of the year. This way, when you are ready to process your year end for your employees, the data will be squeaky clean.
Why would your payroll data need cleaning? There are many reasons that your data might be out of sync:
You might have made an adjustment to a certain employee records and now the summary/detail files are no longer the same.
You might have acquired a new company and processed payroll prior to receiving the corporate tax ID. Now you have history records with blank/incorrect tax ID and one with the correct tax ID.
The infamous power outage right in the middle of your final update of your payroll might have caused the out of sync in some of the history files.
You created a manual check and you overrode the taxes but the gross wages didn’t come across to history the way you wanted. Just to list a few.
How can you find out if your data need cleaning?
There are a few integrity reports you can run to identify the errors for your data.
For U.S. payroll, access the Data Integrity & Global Updates located on menu G0731. Create and run both of these integrity reports: Taxation History F06136 (067011) and Payroll Month PDBAs F06146 (067021).
For Canadian payroll, access the Data Integrity & Global Updates located on menu G7731. Create and run both of these versions: Taxation History F0713 (J077011) and Payroll Month PDBAs F06146 (J077021). Additionally, Canadian payroll also has an EI (Employment Insurance) integrity report that you can run on menu G77311.
These integrity reports will provide you with a list of errors if any discrepancies are found. If no errors are produced, then your data are clean. If you need to know what each of the errors means or how to correct the errors, please see Payroll Tax History Integrity Report (Doc ID 645601.1) for more detail.