Anda di halaman 1dari 66

Oracle Purchasing Release Notes for Release Procurement Family

R12.1.3 September Update 2012 (Doc ID 1496104.1)

Modified:Mar 14, 2013 Type:BULLETIN


Status:PUBLISHED
Priority:3

Comments
(0)

In this Document
Purpose

Scope

Details

1. What's New

2. Documentation

2.1 New and Changed Features Documentation

2.2 Technical Documentation

2.2.1 Data Model Comparison Report

2.2.2 EBS ATG Seed Data Comparison Report

2.3 Integration Repository

To
Bottom

2.4 White Papers

3. New and Changed Features

3.1 Use Oracle Approvals Management (AME) for Purchase Order (PO) Review,
Approval, and E-Signature

3.2 Withdraw Purchase Orders

3.3 Create Global Blanket Purchase Agreement (GBPA) with Outside


Processing (OSP) Line Type

3.4 Use New Purchasing Menus in Buyer Work Center

3.5 Automatic Updates to General Ledger (GL) Date

3.6 Enable All Vendor Sites for Global Contract Purchase Agreements (GCPA)
in Buyer Work Center (BWC)

3.7 Validate Standard Purchase Orders (PO) and Agreements in Buyer Work
Center (BWC)

3.8 Changes in Business Rules of Cancel Action Functionality

3.9 View Correct Action Status for Purchasing Documents

3.10 View Supplier Name and Site in Purchase Order Notification Email to

Suppliers

4. Diagnostics and Logging

5. Known Issues in Oracle Purchasing Release Procurement Family R12.1.3


September Update 2012

6. Change Record

7. Documentation Accessibility

Access to Oracle Support

Copyright Notice

License Restrictions Warranty/Consequential Damages Disclaimer

Warranty Disclaimer

Restricted Rights Notice

Hazardous Applications Notice

Trademark Notice

Third Party Content, Products, and Services Disclaimer

References

Applies to:
Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.
Purpose
This document provides delta information from Release 12.1. 3 to Release
Procurement Family R12.1.3 September Update 2012.
Scope
The information included in this document assumes that you have already installed
Oracle Purchasing Release Procurement Family R12.1.3 September Update 2012.

Details
1. What's New
In Release Procurement Family R12.1.3 September Update 2012, Oracle Purchasing
has added or changed the following features since its last release.

Feature Name

Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.

Wtih this release, Oracle Purchasing provides the flexibility to


add any individual or a group of individuals to the approval
hierarchy (position or supervisor) so that purchase orders can
be routed for review, approval, and e-signature. To setup and
use this feature, Oracle Purchasing provides a new AME
Use Oracle
transaction type and workflow process. Depending on
Approvals
business requirements, Purchasing administrators can setup
Management
either parallel or serial process in AME for purchase order
(AME) for Purchase
review, approval, and e-signature. Voting method can be First
Order (PO) Review,
responder wins, Consensus, or Serial. Enterprises can use the
Approval, and Epredefined AME transaction type and PO workflow process or
Signature
they can create custom transaction type and workflow
process based on the supplied components.
This feature provides a new configurable region to enable
enterprises to personalize the notification page according to
their business requirements. On the Action History page,
buyers can view information about approvers using the new
Current/Pending Approvers region, which shows the AME
sequence, person name, and approver type.
Buyers can now withdraw purchase orders that are at the In
Process or Pre-Approved status.
Purchasing administrators can control the buyers ability to
withdraw purchase orders and define whether withdrawal
Withdraw Purchase
notifications can be sent when purchase orders are
Orders
withdrawn. These controls can be defined in the new
Document Controls region of the Document Style page.
Note : The Withdraw PO feature is supported in OAF pages
only and not supported in Forms.
Create Global
Blanket Purchase
Agreement (GBPA)
with Outside
Processing (OSP)
Line Type

With this release, Oracle Purchasing enables buyers to create


global blanket purchase agreements (GBPA) with outside
processing (OSP) line type. Buyers can now select the Outside
Processing (OSP) line type when they create GBPAs using
Buyer Work Center or Purchase Orders window. Prior to this
release, only blanket purchase agreements supported outside

Feature Name

Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.

Wtih this release, Oracle Purchasing provides the flexibility to


add any individual or a group of individuals to the approval
hierarchy (position or supervisor) so that purchase orders can
be routed for review, approval, and e-signature. To setup and
use this feature, Oracle Purchasing provides a new AME
Use Oracle
transaction type and workflow process. Depending on
Approvals
business requirements, Purchasing administrators can setup
Management
either parallel or serial process in AME for purchase order
(AME) for Purchase
review, approval, and e-signature. Voting method can be First
Order (PO) Review,
responder wins, Consensus, or Serial. Enterprises can use the
Approval, and Epredefined AME transaction type and PO workflow process or
Signature
they can create custom transaction type and workflow
process based on the supplied components.
This feature provides a new configurable region to enable
enterprises to personalize the notification page according to
their business requirements. On the Action History page,
buyers can view information about approvers using the new
Current/Pending Approvers region, which shows the AME
sequence, person name, and approver type.
Buyers can now withdraw purchase orders that are at the In
Process or Pre-Approved status.
Purchasing administrators can control the buyers ability to
withdraw purchase orders and define whether withdrawal
Withdraw Purchase
notifications can be sent when purchase orders are
Orders
withdrawn. These controls can be defined in the new
Document Controls region of the Document Style page.
Note : The Withdraw PO feature is supported in OAF pages
only and not supported in Forms.
Create Global
Blanket Purchase
Agreement (GBPA)
with Outside
Processing (OSP)
Line Type

With this release, Oracle Purchasing enables buyers to create


global blanket purchase agreements (GBPA) with outside
processing (OSP) line type. Buyers can now select the Outside
Processing (OSP) line type when they create GBPAs using
Buyer Work Center or Purchase Orders window. Prior to this
release, only blanket purchase agreements supported outside

Feature Name

Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.

Wtih this release, Oracle Purchasing provides the flexibility to


add any individual or a group of individuals to the approval
hierarchy (position or supervisor) so that purchase orders can
be routed for review, approval, and e-signature. To setup and
use this feature, Oracle Purchasing provides a new AME
Use Oracle
transaction type and workflow process. Depending on
Approvals
business requirements, Purchasing administrators can setup
Management
either parallel or serial process in AME for purchase order
(AME) for Purchase
review, approval, and e-signature. Voting method can be First
Order (PO) Review,
responder wins, Consensus, or Serial. Enterprises can use the
Approval, and Epredefined AME transaction type and PO workflow process or
Signature
they can create custom transaction type and workflow
process based on the supplied components.
This feature provides a new configurable region to enable
enterprises to personalize the notification page according to
their business requirements. On the Action History page,
buyers can view information about approvers using the new
Current/Pending Approvers region, which shows the AME
sequence, person name, and approver type.
Buyers can now withdraw purchase orders that are at the In
Process or Pre-Approved status.
Purchasing administrators can control the buyers ability to
withdraw purchase orders and define whether withdrawal
Withdraw Purchase
notifications can be sent when purchase orders are
Orders
withdrawn. These controls can be defined in the new
Document Controls region of the Document Style page.
Note : The Withdraw PO feature is supported in OAF pages
only and not supported in Forms.
Create Global
Blanket Purchase
Agreement (GBPA)
with Outside
Processing (OSP)
Line Type

With this release, Oracle Purchasing enables buyers to create


global blanket purchase agreements (GBPA) with outside
processing (OSP) line type. Buyers can now select the Outside
Processing (OSP) line type when they create GBPAs using
Buyer Work Center or Purchase Orders window. Prior to this
release, only blanket purchase agreements supported outside

Feature Name

Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.

Wtih this release, Oracle Purchasing provides the flexibility to


add any individual or a group of individuals to the approval
hierarchy (position or supervisor) so that purchase orders can
be routed for review, approval, and e-signature. To setup and
use this feature, Oracle Purchasing provides a new AME
Use Oracle
transaction type and workflow process. Depending on
Approvals
business requirements, Purchasing administrators can setup
Management
either parallel or serial process in AME for purchase order
(AME) for Purchase
review, approval, and e-signature. Voting method can be First
Order (PO) Review,
responder wins, Consensus, or Serial. Enterprises can use the
Approval, and Epredefined AME transaction type and PO workflow process or
Signature
they can create custom transaction type and workflow
process based on the supplied components.
This feature provides a new configurable region to enable
enterprises to personalize the notification page according to
their business requirements. On the Action History page,
buyers can view information about approvers using the new
Current/Pending Approvers region, which shows the AME
sequence, person name, and approver type.
Buyers can now withdraw purchase orders that are at the In
Process or Pre-Approved status.
Purchasing administrators can control the buyers ability to
withdraw purchase orders and define whether withdrawal
Withdraw Purchase
notifications can be sent when purchase orders are
Orders
withdrawn. These controls can be defined in the new
Document Controls region of the Document Style page.
Note : The Withdraw PO feature is supported in OAF pages
only and not supported in Forms.
Create Global
Blanket Purchase
Agreement (GBPA)
with Outside
Processing (OSP)
Line Type

