apupd

8/4/2019 apupd

1/29

OraclerPayables

DocumentationUpdateRELEASE 11.0.2

October 1998

Enabling the Information AgeT

8/4/2019 apupd

2/29

Oracle Payables Docum entation Upd ate

Copyright E 1997, 1998. Oracle Corporation . All rights reserv ed.

Primary Auth ors: Joseph Mu rph y, Christina Ravaglia

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

disclosure and are also protected by copyright, patent and other intellectual and industrial property

laws. Reverse engineering, disassembly or decompilation of the Programs is prohibited.

The information contained in this d ocument is subject to change withou t notice. If you find an y problemsin the documentation, please report them to us in wr iting. Oracle Corporation does not warran t that this

docum ent is errorfree. Except as may be expressly permitted in your license agreement for these

Programs, no part of these Programs m ay be reprodu ced or transmitted in any form or by any m eans,

electronic or mechanical, for any pu rpose, without the express written p ermission of Oracle Corporation.

If the Programs are delivered to the US Government or anyone licensing or u sing the Programs on behalf ofthe US Government, the following notice is applicable:

Restricted Rights Notice

Programs d elivered su bject to the DOD FAR Sup plement are commercial compu ter software and u se,

du plication an d d isclosure of the Programs including d ocumentation, shall be subject to the licensing

restrictions set forth in the app licable Oracle license agreement. Other wise, Programs delivered subject to

the Federal Acquisition Regulations are restricted compu ter software and use, du plication an d disclosure

of the Program s shall be su bject to the rest rictions in FAR 52.22719, Commercial Compu ter Software Restricted Rights (Jun e 1987). Oracle Corporation, 500 Oracle Parkw ay, Redw ood City, CA 94065.

The Programs are not intended for use in any nu clear, aviation, mass transit, medical, or other inherently

dangerou s app lications. It shall be licensees responsibility to take all approp riate failsafe, backup ,

redun dan cy and other m easures to ensure the safe use of such app lications if the Programs are used for

such pu rposes, and O racle disclaims liability for any d amages caused by such u se of the Programs.

Oracle is a registered trademark, and Enabling the Information Age, Oracle7, Oracle8, Oracle Alert, OracleApp lication Object Library, Oracle Discoverer, Oracle Financials, Oracle Workflow, PL/ SQL, Smar tClient,

SQL*Connect, SQL*Forms, SQL*Loader, SQL*Plus, SQL*Report, Oracle Web Customers, and Oracle Web

Employees are trademarks or registered trad emarks of Oracle Corporation.

All other comp any or p rodu ct names are mentioned for identification pu rposes only, and m ay be

tradem arks of their respective owners.

8/4/2019 apupd

3/29

About This Documentation Update

This docum ent contains impor tant information. Please read this

document for the latest upd ates and ad ditions to the Oracle Payables

Users Guide. If you have Release 11.0.2 insta lled, please read this en tire

docum ent. If you d o not have Release 11.0.2 installed, read only the

first section, Oracle Payables Docum enta tion Up date, Release 11.0.1.

8/4/2019 apupd

4/29

1Documentation Up date

Oracle Payables Documentation Update, Release 11.0.1

This section contains important information. Please read th is section

for the latest up dates and add itions to your u sers guide.

Payables Open Interface

The following areas of the docum entation on the Payab les Open

Interface Tables are incorrect. Please refer to the Oracle Payables

Applications Technical Reference Manual, Release 11 for a correct list of the

colum ns in the Open Interface Tables. In add ition, you can dow nload

up dated d ocumen tation for the Open Interface Tables on Oracles

MetaLink w eb site.

Correction to Sequential N umbering

Users shou ld ignore the following incorrect text in the Other Invoice

Values Assigned During Payables Open In terface Importsection ofth e Open

Interface Tables Appendix :

VOUCHER NUMBER. If you u se autom atic sequent ial

num bering, then the import program p opu lates the

AP_INVOICES.DOC_SEQUENCE_ID and

AP_INVOICES.DOC_VALUE columns, and enter s STD INV as

the AP_INVOICES.DOC_CATEGORY_CODE.

See

Other Invoice Values Assigned Dur ing Payables Op en Interface Impor t

(Oracle Payables Users Guide)

Additional Important Information on Sequential Numbering

The following information on sequential nu mbering is correct.

