Purchasing Documentation Updates

8/8/2019 Purchasing Documentation Updates

http://slidepdf.com/reader/full/purchasing-documentation-updates 1/22

– 1Oracle Purchasing Documentation Updates

Oracler Purchasing

Documentation UpdatesRELEASE 11.0.1

June 1998



– 2 O racle Pu rch asin g Docu m en ta tion Up d ates

Copyright E 1998, Oracle Corporat ion. All rights reserved .

The Programs (which include both the software and documentation) contain proprietary

information of Oracle Corporation; they are provided under a license agreement

containing restrictions on use and disclos ure and are also protected by copyright, patent

and other intellectual and industrial property laws. Reverse enginee ring, disassembly

or decompilation of the Programs is prohibited.

The information contained in this docum ent is subject to change w ithout notice. If you

find any problems in the docum entation, please report them to u s in writing. Oracle

Corporation d oes not warran t that this documen t is error–free. Except as may be expressly

perm itted in your license agreement for these Programs, no pa rt of these Programs may be

reprod uced or tran smitted in any form or by any m eans, electronic or mechanical, for any

pu rpose, without the express written perm ission of Oracle Corporation.

If the Programs are d elivered to the US Governm ent or anyon e licensing or using th e

Program s on behalf of the US Governmen t, the following notice is ap plicable:

Restricted Rights Notice

Program s d elivered su bject to the DOD FAR Sup plement are ’comm ercial compu ter

software’ and use, dup lication and d isclosure of the Programs includ ing docum entation,

shall be subject to the licensing restrictions set forth in the applicable Oracle license

agreement. Otherw ise, Programs delivered subject to the Federal Acquisition Regulations

are ’restricted comp uter software’ and u se, dup lication and disclosure of the Program s

shall be su bject to the restrictions in FAR 52.227–19, Comm ercial Comp uter Software ––

Restricted Rights (June 1987). Oracle Corpora tion, 500 Oracle Parkwa y, Redw ood City, CA

94065.

The Programs a re not intended for use in any n uclear, aviation, mass tran sit, med ical, or

other inherently d angerous ap plications. It shall be licensee’s responsibility to take all

app ropriate fail–safe, back–up, redun dan cy and other m easures to ensure the safe use of

such ap plications if the Programs are u sed for such p urp oses, and Oracle disclaims liability

for any dam ages caused by such use of the Programs.

Oracle is a registered tra dem ark, and Oracle Web Employees and Oracle Workflow are

trad emarks of Oracle Corporation. All other company or prod uct names mentioned are

used for identification pur poses only, and m ay be tradem arks of their respective owners.




Oracle Purchasing Documentation Updates

This docum ent contains important information. Please read this

section for the latest up da tes, revisions, and add itions to your user’s

guide.

Setup Overview

Important setup information needs to be ad ded to the ”Setup

Overview” section.

See: Setup Overview, Oracle Purchasing User’s Guide.

Define Locations (Required)

Add th is step after Step 3 Set Up Calendars, Currencies, and Set of

Books. See: Site Locations, Oracle Human Resources User’s Guide.

If you’re also setting u p other Oracle app lications, you m ay already

have d efined locations when you set up th ose applications.

Define Freight Carriers (Optional)

Add th is step after Step 5 Set Up Units of Measure. See: Defining

Freight Carriers, Oracle Inventory User’s Guide.

Note: You m ust p erform this step for each inven tory

organization.

If you’re also setting u p Oracle Inven tory, you m ay already have

defined freight carriers when you set up Inventory.

Define Categories

Add th is step after Step 6 Set Up Items.

Defining categories involves th e following tasks:

• Define category codes. See: Defining Categor ies, Oracle Inventory

User’s Guide. (Required)

• Define category sets. See: Defining Category Sets, Oracle

Inventory User’s Guide. (Required with defaults)

• Define default category sets. (Required w ith defaults) See:

Defining Default Category Sets, Oracle Inventory User’s Guide.

Note: Purchasing requ ires you to enforce a list of valid

categories. Therefore, in the List of Valid Categories in the