With this release, Oracle Purchasing enables buyers to create


global blanket purchase agreements (GBPA) with outside
processing (OSP) line type. Buyers can now select the Outside
Processing (OSP) line type when they create GBPAs using
Buyer Work Center or Purchase Orders window. Prior to this
release, only blanket purchase agreements supported outside

Feature Name

Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.

Wtih this release, Oracle Purchasing provides the flexibility to


add any individual or a group of individuals to the approval
hierarchy (position or supervisor) so that purchase orders can
be routed for review, approval, and e-signature. To setup and
use this feature, Oracle Purchasing provides a new AME
Use Oracle
transaction type and workflow process. Depending on
Approvals
business requirements, Purchasing administrators can setup
Management
either parallel or serial process in AME for purchase order
(AME) for Purchase
review, approval, and e-signature. Voting method can be First
Order (PO) Review,
responder wins, Consensus, or Serial. Enterprises can use the
Approval, and Epredefined AME transaction type and PO workflow process or
Signature
they can create custom transaction type and workflow
process based on the supplied components.
This feature provides a new configurable region to enable
enterprises to personalize the notification page according to
their business requirements. On the Action History page,
buyers can view information about approvers using the new
Current/Pending Approvers region, which shows the AME
sequence, person name, and approver type.
Buyers can now withdraw purchase orders that are at the In
Process or Pre-Approved status.
Purchasing administrators can control the buyers ability to
withdraw purchase orders and define whether withdrawal
Withdraw Purchase
notifications can be sent when purchase orders are
Orders
withdrawn. These controls can be defined in the new
Document Controls region of the Document Style page.
Note : The Withdraw PO feature is supported in OAF pages
only and not supported in Forms.
Create Global
Blanket Purchase
Agreement (GBPA)
with Outside
Processing (OSP)
Line Type

With this release, Oracle Purchasing enables buyers to create


global blanket purchase agreements (GBPA) with outside
processing (OSP) line type. Buyers can now select the Outside
Processing (OSP) line type when they create GBPAs using
Buyer Work Center or Purchase Orders window. Prior to this
release, only blanket purchase agreements supported outside

Return to What's New


Top

2. Documentation
This section provides information on the following topics:
2.1 New and Changed Features Documentation
2.2 Technical Documentation
2.3 Integration Repository
2.4 White Papers
Top

2.1 New and Changed Features Documentation


This document provides information on the new features and enhancements added
in Oracle Purchasing in Release Procurement Family R12.1.3 September Update
2012.
Return to Documentation
Top
2.2 Technical Documentation
The following technical documentation is available:
Oracle Electronic Technical Reference Manuals (eTRM)
Transfer of Information (TOI) Online Training
First-time TOI users: Follow the setup instructions in Document 403349.1
2.2.1 Data Model Comparison Report
The EBS Data Model Comparison Report lists the database object definition changes
between two Oracle E-Business Suite releases to help users to preview the database
object definition changes before upgrading their instances from one release to
another and understand the impact of the database object changes that may affect
the customization or business flows.

For more information about the EBS Data Model Comparison report, see the EBS
Data Model Comparison Report Overview Document 1290886.1.
2.2.2 EBS ATG Seed Data Comparison Report
The EBS ATG Seed Data Comparison Report lists the differences between two Oracle
E-Business Suite releases by documenting the seed data changes delivered by the
product data loader files (.ldt extension) based on the ATG loader control files (.lct
extension). This report enables advanced users to review changes prior to an
upgrade.
For more information about the EBS ATG Seed Data Comparison Report, see
Document 1327399.1.
Return to Documentation
Top
2.3 Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints displayed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool
lets users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the E-Business Suite. As your
instance is patched, the repository is automatically updated with content
appropriate for the precise revisions of interfaces in your environment.
You can navigate to the Oracle Integration Repository through Oracle E-Business
Suite Integrated SOA Gateway.
Return to Documentation
Top
2.4 White Papers
There are no relevant white papers for this product in this release.
Return to Documentation
Top

3. New and Changed Features

In Release Procurement Family R12.1.3 September Update 2012, Oracle Purchasing


has added or changed the following features since its last release.
Use this section to access the following delta information for each feature:
New, Changed, Obsolete Components
Implementation Considerations
Customizations and Extensions
Minimum Level Requirements
Technology Stack Incompatibilities
Technology Architecture Considerations
Troubleshooting Tips
This release provides the following new features and enhancements:
3.1 Use Oracle Approvals Management (AME) for Purchase Order (PO) Review,
Approval, and E-Signature
3.2 Withdraw Purchase Orders
3.3 Create Global Blanket Purchase Agreement (GBPA) with Outside Processing
(OSP) Line Type
3.4 Use New View Purchasing Documents Menus in Buyer Work Center
3.5 Automatic Updates to General Ledger (GL) Date
3.6 Enable All Vendor Sites for Global Contract Purchase Agreements (GCPA) in
Buyer Work Center (BWC)
3.7 Validate Standard Purchase Orders (PO) and Agreements in Buyer Work Center
(BWC)
3.8 Changes in Business Rules of Cancel Action Functionality
3.9 View Correct Action Status for Purchasing Documents
3.10 View Supplier Name and Site in Purchase Order Notification Email to Suppliers
Top

3.1 Use Oracle Approvals Management (AME) for Purchase Order (PO) Review,
Approval, and E-Signature

Description Currently, purchase orders can be routed for approval to only


approvers defined in a position hierarchy or supervisor
hierarchy.
In a typical business environment, purchasing organizations
require:
Documents to be reviewed before approval to comply with
the organization review policy. For example, computer or
server purchases must be reviewed by the IT manager before
approval.
Flexible approval hierarchy to get approval from individuals
or group of individuals along with people listed in the
standard hierarchy. For example, purchase of hazardous
material requires approval from Manager Safety and PO
approval hiearchy.
Multiple signatories to sign purchasing documents. For
example, based on item or total purchase amount, document
requires e-signatures of business unit head and director.
Wtih this release, Oracle Purchasing provides the flexibility to
add any individual or a group of individuals to the approval
hierarchy (position or supervisor) so that purchase orders can
be routed for review, approval, and e-signature. To setup and
use this feature, Oracle Purchasing provides a new AME
transaction type and workflow process. Depending on
business requirements, Purchasing administrators can setup
either parallel or serial process in AME for purchase order
review, approval, and e-signature. Voting method can be First
responder wins, Consensus, or Serial. Enterprises can use the
predefined AME transaction type and PO workflow process or
they can create custom transaction type and workflow
process based on the supplied components. This feature
provides a new configurable region to enable enterprises to
personalize the notification page according to their business
requirements. On the Action History page, buyers can view
information about approvers using the new Current/Pending
Approvers region, which shows the AME sequence, person
name and approver type.
To use the new AME feature for PO review, approval and esignature, purchasing administrators must:

Define Oracle Approvals Management (AME) setup using


either the parallel or serial approval process or a combination
of the processes.
Select the approval workflow, workflow startup process, and
AME transaction type in the Document Controls region of the
Document Styles page.
For information on setup steps, refer to the New and Changed
Setup Steps section.
The following business rules apply during the purchase order
review:
Reviewers have view only access to the document when they
receive notifications for review.
Buyers cannot update the purchase order if the order is in the
In Process or Pre-Approved status.
Reviewers can reject or accept document and add comments
when reviewing purchase orders.
Note: Buyers cannot manually add reviewers in the Add
Adhoc Approver region of the Approval Options page. They
can add approvers and e-signers only.
The following business rules apply during the purchase order
approval:
Buyers have the flexibility to send purchase order documents
to approvers, reviewers, or e-signers based on the AME
setup.
Approvers can edit purchase orders when they receive the
approval notification.
If the e-signature feature is not enabled, then the purchase
order status is set to Approved after all approvals are in.
Approvers can approve, approve and forward, reject, or
reassign the purchase order notification. They can add their
comments to the notification page.
The following business rules apply if the e-signature
functionality is used:
Notifiers who receive the notification for e-signature have

view only access to the document.


