Showing posts with label PAYABLES.. Show all posts
Showing posts with label PAYABLES.. Show all posts

Thursday, 23 February 2017

personalize Ap Invoice Actions Final Post

Goto the Invoice Form.

Navigate Help>Diagnostics>Custom Code>Personalize.

  • Enter the Following data:

            Seq = 10
             Description = Disable a radio button.

  • In the Condition tab enter the below,

         Trigger event = WhenNewFormInstance.
         Processing mode = Only in enter query mode.
         Level = Select the level  
  • Save
  • In the Actions Tab, enter the below,

         Seq = 10
         Description = Disable radio button.
         Object type = radio button
         Target Object = INV_SUM_ACTIONS.ACCOUNTING_DETAILS.FINAL_POST
         Property name = VISIBLE
         Value = False.

  • Save the work , close the form, reopen and retest the issue.

Tuesday, 28 June 2016

Query to get the Suppier Open balances upto particular date.

SELECT  ORG_ID,VENDOR_SITE_CODE SUPPLIER_SITE,SEGMENT1 Supplier_number,case when sign(sum(balance))=-1 then -1*sum(balance) else 0 end CR
                                ,case when sign(sum(balance))=1 then sum(balance) else 0 end DR from
                               (
SELECT VENDOR_NAME,vendor_id,SEGMENT1,
              vendor_site_code,
               invoice_currency_code,
               org_id,
               accts ,
               jai_ap_rpt_apcr_pkg.compute_credit_balance(TO_DATE(:p_as_of_date)+1,vendor_id,2021, vendor_site_code,org_id,invoice_currency_code,accts) CREDIT,
             jai_ap_rpt_apcr_pkg.compute_debit_balance(TO_DATE(:p_as_of_date)+1,vendor_id,2021, vendor_site_code,org_id,invoice_currency_code,accts) debit,
              jai_ap_rpt_apcr_pkg.compute_credit_balance(TO_DATE(:p_as_of_date)+1,vendor_id,2021, vendor_site_code,org_id,invoice_currency_code,accts) - jai_ap_rpt_apcr_pkg.compute_debit_balance(TO_DATE(:p_as_of_date)+1,vendor_id,2021, vendor_site_code,org_id,invoice_currency_code,accts) balance
               FROM (                
             
 SELECT      VENDOR_NAME,api.vendor_id,POV.SEGMENT1,
               povs.vendor_site_code,
               api.invoice_currency_code,
               api.org_id,
               api.accts_pay_code_combination_id accts ,
               api.gl_date
FROM   ap_invoices_all api,
              po_vendors pov,
              ap_supplier_sites_all  povs
WHERE        api.vendor_id = pov.vendor_id
AND       pov.vendor_id = povs.vendor_id
AND       api.vendor_site_id = povs.vendor_site_id
--AND jai_ap_rpt_apcr_pkg.compute_credit_balance(TO_DATE(:p_as_of_date)+1,vendor_id,2022, vendor_site_code,org_id,invoice_currency_code,accts) - jai_ap_rpt_apcr_pkg.compute_debit_balance(TO_DATE(:p_as_of_date)+1,vendor_id,2022, vendor_site_code,83,invoice_currency_code,accts) <> 0
AND        api.vendor_id = NVL(:p_vendor_id, api.vendor_id)
AND      pov.segment1  = NVL(:P_vendor_no,pov.segment1)
AND      (
                (:p_vendor_type_lookup_code is null)
                OR
                ( (:p_vendor_type_lookup_code is not null) and (pov.vendor_type_lookup_code = :p_vendor_type_lookup_code) )
               )
AND (api.gl_date)          <= nvl(:p_as_of_date,api.gl_date)
AND     (api.org_id = :p_org_id )
AND api.accts_pay_code_combination_id = nvl(:p_accts_id,api.accts_pay_code_combination_id)
GROUP BY api.vendor_id,
POV.SEGMENT1 ,
VENDOR_NAME,
               povs.vendor_site_code,
               api.invoice_currency_code,
               api.org_id,
               api.accts_pay_code_combination_id)      
 )
               WHERE  1= 1
               --and  BALANCE<>0
               GROUP BY ORG_ID,VENDOR_SITE_CODE,SEGMENT1
               order by SEGMENT1;
               

