Total Pageviews

Saturday, March 9, 2013


Oracle Account Receivable 11i and R12 Tables


Oracle Account Receivable 11i and R12 Tables


ACCOUNT RECEIVABLES
Un Changed = 498
New Tables = 118
Deleted = 53

 11i  TABLESR12 TABLES
1AQ$_AR_REV_REC_QT_GAQ$_AR_REV_REC_QT_G
2AQ$_AR_REV_REC_QT_HAQ$_AR_REV_REC_QT_H
3AQ$_AR_REV_REC_QT_IAQ$_AR_REV_REC_QT_I
4AQ$_AR_REV_REC_QT_SAQ$_AR_REV_REC_QT_S
5AQ$_AR_REV_REC_QT_TAQ$_AR_REV_REC_QT_T
6AR_ACTION_NOTIFICATIONSAR_ACTION_NOTIFICATIONS
7AR_ADJUSTMENTS_ALLAR_ADJUSTMENTS_ALL
8AR_ADJUSTMENTS_REP_ITFAR_ADJUSTMENTS_REP_ITF
9AR_AE_ALLOC_REC_GTAR_AE_ALLOC_REC_GT
10AR_AGING_BUCKET_LINES_BAR_AGING_BUCKET_LINES_B
11AR_AGING_BUCKET_LINES_TLAR_AGING_BUCKET_LINES_TL
12AR_AGING_BUCKETSAR_AGING_BUCKETS
13AR_APP_RULE_DETAILSAR_APP_RULE_DETAILS
14AR_APP_RULE_SETSAR_APP_RULE_SETS
15AR_APP_RULESAR_APP_RULES
16AR_APPROVAL_ACTION_HISTORYAR_APPROVAL_ACTION_HISTORY
17AR_APPROVAL_USER_LIMITSAR_APPROVAL_USER_LIMITS
18AR_ARCHIVE_CONTROLAR_ARCHIVE_CONTROL
19AR_ARCHIVE_CONTROL_DETAILAR_ARCHIVE_CONTROL_DETAIL
20AR_ARCHIVE_DETAILAR_ARCHIVE_DETAIL
21AR_ARCHIVE_HEADERAR_ARCHIVE_HEADER
22AR_ARCHIVE_PURGE_INTERIMAR_ARCHIVE_PURGE_INTERIM
23AR_ARCHIVE_PURGE_LOGAR_ARCHIVE_PURGE_LOG
24AR_AUDIT_DATAAR_AUDIT_DATA
25AR_AUTOCASH_HIERARCHIESAR_AUTOCASH_HIERARCHIES
26AR_AUTOCASH_RULESAR_AUTOCASH_RULES
27AR_AUTOREC_EXCEPTIONSAR_AUTOREC_EXCEPTIONS
28AR_BANK_DIRECTORYAR_BANK_DIRECTORY
29AR_BATCH_SOURCES_ALLAR_BATCH_SOURCES_ALL
30AR_BATCHES_ALLAR_BATCHES_ALL
31AR_BPA_AREA_ITEMSAR_BPA_AREA_ITEMS
32AR_BPA_CONTENT_AREAS_BAR_BPA_CONTENT_AREAS_B
33AR_BPA_CONTENT_AREAS_TLAR_BPA_CONTENT_AREAS_TL
34AR_BPA_DATA_SOURCES_BAR_BPA_DATA_SOURCES_B
35AR_BPA_DATA_SOURCES_TLAR_BPA_DATA_SOURCES_TL
36AR_BPA_DATA_SRC_PARAMSAR_BPA_DATA_SRC_PARAMS
37AR_BPA_DATASRC_APPS_BAR_BPA_DATASRC_APPS_B
38AR_BPA_DATASRC_APPS_TLAR_BPA_DATASRC_APPS_TL
39AR_BPA_ITEMS_BAR_BPA_ITEMS_B
40AR_BPA_ITEMS_TLAR_BPA_ITEMS_TL
41AR_BPA_PAGE_SETUPS_BAR_BPA_PAGE_SETUPS_B
42AR_BPA_PAGE_SETUPS_TLAR_BPA_PAGE_SETUPS_TL
43AR_BPA_PRINT_REQUESTSAR_BPA_PRINT_REQUESTS
44AR_BPA_RULE_ATTRIBUTES_BAR_BPA_RULE_ATTRIBUTES_B
45AR_BPA_RULE_ATTRIBUTES_TLAR_BPA_RULE_ATTRIBUTES_TL
46AR_BPA_RULE_TEMPLATESAR_BPA_RULE_TEMPLATES
47AR_BPA_RULES_BAR_BPA_RULES_B
48AR_BPA_RULES_TLAR_BPA_RULES_TL
49AR_BPA_TEMPLATE_FIELDSAR_BPA_TEMPLATE_FIELDS
50AR_BPA_TEMPLATE_FILESAR_BPA_TEMPLATE_FILES
51AR_BPA_TEMPLATES_BAR_BPA_TEMPLATES_B
52AR_BPA_TEMPLATES_TLAR_BPA_TEMPLATES_TL
53AR_BPA_URL_PARAMSAR_BPA_URL_PARAMS
54AR_BPA_URLS_BAR_BPA_URLS_B
55AR_BPA_URLS_TLAR_BPA_URLS_TL
56AR_BR_FMT_TMPAR_BR_FMT_TMP
57AR_BR_STAMP_VALUES_ALLAR_BR_STAMP_VALUES_ALL
58AR_BR_STATUS_REP_ITFAR_BR_STATUS_REP_ITF
59AR_BR_STATUS_SUM_ITFAR_BR_STATUS_SUM_ITF
60AR_BR_TRX_BATCH_RPTAR_BR_TRX_BATCH_RPT
61AR_CALL_ACTIONSAR_CALL_ACTIONS
62AR_CASH_BASIS_DISTS_ALLAR_CASH_BASIS_DISTS_ALL
63AR_CASH_RECEIPT_HISTORY_ALLAR_CASH_RECEIPT_HISTORY_ALL
64AR_CASH_RECEIPTS_ALLAR_CASH_RECEIPTS_ALL
65AR_CCID_CORRECTIONS_ALLAR_CCID_CORRECTIONS_ALL
66AR_CHANGE_MATRIXAR_CHANGE_MATRIX
67AR_CM_SUM_TRX_DAYS_GTAR_CM_SUM_TRX_DAYS_GT
68AR_CMGT_AUTO_RECOMMENDSAR_CMGT_AUTO_RECOMMENDS
69AR_CMGT_AUTO_RULE_DTLSAR_CMGT_AUTO_RULE_DTLS
70AR_CMGT_AUTO_RULESAR_CMGT_AUTO_RULES
71AR_CMGT_BANK_REF_ACCTSAR_CMGT_BANK_REF_ACCTS
72AR_CMGT_BANK_REF_DATAAR_CMGT_BANK_REF_DATA
73AR_CMGT_CASE_FOLDERSAR_CMGT_CASE_FOLDERS
74AR_CMGT_CF_AGING_DTLSAR_CMGT_CF_AGING_DTLS
75AR_CMGT_CF_ANL_NOTESAR_CMGT_CF_ANL_NOTES
76AR_CMGT_CF_DNB_DTLSAR_CMGT_CF_DNB_DTLS
77AR_CMGT_CF_DTLSAR_CMGT_CF_DTLS
78AR_CMGT_CF_RECOMMENDSAR_CMGT_CF_RECOMMENDS
79AR_CMGT_CHECK_LIST_DTLSAR_CMGT_CHECK_LIST_DTLS
80AR_CMGT_CHECK_LISTSAR_CMGT_CHECK_LISTS
81AR_CMGT_COLLATERAL_DATAAR_CMGT_COLLATERAL_DATA
82AR_CMGT_CREDIT_REQUESTSAR_CMGT_CREDIT_REQUESTS
83AR_CMGT_CURR_USAGE_GTAR_CMGT_CURR_USAGE_GT
84AR_CMGT_DATA_POINTS_BAR_CMGT_DATA_POINTS_B
85AR_CMGT_DATA_POINTS_TLAR_CMGT_DATA_POINTS_TL
86AR_CMGT_DNB_ELEMENTS_BAR_CMGT_DNB_ELEMENTS_B
87AR_CMGT_DNB_ELEMENTS_TLAR_CMGT_DNB_ELEMENTS_TL
88AR_CMGT_DNB_MAPPINGSAR_CMGT_DNB_MAPPINGS
89AR_CMGT_FINANCIAL_DATAAR_CMGT_FINANCIAL_DATA
90AR_CMGT_GUARANTOR_DATAAR_CMGT_GUARANTOR_DATA
91AR_CMGT_OTHER_DATAAR_CMGT_OTHER_DATA
92AR_CMGT_SCORE_DTLSAR_CMGT_SCORE_DTLS
93AR_CMGT_SCORE_WEIGHTSAR_CMGT_SCORE_WEIGHTS
94AR_CMGT_SCORESAR_CMGT_SCORES
95AR_CMGT_SETUP_OPTIONSAR_CMGT_SETUP_OPTIONS
96AR_CMGT_TRADE_REF_DATAAR_CMGT_TRADE_REF_DATA
97AR_COLINDAR_COLIND
98AR_COLLECTION_INDICATORS_ALLAR_COLLECTION_INDICATORS_ALL
99AR_COLLECTORSAR_COLLECTORS
100AR_CONC_PROCESS_REQUESTSAR_CONC_PROCESS_REQUESTS
101AR_CONC_REQUEST_MESSAGESAR_CONC_REQUEST_MESSAGES
102AR_CONFIRMATION_ACTIONSAR_CONFIRMATION_ACTIONS
103AR_CONS_INV_ALLAR_CONS_INV_ALL
104AR_CONS_INV_TRX_ALLAR_CONS_INV_TRX_ALL
105AR_CONS_INV_TRX_LINES_ALLAR_CONS_INV_TRX_LINES_ALL
106AR_CORR_PAY_SCHED_ALLAR_CORR_PAY_SCHED_ALL
107AR_CORRESPONDENCES_ALLAR_CORRESPONDENCES_ALL
108AR_CREDIT_HISTORIESAR_CREDIT_HISTORIES
109AR_CREDIT_MEMO_AMOUNTSAR_CREDIT_MEMO_AMOUNTS
110AR_CUST_PROF_CLASS_AMOUNTSAR_CUST_PROF_CLASS_AMOUNTS
111AR_CUST_SEARCH_GT 
112AR_CUSTOMER_ALT_NAMESAR_CUSTOMER_ALT_NAMES
113AR_CUSTOMER_BALANCE_ITFAR_CUSTOMER_BALANCE_ITF
114AR_CUSTOMER_CALL_TOPICS_ALLAR_CUSTOMER_CALL_TOPICS_ALL
115AR_CUSTOMER_CALLS_ALLAR_CUSTOMER_CALLS_ALL
116AR_CUSTOMER_PROFILE_AMOUNTSAR_CUSTOMER_PROFILE_AMOUNTS
117AR_CUSTOMER_PROFILE_CLASSESAR_CUSTOMER_PROFILE_CLASSES
118AR_CUSTOMER_PROFILESAR_CUSTOMER_PROFILES
119AR_DEBUGAR_DEBUG
120AR_DISPUTE_HISTORYAR_DISPUTE_HISTORY
121AR_DISTRIBUTION_SET_LINES_ALLAR_DISTRIBUTION_SET_LINES_ALL
122AR_DISTRIBUTION_SETS_ALLAR_DISTRIBUTION_SETS_ALL
123AR_DISTRIBUTIONS_ALLAR_DISTRIBUTIONS_ALL
124AR_DOC_SEQUENCE_AUDITAR_DOC_SEQUENCE_AUDIT
125AR_DOCUMENT_TRANSFERSAR_DOCUMENT_TRANSFERS
126AR_DUNNING_LETTER_SET_LINESAR_DUNNING_LETTER_SET_LINES
127AR_DUNNING_LETTER_SETSAR_DUNNING_LETTER_SETS
128AR_DUNNING_LETTERS_BAR_DUNNING_LETTERS_B
129AR_DUNNING_LETTERS_CUSTOM_TLAR_DUNNING_LETTERS_CUSTOM_TL
130AR_DUNNING_LETTERS_TLAR_DUNNING_LETTERS_TL
131AR_INTERIM_CASH_RCPT_LINES_ALLAR_INTERIM_CASH_RCPT_LINES_ALL
132AR_INTERIM_CASH_RECEIPTS_ALLAR_INTERIM_CASH_RECEIPTS_ALL
133AR_INTERIM_POSTINGAR_INTERIM_POSTING
134AR_IREC_CUSTOM_CUST_GT 
135AR_IREC_CUSTOM_SRCH_GT 
136AR_IREC_PAYMENT_LIST_GT 
137AR_JOURNAL_INTERIM_ALLAR_JOURNAL_INTERIM_ALL
138AR_LOCATION_ACCOUNTS_ALLAR_LOCATION_ACCOUNTS_ALL
139AR_LOCATION_COMBINATIONS 
140AR_LOCATION_RATES 
141AR_LOCATION_VALUES 
142AR_LOCKBOXES_ALLAR_LOCKBOXES_ALL
143AR_MC_ADJUSTMENTSAR_MC_ADJUSTMENTS
144AR_MC_BATCHESAR_MC_BATCHES
145AR_MC_CASH_BASIS_DISTS_ALLAR_MC_CASH_BASIS_DISTS_ALL
146AR_MC_CASH_RECEIPT_HISTAR_MC_CASH_RECEIPT_HIST
147AR_MC_CASH_RECEIPTSAR_MC_CASH_RECEIPTS
148AR_MC_DISTRIBUTIONS_ALLAR_MC_DISTRIBUTIONS_ALL
149AR_MC_MISC_CASH_DISTSAR_MC_MISC_CASH_DISTS
150AR_MC_PAYMENT_SCHEDULESAR_MC_PAYMENT_SCHEDULES
151AR_MC_RATE_ADJUSTMENTSAR_MC_RATE_ADJUSTMENTS
152AR_MC_RECEIVABLE_APPSAR_MC_RECEIVABLE_APPS
153AR_MC_TRANSACTION_HISTORYAR_MC_TRANSACTION_HISTORY
154AR_MEMO_LINES_ALL_BAR_MEMO_LINES_ALL_B
155AR_MEMO_LINES_ALL_TLAR_MEMO_LINES_ALL_TL
156AR_MISC_CASH_DISTRIBUTIONS_ALLAR_MISC_CASH_DISTRIBUTIONS_ALL
157AR_MRC_CASH_HEADERAR_MRC_CASH_HEADER
158AR_MRC_CASH_LINESAR_MRC_CASH_LINES
159AR_MRC_INQ_TRANS_BALANCESAR_MRC_INQ_TRANS_BALANCES
160AR_NOTESAR_NOTES
161AR_PAYMENT_SCHEDULES_ALLAR_PAYMENT_SCHEDULES_ALL
162AR_PAYMENTS_INTERFACE_ALLAR_PAYMENTS_INTERFACE_ALL
163AR_PERIOD_TYPESAR_PERIOD_TYPES
164AR_PERIODSAR_PERIODS
165AR_POSTING_CONTROLAR_POSTING_CONTROL
166AR_POSTING_REPORT_INTERIMAR_POSTING_REPORT_INTERIM
167AR_PURGE_OE_EXCEPTIONSAR_PURGE_OE_EXCEPTIONS
168AR_PURGE_REC_AUXAR_PURGE_REC_AUX
169AR_PURGE_TRX_AUXAR_PURGE_TRX_AUX
170AR_RAMC_AUDIT_TRAILAR_RAMC_AUDIT_TRAIL
171AR_RATE_ADJUSTMENTS_ALLAR_RATE_ADJUSTMENTS_ALL
172AR_RECEIPT_CLASSESAR_RECEIPT_CLASSES
173AR_RECEIPT_METHOD_ACCOUNTS_ALLAR_RECEIPT_METHOD_ACCOUNTS_ALL
174AR_RECEIPT_METHODSAR_RECEIPT_METHODS
175AR_RECEIPTS_REP_ITFAR_RECEIPTS_REP_ITF
176AR_RECEIVABLE_APPLICATIONS_ALLAR_RECEIVABLE_APPLICATIONS_ALL
177AR_RECEIVABLES_TRX_ALLAR_RECEIVABLES_TRX_ALL
178AR_REV_REC_QTAR_REV_REC_QT
179AR_REVENUE_ADJUSTMENTS_ALLAR_REVENUE_ADJUSTMENTS_ALL
180AR_REVENUE_ASSIGNMENTS_GTAR_REVENUE_ASSIGNMENTS_GT
181AR_SALES_TAXAR_SALES_TAX
182AR_SALES_TAX_REP_ITFAR_SALES_TAX_REP_ITF
183AR_SELECTION_CRITERIAAR_SELECTION_CRITERIA
184AR_STANDARD_TEXT_BAR_STANDARD_TEXT_B
185AR_STANDARD_TEXT_TLAR_STANDARD_TEXT_TL
186AR_STATEMENT_CYCLE_DATES_ALLAR_STATEMENT_CYCLE_DATES_ALL
187AR_STATEMENT_CYCLE_INTERVALSAR_STATEMENT_CYCLE_INTERVALS
188AR_STATEMENT_CYCLESAR_STATEMENT_CYCLES
189AR_STATEMENT_FINCHRG_GTAR_STATEMENT_FINCHRG_GT
190AR_STATEMENT_HEADERSAR_STATEMENT_HEADERS
191AR_STATEMENT_LINE_CLUSTERSAR_STATEMENT_LINE_CLUSTERS
192AR_STATEMENTS_HISTORY_ALLAR_STATEMENTS_HISTORY_ALL
193AR_SUM_REF_EVENT_HISTAR_SUM_REF_EVENT_HIST
194AR_SYSTEM_PARAMETERS_ALLAR_SYSTEM_PARAMETERS_ALL
195AR_TA_ASGN_TO_INT_ALL 
196AR_TA_CASHAPP_OB_ALL 
197AR_TA_CR_AGEN_INF_ALL 
198AR_TA_CUST_HIER_CHILD 
199AR_TA_CUST_HIER_PARNT 
200AR_TA_CUST_INT_ALL 
201AR_TA_CUST_TRXSTR_ALL 
202AR_TA_DEDN_ASSGNS_ALL 
203AR_TA_DEDN_INT_ALL 
204AR_TA_DEDN_RELATE_ALL 
205AR_TA_LEGACY_CUST_INT 
206AR_TA_LEGACY_STAT_INT 
207AR_TA_PAYMNT_HIST_ALL 
208AR_TA_PROF_ASSGNT_ALL 
209AR_TA_PROM_CUST_ALL 
210AR_TA_PROM_CUST_MAP 
211AR_TA_PROM_LINES_INT 
212AR_TA_PROM_PAYMNT_ALL 
213AR_TA_PROM_PAYMNT_TYP 
214AR_TA_PROM_PRODS_ALL 
215AR_TA_PROM_STATUS_MAP 
216AR_TA_PROMOTIONS_ALL 
217AR_TA_PROMOTIONS_INT 
218AR_TA_RECON_INFO_ALL 
219AR_TA_RECV_TRXSET_ALL 
220AR_TA_REMIT_HIST_ALL 
221AR_TA_REMIT_PROF_ALL 
222AR_TA_RISK_COMENT_ALL 
223AR_TA_RULE_OUTPUT 
224AR_TA_RULE_SET_LN_ALL 
225AR_TA_RULE_SETS_ALL 
226AR_TA_RULES_ALL 
227AR_TA_TRX_SET_LN_ALL 
228AR_TA_TRX_SETS_ALL 
229AR_TA_TRX_TO_CREATE 
230AR_TA_TRX_TYP_INT_ALL 
231AR_TA_VERSIONS 
232AR_TAX_CODE_COMBINATION_ID_GTAR_TAX_CODE_COMBINATION_ID_GT
233AR_TAX_CONDITION_ACTIONS_ALLAR_TAX_CONDITION_ACTIONS_ALL
234AR_TAX_CONDITION_LINES_ALLAR_TAX_CONDITION_LINES_ALL
235AR_TAX_CONDITIONS_ALLAR_TAX_CONDITIONS_ALL
236AR_TAX_EXTR_SUB_AP_EXT 
237AR_TAX_EXTR_SUB_AR_EXT 
238AR_TAX_EXTR_SUB_COM_EXT 
239AR_TAX_EXTRACT_DCL_ITF 
240AR_TAX_EXTRACT_MATRIX_ITF 
241AR_TAX_EXTRACT_SUB_ITF 
242AR_TAX_GROUP_CODES_ALLAR_TAX_GROUP_CODES_ALL
243AR_TAX_INTERFACEAR_TAX_INTERFACE
244AR_TRANS_FIELD_FORMATSAR_TRANS_FIELD_FORMATS
245AR_TRANS_RECORD_FORMATSAR_TRANS_RECORD_FORMATS
246AR_TRANSACTION_HISTORY_ALLAR_TRANSACTION_HISTORY_ALL
247AR_TRANSACTIONS_REP_ITFAR_TRANSACTIONS_REP_ITF
248AR_TRANSMISSION_FORMATSAR_TRANSMISSION_FORMATS
249AR_TRANSMISSIONS_ALLAR_TRANSMISSIONS_ALL
250AR_TRX_BAL_SUMMARYAR_TRX_BAL_SUMMARY
251AR_TRX_DIST_GTAR_TRX_DIST_GT
252AR_TRX_ERRORS_GTAR_TRX_ERRORS_GT
253AR_TRX_HEADER_GTAR_TRX_HEADER_GT
254AR_TRX_LINES_GTAR_TRX_LINES_GT
255AR_TRX_SALESCREDITS_GTAR_TRX_SALESCREDITS_GT
256AR_TRX_SUMMARYAR_TRX_SUMMARY
257AR_TRX_SUMMARY_HISTAR_TRX_SUMMARY_HIST
258AR_VAT_TAX_ALL_BAR_VAT_TAX_ALL_B
259AR_VAT_TAX_ALL_TLAR_VAT_TAX_ALL_TL
260DR$HZ_CLASS_CODE_DENORM_T1$IDR$HZ_CLASS_CODE_DENORM_T1$I
261DR$HZ_CLASS_CODE_DENORM_T1$KDR$HZ_CLASS_CODE_DENORM_T1$K
262DR$HZ_CLASS_CODE_DENORM_T1$NDR$HZ_CLASS_CODE_DENORM_T1$N
263DR$HZ_CLASS_CODE_DENORM_T1$RDR$HZ_CLASS_CODE_DENORM_T1$R
264HZ_ADAPTER_LOGSHZ_ADAPTER_LOGS
265HZ_ADAPTER_TERRITORIESHZ_ADAPTER_TERRITORIES
266HZ_ADAPTERSHZ_ADAPTERS
267HZ_APPLICATION_TRANS_GTHZ_APPLICATION_TRANS_GT
268HZ_BANK_VAL_GTHZ_BANK_VAL_GT
269HZ_BILLING_PREFERENCESHZ_BILLING_PREFERENCES
270HZ_CERTIFICATIONSHZ_CERTIFICATIONS
271HZ_CITIZENSHIPHZ_CITIZENSHIP
272HZ_CLASS_CATEGORIESHZ_CLASS_CATEGORIES
273HZ_CLASS_CATEGORY_USESHZ_CLASS_CATEGORY_USES
274HZ_CLASS_CODE_DENORMHZ_CLASS_CODE_DENORM
275HZ_CLASS_CODE_RELATIONSHZ_CLASS_CODE_RELATIONS
276HZ_CODE_ASSIGNMENTSHZ_CODE_ASSIGNMENTS
277HZ_CONTACT_POINT_VAL_GTHZ_CONTACT_POINT_VAL_GT
278HZ_CONTACT_POINTSHZ_CONTACT_POINTS
279HZ_CONTACT_PREFERENCESHZ_CONTACT_PREFERENCES
280HZ_CONTACT_RESTRICTIONSHZ_CONTACT_RESTRICTIONS
281HZ_CREDIT_PROFILE_AMTSHZ_CREDIT_PROFILE_AMTS
282HZ_CREDIT_PROFILESHZ_CREDIT_PROFILES
283HZ_CREDIT_RATINGSHZ_CREDIT_RATINGS
284HZ_CREDIT_USAGE_RULE_SETS_BHZ_CREDIT_USAGE_RULE_SETS_B
285HZ_CREDIT_USAGE_RULE_SETS_TLHZ_CREDIT_USAGE_RULE_SETS_TL
286HZ_CREDIT_USAGE_RULESHZ_CREDIT_USAGE_RULES
287HZ_CREDIT_USAGESHZ_CREDIT_USAGES
288HZ_CUST_ACCOUNT_ROLESHZ_CUST_ACCOUNT_ROLES
289HZ_CUST_ACCOUNT_ROLES_MHZ_CUST_ACCOUNT_ROLES_M
290HZ_CUST_ACCOUNTSHZ_CUST_ACCOUNTS
291HZ_CUST_ACCOUNTS_MHZ_CUST_ACCOUNTS_M
292HZ_CUST_ACCT_RELATE_ALLHZ_CUST_ACCT_RELATE_ALL
293HZ_CUST_ACCT_RELATE_ALL_MHZ_CUST_ACCT_RELATE_ALL_M
294HZ_CUST_ACCT_SITES_ALLHZ_CUST_ACCT_SITES_ALL
295HZ_CUST_ACCT_SITES_ALL_MHZ_CUST_ACCT_SITES_ALL_M
296HZ_CUST_CONTACT_POINTSHZ_CUST_CONTACT_POINTS
297HZ_CUST_MERGE_LOG_DICTHZ_CUST_MERGE_LOG_DICT
298HZ_CUST_PROF_CLASS_AMTSHZ_CUST_PROF_CLASS_AMTS
299HZ_CUST_PROFILE_AMTSHZ_CUST_PROFILE_AMTS
300HZ_CUST_PROFILE_AMTS_MHZ_CUST_PROFILE_AMTS_M
301HZ_CUST_PROFILE_CLASSESHZ_CUST_PROFILE_CLASSES
302HZ_CUST_SITE_USES_ALLHZ_CUST_SITE_USES_ALL
303HZ_CUST_SITE_USES_ALL_MHZ_CUST_SITE_USES_ALL_M
304HZ_CUSTOMER_MERGE_LOGHZ_CUSTOMER_MERGE_LOG
305HZ_CUSTOMER_PROFILESHZ_CUSTOMER_PROFILES
306HZ_CUSTOMER_PROFILES_MHZ_CUSTOMER_PROFILES_M
307HZ_DNB_REQUEST_LOGHZ_DNB_REQUEST_LOG
308HZ_DQM_DETAILS_GTHZ_DQM_DETAILS_GT
309HZ_DQM_PARTIES_GTHZ_DQM_PARTIES_GT
310HZ_DQM_STAGE_GTHZ_DQM_STAGE_GT
311HZ_DQM_STAGE_LOGHZ_DQM_STAGE_LOG
312HZ_DQM_SYNC_GTHZ_DQM_SYNC_GT
313HZ_DQM_SYNC_INTERFACEHZ_DQM_SYNC_INTERFACE
314HZ_DSS_ASSIGNMENTSHZ_DSS_ASSIGNMENTS
315HZ_DSS_CRITERIAHZ_DSS_CRITERIA
316HZ_DSS_ENTITIESHZ_DSS_ENTITIES
317HZ_DSS_GROUPS_BHZ_DSS_GROUPS_B
318HZ_DSS_GROUPS_TLHZ_DSS_GROUPS_TL
319HZ_DSS_SCHEME_FUNCTIONSHZ_DSS_SCHEME_FUNCTIONS
320HZ_DSS_SECURED_ENTITIESHZ_DSS_SECURED_ENTITIES
321HZ_DUP_BATCHHZ_DUP_BATCH
322HZ_DUP_EXCLUSIONSHZ_DUP_EXCLUSIONS
323HZ_DUP_MATCH_DETAILSHZ_DUP_MATCH_DETAILS
324HZ_DUP_MERGE_PARTIESHZ_DUP_MERGE_PARTIES
325HZ_DUP_RESULTSHZ_DUP_RESULTS
326HZ_DUP_SET_PARTIESHZ_DUP_SET_PARTIES
327HZ_DUP_SETSHZ_DUP_SETS
328HZ_DUP_WORKER_CHUNK_GTHZ_DUP_WORKER_CHUNK_GT
329HZ_EDUCATIONHZ_EDUCATION
330HZ_EMAIL_DOMAINSHZ_EMAIL_DOMAINS
331HZ_EMPLOYMENT_HISTORYHZ_EMPLOYMENT_HISTORY
332HZ_ENTITY_ATTRIBUTESHZ_ENTITY_ATTRIBUTES
333HZ_EXT_DATA_RULES_TLHZ_EXT_DATA_RULES_TL
334HZ_FINANCIAL_NUMBERSHZ_FINANCIAL_NUMBERS
335HZ_FINANCIAL_PROFILEHZ_FINANCIAL_PROFILE
336HZ_FINANCIAL_REPORTSHZ_FINANCIAL_REPORTS
337HZ_GEO_NAME_REFERENCE_LOGHZ_GEO_NAME_REFERENCE_LOG
338HZ_GEO_NAME_REFERENCESHZ_GEO_NAME_REFERENCES
339HZ_GEO_STRUCT_MAPHZ_GEO_STRUCT_MAP
340HZ_GEO_STRUCT_MAP_DTLHZ_GEO_STRUCT_MAP_DTL
341HZ_GEO_STRUCTURE_LEVELSHZ_GEO_STRUCTURE_LEVELS
342HZ_GEOGRAPHIESHZ_GEOGRAPHIES
343HZ_GEOGRAPHY_IDENTIFIERSHZ_GEOGRAPHY_IDENTIFIERS
344HZ_GEOGRAPHY_RANGESHZ_GEOGRAPHY_RANGES
345HZ_GEOGRAPHY_TYPES_BHZ_GEOGRAPHY_TYPES_B
346HZ_GEOGRAPHY_TYPES_TLHZ_GEOGRAPHY_TYPES_TL
347HZ_GROUP_VAL_GTHZ_GROUP_VAL_GT
348HZ_HIERARCHY_NODESHZ_HIERARCHY_NODES
349HZ_IMP_ADAPTERSHZ_IMP_ADAPTERS
350HZ_IMP_ADDRESSES_INTHZ_IMP_ADDRESSES_INT
351HZ_IMP_ADDRESSES_SGHZ_IMP_ADDRESSES_SG
352HZ_IMP_ADDRESSUSES_INTHZ_IMP_ADDRESSUSES_INT
353HZ_IMP_ADDRESSUSES_SGHZ_IMP_ADDRESSUSES_SG
354HZ_IMP_BATCH_DETAILSHZ_IMP_BATCH_DETAILS
355HZ_IMP_BATCH_SUMMARYHZ_IMP_BATCH_SUMMARY
356HZ_IMP_CLASSIFICS_INTHZ_IMP_CLASSIFICS_INT
357HZ_IMP_CLASSIFICS_SGHZ_IMP_CLASSIFICS_SG
358HZ_IMP_CONTACTPTS_INTHZ_IMP_CONTACTPTS_INT
359HZ_IMP_CONTACTPTS_SGHZ_IMP_CONTACTPTS_SG
360HZ_IMP_CONTACTROLES_INTHZ_IMP_CONTACTROLES_INT
361HZ_IMP_CONTACTROLES_SGHZ_IMP_CONTACTROLES_SG
362HZ_IMP_CONTACTS_INTHZ_IMP_CONTACTS_INT
363HZ_IMP_CONTACTS_SGHZ_IMP_CONTACTS_SG
364HZ_IMP_CREDITRTNGS_INTHZ_IMP_CREDITRTNGS_INT
365HZ_IMP_CREDITRTNGS_SGHZ_IMP_CREDITRTNGS_SG
366HZ_IMP_DUP_DETAILSHZ_IMP_DUP_DETAILS
367HZ_IMP_DUP_PARTIESHZ_IMP_DUP_PARTIES
368HZ_IMP_ERRORSHZ_IMP_ERRORS
369HZ_IMP_FINNUMBERS_INTHZ_IMP_FINNUMBERS_INT
370HZ_IMP_FINNUMBERS_SGHZ_IMP_FINNUMBERS_SG
371HZ_IMP_FINREPORTS_INTHZ_IMP_FINREPORTS_INT
372HZ_IMP_FINREPORTS_SGHZ_IMP_FINREPORTS_SG
373HZ_IMP_INT_DEDUP_RESULTSHZ_IMP_INT_DEDUP_RESULTS
374HZ_IMP_OSR_CHANGEHZ_IMP_OSR_CHANGE
375HZ_IMP_PARTIES_INTHZ_IMP_PARTIES_INT
376HZ_IMP_PARTIES_SGHZ_IMP_PARTIES_SG
377HZ_IMP_RELSHIPS_INTHZ_IMP_RELSHIPS_INT
378HZ_IMP_RELSHIPS_SGHZ_IMP_RELSHIPS_SG
379HZ_IMP_TMP_ERRORSHZ_IMP_TMP_ERRORS
380HZ_IMP_TMP_REL_END_DATEHZ_IMP_TMP_REL_END_DATE
381HZ_IMP_WORK_UNITSHZ_IMP_WORK_UNITS
382HZ_INDUSTRIAL_CLASS_APPHZ_INDUSTRIAL_CLASS_APP
383HZ_INDUSTRIAL_CLASSESHZ_INDUSTRIAL_CLASSES
384HZ_INDUSTRIAL_REFERENCEHZ_INDUSTRIAL_REFERENCE
385HZ_INT_DUP_RESULTSHZ_INT_DUP_RESULTS
386HZ_INT_DUP_RESULTS_GTHZ_INT_DUP_RESULTS_GT
387HZ_LOC_ASSIGNMENTS 
388HZ_LOCATION_PROFILESHZ_LOCATION_PROFILES
389HZ_LOCATION_VAL_GTHZ_LOCATION_VAL_GT
390HZ_LOCATIONSHZ_LOCATIONS
391HZ_LOGHZ_LOG
392HZ_LOG2HZ_LOG2
393HZ_MATCH_RULE_PRIMARYHZ_MATCH_RULE_PRIMARY
394HZ_MATCH_RULE_SECONDARYHZ_MATCH_RULE_SECONDARY
395HZ_MATCH_RULES_BHZ_MATCH_RULES_B
396HZ_MATCH_RULES_TLHZ_MATCH_RULES_TL
397HZ_MATCHED_CONTACTS_GTHZ_MATCHED_CONTACTS_GT
398HZ_MATCHED_CPTS_GTHZ_MATCHED_CPTS_GT
399HZ_MATCHED_PARTIES_GTHZ_MATCHED_PARTIES_GT
400HZ_MATCHED_PARTY_SITES_GTHZ_MATCHED_PARTY_SITES_GT
401HZ_MERGE_BATCHHZ_MERGE_BATCH
402HZ_MERGE_DICTIONARYHZ_MERGE_DICTIONARY
403HZ_MERGE_ENTITY_ATTRIBUTESHZ_MERGE_ENTITY_ATTRIBUTES
404HZ_MERGE_PARTIESHZ_MERGE_PARTIES
405HZ_MERGE_PARTIES_SUGGHZ_MERGE_PARTIES_SUGG
406HZ_MERGE_PARTY_DETAILSHZ_MERGE_PARTY_DETAILS
407HZ_MERGE_PARTY_HISTORYHZ_MERGE_PARTY_HISTORY
408HZ_MERGE_PARTY_LOGHZ_MERGE_PARTY_LOG
409HZ_MERGE_PARTYDTLS_SUGGHZ_MERGE_PARTYDTLS_SUGG
410HZ_MOBILE_PREFIXESHZ_MOBILE_PREFIXES
411HZ_ORG_CONTACT_ROLESHZ_ORG_CONTACT_ROLES
412HZ_ORG_CONTACT_VAL_GTHZ_ORG_CONTACT_VAL_GT
413HZ_ORG_CONTACTSHZ_ORG_CONTACTS
414HZ_ORG_PROFILE_VAL_GTHZ_ORG_PROFILE_VAL_GT
415HZ_ORGANIZATION_INDICATORSHZ_ORGANIZATION_INDICATORS
416HZ_ORGANIZATION_PROFILESHZ_ORGANIZATION_PROFILES
417HZ_ORIG_SYS_MAPPINGHZ_ORIG_SYS_MAPPING
418HZ_ORIG_SYS_REFERENCESHZ_ORIG_SYS_REFERENCES
419HZ_PARAM_TABHZ_PARAM_TAB
420HZ_PARTIESHZ_PARTIES
421HZ_PARTY_INTERFACEHZ_PARTY_INTERFACE
422HZ_PARTY_INTERFACE_ERRORSHZ_PARTY_INTERFACE_ERRORS
423HZ_PARTY_PREFERENCESHZ_PARTY_PREFERENCES
424HZ_PARTY_RELATIONSHIPSHZ_PARTY_RELATIONSHIPS
425HZ_PARTY_SCORE_DTLS_GTHZ_PARTY_SCORE_DTLS_GT
426HZ_PARTY_SITE_USESHZ_PARTY_SITE_USES
427HZ_PARTY_SITE_VAL_GTHZ_PARTY_SITE_VAL_GT
428HZ_PARTY_SITESHZ_PARTY_SITES
429HZ_PARTY_VAL_GTHZ_PARTY_VAL_GT
430HZ_PERSON_INTERESTHZ_PERSON_INTEREST
431HZ_PERSON_LANGUAGEHZ_PERSON_LANGUAGE
432HZ_PERSON_PROFILESHZ_PERSON_PROFILES
433HZ_PHONE_AREA_CODESHZ_PHONE_AREA_CODES
434HZ_PHONE_COUNTRY_CODESHZ_PHONE_COUNTRY_CODES
435HZ_PHONE_FORMATSHZ_PHONE_FORMATS
436HZ_PRIMARY_TRANSHZ_PRIMARY_TRANS
437HZ_PURGE_BATCHESHZ_PURGE_BATCHES
438HZ_PURGE_CANDIDATESHZ_PURGE_CANDIDATES
439HZ_PURGE_GTHZ_PURGE_GT
440HZ_REFERENCESHZ_REFERENCES
441HZ_REG_VERIFICATIONS 
442HZ_REGISTRATIONS 
443HZ_RELATIONSHIP_TYPESHZ_RELATIONSHIP_TYPES
444HZ_RELATIONSHIP_VAL_GTHZ_RELATIONSHIP_VAL_GT
445HZ_RELATIONSHIPSHZ_RELATIONSHIPS
446HZ_ROLE_RESPONSIBILITYHZ_ROLE_RESPONSIBILITY
447HZ_SECONDARY_TRANSHZ_SECONDARY_TRANS
448HZ_SECURITY_ISSUEDHZ_SECURITY_ISSUED
449HZ_SELECT_DATA_SOURCESHZ_SELECT_DATA_SOURCES
450HZ_SRCH_CONTACTSHZ_SRCH_CONTACTS
451HZ_SRCH_CPTSHZ_SRCH_CPTS
452HZ_SRCH_PARTIESHZ_SRCH_PARTIES
453HZ_SRCH_PSITESHZ_SRCH_PSITES
454HZ_STAGED_CONTACT_POINTSHZ_STAGED_CONTACT_POINTS
455HZ_STAGED_CONTACTSHZ_STAGED_CONTACTS
456HZ_STAGED_PARTIESHZ_STAGED_PARTIES
457HZ_STAGED_PARTY_SITESHZ_STAGED_PARTY_SITES
458HZ_STOCK_MARKETSHZ_STOCK_MARKETS
459HZ_STYLE_FMT_LAYOUTS_BHZ_STYLE_FMT_LAYOUTS_B
460HZ_STYLE_FMT_LAYOUTS_TLHZ_STYLE_FMT_LAYOUTS_TL
461HZ_STYLE_FMT_LOCALESHZ_STYLE_FMT_LOCALES
462HZ_STYLE_FMT_VARIATIONSHZ_STYLE_FMT_VARIATIONS
463HZ_STYLE_FORMATS_BHZ_STYLE_FORMATS_B
464HZ_STYLE_FORMATS_TLHZ_STYLE_FORMATS_TL
465HZ_STYLES_BHZ_STYLES_B
466HZ_STYLES_TLHZ_STYLES_TL
467HZ_SUSPENSION_ACTIVITYHZ_SUSPENSION_ACTIVITY
468HZ_THIRDPARTY_EXCEPSHZ_THIRDPARTY_EXCEPS
469HZ_THIRDPARTY_RULEHZ_THIRDPARTY_RULE
470HZ_TIMEZONE_MAPPINGHZ_TIMEZONE_MAPPING
471HZ_TIMEZONESHZ_TIMEZONES
472HZ_TIMEZONES_TLHZ_TIMEZONES_TL
473HZ_TRANS_ATTRIBUTES_BHZ_TRANS_ATTRIBUTES_B
474HZ_TRANS_ATTRIBUTES_TLHZ_TRANS_ATTRIBUTES_TL
475HZ_TRANS_FUNCTIONS_BHZ_TRANS_FUNCTIONS_B
476HZ_TRANS_FUNCTIONS_TLHZ_TRANS_FUNCTIONS_TL
477HZ_USER_CREATE_RULESHZ_USER_CREATE_RULES
478HZ_USER_ORG_GTHZ_USER_ORG_GT
479HZ_USER_OVERWRITE_RULESHZ_USER_OVERWRITE_RULES
480HZ_WIN_SOURCE_EXCEPSHZ_WIN_SOURCE_EXCEPS
481HZ_WORD_LISTSHZ_WORD_LISTS
482HZ_WORD_REPLACEMENTSHZ_WORD_REPLACEMENTS
483HZ_WORK_CLASSHZ_WORK_CLASS
484JE_DE_AR_BATCHESJE_DE_AR_BATCHES
485JE_DE_REMITTANCE_RESULTSJE_DE_REMITTANCE_RESULTS
486JG_ZZ_AR_BALANCESJG_ZZ_AR_BALANCES
487JG_ZZ_AR_TMP_ACCOUNTJG_ZZ_AR_TMP_ACCOUNT
488JG_ZZ_AR_TMP_BALJG_ZZ_AR_TMP_BAL
489JG_ZZ_AR_TMP_DETAILJG_ZZ_AR_TMP_DETAIL
490JG_ZZ_II_INT_RATES_ALLJG_ZZ_II_INT_RATES_ALL
491JG_ZZ_INT_INV_LINES_ALLJG_ZZ_INT_INV_LINES_ALL
492JG_ZZ_INTEREST_BATCHES_ALLJG_ZZ_INTEREST_BATCHES_ALL
493JG_ZZ_INTEREST_INVOICES_ALLJG_ZZ_INTEREST_INVOICES_ALL
494JG_ZZ_JGZZCSLP_MESSAGESJG_ZZ_JGZZCSLP_MESSAGES
495OCM_CREDIT_REVIEW_GTOCM_CREDIT_REVIEW_GT
496RA_ACCOUNT_COMBINATIONSRA_ACCOUNT_COMBINATIONS
497RA_ACCOUNT_DEFAULT_SEGMENTSRA_ACCOUNT_DEFAULT_SEGMENTS
498RA_ACCOUNT_DEFAULTS_ALLRA_ACCOUNT_DEFAULTS_ALL
499RA_ADDRESSES_ALLRA_ADDRESSES_ALL
500RA_BATCH_SOURCES_ALLRA_BATCH_SOURCES_ALL
501RA_BATCHES_ALLRA_BATCHES_ALL
502RA_CM_REQUEST_LINES_ALLRA_CM_REQUEST_LINES_ALL
503RA_CM_REQUESTS_ALLRA_CM_REQUESTS_ALL
504RA_CONTACT_PHONES_INT_ALLRA_CONTACT_PHONES_INT_ALL
505RA_CONTACT_ROLESRA_CONTACT_ROLES
506RA_CONTACTSRA_CONTACTS
507RA_CUST_PAY_METHOD_INT_ALLRA_CUST_PAY_METHOD_INT_ALL
508RA_CUST_RECEIPT_METHODSRA_CUST_RECEIPT_METHODS
509RA_CUST_TRX_LINE_GL_DIST_ALLRA_CUST_TRX_LINE_GL_DIST_ALL
510RA_CUST_TRX_LINE_SALESREPS_ALLRA_CUST_TRX_LINE_SALESREPS_ALL
511RA_CUST_TRX_TYPES_ALLRA_CUST_TRX_TYPES_ALL
512RA_CUSTOMER_BANKS_INT_ALLRA_CUSTOMER_BANKS_INT_ALL
513RA_CUSTOMER_MERGE_HEADERSRA_CUSTOMER_MERGE_HEADERS
514RA_CUSTOMER_MERGESRA_CUSTOMER_MERGES
515RA_CUSTOMER_PROFILES_INT_ALLRA_CUSTOMER_PROFILES_INT_ALL
516RA_CUSTOMER_RELATIONSHIPS_ALLRA_CUSTOMER_RELATIONSHIPS_ALL
517RA_CUSTOMER_TRX_ALLRA_CUSTOMER_TRX_ALL
518RA_CUSTOMER_TRX_LINES_ALLRA_CUSTOMER_TRX_LINES_ALL
519RA_CUSTOMERSRA_CUSTOMERS
520RA_CUSTOMERS_INTERFACE_ALLRA_CUSTOMERS_INTERFACE_ALL
521RA_GROUP_BY_COLUMNSRA_GROUP_BY_COLUMNS
522RA_GROUP_BYSRA_GROUP_BYS
523RA_GROUPING_RULESRA_GROUPING_RULES
524RA_GROUPING_TRX_TYPESRA_GROUPING_TRX_TYPES
525RA_INTERFACE_DISTRIBUTIONS_ALLRA_INTERFACE_DISTRIBUTIONS_ALL
526RA_INTERFACE_ERRORS_ALLRA_INTERFACE_ERRORS_ALL
527RA_INTERFACE_LINES_ALLRA_INTERFACE_LINES_ALL
528RA_INTERFACE_SALESCREDITS_ALLRA_INTERFACE_SALESCREDITS_ALL
529RA_ITEM_EXCEPTION_RATESRA_ITEM_EXCEPTION_RATES
530RA_LINE_ORDER_BY_COLUMNSRA_LINE_ORDER_BY_COLUMNS
531RA_LINE_ORDER_BYSRA_LINE_ORDER_BYS
532RA_LINE_ORDERING_RULESRA_LINE_ORDERING_RULES
533RA_MC_BATCHESRA_MC_BATCHES
534RA_MC_CUSTOMER_TRXRA_MC_CUSTOMER_TRX
535RA_MC_CUSTOMER_TRX_LINESRA_MC_CUSTOMER_TRX_LINES
536RA_MC_TRX_LINE_GL_DISTRA_MC_TRX_LINE_GL_DIST
537RA_PHONESRA_PHONES
538RA_RECUR_INTERIMRA_RECUR_INTERIM
539RA_REMIT_TOS_ALLRA_REMIT_TOS_ALL
540RA_RULE_SCHEDULESRA_RULE_SCHEDULES
541RA_RULESRA_RULES
542RA_SALESREP_TERRITORIESRA_SALESREP_TERRITORIES
543RA_SALESREPS_ALL_OLDRA_SALESREPS_ALL_OLD
544RA_SITE_USES_ALLRA_SITE_USES_ALL
545RA_TAX_EXEMPTIONS_ALLRA_TAX_EXEMPTIONS_ALL
546RA_TERMS_BRA_TERMS_B
547RA_TERMS_LINESRA_TERMS_LINES
548RA_TERMS_LINES_DISCOUNTSRA_TERMS_LINES_DISCOUNTS
549RA_TERMS_TLRA_TERMS_TL
550RA_TERRITORIESRA_TERRITORIES
551SYS_IOT_OVER_375198SYS_IOT_OVER_375198
552 AR_ACTIVITY_DETAILS
553 AR_BASE_GL_ACCT_BALANCES
554 AR_CC_ERROR_HISTORY
555 AR_CC_ERROR_MAPPINGS
556 AR_CCID_BY_GL_ACCOUNTS
557 AR_CHARGE_SCHEDULE_HDRS
558 AR_CHARGE_SCHEDULE_LINES
559 AR_CHARGE_SCHEDULES
560 AR_CLOSED_GL_PERIODS
561 AR_COGS_REV_ITF
562 AR_CONS_BILL_CYCLE_DATES
563 AR_CONS_BILL_CYCLES_B
564 AR_CONS_BILL_CYCLES_TL
565 AR_CONT_ACTIONS_ALL
566 AR_CRH_APP_GT
567 AR_CRH_GT
568 AR_CUST_SEARCH_GT_ALL
569 AR_DEFERRAL_REASONS
570 AR_DEFERRED_LINES_ALL
571 AR_DETECT_GT
572 AR_GL_ACCT_BALANCES
573 AR_GL_RECON_GT
574 AR_INTEREST_BATCHES_ALL
575 AR_INTEREST_HEADERS_ALL
576 AR_INTEREST_LINES_ALL
577 AR_INTERFACE_CONTS_ALL
578 AR_INV_API_DIST_GT
579 AR_INV_API_HEADERS_GT
580 AR_INV_API_LINES_GT
581 AR_IREC_APPLY_CREDIT_GT
582 AR_IREC_CSTM_CUST_GT_ALL
583 AR_IREC_CSTM_SRCH_GT_ALL
584 AR_IREC_PAYMENT_GT_ALL
585 AR_IREC_PRINT_REQUESTS
586 AR_IREC_SELFREG_CUST_QS
587 AR_IREC_SELFREG_SITE_QS
588 AR_LATE_CHARGE_CREDITS_GT
589 AR_LATE_CHARGE_CUST_BALANCE_GT
590 AR_LATE_CHARGE_DOC_GT
591 AR_LATE_CHARGE_TRX_T
592 AR_LC_CUST_SITES_T
593 AR_LINE_APP_DETAIL_GT
594 AR_LINE_CONTS_ALL
595 AR_LINE_DIST_INTERFACE_GT
596 AR_LINE_REV_ADJ_GT
597 AR_LLCA_TRX_ERRORS_GT
598 AR_LLCA_TRX_LINES_GT
599 AR_LOC_COMBINATIONS_OLD
600 AR_LOCATION_RATES_OLD
601 AR_LOCATION_VALUES_OLD
602 AR_RDR_PARAMETERS_GT
603 AR_REC_TRX_LE_DETAILS_ALL
604 AR_RECEIPTS_GT
605 AR_RECEIVABLE_APPS_GT
606 AR_REMIT_GT
607 AR_REVIEWED_LINES_GT
608 AR_SUBMISSION_CTRL_GT
609 AR_TRX_COGS_GT
610 AR_TRX_CONTINGENCIES_GT
611 AR_TRX_DIST_TMP_GT
612 AR_TRX_HEADER_TMP_GT
613 AR_TRX_LINES_TMP_GT
614 AR_TRX_SALESCREDITS_TMP_GT
615 AR_UPG_120_CONTROL
616 AR_XLA_HEADERS_EXTRACT
617 AR_XLA_LINES_EXTRACT
618 ARI_REG_VERIFICATIONS_GT
619 HZ_ADAPTER_USERS
620 HZ_ADDRESS_USAGE_DTLS
621 HZ_ADDRESS_USAGES
622 HZ_BES_GT
623 HZ_BUS_OBJ_DEFINITIONS
624 HZ_BUS_OBJ_TRACKING
625 HZ_CREDIT_RATINGS_EXT_B
626 HZ_CREDIT_RATINGS_EXT_TL
627 HZ_DL_SELECTED_CRITERIA
628 HZ_DQM_SETUP_DIAGNOSTICS
629 HZ_DQM_SH_SYNC_INTERFACE
630 HZ_FIN_NUMBERS_EXT_B
631 HZ_FIN_NUMBERS_EXT_TL
632 HZ_FIN_REPORTS_EXT_B
633 HZ_FIN_REPORTS_EXT_TL
634 HZ_JMS_OUT
635 HZ_LOC_ASSIGNMENTS_OBS
636 HZ_LOCATIONS_EXT_B
637 HZ_LOCATIONS_EXT_TL
638 HZ_MATCH_RULE_CONDITIONS
639 HZ_NON_PURGE_CANDIDATES
640 HZ_ORG_PROFILES_EXT_B
641 HZ_ORG_PROFILES_EXT_SG
642 HZ_ORG_PROFILES_EXT_TL
643 HZ_ORIG_SYSTEMS_B
644 HZ_ORIG_SYSTEMS_TL
645 HZ_PARTY_SITES_EXT_B
646 HZ_PARTY_SITES_EXT_TL
647 HZ_PARTY_USAGE_RULES
648 HZ_PARTY_USAGES_B
649 HZ_PARTY_USAGES_TL
650 HZ_PARTY_USG_ASSIGNMENTS
651 HZ_PER_PROFILES_EXT_B
652 HZ_PER_PROFILES_EXT_SG
653 HZ_PER_PROFILES_EXT_TL
654 HZ_SHADOW_ST_CONTACTS
655 HZ_SHADOW_ST_CPTS
656 HZ_SHADOW_ST_PARTIES
657 HZ_SHADOW_ST_PSITES
658 HZ_TEMP_REL_GT
659 HZ_THIN_ST_CONTACTS
660 HZ_THIN_ST_CPTS
661 HZ_THIN_ST_PARTIES
662 HZ_THIN_ST_PSITES
663 HZ_TRANSFORMATIONS_B
664 HZ_TRANSFORMATIONS_TL
665 HZ_WORD_RPL_COND_ATTRIBS
666 HZ_WORD_RPL_CONDS_B
667 HZ_WORD_RPL_CONDS_TL
668 RA_AR_GT
669 RA_CUSTOMER_TRX_LINES_G

