21.01.2015 Views

NoetixViews for Oracle Payables - Noetix Technical Support

NoetixViews for Oracle Payables - Noetix Technical Support

NoetixViews for Oracle Payables - Noetix Technical Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Views <strong>for</strong> Order Management have per<strong>for</strong>mance problems in version 11.5, later.<br />

Some <strong>Noetix</strong> views <strong>for</strong> <strong>Oracle</strong> Order Management have per<strong>for</strong>mance-related problems in <strong>Oracle</strong><br />

E-Business Suite 11.5 and later. Order statuses are retrieved from the WF_ITEM_ACTIVITY<br />

STATUSES and WF_PROCESS_ACTIVITIES tables; the volume and distribution of data in these<br />

tables affect per<strong>for</strong>mance of these <strong>Noetix</strong> views. Sometimes, order statuses are retrieved from<br />

these tables repeatedly, and retrieval of each order status requires a separate join to <strong>Oracle</strong><br />

Workflow tables.<br />

The affected views are OE_Lines, OE_Order_Territories, and OE_Orders;<br />

OE_Order_Line_Status and OE_Order_Status may also be affected.<br />

Try one of the following workarounds:<br />

• Gather statistics <strong>for</strong> the ONT schema, using a sample size ranging from 30 to 51 percent.<br />

• Purge obsolete in<strong>for</strong>mation from the Workflow tables, as recommended by <strong>Oracle</strong>. These<br />

tables can become quite large, and their size directly affects per<strong>for</strong>mance of the views. For<br />

troubleshooting issues pertaining to workflow data growth, see Note 298550.1 on <strong>Oracle</strong><br />

MetaLink.<br />

• Substitute the Workflow tables used by the affected views with a materialized view or an<br />

equivalent data mart view.<br />

• Contact <strong>Noetix</strong> <strong>Technical</strong> <strong>Support</strong> <strong>for</strong> billable customizations of the affected views so that<br />

they do not use the order-status columns (sourced from the Workflow tables).<br />

[15994]<br />

Queries <strong>for</strong> Purchasing views may work incorrectly after upgrade to 11.5.10.<br />

After <strong>Oracle</strong> E-Business Suite is upgraded to version 11.5.10, time stamps will be stored <strong>for</strong> new<br />

PO receipts. For data that was created be<strong>for</strong>e the upgrade, the time stamp will be 00:00:00. As a<br />

result of this change, queries written <strong>for</strong> the views <strong>for</strong> <strong>Oracle</strong> Purchasing may not return rows <strong>for</strong><br />

transactions that happened after the upgrade unless these time stamps are taken into account.<br />

There<strong>for</strong>e, the queries should be modified. Solutions to this issue include truncating dates, using<br />

the TO_DATE function, and considering the 24-hour periods of dates.<br />

[16752]<br />

Columns return incorrect in<strong>for</strong>mation in views <strong>for</strong> Projects.<br />

In the views <strong>for</strong> <strong>Oracle</strong> Projects, the columns whose labels end with “To_Date” presently return<br />

incorrect values because future transactions are also taken into account. This known issue will be<br />

fixed in a future release.<br />

[19926]<br />

CRP_Department_Resource_Hours returns incorrect data.<br />

The Department_Resource_Hours column of the view returns zero when the shift number is not<br />

equal to 1. This issue will be fixed in a future release.<br />

[19947]<br />

Item category key flexfield columns may return data <strong>for</strong> irrelevant segments.<br />

For the standard and XOP <strong>for</strong>ms of the following views, the respective columns <strong>for</strong> the Item<br />

Categories key flexfield may return in<strong>for</strong>mation <strong>for</strong> segments pertaining to irrelevant structures:<br />

• EAM_Asset_In<strong>for</strong>mation: Asset_Cat$<br />

• EAM_WO_Matrl_Requirements: PO_Cat$, Purch_Cat$, and<br />

Req_Cat$<br />

• EAM_Work_Requests: Asset_Cat$<br />

• GMF_Overhead_Percentages: Cost_Cat$, GL_Cat$,<br />

Item_GL$, and Line_Cat$<br />

• HR_PO_Buyers: Item_Category$<br />

<strong>Noetix</strong> Corporation 9 support.noetix.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!