F1202DateSensitiveRetrieval

F1202 Date Sensitive Retrieval

Minor Business Rule

Object Name: X1200

Parent DLL: CAEC

Location: Client/Server

Language: C

Purpose
Retrieve date sensitive balance information for an account ledger type. The balances are stored in the F1202 table. When a non end of period date is
sent, the F0911 records are backed out of the end of the period or added to the beginning of the period based on where the date lands in the date
pattern.

Setup Notes and Prerequisites
A valid account and data must exist in the F0901, F1202, and F0911.

A company's fiscal date pattern must be set up in the F0010, and the date pattern must exist in the F0008.

This function uses a data structure to store the hUser, hRequestF0911, and hRequestF1202. Memory is allocated and passed back and forth between
the business function and event rules. The ER programmer needs to call Memory Free Fixed Asset Retrieval to clean up the file handles and the user
handles.  The pointer in memory should yield better performance.

OCM: Mappings this function is critical with other applications. These functions B1200005 and B1200006 should be mapped to the same place.
These functions primarily are called with UBEs, so the UBE probably have been mapped to a server, and it should not be an issue.

There are two things left out:
Determine if record is Cost Account for non 'AA' and units ledgers, and independent of 'AA'.

If the ledger type is dependent on the 'AA' ledger for cost, adjust the account ledger balance by any transactions in the 'AA' ledger.

Special Logic
Calculate the mid point between the data pattern to check reading the balance from the start period date and adding to the balance or reading the
balance from the end of period and subtracting the journal entries from the end period date.

The F1202 index must be added to fetch the information: F1202LC - logical on the AS400

FLNUMB
FLMCU
FLOBJ
FLSUB
FLLT
FLCTRY
FLFY
FLFQ
FLSBL
FLSBLT

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnAssetID	NUMB	MATH_NUMERIC	REQ	INPUT
An 8-digit number that uniquely identifies an asset.
szAccountID	AID	char	REQ	INPUT
A number that the system assigns to each general ledger account in the Account Master table (F0901) to uniquely identify it.
szCompany	CO	char	REQ	INPUT
A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany transactions. Note: You can use company 00000 for default values such as dates and automatic accounting instructions. You cannot use company 00000 for transaction entries.
szLedgerType	LT	char	REQ	INPUT
A user defined code (09/LT) that specifies the type of ledger, such as AA (Actual Amounts), BA (Budget Amount), or AU (Actual Units). You can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.
szSubledger	SBL	char	REQ	INPUT
A code that identifies a detailed, auxiliary account within a general ledger account. A subledger can be an equipment item number or an address book number. If you enter a subledger, you must also specify the subledger type.
cSubledgerType	SBLT	char	REQ	INPUT
A user defined code (00/ST) that is used with the Subledger field to identify the subledger type and how the system performs subledger editing. On the User Defined Codes form, the second line of the description controls how the system performs editing. This is either hard-coded or user defined. Valid values include: A Alphanumeric field, do not edit N Numeric field, right justify and zero fill C Alphanumeric field, right justify and blank fill
jdDate	DGL	JDEDATE	REQ	BOTH
A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
cErrorFlag	EV01	char	OPT	OUTPUT
An option that specifies the type of processing for an event.
mnCentury	CTRY	MATH_NUMERIC	REQ	BOTH
The calendar century associated with the year. Enter is the first two digits of the year. For example, 19 indicates any year beginning with 19 (1998, 1999), 20 indicates any year beginning with 20 (2000, 2001), and so on.
mnFiscalYear	FY	MATH_NUMERIC	REQ	BOTH
A number that identifies the fiscal year. Generally, you can either enter a number in this field or leave it blank to indicate the current fiscal year (as defined on the Company Setup form). Specify the year at the end of the first period rather than the year at the end of the fiscal period. For example, a fiscal year begins October 1, 1998 and ends September 30, 1999. The end of the first period is October 31, 1998. Specify the year 98 rather than 99.
mnPeriodNumber	PN	MATH_NUMERIC	REQ	BOTH
A number indicating the current accounting period. This number, used in conjunction with the Company Constants table (F0010) and the General Constants table (F0009), allows the user to define up to 14 accounting periods. See General Ledger Date. The current period number is used to determine posted before and posted after cut off warning messages. It is also used as the default accounting period in the preparation of financial reports.
jdStartPeriod	DGL	JDEDATE	OPT	BOTH
A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
jdEndPeriod	DGL	JDEDATE	OPT	BOTH
A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.
idPointer	GENLNG	ID	REQ	BOTH
General purpose ID variable.
mnInception	AO1OW	MATH_NUMERIC	OPT	OUTPUT
A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid values are: o Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The system calculates force amounts. o Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force Amounts (FA) ledger. The system calculates +/- force amounts. o Percent Complete. This field appears with Methods F, G, O, P, and S. The new total in the Percent Complete (F%) ledger. o Estimate to Complete Amounts. This field appears only with Method E. The system adds the values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers. o Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.
mnYearToDate	AO1OW	MATH_NUMERIC	OPT	OUTPUT
A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid values are: o Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The system calculates force amounts. o Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force Amounts (FA) ledger. The system calculates +/- force amounts. o Percent Complete. This field appears with Methods F, G, O, P, and S. The new total in the Percent Complete (F%) ledger. o Estimate to Complete Amounts. This field appears only with Method E. The system adds the values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers. o Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.
mnPeriod	AO1OW	MATH_NUMERIC	OPT	OUTPUT
A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid values are: o Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The system calculates force amounts. o Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force Amounts (FA) ledger. The system calculates +/- force amounts. o Percent Complete. This field appears with Methods F, G, O, P, and S. The new total in the Percent Complete (F%) ledger. o Estimate to Complete Amounts. This field appears only with Method E. The system adds the values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers. o Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.

