Managed and analyzed the project deliverables, escalations any deviations in timeline

P2P,O2C Cycle setup

Perform Unit/Integration Testing. Designing, developing and Analyzing the Performance of the objects Code Analysis/Review. Bug Fixing/Enhancement of objects.

Commercial Invoice Report , Print Invoice Report and customization of Discrete Job Pick List Report, etc Preparing Test cases and testing. Developed a custom program to import web invoices to Oracle AR. Developed Post Physical Inventory Counts Report in Inventory(Tektronix) Developed Physical Inventory Reservations Exception Report in Inventory(Tektronix) Developed Oracle Alerts Pick Confirmation in Order Management Module(Tektronix) Developed Pending Orders Report((Tektronix) Developed Post Physical Inventory Counts Report in Inventory(Tektronix)

Procure to pay

1)PO_REQUISITIONS_HEADERS_ALL,PO_REQUISITIONS_LINES_ALL. 2)PO_DISTRIBUTIONS_ALL,PO_HEADERS_ALL,PO_LINES_ALL,PO_DISTRIBUTIONS_ALL, PO_LINE_LOCATIONS_ALL, RCV_SHIPMENT_HEADERS,RCV_SHIPMENT_LINES,RCV_TRANSACTIONS, AP_invoice_Headers_all Ap_invoice_lines_all Ap_invoice_distribution_all Ap_payments_schedules_all Ap_checks_all IBY_payments_All Ap_invoice_payments_all/IBY_DOC_Payables Order to Cash

oe_order_headers: Containing order header information 2.oe_order_lines: Containing order line information 3.oe_price_adjustments : stores information of any discounts or charges applied to the order BOOK ORDER he Order Header Status changes to: Booked The line Status Changes to : Awaiting Shipping oe_order_holds table, the entry can be tracked using the header_id of the order. wsh_delivery_details and wsh_delivery_assignments In wsh_delivery_details table entry is made with released_status =R(Ready to Release). Source_header_id = Order Header id Source_line_id = Order line id Source_header_number = order number. ORDER SCHEDULING A new row is inserted in mtl_demand table with column demand_source_line = Order line_id Post Order reservation A new row is inserted in mtl_reservations table with column demand_source_line_id = Order line_id mtl_material_transactions mtl_txn_request_headers and mtl_txn_request_lines using Column: TRX_SOURCE_LINE_ID = Order Line_Id. Entry is made in the table mtl_txn_request_lines for the picked orders. Reference is TRX_SOURCE_LINE_ID = Order line_id mtl_onhand_quantities: transaction id of the mtl_material_transactions table which has the entry of the transfer of good into the staging sub-inventory. the transaction_id field value in wsh_delivery_details table is same as the transaction_id of mtl_material_transactions table which is created for the transfer of goods from the source subinventory to the staging sub-inventory.\\ oe_order_lines: order line status is updated wsh_delivery_details : released status chages to 'Y' if pick release is successful, to 'B' in case the line is backordered

 wsh_new_deliveries: details of the delivery created for the lines pick released wsh_delivery_assignments: association of delivery with order lines mtl_txn_request_headers: move order header information mtl_txn_request_lines: move order line details mtl_onhand_quantities: entries made for the increase of onhand in STAGE and updates for the goods moving out of the source sub-inventory mtl_material_transactions: entries tracking the movement of goods in th

System Changes After Ship Confirmation Order Header Status: Booked Order Line Status: Shipped The delivery which was associated to the order lines is closed. Inventory reduces by the amount of units which are shipped The releases_status for the lines in wsh_delivery_details changes to 'C', signifying shipment of the order line Table Updates: An entry is made into mtl_material_transactions table signifying the shipping of goods from the system; the transaction quantity is negative which means that goods are moving out of the system. The corresponding entry is deleted from mtl_ohand_quantities since the goods have been shipped. If the user queries for the item from the front end now the total available qty in the staging subinventory is reduced by the quantity shipped.