Oracle Fixed Assets 11i and R12 Tables


Oracle Fixed Assets 11i and R12 Tables
FIXED ASSTETS
Un Changed = 179
New Tables = 19
Deleted = 0




11i TABLES
R12 TABLES
1
FA_ACE_BOOKS
FA_ACE_BOOKS
2
FA_ADD_WARRANTIES
FA_ADD_WARRANTIES
3
FA_ADDITION_REP_ITF
FA_ADDITION_REP_ITF
4
FA_ADDITIONS_B
FA_ADDITIONS_B
5
FA_ADDITIONS_TL
FA_ADDITIONS_TL
6
FA_ADJUST_REP_ITF
FA_ADJUST_REP_ITF
7
FA_ADJUSTMENTS
FA_ADJUSTMENTS
8
FA_AMORT_SCHEDULES
FA_AMORT_SCHEDULES
9
FA_ARCHIVE_HISTORY
FA_ARCHIVE_HISTORY
10
FA_ASSET_HIERARCHY
FA_ASSET_HIERARCHY
11
FA_ASSET_HIERARCHY_PURPOSE
FA_ASSET_HIERARCHY_PURPOSE
12
FA_ASSET_HIERARCHY_VALUES
FA_ASSET_HIERARCHY_VALUES
13
FA_ASSET_HISTORY
FA_ASSET_HISTORY
14
FA_ASSET_INVOICES
FA_ASSET_INVOICES
15
FA_ASSET_KEYWORDS
FA_ASSET_KEYWORDS
16
FA_ASSET_LISTING_REP_ITF
FA_ASSET_LISTING_REP_ITF
17
FA_BALANCES_REP_ITF
FA_BALANCES_REP_ITF
18
FA_BALANCES_REPORT
FA_BALANCES_REPORT
19
FA_BALANCES_REPORT_GT
FA_BALANCES_REPORT_GT
20
FA_BONUS_RATES
FA_BONUS_RATES
21
FA_BONUS_RULES
FA_BONUS_RULES
22
FA_BOOK_CONTROLS
FA_BOOK_CONTROLS
23
FA_BOOK_CONTROLS_HISTORY
FA_BOOK_CONTROLS_HISTORY
24
FA_BOOKS
FA_BOOKS
25
FA_BOOKS_GROUPS
FA_BOOKS_GROUPS
26
FA_BOOKS_SUMMARY
FA_BOOKS_SUMMARY
27
FA_BUDGET_DISTRIBUTION
FA_BUDGET_DISTRIBUTION
28
FA_BUDGET_INTERFACE
FA_BUDGET_INTERFACE
29
FA_CALENDAR_PERIODS
FA_CALENDAR_PERIODS
30
FA_CALENDAR_TYPES
FA_CALENDAR_TYPES
31
FA_CAP_REP_ITF
FA_CAP_REP_ITF
32
FA_CAPITAL_BUDGET
FA_CAPITAL_BUDGET
33
FA_CATEGORIES_B
FA_CATEGORIES_B
34
FA_CATEGORIES_TL
FA_CATEGORIES_TL
35
FA_CATEGORY_BOOK_DEFAULTS
FA_CATEGORY_BOOK_DEFAULTS
36
FA_CATEGORY_BOOKS
FA_CATEGORY_BOOKS
37
FA_CEILING_TYPES
FA_CEILING_TYPES
38
FA_CEILINGS
FA_CEILINGS
39
FA_CONVENTION_TYPES
FA_CONVENTION_TYPES
40
FA_CONVENTIONS
FA_CONVENTIONS
41
FA_COSTCLEAR_REP_ITF
FA_COSTCLEAR_REP_ITF
42
FA_DEFERRED_DEPRN
FA_DEFERRED_DEPRN
43
FA_DELETED_MASS_ADDITIONS
FA_DELETED_MASS_ADDITIONS
44
FA_DEPRN_BASIS_RULES
FA_DEPRN_BASIS_RULES
45
FA_DEPRN_DETAIL
FA_DEPRN_DETAIL
46
FA_DEPRN_OVERRIDE
FA_DEPRN_OVERRIDE
47
FA_DEPRN_PERIODS
FA_DEPRN_PERIODS
48
FA_DEPRN_REP_ITF
FA_DEPRN_REP_ITF
49
FA_DEPRN_RULE_DETAILS
FA_DEPRN_RULE_DETAILS
50
FA_DEPRN_SUMMARY
FA_DEPRN_SUMMARY
51
FA_DEPRN_TAX_REP_ITF
FA_DEPRN_TAX_REP_ITF
52
FA_DEPRN_TAX_REP_NBVS
FA_DEPRN_TAX_REP_NBVS
53
FA_DISTRIBUTION_ACCOUNTS
FA_DISTRIBUTION_ACCOUNTS
54
FA_DISTRIBUTION_DEFAULTS
FA_DISTRIBUTION_DEFAULTS
55
FA_DISTRIBUTION_HISTORY
FA_DISTRIBUTION_HISTORY
56
FA_DISTRIBUTION_SETS
FA_DISTRIBUTION_SETS
57
FA_EXCLUDE_HIERARCHY_LEVELS
FA_EXCLUDE_HIERARCHY_LEVELS
58
FA_EXT_INV_RETIREMENTS
FA_EXT_INV_RETIREMENTS
59
FA_FISCAL_YEAR
FA_FISCAL_YEAR
60
FA_FLAT_RATES
FA_FLAT_RATES
61
FA_FORMULAS
FA_FORMULAS
62
FA_GROUP_ASSET_DEFAULT
FA_GROUP_ASSET_DEFAULT
63
FA_GROUP_ASSET_RULES
FA_GROUP_ASSET_RULES
64
FA_GROUP_ASSETS
FA_GROUP_ASSETS
65
FA_GROUP_DEPRN_DETAIL
FA_GROUP_DEPRN_DETAIL
66
FA_GROUP_DEPRN_RATES
FA_GROUP_DEPRN_RATES
67
FA_GROUP_DEPRN_SUMMARY
FA_GROUP_DEPRN_SUMMARY
68
FA_GROUP_REP_ITF
FA_GROUP_REP_ITF
69
FA_HIERARCHY_CONTROLS
FA_HIERARCHY_CONTROLS
70
FA_HIERARCHY_DISTRIBUTIONS
FA_HIERARCHY_DISTRIBUTIONS
71
FA_HIERARCHY_RULE_DETAILS
FA_HIERARCHY_RULE_DETAILS
72
FA_HIERARCHY_RULE_SET
FA_HIERARCHY_RULE_SET
73
FA_HR_RETIREMENT_DETAILS
FA_HR_RETIREMENT_DETAILS
74
FA_HR_RETIREMENT_HEADERS
FA_HR_RETIREMENT_HEADERS
75
FA_INS_LINES
FA_INS_LINES
76
FA_INS_MST_POLS
FA_INS_MST_POLS
77
FA_INS_POLICIES
FA_INS_POLICIES
78
FA_INS_VALUES
FA_INS_VALUES
79
FA_INV_COMPARE_REP_ITF
FA_INV_COMPARE_REP_ITF
80
FA_INV_INTERFACE
FA_INV_INTERFACE
81
FA_INVENTORY
FA_INVENTORY
82
FA_INVMISS_REP_ITF
FA_INVMISS_REP_ITF
83
FA_INVOICE_TRANSACTIONS
FA_INVOICE_TRANSACTIONS
84
FA_ITC_RATES
FA_ITC_RATES
85
FA_ITC_RECAPTURE_RATES
FA_ITC_RECAPTURE_RATES
86
FA_JOURNAL_ENTRIES
FA_JOURNAL_ENTRIES
87
FA_LEASE_PAYMENT_ITEMS
FA_LEASE_PAYMENT_ITEMS
88
FA_LEASE_PAYMENTS
FA_LEASE_PAYMENTS
89
FA_LEASE_SCHEDULES
FA_LEASE_SCHEDULES
90
FA_LEASES
FA_LEASES
91
FA_LIFE_DERIVATION_INFO
FA_LIFE_DERIVATION_INFO
92
FA_LOCATIONS
FA_LOCATIONS
93
FA_LOOKUP_TYPES_B
FA_LOOKUP_TYPES_B
94
FA_LOOKUP_TYPES_TL
FA_LOOKUP_TYPES_TL
95
FA_LOOKUPS_B
FA_LOOKUPS_B
96
FA_LOOKUPS_TL
FA_LOOKUPS_TL
97
FA_MAINT_EVENTS
FA_MAINT_EVENTS
98
FA_MAINT_REP_ITF
FA_MAINT_REP_ITF
99
FA_MAINT_SCHEDULE_DTL
FA_MAINT_SCHEDULE_DTL
100
FA_MAINT_SCHEDULE_HDR
FA_MAINT_SCHEDULE_HDR
101
FA_MASS_ADDITIONS
FA_MASS_ADDITIONS
102
FA_MASS_CHANGES
FA_MASS_CHANGES
103
FA_MASS_CHANGES_ITF
FA_MASS_CHANGES_ITF
104
FA_MASS_EXT_RET_EXCEPTS
FA_MASS_EXT_RET_EXCEPTS
105
FA_MASS_EXT_RETIREMENTS
FA_MASS_EXT_RETIREMENTS
106
FA_MASS_EXTERNAL_TRANSFERS
FA_MASS_EXTERNAL_TRANSFERS
107
FA_MASS_RECLASS
FA_MASS_RECLASS
108
FA_MASS_RECLASS_ITF
FA_MASS_RECLASS_ITF
109
FA_MASS_RET_EXCEPTS
FA_MASS_RET_EXCEPTS
110
FA_MASS_RETIREMENTS
FA_MASS_RETIREMENTS
111
FA_MASS_REVAL_REP_ITF
FA_MASS_REVAL_REP_ITF
112
FA_MASS_REVALUATION_RULES
FA_MASS_REVALUATION_RULES
113
FA_MASS_REVALUATIONS
FA_MASS_REVALUATIONS
114
FA_MASS_TAX_ADJUSTMENTS
FA_MASS_TAX_ADJUSTMENTS
115
FA_MASS_TRANSFERS
FA_MASS_TRANSFERS
116
FA_MASS_UPDATE_BATCH_DETAILS
FA_MASS_UPDATE_BATCH_DETAILS
117
FA_MASS_UPDATE_BATCH_HEADERS
FA_MASS_UPDATE_BATCH_HEADERS
118
FA_MASSADD_DISTRIBUTIONS
FA_MASSADD_DISTRIBUTIONS
119
FA_MASSADD_REP_ITF
FA_MASSADD_REP_ITF
120
FA_MC_ADJUSTMENTS
FA_MC_ADJUSTMENTS
121
FA_MC_ASSET_INVOICES
FA_MC_ASSET_INVOICES
122
FA_MC_BOOK_CONTROLS
FA_MC_BOOK_CONTROLS
123
FA_MC_BOOKS
FA_MC_BOOKS
124
FA_MC_BOOKS_GROUPS
FA_MC_BOOKS_GROUPS
125
FA_MC_BOOKS_RATES
FA_MC_BOOKS_RATES
126
FA_MC_BOOKS_SUMMARY
FA_MC_BOOKS_SUMMARY
127
FA_MC_CONVERSION_HISTORY
FA_MC_CONVERSION_HISTORY
128
FA_MC_CONVERSION_RATES
FA_MC_CONVERSION_RATES
129
FA_MC_DEFERRED_DEPRN
FA_MC_DEFERRED_DEPRN
130
FA_MC_DEPRN_DETAIL
FA_MC_DEPRN_DETAIL
131
FA_MC_DEPRN_PERIODS
FA_MC_DEPRN_PERIODS
132
FA_MC_DEPRN_SUMMARY
FA_MC_DEPRN_SUMMARY
133
FA_MC_GROUP_DEPRN_DETAIL
FA_MC_GROUP_DEPRN_DETAIL
134
FA_MC_GROUP_DEPRN_SUMMARY
FA_MC_GROUP_DEPRN_SUMMARY
135
FA_MC_MASS_RATES
FA_MC_MASS_RATES
136
FA_MC_RETIREMENTS
FA_MC_RETIREMENTS
137
FA_METHODS
FA_METHODS
138
FA_MRC_INQ_FINANCIALS
FA_MRC_INQ_FINANCIALS
139
FA_PARALLEL_WORKERS
FA_PARALLEL_WORKERS
140
FA_PERIOD_MAPS
FA_PERIOD_MAPS
141
FA_PERIODIC_PRODUCTION
FA_PERIODIC_PRODUCTION
142
FA_PLSQL_DEBUG
FA_PLSQL_DEBUG
143
FA_PRICE_INDEX_VALUES
FA_PRICE_INDEX_VALUES
144
FA_PRICE_INDEXES
FA_PRICE_INDEXES
145
FA_PRODUCTION_INTERFACE
FA_PRODUCTION_INTERFACE
146
FA_PROJECT_REP_ITF
FA_PROJECT_REP_ITF
147
FA_PROPTAX_REP_ITF
FA_PROPTAX_REP_ITF
148
FA_RATES
FA_RATES
149
FA_RECLASS_REP_ITF
FA_RECLASS_REP_ITF
150
FA_RESERVE_LEDGER
FA_RESERVE_LEDGER
151
FA_RESERVE_LEDGER_GT
FA_RESERVE_LEDGER_GT
152
FA_RETIRE_REP_ITF
FA_RETIRE_REP_ITF
153
FA_RETIREMENTS
FA_RETIREMENTS
154
FA_RX_ATTRSETS_B
FA_RX_ATTRSETS_B
155
FA_RX_ATTRSETS_TL
FA_RX_ATTRSETS_TL
156
FA_RX_DYNAMIC_COLUMNS
FA_RX_DYNAMIC_COLUMNS
157
FA_RX_LOV
FA_RX_LOV
158
FA_RX_MULTIFORMAT_REPS
FA_RX_MULTIFORMAT_REPS
159
FA_RX_REP_COLUMNS_B
FA_RX_REP_COLUMNS_B
160
FA_RX_REP_COLUMNS_TL
FA_RX_REP_COLUMNS_TL
161
FA_RX_REP_PARAMETERS
FA_RX_REP_PARAMETERS
162
FA_RX_REPORTS
FA_RX_REPORTS
163
FA_RX_SECURITY
FA_RX_SECURITY
164
FA_RX_SUMMARY_TL
FA_RX_SUMMARY_TL
165
FA_SHORT_TAX_RESERVES
FA_SHORT_TAX_RESERVES
166
FA_SUPER_GROUP_RULES
FA_SUPER_GROUP_RULES
167
FA_SUPER_GROUPS
FA_SUPER_GROUPS
168
FA_SYSTEM_CONTROLS
FA_SYSTEM_CONTROLS
169
FA_TAX_INTERFACE
FA_TAX_INTERFACE
170
FA_TAX_REPORT
FA_TAX_REPORT
171
FA_TRACK_MEMBERS
FA_TRACK_MEMBERS
172
FA_TRANSACTION_HEADERS
FA_TRANSACTION_HEADERS
173
FA_TRANSFER_DETAILS
FA_TRANSFER_DETAILS
174
FA_TRANSFER_REP_ITF
FA_TRANSFER_REP_ITF
175
FA_TRX_REFERENCES
FA_TRX_REFERENCES
176
FA_WARRANTIES
FA_WARRANTIES
177
FA_WHATIF_ITF
FA_WHATIF_ITF
178
JE_DE_FA_SUMMARY
JE_DE_FA_SUMMARY
179
JE_HU_BALANCES_REPORT
JE_HU_BALANCES_REPORT
180

