Technical Oracle

66
Interface Tables Key Columns Base Tables KEY Columns PO_REQUISITION_INTERFACE_ALL PO_REQUISITION_HEADERS_ALL Refer above. PO_REQUISITION_LINES_ALL PO_REQ_DIST_INTERFACE_ALL PO_REQ_DISTRIBUTIONS_ALL PO_HEADERS_INTERFACE PO_HEADERS_ALL PO_LINES_INTERFACE PO_LINES_ALL Purchasing PO Requisition AUTHORIZATION_STATUS REQ_NUMBER_SEGMENT1 HEADER_DESCRIPTION DELIVER_TO_LOCATION_ID DESTINATION_ORGANIZATION_ID DESTINATION_TYPE_CODE INTERFACE_SOURCE_CODE PREPARER_NAME SUGGESTED_VENDOR_ID SUGGESTED_VENDOR_SITE_ID CURRENCY_CODE QUANTITY ORG_ID ITEM_DESCRIPTION UNIT_PRICE UOM_CODE LINE_TYPE NEED_BY_DATE CATEGORY_SEGMENT1 CATEGORY_SEGMENT2 REQUISITION_HEADER_ID PREPARER_ID SEGMENT1(Requisition no) AUTHORIZATION_STATUS APPROVED_DATE PO_REQUISITION_INTERFACE_ALL REQUISITION_HEADER_ID REQUISITION_LINE_ID LINE_NUM LINE_TYPE_ID ITEM_ID ITEM DESCRIPTION CATEGORY_ID NEED_BY_DATE UNIT_MEAS_LOOKUP_CODE UNIT_PRICE QUANTITY DELIVER_TO_LOCATION ACCRUAL_ACCOUNT_ID CHARGE_ACCOUNT_ID DESTINATION_ORGANIZATION_ID DISTRIBUTION_NUMBER DIST_SEQUENCE_ID INTERFACE_SOURCE_CODE QUANTITY ORG_ID VARIANCE_ACCOUNT_ID REQ_NUMBER_SEGMENT1 DISTRIBUTION_ATTRIBUTE1 DISTRIBUTION_ATTRIBUTE2 DISTRIBUTION_ID REQUISITION_LINE_ID CODE_COMBINATION_ID PROJECT_ID TASK_ID EXPENDITURE_TYPE DISTRIBUTION_NUM Purchasing Purchase Orders INTERFACE_HEADER_ID INTERFACE_SOURCE_CODE PROCESS_CODE ACTION ORG_ID DOCUMENT_TYPE_CODE DOCUMENT_NUM CURRENCY_CODE RATE_TYPE RATE_TYPE_CODE RATE_DATE RATE AGENT_NAME AGENT_ID VENDOR_NAME VENDOR_ID VENDOR_SITE_CODE VENDOR_SITE_ID VENDOR_CONTACT VENDOR_CONTACT_ID SHIP_TO_LOCATION SHIP_TO_LOCATION_ID BILL_TO_LOCATION BILL_TO_LOCATION_ID VENDOR_NUM APPROVAL_STATUS COMMENTS (po_headers_interface_s.NEXTVAL, PO_HEADER_ID SEGMENT1(PO Number) TYPE_LOOKUP_CODE AUTHORIZATION_STATUS COMMENTS APPROVAL_FLAG APPROVED_DATE PRINT_COUNT PRINT_DATE VENDOR_ID VENDOR_SITE_ID VENDOR_CONTACT_ID AGENT_ID TERM_ID FROM_HEADER_ID ( For Quotations created from RFQ) FROM_TYPE_LOOKUP_CODE CURRENCY_CODE RATE_TYPE RATE_DATE RATE BILL_TO_LOCATION_ID SHIP_TO_LOCATION_ID START_DATE_ACTIVE END_DATE_ACTIVE SHIP_VIA_LOOKUP_CODE FREIGHT_TERMS_LOOKUP_CODE REVISION_NUM INTERFACE_LINE_ID INTERFACE_HEADER_ID ACTION DOCUMENT_NUM SHIPMENT_NUM LINE_NUM LINE_TYPE LINE_TYPE_ID ITEM_ID ITEM_DESCRIPTION UOM_CODE QUANTITY UNIT_PRICE SHIP_TO_ORGANIZATION_ID SHIP_TO_LOCATION SHIP_TO_LOCATION_ID NEED_BY_DATE ORGANIZATION_ID PROMISED_DATE CATEGORY CATEGORY_ID (po_lines_interface_s.NEXTVAL, po_headers_interface_s.CURRVAL, 'ORIGINAL' ) PO_HEADER_ID PO_LINE_ID LINE_NUM LINE_TYPE_ID ITEM_ID CATEGORY_ID UNIT_PRICE QUANTITY UNIT_MEAS_LOOKUP_CODE CLOSED_CODE CLOSED_FLAG CLOSED_DATE CLOSED_REASON CLOSED_ BY CANCEL_FLAG CANCELLED_BY CANCEL_DATE CANCEL_REASON CONTRACT_NUM

Transcript of Technical Oracle

Interface Tables Key Columns Base Tables KEY Columns Concurrent Program

PO_REQUISITION_INTERFACE_ALL PO_REQUISITION_HEADERS_ALLRefer above. PO_REQUISITION_LINES_ALL

PO_REQ_DIST_INTERFACE_ALL PO_REQ_DISTRIBUTIONS_ALL

PO_HEADERS_INTERFACE PO_HEADERS_ALL

PO_LINES_INTERFACE PO_LINES_ALL

PurchasingPO Requisition

AUTHORIZATION_STATUSREQ_NUMBER_SEGMENT1HEADER_DESCRIPTIONDELIVER_TO_LOCATION_IDDESTINATION_ORGANIZATION_IDDESTINATION_TYPE_CODEINTERFACE_SOURCE_CODEPREPARER_NAMESUGGESTED_VENDOR_IDSUGGESTED_VENDOR_SITE_IDCURRENCY_CODEQUANTITYORG_IDITEM_DESCRIPTIONUNIT_PRICEUOM_CODELINE_TYPENEED_BY_DATECATEGORY_SEGMENT1CATEGORY_SEGMENT2

REQUISITION_HEADER_IDPREPARER_IDSEGMENT1(Requisition no)AUTHORIZATION_STATUSAPPROVED_DATE

Requisition Import Program'REQIMPORT'

PO_REQUISITION_INTERFACE_ALL REQUISITION_HEADER_IDREQUISITION_LINE_IDLINE_NUMLINE_TYPE_IDITEM_IDITEM DESCRIPTIONCATEGORY_IDNEED_BY_DATEUNIT_MEAS_LOOKUP_CODEUNIT_PRICEQUANTITYDELIVER_TO_LOCATION

ACCRUAL_ACCOUNT_IDCHARGE_ACCOUNT_IDDESTINATION_ORGANIZATION_IDDISTRIBUTION_NUMBERDIST_SEQUENCE_IDINTERFACE_SOURCE_CODEQUANTITYORG_IDVARIANCE_ACCOUNT_IDREQ_NUMBER_SEGMENT1DISTRIBUTION_ATTRIBUTE1DISTRIBUTION_ATTRIBUTE2

DISTRIBUTION_IDREQUISITION_LINE_IDCODE_COMBINATION_IDPROJECT_IDTASK_IDEXPENDITURE_TYPEDISTRIBUTION_NUM

PurchasingPurchase Orders

INTERFACE_HEADER_IDINTERFACE_SOURCE_CODEPROCESS_CODEACTIONORG_IDDOCUMENT_TYPE_CODEDOCUMENT_NUMCURRENCY_CODE RATE_TYPERATE_TYPE_CODERATE_DATERATEAGENT_NAMEAGENT_IDVENDOR_NAMEVENDOR_IDVENDOR_SITE_CODEVENDOR_SITE_IDVENDOR_CONTACTVENDOR_CONTACT_IDSHIP_TO_LOCATIONSHIP_TO_LOCATION_IDBILL_TO_LOCATIONBILL_TO_LOCATION_IDVENDOR_NUMAPPROVAL_STATUSCOMMENTS(po_headers_interface_s.NEXTVAL, 'DATA MIGRATION', 'PENDING', 'ORIGINAL',ORG_ID,'STANDARD',)

PO_HEADER_IDSEGMENT1(PO Number)TYPE_LOOKUP_CODEAUTHORIZATION_STATUSCOMMENTSAPPROVAL_FLAGAPPROVED_DATEPRINT_COUNTPRINT_DATEVENDOR_IDVENDOR_SITE_IDVENDOR_CONTACT_IDAGENT_IDTERM_IDFROM_HEADER_ID ( For Quotations created from RFQ)FROM_TYPE_LOOKUP_CODECURRENCY_CODERATE_TYPERATE_DATERATEBILL_TO_LOCATION_IDSHIP_TO_LOCATION_IDSTART_DATE_ACTIVEEND_DATE_ACTIVESHIP_VIA_LOOKUP_CODEFREIGHT_TERMS_LOOKUP_CODEREVISION_NUMREVISED_DATEBLANKET_TOTAL_AMOUNTCANCEL_FLAGREQUEST_IDORG_ID

INTERFACE_LINE_IDINTERFACE_HEADER_IDACTIONDOCUMENT_NUMSHIPMENT_NUMLINE_NUMLINE_TYPELINE_TYPE_IDITEM_IDITEM_DESCRIPTIONUOM_CODEQUANTITYUNIT_PRICESHIP_TO_ORGANIZATION_IDSHIP_TO_LOCATIONSHIP_TO_LOCATION_IDNEED_BY_DATEORGANIZATION_IDPROMISED_DATECATEGORYCATEGORY_ID(po_lines_interface_s.NEXTVAL, po_headers_interface_s.CURRVAL, 'ORIGINAL' )

PO_HEADER_IDPO_LINE_IDLINE_NUMLINE_TYPE_IDITEM_IDCATEGORY_IDUNIT_PRICEQUANTITYUNIT_MEAS_LOOKUP_CODECLOSED_CODECLOSED_FLAGCLOSED_DATECLOSED_REASONCLOSED_ BYCANCEL_FLAGCANCELLED_BYCANCEL_DATECANCEL_REASONCONTRACT_NUM

PO_LINE_LOCATIONS_ALL

PO_DISTRIBUTIONS_INTERFACE PO_DISTRIBUTIONS_ALL

PO_ACTION_HISTORY

PO Receipt Interface RCV_HEADERS_INTERFACE RCV_SHIPMENT_HEADERS Receiving Open Interface

RCV_TRANSACTIONS_INTERFACE RCV_SHIPMENT_LINES

RCV_TRANSACTIONS

Item Interface MTL_SYSTEM_ITEMS_INTERFACE MTL_SYSTEM_ITEMS_B Item Import

PO_HEADER_IDPO_LINE_IDLINE_LOCATION_IDQUANTITYQUANTITY_RECEIVEDQUANTITY ACCEPTEDQUANTITY_REJECTEDQUANTITY_BILLEDQUANTITY_CANCELLEDPO_RELEASE_IDSHIP_TO_LOCATION_IDSHIP_VIA_LOOKUP_CODENEED_BY_DATEPROMISED_DATEENCUMBERED_FLAGENCUMBERED_DATESHIP_TO_ORGANIZATION_IDSHIPMENT_NUMORG_IDMATCH_OPTION

INTERFACE_DISTRIBUTION_IDINTERFACE_HEADER_IDINTERFACE_DISTRIBUTION_IDDISTRIBUTION_NUMQUANTITY_ORDEREDDESTINATION_TYPEDELIVER_TO_LOCATIONDELIVER_TO_LOCATION_IDDELIVER_TO_PERSON_FULL_NAMEDELIVER_TO_PERSON_IDDESTINATION_ORGANIZATIONDESTINATION_ORGANIZATION_IDCHARGE_ACCOUNT_IDORG_ID

PO_HEADER_IDPO_LINE_IDLINE_LOCATION_IDPO_DISTRIBUTION_IDREQ_DISTRIBUTION_ID

OBJECT_IDOBJECT_TYPE_CODEOBJECT_SUB_TYPE_CODESEQUENCE_NUMACTION_CODEACTION_DATEEMPLOYEE_ID

HEADER_INTERFACE_IDGROUP_IDPROCESSING_STATUS_CODE ('PENDING')RECEIPT_SOURCE_CODETRANSACTION_TYPE ('NEW' or 'CANCEL')VENDOR_NAMEVALIDATION_FLAGAUTO_TRANSACT_CODE(’RECEIVE’) or direct receipt (’DELIVER’)SHIPMENT_NUM

SHIPMENT_HEADER_ID RECEIPT_SOURCE_CODE VENDOR_ID VENDOR_SITE_ID ORGANIZATION_ID SHIPMENT_NUM RECEIPT_NUM SHIP_TO_LOCATION_ID BILL_OF_LADING PACKING_SLIP SHIPPED_DATE FREIGHT_CARRIER_CODE EXPECTED_RECEIPT_DATE EMPLOYEE_ID NUM_OF_CONTAINERS WAYBILL_AIRBILL_NUM COMMENTS

INTERFACE_TRANSACTION_IDGROUP_IDTRANSACTION_TYPE (SHIP OR RECEIVE)TRANSACTION_DATEPROCESSING_STATUS_CODEPROCESSING_MODE_CODE(Batch or Single)TRANSACTION_STATUS_CODE(ERROR or COMPLETED)QUANTITY

SHIPMENT_LINE_ID SHIPMENT_HEADER_ID LINE_NUM CATEGORY_ID QUANTITY_SHIPPED QUANTITY_RECEIVED UNIT_OF_MEASURE ITEM_DESCRIPTION ITEM_ID PO_HEADER_ID PO_RELEASE_ID PO_LINE_ID PO_LINE_LOCATION_ID PO_DISTRIBUTION_ID REQUISITION_LINE_ID REQ_DISTRIBUTION_ID

TRANSACTION_ID TRANSACTION_TYPE TRANSACTION_DATE QUANTITY UNIT_OF_MEASURE SHIPMENT_HEADER_ID SHIPMENT_LINE_ID USER_ENTERED_FLAG INTERFACE_SOURCE_CODE INTERFACE_SOURCE_LINE_ID INV_TRANSACTION_ID SOURCE_DOCUMENT_CODE DESTINATION_TYPE_CODE PRIMARY_QUANTITY PRIMARY_UNIT_OF_MEASURE UOM_CODE EMPLOYEE_ID PARENT_TRANSACTION_ID PO_HEADER_ID PO_RELEASE_ID PO_LINE_ID PO_LINE_LOCATION_ID PO_DISTRIBUTION_ID PO_REVISION_NUM REQUISITION_LINE_ID

PROCESS_FLAGTRANSACTION_TYPE ('CREATE' or 'UPDATE') SET_PROCESS_ID (to be mentioned at the time of request submission)ORGANIZATION_ID/ORGANIZATION_CODE DESCRIPTIONITEM_NUMBER and/or SEGMENT(n) LIST_PRICE_PER_UNIT TEMPLATE_ID

MTL_ITEM_CATEGORIES_INTERFACE MTL_ITEM_CATEGORIESMTL_INTERFACE_ERRORS

Inventory On-Hand Quantities Interfa

Supplier Creation

AP_SUPPLIERS Supplier Open Interface Import (APXSUIMP)

AP_SUPPLIER_SITES_INT AP_SUPPLIER_SITES_ALL Supplier Sites Open Interface Import (APXSSIMP)AP_SUP_SITE_CONTACT_INT AP_SUPPLIER_CONTACTS_ALL Supplier Site Contacts Open Interface Import (APXSCIMP)AP_SUPPLIER_INT_REJECTIONS Rejections

Payables Open Interface Import

AP_INVOICES_INTERFACE

AP_INVOICE_LINES_INTERFACE

AP_PAYMENT_SCHEDULES_ALL

TRANSACTION_TYPE ('CREATE')SET_PROCESS_ID ORGANIZATION_ID/ORGANIZATION_CODE ITEM_NUMBER/INVENTORY_ITEM_ID or bothCATEGORY_SET_ID or CATEGORY_SET_NAME or bothCATEGORY_ID or CATEGORY_NAME or both

MTL_TRANSACTIONS_INTERFACE

TRANSACTION_SOURCE_NAMETRANSACTION_HEADER_ID TRANSACTION_INTERFACE_ID TRANSACTION_DATETRANSACTION_TYPE_IDPROCESS_FLAG (1 = Yet to be processed, 2 = Processed, 3= Error)TRANSACTION_MODE (2 = Concurrent – to launch a dedicated transaction workerto explicitly process a set of transactions.3 = Background – will be picked up by transaction managerpolling process and assigned to transaction worker. These will not be picked up until thetransaction manager is running)SOURCE_CODESOURCE_HEADER_IDSOURCE_LINE_IDTRANSACTION_SOURCE_ID

MTL_ON_HAND_QUANTITIES Submit Transaction Manager through Interface Manager or explicitly call the API – INV_TXN_MANAGER_PUB.PROCESS_TRANSACTIONS

MTL_TRANSACTION_LOTS_INTERFACE (If the item is Lot controlled) MTL_LOT_NUMBERS

MTL_SERIAL_NUMBERS_INTERFACE (If the item is Serial controlled) MTL_SERIAL_NUMBERS

AP_SUPPLIERS_INT VENDOR_INTERFACE_IDVENDOR_NAMESEGMENT1VENDOR_TYPE_LOOKUP_CODESTART_DATE_ACTIVEEND_DATE_ACTIVEPARTY_ID

VENDOR_IDVENDOR_NAMESEGMENT1VENDOR_TYPE_LOOKUP_CODEPARTY_IDSTART_DATE_ACTIVEEND_DATE_ACTIVE

INVOICE_IDINVOICE_NUMINVOICE_TYPE_LOOKUP_CODEINVOICE_DATEINVOICE_AMOUNTINVOICE_CURRENCY_CODEPO_NUMBERVENDOR_IDVENDOR_NUMVENDOR_SITE_IDTERMS_ID/TERMS_NAMETERMS_DATEDESCRIPTIONGL_DATEVOUCHER_NUMBERORG_IDPAYMENT_METHOD_LOOKUP_CODEPAY_GROUP_LOOKUP_CODESTATUSSOURCE

AP_INVOICES_ALL

INVOICE_IDINVOICE_NUMINVOICE_TYPE_LOOKUP_CODEINVOICE_DATEBASE_AMOUNTINVOICE_CURRENCY_CODEPAYMENT_CURRENCY_CODEAMOUNT_PAIDPO_NUMBERVENDOR_IDVENDOR_NUMVENDOR_SITE_IDTERMS_ID/TERMS_NAMETERMS_DATEDESCRIPTIONGL_DATEVOUCHER_NUMBERORG_IDPAYMENT_METHOD_LOOKUP_CODEPAY_GROUP_LOOKUP_CODEAPPROVED_AMOUNTAPPROVAL_STATUSSOURCE

INVOICE_IDINVOICE_LINE_IDLINE_NUMBERLINE_TYPE_LOOKUP_CODEDATEDESCRIPTIONACCOUNTING_DATEPO_HEADER_IDPO_NUMBERPO_LINE_IDPO_LINE_NUMPO_LINE_LOCATION_IDPO_SHIPMENT_NUMPO_DISTRIBUTION_IDPO_DISTRIBUTION_NUMPO_RELEASE_IDRELEASE_NUMPO_UNIT_OF_MEASUREINVENTORY_ITEM_IDITEM_DESCRIPTIONQUANTITY_INVOICEDUNIT_PRICEDISTRIBUTION_SET_IDDISTRIBUTION_SET_NAMEDIST_CODE_CONCATENATEDDIST_CODE_COMBINATION_IDPROJECT_IDTASK_IDEXPENDITURE_TYPEEXPENDITURE_ORGANIZATION_IDORG_IDRECEIPT_NUMBERRECEIPT_LINE_NUMBERMATCH_OPTION

AP_INVOICE_LINES_ALL INVOICE_IDINVOICE_LINE_IDLINE_NUMBERLINE_TYPE_LOOKUP_CODEDATEDESCRIPTIONACCOUNTING_DATEPO_HEADER_IDPO_NUMBERPO_LINE_IDPO_LINE_NUMPO_LINE_LOCATION_IDPO_SHIPMENT_NUMPO_DISTRIBUTION_IDPO_DISTRIBUTION_NUMPO_RELEASE_IDRELEASE_NUMPO_UNIT_OF_MEASUREINVENTORY_ITEM_IDITEM_DESCRIPTIONQUANTITY_INVOICEDUNIT_PRICEDISTRIBUTION_SET_IDDISTRIBUTION_SET_NAMEDIST_CODE_CONCATENATEDDIST_CODE_COMBINATION_IDPROJECT_IDTASK_IDEXPENDITURE_TYPEEXPENDITURE_ORGANIZATION_IDORG_IDRECEIPT_NUMBERRECEIPT_LINE_NUMBERMATCH_OPTION

AP_INVOICE_DISTRIBUTIONS_ALL

AP_INTERFACE_REJECTIONSAP_INTERFACE_CONTROLS

Additional Info

Oracle Purchasing generates SEGMENT1 using the PO_UNIQUE_IDENTIFIER_CONTROL table if you choose to let Oracle Purchasing generate requisition numbers for you.

LINE_LOCATION_ID identifies the purchase order shipment line on which you placed the requisition. LINE_LOCATION_ID is null if you have not placed the requisition line on a purchase order.

BLANKET_PO_HEADER_ID and BLANKET_PO_LINE_NUM store the suggested blanket purchase agreement or catalog quotation line information for the requisition line.

PARENT_REQ_LINE_ID contains the REQUISITION_LINE_ID from the original requisition line if you exploded or multi-sourced this requisition line.

Stores information about the accounting distributions associated with each requisition line

Primary Key: (SEGMENT1 & TYPE_LOOKUP_CODE ) ORPO_HEADER_IDSEGMENT1 - Derives PO Number from PO_UNIQUE_IDENTIFIER_CONT_ALL table.There are six types of documents that use PO_HEADERS_ALL:

• RFQs

• Quotations

• Standard purchase orders

• Planned purchase orders

• Blanket purchase orders

• Contracts

Authorization Status: APPROVED,CANCELLED,IN PROCESS, INCOMPLETE, PRE-APPROVED,REJECTED,REQUIRES REAPPROVAL, RETURNED.

Closed code : APPROVED,CANCELLED,CLOSED,CLOSED FOR INVOICE,CLOSED FOR RECEIVING,FINALLY CLOSED,IN PROCESS, INCOMPLETE,OPEN,PRE-APPROVED,REJECTED,REQUIRES REAPPROVAL,RETURNED.CONTRACT_NUM: To reference a contract purchase order from a standard purchase order line.

Indicator of whether the invoice for the shipment should be matched to the purchase order or the receipt.

REQ_DISTRIBUTION_ID corresponds to the ID of the requisition distribution you copy on the purchase order.

If you do not autocreate the purchase order from onlinerequisitions, REQ_LINE_REFERENCE_NUM andREQ_HEADER_REFERENCE_NUM contain the requisitionnumber and requisition line number of the corresponding paper requisition. These two columns are not foreign keys to anothertable.

http://www.confluentminds.com/Trainings/SCM/Topic2.2_Ch2_Part4.html

Receiving Transaction Processor performs these steps :Populates the RCV_SHIPMENT_HEADERS & RCV_SHIPMENT_LINES. Populates the RCV_TRANSACTIONS table for each row in the RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES table if the columnAUTO_TRANSACT_CODE in the RCV_TRANSACTIONS_INTERFACE table contains a value of ’RECEIVE’ or ’DELIVER’. Updates supply for accepted line items in the tables MTL_SUPPLY and RCV_SUPPLY.

http://erpschools.com/articles/interfaces-and-conversions

http://apps2fusion.com/apps-training/apps-functional-documents/57-r12-features/209-suppliers-in-tca-a-dive-into-vendor-tables-in-r12

IBY_EXT_BANKACCT_PUB.create_ext_bank_acct

AP_INVOICES_INTERFACE_S.NEXTVAL Mandatory Parameters:1. Source: It can be any of the below listØ Invoice Gateway - Invoice records you entered in the Invoice Gateway windowØ E-Commerce Gateway- Supplier invoices transferred through EDIØ Credit Card- Procurement cards transactions from the credit card issuerØ Oracle Property Manager- Lease invoices from Oracle Property Manager.Ø Oracle Assets- Lease payments from Oracle Assets.User-defined- For invoice loaded from legacy Systems2. Invoice Batch Name Use Batch Control Payables Profile option need to be enabled to use this parameter Payables groups the invoices created from the invoice records you import and creates an invoice batch with the batch name you enterWhile Re-importing the error invoices make sure the batch name remains the sameOptional Parameters:3. Operating Unit: Filtering predicate when null import program process invoice from all operating units.4. Hold Name: When this parameter is provided with the hold name, then the import program creates the invoices and blocks them with mentioned hold.5. Hold Reason: Corresponds to Hold Name6. GL Date: This value is used as a GL date for the invoices whose GL_DATE columns in interface tables are not populated.7. Purge. Enter Yes if you want Payables to delete from the Payables Open Interface tables all successfully imported invoice records that match the Source and Group ID of this import8. Summarize Report: Provides a Summarize report when ‘YES’

AP_INVOICE_LINES_INTERFACE_S.NEXTVAL

Sample procedure to load supplier bank acct.txt

Interface Tables Key Columns Base Tables KEY ColumnsRA_INTERFACE_LINES_ALL

cust_trx_line_gl_dist_idRA_INTERFACE_SALESCREDITS RA_CUST_TRX_LINE_SALESREPS RA_INTERFACE_DISTRIBUTIONS_ALL

RA_INTERFACE_ERRORS

AR_CASH_RECEIPTSAR_CASH_RECEIPT_HISTORYAR_PAYMENT_SCHEDULESAR_RECEIVABLE_APPLICATIONSAR_MISC_CASH_DISTRIBUTIONSAR_ADJUSTMENTSAR_DISTRIBUTIONS_ALL

Organization Structure in R12

FA Tables

AR Receipts Interface AR_RECEIPT_API_PUB.CREATE_CASH

General Ledger Interface GL_INTERFACE

SLA Tables

Accrual Accounting

ReceivablesAuto Invoice Master Program

interface_line_id,interface_line_context,interface_line_attribute1,set_of_books_id,batch_source_name,org_id,trx_number,-- cust_trx_type_name,cust_trx_type_id,trx_date,gl_date, currency_code, conversion_rate,conversion_date,term_id, orig_system_bill_customer_id, orig_system_bill_address_id,orig_system_ship_customer_id, orig_system_ship_address_id, line_type,line_number, description, quantity, amount,conversion_type, primary_salesrep_id,memo_line_id, unit_selling_price,comments,creation_date, created_by,last_update_date, last_updated_by, last_update_loginbatach_source_namedocument_numberORIG_SYSTEM_ BATCH_NAME

RA_CUSTOMER_TRX_ALLRA_CUSTOMER_TRX_LINES_ALL RA_CUST_TRX_LINE_GL_DIST_ALL AR_PAYMENT_SCHEDULES_ALLAR_RECEIVABLE_APPLICATIONSRA_BATCHESAR_ADJUSTMENTSRA_CUST_TRX_LINE_SALESREPS

interface_distribution_id,interface_line_id,account_class('REV','TAX') amount,interface_line_context,interface_line_attribute1, code_combination_id,org_id,percent,creation_date,created_by,last_update_date,last_updated_by,last_update_login

ReceivablesReceipts

Business Group Legal Entity associated with LedgersOperating Unit associated with LedgersInventory Organization can serve multiple Operating units under different ledgers.As such, each inventory organization is attached to a legal entity and a ledger.

FA_BOOKSFA_ADDITIONS_BFA_ASSET_HISTORYFA_ADJUSTMENTSFA_BOOK_CONTROLSFA_MASS_ADDITIONSFA_MASSADD_DISTRIBUTIONS FA_LOOKUPS_BFA_MASS_RETIREMENTSFA_MASS_TRANSFERSFA_RETIREMENTSFA_TRANSACTION_INTERFACEFA_TRANSACTION_HEADERSFA_DISTRIBUTION_HISTORYFA_DEPRN_SUMMARYFA_DEPRN_DETAILFA_TRANSFER_DETAILSFA_CATEGORIES_B

http://www.oracleappshub.com/accounts-receivable/understanding-ar-receipt-point-of-sale-apis-intergration-with-oracle-application/

GL_JE_HEADERSGL_JE_LINESGL_JE_BATCHESGL_BALANCES

XLA_EVENTS XLA_AE_HEADERS XLA_AE_LINES XLA_TRANSACTION_ENTITIES_UPG XLA_DISTRIBUTION_LINKS

XLA_EVENTS.ENTITY_CODE = 'AP_INVOICES'XLA_EVENTS.EVENT_TYPE_CODE =AP_ACCOUNTING_EVENTS_ALL.event_type_code

XLA_TRANSACTION_ENTITIESENTITY_CODE = 'AP_INVOICES' OR 'AP_PAYMENTS' - For AP_INVOICES , data from AP_INVOICES_ALL is used if distributions with accounting_event_id exists - For AP_PAYMENTS, data from AP_CHECKS_ALL is used XLA_EVENTS.EVENT_STATUS_CODE = AP_ACCOUNTING_EVENTS_ALL.event_status_code CREATED -> N INCOMPLETE -> I Any other value -> P

What are the important tables in SLA Accounting?The XLA_EVENTS table stores records for accounting events generated by subledger applications. Each product team populates this table by calling Subledger Accounting API and the respective product team will decide when this table is to be populated during the transaction life cycle.

The XLA_AE_HEADERS table stores subledger journal entries. There is a one-to-many relationship between accounting events and journal entry headers.

The XLA_DISTRIBUTION_LINKS table stores detailed distributions for journal entries. This table stores the data at most granular level and represents data contained in respective subledger product’s distribution tables. The detailed distributions stored in this table are merged into accounting lines and stored in XLA_AE_LINES table. Subledger Accounting uses this table for processing reversals and business flows.

The XLA_AE_LINES table stores the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger journal entry lines. This table will store at least one row for debit and one row for credit for each accounting entry created. If multiple debit or credit journal entry lines exists for any specific event type and if the journal line type allows merge matching lines then these lines will be merged into single line. The unmerged granular level of detail for each accounting line will be available in XLA_DISTRIBUTION_LINKS table.

http://accountingexplained.com/financial/principles/accrual

http://www.wikihow.com/Reconcile-a-General-Ledger-Account

What is sub ledger? How is it linked to GL?

AP HOLDSAccounting Transactions

https://forums.oracle.com/forums/thread.jspa?threadID=2268876&tstart=0http://oracleerp.org/discussion/topic/show/253485http://www.shareoracleapps.com/2011/01/how-payable-invoices-data-is-stored-in.html

Accounting Entries

How to Reconcile a General Ledger Account

A sub ledger is used for tracking individual items and transactions separate to the General Ledger (GL). Sub-ledgers may exist for, but are not limited to Accounts Receivable (AR), Accounts Payable (AP), Inventory and Fixed Assets etc. Without a sub-ledger individual customers or inventory items would require their own GL code making the GL unnecessarily large. Sub-ledgers also allow for more specific detail to be included in transaction details. Each sub-ledger links to the GL by way of a control account (e.g. Debtors control the AR sub-ledger etc.). The total of the sub-ledger account should equal the balabce in the control account at all times. Individual transactions should be posted via sub-ledger not directly to the control account. Reconciliations should be performed between the sub-ledger and control account on at least a monthly basis to ensure this is the case.

GL a/c is a consolidated a/c for sub-ledger. It is not possible to show the line item wise details of all the Customers, Vendors & Assets in the B/S. So whatever the postings made in these sub-ledgers will get posted into GL a/c. The GL(Recon a/c)will be linked in the Customer, Vendor & Asset Master data.

Maintaining Data Integrity between Sub Ledgers and General Ledger

Interesting Findings & Knowledge SharingScribblings of a Microsoft Dynamics GP MVPHome About Poll Archive Archives Events Event Locations Event Categories My Bookings Maintaining Data Integrity between Sub Ledgers and General LedgerHi all

I have been involved in the process of reconciliation between the sub ledgers and the general ledger at various clients and there has been various scenarios in which there has been a break between the sub ledgers and the general ledger balances. A few key scenarios are quoted below

A transaction posted in the sub ledgers do not have a corresponding transaction in the general ledger. A transaction posted in the sub ledger is backed out/corrected at the general ledger level. Manual posting to the sub ledger control accounts in the General Ledger. In this article, I am going to provide some tips to avoid any of the above situations and ensure that there is data integrity between the sub ledgers and the general ledger. This will ensure that the periodic audits done in the system proceeds in a smooth manner to a great extent

http://simplestudies.com/general-ledger-to-subledger-reconciliation.html

Accounting periods are used in Oracle Inventory to group material and work in process (WIP) transactions for accounting purposes.

What is the relevance of these periods? Transactions in Oracle Applications are date-stamped. When we execute a transaction, the transaction date must fall in an open period. If that period is not open then Oracle Inventory prevents us from proceeding any further by displaying the following message.

If we have a transaction in Inventory or WIP, or in any other module that falls in an open period then the same period must be open in Oracle General Ledger (GL). This ensures that when closing the period the transaction will be posted correctly.

http://space.itpub.net/9182041/viewspace-705051

Cycle: Procure to Pay

1. Enter PO: Accounting Impact Nil2. Enter a receipt:-------------Debit --------Inventory Receiving Account-------------Credit-------- AP Accrual Account3. Inspect and Accept: Accounting Impact Nil4. Delivery to stock:-------------Debit ---------Inventory Account-------------Credit --------Inventory receiving account (ISP)5. Enter PO Matched Invoice-------------Debit ---------AP Accrual Account-------------Credit --------Supplier Liability Control Account6. Enter payments against the invoice-------------Debit ---------Supplier Liability Account-------------Credit --------Cash / Bank Account

Document

Concurrent Program Additional InfoAutoInvoice Master Program / Auto Invoice Import Program

AutoInvoice Purge Program

To submit more than one instance of the AutoInvoice Import program, use the AutoInvoice Master program. Submitting multiple instances lets you import your transactions into Receivables more quickly.

Enter a Transaction Source and Default Date for this submission. If you are submitting the AutoInvoice Master program, enter a Number of Instances. API:

ar_invoice_api_pub.create_invoicear_invoice_api_pub.create_single_invoice

http://www.oracleappshub.com/accounts-receivable/understanding-ar-receipt-point-of-sale-apis-intergration-with-oracle-application/

E:\VPN\Study\AR Invoice Interface V

Base Tables KEY Columns Interface Tables Key Columns Concurrent Program Additional Info

Item Creation MTL_SYSTEM_ITEMS_B MTL_SYSTEM_ITEMS_INTERFACE Import ItemsItem Categories MTL_ITEMS_CATEGORIES MTL_ITEM_CATEGORY_INTERFACE Item Assignment to Category

CategoriesOn Hand Quantity

INVENTORY_ITEM_IDORGANIZATION_IDDESCRIPTIONSTART_DATE_ACTIVEEND_DATE_ACTIVESEGMENT1(ITEM_CODE)LIST_PRICE_PER_UNITMARKET_PRICEPRIMARY_UOM_CODEPRIMARY_UNIT_OF_MEASURESECONDARY_UOM_CODEMAX_MINMAX_QUANTITYMIN_MINMAX_QUANTITY

INVENTORY_ITEM_IDORGANIZATION_IDSTART_DATE_ACTIVEEND_DATE_ACTIVEDESCRIPTIONMARKET_PRICELIST_PRICE_PER_UNITPRIMARY_UOM_CODEPRIMARY_UNIT_OF_MEASURESECONDARY_UOM_CODEMAX_MINMAX_QUANTITYMIN_MINMAX_QUANTITY

MTL_CATEGORIES_BMTL_CATEGORY_SETS_BMTL_ITEM_SUB_INVENTORIESMTL_ONHAND_QUANTITIES (View on mtl_onhand_quantities)

MTL_ONHAND_QUANTITIES has two columns, CREATE_TRANSACTION_IDand UPDATE_TRANSACTION_IDs to join toMTL_MATERIAL_TRANSACTIONS.TRANSACTION_ID the transactions thatcreated the row and the transaction that last updated a row

select sum(transaction_quantity)from mtl_onhand_quantitieswhere inventory_item_id=1234and organization_id=201

MTL_ONHAND_QUANTITIES is maintained as a stack of receipt records,which are consumed by issue transactions in FIFO order. The quantityon hand of an item at any particular control level and location can befound by summing TRANSACTION_QUANTITY for all records that match thecriteria

JDR Tables

JDR_ATTRIBUTES, JDR_ATTRIBUTES_TRANS, JDR_COMPONENTS & JDR_PATHS.

OAPageContextOAWebBeanhttp://oracle.anilpassi.com/mds-in-oa-framework-what-exactly-it-is-2.html

Tables DescriptionWF_NOTIFICATIONS

WF_ITEM_ATTRIBUTES

WF_ITEMS

WF_ACTIVITIES

WF_MESSAGESWF_MESSAGE_ATTRIBUTESWF_ROLES Contains information on the roles of which users can be membersWF_USERS

WF_USER_ROLES Contains information on the association of users with roles

API

Standard Workflows

PO Create Documents

PO Account Generator workflow

PO Requisition Account Generator

WF_NOTIFICATIONS holds the runtime information about a specificinstance of a sent message. A new row is created in the table each time amessage is sent.

The WF_ITEM_ATTRIBUTES table stores definitions of attributesassociated with a process. Each row includes the sequence in which theattribute is used as well as the format of the attribute data.

WF_ITEMS is the runtime table for workflow processes. Each rowdefines one work item within the system.

WF_ACTIVITIES table stores the definition of an activity. Activities canbe processes, notifications, functions or folders. A process activity is amodelled workflow process, which can be included as an activity inother processes to represent a sub–process. A notification activity sendsa message to a performer. A functions activity performs an automatedfunction that is written as a PL/SQL stored procedure. A folder activityis not part of a process, it provides a means of grouping activities

Contains information on user names, display names, notification preferences and e-mail addresses

WF_ENGINE WF_NOTIFICATION WF_DIRECTORYWF_LOADWF_EVENTWF_COREWF_PURGEWF_MONITORWF_QUEUEWF_STANDARDFND_WF_STANDARD.

CreateProcess

StartProcess

CompleteActivity

CompleteActivityInternalName

AssignActivity

HandleError

SuspendProcess

ResumeProcess

AbortProcess

SetItemAttrDocument - PL/SQL and Java

getItemAttributes - Java

Based on the result of a previous activity, the engine attempts to execute the next activity directly. An activity may have the following status:

Active - activity is running.

Complete - activity completed normally.

Waiting - activity is waiting to run.

Notified - notification activity is delivered and open.

Deferred - activity is deferred.

Error - activity completed with error.

Suspended - activity is suspended.

Is Automatic Creation Allowed? - The default value of this attribute is set to 'Y,' meaning that automatic document creation is allowed for approved requisition lines. You can prevent automatic document creation by setting the default value of this attribute in the Workflow Builder to 'N' for No.Should Workflow Create The Release? - The default value of this attribute is set to 'Y,' meaning that the workflow tries to create the release; if it cannot, or if the value of this attribute is set to 'N' for No, then the workflow will not create the release; you must use the AutoCreate Documents window to create the release.Is Automatic Approval Allowed? - The default value of this attribute is set to 'N' for No, meaning that documents are not automatically approved after they are created. If you set it to 'Y' for Yes, then the PO Approval workflow is launched to automatically route the documents for approval.

Submit the Workflow Background Process Concurrent Program throughNavigate > Sysadmin > Request > RunItem Type – Select the appropriate Item Type (say PO Approval)Min and Max tershould – (specify 0 to 100 or you can leave it blank)Defered = Yes (so that all defered activities are processed)Timed out=Yes (so that all timedout activities are processed)

For automatically generating accrual, budget, charge, and variance accounts on purchase orders and releases.

workflow for automatically generating accrual, budget, charge, and variance accounts on requisitions.

PO Requisition Approval

PO Approval

PO Send Notifications for Purchasing DocumentsPO Approval Error workflow For troubleshooting errors that occur when using the PO Approval workflow

Account Generator Workflows PO Account Generator Workflow POWFPOAG

PO Requisition Account Generator Workflow POWFRQAGProject Budget Account Generator PABDACWF Generate combinations for budget items

Project Supplier Invoice Account Generator PAAPINVW

Project Web Employees Account Generator(PAAPWEBX)

Initializing Account Generator FND_FLEX_WORKFLOW.INITIALIZE

Adding Users dynamically to the role WF_DIRECTORY.AddUsersToAdhocRole(role_name,user_name);Removing users from the role WF_DIRECTORY.RemoveUsersFromAdHocRole

Access Level and Protection Level

Workflow Components

Business Event SystemsData Types to Attributes TEXT,NUMBER,DATE,LOOKUP,ROLE,ATTRIBUTE,URL,DOCUMENT,FORM,EVENT

Runnable Option in Workflow

Workflow for approving requisitions

Send PO Auto-creation to Background "N"

Workflow for approving purchase orders.

For Purchasing Documents workflow for looking for documents that are incomplete, rejected, or in need of reapproval, and sending notifications to the appropriate people of the document's status.

How do I trace errors in my Workflow processes

If a customized workflow process errors you should check the error stack (using the Workflow Monitor and/or wfstatus.sql script

To generate the WFSTAT output,Run the sql in $FND_TOP/sql/wfstat.sql with above item_type and item_key. Spool the output.To get the wf debug information, run the following query:

SELECT item_key, item_type, debug_messageFROM po_wf_debugWHERE item_key = ‘&Item_key’ORDER BY execution sequence;

Generates PO charge, encumbrance, variance, and accrualaccounting distributions

Generates requisition charge, encumbrance,variance, and accrual accounting distributions

Generates combinations when invoicedistribution references a project

Used by iExpenses to derive accounting combinations for expense report lines that reference a project.

http://docs.oracle.com/cd/A60725_05/html/comnls/us/wf/instal32.htmhttp://oracle.anilpassi.com/oracle-workflows-access-protection-concepts.htmlItem Type: A specific business document or transaction eg. Purchase order can be an item type. All the workflow components mentioned below are grouped together as an Item type. Item Type Attribute: A feature of the item type which stores information that can be globally referenced by any activity in a process. Also referred to as an item attribute.Process Activity: A series of actions that need to be performed to accomplish a business goal. A process is represented by a workflow diagram. A process can include function activities, notification activities, event activities, and other subprocesses.Event Activity: A business event modeled as an activity so that it can be included in a workflow process.Notification Activity: A unit of work that requires human intervention. A notification activity sends a message to a performer. Function Activity: An automated unit of work, usually defined as a PL/SQL stored procedure. A function activity can also run an external function. In the standalone version of Oracle Workflow, a function activity can also run a Java program on the middle tier.Message: The information sent by a notification activity. The message may request the performer to do some work or may simply provide information.Lookup Type / Lookup code: A list of values that can be referenced by any activity in a workflow process. The values in the list are called lookup codes.

Create Event Subscription under Business Events in Oracle Administrator Workflow WindowSpecify the PL/SQL or Work flow Item Type in the subscription and raise the business event by calling wf_event.RAISE function from anonymous block or from a trigger when a Business transaction happens.

wf_event.RAISE(p_event_name => x_event_name ,p_event_key => x_event_key ,p_parameters => x_event_parameter_list );

EVENTS: RECEIVE, SEND, RAISE

A workflow may have many process associated to it, The runnable option determines which process is the parent process to be initiated. It exists in the process level.

A runnable workflow is one that has received the event that it was waiting for but has not yet started processing that event.

Presentation

XML Publisher Vs BI Publisher

If you need to create reports with data from Oracle Ebusiness Suite then the recommended tool is the embedded tool XML Publisher (aka XMLP). If your ERP does not have it then you can patch it. For this you would have to consult Oracle Support for the appropriate patch number foryour environment.

If your reports come from different databases, oracle, msft sql server, db2, flat files, etc then the recommended is BI Publisher stand alone version. Current release 11g (part of BIEE11g suite and therefore it cannot be installed as stand alone). Previous release 10g (10.1.3.4.1) can be installedstand alone.

Presentation

Topic

Collections

PLSQL Version

External Tables

Triggers

Partitioning in Oracle. What? Why? When? Who? Where? How? - Partitioning in Oracle

Instead of Trigger

Pragma

Implicit and Explicit Cursors

Ref Cursors

Mutation Error

DECODE and CASE Functions

Description

Oracle lets you define procedures called triggers that run implicitly when an INSERT, UPDATE, or DELETE statement is issued against the associated table or, in some cases, against a view, or when database system actions occur. These procedures can be written in PL/SQL or Java and stored in the database, or they can be written as C callouts.

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

INSTEAD OF triggers provide a transparent way of modifying views that cannot be modified directly through DML statements (INSERT, UPDATE, and DELETE).

Instead of updating the view, you can create a trigger which overrides the default operation of the update statement:

create or replace trigger update_emp_thru_outemp_viewinstead of update on outempreferencing new as newbeginupdate empset ename = :new.ename,empno = :new.empno,job = :new.job,mgr = :new.mgr,hiredate = :new.hiredate,sal = :new.sal,comm = :new.comm,deptno = ( select deptno from dept where dname = :new.dname )where empno = :old.empno;if ( sql%rowcount = 0 )thenraise_application_error( -20001, 'Error updating the outemp view !!!' );end if;end;CREATE OR REPLACE TRIGGER images_v_insertINSTEAD OF INSERT ON images_vFOR EACH ROWBEGIN /* Call a packaged procedure to perform the insertion. || (The called procedure is not presented in the text.) */ manage_image.create_one(:NEW.image_id, :NEW.file_type, :NEW.file_name, :NEW.bytes, :NEW.keywords);END;Views That Are Not Modifiable

Pragma is a keyword in Oracle PL/SQL that is used to provide an instruction to the compiler.Pragmas are defined in the declarative section in PL/SQL.

The following pragmas are available: AUTONOMOUS_TRANSACTION:EXCEPTION_INIT:RESTRICT_REFERENCES:SERIALLY_REUSABLE:

C:\Users\ganapa\Desktop\Slideshare

PL/SQL issues an implicit cursor whenever you execute a SQL statement directly in your code, as long as that code does not employ an explicit cursor. It is called an "implicit" cursor because you, the developer, do not explicitly declare a cursor for the SQL statement.

An explicit cursor is a SELECT statement that is explicitly defined in the declaration section of your code and, in the process, assigned a name. Implicit cursors are implicitly created by the Oracle server for all DML and SELECT statements.

Implicit cursors are faster and result in much neater code.The answer is simply the volume of code being used. PL/SQL is an interpreted language so every extra line of code adds to the total processing time. As a rule of thumb, make the code as compact as possible without making it unsupportable.

A mutating table is a table that is currently being modified by an UPDATE, DELETE, or INSERT.Mutating occurs when u trying to access the table which is in the process of transition. When trying to access when an insert/update/delete is being carried on the same table on which the trigger is based.The mutating table problem occurs in row-level triggers.It is not encountered in statement-level triggers– They do not have to access table using :new and :old variables.

http://geekexplains.blogspot.com/2008/06/how-to-tune-sql-queries-for-better.html

C:\Users\ganapa\Desktop\REF_CURS

C:\Users\ganapa\Desktop\Slideshare

Attachments

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\REF_CURS

C:\Users\ganapa\Desktop\Slideshare

Topic

Types of Triggers

Sequence of Trigger Fire while Committing

Sequence of Trigger Fire while moving from one text box to another

Master-Detail Relation (Triggers/Procedures/Properties)

Dynamically Populate LOV/List Item

Object Libraries (Use/Benefits)

Object Groups

Key-next/Post-Text (Difference)

Call From/New Form/Open Form (Difference)

Types of Canvases (Stacked/Content Difference)

Various Block Co-ordination Properties

DDL statements from Forms

dynamic SQL from Forms

WHO Columns in Forms

How to attach same LOV to multiple items

standard libraries available in template form

Sequence of firing triggers in forms.

Record Groups

Description

KEY CommitPre CommitPre/On/Post DeletePre/On/Post UpdatePre/On/Post InsertOn commitPost Database Commit

First text box:When Validate itemKey Next ItemPost text Item

Current Text box:Pre text itemwhen new item instance

ADD_LIST_ELEMENT (one by one)POPULATE_LIST built-in

The Object Library provides an easy method of reusing objects andenforcing standards across the entire development organization.

There are several advantages to using object libraries to develop applications:

1. Object libraries are automatically re-opened when you startup Form Builder, making your reusable objects immediately accessible.2. You can associate multiple object libraries with an application. For example, you can create an object library specifically for corporate standards, and you can create an object library to satisfy project-specific requirements.3. Object libraries feature Smart Classes-- objects that you define as being the standard. You use Smart Classes to convert objects to standard objects

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

An object group is a container for a group of objects. You define an object group when you want to package related objects so you can copy or subclass them in another module.Object groups provide a way to bundle objects into higher-level building blocks that can be used in other parts of an application and in subsequent development projects. For example, you might build an appointment scheduler in a form and then decide to make it available from other forms in your applications. The scheduler would probably be built from several types of objects, including a window and canvas, blocks, and items that display dates and appointments, and triggers that contain the logic for scheduling and other functionality. If you packaged these objects into an object group, you could then copy them to any number of other forms in one simple operation.You can create object groups in form and menu modules. Once you create an object group, you can add and remove objects to it as desired.

Post-Text–Item: Fires during the Leave the Item process for a text item. Specifically, this trigger fires when the input focus moves from a text item to any other item.

Call Form: Runs an indicated form while keeping the parent form active. Form Builder runs the called form with the same Runform preferences as the parent form. When the called form is exited Form Builder processing resumes in the calling form at the point from which you initiated the call to CALL_FORM.

New Form: Exits the current form and enters the indicated form. The calling form is terminated as the parent form. If the calling form had been called by a higher form, Form Builder keeps the higher call active and treats it as a call to the new form. Form Builder releases memory (such as database cursors) that the terminated form was using.Form Builder runs the new form with the same Runform options as the parent form. If the parent form was a called form, Form Builder runs the new form with the same options as the parent form.

Open Form: Opens the indicated form. Use OPEN_FORM to create multiple-form applications, that is, applications that open more than one form at the same time.

(i) Content Canvas (Default Canvas) [A content canvas is the required on each window you create](ii) Stack Canvas [you can display more then one stack canvas in a window at the same time] (iii) Tab Type Window [In Tab canvas that have tab pages and have one or more then tab page] (iv) Toolbar Canvas [A toolbar canvas often is used to create Toolbar Windows. There are two type of Toolbar window.a. Horizontal Toolbar Canvas: - Horizontal Toolbar canvases are displayed at the top of the window, Just Under the Main Menu Bar.b. Vertical Toolbar Canvas: - While vertical Toolbar are displayed along the Left Edge of the window.

The various Block Coordination Properties area) ImmediateDefault Setting. The Detail records are shown when the Master Record are shown.b) Deffered with Auto QueryOracle Forms defer fetching the detail records until the operator navigates to the detail block.c) Deferred with No Auto QueryThe operator must navigate to the detail block and explicitly execute a query

