Thursday, February 25, 2016

Oracle GL Periods



What is Period?

1. An interval of time characterized by the occurrence of a certain condition, event, or phenomenon: a period of economic prosperity.

2 Geology A unit of time, longer than an epoch and shorter than an era.

Significance Of Opening Periods in Oracle apps:

TO OPEN MONTHLY PERIODS OF DIFFERENT MODULES OR NEXT YEAR AND FOLLOW THE BELOW STEPS

1. HOW TO OPEN INVENTORY PERIODS (INV) :

Follow the below given navigation path :


INVENTORY - > ORACLE INVENTORY - > ACCOUNTING CLOSE CYCLE - > INVENTORY ACCOUNTING PERIODS

Oracle Inventory Periods


2. HOW TO OPEN PAYABLE PERIODS (AP):

Follow the below given navigation path :

PAYABLES - > ORACLE PAYABLES - > ACCOUNTING - > CONTROL PAYABLES PERIODS

Oracle AR Periods


3. HOW TO OPEN RECEIVABLE PERIODS (AR) :

Follow the below given navigation path :

RECEIVABLES - > ORACLE RECEIVABLES - > CONTROL - > ACCOUNTING - > OPEN/CLOSE PERIODS

4. HOW TO OPEN GENERAL PERIODS (GL) :

Follow the below given navigation path :

GENERAL SUPER LEDGER - > SETUP - > OPEN/CLOSE

https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTojbfaKowPZP_piIbK-awO52xVitGE_RaBifbizjqbTMEHvvk4rkKPsO7U9-JXLn9IUGjdKqSfc8Spn8UMZJjAfU-9czpd_42fa6TC4du-YwROBhnmKesMSlKCFLylAq4SQxSewHlEYkw/s320/gl_period.jpg


5 Navigate to Purchasing SuperUser->Setup->Financials->Accounting->Control Purchasing Periods , then enter the Fiscal year and click Go button.

(If it prompts for selecting Operating Unit,select it and click Go button.)

Oracle Purchasing Periods


Query to get whether accounting period or not?

SELECT   application_id
into     g_application_id
  FROM   fnd_application_tl
 WHERE   application_name = 'Receivables'


SELECT   SET_OF_BOOKS_ID INTO P_SOB_ID FROM GL_SETS_OF_BOOKS

P_ACCOUNTING_DATE IS YOUR period

FUNCTION validate_gl_accounting_date (p_accounting_date   IN DATE,
                                      p_sob_id            IN NUMBER)
   RETURN BOOLEAN
IS
   v_count   NUMBER := 0;
BEGIN
   SELECT   COUNT ( * )
     INTO   v_count
     FROM   gl_period_statuses gps
    WHERE       gps.application_id = g_gl_application_id
            AND gps.set_of_books_id = p_sob_id
            AND gps.closing_status IN ('O', 'F')
            AND p_accounting_date BETWEEN NVL (gps.start_date,
                                               p_accounting_date)
                                      AND  NVL (gps.end_date,
                                                p_accounting_date);

   IF v_count > 0
   THEN
      RETURN TRUE;
   ELSE
      RETURN FALSE;
   END IF;
END validate_gl_accounting_date;



Subledger Accounting:



