Developer Programs

Learn

Docs

loan_schedule_raw

Pipelined Data Sets > Symitar > loan_schedule_raw

Column nameDescriptionModeTypeLength
institutionidThis field stores the JH Platform institution identifierREQUIREDSTRING
eventtimeInternal use onlyNULLABLEINTEGER
sourcetypeInternal use only; SSDB fieldNULLABLESTRING
operationInternal use only; SSDB fieldNULLABLESTRING
extractdateInternal use onlyNULLABLEDATE
processdatetimeInternal use only; SSDB fieldNULLABLETIMESTAMP
loanscheduleuuidThis field stores a JH Platform unique identifier for a loan scheduleNULLABLESTRING
loanuuidThis field stores a JH Platform unique identifier for a loanNULLABLESTRING
accountnumberThis field stores the Symitar account number (membership account number)NULLABLESTRING
loanidThis field stores the 4 digit Loan IDNULLABLESTRING
loanschedulekeyInternal use only; SSDB fieldNULLABLEINTEGER
loankeyInternal use only; SSDB fieldNULLABLEINTEGER
accountkeyInternal use only; SSDB fieldNULLABLEINTEGER
sortrankInternal use only; SSDB fieldNULLABLEINTEGER
deleteidThis field stores a soft delete flag where 0=not deleted, 1=deletedNULLABLEINTEGER
symdateInternal use only; SSDB fieldNULLABLEINTEGER
systemcreatedatetimeInternal use only; SSDB fieldNULLABLEINTEGER
odscreatedatetimeInternal use only; SSDB fieldNULLABLEINTEGER
symInternal use only; SSDB fieldNULLABLEINTEGER
odsdeleteflagInternal use only; SSDB fieldNULLABLEINTEGER
odskeyInternal use only; SSDB fieldNULLABLEINTEGER
idThe system uses this field to keep the Schedule records in order visually. The order of the Schedule records imported into the Loan record is actually based on the Beginning Date fieldNULLABLESTRING
beginningdateThis field stores the date when this particular Schedule record becomes effectiveNULLABLEDATE
expirationThis field stores the date when this particular Schedule record should expireNULLABLEDATE
paymentcalctypeWhile the selection is valid, this field is generally not used for credit card loan typesNULLABLEINTEGER
paymentAn entry in this field is requiredNULLABLENUMERIC
paymenttypeThe amount applied to the loan principal changes each period, since the amount of interest due each period depends on the loan balance and the number of days in the loan period. This is the normal option for most daily interest loansNULLABLEINTEGER
dqcalculationmethodNULLABLEINTEGER
interesttypeNULLABLEINTEGER
repeatcodeThis field stores the code indicating how often you want the system to import the Schedule recordNULLABLEINTEGER
dueday1This stores the day of the month (1-31) on which the first payment is due for semimonthly loans, or the day of the month on which all loan payments are due for annual, semiannual, quarterly, or monthly loansNULLABLEINTEGER
dueday2This stores the day of the month (2-31) on which the second payment is due for semimonthly payment loans. This field is not used for annual, semiannual, quarterly, monthly, or biweekly loansNULLABLEINTEGER
recordchangedateThis field contains the system date from the last time any changes were made to this record. When a record is first created, this field carries the system date on which the record is createdNULLABLEDATE
exceedlevelpmtamtNULLABLEINTEGER
billingmethodNULLABLEINTEGER
billingdefaultdaysNULLABLEINTEGER
billingnoticeNULLABLEINTEGER
applyasbilledNULLABLEINTEGER
percentprincipalNULLABLENUMERIC
levelpaymentamtNULLABLENUMERIC
levelprincipalamtNULLABLENUMERIC
minimumpaymentNULLABLENUMERIC
billingnoticeminNULLABLENUMERIC
useratechangeprocessingWhen you run the Rate Change Processing batch program, the value in this field determines whether the system updates the Payment field value for this Schedule recordNULLABLEINTEGER


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