Category Sets wind ow, you must list all categories that are

eligible for that category set. In particular, make sure that th e

Default Category in the Category Sets wind ow a lso app ears in

the List of Valid Ca tegories.

If you’re also setting u p Oracle Inven tory, you shou ld already havedefined categories wh en you set up Inventory.

Define Payment Terms (Optional)

Add th is step after Step 13 Set Up Cross–Reference Types, Tax

Names, and Location Associations. See: Paym ent Term s, Oracle

Payables User’s Guide.

If you’re also setting u p Oracle Payables, you m ay already have d efined

paym ent terms when you set up Payables.

Define Transaction Reasons (Optional)

Add th is step after Step 22 Set Up Financial Options . See: Defining

Transaction Reasons, Oracle Inventory User’s Guide.

If you’re also setting u p Oracle Inven tory, you m ay already havedefined tran saction reasons when you set up Inventory.

Set Up Approval Workflow Option (Required with defaults)

Add th is step after Step 30 Modify Change Order Workflow Options.

See the section ”Choosing Workflow Options” later in this docum ent

for information on setting up this approval workflow option.

Additional Setup Notes

If you w ant to d efine catalog groups, which is optional, do so after the

step Define Categories above. See: Defining Item Catalog Groups,

Oracle Inventory User’s Guide. (If you’re also setting up Oracle

Inventory, you m ay already have d efined item catalog groups when

you set u p Inventory.)

If you want to d efine d escriptive flexfields, do so last, after all the other

setup steps. See: Oracle Applications Flexfields Guide.

Choosing Workflow Options

In add ition to th e other w orkflow setup options described in the

section ”Choosing Workflow O ptions” in you r documen tation, you




need to consider one m ore option—an item attribute in the Main

Requisition Ap proval Process called ”Send PO Au tocreation to

Background.”

Send PO Autocreation to Background

This item attr ibute is used by th e ”Get AutoCreate PO Mod e” function

activity in the Main Requisition Approval Process. By d efault, the

attr ibute is set to ’Y’ for Yes, to send automatic document creation to

background mod e. But you can change it to ’N’ for No if you’d rather

process automatic docum ent creation in online mode.

Background and online mod es affect your system performance in

different ways. For more information on what background and onlinemean , see PO: Workflow Processing Mode in the section Profile Options

in Purchasing, Oracle Purchasing User’s Guide.

Attention: Since this att ribu te is set to ’Y’ by d efault—which

mean s automatic docum ent creation occurs in backgroun d

mod e—you mu st start the Workflow Background Process in

the Subm it Requests wind ow in the System Ad ministrator

responsibility. As long as this attr ibute is set to ’Y,’ you mu st

start the Workflow Backgrou nd Process. You can subm it the

process for all workflows or just for a p articular w orkflow, in

this case the PO Requ isition App roval workflow. See: To

Schedu le Background Engines, Oracle Workflow Guide.

Note: A function activity in both the PO and Requ isition App roval

workflows, called ”Get Workflow App roval Mode,” sets the processing

mod e for the entire approva l workflow in Purchasing, based on how

the p rofile option PO: Workflow Processing M ode is set. While thisfunction activity sets the processing mod e for the entire approval

workflow in Pu rchasing, the item attribute ”Send PO Au tocreation to

Background ” enables you to change the p rocessing mod e specifically

for automatic docum ent creation, regardless of how the p rofile option

PO: Workflow Processing Mode is set. ”Send PO Autocreation to

Background ” informs the function activity ”Get AutoCreate PO Mod e”

whether ”Launch Create PO Workflow” in th e Main Requisition

App roval Process shou ld initiate automatic docum ent creation inbackground or online m odes.

See:

Choosing Workflow Options, Oracle Purchasing User’s Guide

App roval Workflows, Oracle Purchasing User’s Guide




Profile Options in Purchasing

The first and second descriptions below are abou t new profile options.

The third contains more information about a p rofile option already

described in your d ocum entation.

PO: Workflow Processing Mode

This profile option affects the performance of the Pu rchasing app roval

