Oracle System Documentation - Virginia · flowchart processes relate to program Blocks, screen...

Map-122 Adjustment System

Oracle System Documentation

For internal use by the Department of Medical Assistance Services (DMAS)

February 2000

TABLE OF CONTENTS

1. MANUAL INTRODUCTION ............................................................................................................. 1

1.1 INTENDED USE ................................................................................................................................ 1 1.2 ASSUMPTIONS ABOUT THE READER ................................................................................................ 1 1.3 MAP-122 OVERVIEW ...................................................................................................................... 1

1.3.1 Application Functionality ....................................................................................................... 1 1.3.2 System Design ......................................................................................................................... 2

2. FLOWCHARTS ................................................................................................................................... 2

2.1 USER TASK FLOWCHARTS (APPENDIX A) ........................................................................................ 2 2.1.1 Flowchart A: Enter Map-122 Application ............................................................................. 2 2.1.2 Flowchart B: Insert Adjustment ............................................................................................. 2 2.1.3 Flowchart C: Update Adjustment .......................................................................................... 2 2.1.4 Flowchart D: Delete Adjustment ........................................................................................... 3 2.1.5 Flowchart E: Perform Query ................................................................................................. 3 2.1.6 Flowchart F: Click Facility LOV Button ............................................................................... 3 2.1.7 Flowchart G: Click DSS LOV Button .................................................................................... 3 2.1.8 Flowchart H: Insert Facility .................................................................................................. 3 2.1.9 Flowchart I: Update Facility ................................................................................................. 3 2.1.10 Flowchart J: Delete Facility .................................................................................................. 3 2.1.11 Flowchart K: Exit Facility Block ........................................................................................... 3 2.1.12 Flowchart L: Insert DSS ........................................................................................................ 3 2.1.13 Flowchart M: Update DSS .................................................................................................... 3 2.1.14 Flowchart N: Delete DSS ...................................................................................................... 3 2.1.15 Flowchart O: Exit DSS Input Form ....................................................................................... 4 2.1.16 Flowchart P: Save Pend Reason ........................................................................................... 4 2.1.17 Flowchart Q: Delete Pend Reason ........................................................................................ 4 2.1.18 Flowchart R: Exit Pend Reason Input Form ......................................................................... 4 2.1.19 Flowchart S: Save Reject Reason .......................................................................................... 4 2.1.20 Flowchart T: Delete Reject Reason ....................................................................................... 4 2.1.21 Flowchart U: Exit Reject Reason Input Form ....................................................................... 4 2.1.22 Flowchart V: Save Deny Reason ........................................................................................... 4 2.1.23 Flowchart W: Delete Deny Reason ....................................................................................... 4 2.1.24 Flowchart X: Exit Deny Reason Input Form ......................................................................... 4 2.1.25 Flowchart Y: Print Letters ..................................................................................................... 4 2.1.26 Flowchart Z: Print Reports ................................................................................................... 5 2.1.27 Flowchart AA: Double-click in Department of Social Service Field on Screen for Facility-

based Recipients ..................................................................................................................... 5 2.1.28 Flowchart BB: Double-click in First Pend Field on Adjustment Screen for Facility-based

Recipients ................................................................................................................................ 5 2.1.29 Flowchart CC: Click Radio Button on Adjustment Screen for Community-based Recipients 5 2.1.30 Flowchart DD: Click Reports Radio Button on Adjustment Screen for Facility-based

Recipients ................................................................................................................................ 5 2.1.31 Flowchart EE: Click Letter Radio Button on Adjustment Screen for Facility-based

Recipients ................................................................................................................................ 5 2.1.32 Flowchart FF: Click Envelopes Radio Button on Adjustment Screen for Facility-based

Recipients. ............................................................................................................................... 5 2.1.33 Flowchart GG: Click Pending Dates Button on Adjustment Screen for Facility-based

Recipients ................................................................................................................................ 5 2.1.34 Flowchart HH: Click Clear Radio Button on Adjustment Screen for Facility-based

Recipients ................................................................................................................................ 5 2.1.35 Flowchart II: Click DSS LOV Button on Adjustment Screen for Facility-based Recipients .. 6 2.1.36 Flowchart JJ: Scroll Up (to First Record) in Block of Records ............................................ 6

i

2.1.37 Flowchart KK: Scroll Down (to Last Record) in Block of Records ....................................... 6 2.1.38 Flowchart LL: Click Facility Button on Adjustment Screen for Facility-based Recipients ... 6 2.1.39 Flowchart MM: Click Previous Record Button ..................................................................... 6 2.1.40 Flowchart NN: Click Next Record Button ............................................................................. 6 2.1.40 Flowchart OO: Click Radio Button on Pend Reason Input Form ......................................... 6 2.1.41 Flowchart PP: Click Radio Button on Reject Reason Input Form ........................................ 6 2.1.42 Flowchart QQ: Click Run Envelopes Button on Envelopes Screen ....................................... 6 2.1.43 Flowchart RR: Click Exit Button on Envelopes Screen ......................................................... 7 2.1.44 Flowchart SS: Click DSS Button on Adjustment Screen for Community-based Recipients ... 7 2.1.45 Flowchart TT: Click Pending Dates Button on Adjustment Screen for Community-based

Recipients ................................................................................................................................ 7 2.1.46 Flowchart UU: Click Radio Button on Facility Input Form .................................................. 7

