externalloan_tracking_raw
Pipelined Data Sets
>
Symitar
>
externalloan_tracking_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 | |
| externalloantrackinguuid | This field stores a JH Platform unique identifier for an external loan tracking record | NULLABLE | STRING | |
| accountnumber | This field stores the Symitar account number (membership account number) | NULLABLE | STRING | |
| externalloanlocator | This field stores the external loan locator | NULLABLE | STRING | |
| externalloantrackingkey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| externalloankey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| accountkey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| deleteid | This field stores a soft delete flag where 0=not deleted, 1=deleted | NULLABLE | INTEGER | |
| sortrank | Internal use only; SSDB field | 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 | |
| type | The Tracking Type field indicates how you use the External Loan Tracking record | NULLABLE | INTEGER | |
| id | This field stores the ID of this record's parent External Loan record. The system updates this field automatically. You cannot perform file maintenance on this field | NULLABLE | STRING | |
| idtype | This field stores a number that identifies this record's parent Tracking record type | NULLABLE | INTEGER | |
| userid | This field stores the user number of the user who created the External Loan Tracking record | NULLABLE | INTEGER | |
| fmlastdate | The system updates this field with the system date when you perform file maintenance on the External Loan Tracking record | NULLABLE | DATE | |
| creationdate | The system updates this field with the current system date when you create the External Loan Tracking record | NULLABLE | DATE | |
| creationtime | The system updates this field with the current system time (HHMM) when you create the Loan Tracking record | NULLABLE | INTEGER | |
| expiredate | You can use this field to store an expiration date for the External Loan Tracking record | NULLABLE | DATE | |
| trackingcode | This field stores a user-entered code (0-99) to further identify the purpose of the Loan Tracking record | NULLABLE | INTEGER | |
| usernumber1 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber2 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber3 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber4 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber5 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber6 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber7 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber8 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber9 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber10 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| userchar1 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar2 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar3 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar4 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar5 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar6 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar7 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar8 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar9 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar10 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| useramount1 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount2 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount3 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount4 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount5 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount6 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount7 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount8 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount9 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount10 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| usercode1 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode2 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode3 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode4 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode5 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode6 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode7 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode8 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode9 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode10 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| userdate1 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate2 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate3 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate4 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate5 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate6 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate7 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate8 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate9 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate10 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userrate1 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate2 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate3 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate4 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate5 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate6 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate7 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate8 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate9 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate10 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| locator | Each record's Locator field value is unique in each member account, and can be used as a unique identification of a specific record | NULLABLE | INTEGER | |
| usernumber11 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber12 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber13 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber14 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber15 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber16 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber17 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber18 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber19 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usernumber20 | For tracking types 30-99, you can use this field to store any user-entered number. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| userchar11 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar12 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar13 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar14 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar15 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar16 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar17 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar18 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar19 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| userchar20 | For tracking types 30-99, you can use this field to store any user-entered character data (up to 40 characters). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | STRING | |
| useramount11 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount12 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount13 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount14 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount15 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount16 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount17 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount18 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount19 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| useramount20 | For tracking types 30-99, you can use this field to store any user-entered amount. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| usercode11 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode12 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode13 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode14 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode15 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode16 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode17 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode18 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode19 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| usercode20 | For tracking types 30-99, you can use this field to store any user-entered code (0-9999). You can define the field name with the Account File Tracking Type Parameters | NULLABLE | INTEGER | |
| userdate11 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate12 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate13 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate14 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate15 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate16 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate17 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate18 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate19 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userdate20 | For tracking types 30-99, you can use this field to store any user-entered date. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | DATE | |
| userrate11 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate12 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate13 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate14 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate15 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate16 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate17 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate18 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate19 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| userrate20 | For tracking types 30-99, you can use this field to store any user-entered rate. You can define the field name with the Account File Tracking Type Parameters | NULLABLE | NUMERIC | |
| recordchangedate | The system stores the system date in this field when you create, change, or save the record. The system updates this field when the record is saved, even though there may not be any actual changes to the record | NULLABLE | DATE |
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