iProcurement Setup 11i: Oracle Internet Procurement Functional Setup [ID 134168.

1]

Modified 22-OCT-2008 Type BULLETIN Status PUBLISHED

PURPOSE
-------

To assist viewers of this document in verifying the common setup steps related
to this topic. Please consider all steps or guidelines mentioned below prior to
logging an iTAR with support.

SCOPE & APPLICATION

-------------------

This document is intended for all users, consultants and support analysts
of the iProcurement application. The setup steps listed below are not
necessarily in the proper order, but are simply provided as a tool for
the user to verify their work.

iProcurement Setup 11i: Oracle Internet Procurement Functional Setup

-----------------------------

You must complete the following setup steps to use the full range of features
available in Oracle Internet Procurement 11i.

1. Configure Account Regions Required (11.5.9 and lower)

2. Define Information Templates Optional
3. Define Realms Optional
4. Set Up Procurement Cards Optional
5. Set Up Attachments Required
6. Set Up Profile Options Required
7. Enable Function Security Optional

As you can see steps 1,5-6 are required while steps 2-4,7 are optional steps to
be completed in order to get iProcurement for 11i functional. You will also need
to setup profile values as well as functional security.

Step 1: Configure Account Regions (Required - 11.5.9 and lower)

----------------------------------------------
Configure the following regions to match the accounting structure of your
organization:
POR_BILLING_MULT_CHARGE_AC_R
POR_BILLING_CHARGE_ACCOUNT_R
If your organization has multiple Chart of Accounts, you must configure the
following two profile options to support these multiple Chart of Accounts:
POR: Edit Accounts Region
POR: Multiple Accounts Region

To configure accounting regions for multiple Chart of Accounts

--------------------------------------------------------------
1. Copy the Account regions POR_BILLING_MULT_CHARGE_AC_R and
POR_BILLING_CHARGE_ACCOUNT_R

2. Rename the new regions created in step 1.

3. Modify the region so that the prompt names and field lengths of the
accounting segments match the accounting structure for the Chart of accounts.

4. Assign the name of the new regions to the following profile options.

POR: Edit Accounts Region. This profile option should be set to the new region
name corresponding to POR_BILLING_CHARGE_AC_R created in step 2.

POR: Multiple Accounts Region. This profile option should be set to the
new region name corresponding to POR_BILLING_MULT_CHARGE_
ACCOUNT_R created in step 2.

Step 2: Define Information Templates (Optional)

-----------------------------------------------
Oracle Internet Procurement 11i uses information templates to pass necessary
order processing information to suppliers. You may set up information templates
to gather additional information. When an information template is assigned to a
category or item, Internet Procurement 11i prompts users to provide the
information specified in the template. For example, you can implement
information templates for items like business cards that require additional
information (name, address, email, phone) from the requester. Internet
Procurement 11i will then prompt for name, address, email, and phone number when
you order business cards. Each information template must be associated with an
item or item category. If an information template is associated with an item
category, all items belonging to that category are also associated with the
template.

Note: Do not confuse information templates with requisition templates in Oracle

Purchasing. They are not the same.

To define an information template:

----------------------------------
1. Navigate to the Define Information Template window. From the Oracle
Purchasing menu, select Setup>Information Templates.

2. Enter an attribute name and description. The attribute name is the actual
field prompt that is displayed in Internet Procurement 11i.

3. Optionally, enter a default value to automatically appear in the field.

4. Indicate whether the field is mandatory for Internet Procurement 11i users.
If the field is mandatory, users will be prompted to enter a value in the field
before proceeding to complete the requisition.

5. Indicate whether to activate the attribute to actually display on Self

Service Purchasing pages. In certain circumstances, you may want to define an
attribute, but delay enabling it for display to Internet Procurement 11i users.

6. Choose Associate Template to associate the template with an item or an item

category. The Information Template Association window appears.
7. Select the type of association (item number or item category) you want to
associate with the template.