There are two m ethods you can u se for sequential num bering w hen

you u se the Payables Open Interface:

Manual Entry without Audit. Dur ing Payables Open Interface

Import, any value entered in the colum n

AP_INVOICES_INTERFACE.VOUCH ER_NUM will be in serted

in AP_INVOICES.VOUCH ER_NUM without validation.

8/4/2019 apupd

5/29

2 Oracle Payables

Automatic Voucher Numbering with Audit:A value w ill be

obtained au tomatically for the record being imported and w ill be

popu lated in AP_INVOICES.DOC_SEQUENCE_VALUE. Also,

aud it information w ill be inserted into the aud it table.

If you enter a valu e for DOC_CATEGORY_CODE, then Payables willignore any value you en ter for VOUCH ER_NUM, so automatic

voucher num bering w ill always sup ersede m anual entry.

See

Payables Open Interface Tables (Oracle Payables Users Guide)

Payables Open Interface Report

There are five add itional rejections tha t app ear on the Payables Open

Interface report to iden tify invoices that were rejected because of

sequential numbering p roblems:

Category not needed. The Sequen tial Num bering profile option

is set to N ot Used, and you have entered a value for

DOC_CATEGORY_CODE.

Invalid Category. Payables u ses the Inva lid Category rejection

for one of the following three reasons: 1) The Document

Category Payables option is enabled and you h ave entered one

of the following values for DOC_CATEGORY_CODE: INT INV,

MIX INV, DBM INV, CH ECK PAY, CLEAR PAY, EFT PAY,

FUTURE PAY, MAN FUTURE PAY, PREPAY INV, REC

INV, WIRE PAY, EXP REP INV, 2) You en tered StandardInvoices as the DOC_CATEGORY_CODE and the invoice

amou nt is less than zero, or you entered Credit Memo Invoices

and th e invoice amoun t is greater than zero. Or, 3) The

docum ent category specified is not valid in

FND_DOC_SEQUENCE_CATEGORIES for AP_INVOICES or

AP_INVOICES_ALL.

Override Disabled. The Sequen tial Num bering profile option is

set to Partial or Always, you have entered a va lue for

DOC_CATEGORY_CODE, and the Allow Document Category

Override Payables option is disabled. You cannot enter a value

in this column un less you enable the Allow Docum ent Category

Override Payables option.

8/4/2019 apupd

6/29


Invalid Assignment. You h ave entered a valid value for

DOC_CATEGORY_CODE, but the docum ent category does not

have an active, autom atic sequence assigned to it.

Invalid Sequence. The document category you entered h as a

valid, automat ic sequence assigned to it. However, Payableswas unable to retrieve the next value from the sequence.

The following rejection d escription is correct and shou ld rep lace the

description in the d ocum entation:

Account Required. Accoun ting information is m issing for this

line.

See

Payables Open Interface Report (Oracle Payables Users Guide)

No Foreign Key Relationships in Payables Open Interface Tables

Although colum ns are valida ted against colum ns in other tables, the

tables have no foreign key relationships as ind icated in th e PayablesOp en Interface Table Description s section ofth e Open In terface Tables

Appendix:

Incorrect Columns in the Payables Open Interface Tables

The following colum n information is incorrect in th e Payables Open

Interface Table Descrip tions section ofthe Open Interface Tables

Appendix:

The AP_INVOICES_INTERFACE table does notinclud e the following

columns:

PO_HEADER_ID

PO_NUMBER_ID

The following colum n nam es in the d ocumen tation for

AP_INVOICE_LINES_INTERFACE are incorrect:

ACCOUN T should be ACCOUN T_SEGMENT

COST_CENTER shou ld be COST_CENTER_SEGMENT

8/4/2019 apupd

7/29

4 Oracle Payables

Additional Columns in the AP_INVOICES_INTERFACE table

The following colum n information is missing from the section ofthe

Open Interface Tables Appendix:

The AP_INVOICES_INTERFACE tab le includ es the following

add itional colum ns:

DOC_CATEGORY_CODE. If you are u sing autom atic sequential

nu mbering, then Payables Open Interface Imp ort uses this column to

assign a d ocumen t category to the invoice it creates.

If the Sequen tial Nu mbering p rofile value is Always and you d o not

enter a value in this colum n, then d uring imp ort Payables w ill useStandard as the category if the invoice amoun t is positive, and