workflow processes. You can choose from two values:

Comp letes an entire app roval workflow process

before letting you close the wind ow you’re using,

but p rovides you w ith an up dated Status (forpu rchase orders) as soon as it finishes.

Enables you to p roceed to the next activity while

the p rocess comp letes in the background, even

though you may not see an upd ated Status right

away.

Whichever option you choose, you can always view the current statu s

or action history of a requisition or pu rchase order through theRequisitions Sum mary or Purchase Orders Sum mary wind ows. You

can also view notifications of approval through the Notifications

Sum mary wind ow.

The default valu e (if you d on’t p rovide one) is Background .

Attention: When this profile option is set to Background , you

mu st start th e Workflow Background Process, which you access

through the System Ad ministrator responsibility. It isrecomm end ed that you set this process to run frequently, if you

are using it for Background mode approvals. See: To Schedule

Background Engines.

The user can both view an d u pd ate this profile option. It can also be

up da ted at th e User, Responsibility, App lication, and Site levels.

See: Profile Op tions in Purchasing.

PO: Set D ebug Concurrent ON

This profile option is used , usually by technical support staff only, for

find ing problems with Requisition Imp ort. The default value is No.

The user can view and u pd ate this profile option. It can also be

up da ted at the user, responsibility, app lication, and site levels.

Online

Background




Caution: For performance reasons, it is very important that

this p rofile option always be set to No, un less you are instru cted

otherw ise by Oracle Corpora tion.

PO: Set Debug Workflow ONThis profile option is u sed, usually by technical support staff only, for

find ing problems with Purchasing work flow p rocesses. The default

value is No. The user can view and up da te this profile option. It can

also be up da ted at the user, respon sibility, app lication, and site levels.

Caution: For performance reasons, it is very important that

this p rofile option always be set to No, un less you a re instructed

otherw ise by Oracle Corpora tion.See: Profile Op tions in Purchasing, Oracle Purchasing User’s Guide.

Using the Account Generator in Oracle Purchasing

Note the changes described here if you need to open and view, or

customize, the Accoun t Generator in Purchasing.

The section ”Using the Accoun t Generator in Oracle Purchasing”currently lists eight Accoun t Generator workflows (also called item

types) that au tomat ically build charge, bud get, accrual, and var iance

accoun ts—four for pu rchase orders and releases, and four for

requisitions.

However, to enhan ce the performance of the Accoun t Generator in

Purchasing wh enever an account is generated on a p urchase order or

requisition, these eight item types w ere recently collapsed intotwo—one for pu rchase orders and releases, and one for requisitions:

• PO Accoun t Generator

• PO Requisition Account Generator

This mean s that when you open (or customize) an Account Generator

item type in the Oracle Workflow Builder, you’ll see (or customize) just

these two—not eight, as described in you r documen tation currently.

Collapsing the eight item typ es into tw o has not changed anyth ing else

about how the Accoun t Generator in Purchasing w orks as described

currently in your d ocum entation. How ever, it does change how the

processes are organized w ithin the two item types, and wh at you can

and cannot customize.

The following sections show wh ich parts of your d ocumen tation need

to be upda ted accordingly.




See: Using the Accoun t Generator in Oracle Purchasing, Oracle

Purchasing User’s Guide.

Decide How to Use the Account Generator

This section is unchanged. See your current documentation for the latest

information.

The D efaul t Account Generator Processes for Oracle Purchasing

For this section, substitute the following information.

Evaluate whether the default Accoun t Generator processes meet your

accoun ting requiremen ts. No setup steps are required to use thedefault. The default processes can also be up da ted later as your need s

change.

Note: If you used FlexBuilder in Release 10 but did not custom ize the

default configuration, you can use the d efault Account Generator

process in Release 11, wh ich g ives you th e same result as the d efault

assignm ents in FlexBuild er.

Each Account Generator w orkflow is called an item type. Purchasingcomes with the following Accoun t Generator item typ es for pu rchase

orders, releases, and requisitions:

• PO Accoun t Generator (for purchase orders an d releases)

