Comments
(0)
In this Document
Purpose
Scope
Details
1. What's New
2. Documentation
To
Bottom
3.1 Use Oracle Approvals Management (AME) for Purchase Order (PO) Review,
Approval, and E-Signature
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.10 View Supplier Name and Site in Purchase Order Notification Email to
Suppliers
6. Change Record
7. Documentation Accessibility
Copyright Notice
Warranty Disclaimer
Trademark Notice
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.
Feature Name
Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.
Feature Name
Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.
Feature Name
Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.
Feature Name
Description
Currently, purchase orders can be routed for approval to only
approvers defined in a position hierarchy or supervisor
hierarchy.
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
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.1 Use Oracle Approvals Management (AME) for Purchase Order (PO) Review,
Approval, and E-Signature
New,
Changed,
Obsolete
Component
s
Description
Document
Style
StyleEditPG
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
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.
Stack
feature.
Incompatibi
lities
Technical
There are no technology architecture considerations for this
Architectur feature.
e
Considerati
ons
Troublesho
oting Tips
Technical Description
Name
Withdraw
Withdra
wPG
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
OrdersSummaryHe
adersPG
Action
History
ActionHistoryPG
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
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
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)
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
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
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
New,
Changed,
Obsolete
Components
Technical Description
Name
Distributions
POXRQE
RQ
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
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
Description
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
Contract
PG
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
New,
Changed,
Obsolete
Components
Technica Description
l Name
Update Blanket
Purchase
Agreement
Blanket
PG
Update
Standard
Purchase Order
New,
Changed,
Obsolete
Compone
nts
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
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]."
Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Line Unit Price (&PRICE1) does
not match shipment
Price(&PRICE2)
DIST_AMT
&LINE_SHIP_DIST_NUM :
Shipment &AMT_QTY_TOKEN
(&QTY1) does not match
Distribution &AMT_QTY_TOKEN
(&QTY2)
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
Document #&DOC_NUM,
&LINE_SHIP_DIST_NUM :
Shipment &AMT_QTY_TOKEN
Received[&QTY1 ] is not fully
Delivered [&QTY2].
EN_REL
#&LINE_NUM :
Open releases exist against the
purchase document.
&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
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
New,
Changed,
Obsolete
Component
s
Workfl
ow
Name
PO
Appro
val
Minimum Level
Requirements
Technology
Stack
Incompatibilitie
s
Technical
Architecture
Considerations
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
Document 235307.1
FAQ
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
Document 421245.1
Oracle EBusiness
Suite
Release
Procureme
nt Family
R12.1.3
Septembe
r Update
2012
Diagnostic
Catalogs
Document 368109.1
Document 232116.1
Training
My Oracle Support
My Oracle Support
Document
Title
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
6. Change Record
Date
Description of Change
05-October-2012
Initial publication
14-February-2013
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.