2.2 SYSTEM EVENT FLOWCHARTS (APPENDIX B) ................................................................................. 7 2.2.1 Flowchart 1: PRE-INSERT (ADJUSTMENT1) ..................................................................... 7 2.2.2 Flowchart 2: KEY-NXTBLK (ADJUSTMENT1) .................................................................... 7 2.2.3 Flowchart 3: ON-DELETE (ADJUSTMENT1) ..................................................................... 8 2.2.4 Flowchart 4: ON-UPDATE (ADJUSTMENT1) ..................................................................... 8 2.2.5 Flowchart 5: WHEN-NEW-BLOCK-INSTANCE (ADJUSTMENT1) .................................... 8 2.2.6 Flowchart 6: ON-UPDATE (DSS) ......................................................................................... 8 2.2.7 Flowchart 7: ON-DELETE (DSS) ......................................................................................... 8 2.2.8 Flowchart 8: PRE-INSERT (FACILITY) ............................................................................... 8 2.2.9 Flowchart 9: ON-UPDATE (FACILITY) ............................................................................... 8 2.2.10 Flowchart 10: ON-DELETE (FACILITY) ............................................................................. 8 2.2.11 Flowchart 11: WHEN-VALIDATE-ITEM (Recipient_ID on ADJUSTMENT1) .................... 8 2.2.12 Flowchart 12: POST-TEXT-ITEM (Adjustment_ID on ADJUSTMENT1)) ........................... 8 2.2.13 Flowchart 13: WHEN-VALIDATE-ITEM (Facility_Name on ADJUSTMENT1) .................. 9 2.2.14 Flowchart 14: WHEN-VALIDATE-ITEM (Map_Type on ADJUSTMENT1)......................... 9 2.2.15 Flowchart 15: PRE-TEXT-ITEM (Orig_Date on ADJUSTMENT1) ..................................... 9 2.2.16 Flowcahrt 16: KEY-NXTREC (Description on PEND_REASON) ........................................ 9 2.2.17 Flowchart 17: PRE-TEXT-ITEM (Orig_Date on HOMEBASED) ........................................ 9 2.2.18 Flowchart 18: KEY-NEXT-ITEM (Pend_Reason1 on ADJUSTMENT1) .............................. 9 2.2.19 Flowchart 19: KEY-PRVBLK (ADJUSTMENT) .................................................................... 9

3. DIRECTORIES .................................................................................................................................... 9

4. FORMS.................................................................................................................................................10

5. MENUS.................................................................................................................................................10

6. TRIGGERS, PROGRAM UNITS, AND OTHER CODE................................................................10

6.1 FORM-LEVEL TRIGGERS .................................................................................................................10 6.2 BLOCK-LEVEL TRIGGERS ...............................................................................................................10 6.3 ITEM-LEVEL TRIGGERS ...................................................................................................................11 6.4 PROGRAM UNITS AND “NON-TRIGGER” PROCEDURE CODE ...........................................................15

6.4.1 Program Units .......................................................................................................................15 6.4.2 “Non-trigger” Procedure Code.............................................................................................16

7. ENTITY-RELATIONSHIP MODEL ................................................................................................17

8. DATABASE TABLES .........................................................................................................................17

8.1 TABLE DEFINITIONS .......................................................................................................................17 8.1.1 ADJUSTMENT ......................................................................................................................17 8.1.2 DEN_REASON ......................................................................................................................18 8.1.3 DSS ........................................................................................................................................18 8.1.4 FACILITY ..............................................................................................................................19 8.1.5 MAPREPORT ........................................................................................................................19

ii

8.1.6 NEXT_ADJUSTMENT_NUMBER.........................................................................................19 8.1.7 PEND_REASON ....................................................................................................................19 8.1.8 REJECT .................................................................................................................................19 8.1.9 TEMP_ADJUSTMENT ..........................................................................................................20 8.1.10 TEMP_ADJUST.....................................................................................................................20 8.1.11 T_ADJUSTMENT ..................................................................................................................20

8.2 PARENT/CHILD TABLE RELATIONSHIPS .........................................................................................20 8.3 BLOCKS AND CORRESPONDING BASE TABLES ................................................................................20

APPENDIXES .............................................................................................................................................21

iii

Map-122 Adjustment System Oracle System Documentation

1. Manual Introduction This manual explains the Oracle system processes associated with the functions of the Map-122 Adjustment System. Appendixes of flowcharts provide visual representations of narrative explanations within the manual. Read the subsections below to learn whom this manual is intended for and what the Map-122 Adjustment System does.

1.1 Intended Use This manual is intended for use by Oracle software developers or database administrators who need to make changes or enhancements to the Map-122 application but lack experience in working with it.

1.2 Assumptions About the Reader This manual’s content and approach rest on two major assumptions: - that the reader is an experienced Oracle software developer or individual with similar skills; - and that the reader has no familiarity with the Map-122 interface or the corresponding Oracle

files. In accordance with the latter assumption, narratives about all of the flowcharts explains how flowchart processes relate to program Blocks, screen buttons, etc. This “bridges the gap” between the Map-122 interface and the program files, thus integrating for the reader the process of becoming familiar with the application interface and the files that make it up.

1.3 MAP-122 Overview The subsections below describe Map-122 from both user and developer perspectives.

1.3.1 Application Functionality The Payment Processing Unit of the Department of Medical Assistance Services (DMAS) uses the Map-122 Adjustment System to process Map-122 requests that come from local departments of social services, individuals in the community, or healthcare facilities. In a nutshell, Map-122 requests ask that a Medicaid patients’ income be reduced by the amount of the patient's income, less certain deductions (patient pay amount). One required deduction is an amount "for medical or remedial care not subject to payment by a third party." (This includes necessary medical or remedial care not covered under the Virginia State Plan for the Department of Medical Assistance Services. Medicaid uses the patient pay amount to determine the amount of the facility's monthly billing that the patient will pay.) For patients who live in facilities, patient pay plus Medicaid contribution equals the amount due the facility for the patient's care for that month. Processing Map-122 requests using the Map-122 Adjustment System involves typing recipient information into the system; indicating the status of the request (approved, pending, rejected, denied); sending out status letters to individuals and facilities; printing monthly and annual reports; and following up on those Adjustment requests that initially had pending status. Map-122 has different input screens for the two types of Medicaid recipients (those in facilities and those living in the community).

1


NOTE: Where it is used in this manual, the word “recipient” refers to a Medicaid recipient. Medicaid recipients are the individuals whose Map-122 adjustment requests are processed in the Map-122 Adjustment System.

1.3.2 System Design The Map-122 Adjustment System uses a single Form and a custom menu. Program logic resides in Form-, Block-, and Item-level triggers and in program units and property sheets. Multiple Blocks make up various input forms and the two Adjustment screens. It is important to note that ADJUSTMENT1 is the Block that tracks Adjustment requests from recipients in facilities, and HOMEBASED is the Block that tracks Adjustment requests from recipients who are based in the community (i.e., community-based care, or “CBC”). These Blocks are nearly identical in appearance – the major difference being that ADJUSTMENT1 has fields that accommodate facility-type information and HOMEBASED does not. Both Blocks have ADJUSTMENT as their base table. The ADJUSTMENT1 and HOMEBASED Blocks also have Views that stores Pending Date field values. They are as follows: Block Type of Adjustment Block Associated with View ADJUSTMENT1 Facility-based ADJUSTMENT HOMEBASED Community-based CBC

