Analytics Catalog/Oracle Fusion ERP/Receivables/Greece Notes Receivable - Post Dated Checks and Drafts Report
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Receivables

Greece Notes Receivable - Post Dated Checks and Drafts Report

Receivables

Greek notes receivable — post-dated checks and drafts received from customers, by maturity date and customer, so AR can track instruments not yet matured and the cash they'll convert to, as Greek practice requires.

Sample build of the Greece Notes Receivable - Post Dated Checks and Drafts Report — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Greece Notes Receivable - Post Dated Checks and Drafts Report
Sample build · illustrative
Filters
P Checks
Sample
P Customer Name
Globex Holdings
P Due Gl Date
2026-02-28
P Gl Date
2026-02-28
P Org Id
1003
320
Instruments
$2.80M
Face value
6
Matured unpaid
CustomerInstrumentReceipt DateMaturity DateAmountStatus
Acme IndustrialSample2026-04-302026-04-30$1,240,500.00Open
Northwind Trading2026-03-312026-03-31$842,150.75Posted
Globex HoldingsSample2026-02-282026-02-28$96,400.00Validated
Initech LLC2026-01-312026-01-31$1,005,233.10Open
Umbrella CorpSample2025-12-312025-12-31$58,720.40Paid
Acme IndustrialSample2026-04-302026-04-30$1,240,500.00Open
AI Analyst · active
reading

The report reads post-dated checks and drafts by maturity and customer.

flag

Six instruments matured but weren't cleared — bounced or uncollected post-dated checks, a direct credit-risk signal.

root cause & next step

Follow up on the dishonored instruments and reassess those customers' credit terms before accepting more drafts.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.
SQL data set · genericized · parameterized · no hardcoded segments
Show / hide SQL
SELECT    to_char(max(crh.gl_date), 'mm/DD/yyyy') GL_date,
          cr.receipt_number receipt_number,
          arm.name receipt_method,
          to_char(cr.issue_date,'mm/DD/yyyy') issue_date,
          to_Char(cr.receipt_date,'mm/DD/yyyy') receipt_date,
          to_char(aps.due_date,'mm/DD/yyyy') maturity_date,
          hp.party_number||' '||substr(hp.party_name,1,40) customer_header,
          --hp_branch.party_name Issue_bank,
          cr.issuer_bank_branch_id ,
         -- cr.issuer_name Issuer_name,
		 cr.attribute2 Issue_bank,
		 cr.attribute1 Issuer_name,
		 hp_bank.party_name remitted_bank,
           cr.amount receipt_amount,
           gcc.segment4 segment_value,
		   (select distinct ffvtl.description
						from fnd_flex_values_vl ffv,
						     gl_ledgers gl,
							 fnd_id_flex_segments_vl ffs,
							 fun_all_business_units_v fub,
							 fnd_flex_values_tl ffvtl
						where 1=1 
						and gl.CHART_OF_ACCOUNTS_ID = ffs.ID_FLEX_NUM 
						and ffs.description = 'Account'
						and ffs.FLEX_VALUE_SET_ID = ffv.FLEX_VALUE_SET_ID
						and gl.ledger_id = fub.primary_ledger_id
						and ffv.flex_value = gcc.segment4
						and ffvtl.language='EL'
						and ffvtl.flex_value_id=ffv.flex_value_id
						and fub.bu_id = cr.org_id) segment_description ,
	     cr.org_id,
		 --'CUSTOM A.E.B.E' Company_Name1 
		 (select NAME from XLE_ENTITY_PROFILES where LEGAL_ENTITY_IDENTIFIER='3241') Company_Name1  --REF-284098
						/* ,NVL((SELECT nvl(hl.global_attribute1, 'not exist')
                               FROM   hr_locations_all hl
                                WHERE 1 = 1
								      and hps.location_id = hl.location_id
								      and hl.location_code = 'CUSTOM A.E.B.E.'),'Not Exist') Company_Name --R12*/
          /* ,cr.PAY_FROM_CUSTOMER,	  
          (SELECT account.BANK_ACCOUNT_NUM FROM iby_ext_bank_accounts   account
                                              , iby_pmt_instr_uses_all  acc_instr
                                              , iby_external_payers_all ext_payer 
                                          WHERE 1= 1
                                                AND account.ext_bank_account_id = acc_instr.instrument_id
                                                AND acc_instr.ext_pmt_party_id  = ext_payer.ext_payer_id
                                                AND ext_payer.cust_account_id   = cr.PAY_FROM_CUSTOMER
           ) customer_Bank_account_num */
        ,cr.cash_receipt_id	
		
FROM    ar_cash_receipts_all cr, 
		ar_cash_receipt_history_all crh,
		ar_payment_schedules_all aps,
		hz_cust_site_uses_all csu,
		hz_cust_acct_sites_all cas,
		hz_party_sites hps,
		hz_parties hp,
		ce_bank_acct_uses_all cbaua,
		ce_bank_accounts cba,
		hz_parties hp_bank,
		hz_parties hp_branch,
		hz_relationships hp_relation,
		ar_receipt_methods arm,
		gl_code_combinations gcc
