public class CostCenterActivityType extends VdmEntity<CostCenterActivityType>
Original entity name from the Odata EDM: A_CostCenterActivityTypeType
| Modifier and Type | Class and Description |
|---|---|
static class |
CostCenterActivityType.CostCenterActivityTypeBuilder
Helper class to allow for fluent creation of CostCenterActivityType instances.
|
| Modifier and Type | Field and Description |
|---|---|
static CostCenterActivityTypeField<String> |
ACTIVITY_TYPE_IS_BLOCKED
Use with available fluent helpers to apply the ActivityTypeIsBlocked field to query operations.
|
static CostCenterActivityTypeField<String> |
ACTL_POSTG_COST_CENTER_ACTY_TYPE_CAT
Use with available fluent helpers to apply the ActlPostgCostCenterActyTypeCat field to query operations.
|
static CostCenterActivityTypeField<String> |
ACTUAL_PRICE_ALLOCATION_METHOD
Use with available fluent helpers to apply the ActualPriceAllocationMethod field to query operations.
|
static CostCenterActivityTypeField<Boolean> |
ACTUAL_QUANTITY_IS_SET_MANUALLY
Use with available fluent helpers to apply the ActualQuantityIsSetManually field to query operations.
|
static CostCenterActivityTypeSelectable |
ALL_FIELDS
Selector for all available fields of CostCenterActivityType.
|
static CostCenterActivityTypeField<String> |
ALLOCATION_COST_ELEMENT
Use with available fluent helpers to apply the AllocationCostElement field to query operations.
|
static CostCenterActivityTypeField<String> |
CONTROLLING_AREA
Use with available fluent helpers to apply the ControllingArea field to query operations.
|
static CostCenterActivityTypeField<String> |
COST_CTR_ACTIVITY_TYPE
Use with available fluent helpers to apply the CostCtrActivityType field to query operations.
|
static CostCenterActivityTypeField<String> |
COST_CTR_ACTIVITY_TYPE_CATEGORY
Use with available fluent helpers to apply the CostCtrActivityTypeCategory field to query operations.
|
static CostCenterActivityTypeField<String> |
COST_CTR_ACTIVITY_TYPE_OUTP_QTY_UNIT
Use with available fluent helpers to apply the CostCtrActivityTypeOutpQtyUnit field to query operations.
|
static CostCenterActivityTypeField<String> |
COST_CTR_ACTIVITY_TYPE_QTY_UNIT
Use with available fluent helpers to apply the CostCtrActivityTypeQtyUnit field to query operations.
|
static CostCenterActivityTypeField<String> |
COST_ORIGIN_GROUP
Use with available fluent helpers to apply the CostOriginGroup field to query operations.
|
static CostCenterActivityTypeField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static CostCenterActivityTypeField<String> |
ENTERED_BY_USER
Use with available fluent helpers to apply the EnteredByUser field to query operations.
|
static CostCenterActivityTypeField<Boolean> |
FIXED_COST_IS_PREDISTRIBUTED
Use with available fluent helpers to apply the FixedCostIsPredistributed field to query operations.
|
static CostCenterActivityTypeField<BigDecimal> |
OUTPUT_QUANTITY_FACTOR
Use with available fluent helpers to apply the OutputQuantityFactor field to query operations.
|
static CostCenterActivityTypeField<Boolean> |
PERIOD_PRICE_IS_AVERAGE
Use with available fluent helpers to apply the PeriodPriceIsAverage field to query operations.
|
static CostCenterActivityTypeField<Boolean> |
PLAN_QUANTITY_IS_SET_MANUALLY
Use with available fluent helpers to apply the PlanQuantityIsSetManually field to query operations.
|
static CostCenterActivityTypeField<String> |
PRICE_ALLOCATION_METHOD
Use with available fluent helpers to apply the PriceAllocationMethod field to query operations.
|
static CostCenterActivityTypeLink<CostCenterActivityTypeText> |
TO_TEXT
Use with available fluent helpers to apply the to_Text navigation property to query operations.
|
static CostCenterActivityTypeField<LocalDateTime> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static CostCenterActivityTypeField<LocalDateTime> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
changedOriginalFields| Constructor and Description |
|---|
CostCenterActivityType() |
CostCenterActivityType(String controllingArea,
String costCtrActivityType,
LocalDateTime validityEndDate,
LocalDateTime validityStartDate,
String costCtrActivityTypeQtyUnit,
String costCtrActivityTypeCategory,
String allocationCostElement,
String costCtrActivityTypeOutpQtyUnit,
LocalDateTime creationDate,
String enteredByUser,
String costOriginGroup,
String actlPostgCostCenterActyTypeCat,
BigDecimal outputQuantityFactor,
String activityTypeIsBlocked,
Boolean fixedCostIsPredistributed,
String priceAllocationMethod,
Boolean periodPriceIsAverage,
String actualPriceAllocationMethod,
Boolean actualQuantityIsSetManually,
Boolean planQuantityIsSetManually,
List<CostCenterActivityTypeText> toText) |
| Modifier and Type | Method and Description |
|---|---|
void |
addText(CostCenterActivityTypeText... entity)
Adds elements to the list of associated CostCenterActivityTypeText entities.
|
void |
attachToService(String servicePath,
ErpConfigContext configContext)
Sets the service path and ERP configuration context for the fetch commands of this entity.
|
static CostCenterActivityType.CostCenterActivityTypeBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<CostCenterActivityTypeText> |
fetchText()
Fetches the CostCenterActivityTypeText entities (one to many) associated with this entity.
|
static <T> CostCenterActivityTypeField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getActivityTypeIsBlocked()
Constraints: Not nullable, Maximum length: 1
|
String |
getActlPostgCostCenterActyTypeCat()
Constraints: Not nullable, Maximum length: 1
|
String |
getActualPriceAllocationMethod()
Constraints: Not nullable, Maximum length: 3
|
Boolean |
getActualQuantityIsSetManually()
Constraints: none
|
String |
getAllocationCostElement()
Constraints: Not nullable, Maximum length: 10
|
String |
getControllingArea()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getCostCtrActivityType()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getCostCtrActivityTypeCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getCostCtrActivityTypeOutpQtyUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getCostCtrActivityTypeQtyUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getCostOriginGroup()
Constraints: Not nullable, Maximum length: 4
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
protected String |
getDefaultServicePath() |
String |
getEnteredByUser()
Constraints: Not nullable, Maximum length: 12
|
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
Boolean |
getFixedCostIsPredistributed()
Constraints: none
|
protected Map<String,Object> |
getKey() |
BigDecimal |
getOutputQuantityFactor()
Constraints: Not nullable, Precision: 5, Scale: 2
|
Boolean |
getPeriodPriceIsAverage()
Constraints: none
|
Boolean |
getPlanQuantityIsSetManually()
Constraints: none
|
String |
getPriceAllocationMethod()
Constraints: Not nullable, Maximum length: 3
|
Optional<List<CostCenterActivityTypeText>> |
getTextIfPresent()
Retrieval of associated CostCenterActivityTypeText entities (one to many).
|
List<CostCenterActivityTypeText> |
getTextOrFetch()
Retrieval of associated CostCenterActivityTypeText entities (one to many).
|
Class<CostCenterActivityType> |
getType() |
LocalDateTime |
getValidityEndDate()
(Key Field) Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getValidityStartDate()
Constraints: Not nullable, Precision: 0
|
int |
hashCode() |
void |
setActivityTypeIsBlocked(String activityTypeIsBlocked)
Constraints: Not nullable, Maximum length: 1
|
void |
setActlPostgCostCenterActyTypeCat(String actlPostgCostCenterActyTypeCat)
Constraints: Not nullable, Maximum length: 1
|
void |
setActualPriceAllocationMethod(String actualPriceAllocationMethod)
Constraints: Not nullable, Maximum length: 3
|
void |
setActualQuantityIsSetManually(Boolean actualQuantityIsSetManually)
Constraints: none
|
void |
setAllocationCostElement(String allocationCostElement)
Constraints: Not nullable, Maximum length: 10
|
void |
setControllingArea(String controllingArea)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setCostCtrActivityType(String costCtrActivityType)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setCostCtrActivityTypeCategory(String costCtrActivityTypeCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setCostCtrActivityTypeOutpQtyUnit(String costCtrActivityTypeOutpQtyUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setCostCtrActivityTypeQtyUnit(String costCtrActivityTypeQtyUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setCostOriginGroup(String costOriginGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setEnteredByUser(String enteredByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Deprecated.
Use
attachToService(String, ErpConfigContext) instead. |
void |
setFixedCostIsPredistributed(Boolean fixedCostIsPredistributed)
Constraints: none
|
void |
setOutputQuantityFactor(BigDecimal outputQuantityFactor)
Constraints: Not nullable, Precision: 5, Scale: 2
|
void |
setPeriodPriceIsAverage(Boolean periodPriceIsAverage)
Constraints: none
|
void |
setPlanQuantityIsSetManually(Boolean planQuantityIsSetManually)
Constraints: none
|
void |
setPriceAllocationMethod(String priceAllocationMethod)
Constraints: Not nullable, Maximum length: 3
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setText(List<CostCenterActivityTypeText> value)
Overwrites the list of associated CostCenterActivityTypeText entities for the loaded navigation property
to_Text.
|
void |
setValidityEndDate(LocalDateTime validityEndDate)
(Key Field) Constraints: Not nullable, Precision: 0
|
void |
setValidityStartDate(LocalDateTime validityStartDate)
Constraints: Not nullable, Precision: 0
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setVersionIdentifiergetChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFieldspublic static final CostCenterActivityTypeSelectable ALL_FIELDS
public static final CostCenterActivityTypeField<String> CONTROLLING_AREA
public static final CostCenterActivityTypeField<String> COST_CTR_ACTIVITY_TYPE
public static final CostCenterActivityTypeField<LocalDateTime> VALIDITY_END_DATE
public static final CostCenterActivityTypeField<LocalDateTime> VALIDITY_START_DATE
public static final CostCenterActivityTypeField<String> COST_CTR_ACTIVITY_TYPE_QTY_UNIT
public static final CostCenterActivityTypeField<String> COST_CTR_ACTIVITY_TYPE_CATEGORY
public static final CostCenterActivityTypeField<String> ALLOCATION_COST_ELEMENT
public static final CostCenterActivityTypeField<String> COST_CTR_ACTIVITY_TYPE_OUTP_QTY_UNIT
public static final CostCenterActivityTypeField<LocalDateTime> CREATION_DATE
public static final CostCenterActivityTypeField<String> ENTERED_BY_USER
public static final CostCenterActivityTypeField<String> COST_ORIGIN_GROUP
public static final CostCenterActivityTypeField<String> ACTL_POSTG_COST_CENTER_ACTY_TYPE_CAT
public static final CostCenterActivityTypeField<BigDecimal> OUTPUT_QUANTITY_FACTOR
public static final CostCenterActivityTypeField<String> ACTIVITY_TYPE_IS_BLOCKED
public static final CostCenterActivityTypeField<Boolean> FIXED_COST_IS_PREDISTRIBUTED
public static final CostCenterActivityTypeField<String> PRICE_ALLOCATION_METHOD
public static final CostCenterActivityTypeField<Boolean> PERIOD_PRICE_IS_AVERAGE
public static final CostCenterActivityTypeField<String> ACTUAL_PRICE_ALLOCATION_METHOD
public static final CostCenterActivityTypeField<Boolean> ACTUAL_QUANTITY_IS_SET_MANUALLY
public static final CostCenterActivityTypeField<Boolean> PLAN_QUANTITY_IS_SET_MANUALLY
public static final CostCenterActivityTypeLink<CostCenterActivityTypeText> TO_TEXT
public CostCenterActivityType()
public CostCenterActivityType(@Nullable String controllingArea, @Nullable String costCtrActivityType, @Nullable LocalDateTime validityEndDate, @Nullable LocalDateTime validityStartDate, @Nullable String costCtrActivityTypeQtyUnit, @Nullable String costCtrActivityTypeCategory, @Nullable String allocationCostElement, @Nullable String costCtrActivityTypeOutpQtyUnit, @Nullable LocalDateTime creationDate, @Nullable String enteredByUser, @Nullable String costOriginGroup, @Nullable String actlPostgCostCenterActyTypeCat, @Nullable BigDecimal outputQuantityFactor, @Nullable String activityTypeIsBlocked, @Nullable Boolean fixedCostIsPredistributed, @Nullable String priceAllocationMethod, @Nullable Boolean periodPriceIsAverage, @Nullable String actualPriceAllocationMethod, @Nullable Boolean actualQuantityIsSetManually, @Nullable Boolean planQuantityIsSetManually, List<CostCenterActivityTypeText> toText)
@Nonnull public Class<CostCenterActivityType> getType()
getType in class VdmObject<CostCenterActivityType>public void setControllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
controllingArea - Controlling Areapublic void setCostCtrActivityType(@Nullable String costCtrActivityType)
Original property name from the Odata EDM: CostCtrActivityType
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.
costCtrActivityType - Key uniquely identifying .public void setValidityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
validityEndDate - Date indicating up to when an entry is valid.public void setValidityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
validityStartDate - Date indicating as of when an entry is valid.public void setCostCtrActivityTypeQtyUnit(@Nullable String costCtrActivityTypeQtyUnit)
Original property name from the Odata EDM: CostCtrActivityTypeQtyUnit
The database records the activity type using the unit stored in the activity type master data.You cannot change the unit in the master data if dependent data exists.Subsequent plan or actual postings can use different units provided they are defined as convertible to the unit defined in the master data.
costCtrActivityTypeQtyUnit - The activity unit is either the time or quantity unit used to post the consumed activity quantities.public void setCostCtrActivityTypeCategory(@Nullable String costCtrActivityTypeCategory)
Original property name from the Odata EDM: CostCtrActivityTypeCategory
Activity type category 1 (Manual entry, manual allocation)Activity types of this category use plan activity quantities. The plan activity is allocated to the different receiver objects using activity input planning. It may be necessary to reconcile the activity quantities and the plan scheduled activity.Actual activity quantities are entered for each business transaction using internal activity allocation.Activity type category 2 (Indirect calculation, indirect allocation)The quantities produced by the activity types in this category cannot be calculated or only with great effort. The plan and actual activity quantities are determined in indirect activity allocation using one of the following:The defined sender/receiver relationshpsThe receiver tracing factorsFixed quantities (defined in the segments)Allocating the activities also takes place automatically through indirect activity allocation as described above.The actual and planned activity quantities result from the sum of the activity inputs calculated from the tracing factors on the individual receivers.Plan and scheduled activity quantities are therefore automatically reconciled.Activity type category 3 (Manual entry, indirect allocation)Activity types of this category use activity quantities entered manually. Entering the actual activity quantity takes place on an activity-related basis using a special function (Non-allocatable activities) for which no receiver objects can be given.The plan and actual activity quantities are allocated indirectly using defined sender/receiver relationships. The R/3 System calculates the activity quantity to be allocated for each receiver based on the ratios of tracing factors for all receivers. The manually planned or posted activity is thereby completely allocated to the receivers.This ensures that plan activities are fully reconciled after carrying out indirect activity allocation.Activity type category 4 (Manual entry, no allocation)Activity types of this category use activity quantities entered manually. Allocations to other objects are not possible.The actual activity quantity is entered for each transaction using a special function (Non-allocatable activities). No receiver objects can be entered.You can save a default value in the master data for an activity type or a business process for allocatable activity type categories or allocation categories (category 1, 2 or 3). You can change the default value within planning to a different allocatable activity type category or allocation category if you are planning for the first time.You can only change non-allocatable activity type categories or allocation categories (category 4) to an allocatable activity type category or allocation category (or vice versa) if activity-dependent data exists.
costCtrActivityTypeCategory - Indicator determining the method of activity quantity planning and activity allocation.public void setAllocationCostElement(@Nullable String allocationCostElement)
Original property name from the Odata EDM: AllocationCostElement
The allocation cost element is the central characteristic used in all CO postings. It is therefore also an important criterion for reporting - for example, many reports are structured according to the posted cost elements.You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.The allocation cost element must have been created in the cost element master data as a secondary cost element of category 43 "Allocate activities/processes".Field changesYou can change this field for each fiscal year. For example, you can change the field content for a new fiscal year.Time dependencyThe data in this field is always time-based.
allocationCostElement - The allocation cost element is a secondary cost element, under which the activity type or business
process is allocated.public void setCostCtrActivityTypeOutpQtyUnit(@Nullable String costCtrActivityTypeOutpQtyUnit)
Original property name from the Odata EDM: CostCtrActivityTypeOutpQtyUnit
The unit of measure with which the output is recorded in databases is defined in the activity type master and cannot be changed.You can make subsequent plan and actual postings in an output unit different to the one recorded in the database, provided it can be converted to the unit of measure defined in the activity type master.
costCtrActivityTypeOutpQtyUnit - The output unit is the unit of measure in which the activity produced is posted.public void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate - Date on which the cost estimate was created.public void setEnteredByUser(@Nullable String enteredByUser)
Original property name from the Odata EDM: EnteredByUser
enteredByUser - User ID of the person who created the cost estimate.public void setCostOriginGroup(@Nullable String costOriginGroup)
Original property name from the Odata EDM: CostOriginGroup
When material costs are calculated, each material is given a general ledger account and thus is assigned to a primary cost element. If you enter an origin group for the material, the combination of source group and cost element is updated to the CO component. This means that you canDefine calculation bases for determination of overhead rates for particular material groups.Define cost components in product costing for particular material groups.Create rules for activating work in process for each material group.When overhead is calculated, an object is debited with overhead costs and another object (usually a cost center) is credited. For more information on the origin of overhead rates in the credit record, specify an origin group in the credit key. The system then displays the origin group in Cost Center Accounting, as well as the overhead cost element.
costOriginGroup - Used for subdividing material and overhead costs.public void setActlPostgCostCenterActyTypeCat(@Nullable String actlPostgCostCenterActyTypeCat)
Original property name from the Odata EDM: ActlPostgCostCenterActyTypeCat
Activity type category 1 (Manual entry, manual allocation)Actual activity quantities in internal activity allocation are entered based on transaction.Activity type category 2 (Indirect calculation, indirect allocation)Activity quantities produced by activity types cannot be calculated or only with great effort. The plan and actual activity quantities are determined in indirect activity allocation using defined sender/receiver relationships and receiver tracing factors or fixed quantities (defined in the segments)Allocating the activities also takes place automatically through indirect activity allocation as described above.The actual and plan activity quantities result from the sum of the activity inputs calculated from the tracing factors on the individual receivers.Plan and scheduled activity quantities are therefore automatically reconciled.Activity type category 3 (Manual entry, indirect allocation)Activity quantities are planned manually. Entering the actual activity quantity takes place on a transaction-related basis using a special function (Non-allocatable activities) for which no receiver objects can be given.The plan and actual activity quantities are allocated indirectly using defined sender/receiver relationships. The R/3 System calculates the activity quantity to be allocated for each receiver based on the ratios of tracing factors for all receivers. The manually planned or posted activity is thereby completely allocated to the receivers.This always ensures that the plan activities are fully reconciled after carrying out indirect activity allocation.Activity type category 4 (Manual entry, no allocation)Activity types of this category use actual activity quantities entered on a transaction-related basis using a special function (Non-allocatable activities) where no receiver objects can be entered.Activity type category 5 (Calculation and allocation via target=actual activity allocation)Used in target=actual activity allocation.Because the allocation is used only for actual values, activities used in target=actual activity allocation must be given separate activity type categories for plan and actual. Planning can use categories 1, 2, or 3, where 1 is used as a rule.You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
actlPostgCostCenterActyTypeCat - Indicator determining the method of actual activity allocation.public void setOutputQuantityFactor(@Nullable BigDecimal outputQuantityFactor)
Original property name from the Odata EDM: OutputQuantityFactor
Output quantity = Activity quantity * Output factorIn planning you can calculate the output quantity from the activityquantity and output factor. In the planning transaction, choose "Edit -> Activity -> Output".
outputQuantityFactor - Factor describing the relationship between activity quantity and output quantity, expressed by the
formula:public void setActivityTypeIsBlocked(@Nullable String activityTypeIsBlocked)
Original property name from the Odata EDM: ActivityTypeIsBlocked
If the indicator is active, the affected activity type cannot be included.NotesIf planning is reconciled, meaning plan activity = scheduled activity, the indicator should be activated so that the plan quantity remains unchanged.If the indicator is inactive, the activity type can be drawn upon for activity input planning and indirect activity allocation in plan.If active, the lock indicator has no effect onactual postingsplanning, other than activity input planning and indirect activity allocation in planactivity price changes
activityTypeIsBlocked - Indicator determining whether an activity type is locked for activity input planning.public void setFixedCostIsPredistributed(@Nullable Boolean fixedCostIsPredistributed)
Original property name from the Odata EDM: FixedCostIsPredistributed
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
fixedCostIsPredistributed - Indicator for allowing the activity type or business process to be used in fixed cost predistribution.public void setPriceAllocationMethod(@Nullable String priceAllocationMethod)
Original property name from the Odata EDM: PriceAllocationMethod
To do this there are two fields: The "Price indicator" field controls plan price calculation. For actual allocations you can set an indicator in the "Actual price indicator" field that differs from the plan indicator.You can enter "001", "002" or "003" in the "Price indicator" field or "005" or "006" in the "Actual price indicator" field.The plan price indicator can have the value "004", the actual price indicator "008". This occurs if you have selected "Purely iterative Prices" in version maintenance within Customizing.NoteIf you do not set a price indicator, the system uses the plan price.The meaning of the possible entries is as follows:001:The price of the activity type is determined automatically based on the planned activity and the planned costs required for this plan activity quantity.Fixed price: Fixed planned costs/plan activity quantityVariable price: Variable planned costs/plan activity quantityTotal price: Fixed price + variable price002:The variable portion of the price is calculated based on the plan activity quantity. To determine the fixed portion, the system uses the capacity and not the plan activity quantity.This procedure usually leads to an underabsorption of the cost center or business process from the perspective of quantities.Fixed price: Fixed planned costs/capacityVariable price: Variable planned costs/planned activityTotal price: Fixed price + variable priceNoteIf you have entered the values "001" or "002", the system calculates new prices when determining the plan prices.003:The price of the activity type or business process is set manually.004 (activation of version maintenance):The plan price of the activity type or business process is determined iteratively only.If you activate the indicator purely iterative price in the version, the R/3 System calculates an iterative price along with the price resulting from planning.005: (actual price)The R/3 System determines the price of the activity type using the actual activity of the cost center.006: (actual price)The variable portion of the price is calculated based on the actual activity.NoteIf you have set the values "005" and "006", the system calculates new prices when you execute actual price calculation. Revaluation of actual activity at actual prices occurs only if you have selected Revaluation in version maintenance.007 (manual actual price)The actual price of the activity price or business process is set manually. Using this price indicator, you can set an independent (manual) price that differs from the plan.008: (actual price, selection using version maintenance)Purely iterative actual priceIf you activate the indicator Purely iterative price in the version, the R/3 System calculates an iterative price along with the price resulting from planning.In the master data of the activity type or business process, you can define a default value.When planning for the first time, this default value can be overwritten.
priceAllocationMethod - Indicator showing how the R/3 System calculates the price of a business process or activity type for a
cost center.public void setPeriodPriceIsAverage(@Nullable Boolean periodPriceIsAverage)
Original property name from the Odata EDM: PeriodPriceIsAverage
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.This takes place either on the version level or per cost center/activity type in planning.VersionActivity prices for cost centers/activity types remain constant for the entire fiscal year in the version. The total plan costs and activity are taken into account when activity prices are calculated. Monthly fluctuations are ignored. Activate the "Average activity price" indicator from the fiscal-year dependent version parameters in the version as a planning method.Cost center/activity typeIf you have not defined an average activity price for your version, you can define a constant activity price for the fiscal year for individual cost centers/activity types. Activity price calculation smoothes out fluctuations in the cost center/activity type activity price. Activate the appropriate indicator in activity type planning.A default value for planning can be saved in the activity type master record. This value can be overwritten during planning.
periodPriceIsAverage - Indicator determining that activity prices for cost centers/activity types remain constant for the
entire fiscal year.public void setActualPriceAllocationMethod(@Nullable String actualPriceAllocationMethod)
Original property name from the Odata EDM: ActualPriceAllocationMethod
For actual allocation you can specify an indicator that varies from the plan, "005" and "006".The actual price indicator can also have the value "008". This occurs when you select the "Purely iterative price" indicator in the version maintenance of Customizing.The following values are possible:005 (actual price)When you execute actual price calculation, the R/3 System determines the actual price based on the actual activity.006 (actual price)The variable portion of the price is determined through the actual activity. To determine the fixed portion, however, the system uses the actual capacity. This is relevant for cost centers that must always provide the maximum activity quantity, for example, the provision of energy on an energy cost center. The overall costs for this cost center are fixed.NoteIf you have set the values "005" and "006", the system calculates new prices when you execute actual price calculation. Revaluation of actual activity at actual prices occurs only if you have selected Revaluation in version maintenance.008 (Selecting version maintenance):The actual price of the activity type is caluclated purely iteratively. If you activate the indicator Purely iterative price in the version, the R/3 System calculates an iterative price along with the price resulting from planning.You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
actualPriceAllocationMethod - Indicator showing how the R/3 System calculates the actual price of an activity type for a cost
center.public void setActualQuantityIsSetManually(@Nullable Boolean actualQuantityIsSetManually)
Original property name from the Odata EDM: ActualQuantityIsSetManually
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
actualQuantityIsSetManually - If this indicator is set, you must post a manual quantity, in addition to the quantity with which the
object is credited. This makes sense especially when the quantity leading to the credit of the object
is to be determined indirectly, but the actual quantity from the sender view is already known.public void setPlanQuantityIsSetManually(@Nullable Boolean planQuantityIsSetManually)
Original property name from the Odata EDM: PlanQuantityIsSetManually
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
planQuantityIsSetManually - If you set this indicator, the planned activity quantity is not changed by plan reconciliation, even
if planning is not to be reconciled for the object.protected String getEntityCollection()
getEntityCollection in class VdmEntity<CostCenterActivityType>@Nonnull protected Map<String,Object> getKey()
getKey in class VdmObject<CostCenterActivityType>@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields in class VdmObject<CostCenterActivityType>protected void fromMap(Map<String,Object> inputValues)
fromMap in class VdmObject<CostCenterActivityType>@Nonnull public static <T> CostCenterActivityTypeField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T - The type of the extension field when performing value comparisons.fieldName - The name of the extension field as returned by the OData service.fieldType - The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> CostCenterActivityTypeField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T - The type of the extension field when performing value comparisons.DomainT - The type of the extension field as returned by the OData service.typeConverter - A TypeConverterfieldName - The name of the extension field as returned by the OData service.@Nullable public ErpConfigContext getErpConfigContext()
VdmEntitygetErpConfigContext in class VdmEntity<CostCenterActivityType>@Deprecated public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
attachToService(String, ErpConfigContext) instead.VdmEntitysetErpConfigContext in class VdmEntity<CostCenterActivityType>erpConfigContext - New ERP configuration context to apply to this entityprotected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntityNote: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch in class VdmEntity<CostCenterActivityType>public void attachToService(@Nullable String servicePath, @Nullable ErpConfigContext configContext)
VdmEntityNote: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService in class VdmEntity<CostCenterActivityType>servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.configContext - Optional parameter. New ERP configuration context to apply to this entity and any associated entities
that were previously fetched. If a null value is provided and the ERP configuration context has never
been set, then the ERP configuration context will be set to a new instance of
ErpConfigContext.protected String getDefaultServicePath()
getDefaultServicePath in class VdmEntity<CostCenterActivityType>@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties in class VdmObject<CostCenterActivityType>@Nonnull public List<CostCenterActivityTypeText> fetchText() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<CostCenterActivityTypeText> getTextOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Text of a queried CostCenterActivityType is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public Optional<List<CostCenterActivityTypeText>> getTextIfPresent()
If the navigation property for an entity CostCenterActivityType has not been resolved yet, this method
will not query further information. Instead its Optional result state will be
empty.
Optional with result state
empty is returned.public void setText(@Nonnull List<CostCenterActivityTypeText> value)
If the navigation property to_Text of a queried CostCenterActivityType is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of CostCenterActivityTypeText entities.public void addText(CostCenterActivityTypeText... entity)
If the navigation property to_Text of a queried CostCenterActivityType is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of CostCenterActivityTypeText entities.public static CostCenterActivityType.CostCenterActivityTypeBuilder builder()
@Nullable public String getControllingArea()
Original property name from the Odata EDM: ControllingArea
@Nullable public String getCostCtrActivityType()
Original property name from the Odata EDM: CostCtrActivityType
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 LocalDateTime getValidityEndDate()
Original property name from the Odata EDM: ValidityEndDate
@Nullable public LocalDateTime getValidityStartDate()
Original property name from the Odata EDM: ValidityStartDate
@Nullable public String getCostCtrActivityTypeQtyUnit()
Original property name from the Odata EDM: CostCtrActivityTypeQtyUnit
The database records the activity type using the unit stored in the activity type master data.You cannot change the unit in the master data if dependent data exists.Subsequent plan or actual postings can use different units provided they are defined as convertible to the unit defined in the master data.
@Nullable public String getCostCtrActivityTypeCategory()
Original property name from the Odata EDM: CostCtrActivityTypeCategory
Activity type category 1 (Manual entry, manual allocation)Activity types of this category use plan activity quantities. The plan activity is allocated to the different receiver objects using activity input planning. It may be necessary to reconcile the activity quantities and the plan scheduled activity.Actual activity quantities are entered for each business transaction using internal activity allocation.Activity type category 2 (Indirect calculation, indirect allocation)The quantities produced by the activity types in this category cannot be calculated or only with great effort. The plan and actual activity quantities are determined in indirect activity allocation using one of the following:The defined sender/receiver relationshpsThe receiver tracing factorsFixed quantities (defined in the segments)Allocating the activities also takes place automatically through indirect activity allocation as described above.The actual and planned activity quantities result from the sum of the activity inputs calculated from the tracing factors on the individual receivers.Plan and scheduled activity quantities are therefore automatically reconciled.Activity type category 3 (Manual entry, indirect allocation)Activity types of this category use activity quantities entered manually. Entering the actual activity quantity takes place on an activity-related basis using a special function (Non-allocatable activities) for which no receiver objects can be given.The plan and actual activity quantities are allocated indirectly using defined sender/receiver relationships. The R/3 System calculates the activity quantity to be allocated for each receiver based on the ratios of tracing factors for all receivers. The manually planned or posted activity is thereby completely allocated to the receivers.This ensures that plan activities are fully reconciled after carrying out indirect activity allocation.Activity type category 4 (Manual entry, no allocation)Activity types of this category use activity quantities entered manually. Allocations to other objects are not possible.The actual activity quantity is entered for each transaction using a special function (Non-allocatable activities). No receiver objects can be entered.You can save a default value in the master data for an activity type or a business process for allocatable activity type categories or allocation categories (category 1, 2 or 3). You can change the default value within planning to a different allocatable activity type category or allocation category if you are planning for the first time.You can only change non-allocatable activity type categories or allocation categories (category 4) to an allocatable activity type category or allocation category (or vice versa) if activity-dependent data exists.
@Nullable public String getAllocationCostElement()
Original property name from the Odata EDM: AllocationCostElement
The allocation cost element is the central characteristic used in all CO postings. It is therefore also an important criterion for reporting - for example, many reports are structured according to the posted cost elements.You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.The allocation cost element must have been created in the cost element master data as a secondary cost element of category 43 "Allocate activities/processes".Field changesYou can change this field for each fiscal year. For example, you can change the field content for a new fiscal year.Time dependencyThe data in this field is always time-based.
@Nullable public String getCostCtrActivityTypeOutpQtyUnit()
Original property name from the Odata EDM: CostCtrActivityTypeOutpQtyUnit
The unit of measure with which the output is recorded in databases is defined in the activity type master and cannot be changed.You can make subsequent plan and actual postings in an output unit different to the one recorded in the database, provided it can be converted to the unit of measure defined in the activity type master.
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public String getEnteredByUser()
Original property name from the Odata EDM: EnteredByUser
@Nullable public String getCostOriginGroup()
Original property name from the Odata EDM: CostOriginGroup
When material costs are calculated, each material is given a general ledger account and thus is assigned to a primary cost element. If you enter an origin group for the material, the combination of source group and cost element is updated to the CO component. This means that you canDefine calculation bases for determination of overhead rates for particular material groups.Define cost components in product costing for particular material groups.Create rules for activating work in process for each material group.When overhead is calculated, an object is debited with overhead costs and another object (usually a cost center) is credited. For more information on the origin of overhead rates in the credit record, specify an origin group in the credit key. The system then displays the origin group in Cost Center Accounting, as well as the overhead cost element.
@Nullable public String getActlPostgCostCenterActyTypeCat()
Original property name from the Odata EDM: ActlPostgCostCenterActyTypeCat
Activity type category 1 (Manual entry, manual allocation)Actual activity quantities in internal activity allocation are entered based on transaction.Activity type category 2 (Indirect calculation, indirect allocation)Activity quantities produced by activity types cannot be calculated or only with great effort. The plan and actual activity quantities are determined in indirect activity allocation using defined sender/receiver relationships and receiver tracing factors or fixed quantities (defined in the segments)Allocating the activities also takes place automatically through indirect activity allocation as described above.The actual and plan activity quantities result from the sum of the activity inputs calculated from the tracing factors on the individual receivers.Plan and scheduled activity quantities are therefore automatically reconciled.Activity type category 3 (Manual entry, indirect allocation)Activity quantities are planned manually. Entering the actual activity quantity takes place on a transaction-related basis using a special function (Non-allocatable activities) for which no receiver objects can be given.The plan and actual activity quantities are allocated indirectly using defined sender/receiver relationships. The R/3 System calculates the activity quantity to be allocated for each receiver based on the ratios of tracing factors for all receivers. The manually planned or posted activity is thereby completely allocated to the receivers.This always ensures that the plan activities are fully reconciled after carrying out indirect activity allocation.Activity type category 4 (Manual entry, no allocation)Activity types of this category use actual activity quantities entered on a transaction-related basis using a special function (Non-allocatable activities) where no receiver objects can be entered.Activity type category 5 (Calculation and allocation via target=actual activity allocation)Used in target=actual activity allocation.Because the allocation is used only for actual values, activities used in target=actual activity allocation must be given separate activity type categories for plan and actual. Planning can use categories 1, 2, or 3, where 1 is used as a rule.You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
@Nullable public BigDecimal getOutputQuantityFactor()
Original property name from the Odata EDM: OutputQuantityFactor
Output quantity = Activity quantity * Output factorIn planning you can calculate the output quantity from the activityquantity and output factor. In the planning transaction, choose "Edit -> Activity -> Output".
@Nullable public String getActivityTypeIsBlocked()
Original property name from the Odata EDM: ActivityTypeIsBlocked
If the indicator is active, the affected activity type cannot be included.NotesIf planning is reconciled, meaning plan activity = scheduled activity, the indicator should be activated so that the plan quantity remains unchanged.If the indicator is inactive, the activity type can be drawn upon for activity input planning and indirect activity allocation in plan.If active, the lock indicator has no effect onactual postingsplanning, other than activity input planning and indirect activity allocation in planactivity price changes
@Nullable public Boolean getFixedCostIsPredistributed()
Original property name from the Odata EDM: FixedCostIsPredistributed
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
@Nullable public String getPriceAllocationMethod()
Original property name from the Odata EDM: PriceAllocationMethod
To do this there are two fields: The "Price indicator" field controls plan price calculation. For actual allocations you can set an indicator in the "Actual price indicator" field that differs from the plan indicator.You can enter "001", "002" or "003" in the "Price indicator" field or "005" or "006" in the "Actual price indicator" field.The plan price indicator can have the value "004", the actual price indicator "008". This occurs if you have selected "Purely iterative Prices" in version maintenance within Customizing.NoteIf you do not set a price indicator, the system uses the plan price.The meaning of the possible entries is as follows:001:The price of the activity type is determined automatically based on the planned activity and the planned costs required for this plan activity quantity.Fixed price: Fixed planned costs/plan activity quantityVariable price: Variable planned costs/plan activity quantityTotal price: Fixed price + variable price002:The variable portion of the price is calculated based on the plan activity quantity. To determine the fixed portion, the system uses the capacity and not the plan activity quantity.This procedure usually leads to an underabsorption of the cost center or business process from the perspective of quantities.Fixed price: Fixed planned costs/capacityVariable price: Variable planned costs/planned activityTotal price: Fixed price + variable priceNoteIf you have entered the values "001" or "002", the system calculates new prices when determining the plan prices.003:The price of the activity type or business process is set manually.004 (activation of version maintenance):The plan price of the activity type or business process is determined iteratively only.If you activate the indicator purely iterative price in the version, the R/3 System calculates an iterative price along with the price resulting from planning.005: (actual price)The R/3 System determines the price of the activity type using the actual activity of the cost center.006: (actual price)The variable portion of the price is calculated based on the actual activity.NoteIf you have set the values "005" and "006", the system calculates new prices when you execute actual price calculation. Revaluation of actual activity at actual prices occurs only if you have selected Revaluation in version maintenance.007 (manual actual price)The actual price of the activity price or business process is set manually. Using this price indicator, you can set an independent (manual) price that differs from the plan.008: (actual price, selection using version maintenance)Purely iterative actual priceIf you activate the indicator Purely iterative price in the version, the R/3 System calculates an iterative price along with the price resulting from planning.In the master data of the activity type or business process, you can define a default value.When planning for the first time, this default value can be overwritten.
@Nullable public Boolean getPeriodPriceIsAverage()
Original property name from the Odata EDM: PeriodPriceIsAverage
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.This takes place either on the version level or per cost center/activity type in planning.VersionActivity prices for cost centers/activity types remain constant for the entire fiscal year in the version. The total plan costs and activity are taken into account when activity prices are calculated. Monthly fluctuations are ignored. Activate the "Average activity price" indicator from the fiscal-year dependent version parameters in the version as a planning method.Cost center/activity typeIf you have not defined an average activity price for your version, you can define a constant activity price for the fiscal year for individual cost centers/activity types. Activity price calculation smoothes out fluctuations in the cost center/activity type activity price. Activate the appropriate indicator in activity type planning.A default value for planning can be saved in the activity type master record. This value can be overwritten during planning.
@Nullable public String getActualPriceAllocationMethod()
Original property name from the Odata EDM: ActualPriceAllocationMethod
For actual allocation you can specify an indicator that varies from the plan, "005" and "006".The actual price indicator can also have the value "008". This occurs when you select the "Purely iterative price" indicator in the version maintenance of Customizing.The following values are possible:005 (actual price)When you execute actual price calculation, the R/3 System determines the actual price based on the actual activity.006 (actual price)The variable portion of the price is determined through the actual activity. To determine the fixed portion, however, the system uses the actual capacity. This is relevant for cost centers that must always provide the maximum activity quantity, for example, the provision of energy on an energy cost center. The overall costs for this cost center are fixed.NoteIf you have set the values "005" and "006", the system calculates new prices when you execute actual price calculation. Revaluation of actual activity at actual prices occurs only if you have selected Revaluation in version maintenance.008 (Selecting version maintenance):The actual price of the activity type is caluclated purely iteratively. If you activate the indicator Purely iterative price in the version, the R/3 System calculates an iterative price along with the price resulting from planning.You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
@Nullable public Boolean getActualQuantityIsSetManually()
Original property name from the Odata EDM: ActualQuantityIsSetManually
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
@Nullable public Boolean getPlanQuantityIsSetManually()
Original property name from the Odata EDM: PlanQuantityIsSetManually
You can store a default value in the master data of an activity type or a business process.You can overwrite the default value within planning if you are planning for the first time.
public String toString()
toString in class VdmObject<CostCenterActivityType>public boolean equals(Object o)
equals in class VdmObject<CostCenterActivityType>protected boolean canEqual(Object other)
canEqual in class VdmObject<CostCenterActivityType>public int hashCode()
hashCode in class VdmObject<CostCenterActivityType>Copyright © 2019 SAP SE. All rights reserved.