Staging Inquiry: Monster Culture. Staging Inquiry: Monster Culture.
Dsm Ar Staging Interface Base Tables
-
Upload
nagaraju-sagar -
Category
Documents
-
view
6 -
download
0
description
Transcript of Dsm Ar Staging Interface Base Tables
SELECT * FROM XXIDEA.IDEA_CREDIT_CHECK_TBLWHERE ORDER_NUMBER = 'ORD0000137452'Credit check table will have customer bill to site_use_id numberThis table will store credit check details sent by DSM, instrument details and customer details should be same in DSM and Oracle.SELECT * FROM XXIDEA.IDEA_ORDER_STAGINGWHERE ORIG_SYS_REF = 'ORD0000137452'This is a staging table in oracle application, this table will store details of DSM Orders (OM Related Orders)SELECT * FROM XXIDEA.IDEA_ORDER_STAGING_ARCWHERE ORIG_SYS_REF = 'ORD0000137452'Once the DSM Order is sucessfully inserted in AR Interface data will be deleted from staging table and populate in archive tableSELECT * FROM XXIDEA.IDEADSM_VTOPUP_ORDER_INVWHERE DSMORDERNO = 'ORD0000101135'This table stores data pushed from DSM to Oracle Application for VTOPUP OrdersSELECT * FROM XXIDEA.IDEA_RA_INTER_LIN_STG_VTOPINVWHERE ORDER_NUMBER = 'ORD0000101135'This is a staging table in oracle application, this table will store details of VTOPUP Orders temporarlySELECT * FROM XXIDEA.XXIDEA_RA_IFACE_LINES_ARC_VTOPWHERE ORDER_NUMBER = 'ORD0000101135'Once the VTOPUP Order is sucessfully inserted in AR Interface data will be deleted from staging table and populate in archive tableSELECT * FROM RA_INTERFACE_LINES_ALLWHERE BATCH_SOURCE_NAME = 'VTOPUP'AND HEADER_ATTRIBUTE7 = 'ORD0000101135'SELECT * FROM RA_INTERFACE_LINES_ALLWHERE BATCH_SOURCE_NAME = 'DSM ORDER'AND HEADER_ATTRIBUTE7 = 'ORD0000101135'AND INTERFACE_LINE_ATTRIBUTE1 = '91000080687'This is AR Interface table which will have all unprocessed and error lines inserted from various sourcesSELECT * FROM RA_INTERFACE_LINES_ALL A, RA_INTERFACE_ERRORS_ALL BWHERE A.INTERFACE_LINE_ID = B.INTERFACE_LINE_IDAND A.BATCH_SOURCE_NAME IN ('DSM ORDER','ORDER ENTRY','VTOPUP')This table stores error records in interaceSELECT * FROM RA_CUSTOMER_TRX_ALL AWHERE A.TRX_DATE BETWEEN '01-JAN-2012' AND '14-FEB-2012' AND A.ORG_ID = 107AND A.BATCH_SOURCE_ID IN (SELECT B.BATCH_SOURCE_ID FROM RA_BATCH_SOURCES_ALL B WHERE NAME = 'VTOPUP' AND B.ORG_ID =A.ORG_ID)AND A.CUST_TRX_TYPE_ID IN (SELECT C.CUST_TRX_TYPE_ID FROM RA_CUST_TRX_TYPES_ALL C WHERE NAME LIKE '%Flexi INV' AND C.ORG_ID=A.ORG_ID)AND INTERFACE_HEADER_ATTRIBUTE1 = 'RJ/1201/O0040950'--AND A.ATTRIBUTE7 = 'ORD0000101135'This query to identify the transaction details against VTOPUP OrderSELECT * FROM RA_CUSTOMER_TRX_ALL AWHERE A.TRX_DATE BETWEEN '01-JAN-2012' AND '14-FEB-2012' AND A.ORG_ID = 107AND A.BATCH_SOURCE_ID IN (SELECT B.BATCH_SOURCE_ID FROM RA_BATCH_SOURCES_ALL B WHERE NAME = 'DSM ORDER' AND B.ORG_ID=A.ORG_ID) AND A.INTERFACE_HEADER_ATTRIBUTE1 = '91000080629'--AND A.ATTRIBUTE7 = 'ORD0000101135'This query to identify the transaction details against VTOPUP Orderselect a.customer_trx_id,a.trx_number,a.trx_date,a.attribute7 dsm_order,a.attribute8 distributor_comm,a.attribute9 instrument_number1,a.attribute10 instrument_date1,a.attribute11 instrument_amount1,a.attribute12 instrument_type1,a.attribute13 instrument_number2,a.attribute14 instrument_date2,a.attribute15 instrument_amount2,a.attribute6 instrument_type2,a.attribute1 instrument_number3,a.attribute2 instrument_date3,a.attribute3 instrument_amount3,a.attribute5 instrument_type3,b.amount_due_original,b.amount_due_remaining,b.status,b.class,b.amount_applied,b.gl_datefrom ra_customer_trx_all a, ar_payment_schedules_all bwhere a.customer_trx_id = b.customer_trx_id and a. request_id = 98334775-------------------------Transaction details with Receipt, DSM Order------------select a.receivable_application_id,a.amount_applied,a.gl_date,a.apply_date,a.application_type,a.status,b.trx_number,(select trx_number from ra_customer_trx_all c where c.customer_trx_id = a.applied_customer_trx_id) transaction_number, b.trx_date,b.gl_date,a.cash_receipt_id,a.applied_customer_trx_id,b.amount_due_original,b.amount_due_remaining,b.status,b.class,b.amount_appliedfrom ar_receivable_applications_all a, ar_payment_schedules_all bwhere a.cash_receipt_id = b.cash_receipt_idand a.applied_customer_trx_id in (select customer_trx_id from ra_customer_trx_all where request_id = 98334775)-------------------------receipt application details with receipt and transaction number--------------Problem: Multiple invoices and miscellaneous issue of quantity generated in Oracle Application against DSM OrderCause: DSM Order pushed multiple times from DSM Application (DSM Transaction ID is different)Resolution: Receivables:Unapply if the receipt is applied for extra generated invoices and Query the invoice and create credit memo against the invoice.Inventory:Calculate all the extra quantity issued out from the inventory and do miscellaneous receipt (At the time of miscellaneous issue call support team in case of any concerns).--------------------RMA in oracle application for DSM Orders-------------------select request_id, count(*)from ra_customer_trx_lines_all cwhere c.customer_trx_id in (select a.customer_trx_id from ra_customer_trx_all awhere a.trx_date > '19-FEB-2012'and a.batch_source_id in (select b.batch_source_id from ra_batch_sources_all b where name = 'DSM ORDER' and a.org_id = a.org_id))group by request_id