DFAS-DE 7077.2-M SECTION 16.

29 November 2002

POSTING INTERNAL RECORDS
16.1 LOADING LIMITATIONS, TARGETS--NONOPERATING BUDGET RECORDS. After CSRs, FSRs, and PSRs have been established and audited for validity, establish opening balances by processing limitation or target transactions. The balances loaded may be updated later (increased or decreased). 16.2 UPDATING LIMITATIONS OR TARGETS--NONOPERATING BUDGET RECORDS. Enter the action code, applicable addresses, appropriate post codes to increase or decrease the particular Bal-ID, amount of the adjustment, and the document number through the remote, if applicable. 16.3 LOADING LIMITATIONS, TARGETS--OPERATING BUDGET RECORDS. Establish opening balances for operating-budget-funded records the same as nonoperating budget records (e.g., enter action code, PSRA, FSRA, post code, amount, and document number). Expense or obligation authority base operating budget funds are issued by OBY and FY. Load current-year expense obligation authority as target or limitation to current operating budget year (COBY) and current fiscal year (CFY) records only. Load prior-year expense or obligation authority to prior operating budget year (POBY), and prior fiscal year (PFY) records, or COBY and PFY records. Load expense obligation authority in a way that provides a target for tracking expenses and the limitation for appropriate fund control. Use the following Bal-IDs when loading targets and limitations: G--Annual expense or obligation authority. H--Quarterly expense or obligation authority. J--Anticipated reimbursement. W--Quarterly anticipated reimbursements. a. CFY, COBY Records. Expense and obligations authorities are received from the base budget office at the beginning of each fiscal year and the new targets are loaded into the database. NOTE: These targets are identified to specific Responsibility Center/Cost Center (RC/CC). However, portions of the amounts may be associated with a reimbursable UOO. When applicable, assign fund type L and the appropriate sales code. See paragraph 16.6. b. PFY, COBY Records. The authority loaded to these records provides control over that part of PFY obligations and UOO amounts carried forward and identified to the COBY. During fiscal yearend processing, these amounts are programmatically loaded as quarterly expense authority (QEA) in an amount equal to the actual UOOs as of 1 Oct. Post only increases or decreases to the prior-year documents into these records. c. PFY and POBY Records. The authority loaded to these records provides control over that part of PFY obligations or expenses and earned reimbursements identified to prior years. Yearend programs

DFAS-DE 7077.2-M

will maintain the current balance. Post only increases or decreases to the prior-year documents into these records. 16.4 LOADING OF REIMBURSABLE PROGRAM AUTHORITIES. The loading of reimbursable expense or obligation authority on the OBA document requires special considerations. These reimbursable authorities provide the amount of expected or anticipated reimbursements from COBY operations. To determine amounts to be loaded for the reimbursement program, the budget office: a. Computes the anticipated reimbursement, and determines the amounts to be loaded for anticipated reimbursements by EEIC, sales code, MFP, and RC/CC. Posts these amounts to the fund type M records. Establishes these amounts to track and meet the reimbursable program. b. Computes total authority, and combines the amounts loaded to fund type M records and direct program expense/obligation authority amounts. This total is posted to fund type L records (without sales code) through computations shown in paragraph 16.6. c. Identifies reimbursable UOO and expense or obligation authority associated with reimbursements expected to be initially recorded as UOO. Establish amounts in fund type L, and fund types A and C if sales code is 73 or BPAC is nonreimbursable records with sales code. Also include FMS country, master case, and line item code for sales code 73. 16.5 SEQUENCE OF PROCESSING LIMITATION AND OR TARGET TRANSACTIONS. The sequence in which limitation and or target transactions are processed could cause them to reject unnecessarily. The following are examples of these conditions. a. Example 1: If the increase to quarterly authority (Bal-IDs A, H, or W) is processed before the increase to annual authority (Bal-IDs B, G, or J), the transaction causes quarterly authority to exceed annual authority at FSR level. b. Example 2: When moving quarterly authority from one PSR to another and the decrease is processed first, this causes quarterly authority to be less than total obligations (Bal-IDs O+U+E) at FSR level. To avoid rejects that occur solely because of the sequence of input, it may be desirable to use the "0" limitation override action code described in paragraph 15.2i. If action code is "0" the following procedures: (1) Process an addressable inquiry against the FSRs for which the authority adjustments are to be made (paragraph 20.11). (2) Process the authority adjustment transactions using the "0" override action code. (3) Process an addressable inquiry against the FSRs for which the authority adjustments were processed.

16.36 MESSAGE - 0010 REJ, INVALID ACTION CODE. a. Explanation. Input posting requires special action. An example is post code UX with document number. This requires a DSR to be created with a negative balance. b. Probable Cause. Remote operator or accounting technician error. Correct the action code. 16.37 MESSAGE - 0020 REJ, ADDRESS MUST BE BLANK. a. Explanation. Input posting contains addresses when the action code indicates no addresses should be used (establishment of new CSR, miscellaneous MAFR transactions, etc.). b. Probable Cause. Remote operator or accounting technician error. Determine cause for reject by comparing address field and action code.
Addresses cannot be used with action codes GL, CR, MM, NC, or NF. Correct the source document using the proper action code if addresses are required. 16.38 MESSAGE - 0021 REJ, PSRA ________ EXCEEDS FILE LIMITS. a. Explanation. on the file. Input PSRA is greater than the number of records
b. Probable Cause. Remote operator or accounting technician error. Compare the message to the source document and the PSRs in address directory. Make corrected entry to include PSR, which is in PSR file limits. 16.39 MESSAGE - 0022 REJ, DSRA EXCEEDS FILE LIMITS. a. Explanation. on the file. Input DSRA is greater than the number of records
b. Probable Cause. Remote operator or accounting technician error. Correct input with proper DSRA and send to remote operator for processing. 16.40 MESSAGE - 0023 REJ, PSRA INVALID OR MISSING. See message 0033. 16.41 MESSAGE - 0024 REJ, DSRA INVALID OR MISSING. a. Explanation. Input posting requires a DSRA. An example is a post code CO. A DSRA is required to post the decrease commitment action. This message could also indicate an attempt to post an open balance to FSR/PSR level with no document number in the input. b. Probable Cause. Remote operator or accounting technician error. Correct input with proper DSRA and send to remote operator for posting. 16.42 MESSAGE - 0025 REJ, DSR INACTIVE. a. Explanation. Input transaction attempted to access a killed DSR, or a DSR was not established. b. Probable Cause. Remote operator or accounting technician error. Determine whether transaction was previously posted or if balance was deleted. If document requires posting, prepare new input citing proper post code and correct address to update the correct IAS record, and send to remote operator for processing. 16.43 MESSAGE - 0026 REJ, FSR HAS PSRs LINKED. See message 0605. 16.44 MESSAGE - 0027 REJ, PSR HAS DSRs LINKED. See message 0605.

