Add item images in iProcurement catalogue In iProcurement, items can be queried and selected for raising requisitions. Whenever a user queries for a catalog item, the item is displayed in the catalog search screen along with item details, like category, price, supplier, etc. Oracle gives the option to display item images as well. There are 2 options, 1. Enter items in a BPA for a supplier and attach image names 2. Enter items in Quotation for a supplier and attach image names Both options are demonstrated below along with the configuration steps and the usage.
Configuration steps Set profile option Responsibility: System Administrator Navigation: Profile System POR: Extract BPA/Quote Images = Yes
POR: Hosted Images Directory Set the value to the directory where you will be storing the image files to be used by iProcurement catalogues. We shall use the directory, $OA_MEDIA/POR. $OA_MEDIA/PO R. Set the real path of this directory as the profile option value.
Important: The directory path will contain the URL extension of the image. For instance, after we drop the image in the $OA_MEDIA/POR directory on the server the actual directory path to the image file would be something like, /d06/appltest/testcomn/java/oracle/apps/media/POR / We can view the image from the front end as well if we type in the image URL as http://<
> :<>/OA_MEDIA/<>, file>>, in a web browser. POR: Show Thumbnail Images = Yes
Unix Create a directory, POR POR,, under $OA_MEDIA to store the images as we will store the images in $OA_MEDIA/POR
Copy images to this directory. We shall use 1 image for the time being, dustbin.JPG dustbin.JPG.. Now enable DFF for PO Lines. Lines. Navigation: Application > Flexfield > Descriptive > Segments Query for Application = Purchasing and Title = PO Lines.
Create a new Context, Picture Upload.
Click on Segments button. Add an attribute, ATTRIBUTE13 for Picture Upload.
Go to the Segment details form,
Save and compile the DFF.
Add
images
using
Blanket
Purchase
Agreement
Before the raising the BPA we shall check item CMS002 for which we shall add the image. Before the image is added the item looks like the following. Note the Supplier attached to the item.
Now we need to create a Blanket Purchase Agreement or BPA for item CMS002.
Check Global box. Click on PO Line DFF. Select Context, “Picture Upload“.
Enter the image file name.
Save the BPA. Send the BPA for approval by clicking on Approve button.
Press OK button. Ensure that BPA is approved before you go to the next step . Let us check the data from the backend. Connect to Apps database. Execute the query to see the PO Header 1 2 3
SELECT po_header_id, segment1 FROM po_headers_all WHERE segment1 = '411005548'
Now check the PO Line 1
SELECT item_description, attribute_category, attribute13
2 3
FROM po_lines_all WHERE po_header_id = 108681
Navigate to Purchasing administrator responsibility and execute the following programs, Catalog Data Extract – Classifications Set parameters as Log level = 5 Batch size = 5000
Catalog Data Extract – Items Set parameters as Log level = 5 Batch size = 5000
Rebuild Catalog Item InterMedia Index This request does not take any parameters.
Connect to Apps database and check the iProcurement tables to see if the item is updated or not. Check the Procurement item number ‘CMS002‘, i.e. the same item for which
the BPA has been raised and approved. 1 SELECT rt_item_id, supplier, internal_item_num 2 FROM icx_cat_items_b 3 WHERE internal_item_num = 'CMS002'
The 2nd line is important for us as we are looking at the item, CMS002, that will be supplied by AL GURG STAIONERY. Note theRT_ITEM_ID value. 1 SELECT primary_category_name, supplier, internal_item_num, picture, thumbnail_imag 2 FROM icx_cat_items_tlp 3 WHERE internal_item_num = 'CMS002'
Now check the item in iProcurement
The item, for the supplier for whom the BPA was raised, displays the image.
Add
images
using
In iProcurement, check the catalog items CMS005 and CMS006 Search for item CMS005
Quotations
Search for item CMS006
In the database query for the items in iProcurement tables, 1 2 3
SELECT rt_item_id, supplier, internal_item_num FROM icx_cat_items_b WHERE internal_item_num IN ('CMS005', 'CMS006')
1 2 3
SELECT primary_category_name, supplier, internal_item_num, picture, thumbnail_imag FROM icx_cat_items_tlp WHERE internal_item_num IN ('CMS005', 'CMS006')
Now go to Purchasing responsibility Navigation: RFQ’s and Quotations > Quotations
Create a quotation Supplier: Select a supplier Type: Catalog Quotation Effectivity: Enter a date range so that the current date falls within the range Check the box, Approval Required. Enter the items for which you want to enter images
Enter the details for item, CMS005.
Enter the DFF values for the item with image file name
Now enter the data for item CMS006
Enter the DFF
Click OK to close this window. On the main quotation form select each item line and click on Price Break button. Enter the Quantity for both items as shown below.
Save and close this window. Now the Approve button on the main quotation form is enabled.
Click on Approve. Enter the Type, Reason and Effective dates.
Click on OK button to approve the quotation. A popup is shown with the approval message.
Click OK. Now the quotation is approved. Change the Status field of the quotation header to Active.
Save the quotation. Now execute the 3 programs in series, 1. Catalog Data Extract – Classifications 2. Catalog Data Extract – Items 3. Rebuild Catalog Item InterMedia Index Check the log of the program, Catalog Data Extract – Items. 1 +----------------------------2 | Starting concurrent program execution... 3 +----------------------------4 5 Arguments 6 -----------7 2 8 2500 9 -----------10 11 +---------------------------------------------------------------------------+ 12 Start of log messages from FND_FILE 13 +---------------------------------------------------------------------------+
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
Commented out openLog 04/08/12 15:30:07:3 BEGIN Extractor 04/08/12 15:30:07:3 Start to extract ITEM: job number 13527542, system process id 11 04/08/12 15:30:07:3 Commit size: 2500, Debug level: 2 04/08/12 15:30:07:3 Loader Values[Load Catalog Groups: N, Load Categories: Y, Load Te Items: Y, Cleanup Flag: N, Catalog Groups Last Run Date: , Categories Last Run Date: 04/ Item Master Last Run Date: 04/08/12 15:26:09, Template Lines Last Run Date: , Vendor Items In all Langs: N] 04/08/12 15:30:07:3 Extract item data 04/08/12 15:30:07:3 Multi Org Flag: Y 04/08/12 15:30:07:3 Profile option POR_EXTRACT_A13_AND_A14: Y 04/08/12 15:30:07:3 Handling vendors with name changed. 04/08/12 15:30:07:5 Database Version: 11.2 04/08/12 15:30:09:91 Number of processed items in batch: 1, for vendor name change 04/08/12 15:30:09:91 Total Number of batches processed for vendor name change : 1 04/08/12 15:30:09:91 Handling vendor sites with name changed. 04/08/12 15:30:09:93 Update last run dates 04/08/12 15:30:09:96 Cache hash size is 32768 04/08/12 15:30:09:96 Start to process TEMPLATE 04/08/12 15:30:09:97 Database Version: 11.2 04/08/12 15:30:09:98 Processed records: 0 04/08/12 15:30:09:98 Processed records: 0 04/08/12 15:30:09:98 Processed records: 0 04/08/12 15:30:09:98 Processed records: 0 04/08/12 15:30:09:98 Total processed price rows: 0 04/08/12 15:30:09:98 Cleanup items without price. 04/08/12 15:30:09:98 Total deleted items without price : 0 04/08/12 15:30:09:98 Set active flags. 04/08/12 15:30:09:98 Total processed rows to set active flag: 0 04/08/12 15:30:09:98 Update WHO. 04/08/12 15:30:09:98 Total processed rows to update WHO columns: 0 04/08/12 15:30:09:99 Database Version: 11.2 04/08/12 15:30:09:0 Update last run dates 04/08/12 15:30:09:0 Start to process CONTRACT 04/08/12 15:30:09:2 Database Version: 11.2 04/08/12 15:30:12:21 Database Version: 11.2 04/08/12 15:30:12:23 Processed records: 2 04/08/12 15:30:12:23 Processed records: 2 04/08/12 15:30:12:23 Processed records: 2 04/08/12 15:30:12:23 Processed records: 2
54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93
04/08/12 15:30:12:23 Total processed price rows: 2 04/08/12 15:30:12:23 Cleanup items without price. 04/08/12 15:30:12:24 Total deleted items without price : 0 04/08/12 15:30:12:24 Set active flags. 04/08/12 15:30:12:24 Total processed rows to set active flag: 4 04/08/12 15:30:12:24 Update WHO. 04/08/12 15:30:12:24 Total processed rows to update WHO columns: 4 04/08/12 15:30:12:26 Database Version: 11.2 04/08/12 15:30:12:27 Start to process GLOBAL_AGREEMENT 04/08/12 15:30:12:29 Database Version: 11.2 04/08/12 15:30:12:30 Processed records: 0 04/08/12 15:30:12:30 Processed records: 0 04/08/12 15:30:12:30 Processed records: 0 04/08/12 15:30:12:30 Processed records: 0 04/08/12 15:30:12:30 Total processed price rows: 0 04/08/12 15:30:12:30 Cleanup items without price. 04/08/12 15:30:12:30 Total deleted items without price : 0 04/08/12 15:30:12:30 Set active flags. 04/08/12 15:30:12:30 Total processed rows to set active flag: 0 04/08/12 15:30:12:30 Update WHO. 04/08/12 15:30:12:30 Total processed rows to update WHO columns: 0 04/08/12 15:30:12:31 Database Version: 11.2 04/08/12 15:30:12:33 Update last run dates 04/08/12 15:30:12:33 Start to process ASL 04/08/12 15:30:12:34 Database Version: 11.2 04/08/12 15:30:12:35 Processed records: 0 04/08/12 15:30:12:35 Processed records: 0 04/08/12 15:30:12:35 Processed records: 0 04/08/12 15:30:12:35 Processed records: 0 04/08/12 15:30:12:35 Total processed price rows: 0 04/08/12 15:30:12:35 Cleanup items without price. 04/08/12 15:30:12:35 Total deleted items without price : 0 04/08/12 15:30:12:35 Set active flags. 04/08/12 15:30:12:35 Total processed rows to set active flag: 0 04/08/12 15:30:12:35 Update WHO. 04/08/12 15:30:12:35 Total processed rows to update WHO columns: 0 04/08/12 15:30:12:36 Database Version: 11.2 04/08/12 15:30:12:37 Start to process ITEM 04/08/12 15:30:12:39 Database Version: 11.2 04/08/12 15:30:12:73 Processed records: 0
94 04/08/12 15:30:12:73 Processed records: 0 95 04/08/12 15:30:12:73 Processed records: 0 96 04/08/12 15:30:12:73 Processed records: 0 97 04/08/12 15:30:12:73 Total processed price rows: 0 98 04/08/12 15:30:12:73 Cleanup items without price. 99 04/08/12 15:30:12:73 Total deleted items without price : 0 10004/08/12 15:30:12:73 Set active flags. 10104/08/12 15:30:12:73 Total processed rows to set active flag: 0 10204/08/12 15:30:12:73 Update WHO. 10304/08/12 15:30:12:73 Total processed rows to update WHO columns: 0 10404/08/12 15:30:12:74 Database Version: 11.2 10504/08/12 15:30:12:76 Update last run dates 10604/08/12 15:30:12:76 All updated price rows processing done: 2 10704/08/12 15:30:12:80 END Extractor 10804/08/12 15:30:12:80 Populate interMedia index BEGIN 10904/08/12 15:30:42:22 Populate interMedia index END 110+---------------------------------------------------------------------------+ 111End of log messages from FND_FILE 112+---------------------------------------------------------------------------+ +---------------------------------------------------------------------------+ Executing request completion options...
Note that 2 records have been updated in the Catalog section of the log file. This means both the items have been updated with the supplier and the images. Let us query the iProcurement table, 1 2 3
SELECT primary_category_name, supplier, internal_item_num, picture, thumbnail_imag FROM icx_cat_items_tlp WHERE internal_item_num IN ('CMS005', 'CMS006')
We see that the item CMS005 and CMS006 are attached with the supplier and picture as well as the thumbnail image in the database. Let us check on the iProcurement catalog page now. Search for CMS005
Again search for item CMS006
Both images have been applied through a single quotation. Important: Loading images using quotations is the better method, as a quotation does not need to be fulfilled and for a single supplier there can be multiple quotations. Whereas when we upload images through a BPA this will be a dummy BPA for which no Releases will be created but if genuine BPAs are raised for the same supplier in Oracle the dummy BPA will be displayed in reports and forms which will be confusing to users.