Sunday, 8 November 2015

Query to get the 11i Bank Accounts Setup Data

SELECT ABAA.SET_OF_BOOKS_ID,ABAA.ORG_ID,ABAA.CURRENCY_CODE,ABAA.MULTI_CURRENCY_FLAG,abaa.bank_account_id,abAa.bank_accounT_NAME,ABAA.BANK_ACCOUNT_NUM,
ABAA.CONTACT_FIRST_NAME AS BANKACC_CNCT_FIRST,
ABAA.CONTACT_MIDDLE_NAME  AS BANKACCT_CNCT_MID,ABAA.CONTACT_LAST_NAME AS BANKACC_CNCT_LAST,
ABAA.CONTACT_PREFIX,ABAA.CONTACT_TITLE,ABAA.INACTIVE_DATE,
ABAA.DESCRIPTION AS BANKACC_DESCRIPTION,ABAA.BANK_BRANCH_ID,ABAA.BANK_ACCOUNT_TYPE,ABAA.VALIDATION_NUMBER,ABAA.ACCOUNT_TYPE,ABAA.POOLED_FLAG,ABAA.ZERO_AMOUNTS_ALLOWED,
ABAA.RECEIPT_MULTI_CURRENCY_FLAG,ABAA.ALLOW_MULTI_ASSIGNMENTS_FLAG,ABAA.IBAN_NUMBER,
ABAA.ASSET_CODE_COMBINATION_ID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.ASSET_CODE_COMBINATION_ID) as ASSET_CODE_COMBINATION,
ABAA.GAIN_CODE_COMBINATION_ID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.GAIN_CODE_COMBINATION_ID) as GAIN_CODE_COMBINATION,
ABAA.LOSS_CODE_COMBINATION_ID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.LOSS_CODE_COMBINATION_ID) as LOSS_CODE_COMBINATION,
ABAA.CASH_CLEARING_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.CASH_CLEARING_CCID) as CASH_CLEARING,
ABAA.BANK_CHARGES_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.BANK_CHARGES_CCID) as BANK_CHARGES,
ABAA.BANK_ERRORS_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.BANK_ERRORS_CCID) as BANK_ERRORS,
ABAA.EARNED_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.EARNED_CCID) as EARNED,
ABAA.UNEARNED_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.UNEARNED_CCID) as UNEARNED,
ABAA.ON_ACCOUNT_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.ON_ACCOUNT_CCID) as ON_ACCOUNT,
ABAA.UNAPPLIED_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.UNAPPLIED_CCID) as UNAPPLIED,
ABAA.UNIDENTIFIED_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.UNIDENTIFIED_CCID) as UNIDENTIFIED,
ABAA.FACTOR_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.FACTOR_CCID) as FACTOR,
ABAA.RECEIPT_CLEARING_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.RECEIPT_CLEARING_CCID) as RECEIPT_CLEARING,
ABAA.REMITTANCE_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.REMITTANCE_CCID) as REMITTANCE,
ABAA.EDISC_RECEIVABLES_TRX_ID,
( select name from AR_RECEIVABLES_TRX_ALL where receivables_trx_id =  ABAA.EDISC_RECEIVABLES_TRX_ID) as EDISC_RECEIVABLES_TRX,
ABAA.UNEDISC_RECEIVABLES_TRX_ID,
( select name from AR_RECEIVABLES_TRX_ALL where receivables_trx_id =  ABAA.UNEDISC_RECEIVABLES_TRX_ID) as UNEDISC_RECEIVABLES_TRX,
ABAA.FUTURE_DATED_PAYMENT_CCID,
( select concatenated_segments from gl_code_combinations_kfv where code_combination_id =  ABAA.FUTURE_DATED_PAYMENT_CCID) as FUTURE_DATED_PAYMENT,
abb.bank_name,abb.bank_name_alt,abb.bank_branch_name,abb.bank_branch_name_alt,abb.description as bank_description,
abb.address_line1,abb.address_line2,abb.city,abb.state,abb.zip,abb.country,abb.institution_type
--acsa.name as check_name,acsa.banK_account_id,acsa.disbursement_type_lookup_code,acsa.check_format_id,acsa.last_document_num,acsa.last_available_document_num,acsa.num_setup_checks,
--acsa.inactive_date,--acsa,org_id,
--acsa.bank_charges_ccid,acsa.bank_errors_ccid,acsa.clearing_days,acsa.future_dated_payments_flag,acsa.cash_clearing_ccid--,acsa,transmission_code
FROM ap_bank_accounts_all abaa, ap_bank_branches abb
--,ap_check_stocks_all acsa,
  --ap_check_formats acf
 WHERE abaa.bank_branch_id = abb.bank_branch_id
