Sub Ledger Accounting

Oracle Subledger Accounting (SLA) is a rule-based accounting engine that centralizes journal entry creation across the E-Business Suite. Acting as an intermediate step between a subledger application (such as Oracle Cash Management or Oracle Accounts Payable), and the Oracle General Ledger, Oracle Subledger Accounting creates journal entries for subledger transactions and transfers them to Oracle General Ledger.

Cash Management

Oracle Cash Management helps you manage your enterprise liquidity and cash positions.

• Manage and control your cash cycle
• Upload and reconcile bank statements
• Forecast your cash needs
• Transfer funds between bank accounts
• Manage Bank, Bank Branch and Bank Account information

Per new Bank Account Model, Banks and Bank Branches are created as Trading Community Architecture (TCA) parties (as opposed to Payables owning them in previous releases). Bank Accounts reside within Cash Management application and we can define in which applications this bank account can be used.

Reconciliation Flow:

Step 1. Receive Bank Statement --&gt Manually or automatically (via Bank Statement Open Interface). Each bank statement can refer to one or more payments, receipts, open interface, misc transactions and consists of one header and multiple bank statement lines. Bank statement line status can be - Reconciled, Unreconciled, Error, External.

Step 2. Load and Verify Bank Statement --> 

Step 3. Perform Reconciliation --> 

Step 4. Review --> 

Step 5. Create JEs and Post to GL

Cash Management and External Systems:

You can include cash flows from external systems using the External Cashflow Open Interface.

Reconciliation Open Interface can find external transactions available for clearing and reconciliation. 

Open interface view --> CE_999_Interface_V

AutoInvoicing

AutoInvoice is one of several utilities provided to import transactions. Other options include:

• Oracle EDI Gateway
• Oracle Receivables API's
• XML Invoices (Part of Bill Presentment Architecture)

Despite the availability of alternatives, AutoInvoice is by far the most popular and heavily used integration point for Receivables (AR) transactions.

AutoInvoice is run using the Concurrent Request submission process. Through the Concurrent Request form, AutoInvoice can be scheduled to run on a periodic basis. 

When scheduling or submitting AutoInvoice, parameters allow you to control what data sources are used when importing records and what dates default on transactions.  Additional controls are available on the transaction source that you specify on the records being imported.

AutoInvoice Master Program (RAXMTR):  Upon submission the master program is called. This program coordinates the activities being done such as gathering statistics, marking records for processing (setting request IDs on blocks of records, parallel processing).  The master program also spawns and manages child requests for importing and purging of data.

AutoInvoice Import Program (RAXTRX): The key step in AutoInvoice is the import program.  Upon submission this request is spawned by the Master Program.  It converts the data in the interface table into invoices and also produces the execution and validation reports.

Output of the AutoInvoice Import is referred to as AutoInvoice Execution and Validation report.

AutoInvoice Purge (RAXDEL):  This is conditionally run after import (based upon your AR system options settings).

Tip:

To correct the error, navigate back to the lines form and position your cursor on the Line type field, Click on the folder menu and click on Show field. Doing this will allow you to expose more fields from the table in the form.

Tables involved:

• RA_INTERFACE_LINES_ALL
• RA_INTERFACE_DISTRIBUTIONS_ALL

Oracle Receivables (AR) - Elementary

Oracle Receivables

Trouble Shooting:

Issue: Error 'Please do not supply a GL date when the invoicing rule is Bill in Arrears'.
Sol: Update GL_DATE to NULL if Invoicing_Rule = -3 and Run AutoInvoice.

Purchasing Programs

Key Oracle Purchasing concurrent programs:

• Mass Update of Requisitions for update of Purchase Requisitions or Internal Requisitions (unless it's in Cancelled Status).

• Mass Update of Purchasing Documents program updates person information on Oracle Purchasing documents from a previous (old) person to a new person. It will NOT work on Cancelled, Finally Closed, Closed POs and Frozen POs.

          The following documents will be updated:

•   Standard Purchase Order
•   Blanket Purchase Agreements
•   Blanket Releases
•   Planned Purchase Orders
•   Planned Releases
•   Contract Agreements

• PO Output for Communication is triggered as soon as the Purchase Order is Approved and send a notification (via Oracle Workflow Mailer Engine) to the Supplier by email (if Supplier Site's Communication Method is 'Email').

Profile option PO: Secondary Email address (in R12) can be set to a secondary Email address to which the purchase order will be sent for internal reference or to forward to supplier in case it missed it earlier.

SELECT segment1,
       approved_date,
       supplier_notif_method,
       polc.displayed_field po_status,
       print_count,
       printed_date,
       from_user,
       to_user,

       status,
       mail_status,
       original_recipient
  FROM po_headers_all poh, wf_notifications wn,po_lookup_codes polc
 WHERE   polc.lookup_type(+)= 'AUTHORIZATION STATUS'
        AND poh.authorization_status = polc.lookup_code(+)
       AND wn.user_key(+) = poh.segment1
       AND wn.item_key(+) = poh.wf_item_key  
       AND supplier_notif_method = 'EMAIL'
       AND NVL (edi_processed_flag, 'N') <> 'Y'
       AND NVL(xml_flag,'N') <> 'Y'
       AND message_name(+) = 'AME_EMAIL_PO'
       and  displayed_field='Approved' ;    

If mail_status is MAIL, it means the email delivery is pending for workflow mailer to send the notification.
If mail_status is SENT, its means mailer has sent email
If mail_status is Null & status is NULL or OPEN, its means that no need to send email as notification preference of user is "Don't send email" or the Workflow mailer s not Up and Running

Serial Numbers

Tables Involved:

MTL_SERIAL_NUMBERS

• SERIAL_NUMBER
• CURRENT_STATUS

Status Codes (ID and Meaning) 
--------------------- 
1 Defined but not used 
3 Resides in stores 
4 Issued out of stores 
5 Resides in intransit 
6 Pending status 
7 Resides in receiving 
8 Resides in WIP 

• GROUP_MARK_ID, LINE_MARK_ID, LOT_LINE_MARK_ID

* When the mark ids are populated, other transactions cannot use the serials.

MTL_UNIT_TRANSACTIONS

MTL_SERIAL_NUMBERS_TEMP

MTL_SERIAL_NUMBERS_INTERFACE

Queries:

SELECT SERIAL_NUMBER_CONTROL_CODE 
   FROM apps.MTL_SYSTEM_ITEMS_B
WHERE Inventory_Item_ID = ;

Control Codes (ID and Meaning) 
--------------------- 
1 No serial number control 
2 Predefined serial numbers 
5 Dynamic entry at inventory receipt 
6 Dynamic entry at sales order issue

Oracle Fusion HCM

Oracle Fusion Human Capital Management (Oracle Fusion HCM) suite replaces the full HRMS and brings best of PeopleSoft, Oracle EBS and JD Edwards.

You may implement only one module or the entire HCM suite:

Core HCM/System of Record

• Oracle Fusion Global Human Resources
• Oracle Fusion Global Payroll
• Oracle Fusion Global Payroll Interface
• Oracle Fusion Benefits
• Oracle Fusion Workforce Lifecycle Manager

Business Intelligence

• Oracle Fusion Transactional Business Intelligence for Human Capital Management
• Oracle Fusion Workforce Predictions

Talent Management

• Oracle Fusion Performance Management
• Oracle Fusion Workforce Compensation
• Oracle Fusion Network at Work
• Oracle Fusion Goal Management
• Oracle Fusion Talent Review
• Oracle fusion Incentive Compensation