Credit if the invoice amou nt is negative. We assume that a valid

automatic sequence exists for such categories.

If you enable the Allow Docum ent Category Override Payables option,

you can enter the d ocum ent category you w ant Op en Interface Imp ort

to assign to th e invoice created from this record, instead of the

Stand ard or Cred it documen t category.

The value is a valid value in

AP_INVOICES.FND_DOC_SEQUENCE_

CATEGORIES. Do not enter a valu e in this column

un less the Sequen tial Num bering profile option is

set to Partial or Always, and the Allow Docum ent

Category Override Payables option is enabled. If

you enter th e value of Stand ard, then the invoice

amou nt m ust be p ositive, and if you enter thevalue of Credit, then the invoice amou nt m ust be

negative.

If you en ter a documen t category, it mu st have an

active, autom atic sequence assigned to it.

AP_INVOICES.DOC_CATEGORY_CODE

Validation:

Destination:

8/4/2019 apupd

8/29


VOUCHER_NUM. If you u se manu al sequential num bering, then

enter a unique value for the voucher nu mber you w ant to app ly to the

invoice created from this record. The num ber should n ot exceed n ine

digits.

If you use automatic sequen tial numbering ,Payables ignores any value you load into th is

colum n and instead selects the next available

num ber for the nu mbering sequence assigned to

the docum ent category for imp orted invoices. The

system does not validate the num ber you enter

here.

AP_INVOICES_ALL.VOUCHER_NUM

In addition, the AP_INVOICES_INTERFACE table includ es the

following colum ns which will be used in a futu re release. Do not enter

data in these columns:

GOODS_RECEIVED_DATE

INVOICE_RECEIVED_DATE

PAYMENT_METHOD_LOOKUP_CODE

PAY_GROUP_LOOKUP_CODE

Additional Columns in the AP_INVOICE_LINES_INTERFACE table

The following colum n information is missing from the section ofthe

Open Interface Tables Appendix:

The AP_INVOICE_LINES_INTERFACE tab le includ es th e following

add itional colum n:

USSGL_TRANSACTION_CODE. Enter the default transaction code

you w ant to assign to an invoice.

If you use Oracle Public Sector General Ledger, you may be requ ired to

maintain US Stand ard General Ledger information for your invoice

transactions. Open Interface Imp ort imports any USSGL information

that you load into the interface tables and assigns the information to

the invoices it creates.

None

AP_INVOICES.USSGL_TRANSACTION_CODE

Validation:

Destination:

Validation:

Destination:

8/4/2019 apupd

9/29

6 Oracle Payables

In ad dition, the AP_INVOICE_LINES_INTERFACE table includ es the

following colum ns which will be used in a future release. Do not enter

data in these columns:

ASSETS_TRACKING_FLAG

INCOME_TAX_REGION

STAT_AMOUNT

TYPE_1099

Additional restriction for UNIT_PRICE column

The value you enter here must be a positive num ber. This release of

Open Interface Imp ort does not su pp ort price corrections.

Purchase Order Matching Tolerance Restrictions

If you m atch an invoice to a pu rchase order, then d uring Payables Open

Interface Import, Payables will impor t invoices only if they a re within

the qu antity and price tolerance you have specified in the InvoiceTolerances w indow.

See

Invoice Tolerances (Oracle Payables Users Guide)

Web Employees Expense Reporting

Adding Custom Business Logic

Web Emp loyees includ es two functions that support the ad dition of

custom bu siness logic. By adding logic to the

CUSTOMDEFAULTCOSTCENTER function, you can custom ize the

behavior of the Cost Center default value in the N ew Expense Reportwind ow. By ad ding logic to the CUSTOMVALIDATECOSTCENTER

function, you can customize the validation of cost center values

subm itted w ith an expense report via Web Expenses. You can find

hooks to these two functions in the

$AP_TOP/ admin/ sql/ apwd fcfb.pls file.

8/4/2019 apupd

10/29


CUSTOMDEFAULTCOSTCENTER

When an em ployee navigates to the New Expense Report

wind ow, a default value au tomatically app ears in the Cost

Center field. This default cost center value is extracted from the

DEFAULT_CODE_COMBINATION _ID column of th eHR_EMPLOYEES_CURRENT_V view. You can overr ide th is

default behavior with custom cost center defaulting by add ing