-- AND abaa.BANK_ACCOUNT_ID=acsa.BANK_ACCOUNT_ID
 --AND acsa.CHECK_FORMAT_ID=acf.CHECK_FORMAT_ID
 --AND acsa.INACTIVE_DATE is null
   AND abb.end_date IS NULL
   AND abaa.account_type = 'INTERNAL'

Friday, 17 April 2015

Automatic Offset And Pooled Accounts In Oracle Payables

Automatic Offset And Pooled Accounts In Oracle Payables

PURPOSE OF AUTOMATIC OFFSETS AND POOLED ACCOUNTS

  • If you enter invoices for expense or asset purchases for more than one balancing segment,you may want to use Automatic Offsets to keep your Payables transaction entries balanced at the balancing segment level.
  •  For an invoice, Payables creates offsetting liability distributions; for a payment, Payables creates offsetting cash and discount taken distributions. This helps to ensure that each set of accounts remains balanced by balancing segment.
  •   Automatic Offsets was created for the government and higher education sectors where it is mandated by law that transactions be balanced to the balancing segment level. However, many companies may benefit from the option of having self–balancing sets of accounts. For example, if you have a product segment in your account, Automatic Offsets would allow you to track cash and AP liability by product.

Important: The level of detail that Automatic Offsets provides is only recommended either if it is mandated by law or if it is necessary to produce a balance sheet at a balancing segment level. There are restrictions associated with enabling Automatic Offsets. Be sure you understand the impact of Automatic Offsets before deciding to implement this feature.
  •  Alternatively, you can set up Intercompany Accounting in Oracle General Ledger so that General Ledger automatically creates the intercompany accounting entries necessary to balance a transaction at the balancing segment level.
  •  If you choose to use Intercompany Accounting rather than Automatic Offsets, your Payables transactions that cross multiple balancing segments will not balance at the balancing segment level until you transfer them to General Ledger and submit the Journal Import program.
  •  By enabling Automatic Offsets within Payables, Payables will automatically allocate the liability, discount taken, and gain and loss entries for a given invoice across multiple balancing segments, according to the balancing segments of the invoice distributions.

 If you pay an invoice from a pooled bank account, Payables will also automatically allocate the cash entry across multiple balancing segments, according to the balancing segments on the invoice distributions.

If you pay from a non– pooled bank account, Payables records the cash entry using the Cash Account you specify in the Banks window.
  • Entries in accounts other than liability, cash, discount taken, or realized gain/loss must have manual journal entries made in your general ledger in order to keep the entries balanced at the balancing segment level. Automatic Offsets will not affect these accounts. If you do not enable Automatic Offsets Payables records the liability, cash, discount taken, and gain and loss entries in the accounts you specify in the Payables Options and Banks windows.
  • These accounts have one balancing segment each, so if you enter transactions that cross multiple balancing segments, you may want to consider using the Intercompany Accounting feature to balance these transactions during posting.

Automatic offsets allows you to automatically balance invoice and payment distributions that cross balancing segments by creating offsetting entries for each balancing segment.