16.45 MESSAGE - 0028 REJ, INVALID REC-TYPE. a. Explanation. Record type in the input does not correspond with the action code. For example, action code XD must have a "D" file-ID followed by six digits of numeric data in the first address field. The second address file must have a "P" file-ID followed by six digits of numeric data. b. Probable Cause. Remote operator or accounting technician error. Compare the message to the inquiry request to find out cause of error. Make corrected entry to include proper record code (C, F, P, or D). 16.46 MESSAGE - 0029 REJ, INVALID CURRENCY CODE. See section 29. 16.47 MESSAGE - 0030/0031 REJ, XXXXXXX RELATES TO YYYYYYY. a. Explanation. XXXXXXX is the lower level record addressed and YYYYYYY is the next higher related record that XXXXXXX is related. The lower level record is not linked to higher level record addressed. b. Probable Cause. Correct the entry. Remote operator or accounting technician error.
16.48 MESSAGE - 0032 REJ, FSRA EXCEEDS FILE LIMITS. See message 0603. 16.49 MESSAGE - 0033 REJ, FSRA, INVALID, OR MISSING. a. Explanation. Input posting requires a valid FSR. The input file-ID must be "F" with six digits of numeric data (must be greater than 000000). Each update to IAS records must contain the proper addresses. b. Probable Cause. Remote operator or accounting technician error. Correct input to include applicable FSR. 16.50 MESSAGE - 0034 REJ, FSR INACTIVE. See message 0604. 16.51 MESSAGE - 0035 REJ, PSR INACTIVE. a. Explanation. Input transaction tried to access an inactive PSR.
b. Probable Cause. Remote operator or accounting technician error. Compare the message to the source document. If the error is due to an improperly cited PSRA, reenter with the correct PSRA. Otherwise, look for the accounting classification cited on the source document in the latest directory. If the transaction is to establish a DSR and the required PSR cannot be found in the address directory, then a PSR will need to be established before the transaction can be input. 16.52 MESSAGE - 0040 REJ, INCOMPATIBLE AFO.
a. Explanation. An attempt was made to access records for a different AFO-ID than the AFO-ID currently open on the remote. b. Probable Cause. Remote operator error or accounting technician error. If the reject is caused by improper AFO-ID, the technician prepares corrected input with the proper AFO-ID code. If there is more than one AFO-ID code assigned to the same remote, the documents must be held in proper sequence until the remote is open for the AFOID code applicable to the documents to be recorded. 16.53 MESSAGE - 0041 REJ, INVALID POST CODE. a. Explanation. following reasons: Input post code is invalid for one of the

(1) Invalid action code. (2) Bal-ID codes are not compatible with the fund type. (3) More than one Bal-ID code was used in posting to a balance that is only in the FSR/PSR (ABA and allotment). (4) Bal-ID code is not compatible with the FY/OBY in the record addressed. (5) When posting to a DSR, a new document number was used with no Bal-ID. (6) Action code "F" used with one position of the post code equal to an "X". (7) If input was to kill a record (action code KC, KF, or KP), the post code must be blank. (8) When posting general ledger transactions, the positive BalID field of the input transactions was not "X". b. Probable Cause. Remote operator or accounting technician error. Analyze post code and find out cause for error. Make corrected entry to include valid post code. 16.54 MESSAGE - 0042 REJ, INVALID AFO. a. Explanation. An attempt was made to open a remote with an AFOID code other than 0 through 9. b. Probable Cause. Remote operator error. Check input to determine code used. Make corrected input using proper numeric code assigned to the AFO. 16.55 MESSAGE - 0043 REJ, INVALID FUND TYPE. a. Explanation. The input attempted to establish FSR with an invalid fund type. If input is an inquiry request, an invalid fund type has been requested. Fund type must be blank when creating a CSR.
b. Probable Cause. Remote operator or accounting technician error. Compare the message to the source document, or if inquiry, compare with applicable inquiry in section 20. Make corrected entry to reflect proper fund type. 16.56 MESSAGE - 0044 REJ, INVALID/MISSING 0-1 DATA--AG/SAG DOES NOT MATCH PEC/BA CODE. a. Explanation. Attempting to build an address that contains erroneous data. Receives error message during a database reconciliation. b. Probable Cause. Remote operator or accounting technician error. During an address build, ensure compatible data is entered on the screen, such as compatible factors like the AG/SAG matches PEC/BA code. Address created with correct data element will not present error message during database consolidation. 16.57 MESSAGE - 0050 REJ, * IS NOT POSITIVE BALANCE. a. Explanation. An asterisk represents the negative Bal-ID TRT, position 18, resulting from the input transaction. Action code RD or RP was not used in an attempt to reduce a balance, except paid or collected, which is zero or less. b. Probable Cause. Remote operator or accounting technician error. If a Bal-ID code must be less than zero, use action code RD or RP (depending on the lowest level record being addressed). 16.58 MESSAGE - 0051 REJ, RECORD HAS BALANCE. a. Explanation. Input posting attempted to kill a CSR, FSR, or PSR, which has an amount in one or more Bal-IDs. b. Probable Cause. Remote operator or accounting technician error. Compare the message to the source document. If the record is to be killed, find out what instructions were issued regarding the balance. If unknown, ask PC supervisor for guidance. Make an entry to reduce balance and process another entry to kill the record. 16.59 MESSAGE - 0052 REJ, INVALID AMOUNT. a. Explanation. Amount entered is other than numeric or is blank and an amount is required. b. Probable Cause. Remote operator error. Check message to source document to find cause for reject. Make a correction to include a numeric amount. The amount field may be blank when establishing the FSRs and PSRs, and when processing no-pay vouchers. NP must be in the third and fourth positions of the DOV number when processing no-pay vouchers. Do not use zone punches or parentheses in the amount field. 16.60 MESSAGE - 0060 REJ, DOV BLANK.