logic to the CUSTOMDEFAULTCOSTCENTER function.

To custom ize the CUSTOMDEFAULTCOSTCENTER function,

design you r code so that the function return s a (cost center)

value. If the CUSTOMDEFAULTCOSTCENTER function returns

a value of nu ll, the stand ard d efault value appears in the Cost

Center field of the New Expense Report w indow. If theCUSTOMDEFAULTCOSTCENTER fun ction retu rns a va lue,

then th is value app ears as the default cost center value.

CUSTOMVALIDATECOSTCENTER

When an emp loyee subm its an expense report, Web Emp loyees

checks whether th e cost center iden tified in the expense report is

a valid value as d efined in your chart of accoun ts. If the cost

center is not va lid in you r chart of accoun ts, Web Employees

alerts the employee with an error message. You can override this

validation behavior with custom cost center validation by

adding logic to th e CUSTOMVALIDATECOSTCENTER function.

To customize the CUSTOMVALIDATECOSTCENTER function,

design you r code so that the fun ction return s a value of TRUE. If

the CUSTOMVALIDATECOSTCENTER function retu rns the

value TRUE, it notifies Web Employees tha t custom cost centervalidation has been used , and to therefore skip the p redefined

cost center validation routine. In add ition, set the parameter

p_CostCenterValid to TRUE or FALSE.

If you use the CUSTOMVALIDATECOSTCENTER function, you

can customize the error message that ap pears w hen the

validation fails. To customize this error m essage, give a value to

the p_cs_error variable. If you d o not customize the error

message, Web Expenses displays the stand ard error m essage.

Suggestion: To use custom da ta stored in th e OracleApp lications database with these two functions, you m ustregister all new custom tables within Oracle Applications. See:Oracle Applications Developers Guide.

8/4/2019 apupd

11/29

8 Oracle Payables

Attention: Subsequ ent releases of Oracle Applications m ayinterfere with the prop er fun ctioning of the custom p roceduresthat you w rite. You are responsible for the sup port andup grad e of the logic within these custom procedu res.

Suggestion: Make a copy of all custom code and place it in adirectory protected from up grad e. After an up grad e, ifapp ropriate, reapp ly any custom code.

Manual Payments

Reversing Posted Manual Payments

You can reverse a m anual p ayment th at has been p osted.

Voucher N umbers

Payables Limitation of Nine Digits

In Payables you m ust notuse voucher nu mbers that exceed nine digits.

Payables is unab le to process transactions with voucher num bers thatexceed n ine digits.

See

Voucher Numbers (Oracle Payables Users Guide)

Automatic Tax Calculation

Addition to Setting the Tax Name Source Hierarchy to Duplicate

Functionalit y in Prev ious Releases

The following text needs to be add ed to the Setting the Tax Name Source

Hierarchy to Duplicate Functionality in Previous Releases discussion of the

Entering Taxes on Invoices d iscussion in th e Invoices chap ter:

Note: If your Validate Tax from PO Payables option was enabledbefore the up grad e, Payables will not autom atically set the

hierarchy during the up grade.

Foreign Currency Invoices

Payables calculates the withh olding tax amoun t for foreign currency

invoices by using the functional currency am oun t of the invoice.

8/4/2019 apupd

12/29


Automatic Offsets

Additional Restriction Regarding Interest Liability Account

Automatic Offsets has an ad ditional restriction:

INTEREST LIABILITY ACCOUN T. Payables does not

overwrite the interest liability accoun t if you have enabled

Autom atic Offsets.

See

Automatic Offsets Restrictions (Oracle Payables Users Guide)

Defining and Maintaining Payment Documents

Additional Requirement For Future Dated Payment Documents

When you d efine a payment d ocum ent for a bank account, you mu st

enter a Cash Clearing Accoun t if you u se a Futu re Dated PaymentMethod.

See

Defining and Maintaining Payables Paym ent Docum ents (Oracle

Payables Users Guide)

Reporting Entities

Additional Information Regarding Assigning Balancing Segments

When you define a tax reporting entity, balancing segment valu es must

be un ique across reporting entities. Therefore, the list of values for the

Balancing Segmen t field of the Reporting Entity w indow disp lays only

balancing segments not already assigned to other reporting entities.

See

Reporting Entities (Oracle Payables Users Guide)

8/4/2019 apupd

13/29

10 Oracle Payables