• PO Requisition Accoun t Generator (for requ isitions)

Each item typ e above contains the following top –level processes:

• Generate Default Accoun ts

This process is the default workflow in Pu rchasing that builds

the accoun ts.

• Generate Accounts Using FlexBuilder Rules

In tu rn, each of these top –level processes contains other processes

within them and, within these, additional subprocesses and function

activities. These are described below.

Viewing Account Generator Processes in the Workflow Builder


To open the PO Accoun t Generator in the Oracle Workflow Builder,

choose Open from the File menu an d select PO Account Generator. To

open the PO Requisition Accoun t Generator in the Workflow Builder,




choose Open from the File menu and select PO Requisition Accoun t

Generator. Explore how th ese item typ es break dow n in the Workflow

Builder ’s Navigator.

Although all the processes are listed together in the Workflow Builder ’s

Navigator, only two—Generate Default Accounts and GenerateAccounts Using FlexBuild er Rules—are the top–level processes. Note

that the icons for the two top –level processes look slightly different

from the other p rocess icons, indicating th at they are the top –most

processes. The rest of the processes belong to the tw o top–level

processes. For example, when you op en (dou ble–click) the top–level

process Generate Default Accoun ts to view it as a d iagram, you see it

contains four m ain p rocesses—Generate Default Accrual Account,

Generate Default Bud get Accoun t, Generate Default Charge Accoun t,and Generate Default Variance Accoun t.

When you open the p rocess Generate Default Accrual Accoun t, you see

it contains m any function activities and one subp rocess—Build Project

Related Account. (For an example of how a default Accoun t Generator

process itself looks in the Workflow Builder, see the cur rent Pu rchasing

docum entation.) As you can see, all of these processes and

subp rocesses are listed un der Processes in the Workflow Builder ’s

Navigator.

To better understand wh ich p rocesses are subp rocesses of the others,

use the following structural breakdown:

• PO Account Generator (workflow item type)

– Generate D efault Accounts (top–level process)

– Generate Default Accrual Account (process)

– Work Item Destination Type (function activity)

– PO Project–Related ? (function activity)

– Build Project Related Account (subprocess)

– Accrual Account for Expense Item (function activity)

– Accrua l Accoun t from Organization (function activity)

– Generate Default Budget Account (process)




– Get Bud get Account from Item/ Sub (function activity)

– Get Item Level Bud get Account (function activity)



– 10 O racle Pu rchasing Documen ta tion U pda tes

– Get Org Level Bud get Accoun t (function activity)

– Get Charge Accoun t (function activity)

– Generate Default Charge Account (process)

– Work Item Destination Type (function activity)– Build Expense Charge Accoun t (subprocess)

– Expense Account (function activity)



– Build Inventory Ch arge Accoun t (subprocess)

– Build Shop Floor Charge Account (subprocess)

– Typ e of WIP (function activity)

– Job WIP Account (function activity)

– Schedule Account (function activity)

– Generate Default Variance Account (process)


– Get Charge Accoun t for Variance Accoun t (subprocess)


– Get Charge Accoun t (function activity)


– Get Variance Account from Organization (subprocess)– Variance Account from Organization (function activity)

– Generate Accounts Using FlexBuilder Rules (top–level process)

– Generate Charge Account Using FlexBuilder Rules

– Generate Budget Account Using FlexBuilder Rules

– Generate Accrual Account Using FlexBuilder Rules

– Generate Variance Account Using FlexBuilder Rules

• PO Requisition Account Generator (workflow item type)

This workflow item type breaks dow n exactly like the PO

Accoun t Generator item type above.




Standard Flexfield Workflow

All of the p rocesses listed above contain ad ditional function activities

not listed here, such as Start and End function activities. These are

stand ard function activities provided in the Standard Flexfield

Workflow item typ e. These also includ e the function activities ”CopyValues from Code Combination” and ”Validate Code Combina tion”

that you see used in the Account Generator processes. For information

on how to use th ese fun ction activities, see the Oracle Applications

Flexfields Guide.

Item Attributes

