My Oracle Support Banner

Conductor Type Code Column Length Mismatch Between CSA And FCDM (Doc ID 2933911.1)

Last updated on APRIL 24, 2023

Applies to:

Currency Transaction Reporting - Version 8.0.0 and later
Information in this document applies to any platform.


While we were mapping CSA table STG_CARDS_PAYMENT_TXNS, we realized that the column V_TXN_CNDTR_TYPE_CD is defined as VARCHAR2(1), while the target column in FCDM (CURRENCY_TRXN.CNDTR_TYPE_CD) is defined as VARCHAR2(3). According to the CSA specifications, the values allowed for column V_TXN_CNDTR_TYPE_CD are:

Type (Role) of the conductor in the transaction. List of Values are:
A-Person conducting transaction on own behalf;
B-Person conducting transaction for another;
D-Courier Service (private)

But the supported values for CNDTR_TYPE_CD are:

50 (Person conducting transaction on own behalf)
17 (Person conducting transaction for another)
23 (Person on whose behalf transaction is conducted)
58 (Common Carrier)

We're wondering how the values A, B or D are converted to the values expected by FinCEN (50, 17, 23 or 58) when the CTR is generated. We didn't find anything in the BDFs or T2Ts that would do this conversion.



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.