public class SalesDocumentProposalItem extends VdmEntity<SalesDocumentProposalItem>
Original entity name from the Odata EDM: A_SalesDocumentProposalItemType
| Modifier and Type | Class and Description |
|---|---|
static class |
SalesDocumentProposalItem.SalesDocumentProposalItemBuilder |
| Modifier and Type | Field and Description |
|---|---|
static SalesDocumentProposalItemSelectable |
ALL_FIELDS
Selector for all available fields of SalesDocumentProposalItem.
|
static SalesDocumentProposalItemField<String> |
BATCH
Use with available fluent helpers to apply the Batch field to query operations.
|
static SalesDocumentProposalItemField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static SalesDocumentProposalItemField<BigDecimal> |
ORDER_QUANTITY
Use with available fluent helpers to apply the OrderQuantity field to query operations.
|
static SalesDocumentProposalItemField<String> |
ORDER_QUANTITY_UNIT
Use with available fluent helpers to apply the OrderQuantityUnit field to query operations.
|
static SalesDocumentProposalItemField<String> |
ORGANIZATION_DIVISION
Use with available fluent helpers to apply the OrganizationDivision field to query operations.
|
static SalesDocumentProposalItemField<String> |
PRODUCT
Use with available fluent helpers to apply the Product field to query operations.
|
static SalesDocumentProposalItemField<String> |
SALES_DOCUMENT_TYPE
Use with available fluent helpers to apply the SalesDocumentType field to query operations.
|
static SalesDocumentProposalItemField<String> |
SALES_GROUP
Use with available fluent helpers to apply the SalesGroup field to query operations.
|
static SalesDocumentProposalItemField<String> |
SALES_OFFICE
Use with available fluent helpers to apply the SalesOffice field to query operations.
|
static SalesDocumentProposalItemField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static SalesDocumentProposalItemField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
changedOriginalFields| Constructor and Description |
|---|
SalesDocumentProposalItem() |
SalesDocumentProposalItem(String salesOrganization,
String distributionChannel,
String organizationDivision,
String salesGroup,
String salesOffice,
String soldToParty,
String salesDocumentType,
String product,
String batch,
BigDecimal orderQuantity,
String orderQuantityUnit) |
| 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 SalesDocumentProposalItem.SalesDocumentProposalItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> SalesDocumentProposalItemField<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 |
getBatch()
Constraints: Not nullable, Maximum length: 10
|
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.
|
String |
getDistributionChannel()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
protected Map<String,Object> |
getKey() |
BigDecimal |
getOrderQuantity()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getOrderQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getOrganizationDivision()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
String |
getProduct()
Constraints: Not nullable, Maximum length: 40
|
String |
getSalesDocumentType()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getSalesGroup()
(Key Field) Constraints: Not nullable, Maximum length: 3
|
String |
getSalesOffice()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOrganization()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getSoldToParty()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
Class<SalesDocumentProposalItem> |
getType() |
int |
hashCode() |
void |
setBatch(String batch)
Constraints: Not nullable, Maximum length: 10
|
void |
setDistributionChannel(String distributionChannel)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
void |
setOrderQuantity(BigDecimal orderQuantity)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setOrderQuantityUnit(String orderQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setOrganizationDivision(String organizationDivision)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
void |
setProduct(String product)
Constraints: Not nullable, Maximum length: 40
|
void |
setSalesDocumentType(String salesDocumentType)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setSalesGroup(String salesGroup)
(Key Field) Constraints: Not nullable, Maximum length: 3
|
void |
setSalesOffice(String salesOffice)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOrganization(String salesOrganization)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setSoldToParty(String soldToParty)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
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 SalesDocumentProposalItemSelectable ALL_FIELDS
public static final SalesDocumentProposalItemField<String> SALES_ORGANIZATION
public static final SalesDocumentProposalItemField<String> DISTRIBUTION_CHANNEL
public static final SalesDocumentProposalItemField<String> ORGANIZATION_DIVISION
public static final SalesDocumentProposalItemField<String> SALES_GROUP
public static final SalesDocumentProposalItemField<String> SALES_OFFICE
public static final SalesDocumentProposalItemField<String> SOLD_TO_PARTY
public static final SalesDocumentProposalItemField<String> SALES_DOCUMENT_TYPE
public static final SalesDocumentProposalItemField<String> PRODUCT
public static final SalesDocumentProposalItemField<String> BATCH
public static final SalesDocumentProposalItemField<BigDecimal> ORDER_QUANTITY
public static final SalesDocumentProposalItemField<String> ORDER_QUANTITY_UNIT
public SalesDocumentProposalItem()
public SalesDocumentProposalItem(@Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String organizationDivision, @Nullable String salesGroup, @Nullable String salesOffice, @Nullable String soldToParty, @Nullable String salesDocumentType, @Nullable String product, @Nullable String batch, @Nullable BigDecimal orderQuantity, @Nullable String orderQuantityUnit)
@Nonnull public Class<SalesDocumentProposalItem> getType()
getType in class VdmObject<SalesDocumentProposalItem>public void setSalesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
salesOrganization - An organizational unit responsible for the sale of certain products or services. The responsibility of
a sales organization may include legal liability for products and customer claims.public void setDistributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
distributionChannel - The way in which products or services reach the customer. Typical examples of distribution channels
are wholesale, retail, or direct sales.public void setOrganizationDivision(@Nullable String organizationDivision)
Original property name from the Odata EDM: OrganizationDivision
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.
organizationDivision - 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.public void setSalesGroup(@Nullable String salesGroup)
Original property name from the Odata EDM: SalesGroup
By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
salesGroup - A group of sales people who are responsible for processing sales of certain products or services.public void setSalesOffice(@Nullable String salesOffice)
Original property name from the Odata EDM: SalesOffice
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
salesOffice - A physical location (for example, a branch office) that has responsibility for the sale of certain
products or services within a given geographical area.public void setSoldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
soldToParty - Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.public void setSalesDocumentType(@Nullable String salesDocumentType)
Original property name from the Odata EDM: SalesDocumentType
The sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for.
salesDocumentType - A classification that distinguishes between different types of sales documents.public void setProduct(@Nullable String product)
Original property name from the Odata EDM: Product
product - Alphanumeric key uniquely identifying the material.public void setBatch(@Nullable String batch)
Original property name from the Odata EDM: Batch
batch - Assigns a material that is manufactured in batches or production lots to a specific batch.public void setOrderQuantity(@Nullable BigDecimal orderQuantity)
Original property name from the Odata EDM: OrderQuantity
orderQuantity - Proposed quantity for a certain product.public void setOrderQuantityUnit(@Nullable String orderQuantityUnit)
Original property name from the Odata EDM: OrderQuantityUnit
orderQuantityUnit - Unit of measure in which the material is sold.protected String getEntityCollection()
VdmEntitygetEntityCollection in class VdmEntity<SalesDocumentProposalItem>@Nonnull protected Map<String,Object> getKey()
getKey in class VdmObject<SalesDocumentProposalItem>@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields in class VdmObject<SalesDocumentProposalItem>protected void fromMap(Map<String,Object> inputValues)
fromMap in class VdmObject<SalesDocumentProposalItem>@Nonnull public static <T> SalesDocumentProposalItemField<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> SalesDocumentProposalItemField<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<SalesDocumentProposalItem>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<SalesDocumentProposalItem>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<SalesDocumentProposalItem>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<SalesDocumentProposalItem>protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)@Nonnull public static SalesDocumentProposalItem.SalesDocumentProposalItemBuilder builder()
@Nullable public String getSalesOrganization()
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
@Nullable public String getDistributionChannel()
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
@Nullable public String getOrganizationDivision()
Original property name from the Odata EDM: OrganizationDivision
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 String getSalesGroup()
Original property name from the Odata EDM: SalesGroup
By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria.If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market.You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
@Nullable public String getSalesOffice()
Original property name from the Odata EDM: SalesOffice
When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office.You can assign each customer to a sales office in the customer master record.Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
@Nullable public String getSoldToParty()
Original property name from the Odata EDM: SoldToParty
@Nullable public String getSalesDocumentType()
Original property name from the Odata EDM: SalesDocumentType
The sales document type determines how the system processes the sales document. For example, depending on the sales document type, the system determines which screens to present and which data to ask you for.
@Nullable public String getProduct()
Original property name from the Odata EDM: Product
@Nullable public String getBatch()
Original property name from the Odata EDM: Batch
@Nullable public BigDecimal getOrderQuantity()
Original property name from the Odata EDM: OrderQuantity
@Nullable public String getOrderQuantityUnit()
Original property name from the Odata EDM: OrderQuantityUnit
@Nonnull public String toString()
toString in class VdmObject<SalesDocumentProposalItem>public boolean equals(@Nullable Object o)
equals in class VdmObject<SalesDocumentProposalItem>protected boolean canEqual(@Nullable Object other)
canEqual in class VdmObject<SalesDocumentProposalItem>public int hashCode()
hashCode in class VdmObject<SalesDocumentProposalItem>Copyright © 2021 SAP SE. All rights reserved.