a. Explanation. QD transaction processed. The save indicator has been removed if all other edits are successful. b. Probable Cause. If this is the only message displayed, the QD transaction was successful. If other messages appear with this, the data must be corrected and the transaction reentered. 16.70 MESSAGE - 0081 REJ, FUND TYPE K: DSI WAS NOT DELETED.
a. Explanation. The input QD transaction affected a fund type K record and did not have the override code of "8" in position 113. b. Probable Cause. Remote operator or accounting technician error. If the DSI is to be removed from a fund type K record, positions 49 and 113 must contain the proper data. 16.71 MESSAGE - 0100 REJ, INVALID GL DATA. a. Explanation. Invalid GLA codes input. When both the debit and credit GLA codes contain zeros, the transaction is rejected. b. Probable Cause. Remote operator or accounting technician error. Make corrected entry to include proper GLA codes.
16.72 MESSAGE - 0101 REJ, INVALID DR GLA. a. Explanation. Input posting for action code GL requires a 3- or 5-digit debit GLA code. b. Probable Cause. Remote operator or accounting technician error. Make a corrected entry to include valid GLA code. 16.73 MESSAGE - 0110 REJ, DBOF-EEIC REQUIRED. a. Explanation. Defense Business Operations Fund (DBOF) (fund code 68) general ledger (action code GL) postings to GLAC 321, prior year adjustment, require EEIC. b. Probable Cause. Remote operator or accounting technician error. Prepare corrected input to include EEIC. 16.74 MESSAGE - 0111 REJ, INVALID EEIC. See section 82. 16.75 MESSAGE - 0120 REJ, CSI REQUIRED. a. REJ-INVALID EEIC. Input creating an RCM record must be blank in the EEIC fields, or contain three or five positions of EEIC, left justified. Once a blank position is encountered, the remaining positions must be blank. b. Probable Cause. Remote operator error. Refer to source documents for correct CSI and make a corrected entry.
16.76 MESSAGE - 0121 REJ, INVALID/MISSING CD. a. Explanation. Interim Workload Information Management System (IWIMS) input transaction with a CSI B requires an alpha CD. When the CD is blank or numeric, the transaction is rejected with the above message. b. Probable Cause. Remote operator or accounting technician error. If CSI B is applicable, determine proper CD and reenter transaction. If CSI B is not applicable, reenter transaction without CD or CSI. 16.77 MESSAGE - 0122 REJ, INVALID CR-GLA. a. Explanation. Posting requires a 3- or 5-digit credit GLA code.

b. Probable Cause. Accounting technician error or reject caused by posting budget data. See paragraph 16.143. 16.114 MESSAGE - 0609 REJ, C OVER TAA CSR PRIORITY.
a. Explanation. Gross commitments (E+U+O+C) exceed quarterly total actual authority (A/H or A/H-W+D+F+R whichever is less). b. Probable Cause. This notice is caused by posting an increased unobligated commitment (C) transaction. 16.115 MESSAGE - 0610 REJ, W OVER J CSR PRIORITY. a. Explanation. Quarterly anticipated reimbursement (W) exceed annual anticipated reimbursement (J). b. Probable Cause. Accounting technician error or a reject caused by posting budget data. See paragraph 16.143. 16.116 MESSAGE - 0614 REJ, FSR REQUIRES CSR LINKAGE. a. Explanation. Input posting requires a CSRA.
b. Probable Cause. Remote operator or accounting technician error. Verify addresses with the address directory and reenter with valid CSRA. 16.117 MESSAGE - 0704 REJ, ASN-OBAN INVALID OR MISSING. a. Explanation. Input ASN-OBAN must be alphanumeric, and mandatory at CSR level for fund types A, B, C, D, J, L, and M. ASN is mandatory at FSR level for fund type E. b. Probable Cause. Remote operator or accounting technician error. Compare input to source document. Make corrected entry with valid ASN-OBAN. 16.118 MESSAGE - 0712 REJ, TYPE VENDOR MUST BE BLANK. a. Explanation. If fund code is 9-alpha or fund type is J or M, type vendor code must be blank. This edit must be bypassed, if required by paragraph 15.18a or 19.46b. b. Probable Cause. Remote operator or accounting technician error. Compare input to source document. Make corrected entry without type vendor code, if fund type is J or M. 16.119 MESSAGE - 0713 REJ, DOD FC NOT NUMERIC. a. Explanation. If fund type is L or M, the Department of Defense Functional Category (DoD FC) must be numeric and is mandatory at no lower than PSR level. b. Probable Cause. Remote operator or accounting technician error. Make corrected entry with valid DoD FC. 16.120 MESSAGE - 0714 REJ, DOD FC MUST BE BLANK.
DFAS-DE 7077.2-M a. Explanation. be blank.
If fund type is A and fund code is 29, DoD FC must
b. Probable Cause. Remote operator or accounting technician error. Make corrected entry without DoD FC. 16.121 MESSAGE - 0715 REJ, EEIC INVALID OR MISSING. a. Explanation. If fund type is A, L or M, and fund code is 29, then EEIC is mandatory at no lower than PSR level. Validity check is for alphanumeric characters. This edit is excluded if fiscal year is M and fund code is 29. b. Probable Cause. Remote operator or accounting technician error. Make corrected entry to include valid EEIC. 16.122 MESSAGE - 0717 REJ, RC/CC INVALID OR MISSING. a. Explanation. If fund type is A, L or M, and fund code is 29, RC/CC is mandatory at no lower than PSR level. Exception: If RC/CC equals spaces, PEC must be XXX99F, EEIC must contain at least three digits, and the DoD FC must be 99 (fund type L only). Validity check is for alphanumeric characters. See figure 16-6. b. Probable Cause. Remote operator or accounting technician error. Make corrected entry to include proper coding per figure 16-6. 16.123 MESSAGE - 0720 REJ, ESP INVALID. a. Explanation. Validity check for ESP code is for a 2-position alphanumeric code. See figure 16-6 for fund types applicable to this edit. b. Probable Cause. Remote operator or accounting technician error. Make a corrected entry with valid ESP code. 16.124 MESSAGE - 0721 REJ, RC/CC-PEC-MFP-INCOMPATIBLE. a. Explanation. fiscal year. Validity check on PEC based on fund type and

