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.

<strong><strong>Noetix</strong>Views</strong> <strong>for</strong> <strong>Oracle</strong> Work in Process<br />

The following issues have been fixed in this module:<br />

UPDATES<br />

LoV <strong>for</strong> parameter of WIP_Sales_Orders displays values.<br />

When the answer <strong>for</strong> the view was run, the LoV <strong>for</strong> the customer parameter sometimes did not<br />

display values.<br />

[22633]<br />

Answers <strong>for</strong> Work in Process return unique records.<br />

The answers <strong>for</strong> the following views returned multiple records <strong>for</strong> a job. Now, the answer<br />

parameter condition has been modified, so that only unique records are returned.<br />

• WIP_All_Move_Transactions: What Work In Process move transactions were there <strong>for</strong> a<br />

given discrete or lot based job<br />

• WIP_All_Resource_Dist: How resource transactions are distributed across various accounts<br />

<strong>for</strong> a discrete or a lot based job<br />

• WIP_All_Resource_Trans: What resource transaction were there <strong>for</strong> discrete and lot based<br />

jobs<br />

• WIP_Configuration_Variance: What are the material requirements variances <strong>for</strong> a given<br />

job<br />

• WIP_Job_Values: What Are the Work In Process Cost Incurred and Relieved on a Given<br />

Job<br />

• WIP_Routings: What is the status of work in process operations <strong>for</strong> a given job<br />

[23353]<br />

Updates will affect queries written against previous versions of <strong><strong>Noetix</strong>Views</strong> <strong>for</strong> <strong>Oracle</strong> E-Business Suite.<br />

For in<strong>for</strong>mation about earlier updates, see the release notes <strong>for</strong> earlier versions of <strong><strong>Noetix</strong>Views</strong>. These<br />

release notes can be found in Answer ID 707 on the <strong>Noetix</strong> online knowledge base.<br />

Modified Views<br />

Views have been modified as part of <strong><strong>Noetix</strong>Views</strong> 6.0.1 <strong>for</strong> <strong>Oracle</strong> E-Business Suite. The changes are as<br />

follows:<br />

Structure name columns <strong>for</strong> three global views renamed.<br />

With respect to the key flexfield columns that are generated in global views according to the<br />

naming convention and functionality that existed be<strong>for</strong>e <strong><strong>Noetix</strong>Views</strong> 6.0, the columns in three<br />

views have been renamed as follows:<br />

• HXC_All_Assignment_Hist: The GRADE$Structure_Name column has been renamed as<br />

Grade$Structure_Name.<br />

• PAY_Payment_Methods: The BANK$Structure_Name column has been renamed as<br />

Bank$Structure_Name.<br />

• PAY_Payment_Register: The BANK$Structure_Name column has been renamed as<br />

Bank$Structure_Name.<br />

If you were using the global <strong>for</strong>ms of the views <strong>for</strong> <strong>Oracle</strong> Time and Labor and <strong>Oracle</strong> Human<br />

Resources in a version be<strong>for</strong>e <strong><strong>Noetix</strong>Views</strong> 6.0, and you want to continue using the key flexfield<br />

columns according to the old naming convention and functionality, please change the reports that<br />

are based on the previously listed views.<br />

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

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

Saved successfully!

Ooh no, something went wrong!