Skip to main content
Skip table of contents

Data Conversion Support to Create Labor Pricing for Custom Units in Pricing Conversion

Reference No: R2-10343

Version No: 06.00.06-00

Details

The Data Conversion support to create pricing for labor using a custom units in Pricing Conversion for both Item Pricing and Multi-Currency Item Pricing, has been provided.

Following rows in the Table 15.0 in Section Item Pricing, have been modified.

Column Name

Data Type

Description

Default Value

Mandatory

 Unit

Varchar2(20)

In case of Item Pricing:

  • Unit is a mandatory field. And the possible values for this field are: Weekly, Daily, AM/PM, Hourly, Half Hourly, Qt. Hourly, Minute, Second, Each, Monthly, Regular, OT, and DT.

  • CustomUnit is a Hard Coded field in the system’s backend. Whether we provide a value or not, in either case the system will consider it as NULL.

In case of Labor Pricing:

  •  This field becomes a binary choice field between Unit and CustomUnit option. And the possible values for this field are: Hourly, Regular, OT, and DT.

  • If the CustomUnit Value is Non-Blank, the required value is fetched from PayPolicy Unit defined in R2Labor.

The four possible binary combinations are:  

  • If, Unit = ‘Some Value’ and CustomUnit=Blank, then System Will Allow.

  • If, Unit = ‘Blank’ and CustomUnit= ‘Some Value’, then System Will Allow.

  • If, Unit = ‘Some Value’ and CustomUnit=Some Value, then System Will NOT Allow.

  • If, Unit = ‘Blank’ and CustomUnit=Blank, then System Will NOT Allow.

For Labor: Either CustomUnit or Unit will be Null

For Item: Yes

For Labor: Either CustomUnit or Unit

Minprice

Number(11,2)

For Item Pricing: This field is an optional. Thus as the name suggests, If Minprice > price then system will not allow.

For Labor pricing: This Field is not mandatory. And if we give the MinPrice system will accept as Null.

NULL

 

Custom Unit

Varchar2(100)

In case of Item Pricing:

  • This Field is not mandatory. Whether CustomUnit = ‘Some Value’ or CustomUnit = ‘Blank, in either case System Will Allow.

In case of Labor Pricing :

  • This field becomes a binary choice field between Unit and CustomUnit option.

  • If the  CustomUnit Value is Non-Blank, the required value is fetched from PayPolicy Unit defined in R2Labor.

The four possible binary combinations are:

  • If, Unit = ‘Some Value’ and CustomUnit=Blank, then System Will Allow.

  • If, Unit = ‘Blank’ and CustomUnit= ‘Some Value’, then System Will Allow.

  • If, Unit = ‘Some Value’ and CustomUnit=Some Value, then System Will NOT Allow.

  • If, Unit = ‘Blank’ and CustomUnit=Blank, then System Will NOT Allow.

For Item: Always Null

For Labor: Either CustomUnit or Unit will be Null

For Item: No

For Labor: Either CustomUnit or Unit

For more details, refer Table 29.0 in Section Multi-Currency Item Pricing in DataConversion.doc available in ..\sqls\DataConverter folder.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.