public class TimeSheetDataFields extends VdmComplex<TimeSheetDataFields>
| Modifier and Type | Class and Description |
|---|---|
static class |
TimeSheetDataFields.TimeSheetDataFieldsBuilder |
| 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() |
boolean |
equals(Object o) |
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
|
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
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField@Generated(value="lombok") public TimeSheetDataFields()
@ConstructorProperties(value={"controllingArea","senderCostCenter","receiverCostCenter","internalOrder","activityType","wBSElement","workItem","billingControlCategory","purchaseOrder","purchaseOrderItem","timeSheetTaskType","timeSheetTaskLevel","timeSheetTaskComponent","timeSheetNote","recordedHours","recordedQuantity","hoursUnitOfMeasure","rejectionReason"}) @Generated(value="lombok") 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>@Generated(value="lombok") public static TimeSheetDataFields.TimeSheetDataFieldsBuilder builder()
@Nullable @Generated(value="lombok") public String getControllingArea()
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 @Generated(value="lombok") public String getSenderCostCenter()
@Nullable @Generated(value="lombok") public String getReceiverCostCenter()
@Nullable @Generated(value="lombok") public String getInternalOrder()
@Nullable @Generated(value="lombok") public String getActivityType()
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 @Generated(value="lombok") public String getWBSElement()
@Nullable @Generated(value="lombok") public String getWorkItem()
@Nullable @Generated(value="lombok") public String getBillingControlCategory()
@Nullable @Generated(value="lombok") public String getPurchaseOrder()
@Nullable @Generated(value="lombok") public String getPurchaseOrderItem()
@Nullable @Generated(value="lombok") public String getTimeSheetTaskType()
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 @Generated(value="lombok") public String getTimeSheetTaskLevel()
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 @Generated(value="lombok") public String getTimeSheetTaskComponent()
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 @Generated(value="lombok") public String getTimeSheetNote()
@Nullable @Generated(value="lombok") public BigDecimal getRecordedHours()
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 @Generated(value="lombok") public BigDecimal getRecordedQuantity()
@Nullable @Generated(value="lombok") public String getHoursUnitOfMeasure()
@Nullable @Generated(value="lombok") public String getRejectionReason()
@Generated(value="lombok") public void setControllingArea(@Nullable String 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 - @Generated(value="lombok") public void setSenderCostCenter(@Nullable String senderCostCenter)
senderCostCenter - @Generated(value="lombok") public void setReceiverCostCenter(@Nullable String receiverCostCenter)
receiverCostCenter - @Generated(value="lombok") public void setInternalOrder(@Nullable String internalOrder)
internalOrder - @Generated(value="lombok") public void setActivityType(@Nullable String 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 - @Generated(value="lombok") public void setWBSElement(@Nullable String wBSElement)
wBSElement - @Generated(value="lombok") public void setWorkItem(@Nullable String workItem)
workItem - @Generated(value="lombok") public void setBillingControlCategory(@Nullable String billingControlCategory)
billingControlCategory - @Generated(value="lombok") public void setPurchaseOrder(@Nullable String purchaseOrder)
purchaseOrder - @Generated(value="lombok") public void setPurchaseOrderItem(@Nullable String purchaseOrderItem)
purchaseOrderItem - @Generated(value="lombok") public void setTimeSheetTaskType(@Nullable String 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 - @Generated(value="lombok") public void setTimeSheetTaskLevel(@Nullable String 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 - @Generated(value="lombok") public void setTimeSheetTaskComponent(@Nullable String 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 - @Generated(value="lombok") public void setTimeSheetNote(@Nullable String timeSheetNote)
timeSheetNote - @Generated(value="lombok") public void setRecordedHours(@Nullable BigDecimal 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 - @Generated(value="lombok") public void setRecordedQuantity(@Nullable BigDecimal recordedQuantity)
recordedQuantity - @Generated(value="lombok") public void setHoursUnitOfMeasure(@Nullable String hoursUnitOfMeasure)
hoursUnitOfMeasure - @Generated(value="lombok") public void setRejectionReason(@Nullable String rejectionReason)
rejectionReason - @Generated(value="lombok") public String toString()
toString in class VdmObject<TimeSheetDataFields>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<TimeSheetDataFields>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<TimeSheetDataFields>Copyright © 2018 SAP SE. All rights reserved.