Parameter Name | Data Item | Data Type | Req/Opt | I/O/Both |
jdDateCurrentBillingF1304 | CBDT | JDEDATE | REQ | INPUT |
The date of the current billing. |
cProRateBillingF1304 | PRO | char | REQ | INPUT |
Use this field to specify whether billings are calculated on a hierarchical basis, or are prorated on a monthly basis. The billing program
computes the hierarchical basis based on the lower of the hourly, daily, weekly, or monthly rate. For example, if you bill a piece of equipment to a
job using a weekly rate but use that equipment only three days, you can use the daily rate code associated with that weekly rate code.
The
billing program computes the prorated basis based on the ratio of the number of days that the equipment is used to the total number of
working days in the month. For example, if there are 20 working days in the month and you use a piece of equipment five days, the Location Billing
program charges 25% of the monthly rate.
If you do not specify proration, the system uses monthly, weekly, daily and hourly rate codes to
determine the billing amount. Valid values for this field are:
Y Prorate the monthly rate. You must define the equipment rate code as monthly
N Use Hierarchy until the monthly rate is reached
H Use Hierarchy at all times |
szEquipmentRateCodeF1204 | ERC | char | REQ | INPUT |
A user defined code (00/RC) that indicates a billing rate, such as DY for daily, MO for monthly, and WK for weekly. You can set up multiple
billing rates for a piece of equipment.
If you leave this field blank, the system searches for a valid billing rate in the following sequence:
1.
Account Ledger Master (F0901)
This table contains the most detailed rate information. You can assign multiple rates for a job. For example, you
can set up separate rates for different equipment working conditions.
2. Job or Business Unit Master (F0006)
This table contains less detailed
rate information than the Account Ledger Master. You can only set up a single rate for a job based on this table.
3. Rental Rules (F1302)
This
table contains the least detailed rate code information. The system searches this table according to the criteria you establish when setting up
the table. |
mnBillingRateEquipmentF1304 | EBRT | MATH_NUMERIC | REQ | INPUT |
A code that represents the amount that you want to charge the job. Each piece of equipment can have numerous billing rates based on the
rate code. The equipment billing rate can be composed of up to ten different rates. For example:
Billing Rate = 200
100 Rate 1 (Ownership
Component)
25 Rate 2 (Operating Component)
50 Rate 3 (Maintenance Component)
25 Rate 4 (Other Costs Component)
When
you post time entries to the general ledger, the system recognizes credits in revenue accounts for each of the rate components. This allows
you to separate portions of the equipment billing by type of cost.
Note: You are not required to use rate components. |
jdDateEndingF1204 | END | JDEDATE | REQ | INPUT |
The date when an asset was removed or returned from a particular location.
|
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.
|
szCostCenterLocation | LOC | char | REQ | INPUT |
The current physical location of an asset. The location must have a valid business unit or job number in the Business Unit Master table
(F0006). |
mnAssetItemNumberF1301 | NUMB | MATH_NUMERIC | REQ | INPUT |
An 8-digit number that uniquely identifies an asset.
|
szEquipmentRateTableF1301 | RTTB | char | REQ | INPUT |
A user defined code (system 13, type TB) that identifies tables of different groups of rental rates for equipment. You can set up as many
different tables as you need for a particular organization. For example, you can set up tables for company rates, AED published rates, blue
book rates, and so forth. |
mnHoursBilledF1304 | HRBL | MATH_NUMERIC | OPT | OUTPUT |
The number of hours billed. |
mnAmountCurrentBillingF1304 | CBAM | MATH_NUMERIC | OPT | OUTPUT |
The amount of the current billing. |
mnAmountTotalBilledF1304 | TTBL | MATH_NUMERIC | OPT | BOTH |
The total amount billed. |
mnDelimitedBillingTotalF1304 | DBTT | MATH_NUMERIC | OPT | BOTH |
The billing total for a piece of equipment as of the last billing. |
jdDateBeginningEffectiveF1204 | 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.
|
mnTimeStampBeginningF1204 | DDTS | MATH_NUMERIC | REQ | INPUT |
The time that the asset is transferred to a new location. |
mnTimeStampEndingF1204 | DTSO | MATH_NUMERIC | REQ | INPUT |
The time that the asset was transferred from the job or will no longer be at a specified location. |
mnTimeBeginningDefaultF1302 | TBEG | MATH_NUMERIC | REQ | INPUT |
Standard beginning hour for the work day. For instance, in office work, the standard beginning hour would be 8:00 a.m. for a standard 8:00 to
5:00 day. |
mnTimeEndingDefaultF1302 | TEND | MATH_NUMERIC | REQ | INPUT |
Standard ending hour for the work day. For instance, in office work, the standard ending hour would be 5:00 p.m. for a standard 8:00 to 5:00
day. |
mnQuantityF1204 | QTY | MATH_NUMERIC | REQ | INPUT |
The number of units associated with an asset. |
mnDaysBilledF1304 | DYBL | MATH_NUMERIC | OPT | OUTPUT |
The number of days billed. |
szEquipRateCodeHourlyF1390 | ERCH | char | REQ | INPUT |
For Location Billing clients only. This code is an equipment rate code (system 00, type RC) that is associated with an hourly billing rate. It
allows you to set up a hierarchy of billing rates within the hourly rate code. For example,your bill rate code hierarchy for an hourly rate will be
only hourly. |
szAdditionalRateTableF1302 | CORT | char | REQ | INPUT |
The rate table used as an additional charge or credit during billing. Some examples are: an additional charge for overtime (harsh usage)
or a credit for a preferred customer. |
szEquipmentRateGroupF1301 | RTGR | char | REQ | INPUT |
A user defined code (12/C0) that identifies groups of similar pieces of equipment that are tied together for billing purposes.
|
jdDelimitedDateTsF1304 | DDTE | JDEDATE | REQ | BOTH |
The date/time that the last billing was billed through. |
mnWeeksBilledF1304 | WKBL | MATH_NUMERIC | OPT | OUTPUT |
The number of weeks billed. |
cIsFirstTimeFlag_ev01 | EV01 | char | REQ | INPUT |
An option that specifies the type of processing for an event.
|
cIsContinusFlag_ev01 | EV01 | char | REQ | INPUT |
An option that specifies the type of processing for an event.
|
mnMonthsBilledF1304 | MNBL | MATH_NUMERIC | OPT | OUTPUT |
The number of months billed. |
jdDatePOThru_OD1 | OD1 | JDEDATE | REQ | INPUT |
Lot Proceed information field. |
mnPercentOverride | PO01 | MATH_NUMERIC | REQ | INPUT |
Enter a percentage value for each rate table that you specify for the job. The Location Billing program calculates the percentage you enter
in this field times the rate code for a specific rate table. For example, if the rate code of HR (hourly) equals 100 and the percentage equals 80,
the amount charged equals 80 (100 x 80%). |
szEquipmentRateCodeF1304 | ERC | char | REQ | INPUT |
A user defined code (00/RC) that indicates a billing rate, such as DY for daily, MO for monthly, and WK for weekly. You can set up multiple
billing rates for a piece of equipment.
If you leave this field blank, the system searches for a valid billing rate in the following sequence:
1.
Account Ledger Master (F0901)
This table contains the most detailed rate information. You can assign multiple rates for a job. For example, you
can set up separate rates for different equipment working conditions.
2. Job or Business Unit Master (F0006)
This table contains less detailed
rate information than the Account Ledger Master. You can only set up a single rate for a job based on this table.
3. Rental Rules (F1302)
This
table contains the least detailed rate code information. The system searches this table according to the criteria you establish when setting up
the table. |
cProRateBillingF1302 | PRO | char | REQ | INPUT |
Use this field to specify whether billings are calculated on a hierarchical basis, or are prorated on a monthly basis. The billing program
computes the hierarchical basis based on the lower of the hourly, daily, weekly, or monthly rate. For example, if you bill a piece of equipment to a
job using a weekly rate but use that equipment only three days, you can use the daily rate code associated with that weekly rate code.
The
billing program computes the prorated basis based on the ratio of the number of days that the equipment is used to the total number of
working days in the month. For example, if there are 20 working days in the month and you use a piece of equipment five days, the Location Billing
program charges 25% of the monthly rate.
If you do not specify proration, the system uses monthly, weekly, daily and hourly rate codes to
determine the billing amount. Valid values for this field are:
Y Prorate the monthly rate. You must define the equipment rate code as monthly
N Use Hierarchy until the monthly rate is reached
H Use Hierarchy at all times |
jdDateBeginningEffectiveF1301 | 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.
|
szEquipmentRateCodeF1301 | ERC | char | REQ | INPUT |
A user defined code (00/RC) that indicates a billing rate, such as DY for daily, MO for monthly, and WK for weekly. You can set up multiple
billing rates for a piece of equipment.
If you leave this field blank, the system searches for a valid billing rate in the following sequence:
1.
Account Ledger Master (F0901)
This table contains the most detailed rate information. You can assign multiple rates for a job. For example, you
can set up separate rates for different equipment working conditions.
2. Job or Business Unit Master (F0006)
This table contains less detailed
rate information than the Account Ledger Master. You can only set up a single rate for a job based on this table.
3. Rental Rules (F1302)
This
table contains the least detailed rate code information. The system searches this table according to the criteria you establish when setting up
the table. |
mnBillingRateEquipmentF1301 | EBRT | MATH_NUMERIC | REQ | INPUT |
A code that represents the amount that you want to charge the job. Each piece of equipment can have numerous billing rates based on the
rate code. The equipment billing rate can be composed of up to ten different rates. For example:
Billing Rate = 200
100 Rate 1 (Ownership
Component)
25 Rate 2 (Operating Component)
50 Rate 3 (Maintenance Component)
25 Rate 4 (Other Costs Component)
When
you post time entries to the general ledger, the system recognizes credits in revenue accounts for each of the rate components. This allows
you to separate portions of the equipment billing by type of cost.
Note: You are not required to use rate components. |
jdDateThru_OD1 | OD1 | JDEDATE | REQ | INPUT |
Lot Proceed information field. |
cPOHourFlag_EV01 | EV01 | char | REQ | INPUT |
An option that specifies the type of processing for an event.
|
cPOBillWeekendFlag_EV01 | EV01 | char | REQ | INPUT |
An option that specifies the type of processing for an event.
|
mnAddBillingRateCORT_EBRT | EBRT | MATH_NUMERIC | REQ | INPUT |
A code that represents the amount that you want to charge the job. Each piece of equipment can have numerous billing rates based on the
rate code. The equipment billing rate can be composed of up to ten different rates. For example:
Billing Rate = 200
100 Rate 1 (Ownership
Component)
25 Rate 2 (Operating Component)
50 Rate 3 (Maintenance Component)
25 Rate 4 (Other Costs Component)
When
you post time entries to the general ledger, the system recognizes credits in revenue accounts for each of the rate components. This allows
you to separate portions of the equipment billing by type of cost.
Note: You are not required to use rate components. |
cBeginFlag_ev01 | EV01 | char | OPT | INPUT |
An option that specifies the type of processing for an event.
|
mnDailyBillingRate450_EBRT | EBRT | MATH_NUMERIC | OPT | NONE |
A code that represents the amount that you want to charge the job. Each piece of equipment can have numerous billing rates based on the
rate code. The equipment billing rate can be composed of up to ten different rates. For example:
Billing Rate = 200
100 Rate 1 (Ownership
Component)
25 Rate 2 (Operating Component)
50 Rate 3 (Maintenance Component)
25 Rate 4 (Other Costs Component)
When
you post time entries to the general ledger, the system recognizes credits in revenue accounts for each of the rate components. This allows
you to separate portions of the equipment billing by type of cost.
Note: You are not required to use rate components. |
mnHourlyBillingRate450_EBRT | EBRT | MATH_NUMERIC | OPT | NONE |
A code that represents the amount that you want to charge the job. Each piece of equipment can have numerous billing rates based on the
rate code. The equipment billing rate can be composed of up to ten different rates. For example:
Billing Rate = 200
100 Rate 1 (Ownership
Component)
25 Rate 2 (Operating Component)
50 Rate 3 (Maintenance Component)
25 Rate 4 (Other Costs Component)
When
you post time entries to the general ledger, the system recognizes credits in revenue accounts for each of the rate components. This allows
you to separate portions of the equipment billing by type of cost.
Note: You are not required to use rate components. |
sz1301AddRateGroup | RTGR | char | OPT | INPUT |
A user defined code (12/C0) that identifies groups of similar pieces of equipment that are tied together for billing purposes.
|
mn1301AddAssetNumber | NUMB | MATH_NUMERIC | OPT | INPUT |
An 8-digit number that uniquely identifies an asset.
|
jd1301AddDateBeginEffective | EFTB | JDEDATE | OPT | 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.
|