FND_STANDARD.SET_WHO ( In pre insert and pre-update triggers)

We can use the same LOV for 2 columns by passing the return values in global values and using the global values in the code.

FORMS_DDL('CREATE TABLE X (A DATE)');

FORMS_DDL('INSERT INTO X VALUES ('||col_list||')');

APPCORE - Contains packages & procedures for forms to support menu, toolbar and other standard behavioursAPPDAYPK - The APPDAYPK library contains the packages that control the Oracle Applications Calendar feature. The calendar (or the date picker) is a utility that oracle apps provide to pick the dates for a date type fieldFNDSQF - Routines for handling Message Dictionary, felxfields, prpfiles, concurrent processing, mulicurrency, WHO etcAPPCORE2CUSTOM

1. Pre-Form 2. Pre-Block3. Pre-Record4. Pre-Text-Item5. When-New-Form-Instance6. When-New-Block-Instance 7. When-New-Record-Instance8. When-New-Item-Instance

The folowing sequence should be followed when you exit from the form:

1. post text item2. post record3. post block4. post form

Record Groups.txt

A record group is an oracle forms data structure that has a column/row framework similar to a database table.

There are three types of record groups: query record groups, non-query record groups, and static record groups.

Query record group A query record group is a record group that has an associated SELECT statement. Query record groups can be created and modified at design time or at runtime.

