F1304CalculateWeeklyBilling

F1304 Hierarchical Weekly Billings

Minor Business Rule

Object Name: N1300510

Parent DLL: CMFG

Location: Client/Server

Language: NER

Data Structure

D1300510 - F1304 Hierarchical Weekly Billings

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szEquipmentRateCode1204	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.
szCompanyF1302	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.
szCostCenterLocationF1302	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).
szEquipmentRateTableAdd	RTTB	char	OPT	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	REQ	OUTPUT
The number of hours billed.
mnAmountCurrentBilling1304	CBAM	MATH_NUMERIC	REQ	OUTPUT
The amount of the current billing.
mnAmountTotalBilled1304	TTBL	MATH_NUMERIC	REQ	BOTH
The total amount billed.
mnDelimitedBillingTotal1304	DBTT	MATH_NUMERIC	REQ	BOTH
The billing total for a piece of equipment as of the last billing.
jdDateBeginningEffectiveAdd	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.
mnTimeBeginningDefault1302	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.
mnTimeEndingDefault1302	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.
mnQuantity1204	QTY	MATH_NUMERIC	REQ	INPUT
The number of units associated with an asset.
mnDaysBilled1304	DYBL	MATH_NUMERIC	REQ	OUTPUT
The number of days billed.
cFirstTimeFlag	EV01	char	REQ	INPUT
An option that specifies the type of processing for an event.
cContinuousFlag	EV02	char	REQ	INPUT
An option that specifies the type of processing for an event.
jdDateField1	DATE1	JDEDATE	REQ	INPUT
A field to store user-defined information in a date format.
jdDateBeginningEffective1301	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.
szEquipmentRateCode1301	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.
mnBillingRateEquipment1301	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.
mnTimeStampBeginning1204	DDTS	MATH_NUMERIC	REQ	INPUT
The time that the asset is transferred to a new location.
mnTimeStampEnding1204	DTSO	MATH_NUMERIC	REQ	INPUT
The time that the asset was transferred from the job or will no longer be at a specified location.
jdDelimitedDateTsF1304	DDTE	JDEDATE	REQ	BOTH
The date/time that the last billing was billed through.
mnPercent01	PCT	MATH_NUMERIC	REQ	INPUT
An abbreviation for percentage.
jdDateBeginningEffective1204	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.
jdThruDate	END	JDEDATE	REQ	INPUT
The date when an asset was removed or returned from a particular location.
jdDateEnding1204	END	JDEDATE	REQ	INPUT
The date when an asset was removed or returned from a particular location.
cPHour	EV03	char	REQ	INPUT
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.
mnCort	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.
szEquipRateCodeDaily1390	ERCD	char	REQ	INPUT
For Location Billing clients only. This code is an equipment rate code (system 00, type RC) that is associated with a daily billing rate. It allows you to set up a hierarchy of billing rates within the daily rate code. For example,your billing rate code hierarchy for a daily rate will be hourly and daily.
szEquipmentRateTable1301	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.
szEquipmentRateGroup1301	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.
mnAssetItemNumber1301	NUMB	MATH_NUMERIC	REQ	INPUT
An 8-digit number that uniquely identifies an asset.
jdDateRetirementDateF1301	RTDT	JDEDATE	REQ	INPUT
The date on which the participant retired, if applicable.
jdDateEndingEffective1301	EFTE	JDEDATE	REQ	INPUT
The date on which the item, transaction, or table becomes inactive, or through which you want transactions to appear. This field is used generically throughout the system. It could be a lease effective date, a price or cost effective date, a currency effective date, a tax rate effective date, or whatever is appropriate.
cBillWeekends	WKEN	char	REQ	INPUT
A Yes/No field that indicates whether weekends are billable days or non-billable days for a specific location.
szAdditionalRateTable	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.
mnWeeksBilledF1304	WKBL	MATH_NUMERIC	REQ	OUTPUT
The number of weeks 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.
mnAssetItemNumber1304	NUMB	MATH_NUMERIC	REQ	INPUT
An 8-digit number that uniquely identifies an asset.
szCostCenterLocation1304	LOC	char	REQ	BOTH
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).
szEquipmentRateGroupAdd	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.
mnAssetItemNumberAdd	NUMB	MATH_NUMERIC	OPT	INPUT
An 8-digit number that uniquely identifies an asset.
mnHourlyBillingRate510_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.
mnDailyBillingRate510_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.
mnWeeklyBillingRate510_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.
mnMonthlyBillingRate510_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.
mnMonthsBilled	MNBL	MATH_NUMERIC	OPT	NONE
The number of months billed.

Related Functions

None

Related Tables

None