Oracle EBS Suite Concepts

Index

 E-Business Suite Architecture

 E-Business Suite Technology Stack
 EBS Login
 Oracle EBS Financials introduction
 Procure to Pay (P2P Cycle)
 Order to Cash (O2C/OTC Cycle)
Oracle E-Business Suite Architecture

 The Desktop Tier

 The Application Tier

 The Database Tier

A tier is a logical grouping of services, potentially

spread across more than one physical machine. The
three-tier architecture that comprises an Oracle E-
Business Suite installation is made up of
the database tier, which supports and manages the
Oracle database; the application tier, which
supports and manages the various Oracle E-
Business Suite components, and is sometimes
known as the middle tier; and the desktop tier,
which provides the user interface via an add-on
component to a standard web browser.
E Business Suite Login

Once successfully logged in via the E-Business Suite Home Page, you are not prompted for your user name and
password again, even if you navigate to other tools and products. Oracle E-Business Suite also retains preferences as
you navigate through the system. For example, if you registered in the Home Page that German is your preferred
language, this preference carries over whether you access Forms-based or HTML-based applications.
Defining Calendar

Validating the Calendar

Defining Currency

Accounting Structure
Sample Journal Entry
Sample Journal Entry
Procure to Pay Cycle (P2P Cycle)
Procure to Pay process which is also known as P2P cycle is followed by any
organization in any ERP system if they would like purchase any products (it could raw
materials, office supplies, infrastructure etc.). Of course when there is a purchase there
should be a payment. This entire process of purchasing a product and making payment
for that product to supplier is called procure to pay process.

Though this process is not specific to oracle ERP system, screen shots shown in the
below are from Oracle ERP.

• Create Requisition
• RFQ and Approval
• Create Purchase Order
• Create Inventory Receipt
• Enter AP Invoice
• Make Payment
• Transfer to GL
Creation of Requisition

P2P Cycle Screen Shots

O2C (Order to Cash) Cycle
 ASCP in Manufacturing

3
1 2 4 5

6 9 10

7 8
Step-1: Enter Sales Order
Sales Order Form
Step-2: Book Sales Order

The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will be ‘AWAITING_SHIPPING‘. Record(s) will be created in

the table WSH_DELIVERY_DETAILS with RELEASED_STATUS=’R’ (Ready to Release). Also Record(s) will be
inserted into

Step-3: WSH_DELIVERY_ASSIGNMENTS. At the same time DEMAND INTERFACE PROGRAM runs in the
background and inserts into MTL_DEMAND
Step -4 : Allocate Inventory
Step-5: Launch Pick Release
Key in Based on Rule and Order Number

Pick Release process in turn will kick off several other requests like Pick Slip Report, Shipping Exception
Report and Auto Pack Report
Step-6: Confirm the shipment
Running the Workflow Background Process program that will be creating the Auto invoice Master
program, to pick the lines from the Sales order.
Step-7: Generate Invoice
Step-9: Generate the Receipt for the Invoice in step-7
Applying the transaction number on the receipt apply window
Step-10: Transfer to the General Ledger
Tables Impacted in O2C Cycle
 Sales Order Creation and Booking

This is next stage, when Order is booked then the Flow status changed from Entered to Booked. At this stage, these below table get
affected.

•OE_ORDER_HEADERS_ALL (FLOW_STATUS_CODE as BOOKED, BOOKED_FLAG updated to Y)

•OE_ORDER_LINES_ALL (FLOW_STATUS_CODE as AWAITING_SHIPPING, BOOKED_FLAG updated Y)

•WSH_DELIVERY_DETAILS (DELIVERY_DETAIL_ID is assigned here, RELEASED_STATUS ‘R’ ready to release, LINE_ID

comes as SOURCE_LINE_ID)

•WSH_DELIVERY_ASSIGNMENTS (DELIVERY_ASSIGNMENT_ID is assigned for DELIVERY_DETAIL_ID present

in WSH_DELIVERY_DETAILS, DELIVERY_ID remains blank till this stage)

*In shipping transaction form order status remains "Ready to Release".

PICK Release

• WSH_NEW_DELIVERIES (one record gets inserted with SOURCE_HEADER_ID= order header

ID,STATUS_CODE=OP =>open)

• WSH_DELIVERY_ASSIGNMENTS (DELIVERY_ID gets assigned which comes from WSH_NEW_DELIVERIES)

• WSH_DELIVERY_DETAILS (RELEASED_STATUS ‘S’ ‘submitted for release’)

• MTL_TXN_REQUEST_HEADERS

• MTL_TXN_REQUEST_LINES (LINE_ID goes as TXN_SOURCE_LINE_ID)

• (move order tables. Here request is generated to move item from Source (RM or FG) sub- inventory to
staging sub-inventory)
SHIP Confirm

• OE_ORDER_LINES_ALL (FLOW_STATUS_CODE ‘shipped’)

• WSH_DELIVERY_DETAILS (RELEASED_STATUS ‘C’ ‘Shipped’, SERIAL_NUMBER if quantity is ONE)

• WSH_SERIAL_NUMBERS (records gets inserted with the DELIVERY_DETAIL_ID reference, only in case of shipped
quantity is two or more)

• MTL_TRANSACTION_INTERFACE

• MTL_MATERIAL_TRANSACTIONS (linked through Transaction source header id)

• MTL_TRANSACTION_ACCOUNTS
 Invoice Creation in AR
After shipping the order the order lines gets eligible to get transferred to RA_INTERFACE_LINES_ALL. Workflow background engine
picks those records and post it to RA_INTERFACE_LINES_ALL. This is also called Receivables interface, that mean information moved
to accounting area for invoicing details. Invoicing workflow activity transfers shipped item information to Oracle Receivables. At the
same time records also goes in the table

RA_INTERFACE_SALESCREDITS_ALL which hold details of sales credit for the particular order.

RA_INTERFACE_LINES_ALL (interface table into which the data is transferred from order management) Then Auto invoice program
imports data from this table which get affected into this stage are receivables base table. At the same time records goes in

RA_CUSTOMER_TRX_ALL (CUST_TRX_ID is primary key to link it to TRX_LINES table and TRX_NUMBER is the invoice
number)

RA_CUSTOMER_TRX_LINES_ALL (LINE_ATTRIBUTE_1 and LINE_ATTRIBUTE_6 are linked to order number and LINE_ID of
the orders)