The F0911 index must be changed to add a field to help fetch the information: F0911LY - logical on the AS400 must also be changed to
accommodate this functionality

GLPOST
GLAID
GLLT
GLCTRY
GLFY
GLPN
GLSBL
GLSBLT
GLDGJ

GLASID

Data Structure

D1200A - F1202 Data Sensitive Retrieval

Parameter Name Data Item Data Type Req/Opt I/O/Both

mnAssetID NUMB MATH_NUMERIC REQ INPUT

An 8-digit number that uniquely identifies an asset.

szAccountID AID char REQ INPUT

A number that the system assigns to each general ledger account in the Account Master table (F0901) to uniquely identify it.

szCompany CO char REQ INPUT

A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company
Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany
transactions. Note: You can use company 00000 for default values such as dates and automatic accounting instructions. You cannot use company 00000
for transaction entries.

szLedgerType LT char REQ INPUT

A user defined code (09/LT) that specifies the type of ledger, such as AA (Actual Amounts), BA (Budget Amount), or AU (Actual Units). You
can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.

szSubledger SBL char REQ INPUT

A code that identifies a detailed, auxiliary account within a general ledger account. A subledger can be an equipment item number or an
address book number. If you enter a subledger, you must also specify the subledger type.

cSubledgerType SBLT char REQ INPUT

A user defined code (00/ST) that is used with the Subledger field to identify the subledger type and how the system performs subledger
editing. On the User Defined Codes form, the second line of the description controls how the system performs editing. This is either hard-coded
or user defined. Valid values include: A Alphanumeric field, do not edit   N Numeric field, right justify and zero fill   C Alphanumeric field, right
justify and blank fill

jdDate DGL JDEDATE REQ BOTH

A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.

cErrorFlag EV01 char OPT OUTPUT

An option that specifies the type of processing for an event.

mnCentury CTRY MATH_NUMERIC REQ BOTH

The calendar century associated with the year. Enter is the first two digits of the year. For example, 19 indicates any year beginning with 19
(1998, 1999), 20 indicates any year beginning with 20 (2000, 2001), and so on.

mnFiscalYear FY MATH_NUMERIC REQ BOTH