Non-query record groupA non-query record group is a group that does not have an associated query. Non-query record groups can be created and modified only at runtime.

Static record group A static record group is not associated with a query. Static record groups can be created and modified only at design time.

Record Groups.txt

Attachement

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\Slideshare

Record Groups.txt

Record Groups.txt

Topic Report Level Triggers (Sequence)

User Exits

DDL Statements in Reports

Format Triggers

Conditional Formatting

Lexical & Bind Parameters in Reports

Flex & Confine Mode in Reports

Matrix Reports (Matrix By Groups)

Anchoring

Set completion status of Concurrent Request

Summary Column, Place holder Column, and Formula Column?

Description

· Before parameter form· After parameter form· Before Report· Between Pages· After Report

srw.user_exit(‘ fnd srwinit’) - Before Report Triggersrw.user_exit (‘fnd srwexit’) - After Report Trigger

You build user exits when you want to pass control from Report Builder to a program you have written, which performs some function, and then returns control to Report Builder.

User Exits are 5 Types.

• FND SRWINIT• FND SRWEXIT• FND FORMAT_CURRENCY • FND FLEXIDVAL• FND FLEXSQL

FND SRWINIT--Used to set the profile option and OA Object library environment value.

FND SRWEXIT--Used to release the profile option and environmental value.

