public static class CostCenter.CostCenterBuilder extends Object
Modifier and Type | Method and Description |
---|---|
CostCenter |
build() |
CostCenter.CostCenterBuilder |
businessArea(String businessArea)
Constraints: Not nullable, Maximum length: 4
|
CostCenter.CostCenterBuilder |
cityName(String cityName)
Constraints: Not nullable, Maximum length: 35
|
CostCenter.CostCenterBuilder |
companyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
CostCenter.CostCenterBuilder |
consumptionQtyIsRecorded(String consumptionQtyIsRecorded)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
controllingArea(String controllingArea)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
CostCenter.CostCenterBuilder |
costCenter(String costCenter)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
CostCenter.CostCenterBuilder |
costCenterCategory(String costCenterCategory)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
costCenterCreatedByUser(String costCenterCreatedByUser)
Constraints: Not nullable, Maximum length: 12
|
CostCenter.CostCenterBuilder |
costCenterCreationDate(LocalDateTime costCenterCreationDate)
Constraints: Not nullable, Precision: 0
|
CostCenter.CostCenterBuilder |
costCenterCurrency(String costCenterCurrency)
Constraints: Not nullable, Maximum length: 5
|
CostCenter.CostCenterBuilder |
costCenterStandardHierArea(String costCenterStandardHierArea)
Constraints: Not nullable, Maximum length: 12
|
CostCenter.CostCenterBuilder |
costCtrResponsiblePersonName(String costCtrResponsiblePersonName)
Constraints: Not nullable, Maximum length: 20
|
CostCenter.CostCenterBuilder |
costCtrResponsibleUser(String costCtrResponsibleUser)
Constraints: Not nullable, Maximum length: 12
|
CostCenter.CostCenterBuilder |
costingSheet(String costingSheet)
Constraints: Not nullable, Maximum length: 6
|
CostCenter.CostCenterBuilder |
country(String country)
Constraints: Not nullable, Maximum length: 3
|
CostCenter.CostCenterBuilder |
department(String department)
Constraints: Not nullable, Maximum length: 12
|
CostCenter.CostCenterBuilder |
functionalArea(String functionalArea)
Constraints: Not nullable, Maximum length: 16
|
CostCenter.CostCenterBuilder |
isBlkdForPrimaryCostsPosting(String isBlkdForPrimaryCostsPosting)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
isBlkdForSecondaryCostsPosting(String isBlkdForSecondaryCostsPosting)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
isBlockedForCommitmentPosting(String isBlockedForCommitmentPosting)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
isBlockedForPlanPrimaryCosts(String isBlockedForPlanPrimaryCosts)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
isBlockedForPlanRevenues(String isBlockedForPlanRevenues)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
isBlockedForPlanSecondaryCosts(String isBlockedForPlanSecondaryCosts)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
isBlockedForRevenuePosting(String isBlockedForRevenuePosting)
Constraints: Not nullable, Maximum length: 1
|
CostCenter.CostCenterBuilder |
language(String language)
Constraints: Not nullable, Maximum length: 2
|
CostCenter.CostCenterBuilder |
profitCenter(String profitCenter)
Constraints: Not nullable, Maximum length: 10
|
CostCenter.CostCenterBuilder |
region(String region)
Constraints: Not nullable, Maximum length: 3
|
String |
toString() |
CostCenter.CostCenterBuilder |
validityEndDate(LocalDateTime validityEndDate)
(Key Field) Constraints: Not nullable, Precision: 0
|
CostCenter.CostCenterBuilder |
validityStartDate(LocalDateTime validityStartDate)
Constraints: Not nullable, Precision: 0
|
public CostCenter.CostCenterBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
public CostCenter.CostCenterBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public CostCenter.CostCenterBuilder validityEndDate(@Nullable LocalDateTime validityEndDate)
Original property name from the Odata EDM: ValidityEndDate
public CostCenter.CostCenterBuilder validityStartDate(@Nullable LocalDateTime validityStartDate)
Original property name from the Odata EDM: ValidityStartDate
public CostCenter.CostCenterBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public CostCenter.CostCenterBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
public CostCenter.CostCenterBuilder costCtrResponsiblePersonName(@Nullable String costCtrResponsiblePersonName)
Original property name from the Odata EDM: CostCtrResponsiblePersonName
public CostCenter.CostCenterBuilder costCtrResponsibleUser(@Nullable String costCtrResponsibleUser)
Original property name from the Odata EDM: CostCtrResponsibleUser
In the Person Responsible field, you can type in the name of the person responsible. No consistency check is performed against the user master record.
stored in the SAP user master record.public CostCenter.CostCenterBuilder costCenterCurrency(@Nullable String costCenterCurrency)
Original property name from the Odata EDM: CostCenterCurrency
public CostCenter.CostCenterBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
public CostCenter.CostCenterBuilder department(@Nullable String department)
Original property name from the Odata EDM: Department
used for evaluations.public CostCenter.CostCenterBuilder costingSheet(@Nullable String costingSheet)
Original property name from the Odata EDM: CostingSheet
You must store one costing sheet for each object for which the R/3 System is to determine overhead costs.For orders, you enter the costing sheet in the order master record.For overhead cost orders the costing sheet can be defaulted through a model order.For CO production orders without quantity structure the costing sheet can be defaulted through a planning profile.For production orders, process orders, produc cost collectors, maintenance orders, regular maintenance orders and service orders the costing sheet is defaulted through a valuation variant.The valuation variant is stored in the costing variant. You can store the costing variant as default value per order type and plant.For cost centers you enter the costing sheet in the master data.For buiness processes you enter the costing sheet in the master data.For projects you enter the costing sheet in the project profile.For materials the R/3 System selects the costing sheet through the valuation variant.For base object plannings, enter the costing sheet in the master data of the costing sheet.For cost object IDs the costing sheet is defaulted through the cost object profile.For cost and revenue carrying sales document items the costing sheet is defaulted through the requirements class.
public CostCenter.CostCenterBuilder functionalArea(@Nullable String functionalArea)
Original property name from the Odata EDM: FunctionalArea
Use for Cost-of-Sales AccountingThe functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting. The following are examples of structure criteria:ManufacturingAdministrationSalesResearch and developmentUse for GovernmentThe functional area is needed for Funds Management to meet legal requirements for reporting with functional aspects. You can use the functional area to represent the global targets and goals (such as public safety or city development), in particular the expenses of your organization.Use in cost-of-sales accountingSee the documentation on Filling the Functional Area Field.For comprehensive information on cost-of-sales accounting and on the functional area, see the SAP Library under Accounting -> Financial Accounting -> General Ledger -> Cost-of-Sales Accounting.Use in governmentFor more information on the functional area, see the implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
public CostCenter.CostCenterBuilder country(@Nullable String country)
Original property name from the Odata EDM: Country
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country-code or a typical country key, for example, in Germany the Federal statistics office key.The country keys are determined at system installation in the global settings.The definition of the country key in the SAP system does not have to match political or government entities.Since the country key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country key cannot query the country key T005-LAND1, but have to program based on the ISO code T005 INTCA.
postal code or bank account number.public CostCenter.CostCenterBuilder region(@Nullable String region)
Original property name from the Odata EDM: Region
The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State
public CostCenter.CostCenterBuilder cityName(@Nullable String cityName)
Original property name from the Odata EDM: CityName
public CostCenter.CostCenterBuilder costCenterStandardHierArea(@Nullable String costCenterStandardHierArea)
Original property name from the Odata EDM: CostCenterStandardHierArea
To create cost centers, you require a structure in master data maintenance to which you can assign cost centers. You create this CO structure, the standard hierarchy, when you create a controlling area. If this hierarchy is not present during controlling area maintenance, the system automatically creates the highest node there.Use group maintenance to construct the structure of the standard hierarchy. This is possible in both application and customizing menus.About the Application MenuAbout the Customizing MenuYou may create as many alternative groups as you wish. You cannot create new cost centers in groups, but you can enter existing cost centers and cost centers that are to be created.The direct assignment to the controlling area guarantees that all cost centers of a controlling area are collected together.
public CostCenter.CostCenterBuilder costCenterCategory(@Nullable String costCenterCategory)
Original property name from the Odata EDM: CostCenterCategory
The master data of an activity type includes one or more cost center categories. The activity type may be used only by cost centers of the appropriate categories.You define categories in Customizing. For each category, you can define default values for the "Lock" and "Record quantity" indicators, for transfer to cost center master data. Maintain these indicators only if the entry diverges from the default cost center category.In addition, you may use the categories for reports and evaluations.Production cost centerService cost centerAdministration cost center
public CostCenter.CostCenterBuilder isBlkdForPrimaryCostsPosting(@Nullable String isBlkdForPrimaryCostsPosting)
Original property name from the Odata EDM: IsBlkdForPrimaryCostsPosting
If the indicator is active, no primary costs can be posted to the cost center. You may, however, still use the cost center for evaluations such as summarization, etc.
public CostCenter.CostCenterBuilder isBlkdForSecondaryCostsPosting(@Nullable String isBlkdForSecondaryCostsPosting)
Original property name from the Odata EDM: IsBlkdForSecondaryCostsPosting
UseIf the indicator is active, you cannot post secondary costs to the cost center from now on.This indicatory normally locks the cost center only against actual debits of secondary costs. However, actual credits to the cost center are possible.To alter the effect of this indicator so that sender cost centers are also locked against allocation, change the type of messsage GM 155 from I (information) to E (error).To do so, access the IMG for General Controlling -> Message Control. Enter GM as the work area. You can then create a new entry for message number 155, which entry differs from the standard message type.Message control
public CostCenter.CostCenterBuilder isBlockedForRevenuePosting(@Nullable String isBlockedForRevenuePosting)
Original property name from the Odata EDM: IsBlockedForRevenuePosting
If the indicator is active, you cannot post revenues to the affected cost center.If the indicator is inactive, the revenues are written to the cost center as statistics only.
public CostCenter.CostCenterBuilder isBlockedForCommitmentPosting(@Nullable String isBlockedForCommitmentPosting)
Original property name from the Odata EDM: IsBlockedForCommitmentPosting
If the indicator is active, no commitments can be updated to the affected cost center.
public CostCenter.CostCenterBuilder isBlockedForPlanPrimaryCosts(@Nullable String isBlockedForPlanPrimaryCosts)
Original property name from the Odata EDM: IsBlockedForPlanPrimaryCosts
If the indicator is active, you cannot plan any primary costs on the affected cost center at this time.
public CostCenter.CostCenterBuilder isBlockedForPlanSecondaryCosts(@Nullable String isBlockedForPlanSecondaryCosts)
Original property name from the Odata EDM: IsBlockedForPlanSecondaryCosts
public CostCenter.CostCenterBuilder isBlockedForPlanRevenues(@Nullable String isBlockedForPlanRevenues)
Original property name from the Odata EDM: IsBlockedForPlanRevenues
public CostCenter.CostCenterBuilder consumptionQtyIsRecorded(@Nullable String consumptionQtyIsRecorded)
Original property name from the Odata EDM: ConsumptionQtyIsRecorded
The indicator has no effect on planning.You can also plan consumption quantities at a later date.The indicator has no effect on quantity updates or on the identification of quantities in reports.You must set the indicator if you want to cost using an overhead that is dependent on the unit of measure posted with this cost element.The indicator is an active default setting for the combination of cost center and cost element if in the master data for the cost center and cost element, it is defined that quantities should be managed.You can specify the recording of quantities in two ways:In the master data for the cost center and cost element, you can activate the Record qty indicator.In the master data, the indicator specifies whether consumption quantities should be recorded for each object (cost center, cost element).You can change the indicator in planning.In planning, the indicator specifies whether consumption quantities are to be recorded for planning values as well as actual values. This is for the object combination to be planned (such as cost center/cost element).A combination of objects is used for planning or actual postings, which means that the effect this has depends on the indicator setting for each object combination.The object combination comes fromThe first planning entriesThe first actual postingIf planning does not exist, the system determines whether the indicator is set for the object combination. It does this by using the logical AND link for the field values in the master record of the corresponding single objects.CautionIf you want to record consumption quantities, you need to specify a quantity and a unit of measure for actual and commitment postings.For the first posting in a fiscal year to an object using a particular cost element, specify the following for the object and the corresponding cost element:Whether quantities are to be recorded in the totals recordsWhich unit of measure is to be used for recording the quantitiesOnce you have specified this for the relevant fiscal year, you cannot change it.Specify a different unit of measure for a later posting.If you can convert the unit of measure using that of the first posting (such as kilograms into tons), then- The system converts the units of measure accordingly- The system displays the posted quantities using the unit of measure that you specified for the first posting.If the unit of measure cannot be converted (such as hours into pieces), then- The system does not update any quantities after this posting- The system does not display any quantities in the information system- The system displays the posted quantities in the line items using the corresponding posted unit of measure.
commitment or actual postings.public CostCenter.CostCenterBuilder language(@Nullable String language)
Original property name from the Odata EDM: Language
- the language in which texts are displayed,- the language in which you enter texts,- the language in which the system prints texts.
public CostCenter.CostCenterBuilder costCenterCreatedByUser(@Nullable String costCenterCreatedByUser)
Original property name from the Odata EDM: CostCenterCreatedByUser
public CostCenter.CostCenterBuilder costCenterCreationDate(@Nullable LocalDateTime costCenterCreationDate)
Original property name from the Odata EDM: CostCenterCreationDate
public CostCenter build()
Copyright © 2019 SAP SE. All rights reserved.