public static final class CostCenterActivityType.CostCenterActivityTypeBuilder extends Object
@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder text(CostCenterActivityTypeText... value)
value - The CostCenterActivityTypeTexts to build this CostCenterActivityType with.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder costCtrActivityType(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder validityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder validityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder costCtrActivityTypeQtyUnit(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder costCtrActivityTypeCategory(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder allocationCostElement(@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.
process is allocated.this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder costCtrActivityTypeOutpQtyUnit(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder enteredByUser(@Nullable String enteredByUser)
Original property name from the Odata EDM: EnteredByUser
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder costOriginGroup(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder actlPostgCostCenterActyTypeCat(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder outputQuantityFactor(@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".
formula:this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder activityTypeIsBlocked(@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
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder fixedCostIsPredistributed(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder priceAllocationMethod(@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.
cost center.this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder periodPriceIsAverage(@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.
fiscal year.this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder actualPriceAllocationMethod(@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.
this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder actualQuantityIsSetManually(@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.
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.this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder planQuantityIsSetManually(@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.
planning is not to be reconciled for the object.this.@Nonnull public CostCenterActivityType.CostCenterActivityTypeBuilder costCtrActivityTypeValidCat(@Nullable String costCtrActivityTypeValidCat)
Original property name from the Odata EDM: CostCtrActivityTypeValidCat
Example:Activity type: PCCCost center types: P, SIf you enter "PS" in this field, the activity type can be planned only for cost centers of types P (production cost center) and S (service cost center) and can be drawn upon for use in actual activity allocation.If the activity type is to be valid for all cost center types, enter an asterisk "*", which is the default for all cost center types.
sender in internal activity allocation.this.@Nonnull public CostCenterActivityType build()
Copyright © 2020 SAP SE. All rights reserved.