To determine if automatic offsets is right for your company, you should consider the following information:
1. Do you need the level of detail automatic offsets provides, either because it is mandated by law, or because you need to produce a balance sheet that will balance at the segment level?
2. Are you aware of the restrictions that Automatic Offsets enforces?
3. Are you aware of the alternatives?

You can set up Intercompany Accounting in Oracle General Ledger so that the General Ledger automatically creates the intercompany accounting entries necessary to balance a transaction at the balancing segment level.

SETTING UP AUTOMATIC OFFSETS AND POOLED ACCOUNTS

          Payables will automatically create balancing entries for your invoice and payment transactions when you enable Automatic Offsets. To use this feature, navigate to Payables options : Accounting region and select either Account or Balancing as your Automatic Offset Method.
        Account – Payables retains all segments but the distribution’ s account segment when it builds an offsetting account. Use this option if you want all of your accounts to preserve the same level of distribution detail.
     Balancing – Payables retains only the distribution’s balancing segment when it builds an offsetting account. Companies typically find this level of detail sufficient.
     Prorate Discounts – To prorate discounts across your invoice distributions when you pay an invoice that crosses multiple balancing segments, navigate to Setup&gt;Options&gt;Payables: Payment region and select System Account as your Discount Distribution Method.

 The balancing segment of your system Discount Taken Account is replaced by the balancing segment from the offsetting invoice distribution when Payables builds the accounts for these entries.
Pooled Account – To create a pooled account, navigate to Bank Accounts button; in the Payables Options region check the pooled account box.

If you enable Automatic Offsets, you cannot use any of the following Payables options:
      Allow Adjustments to Paid Invoices – When an invoice is paid or partially paid, you cannot adjust any accounting information on the invoice. Payables prevents you from updating or reversing any of the invoice distributions for paid or partially paid invoices because Payables has already created the payment distributions based on the current invoice accounting lines. Navigation: Setup&gt;Options&gt;Payables: Invoice Region – “Allow Adjustments to Paid Invoices”
    Allow Reconciliation Accounting – If you enable Automatic Offsets, Payables will not create reconciliation accounting entries, however you can still clear payments using Oracle Cash Management. Navigation: Setup&gt;Options&gt;Payables: Accounting Region – “Allow Reconciliation Accounting”
   Automatic Withholding Tax – You cannot use Automatic Withholding Tax if you have enabled Automatic Offsets in Payables. Navigation: Setup&gt;Options&gt;Payables: Withholding Tax Region – “Use Withholding Tax”


AUTOMATIC OFFSETS AND INVOICE PROCESSING

    When Automatic Offsets is used, Payables automatically allocates an invoice’ s liability amount across multiple balancing segments according to the balancing segments on the invoice distributions. This ensures that invoices always balance by balancing segment.

     Payables creates the liability distributions when you submit the invoice for Approval. You can review the liability distributions on the “Expense Distribution Detail Report.”

If you don’t use Automatic Offsets, Payables records the invoice liability using the liability account on the invoice, which defaults from the supplier site. When you distribute invoice distributions across multiple balancing segments, the invoice will not balance by balancing segment. 

However, General Ledger can automatically create intercompany balancing entries when you post the invoice if you have enabled the Balance Intercompany Journals option for your set of books. (Navigation: GL responsibility -Setup&gt; Financial&gt;Books&gt;Define). 


When you use Automatic Offsets and submit Approval for an invoice, Payables automatically builds the offsetting liability account for each invoice distribution on the basis of the default liability account for the invoice, which defaults from the supplier site. You can override this default during invoice entry. Payables gives you a choice of two different methods for building your offsetting accounts on the basis of this default: Account or Balancing.

As previously mentioned, if you select Balancing as your Automatic Offset Method, Payables takes the default liability account for the invoice, substitutes the balancing segment from the invoice distribution and uses that as the distribution’ s offsetting liability account.