Allow Matching Account Override Payables Option

Correction to Payables Option Name

All references to the Allow Flexfield Override Payables option should

be replaced w ith references to the Allow Matching Account Ov erridePayables option.

See

Adjusting Invoices (Oracle Payables Users Guide)

Adjusting Invoice D istributions

Correction to Adjusting Invoice D istributions

The introd uctory paragrap h of this discussion in the Invoices chapter

should n ot include the second sentence, and should instead read as

follows:

If you have not yet posted an invoice distribution and if you do

not u se Autom atic Offsets, you can up da te most of the invoice

distribution d etails, including accounting information,

Descript ion, GL Date, Income Tax Type, Withholding Tax Grou p,

and Income Tax Region. If the d istribution has not been posted

and the distribution has an expense type accoun t, you can also

ad just th e Track as Asset check box. For more information on

changing a p articular field, see the Invoice Ad justm ent chart.

See

Adjusting Invoice Distributions (Oracle Payables Users Guide)

8/4/2019 apupd

14/29


Reconciling Payables Activity/Accounts Payable Trial Balance Report

Additional Information Regarding Payment GL Periods

The following text should be add ed to theReconciling Payables Activity

discussion in the Posting chap ter:

Note: Before runn ing your reports, be sure you have run

Payables Transfer to General Ledger Program with a p ost date

that includes all of the period th at you are reconciling.

Note: When reviewing your Accoun ts Payable Trial Balance

Reports, you m ay notice that the remaining am oun t for a given

invoice is less than you expect or even negative. This may be

caused by recording invoice paym ents in a GL period that

precedes the GL period u sed to record some or all of your

invoice d istributions.

For example: You en ter an invoice with one d istribu tion of $200

that uses a GL date of 04JAN 2000. You p ay th e full invoice

using a GL date of 20DEC1999. If you su bmit the Accounts

Payable Trial Balance report a s of 31DEC1999, then the invoice

will correctly show an amou nt rem aining of .

Payables allows the paym ent GL date to precede the invoice GL

date to supp ort certain accoun ting meth ods (e.g. recording

prepaid items).

See

Reconciling Payables Activity (Oracle Payables Users Guide)

1099 Reporting

Additional Information Regarding TINs

If you en ter n ine zeros, 000000000, as the value for the Tax

Identification N um ber (TIN) for a sup plier, then the TIN will app ear asnu ll on th e following reports: 1099 Tape, 1099 Form s, or the Tax

Inform ation Verification Letter. You can en ter th is value (000000000)

for sup pliers that are waiting for their TINs, and for whom you need to

record 1099 payments.

See

1099 Report ing Overview (Oracle Payables Users Guide)

8/4/2019 apupd

15/29

12 Oracle Payables

1099 Forms

Additional Parameters

There are two new p aram eters for this report:

Supplier Number. If you w ant to submit the report for a single

sup plier, enter the supp lier num ber. Leave this param eter blank

to subm it the report for all supp liers.

Telephone Number. Enter the telephone number of the person

in your organization w hom the payee shou ld call if there are

questions regard ing the 1099 Form.

See

1099 Forms (Oracle Payables Users Guide)

Invoices Window

Additional Fields

The invoices wind ow has two ad ditional fields:

Functional Currency. Payables displays th e functional currency

for your set of books.

Functional Amount. If the invoice currency is different from

your functional currency, Payables displays the invoice amou nt

in you r fun ctional currency.

See

Invoices Window Reference (Oracle Payables Users Guide)

8/4/2019 apupd

16/29


Maximum Shipment Amount Hold/Invoice Tolerances

Correction to Matching Holds

App roval app lies this hold to an invoice if the invoice is matched to a

pu rchase order shipm ent, and the total amount (in transactioncurrency) of all invoice amoun ts matched to a shipm ent exceeds the

Shipm ent Amou nt tolerance. You specify the Shipm ent Amou nt

tolerance in the Invoice Tolerances window.

See

Invoice Tolerances (Oracle Payables Users Guide)

Defining Suppl ier Bank Accounts

Correction Regarding EDI Number

In the task, To define a supplier bank account, step 2 instructs the user to

enter an EDI ID nu mber:

To define a supplier bank account:

1 In th e Ban ks w in dow qu ery an existin g Ban k.

2. Choose the Bank Accounts but ton. Enter the Bank