b. Probable Cause. Remote operator or accounting technician error. Make applicable corrections and reenter. 16.125 MESSAGE - 0722 REJ, RC/CC-DOD FC INCOMPATIBLE. a. Explanation. See figure 16-7.
b. Probable Cause. Remote operator or accounting technician error. Make corrected entry per figure 16-7. 16.126 MESSAGE - 0724 REJ, PEC-BPAC INCOMPATIBLE. a. Explanation. If input is fund type A, fund code 29, and BPAC is 69XXXX, 6X920X, 6X099X, or 6600BB, (where X equals any alphanumeric
character), PEC must be blank. year is M. b. Probable Cause. Make corrected entry.
This edit is excluded if the fiscal
Remote operator or accounting technician error.
16.127 MESSAGE - 0727 REJ, ABOVE REJECTS FATAL FURTHER EDITS NOT FEASIBLE. a. Explanation. Certain reject messages are considered to be fatal and further edits would be meaningless. The following message numbers are considered to be fatal at CSR level (action code NC): 040, 043, 132, 141, 150, 171, 210, 235, and 999. The following message numbers are considered to be fatal at FSR level (action code BF and NF): 002, 028, 040, 043, 076, 210, 211, 231, 250, 603, and 999. The following message numbers are considered to be fatal at PSR level (action codes BP and PF): 002, 028, 032, 033, 034, 076, 077, 210, 231, 250, and 999. b. Probable Cause. Remote operator or accounting technician error. Correct input according to the fatal error received. 16.128 MESSAGE - 0728 REJ, TRANSACTION REJECTED FOR REASONS ABOVE. a. Explanation. When creating a new address (action code NF or PF) and a fatal error is not received, all possible edits are performed on the transaction and multiple reject messages may be received. b. Probable Cause. Remote operator or accounting technician error. Correct the entry according to each reject message received. 16.129 MESSAGE - 0729 REJ, ABOVE REJECT CONDITIONS BYPASSED. a. Explanation. When creating a new address using action codes BF or BP, all edit conditions which are not met are identified as being bypassed. b. Probable Cause. All transactions with action code BF or BP must be post audited before the new address is updated. Action codes BF and BP must be controlled per paragraph 6.7. 16.130 MESSAGE - 0731 REJ, EEIC/FUND TYPE INCOMPATIBLE. a. Explanation. If the EEIC is 599, the fund type must be J or M.

b. Probable Cause. Remote operator or accounting technician error. Reenter with correct EEIC or fund type. 16.131 MESSAGE - 0732 REJ, EEIC-FUND TYPE-DOD FC INCOMPATIBLE. a. Explanation. If the fund type equals L and DoD FC equals 99, then EEIC must be 383, 391, 392, 393, 394, 395, 396, 405, 406, 408, 409, 421, 469, 600, 602, 604, 605, 609, 624, 627, 628, 641, 642, or 693.
b. Probable Cause. Remote operator or accounting technician error. Reenter with correct EEIC, fund type, or DoD FC. 16.132 MESSAGE - 0735 REJ, MISSING CONST PROJ NUMBER. a. Explanation. If fund type is A, fund code is 76, and expenditure account code is 591, the PSR must contain a construction project number (alphanumeric in positions 65-69). b. Probable Cause. Remote operator or accounting technician error. Reenter correct construction project number. 16.133 MESSAGE - 0736 REJ, RC/CC/FC/DOD FC INCOMPATIBLE. a. Explanation. If the RC/CC is XX0927, XX0935, XX45XX, XX4660, or XX4665, the fund code must be 9A, 29, 30, or 54. Also, the DOD FC must be 15 for fund codes 9A, 30, and 54. This edit is excluded if the fund code is 6N. b. Probable Cause. Remote operator or accounting technician error. Reenter with correct RC/CC, DOD FC, or fund code. 16.134 MESSAGE - 0737 REJ, FY-OBY CANNOT EQUAL CFY. a. Explanation. If the first two positions of RC/CC equals 97, the FY and OBY must be other than current year. b. Probable Cause. Remote operator or accounting clerk error. Reenter with correct RC/CC, FY, or OBY. 16.135 MESSAGE - 0740 REJ, CONTRACT STATUS NOT 'C', 'N', OR 'T'. a. Explanation. If fund type is E and fund code is 4E or 4F, then a contract/noncontract code is required in TRT, position 59. b. Probable Cause. Remote operator or accounting technician error. Research and reenter with corrected data. 16.136 MESSAGE - 0901 REJ, PASSWORD INVALID OR MISSING. a. Explanation. When opening a remote for an AFO that uses a password, the input password does not match the password established for the AFO. b. Probable Cause. password and reenter. Remote operator error. Determine correct

