Banner Finance Release Guide

Transcription

1 Banner Finance Release Guide January 2007 Release 7.3 What can we help you achieve?

2 Confidential Business Information This documentation is proprietary information of SunGard Higher Education 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 SunGard Higher Education. Prepared By: SunGard Higher Education 4 Country View Road Malvern, Pennsylvania United States of America SunGard. 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, SunGard Higher Education is not rendering legal, accounting, or other similar professional services. SunGard Higher Education 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. Without limitation, SunGard, the SunGard logo, Banner, Campus Pipeline, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks referenced herein are trademarks or registered trademarks of their respective owners.

3 Release Guide Finance System Section 1 Introduction Enhancements for Release Prerequisites Related Documentation Section 2 Invoice APIs - Functional Overview Section 3 Journal Voucher APIs - Functional Overview Changed Forms Automatic Journal Voucher (FGAAUTO) Journal Voucher Entry (FGAJVCD) Journal Voucher Mass Entry (FGAJVCM) Journal Voucher Quick (FGAJVCQ) Journal Voucher Summary (FGIJSUM)/ List of Suspended Journal Vouchers (FGIJVCD) Document Approval Form (FOAAINP) Document by User (FOADOCU) User Approval Form (FOAUAPP) Journal Voucher Approval Form (FOQJVCD) Section 4 Invoice APIs - Technical Overview Business Process APIs

4 Table of Contents New API Packages Changed API Packages New Finance Common Packages ffkedit (ffkedi1.sql/ffkedit.sql) ffkrulp (ffkrulp.sql/ffkrul1.sql) Changed Finance Common Packages fb_commodity (fokb_comm1.sql) fb_common (fokb_common0.sql/fokb_common1.sql) fb_common_strings (fokb_common_s0.sql/fokb_common_s1.sql) fb_ftvdisc (fvkb_ftvdisc0.sql) fb_purchase_order (fpkb_order0.sql/fpkb_order1.sql) ffkfoap (ffkfoa1.sql/ffkfoap.sql) foksels (foksel1.sql/foksels.sql) foktext (foktext.sql/foktex1.sql) fokutil (fokutil.sql/fokuti1.sql) Other Packages fpkpurr (fpkpur1.sql) Changed Processes fabchka.pc fabmatc.pc fapinvt.pc fgaprot.h fgpbody.pc fgractg.pc fgrtrni.pc forappl.pc furapay.pc Other Changes Check Cancellation Form (FAACHKS) Invoice/Credit Memo Cancel Form (FAAINVD) Finance Release 7.3 January Release Guide Confidential

5 Table of Contents Payment Control Form (FAAPAYC) Recurring Payables Form (FAARUIV) Document Approval Form (FOAAINP) Document by User (FOADOCU) User Approval Form (FOAUAPP) Invoice/Credit Memo Approval Form (FOQINVA) Receipt Required Indicator (FPARRIM) Section 5 Journal Voucher APIs - Technical Overview New Packages Changed Processes fgractg.pc fgrtrni.pc forappl.pc Finance Common Packages Other Changes Section 6 Miscellaneous Enhancements Regulatory Update Changed Forms Batch Check Print Form (FAABATC) On-line Check Print Form (FAAONLC) Reclassification Entry Form (FGARCLE) User Profile Maintenance Form (FOMPROF) Journal Voucher Approval Form (FOQJVCD) Changed Library Finance Library (FOQOLIB) Changed Processes furfeed.pc Changed Views favvic2.sql Obsolete Banner Views Finance Release 7.3 January Release Guide Confidential

6 Table of Contents New Scripts frc06091.sql frc06092.sql frc06093.sql RPEs Section 7 Problem Resolutions Accounts Payable Budget Development Fixed Assets General Ledger Operations Purchasing and Procurement Research Accounting Utilities Validation Tables Miscellaneous Finance Release 7.3 January Release Guide Confidential

7 Section 1 Introduction Enhancements for Release 7.3 Section 1 Introduction This guide documents Release 7.3 of the Banner Finance System. Release 7.3 includes enhancements, regulatory updates, RPEs, and problem resolutions. Note: In this release many processes, forms, and packages are listed in more than one section. Please review the entire document to learn about all changes to specific objects. Enhancements for Release 7.3 This document describes the following enhancements. Invoice APIs New and revised Invoice APIs are identified. Journal Voucher APIs Information about new Journal Voucher APIs is included. Miscellaneous Enhancements Enhancements are identified, including the 1099 regulatory changes to FAM1099, RPEs, information about new scripts, and changes to multiple forms, libraries, and views. Problem Resolutions Problem resolutions are described. Prerequisites Before you install and use Finance Release 7.3, you must first install the following software: General Release 7.3 January 2007 Finance Release 7.3 Confidential Release Guide 7

8 Section 1 Introduction Related Documentation Related Documentation In addition to the Banner Finance 7.3 Release Guide, you may want to refer to the following documentation. Banner General Release Guide, Release 7.3 Finance Release 7.3 January Release Guide Confidential

