accrual account definition-

If the destination type is Expense then the Accrual account is populated from

the Purchasing Options Expense AP accrual account.

Navigation: Purchasing Resp > Setup > Organizations > Organizations > Purchasing

Options

If the destination type is Inventory the accrual account is populated from

the receiving Organization’s Organization Parameters region.

Navigation: Setup > Organizations > Query the Inventory Org > Organization

Classifications > Organization Parameters > Other accounts > Inventory

AP accrual account

Disabling correction button in Oracle Payable invoices

open Oracle Invoice Form,

go to Help> Personalization.

Seq: 10

=========

Description: e.g Hide Correction

Level: Form

Condition:

=========

Trigger Event : WHEN-NEW-FORM-INSTANCE

Trigger Object :

Condition : Null

Processing Mode :Both

Context (Tab)

=======

Level :Responsibility

Value :<Enter the Responsibility> or <Enter User>

Or

Leave it at Site

Actions (Tab)

=======

Seq : 10

Type :Property

Language : All

Enabled : Checked

Object Type : Item

Target Object: INV_SUM_CONTROL.CORRECTIONS

Property Name :DISPLAYED

Value:FALSE

Save and Apply

Exit the Form and Open it again,

Corrections button shouldn't be displayed, and form data entry shouldn't encounter any issue

Duplicate Invoice Number With Different Supplier Site allowed (Doc ID 1674300.1)

APPLIES TO:

Oracle Payables - Version 12.0.1 and later
Information in this document applies to any platform.

SYMPTOMS

 The Invoice Workbench is allowing users to enter duplicate invoice numbers as long as the supplier site is different.

CAUSE

As per Doc ID 1282143.1 there was an Enhancement created where you can create invoices using the same invoice number from the same supplier with different supplier sites.  This functionality was provided by Patch 9105666:R12.AP.A/B.

SOLUTION

If you would prefer this was not allowed, a workaround can be setup using the following personalizations, which still allow the duplicate invoice number to be created, but present a warning message letting the user know they created the duplicate invoice number.
Both personalizations below, need to be used for the warning message to appear and they are meant to work when profile option AP: Use Invoice Batch Controls is switched to NO.

PERSONALIZATION 1
--------------------------

Function Name: AP_APXINWKB (system created)
Form Name: APXINWKB (system created)
Debug Mode: Off (system created)

Sequence: 10
Description: XX_DUP_INVOICE_NUM_1
Level: Function
Enabled: Checked

Condition:
Trigger Event: PRE-INSERT          **(If pre-insert is not in your LOV, you can just type it in)
Trigger Object: << leave blank, will be grayed out >>
Condition:

   0 <(select count(*) from ap_invoices_all ai
   where invoice_num =:INV_SUM_FOLDER.INVOICE_NUM
   and vendor_id =:INV_SUM_FOLDER.VENDOR_ID
   and org_id    = :INV_SUM_FOLDER.org_id
   and ((:inv_sum_folder.invoice_id IS NULL) OR :inv_sum_folder.invoice_id <> ai.invoice_id))

Processing Mode: Both

Context: <I would recommend setting this to whatever responsibility you enter invoices>

Actions:
Sequence: 10
Type: Message
Description: <null>
Language: All
Enabled: Checked

Message Type: Warn
Message Text: You have entered duplicate Invoice Number for same Supplier. Please Use Different Invoice Number.


PERSONALIZATION 2
--------------------------

Function Name: AP_APXINWKB (system created)
Form Name: APXINWKB (system created)
Debug Mode: Off (system created)

Sequence: 10
Description: XX_DUP_INVOICE_NUM_2
Level: Function
Enabled: Checked

Condition:
Trigger Event: PRE-UPDATE          **(If pre-insert is not in your LOV, you can just type it in)
Trigger Object: << leave blank, will be grayed out >>
Condition:

   0 <(select count(*) from ap_invoices_all ai
   where invoice_num =:INV_SUM_FOLDER.INVOICE_NUM
   and vendor_id =:INV_SUM_FOLDER.VENDOR_ID
   and org_id    = :INV_SUM_FOLDER.org_id
   and ((:inv_sum_folder.invoice_id IS NULL) OR :inv_sum_folder.invoice_id <> ai.invoice_id))

Processing Mode: Both

Context: <I would recommend setting this to whatever responsibility you enter invoices>

Actions:
Sequence: 10
Type: Message
Description: <null>
Language: All
Enabled: Checked

Message Type: Warn
Message Text: You have entered duplicate Invoice Number for same Supplier. Please Use Different Invoice Number.

Auto assignment of Locator and Subinventory to Item

goal: How to assign Sub Inventory and Stock locator Automatically when you 
receive the items?

fact: Oracle Inventory 11.5 and later


Note : 
1. Navigation : Inventory -> Items -> Organisation Items -> Query for 
the Item-> Inventory Tab
2. Navigation : Inventory  -> Set Up -> Transactions -> Item 
Transaction Defaults

Ensure the Set Up as below
1.Set the locator control to the item level 
a).Set the flag "restrict sub-inventory" and "restrict locator" 
b).Set the locator control to "pre-specified" 

2.Define Locator name following the below Navigation
In  Item Transaction Defaults Window

a.Sub Inventories Tab 

 Enter Item ,  Value of Default for = Receiving , and  Sub Inventory value
b.Locators tab 
 Enter the Value of the Default Locator for  this Item and  ensure that the
 Value of Default for is Receiving.

Note :
Define at least one locator for an item in one inventory to use "Item 
Transaction Defaults"

YTD Depreciation Incorrect For Assets Added Via ADI and Mass Additions (Doc ID 189519.1)

APPLIES TO:

Oracle Assets - Version 11.5.10.0 to 11.5.10.0 [Release 11.5]
Information in this document applies to any platform.
This document is a replacement for 162929.1 which has been deleted.

SYMPTOMS

The year to date (YTD) depreciation for assets added with ADI is not as expected.  The assets were added via the mass additions interface table and were added with YTD depreciation and depreciation reserve.  

CAUSE

When performing a data conversion into Oracle Fixed Assets, two columns need to be populated in the FA_MASS_ADDITIONS interface table - the Amortize_NBV_Flag ('Y') and Amortization_Start_Date (date in the current FA period).

This is important for correct depreciation calculations when importing assets with accumulated depreciation.  The amortization start date should be a date in the currently open period in FA.  It is an as of or start from date.  The last or the first day in the open FA period could be used.

SOLUTION

Make sure that columns AMORTIZE_NBV_FLAG ('Y') and AMORTIZATION_START_DATE (date in current FA period) in the table FA_MASS_ADDITIONS are populated before posting.

what is table name for prepayment application

exec mo_global.set_policy_context('S',&org_id);

select * from AP_VIEW_PREPAYS_V where vendor_name='&vendor_name' and vendor_site_code='&vendor_site_code';