Accoun t Nam e and Bank Accoun t Number. Enter the EDI ID

nu mber. Op tionally enter an Accoun t Type and Description.

Opt ionally change the account currency, wh ich d efaults fromyour functional currency.

EDI ID is not a required field. The EDI ID nu mber is u sed on ly if you

hav e insta lled Oracle Energy. If you have not installed Oracle Energy,

you can leave this field n ull. The system will ignore any valu e you

enter in this field.

See

Defining Sup plier Bank Accoun ts (Oracle Payables Users Guide)

8/4/2019 apupd

17/29

14 Oracle Payables

Electronic Payment Region of the Suppliers and Supplier Sites Window s

Region N ame Correction to Electronic Data Interchange

The user s gu ide incorrectly refers to this region of the Supp liers and

Sup plier Sites wind ows as the Electronic Payment region. Referencesshou ld instead be to the Electronic Data Interchange region.

See

Electronic Paymen t Region of the Sup pliers and Sup plier Sites

windows (Oracle Payables Users Guide)

Invoice Amount Hold

Correction to Invoice Amount Limit Text

In the Control Region of the Suppliers and Supplier Sites windows, the

description for Invoice Amou nt Limit is incorrect. The text states:

Invoice Amount Limit. If you enter an invoice for a sup plier site

that exceeds th e invoice amou nt limit you specify, Payables

app lies an Amoun t hold to the invoice du ring Approval. This

hold w ill also app ly to EDI invoices you import. You cannot pay

the invoice until you release the hold. You can release the hold

by adjusting the invoice amou nt or you can man ually release the

hold in the H olds window of the Invoice Workbench.

During m anual invoice entry Payables app lies this hold w hen youcommit, not du ring Approval. For invoices you have imported ,

Payables applies this hold wh en you ru n Ap proval after you have

imported them . The text shou ld read as follows:

Invoice Amount Limit. If you enter an invoice for a sup plier site

that exceeds th e invoice amou nt limit you specify, Payables

app lies an Am ount h old to the invoice when you save it.

Payables also app lies this hold w hen you submit Ap proval forinvoices after you import invoices. You cannot pay the invoice

un til you release the hold. You can release the hold by adjusting

the invoice amount or you can man ually release the hold in the

Hold s wind ow of the Invoice Workbench.

8/4/2019 apupd

18/29


Update Income Tax Details Utility and Report

Correction to Location of Income Tax Type Field

This text incorrectly states that the Income Tax Type field is in the

Supp lier Sites window. The field is in the Tax Reporting region of theSup pliers window only.

See

Upd ate Income Tax Details Utility and Report (Oracle Payables Users

Guide)

1099 Suppliers Exception Report

Additional Text for Report Parameters: Start Date and End Date

Start Date. Enter the start d ate, in the form at DDMONYY, for

the range of supp liers with paid or pa rtially paid invoices that

you w ant to include in this report. Payables includes all 1099sup pliers with exceptions for which you entered invoices with

invoice dates on or after the Start Da te you specify.

End Date. Enter the end date, in the format DDMONYY, for

the range of supp liers with paid or pa rtially paid invoices that

you w ant to include in this report. Payables includes all 1099

sup pliers with exceptions for which you have entered invoices

with invoice da tes on or before the End Date you specify.Also, sup pliers can ap pear on th is report w ithout invoices in the

specified d ate range if Reportable Supp liers On ly is No

See

1099 Supplier Exceptions Report (Oracle Payables Users Guide)

CCID

Clarification of CCID

CCID refers to the complete accounting flexfield, includ ing balancing

segment , accoun t, and cost center.

8/4/2019 apupd

19/29

16 Oracle Payables

Expense Reporting Workflow

Additional Workflow Diagrams

The following are ad ditional workflow d iagrams:

AP Standard Expense Report Process

Manager (Spending) Approval Process

8/4/2019 apupd

20/29


Missing Receipts Shortpay Process

No Manager Response Process

8/4/2019 apupd

21/29

18 Oracle Payables

Policy Violation Shortpay Process

Rejection Process

8/4/2019 apupd

22/29


Request Approval Process

Server Side Validation Process

8/4/2019 apupd

23/29

20 Oracle Payables

Shortpay Unverified Receipt Items Process

Third Party Expense Report Process

See

Expense Reporting Workflow (Oracle Payables Users Guide)

8/4/2019 apupd