E-signature can be provided during the post approval phase
only. During the post approval process, approvers cannot be
added and document cannot be sent for approval.
If the purchase order is rejected during the approval, review,
or e-signature stage, then the status of the purchase order
changes to Rejected. Buyers can update and resubmit such
rejected purchase orders.
Note:
Oracle Purchasing supports this functionality for purchase
orders in both OAF pages and in Forms. Purchase orders
created in both Buyer Work Center (OAF pages) and Forms
can be routed for review, approval, and multiple e-signatures.
The following restrictions apply to the use of this functionality
in Oracle Purchasing:
The Current/Pending Approvers information in Action History
is not supported in Forms. This information is available in the
Action History OAF page only.
AME cannot be used for Planned purchase orders and
purchase order releases.
AME cannot be used for local blanket purchase agreements. If
you want to use the AME feature, then use global blanket
purchase agreements.
System Implications: Impact of the New Document Controls
Region in the Document Style Page
Currently, the approval workflow and workflow start process
can be defined at the document type level. With this release,
Oracle Purchasing introduces a new Document Controls
region in the Document Style page. If PO AME Approval Top
Process is defined as the workflow startup process, then
document style definition overrides the setting at the
document type level. If you want to use the standard Oracle
Purchasing approval process and do not want to use AME,
then the Approval Workflow, Workflow Startup Process, and
AME Transaction Type fields in the Document Controls region
of the Document Style page must be left blank (Null).

New,
Changed,
Obsolete
Component
s

This section lists the components that were added, changed,


or made obsolete for this feature in Oracle Purchasing in
Release Procurement Family R12.1.3 September Update
2012. These components may include the following: forms,
windows, reports, C programs, SQL*Loader programs,
workflows, alerts, tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
Changed Windows or Pages
This table lists the changed windows and pages.
Changed
Technical
Window or Name
Page Name

Description

Document
Style

New Document Controls


region is available.

StyleEditPG

To use AME for purchase


order review, approval
and e-signature, the
following fields must be
defined:
Approval Workflow: Select
either the predefined PO
Approval workflow item
type or custom workflow
item type.
Workflow Startup Process:
Select either the
predefined PO AME
Approval Top Process or
custom process.
AME Transaction Type:
Select either the Purchase
Order Approval value or
custom AME transaction
type.

Note: If the approval


workflow and workflow
startup process are
defined at the document
style level, then these
values defined at the
style level take
precedence over the
document type definition.
If approval workflow and
workflow startup process
are not defined at the
document style level,
then the application
considers the values
defined at the document
type level.
Action
History

ActionHistory
PG

Current/Pending
Approvers region
(PoAMECurrentFutureAppr
oversRN) is added to the
Action History page which
shows AME Sequence No,
Person name and
Approver Type of
current/future approvers.
The following action
codes are available:
Review Accepted
Review Rejected
Approve and Forward
Signer Rejected
First Reminder
Second Reminder
Timed Out
The application records
the First and Second

Implement New and Changed Setup Steps


ation
Considerati This section lists the setup steps that were added or changed
for Oracle Purchasing in Release Procurement Family R12.1.3
ons
September Update 2012.
To use Oracle Approvals Management (AME) feature for
purchase order review, approval, e-signature, complete the
following steps:
Completing Setup Steps using Oracle Approvals Management
(AME):
Note that this setup assumes that purchase orders are routed
for review, approval, and e-signature. This setup also
assumes that the predefined Purchase Order Approval
transaction type is used. Oracle Purchasing provides flexibility
to define parallel or serial process and use the following
voting methods First responder wins, Consensus, or Serial.
The processes and voting methods described in this setup are
for example only.
In this example, in addition to the the supervisor hierarchy
that is used for PO approval, the purchasing administrator
completes the setup for approvers (additional), reviewers,
and signers.
Navigate to the Approvals Management Administrator
responsibility.
Search for the Purchase Order Approval (PURCHASE_ORDER)
transaction type.
View the item classes, mandatory attributes, and
configuration variables.
Navigate to the Approvals Management Business Analyst
responsibility.
Select the Business Analyst Dashboard menu.
Search for the Purchase Order Approval transaction type. In
this example setup, you will use the predefined attributes. If
required, you can create conditions based on your business
requirements.

Create rules.
For example:
Approver Rule with following values:
Rule Type = List Creation
Category = Approver
Condition
Action Type = Supervisory level
Action = Require approvals up to the first superior.
Reviewer Rule with the following values:
Rule Type = Combination (While creating rule for reviewers,
you must choose Combination: List Creation or
Combination:List Modification rule type)
Category = Approver
Condition
Action Type = Production rule and Action = Reviewer/Yes
(reviewer is identified through Production rule and the
Reviewer/Yes action).
Action Type = approval-group chain of authority and selectan
appropriate Action value.
Signer Rule with the following values:
Rule Type = Post List Approver Group(while creating rule for
signers, you must select the Post List Approver Group. All
persons with this rule type are recognised assigners).
Category = Approver
Condition
Action Type = post-chain-of-authority approvals. Note that for
approver and review rules, you can use any action type. But
for signer, you must select post chain of authority approvals
as the action type.

Create approver groups.


For example:
Approver group, where the voting method is Serial and select
the approvers. Note that these are additional approvers, in
addition to the people listed in the supervisor hierarchy.
E-signature group, where the voting method is Serial and
select the individuals who have to provide the e-signature.
Review group, where the voting method is First Responder
Wins and select the individuals who will review documents.
Test your setup using Test Workbench feature.
Completing Setup Steps in Oracle Purchasing
Enabling AME for a document is controlled at Style Level. To
use the AME feature for purchase document review, approval,
and e-signature, complete the following steps:
Navigate to the Purchasing responsibility.
Select Document Styles (Setup > Purchasing). You can create
a document style or update an existing document style.
Navigate to the Document Controls region in the Create
Document Style (StyleEditPG) or Update Document Style
(StyleEditPG).
Ensure that you make the following selections to enable AME
for a purchasing document. This example uses predefined
values.
PO Approval in the Approval Workflow field.
PO AME Approval Top Process in the Workflow Startup Process
field.
Purchase Order Approval in the AME Transaction Type.
After you complete these setup steps and when buyers click
Approval Options for purchase orders or agreements, Oracle
Purchasing displays the Approvers region (AME Approval
region). Based on the setup, the Approvers region displays
approvers, reviewers, and signers. In the Add Adhoc Approver
region, buyers can select adhoc approvers or individuals for

e-signature. They cannot select reviewers. Only if a person is


added in the post or after post approval group, then that
person is recognized as the signer. Therefore, buyers must
select an existing signer and then add an individual before or
after the existing signer using insertion point.
Buyers can identify reviewers and signers in the Approvers
region using the action type. Signers are associated with the
post-chain-of-authority approvals action type. Reviewers are
associated with the Production rule action type. Oracle
Purchasing routes the document for review, approval, and esignature based on the AME and workflow rules setup.
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.
New Bulk Interfaces
There are no new bulk interfaces for this feature.
Customizati Customizations and extensions are not possible for this
ons and
feature.
Extensions
Minimum
Level
Requireme
nts

There are no minimum level requirements for this feature.

Technology There are no technology stack incompatibilities for this

Stack
feature.
Incompatibi
lities
Technical
There are no technology architecture considerations for this
Architectur feature.
e
Considerati
ons
Troublesho
oting Tips

There are no troubleshooting tips for this feature.

Return to New and Changed Features


Top
3.2 Withdraw Purchase Orders
Descripti Buyers can now withdraw purchase orders that are at the In
on
Process or Pre-Approved status. When withdrawing a PO, buyers
can specify the withdrawal reason. If the purchase order is
approved, then the buyer cannot withdraw the purchase order
and needs to create a purchase order revision.
When a buyer withdraws a document and if in the Document
Style page, the Send Withdrawal Notification check box is
selected, then Oracle Purchasing sends notification to current
approvers and approvers who have already approved the
document. Future approvers do not receive any withdrawal
notification. After a purchase order is successfully withdrawn,
the Action History region displays the action as withdrawn and
the withdrawal reason. The status of the withdrawn purchase
order is set to Incomplete or Requires Reapproval based on
which stage the document is in the approval cycle. Revised
purchase orders can be withdrawn if they are not approved.
Purchasing administrators can control the buyers ability to
withdraw purchase orders and define whether withdrawal
notifications can be sent when purchase orders are withdrawn.
These controls are available in the Document Controls region of
the Document Style page.
Note : The Withdraw PO feature is supported in OAF pages only

and not supported in Forms.


New,
Changed,
Obsolete
Compone
nts

This section lists the components that were added, changed, or