Table 1.3.2-1. Pending Date View Blocks. 2. Flowcharts The appendixes in this guide depict two kinds of processes: user tasks and system events. User task flowcharts show what happens in Oracle when a user completes a task of some kind, such as inserting a new Adjustment or updating an existing one. System event flowcharts depict Oracle processes that occur by way of built-in triggers such as KEY-NXTREC and WHEN-VALIDATE-ITEM. Refer to Appendix A for all user task flowcharts; see Appendix B for all system event flowcharts.

2.1 User Task Flowcharts (Appendix A) User task flowcharts are located in Appendix A. Refer to them as you read the flowchart explanations below. (See Appendix B for system event flowcharts.)

2.1.1 Flowchart A: Enter Map-122 Application This flowchart shows what happens when a user logs on and clicks the Enter Adjustments Process button to enter the application interface.

2.1.2 Flowchart B: Insert Adjustment This flowchart shows what happens when a user clicks the Insert radio button on the Adjustment screen for facility-based Medicaid recipients (ADJUSTMENT1 Block). NOTE: The HOMEBASED Block corresponds to community-based care (CBC) Medicaid recipients.

2.1.3 Flowchart C: Update Adjustment

This flowchart shows what happens when a user clicks the Update radio button on the Adjustment screen for facility-based Medicaid recipients (ADJUSTMENT1 Block).

2


NOTE: The HOMEBASED Block corresponds to community-based care (CBC) Medicaid recipients.

2.1.4 Flowchart D: Delete Adjustment This flowchart shows what happens when a user clicks the Delete radio button on the Adjustment screen for facility-based Medicaid recipients (ADJUSTMENT1 Block). NOTE: The HOMEBASED Block corresponds to community-based care (CBC) Medicaid recipients.

2.1.5 Flowchart E: Perform Query

The Perform Query flowchart shows what happens when a user clicks the Query radio button on any Block in the Map-122 Adjustment System.

2.1.6 Flowchart F: Click Facility LOV Button This flowchart shows what happens when a user clicks the LOV button on the FACILITY Block.

2.1.7 Flowchart G: Click DSS LOV Button This flowchart shows what happens when a user clicks the LOV button on the DSS Block.

2.1.8 Flowchart H: Insert Facility This flowchart shows what happens when a user clicks the Insert radio button on the FACILITY Block.

2.1.9 Flowchart I: Update Facility The Update Facility flowchart shows what happens when the user clicks the Update radio button on the FACILITY Block.

2.1.10 Flowchart J: Delete Facility This flowchart shows what happens when the user clicks the Delete radio button on the FACILITY Block.

2.1.11 Flowchart K: Exit Facility Block This flowchart shows what happens when a user clicks the Exit radio button on the FACILITY Block.

2.1.12 Flowchart L: Insert DSS This flowchart shows what happens when a user clicks the Insert radio button on the DSS Block.

2.1.13 Flowchart M: Update DSS This flowchart shows what happens when a user clicks the Update radio button on the DSS Block.

2.1.14 Flowchart N: Delete DSS This flowchart shows what happens when a user clicks the Delete radio button on the DSS Block.

3


2.1.15 Flowchart O: Exit DSS Input Form The Exit DSS Input Form shows what happens when a user clicks the Exit radio button on the DSS Block.

2.1.16 Flowchart P: Save Pend Reason This flowchart shows what happens when a user clicks the Save radio button on the PEND_REASON Block.

2.1.17 Flowchart Q: Delete Pend Reason This flowchart shows what happens when a user clicks the Delete radio button on the PEND_REASON Block.

2.1.18 Flowchart R: Exit Pend Reason Input Form This flowchart shows what happens when a user clicks the Exit radio button on the PEND_REASON Block.

2.1.19 Flowchart S: Save Reject Reason This flowchart shows what happens when a user clicks the Save radio button on the REJECT Block.

2.1.20 Flowchart T: Delete Reject Reason This flowchart shows what happens when a user clicks the Delete radio button on the REJECT Block.

2.1.21 Flowchart U: Exit Reject Reason Input Form This flowchart shows what happens when a user clicks the Exit radio button on the REJECT Block.

2.1.22 Flowchart V: Save Deny Reason This flowchart shows what happens when a user clicks the Save radio button on the DEN_REASON Block.

2.1.23 Flowchart W: Delete Deny Reason This flowchart shows what happens when a user clicks the Delete radio button on the DEN_REASON Block.

2.1.24 Flowchart X: Exit Deny Reason Input Form This flowchart shows what happens when a user clicks the Exit radio button on the DEN_REASON Block.

2.1.25 Flowchart Y: Print Letters This flowchart shows what happens when a user prints any of the letters available in the Map-122 Adjustment System.

4


2.1.26 Flowchart Z: Print Reports This flowchart shows what happens when a user prints any of the reports available in the Map-122 Adjustment System.

2.1.27 Flowchart AA: Double-click in Department of Social Service Field on Screen for Facility-based Recipients

This flowchart shows what happens when a user double-clicks in the Department of Social Service field on the Adjustment screen for those recipients who reside in a facility (ADJUSTMENT1 Block).

2.1.28 Flowchart BB: Double-click in First Pend Field on Adjustment Screen for Facility-based Recipients

This flowchart shows what happens when a user double-clicks in the first Pend reason field on the Adjustment screen for facility-based recipients (ADJUSTMENT1 Block). NOTE: The process reflected in this flowchart applies to the other reason and comment fields (e.g., pend reasons 2 and 3, pend comments 1 – 3, denial reasons 1 – 3, and reject reasons 1 – 3) in the ADJUSTMENT1 Block.

2.1.29 Flowchart CC: Click Radio Button on Adjustment Screen for Community-based Recipients

This flowchart shows what happens when a user clicks any of the following radio buttons on the HOMEBASED Block: Query, Letters, Reports, Envelope, Insert, Update, Delete, Clear, Exit.

2.1.30 Flowchart DD: Click Reports Radio Button on Adjustment Screen for Facility-based Recipients

This flowchart shows what happens when a user clicks the Reports radio button on the ADJUSTMENT1 Block.

2.1.31 Flowchart EE: Click Letter Radio Button on Adjustment Screen for Facility-based Recipients

This flowchart shows what happens when a user clicks the Letter radio button on the ADJUSTMENT1 Block.

2.1.32 Flowchart FF: Click Envelopes Radio Button on Adjustment Screen for Facility-based Recipients.

This flowchart shows what happens when a user clicks the Envelopes radio button on the ADJUSTMENT1 Block.

