public class CostCenter extends VdmEntity<CostCenter>
Original entity name from the Odata EDM: A_CostCenterType
Modifier and Type | Class and Description |
---|---|
static class |
CostCenter.CostCenterBuilder |
Modifier and Type | Field and Description |
---|---|
static CostCenterSelectable |
ALL_FIELDS
Selector for all available fields of CostCenter.
|
static CostCenterField<String> |
BUSINESS_AREA
Use with available fluent helpers to apply the BusinessArea field to query operations.
|
static CostCenterField<String> |
CITY_NAME
Use with available fluent helpers to apply the CityName field to query operations.
|
static CostCenterField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static CostCenterField<String> |
CONSUMPTION_QTY_IS_RECORDED
Use with available fluent helpers to apply the ConsumptionQtyIsRecorded field to query operations.
|
static CostCenterField<String> |
CONTROLLING_AREA
Use with available fluent helpers to apply the ControllingArea field to query operations.
|
static CostCenterField<String> |
COST_CENTER
Use with available fluent helpers to apply the CostCenter field to query operations.
|
static CostCenterField<String> |
COST_CENTER_CATEGORY
Use with available fluent helpers to apply the CostCenterCategory field to query operations.
|
static CostCenterField<String> |
COST_CENTER_CREATED_BY_USER
Use with available fluent helpers to apply the CostCenterCreatedByUser field to query operations.
|
static CostCenterField<LocalDateTime> |
COST_CENTER_CREATION_DATE
Use with available fluent helpers to apply the CostCenterCreationDate field to query operations.
|
static CostCenterField<String> |
COST_CENTER_CURRENCY
Use with available fluent helpers to apply the CostCenterCurrency field to query operations.
|
static CostCenterField<String> |
COST_CENTER_STANDARD_HIER_AREA
Use with available fluent helpers to apply the CostCenterStandardHierArea field to query operations.
|
static CostCenterField<String> |
COST_CTR_RESPONSIBLE_PERSON_NAME
Use with available fluent helpers to apply the CostCtrResponsiblePersonName field to query operations.
|
static CostCenterField<String> |
COST_CTR_RESPONSIBLE_USER
Use with available fluent helpers to apply the CostCtrResponsibleUser field to query operations.
|
static CostCenterField<String> |
COSTING_SHEET
Use with available fluent helpers to apply the CostingSheet field to query operations.
|
static CostCenterField<String> |
COUNTRY
Use with available fluent helpers to apply the Country field to query operations.
|
static CostCenterField<String> |
DEPARTMENT
Use with available fluent helpers to apply the Department field to query operations.
|
static CostCenterField<String> |
FUNCTIONAL_AREA
Use with available fluent helpers to apply the FunctionalArea field to query operations.
|
static CostCenterField<String> |
IS_BLKD_FOR_PRIMARY_COSTS_POSTING
Use with available fluent helpers to apply the IsBlkdForPrimaryCostsPosting field to query operations.
|
static CostCenterField<String> |
IS_BLKD_FOR_SECONDARY_COSTS_POSTING
Use with available fluent helpers to apply the IsBlkdForSecondaryCostsPosting field to query operations.
|
static CostCenterField<String> |
IS_BLOCKED_FOR_COMMITMENT_POSTING
Use with available fluent helpers to apply the IsBlockedForCommitmentPosting field to query operations.
|
static CostCenterField<String> |
IS_BLOCKED_FOR_PLAN_PRIMARY_COSTS
Use with available fluent helpers to apply the IsBlockedForPlanPrimaryCosts field to query operations.
|
static CostCenterField<String> |
IS_BLOCKED_FOR_PLAN_REVENUES
Use with available fluent helpers to apply the IsBlockedForPlanRevenues field to query operations.
|
static CostCenterField<String> |
IS_BLOCKED_FOR_PLAN_SECONDARY_COSTS
Use with available fluent helpers to apply the IsBlockedForPlanSecondaryCosts field to query operations.
|
static CostCenterField<String> |
IS_BLOCKED_FOR_REVENUE_POSTING
Use with available fluent helpers to apply the IsBlockedForRevenuePosting field to query operations.
|
static CostCenterField<String> |
LANGUAGE
Use with available fluent helpers to apply the Language field to query operations.
|
static CostCenterField<String> |
PROFIT_CENTER
Use with available fluent helpers to apply the ProfitCenter field to query operations.
|
static CostCenterField<String> |
REGION
Use with available fluent helpers to apply the Region field to query operations.
|
static CostCenterLink<CostCenterText> |
TO_TEXT
Use with available fluent helpers to apply the to_Text navigation property to query operations.
|
static CostCenterField<LocalDateTime> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static CostCenterField<LocalDateTime> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
CostCenter() |
CostCenter(String controllingArea,
String costCenter,
LocalDateTime validityEndDate,
LocalDateTime validityStartDate,
String companyCode,
String businessArea,
String costCtrResponsiblePersonName,
String costCtrResponsibleUser,
String costCenterCurrency,
String profitCenter,
String department,
String costingSheet,
String functionalArea,
String country,
String region,
String cityName,
String costCenterStandardHierArea,
String costCenterCategory,
String isBlkdForPrimaryCostsPosting,
String isBlkdForSecondaryCostsPosting,
String isBlockedForRevenuePosting,
String isBlockedForCommitmentPosting,
String isBlockedForPlanPrimaryCosts,
String isBlockedForPlanSecondaryCosts,
String isBlockedForPlanRevenues,
String consumptionQtyIsRecorded,
String language,
String costCenterCreatedByUser,
LocalDateTime costCenterCreationDate,
ErpConfigContext erpConfigContext,
List<CostCenterText> toText) |
Modifier and Type | Method and Description |
---|---|
void |
addText(CostCenterText... entity)
Adds elements to the list of associated CostCenterText entities.
|
static CostCenter.CostCenterBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<CostCenterText> |
fetchText()
Fetches the CostCenterText entities (one to many) associated with this entity.
|
static <T> CostCenterField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getBusinessArea()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessArea
|
String |
getCityName()
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: CityName
|
String |
getCompanyCode()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CompanyCode
|
String |
getConsumptionQtyIsRecorded()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: ConsumptionQtyIsRecordedThe indicator has no effect on planning.
|
String |
getControllingArea()
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ControllingAreaThe controlling area is the highest organizational unit in Controlling.
|
String |
getCostCenter()
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostCenter
|
String |
getCostCenterCategory()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: CostCenterCategoryThe master data of an activity type includes one or more cost center categories.
|
String |
getCostCenterCreatedByUser()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostCenterCreatedByUser
|
LocalDateTime |
getCostCenterCreationDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CostCenterCreationDate
|
String |
getCostCenterCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: CostCenterCurrency
|
String |
getCostCenterStandardHierArea()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostCenterStandardHierAreaTo create cost centers, you require a structure in master data maintenance to which you can assign cost centers.
|
String |
getCostCtrResponsiblePersonName()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: CostCtrResponsiblePersonName
|
String |
getCostCtrResponsibleUser()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostCtrResponsibleUserIn the Person Responsible field, you can type in the name of the person responsible.
|
String |
getCostingSheet()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: CostingSheetYou must store one costing sheet for each object for which the R/3 System is to determine overhead costs.
|
String |
getCountry()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: CountryThe two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.
|
String |
getDepartment()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: Department
|
protected String |
getEndpointUrl() |
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
String |
getFunctionalArea()
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: FunctionalAreaUse for Cost-of-Sales Accounting
The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting.
|
String |
getIsBlkdForPrimaryCostsPosting()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlkdForPrimaryCostsPostingIf the indicator is active, no primary costs can be posted to the cost center.
|
String |
getIsBlkdForSecondaryCostsPosting()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlkdForSecondaryCostsPostingUse
If the indicator is active, you cannot post secondary costs to the cost center from now on.
|
String |
getIsBlockedForCommitmentPosting()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForCommitmentPostingIf the indicator is active, no commitments can be updated to the affected cost center.
|
String |
getIsBlockedForPlanPrimaryCosts()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForPlanPrimaryCostsIf the indicator is active, you cannot plan any primary costs on the affected cost center at this time.
|
String |
getIsBlockedForPlanRevenues()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForPlanRevenues
|
String |
getIsBlockedForPlanSecondaryCosts()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForPlanSecondaryCosts
|
String |
getIsBlockedForRevenuePosting()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForRevenuePostingIf the indicator is active, you cannot post revenues to the affected cost center.
|
protected Map<String,Object> |
getKey() |
String |
getLanguage()
Constraints: Not nullable, Maximum length: 2 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.
|
String |
getProfitCenter()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProfitCenter
|
String |
getRegion()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RegionThe automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.
|
Optional<List<CostCenterText>> |
getTextIfPresent()
Retrieval of associated CostCenterText entities (one to many).
|
List<CostCenterText> |
getTextOrFetch()
Retrieval of associated CostCenterText entities (one to many).
|
Class<CostCenter> |
getType() |
LocalDateTime |
getValidityEndDate()
(Key Field) Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityEndDate
|
LocalDateTime |
getValidityStartDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityStartDate
|
int |
hashCode() |
void |
setBusinessArea(String businessArea)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessArea
|
void |
setCityName(String cityName)
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: CityName
|
void |
setCompanyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CompanyCode
|
void |
setConsumptionQtyIsRecorded(String consumptionQtyIsRecorded)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: ConsumptionQtyIsRecordedThe indicator has no effect on planning.
|
void |
setControllingArea(String controllingArea)
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ControllingAreaThe controlling area is the highest organizational unit in Controlling.
|
void |
setCostCenter(String costCenter)
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostCenter
|
void |
setCostCenterCategory(String costCenterCategory)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: CostCenterCategoryThe master data of an activity type includes one or more cost center categories.
|
void |
setCostCenterCreatedByUser(String costCenterCreatedByUser)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostCenterCreatedByUser
|
void |
setCostCenterCreationDate(LocalDateTime costCenterCreationDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CostCenterCreationDate
|
void |
setCostCenterCurrency(String costCenterCurrency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: CostCenterCurrency
|
void |
setCostCenterStandardHierArea(String costCenterStandardHierArea)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostCenterStandardHierAreaTo create cost centers, you require a structure in master data maintenance to which you can assign cost centers.
|
void |
setCostCtrResponsiblePersonName(String costCtrResponsiblePersonName)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: CostCtrResponsiblePersonName
|
void |
setCostCtrResponsibleUser(String costCtrResponsibleUser)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostCtrResponsibleUserIn the Person Responsible field, you can type in the name of the person responsible.
|
void |
setCostingSheet(String costingSheet)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: CostingSheetYou must store one costing sheet for each object for which the R/3 System is to determine overhead costs.
|
void |
setCountry(String country)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: CountryThe two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.
|
void |
setDepartment(String department)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: Department
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setFunctionalArea(String functionalArea)
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: FunctionalAreaUse for Cost-of-Sales Accounting
The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting.
|
void |
setIsBlkdForPrimaryCostsPosting(String isBlkdForPrimaryCostsPosting)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlkdForPrimaryCostsPostingIf the indicator is active, no primary costs can be posted to the cost center.
|
void |
setIsBlkdForSecondaryCostsPosting(String isBlkdForSecondaryCostsPosting)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlkdForSecondaryCostsPostingUse
If the indicator is active, you cannot post secondary costs to the cost center from now on.
|
void |
setIsBlockedForCommitmentPosting(String isBlockedForCommitmentPosting)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForCommitmentPostingIf the indicator is active, no commitments can be updated to the affected cost center.
|
void |
setIsBlockedForPlanPrimaryCosts(String isBlockedForPlanPrimaryCosts)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForPlanPrimaryCostsIf the indicator is active, you cannot plan any primary costs on the affected cost center at this time.
|
void |
setIsBlockedForPlanRevenues(String isBlockedForPlanRevenues)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForPlanRevenues
|
void |
setIsBlockedForPlanSecondaryCosts(String isBlockedForPlanSecondaryCosts)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForPlanSecondaryCosts
|
void |
setIsBlockedForRevenuePosting(String isBlockedForRevenuePosting)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsBlockedForRevenuePostingIf the indicator is active, you cannot post revenues to the affected cost center.
|
void |
setLanguage(String language)
Constraints: Not nullable, Maximum length: 2 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.
|
void |
setProfitCenter(String profitCenter)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProfitCenter
|
void |
setRegion(String region)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RegionThe automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.
|
void |
setText(List<CostCenterText> value)
Overwrites the list of associated CostCenterText entities for the loaded navigation property to_Text.
|
void |
setValidityEndDate(LocalDateTime validityEndDate)
(Key Field) Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityEndDate
|
void |
setValidityStartDate(LocalDateTime validityStartDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValidityStartDate
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final CostCenterSelectable ALL_FIELDS
public static final CostCenterField<String> CONTROLLING_AREA
public static final CostCenterField<String> COST_CENTER
public static final CostCenterField<LocalDateTime> VALIDITY_END_DATE
public static final CostCenterField<LocalDateTime> VALIDITY_START_DATE
public static final CostCenterField<String> COMPANY_CODE
public static final CostCenterField<String> BUSINESS_AREA
public static final CostCenterField<String> COST_CTR_RESPONSIBLE_PERSON_NAME
public static final CostCenterField<String> COST_CTR_RESPONSIBLE_USER
public static final CostCenterField<String> COST_CENTER_CURRENCY
public static final CostCenterField<String> PROFIT_CENTER
public static final CostCenterField<String> DEPARTMENT
public static final CostCenterField<String> COSTING_SHEET
public static final CostCenterField<String> FUNCTIONAL_AREA
public static final CostCenterField<String> COUNTRY
public static final CostCenterField<String> REGION
public static final CostCenterField<String> CITY_NAME
public static final CostCenterField<String> COST_CENTER_STANDARD_HIER_AREA
public static final CostCenterField<String> COST_CENTER_CATEGORY
public static final CostCenterField<String> IS_BLKD_FOR_PRIMARY_COSTS_POSTING
public static final CostCenterField<String> IS_BLKD_FOR_SECONDARY_COSTS_POSTING
public static final CostCenterField<String> IS_BLOCKED_FOR_REVENUE_POSTING
public static final CostCenterField<String> IS_BLOCKED_FOR_COMMITMENT_POSTING
public static final CostCenterField<String> IS_BLOCKED_FOR_PLAN_PRIMARY_COSTS
public static final CostCenterField<String> IS_BLOCKED_FOR_PLAN_SECONDARY_COSTS
public static final CostCenterField<String> IS_BLOCKED_FOR_PLAN_REVENUES
public static final CostCenterField<String> CONSUMPTION_QTY_IS_RECORDED
public static final CostCenterField<String> LANGUAGE
public static final CostCenterField<String> COST_CENTER_CREATED_BY_USER
public static final CostCenterField<LocalDateTime> COST_CENTER_CREATION_DATE
public static final CostCenterLink<CostCenterText> TO_TEXT
public CostCenter()
public CostCenter(@Nullable String controllingArea, @Nullable String costCenter, @Nullable LocalDateTime validityEndDate, @Nullable LocalDateTime validityStartDate, @Nullable String companyCode, @Nullable String businessArea, @Nullable String costCtrResponsiblePersonName, @Nullable String costCtrResponsibleUser, @Nullable String costCenterCurrency, @Nullable String profitCenter, @Nullable String department, @Nullable String costingSheet, @Nullable String functionalArea, @Nullable String country, @Nullable String region, @Nullable String cityName, @Nullable String costCenterStandardHierArea, @Nullable String costCenterCategory, @Nullable String isBlkdForPrimaryCostsPosting, @Nullable String isBlkdForSecondaryCostsPosting, @Nullable String isBlockedForRevenuePosting, @Nullable String isBlockedForCommitmentPosting, @Nullable String isBlockedForPlanPrimaryCosts, @Nullable String isBlockedForPlanSecondaryCosts, @Nullable String isBlockedForPlanRevenues, @Nullable String consumptionQtyIsRecorded, @Nullable String language, @Nullable String costCenterCreatedByUser, @Nullable LocalDateTime costCenterCreationDate, @Nullable ErpConfigContext erpConfigContext, List<CostCenterText> toText)
public Class<CostCenter> getType()
getType
in class VdmObject<CostCenter>
public void setControllingArea(@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.
controllingArea
- Uniquely identifies a controlling area.public void setCostCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
costCenter
- A key that uniquely identifies a cost center.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 setCompanyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
companyCode
- The company code is an organizational unit within financial accounting.public void setBusinessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
businessArea
- Key that uniquely identifies a business area.public void setCostCtrResponsiblePersonName(@Nullable String costCtrResponsiblePersonName)
Original property name from the Odata EDM: CostCtrResponsiblePersonName
costCtrResponsiblePersonName
- Person responsible for the given cost center.public void setCostCtrResponsibleUser(@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.
costCtrResponsibleUser
- In this field, you can enter the user ID of the person responsible for the cost center. This user ID is stored in the SAP user master record.public void setCostCenterCurrency(@Nullable String costCenterCurrency)
Original property name from the Odata EDM: CostCenterCurrency
costCenterCurrency
- Currency key for amounts in the system.public void setProfitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
profitCenter
- Key which together with the controlling area uniquely identifies a profit center.public void setDepartment(@Nullable String department)
Original property name from the Odata EDM: Department
department
- In this field, you can enter the name of the department to which the cost center belongs. It then can be used for evaluations.public void setCostingSheet(@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.
costingSheet
- Controls the calculation of overhead.public void setFunctionalArea(@Nullable String functionalArea)
Original property name from the Odata EDM: FunctionalArea
Use for Cost-of-Sales Accounting The 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: Manufacturing Administration Sales Research and development Use for Government The 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 accounting See 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 government For more information on the functional area, see the implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
functionalArea
- Structure criterion for an enterprise or government based on functional aspects.public void setCountry(@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.
country
- The country key contains information which the system uses to check entries such as the length of the postal code or bank account number.public void setRegion(@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 -> Province Brazil -> State Canada -> Province Germany -> State Great Britain -> County Italy -> Province Japan -> Prefecture Switzerland -> Canton USA -> State
region
- In some countries, the region forms part of the address. The meaning depends on the country.public void setCityName(@Nullable String cityName)
Original property name from the Odata EDM: CityName
cityName
- Name of the city as a part of the address.public void setCostCenterStandardHierArea(@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 Menu About the Customizing Menu You 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.
costCenterStandardHierArea
- Standard hierarchypublic void setCostCenterCategory(@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 center Service cost center Administration cost center
costCenterCategory
- Indicator used to define a cost center category.public void setIsBlkdForPrimaryCostsPosting(@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.
isBlkdForPrimaryCostsPosting
- Indicator defining whether a cost center is locked for posting with direct costs.public void setIsBlkdForSecondaryCostsPosting(@Nullable String isBlkdForSecondaryCostsPosting)
Original property name from the Odata EDM: IsBlkdForSecondaryCostsPosting
Use If 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
isBlkdForSecondaryCostsPosting
- Indicator controlling whether the cost center is locked against postings of secondary costspublic void setIsBlockedForRevenuePosting(@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.
isBlockedForRevenuePosting
- Indicator defining whether a cost center is locked for posting with revenues.public void setIsBlockedForCommitmentPosting(@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.
isBlockedForCommitmentPosting
- Indicator defining whether a commitment is updated for the cost center.public void setIsBlockedForPlanPrimaryCosts(@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.
isBlockedForPlanPrimaryCosts
- Indicator defining whether a cost center is locked for planning with direct costs.public void setIsBlockedForPlanSecondaryCosts(@Nullable String isBlockedForPlanSecondaryCosts)
Original property name from the Odata EDM: IsBlockedForPlanSecondaryCosts
isBlockedForPlanSecondaryCosts
- Lock Indicator for Plan Secondary Costspublic void setIsBlockedForPlanRevenues(@Nullable String isBlockedForPlanRevenues)
Original property name from the Odata EDM: IsBlockedForPlanRevenues
isBlockedForPlanRevenues
- Lock Indicator for Planning Revenuespublic void setConsumptionQtyIsRecorded(@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 from The first planning entries The first actual posting If 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. Caution If 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 records Which unit of measure is to be used for recording the quantities Once 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.
consumptionQtyIsRecorded
- Indicator defining whether the system issues a message if no quantity or quantity unit is specified for commitment or actual postings.public void setLanguage(@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.
language
- The language key indicatespublic void setCostCenterCreatedByUser(@Nullable String costCenterCreatedByUser)
Original property name from the Odata EDM: CostCenterCreatedByUser
costCenterCreatedByUser
- User ID of the person who created the cost estimate.public void setCostCenterCreationDate(@Nullable LocalDateTime costCenterCreationDate)
Original property name from the Odata EDM: CostCenterCreationDate
costCenterCreationDate
- Date on which the cost estimate was created.protected String getEndpointUrl()
getEndpointUrl
in class VdmEntity<CostCenter>
protected String getEntityCollection()
getEntityCollection
in class VdmEntity<CostCenter>
protected Map<String,Object> getKey()
getKey
in class VdmObject<CostCenter>
protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<CostCenter>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<CostCenter>
public static <T> CostCenterField<T> field(String fieldName, Class<T> fieldType)
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.protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<CostCenter>
public List<CostCenterText> 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.public List<CostCenterText> getTextOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Text of a queried CostCenter 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.public Optional<List<CostCenterText>> getTextIfPresent()
If the navigation property for an entity CostCenter 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<CostCenterText> value)
If the navigation property to_Text of a queried CostCenter 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 CostCenterText entities.public void addText(CostCenterText... entity)
If the navigation property to_Text of a queried CostCenter 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 CostCenterText entities.public static CostCenter.CostCenterBuilder builder()
@Nullable public String getControllingArea()
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.
@Nullable public String getCostCenter()
Original property name from the Odata EDM: CostCenter
@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 getCompanyCode()
Original property name from the Odata EDM: CompanyCode
@Nullable public String getBusinessArea()
Original property name from the Odata EDM: BusinessArea
@Nullable public String getCostCtrResponsiblePersonName()
Original property name from the Odata EDM: CostCtrResponsiblePersonName
@Nullable public String getCostCtrResponsibleUser()
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.
@Nullable public String getCostCenterCurrency()
Original property name from the Odata EDM: CostCenterCurrency
@Nullable public String getProfitCenter()
Original property name from the Odata EDM: ProfitCenter
@Nullable public String getDepartment()
Original property name from the Odata EDM: Department
@Nullable public String getCostingSheet()
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.
@Nullable public String getFunctionalArea()
Original property name from the Odata EDM: FunctionalArea
Use for Cost-of-Sales Accounting The 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: Manufacturing Administration Sales Research and development Use for Government The 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 accounting See 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 government For more information on the functional area, see the implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
@Nullable public String getCountry()
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.
@Nullable public String getRegion()
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 -> Province Brazil -> State Canada -> Province Germany -> State Great Britain -> County Italy -> Province Japan -> Prefecture Switzerland -> Canton USA -> State
@Nullable public String getCityName()
Original property name from the Odata EDM: CityName
@Nullable public String getCostCenterStandardHierArea()
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 Menu About the Customizing Menu You 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.
@Nullable public String getCostCenterCategory()
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 center Service cost center Administration cost center
@Nullable public String getIsBlkdForPrimaryCostsPosting()
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.
@Nullable public String getIsBlkdForSecondaryCostsPosting()
Original property name from the Odata EDM: IsBlkdForSecondaryCostsPosting
Use If 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
@Nullable public String getIsBlockedForRevenuePosting()
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.
@Nullable public String getIsBlockedForCommitmentPosting()
Original property name from the Odata EDM: IsBlockedForCommitmentPosting
If the indicator is active, no commitments can be updated to the affected cost center.
@Nullable public String getIsBlockedForPlanPrimaryCosts()
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.
@Nullable public String getIsBlockedForPlanSecondaryCosts()
Original property name from the Odata EDM: IsBlockedForPlanSecondaryCosts
@Nullable public String getIsBlockedForPlanRevenues()
Original property name from the Odata EDM: IsBlockedForPlanRevenues
@Nullable public String getConsumptionQtyIsRecorded()
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 from The first planning entries The first actual posting If 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. Caution If 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 records Which unit of measure is to be used for recording the quantities Once 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.
@Nullable public String getLanguage()
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.
@Nullable public String getCostCenterCreatedByUser()
Original property name from the Odata EDM: CostCenterCreatedByUser
@Nullable public LocalDateTime getCostCenterCreationDate()
Original property name from the Odata EDM: CostCenterCreationDate
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<CostCenter>
erpConfigContext
- public String toString()
toString
in class VdmObject<CostCenter>
public boolean equals(Object o)
equals
in class VdmObject<CostCenter>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<CostCenter>
public int hashCode()
hashCode
in class VdmObject<CostCenter>
Copyright © 2018 SAP SE. All rights reserved.