Each accoun t generator (workflow item typ e) contains a num ber of

item attributes. These attributes correspond to all the raw param etersand some derived p aram eters that were used in FlexBuilder. The item

attributes for the PO Requisition Accoun t Generator are slightly

different from the item attributes for the PO Accoun t Generator.

Build Project Related Account

The subp rocess Build Project Related Accoun t is available for you to

custom ize if Oracle Projects is insta lled. To use th is process, youprovid e your ow n ru les to the process, in the form of workflow process

definitions, to build the accoun t.

For more information abou t using the Accoun t Generator wh en you

integrate Purchasing with Oracle Projects, read th e following essay:

Using the Accoun t Genera tor in Oracle Projects (Oracle Projects User’s

Guide).

What the Account Generator Does in Oracle Purchasing


information.

Generate Account Using FlexBuilder Rules Process


If you customized FlexBuilder in a previous release to generate accoun t

combinations, you can u se the Generate Accoun ts Using FlexBuilder

Rules process to replicate your FlexBuilder setup automatically,

without changing any of your pred efined FlexBuilder Rules, and

without customizing the Account Generator. This top–level process

consists of the following processes:




• Generate Ch arge Accoun t Using FlexBuilder Rules replicates

your charge accoun t FlexBuilder rules in th e Accoun t Generator.

• Generate Budget Account Using FlexBuilder Rules replicates

your bud get accoun t FlexBuilder ru les in the Accoun t Generator.

• Generate Accrual Account Using FlexBuilder Rules replicatesyour accrua l accoun t FlexBuilder rules in th e Account Generator.

• Generate Variance Account Using FlexBuilder Rules replicates

your variance accoun t FlexBuilder rules in the Accoun t

Generator.

To bu ild accounts, these processes call the ap prop riate functions that

were generated d uring your up grad e from Release 10 to Release 11.

If you are up grad ing from Release 10, follow the gu idelines in th e

FlexBuilder chapter of the Oracle Applications Upgrade Preparation

Manual.

Customizing the Account Generator for Oracle Purchasing


Purchasing p rovides default Account Generator p rocesses for you to

use. If the defaults do not satisfy your accounting requiremen ts, you

can use th e Oracle Workflow Builder to customize the d efault

processes.

You can customize any of the following p rocesses and the su bprocesses

within them:

• Generate Default Accrual Account

• Generate Default Bud get Accoun t

• Generate Default Charge Account

• Generate Default Variance Account

You cannot custom ize the tw o top–level processes:

• Generate Default Accoun ts

• Generate Accounts Using FlexBuilder Rules

You cannot custom ize any p rocess belonging to Generate Accoun ts

Using FlexBuild er Rules:

• Generate Charge Account Using FlexBuilder Rules

• Generate Budget Account Using FlexBuilder Rules

• Generate Accrual Account Using FlexBuilder Rules




• Generate Variance Account Using FlexBuild er Rules

You cannot customize m ost function activities, since these m ap directly

to PL/ SQL programs in the Oracle database, but you can replace a

function activity with one of your ow n. See Customization Example

below.If you w ant to create a new process or custom ize an existing one to

meet you r business needs, make a backup copy of the default processes

that Oracle provid es, and then u se the Oracle Workflow Builder to

customize a p rocess or create a new one.

For more information on the generic features and functions of the

Accoun t Generator, see Custom izing the Account Gen erator, Oracle

Applications Flexfields Guide.

For more informat ion on how to u se the Oracle Workflow Builder, see

th e Oracle Workflow Guide.

Customization Guidelines


When you choose to customize the Accoun t Generator in Purchasing,consider the following :

Once the Accoun t Generator successfully builds accoun ts for a

document, it does not attemp t to rebuild wh en you up date the

docum ent. For example, if you bu ild a custom p rocess to generate the

requisition charge account for Expense pu rchases based on requ estor,

and change the requestor after the Accoun t Generator constructs the

charge accoun t, it will not attem pt to rebu ild.

Requisition Import does not u se the Accoun t Generator to construct

charge, bud get, accrual, or variance accoun ts. Any custom process that