2.1.33 Flowchart GG: Click Pending Dates Button on Adjustment Screen for Facility-based Recipients

This flowchart shows what happens when a user clicks the PUSH_BUTTON264 item (Pending Dates button) on the ADJUSTMENT1 Block.

2.1.34 Flowchart HH: Click Clear Radio Button on Adjustment Screen for Facility-based Recipients

5


This flowchart shows what happens when a user clicks the Clear radio button on the ADJUSTMENT1 Block.

2.1.35 Flowchart II: Click DSS LOV Button on Adjustment Screen for Facility-based Recipients

This flowchart shows what happens when a user clicks the SS_BTN item (DSS LOV button) on the ADJUSTMENT1 Block.

2.1.36 Flowchart JJ: Scroll Up (to First Record) in Block of Records This flowchart shows what happens when a user clicks the Scroll Up button anywhere in the Map-122 Adjustment System. This button is Item SCROLL_UP on Block BLOCK53.

2.1.37 Flowchart KK: Scroll Down (to Last Record) in Block of Records This flowchart shows what happens when a user clicks the Scroll Down button anywhere in the Map-122 Adjustment System. This button is Item SCROLL_DOWN on Block BLOCK53.

2.1.38 Flowchart LL: Click Facility Button on Adjustment Screen for Facility-based Recipients

Flowchart LL shows what happens when a user clicks the Facility button on the Adjustment screen for facility-based recipients. This button is the FACILITY_BTN Item on Block BLOCK53.

2.1.39 Flowchart MM: Click Previous Record Button This flowchart shows what happens when a user clicks the Previous Record button anywhere in the Map-122 Adjustment System. This button is Item UP on Block BLOCK53. 2.1.40 Flowchart NN: Click Next Record Button This flowchart shows what happens when a user clicks the Next Record button anywhere in the Map-122 Adjustment System. This button is Item DOWN on Block BLOCK53.

2.1.40 Flowchart OO: Click Radio Button on Pend Reason Input Form This flowchart shows what happens when a user clicks any radio button on the Pending Reasons input form. Radio buttons include Query, Save, Delete, Exit, and Clear. These radio buttons are under the PEND_RADIO Item on the PEND_REASON Block.

2.1.41 Flowchart PP: Click Radio Button on Reject Reason Input Form This flowchart shows what happens when a user clicks any radio button on the Reject Reasons input form. Radio buttons include Query, Save, Delete, Exit, and Clear. These radio buttons are under the REJECT_RADIO Item on the REJECT Block.

2.1.42 Flowchart QQ: Click Run Envelopes Button on Envelopes Screen This flowchart shows what happens when a user clicks the Run Envelopes button after clicking a radio button to indicate the type of envelopes desired. Types of envelopes include DSS, resident, CBC, and facility. The Run Envelopes button is the LABEL_BTN Item on the LABEL Block. (A user arrives on this Block by clicking the Envelopes radio button on either of the Adjustment screens.)

6


2.1.43 Flowchart RR: Click Exit Button on Envelopes Screen This flowchart shows what happens when a user clicks the Exit button on the Envelopes screen. (A user arrives on this screen by clicking the Envelopes radio button on either of the Adjustment screens.) The Envelopes screen is the LABEL Block. The Exit button on the Envelopes screen is the EXIT_BTN Item.

2.1.44 Flowchart SS: Click DSS Button on Adjustment Screen for Community-based Recipients

This flowchart shows what happens when a user clicks the DSS button on the Adjustment screen for recipients who reside at home (i.e., in the community) rather than in a facility. The community-based care Adjustment screen is the HOMEBASED Block.

2.1.45 Flowchart TT: Click Pending Dates Button on Adjustment Screen for Community-based Recipients

This flowchart shows what happens when a user clicks the Pending Dates button on the Adjustment screen for community-based recipients. The Pending Dates button is Item PUSH_BUTTON387 on the HOMEBASED Block.

2.1.46 Flowchart UU: Click Radio Button on Facility Input Form This flowchart shows what happens when a user clicks any of the radio buttons on the Facility input form. Radio buttons include Insert, Update, Delete, Query, Clear, and Exit. These radio buttons are under the FACILITY_RADIO_BTN Item on the FACILITY Block.

2.2 System Event Flowcharts (Appendix B) System event flowcharts in Appendix B include both interface events and internal processing events. Interface event triggers fire in response to user interaction with the keyboard, but they are not considered user tasks since they represent internal processing that is set off by a trigger more closely tied to the user task’s execution. Refer to Appendix B as you read the flowchart explanations below. (See Appendix A for user task flowcharts.)

2.2.1 Flowchart 1: PRE-INSERT (ADJUSTMENT1) This built-in trigger fires when a new Adjustment for a facility-based recipient is inserted. The corresponding Block for this Block-level trigger is ADJUSTMENT1.

2.2.2 Flowchart 2: KEY-NXTBLK (ADJUSTMENT1) Identifies ADJUSTMENT as the next navigation Block in the sequence. The corresponding Block for this Block-level trigger is ADJUSTMENT1. ′ NOTE: The ADJUSTMENT Block is used as a view that only shows the Pending Date(s) for a facility-based Adjustment. (A pending date is the date on which an Adjustment was assigned pending status.) The DATE_RECEIVED Item under the ADJUSTMENT Block stores dates for the Pending Dates fields but does not have a trigger attached to it. The PL/SQL code that brings up the pending date(s) is in the WHERE Clause line of the Properties sheet for the ADJUSTMENT Block. The code reads as follows:

7


WHERE RECIPIENT ID =:ADJUSTMENT1.RECIPIENT ID AND COST = :ADJUSTMENT1.COST AND MAP TYPE = ‘P’

The above WHERE Clause ensures that the correct pending dates (i.e., for the current facility-based Adjustment) are retrieved into the Pending Dates fields. (There can be only one pending date, but there are fields available for three pending dates.)

2.2.3 Flowchart 3: ON-DELETE (ADJUSTMENT1) This built-in trigger fires when an Adjustment for a facility-based recipient is deleted. The corresponding Block for this Block-level trigger is ADJUSTMENT1.

2.2.4 Flowchart 4: ON-UPDATE (ADJUSTMENT1) This Block-level trigger updates the database to reflect the current values in all of the fields on the ADJUSTMENT1 Block. (The ADJUSTMENT1 Block is used for facility-based Adjustments.)

