The CREDIT statement is optional. Use it to supplement the accounting algorithm defined on the RATE and PRIORITY statements. Credits may be manually introduced to CA JARS to be applied to a specific job or summarization level (account, department, project, and so forth). Some typical uses for the CREDIT statement are:
Each CREDIT (and DEBIT) statement introduced to CA JARS is formatted into an accounting record to be sorted and reported on as any other input. All CREDIT statement fields are formatted to corresponding fields as referred to in the Basic Accounting Table. For processing purposes, the record is treated as a one-step job.
Note: The creation of CREDIT and DEBIT accounting records is performed during user-defined report processing and the accounting records created for each CREDIT (and DEBIT) statement are not present on the Account file, or made available to an Account exit. However, if output to a History file, and subsequently input into CA JARS, CREDIT and DEBIT history records are present on the Account file and available to an Account exit.
The following fields, if not present on the CREDIT statement, are filled with blanks in the formatted record:
The following fields (or any portion thereof) not present on the CREDIT statement are filled with high values (hex 'FF') in the formatted record:
For collating purposes, note that the date field is moved to the reader start date and run date fields. Also, the time field is moved to the reader start time and start time fields in the formatted record. (Refer to the Basic Accounting Table). The high values portion of these fields, if any, do not print when selected for display and, therefore, are used to reduce keypunch strokes when preparing CREDIT statements or to cause credits to collate last in a certain group of records.
The credit amount, in dollars, is carried by CA JARS and made available for display as DE ID 79 in the Sequenced Output Data Elements Table. The credit amount also affects the total charge (DE ID 46), distributed charge (DE ID 47), and percent totals (DE IDs 41 and 42) at any level of display. Examples of typical CREDIT statement setups are provided next.
position 1 2 3 4 5 8 1........0.........0.........0.........0.........0........ .....0 ACREDIT 6 AAA 9808 150000 ACREDIT 6 AAA 980915TESTDUMP153321 2447
The first CREDIT statement for Report A is to be applied against CPU identification 6. The account number is AAA, assumed to be the first three characters of the accounting fields information. The credit amount of $1500.00 is to be applied against current September billing for August adjustments.
The second CREDIT statement for Report A is to be applied against a specific job run on the system with CPU identification 6. TESTDUMP was run under account AAA at 15.33.21 on September 15, 1998. The rerun credit amount is $24.47.
|
Position |
Field Length |
Field Name |
Notes |
|---|---|---|---|
|
1 |
1 |
Set Code |
Optional |
|
2-9 |
8 |
Statement Type |
CREDIT |
|
10 |
1 |
CPU Identification |
|
|
11-18 |
8 |
User Identification |
|
|
19-34 |
16 |
User Info./Acct. Field |
|
|
35-40 |
6 |
Date |
yymmdd |
|
41-48 |
8 |
Job Name |
|
|
49-54 |
6 |
Time |
hhmmss |
|
55-74 |
20 |
Programmer |
|
|
75-80 |
6 |
Credit Amount |
9999V99; dollars |
| Copyright © 2012 CA. All rights reserved. |
|