Wednesday, 10 June 2015

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

Tuesday, 9 June 2015

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

Monday, 8 June 2015

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"

Wednesday, 3 June 2015

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';

Sunday, 31 May 2015

How Are Purchase Orders Closed Automatically? Closed Status Rolled Up? PO's Are Not Closing? (Doc ID 1265680.1)

APPLIES TO:

Oracle Purchasing - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.

GOAL

What are the key components for moving the approved purchase orders to a closed status?

SOLUTION

There are various factors which must be considered that relate to the systematic closing of the Purchase Order Shipments, Lines and Headers. 

Factor 1 - Matching

2 Way Matching - Approve/Invoice
3 Way Matching - Approve/Invoice/Receipt
4 Way Matching - Approve/Invoice/Inspect/Receipt

The level of matching (2, 3,or 4) defaults in the following order:
Level 1 - Item if not found then
Level 2 - Line Type - if not found then
Level 3 - Supplier - Receiving Tab Options Area - if not found then
Level 4 - Purchasing Options



________





If Receipt Required is Yes and Inspection Required is No
– this is 3 way matching – meaning Approve/Receive/Invoice

If Receipt Required is No and Inspection Required is No
– this is 2 way matching – meaning Approve/Invoice

If Receipt Required is Yes and Inspection Required is Yes
– this is 4 way matching – meaning Approve / Inspect / Receive / Invoice

Take notice that Receipt Close Tolerance is also on the Item as well as Invoice Close Tolerance.
This is also the primary default for these values as well.

________





In the supplier screen – the match approval level can also be set. This is the second defaulting level in the hierarchy.

________





In the Line Type – there are two columns – Receipt Required and Receipt Close.
Receipt Required as Yes – serves as a 3 way match – No – would serve as a 2 way match.
You can name the line type anything – in this example 2 way match was given to help clarify.
Also, you see the receipt close tolerance – in this case is set at 100%. This will be explained in the tolerances section.

________





In the Purchasing Options – there are settings for Match Approval Level – Receipt Close – and Invoice Close tolerance. This is the last location that is checked for values – when entering a Purchase Order.

________


Factor 2 - Receive and Invoice Close Tolerances


The Receive and Invoice Close tolerances are entered based on percentages. 

The defaulting order of these tolerances is as follows:
Receipt Close Tolerance – Defaulting Hierarchy

Level 1
 – Item in the Item Master – if not found then
Level 2 – Line Type – if not found then
Level 3 – Purchasing Options

Invoice Close Tolerance - Defaulting Hierarchy

Level 1
 - Item in the Item Master - if not found then
Level 2 - Purchasing Options

The screen prints in Factor 1 also show the locations for entering the tolerance percentages.

Here is a quick link to the Purchase Order Defaulting Rules - Note 1067175.1.

________

The receipt close tolerance determines how much quantity must be received before a Purchase Order Shipment will move to the status of Closed For Receiving.

The invoice close tolerance determines how much quantity must be billed prior to moving to a status of Closed for Invoicing.

Once a purchase order/blanket release shipment has met both tolerance conditions for closing – as related to invoicing and receipt – the shipment will automatically close. The Closure Status for the shipment will show – Closed with a reason of  Status Rolled Up.

After all shipments have closed for a particular line – the closure status of the Line will become Closed as well. Finally, when all lines have closed on the purchase order – the header level of the Purchase Order will become closed.

________

Here is an example of how the receipt close tolerance works.

Suppose that a purchase order line has a quantity of 100.
The receipt close tolerance is 10%. This is seen on the Purchase Order Shipment – More TAB
10% of 100 is 10. Deduct this from the shipment total as 100 – 10 = 90.

This means that in order for this Purchase Order Shipment to move to a status of Closed for Receiving, at least a quantity of 90 or greater - out of the total 100 would need to be received/delivered.