2.2.5 Flowchart 5: WHEN-NEW-BLOCK-INSTANCE (ADJUSTMENT1) When input focus moves to the ADJUSTMENT1 Block, this trigger hides the LETTER_CAN canvas. (This is the canvas where users choose and generate letters.)

2.2.6 Flowchart 6: ON-UPDATE (DSS) This trigger fires when a user clicks the Update radio button on the DSS input form. The corresponding Block for this Block-level trigger is DSS.

2.2.7 Flowchart 7: ON-DELETE (DSS) This trigger fires when a user clicks the Delete radio button on the DSS input form. The corresponding Block for this Block-level trigger is DSS.

2.2.8 Flowchart 8: PRE-INSERT (FACILITY) This trigger fires when a user clicks the Insert radio button on the Facility input form. The corresponding Block for this Block-level trigger is FACILITY.

2.2.9 Flowchart 9: ON-UPDATE (FACILITY) This trigger fires when a user clicks the Update radio button on the Facility input form. The corresponding Block for this Block-level trigger is FACILITY.

2.2.10 Flowchart 10: ON-DELETE (FACILITY) This trigger fires when a user clicks the Delete radio button on the Facility input form. The corresponding Block for this Block-level trigger is FACILITY.

2.2.11 Flowchart 11: WHEN-VALIDATE-ITEM (Recipient_ID on ADJUSTMENT1) This trigger fires when the user clicks the Insert radio button on the Adjustment screen for facility-based recipients. The corresponding Block for this Item-level trigger is ADJUSTMENT1.

2.2.12 Flowchart 12: POST-TEXT-ITEM (Adjustment_ID on ADJUSTMENT1))

8


When the cursor leaves the Adjustment_ID field on the ADJUSTMENT1 Block, this trigger brings the pending date value from the ADJUSTMENT Block’s Date_Received field into the Date Mailed field (Orig_Date Item) on the ADJUSTMENT1 Block. It does this only where the Map type is “P” (pending) and the Adjustment IDs on the ADJUSTMENT and ADJUSTMENT1 Blocks are the same.

2.2.13 Flowchart 13: WHEN-VALIDATE-ITEM (Facility_Name on ADJUSTMENT1) Once Oracle has validated the Facility Name for a facility-based Adjustment, it populates the facility address fields by way of the PL/SQL code in this trigger.

2.2.14 Flowchart 14: WHEN-VALIDATE-ITEM (Map_Type on ADJUSTMENT1) This trigger fires when the user presses Enter on the keyboard after typing a Map type in the Map Type field on the Adjustment screen for facility-based recipients. The corresponding Block for this Item-level trigger is ADJUSTMENT1.

2.2.15 Flowchart 15: PRE-TEXT-ITEM (Orig_Date on ADJUSTMENT1) This trigger fires when the user presses Enter on the keyboard after typing a date in the Received Date field on the Adjustment screen for facility-based recipients. The corresponding Block for this Item-level trigger is ADJUSTMENT1.

2.2.16 Flowcahrt 16: KEY-NXTREC (Description on PEND_REASON) This trigger fires when the user presses Ctrl + L (use lower-case “L”) in a Reason field on the PEND_REASON Block.

2.2.17 Flowchart 17: PRE-TEXT-ITEM (Orig_Date on HOMEBASED) This trigger fires when the user presses Enter on the keyboard after typing a date in the Received Date field on the Adjustment screen for community-based recipients. The corresponding Block for this Item-level trigger is HOMEBASED.

2.2.18 Flowchart 18: KEY-NEXT-ITEM (Pend_Reason1 on ADJUSTMENT1) This trigger fires when the user presses Ctrl + Tab on the keyboard from within the first Pend field on the Adjustment screen for facility-based recipients. The corresponding Block for this Item-level trigger is ADJUSTMENT1. 2.2.19 Flowchart 19: KEY-PRVBLK (ADJUSTMENT) This trigger moves the cursor to the ADJUSTMENT1 Block when the user presses Ctrl + Page Up on the keyboard The corresponding Block for this Block-level trigger is ADJUSTMENT.

3. Directories S:\DMAS\Testapp\Map\Bin – Contains programs and files for testing; can be modified as needed. S:\DMAS\APP\Map\ - Production source directory; contains the following directories: Bin, Fmb, and Rdf. S:\DMAS\Source\Map – Developer source directory; contains the following directories: Fmb, Rdf, and Sql.

9


4. Forms The Map-122 Adjustment System uses a single Form for all processes: Map122.fmx 5. Menus Map-122 uses a custom menu: Map.mmb 6. Triggers, Program Units, and Other Code Triggers supply nearly all of Map-122’s functionality, and most triggers are at the Item level. Refer to the tables in subsections 6.1 – 6.3 (below) for information on which triggers correspond to which Forms, Blocks, or Items. Where applicable, see the corresponding appendix and flowchart named in the table. Refer to subsection 6.4 for information on Map-122 program units and “non-trigger” procedure code.

6.1 Form-level Triggers Table 6.1-1 below names the Form-level triggers in Map-122. See the corresponding flowcharts for a visual representation of the trigger processes. Form Trigger Appendix Flowchart MAP122 WHEN-NEW-BLOCK-INSTANCE A A MAP122 WHEN-NEW-FORM-INSTANCE A A Table 6.1-1. Form-level Triggers.

6.2 Block-level Triggers Table 6.2-1 below names the Block-level triggers in Map-122. See the corresponding flowcharts for a visual representation of the trigger processes. Block Trigger(s) Appendix Flowchart Adjustment1 • PRE-INSERT

• KEY-NXTBLK • ON-DELETE • ON-UPDATE • WHEN-NEW-BLOCK-INSTANCE

B 1 B 2 B 3 B 4 B 5

Adjustment KEY-PRVBLK B 19 DSS • ON-UPDATE

• ON-DELETE B 6 B 7

FACILITY • PRE-INSERT

• ON-UPDATE • ON-DELETE

B 8 B 9

B 10

Table 6.2-1. Block-level Triggers.

10


6.3 Item-level Triggers Table 6.3-1 below indicates the Item-level triggers in Map-122. See the corresponding flowcharts for a visual representation of the trigger processes. Block Item Trigger(s) Appendix Flowchart ADMIN ENTER_BTN WHEN-BUTTON-PRESSED A A ADMIN EXIT_BTN WHEN-BUTTON-PRESSED A A ADJUSTMENT1 RECIPIENT_ID WHEN-VALIDATE-ITEM B 11 ADJUSTMENT1 ADJUSTMENT_ID POST-TEXT-ITEM B 12 ADJUSTMENT1 FACILITY_NAME WHEN-VALIDATE-ITEM B 13 ADJUSTMENT1 MAP_TYPE WHEN-VALIDATE-ITEM B 14 ADJUSTMENT1 DSS WHEN-MOUSE-