16.137 MESSAGE - 0998, ALL RECORDS RESTORED. a. Explanation. Informs the user that since the transaction was rejected, the database has not been changed. b. Probable Cause. Due to a rejected transaction.
16.138 MESSAGE - 0999 REJ, INVALID ADDRESS, CALL HQ SSG FOR ASSISTANCE. a. Explanation. The online system cannot read a disk record that is needed in processing the transaction. b. Probable Cause. Normally due to a hardware problem. Field Assistance Branch (FAB), DSN 596-5771. 16.139 MESSAGE - 2044 REJ, ALL 27 ACCOUNTING AREAS FULL. a. Explanation. There are too many travel details posted against the members Travel Master Record. Additional details cannot be added until some of them are stripped to the travel detail tape. b. Probable Cause. The details posted to the member's record do not meet the stripping criteria outlined in section 30. Display frame TV03 on the screen and perform an inquiry of the members record. If the type travel is "B" change it to a "T", or if the type travel is "T" change it to a "B", then request the Defense Enterprise Computing Center (DECC) run option 01 to the end-of-day. If travel details meeting the stripping criteria are stripped to the travel detail tape, reverse the type travel back to the original designation. However, if travel details meeting the stripping criteria are NOT stripped to the travel detail tape, reverse the type travel, then call the Field Assistance Branch (FAB), DSN 596-5771. 16.140 MESSAGE - 0201 REJ, JOB ORDER NUMBER MISSING OR INVALID. a. Explanation. CSI of J, fund type A, C, or L, requires 8position Job Order Number (JON) for Bal-IDs C, O, U, and E. b. Probable Cause. Remote operator or accounting technician error. Reenter using an 8-position JON. 16.141 MESSAGE - 1230 REJ, INVALID GENERAL LEDGER PROCESSING CODE. a. Explanation. The GL transactions must contain a valid general ledger processing code. The general ledger processing codes in the transaction must be 10, 37, 47, 61, 62, 63, 67, 68, 6B, 6C, 6E, and 6H. b. Probable Cause. Correct the entry. Remote operator or accounting technician error. Call the
16.142 MESSAGE - 7001 REJ, PID <PID NUMBER> NOT OPEN TO SYSTEM BQ. a. Explanation. The user attempted to process a transaction without processing an *OPEN. b. Remote Operator or Accounting Technician Error. *OPEN and reenter the transaction. Process an
16.143 MESSAGE - 7002 REJ, <USERID> NOT AUTHORIZED TO USE AFO <AFO>.

(3) The PC supervisor checks reject and other supporting documentation. If input was processed correctly, give the reject message to the Reports and Analysis Division/Funds Control for resolution. Several product requests may be required to obtain fund, program, and open item status listings to determine whether the reject can be resolved by decommitment or deobligation action. However, advise the Reports and Analysis Division/Funds Control of the reject immediately. (4) The Reports and Analysis Division/Funds Control reviews all rejects for resolution. If unable to resolve locally, Reports and Analysis Division/Funds Control sends the reject to the Budget office for necessary action. However, Reports and Analysis Division/Funds Control may resolve the rejects by one of the following methods: (a) Review reject message and source documents to determine cause of reject. If the posting of a decrease budget data action precedes the posting of an offsetting increase action, prepare a new entry to post the increase first and decrease afterwards. (b) Review all postings to ensure they are correct and in proper sequence, and an overall budget data decrease created the reject. Send the reject to Budget for resolution. (c) If a commitment rejects and open items are valid, contact the Budget office for resolution. 1 If funds are forthcoming and Budget authorizes the transaction, return the reject message and supporting documents to PC for processing with an override authority. Obtain necessary signature for use of override code "O" as required by paragraph 6.7. 2 If funds are not made available and the Budget office does not authorize the transaction, advise the PC to deny the fund citation. (d) If fund citation was made and the commitment results in a violation, comply with DFAS-DE 7200.1-R. e. Management Notices. The computer provides management notices when PSR limitation balances are exceeded by budget data, unobligated commitments, and obligations, unless the PSR contains a management notice option code of "B" or "P". Management reject notices are not suppressed for commitments. When CSR or FSR limitation balances are exceeded by obligation transactions, the message includes CSR PRIORITY or FSR PRIORITY (as applicable) to identify. The transaction may require priority attention of the Reports and Analysis Division/Funds Control and Budget. When this occurs: (1) The remote operator compares the notice with the source document. (a) If input is incorrect, the operator reverses the initial entry and reenters the correct posting.
(b) If input is correct and the management notice is due to budget data being processed, the notice and source documents are returned to the Reports and Analysis Division/Funds Control for resolution. (c) If input is correct and the management notice is due to commitment or obligation data being processed, the remote operator processes an addressable inquiry for indicative data and an inquiry for gross document summary amounts. (2) The accounting technician reviews the management notice and basic source document to determine if posting was to the correct DSR address, and if post action code was complete. (a) If incorrect, make an entry to reverse the erroneous posting and make a second entry to record the correct entry. The accounting technician sends the source document to the remote operator for reentry into the remote. (b) If correct, the accounting technician reviews a program status and Open Item List to aid in researching the management notice. Deobligate or decommit funds if a commitment or obligation document required adjustment. Process a transaction to adjust the DSRs involved. (3) If the management notice is a CSR or FSR PRIORITY and is correct, send a copy of the CRT printed listing to the Reports and Analysis Division/Funds Control for resolution. All CSR and FSR PRIORITY notices must be resolved. Exercise local determination when the management notice is not CSR or FSR PRIORITY. Advise the PC supervisor of all management notices sent to the Reports and Analysis Division/Funds Control for resolutions. (4) The Reports and Analysis Division/Funds Control contacts Budget for resolution of management notices and then advises the PC for disposition. The Reports and Analysis Division/Funds Control reviews DFAS-DE 7200.1-R for possible violations and makes a report, if necessary. f. Output Message Number. Output messages have been numbered to aid in identifying reject and management notices. 16.164 RECONCILING TARGETS OR LIMITATIONS TO FUNDING DOCUMENTS. Automated procedures have been developed to expedite the reconciliation of the targets or limitations posted in the BQ system to the amounts authorized by funding documents. Description of the process is as follows: a. The Command Budget Automated System (CBAS) will provide the General Accounting and Finance System (BQ), via the Defense Automatic Addressing System (DAAS), files containing funding authorizations. The funding authority reconciliation files are generated by CBAS at EOM, and routed to the accountable ADSN by DAAS. The records will contain all accounting data elements necessary to perform the reconciliation. This level of detail encompasses all fund codes for

