GFEBS Project Systems Course Exam
Graded A+ Verified
Account Assignment Element - ANSWER-WBS's that can have actual costs accrued
(executed) against them must be marked by checking the Account Assignment Element
Operative Indicator.
Availability Control - ANSWER-During Availability Control, the corresponding assigned
funds are calculated and checked against the budget using Funds Availability Control.
Before a WBS can be executed against, commitment items are created and actual costs
are incurred.
If certain tolerance thresholds are breached (funds exceeded), this can trigger a hard
stop in the GFEBS system.
A hard stop in the GFEBS system is a process that stops all action on an item until the
issue causing the hard stop has been resolved. Because GFEBS is an integrated, real
time system, it is able to check fund availability and reserves funds so they are no
longer available for other projects.
NOTE: For a discussion for COED (Commitments, Obligations, Expenses and
Disbursements), refer to Funds Management training courses, aids, and Online Help
Procedures (OLHPs).
BI (Business Intelligence) - ANSWER-BI (Business Intelligence): the data warehousing
component of GFEBS) BI is not real-time, but is updated several times a day
Example roles / reports are:
Command Budget Reporter
Costs Management Reporter
BI Advanced Expert
Billing Element - ANSWER-WBS's that can be referenced on a Sales order for a
reimbursable must be marked by checking the Billing Element Operative Indicator.
Cost Planning (1 of 3) - ANSWER-Cost Planning is used to plan costs at the WBS level
(though the cost may be viewed at an overall project level by the rollup of costs from
bottom-up planning).
There are multiple ways to conduct cost planning. This planning information is
leveraged within GFEBS to assist in the budget formulation process and to compare
cost estimates to actuals. The planning capability within Project Systems allows GFEBS
users to plan overall, current year, or out to as many years out as required.
, Cost Planning (2 of 3) - ANSWER-In GFEBS, Cost Planning is generally carried out in
one of two ways:
Structure Planning
Using transaction CJ40 - this allows you to put in plan values (overall, annual, or both)
in any WBS which has it Planning Element Operative Indicator set.
The cost model in GFEBS for Structure Planning is strictly bottom-up. All costs entered
at a lower level aggregate to the levels above them. For this reason, a good practice is
to only enter plan values at the lowest (execution) levels. Values entered at higher
levels will be overwritten by the aggregated values of the levels beneath it if they exist.
Easy Cost Planning (ECP)
This allows you to easily enter values for cost at a WBS level broken out into Object
Class Categories, such as Labor, Travel, etc. ECP also allows multi-year planning. ECP
is available from within the Project Builder.
Cost Planning (3 of 3) - ANSWER-Structure Planning and ECP are not mutually
exclusive. Both could be done on the same project. You could, for instance, use
Structure planning for a rough estimate early in the project lifecycle and use ECP later
when more refined, categorized cost estimates are available.
Both Structure and ECP Planning support versions, starting with a default version
number 0.
Finally, order cost planning can be done for maintenance orders.
It is important to note that planned costs do not act as constraints or hard stops for
execution of actual costs. Rather they are used for purposes of budget formulation and
forecasting, as well as to run certain types of reports (Planned vs. Actuals etc)
Date Planning - ANSWER-The Project Scheduling Tool allows GFEBS to schedule a
project timeline, either at the Project Definition or WBS Element level, to plan the correct
project timeframe.
WBS Element Scheduling characteristics include:
Basic start and finish dates can be planned for the
WBS elements.
The dates can be extrapolated from lower to higher-level WBS elements, or passed on
from higher to lower-level WBS elements.
The consistency of scheduling data can be verified from within the WBS structure to
avoid project delays.
Dates may be entered at the project definition level. WBS dates that occur before or
after these dates will trigger an error message to ensure scheduling consistency. For
Graded A+ Verified
Account Assignment Element - ANSWER-WBS's that can have actual costs accrued
(executed) against them must be marked by checking the Account Assignment Element
Operative Indicator.
Availability Control - ANSWER-During Availability Control, the corresponding assigned
funds are calculated and checked against the budget using Funds Availability Control.
Before a WBS can be executed against, commitment items are created and actual costs
are incurred.
If certain tolerance thresholds are breached (funds exceeded), this can trigger a hard
stop in the GFEBS system.
A hard stop in the GFEBS system is a process that stops all action on an item until the
issue causing the hard stop has been resolved. Because GFEBS is an integrated, real
time system, it is able to check fund availability and reserves funds so they are no
longer available for other projects.
NOTE: For a discussion for COED (Commitments, Obligations, Expenses and
Disbursements), refer to Funds Management training courses, aids, and Online Help
Procedures (OLHPs).
BI (Business Intelligence) - ANSWER-BI (Business Intelligence): the data warehousing
component of GFEBS) BI is not real-time, but is updated several times a day
Example roles / reports are:
Command Budget Reporter
Costs Management Reporter
BI Advanced Expert
Billing Element - ANSWER-WBS's that can be referenced on a Sales order for a
reimbursable must be marked by checking the Billing Element Operative Indicator.
Cost Planning (1 of 3) - ANSWER-Cost Planning is used to plan costs at the WBS level
(though the cost may be viewed at an overall project level by the rollup of costs from
bottom-up planning).
There are multiple ways to conduct cost planning. This planning information is
leveraged within GFEBS to assist in the budget formulation process and to compare
cost estimates to actuals. The planning capability within Project Systems allows GFEBS
users to plan overall, current year, or out to as many years out as required.
, Cost Planning (2 of 3) - ANSWER-In GFEBS, Cost Planning is generally carried out in
one of two ways:
Structure Planning
Using transaction CJ40 - this allows you to put in plan values (overall, annual, or both)
in any WBS which has it Planning Element Operative Indicator set.
The cost model in GFEBS for Structure Planning is strictly bottom-up. All costs entered
at a lower level aggregate to the levels above them. For this reason, a good practice is
to only enter plan values at the lowest (execution) levels. Values entered at higher
levels will be overwritten by the aggregated values of the levels beneath it if they exist.
Easy Cost Planning (ECP)
This allows you to easily enter values for cost at a WBS level broken out into Object
Class Categories, such as Labor, Travel, etc. ECP also allows multi-year planning. ECP
is available from within the Project Builder.
Cost Planning (3 of 3) - ANSWER-Structure Planning and ECP are not mutually
exclusive. Both could be done on the same project. You could, for instance, use
Structure planning for a rough estimate early in the project lifecycle and use ECP later
when more refined, categorized cost estimates are available.
Both Structure and ECP Planning support versions, starting with a default version
number 0.
Finally, order cost planning can be done for maintenance orders.
It is important to note that planned costs do not act as constraints or hard stops for
execution of actual costs. Rather they are used for purposes of budget formulation and
forecasting, as well as to run certain types of reports (Planned vs. Actuals etc)
Date Planning - ANSWER-The Project Scheduling Tool allows GFEBS to schedule a
project timeline, either at the Project Definition or WBS Element level, to plan the correct
project timeframe.
WBS Element Scheduling characteristics include:
Basic start and finish dates can be planned for the
WBS elements.
The dates can be extrapolated from lower to higher-level WBS elements, or passed on
from higher to lower-level WBS elements.
The consistency of scheduling data can be verified from within the WBS structure to
avoid project delays.
Dates may be entered at the project definition level. WBS dates that occur before or
after these dates will trigger an error message to ensure scheduling consistency. For