DOUBLECLICK A AA

ADJUSTMENT1 ORIG_DATE PRE-TEXT-ITEM B 15 ADJUSTMENT1 PEND_REASON1 • WHEN-MOUSE-

DOUBLECLICK • KEY-NEXT-ITEM

A BB

B 18

ADJUSTMENT1 PEND_REASON2 • WHEN-MOUSE-DOUBLECLICK

• KEY-NEXT-ITEM

A See Flowchart BB

B See Flowchart 18

ADJUSTMENT1 PEND_REASON3 • WHEN-MOUSE-DOUBLECLICK

• KEY-NEXT-ITEM

A See Flowchart BB

B See Flowchart 18

ADJUSTMENT1 PEND_COMMENT1 • WHEN-MOUSE-DOUBLECLICK

• KEY-NEXT-ITEM

A See Flowchart BB

B See Flowchart 18

ADJUSTMENT1 PEND_COMMENT2 • WHEN-MOUSE-DOUBLECLICK

• KEY-NEXT-ITEM

A See Flowchart BB

B See Flowchart 18

ADJUSTMENT1 PEND_COMMENT3 WHEN-MOUSE-DOUBLECLICK

A See Flowchart BB

ADJUSTMENT1 DEN_REASON1 WHEN-MOUSE-DOUBLECLICK

A See Flowchart BB


A See Flowchart BB


A See Flowchart BB

ADJUSTMENT1 REJ_REASON1 WHEN-MOUSE-DOUBLECLICK

A See Flowchart BB


A See Flowchart BB


A See Flowchart BB

ADJUSTMENT1 ADJUSTMENT_ RADIO (Includes

WHEN-MOUSE-CLICK A CC

11


Block Item Trigger(s) Appendix Flowchart Query, Letters, Report, Envelope, Insert, Update, Delete, and Clear radio buttons)

ADJUSTMENT1 INSERT_BTN WHEN-BUTTON-PRESSED A B ADJUSTMENT1 DELETE_BTN WHEN-BUTTON-PRESSED A D ADJUSTMENT1 UPDATE_BTN WHEN-BUTTON-PRESSED A C ADJUSTMENT1 REPORTS WHEN-BUTTON-PRESSED A DD ADJUSTMENT1 LETTER_BTN WHEN-BUTTON-PRESSED A EE ADJUSTMENT1 LABEL_BTN

(Envelopes button)

WHEN-BUTTON-PRESSED A FF

ADJUSTMENT1 PUSH_BUTTON264 (Pending Dates button)

WHEN-BUTTON-PRESSED A GG

ADJUSTMENT1 CLEAR_BTN WHEN-BUTTON-PRESSED A HH ADJUSTMENT1 SS_BTN

(DSS button)

WHEN-BUTTON-PRESSED A I I

BLOCK53 QUERY WHEN-BUTTON-PRESSED A E BLOCK53 SCROLL_UP WHEN-BUTTON-PRESSED A JJ BLOCK53 SCROLL_DOWN WHEN-BUTTON-PRESSED A KK BLOCK53 FACILITY_BTN WHEN-BUTTON-PRESSED A LL BLOCK53 ID_LOV_BTN WHEN-BUTTON-PRESSED (Not used) (N/A) BLOCK53 UP WHEN-BUTTON-PRESSED A MM BLOCK53 DOWN WHEN-BUTTON-PRESSED A NN LETTER LETTER_BTN WHEN-BUTTON-PRESSED A Y LETTER EXIT_BTN WHEN-BUTTON-PRESSED A Y REPORT REPORT_BTN WHEN-BUTTON-PRESSED A Z REPORT EXIT_BTN WHEN-BUTTON-PRESSED A Z PEND_REASON DESCRIPTION KEY-NXTREC B 16 PEND_REASON PEND_RADIO

(Includes Query, Save, Delete, Exit, and Clear radio buttons)

WHEN-MOUSE-CLICK A OO

PEND_REASON DELETE_BTN WHEN-BUTTON-PRESSED A Q PEND_REASON SAVE_BTN WHEN-BUTTON-PRESSED A P PEND_REASON EXIT_BTN WHEN-BUTTON-PRESSED A R

12


Block Item Trigger(s) Appendix Flowchart DEN_REASON DESCRIPTION KEY-NXTREC B See Flowchart

16 DEN_REASON DEN_RADIO


WHEN-MOUSE-CLICK A See Flowchart OO

DEN_REASON SAVE_BTN WHEN-BUTTON-PRESSED A V DEN_REASON DELETE_BTN WHEN-BUTTON-PRESSED A W DEN_REASON EXIT_BTN WHEN-BUTTON-PRESSED A X REJECT DESCRIPTION KEY-NXTREC B See Flowchart

16 REJECT SAVE_BTN WHEN-BUTTON-PRESSED A S REJECT DELETE_BTN WHEN-BUTTON-PRESSED A T REJECT EXIT_BTN WHEN-BUTTON-PRESSED A U REJECT REJECT_RADIO


WHEN-MOUSE-CLICK A PP

DSS DSS_BTN WHEN-BUTTON-PRESSED A G DSS DSS_RADIO

(Includes Query, Insert, Update, Delete, Clear, and Exit radio buttons)

WHEN-MOUSE-CLICK A See Flowchart OO

DSS SCROLL_UP WHEN-BUTTON-PRESSED A See Flowchart JJ

DSS SCROLL_DOWN WHEN-BUTTON-PRESSED A See Flowchart KK

DSS UP WHEN-BUTTON-PRESSED A See Flowchart MM

DSS DOWN WHEN-BUTTON-PRESSED A See Flowchart NN

DSS INSERT_BTN WHEN-BUTTON-PRESSED A L DSS DELETE_BTN WHEN-BUTTON-PRESSED A N DSS UPDATE_BTN WHEN-BUTTON-PRESSED A M DSS EXIT_BTN WHEN-BUTTON-PRESSED A O LABEL LABEL_BTN

(Run Envelopes button)

WHEN-BUTTON-PRESSED A QQ

LABEL EXIT_BTN WHEN-BUTTON-PRESSED A RR

13


Block Item Trigger(s) Appendix Flowchart FACILITY FACILITY_RADIO