you create cannot be u sed by this utility.

Customization Example


In the Generate Default Charge Account p rocess, un der th e PO

Accoun t Generator item typ e, you could m odify the Build Expense

Charge Account subprocess by replacing the Get Expense Accoun t ID

function activity with one of your ow n. A new function activity,

how ever, must have the sam e result type as the fun ction activity you

replace. In your new function activity in this examp le, you also must

set the item attr ibute, Temp Account ID , with the code combination

identification nu mber (CCID) of the accoun t being bu ilt. This attribute




is used by the function activity, Copy Values from Account ID, to fetch

the concatenated segm ents.

You m ust test any customizations to the Accoun t Generator before

using them on a produ ction database.

Implementing a Customized Account Generator Process


Use the Accoun t Generator Processes wind ow to choose either the

Generate Default Accoun ts process or the Generate Accounts Using

FlexBuilder Rules process and associate the p rocess w ith th e

app ropriate Accoun ting Flexfield stru cture and item type.

Choosing the Process for a Flexfield Structure


If you customize any of the customizable processes belonging to the

Generate Default Accounts process, and you m ake sure the Generate

Default Accoun ts process is associated with the ap prop riate

Accoun ting Flexfield stru cture and item type in the Accoun t GeneratorProcesses wind ow, your customizations w ill take effect.

1. Navigate to the Account Generator Processes window by switching

to the System Ad ministrator respon sibility and choosing

Application > Flexfield > Key > Accoun ts.

2. With your cursor in the Application field, choose Query > Find and

select the combina tion of Application, Flexfield Title, and Stru cture

that you need.

Or, perform a Query > Run an d locate the PO Accoun t Generator

and PO Requisition Accoun t Generator item typ es in the Item Type

column.

3. In the Process field, specify the p rocess—Generate Default

Accoun ts or Generate Accoun ts Using FlexBuilder Rules—that you

want to use to generate these accoun ts.

The default p rocess, Generate Default Accounts, will default in.

Using the Account Generator Profile Option


information.




– Line 1: the sam e line–level record (another row) in

PO_LINES_INTERFACE w ith the other corresponding shipm ent:

– Shipment 2: the other shipm ent record in

PO_LINES_INTERFACE corresp ond ing to Line 1

See:

Receiving Price/ Sales Catalog Information Electronically, Oracle

Purchasing User’s Guide

Purchasing Documents Open Interface, Oracle Manufacturing,

Distribution, Sales and Service Open Interfaces Manual, Release 11

Confirm Receipts Workflow Select Orders Process

The Confirm Receipts Workflow Select Orders process in Purchasing

mu st be running in order to use the Confirm Receipts workflow. The

Confirm Receipts w orkflow sends n otifications throu gh the Web,

e–mail, or Notifications Sum mary wind ow to requestors or buyers who

create requ isitions throu gh Oracle Self–Service Web Applications or

Purchasing.

The Confirm Receipts w orkflow sends n otifications for items w ith a

Destination or Deliver–To Type of Expen se, a Routing of Direct

Delivery, and a Need –By date that is equal to or later than the current

date.

The Workflow Background Process mu st be running before you can

submit the Confirm Receipts Workflow Select Ord ers process. In the

Subm it Requests w indow, in the System Adm inistrator responsibility,

select Workflow Backgrou nd Process in the Request Nam e field. See:To Schedule Backgrou nd Engines, Oracle Workflow Guide.

To subm it the Confirm Receipts Workflow Select Orders process,

navigate to the Submit Requests w indow, select Confirm Receipts

Workflow Select Ord ers in th e Request N ame field, choose Schedu le,

and choose how often you wan t the process to run. For example, if you

set it to run one or tw o times a day, the Confirm Receipts work flow

will query for pu rchase orders that meet the criteria described aboveand send notifications (if required) one or tw o times a d ay.

See: Confirm Receipts, Oracle Web Employees online documentation.

Advance Shipment Notices (ASNs)

In the section Types of ASNs, a Replacement ASN is listed as one typ e of