8. If you selected Item Number in the previous step, enter the number. If you
selected Item Category, enter the category.

Step 3: Define Realms (Optional)

--------------------------------
Application security in Oracle Applications is maintained and managed by
assigning responsibilities, excluding attributes, and securing attributes to
users. Internet Procurement 11i uses a security realm as an additional layer for
application security.

A realm is a set of access privileges to internal catalogs, external catalogs,

or categories within internal catalogs. Realms appear as securing attributes in
the System Administrator User window; they are assigned to users in exactly the
same manner as securing attributes are assigned.

A security realm is a list of objects (item source or a category) to which a

user is granted access. Examples of item sources include a company’s internal
catalog or an external supplier’s catalog or marketplace. A category, unlike an
item source, represents a grouping of items within the internal catalog. You
cannot use security realms to enforce content policies for external suppliers.

You cannot enforce access restrictions within a realm; access to a realm

automatically means access to all the categories or sources within that realm.
Restricting access to categories may require substantial maintenance. For
example when you add a new category you must add that category as a value in
each user’s securing attribute. If you want to exclude the use of one category
(for example, MISC.MISC) out of a total of 100 categories, you must define a
realm that lists the 99 categories you wish to allow access to.

To define a realm:
------------------
1. Navigate to the Realms window. From the Oracle Purchasing menu, select
Setup>E-Catalog Admin>Realms.

2. Enter a name and description for the new realm.

3. Select either Item Source or Category as the component type.

4. If you selected Item Source in the previous step, select internal or external
catalogs from the list of components. If you selected Category as the component
type, select a category from the list of values.

5. Save your work.

Applying Realms to Users and Responsibilities:

----------------------------------------------
Security is applied at the responsibility level using the values obtained from
individual users.
Security realms consist of either item sources or categories, but never both in
the same realm. At the responsibility level, select whether to restrict access
to categories, item sources, or both by selecting from the following securing
attributes:

RT_CATEGORY_ID (for categories).

ICX_POR_ITEM_SOURCE_ID (for external item sources such as TPN Register).
ICX_POR_REALM_ID
RT_CATEGORY_ID
ICX_POR_ITEM_SOURCE_ID

At the user level you must choose the securing attribute ICX_POR_REALM_ID and
supply the list of Realm IDs to which you are granting access to users. This
list can contain both item source restricted realms and category restricted
realms.

When a Internet Procurement 11i user chooses a function tied to a

responsibility, a security check is performed to identify the securing
attributes tied to the responsibility. If item sources are being restricted,
only the item sources in the realms assigned to the user are displayed to the
user.

If the user has access to the internal catalog and searches for items, only
those categories and relevant included items listed in the realms assigned to
the user will be displayed. For example, assume that the user has access only
to the “pens” category. If the user searches for “office supplies,” pens,
pencils, rulers, and so on from multiple categories are returned. But the user
will see only the items belonging to the “pens” category.

Note that you can select only one component at a time for inclusion in the
components list for the realm. You cannot exclude components.

Step 4: Set Up Procurement Cards (Optional)

-------------------------------------------
For detailed information on setting up procurement cards, see the sections on
Setting Up Credit Card Programs and Procurement Card Integration in the Oracle
Payables User’s Guide. In addition to the setup steps provided in the Oracle
Payables Users’ Guide, you will need to enable supplier sites to accept
procurement cards.

To enable supplier sites to accept procurement cards:

-----------------------------------------------------
1. Navigate to the Supplier Sites window. From the Payables menu, choose
Suppliers>Entry.

2. Query for the supplier for which you want to enable procurement cards and
open the Sites region.

3. Enable the Procurement Card Site check box to indicate that the supplier is
set up to accept the card brands you use.

4. Save your work.

Step 5: Set Up Attachments (Required)
-------------------------------------
In Oracle Internet Procurement 11i, users can add attachments to an order at the
time of checking out their shopping cart.

