Administration Help   I   Human Resource Management Help  I   Performance Budgeting Help

Field Name

Description

Sequence order on Budget Transaction/s spawned through CAM/CAS

(CAS_CAM_BUD_SEQ)

The parameter controls the configuration of the sequence of budget lines for budget transactions generated through cost accounting transactions (CAS and CAM). The default value is set to a sequence that includes BUD_DOC_CD, MJR_PROG_CD, PROG_CD, PPC_CD, PHASE_CD, FPRFL_CD, and FPRTY_CD.

Add DOC_BUDLN_LN_NO next to BUD_DOC_CD to keep the same sorting as CAS/CAM > Budget tab.

Any change requires a bounce of all VLSs to take effect.  

CAS/CAM Budget Transaction Submit Default

(CAS_CAM_BUD_DOC_SBMT_DFLT)

This parameter controls the defaulting of the Submit Budget Transaction(s) flag on CAS and CAM transactions header. The default value for the parameter is yes. 

Default Split Type

(DFLT_MJPROG_SPLT_TYP)

The parameter controls the initial default for the Split Type field on Major Program and Cost Accounting Setup. The parameter allows changing the default so that the most common, the only allowed, or the most conservative value can default.

Valid values are: 1 (Front End Split FES), 2 (Back End Split BES), 3 (No Automated Splits - No Bill), and 4 (No Automated Splits - Manual). As delivered, No Automated Splits - No Bill is the default.

Default Reporting Basis

(DFLT_MJPRG_REIM_BAS_IND)

The parameter controls the initial default for the Reporting Basis field on the Major Program reference page and the Major Program tab of the Cost Accounting Setup transaction. The parameter allows changing the default so the most common, the only allowed, or the most conservative value can default.

Valid values are: 1 (Accrual), 2 (Cash), 3 (Encumbrance), 4 (Required-No Inference), and 5 (Prohibited). As delivered, Accrual is the default.

Posting Logic to Support Performance Unit

(PERF_UNIT_FES)

When set to yes, this parameter instructs the system to split the Performance Unit attribute on Accounting Lines of Charge Transaction Type on Posting Lines in the same proportion as the Posting Amount when a front-end split Major Program is used.

Please see Split Performance Unit in the Advantage – Unique Features section of this user guide for more information on this type of split.

Reimbursement Budget Availability

(REIM_BUD_AVAIL)

The Budget Control ID that will be used by the application to determine budget availability for reimbursement budget structures when performing Front End Split (FES) and Back End Split (BES). As delivered, this parameter can be set to budget control IDs: 13, 14, 29, 31 and 41.

The control selected should match the formula of the Split Availability budget amount.

Reimbursement Budget Total Costs

(REIM_BUD_TOT_COSTS)

The amounts from the Reimbursement Budget Availability formula that will be set to zero when the application is calculating Total Costs for splitting. As delivered, this parameter is budget amount 21 – Awarded.

Perform BFY Logic in FES

(BFY_FES)

This parameter indicates if a secondary split based on Budget Fiscal Year in a non-reimbursement budget structure should be a feature available to funding lines.

Please see Splitting under Major Features in this User Guide for more information on this feature.

BFY FES Budget Structure

(BFY_FES_STRU_ID)

This parameter indicates the budget structure with a BFY key that controls the secondary split in FES based on budget fiscal year.  Such a structure should be an expense only or appropriation structure.

BFY FES Budget Level

(BFY_FES_LVL_ID)

This parameter indicates the budget level in the BFY FES Budget Structure that controls the secondary split in FES.

BFY FES Budget Control ID

(BFY_FES_CNST_ID)

This parameter indicates the budget control used in the secondary split of FES to define what funds are available for a budget year.

COA Inferences to Skip in Front End Split

(DISABLE_DOCCOA_PL_EDTR_PRNT_CHCK)

When a COA inference should not occur on a posting line that will undergo front end split because the change of COA after the split will conflict with the inference, this parameter is used. Currently, only the Function Inference (INF_FUNC) is supported as most inferences will not conflict.

Validate Fund and Appr against VFAPPR on Funding lines

(VLDT_VFAPPR_FL)

When True, an edit is triggered on Funding Profile to check if the Fund and Appr combination is present in the VFAPPR table on funding and Internal Buyer Funding Lines. Valid values are True or False.