Auto Allocation

Business Intelligence (BI)

Oracle Business Intelligence (BI) Application extracts, transfers and load Oracle Systems (Sales, Service, Marketing, OM etc) data to a pre-mapped data warehouse schema.

From that, we are able to interact with that data through dashboards, reports, ad hoc analysis, proactive detection and alerts, disconnected analysis, MS Office Plug-in or some of the other Web Services.

Key components:

1. Prebuilt data warehouse with conforming dimensions
2. Prebuilt extract, transform, and load (ETL) to extract data from Oracle and non-Oracle sources
3. Premapped metadata embedding best practices form metrics and KPIs
4. Best practice library of dashboard and reports

Deployment Options:

1. Stand alone dashboards
2. Portal integration
3. Embedded directly in Oracle EBS

Action links allow you to drill from an analytical report directly to the transnational detail.

Deal Management

Introduced in R12 and built to be part of the quote and order process, Oracle Deal Management provides essential decision support tools and scenario modeling to help sales people achieve maximum profit on every deal.

You get real-time access to pricing data for up-to-the-minute decision-making and a centralized repository of deal information for historical reference and "rearview" aggregated analysis. With automated movement of data, the process becomes more efficient and profitable—with less risk of mistakes.

With Oracle Deal Management you can:

• Enforce price policies
• Analyze deal profitability
• Review customer price history
• Review deal metrics and waterfall
• Perform "what-if" comparisons

Invoicing Rules

Invoicing and accounting rules let you create invoices that span several accounting periods. 

Accounting rules determine the accounting period or periods in which the revenue distributions for an invoice line are recorded. You can assign a different accounting rule to each invoice line.

Accounting rules of Fixed Duration span a predefined number of periods. Accouning rules of Variable Duration let you define the number of periods during invoice entry.

Invoicing rules determine the accounting period in which the receivable amount is recorded. You can only assign one invoicing rule to an invoice.

Receivables provides the following invoicing rules:

• Bill In Advance: Use this rule to recognize your receivable immediately 

• Bill In Arrears: Use this rule if you want to record the receivable at the end of the revenue recognition schedule.

With Cash Basis Accounting, you only recognize revenue when payment is received. Invoices with rules are therefore not applicable for this method of accounting.

You can assign invoicing and accounting rules to transactions that you import into Receivables using AutoInvoice and to invoices that you create manually in the Transactions window.

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

Oracle Spares Management

Oracle Spares Management is tightly integrated with Oracle Field Service and provide for efficient spares sourcing, ordering, receiving, tracking, debriefing and costing/billing.

Key features / functionality:

• Warehouse Replenishment Planning (WRP) Planner Order Release Automation
•  New HTML Parts Search and Orderning UI to search for spare parts by distance from customer site or technician location

Abbreviations used in Oracle EBS

Some common and uncommon abbreviations used in Oracle EBS:

A

• AGIS - Oracle Advanced Global Intercompany System. It replaces the Global Intercompany System (GIS) feature in 11i.
• AIA - Applications Integration Architecture
• AMB - Accounting Methods Builder
• AOL - Application Object Library
• API - Application Programming Interface

B

• BI - Business Intelligence (Oracle BI Publisher)

C

• CCID - (GL account) Code Combinations ID
• CEMLI  - Customization, Extension, Modification, Localization, and Integration
• CMA - Custom Matching Attribute
• CPUs - Critical Patch Updates
• CUP - Cumulative Upgrade Patch

D

E

• EDI - Electronic Data Interchange
• ERE - External Repair Execution
• eTRM - Oracle Electronic Technical Reference Manual

F

• FSG - Financial Statement Generator

G

• GDF - Generic DataFix Patch
• GDFs - Global Descriptive Flexfields
• GIS - Global Intercompany System. Also see AGIS
• GTP - Generate Territory Concurrent program

H

• HCM - Oracle Fusion Human Capital Management
• HRMS - Human Resource Management System

I

J

K

L

M

• MOAC - Multiple Organization Access Control
• MRC - Multiple Reporting Currencies

N

O

• OATM - Oracle Applications Tablespace Model
• OATS - Oracle Applications Testing Suite
• OCM - Oracle Configuration Manager
• OIE - Oracle Internet Expenses
• OTN - Oracle Technology Network

P

Q

• QBE - Query By Example

R

• RCD - Release Content Document
• RUPs - Release Update Packs

S

• SaaS - Software as a Service
• SLA - Subledger Accounting
• SLAs - Service Level Agreements
• SOA - Service-oriented architecture
• SOD - Segregation of Duties
• SRs - Service Requests)
• STAR - Synchronize Territory Assignment Rules (concurrent program)

T

• TCA - Trading Community Architecture
• TOI - Transfer of Information
• TUMS - The Upgrade Manual Script

U

• UPK - Oracle User Productivity Kit; tool for training end users on how to use the system.