made obsolete for this feature in Oracle Purchasing in Release
Procurement Family R12.1.3 September Update 2012. These
components may include the following: forms, windows,
reports, C programs, SQL*Loader programs, workflows, alerts,
tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
New Windows or Pages
This table lists the new windows and pages.
New Window or
Page Name

Technical Description
Name

Withdraw

Withdra
wPG

New page to withdraw


purchase order that is at
the In Process or PreApproved status. This
page appears when buyer
selects the Withdraw
action for a document in
the Orders page. Buyer
can provide the
withdrawal reason and this
information appears in the
withdrawal email
notification. Purchasing
sends withdrawal
notification to approvers
depending on the
definition set by the
purchasing administrator
in the Document Controls
region of the Document
Style page.
If the withdrawal is
successful, then the Action

History of the purchase


order is updated with the
Withdraw action and the
reason is recorded. All
approvers who approved
the document and
approvers whose approval
is pending are sent FYI
withdrawal notifications.
Changed Windows or Pages
This table lists the changed windows and pages.
Changed
Window or
Page Name

Technical Name

Description

Document
Style

StyleEditPG

New Document
Controls region
(DocControlsHdrRN)
provides the
following new control
fields for a document
style. Purchasing
administrator can
define these controls:
Allow Document
Withdrawal: If this
check box is
selected, then buyers
can withdraw
purchasing
documents. By
default, this check
box is selected.
Send Withdrawal
Notifications to all
Approvers: If this
check box is
selected, then

approvers receive FYI


notifications when
buyers withdraw
purchasing
documents. By
default, this check
box is selected.
Orders

OrdersSummaryHe
adersPG

New action Withdraw


is available in the
Order Action list. The
Withdraw action is
available for
documents that are
at the In Process or
Pre-Approved status.
When a buyer selects
this action, the new
Withdraw page
appears.

Action
History

ActionHistoryPG

Displays the action


as Withdraw if a
buyer withdraws the
purchasing document
along with sequence,
date and time of the
withdrawal and
person who has
withdrawn the
document.

New Function
This table lists new function.
New Technica Description
Funct l Name
ion
Name
Withd PO_WITH HTML Call: OA.jsp?

raw
DRAW
Docu
ment
Page

page=/oracle/apps/po/document/comm
on/webui/WithdrawPG
This function is associated with the Po
Order Tab (PO_ORDER_TAB) menu.

Changed Workflows
This table lists the changed workflows.
New Workflow
Name

Technical
Name

Description

PO AME Approval poxwfpoa This workflow item type


Top Process
.wft
includes a new PO AME
Approval Top Process that
provides a new message:
PO_WITHDRAWN. When a
buyer withdraws a
purchase order, a FYI
notification is sent to
approvers who have
approved the order and to
approvers who are yet to
approve the order.
Impleme New and Changed Setup Steps
ntation
Consider This section lists the setup steps that were added or changed
for Oracle Purchasing in Release Procurement Family R12.1.3
ations
September Update 2012.
To enable buyers to withdraw purchase orders, purchasing
administrators must complete the following steps:
Log in to the Oracle Purchasing responsibility.
Navigate to the Document Controls region of the Document
Style page (Setup > Purchasing > Document Styles).
Select the following Withdrawal Options:
Allow Document Withdrawal

Send Withdrawal Notifications to All Approvers


Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.
New Bulk Interfaces
There are no new bulk interfaces for this feature.
Customiz Customizations and extensions are not possible for this feature.
ations
and
Extensio
ns
Minimum There are no minimum level requirements for this feature.
Level
Requirem
ents
Technolo There are no technology stack incompatibilities for this feature.
gy Stack
Incompat
ibilities
Technical There are no technology architecture considerations for this
Architect feature.
ure
Consider

ations
Troublesh There are no troubleshooting tips for this feature.
ooting
Tips
Return to New and Changed Features
Top
3.3 Create Global Blanket Purchase Agreement (GBPA) with Outside Processing
(OSP) Line Type
Description

With this release, Oracle Purchasing enables buyers to


create global blanket purchase agreements (GBPA) with
outside processing (OSP) line type. Buyers can now select
the Outside Processing (OSP) line type when they create
GBPAs using Buyer Work Center or Purchase Orders
window. Prior to this release, only blanket purchase
agreements supported outside processing line types.
Using the Purchase Orders window, blanket purchase
agreement with OSP line type can be copied to the global
blanket purchase agreement . The Import Price Catalogs
process supports importing GBPAs with OSP line types.
Purchasing administrators can select Outside Processing as
the default line type in the Document Controls region of
the Purchasing Options page for organizations. This default
value appears automatically as the line type when buyers
create GBPAs using Purchase Orders window or the
Agreement Line Details page in Buyer Work Center.
In addition, the following changes are available with this
enhancement:
GPBA, Controls tab region changes:
In the Operating Unit Access region, buyers can select
multiple requesting and purchasing operating units.
In the Automatic Processes region, if the Enable Automatic
Sourcing option is selected, then Sourcing rules are
created for OSP item. If the Update Sourcing Rules and
Assignments option is selected, then existing sourcing

rules are updated for the OSP item.


Standard Purchase Order - Lines tab region changes:
Buyers can:
Select a GBPA document with OSP line type in the Source
Document region.
Copy GBPA with OSP line to a new line using the Duplicate
option in the Action column.
Select Recalculate Price option to update the Price field
based on the selected GBPA with OSP item.
Autocreate and ASL changes:
Buyers can:
Search for a GBPA with OSP item for New Order type in
Document Builder when autocreating purchase orders.
Purchasing enables auto creation of purchase order based
on sourcing rules when a requisition is auto created for the
OSP item based on the job or operation release type. In the
auto created purchase order, the price of the OSP item is
updated based on the GBPA.
Select GBPA document in the Source Documents tab when
mapping supplier item attribute.
New,
Changed,
Obsolete
Components

This section lists the components that were added,


changed, or made obsolete for this feature in Oracle
Purchasing in Release Procurement Family R12.1.3
September Update 2012. These components may include
the following: forms, windows, reports, C programs,
SQL*Loader programs, workflows, alerts, tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
Changed Windows or Pages
This table lists the changed windows and pages.
Changed

Technical Name

Description

Window or
Page
Name
Purchasing PurchasingOptionsP In the Document
Options
G
Control region,
Line Type field, the
Outside
processing value
is available to set
as the default
option.
Update
Line

AgreementLineDeta Outside
ilsPG
processing line
type value is
available in the
Line Type field.

Purchase
Orders

POXPOEPO

Following change
are supported in
this window:
Outside
processing line
type value is
available in the
Line Type field for
GBPAs.
Copying blanket
purchase
agreement with
outside processing
line type to global
blanket purchase
agreement is now
supported .

Changed Programs
This table lists the changed programs.

Program Name

Description

Import Price
Catalogs
(POXPDOI)

This process now supports


importing global blanket
purchase agreements with
outside processing line type.

Implementati New and Changed Setup Steps


on
Consideration This section lists the setup steps that were added or
changed for Oracle Purchasing in Release Procurement
s
Family R12.1.3 September Update 2012.
To default Outside processing as the line type in GBPAs,
purchasing administrators can select Outside processing
value in the Purchasing Options page, Document Control
region, Line Type field.
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.
New Bulk Interfaces
There are no new bulk interfaces for this feature.
Customization Customizations and extensions are not possible for this
s and
feature.
Extensions

Minimum
There are no minimum level requirements for this feature.
Level
Requirements
Technology
There are no technology stack incompatibilities for this
Stack
feature.
Incompatibiliti
es
Technical
There are no technology architecture considerations for
Architecture
this feature.
Consideration
s
Troubleshooti
ng Tips

There are no troubleshooting tips for this feature.

Return to New and Changed Features


Top
3.4 Use New Purchasing Menus in Buyer Work Center
Description Oracle Purchasing now offers the following new menus:
View Purchasing Documents
(PO_VIEW_PURCHASING_DOCUMENTS): This menu enables
buyers to view all details of purchase orders and agreements.
Purchasing administrators can assign this menu to users such
as requesters or project managers who do not have access to
the Purchasing responsibility to view purchasing documents.
Users assigned this menu can only view documents and
cannot perform any update actions.
The following view actions are available for purchase orders:
View Acknowledgments
View Acquisition Cost
View Action History
View Approval Workflow
View Change History