FA_ASSET_FAILURES_GT
181

FA_BOOK_CONTROLS_GT
182

FA_DEFERRED_DEPRN_EVENTS
183

FA_DEPRN_DETAIL_H
184

FA_DEPRN_EVENTS
185

FA_DEPRN_SUMMARY_H
186

FA_INQUIRY_TRX_GT
187

FA_MASS_ADDITIONS_GT
188

FA_MASS_TAX_ADJ_REP_T
189

FA_MC_DEPRN_DETAIL_H
190

FA_MC_DEPRN_SUMMARY_H
191

FA_TRANSACTION_INTERFACE
192

FA_WORKER_JOBS
193

FA_XLA_EXT_HEADERS_B_GT
194

FA_XLA_EXT_LINES_B_GT
195

FA_XLA_EXT_LINES_STG_GT
196

FA_XLA_EXT_LINES_TL_GT
197

FA_XLA_UPG_EVENTS_GT
198

FA_XLA_UPG_HEADERS_GT

Oracle Receivables Setup Steps


Oracle Receivables Setup Steps

This section provides a brief description of each Receivables setup step. Some of the operations listed are optional, but you should perform the required steps in
the order shown to be sure that your system is set up properly.
Step 1 Define Your Set of Books (Required)
You need to define at least one set of books before you can implement and use Receivables. A set of books includes an accounting calendar, a functional currency,
and an Accounting Flexfield structure.
If you previously defined your set of books in the Setting Up Oracle Applications Set of Books section while setting up a different Oracle Applications product,
proceed to the next step.
If you have not defined your set of books, see: Defining Sets of Books to complete the following steps:
Define your Accounting Flexfield
Define your Calendar Period Types
Define your Calendar Periods
Define your Currencies
Define your Accounting Flexfield Combinations (Optional)
Define your Set of Books
Assign your Set of Books to a Responsibility
Define your Daily Conversion Rate Types
Define your Daily Rates (Optional)
You specify which set of books your Receivables installation uses in the System Options window.
Additional Information: If you use the Oracle Applications Multiple Organization Support feature, you can use multiple sets of books for one Receivables
installation. See: Using the Multiple Organization Support Feature.
Step 2 Decide How to Use the Account Generator (Required)
The Account Generator ensures that Receivables substitutes the correct balancing segment values when you generate finance charges or post exchange rate gains
and losses to your general ledger. You need to review the default process that Receivables uses to see if it meets your accounting requirements. You can optionally
customize the Account Generator for each set of books that you have defined. See: Using the Account Generator in Oracle Receivables.
Step 3 Define Your System Items Flexfield Structure (Required)
Proceed to the next step if you previously defined your System Items Flexfield while setting up another Oracle Applications product.
If you have not installed Oracle Inventory or Oracle Order Entry and you want to record and report your item information, you need to define your System Items
Flexfield.
All Oracle products that reference items share the System Item Flexfield and support multiple segment implementation. The system provides a seeded System Item
Flexfield for you (Code = 'MSTK'). You must define a structure for this flexfield rather than creating a new flexfield.
Once you have defined your System Item Flexfield structure, you need to specify your Item Flexfield profile options.
Set the OE: Item Flexfield profile option at the site level to specify the System Item Flexfield structure you want to use. Set this to 'System Items,' which is the
System Item Flexfield structure you have just defined.
Next, set your AR: Item Flexfield Mode profile option to choose your preferred method of entry for this flexfield within Receivables. This default value is
concatenated segment entry. Refer to Step 37 for details on how to set up profile options.
Step 4 Define Your Organizations (Required)
Proceed to sub step 3, Specify your Item Validation Organization Profile Option, if you have previously defined your organizations while setting up another Oracle
Applications product.
1. Define Organization
You need to define at least one organization to use Receivables. This organization lets you use the inventory forms in Receivables if you do not have Oracle
Inventory installed.
2. Define Organization Parameters
You must define the control options and account defaults for your organization before you can define items or perform any transactions. You must assign a unique
short code to your organization and use this code to identify the organization with which you want to work.
3. Specify your Item Validation Organization
You need to set the OE: Item Validation Organization profile option to the organization of the Inventory Organization whose item master you want to use.
If you defined your organization in step 1, set the profile option to this organization. Otherwise, select an organization from the list of values. See: Organizations.
Refer to Step 37 for details on how to set up profile options.
4. Define Items
Once you have set up your Item Flexfield and chosen your Item Validation Organization, you can optionally define your items in the Items window. Proceed to the
next step if you have previously defined your items while setting up another Oracle Applications product. See: Items.
Step 5 Define Your Territory Flexfield (Optional)
You can use Territory Flexfields for reporting purposes. Receivables provides a default structure for your Territory Flexfield. You can associate Territory Flexfields
with salespeople, invoices, commitments, and customer business purposes. See: Territory Flexfield.
Proceed to the next step if you do not want to define Territory Flexfields.
Step 6 Define Sales Tax Location Flexfield Structure (Required, Default)
Receivables uses the customer shipping address to determine the sales tax rate on transactions for all customers in the country you define in the Systems Option
window as your home country. Proceed to the next step if you are not charging your customers tax based on their shipping address.
The seeded Sales Tax Location Flexfield structures are as follows:
Country
State and City
Province and City
City
Province
State, County and City
Proceed to sub-step four if you are planning to use one of the seeded structures, otherwise begin with sub step one.
Attention: If you use a Sales Tax Location Flexfield that contains a segment other than country and wish to set up a flexible address format for
your home country, every component in your Sales Tax Location Flexfield structure must also exist in your flexible address style for that country. See: Flexible
Addresses.
Sub-step one through sub-step three briefly describe how you can create a customized Sales Tax Location Flexfield structure if none of the seeded structures meet
your taxing requirements. For detailed information on customizing your Sales Tax Location Flexfield, see: Customizing Your Sales Tax Location Flexfield in the
Calculating Tax essay.
1. Define Value Sets
Receivables provides several value sets which are used with the seeded Sales Tax Location Flexfield structures. You will either use these for your customized
structure or create your own.
2. Define Key Flexfield Structure
Query 'Sales Tax Location Flexfield' in the Title field of the Key Flexfield region. Receivables provides a six seeded Sales Tax Location Flexfield structures. You
need to create a new customized structure if you do not wish to use any of the seeded structures. You should not simply modify a seeded structure.
3. Define Descriptive Flexfield Context
After defining your customized Sales Tax Location Flexfield structure, you need to define customized contexts for the following descriptive flexfields in the
Descriptive Flexfield Segments window:
Tax Rates Flexfield: This flexfield appears in the Review Sales Tax Rates window.
Item Exception Rate Assignment Flexfield: This flexfield pops up in the Tax Rate field of the Item Tax Rate Exceptions window.
Item Exception Rate Location Flexfield: This flexfield pops up in the Location field of the Item Tax Rate Exceptions window.
Exempt Regions Flexfield: This flexfield pops up in the Location field of the Tax Exemptions window.
Override Sales Tax Rates Flexfield: This field pops up in the Override field of the Tax Locations and Rates window.
4. Define Key Flexfield Segment Qualifiers
Verify that the Tax Account and Exemption qualifiers are set at the correct level for your needs. The Tax Account qualifier determines at which level of your
location flexfield you will assign tax accounts. The Exemption qualifier determines at which level the Receivables tax engine will create automatic exemptions.
5. Define Tax Locations and Rates
Enter and maintain locations for each segment of your Sales Tax Location Flexfield structure and assign tax rates to each location. Receivables uses Tax locations
to validate your customers' shipping address and to determine the proper tax amount. You can either use the sales Tax Rate Interface program to load locations
and tax rates or manually enter them in the Tax Locations and Rates window. See: Tax Locations and Rates.
See Also
Calculating Tax
Implementing Value Added Tax
Implementing US Sales Tax
Using Sales Tax Rate Interface
Step 7 Set Up Flexible Address Formats (Optional)
If the standard address format (Country, Address Line 1-4, City, State, Postal Code, Province and County) suits your business needs, you do not need to use the
flexible address formats feature.
Alternatively, you can associate address styles with countries to enable you to enter addresses in country specific formats throughout Receivables. This lets you
enter addresses in the style most appropriate to the country in which you or your customers conduct business. Receivables also offers the functionality to perform
country specific validation upon entry of addresses.
To implement flexible address formats, you need to assign an address style to a country in the Maintain Countries and Territories window.
Receivables provides the following address styles:
Japanese
Northern European
Southern European
South American
United Kingdom/Asia/Australasia
You can also create your own address styles and validation rules by defining alternative descriptive flexfield structures.
Proceed to the next step if you are planning to use one of the seeded address styles. For detailed information on how to define your own address styles, see: Using
Flexible Addresses.
Step 8 Maintain Countries and Territories (Optional)
You can view all countries and territories within your system in the Maintain Countries and Territories window.
Use the address style field to assign address styles to countries if you wish to use the Flexible Address Formats feature.
You can identify which countries are part of the European Union (EU) by entering a VAT Member State Code against these countries. The Receivables European
Sales Listing report uses this information to produce a listing of all sales to customers in European Community member states other than your own.
Step 9 Define Your Transaction Flexfield Structure (Optional)
Proceed to the next step if you are not using AutoInvoice.
If you are using AutoInvoice, you need to define your Transaction Flexfields to uniquely identify imported transactions. Because Transaction Flexfields are unique,
you can also use them to link and reference other transaction lines.
If you are using AutoInvoice, the Line and Invoice Transaction Flexfields are mandatory. When you define your Invoice Transaction Flexfield, you must use the
same structure that you used for your Line Transaction Flexfield, but only include those segments that refer to header-level information.
The Link-to and Reference Transaction Flexfields refer to the structure you define for your Invoice Transaction Flexfield, but can be optionally defined if you want
to create a customized form that displays your Link-to and Reference Transaction Flexfield.
Define the structure, segments, and values for your Transaction Flexfield in the Descriptive Flexfield Segments window. Execute a query on the Title field. You can
define your Line Transaction Flexfield, Link-to Transaction Flexfield, Reference Transaction Flexfield and Invoice Transaction Flexfield here.
Suggestion: If you want to query your Transaction Flexfield, you may want to update the Transaction Flexfield information for previously entered transactions.
We advise that you create indexes on your Transaction Flexfield columns if you want to query Transaction Flexfield information in your invoice headers and lines.
Additionally, without indexes the validation portions of the AutoInvoice program can be slow. For complete information about defining Transaction Flexfield
indexes, see: Importing Invoice Information Using AutoInvoice.
Step 10 Define Your AutoCash Rule Sets (Optional)
If you are using AutoCash, you need to define your AutoCash rule set before defining your system parameters or customer profiles classes. AutoCash rules
determine the sequence of application methods Receivables uses when automatically applying receipts to open debit and credit items. See: AutoCash Rule Sets.
See Also
Post QuickCash
AutoCash Rules
Discounts
Step 11 Define Your QuickCodes (Optional)
Receivables provides several default QuickCodes. These are used throughout Receivables to provide validated default values and list of values choices. You can
add or update these to customize your list of values and speed data entry. For example, you can define additional freight carriers that are used by your business.
Below is a list of all user updatable QuickCodes types:
Account Status
Address Categories
Adjustment Reason
Approval Type
Business Purposes for a Customer Address
Canadian Provinces
Collector Actions
Collector Follow Up Action
Credit Memo Reason
Credit Rating for Customers
Customer Class
Customer Credit Risk
Customer Relationship Type
Customer Response Reason
Define Freight Carriers
Demand Class
FOB (free on board)
Invoice Reason
Job Titles for Customer Contact
Mandatory Field Prompt for Message Dictionary
Possible Outcomes of a Customer Call
Reverse Payment Reason
Special Instructions
Tax Exemption Reason
Tax Rate Exception Reason
Tax Types
Titles For Contact Persons at Customer Sites
Type of Data to Include in a Specific Bucket
Types of Communication Used in Contacting Customers
Types of Documentation to Send to Customers with this Relationship to Primary Customer
Types of Messages
Types of Standard text usage
See Also
Defining Receivables QuickCodes
Freight Carriers
Step 12 Define Your AutoInvoice Line Ordering Rules (Optional)
If you are using AutoInvoice, you need to specify how you want to order and number your transaction lines after they have been grouped into invoices, debit
memos, and credit memos. Receivables provides many attributes that you can use to define your line ordering rules. See: AutoInvoice Line Ordering
Rules and Importing Transactions Using AutoInvoice.
Step 13 Define Your AutoInvoice Grouping Rules (Optional)
If you are using AutoInvoice, you need to specify how you want to group transaction lines. In order for transaction lines to be part of one transaction, certain
attributes must be identical. Receivables provides many attributes that you can use to define your grouping rules. See: Grouping Rules and Importing Transactions
Using AutoInvoice.
Step 14 Define Your System Options (Required)
Define your accounting, discount, tax, and invoice system options to control how Receivables works. For example, you can determine whether to charge your
customers Sales Tax or Value Added Tax (VAT). If you choose Sales Tax, Receivables supports location based Sales Tax for your home country only. You also
define your default (i.e. home) country in the System Options window. See: Defining Receivables System Optionsand Calculating Tax.
You can also specify a default Application Rule Set in the System Options window. An Application Rule Set determines how Receivables reduces the balance due
for debit items and their associated charges when you apply payments in the Applications window or by using Post QuickCash. Receivables only uses this rule set
if none is assigned to the debit item's transaction type. See: Receivables Application Rule Sets.
You can update the Default Country in this window at install time, provided you have not entered any customer addresses.
Attention: If you will be using flexible address formats to enter and validate your customer address information, we recommend that you implement the seeded
Sales Tax Location Flexfield structure, Country - No Validation. Alternatively, if you use a Sales Tax Location Flexfield that contains a segment other than country
and wish to set up a flexible address format for your home Country, every component in your Sales Tax Location Flexfield structure must also exist in your flexible
address style for that country. See: Using Flexible Addresses.
Below is a list of optional system options. All other system options are required. No default values are provided.
AutoCash Rule Set
Tax Registration Number
Accounting Flex Tuning Segment
System Items Tuning Segment
Territory Tuning Segment
SQL Trace
Purge Interface Tables
Unallocated Revenue Account*
* Required if your Accounting Method is Cash Basis.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 15 Define Your Payment Terms (Required, Default)
You must specify the payment terms to associate with your invoices, debit memos and commitments to determine your customer's payment schedule. You can also
include tiered discounts for early payment. Receivables provides a predefined payment term, '30 NET'. See: Discounts and Payment Terms.
Step 16 Define Your Accounting Rules (Optional)
If you want to recognize revenue over multiple accounting periods, you must define accounting rules. Receivables lets you define as many accounting rules as you
want. If you use an accounting rule, you must associate it with an invoicing rule. Invoicing rules determine when to book your receivables. Receivables provides
two invoicing rules: 'Bill in Advance' and 'Bill in Arrears'.
When you use accounting rules, you also need to define the appropriate periods to which your rule refers. You enter these periods in the Calendar window and
they must refer to the same period type as your accounting rule. For example, if you are using an accounting rule that recognizes revenue monthly from Jan-93
through Jun-93, you must define periods from Jan-93 through Jun-93 where the period type is 'Month.' These periods must be defined in the same calendar as
your accounting periods.
Attention: If you have an accounting period type that is not 'Month' and you use AutoInvoice with Oracle Order Entry, you should update the Period field for the
predefined IMMEDIATE accounting rule to the same period as your accounting period type.
See: Accounting Rules and Defining Calendars.
Step 17 Open Your Accounting Periods (Required)
Maintain the accounting periods to control transaction entry, receipt application, and posting. Receivables provides the following period statuses: Not Opened,
Future, Open, Close Pending, and Closed. See: Opening and Closing Accounting Periods.
Step 18 Define Your AutoAccounting (Required)
Define all of your AutoAccounting account structures that Receivables uses. Receivables creates default revenue, receivables, freight, tax, suspense, unbilled
revenue, and unearned revenue accounts based on the information you enter for your AutoAccounting structures.
See: AutoAccounting and Using AutoAccounting.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 19 Set up Cash Basis Accounting (Optional)
If you are not using the Cash Basis accounting method, you can skip this step.
If you are using the Cash Basis method of accounting, you must perform various steps in addition to setting your Accounting Method system option to 'Cash Basis'.
For more information, see: Using Cash Basis Accounting.
One of the steps to set up Cash Basis Accounting requires that you define transaction types. Transaction types are discussed in more detail in the next step.
Step 20 Define Your Transaction Types (Required, Default)
Define the transaction types that you assign to your invoices, debit memos, commitments, chargebacks, credit memos, and on-account credits. Receivables uses
transaction types to default payment term, account, tax, freight, creation sign, posting, and receivables information. Receivables provides two predefined
transaction types: 'Invoice' and 'Credit Memo'. See: Transaction Types.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 21 Define Your Transaction Sources (Required, Default)
Define the transaction sources that you will assign to your invoices, debit memos, commitments, credit memos, and on-account credits. Receivables uses
transaction sources to control your transaction and transaction batch numbering, to specify your default transaction type, and to select validation options for
imported transactions. Before you can define a transaction source for your invoices, you must define transaction sources for your credit memos. Receivables
provides the following predefined transaction sources: 'MANUAL-OTHER', 'DM Reversal,' and 'Chargeback'. See: Transaction Batch Sources.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 22 Define Your Collectors (Required, Default)
Define collectors to assign to your customers through credit profile class assignments. You can use the customer account review windows and collection reports to
alert your collectors of their customer's past due items. Receivables provides a single collector called 'DEFAULT.' See: Collectors.
Step 23 Define Your Adjustment Approval Limits (Required)
Assign adjustment approval limits to each user to control adjustments made to invoices, debit memo, and chargebacks. Receivables lets you assign approval limits
by currency. These limits are used in the Adjustments, Approve Adjustments, and Receipts windows. See: Adjustment Approval Limits.
Step 24 Define Your Remittance Banks (Required)
Proceed to the next step if you have already defined your remittance banks in Oracle Payables.
Define all of the banks and bank accounts you use to remit your payments. You can define as many banks and bank accounts as you want, but each bank account
must refer to one currency. Receivables requires that you enter a cash account for each bank account. See: Defining Banks.
Step 25 Define Your Distribution Sets (Optional)
Define distribution sets if you have non-invoice related transactions and you want to use a predefined revenue distribution set. To speed data entry, revenue
distribution sets can also be assigned to receivables activities with a type of Miscellaneous Cash. See: Distribution Sets and Entering Miscellaneous Transactions.
Step 26 Define Your Receivables Activities (Required)
You must define receivables activities to link accounting information to your adjustments, finance charges, and miscellaneous cash transactions. See: Receivables
Activities.
Step 27 Define Your Receipt Classes (Required)
Define receipt classes to specify whether receipts are created manually or automatically. For manual receipts, you can specify whether to automatically remit it to
the bank and/or clear your accounts. For automatic receipts, you can specify a remittance and clearance method, and whether receipts using this class require
confirmation. See: Receipt Classes and Automatic Receipts.
Step 28 Define Your Payment Methods (Required)
Define the payment methods to assign to your receipt classes. When you define your payment methods, you must enter a receipt class, remittance bank
information, and the accounts associated with your payment receivables type. You can also specify accounts for confirmation, remittance, factoring, bank charges,
and short-term debt. See: Payment Methods.
Step 29 Define Your Receipt Sources (Required)
Define the receipt sources that you assign to receipts. When you define a receipt source, you can enter a default receipt class and payment method. See: Receipt
Sources.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 30 Define Your Aging Buckets (Optional)
You can define additional aging buckets to use when aging your receivables. Aging buckets are used by the Customer Aging window, statements, and the Credit
Snapshot and Aging reports. Aging buckets can include pending adjustments, items that are past due, not past due, current, due in the future, and in dispute.
See: Aging Buckets.
Step 31 Define Your Statement Cycles (Optional)
If you want to send your customers statements, define statement cycles and statement dates. The dates you associate with each statement cycle are the dates for
which you plan to generate statements for your customers. You can then assign statement cycles to your customers in the Customer Profile Classes window.
See: Statement Cycles, Using Statements and Assigning Profile Classes to Customers.
Step 32 Define Your Statement Messages (Optional)
To customize your statements with personal messages, define statement messages. These messages automatically print on the bottom of your statements. Use the
Print Statements window to assign statement messages and submit statements for printing. See: Standard Messages and Printing Statements.
Step 33 Define Your Dunning Letters (Optional)
To send your customers dunning letters to inform them of past due items and finance charges, define dunning letters. Receivables provides three predefined letters
named 'STANDARD1' through 'STANDARD3' and ten user definable letters named 'USER1' through 'USER10'. You can customize each dunning letter by
printing variables that are specific to each customer. These variables can be included in the text of the letter. Dunning letters must also be grouped into dunning
letter sets (see Step 34). See: Dunning Letters.
Step 34 Define Your Dunning Letter Sets (Optional)
If you want to send your customers dunning letters, you must define dunning letter sets. Dunning letter sets let you combine a sequence of dunning letters into one
group and increase the severity of each letter that you send. You can assign dunning letter sets to your customers in the Customer Profile Classes window.
Receivables provides one letter set named 'STANDARD,' which includes the three STANDARD letters described in the previous step. See: Creating Dunning
Letter Sets.
Step 35 Define Your Territories (Optional)
If you have defined your Territory Flexfield and want to create customized reports, you can define your Territory Flexfield combinations. Receivables lets you
assign Territory Flexfields to salespeople, invoices, and customer business purposes. See: Territories.
Step 36 Define Your Salespeople (Required, Default)
Define the salespeople you assign to your invoices, debit memos, and commitments to allocate sales credits. If you do not want to assign sales credits to a
transaction, you can enter 'No Sales Credit'. See: Salespersons.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 37 Define Your Profile Options (Required)
For each Receivables application, specify values for your personal profile options. Profile options determine default values for some Receivables operations, how
Receivables processes data control and control which actions a user can perform. Your system administrator determines which profile options you can choose.
You can use the Personal Profile Values window to set profile options only at the user level. System administrators use the System Profile Values window to set
profile options at the site, application, responsibility, and user levels. Receivables defaults all profile options at the site level.
See: Overview of Receivables User Profile Options.
For more information, please refer to Update Personal Profile Options in the Oracle Applications User's Guide and Update System Profile Options in the Oracle
Applications System Administration User's Guide.
Step 38 Define Your Tax Codes and Rates (Required)
If your Tax Method in the System Options window is set to 'VAT', you should enter the tax codes and tax rates you want Receivables to use when calculating tax
for your transactions. Tax codes can be assigned to customers, customer site uses, and standard memo lines. See: Tax Codes and Rates.
If your Tax Method in the System Options window is set to 'Sales Tax', you must define at least one tax code with a type of 'Location' in the Tax Codes and Rates
window. Receivables will use this tax code to calculate your location based tax. Enter a name for your location tax code, enter a type of 'Location,' and a tax
account. This account cannot be updated once you have committed your change. You can, however, enter additional 'Location' tax codes for different date ranges.
For either Tax Method, you may wish to set up an 'International', zero-rated tax code to assign to foreign addresses.
For complete information on setting up tax codes for VAT and Sales tax, see: Implementing Value Added Tax and Implementing U.S. Sales Tax. For information
about setting up tax codes for Canadian Sales Tax, see:Implementing Canadian Sales Tax.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 39 Define Your Customer Profile Classes (Required, Default)
You must define customer profile classes to categorize your customers based on credit, payment terms, statement cycles, automatic receipt, finance charge,
dunning, and invoicing information. When you initially set up your customers, you assign each customer to a profile class. To customize the profile class for a
specific customer, use the Customer Profile Classes window. Receivables provides the predefined customer profile class 'DEFAULT'. See: Defining Customer
Profile Classes.
Step 40 Define Your Customers (Required)
Proceed to the next step if you have already defined your customers while setting up another Oracle Applications product.
You must define your customers and customer site uses to enter transactions and receipts in Receivables. When you enter a new customer, you must enter the
customer's name, profile class and number (if automatic customer numbering is set to No). You can enter addresses, contacts, site uses and telephone numbers for
your customers. You will be required to enter all the components of your chosen Sales Tax Location Flexfield when entering customer addresses in your home
country. You define your Sales Tax Location Flexfield and home country in the System Options window. See: Entering Customers and Calculating Tax.
Step 41 Define Your Remit-To Addresses (Required)
Define remit-to addresses to inform your customers where to send their payments. Associate each remit-to address with one or more state, country and postal
code combinations. For example, if you want your customers in California and Nevada to send their payments to a specific address, enter the remit-to address and
associate the states CA and NV with this address. Remit-to addresses are assigned based on the bill-to address on the transaction.
If you do not wish to set up a remit-to address for each location, you can set up one remit-to address with a default assignment. This will be used for all locations
or for any locations that do not have specific location assignments.
To set up a default remit-to address, enter the remit-to address, navigate to the assignment region then, using the list of values in the Country field, select 'Default
Value'. Move to the next field and select the 'DEFAULT' state from the list of values. Then save your record. See: Remit-To Addresses.
Suggestion: It is a good idea to set up a default remit-to address, even if you have other remit-to addresses defined, because Receivables can use this address if
the bill-to location on the transaction is not covered by any other remit-to address assignment. This may happen, for example, when you use new customers.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 42 Define Your Customer Relationships (Optional)
If you want to restrict receipt application to related customers only, define relationships between your customers and set the system option 'Allow Payment of
Unrelated Invoices' to No. When you create relationships, customers can also apply invoices to related customer commitments. Receivables lets you define one
way and reciprocal relationships between your customers. See: Creating Customer Relationships.
Step 43 Define Your Customer Banks (Optional)
If you want to create automatic receipts, you need to define your customer banks and bank accounts. With automatic receipts, Receivables transfers funds directly
from your customer's bank to your remittance bank on the receipt maturity date. See: Defining Banks and Automatic Receipts.
Step 44 Define Your Lockboxes (Optional)
To use the AutoLockbox program to automatically record receipts from your banks, define your lockboxes. For each lockbox, enter the lockbox number, bank
name, batch source, bank account, bank origination number and cash account. See: Lockboxes.
Step 45 Define Your Transmission Format (Optional)
To use the AutoLockbox program, define your transmission file format. A transmission format is required to successfully import receipt information from your bank
into Receivables. Receivables provides two standard transmission formats that you can modify: Default and Convert. See: Transmission Formats and Using
AutoLockbox.
Step 46 Define Your Receipt Programs (Optional)
To use the Automatic Receipts feature, define the receipt programs you will use to send paper and electronic documents to your customers and remittance
banks. See: Automatic Receipt Programs and Automatic Receipts.
Step 47 Define Your Unit of Measure Classes (Optional)
Proceed to the next step if you have already defined your units of measure classes while setting up another Oracle Applications product.
Use the Units of Measure Classes window to define and update groups of units of measure with similar characteristics (for example, Volume or Length). A class
consists of a base unit of measure and other assigned units of measure. Use this window to define the base unit of measure for each class. See: Unit of Measure
Classes.
Step 48 Define Your Units of Measure (Required, Default)
Proceed to the next step if you have already defined your units of measure while setting up another Oracle Applications product.
Use the Units of Measure window to define one or more units of measure. Each item that you define in Receivables must have a primary unit of measure that you
will have defined in this window. The number of units of measure that you define in this window depends on the variety of physical characteristics of your
organization's inventory. See: Units of Measure.
Step 49 Define Your Standard Memo Lines (Optional)
To enter predefined lines for debit memos, on-account credits and invoices, define standard memo lines. When you define your standard memo lines, you can
specify whether a line is for charges, freight, line, or tax. Receivables also lets you define one chargeback and one debit memo reversal line. See: Standard Memo
Lines.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 50 Define Your Item Tax Rate Exceptions (Optional)
To assign special tax rates to items shipped to specific addresses, define your item exceptions for specific Location Flexfields. In order for Receivables to use these
exception rates, you should not assign tax codes to your customers or their site uses. See: Tax Rate Exceptions and Calculating Tax.
Step 51 Define Your Tax Exemptions (Optional)
To partially or fully exempt your customers or items from specific tax rates, define customer and item tax exemptions. See: Tax Rate Exceptions and Calculating
Tax.
Attention: If you use the Oracle Applications Multiple Organization Support feature, you need to perform this step for each of your operating units. For more
information about multiple organizations, refer to the Multiple Organizations in Oracle Applications manual.
Step 52 Define Document Sequences (Optional)
By assigning unique numbers to documents, you can account for each transaction you enter and the document that accompanies it.
To enable sequential numbering, set the Sequential Numbering profile option to either 'Always' or 'Partially Used'. You must then define and assign categories and
sequences for each transaction type, payment method, adjustment, and finance charge activity that you use. See: Implementing Document Sequences.