ASN. There is no Replacement ASN. There are only Original,




Cancellation, and Test ASNs. To replace an ASN with a new or

corrected ASN, your sup plier should send a Cancellation ASN to

cancel the Original ASN, and then send a new Original ASN.

Users should note that any references to a Replacement ASN are

simply the act of sending a Cancellation ASN followed by a newOriginal ASN.

See: Ad van ce Shipment Notices (ASNs).

Workflow Background Process

In your user ’s guid e, the Workflow Background Process is described as

app earing in the list of values in the Subm it Request window when youchoose Reports > Run. The Workflow Backgroun d Process is accessible

only throu gh the Oracle System Adm inistrator responsibility, not

Purchasing.

The Workflow Background Process must be running if you are using

the following options:

• The Background mod e for Purchasing approvals. By default the

profile option in PO: Workflow Processing Mode is set to Background . You m ust start the Workflow Backgrou nd Process in

order for the Background mode to work.

• The Timeout feature in the ap proval w orkflow processes for

pu rchase orders or requisitions. The Timeout feature is enabled

only if you m odify the n otification(s) associated w ith it in the

Oracle Workflow Builder. The Timeou t feature send s per iodic

remind ers to approvers or autom atically forwards a notification

to the next app rover in the hierarchy after no response isreceived over a p articular period of time.

See: Approval Workflows and Workflow Backgrou nd Process.

Receiving Price/Sales Catalog Information Electronically

Important Addition to Setup Requirements

Following are add itional setup requirements for importing p rice/ sales

catalog information.

Allowing up da ting of the item master enables pr ice or item d escription

changes to be commu nicated quickly to Purchasing. Before you run the

EDI Price/ Sales Catalog Inbound Program or the EDI Response to

Request for Quote Inboun d Program , you need to make sure of the

following settings if you w ant to up da te the item m aster:




• Allow upd ating of item descriptions. Navigate to the Purchasing

Options window. In the Control options region, check Allow

Item Description Upd ate.

• Allow up da ting of item status codes at the site level. Navigate

to the Personal Profiles wind ow. Make sure that INV: DefaultItem Status is set to Active.

Make sure defau lt category sets are set up app ropriately for both

Purchasing and Inventory by performing the following steps:

1. Navigate to the Default Category Sets window by choosing Setup >

Items > Categories > Default Category Sets in the Pu rchasing

responsibility.

Make sure that both Purchasing and Inventory are listed in theFunctional Area column an d each has a default Category Set

defined for it.

2. Make sure that you have a d efault category set for both Purchasing

and Inven tory in the Category Sets window. Navigate to the

Category Sets wind ow by choosing Setup > Items > Categories >

Category Sets in the Purchasing responsibility.

See: Defining Category Sets.

If you’ve selected the Enforce List of Valid Categor ies checkbox in

the Category Sets window, make su re that the Default Category

also app ears in that List of Valid Categories. If not , enter it in the

list.

Additional Information about Sourcing

Please note the following add itional information abou t sourcing ruleswh en imp orting p rice/ sales catalog information.

When you import p rice/ sales catalog information into Purchasing

through the EDI Catalog Inbound or EDI Respon se to RFQ Inbou nd

report in Oracle EDI Gateway, you have the op tion of choosing Yes or

No in the Create Sourcing Rules field in the Param eters wind ow th at

appears. If you choose Yes, Purchasing checks to see if a sourcing ru le

is assigned to th e item at the item level:• If no sou rcing rules exist for the item, Purchasing generates a

sourcing ru le autom atically, allocating 100 percent to the sup plier

importing the information.

• If a sou rcing rule exists for the item, Purchasing comp ares the

effectivity dates of the incoming d ocumen t w ith those of the

existing sourcing ru le for the item. To ensure that only one

sourcing rule is used for the item, Purchasing does the following:




If the effectivity da tes of the incoming docum ent are the same as

the existing sourcing ru le’s effectivity dates, Purchasing checks

to see if the supp lier is in the Ap proved Sup plier List. If not,

Purchasing adds the supp lier to the existing sourcing ru le with

