Large Quantity Of Inventory Items With Null List Price Cannot Be Updated [ID 729641.

1]
Modified: Feb 9, 2012 Type: PROBLEM Status: PUBLISHED Priority: 3

In this Document Symptoms Changes Cause Solution

Applies to:
Oracle iProcurement - Version: 12.0.4 and later [Release: 12 and later ] Information in this document applies to any platform.

Symptoms
Users find after the Release12 upgrade, more than 3000 items that have null List Price and as such are not displayed in iProcurement. When setting the value to 0 in the Item Master form the items are then shown in iProcurement, however this manual process is not practical for so many items. Manually updating MTL_SYSTEM_ITEMS_B table corrects the list price, but the items are still not shown in iProcurement. Due to this issue, users cannot see items in iProcurement for creating requisitions Steps To Reproduce: 1. Create Item with null list price. 2. Notice item is not displayed in iProcurement. 3. This rule is applied to 3000 items after the upgrade.

Changes
Release 12 upgrade from 11.5.9 or earlier.

Cause
List Price is required for items to be shown in iProcurement. The iProcurement item search requires the running of an internal process (online extract API) against item updates, which then makes the item eligible for the search. This is implicit when using standard forms and processes, but is not launched when making table updates by sql. Notes explaining List Price value is needed for iProcurement include; Note 459871.1 - When Adding Item To Cart Get 'Invalid Category' Error Note 183336.1 - Items Without List Price are not Extracted to iProcurement Catalog Since this was a datafix issue it was also verified internally. Note 461747.1 also explains the online implicit extract process in Release 12 iProcurement.

Solution
To implement the solution, execute the following steps: 1) Ensure that you have taken a backup of your system before applying the recommended solution.

2) Find the item/s to change the list price. You could use SQL like the following:

S Q L >s e l e c ti n v e n t o r y _ i t e m _ i df r o mm t l _ s y s t e m _ i t e m sw h e r el i s t _ p r i c e _ p e r _ u n i ti s n u l l
3) Update the List Price value:

S Q L >U P D A T Em t l _ s y s t e m _ i t e m s _ bS E Tl i s t _ p r i c e _ p e r _ u n i t = 0W H E R Ei n v e n t o r y _ i t e m _ i d i n( [ y o u r I D s ] ) ; c o m m i t ;
4) Query the ROWIDs from the table for input into API in step 5 below:

S Q L >S E L E C TM I N ( R O W I D ) ,M A X ( R O W I D )F R O Mm t l _ s y s t e m _ i t e m s _ b ;
5) Run the API, passing in the ROWID values from above. Note that the first parameter in the last line (ICX_CAT_POPULATE...) determined which items to include based on their last update date. Current this is items updated in the last year, but if you want all items increase this value accordingly:

B E G I N I C X _ C A T _ U T I L _ P V T . s e t C o m m i t P a r a m e t e r ( F N D _ A P I . G _ T R U E ) ; I C X _ C A T _ U T I L _ P V T . s e t B a t c h S i z e ( 1 0 0 ) ; I C X _ C A T _ U T I L _ P V T . g e t P u r c h a s i n g C a t e g o r y S e t I n f o ; I C X _ C A T _ U T I L _ P V T . s e t W h o C o l u m n s ( n u l l ) ; I C X _ C A T _ P O P U L A T E _ M I _ P V T . u p g r a d e R 1 2 M I s ( s y s d a t e 3 6 5 , ' & m i n R O W I D ' , ' & m a x R O W I D ' ) ; E N D ;

6) Submit the Rebuild Catalog Intermedia Index concurrent request and wait for it to be completed successfully. 7) Log in and search again; the item will be shown in iProcurement