View Invoices
View PDF
View Payments
View Receipts
View Requisitions
View Revision History
The following view actions are available for agreements:
View Acknowledgements
View Action History
View Approval Work Flow
View Change History
View PDF
View Revision History
The view actions that appear in the Actions list in the
Standard Purchase Order or Agreements page depend on the
status of the purchase order or agreement. By default, this
menu is associated with the Purchasing SuperUser GUI
(PO_SUPERUSER_GUI) and Purchasing Buyer Work Center
(PO_BUYER_WORK_CENTER) menus. If enterprises use custom
Purchasing responsibility, then they must grant this menu to
the custom responsibility to enable buyers to view purchasing
documents from Buyer Work Center.
Non-CLM Views (PO_VW_FUNCTIONS): The Non-CLM Views
menu groups the functions that enables access to the
predefined views in the Buyer Work Center. Purchasing
administrators can use this menu to control access to
predefined views. For example, access to the existing
predefined views such as My In Process Orders or My
Incomplete Orders can be granted or revoked using this new
menu. The Non-CLM Views (PO_VW_FUNCTIONS) menu is
associated by default with the predefined Purchasing
SuperUser GUI (PO_SUPERUSER_GUI) and Purchasing Buyer
Work Center (PO_BUYER_WORK_CENTER) menus. If
enterprises use the custom Purchasing responsibility, they

they must grant the Non-CLM Views (PO_VW_FUNCTIONS)


menu to the custom responsibility. Otherwise, views in Buyer
Work Center cannot be accessed.
New,
Changed,
Obsolete
Componen
ts

This section lists the components that were added, changed,


or made obsolete for this feature in Oracle Purchasing in
Release Procurement Family R12.1.3 September Update 2012.
These components may include the following: forms,
windows, reports, C programs, SQL*Loader programs,
workflows, alerts, tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
New Menus
This table lists the new menus.
New
Menu
Name

Technical Name

View
PO_VIEW_PURCHASING_DO
Purchasi CUMENTS
ng
Docume
nts

Description

Prompt:
Orders
Agreements
Submenu
associated with
this menu:
Purchasing
Buyer Home
Page Read Only
view
Functions
associated with
this menu:
PO Orders
Summary Page
For Read Only
View

PO View
Agreements
Summary Page
For Read Only
View
NonCLM
Views

PO_VW_FUNCTIONS

Functions
associated with
this menu:
Pending Change
Requests Orders
Incomplete
Orders
In Process
Orders
Open Orders
Rejected
Acknowledgmen
ts Orders
Expiring
Agreements
Pending Change
Requests
Agreements
Incomplete
Agreements
Rejected
Acknowledgmen
ts Agreements
Requisitions
Requiring RFQ

Changed Menus
This table lists the changed menus.

Chang
ed
Menu
Name

Technical Name

Description

Purcha PO_SUPERUSER_G By default, this predefined


sing
UI
menu includes the two
SuperU
new menus:
ser GUI
View Purchasing
Documents
(PO_VIEW_PURCHASING_D
OCUMENTS)
Non-CLM Views
(PO_VW_FUNCTIONS)

Purcha PO_BUYER_WORK By default, this predefined


sing
_CENTER
menu includes the two
Buyer
new menus:
Work
View Purchasing
Center
Documents
(PO_VIEW_PURCHASING_D
OCUMENTS)
Non-CLM Views
(PO_VW_FUNCTIONS)
Implement New and Changed Setup Steps
ation
Considerati This section lists the setup steps that were added or changed
for Oracle Purchasing in Release Procurement Family R12.1.3
ons
September Update 2012.
If your enterprise uses the custom Purchasing responsibility,
then the Purchasing administrator must grant the following
menus to the custom responsibility:
View Purchasing Documents
(PO_VIEW_PURCHASING_DOCUMENTS) to enable buyers to to
view all details of purchase orders and agreements.

Non-CLM Views (PO_VW_FUNCTIONS) to access views in Buyer


Work Center.
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.
New Bulk Interfaces
There are no new bulk interfaces for this feature.
Customizat Customizations and extensions are not possible for this
ions and
feature.
Extensions
Minimum
There are no minimum level requirements for this feature.
Level
Requireme
nts
Technology There are no technology stack incompatibilities for this
Stack
feature.
Incompatib
ilities
Technical
There are no technology architecture considerations for this
Architectur feature.
e
Considerati
ons

Troublesho There are no troubleshooting tips for this feature.


oting Tips
Return to New and Changed Features
Top
3.5 Automatic Updates to General Ledger (GL) Date
Description

Buyers can specify the GL date (encumbrance date) for


each distribution against a line at the time of creating
purchase orders. If the value of the GL Date is invalid, for
example, the date is in a closed GL period, or in a period
that is not yet open, then the application automatically
defaults the GL date to the system date if the current period
is open. The GL date is also validated during the time the
purchase order is submitted for approval. To use this
feature, the value of the PO: Validate GL Date Period profile
option must be set to the newly introduced Redefault value.

New,
Changed,
Obsolete
Components

This section lists the components that were added,


changed, or made obsolete for this feature in Oracle
Purchasing in Release Procurement Family R12.1.3
September Update 2012. These components may include
the following: forms, windows, reports, C programs,
SQL*Loader programs, workflows, alerts, tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
Changed Windows or Pages
This table lists the changed windows and pages.
Changed
Window or Page
Name

Technical Description
Name

Distributions

POXRQE
RQ

Setting of the PO:


Validate GL Period profile
option impacts the GL
Date field in the
Distributions window.

Purchasing
administrators can set
the PO: Validate GL
Period profile option
value to Redefault, so
that the GL date is
automatically corrected
to the system date, if
found invalid.
Changed Profile Options
This table lists the changed profile options.
Profile Option
Name

Feature
Area

Description

PO:Validate GL
Period

GL Date
in
purchase
order
distributio
ns and
requisitio
n
distributio
ns

This existing profile


option controls the
validation of the GL
Date in purchase order
distributions and
requisition distributions.
Currently, two values
are available for this
profile option:
Yes: The application
verifies the GL date and
displays an error
message if the date is
invalid, for example, the
date is in a closed GL
period or in a period
that is not yet open.
Buyers must modify the
date to reflect a valid
date. Yes is the default
value.
No: The application
does not validate the GL

date.
With this release, a new
Redefault value is
available. Purchasing
administrators can
select this value, so that
if the date is found
invalid, for example, the
date is in a closed GL
period, or in a period
that is not yet open, the
application
automatically corrects
the GL date to reflect
the current system date.
A message informs the
buyer that the GL date
is updated
automatically.
Changed Public APIs
This table lists the changed APIs.
Changed API
Name

Description

POXCOPES.pls

Includes a new procedure


PO_PERIODS_SV.build_GL_Encumber
ed_Date to build the GL Date and
Period Name when the PO:Validate
GL Period profile option is set to
Redefault.

New Custom Hook


This table lists the new custom hook.
Custom Hook

Description

PO_CUSTOM_FUNDS_PK A new procedure gl_date


G.plb
(PO_CUSTOM_FUNDS_PKG.g

l_date) is available to write


custom code to default the
GL Date.
Implementat New and Changed Setup Steps
ion
Consideratio This section lists the setup steps that were added or
changed for Oracle Purchasing in Release Procurement
ns
Family R12.1.3 September Update 2012.
To automatically correct the invalid GL date to system date,
complete the following steps:
Log in to the System Administrator responsibility.
Navigate to the System Profiles window.
Search for the PO:Validate GL Period profile option.
Select the Redefault value at the appropriate level.
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.
New Bulk Interfaces
There are no new bulk interfaces for this feature.

Customizatio Using the PO_CUSTOM_FUNDS_PKG.plb custom hook,


ns and
custom code can be written to default the GL date.
Extensions
Minimum
There are no minimum level requirements for this feature.
Level
Requirement
s
Technology
There are no technology stack incompatibilities for this
Stack
feature.
Incompatibili
ties
Technical
There are no technology architecture considerations for this
Architecture feature.
Consideratio
ns
Troubleshooti There are no troubleshooting tips for this feature.
ng Tips
Return to New and Changed Features
Top
3.6 Enable All Vendor Sites for Global Contract Purchase Agreements (GCPA) in
Buyer Work Center (BWC)
Description

Buyers can now enable global contract purchase


agreements for all valid purchasing sites using the new
Enable All Sites check box in the Controls tab of the
Contract Purchase Agreement page. This helps buyers as
they need not manually select purchasing sites for each
GCPA. Buyers can select this check box for incomplete
GCPAs only. Standard purchase orders in BWC with same
supplier but different supplier site can reference GCPAs
with enable all sites option as source documents.

New, Changed, This section lists the components that were added,
Obsolete
changed, or made obsolete for this feature in Oracle
Components
Purchasing in Release Procurement Family R12.1.3
September Update 2012. These components may include

the following: forms, windows, reports, C programs,