9 Section 2 Invoice APIs - Functional Overview Section 2 Invoice APIs - Functional Overview SunGard Higher Education is delivering business process APIs for invoices with Banner Finance Release 7.3. Banner Finance Release 7.3 provides both the completion logic and the necessary functionality to satisfy business rules/actions and edits across tables. With this release, it is possible to develop local scripts to invoke the APIs and create Banner invoices with external data. This release represents the second building block of a planned multiple-phased approach delivery of Invoice APIs. With this release, most functions and processes have been modified to implement the invoice APIs. The invoice forms (FAAINVE, FACICON) will be modified in the future to implement the APIs and will be made available through electronic distribution. Although a number of Banner Finance forms that perform create, update, or delete functions have been modified to use the APIs, no changes have been made to these forms that affect navigation or function. The modifications made are of a technical nature and are not visible to the end user. For information about these changes, please refer to the Invoice APIs - Technical section labelled Other Changes on page 24. January 2007 Finance Release 7.3 Confidential Release Guide 9

10 Section 2 Invoice APIs - Functional Overview This page intentionally left blank Finance Release 7.3 January Release Guide Confidential

11 Section 3 Journal Voucher APIs - Functional Overview Section 3 Journal Voucher APIs - Functional Overview SunGard Higher Education is delivering both business entity and process level APIs with Banner Finance Release 7.3. These APIs support journal voucher functionality. Enhancements to journal vouchers are also being delivered with this release. Changed Forms With this release, both functional and technical changes have been incorporated into the Banner Finance forms used for journal vouchers. To simplify information access, all these forms changes are included in this section. For information about closed RPEs and defects that impact the journal voucher forms, please refer to Miscellaneous Enhancements on page 31 and Problem Resolutions on page 37. Automatic Journal Voucher (FGAAUTO) A display of the status of the individual journal vouchers associated with the automatic journal voucher has been added to this form. This ensures that you will be made aware if any incomplete journal vouchers exist. Incomplete journal vouchers need to be addressed via FGAJVCD before the next submission can run. Journal Voucher Entry (FGAJVCD) Journal Voucher Mass Entry (FGAJVCM) Journal Voucher Quick (FGAJVCQ) Changed Fields The following obsolete fields have been removed from both FGAJVCD and FGAJVCQ: Pool COA Pool Fund January 2007 Finance Release 7.3 Confidential Release Guide 11

12 Section 3 Journal Voucher APIs - Functional Changed Forms Code Consolidation Code from these forms has been consolidated in database functions and procedures to improve efficiency and consistency. This includes rules enforced in the new APIs for JV_HEADER and JV_DETAIL, as well as Rule Class Process Code editing via FFKRULP, Rule Class Edits and defaults via FFKEDIT, validation and security of FOAPAL information via FFKFOAP, and various utilities in FOKUTIL and FOKSELS. Copy Journal Voucher When creating a journal voucher, you may now use the icon in the header or the options menu of these forms to copy an existing journal voucher. An existing journal voucher refers to a journal voucher that is either in process or has already been posted. Note: This change addresses the following RPEs: #CMS-RPE13033, #CMS-RPE19874, and #CMS-RPE Copy Journal You may now copy a journal from the journal voucher forms using the following process. 1. Select the Copy Journal option from the options menu or press the Copy icon. 2. Enter the source journal voucher document number. 3. Enter a new document number, leave this field blank or enter NEXT to generate a new document number. 4. Change the transaction date as required (the default value is the current date). 5. You may reverse the entry. Select the Reverse JV check box to create the new journal with the opposite sign from the Copy From journal. 6. Optional: Select the Copy Text check box to copy header text from the source journal voucher. 7. Select OK. Finance Release 7.3 January Release Guide Confidential

13 Section 3 Journal Voucher APIs - Functional Changed Forms Workflow Complete If a journal voucher (JV) is completed as part of a workflow activity, an Information Alert will display to advise the user of the disposition of the JV. The workflow activity is submitted as complete. Journal Voucher Summary (FGIJSUM)/ List of Suspended Journal Vouchers (FGIJVCD) The Document Number field has been expanded. The Sequence Number fields can no longer be updated after the sequence number has been assigned and is visible to the user. Properties have been changed to reflect that these are query-only forms. Document Approval Form (FOAAINP) Document by User (FOADOCU) User Approval Form (FOAUAPP) When a previously completed journal voucher that has been routed into the Finance approvals process is disapproved, the journal is reset to incomplete so you may edit the disapproved journal. The update of the indicators in the journal voucher header and detail tables is performed by invoking the APIs. January 2007 Finance Release 7.3 Confidential Release Guide 13

14 Section 3 Journal Voucher APIs - Functional Changed Forms Journal Voucher Approval Form (FOQJVCD) Updates to the NSF indicator are now performed through the API. Finance Release 7.3 January Release Guide Confidential

15 Section 4 Invoice APIs - Technical Overview Section 4 Invoice APIs - Technical Overview New application programming interfaces (API) and supporting database packages have been delivered with this release. Other supporting database packages for APIs have also been reissued. Each new API for a database table comprises database packages that contain the validation rules and other related processing for the table. Business Process APIs The Banner business process APIs are new with 7.3. These APIs span calls to multiple Banner business entity APIs within a single transaction. For example, you can now invoke APIs to create a multiple vendor invoice against a purchase order. The business process APIs play a significant role in processing wrap up and balancing routines necessary for completion of invoices, as well as the creation and update of all types of invoices. These APIs aggregate the rows created by the business entity APIs in each of the invoice base tables, evaluate all data required to establish a complete invoice document in Banner Finance, and perform cross-table updates across multiple tables and forms. New API Packages For detailed information about these new APIs, please refer to the API technical documentation available via the Customer Support Center. Object Name Entity Name Task Performed Associated Tables Associated Packages fp_invoice (fakp_invoice0.sql/ fakp_invoice1.sql) INVOICE Common Business interface for the composite entity Invoice (FP_INVOICE). Invoice Tables: FABINVH FARINVA FARINVC FARINTX fp_invoice_strings (fakp_invoice_s0.sql/ fakp_invoice_s1.sql) Provides error messages and error message functions for INVOICE. January 2007 Finance Release 7.3 Confidential Release Guide 15

