public static class SalesDocumentRjcnReason.SalesDocumentRjcnReasonBuilder extends Object
Modifier and Type | Method and Description |
---|---|
SalesDocumentRjcnReason |
build() |
SalesDocumentRjcnReason.SalesDocumentRjcnReasonBuilder |
salesDocumentRjcnReason_Text(String salesDocumentRjcnReason_Text)
Constraints: Not nullable, Maximum length: 40
|
SalesDocumentRjcnReason.SalesDocumentRjcnReasonBuilder |
salesDocumentRjcnReason(String salesDocumentRjcnReason)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
String |
toString() |
@Nonnull public SalesDocumentRjcnReason.SalesDocumentRjcnReasonBuilder salesDocumentRjcnReason(@Nullable String salesDocumentRjcnReason)
Original property name from the Odata EDM: SalesDocumentRjcnReason
The rejection can come from your organization (for example, you can reject a customer request for a credit memo because it is unreasonable) or from the customer (for example, the customer rejects a quotation because the price is too high). The following list shows the effects on different document types after you enter a reason for rejection:Inquiries and quotations: no further references by other documentsSales orders: no further delivery of itemsContracts: no further creation of release ordersCredit and debit memo requests: no further processing of credit or debit memosEnter one of the values predefined for your system.If you enter a reason for rejection, the system automatically cancels any MRP requirements previously generated for the items.
this
.@Nonnull public SalesDocumentRjcnReason.SalesDocumentRjcnReasonBuilder salesDocumentRjcnReason_Text(@Nullable String salesDocumentRjcnReason_Text)
Original property name from the Odata EDM: SalesDocumentRjcnReason_Text
this
.@Nonnull public SalesDocumentRjcnReason build()
Copyright © 2020 SAP SE. All rights reserved.