A number that identifies the fiscal year. Generally, you can either enter a number in this field or leave it blank to indicate the current fiscal
year (as defined on the Company Setup form). Specify the year at the end of the first period rather than the year at the end of the fiscal period.
For example, a fiscal year begins October 1, 1998 and ends September 30, 1999. The end of the first period is October 31, 1998. Specify the
year 98 rather than 99.

mnPeriodNumber PN MATH_NUMERIC REQ BOTH

A number indicating the current accounting period.  This number, used in conjunction with the Company Constants table (F0010) and the
General Constants table (F0009), allows the user to define up to 14 accounting periods. See General Ledger Date.  The current period number
is used to determine posted before and posted after cut off warning messages.  It is also used as the default accounting period in the
preparation of financial reports.

jdStartPeriod DGL JDEDATE OPT BOTH

A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.

jdEndPeriod DGL JDEDATE OPT BOTH

A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.

idPointer GENLNG ID REQ BOTH

General purpose ID variable.

mnInception AO1OW MATH_NUMERIC OPT OUTPUT

A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid
values are:   o  Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The
system calculates force amounts.   o  Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force
Amounts (FA) ledger. The system calculates +/- force amounts.   o  Percent Complete. This field appears with Methods F, G, O, P, and S. The new
total in the Percent Complete (F%) ledger.   o  Estimate to Complete Amounts. This field appears only with Method E. The system adds the
values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the
estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.   o
Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the
Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.

mnYearToDate AO1OW MATH_NUMERIC OPT OUTPUT

A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid
values are:   o  Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The
system calculates force amounts.   o  Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force
Amounts (FA) ledger. The system calculates +/- force amounts.   o  Percent Complete. This field appears with Methods F, G, O, P, and S. The new
total in the Percent Complete (F%) ledger.   o  Estimate to Complete Amounts. This field appears only with Method E. The system adds the
values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the
estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.   o
Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the
Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.

mnPeriod AO1OW MATH_NUMERIC OPT OUTPUT

A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid
values are:   o  Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The
system calculates force amounts.   o  Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force
Amounts (FA) ledger. The system calculates +/- force amounts.   o  Percent Complete. This field appears with Methods F, G, O, P, and S. The new
total in the Percent Complete (F%) ledger.   o  Estimate to Complete Amounts. This field appears only with Method E. The system adds the
values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the
estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.   o
Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the
Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.

Related Functions

B5100016 Validate Job Cost Date and Period

X1202 F1201 Validate Asset Number

XX0901 Validate Account Number

Related Tables

F0025 Ledger Type Master File

F0911 Account Ledger

F1202 Asset Account Balances File

F1202ValidateProjectionBalances
F1202ValidateProjectionBalances

F1202 Date Sensitive Retrieval

Minor Business Rule

Object Name: X1200

Parent DLL: CAEC

Location: Client/Server

Language: C

Purpose
This function validates depreciation projection balances for two modes.
Projection Balances DPCF
^

Data Structure

D1200B - Validate Depreciation Projections

Parameter Name Data Item Data Type Req/Opt I/O/Both

cDepreciationProjection_DPCF DPCF char REQ INPUT

A code that indicates whether a record in the Asset Account Balances table (F1202) is the result of running the Depreciation Projections
program (R12865). The Depreciation Projections program updates the F1202 in the future for budgeting, reporting, tax deferrals, and so on. This
code is only updated on the Accumulated Depreciation and Depreciation expense accounts. The only way to determine whether a balance
is the result of User Defined Actual Depreciation from a balance that has been projected is to review this field. Projection balances must be
purged using the Purge Depreciation Projections program (R12859) before actual depreciation balances can be updated. Valid values
are: Blank Actual Accumulated Depreciation and Depreciation expense. 1        Projected Accumulated Depreciation and Depreciation expense.

szAccountId_AID AID char REQ INPUT

A number that the system assigns to each general ledger account in the Account Master table (F0901) to uniquely identify it.

cSuppressError_EV01 EV01 char OPT INPUT

An option that specifies the type of processing for an event.