FND FORMAT_CURRENCY--Used to format the currency dynamically.

FND FLEXIDVAL--Used to populate the fields for display.

FND FLEXSQL--this user exit is called to create a SQL fragment usable by your report to tailer your SELECT statement that retrives FLEX FIELD value.

eg: srw.user_exit('FND SRWINT')

SRW.MESSAGEThis procedure allows developers to create their own messages and return them at runtime. It takes two arguments, a message number and message text. It can be used for error handling or debugging. Applications uses this feature to standardize and share messages across reports.

ExampleSRW.MESSAGE('500','First debug point');

SRW.USER_EXIT and SRW.REFERENCEBecause Applications reports commonly call user exits it is critical that Oracle Reports support such calls. To facilitate this requirement the Package offers SRW.USER_EXIT

SRW.DO_SQL and SRW.DO_SQL_FAILURESRW Package is a collection of PL/SQL constructs that provide developers with a suite of built-in functions, procedures, and exceptions that can be used in any of your libraries or reports. The following lists several of these constructs, and briefly describes how Applications uses them in reports.

SRW.DO_SQL and SRW.DO_SQL_FAILUREWhen it is necessary to perform data definition statements (DDL), the SRW.DO_SQL packaged procedure must be used. You cannot perform DDL statements in PL/SQL. In conjunction with this, we use the SRW.DO_SQL_FAILUREexception which raises an error if the statement should fail.

