Lookup Code
|
Lookup Values & Messages
|
F00
|
Insufficient funds (detail) This detail transaction fails funds check
|
F01
|
Insufficient funds (->summary) This detail transaction causes a
summary account to fail funds check
|
F02
|
Insufficient funds (summary) This summary account fails funds check
|
F03
|
Insufficient funds (pending) One or more earlier pending transactions
cause this transaction to fail
|
F04
|
Insufficient funds (both) This detail transaction fails and causes a
summary account to fail funds check
|
F05
|
Insuff funds (<-generated) One or more associated generated
transactions cause this transaction to fail
|
F06
|
Insuff funds (prop<-assoc) One or more associated transactions
cause this proprietary transaction to fail
|
F10
|
Insufficient funds (budgetary) This budgetary detail transaction fails
funds check
|
F11
|
Insuff funds (->sum budgetary) This budgetary detail transaction
causes a summary account to fail funds check
|
F12
|
Insuff funds (sum budgetary) This budgetary summary account fails
funds check
|
F13
|
Insuff funds (pend budgetary) One or more earlier pending transactions
cause the budgetary transaction to fail
|
F14
|
Insuff funds (both budgetary) This budgetary transaction fails and
also causes a summary account to fail
|
F15
|
Insuff funds (budg<-assoc) One or more associated transactions
cause this budgetary transaction to fail
|
F20
|
Nonexistent flexfield This Accounting Flexfield does not exist
|
F21
|
Disabled or expired flexfield This Accounting Flexfield is disabled or
out-of-date
|
F22
|
Posting not allowed This Accounting Flexfield does not allow detail
posting
|
F23
|
Budgeting not allowed This Accounting Flexfield does not allow detail
budget posting
|
F24
|
Nonexistent period This accounting period does not exist
|
F25
|
Period not open or future This accounting period is neither Open nor
Future Enterable
|
F26
|
Period not in open budget year This accounting period is not within an
open budget year
|
F27
|
Frozen budget This budget is frozen
|
F28
|
Expired USSGL transaction code This USSGL transaction code is
out-of-date
|
P00
|
Funds not reduced This transaction does not reduce funds available
|
P01
|
Funds check not required This account does not require funds check
|
P02
|
Not funding budget This budget transaction applies to a budget other
than your funding budget
|
P03
|
Foreign currency budget This foreign currency budget transaction does
not require funds check
|
P04
|
Add Summary program created This summary transaction is created by the
Add Summary Accounts program
|
P05
|
Force passed funds check This transaction passes funds check in force
pass mode
|
P10
|
Passed funds check This transaction passes funds check
|
P15
|
Passed funds check (budgetary) This budgetary transaction passes funds
check
|
P20
|
Advisory warning This transaction fails funds check; advisory checking
is in force
|
P21
|
Passed due to override This transaction fails funds check; you
overrode the failure
|
P22
|
Advisory warning (->summary) This detail transaction causes a
summary account to fail funds check (advisory)
|
P23
|
Passed due to override (sum) This summary account fails funds check;
you overrode the detail(s)
|
P25
|
Advisory warning (budgetary) This budgetary transaction fails funds
check; advisory checking is in force
|
P26
|
Passed due to override (gen) This transaction or its associates fail
funds check; you overrode the original
|
P27
|
Advisory warning (->sum bud) This budgetary transaction causes a
summary account to fail check (advisory)
|
F29
|
The transaction account and budget account are different
|
F30
|
The transaction failed funds check at the resource level
|
F31
|
The transaction failed funds check at resource group level
|
F32
|
The transaction failed funds check at the task level
|
F33
|
The transaction failed funds check at the top task level
|
F34
|
The transaction failed funds check at the project level
|
F35
|
The transaction failed funds check at project account level
|
F36
|
Funds check failed because of unexpected error
|
F37
|
Failed because year end rollover process is in progress
|
F38
|
Funds check failed because of invalid budget versions
|
F39
|
No budget account on raw line
|
F40
|
The resource list is invalid or null
|
F41
|
The amount type or boundary code is invalid
|
F42
|
The amount type or boundary code is invalid for no time phase
|
F43
|
Invalid boundary code for amount type 'Project to date'
|
F44
|
Invalid boundary code for amount type 'Year to date'
|
F45
|
Invalid boundary code for amount type 'Period to date'
|
F46
|
Funds check failed because of invalid resource list member
|
F47
|
Start date or end date is null for the specified date range
|
F48
|
Not able to derive PA date
|
F49
|
Invalid budget entry method or missing baseline version
|
F50
|
Could not map to a budget line while deriving budget account
|
F51
|
Not able to derive GL date
|
F52
|
The encumbrance type is null or invalid
|
F53
|
Funds check failed because budget baselining is in progress
|
F54
|
No matching requisition was found for this purchase order
|
F55
|
No matching purchase order was found for this invoice
|
F56
|
Could not acquire lock: funds checks are running concurrently
|
F57
|
Transaction failed because of CBC funds check
|
F58
|
Transaction failed because of GL funds check
|
F59
|
No budget exists at the resource level
|
F60
|
No budget exists at the resource group level
|
F61
|
No budget exists at the task level
|
F62
|
No budget exists at the top task level
|
F63
|
No budget exists at the project level
|
F64
|
No budget exists at the project account level
|
P28
|
Funds check passed at the project account level
|
P29
|
Funds check passed at project account level in advisory mode
|
P30
|
Funds check passed at the project level
|
P31
|
Funds check passed at the project level in advisory mode
|
P32
|
Increase in funds does not require funds check
|
P33
|
Invoice interfaced from projects does not require funds check
|
P34
|
Expense report from projects requires no funds check
|
P35
|
Funds check passed at the resource level in advisory mode
|
P36
|
Funds check passed at resource group level in advisory mode
|
P37
|
Funds check passed at the task level in advisory mode
|
P38
|
Funds check passed at the top task level in advisory mode
|
P39
|
GMS: Transaction passed Funds Check in advisory mode
|
F65
|
PO/CBC: Single year validation failure
|
F66
|
PO/CBC: Accounting Date validation failure
|
F67
|
GMS:Funds check processing error,contact system administrator
|
F68
|
GMS: Funds Check failed due to invalid award number
|
F69
|
GMS: Funds Check failed at Top Task Level
|
F70
|
GMS: Funds Check failed in full mode
|
F71
|
GMS: Funds Check failed at the Award level
|
F72
|
GMS: Funds Check failed at the Task level
|
F73
|
GMS: Funds Check failed at the Resource level
|
F74
|
GMS: Funds Check failed at the Resource Group level
|
Sunday, May 10, 2015
What are the possible values in the Column FAILED_FUNDS_LOOKUP_CODE in PO_REQ_DISTRIBUTIONS_ALL and PO_DISTRIBUTIONS_ALL and what do they stand for?
Labels:
Budget,
Encumbrance
Subscribe to:
Post Comments (Atom)
kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - kayseri escort - gaziantep escort
ReplyDelete