_BTN (Includes Insert, Update, Delete, Query, Clear, and Exit radio buttons)

WHEN-MOUSE-CLICKED A UU

FACILITY FACILITY_LOV_ BTN

WHEN-BUTTON-PRESSED A F

FACILITY INSERT_BTN WHEN-BUTTON-PRESSED A H FACILITY UPDATE_BTN WHEN-BUTTON-PRESSED A I FACILITY DELETE_BTN WHEN-BUTTON-PRESSED A J FACILITY EXIT_BTN WHEN-BUTTON-PRESSED A K BUTTON_ PALETTE

SCROLL_UP WHEN-BUTTON-PRESSED A See Flowchart JJ

BUTTON_ PALETTE

UP WHEN-BUTTON-PRESSED A See Flowchart MM

BUTTON_ PALETTE

SCROLL_DOWN WHEN-BUTTON-PRESSED A See Flowchart KK

BUTTON_ PALETTE

DOWN WHEN-BUTTON-PRESSED A See Flowchart NN

HOMEBASED ORIG_DATE PRE-TEXT-ITEM B 17 HOMEBASED PEND_REASON1 WHEN-MOUSE-

DOUBLECLICK A See Flowchart

BB HOMEBASED PEND_REASON2 WHEN-MOUSE-


BB HOMEBASED PEND_REASON3 WHEN-MOUSE-


BB HOMEBASED PEND_COMMENT1 WHEN-MOUSE-






BB HOMEBASED DEN_REASON1 WHEN-MOUSE-






BB HOMEBASED REJ_REASON1 WHEN-MOUSE-






BB

HOMEBASED PUSH_BUTTON383

WHEN-MOUSE-DOUBLECLICK

A SS

14


Block Item Trigger(s) Appendix Flowchart (DSS button)

HOMEBASED PUSH_BUTTON387 (Pending Dates button)

WHEN-MOUSE-DOUBLECLICK

A TT

HOMEBASED ADJUSTMENT_ RADIO (Includes Query, Letter, Report, Envelope, Insert, Update, Delete, Clear, and Exit)

WHEN-MOUSE-CLICK A See Flowchart CC

BLOCK363 SCROLL_UP WHEN-BUTTON-PRESSED A See Flowchart

JJ BLOCK363 UP WHEN-BUTTON-PRESSED A See Flowchart

MM BLOCK363 DOWN WHEN-BUTTON-PRESSED A See Flowchart

NN BLOCK363 SCROLL_DOWN WHEN-BUTTON-PRESSED A See Flowchart

KK BLOCK363 QUERY WHEN-BUTTON-PRESSED A See Flowchart E BLOCK363 SAVE WHEN-BUTTON-PRESSED (Not used) (N/A) Table 6.3-1. Item-level Triggers.

6.4 Program Units and “Non-trigger” Procedure Code While nearly all of Map-122’s functionality lies in trigger code, the application does include program units and code stored in Block property sheets. See subsections 6.4.1 and 6.4.2 below for additional information.

6.4.1 Program Units The following program units appear under the Program Units node of the Map-122 file system, but only the second one (CHECK_PK_ADJUSTMENT) is used: • CHECK_NOT_NULL_FIELDS • CHECK_PK_ADJUSTMENT* • CREATE_ADJUSTMENT • STRIP_CONSTRAINT_NAME *The triggers shown in Table 6.4.1-1 below call the CHECK_PK_ADJUSTMENT program unit:

15


Block Item Trigger HOMEBASED Adjustment_Radio

(Insert radio button only)

WHEN-MOUSE-CLICKED

HOMEBASED Insert_Btn WHEN-BUTTON-PRESSED ADJUSTMENT1 Adjustment_Radio

(Insert radio button only)

WHEN-BUTTON-PRESSED

ADJUSTMENT1 Insert_Btn WHEN-BUTTON-PRESSED Table 6.4.1-1. Calls to CHECK_PK_ADJUSTMENT Program Unit. The purpose of the CHECK_PK_ADJUSTMENT program unit is as follows:

To determine whether or not the Adjustment that a user is attempting to insert already exists. (It is for this reason that calls to the CHECK_PK_ADJUSTMENT program unit only appear in triggers that are tied to the Insert buttons on the ADJUSTMENT1 and HOMEBASED Blocks.) If it is determined that an Adjustment does already exist, then CHECK_PK_ADJUSTMENT raises an alert that says, ‘Adjustment already entered. Please insert another Adjustment.’

Click here to view the CHECK_PK_ADJUSTMENT PL/SQL code Appendix C 6.4.2 “Non-trigger” Procedure Code The property sheets of several Blocks have PL/SQL code in the WHERE Clause line. Those Blocks, the code, and the function of the code are as shown in Table 6.4.2-1 below: Block PL/SQL Code Code Function ADJUSTMENT1 WHERE Destination NOT IN

('DR','C') Ensures that Adjustments whose Destination radio buttons have “C” or “DR” in the Value line of the property sheet will not be retrieved. “C” and “DR” are the values that correspond to the Recipient and DSS Destination radio buttons on the HOMEBASED Block. (“C” corresponds to the Recipient destination and refers to the fact that the recipient is community-based; “DR” corresponds to the DSS destination.)

ADJUSTMENT (View for ADJUSTMENT1)

WHERE RECIPIENT_ID = :ADJUSTMENT1.RECIPIENT_ID AND COST = :ADJUSTMENT1.COST AND MAP_TYPE = 'P'

Ensures that pending dates associated with only the current facility-based Adjustment will be retrieved.

HOMEBASED WHERE Destination IN ('DR','C')