16 Section 4 Invoice APIs - Technical Changed API Packages Changed API Packages All Invoice API packages delivered with 7.2 have been revised and reissued to implement the second phase of the Invoice API enhancement. These packages now include edits for the create, update, and delete of a single row of the relevant entity. In addition, new procedures and functions have been added that are essential for code consolidation. Note: For detailed information about these APIs, please refer to the API technical documentation available via the Customer Support Center. Object Name Entity Name Task Performed Associated Tables Associated Packages fb_invoice_header (fakb_invhead0.sql/ fakb_invhead1.sql) INVOICE_ HEADER Common Business interface for the Invoice Header (INVOICE_ HEADER). Invoice Header Table (FABINVH) fb_invoice_ header_strings (fakb_invhead_s0.sql/ fakb_invhead_s1.sql) Provides error messages and error message functions for INVOICE_HEADER. fb_invoice_ header_rules (fakb_invhead_r0.sql/ fakb_invhead_r1.sql) Provides supporting subprograms for INVOICE_HEADER. dml_fabinvh (fokd_fabinvh0.sql/ fokd_fabinvh1.sql) Provides the procedures to insert, update, and delete from various Banner tables. Finance Release 7.3 January Release Guide Confidential

17 Section 4 Invoice APIs - Technical Changed API Packages Object Name Entity Name Task Performed Associated Tables Associated Packages fb_invoice_item (fakb_invitem0.sql/ fakb_invitem1.sql) INVOICE_ITEM Common Business interface for the Invoice Item (fb_invoice_ item). Invoice Commodity Table (FARINVC) fb_invoice_item_ strings (fakb_invitem_s0.sql/ fakb_invitem_s1.sql) Provides error messages and error message functions for INVOICE_ITEM. fb_invoice_item_ rules (fakb_invitem_r0.sql/ fakb_invitem_r1.sql) Provides supporting subprograms for INVOICE_ITEM. dml_farinvc (fokd_farinvc0.sql/ fokd_farinvc1.sql) Provides the procedures to insert, update, and delete from various Banner tables. January 2007 Finance Release 7.3 Confidential Release Guide 17

18 Section 4 Invoice APIs - Technical Changed API Packages Object Name Entity Name Task Performed Associated Tables Associated Packages fb_invoice_acctg (fakb_invacctg0.sql/ fakb_invacctg1.sql) INVOICE_ACCTG Common Business interface for the Invoice Accounting (fb_invoice_ acctg). Invoice Accounting Table (FARINVA) fb_invoice_acctg_ strings (fakb_invacctg_s0.sql/ fakb_invacctg_s1.sql) Provides error messages and error message functions for INVOICE_ACCTG. fb_invoice_acctg_ rules (fakb_invacctg_r0.sql/ fakb_invacctg_r1.sql) Provides supporting subprograms for INVOICE_ACCTG. dml_farinva (fokd_farinva0.sql/ fokd_farinva1.sql) Provides the procedures to insert, update, and delete from various Banner tables. Finance Release 7.3 January Release Guide Confidential

19 Section 4 Invoice APIs - Technical New Finance Common Packages Object Name Entity Name Task Performed Associated Tables Associated Packages fb_invoice_tax (fakb_invtax0.sql/ fakb_invtax1.sql) INVOICE_TAX Common Business interface for the Invoice Tax (FB_INVOICE_ TAX). Invoice Tax Allocation Table (FARINTX) fb_invoice_tax_ strings (fakb_invtax_s0.sql/ fakb_invtax_s1.sql) Provides error messages and error message functions for INVOICE_TAX. fb_invoice_tax_ rules (fakb_invtax_r0.sql/ fakb_invtax_r1.sql) Provides supporting subprograms for INVOICE_TAX. dml_farintx (fokd_farintx0.sql/ fokd_farintx1.sql) Provides the procedures to insert, update, and delete from various Banner tables. New Finance Common Packages The following new packages may be used across all Finance modules. ffkedit (ffkedi1.sql/ffkedit.sql) This package consolidates the editing and defaulting for Rule Class edits. ffkrulp (ffkrulp.sql/ffkrul1.sql) This package contains editing routines for Rule Process codes. January 2007 Finance Release 7.3 Confidential Release Guide 19

20 Section 4 Invoice APIs - Technical Changed Finance Common Packages Changed Finance Common Packages The following changed packages may be used across all Finance modules. fb_commodity (fokb_comm1.sql) The Where clause of the query functions was corrected. fb_common (fokb_common0.sql/fokb_common1.sql) A new Finance record, error record, associated table types, and additional utility functions and procedures were added to this package in support of the APIs. fb_common_strings (fokb_common_s0.sql/fokb_common_s1.sql) Documentation was added for the Finance internal update failure error string. fb_ftvdisc (fvkb_ftvdisc0.sql) Syntax and semantic errors were corrected for API technical documentation. fb_purchase_order (fpkb_order0.sql/fpkb_order1.sql) The f_is_po_inventory function was added to return the inventory indicator. ffkfoap (ffkfoa1.sql/ffkfoap.sql) A new parameter (jv_ind) was added for the p_validate_foapal and p_validate_accounting procedures to bypass the edit of the account code's data entry indicator. The JV Detail Rules package will perform this edit to enable use of Budget Only account codes when appropriate. Finance Release 7.3 January Release Guide Confidential

