Skip to main content

Steps to Enable Note To Buyer Field On Shopping Cart Page in iProcurement

 Note To Buyer entered in the iProcurement requisition checkout step applies for only line 1 in the Autocreate form, the below article explains how can the Note To Buyer column be enabled on the Shopping Cart page to allow requisition preparer to enter Note To Buyer for each requisition line.

This functionality of Note To Buyer on the checkout page applies only to line 1 of the requisition.  The Note To Buyer value on the checkout step 2 of 3 in iProcurement is a header level value that is saved to PO_REQUISITION_HEADERS_ALL.NOTE_TO_BUYER. Note To Buyer column shown on  the Autocreate form is a line level value that is from PO_REQUISITION_LINES_ALL.NOTE_TO_AGENT.  Per Bug 14035820, iProcurement saves the Note To Buyer header level value to the First Requisition Line Note To Agent line level value, so that the value is shown to the buyer at auto-create in the Note to Buyer (PO_REQUISITION_LINES_ALL.NOTE_TO_AGENT) column. But it is only shown for the first requisition line.

We understand that this could cause problems if the buyer decides to autocreate requisition line 1 onto a purchase order. The buyer will see the note just fine for the first requisition line during autocreate. But when the buyer comes back later and queries for the requisition in autocreate the note to buyer value will be blank for the remaining lines that are eligible for autocreate, and therefore the buyer will not be aware of the note to buyer. But this is the standard and intended functionality in the current and previous releases. A change to this would require an Enhancement Request.

Currently, the only way to have the Note To Buyer populated for all the requisition lines is to actually populate the line level Note to Buyer (PO_REQUISITION_LINES_ALL.NOTE_TO_AGENT) value, rather than the header level Note to Buyer (PO_REQUISITION_HEADERS_ALL.NOTE_TO_BUYER) value in the checkout page. The line level Note To Buyer by default is only available in iProcurement on the edit single line page. However, this value can also be added to the Shopping Cart page.

Consider this workaround of enabling the Line Level Note To Buyer value in the iProcurement Shopping Cart page and have the requisition preparer populate the value for all Requisition lines that require a note to the buyer at autocreate.
SUGGESTED WORKAROUND - Enable Note To Buyer at the Requisition Line level on the iProcurement Shopping Cart page

1. Enable personalization links in iProcurement

2. Navigate to iProcurement / Shopping Cart page

3. Click the personalize link just above the table (Personalize "Table containing items in the shop...") or click the Personalize Page link

4. Click Complete View / Expand All

5. In the row labeled Table: Table containing ...
- Click the 'Create Item' icon

6 Choose Item Style = Message Text Input

Specify the following details
ID = NoteToAgent
Prompt = Note To Buyer
View Attribute = NoteToAgent
View Instance = PoRequisitionLinesVO

Apply the change

7. Back on the personalize page...

In the row labeled Table: Table containing ...
- Click the Reorder icon

Find the new 'Note To Buyer' at the bottom of the list. Move it just above (DescFlex) or higher in the list so it will be noticed by the requisition preparer when they navigate to the shopping cart page. Apply the change.

8. Click Return To Application near the lower left

9. See that the Note To Buyer column and text fields are available for the requisition preparer to enter this value for each requisition line. Enter the values desired for the requisitions lines and approve the requisition.

10. Query the requisition in Auto-create, and see that the Note To Buyer values are shown for the requisition lines as entered on the shopping cart page

Note: This is applicable only up-to Release R12.2.3 as Oracle Introduced the Popup Shopping Cart Region in R12.2.4

References : 
1) How to Enable Note To Buyer Field On Shopping Cart Page in iProcurement (Doc ID 1589504.1)
2) iProcurement Personalization: Initial Value For Note To Buyer Does Not Populate (Doc ID 1901469.1)
3) How To Enable 'Note to Buyer' Field At Line Level ? (Doc ID 1119147.1)


Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line_type_id    = pol.line_type_id AND povs.vendor_site_id     = poh.vendor_site_id AND pov.vendor_id           = poh.vendor_id AND pol.item_id             = msib.inventory_item_id AND msib.organization_id  

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,                  hroutl_ou . organization_id   org_id ,                  hrl . location_id ,                  hrl . location_code ,                  glev . flex_segment_value FROM     apps . xle_entity_profiles   lep ,         apps . xle_registrations   reg ,         apps . hr_locations_all   hrl ,         apps . hz_parties   hzp ,         apps . fnd_territories_vl   ter ,         apps . hr_operating_units   hro ,         apps . hr_all_organization_units_tl   hroutl_bg ,         apps . hr_all_organization_units_tl   hroutl_ou ,         hr_organization_units   gloperatingunitseo ,         apps . gl_legal_entities_bsvs   glev WHERE    lep . transacting_entity_flag   =   'Y'         AND   l

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     AP_POL_LOCATIONS_TL Table