public class CustProjSlsOrd extends VdmEntity<CustProjSlsOrd>
Original entity name from the Odata EDM: A_CustProjSlsOrdType
Modifier and Type | Class and Description |
---|---|
static class |
CustProjSlsOrd.CustProjSlsOrdBuilder
Helper class to allow for fluent creation of CustProjSlsOrd instances.
|
Modifier and Type | Field and Description |
---|---|
static CustProjSlsOrdSelectable |
ALL_FIELDS
Selector for all available fields of CustProjSlsOrd.
|
static CustProjSlsOrdField<String> |
CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
|
static CustProjSlsOrdField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static CustProjSlsOrdField<String> |
CUSTOMER_PROJECT
Use with available fluent helpers to apply the CustomerProject field to query operations.
|
static CustProjSlsOrdField<LocalDateTime> |
CUSTOMER_PURCHASE_ORDER_DATE
Use with available fluent helpers to apply the CustomerPurchaseOrderDate field to query operations.
|
static CustProjSlsOrdField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static CustProjSlsOrdField<String> |
HEADER_BILLING_BLOCK_REASON
Use with available fluent helpers to apply the HeaderBillingBlockReason field to query operations.
|
static CustProjSlsOrdField<String> |
ORGANIZATION_DIVISION
Use with available fluent helpers to apply the OrganizationDivision field to query operations.
|
static CustProjSlsOrdField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static CustProjSlsOrdField<String> |
SALES_GROUP
Use with available fluent helpers to apply the SalesGroup field to query operations.
|
static CustProjSlsOrdField<String> |
SALES_OFFICE
Use with available fluent helpers to apply the SalesOffice field to query operations.
|
static CustProjSlsOrdField<String> |
SALES_ORDER
Use with available fluent helpers to apply the SalesOrder field to query operations.
|
static CustProjSlsOrdField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static CustProjSlsOrdField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static CustProjSlsOrdLink<CustProjSlsOrdItem> |
TO_CUST_PROJ_SLS_ORD_ITEM
Use with available fluent helpers to apply the to_CustProjSlsOrdItem navigation property to query
operations.
|
static CustProjSlsOrdLink<CustProjSlsOrdPartner> |
TO_CUST_PROJ_SLS_ORD_PARTNER
Use with available fluent helpers to apply the to_CustProjSlsOrdPartner navigation property to query
operations.
|
static CustProjSlsOrdLink<CustProjSlsOrdText> |
TO_CUST_PROJ_SLS_ORD_TEXT
Use with available fluent helpers to apply the to_CustProjSlsOrdText navigation property to query
operations.
|
static CustProjSlsOrdField<BigDecimal> |
TOTAL_NET_AMOUNT
Use with available fluent helpers to apply the TotalNetAmount field to query operations.
|
static CustProjSlsOrdField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
CustProjSlsOrd() |
CustProjSlsOrd(String customerProject,
String salesOrder,
String soldToParty,
BigDecimal totalNetAmount,
String transactionCurrency,
String purchaseOrderByCustomer,
LocalDateTime customerPurchaseOrderDate,
String salesOffice,
String salesGroup,
String customerPaymentTerms,
String customerAccountAssignmentGroup,
String headerBillingBlockReason,
String salesOrganization,
String distributionChannel,
String organizationDivision,
List<CustProjSlsOrdItem> toCustProjSlsOrdItem,
List<CustProjSlsOrdPartner> toCustProjSlsOrdPartner,
List<CustProjSlsOrdText> toCustProjSlsOrdText) |
Modifier and Type | Method and Description |
---|---|
void |
addCustProjSlsOrdItem(CustProjSlsOrdItem... entity)
Adds elements to the list of associated CustProjSlsOrdItem entities.
|
void |
addCustProjSlsOrdPartner(CustProjSlsOrdPartner... entity)
Adds elements to the list of associated CustProjSlsOrdPartner entities.
|
void |
addCustProjSlsOrdText(CustProjSlsOrdText... entity)
Adds elements to the list of associated CustProjSlsOrdText entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static CustProjSlsOrd.CustProjSlsOrdBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<CustProjSlsOrdItem> |
fetchCustProjSlsOrdItem()
Fetches the CustProjSlsOrdItem entities (one to many) associated with this entity.
|
List<CustProjSlsOrdPartner> |
fetchCustProjSlsOrdPartner()
Fetches the CustProjSlsOrdPartner entities (one to many) associated with this entity.
|
List<CustProjSlsOrdText> |
fetchCustProjSlsOrdText()
Fetches the CustProjSlsOrdText entities (one to many) associated with this entity.
|
static <T> CustProjSlsOrdField<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 |
getCustomerAccountAssignmentGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
String |
getCustomerProject()
(Key Field) Constraints: Not nullable, Maximum length: 40
|
LocalDateTime |
getCustomerPurchaseOrderDate()
Constraints: Not nullable, Precision: 0
|
io.vavr.control.Option<List<CustProjSlsOrdItem>> |
getCustProjSlsOrdItemIfPresent()
Retrieval of associated CustProjSlsOrdItem entities (one to many).
|
List<CustProjSlsOrdItem> |
getCustProjSlsOrdItemOrFetch()
Retrieval of associated CustProjSlsOrdItem entities (one to many).
|
io.vavr.control.Option<List<CustProjSlsOrdPartner>> |
getCustProjSlsOrdPartnerIfPresent()
Retrieval of associated CustProjSlsOrdPartner entities (one to many).
|
List<CustProjSlsOrdPartner> |
getCustProjSlsOrdPartnerOrFetch()
Retrieval of associated CustProjSlsOrdPartner entities (one to many).
|
io.vavr.control.Option<List<CustProjSlsOrdText>> |
getCustProjSlsOrdTextIfPresent()
Retrieval of associated CustProjSlsOrdText entities (one to many).
|
List<CustProjSlsOrdText> |
getCustProjSlsOrdTextOrFetch()
Retrieval of associated CustProjSlsOrdText entities (one to many).
|
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()
Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getHeaderBillingBlockReason()
Constraints: Not nullable, Maximum length: 2
|
protected Map<String,Object> |
getKey() |
String |
getOrganizationDivision()
Constraints: Not nullable, Maximum length: 2
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getSalesGroup()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesOffice()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOrder()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
BigDecimal |
getTotalNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<CustProjSlsOrd> |
getType() |
int |
hashCode() |
void |
setCustomerAccountAssignmentGroup(String customerAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setCustomerProject(String customerProject)
(Key Field) Constraints: Not nullable, Maximum length: 40
|
void |
setCustomerPurchaseOrderDate(LocalDateTime customerPurchaseOrderDate)
Constraints: Not nullable, Precision: 0
|
void |
setCustProjSlsOrdItem(List<CustProjSlsOrdItem> value)
Overwrites the list of associated CustProjSlsOrdItem entities for the loaded navigation property
to_CustProjSlsOrdItem.
|
void |
setCustProjSlsOrdPartner(List<CustProjSlsOrdPartner> value)
Overwrites the list of associated CustProjSlsOrdPartner entities for the loaded navigation property
to_CustProjSlsOrdPartner.
|
void |
setCustProjSlsOrdText(List<CustProjSlsOrdText> value)
Overwrites the list of associated CustProjSlsOrdText entities for the loaded navigation property
to_CustProjSlsOrdText.
|
void |
setDistributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
void |
setHeaderBillingBlockReason(String headerBillingBlockReason)
Constraints: Not nullable, Maximum length: 2
|
void |
setOrganizationDivision(String organizationDivision)
Constraints: Not nullable, Maximum length: 2
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setSalesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOrder(String salesOrder)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesOrganization(String salesOrganization)
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)
Constraints: Not nullable, Maximum length: 10
|
void |
setTotalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final CustProjSlsOrdSelectable ALL_FIELDS
public static final CustProjSlsOrdField<String> CUSTOMER_PROJECT
public static final CustProjSlsOrdField<String> SALES_ORDER
public static final CustProjSlsOrdField<String> SOLD_TO_PARTY
public static final CustProjSlsOrdField<BigDecimal> TOTAL_NET_AMOUNT
public static final CustProjSlsOrdField<String> TRANSACTION_CURRENCY
public static final CustProjSlsOrdField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final CustProjSlsOrdField<LocalDateTime> CUSTOMER_PURCHASE_ORDER_DATE
public static final CustProjSlsOrdField<String> SALES_OFFICE
public static final CustProjSlsOrdField<String> SALES_GROUP
public static final CustProjSlsOrdField<String> CUSTOMER_PAYMENT_TERMS
public static final CustProjSlsOrdField<String> CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
public static final CustProjSlsOrdField<String> HEADER_BILLING_BLOCK_REASON
public static final CustProjSlsOrdField<String> SALES_ORGANIZATION
public static final CustProjSlsOrdField<String> DISTRIBUTION_CHANNEL
public static final CustProjSlsOrdField<String> ORGANIZATION_DIVISION
public static final CustProjSlsOrdLink<CustProjSlsOrdItem> TO_CUST_PROJ_SLS_ORD_ITEM
public static final CustProjSlsOrdLink<CustProjSlsOrdPartner> TO_CUST_PROJ_SLS_ORD_PARTNER
public static final CustProjSlsOrdLink<CustProjSlsOrdText> TO_CUST_PROJ_SLS_ORD_TEXT
public CustProjSlsOrd()
public CustProjSlsOrd(@Nullable String customerProject, @Nullable String salesOrder, @Nullable String soldToParty, @Nullable BigDecimal totalNetAmount, @Nullable String transactionCurrency, @Nullable String purchaseOrderByCustomer, @Nullable LocalDateTime customerPurchaseOrderDate, @Nullable String salesOffice, @Nullable String salesGroup, @Nullable String customerPaymentTerms, @Nullable String customerAccountAssignmentGroup, @Nullable String headerBillingBlockReason, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String organizationDivision, List<CustProjSlsOrdItem> toCustProjSlsOrdItem, List<CustProjSlsOrdPartner> toCustProjSlsOrdPartner, List<CustProjSlsOrdText> toCustProjSlsOrdText)
@Nonnull public Class<CustProjSlsOrd> getType()
getType
in class VdmObject<CustProjSlsOrd>
public void setCustomerProject(@Nullable String customerProject)
Original property name from the Odata EDM: CustomerProject
customerProject
- Identifies a customer or internal project.public void setSalesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
salesOrder
- Sales Orderpublic void setSoldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
soldToParty
- The customer who orders the goods or services. The sold-to party is contractually responsible for
sales orders.public void setTotalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
totalNetAmount
- The total value of all items in the sales document, after any discounts and surcharges are taken into
account. The value is expressed in the document currency.public void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency
- The currency that applies to the document (for example, to a sales order or an invoice).public void setPurchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
purchaseOrderByCustomer
- Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a
purchase order).public void setCustomerPurchaseOrderDate(@Nullable LocalDateTime customerPurchaseOrderDate)
Original property name from the Odata EDM: CustomerPurchaseOrderDate
customerPurchaseOrderDate
- The date that appears on the customer's purchase order. This date can be, for example, the date on
which the customer created the purchase order.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 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 setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
customerPaymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setCustomerAccountAssignmentGroup(@Nullable String customerAccountAssignmentGroup)
Original property name from the Odata EDM: CustomerAccountAssignmentGroup
The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
customerAccountAssignmentGroup
- The account assignment group to which the system automatically posts the sales document.public void setHeaderBillingBlockReason(@Nullable String headerBillingBlockReason)
Original property name from the Odata EDM: HeaderBillingBlockReason
The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
headerBillingBlockReason
- Indicates if the entire sales document is blocked for billing.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.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<CustProjSlsOrd>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<CustProjSlsOrd>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<CustProjSlsOrd>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<CustProjSlsOrd>
@Nonnull public static <T> CustProjSlsOrdField<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> CustProjSlsOrdField<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()
VdmEntity
getDestinationForFetch
in class VdmEntity<CustProjSlsOrd>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: 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<CustProjSlsOrd>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: 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<CustProjSlsOrd>
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()
VdmEntity
getDefaultServicePath
in class VdmEntity<CustProjSlsOrd>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<CustProjSlsOrd>
@Nonnull public List<CustProjSlsOrdItem> fetchCustProjSlsOrdItem() 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.@Nonnull public List<CustProjSlsOrdItem> getCustProjSlsOrdItemOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_CustProjSlsOrdItem of a queried CustProjSlsOrd 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.@Nonnull public io.vavr.control.Option<List<CustProjSlsOrdItem>> getCustProjSlsOrdItemIfPresent()
If the navigation property for an entity CustProjSlsOrd has not been resolved yet, this method will not
query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setCustProjSlsOrdItem(@Nonnull List<CustProjSlsOrdItem> value)
If the navigation property to_CustProjSlsOrdItem of a queried CustProjSlsOrd 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 CustProjSlsOrdItem entities.public void addCustProjSlsOrdItem(CustProjSlsOrdItem... entity)
If the navigation property to_CustProjSlsOrdItem of a queried CustProjSlsOrd 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 CustProjSlsOrdItem entities.@Nonnull public List<CustProjSlsOrdPartner> fetchCustProjSlsOrdPartner() 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.@Nonnull public List<CustProjSlsOrdPartner> getCustProjSlsOrdPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_CustProjSlsOrdPartner of a queried CustProjSlsOrd 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.@Nonnull public io.vavr.control.Option<List<CustProjSlsOrdPartner>> getCustProjSlsOrdPartnerIfPresent()
If the navigation property for an entity CustProjSlsOrd has not been resolved yet, this method will not
query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setCustProjSlsOrdPartner(@Nonnull List<CustProjSlsOrdPartner> value)
If the navigation property to_CustProjSlsOrdPartner of a queried CustProjSlsOrd 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 CustProjSlsOrdPartner entities.public void addCustProjSlsOrdPartner(CustProjSlsOrdPartner... entity)
If the navigation property to_CustProjSlsOrdPartner of a queried CustProjSlsOrd 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 CustProjSlsOrdPartner entities.@Nonnull public List<CustProjSlsOrdText> fetchCustProjSlsOrdText() 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.@Nonnull public List<CustProjSlsOrdText> getCustProjSlsOrdTextOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_CustProjSlsOrdText of a queried CustProjSlsOrd 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.@Nonnull public io.vavr.control.Option<List<CustProjSlsOrdText>> getCustProjSlsOrdTextIfPresent()
If the navigation property for an entity CustProjSlsOrd has not been resolved yet, this method will not
query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setCustProjSlsOrdText(@Nonnull List<CustProjSlsOrdText> value)
If the navigation property to_CustProjSlsOrdText of a queried CustProjSlsOrd 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 CustProjSlsOrdText entities.public void addCustProjSlsOrdText(CustProjSlsOrdText... entity)
If the navigation property to_CustProjSlsOrdText of a queried CustProjSlsOrd 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 CustProjSlsOrdText entities.public static CustProjSlsOrd.CustProjSlsOrdBuilder builder()
@Nullable public String getCustomerProject()
Original property name from the Odata EDM: CustomerProject
@Nullable public String getSalesOrder()
Original property name from the Odata EDM: SalesOrder
@Nullable public String getSoldToParty()
Original property name from the Odata EDM: SoldToParty
@Nullable public BigDecimal getTotalNetAmount()
Original property name from the Odata EDM: TotalNetAmount
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable public String getPurchaseOrderByCustomer()
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
@Nullable public LocalDateTime getCustomerPurchaseOrderDate()
Original property name from the Odata EDM: CustomerPurchaseOrderDate
@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 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 getCustomerPaymentTerms()
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
@Nullable public String getCustomerAccountAssignmentGroup()
Original property name from the Odata EDM: CustomerAccountAssignmentGroup
The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
@Nullable public String getHeaderBillingBlockReason()
Original property name from the Odata EDM: HeaderBillingBlockReason
The system can propose the billing block according to the type of sales document. The billing block applies to the entire document. You can block or unblock the entire document manually in the header. If you want to block only a particular item, enter a value at the item level.You may want to apply a billing block to certain documents so that prices can be checked before further processing.
@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.
public String toString()
toString
in class VdmObject<CustProjSlsOrd>
public boolean equals(Object o)
equals
in class VdmObject<CustProjSlsOrd>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<CustProjSlsOrd>
public int hashCode()
hashCode
in class VdmObject<CustProjSlsOrd>
Copyright © 2020 SAP SE. All rights reserved.