szErrorMessage_DTAI DTAI char OPT OUTPUT

A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or
special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.

Related Functions

B5100016 Validate Job Cost Date and Period

X1202 F1201 Validate Asset Number

XX0901 Validate Account Number

Related Tables

F0025 Ledger Type Master File

F0911 Account Ledger

F1202 Asset Account Balances File

MemoryFreeFixedAssetRetrieval
MemoryFreeFixedAssetRetrieval

F1202 Date Sensitive Retrieval

Minor Business Rule

Object Name: X1200

Parent DLL: CAEC

Location: Client/Server

Language: C

Purpose
The F1202 GL Date Sensitive Retrieval uses a Pointer to store the hUser, hRequestF1202, and hRequestF0911.
This function will close the tables, and free memory.

Setup Notes and Prerequisites
A valid Pointer should exist from the F1202 GL Date Sensitive Retrieval BSFN.

^

Data Structure

D1200A - F1202 Data Sensitive Retrieval

Parameter Name Data Item Data Type Req/Opt I/O/Both

mnAssetID NUMB MATH_NUMERIC REQ INPUT

An 8-digit number that uniquely identifies an asset.

szAccountID AID char REQ INPUT

A number that the system assigns to each general ledger account in the Account Master table (F0901) to uniquely identify it.

szCompany CO char REQ INPUT

A code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the Company
Constants table (F0010) and must identify a reporting entity that has a complete balance sheet. At this level, you can have intercompany
transactions. Note: You can use company 00000 for default values such as dates and automatic accounting instructions. You cannot use company 00000
for transaction entries.

szLedgerType LT char REQ INPUT

A user defined code (09/LT) that specifies the type of ledger, such as AA (Actual Amounts), BA (Budget Amount), or AU (Actual Units). You
can set up multiple, concurrent accounting ledgers within the general ledger to establish an audit trail for all transactions.

szSubledger SBL char REQ INPUT

A code that identifies a detailed, auxiliary account within a general ledger account. A subledger can be an equipment item number or an
address book number. If you enter a subledger, you must also specify the subledger type.

cSubledgerType SBLT char REQ INPUT

A user defined code (00/ST) that is used with the Subledger field to identify the subledger type and how the system performs subledger
editing. On the User Defined Codes form, the second line of the description controls how the system performs editing. This is either hard-coded
or user defined. Valid values include: A Alphanumeric field, do not edit   N Numeric field, right justify and zero fill   C Alphanumeric field, right
justify and blank fill

jdDate DGL JDEDATE REQ BOTH

A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.

cErrorFlag EV01 char OPT OUTPUT

An option that specifies the type of processing for an event.

mnCentury CTRY MATH_NUMERIC REQ BOTH

The calendar century associated with the year. Enter is the first two digits of the year. For example, 19 indicates any year beginning with 19
(1998, 1999), 20 indicates any year beginning with 20 (2000, 2001), and so on.

mnFiscalYear FY MATH_NUMERIC REQ BOTH

A number that identifies the fiscal year. Generally, you can either enter a number in this field or leave it blank to indicate the current fiscal
year (as defined on the Company Setup form). Specify the year at the end of the first period rather than the year at the end of the fiscal period.
For example, a fiscal year begins October 1, 1998 and ends September 30, 1999. The end of the first period is October 31, 1998. Specify the
year 98 rather than 99.

mnPeriodNumber PN MATH_NUMERIC REQ BOTH

A number indicating the current accounting period.  This number, used in conjunction with the Company Constants table (F0010) and the
General Constants table (F0009), allows the user to define up to 14 accounting periods. See General Ledger Date.  The current period number
is used to determine posted before and posted after cut off warning messages.  It is also used as the default accounting period in the
preparation of financial reports.

jdStartPeriod DGL JDEDATE OPT BOTH

A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.

jdEndPeriod DGL JDEDATE OPT BOTH

