public static class CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder extends Object
public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder deliveryDocument(@Nullable String deliveryDocument)
Original property name from the Odata EDM: DeliveryDocument
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder shippingPoint(@Nullable String shippingPoint)
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps).If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars.The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually.
item.this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder lastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
orders.this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder controllingAreaCurrency(@Nullable String controllingAreaCurrency)
Original property name from the Odata EDM: ControllingAreaCurrency
credit control area.this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder creditBlockReleaseDate(@Nullable LocalDateTime creditBlockReleaseDate)
Original property name from the Odata EDM: CreditBlockReleaseDate
reasons.this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder 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
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder overallGoodsMovementStatus(@Nullable String overallGoodsMovementStatus)
Original property name from the Odata EDM: OverallGoodsMovementStatus
The status tells you whether the delivery has already left your warehouse, is still being processed, or whether processing has not yet begun.
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder totalCreditCheckStatus(@Nullable String totalCreditCheckStatus)
Original property name from the Odata EDM: TotalCreditCheckStatus
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder finDocCreditCheckStatus(@Nullable String finDocCreditCheckStatus)
Original property name from the Odata EDM: FinDocCreditCheckStatus
this
.public CreditBlockedDeliveryDoc.CreditBlockedDeliveryDocBuilder centralCreditCheckStatus(@Nullable String centralCreditCheckStatus)
Original property name from the Odata EDM: CentralCreditCheckStatus
this
.public CreditBlockedDeliveryDoc build()
Copyright © 2020 SAP SE. All rights reserved.