Process BXU/LXG file



BXU and LXG

RECONCILIATION

Verified and Updated November 2007

Procedures for Reviewing and Working the BXU/LXG Reconciliation

Purpose: To describe procedures to be used for correcting errors discovered during the BXU/LXG reconciliation process which are identified on the AVK569 Report.

References: STANFINS USERS Manual, Chapter 15-175



The AVK569 report from STANFINS compares the BXU file and the LXG file for current values of undelivered orders, accounts payable, and unliquidated obligations. Any differences between the three values on the two files are printed out and have to be researched and corrected. The AVK569 Report can be run through DARS to extract only the lines that need need research and corrective action. This report can also be obtained from OLRV (On Line Report Viewing ) as an alternative method to extract those lines that have erred out and require research and corrective action.

Procedures to Acquire AVK569 File from CDOIM

1) Receive request from Management Accounting asking for the AVK569 formatted for input into DARS.

2) Contact CDOIM and ask to have them provide the text file for the AVK569 out of the S4 cycle:

a. Give analyst the installation site id(s) for the AVK569(s)

b. Give analyst the file name of BXLX##.TXT (where ## is the siteid) for each AVK569

c. Give analyst the address of where to send the file(s). Example: Corp1 dARS subdirectory

d. Ask that the AVKJS4## job be modified to send the BXLX##.TXT files automatically to the server address after each S4 job.

3) Notify Management Accounting that the file is available.

a. Give applicable Management Accounting personnel locations and file name.

b. If necessary, arrange for Management Accounting personnel to have access to subdirectory.

c. If the file location is the Corp1 Server, Management Accounting personnel will:

1. Copy the BXLS##.TXT files to an accessible directory.

2. Copy file in ASCII mode.

3. If file is missing, contact Systems Management Division for assistance.

Note: Files are resident on the CORP1 Server for three working days. In the event that three working days pass, Systems Management Division must contact CDOIM to retransmit file.

PROCESS BXU/LXG FILE

A. STEPS TO RETRIEVE FILE FROM FILE TRANSFER PROTOCOL (FTP)

1. Retrieve AVK 569 file from local shared drive or from FTP Server. Check with systems to determine exact location for your site.

2. Copy AVK569.txt file to C: DARS/BXULXG directory

B. STEPS TO RENAME AND REMOVE THE HEADER LINE

1. The AVK569.txt file must be renamed and modified before Databased Accounting Reconciliation Systems (DARS) will upload the file successfully.

2. Using Windows NT Explorer, access C:\DARS\BXULXG and double click on the AV569.txt file.

3. The file will open into notepad where the modifications can be done and then rename the file BXLX##.txt.

4. The entire first line must be deleted so DARS will read the appropriate records. Highlight the entire first line and delete it, you must include the first asterisks in the 2nd line also. See line in bold and underlined example below.

Sample of the first page of the AVK 569 Report:

5. Click on File Save as and rename the file BXLX##.txt

6. Exit Windows NT Explorer

C. STEPS TO PROCESS FILE THROUGH DARS

1. Enter DARS

2. Select J (BXU/LXG, GL and TE files).

3. Select 1 (BXU LXG Reconciliation).

4. Select 1 (Upload new BXU/LXG file).

5. Select E (Upload the BXU LXG file).

6. Select 2 (Process the BXU LXG Reconciliation).

7. Select 3 (Print the BXU LXG Reconciliation).

8. Select X 3 times to exit DARS.

Procedures to Access AVK569 Report in OLRV

Note: If the steps do not work contact your OLRV modeler.

STEPS:

1. Log into OLRV

2. Select "View by Folder"

3. Select the specific installation reports folder.

4. Scroll down through the listed reports and select the AVK569**S4 (** equals the site ID number).

Select the most current BXU/LXG recon summary file (Excel format)

Correction Process for the BXU/LXG Reconciliation

1. There are two types of lines; the TML and TMK.

a. The TML line refers to the BXU (contains all the transactions in the 218/112 reports).

b. The TMK line refers to the LXG (contains only unliquidated obligations).

Always make sure nothing has changed before starting to correct one of these discrepancies.

2. There are several reasons that BXU/LXG errors occur. The primary reason is changes are made to Accounting Processing Codes (APC’s) without backing out transactions that have already processed against this APC.