Attachments can be: Internal to Requisition - the attachment can be viewed only
from the requisition.

To Buyer - the attachment information is passed on to the purchase order created

from the requisition.

To Approver - the attachment information can be viewed by the appropriate

approvers.

To Receiver - the attachment information can be viewed by the receiver, if the

Receiver is not the requester.

To Supplier - text and non-image file attachments can be transmitted via EDI to
the supplier when the Purchase Order autocreated from the requisition is
transmitted.

Miscellaneous
Oracle Internet Procurement 11i users can also add the following type of
Attachments:
File - any file type supported by the browser
URL Any URL accessible by the system
Text Free form text messages

Set up the Attachment File Directory profile option to point to the directory
where the files for attachments will be stored. Make sure that the directory
path specified for this profile option is accessible from the machine on which
the Web Server is running.

Setting up Profile Options

---------------------------
A number of profile options govern the behavior of Oracle Internet Procurement
11i. During implementation, you must set a value for each profile option to
specify how Oracle Internet Procurement 11i controls access to and processes
data. The following table displays profile options necessary for Oracle
Internet Procurement 11i.

The System Administrator sets the following profile options.

Attachment File Directory - Specifies the directory path on your local system
where the attachment files will be maintained.

ICX: Allow Funds Override - Indicates whether a requestor can override their
allowed funds, if encumbrance is enabled.

ICX: Date Format Mask - Determines the date format.

ICX: Days Needed By - Sets the number of days until the user needs to receive
an order.

ICX: Language - Determines the language.

ICX: Limit Connect - Sets the maximum number of page hits per session. Set the
value to 1000.

ICX: Limit Time - Determines the maximum time limit a user can be logged into
the system. Default is 4 hours.

ICX: LOV Type - Should always be set to “HTML”.

ICX: Override Location Flag - Determines whether users can override the default
location to deliver orders.

ICX: Override Requestor - Determines whether users can override the default
requestor. This setting can be limited to user only, users within the same
personnel organization, or users within the same business group.

ICX: Requisition Sever - The host name of the Oracle Application Server that
provides basic Self Service Purchasing functionality.

POR: Amount Based Services Line Type - Determines the line type for amount-based
services. An amount-based service is expressed in monetary terms, for example,
500 USD worth of service. The value set here should be distinct from the values
set for POR: Goods Line Type and POR: Rate Based Services Line Type. POR:
Approved Pricing Only Restricts user access to only those items associated with
contracts or templates.

POR: Cleanup Thread Interval - A number in milliseconds. Self-Service Purchasing

cleans up unused requisition objects on the middle tier every x milliseconds,
where x is the value you enter.

POR: Debugging - Sets debugging On or Off.

POR: Enable Requisition Line Customization - If set to Yes, Self-Service

Purchasing calls a customization API for requisition lines where custom business
logic can be introduced. Performance is better when set to No.

POR: Goods Line Type - Determines line type for goods type non-catalog order.
The value set here should be distinct from the values set for POR: Amount Based
Services Line Type and POR: Rate Based Services Line Type.

POR: Rate Based Services Line Type - Determines line type for rate-based Service
type non-catalog orders. A rate-based Service is a monetary charge per four,
day, and month. The value set here should be distinct from the values set for
POR: Goods Line Type and POR: Amount Based Services Line Type. POR: Help Path
The location of the help files for multi-org environments. For example,
/<OU Name>/, where OU Name is the name of the operating unit.

POR: System Approvers are Mandatory - Determines whether the default approvers
on the approver list are mandatory and may not be deleted.

PO: Workflow Processing Mode - Affects the performance of the Purchasing