Customer Interface Information

Hello everyone,

This is a just how customer informations are stored in apps tables. This post gives you clear explanation of how customers information are getting stored.

Customer Created Name: TESTCUST_1

Customer Accounts Created under the customer TESTCUST_1:
1.TESTCUST_1_1
2.TESTCUST_1_2

For Customer:

SELECT * FROM HZ_PARTIES
WHERE PARTY_NAME LIKE 'TESTCUST_1'

Party Id: 307957

For Customer Accounts:

SELECT * FROM HZ_CUST_ACCOUNTS hca
WHERE hca.ACCOUNT_NAME IN ('TESTCUST_1_1','TESTCUST_1_2')

Account Number: 5391,5392
Account Id: 96675,96677

Customer Accounts Sites:

Under the Customer Account:
1.TESTCUST_1_1
Sites Name:
1.TESTCUSTS1_1
2.TESTCUSTS1_2
/*2.TESTCUST_1_2
Site Name:
1.TESTCUSTS2_1
2.TESTCUSTS2_1*/
SELECT * FROM HZ_CUST_ACCT_SITES_ALL hcsa
where hcsa.CUST_ACCOUNT_ID IN (96675) -- Customer Account Id of TESTCUST_1_1 ---Sites - TESTCUSTS1_1,TESTCUSTS1_2