SQL*Loader programs, workflows, alerts, tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
Changed Windows or Pages
This table lists the changed windows and pages.
Changed
Technical Description
Window or Page Name
Name
Contract
Purchase
Agreement

Contract
PG

Enable All Sites check


box is provided in the
Controls tab, Operating
Unit Access region.

Implementatio New and Changed Setup Steps


n
Considerations There are no new or changed setup steps for this feature.
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.
New Bulk Interfaces
There are no new bulk interfaces for this feature.

Customization Customizations and extensions are not possible for this


s and
feature.
Extensions
Minimum Level There are no minimum level requirements for this feature.
Requirements
Technology
Stack
Incompatibiliti
es

There are no technology stack incompatibilities for this


feature.

Technical
There are no technology architecture considerations for
Architecture
this feature.
Considerations
Troubleshootin There are no troubleshooting tips for this feature.
g Tips
Return to New and Changed Features
Top
3.7 Validate Standard Purchase Orders (PO) and Agreements in Buyer Work Center
(BWC)
Description

Oracle Purchasing provides a new Validate Document


action in Buyer Work Center to help buyers verify standard
purchase orders and agreements before submitting them
for approval. This action performs validation checks and
displays errors or warnings, but does not submit the
document for approval. The Validate Document action is
available to buyers when they update standard purchase
orders and agreements.

New,
Changed,
Obsolete
Components

This section lists the components that were added,


changed, or made obsolete for this feature in Oracle
Purchasing in Release Procurement Family R12.1.3
September Update 2012. These components may include
the following: forms, windows, reports, C programs,
SQL*Loader programs, workflows, alerts, tables, or APIs.
For additional information, refer to the Oracle Electronic

Technical Reference Manuals (eTRM) located on My Oracle


Support.
Changed Windows or Pages
This table lists the changed windows and pages.
Changed
Window or Page
Name

Technica Description
l Name

Update Blanket
Purchase
Agreement

Blanket
PG

Update
Standard
Purchase Order

OrderPG The Actions drop-down


provides a new Validate
Document
(PO_VALIDATE_DOCUME
NT) action.

The Actions drop-down


provides a new Validate
Document
(PO_VALIDATE_DOCUME
NT) action.

Implementati New and Changed Setup Steps


on
Consideration There are no new or changed setup steps for this feature.
s
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.

New Bulk Interfaces


There are no new bulk interfaces for this feature.
Customization Customizations and extensions are not possible for this
s and
feature.
Extensions
Minimum
There are no minimum level requirements for this feature.
Level
Requirements
Technology
There are no technology stack incompatibilities for this
Stack
feature.
Incompatibiliti
es
Technical
There are no technology architecture considerations for
Architecture
this feature.
Consideration
s
Troubleshooti
ng Tips

There are no troubleshooting tips for this feature.

Return to New and Changed Features


Top
3.8 Changes in Business Rules of Cancel Action Functionality
Descripti
on

Oracle Purchasing now provides the following changes in


business rules of the Cancel action functionality:
When buyers cancel an approved document at the header
level, Oracle Purchasing will no longer launch the Approval
Workflow for Cancel actions (APPROVAL WF). The application
creates the document's new revision, if the document is
approved and maintains archived and action history indicating
the cancel action. This information is communicated to
suppliers.
Buyers can cancel purchasing documents (at any level :
header, line, and shipment) that are at the Requires Reapproval

status. For example, buyers can cancel a shipment that is at


the Requires Reapproval status.
When a buyer cancels a purchasing document that has
changes since its last revision, the application now displays a
warning message, which clearly indicates changes, if any, in
the Quantity, Amount, Price, Need By, and Promised Date
fields. The application does not validate any other fields when
performing the cancel action. Buyers can revert changes in
specific fields and continue with the cancel action.
Communication is sent to the supplier along with PDF
attachment, which reflects the changed details. Note that this
change does not impact blanket purchase agreements as there
are no shipments for these documents. Note: If there is a
change in the listed attributes of only one shipment, then the
warning indicates the changes done clearly. But, if changes are
there to multiple shipments, then the warning is generic
indicating that there are some pending changes to the
document and buyers can ignore the changes if they want and
continue with the transaction.
When invoice cancellation happens after the cancellation of a
purchase order, the Canceled Quantity on the purchase order
line or the purchase order total does not reflect the quantity
which was utilized by invoice and is now canceled and no
longer in use. To correctly recalculate quantity, buyers must
final close the document in Oracle Purchasing. Communication
is sent to the supplier along with PDF attachment, which
reflects the correct recalculated quantity. Prior to this change,
the value of the quantity cancelled varied depending on the
order of steps in which the invoice creation, cancel action of the
purchase order, and invoice cancellation were performed. This
change ensures that the quantity cancelled is reflected
correctly irrespective of the order of the actions.
Buyers can recreate a demand for internal requisition if the
complex purchase order line is not received or billed. If a
complex order is partially received or invoiced or if the
cancellation is at the shipment level, then demand cannot be
recreated for complex purchase orders.
Note that there are no changes to the basic cancel
functionality.

New,
Changed,
Obsolete
Compone
nts

This section lists the components that were added, changed, or


made obsolete for this feature in Oracle Purchasing in Release
Procurement Family R12.1.3 September Update 2012. These
components may include the following: forms, windows,
reports, C programs, SQL*Loader programs, workflows, alerts,
tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
New Public API
This table lists the new Application Program Interfaces (APIs).
New API
Name

Technical Name

Description

Purchase
PO_Document_Contr Provides the ability
Order
ol_PUB
to cancel Purchasing
Document
documents in bulk
File
Name:
Control APIs
directly through an
POXPDCOS.pls
API. This API
performs all of the
same processing
that would be done
if a cancellation was
requested through
the PO Summary
Form Control
window.
The New API
supports canceling
multiple purchase
orders, agreements,
releases, purchase
order lines, purchase
agreements lines or
PO/Release
Shipments in one
go. The documents
being canceled can
be of any Type and

at any level. For


example, users can
pass PO Header and
Release Shipments
details to be
canceled in one go.
New Messages
This table lists new messages.
Changed Window or
Page Name

Description

PO_CAN_SHIP_REC_G
RT_ORD

Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Shipment is Fully Received.
&AMT_QTY_TOKEN Received is
[&QTY1] and &AMT_QTY_TOKEN
Ordered is [&QTY2]."

PO_CAN_PRICE_LIMIT_ Document #&DOC_NUM,


LT_PRICE
&LINE_SHIP_DIST_NUM :
Line
&AMT_PRICE_TOKEN[&PRICE1] is
greater than the Price
Limit[&PRICE2] specified.
PO_CAN_PO_LINE_NE_ Document #&DOC_NUM,
SHIP_AMT
&LINE_SHIP_DIST_NUM :
Line &AMT_QTY_TOKEN (&QTY1)
does not match shipment
&AMT_QTY_TOKEN (&QTY2)
PO_CAN_SHIP_PRICE_
NE_LINE

Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Line Unit Price (&PRICE1) does
not match shipment
Price(&PRICE2)

PO_CAN_PO_SHIP_NE_ Document #&DOC_NUM,

DIST_AMT

&LINE_SHIP_DIST_NUM :
Shipment &AMT_QTY_TOKEN
(&QTY1) does not match
Distribution &AMT_QTY_TOKEN
(&QTY2)

PO_CAN_SHIP_INV_MA Document #&DOC_NUM,


TCH_NE_R
&LINE_SHIP_DIST_NUM :
Match Option should be 'Receipt'
for LCM enabled shipment.
PO_CAN_DIST_DEST_T Document #&DOC_NUM,
YPE_NE_I
&LINE_SHIP_DIST_NUM :
Destination Type should be
'Inventory' for LCM enabled
shipment.
PO_CAN_DIST_DEL_GR Document #&DOC_NUM,
T_ORD
&LINE_SHIP_DIST_NUM :
Distribution &AMT_QTY_TOKEN
Delivered[&QTY1 ] is greater
than &AMT_QTY_TOKEN Ordered
[&QTY2].
PO_CAN_DIST_BILL_G
RT_ORD

Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Distribution &AMT_QTY_TOKEN
Billed[&QTY1 ] is greater than
&AMT_QTY_TOKEN Ordered
[&QTY2].

PO_CAN_SHIP_BILL_G
RT_REC

Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Distribution &AMT_QTY_TOKEN
Billed[&QTY1 ] is greater than
&AMT_QTY_TOKEN Received
[&QTY2].

PO_CAN_DIST_BILL_G
RT_DEL

Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Distribution &AMT_QTY_TOKEN

Billed[&QTY1 ] is greater than


