public static class CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder extends Object
@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder salesDocument(@Nullable String salesDocument)
Original property name from the Odata EDM: SalesDocument
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder sDDocumentCategory(@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).
sales orders, deliveries, and invoices.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder salesDocumentType(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder salesOrganization(@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.
sales organization may include legal liability for products and customer claims.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder distributionChannel(@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.
wholesale, retail, or direct sales.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder organizationDivision(@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.
areas and the business areas for a material, product, or service.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder salesOffice(@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.
products or services within a given geographical area.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder salesGroup(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder lastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
orders.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder totalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
account. The value is expressed in the document currency.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder transactionCurrency(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder customerCreditAccount(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder controllingAreaCurrency(@Nullable String controllingAreaCurrency)
Original property name from the Odata EDM: ControllingAreaCurrency
credit control area.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder releasedCreditAmount(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder creditBlockReleaseDate(@Nullable LocalDateTime creditBlockReleaseDate)
Original property name from the Odata EDM: CreditBlockReleaseDate
reasons.this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder nextShippingDate(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder nextCreditCheckDate(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder finDocCreditCheckStatus(@Nullable String finDocCreditCheckStatus)
Original property name from the Odata EDM: FinDocCreditCheckStatus
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder totalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder overallSDProcessStatus(@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.
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder centralCreditCheckStatus(@Nullable String centralCreditCheckStatus)
Original property name from the Odata EDM: CentralCreditCheckStatus
this
.@Nonnull public CreditBlockedSalesDocument.CreditBlockedSalesDocumentBuilder centralCreditChkTechErrSts(@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.
this
.@Nonnull public CreditBlockedSalesDocument build()
Copyright © 2021 SAP SE. All rights reserved.