an allocation of 0 percent. Later, you can query the sou rcing ru le

and define your own percentage splits between supp liers.

If the effectivity d ates of the incoming docum ent are different

than the existing sourcing ru le’s effectivity d ates, but are w ithin

or overlap the existing effectivity da tes, then no new sourcing

rule is created th at w ill conflict w ith the existing sourcing ru le.

If the effectivity dates of the incoming docum ent d o not overlap

the existing sourcing rule’s effectivity d ates, Purchasing u pd ates

the item’s sourcing rule w ith the new effectivity da tes, addingthe su pp lier at an allocation of 100 percent.

See: Receiving Price/ Sales Catalog Information Electronically and

Purchasing Documen ts Open Interface.

Assigning Sourcing Rules and Bills of D istribution

When you enter an Assignm ent Set name in the Sourcing Rule/ Bill of Distribution Assignments w indow, make sure you u se the same nam e

that ap pears (or that you’ve provid ed) in the profile option MRP:

Default Sourcing Assignment Set.

Tax Defaults in Purchasing

In the section H ow Tax Defaults Affect Purchasing Docum ents, one of

the p oints listed reads as follows:

• Once you created a pu rchase order shipm ent and a tax name has

already been defaulted on to the shipment, if you change any of

the tax sources (for examp le, the Supp lier or Site on a pu rchase

order head er), Purchasing will not automatically up da te the tax

nam e. For examp le, if you change a Sup plier or Site after a Tax

Nam e has already d efaulted onto the pu rchase order shipment,

you w ill have to man ually upd ate the Tax Nam e for the newSup plier or Site you entered.

Instead, it should read as follows:

• If you change any of the tax sources (for examp le, the Supp lier or

Site on a purchase order head er) when you create a pu rchase

order, Purchasing defaults a new Tax Nam e correspond ing with




the new tax source on all new sh ipments you create but does not

use the new Tax Nam e on p revious shipments you created.

• If you overrid e a defaulted Tax Nam e on the shipm ent you’re

currently entering and then change any of the tax sources (such

as Sup plier or Site) on the pu rchase order, Purchasing d oes notdefault a new Tax Nam e.

See: How Tax Defau lts Affect Purchasing Docum ents.

Upgrade N otifications to Release 11 Process

In Release 11, docum ent ap proval is hand led by Oracle Workflow

technology. Because of Workflow, the N otifications wind ow in

Purchasing has been replaced by a new Notifications Sum mary

wind ow, and all not ifications are Workflow notifications. Release 11

recognizes your existing notifications only if you u pgrade them to

Workflow n otifications. This is wh at the Up grad e Notifications to

Release 11 process does. It routes your existing d ocumen ts that are

pend ing app roval through the new app roval workflow processes, so

that their notifications become Workflow notifications.

Attention: You n eed to run th is process only if you ’reup grad ing from a p revious release of Purchasing. See: Oracle

Applications Upgrade Manual.

See:

App roval Workflows

Viewing and Responding to Notifications

Viewing Changes to Purchase Orders

You can view at a glance all past revisions mad e to archived pu rchase

orders through the PO Change History menu item in the Oracle

Purchasing Nav igator. This men u item uses a Web browser to display

the archived revisions. You can compare the current p urchase order

with a previous revision or view a ll past changes to the purchase order.

You can see what fields changed an d w hat the fields were before and

after the change. This menu item is also part of Oracle Self–Service

Web Ap plications, if you have access to th e Purchasing responsibility

within O racle Self–Service Web Ap plications.

To nav igate to this w indow from the Oracle Purchasing responsibility,

choose Purchase Orders > PO Chan ge History.

See also: .




Quick Access to Particular Purchase Orders or Requisitions

Please note the following ad ditional information about p urchase orders

or requ isitions placed in the Oracle App lications N avigator.

Once you p lace a documen t in the N avigator, it is the first thing you see

in the Navigator the next time you log into Purchasing. Choose

Functions to return to the Purchasing menu .

Purchasing Documentation Updates

Documents

Transcript of Purchasing Documentation Updates