cpworkcard_raw
Pipelined Data Sets
>
Symitar
>
cpworkcard_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 | |
| cpworkcarduuid | This field stores a JH Platform unique identifier for a cp workcard | NULLABLE | STRING | |
| accountuuid | This field stores a JH Platform unique identifier for an account | NULLABLE | STRING | |
| accountnumber | This field stores the Symitar account number (membership account number) | NULLABLE | STRING | |
| cpworkcardkey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| accountkey | 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 | |
| type | This field identifies the kind of Work Card record. Only defined Work Card Types are displayed as options for this field | NULLABLE | INTEGER | |
| fmlastdate | The system updates this field with the current system date whenever you perform file maintenance on this CP Work Card record. This field in the CP Work Card record is not updated when the file maintenance is performed by a batch process | NULLABLE | DATE | |
| closedate | Enter a close date for the Work Card record following your credit union's policies. When Daily Posting runs after this date, the system sets the Active field to (0) Inactive | NULLABLE | DATE | |
| nextworkdate | Enter the next date you expect to work this Work Card record | NULLABLE | DATE | |
| lastworkdate | The system updates this field with the current system date whenever a collector creates a collection Note record, records a promise to pay, or generates a collection letter | NULLABLE | DATE | |
| lastworktime | The system updates this field with the current system time whenever a collector creates a collection Note record, records a promise to pay, or generates a collection letter | NULLABLE | INTEGER | |
| notepurgedate | This field is not currently used | NULLABLE | DATE | |
| lastcollectorid | Whenever the Daily Posting batch program assigns a CP Work Card record to a collector, the system updates the Collector ID 0 field with the assigned collector's user number. You can change which collector is assigned to a CP Work Card record through file maintenance of this field. The system validates the field value against the Valid Collector List section in the Collection Work Card parameters | NULLABLE | INTEGER | |
| active | This field identifies the status of the Work Card record | NULLABLE | INTEGER | |
| locator | The system stores a unique number within each member account in this field that can be used as a unique identification of this record | NULLABLE | INTEGER | |
| priority | This field contains the Priority 0 field value you assigned with the Daily Posting batch program using the custom specfile you entered at the Collection Queue Specification File prompt. You can perform file maintenance on this field | NULLABLE | STRING | |
| secpriority_1 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_2 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_3 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_4 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_5 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_6 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_7 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_8 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| secpriority_9 | These fields determine the order in which the work cards appear in the collection queue. They contain the priority you assigned with the Daily Posting Batch Program using the custom specfile you entered at the Collection Queue Specification File prompt | NULLABLE | STRING | |
| seccollectorid_1 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_2 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_3 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_4 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_5 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_6 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_7 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_8 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| seccollectorid_9 | We replaced the Secondary Collector ID List field with new Collector ID 1 - Collector ID 9 fields. These fields are used when a CP Work Card record is assigned to more than one collector | NULLABLE | INTEGER | |
| recordchangedate | The system stores the system date in this field when you create, change, or save the Collection Work Card record. There are times when the system updates this field because the record was saved, even though there may not be any actual changes in 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