3. In several of the examples listed below it will state “have systems run a User Aid”. A User Aid 12 should be run just before the Database goes to “clean up” each month. This will allow the program to correct the LXG records that have been affected by changes to Army Management Structure (AMS) or Program Element (PE). This will reduce the number of out-of-balance conditions on the BXU/LXG Report. Note: User Aid will not fix Ledger Code (LC) errors.

4. Sometimes a Phase has been performed to eliminate a line on the LXG that a site is unable to back out through Terminal Application Process System (TAPS). This is only okay if the BXU/LXG was already out-of-balance. If an out-of-balance condition does not exist, this phase process will cause one.

5. If a Phase is required then the input must be sent to the systems office by disk. See Page 32 for the specific layout for adding back a TML line to the LXG. See Page 33 for the specific layout for deleting a TML line from the LXG.

6. There are three reports that are generated with each Phase.

a. AVK 896 report merges the input from the Phase to the LXG.

b. AVK 758 report is the Card Error Non Stock Fund U/O LXGAVK Report.

c. AVK 760 report is the LXGAVK NSF U/O Card Input.

7. Sometimes both the AVK 758 and AVK 760 (R7 Cycle) reports are on the same text file and it is difficult to determine if a line actually erred out. Look all the way to the right hand side of the page under Error Codes. If there is an error code listed, refer to the legend at the bottom of the page to determine if the error code is a showstopper.

8. The AVK896 (RB Cycle) must be run to merge the fixes from the phase, into the LXG before an S4 can be processed.

9. It is essential that a log be maintained depicting the error and the related correction. For example, copies of the current LXG, the current BXU, the LXG after the correction, and the BXU after the correction would provide documentation of the error and the correction action(s). If your correction requires a Phase cycle(s) a copy of the Phase cycle(s) reports should also be maintained.

10. Following are examples of the various errors that show up on the BXU/LXG Reconciliation Report and the steps for correcting these errors. .

EXAMPLES

Example 1: Element of Resource (EOR) and Ledger Code error and the transactions are only showing up in the TML records.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |6 |2080 |

|21 |6 |2080 |

STEPS:

1. Verify that there are no transactions in the DAR file (See example of query on Page 21) and no transactions on the LXG. Verify that the amount of the TML line is actually on the BXU record (Use a query that has inception data see example on Page 19). Process a type action 40 in TAPS to reverse the 4140 line and verify after the daily cycle that the BXU record is showing a cumulative disbursement of $0.00 in that appropriation. If you can not find the original Document Reference Number (DRN) use a DRN with "BXULXG" within the body of the document number, one example follows:

DRN 000000BXULXG##

2. Process a type action 42 in TAPS to reverse the 4110 line. Verify after the daily cycle that the BXU record was showing a cumulative disbursement of $0.00 in that appropriation. .

3. Perform a phase to delete the two lines that were created by the LXG.

Example of LXG Record after Non-TBO blocks have processed.

FY LC DOC-NO APC EOE ODC OBLIG ACCRUAL DISB OBLIG-DATE DISB-DATE

--------------------------------------------------------------------------------

6 01 BXULXGCORRAMP1 6CAE 4140 2 .00 .00 12.30 00000 00109

6 17 BXULXGCORRAMP2 6CAE 4110 2 .00 .00 12.30- 00000 00110

GRAND TOTAL * .00 * .00 * .00

Sample Delete Phase Format:

MKBXULXGCORRAMP121 62080000002306500540041400121026CAE2 D

MKBXULXGCORRAMP221 62080000002306500540041100121026CAE2 D

4. Remember to delete the new entry that will post to the DAR file because of the TA 40’s to 4110 and 4140.

Example 2: Different Ledger Code for the TML and TMK lines, EOR is not 41##.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |6 |2080 |

|21 |6 |2080 |

STEPS:

1. At the time of correction, the LC was 23. Back out all transactions that have a LC 23 attached to them in a Closed cycle by disk input. (If you are certain that no additional lines would be created on the LXG, the reversal could be done on a daily cycle.) Notify appropriate personnel that Cash will temporarily be placed out of balance. Verify on the AVK 018 Report that the block processed.

Note: If the Current LC code for this APC is correct you will have to change the LC to the incorrect LC before beginning Step 1.

2. Change LC on the 2nd Closed cycled. Verify on the AVK 006 and AVK 003 report that the LC change processed.

