public class BreakdownBySubassignment extends VdmEntity<BreakdownBySubassignment>
Original entity name from the Odata EDM: BreakdownBySubassignmentType
| Modifier and Type | Class and Description |
|---|---|
static class |
BreakdownBySubassignment.BreakdownBySubassignmentBuilder |
| Modifier and Type | Field and Description |
|---|---|
static BreakdownBySubassignmentSelectable |
ALL_FIELDS
Selector for all available fields of BreakdownBySubassignment.
|
static BreakdownBySubassignmentField<String> |
BREAKDOWN_CATEGORY
Use with available fluent helpers to apply the BreakdownCategory field to query operations.
|
static BreakdownBySubassignmentField<String> |
BREAKDOWN_CATEGORY_TEXT
Use with available fluent helpers to apply the BreakdownCategory_Text field to query operations.
|
static BreakdownBySubassignmentField<String> |
BREAKDOWN_TYPE
Use with available fluent helpers to apply the BreakdownType field to query operations.
|
static BreakdownBySubassignmentField<String> |
BREAKDOWN_TYPE_TEXT
Use with available fluent helpers to apply the BreakdownType_Text field to query operations.
|
static BreakdownBySubassignmentField<String> |
CNSLDTN_FIXED_VALUE_OF_SUBASSGMT
Use with available fluent helpers to apply the CnsldtnFixedValueOfSubassgmt field to query operations.
|
static BreakdownBySubassignmentField<String> |
CNSLDTN_SUBASSIGNMENT
Use with available fluent helpers to apply the CnsldtnSubassignment field to query operations.
|
static BreakdownBySubassignmentField<String> |
CNSLDTN_SUBASSIGNMENT_TEXT
Use with available fluent helpers to apply the CnsldtnSubassignment_Text field to query operations.
|
static BreakdownBySubassignmentField<String> |
CONSOLIDATION_CHART_OF_ACCOUNTS
Use with available fluent helpers to apply the ConsolidationChartOfAccounts field to query operations.
|
static BreakdownBySubassignmentField<String> |
CONSOLIDATION_CHART_OF_ACCOUNTS_TEXT
Use with available fluent helpers to apply the ConsolidationChartOfAccounts_Text field to query
operations.
|
changedOriginalFields| Constructor and Description |
|---|
BreakdownBySubassignment() |
BreakdownBySubassignment(String consolidationChartOfAccounts,
String consolidationChartOfAccounts_Text,
String breakdownCategory,
String breakdownCategory_Text,
String cnsldtnSubassignment,
String cnsldtnSubassignment_Text,
String breakdownType,
String breakdownType_Text,
String cnsldtnFixedValueOfSubassgmt) |
| Modifier and Type | Method and Description |
|---|---|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static BreakdownBySubassignment.BreakdownBySubassignmentBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> BreakdownBySubassignmentField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getBreakdownCategory_Text()
Constraints: Not nullable, Maximum length: 30
|
String |
getBreakdownCategory()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getBreakdownType_Text()
Constraints: Not nullable, Maximum length: 60
|
String |
getBreakdownType()
Constraints: Not nullable, Maximum length: 1
|
String |
getCnsldtnFixedValueOfSubassgmt()
Constraints: Not nullable, Maximum length: 10
|
String |
getCnsldtnSubassignment_Text()
Constraints: Not nullable, Maximum length: 40
|
String |
getCnsldtnSubassignment()
(Key Field) Constraints: Not nullable, Maximum length: 30
|
String |
getConsolidationChartOfAccounts_Text()
Constraints: Not nullable, Maximum length: 30
|
String |
getConsolidationChartOfAccounts()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
protected Map<String,Object> |
getKey() |
Class<BreakdownBySubassignment> |
getType() |
int |
hashCode() |
void |
setBreakdownCategory_Text(String breakdownCategory_Text)
Constraints: Not nullable, Maximum length: 30
|
void |
setBreakdownCategory(String breakdownCategory)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setBreakdownType_Text(String breakdownType_Text)
Constraints: Not nullable, Maximum length: 60
|
void |
setBreakdownType(String breakdownType)
Constraints: Not nullable, Maximum length: 1
|
void |
setCnsldtnFixedValueOfSubassgmt(String cnsldtnFixedValueOfSubassgmt)
Constraints: Not nullable, Maximum length: 10
|
void |
setCnsldtnSubassignment_Text(String cnsldtnSubassignment_Text)
Constraints: Not nullable, Maximum length: 40
|
void |
setCnsldtnSubassignment(String cnsldtnSubassignment)
(Key Field) Constraints: Not nullable, Maximum length: 30
|
void |
setConsolidationChartOfAccounts_Text(String consolidationChartOfAccounts_Text)
Constraints: Not nullable, Maximum length: 30
|
void |
setConsolidationChartOfAccounts(String consolidationChartOfAccounts)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifiergetChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationPropertiespublic static final BreakdownBySubassignmentSelectable ALL_FIELDS
public static final BreakdownBySubassignmentField<String> CONSOLIDATION_CHART_OF_ACCOUNTS
public static final BreakdownBySubassignmentField<String> CONSOLIDATION_CHART_OF_ACCOUNTS_TEXT
public static final BreakdownBySubassignmentField<String> BREAKDOWN_CATEGORY
public static final BreakdownBySubassignmentField<String> BREAKDOWN_CATEGORY_TEXT
public static final BreakdownBySubassignmentField<String> CNSLDTN_SUBASSIGNMENT
public static final BreakdownBySubassignmentField<String> CNSLDTN_SUBASSIGNMENT_TEXT
public static final BreakdownBySubassignmentField<String> BREAKDOWN_TYPE
public static final BreakdownBySubassignmentField<String> BREAKDOWN_TYPE_TEXT
public static final BreakdownBySubassignmentField<String> CNSLDTN_FIXED_VALUE_OF_SUBASSGMT
public BreakdownBySubassignment()
public BreakdownBySubassignment(@Nullable String consolidationChartOfAccounts, @Nullable String consolidationChartOfAccounts_Text, @Nullable String breakdownCategory, @Nullable String breakdownCategory_Text, @Nullable String cnsldtnSubassignment, @Nullable String cnsldtnSubassignment_Text, @Nullable String breakdownType, @Nullable String breakdownType_Text, @Nullable String cnsldtnFixedValueOfSubassgmt)
@Nonnull public Class<BreakdownBySubassignment> getType()
getType in class VdmObject<BreakdownBySubassignment>public void setConsolidationChartOfAccounts(@Nullable String consolidationChartOfAccounts)
Original property name from the Odata EDM: ConsolidationChartOfAccounts
consolidationChartOfAccounts - Enter a Consolidation Chart of Accountspublic void setConsolidationChartOfAccounts_Text(@Nullable String consolidationChartOfAccounts_Text)
Original property name from the Odata EDM: ConsolidationChartOfAccounts_Text
consolidationChartOfAccounts_Text - Consolidation Chart of Accounts Descriptionpublic void setBreakdownCategory(@Nullable String breakdownCategory)
Original property name from the Odata EDM: BreakdownCategory
breakdownCategory - Enter a Breakdown Category.public void setBreakdownCategory_Text(@Nullable String breakdownCategory_Text)
Original property name from the Odata EDM: BreakdownCategory_Text
breakdownCategory_Text - Enter a description of up to 30 characters in length.public void setCnsldtnSubassignment(@Nullable String cnsldtnSubassignment)
Original property name from the Odata EDM: CnsldtnSubassignment
cnsldtnSubassignment - Subassignmentpublic void setCnsldtnSubassignment_Text(@Nullable String cnsldtnSubassignment_Text)
Original property name from the Odata EDM: CnsldtnSubassignment_Text
cnsldtnSubassignment_Text - Subassignment Descriptionpublic void setBreakdownType(@Nullable String breakdownType)
Original property name from the Odata EDM: BreakdownType
The following breakdown types exist:If you do not specify a subassignment in the breakdown category, or if you specify breakdown type 0 (no breakdown) for a subassignment in the breakdown category, then the associated items cannot be sub-classified by the subassignment.If you specify breakdown type 1 (optional breakdown) for a subassignment in the breakdown category, then you can sub-classify the associated items by the subassignment; but it is also possible not to break down the items by the subassignment. The values permitted for the subassignment are all values permitted by the data type of the subassignment, including the initialized (blank) value.All other breakdown types (2, 3 and 4) make the breakdown mandatory, that is, the associated items must be broken down by the subassignment; the initialized value is not permitted for the subassignment. These required breakdown types differ as follows:If you specify breakdown type 2 for a subassignment in the breakdown category, then a value does not need to be specified for the subassignment. If no value is specified, the system uses the general default value.If you specify breakdown type 3 for a subassignment in the breakdown category, then a value must be entered for the subassignment. Manual transaction, such as data entry or manual posting, prompt you to enter a value. Automatic posting produces an error message.If you specify breakdown type 4 for a subassignment in the breakdown category, then a value must be entered, as with breakdown type 3. However, the general default value is not permitted.Special Considerations:If subassignment has no general default value, breakdown types 2 and 4 are not permitted.Only breakdown types 0 and 3 are permitted for subassignments, the breakdown category of which has a fixed value (for example, the subitem category or the unit of measure).If the given subassignment has a dependent characteristic, keep the following in mind: If there is a breakdown by the independent characteristic (subitem category), there must also be a breakdown by the dependent characteristic (subitem).Note the following for subassignments that belong to a compound of characteristics: If there is breakdown by the dependent characteristic, there must also be a breakdown by the independent characteristic. If the dependent characteristic has a required breakdown, the independent characteristic must also have a required breakdown.The subassignment "transaction currency" only permits breakdown types 0 and 2.The subassignment "unit of measure" only allows the definition of a fixed value in the breakdown category.Say, you want to sub-classify your receivables, payables and revenue by the partner units. For these items you would specify a breakdown category that has the breakdown types 1, 2, 3 or 4 for the partner unit. Consider the following scenario:You want to enter revenue for each partner unit. The partner unit should always be specified for revenue. If, at first, only the total revenue is known for a consolidation unit, and the details are reported at a later date, the data entry should still be possible. To do this, you create the consolidation unit "Third Parties" and define this unit as the general default value for the partner unit. To the revenue item you assign a breakdown category with breakdown type 2 for the partner unit. Now you no longer need to enter a partner unit when entering revenues. Data entry then saves partner unit "Third Parties". Later on, when the details are reported, you can nullify the value for partner unit "Third Parties" and allocate the value to the reported partner units.For the receivables and payables your select a different procedure because the partner unit details are always known. You distinguish between the items for receivables/payables to/from third parties, for which you have no partner breakdown, and the items for receivables/payables to/from affiliated companies. For the latter items you define breakdown type 4 in the breakdown category because you want to prevent these items from being posted with partner unit "Third parties".Say, in Interunit Elimination, you want to allocate elimination differences to currency-related and other differences. To do this, for the items to be eliminated and the differential items you specify breakdown categories with breakdown type 2 for the transaction currency.Say, you want to translate the transferred asset items with historical exchange rates. For this, you want to sub-classify the items by the year of acquisition. To do this, you assign breakdown type 2 or 3 for the year of acquisition in the respective breakdown categories.Say, you use country and region as custom characteristics, these reflecting a compound of characteristics. In Characteristic Maintenance you define for both subassignments that there is no general default. Then only the breakdown types 0, 1 and 3 are allowed. Because of the compound (country being the independent characteristic) only the following combinations of breakdown types are permitted:Country Region0 01 0 <-- Here a country breakdown exists,3 0 <-- but no regional breakdown exists!1 13 13 3
breakdownType - For each subassignment you can define a breakdown type within a breakdown category. The breakdown type
determines whether you can sub-classify an item, to which the breakdown category is assigned, by the
subassignment during data entry or posting.public void setBreakdownType_Text(@Nullable String breakdownType_Text)
Original property name from the Odata EDM: BreakdownType_Text
breakdownType_Text - Breakdown Type Descriptionpublic void setCnsldtnFixedValueOfSubassgmt(@Nullable String cnsldtnFixedValueOfSubassgmt)
Original property name from the Odata EDM: CnsldtnFixedValueOfSubassgmt
cnsldtnFixedValueOfSubassgmt - Subassignment Fixed Valueprotected String getEntityCollection()
VdmEntitygetEntityCollection in class VdmEntity<BreakdownBySubassignment>@Nonnull protected Map<String,Object> getKey()
getKey in class VdmObject<BreakdownBySubassignment>@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields in class VdmObject<BreakdownBySubassignment>protected void fromMap(Map<String,Object> inputValues)
fromMap in class VdmObject<BreakdownBySubassignment>@Nonnull public static <T> BreakdownBySubassignmentField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T - The type of the extension field when performing value comparisons.fieldName - The name of the extension field as returned by the OData service.fieldType - The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> BreakdownBySubassignmentField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T - The type of the extension field when performing value comparisons.DomainT - The type of the extension field as returned by the OData service.typeConverter - A TypeConverterfieldName - The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntitygetDestinationForFetch in class VdmEntity<BreakdownBySubassignment>protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntityNote: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch in class VdmEntity<BreakdownBySubassignment>public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntityNote: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService in class VdmEntity<BreakdownBySubassignment>servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination - New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntitygetDefaultServicePath in class VdmEntity<BreakdownBySubassignment>protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)public static BreakdownBySubassignment.BreakdownBySubassignmentBuilder builder()
@Nullable public String getConsolidationChartOfAccounts()
Original property name from the Odata EDM: ConsolidationChartOfAccounts
@Nullable public String getConsolidationChartOfAccounts_Text()
Original property name from the Odata EDM: ConsolidationChartOfAccounts_Text
@Nullable public String getBreakdownCategory()
Original property name from the Odata EDM: BreakdownCategory
@Nullable public String getBreakdownCategory_Text()
Original property name from the Odata EDM: BreakdownCategory_Text
@Nullable public String getCnsldtnSubassignment()
Original property name from the Odata EDM: CnsldtnSubassignment
@Nullable public String getCnsldtnSubassignment_Text()
Original property name from the Odata EDM: CnsldtnSubassignment_Text
@Nullable public String getBreakdownType()
Original property name from the Odata EDM: BreakdownType
The following breakdown types exist:If you do not specify a subassignment in the breakdown category, or if you specify breakdown type 0 (no breakdown) for a subassignment in the breakdown category, then the associated items cannot be sub-classified by the subassignment.If you specify breakdown type 1 (optional breakdown) for a subassignment in the breakdown category, then you can sub-classify the associated items by the subassignment; but it is also possible not to break down the items by the subassignment. The values permitted for the subassignment are all values permitted by the data type of the subassignment, including the initialized (blank) value.All other breakdown types (2, 3 and 4) make the breakdown mandatory, that is, the associated items must be broken down by the subassignment; the initialized value is not permitted for the subassignment. These required breakdown types differ as follows:If you specify breakdown type 2 for a subassignment in the breakdown category, then a value does not need to be specified for the subassignment. If no value is specified, the system uses the general default value.If you specify breakdown type 3 for a subassignment in the breakdown category, then a value must be entered for the subassignment. Manual transaction, such as data entry or manual posting, prompt you to enter a value. Automatic posting produces an error message.If you specify breakdown type 4 for a subassignment in the breakdown category, then a value must be entered, as with breakdown type 3. However, the general default value is not permitted.Special Considerations:If subassignment has no general default value, breakdown types 2 and 4 are not permitted.Only breakdown types 0 and 3 are permitted for subassignments, the breakdown category of which has a fixed value (for example, the subitem category or the unit of measure).If the given subassignment has a dependent characteristic, keep the following in mind: If there is a breakdown by the independent characteristic (subitem category), there must also be a breakdown by the dependent characteristic (subitem).Note the following for subassignments that belong to a compound of characteristics: If there is breakdown by the dependent characteristic, there must also be a breakdown by the independent characteristic. If the dependent characteristic has a required breakdown, the independent characteristic must also have a required breakdown.The subassignment "transaction currency" only permits breakdown types 0 and 2.The subassignment "unit of measure" only allows the definition of a fixed value in the breakdown category.Say, you want to sub-classify your receivables, payables and revenue by the partner units. For these items you would specify a breakdown category that has the breakdown types 1, 2, 3 or 4 for the partner unit. Consider the following scenario:You want to enter revenue for each partner unit. The partner unit should always be specified for revenue. If, at first, only the total revenue is known for a consolidation unit, and the details are reported at a later date, the data entry should still be possible. To do this, you create the consolidation unit "Third Parties" and define this unit as the general default value for the partner unit. To the revenue item you assign a breakdown category with breakdown type 2 for the partner unit. Now you no longer need to enter a partner unit when entering revenues. Data entry then saves partner unit "Third Parties". Later on, when the details are reported, you can nullify the value for partner unit "Third Parties" and allocate the value to the reported partner units.For the receivables and payables your select a different procedure because the partner unit details are always known. You distinguish between the items for receivables/payables to/from third parties, for which you have no partner breakdown, and the items for receivables/payables to/from affiliated companies. For the latter items you define breakdown type 4 in the breakdown category because you want to prevent these items from being posted with partner unit "Third parties".Say, in Interunit Elimination, you want to allocate elimination differences to currency-related and other differences. To do this, for the items to be eliminated and the differential items you specify breakdown categories with breakdown type 2 for the transaction currency.Say, you want to translate the transferred asset items with historical exchange rates. For this, you want to sub-classify the items by the year of acquisition. To do this, you assign breakdown type 2 or 3 for the year of acquisition in the respective breakdown categories.Say, you use country and region as custom characteristics, these reflecting a compound of characteristics. In Characteristic Maintenance you define for both subassignments that there is no general default. Then only the breakdown types 0, 1 and 3 are allowed. Because of the compound (country being the independent characteristic) only the following combinations of breakdown types are permitted:Country Region0 01 0 <-- Here a country breakdown exists,3 0 <-- but no regional breakdown exists!1 13 13 3
@Nullable public String getBreakdownType_Text()
Original property name from the Odata EDM: BreakdownType_Text
@Nullable public String getCnsldtnFixedValueOfSubassgmt()
Original property name from the Odata EDM: CnsldtnFixedValueOfSubassgmt
public String toString()
toString in class VdmObject<BreakdownBySubassignment>public boolean equals(Object o)
equals in class VdmObject<BreakdownBySubassignment>protected boolean canEqual(Object other)
canEqual in class VdmObject<BreakdownBySubassignment>public int hashCode()
hashCode in class VdmObject<BreakdownBySubassignment>Copyright © 2020 SAP SE. All rights reserved.