| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szCurrencyCodeFrom | CRCD | char | OPT | NONE |
A code that identifies the currency of a transaction.
|
| szValuationMethod | SVVM | char | OPT | NONE |
A two-character abbreviation for the methods that the system uses to determine the value of your company's stock for reporting and
financial purposes.
Examples include:
o FI (FIFO)
o F2 (FIFO Detail by Branch)
o LI (LIFO)
When you run the Stock Valuation Extraction
program, the system updates the Stock Valuation Detail tables for the assigned valuation methods. |
| mnFiscalYear999999999 | SVYR | MATH_NUMERIC | OPT | NONE |
The fiscal year for the period being processed. |
| mnPeriodNumberCurrent | PNC | MATH_NUMERIC | OPT | NONE |
A number (from 1 to 14) that identifies the current accounting period . The system uses this number to generate error messages, such as
PBCO (posted before cut off) and PACO (posted after cut off). |
| szItemPool | ITPL | char | OPT | NONE |
A user defined code (41/05) that indicates a group of items that are evaluated using the same set of valuation methods. You assign the item
pool to the item and then set up valuation methods for the pool using the Pool Valuation Method Maintenance program. |
| mnIdentifierShortItem | ITM | MATH_NUMERIC | OPT | NONE |
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item
numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and
so forth. The item numbers are as follows:
o Item Number (short) - An eight-digit, computer-assigned item number
o 2nd Item Number - The
25-digit, free-form, user defined alphanumeric item number
o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item
number |
| szCompany | CO | char | OPT | NONE |
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.
|
| szCostCenter | MCU | char | OPT | NONE |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit
might be a warehouse location, job, project, work center, branch, or plant.
You can assign a business unit to a document, entity, or person for
purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by
business unit to track equipment by responsible department.
Business unit security might prevent you from viewing information about business units
for which you have no authority.
|
| szDataItem | DTAI | char | OPT | NONE |
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.
|
| cValuationType | VLTY | char | OPT | NONE |
A hard-coded user defined code (system 39/type VA) indicating the type of process that the valuation method should use in stock
valuation. Identify if the method is a LIFO, FIFO, or Weighted Average Cost valuation type. |
| szBusFunNegetiveInventory | BFNN | char | OPT | NONE |
A business function that retrieves a replacement unit cost when the Stock Valuation closing quantity is negative. A custom user defined
BSFN or the Stock Valuation BSFN can also be used. |
| szBusFuncNamUnitCost | BFNU | char | OPT | NONE |
A business function that determines a unit cost for any valuation method within Stock Valuation. A custom user-defined BSFN or the Stock
Valuation BSFN can be used. |
| cWithinBranchorCompany | WBOC | char | OPT | NONE |
Use this processing option to identify how the system allocates the historical layers built by the valuation method. Valid values are:
1
Within company. The system creates one record per company, item or pool, valuation method, and period.
2 Within branch. The period detail
contains one record per branch, item or pool, valuation method, and period.
At the end of the year, the system rolls all detail layers and
period summary layers into one layer for LIFO. |
| jdGLDate | DGL | JDEDATE | OPT | NONE |
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.
|
| cIncludeLIFOAdjustment | LIFA | char | OPT | NONE |
Use this adjustment to remove the effect of any accumulation or depletion at the end of a reporting period. Do not apply the LIFO
adjustment for the closing period of a fiscal year. Record the adjustment against the income statement and balance sheet accounts.
The system uses
the following formula to determine the LIFO adjustment:
(average cost of the accumulation or depletion - current period's average cost) *
accumulation or depletion
If this valuation method is a LIFO method type and set up as a company-wide method, you might want the system to
calculate a LIFO adjustment. Valid values are:
Y or 1 include the LIFO adjustment calculation. This is a company-wide LIFO valuation
method, and the default.
N or 0 do not include the LIFO adjustment. This LIFO method is either layered within a branch/plant or is not
company-wide. |