public class ReturnsDeliveryDocFlow extends VdmEntity<ReturnsDeliveryDocFlow>
Original entity name from the Odata EDM: A_ReturnsDeliveryDocFlowType
Modifier and Type | Class and Description |
---|---|
static class |
ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder |
Modifier and Type | Field and Description |
---|---|
static ReturnsDeliveryDocFlowSelectable |
ALL_FIELDS
Selector for all available fields of ReturnsDeliveryDocFlow.
|
static ReturnsDeliveryDocFlowField<String> |
DELIVERY_VERSION
Use with available fluent helpers to apply the DeliveryVersion field to query operations.
|
static ReturnsDeliveryDocFlowField<String> |
PRECEDING_DOCUMENT
Use with available fluent helpers to apply the PrecedingDocument field to query operations.
|
static ReturnsDeliveryDocFlowField<String> |
PRECEDING_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the PrecedingDocumentCategory field to query operations.
|
static ReturnsDeliveryDocFlowField<String> |
PRECEDING_DOCUMENT_ITEM
Use with available fluent helpers to apply the PrecedingDocumentItem field to query operations.
|
static ReturnsDeliveryDocFlowField<BigDecimal> |
QUANTITY_IN_BASE_UNIT
Use with available fluent helpers to apply the QuantityInBaseUnit field to query operations.
|
static ReturnsDeliveryDocFlowField<String> |
SD_FULFILLMENT_CALCULATION_RULE
Use with available fluent helpers to apply the SDFulfillmentCalculationRule field to query operations.
|
static ReturnsDeliveryDocFlowField<String> |
SUBSEQUENT_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the SubsequentDocumentCategory field to query operations.
|
static ReturnsDeliveryDocFlowField<String> |
SUBSEQUENT_DOCUMENT_ITEM
Use with available fluent helpers to apply the SubsequentDocumentItem field to query operations.
|
static ReturnsDeliveryDocFlowField<String> |
SUBSEQUENTDOCUMENT
Use with available fluent helpers to apply the Subsequentdocument field to query operations.
|
static ReturnsDeliveryDocFlowField<Boolean> |
TRANSFER_ORDER_IN_WRHS_MGMT_IS_CONFD
Use with available fluent helpers to apply the TransferOrderInWrhsMgmtIsConfd field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
ReturnsDeliveryDocFlow() |
ReturnsDeliveryDocFlow(String deliveryVersion,
String precedingDocument,
String precedingDocumentCategory,
String precedingDocumentItem,
String subsequentdocument,
BigDecimal quantityInBaseUnit,
String subsequentDocumentItem,
String sDFulfillmentCalculationRule,
String subsequentDocumentCategory,
Boolean transferOrderInWrhsMgmtIsConfd,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
static ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> ReturnsDeliveryDocFlowField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getDeliveryVersion()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: DeliveryVersion
|
protected String |
getEndpointUrl() |
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
protected Map<String,Object> |
getKey() |
String |
getPrecedingDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PrecedingDocument
|
String |
getPrecedingDocumentCategory()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PrecedingDocumentCategory
|
String |
getPrecedingDocumentItem()
(Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: PrecedingDocumentItem
|
BigDecimal |
getQuantityInBaseUnit()
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: QuantityInBaseUnitA sales order item has an order quantity of 100 pieces.
|
String |
getSDFulfillmentCalculationRule()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SDFulfillmentCalculationRuleThe system uses this indicator to determine how the quantity in the source document is affected.
|
String |
getSubsequentdocument()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Subsequentdocument
|
String |
getSubsequentDocumentCategory()
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SubsequentDocumentCategory
|
String |
getSubsequentDocumentItem()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SubsequentDocumentItem
|
Boolean |
getTransferOrderInWrhsMgmtIsConfd()
Constraints: noneOriginal property name from the Odata EDM: TransferOrderInWrhsMgmtIsConfd
|
Class<ReturnsDeliveryDocFlow> |
getType() |
int |
hashCode() |
void |
setDeliveryVersion(String deliveryVersion)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: DeliveryVersion
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setPrecedingDocument(String precedingDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PrecedingDocument
|
void |
setPrecedingDocumentCategory(String precedingDocumentCategory)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PrecedingDocumentCategory
|
void |
setPrecedingDocumentItem(String precedingDocumentItem)
(Key Field) Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: PrecedingDocumentItem
|
void |
setQuantityInBaseUnit(BigDecimal quantityInBaseUnit)
Constraints: Not nullable, Precision: 15, Scale: 3 Original property name from the Odata EDM: QuantityInBaseUnitA sales order item has an order quantity of 100 pieces.
|
void |
setSDFulfillmentCalculationRule(String sDFulfillmentCalculationRule)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SDFulfillmentCalculationRuleThe system uses this indicator to determine how the quantity in the source document is affected.
|
void |
setSubsequentdocument(String subsequentdocument)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Subsequentdocument
|
void |
setSubsequentDocumentCategory(String subsequentDocumentCategory)
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SubsequentDocumentCategory
|
void |
setSubsequentDocumentItem(String subsequentDocumentItem)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SubsequentDocumentItem
|
void |
setTransferOrderInWrhsMgmtIsConfd(Boolean transferOrderInWrhsMgmtIsConfd)
Constraints: noneOriginal property name from the Odata EDM: TransferOrderInWrhsMgmtIsConfd
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final ReturnsDeliveryDocFlowSelectable ALL_FIELDS
public static final ReturnsDeliveryDocFlowField<String> DELIVERY_VERSION
public static final ReturnsDeliveryDocFlowField<String> PRECEDING_DOCUMENT
public static final ReturnsDeliveryDocFlowField<String> PRECEDING_DOCUMENT_CATEGORY
public static final ReturnsDeliveryDocFlowField<String> PRECEDING_DOCUMENT_ITEM
public static final ReturnsDeliveryDocFlowField<String> SUBSEQUENTDOCUMENT
public static final ReturnsDeliveryDocFlowField<BigDecimal> QUANTITY_IN_BASE_UNIT
public static final ReturnsDeliveryDocFlowField<String> SUBSEQUENT_DOCUMENT_ITEM
public static final ReturnsDeliveryDocFlowField<String> SD_FULFILLMENT_CALCULATION_RULE
public static final ReturnsDeliveryDocFlowField<String> SUBSEQUENT_DOCUMENT_CATEGORY
public static final ReturnsDeliveryDocFlowField<Boolean> TRANSFER_ORDER_IN_WRHS_MGMT_IS_CONFD
public ReturnsDeliveryDocFlow()
public ReturnsDeliveryDocFlow(@Nullable String deliveryVersion, @Nullable String precedingDocument, @Nullable String precedingDocumentCategory, @Nullable String precedingDocumentItem, @Nullable String subsequentdocument, @Nullable BigDecimal quantityInBaseUnit, @Nullable String subsequentDocumentItem, @Nullable String sDFulfillmentCalculationRule, @Nullable String subsequentDocumentCategory, @Nullable Boolean transferOrderInWrhsMgmtIsConfd, @Nullable ErpConfigContext erpConfigContext)
public Class<ReturnsDeliveryDocFlow> getType()
getType
in class VdmObject<ReturnsDeliveryDocFlow>
public void setDeliveryVersion(@Nullable String deliveryVersion)
Original property name from the Odata EDM: DeliveryVersion
deliveryVersion
- Delivery Versionpublic void setPrecedingDocument(@Nullable String precedingDocument)
Original property name from the Odata EDM: PrecedingDocument
precedingDocument
- Number that uniquely identifies the preceding sales, delivery, or billing document (for example, the quotation from which you created a sales order).public void setPrecedingDocumentCategory(@Nullable String precedingDocumentCategory)
Original property name from the Odata EDM: PrecedingDocumentCategory
precedingDocumentCategory
- Specifies the sales document category of the preceding sales, delivery, or billing document.public void setPrecedingDocumentItem(@Nullable String precedingDocumentItem)
Original property name from the Odata EDM: PrecedingDocumentItem
precedingDocumentItem
- Preceding Item of an SD Documentpublic void setSubsequentdocument(@Nullable String subsequentdocument)
Original property name from the Odata EDM: Subsequentdocument
subsequentdocument
- Number that uniquely identifies the subsequent sales, delivery, or billing document (for example, the sales order that you create from a previous quotation).public void setQuantityInBaseUnit(@Nullable BigDecimal quantityInBaseUnit)
Original property name from the Odata EDM: QuantityInBaseUnit
A sales order item has an order quantity of 100 pieces. You create two delivery notes against the order: the first for 20 pieces, the second for 80 pieces. In the first case, the referenced quantity is 20 pieces; in the second case, 80 pieces.
quantityInBaseUnit
- Specifies how much of an item quantity has already been processed in a subsequent document. The referenced quantity is expressed in basic stock units.public void setSubsequentDocumentItem(@Nullable String subsequentDocumentItem)
Original property name from the Odata EDM: SubsequentDocumentItem
subsequentDocumentItem
- Number that uniquely identifies the item in the subsequent document (for example, in a sales order that you created from a quotation).public void setSDFulfillmentCalculationRule(@Nullable String sDFulfillmentCalculationRule)
Original property name from the Odata EDM: SDFulfillmentCalculationRule
The system uses this indicator to determine how the quantity in the source document is affected. For example, if youCreate a quotation item for 100 pieces,Copy the quotation into a sales order, andCreate a sales order item for 80 pieces,the copying has a positive effect on the quotation. In effect, you have added 80 pieces to the quotation quantity that is now considered complete. 20 pieces in the quotation remain to be completed.If you do not make an entry in this field, or set indicator 0, the source document is not blocked, which allows you to create several target documents at once (for example, when using EDI and frequent contract releases).While the source document (such as quotation or quantity contract) is being processed, it is blocked. For instance, if you are working on a quantity contract, no one can create a release order for that contract).In sales documents, for example, you can expect the following results:Quotation -> Sales order: positiveContract -> Return: negativeSales order -> Sales order: no effectIn billing documents, for example, you can expect the following results:Delivery -> Invoice: positiveDelivery -> Cancellation: negativeDelivery -> Pro-forma invoice: no effect
sDFulfillmentCalculationRule
- Indicates whether, during copying, the quantity or value in the target document has a negative effect, positive effect, or no effect at all on the quantity still to be completed in the source document.public void setSubsequentDocumentCategory(@Nullable String subsequentDocumentCategory)
Original property name from the Odata EDM: SubsequentDocumentCategory
subsequentDocumentCategory
- The document category of the sales document that you have created from a preceding document (for example, a delivery note that has been created from a sales order).public void setTransferOrderInWrhsMgmtIsConfd(@Nullable Boolean transferOrderInWrhsMgmtIsConfd)
Original property name from the Odata EDM: TransferOrderInWrhsMgmtIsConfd
transferOrderInWrhsMgmtIsConfd
- Indicates whether the transfer order in the warehouse management (WM) system is confirmed.protected String getEndpointUrl()
getEndpointUrl
in class VdmEntity<ReturnsDeliveryDocFlow>
protected String getEntityCollection()
getEntityCollection
in class VdmEntity<ReturnsDeliveryDocFlow>
protected Map<String,Object> getKey()
getKey
in class VdmObject<ReturnsDeliveryDocFlow>
protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<ReturnsDeliveryDocFlow>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<ReturnsDeliveryDocFlow>
public static <T> ReturnsDeliveryDocFlowField<T> field(String fieldName, Class<T> fieldType)
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.public static ReturnsDeliveryDocFlow.ReturnsDeliveryDocFlowBuilder builder()
@Nullable public String getDeliveryVersion()
Original property name from the Odata EDM: DeliveryVersion
@Nullable public String getPrecedingDocument()
Original property name from the Odata EDM: PrecedingDocument
@Nullable public String getPrecedingDocumentCategory()
Original property name from the Odata EDM: PrecedingDocumentCategory
@Nullable public String getPrecedingDocumentItem()
Original property name from the Odata EDM: PrecedingDocumentItem
@Nullable public String getSubsequentdocument()
Original property name from the Odata EDM: Subsequentdocument
@Nullable public BigDecimal getQuantityInBaseUnit()
Original property name from the Odata EDM: QuantityInBaseUnit
A sales order item has an order quantity of 100 pieces. You create two delivery notes against the order: the first for 20 pieces, the second for 80 pieces. In the first case, the referenced quantity is 20 pieces; in the second case, 80 pieces.
@Nullable public String getSubsequentDocumentItem()
Original property name from the Odata EDM: SubsequentDocumentItem
@Nullable public String getSDFulfillmentCalculationRule()
Original property name from the Odata EDM: SDFulfillmentCalculationRule
The system uses this indicator to determine how the quantity in the source document is affected. For example, if youCreate a quotation item for 100 pieces,Copy the quotation into a sales order, andCreate a sales order item for 80 pieces,the copying has a positive effect on the quotation. In effect, you have added 80 pieces to the quotation quantity that is now considered complete. 20 pieces in the quotation remain to be completed.If you do not make an entry in this field, or set indicator 0, the source document is not blocked, which allows you to create several target documents at once (for example, when using EDI and frequent contract releases).While the source document (such as quotation or quantity contract) is being processed, it is blocked. For instance, if you are working on a quantity contract, no one can create a release order for that contract).In sales documents, for example, you can expect the following results:Quotation -> Sales order: positiveContract -> Return: negativeSales order -> Sales order: no effectIn billing documents, for example, you can expect the following results:Delivery -> Invoice: positiveDelivery -> Cancellation: negativeDelivery -> Pro-forma invoice: no effect
@Nullable public String getSubsequentDocumentCategory()
Original property name from the Odata EDM: SubsequentDocumentCategory
@Nullable public Boolean getTransferOrderInWrhsMgmtIsConfd()
Original property name from the Odata EDM: TransferOrderInWrhsMgmtIsConfd
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<ReturnsDeliveryDocFlow>
erpConfigContext
- public String toString()
toString
in class VdmObject<ReturnsDeliveryDocFlow>
public boolean equals(Object o)
equals
in class VdmObject<ReturnsDeliveryDocFlow>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<ReturnsDeliveryDocFlow>
public int hashCode()
hashCode
in class VdmObject<ReturnsDeliveryDocFlow>
Copyright © 2018 SAP SE. All rights reserved.