public class CreditBlockedSalesDocument extends VdmEntity<CreditBlockedSalesDocument>
Original entity name from the Odata EDM: A_CreditBlockedSalesDocumentType
Modifier and Type | Class and Description |
---|---|
static class |
CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder |
Modifier and Type | Field and Description |
---|---|
static CreditBlockedSalesDocumentSelectable |
ALL_FIELDS
Selector for all available fields of CreditBlockedSalesDocument.
|
static CreditBlockedSalesDocumentField<String> |
CENTRAL_CREDIT_CHECK_STATUS
Use with available fluent helpers to apply the CentralCreditCheckStatus field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
CENTRAL_CREDIT_CHK_TECH_ERR_STS
Use with available fluent helpers to apply the CentralCreditChkTechErrSts field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
CONTROLLING_AREA_CURRENCY
Use with available fluent helpers to apply the ControllingAreaCurrency field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
CREATED_BY_USER
Use with available fluent helpers to apply the CreatedByUser field to query operations.
|
static CreditBlockedSalesDocumentField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static CreditBlockedSalesDocumentField<LocalDateTime> |
CREDIT_BLOCK_RELEASE_DATE
Use with available fluent helpers to apply the CreditBlockReleaseDate field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
CUSTOMER_CREDIT_ACCOUNT
Use with available fluent helpers to apply the CustomerCreditAccount field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
FIN_DOC_CREDIT_CHECK_STATUS
Use with available fluent helpers to apply the FinDocCreditCheckStatus field to query operations.
|
static CreditBlockedSalesDocumentField<LocalDateTime> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
LAST_CHANGED_BY_USER
Use with available fluent helpers to apply the LastChangedByUser field to query operations.
|
static CreditBlockedSalesDocumentField<LocalDateTime> |
NEXT_CREDIT_CHECK_DATE
Use with available fluent helpers to apply the NextCreditCheckDate field to query operations.
|
static CreditBlockedSalesDocumentField<LocalDateTime> |
NEXT_SHIPPING_DATE
Use with available fluent helpers to apply the NextShippingDate field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
ORGANIZATION_DIVISION
Use with available fluent helpers to apply the OrganizationDivision field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
OVERALL_SD_PROCESS_STATUS
Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
|
static CreditBlockedSalesDocumentField<BigDecimal> |
RELEASED_CREDIT_AMOUNT
Use with available fluent helpers to apply the ReleasedCreditAmount field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
SALES_DOCUMENT
Use with available fluent helpers to apply the SalesDocument field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
SALES_DOCUMENT_TYPE
Use with available fluent helpers to apply the SalesDocumentType field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
SALES_GROUP
Use with available fluent helpers to apply the SalesGroup field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
SALES_OFFICE
Use with available fluent helpers to apply the SalesOffice field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
SD_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the SDDocumentCategory field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
TOTAL_CREDIT_CHECK_STATUS
Use with available fluent helpers to apply the TotalCreditCheckStatus field to query operations.
|
static CreditBlockedSalesDocumentField<BigDecimal> |
TOTAL_NET_AMOUNT
Use with available fluent helpers to apply the TotalNetAmount field to query operations.
|
static CreditBlockedSalesDocumentField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
CreditBlockedSalesDocument() |
CreditBlockedSalesDocument(String salesDocument,
String sDDocumentCategory,
String salesDocumentType,
String salesOrganization,
String distributionChannel,
String organizationDivision,
String salesOffice,
String salesGroup,
String createdByUser,
LocalDateTime creationDate,
String lastChangedByUser,
LocalDateTime lastChangeDate,
String soldToParty,
BigDecimal totalNetAmount,
String transactionCurrency,
String customerCreditAccount,
String controllingAreaCurrency,
BigDecimal releasedCreditAmount,
LocalDateTime creditBlockReleaseDate,
LocalDateTime nextShippingDate,
LocalDateTime nextCreditCheckDate,
String finDocCreditCheckStatus,
String totalCreditCheckStatus,
String overallSDProcessStatus,
String centralCreditCheckStatus,
String centralCreditChkTechErrSts) |
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 CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> CreditBlockedSalesDocumentField<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 |
getCentralCreditCheckStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getCentralCreditChkTechErrSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getControllingAreaCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getCreatedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getCreditBlockReleaseDate()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerCreditAccount()
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()
Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getFinDocCreditCheckStatus()
Constraints: Not nullable, Maximum length: 1
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getLastChangeDate()
Constraints: Not nullable, Precision: 0
|
String |
getLastChangedByUser()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getNextCreditCheckDate()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getNextShippingDate()
Constraints: Not nullable, Precision: 0
|
String |
getOrganizationDivision()
Constraints: Not nullable, Maximum length: 2
|
String |
getOverallSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getReleasedCreditAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getSalesDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSalesDocumentType()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesGroup()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesOffice()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
String |
getSDDocumentCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getTotalCreditCheckStatus()
Constraints: Not nullable, Maximum length: 1
|
BigDecimal |
getTotalNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<CreditBlockedSalesDocument> |
getType() |
int |
hashCode() |
void |
setCentralCreditCheckStatus(String centralCreditCheckStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setCentralCreditChkTechErrSts(String centralCreditChkTechErrSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setControllingAreaCurrency(String controllingAreaCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setCreatedByUser(String createdByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreditBlockReleaseDate(LocalDateTime creditBlockReleaseDate)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerCreditAccount(String customerCreditAccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setDistributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
void |
setFinDocCreditCheckStatus(String finDocCreditCheckStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setLastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setLastChangedByUser(String lastChangedByUser)
Constraints: Not nullable, Maximum length: 12
|
void |
setNextCreditCheckDate(LocalDateTime nextCreditCheckDate)
Constraints: Not nullable, Precision: 0
|
void |
setNextShippingDate(LocalDateTime nextShippingDate)
Constraints: Not nullable, Precision: 0
|
void |
setOrganizationDivision(String organizationDivision)
Constraints: Not nullable, Maximum length: 2
|
void |
setOverallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setReleasedCreditAmount(BigDecimal releasedCreditAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setSalesDocument(String salesDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSalesDocumentType(String salesDocumentType)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
void |
setSalesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
void |
setSDDocumentCategory(String sDDocumentCategory)
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 |
setTotalCreditCheckStatus(String totalCreditCheckStatus)
Constraints: Not nullable, Maximum length: 1
|
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() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final CreditBlockedSalesDocumentSelectable ALL_FIELDS
public static final CreditBlockedSalesDocumentField<String> SALES_DOCUMENT
public static final CreditBlockedSalesDocumentField<String> SD_DOCUMENT_CATEGORY
public static final CreditBlockedSalesDocumentField<String> SALES_DOCUMENT_TYPE
public static final CreditBlockedSalesDocumentField<String> SALES_ORGANIZATION
public static final CreditBlockedSalesDocumentField<String> DISTRIBUTION_CHANNEL
public static final CreditBlockedSalesDocumentField<String> ORGANIZATION_DIVISION
public static final CreditBlockedSalesDocumentField<String> SALES_OFFICE
public static final CreditBlockedSalesDocumentField<String> SALES_GROUP
public static final CreditBlockedSalesDocumentField<String> CREATED_BY_USER
public static final CreditBlockedSalesDocumentField<LocalDateTime> CREATION_DATE
public static final CreditBlockedSalesDocumentField<String> LAST_CHANGED_BY_USER
public static final CreditBlockedSalesDocumentField<LocalDateTime> LAST_CHANGE_DATE
public static final CreditBlockedSalesDocumentField<String> SOLD_TO_PARTY
public static final CreditBlockedSalesDocumentField<BigDecimal> TOTAL_NET_AMOUNT
public static final CreditBlockedSalesDocumentField<String> TRANSACTION_CURRENCY
public static final CreditBlockedSalesDocumentField<String> CUSTOMER_CREDIT_ACCOUNT
public static final CreditBlockedSalesDocumentField<String> CONTROLLING_AREA_CURRENCY
public static final CreditBlockedSalesDocumentField<BigDecimal> RELEASED_CREDIT_AMOUNT
public static final CreditBlockedSalesDocumentField<LocalDateTime> CREDIT_BLOCK_RELEASE_DATE
public static final CreditBlockedSalesDocumentField<LocalDateTime> NEXT_SHIPPING_DATE
public static final CreditBlockedSalesDocumentField<LocalDateTime> NEXT_CREDIT_CHECK_DATE
public static final CreditBlockedSalesDocumentField<String> FIN_DOC_CREDIT_CHECK_STATUS
public static final CreditBlockedSalesDocumentField<String> TOTAL_CREDIT_CHECK_STATUS
public static final CreditBlockedSalesDocumentField<String> OVERALL_SD_PROCESS_STATUS
public static final CreditBlockedSalesDocumentField<String> CENTRAL_CREDIT_CHECK_STATUS
public static final CreditBlockedSalesDocumentField<String> CENTRAL_CREDIT_CHK_TECH_ERR_STS
public CreditBlockedSalesDocument()
public CreditBlockedSalesDocument(@Nullable String salesDocument, @Nullable String sDDocumentCategory, @Nullable String salesDocumentType, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String organizationDivision, @Nullable String salesOffice, @Nullable String salesGroup, @Nullable String createdByUser, @Nullable LocalDateTime creationDate, @Nullable String lastChangedByUser, @Nullable LocalDateTime lastChangeDate, @Nullable String soldToParty, @Nullable BigDecimal totalNetAmount, @Nullable String transactionCurrency, @Nullable String customerCreditAccount, @Nullable String controllingAreaCurrency, @Nullable BigDecimal releasedCreditAmount, @Nullable LocalDateTime creditBlockReleaseDate, @Nullable LocalDateTime nextShippingDate, @Nullable LocalDateTime nextCreditCheckDate, @Nullable String finDocCreditCheckStatus, @Nullable String totalCreditCheckStatus, @Nullable String overallSDProcessStatus, @Nullable String centralCreditCheckStatus, @Nullable String centralCreditChkTechErrSts)
@Nonnull public Class<CreditBlockedSalesDocument> getType()
getType
in class VdmObject<CreditBlockedSalesDocument>
public void setSalesDocument(@Nullable String salesDocument)
Original property name from the Odata EDM: SalesDocument
salesDocument
- The number that uniquely identifies the sales document.public void setSDDocumentCategory(@Nullable String sDDocumentCategory)
Original property name from the Odata EDM: SDDocumentCategory
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
sDDocumentCategory
- A classification for the different types of documents that you can process, for example, quotations,
sales orders, deliveries, and invoices.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 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 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 setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser
- Name of Person Who Created Objectpublic void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on Which Record Was Createdpublic void setLastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
lastChangedByUser
- User Who Last Changed the Business Documentpublic void setLastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
lastChangeDate
- Date of Last Changepublic 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 setCustomerCreditAccount(@Nullable String customerCreditAccount)
Original property name from the Odata EDM: CustomerCreditAccount
You need this field if you want to assign the credit limit for a group of customers, instead of one customer. In this case you assign the credit limit to one of the customers in the group. All other customers in the group use this field to link to reference to this customer.
customerCreditAccount
- Customer account that the system uses to monitor the credit limit.public void setControllingAreaCurrency(@Nullable String controllingAreaCurrency)
Original property name from the Odata EDM: ControllingAreaCurrency
controllingAreaCurrency
- Identifies the currency of the amounts that are being transacted. The currency is the currency of the
credit control area.public void setReleasedCreditAmount(@Nullable BigDecimal releasedCreditAmount)
Original property name from the Odata EDM: ReleasedCreditAmount
order: the basis for calculating this value is the cumulated confirmed quantityIf changes are made to the document after release, the system uses the released credit value to determine whether the document requires a further credit check.
releasedCreditAmount
- Specifies the credit value of a sales order or a delivery at the time of release.public void setCreditBlockReleaseDate(@Nullable LocalDateTime creditBlockReleaseDate)
Original property name from the Odata EDM: CreditBlockReleaseDate
creditBlockReleaseDate
- Specifies the date on which the sales order or delivery was released after being blocked for credit
reasons.public void setNextShippingDate(@Nullable LocalDateTime nextShippingDate)
Original property name from the Odata EDM: NextShippingDate
In the delivery header, the field specifies the next planned picking or goods issue date.Using these dates in the headers of sales documents and deliveries, the system is able to recognize those documents for which processing time is critical.
nextShippingDate
- In the sales order header, this field specifies the next planned delivery date.public void setNextCreditCheckDate(@Nullable LocalDateTime nextCreditCheckDate)
Original property name from the Odata EDM: NextCreditCheckDate
The system stores this date if, during a dynamic credit check, some items or schedule lines in the document lie outside the credit horizon.
nextCreditCheckDate
- Specifies the date of the next credit check required for the document.public void setFinDocCreditCheckStatus(@Nullable String finDocCreditCheckStatus)
Original property name from the Odata EDM: FinDocCreditCheckStatus
finDocCreditCheckStatus
- Status of Credit Check Against Financial Documentpublic void setTotalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
totalCreditCheckStatus
- Overall Status of Credit Checkspublic void setOverallSDProcessStatus(@Nullable String overallSDProcessStatus)
Original property name from the Odata EDM: OverallSDProcessStatus
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
overallSDProcessStatus
- The processing status of the entire sales document.public void setCentralCreditCheckStatus(@Nullable String centralCreditCheckStatus)
Original property name from the Odata EDM: CentralCreditCheckStatus
centralCreditCheckStatus
- Status of Credit Check SAP Credit Managementpublic void setCentralCreditChkTechErrSts(@Nullable String centralCreditChkTechErrSts)
Original property name from the Odata EDM: CentralCreditChkTechErrSts
The technical error status of the sales document indicates whether the sales order was blocked due to a technical error during the sales document creation or changing.
centralCreditChkTechErrSts
- The technical error status of the sales document for SAP Credit Management.protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<CreditBlockedSalesDocument>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<CreditBlockedSalesDocument>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<CreditBlockedSalesDocument>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<CreditBlockedSalesDocument>
@Nonnull public static <T> CreditBlockedSalesDocumentField<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> CreditBlockedSalesDocumentField<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<CreditBlockedSalesDocument>
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<CreditBlockedSalesDocument>
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<CreditBlockedSalesDocument>
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<CreditBlockedSalesDocument>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull public static CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder builder()
@Nullable public String getSalesDocument()
Original property name from the Odata EDM: SalesDocument
@Nullable public String getSDDocumentCategory()
Original property name from the Odata EDM: SDDocumentCategory
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
@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 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 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 getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public String getLastChangedByUser()
Original property name from the Odata EDM: LastChangedByUser
@Nullable public LocalDateTime getLastChangeDate()
Original property name from the Odata EDM: LastChangeDate
@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 getCustomerCreditAccount()
Original property name from the Odata EDM: CustomerCreditAccount
You need this field if you want to assign the credit limit for a group of customers, instead of one customer. In this case you assign the credit limit to one of the customers in the group. All other customers in the group use this field to link to reference to this customer.
@Nullable public String getControllingAreaCurrency()
Original property name from the Odata EDM: ControllingAreaCurrency
@Nullable public BigDecimal getReleasedCreditAmount()
Original property name from the Odata EDM: ReleasedCreditAmount
order: the basis for calculating this value is the cumulated confirmed quantityIf changes are made to the document after release, the system uses the released credit value to determine whether the document requires a further credit check.
@Nullable public LocalDateTime getCreditBlockReleaseDate()
Original property name from the Odata EDM: CreditBlockReleaseDate
@Nullable public LocalDateTime getNextShippingDate()
Original property name from the Odata EDM: NextShippingDate
In the delivery header, the field specifies the next planned picking or goods issue date.Using these dates in the headers of sales documents and deliveries, the system is able to recognize those documents for which processing time is critical.
@Nullable public LocalDateTime getNextCreditCheckDate()
Original property name from the Odata EDM: NextCreditCheckDate
The system stores this date if, during a dynamic credit check, some items or schedule lines in the document lie outside the credit horizon.
@Nullable public String getFinDocCreditCheckStatus()
Original property name from the Odata EDM: FinDocCreditCheckStatus
@Nullable public String getTotalCreditCheckStatus()
Original property name from the Odata EDM: TotalCreditCheckStatus
@Nullable public String getOverallSDProcessStatus()
Original property name from the Odata EDM: OverallSDProcessStatus
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
@Nullable public String getCentralCreditCheckStatus()
Original property name from the Odata EDM: CentralCreditCheckStatus
@Nullable public String getCentralCreditChkTechErrSts()
Original property name from the Odata EDM: CentralCreditChkTechErrSts
The technical error status of the sales document indicates whether the sales order was blocked due to a technical error during the sales document creation or changing.
@Nonnull public String toString()
toString
in class VdmObject<CreditBlockedSalesDocument>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<CreditBlockedSalesDocument>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<CreditBlockedSalesDocument>
public int hashCode()
hashCode
in class VdmObject<CreditBlockedSalesDocument>
Copyright © 2021 SAP SE. All rights reserved.