Ensures that Adjustments whose Destination radio buttons have “C” or “DR” in the Value line of the property sheet will be retrieved. In other words, it ensures that facility-based Adjustments will not be retrieved and community-based care Adjustments will be retrieved. (Facility-based Adjustments are tracked in the ADJUSTMENT1 Block. The Destination radio buttons on the ADJUSTMENT1 Block are Facility and DSS. They have “F” (for

16


facility) and “D” (for DSS) in the Value lines of their respective property sheets.

CBC (View for HOMEBASED)

WHERE RECIPIENT_ID = :HOMEBASED.RECIPIENT_ID AND COST = :HOMEBASED.COST AND MAP_TYPE = 'P' AND DESTINATION IN ('C', 'DR')

Ensures that pending dates associated with only the current community-based Adjustment will be retrieved.

Table 6.4.2-1. Block Property Sheet Code. 7. Entity-Relationship Model The database tables in Map-122 do not have any primary/foreign key relationships, so an ERD has not been included. 8. Database Tables Subsections 8.1 and 8.2 describe the purpose of each table; name the fields, attributes, constraints, indexes, and primary keys (where applicable) for each table; and explain any parent/child relationships between tables. Subsection 8.3 names the Blocks that correspond to the various database tables.

8.1 Table Definitions This subsection describes each database table and names its fields, attributes, constraints, and indexes (where applicable). The owner of each table is MAPA.

8.1.1 ADJUSTMENT Stores Adjustment information for those Medicaid recipients who reside either in a facility or in the community (i.e., at home). There are no indexed columns in this table. RECIPIENT_ID NOT NULL VARCHAR2(15) ADJUSTMENT_ID NOT NULL NUMBER FIRST_NAME VARCHAR2(20) LAST_NAME NOT NULL VARCHAR2(20) FACILITY_NAME VARCHAR2(75) FACILITY_ADDRESS VARCHAR2(40) FACILITY_ADDRESS2 VARCHAR2(40) CITY VARCHAR2(30) STATE VARCHAR2(2) ZIP VARCHAR2(15) SALUTATION VARCHAR2(40) SERVICE VARCHAR2(50) DESCRIPTION VARCHAR2(100) COST NUMBER(8,2) MAP_TYPE VARCHAR2(1) PEND_REASON1 VARCHAR2(1000) PEND_REASON2 VARCHAR2(1000) PEND_REASON3 VARCHAR2(1000) PEND_COMMENT1 VARCHAR2(1000) PEND_COMMENT2 VARCHAR2(1000) PEND_COMMENT3 VARCHAR2(1000) REJ_REASON1 VARCHAR2(1000)

17


REJ_REASON2 VARCHAR2(1000) REJ_REASON3 VARCHAR2(1000) DEN_REASON1 VARCHAR2(1000) DEN_REASON2 VARCHAR2(1000) DEN_REASON3 VARCHAR2(1000) ELIGIBILITY VARCHAR2(40) DSS VARCHAR2(75) POC VARCHAR2(40) POA VARCHAR2(40) DATE_RECEIVED DATE REVISED CHAR(1) ORIG_DATE DATE DESTINATION VARCHAR2(4) HOME_ADDRESS VARCHAR2(40) HOME_ADDRESS2 VARCHAR2(40) HOME_CITY VARCHAR2(30) HOME_STATE VARCHAR2(2) HOME_ZIP VARCHAR2(15) H_ADDRESS VARCHAR2(40) H_ADDRESS2 VARCHAR2(40) H_CITY VARCHAR2(30) H_STATE VARCHAR2(2) H_ZIP VARCHAR2(15)

8.1.2 DEN_REASON Stores the numerous reasons why Adjustment requests may be denied. Index name: PK_DEN. Index column: REASON_ID. REASON_ID NOT NULL VARCHAR2(4) DESCRIPTION NOT NULL VARCHAR2(1000)

8.1.3 DSS Stores address information for the different departments of social services that interact with DMAS. Index name: UNIQUE_DSS. Index column: CODE. DSS NOT NULL VARCHAR2(75) ADDR1 VARCHAR2(40) ADDR2 VARCHAR2(40) CITY VARCHAR2(30) STATE VARCHAR2(2) ZIP VARCHAR2(10) CODE NOT NULL VARCHAR2(5)

18


8.1.4 FACILITY

Stores address information for nursing homes and other facilities whose employees or residents submit and/or follow up on Map-122 Adjustment requests. Index name: UNIQUE_FAICLITY_ID. Index column: FACILITY_ID. FACILITY_ID NOT NULL NUMBER FACILITY_NAME NOT NULL VARCHAR2(75) FACILITY_ADDRESS NOT NULL VARCHAR2(40) ADDRESS2 VARCHAR2(40) CITY NOT NULL VARCHAR2(30) STATE NOT NULL VARCHAR2(2) ZIP VARCHAR2(15) PHONE VARCHAR2(15) FAX VARCHAR2(15)

8.1.5 MAPREPORT This is an audit table for reports. It tracks which users have run which reports on what dates. This table does not have an index column. DATE_RUN DATE USER_RUN VARCHAR2(10) TYPE VARCHAR2(1)

8.1.6 NEXT_ADJUSTMENT_NUMBER This table stores Adjustment ID numbers. This table does not have any index columns associated with it. NEXT_ADJUSTMENT_ID NUMBER

8.1.7 PEND_REASON Stores the numerous reasons why Adjustment requests may be pending. Index name: PK_PEND. Index column: REASON_ID. REASON_ID NOT NULL VARCHAR2(4) DESCRIPTION NOT NULL VARCHAR2(1000)

8.1.8 REJECT Stores the numerous reasons why Adjustment requests may be rejected. This table does not have an index column associated with it. REASON_ID NOT NULL VARCHAR2(4) DESCRIPTION NOT NULL VARCHAR2(1000)

19


8.1.9 TEMP_ADJUSTMENT

This table is not used in the Map-122 Adjustment application.

8.1.10 TEMP_ADJUST This table is not used in the Map-122 Adjustment application.

8.1.11 T_ADJUSTMENT This table is not used in the Map-122 Adjustment application.

8.2 Parent/Child Table Relationships There are no parent/child table relationships among the Map-122 database tables.

8.3 Blocks and Corresponding Base Tables Table 8.3-1 below shows which database tables correspond to which Blocks in the Map-122 Adjustment System application.

Block Base Table ADJUSTMENT1 ADJUSTMENT ADJUSTMENT ADJUSTMENT PEND_REASON PEND_REASON DEN_REASON DEN_REASON REJECT REJECT DSS DSS FACILITY FACILITY HOMEBASED ADJUSTMENT CBC ADJUSTMENT

Table 8.3-1. Blocks and Base Tables. NOTE: The following database tables are not base tables for any Map-122 Blocks: MAPREPORT and NEXT_ADJUSTMENT_NUMBER.

20


Appendixes Click on the appendix you would like to view. Note that Appendixes A and B are Visio (.vsd) files, and Appendix C is a MS Word (.doc) file. Appendix A (User Task Flowcharts) Appendix B (System Event Flowcharts) Appendix C (Program Unit Code)

21

Date post:	16-May-2018
Category:	Documents
Upload:	votram
View:	225 times
Download:	1 times

Oracle System Documentation - Virginia · flowchart processes relate to program Blocks, screen...

Documents