Example: You enable Automatic Offsets using the Balancing method, and your Accounting Flexfield structure is Balancing Segment–Cost Center–Account. Your default liability account for supplier site ABC is 100–000–2000. You enter an invoice for this site and distribute it as follows:
DR 100–100–4100 $60
DR 200–201–4200 $40
Payables automatically records the following liability account offsets when you approve the invoice:
CR 100–000–2000 $60
CR 200–000–2000 $40

If you select Account as your Automatic Offset Method, Payables takes the account used for the invoice distribution and substitutes the account segment from the default liability account for the invoice, preserving all other segment values.

Example: You enable Automatic Offsets using the Account method, and your Accounting Flexfield structure is Balancing Segment–Cost Center–Account. Your default liability account for supplier site ABC is 100–000–2000. You enter an invoice for this site and distribute it as follows:
DR 100–100–4100 $60
DR 200–201–4200 $40
Payables automatically records the following liability account offsets when you approve the invoice:
CR 100–100–2000 $60
CR 200–201–2000 $40
If you adjust the liability account or an invoice distribution account for an unpaid invoice, you must resubmit Approval to pay or post the invoice. At that point Payables automatically adjusts the balancing liability distributions created by Automatic Offsets.

Note:When an invoice is paid or partially paid, you can’t adjust any accounting information on the invoice. You will be prevented from reversing or updating any of the invoice distributions for paid or partially paid invoices because Payables has already created the payment distributions based on the current invoice accounting lines.

When you enter invoices with tax, freight or miscellaneous charges, you may want to prorate these expenses in the Distributions window of the Invoice Workbench to ensure that the expenses are distributed across the other invoice distributions.

If you have a prepayment that crosses multiple balancing segments, you must split it up into the 
appropriate number of prepayments, since Payables does not support multiple distributions for prepayments. If you use Automatic Offsets, Payables automatically creates liability distributions based on your chosen Automatic Offset Method, just as it does for any other invoice.

If you use Automatic Offsets and have chosen System Account as your Discount Distribution Method in the Payables Options window, Payables prorates the entire discount amount across your invoice distributions when you pay an invoice that crosses multiple balancing segments. The balancing segment from the offsetting invoice distribution replaces the balancing segment of your system Discount Taken account when Payables builds the accounts for these entries.

 If you enable the Automatic Offsets and Pooled Account option, Payables creates a corresponding cash payment distribution for each liability distribution that you pay using a bank account with this option enabled. Payables uses the cash account you define for the bank account with the Automatic Offset Method you choose in the Payables Options window to create the cash payment distributions. If you enable Automatic Offsets, you can choose to pool any or all of your bank accounts. Multiple balancing segments share the cash in a pooled bank account; the cash in a non-–pooled bank account is associated with a single balancing segment. If you do not enable Automatic Offsets, you can only have non–pooled bank accounts.


 When you create a payment from a pooled bank account using Automatic Offsets, Payables automatically builds the cash account for each payment distribution on the basis of the bank account’ s associated cash account. Payables use the Automatic Offset Method you specified when you enabled this feature in building these cash accounts.

• If you selected Balancing as your Automatic Offset Method, Payables takes the cash account associated with your pooled bank account, substitutes the balancing segment from the invoice distribution and uses that as the distribution’ s offsetting cash account.

• If you selected Account as your Automatic Offset method, Payables takes the account used for the invoice distribution and substitutes the account segment from the cash account associated with your pooled bank account, preserving all other segment values.

Example: You enable Automatic Offsets using the Balancing method, and your Accounting Flexfield structure is Balancing Segment–Cost Center–Account. Your default liability account for supplier site ABC is 101–000–2300. The default cash account for your Division A bank account, in which you have pooled funds for investment, is 101–000–1100. You enter an invoice for supplier site ABC and distribute it as follows:
DR 101–100–4500 $60
DR 200–201–4610 $40
Payables records the following liability account offsets automatically when you approve the invoice:
CR 101–000–2300 $60
CR 200–000–2300 $40
You post the invoice and pay it out of your Division A bank account. When you create the payment, Payables automatically creates the following entries:
DR 101–000–2300 $60
DR 200–000–2300 $40
CR 101–000–1100 $60
CR 200–000–1100 $40