V

W

• WRP - Warehouse Replenishment Planning

X

Y

Z

Printer issues in Oracle EBS

Printer Generic Queries:

SELECT NUMBER_OF_COPIES
     , NLS_LANGUAGE
     , NLS_TERRITORY
     , PRINTER
     , PRINT_STYLE
     , COMPLETION_TEXT
     , OUTPUT_FILE_TYPE
     , NLS_CODESET
     , OUTFILE_NODE_NAME
     , OUTFILE_NAME
  FROM APPS.FND_CONCURRENT_REQUESTS 
WHERE REQUEST_ID = ;

SELECT PRINTER_STYLE_NAME
     , SRW_DRIVER
     , WIDTH
     , LENGTH
     , ORIENTATION
  FROM apps.FND_PRINTER_STYLES
 WHERE PRINTER_STYLE_NAME =
        ( SELECT PRINT_STYLE
            FROM apps.FND_CONCURRENT_REQUESTS
           WHERE REQUEST_ID =
         );
         
SELECT PRINTER_DRIVER_NAME
     , USER_PRINTER_DRIVER_NAME
     , PRINTER_DRIVER_METHOD_CODE
     , SPOOL_FLAG
     , SRW_DRIVER
     , COMMAND_NAME
     , ARGUMENTS
     , INITIALIZATION
     , RESET
  FROM apps.FND_PRINTER_DRIVERS
 WHERE PRINTER_DRIVER_NAME = 
        ( SELECT PRINTER_DRIVER
            FROM apps.FND_PRINTER_INFORMATION
           WHERE PRINTER_STYLE =
                  ( SELECT PRINT_STYLE
                      FROM apps.FND_CONCURRENT_REQUESTS
                     WHERE REQUEST_ID=
                       AND PRINTER_TYPE = (
                             SELECT PRINTER_TYPE
                               FROM apps.FND_PRINTER
                              WHERE PRINTER_NAME = (
                                      SELECT PRINTER
                                        FROM apps.FND_CONCURRENT_REQUESTS
                                       WHERE REQUEST_ID =
                                                    )
                                           )
                  )
         );   
         
SELECT r.request_id, C.application_name, 
t.user_concurrent_program_name, a.basepath, 
e.execution_file_name, p.concurrent_program_name, 
p.execution_method_code, p.execution_options, 
p.output_file_type, p.save_output_flag, p.print_flag, 
p.minimum_width, p.minimum_length, 
p.output_print_style, p.required_style, p.printer_name, 
TO_CHAR(r.actual_completion_date, 'DD-MON-RR HH24:MI:SS'), 
r.logfile_node_name, r.logfile_name, r.outfile_name, 
r.ofile_size, r.nls_language, r.nls_territory, 
r.nls_codeset, r.is_sub_request, r.phase_code, 
r.status_code, r.completion_text, r.output_file_type, 
r.number_of_copies, r.printer, r.print_style, 
s.width, s.length, s.srw_driver, n.printer_type, 
i.printer_style, i.printer_driver, 
d.srw_driver,printer_driver_method_code, 
spool_flag, stdin_flag, d.command_name, d.arguments, 
d.initialization, b.responsibility_name, r.argument_text,u.user_name 
FROM apps.fnd_concurrent_programs_tl t, 
apps.fnd_concurrent_programs p, apps.fnd_executables e, 
apps.fnd_application a, apps.fnd_application_tl c, 
apps.fnd_concurrent_requests r, apps.fnd_printer n, 
apps.fnd_printer_information i, apps.fnd_printer_drivers d, 
apps.fnd_languages l, apps.fnd_responsibility_tl b, apps.fnd_user u, 
apps.fnd_printer_styles s 
WHERE c.application_id = t.application_id 
and c.application_id = a.application_id 
and r.concurrent_program_id = t.concurrent_program_id 
and t.concurrent_program_id = p.concurrent_program_id 
and p.executable_id = e.executable_id 
and n.printer_name = r.printer 
and (n.printer_type = i.printer_type) 
and (i.printer_driver = d.printer_driver_name) 
and d.platform_code is NULL 
and i.printer_style = r.print_style 
and r.responsibility_id = b.responsibility_id 
and b.language = l.language_code 
and r.requested_by = u.user_id 
and r.nls_language = l.nls_language 
and i.printer_style = s.printer_style_name 
and l.language_code = t.language 
and l.language_code = c.language 
and r.request_id = ; 

Oracle Service Request - An Overview

First step of CRM Service suite is creation of Service Request.

A service request (SR) can be created in multiple ways - one way from Field Service:

Field Service Dispatcher:Service Request:Service Requests:Create Service Requests

Technically, it's the Incident_Number in CS_INCIDENTS_ALL_B

In R12, a SR can be purged via 'Service Request Data Purge' concurrent program.