approval workflow processes. Online completes an entire approval workflow
process before letting you proceed to the next activity, but provides you with
an updated Status (for purchase orders) as soon as it finishes. Background
allows you to proceed to the next activity while the approval process completes
in the background. Whichever option you choose, you can always view the current
status of a requisition or purchase order through the Requisitions Summary or
Purchase Orders Summary windows. When this profile option is set to Background,
you must start the Workflow Background Process, which you access through the
System Administration responsibility. It is recommended that you set this
process to run frequently, if you are using it for Background mode approvals

ECE: Output file path - The data extraction process for Self-Service Purchasing
uses the same directory to store the data files as does the EDI Gateway.
However, this feature of Self-Service Purchasing in no way requires EDI Gateway.

POR: Default Currency Conversion Rate - Enables users to set the default
exchange rate type. Currency conversion rate must be table based.

POR: Edit Accounts Region - Enables the user to support multiple chart of
accounts. Using Web Application Dictionary, you could create a region with a
certain chart of accounts structure, and associate this region at the
responsibility level. The region defined takes precedence to display the Edit
Accounts Page. If this profile is left blank, the default page is displayed.

POR: Multiple Accounts Region - Enables the user to support multiple chart of
accounts. Using Web Application Dictionary, you could create a region with a
certain chart of accounts structure, and associate this region at the
responsibility level. The region defined takes precedence to display the Edit
Multiple Accounts Page. If this profile is left blank, the default page is
displayed. See: POR: Edit Accounts Region.

POR: ITEM PIC FILE PATH - Enables the user to specify the directory path on the
local system where the picture files are stored for the items in Oracle Internet
Procurement 11i catalog.

POR: Select Inventory Replenishment Lines for Confirm Receipts - Set this
profile option to “Yes” if you want the Confirm Receipts Workflow process to
select PO Shipments with destination type “Inventory” in addition to PO
Shipments with destination type “Expense”.

POR: Servlet Virtual Path - The virtual path name on the apache configuration.

POR: Use sequence for requisition numbering - For improved performance, you can
set this profile option to ‘Yes’. This will generate requisition numbers using
the database sequence. Note: The requisition numbers sequence will be shared
across operating units.

Profile Options Set from User’s Profile

---------------------------------------
The System Administrator should not set these profile options. These values are
set when users defines their profiles in Oracle Internet Procurement 11i using
My Profile.

POR: Preferences - Deliver to Location Enables users to set their deliver to

location user preference.

POR: Preferences - Expenditure Item Date Enables users to set their expenditure
item date user preference for project-related requisitions.

POR: Preferences - Expenditure Org Enables users to set their expenditure

organization user preference for project-related requisitions.

POR: Preferences - Expenditure Type Enables users to set their expenditure type
user preference for project-related requisitions.

POR: Preferences - Project Users can set their project number user preference
for project related requisitions.

POR: Preferences - Requester Users can set their requester user preference.

POR: Preferences - Selected Items Default to Inventory Enables user to indicate

their user preference of whether ordered items are to replenish inventory.

POR: Preferences - Subinventory Users can set their Subinventory user

preference. This is only valid if the POR: Preferences - Inventory Replenishment
profile is set to Yes.

POR: Preferences - Task Users can set their task number user preference for
project related requisitions.

POR: Result Set Size The number of records returned from a search in Search
Results, View Orders and Receiving pages.

NOTE: POR: Preferences - Inventory Replenishment <<==>> POR : Preferences - Selected

Items Default to Inventory

Function Security:
--------------------
To enable further security and usage restrictions for groups of users,
Oracle Internet Procurement 11i has implemented function security against
certain functions and actions in various pages, including the Order Status page,
Approvals page, Add Approvers page, Receive Orders page and power checkout. You
can restrict user access to the functions available on these pages by enabling
function security on the functions available in these pages. For example, you
can allow users to query up orders, but not receive items against them by
enabling function security using the Receive button on the Order Status page.
Function security attributes are defined at the Responsibility level.

To enable function security:

1. Navigate to the Responsibilities window use the following navigation path:
Security>Responsibility>Define

2. Create a new responsibility for Self-Service Purchasing. This responsibility

