NoetixViews for Oracle Payables - Noetix Technical Support
NoetixViews for Oracle Payables - Noetix Technical Support
NoetixViews for Oracle Payables - Noetix Technical Support
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
PAY_Accruals does not support DML statements in <strong>for</strong>mulas.<br />
To show correct results <strong>for</strong> accrual plans, the PAY_Accruals view uses <strong>Oracle</strong> Payroll <strong>for</strong>mulas<br />
that have been defined <strong>for</strong> each benefit accrual plan. Users can customize these <strong>for</strong>mulas<br />
according to business needs. However, if customization involves the use of Data Manipulation<br />
Language (DML) statements (such as inserts, updates, or deletes), the view will malfunction. The<br />
PAY_Accruals view is designed to use only <strong>for</strong>mulas without DML statements.<br />
For a solution, consider not altering the <strong>for</strong>mulas and instead relocating DML statements<br />
elsewhere. Otherwise, contact <strong>Noetix</strong> <strong>Technical</strong> <strong>Support</strong> to request a quote <strong>for</strong> a billable<br />
customization that alters the <strong>Noetix</strong> Payroll Data Mart and the PAY_Accruals view <strong>for</strong> support of<br />
customized <strong>for</strong>mulas.<br />
[13879]<br />
XOP <strong>for</strong>m of RA_Customers returns multiple records.<br />
The XOP <strong>for</strong>m of the RA_Customers view returns a record <strong>for</strong> each active, primary bill-to address<br />
defined <strong>for</strong> a customer in an operating unit. This known issue also occurs if the XOP <strong>for</strong>m of this<br />
view is joined to the XOP <strong>for</strong>m of other views. For a workaround to this problem in XOP views,<br />
use the Operating_Unit_Name column as a <strong>for</strong>eign key in the query that joins the XOP <strong>for</strong>m of<br />
the views.<br />
[19627]<br />
EAM_WO_Cost_Details returns incorrect data.<br />
If a resource is associated with an operation sequence multiple times through different resource<br />
sequence numbers, the view returns incorrect data. This issue will be fixed in a future release.<br />
[23394]<br />
<strong>Oracle</strong> Database 9.2.x causes errors in views <strong>for</strong> Human Resources.<br />
On <strong>Oracle</strong> Database versions 9.2.0.3 and 9.2.0.4, views <strong>for</strong> <strong>Oracle</strong> Human Resources that use<br />
hierarchical structures, such as organizations and positions, may not work correctly, and the<br />
following error may appear: “ORA-01436: CONNECT BY loop in user data”. This error is due to a<br />
bug in the <strong>Oracle</strong> Database that first appeared in version 9.0.1.1.1 and was subsequently fixed<br />
with database patches. This bug reappeared in version 9.2.x of the database. At the time of this<br />
release, a patch from <strong>Oracle</strong> Corporation was unavailable <strong>for</strong> this bug.<br />
The affected views are HR_Org_Hierarchies, HR_Pos_Hier_Elem, and HR_Pos_Hierarchies.<br />
[11243]<br />
Error about check constraint logged.<br />
When <strong>Noetix</strong> views are generated or regenerated or when preupd.sql is run, if there are more<br />
than 1,000 <strong>Noetix</strong> roles, an error message similar to the following is logged: “ORA-02290: check<br />
constraint (…) violated”. Contact <strong>Noetix</strong> <strong>Technical</strong> <strong>Support</strong> <strong>for</strong> a workaround.<br />
[14432]<br />
<strong>Noetix</strong> Corporation 8 support.noetix.com