Example: You enable Automatic Offsets using the Account method, and your Accounting Flexfield structure is Balancing Segment–Cost Center–Account. Your default liability account for supplier site ABC is 101–000–2300. The default cash account for your Division A bank account, in which you have pooled funds for investment, is 101–000–1100. You enter an invoice for supplier site ABC and distribute it as follows:
DR 101–100–4500 $60
DR 200–201–4610 $40
Payables records the following liability account offsets automatically when you approve the invoice:
CR 101–100–2300 $60
CR 200–201–2300 $40
You post the invoice and pay it out of your Division A bank account. When you create the payment, Payables automatically creates the following entries:
DR 101–100–2300 $60
DR 200–201–2300 $40
CR 101–100–1100 $60
CR 200–201–1100 $40

Attention: When you make a payment using a non–pooled bank account, Payables generates only a single cash offset even if Automatic Offsets is enabled. For payment distributions that cross balancing segments, you can either enter balancing entries manually, or set General Ledger up to create them automatically on posting.

Automatic Offsets and Pooled Accounts are very useful options for keeping invoice and payment distributions that cross balancing segment in balance. However, enabling these option does restrict some functions in the system and there are alternatives. Review all of the costs and benefits of enabling these options before implementing. And make sure you continue to use the features correctly after implementing.


Monday, 23 February 2015

Accounts Payable Period Close Checklist

Following steps need to follow before the payable period closure


Check Details    
Product Period Close Phase Description Action Item   Pre-requisite Standard Oracle/ Custom process
AP 1: Evaluate and Prepare Apply Recommended Patches EBS: R12.1 Oracle Financials Recommended Patches     Oracle
             
AP 1: Evaluate and Prepare Apply Recommended Patches R12 Troubleshooting Period Close in Payables     Oracle
             
AP 1: Evaluate and Prepare Ensure Data Consistency R12: Experience Smoother Accounting and Period Close By Proactively Eliminating Data Integrity Issues      Oracle
             
AP 1: Evaluate and Prepare Ensure Data Consistency R12: Master GDF Diagnostic to Validate Data Related to Invoices, Payments, Accounting and Suppliers      Oracle
             
AP 1: Evaluate and Prepare Ensure Data Consistency How to Register the Master GDF Diagnostic as a Concurrent Program      Oracle
             
AP 1: Evaluate and Prepare Ensure Data Consistency What is a Generic Datafix Patch (GDF) and what GDFs are available for Payables?      Oracle
             
AP 2: Process Transactions Complete Invoices and Credits       Oracle
             
AP 2: Process Transactions Complete Invoice Import        Oracle
             
AP 2: Process Transactions Import from external system or Internet Expenses       Oracle
             
AP 2: Process Transactions Run Invoice Validation        Oracle
             
AP 2: Process Transactions Review the Invoice on Hold Report        Oracle
             
AP 2: Process Transactions Complete Payments        Oracle
             
AP 2: Process Transactions Run a Payment Process Request at the month end (Optional)       Oracle
             
AP 2: Process Transactions Confirm all Payment Instructions       Oracle
             
AP 2: Process Transactions Reconcile Payments to Bank Statement Activity for the Period         Oracle
             
AP 2: Process Transactions Run the Payments Register (Optional)       Oracle
             
AP 2: Process Transactions Submit the Update Matured Bills Payables Status Process       Oracle
             
AP 3: Create Accounting Run Create Accounting       Oracle
             
AP 3: Create Accounting Review the Transfer Journal Entries to GL       Oracle
             
AP 3: Create Accounting Run and Review the Unaccounted Transactions Report       Oracle
             
AP 3: Create Accounting Transfer All accounted Invoices and Payments to the General Ledger       Oracle
             
AP 3: Create Accounting Review the Transfer Journal Entries to GL Report generated from step 4       Oracle
             
AP 3: Create Accounting Run the Posted Invoices Register       Oracle
             