3. Process transactions back into STANFINS during the next daily cycle to bring Cash back in balance.

4. When the APC has the correct LC , then have systems run a User Aid 12 which will allow the LXG records to be overwritten with the current information from the APC Master file. These lines should not be showing on the next BXU/LXG reconciliation spreadsheet

Example 3: Only have TMK line Obligation, Accrual and Disbursement are equal.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

| |

|21 |0 |2080 |

STEPS:

1. There is nothing to do to this line. The line will fall off on the next AVK569 update.

Note: If the S4 cycle is run before the end of month jobs (M3, MA, and M4) you could see these types of lines. If the S4 cycle is run after the end of month jobs you should not see these types of lines.

Example 4: Fiscal Station Number (FSN) 000000 and No APC is listed

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

| |

|NO APC |0000 |0 |

STEPS:

1. This error occurs when an APC is deleted from the APC Master file while there is still an open line on the Non-Stock Fund Orders & Payables (NSFOP). This will also affect your 218 Submission to departmental accounting.

2. Add back APC during regular daily cycle.

3. There should be an offsetting TMK line showing on the BXU/LXG Reconciliation Page.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

| |

|21 |9 |2010 |

Example 5: Different LC and multiple TML and TMK lines and EOR is 41##.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |0 |2010 |

|21 |0 |2010 |

Note: Total Disb diff amount $2784.38

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |0 |2010 |

|21 |0 |2010 |

Note: Total Disb diff amount $-2784.38

STEPS:

1. This condition is caused when the LC is changed without backing out any of the data on the LXG.

2. In this case for Operating Agency (OA) 01 Special Open Allotment for Retirement Advances the LC must be a ledger code 17. When the LC was changed to 05 then the advances showed up under the Accounts Payable section on the 218 Report and not the Advance Section (19).

3. At the time of correction, the LC was 05. Back out all transactions that have a LC 05 attached to them in a Closed cycle by disk input. (If you are certain that no additional lines would be created on the LXG, the reversal could be done on a daily cycle.) Notify appropriate personnel that Cash will temporarily be placed out of balance. Verify on the AVK 018 Report that the block processed.

Note: If the Current LC code for this APC is correct you will have to change the LC to the incorrect LC before beginning Step 1.

4. Change LC on the 2nd Closed cycled. Verify on the AVK 006 and AVK 003 report that the LC change processed.

5. Process transactions back into STANFINS during the next daily cycle to bring Cash back in balance.

Example 6: Difference between TMK and TML due to Program Year (PY) without Disbursements.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|21 |1 |2020 |

STEPS:

1. Verify the APC that is in the APC Master file has the correct PY. If it doesn’t process M2 Card to change APC in the next daily cycle.

2. When the APC has the correct PY, then have systems office run a User Aid 12, which will allow the LXG records to be overwritten with the current information from the APC Master file. Line should not be showing on the next BXU/LXG reconciliation spreadsheet.

Note: Since Disbursements are not involved you do not need to reverse disbursements prior to changing APC’s. See Example 7 if a disbursement is involved.

Example 7: Difference between TMK and TML due to Program Year (PY) with Disbursements.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|21 |1 |2020 |

STEPS:

1. At the time of correction, the PY was 1 Back out all transactions that have a PY 1 attached to them in a Closed cycle by disk input. (If you are certain that no additional lines would be created on the LXG, the reversal could be done on a daily cycle.) Notify appropriate personnel that Cash will temporarily be placed out of balance. Verify on the AVK 018 Report that the block processed.

Note: If the Current PY code for this APC is correct you will have to change the PY to the incorrect PY before beginning Step 1.

2. Change PY on the 2nd Closed cycled. Verify on the AVK 006 and AVK 003 report that the LC change processed.

3. Process transactions back into STANFINS during the next daily cycle to bring Cash back in balance.

4. When the APC has the correct PY, then have systems run a User Aid 12, which will allow the LXG records to be overwritten with the current information from the APC Master file. These lines should not be showing on the next BXU/LXG reconciliation spreadsheet

Example 8: Difference between TMK and TML due to Program Element (PE) without Disbursements

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|21 |1 |2020 |

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

| |

|21 |1 |2020 |

STEPS:

1. Verify the APC that is in the APC Master file has the correct PE. If it doesn’t, process a M2 Card to change the APC in the next daily cycle.