Subledger Accounting:
Subledger accounting is a new product in R12 which significantly enhances the accounting support across the E-Business Suite products.  Subledger Accounting includes new ledger support and enhances the legal entity and intercompany accounting features. 
• SLA is a toolset, engine, and repository for centralized accounting processing.  This means that SLA provides the ability to set up journal creation rules and creates journal entries according to multiple different accounting methods simultaneously. However, there are many options and advanced features that facilitate the entire accounting process, including: 
• Converting foreign currency journals into the functional currency 
• Calculating exchange rate gain/loss 
• Scheduling the automatic recognition of deferred revenue and expenses across the relevant accounting periods 
Supporting automatic accrual reversals 
• Tracking versions and effective dates on rules 
• Processing a subset of transactions at a time, based on transaction type 
• Enabling straight through accounting processing generating journal entries straight from the transaction view to posting to general ledger at the single click of a button 
• Allowing testing of rule setup by what-if type of analysis with draft accounting 
• Easy to use inquiry pages and customizable reports 
• Intelligible errors reporting and tools to troubleshoot 
• Ability to copy rules in and between environments 
• Manual adjustment entries in each subledger application 
• Auto-maintenance of rules when accounts are disabled 
• Various geography-specific requirements such as journal entry sequencing, and control accounts reporting 
Benefits
In 11i, accounting information and the tie back to the underlying transaction is maintained differently for each module. Different sub ledgers/modules have their own model as to how and what they capture in terms of accounting data.  Some allow capturing more details and some link between the journals and the underlying transactions.  Some do not have the same flexibility or detail. This causes difficulty and inconsistency in reporting for auditing, reconciliation or whichever purpose across modules 
• In R12, SLA provides the ability to retain the full link between transaction and accounting data for all modules, and thus allow auditability. The accounting SLA creates is strongly tied to the underlying transactions. 
• Faster, Easier Reconciliation 
• Improved Audit- ability 
• Improved Internal Control 


TCA Changes for Suppliers



TCA Changes for Suppliers
New Tables
The following are the new tables added in Release 12 as a part of this initiative. Refer to the Oracle E-Business Suite Electronic Technical Reference Manual for the table and column descriptions..

• AP_SUPPLIERS
• AP_SUPPLIER_SITES_ALL
• AP_SUPPLIER_CONTACTS
• AP_SUPPLIER_INT_REJECTIONS

New Views

The following are the new views added in Release 12 as a part of this initiative. These are backwards compatible views that join the Suppliers table in Payables and the TCA tables, so that any teams using the old suppliers tables have no impact.

• PO_VENDORS
• PO_VENDOR_SITES_ALL
• PO_VENDOR_CONTACTS

The following tables are obsoleted:

• PO_VENDORS
• PO_VENDOR_SITES_ALL
• PO_VENDOR_CONTACTS

Payble Periods Ends Process



  •  Isolating Information 
  •  Produce The Income Statements 
  •  Key Business Decisions


 


  •  Complete Transactions 
  •  Creating Accounting 
  •  Post To GL 
  •  Reconcile Accounting 
  •  Close Period 
Period Close Sequence - R12 
Key Process

Process


01. Complete all transactions for the period being closed
02. Run the payable approval process for all invoices
03. Review and resolve amounts to the General Ledger
04. Reconcile the Payment to Bank Statement Activity for the period
05. Transfer all Approved invoices and payments to the General Ledger
06. Review the Payable to General Ledger posting Process after completion
07. Submit the unaccounted Transaction sweep program
08. Close the current payable period
09. Accrue unvoiced receipts
10. Reconcile payable activity for the period
11. Run mass additions transfer to Assets