will be used to enforce function security.

3. From the list of values available in the Function and Menu exclusions region,
select the appropriate securing attribute.
4. Save the responsibility.

5. Navigate to the Users window, and assign the responsibility to the

appropriate user. Use the following navigation path to open the Users window.

6. Assign the responsibility to Oracle Internet Procurement 11i users.

RELATED DOCUMENTS
-----------------

Oracle Internet Procurement

Related

Products

 Oracle E-Business Suite > Procurement > Procurement > Oracle iProcurement

Back to top

Rate this document

Article Rating Comments
Rate this document

Excellent

Good

Poor

Did this document help you?

Yes

No

Just browsing
Important Note: this feedback may be anonymously visible to other
customers until processed by Oracle Support.
How easy was it to find this document?

Very easy

Somewhat easy

Not easy

Cancel
==============
How to Diagnose Issues Related to the Shopping Cart Within iProcurement [ID 739051.1]

Modified 31-MAR-2011 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
INTRODUCTION
DOCUMENTATION
PROCESSING OVERVIEW
SETUP
LOGGING
TRACING
DATA AND QUERIES
RELATED PROCESSING
CODE FILES
PATCHES
DATA CORRUPTION

Applies to:

Oracle iProcurement - Version: 11.5.10 to 12.2 - Release: 11.5 to 12

Information in this document applies to any platform.

Goal

This HOW-TO note has been created with the main objective of provide to support engineers and
customers a troubleshoot document for the shopping cart functionality within iProcurement.

Solution

INTRODUCTION

The shopping cart is a functionality that allows the preparer to add items to it, in order to requisition for
approval. From the Search Results Summary or Search Results pages, the preparer can add the items to
the shopping cart.

The shopping cart is the middle step of the creation of a requisition. The main process includes search
internal items, source document items, bulkloaded items, punchout items or non-catalog items, add them
to the shopping cart and the proceed and do the checkout in order to submit the requisition for approval.

An additional way to add items to the cart is using the copy button, from a requisition already created or
from the shopping list or from the favorites list.

The shopping cart is handled as a requisition, and when you add an item to the shopping cart you are
basically adding a line to requisition header that is marked with the flag active_Shopping_cart_flag with
"Y" (Yes) and status "SYSTEM_SAVED"
Note: Oracle iProcurement prevents combining goods and temporary labor on the same requisition. If the
requester tries to create a contractor request while there are goods in the shopping cart (or vice versa),
Oracle iProcurement will guide the requester to keep these on separate requisitions.

Saved Carts. Requesters can save an unlimited number of shopping carts in progress. This enables
them to save selected items and return later to add more items and check out.

Procurement Card Purchases. Oracle iProcurement automatically flags shopping cart lines for
procurement card (P-Card) payment and defaults the P-Card number depending on the requester and
supplier profiles.

Oracle Projects/Grants Integration. Integration with Oracle Projects , Grants and Oracle Project
Manufacturing enables requesters to optionally reference project, grants and task information on
shopping cart order lines.

DOCUMENTATION

Note 134255.1 - iProcurement: Shopping List Troubleshooting Guide

Oracle® iProcurement - Implementation Guide Release 11i Part No. A85361-05

Oracle® iProcurement - Implementation and Administration Guide Release 12 Part No. B31402-01

Both guides are available in My.Oracle/Metalink > Knowledge.

PROCESSING OVERVIEW

How the shopping cart works? Basically, the shopping cart works as a recipient where you put the
request items, and those items can be added from different places within the application, those places
are:

- Using the Search engine

- From the iProcurement HomePage, within my requisition section and using the copy button

- From the shopping list, where you add items from your favorite list or the templates available

- From Requisitions Tab, after you search a requisition, you can use "Copy to Cart" button to add ALL the
items from that particular requisition to the shopping cart.

- As a non-catalog item where the information of the item is entered before adding to the cart.