ExampleBEGINSRW.DO_SQL('Create table Test...');EXCEPTION when SRW.DO_SQL_FAILURE then .....END;

A format trigger is used when we want to display a particular field, if certain conditions are met.

A format trigger is a PL/SQL function executed before an object is formatted. A trigger can be used to dynamically change the formatting attributes of the object.The Format Trigger property allows you to code your own PL/SQL functions to perform conditional formatting. Because you write the code yourself, you have more flexibility and complete control when compared to using the Conditional Formatting and Format Exception dialog boxes alone.

The Conditional Formatting and Format Exception dialog boxes lets you specify multiple conditions and formatting attributes (font, text color, border, and fill color) for a selected layout object. You don't write any code with this method.

Confine mode:

On: child objects cannot be moved outside their enclosing parent objects.Off: child objects can be moved outside their enclosing parent objects.

Flex mode:

On: parent borders “stretch” when child objects are moved against them.Off: parent borders remain fixed when child objects are moved againstthem.

A matrix (cross tab) report contains one row of labels, one column of labels, and information in a grid format that is related to the row and column labels. A distinguishing feature of matrix reports is that the number of columns is not known until the data is fetched from the database. To create a matrix report, you need at least four groups: one group must be a cross-product group, two of the groups must be within the cross-product group to furnish the "labels," and at least one group must provide the information to fill the cells. The groups can belong to a single query or to multiple queries.

