participant_raw
Pipelined Data Sets
>
Symitar
>
participant_raw
| Column name | Description | Mode | Type | Length |
|---|---|---|---|---|
| institutionid | This field stores the JH Platform institution identifier | REQUIRED | STRING | |
| eventtime | Internal use only | NULLABLE | INTEGER | |
| sourcetype | Internal use only; SSDB field | NULLABLE | STRING | |
| operation | Internal use only; SSDB field | NULLABLE | STRING | |
| extractdate | Internal use only | NULLABLE | DATE | |
| processdatetime | Internal use only; SSDB field | NULLABLE | TIMESTAMP | |
| participantuuid | This field stores a JH Platform unique identifier for a participant | NULLABLE | STRING | |
| participantkey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| sortrank | Internal use only; SSDB field | NULLABLE | INTEGER | |
| deleteid | This field stores a soft delete flag where 0=not deleted, 1=deleted | NULLABLE | INTEGER | |
| symdate | Internal use only; SSDB field | NULLABLE | INTEGER | |
| systemcreatedatetime | Internal use only; SSDB field | NULLABLE | INTEGER | |
| odscreatedatetime | Internal use only; SSDB field | NULLABLE | INTEGER | |
| sym | Internal use only; SSDB field | NULLABLE | INTEGER | |
| odsdeleteflag | Internal use only; SSDB field | NULLABLE | INTEGER | |
| odskey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| number | This field must contain a unique number associated with the participant. The number provides a key to this record | NULLABLE | STRING | |
| name | This field stores the name of the participant (up to 40 characters) | NULLABLE | STRING | |
| vendornumber | This optional field stores the vendor identification used for payments paid via check and ACH origination | NULLABLE | STRING | |
| achtrancodeout | This field stores the translation code used when the statement is sent via ACH origination | NULLABLE | INTEGER | |
| opendate | This field stores the date the user entered the participant into the system | NULLABLE | DATE | |
| closedate | This field stores the date after which the participant can no longer be added to Agreement records | NULLABLE | DATE | |
| lastfmdate | This field stores the date of the last file maintenance performed on the Participant record | NULLABLE | DATE | |
| fmlastpurgedate | This field stores the date through which you last purged file maintenance history for the participant with the Purge Transaction Processing batch program | NULLABLE | DATE | |
| statementdate | Whenever the Participant Statement batch program affects this participant, the system transfers the value in this field to the Statement Previous Date field and updates this field with the effective date of the Participant Statement batch run | NULLABLE | DATE | |
| statementprevdate | This field stores the date the previous statement was produced for this participant. Whenever the Participant Statement batch program affects this participant, the system transfers the value in the Statement Date field to this field | NULLABLE | DATE | |
| statementgroup | This field stores the number of the statement group (0-99) that includes statements for this participant | NULLABLE | INTEGER | |
| paymentmethod | This field stores the payment method used to pay the participant principal and interest due | NULLABLE | INTEGER | |
| balance | This field stores the current balance for the participant. The system updates this field as it distributes loan payments and advances among participants associated with a participation loan, when funding is required or paid, and when it makes disbursements to the participant | NULLABLE | NUMERIC | |
| lastpurgedate | This field stores the date of the last purge for participant transactions. Whenever you purge participant transactions for this Participant record using the Purge Transaction Processing batch program, the system updates this field with the calendar date one day before the Save Loan Transactions From date you enter in the batch program | NULLABLE | DATE | |
| lastdisbursaldate | This field stores the date of the last disbursal from the owner to pay the participant. It is updated in the Participant Statement Cutoff Processing batch program | NULLABLE | DATE | |
| type | This field stores a code that indicates if this record is for participant or dealer. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | INTEGER | |
| subtype | This field stores a credit union-defined reference code to define dealer types such as Automobile, Marine, or Motorcycle. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | INTEGER | |
| totalreserveaccrual | The system does not currently use or display this field | NULLABLE | NUMERIC | |
| buckets_1 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_2 | These fields each store the total amount of dealer payments on all loans for this dealer during a single period (usually each previous month). These fields are only used by specfiles and are not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_3 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_4 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_5 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_6 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_7 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_8 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_9 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_10 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_11 | This field stores the total amount of dealer payments on all loans for the most recent period this year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| buckets_12 | These fields each store the total amount of dealer payments on all loans for this dealer during a single period (usually each previous month). These fields are only used by specfiles and are not visible in the Participant record | NULLABLE | NUMERIC | |
| paymentslastyear | This field stores the calculated amount of total payments to the dealer for the previous year. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| paymentsltd | This field stores the calculated amount of total payments life-to-date for this dealer. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| legacycode | This field stores any legacy system number, that is, an identification code from your previous indirect loan system. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | STRING | |
| branch | This field stores the branch number associated with the dealer. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | INTEGER | |
| reservepaymentmethod | This field stores a code that identifies how the system should process the dealer's monthly payments. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | INTEGER | |
| userchar1 | This field stores any character data you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | STRING | |
| userchar2 | This field stores any character data you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | STRING | |
| userchar3 | This field stores any character data you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | STRING | |
| useramount1 | This field can store any amounts you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| useramount2 | This field can store any amounts you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| usernumber1 | This field can store any numeric value you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | INTEGER | |
| userrate1 | This field can store any percentage you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| userdate1 | This field can store any date you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | DATE | |
| usercode1 | This field can store any information with code options you define using the Dealer User Field Names parameters. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | INTEGER | |
| recordchangedate | This field stores the system date when you create, change, or save the Participant record. The system does not change this field when a calculated field changes | NULLABLE | DATE | |
| beginningballs | This field stores the beginning balance amount used in the last statement. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| upfrontrsrvls | This field stores the upfront reserve amount used in the last statement. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| chargebackls | This field stores the amount of the chargeback total used in the last statement. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| feesls | This field stores the total fees amount used in the last statement. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| adjls | This field stores the total adjustments amount used in the last statement. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| holdbackls | This field stores the holdback amount used in the last statement. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC | |
| paymentsytd | This field stores the total amount of dealer payments on all loans for this dealer during the past year as a rolling 12-month balance. This field is only used by specfiles and it is not visible in the Participant record | NULLABLE | NUMERIC |
Have a Question?
- Have a how-to question? Seeing a weird error? Get help on our collaborative Discourse page.
- Register for the Developer Office Hours where we answer technical Q&A, in real time, from the audience.
Did this page help you?
Last updated Tue Sep 15 2026