Now, for 2 way matching – the desire is to only have to approve and then create an invoice. For this to work – it is necessary to have the receipt close tolerance come in as 100%. By putting in 100% - the system is being told that no receipt would need to be done – as 100% of the quantity is all quantity ordered.

By using 100% receipt close tolerance with 2 way match – the system will move the purchase order shipment immediately to Closed for Receiving. See below:





Here is a purchase order – that is having 2 way match – with 100% receipt close tolerance.
Notice the status tab – below – the shipment is already Closed for Receiving. This now sets up the system so that when the invoicing is conducted – and reaches within the invoice close tolerance – the purchase order shipment will be closed. In this case – the invoice close tolerance is 0% which means that this purchase order shipment would require the full amount to be invoiced. If the full amount is not billed – the shipment will remain in the Closed for Receiving status – and not close (roll up) automatically.





________

Factor 3 - Receipt Close Point

The receipt close point is a key component when using 3 and 4 way matching.  This determines when the closure process should be engaged for the Receive/Inspection portion of the Purchase Order Receipt.

The receipt close point is set in the Purchasing Options.





When a Purchase Order Receipt is conducted - it consists of two transactions - Receive and Deliver.
The Receipt Close Point tells the system when to determine/consider the shipment for Closure.

Receive is completed - Receiving/Receipts
Deliver is completed - Receiving/Receiving Transactions

Receipt Routing is set in the Purchase Order Shipment - Receiving Controls. There are three different types of Receipt Routing:
 - Standard Receipt - The Receive and Deliver will be done separately
 - Direct Delivery - The Receive and Deliver transaction are done at the time of Receive
 - Inspection Required - The Receive - Inspect - and Deliver are done separately

Here is an example:
 - Purchase Order - Line 1 - quantity 100 - and shipment is having Receiving Routing - Standard Receipt
 - The Receive Close Tolerance is set to 0% - meaning that the quantity will need to be fully Receipted
 - The Purchasing Options -  Receive Close Point is set to Deliver

The user enters Receiving/Receipts - and conducts the first portion of the Receipt.
 - The user does not conduct the Delivery of the receipt
 - The shipment will still be open - it will not goto Closed For Receiving - as the receipt close point is Deliver and the Deliver transaction has not yet been accomplished.

Now, in the above scenario - had the Receipt Routing on the Purchase Order Shipment - Receiving Controls - been Direct Delivery - then at the time the user conducted the Receive portion of  the Receipt - the Deliver would also have been done - which satisfies the Receipt Close Point of Deliver. This would move the shipment to Closed For Receiving.
Note: If receipt close point is set to 'Accepted' try changing to 'Receive' or 'Deliver' for automatic close.

What are the definitions of the Closure statuses:
Closed for Invoicing and Closed for Receiving:
Purchasing automatically closes your purchase order for receipt when it is fully received. You can manually close partially received purchase orders if you no longer expect any
more receipts against them. Close for invoicing and close for receiving are managed using tolerances. You can specify that when you have received a certain percentage
of a shipment, Purchasing will close the receipt. This is a soft close, and you can reopen the receipt. Purchasing rolls up closing to the line and header level, and
"Closed" information does not show in the Open Purchase Orders Report. Also, if there is a remaining balance, closed quantities are no longer visible as supply
scheduled receipts to MRP/ATP

Closed:
As the receiving and invoice tolerances are met on each shipment, the shipments will close - and as all shipments reach a closed status - the line will then close.
As all lines eventually close on the purchase order - the header will then close as well.  It is possible to use the purchase order summary to again Open a Closed Purchase Order.
Finally Closed:
Finally Closed status leaves the purchase order in a state where no further actions are possible.  Any supply picture should be removed as well as reversal of any uncumbered funds.
Once a Purchase Order is Finally Closed - no further actions are possible. Finally Close actions are done via the Purchase Order Summary - and are also possible during the invoice
match which is taking place from Oracle Payables - known as a Final Match.

________