TimeSheetDataFields (SAP S/4HANA Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject<ObjectT>
- - com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmComplex<TimeSheetDataFields>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.workforcetimesheet.TimeSheetDataFields

public class TimeSheetDataFields
extends VdmComplex<TimeSheetDataFields>

Original complex type name from the Odata EDM: TimeSheetDataFields

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class TimeSheetDataFields.TimeSheetDataFieldsBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`TimeSheetDataFields.TimeSheetDataFieldsBuilder`

Field Summary
- Fields inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
  changedOriginalFields

Constructor Summary

Constructors
Constructor and Description
`TimeSheetDataFields()`
`TimeSheetDataFields(String controllingArea, String senderCostCenter, String receiverCostCenter, String internalOrder, String activityType, String wBSElement, String workItem, String billingControlCategory, String purchaseOrder, String purchaseOrderItem, String timeSheetTaskType, String timeSheetTaskLevel, String timeSheetTaskComponent, String timeSheetNote, BigDecimal recordedHours, BigDecimal recordedQuantity, String hoursUnitOfMeasure, String rejectionReason)`

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`static TimeSheetDataFields.TimeSheetDataFieldsBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`protected void`	`fromMap(Map<String,Object> inputValues)`
`String`	`getActivityType()` Constraints: Not nullable, Maximum length: 6
`String`	`getBillingControlCategory()` Constraints: Not nullable, Maximum length: 8
`String`	`getControllingArea()` Constraints: Not nullable, Maximum length: 4
`String`	`getHoursUnitOfMeasure()` Constraints: Not nullable, Maximum length: 3
`String`	`getInternalOrder()` Constraints: Not nullable, Maximum length: 12
`protected Map<String,Object>`	`getKey()`
`String`	`getPurchaseOrder()` Constraints: Not nullable, Maximum length: 10
`String`	`getPurchaseOrderItem()` Constraints: Not nullable, Maximum length: 5
`String`	`getReceiverCostCenter()` Constraints: Not nullable, Maximum length: 10
`BigDecimal`	`getRecordedHours()` Constraints: Not nullable, Precision: 4, Scale: 2
`BigDecimal`	`getRecordedQuantity()` Constraints: Not nullable, Precision: 15, Scale: 3
`String`	`getRejectionReason()` Constraints: Not nullable, Maximum length: 4
`String`	`getSenderCostCenter()` Constraints: Not nullable, Maximum length: 10
`String`	`getTimeSheetNote()` Constraints: Not nullable
`String`	`getTimeSheetTaskComponent()` Constraints: Not nullable, Maximum length: 8
`String`	`getTimeSheetTaskLevel()` Constraints: Not nullable, Maximum length: 8
`String`	`getTimeSheetTaskType()` Constraints: Not nullable, Maximum length: 4
`Class<TimeSheetDataFields>`	`getType()`
`String`	`getWBSElement()` Constraints: Not nullable, Maximum length: 24
`String`	`getWorkItem()` Constraints: Not nullable, Maximum length: 10
`int`	`hashCode()`
`void`	`setActivityType(String activityType)` Constraints: Not nullable, Maximum length: 6
`void`	`setBillingControlCategory(String billingControlCategory)` Constraints: Not nullable, Maximum length: 8
`void`	`setControllingArea(String controllingArea)` Constraints: Not nullable, Maximum length: 4
`void`	`setHoursUnitOfMeasure(String hoursUnitOfMeasure)` Constraints: Not nullable, Maximum length: 3
`void`	`setInternalOrder(String internalOrder)` Constraints: Not nullable, Maximum length: 12
`void`	`setPurchaseOrder(String purchaseOrder)` Constraints: Not nullable, Maximum length: 10
`void`	`setPurchaseOrderItem(String purchaseOrderItem)` Constraints: Not nullable, Maximum length: 5
`void`	`setReceiverCostCenter(String receiverCostCenter)` Constraints: Not nullable, Maximum length: 10
`void`	`setRecordedHours(BigDecimal recordedHours)` Constraints: Not nullable, Precision: 4, Scale: 2
`void`	`setRecordedQuantity(BigDecimal recordedQuantity)` Constraints: Not nullable, Precision: 15, Scale: 3
`void`	`setRejectionReason(String rejectionReason)` Constraints: Not nullable, Maximum length: 4
`void`	`setSenderCostCenter(String senderCostCenter)` Constraints: Not nullable, Maximum length: 10
`void`	`setTimeSheetNote(String timeSheetNote)` Constraints: Not nullable
`void`	`setTimeSheetTaskComponent(String timeSheetTaskComponent)` Constraints: Not nullable, Maximum length: 8
`void`	`setTimeSheetTaskLevel(String timeSheetTaskLevel)` Constraints: Not nullable, Maximum length: 8
`void`	`setTimeSheetTaskType(String timeSheetTaskType)` Constraints: Not nullable, Maximum length: 4
`void`	`setWBSElement(String wBSElement)` Constraints: Not nullable, Maximum length: 24
`void`	`setWorkItem(String workItem)` Constraints: Not nullable, Maximum length: 10
`protected Map<String,Object>`	`toMapOfFields()`
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties

Methods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, wait

- Constructor Detail
  - TimeSheetDataFields
```
public TimeSheetDataFields()
```
  - TimeSheetDataFields
```
public TimeSheetDataFields(@Nullable
                           String controllingArea,
                           @Nullable
                           String senderCostCenter,
                           @Nullable
                           String receiverCostCenter,
                           @Nullable
                           String internalOrder,
                           @Nullable
                           String activityType,
                           @Nullable
                           String wBSElement,
                           @Nullable
                           String workItem,
                           @Nullable
                           String billingControlCategory,
                           @Nullable
                           String purchaseOrder,
                           @Nullable
                           String purchaseOrderItem,
                           @Nullable
                           String timeSheetTaskType,
                           @Nullable
                           String timeSheetTaskLevel,
                           @Nullable
                           String timeSheetTaskComponent,
                           @Nullable
                           String timeSheetNote,
                           @Nullable
                           BigDecimal recordedHours,
                           @Nullable
                           BigDecimal recordedQuantity,
                           @Nullable
                           String hoursUnitOfMeasure,
                           @Nullable
                           String rejectionReason)
```
- Method Detail
  - getType
```
@Nonnull
public Class<TimeSheetDataFields> getType()
```
    Specified by:
    
    getType in class VdmObject<TimeSheetDataFields>
    
    Returns:
    
    The class of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<TimeSheetDataFields>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<TimeSheetDataFields>
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<TimeSheetDataFields>
    
    Returns:
    
    The compound key of this object.
  - builder
```
public static TimeSheetDataFields.TimeSheetDataFieldsBuilder builder()
```
  - getControllingArea
```
@Nullable
public String getControllingArea()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: ControllingArea
    
    The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
    
    Returns:
    
    Uniquely identifies a controlling area.
  - getSenderCostCenter
```
@Nullable
public String getSenderCostCenter()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: SenderCostCenter
    
    Returns:
    
    Identifies the cost center you selected as the sender object.
  - getReceiverCostCenter
```
@Nullable
public String getReceiverCostCenter()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: ReceiverCostCenter
    
    Returns:
    
    Key specifically identifying the cost center selected as the receiver object.
  - getInternalOrder
```
@Nullable
public String getInternalOrder()
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: InternalOrder
    
    Returns:
    
    Key specifically identifying the order selected as the receiver object.
  - getActivityType
```
@Nullable
public String getActivityType()
```
    Constraints: Not nullable, Maximum length: 6
    Original property from the Odata EDM: ActivityType
    
    Activity types describe the activity produced by a cost center and are measured in units of time or quantity.In activity type planning, control data determines whether the activity price for evaluation of the activity type is manually set or is derived iteratively through activity price calculation.
    
    Returns:
    
    Key uniquely identifying .
  - getWBSElement
```
@Nullable
public String getWBSElement()
```
    Constraints: Not nullable, Maximum length: 24
    Original property from the Odata EDM: WBSElement
    
    Returns:
    
    Key identifying a WBS element.
  - getWorkItem
```
@Nullable
public String getWorkItem()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: WorkItem
    
    Returns:
    
    Work Item ID
  - getBillingControlCategory
```
@Nullable
public String getBillingControlCategory()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: BillingControlCategory
    
    Returns:
    
    Billing Control Category
  - getPurchaseOrder
```
@Nullable
public String getPurchaseOrder()
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: PurchaseOrder
    
    Returns:
    
    Specifies an alphanumeric key that uniquely identifies the Sender purchase order.
  - getPurchaseOrderItem
```
@Nullable
public String getPurchaseOrderItem()
```
    Constraints: Not nullable, Maximum length: 5
    Original property from the Odata EDM: PurchaseOrderItem
    
    Returns:
    
    Specifies a number that uniquely identifies the item within the purchasing document.
  - getTimeSheetTaskType
```
@Nullable
public String getTimeSheetTaskType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: TimeSheetTaskType
    
    In the Cross-Application Time Sheet (SAP CATS), the task type, task component, and task level fields enable you to specify the task elements that are relevant for valuation. For example, elements that are relevant for valuation are entered for the following business processes:Payroll (wage types, attendance types)Controlling and billing (activity types, statistical key figures)Invoice verification for external employees (activity numbers)The SAP R/3 system can derive the following working time attributes from the combination of task types, components, and levels:Attendance/absence typesWage typesActivity typesStatistical key figuresActivity numbersSender business processesYou can replace these input fields on your time sheet user interface with the task type, task component, and task level input fields, which are tailored to suit task recording needs. You can also valuate the task type, component, and level in reporting.You can make the relevant settings in the Implementation Guide (IMG), under Cross-Application Components -> Time Sheet-> Time Recording -> Task Levels, Components, and Categories.ExampleAt a consultancy, employees record their tasks. The data recorded is then used for creating invoices.Task type: consultingTask components for consulting: working hours, overtime, number of kilometers drivenTask levels for consulting: junior, seniorThe SAP R/3 system valuates the "overtime" task component for the "junior" task level with a specific activity type. The SAP R/3 system valuates the "overtime" task component for the "senior" task level with a different activity type with a higher price.
    
    Returns:
    
    Characterisation of content of a specific task that an employee performs, for example "consulting" or "instructor function". Specific task components are usual for each task type.
  - getTimeSheetTaskLevel
```
@Nullable
public String getTimeSheetTaskLevel()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: TimeSheetTaskLevel
    
    Specific task levels are allowed for each task type. The task levels determine the valuation level for each task component.In the Cross-Application Time Sheet (SAP CATS), the task type, task component, and task level fields enable you to specify the task elements that are relevant for valuation. For example, elements that are relevant for valuation are entered for the following business processes:Payroll (wage types, attendance types)Controlling and billing (activity types, statistical key figures)Invoice verification for external employees (activity numbers)The SAP R/3 system can derive the following working time attributes from the combination of task types, components, and levels:Attendance/absence typesWage typesActivity typesStatistical key figuresActivity numbersSender business processesYou can replace these input fields on your time sheet user interface with the task type, task component, and task level input fields, which are tailored to suit task recording needs. You can also valuate the task type, component, and level in reporting.You can make the relevant settings in the Implementation Guide (IMG), under Cross-Application Components -> Time Sheet-> Time Recording -> Task Levels, Components, and Categories.ExampleAt a consultancy, employees record their tasks. The data recorded is then used for creating invoices.Task type: consultingTask components for consulting: working hours, overtime, number of kilometers drivenTask levels for consulting: junior, seniorThe SAP R/3 system valuates the "overtime" task component for the "junior" task level with a specific activity type. The SAP R/3 system valuates the "overtime" task component for the "senior" task level with a different activity type with a higher price.
    
    Returns:
    
    Differentiation between an employee's tasks depending on the level of valuation.
  - getTimeSheetTaskComponent
```
@Nullable
public String getTimeSheetTaskComponent()
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: TimeSheetTaskComponent
    
    A task generally comprises more than one task component, for example, normal working hours, overtime, or travel hours. Specific task components are usual for each task type.In the Cross-Application Time Sheet (SAP CATS), the task type, task component, and task level fields enable you to specify the task elements that are relevant for valuation. For example, elements that are relevant for valuation are entered for the following business processes:Payroll (wage types, attendance types)Controlling and billing (activity types, statistical key figures)Invoice verification for external employees (activity numbers)The SAP R/3 system can derive the following working time attributes from the combination of task types, components, and levels:Attendance/absence typesWage typesActivity typesStatistical key figuresActivity numbersSender business processesYou can replace these input fields on your time sheet user interface with the task type, task component, and task level input fields, which are tailored to suit task recording needs. You can also valuate the task type, component, and level in reporting.You can make the relevant settings in the Implementation Guide (IMG), under Cross-Application Components -> Time Sheet-> Time Recording -> Task Levels, Components, and Categories.ExampleAt a consultancy, employees record their tasks. The data recorded is then used for creating invoices.Task type: consultingTask components for consulting: working hours, overtime, number of kilometers drivenTask levels for consulting: junior, seniorThe SAP R/3 system valuates the "overtime" task component for the "junior" task level with a specific activity type. The SAP R/3 system valuates the "overtime" task component for the "senior" task level with a different activity type with a higher price.
    
    Returns:
    
    Task element that is relevant for valuation.
  - getTimeSheetNote
```
@Nullable
public String getTimeSheetNote()
```
    Constraints: Not nullable
    Original property from the Odata EDM: TimeSheetNote
    
    Returns:
    
    Time Sheet Note
  - getRecordedHours
```
@Nullable
public BigDecimal getRecordedHours()
```
    Constraints: Not nullable, Precision: 4, Scale: 2
    Original property from the Odata EDM: RecordedHours
    
    When you maintain the time sheet, one data record is stored for each entry you make in the Hours field - that is, per day and account assignment (order number, attendance/absence type, purchase order number).
    
    Returns:
    
    The duration of an activity or absence in hours.
  - getRecordedQuantity
```
@Nullable
public BigDecimal getRecordedQuantity()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property from the Odata EDM: RecordedQuantity
    
    Returns:
    
    Specifies the number of units entered for the unit of measure.
  - getHoursUnitOfMeasure
```
@Nullable
public String getHoursUnitOfMeasure()
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: HoursUnitOfMeasure
    
    Returns:
    
    Specifies the unit of measure in which the quantity represented is displayed.
  - getRejectionReason
```
@Nullable
public String getRejectionReason()
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: RejectionReason
    
    Returns:
    
    Comment line that can go back to the person who entered the data when an approval is rejected.
  - setControllingArea
```
public void setControllingArea(@Nullable
                               String controllingArea)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: ControllingArea
    
    The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
    
    Parameters:
    
    controllingArea -
  - setSenderCostCenter
```
public void setSenderCostCenter(@Nullable
                                String senderCostCenter)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: SenderCostCenter
    
    Parameters:
    
    senderCostCenter -
  - setReceiverCostCenter
```
public void setReceiverCostCenter(@Nullable
                                  String receiverCostCenter)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: ReceiverCostCenter
    
    Parameters:
    
    receiverCostCenter -
  - setInternalOrder
```
public void setInternalOrder(@Nullable
                             String internalOrder)
```
    Constraints: Not nullable, Maximum length: 12
    Original property from the Odata EDM: InternalOrder
    
    Parameters:
    
    internalOrder -
  - setActivityType
```
public void setActivityType(@Nullable
                            String activityType)
```
    Constraints: Not nullable, Maximum length: 6
    Original property from the Odata EDM: ActivityType
    
    Activity types describe the activity produced by a cost center and are measured in units of time or quantity.In activity type planning, control data determines whether the activity price for evaluation of the activity type is manually set or is derived iteratively through activity price calculation.
    
    Parameters:
    
    activityType -
  - setWBSElement
```
public void setWBSElement(@Nullable
                          String wBSElement)
```
    Constraints: Not nullable, Maximum length: 24
    Original property from the Odata EDM: WBSElement
    
    Parameters:
    
    wBSElement -
  - setWorkItem
```
public void setWorkItem(@Nullable
                        String workItem)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: WorkItem
    
    Parameters:
    
    workItem -
  - setBillingControlCategory
```
public void setBillingControlCategory(@Nullable
                                      String billingControlCategory)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: BillingControlCategory
    
    Parameters:
    
    billingControlCategory -
  - setPurchaseOrder
```
public void setPurchaseOrder(@Nullable
                             String purchaseOrder)
```
    Constraints: Not nullable, Maximum length: 10
    Original property from the Odata EDM: PurchaseOrder
    
    Parameters:
    
    purchaseOrder -
  - setPurchaseOrderItem
```
public void setPurchaseOrderItem(@Nullable
                                 String purchaseOrderItem)
```
    Constraints: Not nullable, Maximum length: 5
    Original property from the Odata EDM: PurchaseOrderItem
    
    Parameters:
    
    purchaseOrderItem -
  - setTimeSheetTaskType
```
public void setTimeSheetTaskType(@Nullable
                                 String timeSheetTaskType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: TimeSheetTaskType
    
    In the Cross-Application Time Sheet (SAP CATS), the task type, task component, and task level fields enable you to specify the task elements that are relevant for valuation. For example, elements that are relevant for valuation are entered for the following business processes:Payroll (wage types, attendance types)Controlling and billing (activity types, statistical key figures)Invoice verification for external employees (activity numbers)The SAP R/3 system can derive the following working time attributes from the combination of task types, components, and levels:Attendance/absence typesWage typesActivity typesStatistical key figuresActivity numbersSender business processesYou can replace these input fields on your time sheet user interface with the task type, task component, and task level input fields, which are tailored to suit task recording needs. You can also valuate the task type, component, and level in reporting.You can make the relevant settings in the Implementation Guide (IMG), under Cross-Application Components -> Time Sheet-> Time Recording -> Task Levels, Components, and Categories.ExampleAt a consultancy, employees record their tasks. The data recorded is then used for creating invoices.Task type: consultingTask components for consulting: working hours, overtime, number of kilometers drivenTask levels for consulting: junior, seniorThe SAP R/3 system valuates the "overtime" task component for the "junior" task level with a specific activity type. The SAP R/3 system valuates the "overtime" task component for the "senior" task level with a different activity type with a higher price.
    
    Parameters:
    
    timeSheetTaskType - "instructor function". Specific task components are usual for each task type.
  - setTimeSheetTaskLevel
```
public void setTimeSheetTaskLevel(@Nullable
                                  String timeSheetTaskLevel)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: TimeSheetTaskLevel
    
    Specific task levels are allowed for each task type. The task levels determine the valuation level for each task component.In the Cross-Application Time Sheet (SAP CATS), the task type, task component, and task level fields enable you to specify the task elements that are relevant for valuation. For example, elements that are relevant for valuation are entered for the following business processes:Payroll (wage types, attendance types)Controlling and billing (activity types, statistical key figures)Invoice verification for external employees (activity numbers)The SAP R/3 system can derive the following working time attributes from the combination of task types, components, and levels:Attendance/absence typesWage typesActivity typesStatistical key figuresActivity numbersSender business processesYou can replace these input fields on your time sheet user interface with the task type, task component, and task level input fields, which are tailored to suit task recording needs. You can also valuate the task type, component, and level in reporting.You can make the relevant settings in the Implementation Guide (IMG), under Cross-Application Components -> Time Sheet-> Time Recording -> Task Levels, Components, and Categories.ExampleAt a consultancy, employees record their tasks. The data recorded is then used for creating invoices.Task type: consultingTask components for consulting: working hours, overtime, number of kilometers drivenTask levels for consulting: junior, seniorThe SAP R/3 system valuates the "overtime" task component for the "junior" task level with a specific activity type. The SAP R/3 system valuates the "overtime" task component for the "senior" task level with a different activity type with a higher price.
    
    Parameters:
    
    timeSheetTaskLevel -
  - setTimeSheetTaskComponent
```
public void setTimeSheetTaskComponent(@Nullable
                                      String timeSheetTaskComponent)
```
    Constraints: Not nullable, Maximum length: 8
    Original property from the Odata EDM: TimeSheetTaskComponent
    
    A task generally comprises more than one task component, for example, normal working hours, overtime, or travel hours. Specific task components are usual for each task type.In the Cross-Application Time Sheet (SAP CATS), the task type, task component, and task level fields enable you to specify the task elements that are relevant for valuation. For example, elements that are relevant for valuation are entered for the following business processes:Payroll (wage types, attendance types)Controlling and billing (activity types, statistical key figures)Invoice verification for external employees (activity numbers)The SAP R/3 system can derive the following working time attributes from the combination of task types, components, and levels:Attendance/absence typesWage typesActivity typesStatistical key figuresActivity numbersSender business processesYou can replace these input fields on your time sheet user interface with the task type, task component, and task level input fields, which are tailored to suit task recording needs. You can also valuate the task type, component, and level in reporting.You can make the relevant settings in the Implementation Guide (IMG), under Cross-Application Components -> Time Sheet-> Time Recording -> Task Levels, Components, and Categories.ExampleAt a consultancy, employees record their tasks. The data recorded is then used for creating invoices.Task type: consultingTask components for consulting: working hours, overtime, number of kilometers drivenTask levels for consulting: junior, seniorThe SAP R/3 system valuates the "overtime" task component for the "junior" task level with a specific activity type. The SAP R/3 system valuates the "overtime" task component for the "senior" task level with a different activity type with a higher price.
    
    Parameters:
    
    timeSheetTaskComponent -
  - setTimeSheetNote
```
public void setTimeSheetNote(@Nullable
                             String timeSheetNote)
```
    Constraints: Not nullable
    Original property from the Odata EDM: TimeSheetNote
    
    Parameters:
    
    timeSheetNote -
  - setRecordedHours
```
public void setRecordedHours(@Nullable
                             BigDecimal recordedHours)
```
    Constraints: Not nullable, Precision: 4, Scale: 2
    Original property from the Odata EDM: RecordedHours
    
    When you maintain the time sheet, one data record is stored for each entry you make in the Hours field - that is, per day and account assignment (order number, attendance/absence type, purchase order number).
    
    Parameters:
    
    recordedHours -
  - setRecordedQuantity
```
public void setRecordedQuantity(@Nullable
                                BigDecimal recordedQuantity)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    Original property from the Odata EDM: RecordedQuantity
    
    Parameters:
    
    recordedQuantity -
  - setHoursUnitOfMeasure
```
public void setHoursUnitOfMeasure(@Nullable
                                  String hoursUnitOfMeasure)
```
    Constraints: Not nullable, Maximum length: 3
    Original property from the Odata EDM: HoursUnitOfMeasure
    
    Parameters:
    
    hoursUnitOfMeasure -
  - setRejectionReason
```
public void setRejectionReason(@Nullable
                               String rejectionReason)
```
    Constraints: Not nullable, Maximum length: 4
    Original property from the Odata EDM: RejectionReason
    
    Parameters:
    
    rejectionReason -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<TimeSheetDataFields>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<TimeSheetDataFields>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<TimeSheetDataFields>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<TimeSheetDataFields>

Class TimeSheetDataFields

Nested Class Summary

Field Summary

Fields inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Constructor Detail

TimeSheetDataFields

TimeSheetDataFields

Method Detail

getType

toMapOfFields

fromMap

getKey

builder

getControllingArea

getSenderCostCenter

getReceiverCostCenter

getInternalOrder

getActivityType

getWBSElement

getWorkItem

getBillingControlCategory

getPurchaseOrder

getPurchaseOrderItem

getTimeSheetTaskType

getTimeSheetTaskLevel

getTimeSheetTaskComponent

getTimeSheetNote

getRecordedHours

getRecordedQuantity

getHoursUnitOfMeasure

getRejectionReason

setControllingArea

setSenderCostCenter

setReceiverCostCenter

setInternalOrder

setActivityType

setWBSElement

setWorkItem

setBillingControlCategory

setPurchaseOrder

setPurchaseOrderItem

setTimeSheetTaskType

setTimeSheetTaskLevel

setTimeSheetTaskComponent

setTimeSheetNote

setRecordedHours

setRecordedQuantity

setHoursUnitOfMeasure

setRejectionReason

toString

equals

canEqual

hashCode