2. When the APC has the correct PE, then have systems run a User Aid 12, which will allow the LXG records to be overwritten with the current information from the APC Master file. These lines should not be showing on the next BXU/LXG reconciliation spreadsheet

Note: Since Disbursements are not involved you do not need to reverse disbursements prior to changing APC’s. See Example 9 if a disbursement is involved.

Example 9: Difference between TMK and TML due to Program Element (PE) with Disbursements

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|21 |1 |2020 |

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

| |

|21 |1 |2020 |

STEPS:

1. At the time of correction, the PE was 1210. Back out all transactions that have a PE 1210 attached to them in a Closed cycle by disk input. (If you are certain that no additional lines would be created on the LXG , the reversal could be done on a daily cycle.) Notify appropriate personnel that Cash will temporarily be placed out of balance. Verify on the AVK 018 Report that the block processed.

Note: If the Current PE code for this APC is correct you will have to change the PE to the incorrect PE before beginning Step 1.

2. Change PE on the 2nd Closed cycled. Verify on the AVK 006 and AVK 003 report that the PE change processed.

3. Process transactions back into STANFINS during the next daily cycle to bring Cash back in balance.

4. When the APC has the correct PE, then have systems run a User Aid 12 which will allow the LXG records to be overwritten with the current information from the APC Master file. These lines should not be showing on the next BXU/LXG reconciliation spreadsheet

Example 10: Difference due to LC only and TMK Error.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|97 |9 |0130 |

|97 |9 |0130 |

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|97 |9 |0130 |

STEPS:

1. Run the LXG Query and insert LC NE ‘17’ and EOE = ‘4110’ to identify which lines are being applied to LC 25 TMK line.

2. Input into TAPS a Type Action (TA) 40 debit and credit against each of these lines and the system will overlay the LC 25 with a LC 17.

LXG QUERY:

DATAQUERY: EDITOR

------------------------------------------------------------------------------------------------------------------------------

NAME: LXG TYPE: QUERY STATUS: PUBLIC

DESCRIPTION: LXG FOR ERRORS

…...+…...1…...+…...2......+…...3…...+…...4…...+…...5…...+…...6…...+…...7…...+…….

=============================== T O P =====================================

01 FIND LXG### APC = '####' FY = '#' EOE = '####'

02 SORT FY DOC-NO

03 PRINT TITLE 'LXG### EAST DATABASE'

04 FY APC EOE DOC-NO OBLIG AVK###MD$ ACCRUAL AVK###MD$ DISB AVK###MD$

05 ACCT-CLASS

=========================== B O T T O M ==================================

BXU query layout with Inception Data

01 FIND BXU### WITH FY = '#' EOR = '####' APC = '####' RT = '#'

02 OA = '##' ASN = '####' BSN = '####' LIMIT = '####' AMS4 = '####'

03

04 SET TOTOBLIG (11.2) = OBLIG-CM + OBLIG-FYTD + OBLIG-INC + DEOB-FYTD

05 + DEOB-CM

06 SET TOTDISB (11.2) = DISB-CM-BY-US + DISB-CM-BY-OTH + DISB-FYTD

07 + DISB-CM-BY-INT + DISB-INC

08 SET TOTACCR (11.2) = ACCR-CM + ACCR-FYTD + ACCR-INC

09 PRINT FY RT AMS4 APC LC EOR ODC (TOTOBLIG) AVK###MD$ (TOTACCR) AVK###MD$

10 (TOTDISB) AVK###MD$ (OBLIG-INC) AVK###MD$ (OBLIG-FYTD) AVK###MD$

11 (OBLIG-CM) AVK###MD$ (ACCR-INC) AVK###MD$(ACCR-FYTD) AVK###MD$

12 (ACCR-CM) AVK###MD$ (DISB-INC) AVK###MD$ (DISB-FYTD) AVK###MD$

13 (DISB-CM-BY-US) AVK###MD$ (DISB-CM-BY-OTH) AVK###MD$ (DISB-CM-BY-INT)

14 AVK###MD$

BXU query output with Inception Data

|F |

|Y |

|Dept |FY |BSN |

|21 |1 |2020 |

|21 |1 |2010 |

STEPS:

1. Verify that there are no transactions on the LXG. Verify that the amount of the TML line is actually on the BXU record (Use a query that has inception data see example on Page 19). Verify document reference number in ATLAS. Verify if APC is still established incorrectly.

5. Change APC back to invalid LC. Process a TA23, TA32, and TA40 to reverse the obligation, accrual, and disbursement. Have systems perform a UserAid 12. Verify after the daily (or closed) cycle that the BXU record is showing a cumulative accounting line of $0.00 in that LC appropriation. If you can not find the original Document Reference Number (DRN) use a DRN with "BXULXG" within the body of the document number, one example follows:

DRN 000000BXULXG##

2. Change the APC back to the valid LC. Process a TA23, TA32, and TA40 to reprocess lines. Have systems perform a UserAid 12. Verify after the daily cycle that the BXU record is showing an obligation, accrual, and disbursement for the same dollar figure in the valid LC.

Example 12: Difference due to EOR TML and TMK Error.

There are lines on the LXG. The difference is between EOR. This is a direct appropriation.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|21 |1 |2020 |

|21 |1 |2020 |

|21 |1 |2020 |

|21 |1 |2020 |

STEPS:

1. Query the BXU for each EOR to determine which dollar values are incorrect and by what APC. ATLAS was pulled for each APC. Obligations and disbursements were matched to the BXU determine which APCs were out-of-balance.

2. Query the LXG for the open obligations and disbursements. Deduct the open LXG lines from the BXU to determine if the out-of-balance agrees with AVK569.

6. The BXU was adjusted for disbursements in the above example. This adjustment creates lines on the LXG. It could not be determined which document reference number created the out-of-balance. If you can not find the original Document Reference Number (DRN) use a DRN with "BXULXG" within the body of the document number, one example follows:

DRN 000000BXULXG##

3. Verify that the BXU is now corrected. Process a phase II to clear the lines created on the LXG by the adjustment in step 3.

4. Verify that the BXU and LXG have been corrected.

Example 13: Difference due to LC only TML Error Automatic

There are no open lines in the LXG. The difference is between the LC for an automatic appropriation.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |8 |2020 |

|21 |8 |2020 |

STEPS:

1. Verify that there are no transactions on the LXG. Verify that the amount of the TML line is actually on the BXU record (Use a query that has inception data see example on Page 19). Verify document reference number in ATLAS and that the line being corrected is AFCR 1 (Automatic Fund Control Register). AFCR 1 is a manual transaction. AFCR 5 is a process creation. Correct the AFCR 1 only, this will automatically correct the AFCR 5 transaction. Verify if APC is still established incorrectly.

7. Change APC back to invalid LC. Process a TA23, TA32, and TA40 to reverse the obligation, accrual, and disbursement. Have systems perform a UserAid 12. Verify after the daily (or closed) cycle that the BXU record is showing a cumulative accounting line of $0.00 in that LC appropriation. If you can not find the original Document Reference Number (DRN) use a DRN with "BXULXG" within the body of the document number, one example follows:

DRN 000000BXULXG##

2. Change the APC back to the valid LC. Process a TA23, TA32, and TA40 to reprocess lines. Have systems perform a UserAid 12. Verify after the daily cycle that the BXU record is showing an obligation, accrual, and disbursement for the same dollar figure in the valid LC.

Example 14: Difference due to EOR 46## with obligation TML only.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |0 |2020 |

Contact Systems and Procedures for assistance in this type of error.

Example 15: Difference due to ledger code TML and TMK error.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

STEPS:

1. Reverse the 4140 under the wrong AMS 9966 – LXG (LC 01).

2. Post the disbursement under the correct AMS 9948 (LC 18).

Example 16: Difference due to ODC TML error.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |1 |2020 |

|21 |1 |2020 |

NOTE: Total Undelivered Orders difference amount $ 986.74

Contact Systems and Procedures for assistance in this type of error. Systems and Procedures will add ODC in the BXU to match corresponding LXG records.

Example 17: Difference due to ledger code TML error.

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |0 |2020 |

|21 |0 |2020 |

|Sample extract from the AVK569 report: |

|Dept |FY |BSN |

|21 |0 |2020 |

NOTE: Total Disbursement difference amount $ 145,105.44

STEPS:

1. Perform a phase to delete the lines of the LXG (LC 17) with the invalid EOR.

2. Perform phase to add the lines back under EOR 4140 (LC 18).