21 Section 4 Invoice APIs - Technical Changed Finance Common Packages For feeds from other systems to be processed, rule group and fund/org security in p_validate_accounting are bypassed if the journal voucher process context is INTERFACE. Parameters (user_id and check_user_auth) have been added to the p_validate_foapal and p_validate_fund procedures. If check_user_auth is set to Y and the transaction date falls between the termination and expenditure end dates, then the user should have the authority to post within that time period. foksels (foksel1.sql/foksels.sql) A new function (f_get_ftvsdat_data) was added to return ftvsdat_data from FTVSDAT. A new cursor (GetActlC) and function (p_get_ftvactl_rec) were added to retrieve FTVACTL records. A new cursor (GetFspdC) and function (p_get_ftvfspd_rec) were added to retrieve FTVFSPD records. A new cursor (GetFsyrC) and function (p_get_ftvfsyr_rec) were added to retrieve FTVFSYR records. The FOAPAL selection for term_date was changed from greater than (>) to greater than or equal to (>=) so that transaction and termination dates both set to 23:59:59 will match. foktext (foktext.sql/foktex1.sql) A new function (f_exists) was created to check to see if text exists. fokutil (fokutil.sql/fokuti1.sql) Support for Finance APIs was added, as follows: p_insert_fobdinp was added to insert records into the Document In Progress table; and p_insert_fgrtrnr was added to insert records into the Error Message table. A new procedure was added: p_get_fsyr_fspd. An optional parameter (p_user_id) was added for p_validate_transdate. January 2007 Finance Release 7.3 Confidential Release Guide 21

22 Section 4 Invoice APIs - Technical Other Packages The submission number check was removed from the where clause and only the NOOP rule class is now used for reversal. This change ensures that the p_reverse_abal procedure reverses abal correctly for invoice documents. The call to p_ validate_transdate in the p_is_foap_postable procedure was modified to pass in the user ID. This will ensure that the e-procurement documents will not post in the accrual period if the user does not have accrual period posting authorization. Other Packages fpkpurr (fpkpur1.sql) Calls to p_validate_foapal and p_validate_transdate have been modified to take into account the new parameters for these procedures. Changed Processes fabchka.pc This process was modified to invoke the invoice APIs to perform updates to the invoice tables. fabmatc.pc All updates to FABINVH and FARINVC were modified to use the APIs. fapinvt.pc Invoice creation business logic was removed and replaced with calls to the invoice business process API. All codes from this process have been consolidated into the database package procedure FP_INVOICE.p_create_pcard_invoices. This process will now get the parameters from the user either via job submission or the host prompt, and will pass these parameters to the above named procedure which will perform the processing. Finance Release 7.3 January Release Guide Confidential

23 Section 4 Invoice APIs - Technical Changed Processes Declarations and definitions were removed for all unused variables, procedures, and functions. Calls to select the job submission parameters were replaced with the function in fb_common. The control report will now print the invoice document numbers created for the procurement card transactions. If any errors were raised during processing, the control report will also list the errors. fgaprot.h A new function (local_postora_api) was added in support of API error message handling for batch processes. fgpbody.pc All updates to FABINVH, FARINVC, FARINVA, and FARINTX were replaced with API calls. fgractg.pc All updates to FABINVH, FARINVC, FARINVA, and FARINTX were replaced with API calls. fgrtrni.pc This process has been modified to invoke invoice entity API procedures to perform data changes on the invoice tables. forappl.pc Direct updates to the invoice header table and invoice accounting table were replaced with calls to the invoice header and invoice accounting APIs, respectively. When final approval of the invoice is given, the update to the approval indicator in the two tables is performed via the APIs using the appropriate context. furapay.pc This process has been rewritten to use the invoice APIs. All unused variables, procedures and function declarations and definitions have been deleted. The furapay business logic has been consolidated into the database package procedure, January 2007 Finance Release 7.3 Confidential Release Guide 23