Run the workflow Background Process which picks up all the shipped order lines, changes their status to CLOSED and inserts corresponding records in the ra_iterface_lines_all table. Lines in the RA_INTERFACE_LINES_ALL can be referenced using column INTRFACE_LINE_ATTRIBUTE1 = Order Number, INTERFACE_LINE_ATTRIBUTE3 = shipment number/delivery_id INTERFACE_LINE_ATTRIBUTE6 = Order Line Id o generate invoice navigate to AR Super User Interface Auto Invoice Run the autoinvoice master program with the appropriate parameters. Once the program is completed eligible data from the ra_interface_lines_all table is fetched, validations to be performed by oracle are carried out and new records are inserted in the tables ra_customer_trx_all and ra_customer_trx_lines_all. To track the invoices created in ra_customer_trx_all Interface_header_attribute1 = order_number Interface_header_attribute6= line_number Interface_header_attribute3 = shipment number RECEIPTS

When payment is received from a customer the corresponding needs to be entered in Oracle. This is done from the Receipts screen. AR Super User Receipts Receipts Here the user needs to enter the amount received from the customer and apply it to the corresponding invoices to which he desires. The receipt amount can either be applied to a single invoice or multiple invoices. In each of the case the outstanding amount for the invoice to which the receipt is applied reduces by the amount applied. The details of the receipt applied to the invoices can be searched in the view ar_receivable_applications_v. Data in the view can be searched by referencing any of these columns: receipt_number = receipt number entered in the receipt screen trx_number = Invoice number/Transaction number generated when the invoice was created. After performing the receipts for the Invoices , the whole cycle gets completed since all the activities ie Receipt of Order --> Fulfilment of Order --> Raising Invoice to Customer --> Receiving payments for the goods shipped is completed. CHARGE ACCOUNT This is the charge account is the account that will be charged for the purchase on either the balance sheet or income statement
The charge account

is defaulted from the setups you make while defining your respective Inventory Organization ,Purchasing Options and Financial Options.

BI publisher report nitialize a variable, say V_SNO to 1 before the table <_?xdoxslt:set_variable($_XDOCTX, 'V_SNO', 1)?> 2. Display the variable defined above and increment the variable value with 1 everytime its displayed <_?xdoxslt:get_variable($_XDOCTX, 'V_SNO')?><_?xdoxslt:set_variable($_XDOCTX, 'V_SNO', xdoxslt:get_variable($_XDOCTX, 'V_SNO') +1)?>

CEMLI Stands for Configurations/Customization, Extension, Modification, Localization, and Integration. In Oracle 11i We have three tires Database tire: 8.0.6 directory contains the ORACLE_HOME for the Developer 6i products (Forms, Reports and Graphics).The product libraries in 8.0.6 Oracle_Home are used to relink Oracle Applications executables. IAS directory contains the Oracle_Home for oracle9i Application server, which includes the Oracle HTTP server. Oracle_Home on dbTier used by database software usually 8i, 9i or 10g Desktop tire: Application tire: Apache (or) web server: it listenes request from the URL and routes appropriate serv Form server: Form server: Whenever a user try to access forms,\u201cf60we bmx\u201dpicks up the file and based on this config file creates a forms session to user/client

Concurrent Processing server Administration server

It executes tasks parallely. Concurrent manager executes concurrent requests by taking resources from concurrent server

When user makes a request from browser by typing URL, then the request hit to oracle webserver and these requests are recorded in logs. Webserver checks with http request there is no cookie attached (Cookie is message given by webserver to identify client) and hence user is new it passes login page to User. User types his Username/Password in login window and click submit button Webserver checks the username/password that is needs to authenticate against database FND_USER table, so it needs some user to check clients username password in database. It usesGUEST/ORACLE user to authenticate user in database. This information is located inFND_TOP /secure/ <conte xt_nam e>.dbc Once user is authenticated it checks against FND_RESPONSIBILITY for authorization about users responsibilities and assigned responsibilities back to user. When webserver tries to connect to database for plsql or any other type of connection it asksIAS_ORACLE_HO ME/Apache/m odplsql/cfg to fulfill request and connection string information is stored inw dbsvr.app file. User submits his requests for batch processing or something else etc. These requests are fulfilled by concurrent managers When user wants to see reports of all these things request is being forwarded to