- Finally, when you are using Services via Contractor request.

Before you add non-catalog items to the cart, the application can ask the information template fields
values and validate those.

After you add the items to the cart, the application displays the Shopping Cart page, this page will show
all the items you have added to the cart and it is the star point for the checkout process.

During the Shopping Cart display, the application invokes the POR_CUSTOM_PKG validation at Line
level and also displays the Descriptive Flexfields created under Purchase - Requisition Lines.
Additional to the validation and displays above documented, you can personalize the shopping cart page
using personalization method. Only those columns provided under personalization can be added or hide
it, if there any columns not provided and your business requires it, this will be considered an
enhancement request.

SETUP

There is no special setup related to the shopping cart. Only personalizations will tak place here, if you
need to display additional items or hide the default ones. Please refer to section "RELATED
PROCESSING" for personalization under shopping cart page.

LOGGING

There are several ways to enable the logging when an OA Framework issue occurs:

A. Enable the logging in the page, to do this please execute the following:

 Using System Administrator responsibility, set profile option at the user level: FND: Diagnostics =
Yes
 Log in with user or responsibility with profile enabled.

 Once you enabled FND: Diagnostics to Yes, a link Diagnostics will show up at the top of the page.

 Click Diagnostics link.

 Use option Show Log on Screen.

 Click Go.

 Choose Log Level Statement (1).

 Enter in Module %

 Click Go to see the log (debug.log). You will see that all the pages will include the log in the
bottom of the page, something like this:

B. Enable the logging and storage those from the table, to do this please execute the Following:

 Using System Administrator responsibility, set profile options at the user level:

FND: Debug Log Enabled : Yes

FND: Debug Log Filename : leave it as null
FND: Debug Log Level : Statement
FND: Debug Log Module : %

 Truncate table APPLSYS.FND_LOG_MESSAGES

 Bounce iAS/Apache

 Reproduce the issue

 Get the table dump of fnd_log_messages in spreadsheet format.

C. Enable the logging and storage those into a file, to do this please execute the following:

 Using System Administrator responsibility, set profile options at the user level:

FND: Log Enabled = Yes

FND: Log Level = Statement
FND: Log Filename = /usr/tmp/debug.log (or any other directory with write privileges)
FND: Log Module = %
 Reproduce the issue in the application. Go to /usr/tmp/ and get the debug.log

Any of these three methods are accepted by support and development.

TRACING

When we talk about tracing, we are talking to collect the access executed by the application to the
database in terms of queries or DML scripts, like UPDATE, INSERT or DELETE. To enable the trace,
there are also several methods:

A. Traditional trace enabled within the application:

 Set profile FND: Diagnostics to Yes at user level.

 Login as the above user

 Click on Diagnostics icon.

 Select 'Set Trace Level' and click Go

 Select the desired trace level with binds and waits and click Save

 Perform the activity to reproduce the issue

 Click Diagnostics icon again

 Select 'Set Trace Level' and click Go

 Take note of the all trace file numbers on the left side of the page

 Disable trace
 Find the trace files with contains the trace numbers under the UDUMP directory on the database
server

 Execute tkprof in the trace files

 Upload raw and tkprof files

B. There is another old method that is still valid for 11i or R12.

 Log onto core Applications with the Application Developer responsibility.

 Navigate to the Profile menu.

 Query up the profile name "FND_INIT_SQL"

  In the bottom block of the form, make sure that ALL checkboxes are checked.

 Typically, you will have to enable the checkboxes under "User Access" to make it "Visible" and
"Updatable".

 Save changes and exit this form.

 Switch responsibility to System Administrator.

 Navigate: Profile > System.

 On the "Find System Profile Values" form, make sure the checkboxes for "User" and "Profiles with
no Values" are checked.

 Beside the "User" checkbox use the LOV to select the user who's activity you need to trace.

 In the "Profile" field, type: %Initialization% Then click the "Find" button.

 In the "System Profile Values" form, enter the following in the field for the profile "Initialization SQL