Types of Matrix ReportsSimple Matrix Report:Nested Matrix Report:Multi-Query Matrix with BreakMatrix Break Reports

Bind parameters are used to substitute one value at runtime for evaluation and are identified by a preceding ‘:’. An example of a bind parameter in a select statement is provided below, where :P_EMP is the bind parameter reference.Lexical parameters are used to substitute multiple values at runtime and are identified by a preceding ‘&’. Lexicals can consist of as little a one line where clause to an entire select statement. An example of a lexical parameter usage in a select statement is below where &L_EMP is the lexical parameter reference.

Set completion status of Concurrent Request

It is a feature thru which we can control the position of the boiler plate or data fields in layout.Anchors are used to determine the vertical and horizontal positioning of a child object relative to its parent. The end of the anchor with a symbol is attached to the parent object. When you create a default layout, Reports will create some of its own implicit anchors. These are not visible. There may be occasions when you want to create your own explicit anchors to force objects to be positioned together or to conditionally specify when the object prints. You c e anchor at any distance down the edge of the object. The distance is a percentage of the total length of the edge. You can adjust this position in the anchor property sheet. Examples of using explicit anchors: ANCHORING BOILERPLATE TO A FRAME

A summary column performs a computation on another column's data. Using the Report Wizard or Data Wizard, you can create the following summaries: sum, average, count, minimum, maximum, % total. You can also create a summary column manually in the Data Model view, and use the Property Palette to create the following additional summaries: first, last, standard deviation, variance.A placeholder is a column for which you set the data type and value in PL/SQL that you define. You can set the value of a placeholder column in the following places. A place holder column stores a value which we can refer in the layout.A formula column performs a user-defined computation on another column(s) data, including placeholder columns. Formula columns should not be used to set values for parameters.

