| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szCashType | CSHTYP | char | REQ | BOTH |
A unique 10-character value identifying a source of cash inflow or outflow, such as open invoices, open vouchers, or bank accounts. This
name must exist in User Defined Codes 09|CT.
|
| szPrevCashType | CSHTYP | char | REQ | BOTH |
A unique 10-character value identifying a source of cash inflow or outflow, such as open invoices, open vouchers, or bank accounts. This
name must exist in User Defined Codes 09|CT.
|
| szSourceSystem | SRCSYS | char | REQ | BOTH |
The accounting system that contains the source table to be used when extracting cash forecasting information for a cash type. Valid values
are:
03B
Accounts Receivable System (for cash types involving open A/R invoices).
04
Accounts Payable System (for cash types involving
A/P open vouchers).
09
General Ledger System (for cash types involving balances for G/L bank accounts).
|
| szPrevSourceSystem | SRCSYS | char | REQ | BOTH |
The accounting system that contains the source table to be used when extracting cash forecasting information for a cash type. Valid values
are:
03B
Accounts Receivable System (for cash types involving open A/R invoices).
04
Accounts Payable System (for cash types involving
A/P open vouchers).
09
General Ledger System (for cash types involving balances for G/L bank accounts).
|
| szBankAID | BNKAID | char | REQ | BOTH |
A number that the system assigns to general ledger accounts in the Account Master table (F0901) to uniquely identify them.
|
| szPrevBankAID | BNKAID | char | REQ | BOTH |
A number that the system assigns to general ledger accounts in the Account Master table (F0901) to uniquely identify them.
|
| szCurrCodeBase | BCRC | char | REQ | BOTH |
A code that represents the currency of the company for a transaction. For a foreign currency transaction, this is the currency code of the
domestic side of the transaction.
|
| szPrevCurrCodeBase | BCRC | char | REQ | BOTH |
A code that represents the currency of the company for a transaction. For a foreign currency transaction, this is the currency code of the
domestic side of the transaction.
|
| cCurrCodeBase_Asterisk | EV02 | char | REQ | BOTH |
An option that specifies the type of processing for an event.
|
| szDocType | DCT | char | REQ | BOTH |
A user defined code (00/DT) that identifies the origin and purpose of the transaction. PeopleSoft reserves several prefixes for document
types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are:
P
Accounts payable
documents
R
Accounts receivable documents
T
Time and Pay documents
I
Inventory documents
O
Purchase order documents
S
Sales order
documents
|
| szPrevDocType | DCT | char | REQ | BOTH |
A user defined code (00/DT) that identifies the origin and purpose of the transaction. PeopleSoft reserves several prefixes for document
types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are:
P
Accounts payable
documents
R
Accounts receivable documents
T
Time and Pay documents
I
Inventory documents
O
Purchase order documents
S
Sales order
documents
|
| cDocType_Asterisk | EV03 | char | REQ | BOTH |
A radio button that specifies the level at which trace/track result is to be displayed. Select the Detail to display all transactions except IB, IX,
and IZ types. Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.
|
| cPmtInstr | PYIN | char | REQ | BOTH |
A user defined code (00/PY) that determines the means by which a payment is issued to a supplier or received from the customer.
Examples of payment instruments include check, electronic funds transfer, lockbox, and EDI.
|
| cPrevPmtInstr | PYIN | char | REQ | BOTH |
A user defined code (00/PY) that determines the means by which a payment is issued to a supplier or received from the customer.
Examples of payment instruments include check, electronic funds transfer, lockbox, and EDI.
|
| cPmtInstr_Asterisk | EV04 | char | REQ | BOTH |
PeopleSoft event point processing flag 04.
|
| cAROrigModule | OMOD | char | REQ | BOTH |
A user defined code (03B/OS) that identifies the system that generated the invoice or credit memo. Valid values are:
Blank
Not Applicable.
The system does not update this field if the invoice record was generated from a receipt or draft application. Examples are deduction (R5),
draft (R1), and chargeback (RB) records.
0
Accounts Receivable.
1
Real Estate Management.
2
Contract Billing.
3
Sales Order
Management.
4
Service Billing.
Note: All invoice records generated prior to release ERP 9.0 will be updated with 0.
|
| cPrevAROrigModule | OMOD | char | REQ | BOTH |
A user defined code (03B/OS) that identifies the system that generated the invoice or credit memo. Valid values are:
Blank
Not Applicable.
The system does not update this field if the invoice record was generated from a receipt or draft application. Examples are deduction (R5),
draft (R1), and chargeback (RB) records.
0
Accounts Receivable.
1
Real Estate Management.
2
Contract Billing.
3
Sales Order
Management.
4
Service Billing.
Note: All invoice records generated prior to release ERP 9.0 will be updated with 0.
|
| cAROrigMod_Asterisk | EV05 | char | REQ | BOTH |
A flag that indicates whether automatic spell check is turned on. |
| cAPOrigModule | RP3 | char | REQ | BOTH |
In Accounts Receivable, a code to designate whether cash records from cash receipts are written in detail or summary. All records within a
batch have the same value. Valid values are:
Blank
Cash records are written in summary.
1
Cash records are written in detail.
In Accounts
Payable, a code to designate the status of a voucher that was created by a software module other than Accounts Payable. Valid values
are:
P
Preliminary Invoice (without redistribution)
R
Redistribution complete
C
Credit tied to debit business unit
M
Voucher match
L
Logged voucher for a
purchase order
|
| cPrevAPOrigModule | RP3 | char | REQ | BOTH |
In Accounts Receivable, a code to designate whether cash records from cash receipts are written in detail or summary. All records within a
batch have the same value. Valid values are:
Blank
Cash records are written in summary.
1
Cash records are written in detail.
In Accounts
Payable, a code to designate the status of a voucher that was created by a software module other than Accounts Payable. Valid values
are:
P
Preliminary Invoice (without redistribution)
R
Redistribution complete
C
Credit tied to debit business unit
M
Voucher match
L
Logged voucher for a
purchase order
|
| cAPOrigMod_Asterisk | EV06 | char | REQ | BOTH |
An option that specifies the type of processing for an event.
|
| szBegObject | BEGOBJ | char | REQ | BOTH |
The beginning object in a range of accounts (the object represents the portion of a general ledger account that refers to the division of the
Cost Code (for example, labor, materials, and equipment) into subcategories). For example, you can divide the Cost Code for labor into
regular time, premium time, and burden).
Note: If you use a flexible chart of accounts and the object account is set to 6 digits, J.D. Edwards
recommends that you use all 6 digits. For example, entering 000456 is not the same as entering 456 because if you enter 456 the system enters three
blank spaces to fill a 6-digit object.
|
| szPrevBegObject | BEGOBJ | char | REQ | BOTH |
The beginning object in a range of accounts (the object represents the portion of a general ledger account that refers to the division of the
Cost Code (for example, labor, materials, and equipment) into subcategories). For example, you can divide the Cost Code for labor into
regular time, premium time, and burden).
Note: If you use a flexible chart of accounts and the object account is set to 6 digits, J.D. Edwards
recommends that you use all 6 digits. For example, entering 000456 is not the same as entering 456 because if you enter 456 the system enters three
blank spaces to fill a 6-digit object.
|
| szBegSubsid | BEGSUB | char | REQ | BOTH |
The starting subsidiary, used together with the starting object, to begin a range of accounts (the subsidiary represents the subset of an
object account). Subsidiary accounts include detailed records of the accounting activity for an object account.
|
| szPrevBegSubsid | BEGSUB | char | REQ | BOTH |
The starting subsidiary, used together with the starting object, to begin a range of accounts (the subsidiary represents the subset of an
object account). Subsidiary accounts include detailed records of the accounting activity for an object account.
|
| szEndObject | ENDOBJ | char | REQ | BOTH |
The ending object in a range of accounts (the object represents the portion of a general ledger account that refers to the division of the Cost
Code (for example, labor, materials, and equipment) into subcategories). For example, you can divide the Cost Code for labor into regular
time, premium time, and burden).
Note: If you use a flexible chart of accounts and the object account is set to 6 digits, J.D. Edwards
recommends that you use all 6 digits. For example, entering 000456 is not the same as entering 456 because if you enter 456 the system enters three
blank spaces to fill a 6-digit object.
|
| szPrevEndObject | ENDOBJ | char | REQ | BOTH |
The ending object in a range of accounts (the object represents the portion of a general ledger account that refers to the division of the Cost
Code (for example, labor, materials, and equipment) into subcategories). For example, you can divide the Cost Code for labor into regular
time, premium time, and burden).
Note: If you use a flexible chart of accounts and the object account is set to 6 digits, J.D. Edwards
recommends that you use all 6 digits. For example, entering 000456 is not the same as entering 456 because if you enter 456 the system enters three
blank spaces to fill a 6-digit object.
|
| szEndSubsid | ENDSUB | char | REQ | BOTH |
The ending subsdiary used together with the ending object to complete a range of accounts (the subsidiary represents the subset of an
object account). Subsidiary accounts include detailed records of the accounting activity for an object account.
|
| szPrevEndSubsid | ENDSUB | char | REQ | BOTH |
The ending subsdiary used together with the ending object to complete a range of accounts (the subsidiary represents the subset of an
object account). Subsidiary accounts include detailed records of the accounting activity for an object account.
|
| cPastDueCateg | PDCATG | char | REQ | BOTH |
If this flag is on, then the cash type is considered to be a past due cash type and any corresponding forecasting data will be created by
selecting A/R or A/P net due date ranges that are prior to the date that cash forecast data is being refreshed on, according to the beginning and
ending past due days specified for this cash type rule.
If this flag is off, then data will be created for this cash type by selecting net due dates
that are greater than or equal to the to the date cash forecast data is being refreshed on.
|
| cPrevPastDueCateg | PDCATG | char | REQ | BOTH |
If this flag is on, then the cash type is considered to be a past due cash type and any corresponding forecasting data will be created by
selecting A/R or A/P net due date ranges that are prior to the date that cash forecast data is being refreshed on, according to the beginning and
ending past due days specified for this cash type rule.
If this flag is off, then data will be created for this cash type by selecting net due dates
that are greater than or equal to the to the date cash forecast data is being refreshed on.
|
| mnPastDueBegDays | PDDAYB | MATH_NUMERIC | REQ | BOTH |
The beginning number of days prior to the date cash forecast data is refreshed on, for using to select A/R or A/P net due date ranges within
the beginning and ending number of days past due (e.g. beginning 1 day past due and ending 7 days past due), so that past due amounts
can be included in cash forecasting when desired.
|
| mnPrevPastDueBegDays | PDDAYB | MATH_NUMERIC | REQ | BOTH |
The beginning number of days prior to the date cash forecast data is refreshed on, for using to select A/R or A/P net due date ranges within
the beginning and ending number of days past due (e.g. beginning 1 day past due and ending 7 days past due), so that past due amounts
can be included in cash forecasting when desired.
|
| mnPastDueEndDays | PDDAYE | MATH_NUMERIC | REQ | BOTH |
The ending number of days prior to the date cash forecast data is refreshed on, for using to select A/R or A/P net due date ranges within the
beginning and ending number of days past due (e.g. beginning 1 day past due and ending 7 days past due), so that past due amounts can
be included in cash forecasting when desired.
|
| mnPrevPastDueEndDays | PDDAYE | MATH_NUMERIC | REQ | BOTH |
The ending number of days prior to the date cash forecast data is refreshed on, for using to select A/R or A/P net due date ranges within the
beginning and ending number of days past due (e.g. beginning 1 day past due and ending 7 days past due), so that past due amounts can
be included in cash forecasting when desired.
|
| cPastDueProcMode | PDPROC | char | REQ | BOTH |
If this flag is blank or zero, then the past due amount calculated for this cash type rule will be rolled into the first date period column on the
Cash Forecast Analysis.
If this processing flag is 1, then the past due amount calculated for this cash type rule will be listed in an initial past due
column on the Cash Forecast Analysis, and will not be included in any date period columns.
Valid values are:
0 - Roll amount into first date
column.
1 - Show amount in separate past due column.
|
| szNodeRevalCurr | NDCRCD | char | REQ | BOTH |
A currency that cash forecast amounts for this cash type will be stored in (F09522). If revaluation is necessary for cash forecast amounts
when data is being refreshed, the exchange rates used in calculating the revalued amount will be retrieved corresponding to the refresh based
on date.
|
| mnWeightFactor | WGHTNO | MATH_NUMERIC | REQ | BOTH |
This field indicates a multiplier by which to measure the customer's confidence level about receiving the actual amount of cash forecasted
for an item (such as expecting only about 80% (or 0.80 weight factor)) of open invoices to actually be paid on a due date, or using a weight
factor of 1.10 to increase the amount of open vouchers on a cash forecast by 10% to adjust for unexpected events. The default is 1.
|
| cRuleStatus | RLSTAT | char | REQ | BOTH |
A flag that denotes whether a cash type rule is active or inactive. Only cash type rules that are at an active status will be used to create
cash forecast data during the refresh. The default is active.
Valid values are
1 (Active)
0 (Inactive)
|
| szErrorNumber | ERNO | char | REQ | BOTH |
The error number assigned by the JDE edit/update programs designating the exact error that occured. |
| cErrorFlag | EV07 | char | REQ | BOTH |
An option that specifies the type of processing for an event.
|
| cProcessingMode | EV08 | char | REQ | BOTH |
An option that specifies the type of processing for an event.
|
| szBankANI | BNKANI | char | REQ | BOTH |
A value that identifies a bank account in the general ledger. Use one of the following formats to enter account numbers:
o Standard account
number (business unit.object.subsidiary or flex format).
o Third G/L number (maximum of 25 digits).
o Account ID number. The number is
eight digits long.
o Speed code, which is a two-character code that you concatenate to the AAI item SP. You can then enter the code instead
of an account number.
The first character of the account number indicates its format. You define the account format in the General Accounting
constants. Bank account numbers are required to be assigned by customers to A/R cash types and will be updated to the cash forecast
table during the refresh (for subsequent display on the cash forecast analysis) because the bank account cannot accurately be determined for
open A/R invoices until cash receipt time. Thus the A/R bank account must be specified in the cash type rule.
However, in Accounts Payable,
Bank Accounts may optionally be used in data selection criteria for a cash type because the bank account is already known for the voucher
and exists in the source table.
|
| szPrevBankANI | BNKANI | char | REQ | BOTH |
A value that identifies a bank account in the general ledger. Use one of the following formats to enter account numbers:
o Standard account
number (business unit.object.subsidiary or flex format).
o Third G/L number (maximum of 25 digits).
o Account ID number. The number is
eight digits long.
o Speed code, which is a two-character code that you concatenate to the AAI item SP. You can then enter the code instead
of an account number.
The first character of the account number indicates its format. You define the account format in the General Accounting
constants. Bank account numbers are required to be assigned by customers to A/R cash types and will be updated to the cash forecast
table during the refresh (for subsequent display on the cash forecast analysis) because the bank account cannot accurately be determined for
open A/R invoices until cash receipt time. Thus the A/R bank account must be specified in the cash type rule.
However, in Accounts Payable,
Bank Accounts may optionally be used in data selection criteria for a cash type because the bank account is already known for the voucher
and exists in the source table.
|
| cBankANI_Asterisk | EV09 | char | REQ | BOTH |
An option that specifies the type of processing for an event.
|
| cBegSubsid_Asterisk | EV01 | char | REQ | BOTH |
An option that specifies the type of processing for an event.
|
| cEndSubsid_Asterisk | EV01 | char | REQ | BOTH |
An option that specifies the type of processing for an event.
|
| szCacheName | DL01 | char | REQ | BOTH |
A user defined name or remark. |
| mnJobNumber | JOBS | MATH_NUMERIC | REQ | BOTH |
The job number (work station ID) which executed the particular job. |
| szRptStructureName | RSTRUC | char | REQ | BOTH |
The unique name for a hierarchical structure created for the purpose of governing how data is displayed in cash forecasting. This name
must exist in Reporting Structures (F09523).
|