&AMT_QTY_TOKEN Delivered
[&QTY2].
PO_CAN_SHIP_REC_N
OT_DEL

Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Shipment &AMT_QTY_TOKEN
Received[&QTY1 ] is not fully
Delivered [&QTY2].

PO_CAN_SHIP_WITH_R Document #&DOC_NUM, Line


CV_TRX
#&LINE_NUM, Shipment
#&SHIP_NUM:
Unprocessed Receiving
Transactions exist
PO_CAN_SHIP_WITH_A Document #&DOC_NUM, Line
SN
#&LINE_NUM, Shipment
#&SHIP_NUM:
Open ASN exists agianst this
shipment.
PO_CAN_DIST_INV_CH Document #&DOC_NUM, Line
ARGE_ACCT
#&LINE_NUM, Shipment
#&SHIP_NUM, Distribution
#&DIST_NUM:
Charge Account is Invalid.
PO_CAN_GA_WITH_OP Document #&DOC_NUM, Line
EN_STD_REF
#&LINE_NUM :
Open Standard Purchase Order
lines exist which reference this
Global Agreement.
PO_CAN_DIST_INV_BU Document #&DOC_NUM, Line
DGET_ACCT
#&LINE_NUM, Shipment
#&SHIP_NUM, Distribution
#&DIST_NUM:
Budget Account is Invalid.
PO_CAN_PA_WITH_OP Document #&DOC_NUM, Line

EN_REL

#&LINE_NUM :
Open releases exist against the
purchase document.

PO_CAN_CGA_WITH_O Document #&DOC_NUM:


PEN_STD_REF
Open Standard Purchase Order
lines exist which reference this
Agreement.
PO_CAN_CONTROL_SE Document #&DOC_NUM:
CURITY_FAILED
You do not have sufficient
authority to control the status of
this document.
PO_CAN_CONTROL_IN Document #&DOC_NUM:
VALID_ACTION
Cancel action at &ENTITY_LEVEL
Level is invalid for this
document.
PO_CHANGED_CANT_
CANCEL_ERR

&DOC_LINE_SHIP_DIST_NUM :
There are some pending
changes to the document in the
current revision.
Price: &PRICE_TOKEN],
[&AMT_QTY_TOKEN:&QTY_AMT],
[Need By Date:
&NEED_BY_PRM_DATE]
Please undo those changes
before taking the cancel Action.

PO_CHANGED_CANT_
CANCEL_INFO

&DOC_LINE_SHIP_DIST_NUM :
There were some pending
changes to the document in the
current revision.
[Price: &PRICE_TOKEN],
[&AMT_QTY_TOKEN:&QTY_AMT],
[Need By Date:
&NEED_BY_PRM_DATE].System
has undone those changes.

PO_CHANGED_CANT_

&DOC_LINE_SHIP_DIST_NUM :

CANCEL_WARN

There are some pending


changes to the document in the
current revision.
[Price: &PRICE_TOKEN],
[&AMT_QTY_TOKEN:&QTY_AMT],
[Need By Date:
&NEED_BY_PRM_DATE]
Do you wish to ignore them and
continue?

PO_CANT_REVERT_PE
NDING_CHG

&DOC_LINE_SHIP_DIST_NUM :
There are some pending
changes to the document in the
current revision.
System could not revert those
changes.
Please undo those changes
revision before taking the cancel
action

PO_INVALID_CANCEL_ The value of the runtime


REQS_FLAG
parameter p_cancel_reqs_flag
(used to determine whether or
not the backing requisition
should be cancelled)[Value
=&USER_VALUE]
conflicted with the Purchasing
Organization System
Setup[Value =&SYSTEM_VALUE].
Therefore, the Purchasing
Organization System Setup was
enforced and the runtime
parameter was ignored.
PO_INVALID_DOC_TYP Document #&DOC_NUM:
E_SUBTYPE
The document type (Value =
&TYPE) and subtype (Value =
&SUBTYPE) are invalid, or do not
match.
PO_INVALID_DOC_IDS Your document ID [Doc Id

=&DOC_ID] is invalid, or could


not found.
PO_ACTION_DATE_INV Document #&DOC_NUM:
ALID
Cancel action
date[Date=&ACTION_DATE] is
not in Open Period. Please
Choose a different Cancel Action
date or open the period for this
date.
PO_CAN_DIFF_OU_DO Cannot proceed with Cancel
CS
Action.
The selected documents do not
belong to same operating Unit
Code Changes
Following this release, Oracle Purchasing will no longer launch
Approval Workflow for Cancel actions.
The code for cancel action is moved from pro*c to plsql for
better maintainability.
Implemen New and Changed Setup Steps
tation
Considera There are no new or changed setup steps for this feature.
tions
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.

New Bulk Interfaces


There are no new bulk interfaces for this feature.
Customiz Customizations and extensions are not possible for this feature.
ations
and
Extension
s
Minimum There are no minimum level requirements for this feature.
Level
Requirem
ents
Technolog There are no technology stack incompatibilities for this feature.
y Stack
Incompati
bilities
Technical There are no technology architecture considerations for this
Architect feature.
ure
Considera
tions
Troublesh There are no troubleshooting tips for this feature.
ooting
Tips
Return to New and Changed Features
Top
3.9 View Correct Action Status for Purchasing Documents
Description Oracle Purchasing now displays the correct action status for
purchasing documents based on the approver's action. Prior
to this release, the application displayed the action as
Forward whenever any of the three actions were performed:
Approve, Forward, and Approve and Forward.
Now, buyers can view the action as:

Approve, if the approver has approved the purchasing


document.
Forward, if the approver has forwarded the purchasing
document to another approver.
Approve and Forward, if the approver has approved the
purchasing document and forwarded it to another approver.
This change is applicable to all purchasing documents in
Purchasing professional interface and BWC: purchase orders,
blanket purchase agreements, global purchase agreements,
and global contract purchase agreements.
From this release, a new ' Delegate' action code is available
for purchase orders, agreements, and releases. Whenever an
approver delegates an action to another approver, Oracle
Purchasing displays this action as 'Delegate'. Currently, this
feature is available for requisitions only.
For all purchasing documents, when the delegated person
performed any action, the Action History recorded this action
as the original approver's action. Now, when the delegated
person performs any action, Action History displays the
delegated person as the performer of the action.

New,
Changed,
Obsolete
Component
s

This section lists the components that were added, changed,


or made obsolete for this feature in Oracle Purchasing in
Release Procurement Family R12.1.3 September Update
2012. These components may include the following: forms,
windows, reports, C programs, SQL*Loader programs,
workflows, alerts, tables, or APIs.
For additional information, refer to the Oracle Electronic
Technical Reference Manuals (eTRM) located on My Oracle
Support.
Changed Workflows
This table lists the changed workflows.
Chang Technical Description
ed
Name

Workfl
ow
Name
PO
Appro
val

poxwfpoa Following changes are made to this


.wft
workflow item type:
Removed all the
IS_FORWARD_TO_VALID function
nodes from the
NOTIFY_APPROVER_PROCESS sub
process and connected Notify
Approver subprocess directly to
function node Set Forward-To/From
For Forward Action. Corresponding
logic is placed in the
PO_WF_PO_NOTIFICATION.POST_AP
PROVAL_NOTI procedure.
Added codes to set workflow
attributes for these actions:
Approve, Forward, and Approve
and Forward.

Implement New and Changed Setup Steps


ation
Considerati There are no new or changed setup steps for this feature.
ons
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing

There is no load balancing information for this feature.


New Bulk Interfaces
There are no new bulk interfaces for this feature.
Customizati Customizations and extensions are not possible for this
ons and
feature.
Extensions
Minimum
Level
Requireme
nts

There are no minimum level requirements for this feature.

Technology There are no technology stack incompatibilities for this


Stack
feature.
Incompatibi
lities
Technical
There are no technology architecture considerations for this
Architectur feature.
e
Considerati
ons
Troubleshoo There are no troubleshooting tips for this feature.
ting Tips
Return to New and Changed Features
Top
3.10 View Supplier Name and Site in Purchase Order Notification Email to Suppliers
Description

The purchase order email notification to suppliers had


the language suffix appended to the email address.
With this release, to provide clarity, the language suffix is
removed and the recipient in the purchase order email
notification to the supplier displays the combination of
vendor name and vendor site code. If a secondary email
address is defined in the PO: Secondary E-mail Address
profile option, then the To Address displays the

secondary email address.


