| Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
|---|
| szBasisComponentOld | CBSS | char | REQ | INPUT |
A component code that identifies a provisional burden that is accounted for at the billing detail transaction level. |
| szComponentTableOld | CTBL | char | REQ | INPUT |
Component tables allow you to set up provisional burdens which are attached at the billing detail transaction level. You can base the
component calculations on the cost, invoice (including taxes), and/or revenue amounts of the base billing detail transaction.
For example,
components based on the cost amount would allow you to apply additional overhead to costs incurred by the organization. Components based on
the invoice amount would allow you to apply charges in addition to the markup amount for billing.
You control the amount basis for this
calculation in the fold area of the Cost Plus Markup table. When you enter the name of the component table in the Cost Table field, the system bases
all calculations on the cost amount. Similarly,when you enter the name of the component table in the Inv/Rev Tbl field, the system bases all
calculations on the invoice and/or revenue amounts, depending on the generation type of the Cost Plus Markup table and the Journal
Generation Control flag setting in the system constants. |
| jdDateBeginningEffectiveOld | EFTB | JDEDATE | REQ | INPUT |
The date that an address, item, transaction, or table record becomes active. The meaning of this field differs, depending on the program.
For example, the effective date could represent the following:
o When a change of address becomes effective.
o When a lease becomes
effective.
o When a price becomes effective.
o When the currency exchange rate becomes effective.
o When a tax rate becomes effective.
|
| szCurrencyCodeFromOld | CRCD | char | REQ | INPUT |
A code that identifies the currency of a transaction.
|
| szComponentTableNew | CTBL | char | REQ | INPUT |
Component tables allow you to set up provisional burdens which are attached at the billing detail transaction level. You can base the
component calculations on the cost, invoice (including taxes), and/or revenue amounts of the base billing detail transaction.
For example,
components based on the cost amount would allow you to apply additional overhead to costs incurred by the organization. Components based on
the invoice amount would allow you to apply charges in addition to the markup amount for billing.
You control the amount basis for this
calculation in the fold area of the Cost Plus Markup table. When you enter the name of the component table in the Cost Table field, the system bases
all calculations on the cost amount. Similarly,when you enter the name of the component table in the Inv/Rev Tbl field, the system bases all
calculations on the invoice and/or revenue amounts, depending on the generation type of the Cost Plus Markup table and the Journal
Generation Control flag setting in the system constants. |
| jdDateBeginningEffectiveNew | EFTB | JDEDATE | REQ | INPUT |
The date that an address, item, transaction, or table record becomes active. The meaning of this field differs, depending on the program.
For example, the effective date could represent the following:
o When a change of address becomes effective.
o When a lease becomes
effective.
o When a price becomes effective.
o When the currency exchange rate becomes effective.
o When a tax rate becomes effective.
|
| szCurrencyCodeFromNew | CRCD | char | REQ | INPUT |
A code that identifies the currency of a transaction.
|