Trace file will be generated at location:select value from v$parameter where name = 'user_dump_dest';

format the generated trace file with tkprof statement.

C:\Users\ganapa\Desktop\Slideshare

Phase Status Description PENDING Normal Request is waiting for the next available manager Standby Program to run request is incompatible with other program(s) currently running Scheduled Request is scheduled to start at a future time or date. Waiting A child request is waiting for its Parent request to mark it ready to run. For example, a request in a request set that runs sequentially must wait for a prior request to complete RUNNING Normal Request is running normally Paused Parent request pauses for all its child requests to finish running. For example, a request set pauses for all requests in the set to complete. Resuming All requests submitted by the same parent request have completed running. The Parent request resumes running. Terminating Request is terminated by choosing the Cancel Request button in Requests window COMPLETED Normal Request completed successfully. Error Request failed to complete successfully Warning Request completed with warnings. For example, a request is generated successfully but fails to print Cancelled Pending or Inactive request is cancelled by choosing the Cancel Request button in the Requests window. Terminated Request is terminated by choosing the Cancel Request button in the Requests window. Inactive Disabled Program to run request is not enabled. Contact your system administrator. On Hold Pending request is placed on hold by choosing the Hold Request button in the Requests window. No Manager No manager is defined to run the request. Check with your system administrator. A status of No Manager is also given when all managers are locked by run-alone requests.

DECLARECURSOR c1SELECT Customer_Account_Id, Effective_Date,Expired_Date FROM CustomerWHERE Effective_Date BETWEEN TO_DATE(’01-Jan-2003’, ‘DD-MON-RRRR’) And TO_DATE(’01-Jan-2004’, ‘DD-MON-RRRR’);TYPE Cust_tab IS TABLE OF C1%ROWTYPE;Custs Cust_tab;BEGIN OPEN c1; LOOP FETCH c1 BULK COLLECT INTO Custs LIMIT 100; END LOOP;FORALL i IN 1 .. Custs.COUNTSAVE EXCEPTIONSINSERT into Customer_History VALUES Custs (i);

Attachment

select *from empwhere emp.name = :P_EMP;

select *from empwhere &L_EMP;

C:\Users\ganapa\Desktop\Slideshare

PAY on Receipt Attachments

PO Matching 2-Way/3-Way/4-WayInvoice Matching PO and Receipt

Receipt Routing Standard Routing/Direct Delivery/Insp

General Ledger

Create Accounting at Sub Ledger Level

MOAC

Requisition_Purchasing_Query

Account Receivables

Customer Creation API - hz_party_site_v2pub

HZ Tables in Oracle Receivables

Receivables Receipts API

Pay on Receipt: This feature is alternately known in Oracle User Guides as:Evaluated Receipt Settlement (ERS)Payment on Receipt (POR)Self-Billing Invoices (SBI)

New Profile Option "SLA: Disable Journal Import"

Presentation

E:\VPN\Study\GLr12 - SLA Disable

Document

E:\VPN\Study\Customer Import us

E:\VPN\Study\REQ_PUR_QUERY.r

E:\VPN\Study\The 10 AR Receipt API.

Document

C:\Users\ganapa\Desktop\Slideshare

C:\Users\ganapa\Desktop\R12 MOAC

C:\Documents and Settings\Administrator\Desktop\Knowledge Base\HZ tables in Oracle Receivables.doc

User Exits

Oracle Report Triggers

Types of Columns in Report

Security Rules

Cross Validation Rules

RFQ - Three types of RFQs

Bid/Catalog/Standard

Documentation