A date that identifies the financial period to which the transaction is to be posted. The company constants specify the date range for each
financial period. You can have as many as 14 periods. Generally, period 14 is used for audit adjustments. The system validates this field for
PBCO (posted before cutoff), PYEB (prior year ending balance), PACO (post after cutoff), and WACO (post way after cutoff) messages.

idPointer GENLNG ID REQ BOTH

General purpose ID variable.

mnInception AO1OW MATH_NUMERIC OPT OUTPUT

A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid
values are:   o  Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The
system calculates force amounts.   o  Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force
Amounts (FA) ledger. The system calculates +/- force amounts.   o  Percent Complete. This field appears with Methods F, G, O, P, and S. The new
total in the Percent Complete (F%) ledger.   o  Estimate to Complete Amounts. This field appears only with Method E. The system adds the
values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the
estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.   o
Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the
Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.

mnYearToDate AO1OW MATH_NUMERIC OPT OUTPUT

A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid
values are:   o  Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The
system calculates force amounts.   o  Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force
Amounts (FA) ledger. The system calculates +/- force amounts.   o  Percent Complete. This field appears with Methods F, G, O, P, and S. The new
total in the Percent Complete (F%) ledger.   o  Estimate to Complete Amounts. This field appears only with Method E. The system adds the
values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the
estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.   o
Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the
Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.

mnPeriod AO1OW MATH_NUMERIC OPT OUTPUT

A value that the method of computation and processing options are set to in order to determine which fields appear on this form. Valid
values are:   o  Force +/- Amounts. This field appears with Methods F, G, O, Q, and S. Incremental change to the Force Amounts (FA) ledger. The
system calculates force amounts.   o  Force Total Amounts. This field appears with Methods F, G, O, Q, and S. The new total in the Force
Amounts (FA) ledger. The system calculates +/- force amounts.   o  Percent Complete. This field appears with Methods F, G, O, P, and S. The new
total in the Percent Complete (F%) ledger.   o  Estimate to Complete Amounts. This field appears only with Method E. The system adds the
values in this field, the Estimate to Complete Units fields, and Unit Rate field to the Actual Units and Actual Amounts fields to determine the
estimate total (projected final values). The system updates the Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.   o
Estimate Total Amounts. This field appears only with Method E. The values in this field are the projected final values. The system updates the
Projected Final Amounts (HA) and Projected Final Units (HU) ledgers.

Related Functions

B5100016 Validate Job Cost Date and Period

X1202 F1201 Validate Asset Number

XX0901 Validate Account Number

Related Tables

F0025 Ledger Type Master File

F0911 Account Ledger

F1202 Asset Account Balances File

B5100016 Validate Job Cost Date and Period
X1202 F1201 Validate Asset Number
XX0901 Validate Account Number

F0025 Ledger Type Master File
F0911 Account Ledger
F1202 Asset Account Balances File

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cDepreciationProjection_DPCF	DPCF	char	REQ	INPUT
A code that indicates whether a record in the Asset Account Balances table (F1202) is the result of running the Depreciation Projections program (R12865). The Depreciation Projections program updates the F1202 in the future for budgeting, reporting, tax deferrals, and so on. This code is only updated on the Accumulated Depreciation and Depreciation expense accounts. The only way to determine whether a balance is the result of User Defined Actual Depreciation from a balance that has been projected is to review this field. Projection balances must be purged using the Purge Depreciation Projections program (R12859) before actual depreciation balances can be updated. Valid values are: Blank Actual Accumulated Depreciation and Depreciation expense. 1 Projected Accumulated Depreciation and Depreciation expense.
szAccountId_AID	AID	char	REQ	INPUT
A number that the system assigns to each general ledger account in the Account Master table (F0901) to uniquely identify it.
cSuppressError_EV01	EV01	char	OPT	INPUT
An option that specifies the type of processing for an event.
szErrorMessage_DTAI	DTAI	char	OPT	OUTPUT
A code that identifies and defines a unit of information. It is an alphanumeric code up to 8 characters long that does not allow blanks or special characters such as %, &, or +. You create new data items using system codes 55-59. You cannot change the alias.