ACTION CODE---[XP,] P/D ADDRESS---[P000652] F/P ADDRESS---[F001607] POST CODE-----[XH] AMOUNT--------[ 25000000] AMOUNT FIELD IS RIGHT JUSTIFIED DOCUMENT ID---[ ] DSI/DLT-------[ ] UOC/MAFR------[ ] FOR CUR-------[ ] PC -----------[ ] USE 2D POSITION TO IDENTIFY TECHNICIAN CODE TYPE VENDOR---[ ] DATE----------[ ] *
ACTION CODE---[XP,] P/D ADDRESS---[P000653] F/P ADDRESS---[F001607] POST CODE-----[XG] AMOUNT--------[ 25000000] AMOUNT FIELD IS RIGHT JUSTIFIED DOCUMENT ID---[ ] DSI/DLT-------[ ] UOC/MAFR------[ ] FOR CUR-------[ ] PC -----------[ ] USE 2D POSITION TO IDENTIFY TECHNICIAN CODE TYPE VENDOR---[ ] DATE----------[ ] *

Figure 16-2.

Sample Loading Limitation Amounts.
ACTION CODE---[XP,] P/D ADDRESS---[P000653] F/P ADDRESS---[F001607] POST CODE-----[XH] AMOUNT--------[ 5000000] AMOUNT FIELD IS RIGHT JUSTIFIED DOCUMENT ID---[ ] DSI/DLT-------[ ] UOC/MAFR------[ ] FOR CUR-------[ ] PC -----------[ ] USE 2D POSITION TO IDENTIFY TECHNICIAN CODE TYPE VENDOR---[ ] DATE----------[ ] *
ACTION CODE---[XP,] P/D ADDRESS---[P000654] F/P ADDRESS---[F001607] POST CODE-----[JX] AMOUNT--------[ 1500000] AMOUNT FIELD IS RIGHT JUSTIFIED DOCUMENT ID---[ ] DSI/DLT-------[ ] UOC/MAFR------[ ] FOR CUR-------[ ] PC -----------[ ] USE 2D POSITION TO IDENTIFY TECHNICIAN CODE TYPE VENDOR---[ ] DATE----------[ ] *
ACTION CODE---[XP,] P/D ADDRESS---[P000654] F/P ADDRESS---[F001607] POST CODE-----[WX] AMOUNT--------[ 1500000] AMOUNT FIELD IS RIGHT JUSTIFIED DOCUMENT ID---[ ] DSI/DLT-------[ ] UOC/MAFR------[ ] FOR CUR-------[ ] PC -----------[ ] USE 2D POSITION TO IDENTIFY TECHNICIAN CODE TYPE VENDOR---[ ] DATE----------[ ] *

[TRAV1]

TRAVEL OBLIGATIONS ACTION CODE -----P/D ADDRESS -----F/P ADDRESS -----POST CODE -------AMOUNT ----------TRAVEL ORDER NO -DATE ------------TRAVELER'S NAME -[XP,] [P009240] [F001607] [XC] [ 1000000] [H00079T10 ] [ ] [

* D007192

TRAVEL OBLIGATIONS ACTION CODE -----P/D ADDRESS -----F/P ADDRESS -----POST CODE -------AMOUNT ----------TRAVEL ORDER NO -DATE ------------TRAVELER'S NAME -[XD,] [D007192] [P009240] [CU] [8000 [TTA001899 [ ] [HAMILTON

all annual targets and all quarterly targets, excluding SBSS targets.
*Please ensure you indicate in the type column whether the
(Reverse of AF Form 1269, May 86)
*U.S. G.P.O.:1991-281-437:85965

Figure 16-5.

Sample Load of Medical Materiel Accounting System.
29 November 2002 EDITS FOR THE PRESENCE OF DATA ELEMENTS
F T L L M A A B C E J R S T
FC 9A Othe r Any 29 Othe r Any Any Any Any Any Any Any 2 2

ASN/ OBAN 2

MF P 2

PROJ 2 2

DOD FC 1 5

EEIC 2 2

RC/CC 2 2, 2, 6

CASE 5 1

2, 2 2, 8 2, 7

2 2, 4

