public class TimeSheetDataFields extends VdmComplex<TimeSheetDataFields>
Original complex type name from the Odata EDM: TimeSheetDataFields
Modifier and Type | Class and Description |
---|---|
static class |
TimeSheetDataFields.TimeSheetDataFieldsBuilder |
changedOriginalFields
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) |
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 Original property from the Odata EDM: ActivityTypeActivity 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.
|
String |
getBillingControlCategory()
Constraints: Not nullable, Maximum length: 8 Original property from the Odata EDM: BillingControlCategory
|
String |
getControllingArea()
Constraints: Not nullable, Maximum length: 4 Original property from the Odata EDM: ControllingAreaThe 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.
|
String |
getHoursUnitOfMeasure()
Constraints: Not nullable, Maximum length: 3 Original property from the Odata EDM: HoursUnitOfMeasure
|
String |
getInternalOrder()
Constraints: Not nullable, Maximum length: 12 Original property from the Odata EDM: InternalOrder
|
protected Map<String,Object> |
getKey() |
String |
getPurchaseOrder()
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: PurchaseOrder
|
String |
getPurchaseOrderItem()
Constraints: Not nullable, Maximum length: 5 Original property from the Odata EDM: PurchaseOrderItem
|
String |
getReceiverCostCenter()
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: ReceiverCostCenter
|
BigDecimal |
getRecordedHours()
Constraints: Not nullable, Precision: 4, Scale: 2 Original property from the Odata EDM: RecordedHoursWhen 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).
|
BigDecimal |
getRecordedQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3 Original property from the Odata EDM: RecordedQuantity
|
String |
getRejectionReason()
Constraints: Not nullable, Maximum length: 4 Original property from the Odata EDM: RejectionReason
|
String |
getSenderCostCenter()
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: SenderCostCenter
|
String |
getTimeSheetNote()
Constraints: Not nullableOriginal property from the Odata EDM: TimeSheetNote
|
String |
getTimeSheetTaskComponent()
Constraints: Not nullable, Maximum length: 8 Original property from the Odata EDM: TimeSheetTaskComponentA task generally comprises more than one task component, for example, normal working hours, overtime, or travel hours.
|
String |
getTimeSheetTaskLevel()
Constraints: Not nullable, Maximum length: 8 Original property from the Odata EDM: TimeSheetTaskLevelSpecific task levels are allowed for each task type.
|
String |
getTimeSheetTaskType()
Constraints: Not nullable, Maximum length: 4 Original property from the Odata EDM: TimeSheetTaskTypeIn 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.
|
Class<TimeSheetDataFields> |
getType() |
String |
getWBSElement()
Constraints: Not nullable, Maximum length: 24 Original property from the Odata EDM: WBSElement
|
String |
getWorkItem()
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: WorkItem
|
int |
hashCode() |
void |
setActivityType(String activityType)
Constraints: Not nullable, Maximum length: 6 Original property from the Odata EDM: ActivityTypeActivity 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.
|
void |
setBillingControlCategory(String billingControlCategory)
Constraints: Not nullable, Maximum length: 8 Original property from the Odata EDM: BillingControlCategory
|
void |
setControllingArea(String controllingArea)
Constraints: Not nullable, Maximum length: 4 Original property from the Odata EDM: ControllingAreaThe 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.
|
void |
setHoursUnitOfMeasure(String hoursUnitOfMeasure)
Constraints: Not nullable, Maximum length: 3 Original property from the Odata EDM: HoursUnitOfMeasure
|
void |
setInternalOrder(String internalOrder)
Constraints: Not nullable, Maximum length: 12 Original property from the Odata EDM: InternalOrder
|
void |
setPurchaseOrder(String purchaseOrder)
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: PurchaseOrder
|
void |
setPurchaseOrderItem(String purchaseOrderItem)
Constraints: Not nullable, Maximum length: 5 Original property from the Odata EDM: PurchaseOrderItem
|
void |
setReceiverCostCenter(String receiverCostCenter)
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: ReceiverCostCenter
|
void |
setRecordedHours(BigDecimal recordedHours)
Constraints: Not nullable, Precision: 4, Scale: 2 Original property from the Odata EDM: RecordedHoursWhen 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).
|
void |
setRecordedQuantity(BigDecimal recordedQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3 Original property from the Odata EDM: RecordedQuantity
|
void |
setRejectionReason(String rejectionReason)
Constraints: Not nullable, Maximum length: 4 Original property from the Odata EDM: RejectionReason
|
void |
setSenderCostCenter(String senderCostCenter)
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: SenderCostCenter
|
void |
setTimeSheetNote(String timeSheetNote)
Constraints: Not nullableOriginal property from the Odata EDM: TimeSheetNote
|
void |
setTimeSheetTaskComponent(String timeSheetTaskComponent)
Constraints: Not nullable, Maximum length: 8 Original property from the Odata EDM: TimeSheetTaskComponentA task generally comprises more than one task component, for example, normal working hours, overtime, or travel hours.
|
void |
setTimeSheetTaskLevel(String timeSheetTaskLevel)
Constraints: Not nullable, Maximum length: 8 Original property from the Odata EDM: TimeSheetTaskLevelSpecific task levels are allowed for each task type.
|
void |
setTimeSheetTaskType(String timeSheetTaskType)
Constraints: Not nullable, Maximum length: 4 Original property from the Odata EDM: TimeSheetTaskTypeIn 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.
|
void |
setWBSElement(String wBSElement)
Constraints: Not nullable, Maximum length: 24 Original property from the Odata EDM: WBSElement
|
void |
setWorkItem(String workItem)
Constraints: Not nullable, Maximum length: 10 Original property from the Odata EDM: WorkItem
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public 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)
public Class<TimeSheetDataFields> getType()
getType
in class VdmObject<TimeSheetDataFields>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<TimeSheetDataFields>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<TimeSheetDataFields>
protected Map<String,Object> getKey()
getKey
in class VdmObject<TimeSheetDataFields>
public static TimeSheetDataFields.TimeSheetDataFieldsBuilder builder()
@Nullable public String getControllingArea()
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.
@Nullable public String getSenderCostCenter()
Original property from the Odata EDM: SenderCostCenter
@Nullable public String getReceiverCostCenter()
Original property from the Odata EDM: ReceiverCostCenter
@Nullable public String getInternalOrder()
Original property from the Odata EDM: InternalOrder
@Nullable public String getActivityType()
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.
@Nullable public String getWBSElement()
Original property from the Odata EDM: WBSElement
@Nullable public String getWorkItem()
Original property from the Odata EDM: WorkItem
@Nullable public String getBillingControlCategory()
Original property from the Odata EDM: BillingControlCategory
@Nullable public String getPurchaseOrder()
Original property from the Odata EDM: PurchaseOrder
@Nullable public String getPurchaseOrderItem()
Original property from the Odata EDM: PurchaseOrderItem
@Nullable public String getTimeSheetTaskType()
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.
@Nullable public String getTimeSheetTaskLevel()
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.
@Nullable public String getTimeSheetTaskComponent()
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.
@Nullable public String getTimeSheetNote()
Original property from the Odata EDM: TimeSheetNote
@Nullable public BigDecimal getRecordedHours()
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).
@Nullable public BigDecimal getRecordedQuantity()
Original property from the Odata EDM: RecordedQuantity
@Nullable public String getHoursUnitOfMeasure()
Original property from the Odata EDM: HoursUnitOfMeasure
@Nullable public String getRejectionReason()
Original property from the Odata EDM: RejectionReason
public void setControllingArea(@Nullable String controllingArea)
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.
controllingArea
- public void setSenderCostCenter(@Nullable String senderCostCenter)
Original property from the Odata EDM: SenderCostCenter
senderCostCenter
- public void setReceiverCostCenter(@Nullable String receiverCostCenter)
Original property from the Odata EDM: ReceiverCostCenter
receiverCostCenter
- public void setInternalOrder(@Nullable String internalOrder)
Original property from the Odata EDM: InternalOrder
internalOrder
- public void setActivityType(@Nullable String activityType)
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.
activityType
- public void setWBSElement(@Nullable String wBSElement)
Original property from the Odata EDM: WBSElement
wBSElement
- public void setWorkItem(@Nullable String workItem)
Original property from the Odata EDM: WorkItem
workItem
- public void setBillingControlCategory(@Nullable String billingControlCategory)
Original property from the Odata EDM: BillingControlCategory
billingControlCategory
- public void setPurchaseOrder(@Nullable String purchaseOrder)
Original property from the Odata EDM: PurchaseOrder
purchaseOrder
- public void setPurchaseOrderItem(@Nullable String purchaseOrderItem)
Original property from the Odata EDM: PurchaseOrderItem
purchaseOrderItem
- public void setTimeSheetTaskType(@Nullable String timeSheetTaskType)
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.
timeSheetTaskType
- public void setTimeSheetTaskLevel(@Nullable String timeSheetTaskLevel)
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.
timeSheetTaskLevel
- public void setTimeSheetTaskComponent(@Nullable String timeSheetTaskComponent)
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.
timeSheetTaskComponent
- public void setTimeSheetNote(@Nullable String timeSheetNote)
Original property from the Odata EDM: TimeSheetNote
timeSheetNote
- public void setRecordedHours(@Nullable BigDecimal recordedHours)
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).
recordedHours
- public void setRecordedQuantity(@Nullable BigDecimal recordedQuantity)
Original property from the Odata EDM: RecordedQuantity
recordedQuantity
- public void setHoursUnitOfMeasure(@Nullable String hoursUnitOfMeasure)
Original property from the Odata EDM: HoursUnitOfMeasure
hoursUnitOfMeasure
- public void setRejectionReason(@Nullable String rejectionReason)
Original property from the Odata EDM: RejectionReason
rejectionReason
- public String toString()
toString
in class VdmObject<TimeSheetDataFields>
public boolean equals(Object o)
equals
in class VdmObject<TimeSheetDataFields>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<TimeSheetDataFields>
public int hashCode()
hashCode
in class VdmObject<TimeSheetDataFields>
Copyright © 2018 SAP SE. All rights reserved.