reports server. In R12

Auto-config will not write anything in APPL_TOP, COMMON_TOP area in R12. All instance specific configurations, log files are written in INST_TOP area.

The additional Instance Home makes the middle tier easier to manage and organized since the data is kept separate from the config files.

across multiple instances.

APPL_TOP and ORACLE_HOME can also be made read only file system if required. -tier, just create a new instance_top with proper config files and NFS Mount the middle tier in the
$APPL_TOP /fnd/12.0.0/secure : FND_SECURE: dbc files here
OM: Set up every aspect of Order Management that you want to use with imported orders, including customers, pricing, items, and bills. Define and enable your Order Import sources using the Order Import Sources window. Determine if you should submit the Order Import Statistics concurrent program. OE_HEADERS_IFACE_ALL: order category : RETURN or MIXED Line_type _id is optional, provided a default line_type has been defined for the specified Order Type You can import new, booked or closed orders. If an order is imported with an entry status of Booked (OE_HEADERS_IFACE_ALL.BOOKED_FLAG=Y) the result after import is that a Action Request of BOOK_ORDER is initiated. You may also pass the Action Request to BOOK_ORDER; both methods are supported Order Source Choose a specific Order Import source that you have defined in the Order Import Sources window so that only records with that source are processed, or leave this parameter blank so that all enabled sources are processed for data existing in the interface tables. Order References You can enter the System Document Reference if you want to run Order Import for a specific order. Validate Only (Yes/No) Choose whether to validate only the data in the interface tables. If Yes, the order will be validated, but not imported into the base orders tables. The default value is No.

TRANSACTIONAL_CURR_CODE = FND_CURRENCIES.CURRENCY_CODE SOLD_FROM_ORG_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID ACCOUNTING_RULE_ID = RA_RULES.RULE_ID INVOICING_RULE_ID = RA_RULES.RULE_ID SALESREP_ID = RA_SALESREPS_ALL.SALESREP_ID SALESREP = RA_SALESREPS_ALL.NAME PAYMENT_TERM_ID = RA_TERMS_B.TERM_ID CUSTOMER_PAYMENT_TERM_ID = RA_TERMS_B.TERM_ID PAYMENT_TERM = RA_TERMS_TL.NAME CUSTOMER_PAYMENT_TERM = RA_TERMS_TL.NAME AGREEMENT_ID = OE_AGREEMENTS_B.AGREEMENT_ID ORDER_SOURCE_ID = OE_ORDER_SOURCES.ORDER_SOURCE_ID HEADER_ID = OE_ORDER_HEADERS_ALL.HEADER_ID PRICE_LIST_ID = QP_LIST_HEADERS_TL.LIST_HEADER_ID

OE_LINES_IFACE_ALL Derived Values

AGREEMENT_ID = OE_AGREEMENTS_TL.AGREEMENT_ID SHIP_FROM_ORG_ID = HR_ALL_ORGANIZATION_ UNITS.ORGANIZATION_ID SOLD_FROM_ORG_ID = HR_ALL_ORGANIZATION_ UNITS.ORGANIZATION_ID ACCOUNTING_RULE_ID = RA_RULES.RULE_ID INVOICING_RULE_ID = RA_RULES.RULE_ID SALESREP_ID = RA_SALESREPS_ALL.SALESREP_ID PRICE_LIST_ID = QP_LIST_HEADERS_TL.LIST_HEADER_ID PAYMENT_TERM_ID = RA_TERMS_B.TERM_ID CUSTOMER_PAYMENT_TERM_ID = RA_TERMS_B.TERM_ID SALESREP = RA_SALESREPS_ALL.NAME CUSTOMER_PAYMENT_TERM = RA_TERMS_TL.NAME PAYMENT_TERM = RA_TERMS_TL.NAME PRICE_LIST = QP_LIST_HEADERS_TL.NAME ORDER_SOURCE_ID = OE_ORDER_SOURCES.ORDER_SOURCE_ID ORIG_SYS_DOCUMENT_REF = OE_HEADERS_IFACE_ALL.ORIG_SYS_DOCUMENT_REF LINK_TO_LINE_REF = OE_LINES_IFACE_ALL.ORIG_SYS_LINE_REF TOP_MODEL_LINE_REF = OE_LINES_IFACE_ALL.ORIG_SYS_LINE_REF