24 Section 4 Invoice APIs - Technical Other Changes FP_INVOICE.p_Create_refund_invoices. The furapay process now invokes this API. All process-level code that is now being performed by the API has been deleted. The business process API invokes the entity level invoice APIs to create the invoice records in the database. It then calls the completion business process FP_INVOICE.p_complete to perform the necessary wrap up logic and forwards the invoices to the posting process. The consolidated logic also invokes the consolidated procedures to perform the rule class edits. Changes for PLUS Loan Refunds introduced in (CMS-RPE30164, CMS-RPE38415, and #1-G6179) were also moved into p_create_refund_invoices. Other Changes With this release, modifications have been made to a number of Banner Finance forms to invoke invoice APIs. These changes are of a technical nature and are not visible to the user. There have been no changes made to these forms that affect navigation or function. The invoice business entity is a complex structure consisting of a single invoice header (FABINVH) having multiple items (FARINVC), accounting elements (FARINVA), and tax information (FARINTX). Various Banner forms and processes perform updates on multiple items and accounting rows at the same time. To accommodate the multiple row updates, the entity APIs for the invoice item and accounting tables now contain a procedure called p_update_internal. This procedure has been made context-sensitive to ensure data integrity. Similar functionality can also be found in the invoice header API, which handles the cancellation of invoices for a given check and bank. Check Cancellation Form (FAACHKS) Direct updates to the invoice tables from this form have been moved into the API in the p_update_internal procedure. Using the appropriate context, the form invokes the API. Invoice/Credit Memo Cancel Form (FAAINVD) This form has been modified to invoke the invoice cancellation business process API, FP_INVOICE.p_cancel. In addition, all edits and cancellation logic code embedded in the form have been removed, since that logic will now be performed by the API. Unused form items, blocks, and canvasses have also been removed. Finance Release 7.3 January Release Guide Confidential

25 Section 4 Invoice APIs - Technical Other Changes The form no longer updates fiscal year, fiscal period, and rule classes in the invoice accounting table; this task is now performed by the posting process when the cancellation is posted to the ledgers. If the posting of the cancellation rolls back for any reason, this change enables data to return to its previous state. If a rollback of the cancellation occurs, the posting process updates the hold status of the invoice document to Y. Then the invoice will not be selected for processing checks. Payment Control Form (FAAPAYC) The payment control will now update the invoice payment due date and hold indicator in the invoice header table (FABINVH) by invoking the invoice header API using the appropriate context. Similarly, if the hold indicator of an invoice item is being set or reset, the update of the hold indicator in the invoice item table (FARINVC) will be performed by the invoice item API using the appropriate context. Recurring Payables Form (FAARUIV) When the next submission date has been modified, the payment due date in the invoice header table is updated to the next submission date by calling the invoice header API using the appropriate context. Document Approval Form (FOAAINP) Document by User (FOADOCU) User Approval Form (FOAUAPP) When a previously completed invoice document that has been routed into the Finance approvals process is disapproved, the invoice is reset to incomplete so you may edit the disapproved invoice. The update of the invoice indicators in the invoice header and accounting tables is performed by invoking the invoice header and accounting APIs. Invoice/Credit Memo Approval Form (FOQINVA) Triggers have been added under the FARINVA block to apply invoice APIs for the update. Receipt Required Indicator (FPARRIM) When an invoice document that has been routed to the matching process must be reset and forwarded to the posting process, the update to the match required indicator and completion indicator in the invoice header table (FABINVH) is now performed by invoking the invoice header API. January 2007 Finance Release 7.3 Confidential Release Guide 25

26 Section 4 Invoice APIs - Technical Other Changes This page intentionally left blank Finance Release 7.3 January Release Guide Confidential

27 Section 5 Journal Voucher APIs - Technical Overview Section 5 Journal Voucher APIs - Technical Overview New application programming interfaces (API) and supporting database packages have been delivered with this release. Other supporting database packages for APIs have also been reissued. Each new API for a database table comprises database packages that contain the validation rules and other related processing for the table. New Packages Note: For detailed information about each of these APIs, please refer to the API technical documentation available via the Customer Support Center. Object Name Entity Name Task Performed Associated Table Associated Packages fb_jv_header (fgkb_jvhead0.sql/ fgkb_jvhead1.sql) JV_HEADER Common Business interface for the Journal Voucher Header API (JV_HEADER). Journal Voucher Header Table (FGBJVCH) fb_jv_header_strings (fgkb_jvhead_s0.sql/ fgkb_jvhead_s1.sql) Provides error messages and error message functions for JV_HEADER. fb_jv_header_rules (fgkb_jvhead_r0.sql/ fgkb_jvhead_r1.sql) Provides supporting subprograms for JV_HEADER. dml_fgbjvch (fokd_fgbjvch0.sql/ fokd_fgbjvch1.sql) Provides the procedures to insert, update, and delete from various Banner tables. January 2007 Finance Release 7.3 Confidential Release Guide 27

28 Section 5 Journal Voucher APIs - Technical Changed Processes Object Name Entity Name Task Performed Associated Table Associated Packages fb_jv_detail (fgkb_jvdetail0/sql/ fgkb_jvdetail1.sql) JV_DETAIL Common Business interface for the Journal Voucher Detail API (JV_DETAIL). Journal Voucher Detail Table (FGBJVCD) fb_jv_detail_strings (fgkb_jvdetail_s0.sql/ fgkb_jvdetail_s1.sql) Provides error messages and error message functions for JV_DETAIL. fb_jv_detail_rules (fgkb_jvdetail_r0.sql/ fgkb_jvdetail_r1.sql) Provides supporting subprograms for JV_DETAIL. dml_fgbjvcd (fokd_fgbjvcd0.sql/ fokd_fgbjvcd1.sql) Provides the procedures to insert, update, and delete from various Banner tables. fp_journal_voucher (fgkp_journal0.sql/ fgkp_journal1.sql) JOURNAL_ VOUCHER Process API for Journal Vouchers (JOURNAL_ VOUCHER). Journal Voucher Tables (FGBJVCH/ FGBJVCD) fp_journal_voucher_ strings (fgkp_journal_s0.sql/ fgkp_journal_s1.sql) Provides error messages and error message functions for JOURNAL_VOUCHER. Changed Processes fgractg.pc If journals are unable to post, they are reset via the API. When a journal posts, it is now deleted via the API. Finance Release 7.3 January Release Guide Confidential

29 Section 5 Journal Voucher APIs - Technical Finance Common Packages fgrtrni.pc The Finance Interface Process (FGRTRNI) Creates journals from the interface table, as populated by FURFEED or other interface processes. Creates iterations of automatic journal vouchers, and Processes deferred edits of journals. Note: If a client has Rule Class Security turned on, and then uses deferred editing of journals, the person who creates a deferred journal voucher must be authorized to use the rule classes with FGAJVCD. This is true whether the deferred journal is entered on FGAJVCD, FGAJVCQ, or FGAJVCM. forappl.pc Updates to the journal voucher header table were replaced with calls to the journal voucher header API. When final approval is made, the updates to the journal tables are made via the APIs. Finance Common Packages For a list of packages that may be used across all Finance modules, refer to the section labelled Changed Finance Common Packages on page 20. Other Changes With this release, modifications have been made to a number of Banner Finance forms used for journal vouchers that are of a technical nature and are not visible to the user. Since functional changes were also made to many of these forms, all journal voucher forms changes are included in the Journal Voucher APIs - Functional section. Refer to Changed Forms on page 11. January 2007 Finance Release 7.3 Confidential Release Guide 29

30 Section 5 Journal Voucher APIs - Technical Other Changes This page intentionally left blank Finance Release 7.3 January Release Guide Confidential

31 Section 6 Miscellaneous Enhancements 1099 Regulatory Update Section 6 Miscellaneous Enhancements This section identifies miscellaneous enhancements to Banner Finance included in Release Regulatory Update The 1099Misc IRS file layout has been modified for 2006 tax reporting. This change affects the 1099 Magnetic File Build Process (FAM1099), and includes parameter changes Magnetic File Build/Tape Summary Audit Report (FAM1099) Changed Parameters The descriptions for two FAM1099 parameters have changed with this release. Parameter Number Parameter Description Reason for Change 06 Not used at this time (formerly, Replacement Alpha Character) The replacement alpha character is no longer captured. 07 Not used at this time (formerly, Electronic File Name) The electronic file name is no longer captured. Changed Forms Batch Check Print Form (FAABATC) The Perform Accounting check box has been deleted, since it is no longer needed. January 2007 Finance Release 7.3 Confidential Release Guide 31

32 Section 6 Miscellaneous Enhancements Changed Library The Print Test Pattern and Process/Print check boxes have been changed to icons. When selected, you can now test alignment of your check or print checks without having to select SAVE. On-line Check Print Form (FAAONLC) The Print Test Pattern and Process/Print Check check boxes have been changed to icons. You can now test alignment of your check or print checks without having to select SAVE. Reclassification Entry Form (FGARCLE) The G$_OPT_GROUP object group was subclassed from the GOQOLIB library. User Profile Maintenance Form (FOMPROF) The label for the expenditure end date check box has been changed to Expenditure End Date Posting. Journal Voucher Approval Form (FOQJVCD) The Document Number, Reference Document Number, Deposit Number and Encumbrance Number fields have been expanded. Changed Library Finance Library (FOQOLIB) The Order by clause in record group FTVAGCY_RG was changed from ftvagcy_agcy_code_pidm to spriden_id asc. Finance Release 7.3 January Release Guide Confidential

33 Section 6 Miscellaneous Enhancements Changed Processes Changed Processes furfeed.pc The select was changed to get four digits to ensure proper display in the report heading. Changed Views favvic2.sql This view, used in the Vendor Detail History Form (FAIVNDH), has been modified to include columns for both invoice date and transaction date. Obsolete Banner Views The following Banner views, which were used in available balance processing prior to Release 3.1, have been deleted from this release. fgvbva1.sql fgvbvat.sql fgvbvb1.sql fgvbvbd.sql fgvbvac1.sq fgvbvcc.sql fgvbvck.sql fgvbve1.sql fgvbve2.sql fgvbve3.sql fgvbvee.sql fgvbvfd.sql fgvbvii.sql fgvbvo1.sql fgvbvoo.sql fgvbvor.sql fgvbvrp.sql fgvbvw1.sql January 2007 Finance Release 7.3 Confidential Release Guide 33

34 Section 6 Miscellaneous Enhancements New Scripts fgvbvw2.sql fgvbvw3.sql fgvbvw4.sql fgvbvyp.sql New Scripts frc06091.sql This script for CFDA data will insert new programs that are not already in the database, based on the September 2006 Print Edition. frc06092.sql This script will update CFDA descriptions of existing rows, based on the September 2006 Print Edition. If a program does not exist, it will be added. frc06093.sql This script will update the status to Inactive for CFDA codes made obsolete in the September 2006 print edition. RPEs FGAJVCQ (#CMS-RPE48273) The descriptions on the FGAJVCQ form are removed if the FOAPAL code is removed. FRABUDP/ FOMPROF/ FPARDEL/ FPAPDEL/ FPACDEL (#CMS-RPE#1-SV1RJ) Tabs were added to these forms to improve navigation and to simplify information access. Finance Release 7.3 January Release Guide Confidential

35 Section 6 Miscellaneous Enhancements RPEs FGIDOCR/ FGQDOCN/ FGITRND/ FGIGLAC/ FGAJVCD/ FGAJVCM/ FGAJVCQ/ FGIJSUM/ FGIJVCD (#CMS-RPE47391) The length of the Document Number field was increased to improve usability. FGAJVCD/ FGAJVCQ/ FGAJVCM FGAJVCD (#CMS-RPE13033, #CMS-RPE19874, #CMS-RPE48808) You now have the ability to copy a journal entry (with the ability to change transaction date, total, etc.) and/or reverse a journal entry in progress or that has already been posted. (#CMS-RPE38451) Previously you could create a journal entry using a closed encumbrance, and the document would roll back in Posting. Now, when you enter an encumbrance, changes made to journal voucher detail editing ensure that you receive a message when the encumbrance is closed except when re-opening the encumbrance. FGAJVCD/ FGAJVCM/ FGAJVCQ FGRTRNI (#CMS-RPE29263) Previously, FGAJVCD and FGAJVCQ did not recognize inactivated rule codes. They now correctly reference FTMRUCL effective dates, termination dates, and the inactive indicator. (#CMS-RPE4101) Since you cannot have multiple submissions of an automatic journal voucher in approvals at the same time, FGRTRNI will check the FOAUAPP table. If a previous iteration of an Auto JV is pending approval, FGRTRNI will display an error message and continue with other documents rather than stopping. FGRTRNI (#CMS-RPE25834) FGRTRNI was changed to reduce the frequency and duration of table locks. This will minimize the impact on users who need to create journal vouchers using the journal voucher forms. January 2007 Finance Release 7.3 Confidential Release Guide 35

36 Section 6 Miscellaneous Enhancements RPEs This page intentionally left blank Finance Release 7.3 January Release Guide Confidential

37 Section 7 Problem Resolutions Accounts Payable Section 7 Problem Resolutions This section identifies the changes made to Finance in Release 7.3 to resolve system defects. Defects are listed by module. Accounts Payable FAACHKS FAAINVD/ FGRACTG FAAINVD/ FGRACTG (#1-M7S6M) Description: FAAINVE allows editing of cancelled invoices. Impact: With certain navigation, FAAINVE permitted you to recomplete an invoice that had been cancelled and not re-established with a check cancellation. Resolution: This form was changed to set the complete and approval indicator to Y when the invoice is not re-established as part of the cancellation. This will prevent users from accessing a cancelled invoice in FAAINVE. (#1-1IIY8R) Description: An issue was encountered with a data processing invoice cancellation in which the invoice rolls back in posting. Impact: Invoice cancellation transactions that fail in posting do not have all data reset correctly in the invoice tables, and are available for check processing. If processed, the check posting fails. Resolution: This form has been modified to invoke the invoice cancellation business process API, FP_INVOICE.p_cancel. In addition, all edits and cancellation logic code embedded in the form have been removed, since that logic will now be performed by the API. Unused form items, blocks, and canvasses have also been removed. The form no longer updates fiscal year, fiscal period, and rule classes in the invoice accounting table; this task is now performed by the posting process when the cancellation is posted to the ledgers. If the posting of the cancellation rolls back for any reason, this change enables data to return to its previous state. If a rollback of the cancellation occurs, the posting process updates the hold status of the invoice document to Y. Then the invoice will not be selected for processing checks. (#1-1IJEJR) Description: The invoice tables are not being updated correctly when an invoice is cancelled in the new year against an invoice and purchase order that were created in the prior year, before the encumbrance roll is done. The invoice cancellation rolls back in posting, but the complete and approved indicators are still set to Y and the cancel indicator and cancel date are nulled out. The invoice is picked up for payment in the next check run, then the check errors out in posting with an ORA 1400 error because the rule code on the invoice is still set to ICEI. Impact: Invoice cancellation transactions that fail in posting do not have all data January 2007 Finance Release 7.3 Confidential Release Guide 37

38 Section 7 Problem Resolutions Accounts Payable reset correctly in the invoice tables, and are available for check processing. If processed, the check posting fails. Resolution: This form has been modified to invoke the invoice cancellation business process API, FP_INVOICE.p_cancel. In addition, all edits and cancellation logic code embedded in the form have been removed, since that logic will now be performed by the API. Unused form items, blocks, and canvasses have also been removed. The form no longer updates fiscal year, fiscal period, and rule classes in the invoice accounting table; this task is now performed by the posting process when the cancellation is posted to the ledgers. If the posting of the cancellation rolls back for any reason, this change enables data to return to its previous state. If a rollback of the cancellation occurs, the posting process updates the hold status of the invoice document to Y. Then the invoice will not be selected for processing checks. FAIINVE FAIINVE FACICON FAIVNDH (#CMS-DFCT102492) Description: The 1099 Income Type field on FAIINVE was blank if the income type was entered or changed on the Additional Header Information page on FAAINVE. Impact: You could not see the income type on FAIINVE. Resolution: The form was changed to query for the income type from the invoice data. (#1-XW7D4) Description: During processing of the vendor invoice on the Invoice Form (FAAINVE), the Direct Deposit Status field would be correctly valued as a Y if the vendor had an appropriate GXADIRD record. However, after the invoice was completed, the Direct Deposit Status field on FAIINVE would not be correctly valued. Impact: The Invoice Query form (FAIINVE) was not displaying correct data in the Direct Deposit Status field. Resolution: The form will now correctly display a Y in the Direct Deposit Status field, if the invoice will be paid via direct deposit (ACH). If payment of the invoice was done by producing a check, the field will display N. (#CMS-DFCT90207) Description: Data in FACICON disappear from the document if you exit the form. Impact: A problem occurs when processing a multiple invoice document as commodity level accounting. If you delete one of the vendor invoice records after accounting records have been created, the accounting records for the deleted vendor invoice are left in FARINVA. Resolution: New code has been added to the FACICON form to delete the related invoice accounting records when a vendor invoice is deleted. (#CMS-DFCT88343) Finance Release 7.3 January Release Guide Confidential

39 Section 7 Problem Resolutions Budget Development Description: Invoices with an invoice date and payment due date on the last day of fiscal year were not displaying on the FAIVNDH form if there was a timestamp other than Impact: Invoices having an invoice and transaction date as the last day of the fiscal year were not being displayed if the time stamp was anything other than Resolution: The timestamp component of the dates retrieved was removed. FAIVNDH FAM1099 FARVALP (#CMS-DFCT64996) Description: Invoice was put in June (FY01) with a due date of July (FY02). It was expected that the invoice would be on FAIVNDH for FY01, but the invoice was only seen in FY02. Impact: Invoices were queried based on payment due date, but they needed to be queried based on transaction date. Resolution: The functionality of the form was changed and two new date fields were added. This enables you to query invoices that have invoice dates between the two dates entered. You can also query with the fiscal year, which retrieves invoices with transaction dates in the fiscal year. (#1-10N23R) Description: This defect enabled the posting of 1099Misc regulatory changes. Impact: 1099Misc regulatory updates were available for client use. Resolution: 1099Misc regulatory changes were posted. (#CMS-DFCT96705) Description: There is no list of values (LOVs) for the parameters on GJAPCTL when running FARVALP. Impact: When you click on the Search button to access the LOV, an error message displays: FRM 40010, cannot read from FTVVTYP. Resolution: The typographical error was corrected; the list of values column for the GJBPDEF table was changed to FTMVTYP from FTVVTYP. Budget Development FBABDRA (#1-6WUN3) Description: On the Accounting Entry Information, account codes are not sorted in the correct order in Banner Finance 7.1, Oracle 10G. Impact: The account codes are not sorted in the correct order. Resolution: An explicit order by fbbblin_acct_code was added to the where clause of the fbbblin block. January 2007 Finance Release 7.3 Confidential Release Guide 39

40 Section 7 Problem Resolutions Fixed Assets Fixed Assets FFRPROP.pc (#1-IQ4P6) Description: An error was received when you ran the Fixed Asset Report (FFRPROP) if the custodian name exceeded 17 characters. Impact: There is only room for 17 characters to print for the custodian name. Resolution: The custodian name size has been restricted to 17 characters. General Ledger FGAAUTO/ FGTRNI FGAAUTO/ FGAJVCD (#1-VY5S1) Description: When the journal voucher associated with an automatic journal voucher is entered but left in process, the Completed, First/Next Submission, and Remaining fields are updated but the journal voucher iteration is not created because the base (0 submission) was not completed. Impact: Recurring journal entries do not process. Resolution: Additional edits look for the situation where an automatic journal voucher is scheduled to run but submission zero has not been completed. FGRTRNR will capture the error and the automatic journal voucher will not be created. Thus, the number of submissions will not be falsely incremented. (#CMS-DFCT90217) Description: Journal vouchers created through the Auto JV form will allow an out-of-balance journal voucher to post, even if using a rule code that has a balance by method. Impact: Journal vouchers created through the Auto JV form will allow an out-of-balance journal to post. Resolution: In the FGAJVCD form, an edit was added to prevent entry into the detail of the base record of a recurring journal (submission 0) while the header status is C' (Complete). Note that you may overtype the Document Total to change the status to I (Incomplete) and make changes, but must re-complete a balanced JV before new submissions will be created. Finance Release 7.3 January Release Guide Confidential

41 Section 7 Problem Resolutions General Ledger FGAJVCD FGAJVCD FGAJVCD FGAJVCD/ FGAJVCQ FGAJVCD/ FGAJVCQ/ FGRTRNI/ FTMRUCL (#1-FXM9V) Description: Journal voucher records are being created in the FGBJVCH table when you enter a document number and perform a next block, even if you exit out of the form without saving anything. Impact: A record is written to FGBJVCH before any data is saved. Resolution: Implementation of API and ON-ERROR trigger have resolved this defect; now, you must Save or acknowledge otherwise when exiting the Key block. (#1-QNXY1) Description: When trying to post to an organization for which you do not have posting authority, an error message pops up that reads: User is not authorized to post with the entered oraganization. Impact: The word organization was spelled incorrectly. Resolution: Corrected spelling of organization. (#CMS-DFCT81059) Description: When on the header record of a Journal Voucher (FGAJVCD), the Access Completion option appeared, even though this option is not available. Impact: This option should be either grayed out or not listed. Resolution: A script will update one existing row in the GUROPTM table. Beginning with this release, the option to select Access Completion will display only when you are in the Detail window. (#CMS-DFCT103773) Description: When you entered the header for either of these forms and then executed the ENTER QUERY function before performing any input, you were put into a loop where it was not possible to exit the form or return to input mode. Impact: You could not exit from query mode if performing an Enter Query function in the detail record before any records existed. Resolution: Since the forms have been modified to implement Journal Voucher APIs and remove many obsolete form triggers, the Exit functionality now works correctly in the Enter Query mode of the detail block. (#CMS-DFCT78896) Description: A rule class with edit code 0004 did not default a user-specified value. Impact: Edit code 0004 was not working to default a user-specified value. Resolution: This problem has been corrected with this release. January 2007 Finance Release 7.3 Confidential Release Guide 41