24/29


Credit Card Transaction Employee Workflow



Procurement Card Employee Verification Parent Process

Procurement Card Transaction Employee Verification

See

Credit Card Transaction Employee Workflow (Oracle Payables Users

Guide)

C dit C d T ti M W kfl

8/4/2019 apupd

25/29

22 Oracle Payables

Credit Card Transaction Manager Workflow



Procurement Card Manager Approval Parent Process

Procurement Card Transaction Manager Approval Process

Manager Rejection of PCard Transactions Process

8/4/2019 apupd

26/29


Manager Rejection of PCard Transactions Process

See

Credit Card Transaction Manager Workflow (Oracle Payables Users

Guide)

Oracle Payables Documentation Update Release 11 0 2

8/4/2019 apupd

27/29

24 Oracle Payables

Oracle Payables Documentation Update, Release 11.0.2

In Release 11.0.2 the following features and changes are new in Oracle

Payables and Web Employees.

Web Employees and Oracle Projects Integration

Employees can enter Oracle Projects information on expense reports

created via Web Employees. Web Employees validates the

projectrelated information and creates expense item GL accoun ts

according to ru les defined in Oracle Projects.

See

Oracle Web Employees and Oracle Projects In tegration Documentation

Supplement, in the Oracle Projects Documentation Up da te.

Profile Option

A new profile option has been ad ded to supp ort Web Emp loyees and

Oracle Projects Integration:

WebExpenses:Enable Projects

Web Employees Function

A new function, View Projects and Tasks, has been added to the

Expense Reports responsibility of Web Employees. A view,

AP_WEB_PA_PROJECTS_TASKS_V, has been created to sup port th e View

Projects and Tasks function.

Web Applications Dictionary

Three new regions have been ad ded to the Web App lications

Dictionary:

AP_WEB_PA_PROJ_TASK

AP_WEB_PA_TASKS_LOV

AP_WEB_PA_PROJECTS_LOV

Expense Report Templates

A new field, Projects Expend iture Type, has been ad ded to the Expense

Report Temp lates wind ow. A column, PROJ_EXPENDITURE_TYPE , has

been added to the AP_EXPENSE_REPORT_PARAMS table.

Client Extension

8/4/2019 apupd

28/29


Client Extension

A client extension, CustomValidateLine, has been ad ded to sup port

validation of projectrelated information en tered on expense reports in

Web Employees.

Refund Tracking

Employees can enter negative receipts (credit lines) when creating an

expense report in Web Emp loyees. An employee enters a negative

receipt to report the refun d of a previously reimbursed expense, for

example, the refund of an u nu sed airline ticket.

Expense Reporting Workflow

Three mod ifications have been m ade to the Expense Reporting

Workflow to supp ort refun d tracking.

A n ew activity,Level of Manager Involvement, has been add ed to

theManager (Spending) Approval Process. The default behavior of

theLevel of Manager Involvementactivity requires man ager

approval wh enever an expense report contains one or m ore

positive expense lines. If an expense rep ort contains only credit

lines, then the default behav ior requires only man ager

notification. This ensures that manager ap proval is necessary for

every expense report th at contains an expense line, even if the

total amou nt of an expense report is less than or equ al to zero.

For examp le, an expense report th at consists of one expense line

of 400 and one credit line of 500 would require manager

app roval, even th ough the total amount of the expense report is

negative (100).

The Verify Authority activity in theManager (Spending) Approval

Process has been mod ified so that it comp ares the sum of the

positive expense lines in an expen se report to the signing limit of

the approver. The activity ignores credit lines. This ensu res that

a manager w ith a signing limit of 1000 cannot ap prove an

expense report that contains a positive expense line of 1200 and a

credit line of 1000, even th ough the total am oun t of the expensereport (200) falls below h er signing limit. Since the sum of the

positive expense lines (1200) exceeds her s igning lim it total

(1000), the Verify Authority activity determ ines that she cannot

app rove the expense report.

A new activity, Credit Lines Only, has been add ed to theAP

A pproval Process. The Credit Lines Only activity au tomatically

gives Accounts Payable app roval to an expense report that

8/4/2019 apupd

29/29

26 Oracle Payables

g y pp p p

contains only credit lines.

Profile Options

A new profile option h as been add ed to sup port Refund Tracking:

WebExpenses:Allow Cred it Lines