Section 11
Profile Transactions

This table permits you to define groups of transaction types (trancodes) that are frequently processed together, for example, building permits, business license, new utility accounts, etc.. You can create an unlimited number of profile transactions by entering records into this table to define them to the program. For examples of how profile transactions are processed please see this link. Each field in the table is listed, along with a short description, below:

1. PROFILE_NAME
   
   You will assign a PROFILE_NAME of your choosing (up to 50 characters long) for each record you add to this table. For example BUILDING PERMIT. This is used to group the items that belong together on the specific profile transaction so that they all appear on the screen when you select a specific profile name from the selection list. The profile name will repeat for EACH record in the profile ... that is, if you have a profile with five Tran_Codes on it, there will be five records in the table, and each of the records share a common PROFILE NAME, linked to the TRAN_CODE[s] assigned to that profile.
   
   
2. TRAN_CODE
   
   This is the tran_code of the item you wish to process as part of the profile transaction. It must be a valid code in order for it to appear on the entry screen. If it is not valid, it won't be displayed during entry.
   
   
3. SEQUENCE_NUMBER
   
   This is a numeric value you can assign to each item so that the list of Tran_Codes you select for each profile will appear in an order that you control. You can enter the values as whole number ( 1, 2, 3, 4, etc.) or as fractional values ...( 1.1, 1.2, 1.3, etc.) or as a combination of the two ( 1, 2, 2.1, 2.2, 3, etc.). The items will be displayed in ascending numeric order on the profile entry screen.
   
   Assigning a proper order to your items is especially useful if the basis for your entry is a standard remittance form submitted from another department.
4. PROFILE_FEE_AMOUNT
   
   If the amount on a profile transaction line item should be preset you can enter the standard value here or just set it to 0.00. The user will have the option to override this amount at entry time if required. Amounts related to the tran_code on the transaction code entry in the TRANCODES table ARE NOT used as the source for default amounts on profile transactions.
   
   
5. DEPT_CODE
   
   This setting controls which departments are permitted to process each particular profile transaction. For example, suppose you have 3 different profiles set up, P1, P2, and P3.
   
   Suppose that profile P1 should be processed only by the FIN department, P2 can only be processed by the REC department, and P3 can be processed by both the FIN or REC departments.
   
   On EACH line defined for the 3 profiles, you need to tell it which departments can process the items. In the example discussed here:
   
   each entry for p1 would have /FIN/ in the DEPT_CODE field
   
   each entry for p2 would have /rec/ in the DEPT_CODE field
   
   each entry for p3 would have /fin/rec/ in the DEPT_CODE field
   
   
   This will cause each profile to be available if the user processing the profile is assigned to a department that is permitted to the defined departments.
   
   Note that the delimiter used is a forward slash, and must appear both BEFORE and AFTER the specified department code entries. The ORDER of the entries (e.g., /FIN/REC/ vs. /REC/FIN/ is not important.
   
   

NOTE: The combination of the first three fields ( PROFILE_NAME + TRAN_CODE + SEQUENCE_NUMBER ) in each record forms a unique key value for the records in is table. If you try to enter a record and all three values are the same as for another record, the system will not permit it and warn of a duplicate entry.