OE_PRICE_ADJS_IFACE_ALL

ORIG_SYS_DISCOUNT_REF =OE_ORDER_HEADERS_ALL.ORIG_SYS_ DOCUMENT_REF ORIG_SYS_LINE_REF = OE_ORDER_LINES_ALL.ORIG_SYS_LINE_REF ORIG_SYS_SHIPMENT_REF = OE_ORDER_LINES_ALL.ORIG_SYS_ SHIPMENT_REF LIST_HEADER_ID = QP_LIST_HEADERS_B.LIST_HEADER_ID LIST_NAME = QP_LIST_HEADERS_TL.NAME LIST_LINE_ID = QP_LIST_LINES.LIST_LINE_ID

oe_order_pub.Process_Order will be used

Integrated SOA Gateway (ISG) is an integral part of Oracle E-Business Suite R12.1. With the support of SOA and Oracle Fusion Middleware, ISG provides integration infrastructure between service interfaces and loosely coupled applications. In other words, ISG is a framework which helps in the integration of end-to-end business processes. It also handles orchestration of native

services, service security, grants roles and supports integration interface types like PL/SQL, Business Events, XML Gateway and so on. ISG allows invoking external services and also allows external clients to make use of the services provided by E-Business Suite Oracle Application Integration Architecture (AIA) delivers pre-built content, templates and methodologies for orchestrating agile user-centric business processes across enterprise applications. Oracle enables best-in-class applicationsOracle and non-Oracleto work together, leveraging industry best practices and open standards to reduce costs and increase business Oracle Application Integration Architecture (AIA) is built on Oracle Fusion Middleware's market leading SOA and BPM products. These products deliver a comprehensive SOA & BPM infrastructure for connecting heterogeneous applications and business partners, managing structured and unstructured business processes and advanced management via a unified framework for governance and monitoring. Learn more about Oracle's SOA and BPM Products and other Application Integration products. AR: Oracle receivables have a deposit transaction class and meantime have a prepayment receipt type. From business view, it looks the same, but why does Oracle designed duplicated? Whats the difference between them? I think it for a long time, and get some points to share with our friends here. Hopefully it is helpful for your implementation and support . When deposit or prepayment created in AR, the actual AR invoice for goods or services have not been generated. This is normal business process for concept of deposit/prepayment. Deposit is created in Oracle Receivables independently for a customer. It is not able to be associated or called matched directly with any prior business documents before AR invoice, like sales order in OM. But Prepayment type receipt is generated from feeder module(like OM), it is associated with sales order in sales order additional information. 2. One AR invoice can apply with only one deposit, but one ar invoice can apply multiple prepayment type receipts. It is also means that one sales order can be prepaid for multiple times before ship confirm. This is very useful for multiple times prepayment/deposit. 3. Payment term flexibility: deposit can have its own payment term, while sales order/AR invoice can have different payment term. It is very flexible for customer balance control. As prepayment is a receipt type and it is auto generated from sales order, it is must be immediate. And sales order must have a payment term which is prepayment enable. At last, I would like to say the offset account for both deposit and prepayment should be set up as an actual liability account. Some customers use on-account receipt for prepayment business before. It is not recommended, as on-account account is always set up as an actual asset account.

For AR: 1. Flexifield 2. System Options 3. Payment Terms 4. Open period 5. Auto Accounting 6. Transaction Type 7. Transaction Source