Oracle Apps Module Details

1) SCM Core Modules:

1)Purchasing (Procurement/procurement to pay/Requestion and purchase order creation)
2)Inventory
3)Order Management

High Level functionality in SCM:

If  LSP Sales ref will doing some order behalf of customer. At that time
customer wants 100 items, but in inventory we have only 50 items available.

So that time LSP Sales ref will  create the purchase order for the required items using
purchasing module, and full fill the inventory with required availability.

(Process flow is taken for getting items from dealers or manufacturing company etc...)
Reference Link:

2) Account Payables: 
Core functionality:
 Invoices:
Invoices is a formal document to pay to vendor. Upon shipments of goods invoices are normally
sent by supplier and the same is entered in payable module.
You can create /update invoices or invoice batches in invoice workbench. Invoice can be manually or automatically
imported from purchasing or edi interface.

Credit and Debit Memos:
Credit Memo is a negative amount invoice given by supplier to give a credit.
Debit Memo is a negative amount invoice created by you and sent to supplier.

Invoice Holds:
Holds are applied to prevent payments to suppliers.

Payment:
For each eligible invoices ot invoice lines payments are created.

IMP tables: 

ap_checks_all (checks) ap_invoice_payments_all (invoices - checks) ap_schedule_payments_all (schedule payments)  AR:  ra_customer_trx_all (transactions) ar_customers 

3) Account Receivables: 

•    Apply concepts of Order-to-Cash life cycle and Oracle Receivables Process
 •    Manage Parties and Customer Accounts
 •    Process Invoices
 •    Implement features of Bill Presentment Architecture and Credit Management
 •    Implement Customer Invoicing, Receipts and, Tax Processing
 •    Apply concepts of Period Closing Process

4) Oracle Quoting configuration:

1)Setup Manadatory profile options
2)Setup the Quote status and QUote transitions
3)Setup Quoting parameters
4)Enabling Credit check
5)Setup Defaulting rules
6)Setup the approvals
7)Assigning roles and responsibilty to user
 

5) Vendor / Supplier /Customer :

(The term Vendor tends to be used from the technical side (po_vendors, po_vendor_sites_all, ...) and Supplier tend to be used from functional side (in the PO responsibilities you will find Supply Base, Approver Supplier List, Supplier Merge), but both Vendor and Supplier refer to the same entity.)

     Now assume LSP is the owner of a fruit shop. He buys various fruits like apples, oranges, mangos and grapes etc from farmers directly and sells them to retail shop owners and also to the direct customers. The farmers are referred to as VENDORS / SUPPLIERS in Oracle Applications.  

lsp keeps track of all his vendors’ information like addresses, bank account and the amount he owes to them for the fruits that he bought etc, in a book named PAYABLES.

LSP gets an order from a retail shop owner of Fruit Mart, for a shipment of 11 bags of apples, 25 bags of oranges and 32 KGS of grapes. In Oracle Apps, bags and KGS are referred to as UOM (unit of measure), Fruit Mart is called CUSTOMER and the order is referred to as SALES ORDER.

 LSP maintains a book called ORDER MANAGEMENT where he writes down all the details of the SALES ORDERS that he gets from his customers.

 Say the fruits have been shipped to the customer Fruit Mart. LSP now sends him the details like cost of each bag/fruit, the total amount that the customer has to pay etc on a piece of paper which is called INVOICE / TRANSACTION. Once the INVOICE has been sent over, the customer then validates this against the actual quantity of fruits that he received and will process the payments accordingly. The invoice amount could be paid as a single amount or could be paid in installments.

 LSP’s customer, Fruit Mart pays him in installments (partial payments). So LSP has to make a note of the details like date received, amount received, amount remaining, amount received for what goods/shipments/invoice etc, when LSP receives the payments. This detail is called RECEIPT, which will be compared to the invoice by LSP to find how much Fruit Mart has paid to him and how much has to be paid yet. This information is maintained in a book named RECEIVABLES to keep track of all the customers, their addresses (to ship the items), what and how much he has shipped to his customers and the amount his customers owe him etc.

 LSP’s fruit business has begun to improve and has attracted more and more customers. As a result, LSP decided to buy a cold storage unit where he could stock more fruits. In Apps, this cold storage unit is known as WAREHOUSE and all the fruits are referred to as INVENTORY.

 

Due to increase in customers, LSP needs to hire more people to help him out in his business without any hiccups. These workers are called EMPLOYEES. At the end of every month, LSP pays the salary for all his employees through Checks. These checks are nothing but PAYROLL in Apps.

 At the end of every month, LSP prepares a balance sheet in a book called GENERAL LEDGER to determine how much profit/loss he got and keeps track of the money going out and going in.