3. Contact Systems & Procedures Office to correct the AXU to match the LXG.

APPENDIX

A-1

AVK 896 Report layout

FINANCIAL MANAGEMENT SYSTEM

STATUS OF XG TAPE MERGE

PROGRAM PXGAVK18 00000 RRC AVK-896 PCN AVK-896

TIME 13.44.27

DATE PREPARED 04 20 00

PRINTER * PUNCH

NO COPIES 1 * CARD FORM NONE

FORM NUMBER 1413 * STKR P1 NONE

20/04/00 STATUS OF XG TAPE MERGE

FILE SOURCE INPUT RECORD OUTPUT RECORD

******** DUPLICATE RECORD KEYS ********

BXGAVK OLD BXGAVK 0 0

EXGAVK OLD EXGAVK 60 60

FXGAVK OLD FXGAVK 838 838

GXGAVK OLD GXGAVK 0 0

HXGAVK OLD HXGAVK 5,743 5,743

JXGAVK OLD JXGAVK 873 873

LXGAVK CANDIDATE 108,851 108,851

NXGAVK OLD NXGAVK 125,338 125,338

PAGE 1

END OF REPORT

A-2

AVK758 and AVK 760 Combined no errors

FINANCIAL MANAGEMENT SYSTEM

CARD ERROR NON STOCK FUND U/O LXGAVK

PROGRAM ALKIR PWRAVK12 RRC AVK-758 PCN AVK-758

TIME 07.45.03

DATE PREPARED 07 06 00

PRINTER * PUNCH

NO COPIES 3 * CARD FORM N/A

FORM NO 1413 * STKR P1 N/A

FINANCIAL MANAGEMENT SYSTEM

LXGAVK NSF U/O CARD INPUT

PROGRAM ALKIR PWRAVK12 RRC AVK-760 PCN AVK-760

TIME 07.45.03

DATE PREPARED 07 06 00

PRINTER * PUNCH

NO COPIES 3 * CARD FORM N/A

FORM NO 1413 * STKR P1 N/A

CARD ERROR NON STOCK FUND U/O LXGAVK 06/07/00

ERROR CODES LXGAVK NSF U/O CARD INPUT 06/07/00

PWRAVK-CNTL01=PRINT

MKMAR92160000000801104110200000 00000580300 KA

MKMAR92160000000801101199200000 0000058030} KA

MKMIPR6BLOF0000121 62080000002306500540025GZ0121026CAE1 D

MKMIPR6BLOF0000221 62080000002306500540025GZ0121026CAE1 D

-LEGEND

*1 NO MATCHING APC

*2 INVALID DOCUMENT NUMBER

*3 INVALID OBLIGATION DATA CODE

*4 INVALID CYCLE DATE

*5 NON-NUMERIC AMOUNT FIELD

*6 INVALID FINAL INDICATOR.

*7 INVALID ACTION-CODE

*8 INVALID LEDGER-CODE ON APC-MASTER

*9 INVALID STATUS FLAG

*10 CARD ID IS NOT LXGAVK

PAGE 1

END OF REPORT

PAGE 1

END OF REPORT

A-3

AVK758 and AVK 760 Combined with errors

FINANCIAL MANAGEMENT SYSTEM

LXGAVK NSF U/O CARD INPUT

PROGRAM ALKIR PWRAVK12 RRC AVK-760 PCN AVK-760

TIME 07.06.12

DATE PREPARED 12 21 00

PRINTER * PUNCH

NO COPIES 3 * CARD FORM N/A

FORM NO 1413 * STKR P1 N/A

CARD ERROR NON STOCK FUND U/O LXGAVK 21/12/00

ERROR CODES

LXGAVK NSF U/O CARD INPUT 21/12/00

PWRAVK-CNTL01=PRINT

MKMAR9216000000021 820100000001004019998411001210201102 D

MKMAR9216000000021 820100000001004019998119901210201102 D

MKCAR384100000006GGGG4110200000 0000001676Q KA

MKHIN8209MISCOLL6GGGG4120200000 0000000240} KA

MKJOH228700000006GGGG4120200000 0000020711R KA

MKMAR831600000006GGGG4110200000 0000002608K KA

MKWEB898611002006GGGG4110200000 0000000850L KA

* 10

MKCAR3841000000021 6207000000230993009301198012102GGGG2 D