Statement - Custom" for the specific User:

begin FND_CTL.FND_SESS_CTL('','', '', 'TRUE','','ALTER SESSION SET

TRACEFILE_IDENTIFIER='||''''||'USERXXX' ||''''||' EVENTS ='||''''||' 10046 TRACE NAME
CONTEXT FOREVER, LEVEL 12 '||''''); end;

NOTE: It is all single quotes. If there is a typo, the user will not be able to login. Optional to replace
USERXXX by the user executing trace.

 Save changes and exit the form.

 Find where the trace files are created in the instance. Check table v$parameter for
user_dump_dest directory location. Delete all trace files from this directory.

 Log onto applications as the user for whom turned on tracing,and promptly recreate the problem,
then log off.

 Execute tkprof in the trace files. Upload the tkprofed trace file(s) created.

 Make sure to clear the "Initialization SQL Statement - Custom" profile option for the user who's
activity you traced.

Both tracing methods are valid and accepted by support and development teams.

DATA AND QUERIES

Since the shopping cart is saved like a regular requisition, these are the queries to retrieve the information
for it:

HEADER

select h.*
from po_requisition_headers_all h,
fnd_user u
where h.preparer_id = u.employee_id
and h.active_shopping_cart_flag = 'Y'
and u.user_name = upper('&user_name');

LINES

select l.*
from po_requisition_headers_all h,
fnd_user u,
po_requisition_lines_all l
where h.preparer_id = u.employee_id
and h.requisition_header_id = l.requisition_header_id
and h.active_shopping_cart_flag = 'Y'
and u.user_name = upper('&user_name')
order by line_num;

RELATED PROCESSING

Personalize Oracle iProcurement Using Oracle Applications Framework. Oracle iProcurement is built
upon the Oracle Applications Framework technology. Oracle Applications Framework enables system
administrators to easily personalize the user interface in Oracle iProcurement. Examples include showing,
hiding, moving, or modifying regions (such as the My Requisitions section on the shop Home page), items
(such as a button), or fields (such as showing the Rate Type field, which is hidden by default in the
shopping cart).

You can use personalizations to hide or display only those fields enabled by the developers. If you do not
find a field under the page definition, then, this will be considered an enhancement request.

Example of a personalization:

Figure 1.

Figure 2.

By default, Oracle iProcurement is already set up to display the optimum information to requesters. For
example, the first figure above shows that by default the shopping cart shows basic item fields, such as
Item Description, Unit, and Price. You can, however, additionally display one or more fields that are
hidden by default. In the second figure above, the following hidden fields are now displayed: Supplier
Config ID, which is used by punchout for suppliers with configured items; and Source Document Type,
Source Document Number, and Source Document Line.

There is another way to customize the shopping cart, via the POR_CUSTOM_PKG. This package let you
default values or validate information for the shopping cart, but only at line level.

CUSTOM_DEFAULT_REQ_LINE This procedure can be used to include logic to default the information
onto a requisition line. This procedure is called from the executeCustomDefaultingLogic
method in CustomReqLineHelper when a new line is added to the shopping cart.
CUSTOM_VALIDATE_REQ_ LINE This procedure can be used to include logic to validate the information
on the requisition line. This procedure is called from the validate method in CustomReqLineHelper on
every page in the checkout flow.

You can also add Descritive Flexfields information to the shopping cart. These will come from Application
Purchasing, Requisition Lines. You can review the following two notes in order to understand the DFF
functionality under the shopping cart page.

Note 339141.1 - How To Display Requisition Line DFF On Requisitions Detail Page .

Note: 332364.1 - How Are Descriptive Flex Fields Supported Against Context
to understand the DFF context.

CODE FILES

Below is the main information for the shopping cart page.

Source page: $JAVA_TOP/oracle/apps/icx/por/req/webui/ShoppingCartPG.xml

Constructor class: ShoppingCartCO.class

The shopping cart page as is, does not contain too much processing, the real validations are executed
from the pages where you are adding the items to the shopping cart, these possible places are:

- Home Page: Copy from My Requisition to the cart

Source Page: ShoppingHomePG.xml

Constructor class: ShoppingHomeCO.class

- Non-Catalog Page: Add to cart after you enter all the non-catalog information required

Source Page: NonCatalogRequestPG.xml

Constructor class: NonCatalogRequestCO.class

- Shopping List Page: My favorites and templates

Source Page: SearchResultsPG.xml

Constructor class: SearchResultsCO.class

The page and constructor class above is used also when you use the search engine provided by the
application, this displays the results found and you click on "Add to Cart" button.

- Requisition Page: After you search a requisition and you click on "Copy to Cart"
Source Page: ReqSummaryPG.xml

Constructor class: ReqSummaryCO.class

All the constructor classes above have the action to add the items to the shopping cart.

PATCHES

The eBusiness Suite Recommended Patch List is now available from the following navigation -

 Under MetaLink home page, click on the "Patches" button

 Click on the "eBusiness Suite Recommended Patch List" link

 Specify your query criteria to retrieve application recommended patches for your instance

Some important patches:

Note 580002.1 - Adding To Cart Delivers Error - ORA-01400 Cannot Insert NULL Into
("PO"."PO_REQUISITION_LINES_ALL"."DELIVER_TO_LOCATION_ID")

DATA CORRUPTION

Some times the shopping cart gets corrupted and needs to be deleted. There are two options, you can set
the requisition tied to the shopping cart as a SAVED CART and then run the concurrent 'Purge System
Saved Requisition' request in order to purge it, or you can delete the active shopping cart with the
following queries.

Note: If you choose to delete the shoppig cart, the requisition number tied to it will not be used anymore.

To switch the shopping cart to a Saved cart run the following query:

UPDATE po_requisition_headers_all
SET active_shopping_cart_flag = NULL
WHERE requisition_header_id = 2087;

To delete the active shopping cart run the following queries:

DELETE po_requisition_headers_all
WHERE requisition_header_id = ( select h.requisition_header_id
from po_requisition_headers_all h,
fnd_user u
where h.preparer_id = u.employee_id
and h.active_shopping_cart_flag = 'Y'
and u.user_name = upper('&user_name'));

DELETE po_req_distributions_all
WHERE requisition_line_id IN
(SELECT requisition_line_id
FROM po_requisition_lines_all
WHERE requisition_header_id = ( select h.requisition_header_id
from po_requisition_headers_all h,
fnd_user u
where h.preparer_id = u.employee_id
and h.active_shopping_cart_flag = 'Y'
and u.user_name = upper('&user_name')));
DELETE po_requisition_lines_all
WHERE requisition_header_id = ( select h.requisition_header_id
from po_requisition_headers_all h,
fnd_user u
where h.preparer_id = u.employee_id
and h.active_shopping_cart_flag = 'Y'
and u.user_name = upper('&user_name'));

REFERENCES

Note 290614.1 - How To Get Log Files In iProcurement

Attachments

p2 (44.6 KB)
p4 (59.07 KB)
p5 (47.81 KB)
p6 (41.29 KB)
Related

Products

 Oracle E-Business Suite > Procurement > Procurement > Oracle iProcurement

Keywords

ADD ITEMS; OA FRAMEWORK; POR_CUSTOM_PKG; SHOPPING CART;

SHOPPINGCARTCO.JAVA
Errors

ORA-1400

Back to top

Rate this document

Article Rating Comments
Rate this document

Excellent

Good

Poor

Did this document help you?

Yes
 No

Just browsing

How easy was it to find this document?

Very easy

Somewhat easy

Not easy

Important Note: this feedback may be anonymously visible to other

customers until processed by Oracle Support.

Cancel