AP 3: Create Accounting Run the Posted Payments Register       Oracle
             
AP 4: Reconcile Run the Accounts Payable Trial Balance

Run the Payables Posted Invoice Register for this month
  Keep the Last Months Accounts Payable Trial Balance handy as you would need this for Trial balance. Oracle
             
AP 4: Reconcile Run the Accounts Payable Trial Balance Run the Payables Posted Payment Register for this month     Oracle
             
AP 5: Close Period Close the Current Oracle Payables Period       Oracle
             
AP 5: Close Period Submit the Unaccounted Transactions Sweep Program     Before running the sweep program, you will need to open the next accounting period Oracle
             
AP 5: Close Period Accrue Uninvoiced Receipts       Oracle
             
AP 5: Close Period Run Mass Additions Transfer to Oracle Assets       Oracle
             
AP 5: Close Period Open the Next Oracle Payables Period Open the next accounting period by using the Control Payables Periods window to set the Period Status to Open.     Oracle

Friday, 16 January 2015

Payables Period Closing Process


Accounts Payables(AP) Period Closing Process


 Before submitting the Payables Accounting Process


1.    Run the following Standard reports.

a)   Invoice Register (with Invalidated Invoices parameter as “YES”).
This report gives the details of invoices entered into the system, but no action is taken i.e. the status of the invoice is Never Validated.

b)   Invoice on hold Report.

This report gives details of all the invoices that are on hold in the system. Pass the Parameters as shown in the Screen Shot below, give the period end date in the To Entered Date field.

Resolve the Holds in the period end so that no Invoices are carried forward to the next period during the Year End Close. In the Month End Closing you can also choose to Sweep the Invoices in the next period. .

2.    Based on the information from above reports, take necessary action on invoices. Approve the Unvalidated Invoices, Account for the Unaccounted Invoices, Release Holds where ever the Invoices are placed on Hold.

3.    If payment batches are used, confirm all the Payment Batches.

4.    Submit the Payables Accounting Process Program to account for transactions. All the transactions needs to be accounted before transferred to General Ledger.

5.    Run and Review the Standard report Unaccounted Transactions Report. Review any unaccounted transactions and correct data as necessary. Then resubmit the Payables Accounting Process to account for transactions corrected.

6.    Unposted Payable Journal entries will be found in the GL and it will be posted into the General ledger.

7.    This will be queried in the Journal Entry form with source as “Payables” and posting status as “Unposted”. These Journal entries will be reviewed and Posted into the GL. If Autopost is scheduled for Payables Invoices, query for any unposted journals that are remaining after the program runs. Review and post the remaining entries.

8.    After running the “Payables Accounting Process Program” program, run ‘Create Mass Additions’ program from Account Payables responsibility. This program transfers all the account lines that are marked as ‘Track as Asset’ and have corresponding Clearing Account set up in Fixed Assets. (You cannot run this program before Payable Transfer to General Ledger program is run, as it considers all lines to be interfaced to the Fixed Assets must be transferred to the General Ledger).

9.    Reconcile with the General Ledger .The following standard reports from payables module can be used for reconciliation.

1.   Account Payables Trial Balance.
2.   Posted Invoice Register.
                          3.    Posted Payment register.

1.2  Opening/Closing of AP periods

Navigation: Accounting > Control Payables Periods.

1.    Complete the Transfer to General Ledger from the Payables for the period to be closed.
2.    Select the period to close. Select ‘Closed’ from list of values in the Period Status and save the record. I
3.    If any invoice/s, debit/credit memo, prepayment, expenses reports are not approved, these will be swept into the next or decided open/future period. If sweep is required, future period should be opened before sweeping is done.
4.    Select the Next period to open. Select ‘Open’ from list of values in the period status and save the record.
SUBLEDGER PERIOD CLOSE EXCEPTION REPORT(Before closing period we have to run this report the data will be no data)








Fusion General Ledger: Currency creation Setup/ Configuration

Definition: A system of money in general use in a particular country called currency Types of currencies Functional currency/Accounted curre...