Documente Academic
Documente Profesional
Documente Cultură
TRM Supplement
SCT Banner
Confidential Business Information
This documentation is proprietary information of SCT and is not to be copied, reproduced, lent or disposed of, nor used for any
purpose other than that for which it is specifically provided without the written permission of SCT.
© 1994-1995, 1997, 1999-2003, Systems & Computer Technology Corporation. All rights reserved. The unauthorized
possession, use, reproduction, distribution, display or disclosure of this material or the information contained herein is
prohibited.
In preparing and providing this publication, SCT is not rendering legal, accounting, or other similar professional services. SCT
makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with
applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar
professional services from competent providers of the organization's own choosing.
"SCT," the SCT logo, "Banner" and the Banner logo are trademarks of SCT. Third party hardware and software product names
and trademarks are owned by their respective third party owners/providers, and SCT makes no claim to such names or
trademarks.
Technical Reference Supplement
Accounts Receivable
Preface
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Consulting/Modification Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
1 Database Schematics
Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Automated Clearing House (ACH) . . . . . . . . . . . . . . . . . . . . . . . 1-5
Accounts Receivable Processing . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Accounts Receivable Collector/Temporary Tables . . . . . . . . . . . . . . . . 1-7
iii
Table of Contents
Sleep/Wake-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Setting Up Sleep/Wake Processes Using Method One . . . . . . . . . . . . . . 2-8
Setting Up Sleep/Wake Processes Using Method Two . . . . . . . . . . . . . . 2-9
Operating Systems Without Sleep/Wake-up Commands . . . . . . . . . . . . . 2-10
Collector File Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
3 Interfaces
4 Conversion
Index
Preface
Documentation for SCT Banner systems consists of Online Help and
complementary user and reference manuals. The Online Help contains topics for
which online navigation offers a clear advantage, such as form descriptions and field
descriptions. The user manuals provide an overview perspective, and contain
material for which an online format is less appropriate, such as report descriptions
and operations cycles.
The General Technical Reference Manual (TRM) and its product-specific supplements
provide information about the overall technical operations and capabilities of SCT
Banner. TRM supplements are available for Student, Financial Aid, Finance,
Accounts Receivable, Advancement, and Human Resources.
This manual is the Accounts Receivable TRM Supplement to the General Technical
Reference Manual. It provides information needed by the technical staff members
who support your Accounts Receivable product, including operations personnel,
DBAs, programmer analysts, systems analysts, and other technical specialists. Staff
members should be familiar with the hardware system in use at your site and all
should have a basic understanding of Oracle products.
Related Documentation
General User Guide– a user’s guide to the General module, its functions and
features
SCT uses similar naming conventions to create the file name of every document
delivered in electronic format. This section describes the components of this name.
The PDF file names for most electronic documents generated from SCT Banner use
the following naming convention: Product Identifier / five-digit Release Identifier /
Manual Type Identifier. The Release Identifier uses five digits to accommodate
products that distribute double-digit interim releases within a main release. An
example of a file name for a manual delivered as one file is humres60301rg.pdf.
• Manuals requiring more than one file, due to size, may have slightly different
conventions. For example, a Human Resources User Guide is divided into
chapters with file names that contain product and chapter information only.
• Some manuals are produced for multiple releases and require a date rather
than a release number. For example, this Release Identifier would be 0603 for
June 2003.
• Some manuals do not have a release number. An underscore replaces the
release number.
• On occasion some products have an electronic distribution release. This is
characterized by 6 digits rather than 5 digits as the release identifier. One
additional release number is added to indicate the electronic distribution.
Electronic Documents on CD
User manuals, reference manuals, and other product documents are delivered as
electronic files in portable document format (PDF) on one or more CDs. You may
print the files in whole or in part, and copies may be freely distributed to users at
your institution. Your system administrator may choose to make the PDF files
available electronically from a secured intranet Web site, or directly from the SCT
Banner graphical user interface (GUI) with the Bookshelf help option.
is under development for the entire product line. Over time, it will replace Dynamic
Help Query for every SCT Banner form. It provides context-sensitive online help for
forms, fields, and procedures. Form help provides an overview of the purpose and
use of the form; field help gives details about the contents of each field; procedural
help relates the form functions to the real-life tasks you’ll perform. For detailed
information about online help, refer to Chapter 2, Using SCT Banner.
ActionWeb csr@sct.com
E-mail distserv@sct.com
ActionLine
ActionLine is a telephone support service available to SCT maintenance customers.
It helps users resolve any questions or concerns that relate to SCT products and
services.
ActionWeb
The ActionWeb refers to the secured area of SCT's World Wide Web site dedicated
to ActionLine and other related services available to clients. Users must be
registered to obtain access to the secured site. Today, users can request an account
to gain access to SCT's secured ActionWeb pages by accessing http://www.sct.com,
and proceeding as follows:
2. In the Client Login section, click on the link Click Here to create a new
account.
(b) Enter your client site name and address, and select Register.
(c) Create your own User ID and password. (The password must be eight
characters long.)
SCT will verify a new ActionWeb user's information and send a confirmation e-mail
message when the ActionWeb account has been set up and he/she is registered.
Within the ActionWeb you can take advantage of the following online functions:
• Choose the Frequently Asked Questions (FAQ) section to take you to the FAQ
section within the Extended Search category.
SCT’s Education Centers provide a centralized location for training on the entire
SCT Banner series of systems and on various other products, including Oracle. The
Education Centers provide an environment where SCT clients can leave behind
daily office responsibilities and focus their attention on learning to use Banner. The
Centers also offer an ideal opportunity to interact with colleagues from other
installations, compare notes on implementations, and share information.
The SCT Education Center courses are led by seasoned SCT professional service
consultants. Participants receive detailed training on each specific module. They are
also provided with SCT Professional Services training materials that can be used for
internal training upon their return to their respective institutions. Each class is
conducted as a hands-on training session. Classes covering each module of the
Banner series are available on a regularly scheduled basis.
Malvern, PA
Rochester, NY
San Diego, CA
Toronto, Canada
Altrincham, UK
Consulting/Modification Services
SCT offers several SCT Banner short- and long-term consulting and custom system
modification services. Your institution’s GES Account Representative will work with
you to determine a package of support services that meets your needs.
This section includes lists of tables used by Accounts Receivable, entity relationship
diagrams that identify columns contained in these tables, and graphics that display
the relationships among various tables. The following conventions are used to
display those relationships.
Symbols
Table Table
Table Table
Table
Table
Table
Table
CONTRACT
EXEMPTION PRIORITY,
CODE, TERM TERM
PIDM PIDM PIDM PIDM PIDM PIDM
PIDM
PIDM
INSTALL PLAN
TBRISTL
PIDM, TERM
USERID USERID SESSION ID
TBRCOLR GXVBANK
TBRCBRQ TBRCRCP
TBRMESG TBBCSHR
TBRSBRL TBRMISD
TBRCMIS TBRCCRC
TGRCLR3 TBBCCLR
Product-specific Product-specific
Human Resources GXVBANK Finance
Interface Interface
Product-specific
Accounts Receivable
Interface
Tables
* The TBRCRCP table automatically takes care of itself, because the records are deleted when the receipt is
printed. If you want to generate a receipt number but do not want to print them, create a script to delete the
records with TBRCRCP_PRINTER = 'RPEDISB'.
TTRDTLC TRA Tax Reporting Collector A 1098 Student Tax Detail Report
STVHLDD
(Person Hold Type Validation)
CODE X(02)
TPRRHLD
(Auto Hold/release Rules) REG_HOLD_IND X(01)
TRANS_HOLD_IND X(01)
HOLD_RULE_CODE X(06) GRAD_HOLD_IND X(01)
GRADE_HOLD_IND X(01)
HLDD_CODE X(02) DESC X(30)
NONPERS_IND X(01) AR_HOLD_IND X(01)
FIN_AID_IND X(01) ENV_HOLD_IND X(01)
FUT_IND X(01) VR_MSG_NO 9(06)
AR_MEMO_IND X(01) DISP_WEB_IND X(01)
CONT_MEMO_IND X(01)
FINAID_MEMO_IND X(01)
PURGE_PRIOR_IND X(01)
NONCON_HOLD_IND X(01)
RELEASE_IND X(01)
FROM_DATE DATE
TO_DATE DATE
TTVRHLD REASON X(30)
(Auto Hold/release Rules AMOUNT_OWED 9(07)
Code Validation) ORIG_CODE X(04)
FIN_AID_TERM_OP X(02)
CODE X(06) FIN_AID_TERM_CODE X(06)
DESC X(30) MEMO_TERM_OP X(02)
MEMO_TERM_CODE X(06)
MIN_CURR_BALANCE 9(07)
MAX_CURR_BALANCE 9(07)
AS_OF_DATE DATE Legend
AGING_DATE_CODE X(01)
MIN_AGING_DAYS 9(07) X Alphanumeric
MAX_AGING_DAYS 9(07) 9 Numeric
MIN_AGING_BALANCE 9(07)
MAX_AGING_BALANCE 9(07)
TBRACCD TBBETBD
(Amount Charge/Payment Detail TBBDETC (Effective Date Term-based
Information) (Detail Change/Payment Designator Definition)
Code Definition)
EFF_DATE DATE
PIDM 9(22)
DETAIL_CODE X(4) NCHG_DATE DATE
TRAN_NUMBER 9(22)
DESC X(30) ACTIVITY_DATE DATE
TERM_CODE X(6)
TYPE_IND X(1) USER_ID X(30)
DETAIL_CODE X(4)
PRIORITY X(3) TERM_DATE DATE
USER X(30)
LIKE_TERM_IND X(1)
ENTRY_DATE DATE
DCAT_CODE X(3)
AMOUNT 9(22)
AMOUNT 9(22)
BALANCE 9(22)
TERM_CODE X(6)
EFFECTIVE_DATE DATE
EFFECTIVE_DATE DATE
BILL_DATE DATE
REFUNDABLE_IND X(1)
DUE_DATE DATE
RECEIPT_IND X(1) TBBTBDS
DESC X(30)
REFUND_IND X(1) (Term-based Designator Rules)
RECEIPT_NUMBER 9(22)
ACTIVITY_DATE DATE
TRAN_NUMBER_PAID 9(22)
PAYT_CODE X(1)
CROSSREF_PIDM 9(22) TBDS_CODE X(2)
PREBILL_PRINT_IND X(1)
CROSSREF_NUMBER 9(22) OPERATOR X(1)
GL_NOS_ENTERABLE X(1)
CROSSREF_DETAIL_CODE X(4) TERM_CODE X(6)
TAXT_CODE X(2)
SRCE_CODE X(1) PRIOR_SUM_OP X(2)
TBDC_IND X(1)
ACCT_FEED_IND X(1) PRIOR_SUM_TERM_SUFX X(2)
DETAIL_CODE_IND X(1)
ACTIVITY_DATE DATE ACTIVITY_DATE DATE
DETC_ACTIVE_IND X(1)
SESSION_NUMBER 9(22) USER_ID X(30)
DIRD_IND X(1)
CSHR_END_DATE DATE TBRACCT EFF_DATE DATE
CRN X(5) (Detail Code Account
CROSSREF_SRCE_CODE X(1) Definition_
LOC_MDT X(1)
TBBEACT
LOC_MDT_SEQ 9(22) DETAIL_CODE X(4) (Effective Date Detail
RATE 9(22) ACCOUNT_A X(60) Code Amount Definition)
UNITS 9(22) ACCOUNT_B X(60)
DOCUMENT_NUMBER X(8) PERCENT 9(22)
TRANS_DATE DATE ACTIVITY_DATE DATE DETAIL_CODE X(4)
PAYMENT_ID X(20) TBDS_CODE X(2)
INVOICE_NUMBER X(8) EFF_DATE DATE Legend
DETC_EFF_DATE DATE
STATEMENT_DATE DATE USER_ID X(30) NCHG_DATE DATE
ACTIVITY_DATE DATE X Alphanumeric
INV_NUMBER_PAID X(8)
USER_ID X(30) 9 Numeric
CURR_CODE X(4)
EXCHANGE_DIFF 9(22) TBDC_IND X(1)
FOREIGN_AMOUNT 9(22) TERM_DATE DATE
LATE_DCAT_CODE X(3)
FEED_DATE DATE
FEED_DOC_CODE X(8)
ATYP_CODE X(2)
ATYP_SEQNO 9(22)
CARD_TYPE_VR X(1)
CARD_EXP_DATE_VR DATE
CARD_AUTH_NUMBER_VRX(12)
CROSSREF_DCAT_CODE X(3)
Legend
COLC_AGENCY_PIDM 9(22) PIDM 9(22) CODE X(1)
PIDM 9(22)
X Alphanumeric SEQ_NUMBER 9(22) CONTRACT_NUMBER 9(22)
CONTRACT_NUMBER 9(22) DESC X(30)
9 Numeric TEXT 2(60) TERM_CODE X(6)
TERM_CODE X(6)
MIN_AMOUNT 9(22)
SEQNO 9(22)
MAX_AMOUNT 9(22)
SUBJ_CODE X(4)
PERCENT 9(22)
CRSE_NUMB X(5) SRCE_CODE X(1)
ACC_PRIORITY 9(22)
TBRCCSI
(Include/Exclude Category
TBBCONT Code by Source)
TBBCSTT TBBCSTU (Contract Information)
(Student Text) (Student Authorization
PIDM 9(22)
Information)
CONTRACT_NUMBER 9(22)
PIDM 9(22) PIDM 9(22)
TBRCCAT TERM_CODE X(6)
CONTRACT_PIDM 9(22) STU_PIDM 9(22) CONTRACT NUMBER 9(22)
TERM_CODE X(6) (Category Code Level DCAT_CODE X(4)
CONTRACT_NUMBER 9(22) CONTRACT_PRIORITY 9(22)
CONTRACT_PIDM 9(22) Authentication)
TERM_CODE X(6)
SEQ_NUMBER 9(22) CONTRACT_NUMBER 9(22) DESC X(30)
PRINT_IND X(1) TERM_CODE X(6) DETAIL_PAY_CODE X(4) PIDM 9(22)
ACTIVITY_DATE DATE AUTH_NUMBER X(30) DETAIL_CHG_CODE X(4) CONTRACT_NUMBER 9(22)
USER_ID X(30) AUTH_IND X(1) CONTRACT_ROLL_IND X(1) TERM_CODE X(6)
TEXT X(60) STUDENT_CONT_ROLL_IND X(1) STUDENT_CONT_ROLL_IND X(1) DCAT_CODE X(3) TTVDCAT
MAX_STUDENT_AMOUNT 9(22) TPRL_CODE X(10) MIN_AMOUNT 9(22) (Category Code Validation)
MAX_AMOUNT 9(22)
PERCENT 9(22) CODE X(3)
I_E_SOURCE_IND X(1) DESC X(30)
DCAT_PRIORITY 9(22)
TBBCCTX
(Contract/Contract Number Text)
TBBTPRL
TTVTPRC (Rule Code Definition)
(Rule Code Validation) CONTRACT_PIDM 9(22) TBRCDSI
TPRC_CODE X(10) CONTRACT_NUMBER 9(22) (Included/Excluded Detail
CODE X(10) PRINT_SCHEDULE_IND X(1) TERM_CODE X(6) TBRCDET Code by Source)
DESC X(30) PRINT_SUMMARY_IND X(1) SEQ_NUMBER 9(22) (Detail Code Level
INDIVIDUAL_BILL_IND X(1) PRINT_IND X(1) Authentication)
AUTHORIZE_NUM_IND X(1) PIDM 9(22)
CONTRACT_NUMBER 9(22)
PIDM 9(22) TERM_CODE X(6)
CONTRACT_NUMBER 9(22) DETAIL_CODE X(4)
TERM_CODE X(6) SOURCE_CODE X(1)
DETAIL_CODE X(4)
MIN_AMOUNT 9(22)
MAX_AMOUNT 9(22)
PERCENT 9(22)
I_E_SOURCE_IND X(1)
DETAIL_PRIORITY 9(22)
TBBDETC
(Detail Code Definition)
DETAIL_CODE X(4)
DESC X(30)
DETC_ACTIVE_IND X(1)
Exemption Setup
TBREACC
(Account Level Authorization) TTVSRCE
(Source Validation)
Legend
EXEMPTION_CODE X((8)
X Alphanumeric TERM_CODE X(6) SRCE_CODE X(1)
TBRBCSI DESCRIPTION X(30)
9 Numeric SRCE_CODE X(1) (Included/Exclude Category
MIN_AMT 9(22) Code by Source)
MAX_AMT 9(22)
PERCENT 9(22)
ACC_PRIORITY X(22)
EXEMPTION_CODE X(8)
TERM_CODE X(6)
DCAT_CODE X(3)
SOURCE_CODE X(1)
TBRECAT
TBREREQ TBBEXPT (Category Code Level
(Exemption Course (Exemption Information) Authorization)
Requirements)
TTVDCAT
EXEMPTION_CODE X(8) (Category Code Validation)
EXEMPTION CODE X(8) TERM_CODE X(6) EXEMPTION_CODE X(8)
TERM_CODE X(6) DESC X(30) TERM_CODE X(6)
SEQ_NUMBER 9(22) DETAIL_CODE X(4) DCAT_CODE X(3)
DCAT_CODE X(3)
SUBJ_CODE X(4) EXEMPTION_ROLL_IND X(1) MIN_AMT 9(22)
DESCRIPTION X(30)
CRRSE_NUMB X(5) EXPT_ROLL_IND X(1) MAX_AMT 9(22)
PERCENT X(22)
DCAT_PRIORITY X(3)
I_E_SOURCE_IND X(1)
TBREDSI
(Include/Exclude Detail
Code by Source)
TBREDET
(Detail Code Level EXEMPTION_CODE X(8)
Authorization) TERM_CODE X(6)
DETAIL_CODE X(4)
EXEMPTION_CODE X(3) SOURCE_CODE X(1)
TERM_CODE X(6)
TBBESTU DETAIL_CODE X(4)
(Student Authorization MIN_AMT 9(22)
Information) MAX_AMT 9(22) TBBDETC
PIDM 9(22) PERCENT 9(22) (Detail Code Definition)
EXEMPTION_PRIORITY 9(22) DETAIL_PRIORITY X(3)
EXEMPTION_CODE X(8) I_E_SOURCE_IND X(1) DETAIL_CODE X(4)
TERM_CODE X(6) DESCRIPTION X(30)
STUDENT_EXPT_ROLL_IND X(1) DETC_ACTIVE_IND X(1)
MAX_STUDENT_AMOUNT 9(22)
The following pages contain brief descriptions of reports in the Accounts Receivable
module.
TFRLATE Assess Late Charges for Billing Report Shows assessment of late charges for
outstanding Accounts Receivable accounts.
TFRRFND Auto Refunding of Credit Amounts Identifies accounts which have a credit
balance identified, flagged and reported.
TGPHOLD Auto Hold Release Process Based on the parameters and rules form,
automatically adds and releases holds on a
student account.
TGRCDEL Cashier Delete Process Deletes the cashiering records for which all
corresponding detail records have been fed
to accounting.
TGRCLOS Cashier Session Close Process Automates the closing and/or finalizing of
cashier sessions.
TGRCSHR Cashier Delete Report Shows daily bank deposit and user audit.
TGRDELI Batch Update of Delinquencies Identifies past due accounts and those with a
delinquency code.
TGRDETC Detail Code Report An Oracle report that displays detail codes
and their associated accounting
distributions.
TGRFEED Accounting Feed Process Shows audit trail of all cashier transactions.
TGRRCPT Account Receipt Report Shows receipt printout for account related
transactions.
TRRAGES Grant Aging Analysis Report Provides analysis of the grant receivables. You
can print this report for aging of both billed
and unbilled receivables.
TRRAPPL Application of Payment Process This process enables you apply payments to
the charges. This process has no parameters.
It applies payments to charges by grant. If a
Tpay number or invoice paid number is
entered by the user in the payments entry
form (FRAAREV), this process first applies
the payment to that specific charge
transaction number or for that specific bill
invoice number. If these two fields are not
entered by the user, then the process will
apply the payment against a grant to the
oldest charge
TRRRCON Grant Reconciliation Report This report reconciles data between the
Accounts Receivable module and the
Finance module for Grant Billing
transactions only. You can reconcile by chart
or by grant or by payment management
system code. You can also print just the
grants that are out of balance or just the
Payment management system codes that are
out of balance.
TRRUNAP Unapplication of Payments Process Enables you to unapply payments that have
been incorrectly applied to a charge. After
you run this process, you can apply the
payment to the appropriate charge
TRRUNPL Unapplied Payments Listing This report prints a list of all payments that
have not been applied to charges. It also
prints the fund codes the exact payment was
posted to. This report is sorted by grant
TSP1098 1098 Student Tax Notification Process The TSP1098 process retrieves existing data
from the Tax Information Form (TSATAXI),
and other fields within Banner and
populates the Student Tax Notification Form
(TSATAXN).
TSPISTT Create Installment Transaction This process is used to create the installment
plan transactions in the Accounts Receivable
Transaction Detail Table (TBRACCD). Rules
created on the new Installment Plan Rules
Form (TSAISTR) are used for processing.
TSR1098 1098 Tax Report Process Use the TSR1098 Process to print 1098-T
paper forms for IRS/ Student Notifications
on Moore Business Forms or produce the
IRS file.
TSRBTOT Total Billed Report The A/R Supervisor uses this report to review
the billing amounts by detail code by term.
TSRDETL Account Detail Report The A/R Supervisor uses this report to review
the account transaction ledger by term.
TSRLATE Assess Penalty/Interest Charges Report The A/R Supervisor uses this report to assess
penalty and interest charges for outstanding
student accounts.
TSRLBOX Lockbox Tape Unload Process Posts payments received through electronic
funds transfer to a person’s account.
TSRPDRV Lockbox Result Print Program Prints the Lockbox Error Report and the
Lockbox Results Report.
TSRRFND Auto Refunding of Credit Amounts Identifies and flags those accounts which
have a credit balance with a refund detail
code. In addition, it lists the generated
refund transactions with an address.
TSRROLL Contract and Exemption Roll Process Allows contracts and/or exemptions and
associated students to roll from one term to
the next term.
TSRSSUM Student Transaction Summary Report Displays a student’s balance and individual
charges and payments.
TSRTBIL Third Party Billing Statement Processes third party charges and payments
in either invoice or statement mode. The A/
R supervisor uses this report on a monthly or
user-defined time frame.
TSRTRAF Tax Relief Act Flat File Process Use the TSRTRAF process to produce a flat
file of Tax Notification Data to send to third
party servicers and/or to print the detail for
all tax report codes created for the given tax
year. This detail may be included in Student
Notification mailings.
TVPREQA Create Title IV Authorizations from Use this process to create authorizations
Requirements from financial aid tracking requirements for
students with statuses that have been
updated since a date that you specify. You can
use this process on an as-needed basis to
keep track of students as they complete their
financial aid requirements.
TVRCRED Students with Title IV Credit Report Use the TVRCRED process to produce a
report that displays Title IV students who
have a credit account balance. Run the
report after Disbursements (RPEDISB) and
Application of Payments (TGRAPPL).
Students who have authorized the institution
to hold Title IV funds are shown separately
on this report. You may contact other
students with a Title IV credit balance
regarding authorization to apply Title IV aid
to other amounts due or initiate a refund for
them.
Legend
Report or Process The report/batch process name
Language Identifies the language for the process - COBOL, C
Update/Query Does the process update any tables, or is it strictly a query-only report?
Audit Can you run the update process in Audit Mode, so that you can produce the report
without an update taking place?
Job Submission Can you run the process via job submission?
Sleep/Wake Is the process used in conjunction with Sleep/Wake?
Off Peak Does SCT recommend that you defer this program to an off peak processing time
(late night, weekends) for performance reasons?
Restart If the process aborts or is terminated after the process is initiated, can you restart
the process without any adverse consequences?
Report or Process Language Update/ Audit Job Sleep/ Off Peak Restart
Query Submission Wake
Report or Process Language Update/ Audit Job Sleep/ Off Peak Restart
Query Submission Wake
Report or Process Language Update/ Audit Job Sleep/ Off Peak Restart
Query Submission Wake
For a more detailed description of each report and its parameters, generate a List of
Reports and Parameters (GJRRPTS). This report also includes batch processes.
Sleep/Wake-up
SCT Banner provides two different mechanisms for running jobs in a cyclical or
"sleep/wake-up" manner.
UNIX
The first command procedure, sleepunx, prompts for parameters needed by the
second procedure and SQL*Plus scripts, sleepunx.shl and sleepunx.sql
respectively. This procedure then starts (or submits) sleepunx.shl, which in turn
starts sleepunx.sql. The SQL*Plus script sleepunx.sql will spool OS-specific
commands to run the job into a file, provided there is actually work to do as
determined by the parameters previously entered. When the SQL*Plus script exits,
sleepunx.shl executes the "spool" file. The parameters needed by the program
are contained in a XXXXXXX.dat file which are read via input redirection when the
job executes. The second command procedure sleepunx.shl then "sleeps" for the
specified interval, awakes, and loops back to start the SQL*Plus script again.
VMS
This is essentially the same as for UNIX. The script names are sleep.com,
sleepdec.com, and sleepdec.sql. Command input redirection is accomplished
by defining sys$input as the .dat file. The "sleeping" is done with the "wait"
command.
CMS
In this environment, there is only one command script, sleepcms.exec. Each job
run in sleep/wake mode must have its own .exec script. The command script
sleepcms.exec is provided as the model. You also need to set up separate CMS
accounts for each job or you may combine the execs to run sequentially on a single
account. The .dat file is read via input redirection. "Sleeping" is performed using
the CP SLEEP command.
Note: The following Banner systems and processes are valid for the Sleep/Wake
processing described in this section:
Report/Process Description
TGRRCPT Account Receipt
TSRCBIL Student Billing Statement (Invoices)
TGRMISC Miscellaneous Receipt
TSRSSUM Student Transaction Summary Report
3. On the Process Submission Control Form (GJAPCTL), for the valid sleep/
wake jobs listed previously, enter the correct response for the parameter that
specifies that the job should be processed for collector table entries. Refer to
the documentation for each specific process to determine the appropriate
response in each case (correct responses may be COLLECTOR, Y, %, etc.). In
addition, each sleep/wake job has a printer code parameter. You must specify
exactly the same code for this parameter answer that was entered on either
SOADEST or TOADEST. A value of Y should be entered for the run in sleep/
wake mode parameter, and a number of seconds should be specified for the
sleep/wake interval (cycle) for each process.
Note: Do not enter the printer code in the top section of GJAPCTL; only enter
it in the parameter section of the form.
To stop the process, enter N in the Continue to Run field and do a Save
function. The job will not stop immediately, but rather will stop after the next
time the process "wakes up" and finishes the next processing cycle. To change
the sleep interval, enter the desired interval in the Next Cycle Time field and
do a Save function.
The GJASWPT form can also be used to view statistics regarding how many rows
were processed for the most recent wakeup cycle and the total number of rows
processed since the process was initiated. You can also determine if the
processes terminated abnormally. by viewing the Abnormal Termination field.
If there is a Y in Abnormal Termination, something caused the process to fail.
You should review log files to determine the cause.
When running through Internet Native Banner, Reports is not currently able to
access the default role defined for the Report in the bansecr schema. Therefore,
product-specific roles are being created with the base privileges needed to run the
Reports, which must be granted to any user who will run Reports for that product
using Internet Native Banner.
In the Accounts Receivable product “plus” sub-directory, you will find tasorep.sql.
This script will create the necessary role and assign the privileges needed to run the
Reports. Please review this script before applying it to your production database.
2 Next, grant the role to the users who will be running the reports and set it as one of
their default roles.
sql_cmd system/password [ENTER]
grant ban_arsys_rep to “your_user” [ENTER]
Note: The “alter user” statement should include all of the user’s default roles.
Refer to sys.dba_role_privs for existing roles where
default_role=YES for “your_user” as grantee.
Chapter 3 Interfaces
This chapter identifies Banner products that interface with SCT Banner Accounts
Receivable and tables used by these interfaces. This chapter also provides detailed
information about the Lockbox Tape Unload Process (TSRLBOX).
The SCT Banner Accounts Receivable system interfaces with the following SCT
Banner products:
Higher Education
GURAPAY Table This table contains single line invoices from other SCT
Banner applications or client-developed applications,
which are to be processed into SCT Banner using the
FURAPAY process.
Note: The tape format must include at least one detail record and one batch
summary record in order for the tape to be processed.
If the data received from the bank via the tape is in error, use the Lockbox
Correction Form (TSALBOX) to correct errors. ID transaction date and invoice
number paid can be modified. After corrections have been made, rerun TSRLBOX
using the Lockbox Intermediate Table (TBRLBOX) as input.
Processing Details:
This process unloads the Lockbox electronic funds transfer tape data to a database
table (TBRLBOX) and/or attempts to post the information from the Lockbox
Intermediate Table to the Account Detail Table (TBRACCD).
If the input to the process is TAPE, the Lockbox tape is read. File header, batch
header, and file summary records are not loaded to the TBRLBOX table. The
TBRLBOX table contains only batch detail and batch summary records. Each batch
detail record read from the tape is loaded to TBRLBOX. When a batch summary
record is encountered, information about the batch is loaded to an internal table
(which will be printed on the control report), the record is loaded to TBRLBOX,
the batch is committed to the database and the TBRLBOX_BATCH_VERIFY_IND is set.
A batch is marked as verified (TBRLBOX_BATCH_VERIFY_IND = Y) when the
computed total of the batch detail amounts is the same as the total on the batch
summary record. An entire batch is either verified on unverified (i.e., the indicator
is set on the batch summary record and on all the batch detail records).
Once the data have been loaded to the database, or the input to the process is
TABLE, the Lockbox Intermediate Table (TBRLBOX) is processed. The ID must
be a valid ID on SPRIDEN. The invoice number paid (if present) must be a valid
invoice number on TBRACCD for the ID. The amount to be paid against an invoice
must also be valid. When it is determined that at least one payment will be posted to
the Account Detail Table (TBRACCD), a cashiering session is created. For each
payment to be posted to TBRACCD, a tran number will be generated, the payment
will be inserted into TBRACCD, and the TBRLBOX record processed will be
deleted. When all batch details are deleted from TBRLBOX, the batch summary
will be deleted from TBRLBOX.
Note: The Lock Box process must be tailored to your specific input format,
including the check digit algorithm if you choose to use one. The tape
layout provides for check digits for further verification of data. Check
digit verification should occur when validating ID, invoice number paid,
etc. Add logic to use your check digit algorithm. Technical staff should
refer to the Cobol source code TSRLBOX.pco.
Year 2000 Note: The program has been changed to insert a year 2000
compliant date into TBRLBOX when reading from TAPE. There is a
SUBSTR function used and the format for the SUBSTR function is
YYMMDD. So the date being read from the tape should be in YYMMDD
The Lock Box process must be tailored to your specific input format. The record
length of the Lock Box input file is 80 characters. The basis of this layout is that each
record contains a record type and a batch number. If this basic premise cannot be
kept intact, the BANNER AR Lock Box process should not be used since this is
inherent in the design. The record length may be changed, but the record must
contain a record type and a batch number. The length of record type and batch
number may be modified.
To modify the record types, change the value of the following05-level variables
under the 01 level DECLARE-SPECIFIC:
05 DECL-FILE-HEADER PICTURE X(01) VALUE '1'
1. Modify the LBOXFILE File Definition (FD); change the RECORD CONTAINS
clause and the picture clause on the 01 level LBOX-RECORD. This is only
necessary if record length is being modified.
2. Modify the 05-level and 07-level variables under the 03 level WS-LBOX-RECORD
in the WORKING-STORAGE SECTION. Keep in mind that the different record
types were defined using a REDEFINES clause. When the length of the 05 level
LBOX-DATA (length 76) is added to the length of the 05 levels LBOX-BATCH-
NUMBER (length 3) and LBOX-RECORD-TYPE (length 1), the total is 80.
Therefore, any change in record length must be accounted for when
redefining.
4. Keep in mind that any references, whether direct (i.e., the field itself) or
implied (e.g., hold fields), to fields that have been modified or deleted, must
be modified or removed
An internal table, used to display information about what was contained on the lock
box file, is loaded in paragraph MBI-LOAD-BATCH-TABLE. The table can hold
information for a maximum of 100 batches. If your input file contains more than
100 batches, modify the OCCURS clause on the 03 level BATCH-INFO and change the
reference to 100 in MBI-LOAD-BATCH-TABLE.
The record layout for the extract record, which is passed to a sort program and a
print program, resides in the include module TSRLBOXO. If any changes are made
to the extract record, the sort program (TSRSORT) and the print program
(TSRPDRV) must be modified to accommodate the changes.
Note: The program has been changed to insert a year 2000 compliant date into
TBRLBOX when reading from TAPE. There is a SUBSTR function used
and the format for the SUBSTR is YYMMDD. So the date being read from
the tape should be in YYMMDD format. This gets inserted into
TBRLBOX_BATCH_TRANS_DATE with appropriate century. If the format is
different on the tape then the code for the SUBSTR function needs to be
changed
If the value of record type has been changed in TSRLBOX, the Lock Box Correction
Form (TSALBOX) must also be modified. Specifically:
Chapter 4 Conversion
To successfully convert your data, you should have a basic understanding of the SCT
Banner Data Element Dictionary (DED), and a report called 'Tables and Views'. You
should print hard copies of the General DED and the Accounts Receivable DED
when SCT delivers each new tape.
On the following pages are the conversion tables you need to convert your data for
SCT Banner Accounts Receivable.
Step 1 Add IDs using the Identification Form.
Step 2 Populate the Detail Charge/Payment Code Definition Table
(TBBDETC) and the Detail Code Account Definition Table
(TBRACCT) using the Detail Code Control Form. If you will be
loading transactions in detail, you must build an entry for each
unique detail code contained in your existing file. If you will be
loading only summary information, you only need to build one or
two codes. You would create two if you will identify credits with a
detail code different from charges. You would build one if you use
the same detail code for credits or charges.
For example: BFWP - Balance forward payment, BFWC - Balance
forward charge, or BFWD - Balance forward.
TBRACCD_RECEIPT_NUMBER Null.
TBRACCD_TRAN_NUMBER_PAID Null.
TBRACCD_CROSSREF_PIDM Null.
TBRACCD_CROSSREF_NUMBER Null.
TBRACCD_CROSSREF_DETAIL_CODE Null.
TBRACCD_CRN Null.
TBRACCD_CROSSREF_SRCE_CODE Null.
TBRACCD_LOC_MDT Null.
TBRACCD_LOC_MDT_SEQ Null.
TBRACCD_RATE Null.
TBRACCD_UNITS Null.
TBRACCD_DOCUMENT_NUMBER Null.
TBRACCD_PAYMENT_ID Null.
TBRACCD_INVOICE_NUMBER Null.
TBRACCD_INV_NUMBER_PAID Null.
TBRACCD_CURR_CODE Null.
TBRACCD_EXCHANGE_DIFF Null.
TBRACCD_FOREIGN_AMOUNT Null.
TBRACCD_LATE_DCAT_CODE Null.
TBRACCD_FEED_DATE Null.
TBRACCD_FEED_DOC_CODE Null.
Note: If you wish the transactions you create to appear in detail when
statements are produced, these fields must be null. If you wish them to
appear in summary as a previous balance, you should include the system
date excluding hours, minutes, and seconds.
If you run these transactions through the Accounting Feed Process (TGRFEED),
supply the following values for these columns:
All transactions you create during a given conversion run must have the same value
for the TBRACCD_ENTRY_DATE and TBRACCD_CSHR_END_DATE. You also need to
create an entry in the Cashier Session Table with the following values:
Run the Cashiering Report (TGRCSHR) to verify your work. Once satisfied, proceed
by running the Accounting Feed Process (TGRFEED).
In its enhancement of the Accounts Receivable module, SCT added three data
elements to the Detail Code Table (TBBDETC) to process Title IV credits and
returns. These elements must be populated to use the new features related to
handling Title IV credits in application of payments and refunding.
Furthermore, SCT added one data element to the Accounts Receivable Detail Table
(TBRACCD), to be used in calculating original charges for Title IV returns. This
data element needs to be updated for any term(s) for which calculations are likely
to be made under the new methodology.
Index
A ordering
ActionLine viii
ActionWeb viii
Accounting Feed Options 4-4 address viii
Accounting Feed Process (TGRFEED) 4-4 E-mail viii
Accounts Receivable Collector/Temporary Tables 1-7 telephone viii
Accounts Receivable Processing Database Schematic related documentation
diagram 1-2 Accounts Receivable Release Guide vi
list of tables 1-5 Accounts Receivable Upgrade Guide vi
Accounts Receivable Release Guide vi Accounts Receivable User Guide vi
Accounts Receivable Upgrade Guide vi Documentation Bookshelf Implementation Guide
vi
Accounts Receivable User Guide vi
General Technical Reference Manual vi, 2-12
ActionLine viii
General User Guide vi
ActionWeb ix GTVSDAX with Object Access Implementation
Auto/Hold Release Setup ERD 1-9 Guide vi
Automated Clearing House (ACH) Documentation Bookshelf Implementation Guide vi
diagram 1-4
list of tables 1-5
E
C
education centers x
electronic documentation vii
Cashiering Report (TGRCSHR) 4-4 entity relationship diagrams
CMS 2-9 see ERDs
Collector File Entries 2-11 ERDs
Consulting/Modification Services x Auto/Hold Release Setup 1-9
consulting/modification services x Detail Code Setup 1-10
Conversion 4-1 Exemption Setup 1-12
Conversion Tables 4-1 Third Party Contract Setup 1-11
Detail Code Control Form 4-1 Exemption Setup 1-12
TBBDETC Detail Charge/Payment Code Definition
Table 4-1
TBRACCD Account Detail Table 4-2
TBRACCT Detail Code Account Definition Table 4-1 F
I R
S
N
Setting 2-8
Sleep/Wake Maintenance Form (GJASWPT) 2-10
naming conventions vi
Sleep/Wake-up processes 2-8
changing the interval 2-10
collector tables 2-10
operating without sleep/wake-up commands 2-10
O OS command scripts 2-8
reports and processes 2-9
online documentation vii setting up
Online Help v Method One 2-8
Oracle Reports, running 2-12 Method Two 2-9
stopping the process 2-10
Ordering Information
viewing statistics 2-10
Related Documentation vii
SQL*Plus scripts 2-8, 2-12
OS command scripts 2-8
System Distribution Initialization Information Form
(SOADEST) 2-9
System Distribution Initialization Information Form
P (TOADEST) 2-9
VMS 2-9