User Exists are 5 Types.

• FND SRWINIT• FND SRWEXIT• FND FORMAT_CURRENCY • FND FLEXIDVAL• FND FLEXSQL

RD 10 --> Current Financial and Operating StructureRD 20 --> Current Business BaselineRD 50 --> Business Requirements Scenario

BP 80 --> Business Process Design ( To be process )BR 10 --> High Level Gap AnalysisBR 30 --> Business Requirements MappingMD 50 --> Application Extension Functional DesignMD 70 --> Application Extension Technical Design

BR 100 --> Application SetupTE 20 --> Unit Test ScriptTE 40 --> System Test ScriptTE 50 --> System Integration Test ScriptTE 120 --> System Integration Test Plan

TE 130 - User Acceptance Test Report

User ManualsClient's sign off on the Acceptance Certificate

E:\VPN\Study\Release12Payment

E:\VPN\Study\GL Flexfield Security R

E:\VPN\Study\Cross-Validation Rul

Payment Manager in R12 (PPR)

Types of Books in FAR12 Subledger Accounting (SLA)

What's new in Oracle Applications R12

ERRBUFF and RETCODECreating DFF and KFF DinamicallyValueSets

Depreciation Book and Tax Books

Revenues TCS - 3 Billion (2356.2 $m)Infosys - 1658.1 $mWIPRO - 1.7 Billion (1456.4 $m)HCL Technology - 969.4 $mIBM - 29 BillionAccenture: 21 Billion

E:\VPN\Study\Release12Payment

E:\VPN\Study\R12 Subledger Accounti

C:\Documents and Settings\srvis\Desk

C:\Users\ganapa\Desktop\Slideshare

FND Profile

How to Change AP Formats in R12

Blanket Purchase Agreements:

Types of Assets in FAAsset Life CycleAP to FA or FA to AP APIPage break in ReportHide and show header/detail in XML ReportTypes of Discoverer ReportsParameters for Workflow Background Process (Deferred,Immediate)Common Parameter when calling APIHow to Migrate Forms

Oracle Inventory - Inventory Status TypesReceiving Options - To receive more than than PO qty or equal to PO qtyMatchingHandling tax in AP LinesFOR ALL (setting limit)FA to GL data flowAccounting Entries (When we procure and when we sell)Calling OAF region in Workflow

Accounting Convention: 4TH C

There is no set of books in R12, instead a Ledger had to becreated. In addition to the 3 C’s of Calendar, Chart of Accounts and Currencywhich were the components of Set of Books in R11i, R12 introduced a 4th C,Convention. The Convention represents the accounting method used atsubledger level like Accrual basis of accounting or Cash basis of accounting

In 11i the subledger accounting method (cash/accrual) was used to be defined at the subledger setup (AP/AR). However in R12 things have changed. You define the subledger accounting method at the ledger level. All subledgers tied to that ledger will use that particular accounting convention. So there is a difference in 11i and R12. The accounting "Convention" is now married to the ledger and hence the term 4Cs.

If you are not planning to use subledgers then you do not have to choose a value in the accounting method field. You can leave it blank. Your GL functionality will remain unaffected. However you will have to specify an accounting method at the ledger setup, before you could use a subledger.

FND Load - Loading onto multiple tables, sql functions, condition for more than 10 errors,dynamic parameters

C:\Users\ganapa\Desktop\Slideshare

C:\Documents and Settings\Administrator\Desktop\Knowledge Base\Blanket Purchase Agreements.doc

Qutation Tables

AERESATEWZPPPPFADRYDZ

direct--------goods recieved from

supplier ----------> sub inventory.

standard ------supplier---->recieving area(stagging area)------>sub inventory

inspection----------

supplier----> recieving area------->inspection(done)---->sub inventory.

To understand which applications have multiple organizations access control feature enabled you can query a new table “FND_MO_PRODUCT_INIT). If the product that is enabled has a “Y” for status field then that product can use the MOAC feature.

z

FND SRWINIT--Used to set the profile option and OA Object library environment value.

FND SRWEXIT--Used to release the profile option and environmental value.

FND FORMAT_CURRENCY--Used to format the currency dynamically.

FND FLEXIDVAL--Used to populate the fields for display.

FND FLEXSQL--this user exit is called to create a SQL fragment usable by your report to tailer your SELECT statement that retrives FLEX FIELD value.

eg: srw.user_exit('FND SRWINT')

Before Parameter FormAfter Parameter FormBefore ReportBetween PagesAfter Report

Summary ColumnsFormula ColumnsPlace Folder Columns

Bid : If company is going to purchase large number of items which are expensive. We will create bid RFQ where we will specify Headers, lines and shipments, where we are not specify any price breaks in Bid RFQ.

Catalog : If company is purchasing materials regularly fixed quantity location and date, then we will select regularly we can include price breaks at different levels.

Standard : This will be created for items we need only once or not regularly, we can include price breaks at different quality levels

Below Concurrent Programs are submitted in SRS while runningPayment Process Request from Payment Manager1) Auto Select (Payment Process Request Program)2) Scheduled Payment Selection Report3) Build Payments4) Format Payment Instructions

http://www.slideshare.net/ngcoders2001/r12-payment-process-request-status-flow

http://oracleerp4u.blogspot.com/2010/06/ap-payment-testing-in-r12.html

IBY_DOCS_PAYABLE_ALLIBY_PAYMENTS_ALLIBY_PAY_SERVICE_REQUESTSIBY_PAY_INSTRUCTIONS_ALLIBY_PMT_INSTR_USES_ALL

An asset can belong to any number of depreciation books, but must belong to only one corporate depreciation book. You must assign a new asset to a corporate depreciation book before you can assign it to any tax books.

Ledger SetsSubledger Accounting Transaction Based Taxes (EBTAX)Advanced Intercompany System(AGIS)Multi Organization Access Control(MOAC)

The ERRBUF is the message that you return and RETCODE is the return code.If the RETCODE is 0 stands for Success, 1 for success with warnings and 2 for Errors.CREATE PROCEDURE TEST_CONC(ERRBUF OUT VARCHAR2,RETCODE OUT VARCHAR2)

IBY_FD_EXTRACT_EXT_PUB

FND_GLOBAL.APPS_INITIALIZE (User Id,Resp ID,Resp Appl id)FND_GLOBAL.USER_IDFND_GLOBAL.LOGIN_IDFND_GLOBAL.CONC_LOGIN_IDFND_GLOBAL.CONC_REQUEST_IDFND_PROFILE.PUTFND_PROFILE.GETFND_PROFILE.VALUE('PROFILEOPTION')FND_PROFILE.VALUE('MFG_ORGANIZATION_ID')FND_PROFILE.VALUE('LOGIN_ID')FND_PROFILE.VALUE('USER_ID')FND_PROFILE.VALUE('USERNAME')FND_PROFILE.VALUE('CONCURRENT_REQUEST_ID')FND_PROFILE.VALUE('GL_SET_OF_BKS_ID')FND_PROFILE.VALUE('ORG_ID')FND_PROFILE.VALUE('APPL_SHRT_NAME')FND_PROFILE.VALUE('RESP_NAME')FND_PROFILE.VALUE('RESP_ID')

Import Price CatelogImport Standard Purchase Order

Topic Description

1 Importing Business Area

2 Registering Custom PLSQL Functions in Discoverer

C:\Documents and Settings\Administrator\Desktop\Knowledge Base\Export-Import Discoverer Business Area.doc

C:\Documents and Settings\Administrator\Desktop\Knowledge Base\Regiserting Custom PLSQL Functions in Discoverer.doc

Attachments

C:\Documents and Settings\Administrator\Desktop\Knowledge Base\Export-Import Discoverer Business Area.doc

C:\Documents and Settings\Administrator\Desktop\Knowledge Base\Regiserting Custom PLSQL Functions in Discoverer.doc

Migrating Oracle Alerts

Periodic Alert Scheduler (ALEPPE)

Types of Alerts

FNDLOAD Utility

Using Alert Manager Responsibility:

EVENT Alert and PERIODIC Alert

AttachmentFNDLOAD apps_user_name/apps_password 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct my_file.ldt ALR_ALERTS APPLICATION_SHORT_NAME=’XXCUST’ ALERT_NAME=<Alert name to download>

FNDLOAD apps_user_name/apps_password 0 Y UPLOAD $ALR_TOP/patch/115/import/alr.lct my_file.ldt – CUSTOM_MODE=FORCE

(Check the attachment)

The Periodic Alert Scheduler (ALEPPE) is a concurrent program that automatically checks your scheduled periodic alerts.

The Periodic Alert Scheduler runs at each day at 12 AM. When it runs, the Periodic Alert Scheduler looks for all periodic alerts scheduled to be checked that day, and then submits one concurrent request for each scheduled check.

EVENT Alerts are triggered when an event or change is made to a table in the database.

PERIODIC Alerts are activated on a scheduled basis to monitor database activities or changes.

C:\Users\ganapa\Desktop\Slideshare