Note: This change is applicable only to purchase orders
created or updated using the Purchase Orders form and
not to purchase orders created or updated using Buyer
Work Center.
Implementation New and Changed Setup Steps
Considerations
This section lists the setup steps that were added or
changed for Oracle Purchasing in Release Procurement
Family R12.1.3 September Update 2012.
The following setup steps are required:
Workflow Mailer is up for the supplier site email address.
Email is selected as the supplier Notification Method for
supplier sites.
(N) Purchasing > Supply Base > Suppliers > Supplier >
Address Book > Manage Sites > Communication tab >
Notification Method
Supplier site is not EDI enabled.
Upgrade Considerations
There are no upgrade considerations for this feature.
Sizing
Tablespace Considerations
There are no tablespace considerations for this feature.
Performance Considerations
XMLDB Usage
There are no XMLDB usages for this feature.
Load Balancing
There is no load balancing information for this feature.
New Bulk Interfaces

There are no new bulk interfaces for this feature.


Customizations
and Extensions

Customizations and extensions are not possible for this


feature.

Minimum Level
Requirements

There are no minimum level requirements for this


feature.

Technology
Stack
Incompatibilitie
s

There are no technology stack incompatibilities for this


feature.

Technical
Architecture
Considerations

There are no technology architecture considerations for


this feature.

Troubleshooting There are no troubleshooting tips for this feature.


Tips
Return to New and Changed Features
Top

4. Diagnostics and Logging


Oracle Purchasing utilizes Oracle E-Business Suite Diagnostics, a tool to help
standardize data gathering and troubleshooting. This tool is delivered within the
maintenance pack (product code IZU) and consists of two components:
The Oracle E-Business Suite Diagnostics framework (ODF)
Provides a place for product-specific tests to be processed and reported
Is accessible using the 'Application Diagnostics' responsibility which is assigned
through diagnostic roles within the RBAC security model
Note: If no role is assigned using RBAC and the "Application Diagnostics"
responsibility is directly assigned to users, such as through the System
Administrator Users form, all Diagnostics tabs open for those users. However, in the
Diagnose tab, tests do not appear under any application except HTML Platform;
users cannot run any test, except those for the HTML Platform application or
configure inputs for any other application.

Complete RBAC setup details for diagnostics are available through My Oracle
Support Document 167000.1
Product content (referred to as 'tests')
Primarily organized by functional groups
Provides data in a structured format
May include detailed error identification followed by actions to be taken when 'bad'
data is detected
It is highly recommended that following the successful installation of the Release
Procurement Family R12.1.3 September Update 2012 for Oracle Purchasing, the
following actions are taken:
Verify that the latest Oracle E-Business Suite Diagnostics patch is applied (see
Document 167000.1 for latest patch information) as this will ensure that the latest
tools are available.
Run the related product family pre-production test set(s) to verify existing product
setups have not been compromised and all new, required setups are flagged for
action.
After installation, review Document 783319.1, the diagnostic catalog, to identify
other helpful tests that you can use for maintaining a healthy environment.
For questions about Oracle E-Business Suite Diagnostics or any issues using this
tool, please consult Document 235307.1, FAQ, in My Oracle Support for the latest
answers and discussion.
E-Business Suite Diagnostics Quick Reference
My Oracle Support
Document
Document 167000.1

Title

Purpose

Installatio Use this Note to download the latest


n Guide
Diagnostics patch.
Follow the installation instructions to
eliminate common installation and
usage problems.
A link to how to set up RBAC security
for Oracle E-Business Suite
Diagnostics is included.

Document 235307.1

FAQ

Do you have a problem installing

My Oracle Support
Document

Title

Purpose
Diagnostics?
Do you have a question about how
Diagnostics works and what it can do
for you? This Note is a great first-line
resource to getting the information
that you need.

Document 342459.1

Overview

The Overview highlights Oracle EBusiness Suite Diagnostics, and what


this tool can do for you and your EBusiness Suite applications.

Document 421245.1

Oracle EBusiness
Suite
Release
Procureme
nt Family
R12.1.3
Septembe
r Update
2012
Diagnostic
Catalogs

This Note lists all tests that are


available for Oracle E-Business Suite
Release Procurement Family R12.1.3
September Update 2012.

Document 368109.1

PreTests that are grouped together


production (known as test sets) by a product
test sets family, designed to aid in verifying
that all included applications are set
up correctly.
Designed to detect missing or
incorrect setup and prevent
corruption before implementation or
usage of applications.

Document 232116.1

Training

Viewlets and presentations,


explaining the various aspects of
Oracle E-Business Suite Diagnostics.

My Oracle Support

Diagnosibi This is an open forum to discuss

My Oracle Support
Document

Title

Diagnosibility Community lity link

Purpose
Oracle E-Business Suite Diagnostics,
and is monitored by the Oracle EBusiness Suite Diagnostics
development team.

Oracle Purchasing uses the common diagnostics features in Oracle E-Business Suite.
This enables users and system administrators to use a centralized set of options to
control logging level, as well as output destination. To run diagnostics, use the
following profile options:
FND: Debug Log Enabled
FND: Debug Log Module
FND: Debug Log Level
Setting the log level to Statement produces detail logging of code execution. To
reduce the size of the output and make it more manageable, you can use PO% as a
module to restrict messages to those coming from Oracle Purchasing code.
The preceding profile options can be turned on at the user, function, responsibility,
or site level. It is preferable, however, to set profiles at the user level to restrict the
overhead they add to the system. If issues are experienced, logging profiles should
be set at the user level experiencing the issue. For authorization servlet-related
issues, you must set the diagnostics profile at the user level to ANONYMOUS.
To diagnose user interface issues, you can use the filter iby%,fnd.framework%,jbo%
and set the diagnostics go-to screen by clicking the Diagnostics Global button. To
enable this functionality, you must set the following profile option:
FND: Diagnostics
The FND: Diagnostics profile option controls whether the Diagnostics button is
rendered. It also controls the display of the About this Page link.
For system issues, such as exceptions, timeouts, or unexpected behavior, you can
turn on logging, based on where you are experiencing the issues, as follows:
For a concurrent program, you can capture the log file for the program processed by
turning on logging at the statement level.
For user interface, you can capture the logging shown on the screen by clicking the
Diagnostics button, and full stack trace of any exceptions you see on the page.

You can also capture additional information about the system by printing the report
from the About this Page link, as well as from the jsp:
/OA_HTML/jsp/fnd/fndversion.jsp.
For more information on Logging, see the Oracle Applications System
Administrator's Guide Documentation Set and the Oracle Applications Developer's
Guide in the Documentation Library.
Return to Diagnostics and Logging
Top

5. Known Issues in Oracle Purchasing Release Procurement Family R12.1.3


September Update 2012
There are no known issues for this product.
Return to Known Issues
Top

6. Change Record
Date

Description of Change

05-October-2012

Initial publication

14-February-2013

Updates section: Automatic Updates to General


Ledger (GL) Date

Top

7. Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Copyright Notice
Copyright 2012, Oracle and/or its affiliates. All rights reserved.
License Restrictions Warranty/Consequential Damages Disclaimer
This software and related documentation are provided under a license agreement
containing restrictions on use and disclosure and are protected by intellectual
property laws. Except as expressly permitted in your license agreement or allowed
by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by
any means. Reverse engineering, disassembly, or decompilation of this software,
unless required by law for interoperability, is prohibited.
Warranty Disclaimer
The information contained herein is subject to change without notice and is not
warranted to be error-free. If you find any errors, please report them to us in writing.
Restricted Rights Notice
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related
documentation and technical data delivered to U.S. Government customers are
"commercial computer software" or "commercial technical data" pursuant to the
applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, the use, duplication, disclosure, modification, and adaptation
shall be subject to the restrictions and license terms set forth in the applicable
Government contract, and, to the extent applicable by the terms of the Government
contract, the additional rights set forth in FAR 52.227-19, Commercial Computer
Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway,
Redwood City, CA 94065.
Hazardous Applications Notice
This software or hardware is developed for general use in a variety of information
management applications. It is not developed or intended for use in any inherently
dangerous applications, including applications that may create a risk of personal
injury. If you use this software or hardware in dangerous applications, then you shall
be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any
liability for any damages caused by use of this software or hardware in dangerous
applications.

Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other
names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All
SPARC trademarks are used under license and are trademarks or registered
trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD
Opteron logo are trademarks or registered trademarks of Advanced Micro Devices.
UNIX is a registered trademark of The Open Group.
Third Party Content, Products, and Services Disclaimer
This software or hardware and documentation may provide access to or information
on content, products, and services from third parties. Oracle Corporation and its
affiliates are not responsible for and expressly disclaim all warranties of any kind
with respect to third-party content, products, and services. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to
your access to or use of third-party content, products, or services.

Anda mungkin juga menyukai