Modifier and Type | Class and Description |
---|---|
static class |
Division.DivisionBuilder |
Modifier and Type | Field and Description |
---|---|
static DivisionSelectable |
ALL_FIELDS
Selector for all available fields of Division.
|
static DivisionField<String> |
DIVISION
Use with available fluent helpers to apply the Division field to query operations.
|
static DivisionLink<DivisionText> |
TO_TEXT
Use with available fluent helpers to apply the to_Text navigation property to query operations.
|
changedOriginalFields
Constructor and Description |
---|
Division() |
Division(String division,
ErpConfigContext erpConfigContext,
List<DivisionText> toText) |
Modifier and Type | Method and Description |
---|---|
void |
addText(DivisionText... entity)
Adds elements to the list of associated DivisionText entities.
|
static Division.DivisionBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<DivisionText> |
fetchText()
Fetches the DivisionText entities (one to many) associated with this entity.
|
static <T> DivisionField<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 |
getDivision()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
protected Map<String,Object> |
getKey() |
Optional<List<DivisionText>> |
getTextIfPresent()
Retrieval of associated DivisionText entities (one to many).
|
List<DivisionText> |
getTextOrFetch()
Retrieval of associated DivisionText entities (one to many).
|
Class<Division> |
getType() |
int |
hashCode() |
void |
setDivision(String division)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setText(List<DivisionText> value)
Overwrites the list of associated DivisionText entities for the loaded navigation property to_Text.
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setServicePathForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final DivisionSelectable ALL_FIELDS
public static final DivisionField<String> DIVISION
public static final DivisionLink<DivisionText> TO_TEXT
public Division()
public Division(@Nullable String division, @Nullable ErpConfigContext erpConfigContext, List<DivisionText> toText)
public void setDivision(@Nullable String division)
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
division
- A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<Division>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<Division>
@Nonnull public static <T> DivisionField<T> field(@Nonnull String fieldName, @Nonnull 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.@Nonnull public static <T,DomainT> DivisionField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<Division>
public List<DivisionText> 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<DivisionText> getTextOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Text of a queried Division 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<DivisionText>> getTextIfPresent()
If the navigation property for an entity Division 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<DivisionText> value)
If the navigation property to_Text of a queried Division 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 DivisionText entities.public void addText(DivisionText... entity)
If the navigation property to_Text of a queried Division 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 DivisionText entities.public static Division.DivisionBuilder builder()
@Nullable public String getDivision()
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<Division>
erpConfigContext
- Copyright © 2018 SAP SE. All rights reserved.