2 2, 2 1, 7 1, 7
Blanks represents no edits required NOTE NOTE NOTE NOTE NOTE NOTE 1: 2: 3: 4: 5: 6: Numeric (may not be spaces). Alphanumeric (may not be spaces). Two-position alphanumeric or spaces (may not be one position). Must be spaces if BPAC 69XXXX, 6X920X, or 6600BB (X = any alphanumeric character). Must be spaces. If RC/CC equals spaces, PE must equal XXX99F, EEIC must contain at least three digits, and the DOD FC must be 99 (fund type L only). Except if fund code 76, must be spaces. Except if fund codes 75, 76, and 4B through 4Z, FY must be spaces. Required for fund codes 11, 15, 17 only.

NOTE 7: NOTE 8: NOTE 9:

Figure 16-6.
Edits for the Presence of Data Elements.
EDITS FOR THE COMPATIBILITY OF DATA ELEMENTS 1. If the fund type is L or M and RC/CC is XX461X or XX486X, the DOD FC must be 04. 2. If the DOD FC is other than 99, the RC/CC cannot be spaces.
3. If the fund type equals L or M and any fund code or fund type A and fund code 29, and the OBY does not equal spaces or CFY, the first two positions of RC/CC must equal 97. 4. If the fund type equals L or M, both the FY and OBY must equal CFY, first PFY, second PFY, third PFY, fourth PFY, or fifth PFY. 5. 6. If RC/CC is XX463X, the DoD FC must be 07. If EEIC is 599, the fund type must be J or M.
7. If the fund type equals L and DoD FC equals 99, the EEIC must be 383, 391, 392, 393, 394, 395, 396, 405, 406, 408, 409, 421, 469, 600, 602, 604, 605, 609, 624, 627, 628, 641, 642, or 693. 8. If the first two positions of RC/CC equals 97, the FY and OBY must be other than current year. 9. If the fund code is 9A and PEC is 88721F, the EEIC must be 2210X and the RC/CC must be XX5895. 10. If the fund code is 9A and PEC is 94901F, the EEIC must be 2230X and the RC/CC must be XX8671. 11. If the fund code is 9A and PEC is 88732F, the EEIC must be 2240X and the RC/CC must be XX8661.

FUNDING AUTHORITY RECONCILIATION DFAS-DAYTON ADSN: 503000 SC/ FMS FC/ FMS FY LNE PEC REC TYPE/ DOC NBR CSR/FSR C009384
PCN SH069-58A AS OF 99 MAR 06
DIRECT AUTHORITY ANNUAL QUARTERLY 1825000.00 --------------1825000.00*.** 0.00 --------------0.00 *.** 0.00 --------------0.00 29635000.00 --------------29635000.00 20829311.00 25800.00 --------------20803511.00 25800.00 --------------25800.00 *.** 0.00 --------------0.00 *.** 0.00 0.00 --------------0.00 *.** 0.00 0.00 --------------0.00 *.** 0.00 0.1825000.00 --------------1825000.0020000.00 15560.85 --------------4439.15 534.00 534.00 --------------0.00 29635000.00 --------------29635000.00 20829311.00 25800.00 --------------20803511.00 25800.00 --------------25800.00 639925.70 639925.70 --------------0.00 152756000.00 117549700.00 16400000.00 --------------18806300.00 156523439.00 31676200.00 15161007.00 --------------109686232.00 154290998.10 115888045.10 16297636.77
REIMBURSABLE AUTHORITY ANNUAL QUARTERLY

ADJ FLG

*** NO MATCHING FUNDING RECORD FOUND *** C0002 (MOD) 171 C001412 *** OUT OF BALANCE *** 177 *** NO MATCHING BQ RECORD FOUND *** *** OUT OF BALANCE *** *** NO MATCHING BQ RECORD FOUND *** C0002
0.00 0.00 --------------- --------------0.00 0.00 0.00 0.00 --------------- --------------0.00 0.00 0.00 0.00 --------------- --------------0.00 0.00 --------------- --------------0.00 0.00 0.00 0.00 --------------- --------------0.00 0.00 --------------- --------------0.00 0.00 0.00 0.00 --------------- --------------0.00 0.00 0.00 0.00 0.00 16400000.00 --------------- --------------0.00 16400000.000.00 0.00 0.00 16699674.86 --------------- --------------0.00 16699674.860.00 0.00 0.00 16297636.77

C001550

19990112 CC0007

C009558

19990112 CC0005

C001466

19990112 C19990112 C0015

C001491 C001492

*** OUT OF BALANCE *** *** OUT OF BALANCE *** PCN SH069-58A

C001418 C001482

19990112 C0023

C001422 C001424 PAGE

Figure 16-16.
Funding Authority Reconciliation List.

11 JAN MAR APR NOV APR OCT JAN 1991
07B 04D 05D 06D 14B 16B 15B

Belgium

30 MAY APR SEP JAN APR FEB APR JAN MAR 1978
08A 07A 10C 18D 17D 18D 25D 27B 12C

BIH BLR

Bosnia & Herzegovina Belarus

05 FEB NOV 1984

10A 22C

Bulgaria

27 SEP DEC MAR APR JAN OCT OCT MAY 1991
01C 02C 03C 11C 18A 19A 17A 24B 25B

Croatia

06 APR MAY DEC SEP DEC JUN APR OCT APR AUG NOV NOV JAN JUN MAY 1997
17D 18D 04C 06C 05C 16B 17B 15B 16C 14C 15C 04A 06A 05A 25A 26A 27A

AR_C32E

