public class CostCenter extends VdmEntity<CostCenter>
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<Calendar> |
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 CostCenterField<Calendar> |
VALIDITY_END_DATE
Use with available fluent helpers to apply the ValidityEndDate field to query operations.
|
static CostCenterField<Calendar> |
VALIDITY_START_DATE
Use with available fluent helpers to apply the ValidityStartDate field to query operations.
|
Constructor and Description |
---|
CostCenter() |
CostCenter(String controllingArea,
String costCenter,
Calendar validityEndDate,
Calendar 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,
Calendar costCenterCreationDate,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
static CostCenter.CostCenterBuilder |
builder() |
boolean |
equals(Object o) |
static <T> CostCenterField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getBusinessArea()
Constraints: Not nullable, Maximum length: 4
|
String |
getCityName()
Constraints: Not nullable, Maximum length: 35
|
String |
getCompanyCode()
Constraints: Not nullable, Maximum length: 4
|
String |
getConsumptionQtyIsRecorded()
Constraints: Not nullable, Maximum length: 1
|
String |
getControllingArea()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getCostCenter()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getCostCenterCategory()
Constraints: Not nullable, Maximum length: 1
|
String |
getCostCenterCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
Calendar |
getCostCenterCreationDate()
Constraints: Not nullable, Precision: 0
|
String |
getCostCenterCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getCostCenterStandardHierArea()
Constraints: Not nullable, Maximum length: 12
|
String |
getCostCtrResponsiblePersonName()
Constraints: Not nullable, Maximum length: 20
|
String |
getCostCtrResponsibleUser()
Constraints: Not nullable, Maximum length: 12
|
String |
getCostingSheet()
Constraints: Not nullable, Maximum length: 6
|
String |
getCountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getDepartment()
Constraints: Not nullable, Maximum length: 12
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getFunctionalArea()
Constraints: Not nullable, Maximum length: 16
|
String |
getIsBlkdForPrimaryCostsPosting()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsBlkdForSecondaryCostsPosting()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsBlockedForCommitmentPosting()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsBlockedForPlanPrimaryCosts()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsBlockedForPlanRevenues()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsBlockedForPlanSecondaryCosts()
Constraints: Not nullable, Maximum length: 1
|
String |
getIsBlockedForRevenuePosting()
Constraints: Not nullable, Maximum length: 1
|
String |
getLanguage()
Constraints: Not nullable, Maximum length: 2
|
String |
getProfitCenter()
Constraints: Not nullable, Maximum length: 10
|
String |
getRegion()
Constraints: Not nullable, Maximum length: 3
|
Class<CostCenter> |
getType() |
Calendar |
getValidityEndDate()
(Key Field) Constraints: Not nullable, Precision: 0
|
Calendar |
getValidityStartDate()
Constraints: Not nullable, Precision: 0
|
int |
hashCode() |
void |
setBusinessArea(String businessArea)
Constraints: Not nullable, Maximum length: 4
|
void |
setCityName(String cityName)
Constraints: Not nullable, Maximum length: 35
|
void |
setCompanyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setConsumptionQtyIsRecorded(String consumptionQtyIsRecorded)
Constraints: Not nullable, Maximum length: 1
|
void |
setControllingArea(String controllingArea)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setCostCenter(String costCenter)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setCostCenterCategory(String costCenterCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setCostCenterCreatedByUser(String costCenterCreatedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCostCenterCreationDate(Calendar costCenterCreationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCostCenterCurrency(String costCenterCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setCostCenterStandardHierArea(String costCenterStandardHierArea)
Constraints: Not nullable, Maximum length: 12
|
void |
setCostCtrResponsiblePersonName(String costCtrResponsiblePersonName)
Constraints: Not nullable, Maximum length: 20
|
void |
setCostCtrResponsibleUser(String costCtrResponsibleUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCostingSheet(String costingSheet)
Constraints: Not nullable, Maximum length: 6
|
void |
setCountry(String country)
Constraints: Not nullable, Maximum length: 3
|
void |
setDepartment(String department)
Constraints: Not nullable, Maximum length: 12
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setFunctionalArea(String functionalArea)
Constraints: Not nullable, Maximum length: 16
|
void |
setIsBlkdForPrimaryCostsPosting(String isBlkdForPrimaryCostsPosting)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsBlkdForSecondaryCostsPosting(String isBlkdForSecondaryCostsPosting)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsBlockedForCommitmentPosting(String isBlockedForCommitmentPosting)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsBlockedForPlanPrimaryCosts(String isBlockedForPlanPrimaryCosts)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsBlockedForPlanRevenues(String isBlockedForPlanRevenues)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsBlockedForPlanSecondaryCosts(String isBlockedForPlanSecondaryCosts)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsBlockedForRevenuePosting(String isBlockedForRevenuePosting)
Constraints: Not nullable, Maximum length: 1
|
void |
setLanguage(String language)
Constraints: Not nullable, Maximum length: 2
|
void |
setProfitCenter(String profitCenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setRegion(String region)
Constraints: Not nullable, Maximum length: 3
|
void |
setValidityEndDate(Calendar validityEndDate)
(Key Field) Constraints: Not nullable, Precision: 0
|
void |
setValidityStartDate(Calendar validityStartDate)
Constraints: Not nullable, Precision: 0
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField
public static final CostCenterSelectable ALL_FIELDS
public static final CostCenterField<String> CONTROLLING_AREA
public static final CostCenterField<String> COST_CENTER
public static final CostCenterField<Calendar> VALIDITY_END_DATE
public static final CostCenterField<Calendar> 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<Calendar> COST_CENTER_CREATION_DATE
@Generated(value="lombok") public CostCenter()
@ConstructorProperties(value={"controllingArea","costCenter","validityEndDate","validityStartDate","companyCode","businessArea","costCtrResponsiblePersonName","costCtrResponsibleUser","costCenterCurrency","profitCenter","department","costingSheet","functionalArea","country","region","cityName","costCenterStandardHierArea","costCenterCategory","isBlkdForPrimaryCostsPosting","isBlkdForSecondaryCostsPosting","isBlockedForRevenuePosting","isBlockedForCommitmentPosting","isBlockedForPlanPrimaryCosts","isBlockedForPlanSecondaryCosts","isBlockedForPlanRevenues","consumptionQtyIsRecorded","language","costCenterCreatedByUser","costCenterCreationDate","erpConfigContext"}) @Generated(value="lombok") public CostCenter(@Nullable String controllingArea, @Nullable String costCenter, @Nullable Calendar validityEndDate, @Nullable Calendar 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 Calendar costCenterCreationDate, @Nullable ErpConfigContext erpConfigContext)
public Class<CostCenter> getType()
getType
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.@Generated(value="lombok") public static CostCenter.CostCenterBuilder builder()
@Nullable @Generated(value="lombok") public String getControllingArea()
The controlling area is the highest organizational unit in Controlling. Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
@Nullable @Generated(value="lombok") public String getCostCenter()
@Nullable @Generated(value="lombok") public Calendar getValidityEndDate()
@Nullable @Generated(value="lombok") public Calendar getValidityStartDate()
@Nullable @Generated(value="lombok") public String getCompanyCode()
@Nullable @Generated(value="lombok") public String getBusinessArea()
@Nullable @Generated(value="lombok") public String getCostCtrResponsiblePersonName()
@Nullable @Generated(value="lombok") public String getCostCtrResponsibleUser()
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 @Generated(value="lombok") public String getCostCenterCurrency()
@Nullable @Generated(value="lombok") public String getProfitCenter()
@Nullable @Generated(value="lombok") public String getDepartment()
@Nullable @Generated(value="lombok") public String getCostingSheet()
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 @Generated(value="lombok") public String getFunctionalArea()
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 @Generated(value="lombok") public String getCountry()
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 @Generated(value="lombok") public String getRegion()
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 @Generated(value="lombok") public String getCityName()
@Nullable @Generated(value="lombok") public String getCostCenterStandardHierArea()
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 @Generated(value="lombok") public String getCostCenterCategory()
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 @Generated(value="lombok") public String getIsBlkdForPrimaryCostsPosting()
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 @Generated(value="lombok") public String getIsBlkdForSecondaryCostsPosting()
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 @Generated(value="lombok") public String getIsBlockedForRevenuePosting()
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 @Generated(value="lombok") public String getIsBlockedForCommitmentPosting()
If the indicator is active, no commitments can be updated to the affected cost center.
@Nullable @Generated(value="lombok") public String getIsBlockedForPlanPrimaryCosts()
If the indicator is active, you cannot plan any primary costs on the affected cost center at this time.
@Nullable @Generated(value="lombok") public String getIsBlockedForPlanSecondaryCosts()
@Nullable @Generated(value="lombok") public String getIsBlockedForPlanRevenues()
@Nullable @Generated(value="lombok") public String getConsumptionQtyIsRecorded()
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 @Generated(value="lombok") public String getLanguage()
- the language in which texts are displayed, - the language in which you enter texts, - the language in which the system prints texts.
@Nullable @Generated(value="lombok") public String getCostCenterCreatedByUser()
@Nullable @Generated(value="lombok") public Calendar getCostCenterCreationDate()
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setControllingArea(@Nullable String controllingArea)
The controlling area is the highest organizational unit in Controlling. Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
controllingArea
- @Generated(value="lombok") public void setCostCenter(@Nullable String costCenter)
costCenter
- @Generated(value="lombok") public void setValidityEndDate(@Nullable Calendar validityEndDate)
validityEndDate
- @Generated(value="lombok") public void setValidityStartDate(@Nullable Calendar validityStartDate)
validityStartDate
- @Generated(value="lombok") public void setCompanyCode(@Nullable String companyCode)
companyCode
- @Generated(value="lombok") public void setBusinessArea(@Nullable String businessArea)
businessArea
- @Generated(value="lombok") public void setCostCtrResponsiblePersonName(@Nullable String costCtrResponsiblePersonName)
costCtrResponsiblePersonName
- @Generated(value="lombok") public void setCostCtrResponsibleUser(@Nullable String 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
- @Generated(value="lombok") public void setCostCenterCurrency(@Nullable String costCenterCurrency)
costCenterCurrency
- @Generated(value="lombok") public void setProfitCenter(@Nullable String profitCenter)
profitCenter
- @Generated(value="lombok") public void setDepartment(@Nullable String department)
department
- @Generated(value="lombok") public void setCostingSheet(@Nullable String 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
- @Generated(value="lombok") public void setFunctionalArea(@Nullable String 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
- @Generated(value="lombok") public void setCountry(@Nullable String 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
- @Generated(value="lombok") public void setRegion(@Nullable String 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
- @Generated(value="lombok") public void setCityName(@Nullable String cityName)
cityName
- @Generated(value="lombok") public void setCostCenterStandardHierArea(@Nullable String 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
- @Generated(value="lombok") public void setCostCenterCategory(@Nullable String 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
- @Generated(value="lombok") public void setIsBlkdForPrimaryCostsPosting(@Nullable String 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
- @Generated(value="lombok") public void setIsBlkdForSecondaryCostsPosting(@Nullable String 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
- @Generated(value="lombok") public void setIsBlockedForRevenuePosting(@Nullable String 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
- @Generated(value="lombok") public void setIsBlockedForCommitmentPosting(@Nullable String isBlockedForCommitmentPosting)
If the indicator is active, no commitments can be updated to the affected cost center.
isBlockedForCommitmentPosting
- @Generated(value="lombok") public void setIsBlockedForPlanPrimaryCosts(@Nullable String isBlockedForPlanPrimaryCosts)
If the indicator is active, you cannot plan any primary costs on the affected cost center at this time.
isBlockedForPlanPrimaryCosts
- @Generated(value="lombok") public void setIsBlockedForPlanSecondaryCosts(@Nullable String isBlockedForPlanSecondaryCosts)
isBlockedForPlanSecondaryCosts
- @Generated(value="lombok") public void setIsBlockedForPlanRevenues(@Nullable String isBlockedForPlanRevenues)
isBlockedForPlanRevenues
- @Generated(value="lombok") public void setConsumptionQtyIsRecorded(@Nullable String 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
- @Generated(value="lombok") public void setLanguage(@Nullable String language)
- the language in which texts are displayed, - the language in which you enter texts, - the language in which the system prints texts.
language
- @Generated(value="lombok") public void setCostCenterCreatedByUser(@Nullable String costCenterCreatedByUser)
costCenterCreatedByUser
- @Generated(value="lombok") public void setCostCenterCreationDate(@Nullable Calendar costCenterCreationDate)
costCenterCreationDate
- @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext
- @Generated(value="lombok") public String toString()
toString
in class VdmObject<CostCenter>
@Generated(value="lombok") public boolean equals(Object o)
equals
in class VdmObject<CostCenter>
@Generated(value="lombok") public int hashCode()
hashCode
in class VdmObject<CostCenter>
Copyright © 2018 SAP SE. All rights reserved.