iExpenses Profile Options

User profile Options

Comments

Post a Comment

Popular posts from this blog

Sub Ledger Period Close Exception Report - R12

Image
Sub Ledger period close exception Report is used by finance and accounts department to view list of un-accounted transactions in Accounts receivables before closing GL Period Un-processed transactions will be listed in the report for GL period Report summary shows following details: Against a specific ledger, period, and journal source how many exceptions are there (i.e., unprocessed transactions with count) Detail of transactions which are un-processed will be grouped against journal category and event classes This report helps in resolving exceptions quickly so that exceptions are not left to slow down the period-end close It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or non-transferred journal entries. 
Read more

Query to get FSG report details with row/column set

Below query is to fetch FSG report titles, names, and description along with will give a view to list of row sets and column sets associated with the report. -- FSG REPORTS -- SELECT fst.id_flex_structure_name , R.NAME , R.report_title , R.DESCRIPTION , R.column_set "COLUMN SET" , rw2.structure_id , rw2.DESCRIPTION "COL DESC" , R.row_set "ROW SET" , rw.DESCRIPTION "ROW DESC" , R.report_display_set "DISPLAY SET" , R.content_set "CONTENT SET" , R.row_order "ROW ORDER" , R.rounding_option "RND" , u.user_name , u.DESCRIPTION , R.creation_date FROM rg_reports_v R    , fnd_id_flex_structures_v fst    , fnd_user u    , rg_report_axis_sets_v rw    , rg_report_axis_sets_v rw2 WHERE r.structure_id = fst.id_flex_num AND R.row_set_id     = rw.axis_set_id AND r.column_set_id  = rw2.axis_set_id AND SUBSTR(fst.id_flex_structure_name,1,2) IN ('DC') AND R.created_by     = u.user_id OR...
Read more

How to create a sale order using open interfaces R12

Create header records in sale orders open interface tables Order sources can be through Telesales, Online channel, iStores, Siebel CRM or any custom sources (Check OE_ORDER_SOURCES table) original system document reference should be used to create sale order Org id indicates operating unit for which sale order to be booked Price list for sales order Payment terms to be assigned to sale order currency bill to, ship to org id indicates site use id of customer accounts sold from and sold to org id indicates operating units ship from org id indicates sub-inventory org id invoice to org id indicates bill to -site use id of customer accounts customer id indicates customer account id booked flag = 'Yes' operation code = 'Insert' mode for new sale orders INSERT INTO apps.oe_headers_iface_all   ( order_source_id ,     orig_sys_document_ref ,     org_id ,     ordered_date ,     order_type_id ,     price_list_id ,...
Read more