MKHIN8209MISCOLL21 62070000002309930093011BB012102GGGG2 D

MKJOH2287000000021 62070000002309930093011BB012102GGGG2 D

MKMAR8316000000021 6207000000230993009301198012102GGGG2 D

MKWEB8986110020021 6207000000230993009301198012102GGGG2 D

* 10

LEGEND

1 NO MATCHING APC

2 INVALID DOCUMENT NUMBER

3 INVALID OBLIGATION DATA CODE

4 INVALID CYCLE DATE

5 NON-NUMERIC AMOUNT FIELD

6 INVALID FINAL INDICATOR.

7 INVALID ACTION-CODE

8 INVALID LEDGER-CODE ON APC-MASTER

9 INVALID STATUS FLAG

10 CARD ID IS NOT LXGAVK

PAGE 1

END OF REPORT

A-4

STANFINS User’s Manual Change 44, 1 Mar 1989

FILE: NON-STOCK FUND ORDERS AND PAYABLES FILE (LXGAVK)

RECORD FORMAT: ADD OR CHANGE

DESCRIPTION

LENGTH POSITION

File ID (Constant ‘MK’) 2 AN 1-2

Document Number 14 AN 3-16

Fiscal Year 1 AN 17

Accounting Processing Code 4 AN 18-21

Element of Resource 4 AN 22-25

Obligation Data Code 1 AN 26

(’1’ or ‘2’)

Obligation Cycle Date 5 AN 27-31

(Julian Date)

Blank 3 AN 32-34

Name 6 AN 35-40

Blank 2 AN 41-42

Obligation Amount 1 1AN 43-53

Accrual Amount 11 AN 54-64

Disbursement Amount 11 AN 65-75

Accrual-Final (’F’ or Blank) 1 AN 76

Disbursement-Final 1 AN 77

('F’ or Blank)

Status Flag (’L’ or Blank) 1 AN 78

Liquidation Indicator 1 AN 79

Action Code (Add or Change) 1 AN 80

(’A’ or ‘C’)

A-5

STANFINS User’s Manual Change 44, 1 Mar 1989

FILE: NON-STOCK FUND ORDERS AND PAYABLES FILE (LXGAVK)

Record Format: Delete

DESCRIPTION LENGTH POSITION

File ID (Constant ‘MK’) 2 AN 1-2

Document Number 14 AN 3-16

Accounting Classification 4 AN 17-50

Department 2 AN 17-18

Blank 1 AN 19

Fiscal Year 1 AN 20

Basic Symbol 4 AN 21-24

Limit 4 AN 25-28

Program Year 1 AN 29

Operating Agency 2 AN 30-31

Disbursement Desig. 1 AN 32

Allotment Serial 4 AN 33-36

Program Element 4 AN 37-40

Element of Expense 4 AN 41-44

Fiscal Station Number 6 AN 45-50

Accounting Processing Code 4 AN 51-54

Obligation Data Code 1 AN 55

Blanks 24 AN 56-79

Action Code (Constant ‘D’) 1 AN 80

|Acronym Table |

|AMS |Army Management Structure |

|APC |Accounting Processing Code |

|DARS |Databased Accounting Reconciliation Systems |

|DRN |Document Reference Number |

|EOR |Element of Resource |

|EXP-ANN |Expense Annual or Expenditure Annual |

|FSN |Fiscal Station Number |

|FTP |File Transfer Protocol |

|LC |Ledger Code |

|LEV |Level |

|NSFOP |Non-Stock Fund Orders & Payables |

|OA |Operating Agency |

|PE |Program Element |

|PY |Program Year |

|SOP |Standard Operating Procedures |

|STANFINS |Standard Finance System |

|TA |Type Action Code |

|TAPS |Terminal Application Process System |

|TBO |Transaction By Others |

-----------------------

1520569 D R U0

*

*

*

* FINANCIAL MANAGEMENT SYSTEM

* BXUAVK VS LXGAVK RECONCILIATION

* PROGRAM ALKIR PTZAVK25 RRC AVK-569 PCN AVK-569

* TIME 14.44.16

* DATE PREPARED 08 31 00

* PRINTER * PUNCH

* NO COPIES 6 * CARD FORM N/A

* FORM NO 1413 * STKR P1 N/A

*

*

[pic]

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download