Question What are the most common issues encountered while AP Period Closing process?
Answer Without going to technicality, on a broader level the most common issues are:
- Invoice (Distributions) not Validated
- Invoices on Hold 
- Invoices not Accounted
- Payments not Accounted
- Invoices & Payments accounting entries not transferred to GL
- Maturity Accounting not done for Future Dated payment
  • P2P Queries



    1)What is the name of the supplier who sent this invoice?
    2.  What is the amount and date of this invoice?
    3.  To what accounts was this invoice distributed?
    4.  What is the invoice due date and the amount left to be paid on this invoice?

    1) SELECT   v.vendor_name, v.vendor_id
      FROM   ap_supliers v, ap_invoices_all i
     WHERE       i.vendor_site_id = 12
             AND i.invoice_num = 'W33578'
             AND i.org_id = 204
             AND v.vendor_id = i.vendor_id;


    2)
    SELECT   invoice_amount, invoice_date, invoice_id
      FROM   ap_invoices_all
     WHERE   vendor_site_id = 12 AND invoice_num = 'W33578' AND org_id = 204;
    3)
    SELECT   c.segment1,
             c.segment2,
             c.segment3,
             c.segment4,
             c.segment5
      FROM   gl_code_combinations c, ap_invoice_distributions_all d
     WHERE       d.invoice_id = 10916
             AND c.chart_of_accounts_id = 101
             AND c.code_combination_id = d.dist_code_combination_id
    4)
    SELECT   due_date, amount_remaining
      FROM   ap_payment_schedules_all
     WHERE   invoice_id = 10916;

    Oracle P2P cycle Queries



    Joining between RFQ,Quotation and Purchase order

    SELECT   R.SEGMENT1 AS RFQ_NUM, Q.SEGMENT1 AS QUOTATION_NUM
      FROM   PO_HEADERS_ALL R, PO_HEADERS_ALL Q, PO_HEADERS_ALL P
     WHERE       R.PO_HEADER_ID = Q.FROM_HEADER_ID
             AND Q.PO_HEADER_ID = P.FROM_HEADER_ID
             AND P.SEGMENT1 = '6128'(Purchase Order number)

    Joining between PO Requisitions and Purchase Orders

    SELECT   prha.segment1 AS pr_number
      FROM   po_requisition_headers_all prha,
             po_requisition_lines_all prla,
             po_req_distributions_all prda,
             po_distributions_all pda,
             po_headers_all pha
     WHERE       prha.requisition_header_id = prla.requisition_header_id
             AND prla.requisition_line_id = prda.requisition_line_id
             AND prda.distribution_id = pda.req_distribution_id
             AND pda.po_header_id = pha.po_header_id
             AND pha.segment1 = '6129';


    Joining between AP_INVOICES AND PO_HEADERS
    select pha.segment1,apa.invoice_id
    from
    ap_invoices_all apa
    ,ap_invoice_lines_all aila
    ,po_headers_all   pha
    , ap_suppliers as1
    where apa.invoice_id=aila.invoice_id
    and aila.po_header_id=pha.po_header_id
    and apa.invoice_num='10012'
    and apa.vendor_id=as1.vendor_id
    and trunc(apa.creation_date)=trunc(sysdate)-2


    Joining between AP_INVOICES and xla tables

    SELECT DISTINCT xe.*
    FROM   ap_invoices_all ai,
           xla_events xe,
           xla.xla_transaction_entities xte
    WHERE  xte.application_id = 200
    AND    xte.application_id   = xe.application_id
    AND    ai.invoice_id        = '212200'---Invoice id is dervied from above query
    AND    xte.entity_code      = 'AP_INVOICES'
    AND    xte.source_id_int_1  = ai.invoice_id
    AND    xte.entity_id        = xe.entity_id
    ORDER BY
           xe.entity_id,
           xe.event_number;

    xla_transaction_entities (xte).entity_code =
    'TRANSACTIONS' or 'RECEIPTS' or 'ADJUSTMENTS' or 'PURCHASE_ORDER' or
    'AP_INVOICES' or 'AP_PAYMENTS' or 'MTL_ACCOUNTING_EVENTS' or
    'WIP_ACCOUNTING_EVENTS'

    xte.source_id_int_1 = 'INVOICE_ID' or 'CHECK_ID' or'TRX_NUMBER'

    Oracle PO tables



    Oracle Project Types



    Understanding Of Technical Components 



    Oracle Projects
    Oracle Projects-Project Type

    Name Enter Project Type Name, which is unique

    Class Select Indirect, Capital or Contract from the list.
    Effective From Enter start date, from which project type will be effective
    Service Type Select appropriate service type from list.
    A service type is a custom reporting attribute that you assign to each financial task to represent activities that you want to track for financial purposes. You can use service types to group tasks for custom reporting
    Work Type Select appropriate work type to represent a classification of work from list

    • Administrative Use this box to identify administrative indirect projects on which that you can create administrative assignments in Oracle Project Resource Management
    •  Unassigned Time Enable this option if you want to track available resource time in utilization reporting
    •  Inter company Billing Choose this box if you want to use this project type for inter company billing projects 
    • Organization Planning Define a unique project type to identify organization projects used in organization forecasting. Define project type for organization forecasting projects with a class of indirect and then enable the Organization Planning check box. 

    Oracle Projects



    Implementation Options
    Projects, Vision Operations->Setup->System->Implementation Options


    PA Implementation Options

       Creating a Project
    Project Creation

    Normally when we are a creating a new project,we will get following error
    Cannot copy a budget to a period which is out of the range of system defined periods (e.g. PA period or GL period)"

    Solution

    While copying the template we need to take the Project Start Date as it is in the Template Transaction Start Date then only it work
    If you got any work plan related issue
     Go to
    Structures ->Click Details
    PA Structures

     Check the Work plan Structure 

    PA Financial Options


    Partial Shared Structures: This scenario allows users to share the top level of the WBS with the financial structure while allowing Project managers to build out additional granularity for their work plan activities below the levels of the shared activities. This scenario typically works very well when the top level of the WBS can be easily shared by scheduled work and financial needs.

    Non-Shared, Mapped Structures: This model applies when you have a scenario wherein the workplan is structured very differently from how the financials of the project are managed, but it is possible to map work plan activities (at any level of the Work plan WBS) to activities in the financial WBS. This model enables the project manager (PM) and the financial analyst to have independent control over their areas of responsibility but still maintains the association between them. This allows for improved interactivity between the two in terms of generating budgets and forecasts based on work plans and also pulling work plan progress – percent complete – into the financial structure in order to process revenue and billing based on physical percent complete.
    Shared Structures: This scenario allows users to share the complete WBS with the financial structure

    Part 2
    .
    Project Structures
    There are two types of project structures, Workplan Structures and Financial Structures.
       
    WP and FP


    Workplan Structures
    A project uses a workplan structure to define, plan and track on a project. 
    Financial Structure
    Financial structures are used by persons with financial interest in projects to track billing, costs, budgets, and other financial information for projects.
    Financial Structure Task Attributes
    There are attributes related to the financial structure. They include, but are not limited to:
    ·                     Transaction Start and Finish Dates
    ·                     Work Type
    ·                     Service Type
    ·                     Customer Work Site
    ·                     ETC Source
    ·                     Chargeable
    ·                     Billable
    ·                     Receive Inter-Project Invoices
    Project Attributes
    Various attributes are stored against a project to facilitate processing and reporting. Some of these will be defaulted from the template, whilst others will be entered/updated during the course of the projects lifecycle.
    The following attributes will be captured against all projects:
    ·                     Project Number
    ·                     Project Name
    ·                     Project Owning Organization
    ·                     Project Start/End Dates
    ·                     Project Classifications
    ·                     Team/Key Members
    ·                     Customer/funder information

    Pic 1:

    Overview Of Projects


    Overview Of Projects1


    Oracle Project Costing overview
    • Setup
    • Expenditures
    • Costing
    • Auto Accounting
    • AP-PO-PA Integration
    • Project Status Inquiry
    • Capitalization 

    PA Business Process


    Create Project Templates
    A standard project you create for use in creating other projects. You set up project templates that have features common in the projects you want to create. Projects can not be created without template. Project
    Templates are created from Project Types.

    Project Template: Defines the basic characteristics of the project, and consists of:
    ·         Basic project information
    ·         Work breakdown structure (WBS)
    ·         Agreement and funding (optional)
    ·         Project and task options, including key members, classifications, Transaction controls,     any other project and task options
    ·         Budgets (optional)
    ·         Quick Entry fields which specify fields to enter for the new project when creating it from a template
    ·         Project Option controls which list the project options to display for new projects created from  a template 

    N: Setup  Projects  Templates

    PA templates

    I explained while coping the template ,have to check Transaction start date,Transaction end date (Transaction end date either needs to be or needs to be greater than system date the copied template needs to be in the same range
    PA templates Range

    PA templates Range1
    Main table involved in this
    PA_projects_all
    Pa_project_types_all
    Setups
    Oracle Projects – Setup

    PA Setup


    PA Setup1


    Organization Hierarchy
    • Project/Task owning org hierarchy
    • Exp/Event org hierarchy
    PA Hierarchy
    Project Setup

    Project Setup1