Page 5/36
NOC CZE Country Czech Republic Name HAJDUK Milan BULIR Martin JAROCHOVA Marcela HAJDUK Frantisek PERTLIK Filip RADA Petr JENSEN Martin Patrick LYKKEBAEK Klaus WEISS Johan CHRISTIANSEN Carina Rosenvinge JAGER Maja Buskbjerg DAMSBO Martin FRIESE Nicklas LAURSEN Patrick SOEMOD Camilla FRANTZEN Claus KNUDSEN Mads KROGSHEDE Mads Juul FRANDSEN Ida SIGIL Michalina Josephine SONNICHSEN Sarah Holst CARPIGNANO Marco ERICA Robert GALEYRAND Jean-Pierre LIPSCOMB Katy PAPADOPOULOU Evelyn PISCIOTTI Marinella PRASKALO Andjelko ROSA Irena SALUKVADZE Natalia SCARZELLA Ardingo SCARZELLA Mario SKJOLDBORG Flemming STEFFENS Sabrina VILLI Miroslav VRAN Svetlana WAGEMAKERS Henk WIGGELEER Patrick DUO Jose ENCINAS Azucena CANALEJAS Victor CATALAN Jose Ignacio CORNELIS Juan Carlos CERNUDA Dolores AGUADO Luis Miguel ROSADO ALINDADO Alejandro VALVERDE Francisco Javier NIETO TALADRIZ Clara KIVILO Raul LUIK Siret PREIMANN Anneli PARNAT Reena Date of Birth Back No. Event Officials Other Recurve Men Recurve Women Recurve Junior Men Recurve Junior Men Recurve Junior Men Officials Team Captain Officials Team Captain Recurve Men Recurve Women Recurve Women Compound Men Compound Men Compound Men Compound Women Compound Junior Men Compound Junior Men Compound Junior Men Compound Junior Women Compound Junior Women Compound Junior Women Organizing Commettee Result Crew Judges International Judge Judges International Judge Judges International Judge Organizing Commettee Technical Delegate VIP Vip Judges International Judge Judges Director of Shooting Organizing Commettee Result Crew Organizing Commettee Result Crew VIP EMAU President Judges International Judge Judges International Judge Judges International Judge Judges International Judge Judges Director of Shooting Judges Chairman of Judge Officials Coach Officials Coach Compound Men Compound Men Compound Men Compound Women Compound Junior Men Compound Junior Men Compound Junior Men Compound Junior Women Officials Team Captain Recurve Women Recurve Women Recurve Junior Women

08 APR MAY FEB MAY DEC 1992

09D 20B 09A 10A 08A

Denmark
17 APR FEB DEC MAY MAR FEB OCT FEB OCT APR OCT FEB 1995
08B 20D 19D 09C 07C 08C 19D 03A 02A 01A 22B 24B 23B
13 SEP APR JAN MAY MAR SEP MAY JUN 1994
07B 09B 08B 19C 01D 03D 02D 27C

Estonia

28 SEP DEC DEC 1993

20C 21C 26B

Page 6/36
NOC FIN Country Finland Name LINDROOS Tero VAAJAMAKI Vesa VIRTANEN Aki JARVENPAA Marko RYTKY Lauri SIIVONEN Reima JARVENPAA Erja MAKKONEN Susanna RYTKY Merja BINON Benoit BOUCLET Philippe DELLENBACH Marc LAFOREST Christian MICHAUT Anne MUSY Frdrique PAILLET Laurent PIGEAUD Damien TAVERNIER Olivier VALLADONT Jean-Charles BEZAULT Celine SCHUH Berengere TABARD Anne-Sophie DELOCHE Pierre Julien DOUSSOT Christophe GENET Dominique TCHEPIKOFF Patricia FAUCHERON Thomas LEFEBVRE Anthony DAM Rakul VANG Schandorff NICLASEN Jogvan ANDREASSEN Magnus MACHAIDZE Lasha PHUTKARADZE Tamaz DIASAMIDZE Asmat ESEBUA Kristine NARIMANIDZE Khatuna BACHMANN Viktor FREDERICK Martin NULLE Wiebke ROHRBERG Sebastian SEIBOLD Juergen TUCHSCHERER Dirk POSSNER Susanne UNRUH Lisa WINTER Karina MAYR Camilo SKOERIES Eric WACHSMUTH Markus ERNST Christine KNAAK Antonia VIEHMEIER Isabel NASOULAS Alexandros TSERKEZIS Stefanos AERIKOS Christos CSOREGH Pal KOSY Nandor Date of Birth Back No. 17 DEC MAY DEC MAY JAN NOV SEP OCT 1967 05D 06D 04D 07D 09D 08D 15C 16C 17C Event Recurve Men Recurve Men Recurve Men Compound Men Compound Men Compound Men Compound Women Compound Women Compound Women Officials Coach Officials Delegation Official Officials Coach Officials Other Officials Team Captain Officials Coach Officials Medical Person Recurve Men Recurve Men Recurve Men Recurve Women Recurve Women Recurve Women Compound Men Compound Men Compound Men Compound Women Recurve Junior Men Recurve Junior Men Officials Coach Officials Team Captain Compound Men Compound Junior Men Officials Coach Officials Coach Recurve Women Recurve Women Recurve Women Officials Coach Officials Team Captain Officials Coach Recurve Men Recurve Men Recurve Men Recurve Women Recurve Women Recurve Women Recurve Junior Men Recurve Junior Men Recurve Junior Men Recurve Junior Women Recurve Junior Women Recurve Junior Women Officials Coach Recurve Men Compound Junior Men Recurve Men Recurve Men

France

11 JAN SEP MAR SEP JUN JUN FEB MAY NOV JUN FEB MAR 1990
01D 03D 02D 15A 16A 14A 03B 02B 01B 18B 18B 17B

Faroe Islands

26 AUG APR 1992

11B 05D

Georgia

30 JAN MAR FEB 1974

17B 18B 19B

Germany

13 MAR JUN MAR JAN JAN MAR MAY OCT SEP FEB JUN 1992
06C 04C 05C 14D 15D 16D 09B 10B 08B 22D 21D 23D