WHERE 1=1
	--and cr.receipt_number = 'Test12345'
	and cr.cash_receipt_id = crh.cash_receipt_id
	and cr.cash_receipt_id = aps.cash_receipt_id
	and cr.customer_site_use_id = csu.site_use_id
	and csu.cust_acct_site_id = cas.cust_acct_site_id
	and cas.party_site_id = hps.party_site_id
	and hps.party_id = hp.party_id
	and cr.remit_bank_acct_use_id = cbaua.bank_acct_use_id
	and cr.org_id = cbaua.org_id
	and cbaua.bank_account_id = cba.bank_account_id
	and cba.bank_id = hp_bank.party_id
	and cba.bank_branch_id = hp_branch.party_id
	and hp_bank.party_id (+) = hp_relation.object_id
	and hp_relation.subject_id (+) = hp_branch.party_id
	and hp_relation.relationship_type (+)             = 'BANK_AND_BRANCH'
	and hp_relation.relationship_code (+)             = 'BRANCH_OF'
	and hp_relation.subject_table_name (+)            = 'HZ_PARTIES'
	and hp_relation.subject_type (+)                  = 'ORGANIZATION'
	and hp_relation.object_table_name (+)             = 'HZ_PARTIES'
	and hp_relation.object_type (+)                   = 'ORGANIZATION'
	and cr.receipt_method_id = arm.receipt_method_id
	and crh.account_code_combination_id = gcc.code_combination_id	
	and crh.status in ('REMITTED','CONFIRMED') -- CLEARED 'Test12345'
	--and 'Draft' = :p_checks
	and (( gcc.segment4 in ('3390000000','3390020000','3391000000') and :p_checks='Check' and arm.name like '%ΕΠΙΤΑΓΕΣ%' )   
	       OR
		 (gcc.segment4 in ('3100000000','3101000000','3103000000') and :p_checks='Draft' and arm.name like '%ΓΡΑΜΜΑΤΙΑ%')
		)

	and cr.org_id = NVL(:p_org_id,cr.org_id)
	--and trunc(crh.gl_date) <= NVL(:p_gl_date,trunc(crh.gl_date))
	 and crh.status = (select status
                   from ar_cash_receipt_history_all
                   where cash_receipt_history_id = (select max(cash_receipt_history_id)
                                        from ar_cash_receipt_history_all
                                        where gl_date <=:p_due_gl_date
                                        and cash_receipt_id = cr.cash_receipt_id
and REVERSAL_GL_DATE is null ))
	and hp.party_name = NVL(:p_customer_name,hp.party_name)
	and cr.org_id in ( SELECT distinct bu.bu_id
								FROM fusion.FUN_ALL_BUSINESS_UNITS_V bu
								,fusion.FUN_USER_ROLE_DATA_ASGNMNTS role
								,fusion.per_users pu
								,fusion.per_roles_dn_vl pr
								,fusion.per_roles_dn_tl prtl
								WHERE role.org_id = bu.bu_id
								AND pu.USER_GUID = role.USER_GUID
								AND pr.ROLE_COMMON_NAME = role.ROLE_NAME
								and role.active_flag ='Y' 
								and pu.username = fnd_global.user_name
								and bu.bu_name ='GR BU EUR'
								and pr.role_id=prtl.role_id
								and prtl.LANGUAGE='US'
								and prtl.ROLE_NAME  in  ('XXC Accounts Receivable Analyst'
														 ,'XXC Accounts Receivable Manager'
														 ,'XXC Receivables Inquiry'
														)
							   )
	
GROUP BY 
        cr.cash_receipt_id,
        cr.receipt_number, 
		arm.name, 
		cr.issue_date, 
		cr.receipt_date, 
		aps.due_date, 
		hp.party_number||' '||substr(hp.party_name,1,40), 
		hp_branch.party_name, 
		cr.issuer_bank_branch_id ,
		cr.attribute2 ,
		cr.attribute1 ,
		hp_bank.party_name,
        cr.amount, 
	    gcc.segment4,
	    cr.org_id
ORDER BY aps.due_date ASC
:p_checks :p_customer_name :p_due_gl_date :p_gl_date :p_org_id

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

AR_CASH_RECEIPTS_ALLdimensionAR_TRANSACTION_HISTORY_A…dimensionHZ_CUST_ACCOUNTSdimensionGL_LEDGERSdimensionRA_CUSTOMER_TRX_ALLfact · one row per source transactionAmount
●— fact → dimension join
ElementTypeDefinition
AR_CASH_RECEIPTS_ALLdimensiondimension
AR_TRANSACTION_HISTORY_ALLdimensiondimension
HZ_CUST_ACCOUNTSdimensiondimension
GL_LEDGERSdimensiondimension
Amountmeasuremeasure
Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.
How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →
See the complete model
How this report's fact and dimensions fit the full picture, via conformed keys.
Receivables data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

TableReporting columnsSubject areas
RA_CUSTOMER_TRX_ALL5816
AR_CASH_RECEIPTS_ALL259
AR_TRANSACTION_HISTORY_ALL131
HZ_CUST_ACCOUNTS1443
GL_LEDGERS10104
Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.