Customer Account Site Id: 10554 - TESTCUSTS_1_2
10558 - TESTCUSTS_1_1

SELECT * FROM HZ_PARTY_SITES
WHERE PARTY_ID = 307957 -- Check Party Site Name : TESTCUSTS1_1,TESTCUSTS1_2

Party site Id: 179402 - TESTCUSTS_1_2
179404 - TESTCUSTS_1_1


For the Site TESTCUSTS1_1:

Contact Creation:

1.Contact Name: TESTS_1_1
2.Telephone - created
3.Email

There are two Id need to get, one is subject id and other is object id

1.Subject Id is related to Organization that is customer Party id here the party id is
SELECT * FROM HZ_PARTIES
WHERE PARTY_NAME LIKE 'TESTCUST_1'

Party Id: 307957 - subject Id

2.Object Id is related to the contact name created that is Party Id of the person(Contact)

SELECT * FROM HZ_PARTIES
WHERE PARTY_NAME LIKE 'TESTS_1_1'

Party Id : 307959 - Object id

Now Check in the Relationship table using subject id and object id

SELECT * FROM HZ_RELATIONSHIPS hr
WHERE hr.SUBJECT_ID = 307957
and hr.OBJECT_ID = 307959

and the reverse entry will also be there

SELECT * FROM HZ_RELATIONSHIPS hr
WHERE hr.SUBJECT_ID = 307959
and hr.OBJECT_ID = 307957

Relatonship Id:137025
Party Id:307960

SELECT * FROM HZ_PARTIES hp
WHERE hp.PARTY_ID = 307960 -- Party_type will be PARTY_RELATIONSHIP


SELECT * FROM HZ_ORG_CONTACTS hoc
where hoc.PARTY_RELATIONSHIP_ID = 137025 -- Relatioship Id

Org Contact Id: 118071


SELECT * FROM HZ_CONTACT_POINTS hp --HZ_CUST_CONTACT_POINTS hcp
WHERE hp.OWNER_TABLE_ID = 179404 --Party Site Id of the Contact - TESTCUSTS_1_1

SELECT * FROM HZ_CUST_ACCOUNT_ROLES hcr
WHERE hcr.CUST_ACCT_SITE_ID = 10558 --Customer Account Role created when creating contacts --This is the Customer Site Id of TESTCUSTS_1_1