public class BillingDocumentRequestItem extends VdmEntity<BillingDocumentRequestItem>
Original entity name from the Odata EDM: A_BillingDocumentRequestItemType
Modifier and Type | Class and Description |
---|---|
static class |
BillingDocumentRequestItem.BillingDocumentRequestItemBuilder |
Modifier and Type | Field and Description |
---|---|
static BillingDocumentRequestItemField<BigDecimal> |
ABSLT_PRICE_DETN_EXCHANGE_RATE
Use with available fluent helpers to apply the AbsltPriceDetnExchangeRate field to query operations.
|
static BillingDocumentRequestItemSelectable |
ALL_FIELDS
Selector for all available fields of BillingDocumentRequestItem.
|
static BillingDocumentRequestItemField<String> |
BILLG_DOC_REQUEST_ITEM_IN_PART_SGMT
Use with available fluent helpers to apply the BillgDocRequestItemInPartSgmt field to query operations.
|
static BillingDocumentRequestItemField<String> |
BILLING_DOCUMENT_REQUEST
Use with available fluent helpers to apply the BillingDocumentRequest field to query operations.
|
static BillingDocumentRequestItemField<String> |
BILLING_DOCUMENT_REQUEST_ITEM
Use with available fluent helpers to apply the BillingDocumentRequestItem field to query operations.
|
static BillingDocumentRequestItemField<String> |
BILLING_DOCUMENT_REQUEST_ITEM_TEXT
Use with available fluent helpers to apply the BillingDocumentRequestItemText field to query operations.
|
static BillingDocumentRequestItemField<BigDecimal> |
BILLING_QUANTITY
Use with available fluent helpers to apply the BillingQuantity field to query operations.
|
static BillingDocumentRequestItemField<String> |
BILLING_QUANTITY_UNIT
Use with available fluent helpers to apply the BillingQuantityUnit field to query operations.
|
static BillingDocumentRequestItemField<String> |
BUSINESS_AREA
Use with available fluent helpers to apply the BusinessArea field to query operations.
|
static BillingDocumentRequestItemField<String> |
CONTROLLING_AREA
Use with available fluent helpers to apply the ControllingArea field to query operations.
|
static BillingDocumentRequestItemField<String> |
COST_CENTER
Use with available fluent helpers to apply the CostCenter field to query operations.
|
static BillingDocumentRequestItemField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static BillingDocumentRequestItemField<LocalTime> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static BillingDocumentRequestItemField<String> |
DEPARTURE_COUNTRY
Use with available fluent helpers to apply the DepartureCountry field to query operations.
|
static BillingDocumentRequestItemField<String> |
DIVISION
Use with available fluent helpers to apply the Division field to query operations.
|
static BillingDocumentRequestItemField<BigDecimal> |
GROSS_AMOUNT
Use with available fluent helpers to apply the GrossAmount field to query operations.
|
static BillingDocumentRequestItemField<String> |
HIGHER_LEVEL_ITEM
Use with available fluent helpers to apply the HigherLevelItem field to query operations.
|
static BillingDocumentRequestItemField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static BillingDocumentRequestItemField<String> |
MATL_ACCOUNT_ASSIGNMENT_GROUP
Use with available fluent helpers to apply the MatlAccountAssignmentGroup field to query operations.
|
static BillingDocumentRequestItemField<BigDecimal> |
NET_AMOUNT
Use with available fluent helpers to apply the NetAmount field to query operations.
|
static BillingDocumentRequestItemField<String> |
ORDER_ID
Use with available fluent helpers to apply the OrderID field to query operations.
|
static BillingDocumentRequestItemField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static BillingDocumentRequestItemField<Boolean> |
PRICE_DETN_EXCH_RATE_IS_INDRCT_QTAN
Use with available fluent helpers to apply the PriceDetnExchRateIsIndrctQtan field to query operations.
|
static BillingDocumentRequestItemField<LocalDateTime> |
PRICING_DATE
Use with available fluent helpers to apply the PricingDate field to query operations.
|
static BillingDocumentRequestItemField<String> |
PRODUCT_HIERARCHY_NODE
Use with available fluent helpers to apply the ProductHierarchyNode field to query operations.
|
static BillingDocumentRequestItemField<String> |
PRODUCT_TAX_CLASSIFICATION1
Use with available fluent helpers to apply the ProductTaxClassification1 field to query operations.
|
static BillingDocumentRequestItemField<String> |
PROFIT_CENTER
Use with available fluent helpers to apply the ProfitCenter field to query operations.
|
static BillingDocumentRequestItemField<String> |
PROFITABILITY_SEGMENT
Use with available fluent helpers to apply the ProfitabilitySegment field to query operations.
|
static BillingDocumentRequestItemField<String> |
REFERENCE_DOCUMENT
Use with available fluent helpers to apply the ReferenceDocument field to query operations.
|
static BillingDocumentRequestItemField<String> |
REFERENCE_DOCUMENT_ITEM
Use with available fluent helpers to apply the ReferenceDocumentItem field to query operations.
|
static BillingDocumentRequestItemField<String> |
REFERENCE_LOGICAL_SYSTEM
Use with available fluent helpers to apply the ReferenceLogicalSystem field to query operations.
|
static BillingDocumentRequestItemField<LocalDateTime> |
SERVICES_RENDERED_DATE
Use with available fluent helpers to apply the ServicesRenderedDate field to query operations.
|
static BillingDocumentRequestItemField<BigDecimal> |
TAX_AMOUNT
Use with available fluent helpers to apply the TaxAmount field to query operations.
|
static BillingDocumentRequestItemField<String> |
TAX_JURISDICTION
Use with available fluent helpers to apply the TaxJurisdiction field to query operations.
|
static BillingDocumentRequestItemLink<BillingDocumentRequest> |
TO_BILLING_DOCUMENT_REQUEST
Use with available fluent helpers to apply the to_BillingDocumentRequest navigation property to query operations.
|
static BillingDocumentRequestItemLink<BillingDocReqItemPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static BillingDocumentRequestItemLink<BillingDocReqItemPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static BillingDocumentRequestItemField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
static BillingDocumentRequestItemField<String> |
WBS_ELEMENT
Use with available fluent helpers to apply the WBSElement field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
BillingDocumentRequestItem() |
BillingDocumentRequestItem(String billingDocumentRequest,
String billingDocumentRequestItem,
LocalDateTime creationDate,
LocalTime creationTime,
String referenceLogicalSystem,
String division,
String material,
String productHierarchyNode,
String plant,
String billingDocumentRequestItemText,
LocalDateTime servicesRenderedDate,
BigDecimal billingQuantity,
String billingQuantityUnit,
BigDecimal netAmount,
String transactionCurrency,
BigDecimal grossAmount,
LocalDateTime pricingDate,
BigDecimal absltPriceDetnExchangeRate,
Boolean priceDetnExchRateIsIndrctQtan,
BigDecimal taxAmount,
String departureCountry,
String taxJurisdiction,
String productTaxClassification1,
String businessArea,
String profitCenter,
String wBSElement,
String controllingArea,
String profitabilitySegment,
String orderID,
String costCenter,
String matlAccountAssignmentGroup,
String referenceDocument,
String referenceDocumentItem,
String higherLevelItem,
String billgDocRequestItemInPartSgmt,
ErpConfigContext erpConfigContext,
BillingDocumentRequest toBillingDocumentRequest,
List<BillingDocReqItemPartner> toPartner,
List<BillingDocReqItemPrcgElmnt> toPricingElement) |
Modifier and Type | Method and Description |
---|---|
void |
addPartner(BillingDocReqItemPartner... entity)
Adds elements to the list of associated BillingDocReqItemPartner entities.
|
void |
addPricingElement(BillingDocReqItemPrcgElmnt... entity)
Adds elements to the list of associated BillingDocReqItemPrcgElmnt entities.
|
static BillingDocumentRequestItem.BillingDocumentRequestItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
BillingDocumentRequest |
fetchBillingDocumentRequest()
Fetches the BillingDocumentRequest entity (one to one) associated with this entity.
|
List<BillingDocReqItemPartner> |
fetchPartner()
Fetches the BillingDocReqItemPartner entities (one to many) associated with this entity.
|
List<BillingDocReqItemPrcgElmnt> |
fetchPricingElement()
Fetches the BillingDocReqItemPrcgElmnt entities (one to many) associated with this entity.
|
static <T> BillingDocumentRequestItemField<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) |
BigDecimal |
getAbsltPriceDetnExchangeRate()
Constraints: Not nullable, Precision: 9, Scale: 5
|
String |
getBillgDocRequestItemInPartSgmt()
Constraints: Not nullable, Maximum length: 6
|
String |
getBillingDocumentRequest()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
Optional<BillingDocumentRequest> |
getBillingDocumentRequestIfPresent()
Retrieval of associated BillingDocumentRequest entity (one to one).
|
String |
getBillingDocumentRequestItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getBillingDocumentRequestItemText()
Constraints: Not nullable, Maximum length: 40
|
BillingDocumentRequest |
getBillingDocumentRequestOrFetch()
Retrieval of associated BillingDocumentRequest entity (one to one).
|
BigDecimal |
getBillingQuantity()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getBillingQuantityUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getBusinessArea()
Constraints: Not nullable, Maximum length: 4
|
String |
getControllingArea()
Constraints: Not nullable, Maximum length: 4
|
String |
getCostCenter()
Constraints: Not nullable, Maximum length: 10
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
String |
getDepartureCountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getDivision()
Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
BigDecimal |
getGrossAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getHigherLevelItem()
Constraints: Not nullable, Maximum length: 6
|
protected Map<String,Object> |
getKey() |
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMatlAccountAssignmentGroup()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getOrderID()
Constraints: Not nullable, Maximum length: 12
|
Optional<List<BillingDocReqItemPartner>> |
getPartnerIfPresent()
Retrieval of associated BillingDocReqItemPartner entities (one to many).
|
List<BillingDocReqItemPartner> |
getPartnerOrFetch()
Retrieval of associated BillingDocReqItemPartner entities (one to many).
|
String |
getPlant()
Constraints: Not nullable, Maximum length: 4
|
Boolean |
getPriceDetnExchRateIsIndrctQtan()
Constraints: none
|
LocalDateTime |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
Optional<List<BillingDocReqItemPrcgElmnt>> |
getPricingElementIfPresent()
Retrieval of associated BillingDocReqItemPrcgElmnt entities (one to many).
|
List<BillingDocReqItemPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated BillingDocReqItemPrcgElmnt entities (one to many).
|
String |
getProductHierarchyNode()
Constraints: Not nullable, Maximum length: 18
|
String |
getProductTaxClassification1()
Constraints: Not nullable, Maximum length: 1
|
String |
getProfitabilitySegment()
Constraints: Not nullable, Maximum length: 10
|
String |
getProfitCenter()
Constraints: Not nullable, Maximum length: 10
|
String |
getReferenceDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getReferenceDocumentItem()
Constraints: Not nullable, Maximum length: 6
|
String |
getReferenceLogicalSystem()
Constraints: Not nullable, Maximum length: 10
|
LocalDateTime |
getServicesRenderedDate()
Constraints: Not nullable, Precision: 0
|
BigDecimal |
getTaxAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
String |
getTaxJurisdiction()
Constraints: Not nullable, Maximum length: 15
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<BillingDocumentRequestItem> |
getType() |
String |
getWBSElement()
Constraints: Not nullable, Maximum length: 24
|
int |
hashCode() |
void |
setAbsltPriceDetnExchangeRate(BigDecimal absltPriceDetnExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5
|
void |
setBillgDocRequestItemInPartSgmt(String billgDocRequestItemInPartSgmt)
Constraints: Not nullable, Maximum length: 6
|
void |
setBillingDocumentRequest(BillingDocumentRequest value)
Overwrites the associated BillingDocumentRequest entity for the loaded navigation property to_BillingDocumentRequest.
|
void |
setBillingDocumentRequest(String billingDocumentRequest)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setBillingDocumentRequestItem(String billingDocumentRequestItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setBillingDocumentRequestItemText(String billingDocumentRequestItemText)
Constraints: Not nullable, Maximum length: 40
|
void |
setBillingQuantity(BigDecimal billingQuantity)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setBillingQuantityUnit(String billingQuantityUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setBusinessArea(String businessArea)
Constraints: Not nullable, Maximum length: 4
|
void |
setControllingArea(String controllingArea)
Constraints: Not nullable, Maximum length: 4
|
void |
setCostCenter(String costCenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setDepartureCountry(String departureCountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setDivision(String division)
Constraints: Not nullable, Maximum length: 2
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setGrossAmount(BigDecimal grossAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setHigherLevelItem(String higherLevelItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40
|
void |
setMatlAccountAssignmentGroup(String matlAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setNetAmount(BigDecimal netAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setOrderID(String orderID)
Constraints: Not nullable, Maximum length: 12
|
void |
setPartner(List<BillingDocReqItemPartner> value)
Overwrites the list of associated BillingDocReqItemPartner entities for the loaded navigation property to_Partner.
|
void |
setPlant(String plant)
Constraints: Not nullable, Maximum length: 4
|
void |
setPriceDetnExchRateIsIndrctQtan(Boolean priceDetnExchRateIsIndrctQtan)
Constraints: none
|
void |
setPricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
void |
setPricingElement(List<BillingDocReqItemPrcgElmnt> value)
Overwrites the list of associated BillingDocReqItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
|
void |
setProductHierarchyNode(String productHierarchyNode)
Constraints: Not nullable, Maximum length: 18
|
void |
setProductTaxClassification1(String productTaxClassification1)
Constraints: Not nullable, Maximum length: 1
|
void |
setProfitabilitySegment(String profitabilitySegment)
Constraints: Not nullable, Maximum length: 10
|
void |
setProfitCenter(String profitCenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setReferenceDocument(String referenceDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setReferenceDocumentItem(String referenceDocumentItem)
Constraints: Not nullable, Maximum length: 6
|
void |
setReferenceLogicalSystem(String referenceLogicalSystem)
Constraints: Not nullable, Maximum length: 10
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setServicesRenderedDate(LocalDateTime servicesRenderedDate)
Constraints: Not nullable, Precision: 0
|
void |
setTaxAmount(BigDecimal taxAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setTaxJurisdiction(String taxJurisdiction)
Constraints: Not nullable, Maximum length: 15
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setWBSElement(String wBSElement)
Constraints: Not nullable, Maximum length: 24
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getEndpointUrl, getServicePathForFetch, getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final BillingDocumentRequestItemSelectable ALL_FIELDS
public static final BillingDocumentRequestItemField<String> BILLING_DOCUMENT_REQUEST
public static final BillingDocumentRequestItemField<String> BILLING_DOCUMENT_REQUEST_ITEM
public static final BillingDocumentRequestItemField<LocalDateTime> CREATION_DATE
public static final BillingDocumentRequestItemField<LocalTime> CREATION_TIME
public static final BillingDocumentRequestItemField<String> REFERENCE_LOGICAL_SYSTEM
public static final BillingDocumentRequestItemField<String> DIVISION
public static final BillingDocumentRequestItemField<String> MATERIAL
public static final BillingDocumentRequestItemField<String> PRODUCT_HIERARCHY_NODE
public static final BillingDocumentRequestItemField<String> PLANT
public static final BillingDocumentRequestItemField<String> BILLING_DOCUMENT_REQUEST_ITEM_TEXT
public static final BillingDocumentRequestItemField<LocalDateTime> SERVICES_RENDERED_DATE
public static final BillingDocumentRequestItemField<BigDecimal> BILLING_QUANTITY
public static final BillingDocumentRequestItemField<String> BILLING_QUANTITY_UNIT
public static final BillingDocumentRequestItemField<BigDecimal> NET_AMOUNT
public static final BillingDocumentRequestItemField<String> TRANSACTION_CURRENCY
public static final BillingDocumentRequestItemField<BigDecimal> GROSS_AMOUNT
public static final BillingDocumentRequestItemField<LocalDateTime> PRICING_DATE
public static final BillingDocumentRequestItemField<BigDecimal> ABSLT_PRICE_DETN_EXCHANGE_RATE
public static final BillingDocumentRequestItemField<Boolean> PRICE_DETN_EXCH_RATE_IS_INDRCT_QTAN
public static final BillingDocumentRequestItemField<BigDecimal> TAX_AMOUNT
public static final BillingDocumentRequestItemField<String> DEPARTURE_COUNTRY
public static final BillingDocumentRequestItemField<String> TAX_JURISDICTION
public static final BillingDocumentRequestItemField<String> PRODUCT_TAX_CLASSIFICATION1
public static final BillingDocumentRequestItemField<String> BUSINESS_AREA
public static final BillingDocumentRequestItemField<String> PROFIT_CENTER
public static final BillingDocumentRequestItemField<String> WBS_ELEMENT
public static final BillingDocumentRequestItemField<String> CONTROLLING_AREA
public static final BillingDocumentRequestItemField<String> PROFITABILITY_SEGMENT
public static final BillingDocumentRequestItemField<String> ORDER_ID
public static final BillingDocumentRequestItemField<String> COST_CENTER
public static final BillingDocumentRequestItemField<String> MATL_ACCOUNT_ASSIGNMENT_GROUP
public static final BillingDocumentRequestItemField<String> REFERENCE_DOCUMENT
public static final BillingDocumentRequestItemField<String> REFERENCE_DOCUMENT_ITEM
public static final BillingDocumentRequestItemField<String> HIGHER_LEVEL_ITEM
public static final BillingDocumentRequestItemField<String> BILLG_DOC_REQUEST_ITEM_IN_PART_SGMT
public static final BillingDocumentRequestItemLink<BillingDocumentRequest> TO_BILLING_DOCUMENT_REQUEST
public static final BillingDocumentRequestItemLink<BillingDocReqItemPartner> TO_PARTNER
public static final BillingDocumentRequestItemLink<BillingDocReqItemPrcgElmnt> TO_PRICING_ELEMENT
public BillingDocumentRequestItem()
public BillingDocumentRequestItem(@Nullable String billingDocumentRequest, @Nullable String billingDocumentRequestItem, @Nullable LocalDateTime creationDate, @Nullable LocalTime creationTime, @Nullable String referenceLogicalSystem, @Nullable String division, @Nullable String material, @Nullable String productHierarchyNode, @Nullable String plant, @Nullable String billingDocumentRequestItemText, @Nullable LocalDateTime servicesRenderedDate, @Nullable BigDecimal billingQuantity, @Nullable String billingQuantityUnit, @Nullable BigDecimal netAmount, @Nullable String transactionCurrency, @Nullable BigDecimal grossAmount, @Nullable LocalDateTime pricingDate, @Nullable BigDecimal absltPriceDetnExchangeRate, @Nullable Boolean priceDetnExchRateIsIndrctQtan, @Nullable BigDecimal taxAmount, @Nullable String departureCountry, @Nullable String taxJurisdiction, @Nullable String productTaxClassification1, @Nullable String businessArea, @Nullable String profitCenter, @Nullable String wBSElement, @Nullable String controllingArea, @Nullable String profitabilitySegment, @Nullable String orderID, @Nullable String costCenter, @Nullable String matlAccountAssignmentGroup, @Nullable String referenceDocument, @Nullable String referenceDocumentItem, @Nullable String higherLevelItem, @Nullable String billgDocRequestItemInPartSgmt, @Nullable ErpConfigContext erpConfigContext, @Nullable BillingDocumentRequest toBillingDocumentRequest, List<BillingDocReqItemPartner> toPartner, List<BillingDocReqItemPrcgElmnt> toPricingElement)
@Nonnull public Class<BillingDocumentRequestItem> getType()
getType
in class VdmObject<BillingDocumentRequestItem>
public void setBillingDocumentRequest(@Nullable String billingDocumentRequest)
Original property name from the Odata EDM: BillingDocumentRequest
billingDocumentRequest
- Billing Document Requestpublic void setBillingDocumentRequestItem(@Nullable String billingDocumentRequestItem)
Original property name from the Odata EDM: BillingDocumentRequestItem
billingDocumentRequestItem
- Billing Document Request Itempublic void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on Which Record Was Createdpublic void setCreationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
creationTime
- The time of day at which the document was posted and stored in the system.public void setReferenceLogicalSystem(@Nullable String referenceLogicalSystem)
Original property name from the Odata EDM: ReferenceLogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
referenceLogicalSystem
- System in which applications run integrated on a shared data basis.public void setDivision(@Nullable String division)
Original property name from the Odata EDM: Division
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.
division
- 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 setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setProductHierarchyNode(@Nullable String productHierarchyNode)
Original property name from the Odata EDM: ProductHierarchyNode
In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.Level Number of characters allowed1 52 53 8You define a product hierarchy with the following levels:Level Example Description1 00005 Electrical goods2 00003 Wet appliances3 00000001 Washing machineIn this case, a washing machine belongs to the product hierarchy 000050000300000001.
productHierarchyNode
- Alphanumeric character string for grouping together materials by combining different characteristics. It is used for analyses and price determination.public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setBillingDocumentRequestItemText(@Nullable String billingDocumentRequestItemText)
Original property name from the Odata EDM: BillingDocumentRequestItemText
Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations.The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
billingDocumentRequestItemText
- A short description of the item.public void setServicesRenderedDate(@Nullable LocalDateTime servicesRenderedDate)
Original property name from the Odata EDM: ServicesRenderedDate
If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
servicesRenderedDate
- The date of services rendered that determines when the system calculates taxes (for example, sales tax) for the material.public void setBillingQuantity(@Nullable BigDecimal billingQuantity)
Original property name from the Odata EDM: BillingQuantity
For assets in which a base unit of measure is entered, you can enter a quantity when you post acquisitions and retirements. The system then updates the asset according to this quantity when you post, based on the debit/credit flag of the transaction posted.In addition, you can already specify a quantity when you create a new asset master record. However, any quantity you enter in master data maintenance (such as 1) is added to any quantity that is entered in the acquisition posting.
billingQuantity
- Quantity that the system manages on the assetpublic void setBillingQuantityUnit(@Nullable String billingQuantityUnit)
Original property name from the Odata EDM: BillingQuantityUnit
billingQuantityUnit
- Unit of measure in which the material is sold.public void setNetAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
netAmount
- The net value of the billing item including discounts, surcharges and other pricing conditions (such as freight costs), but excluding sales taxes.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 setGrossAmount(@Nullable BigDecimal grossAmount)
Original property name from the Odata EDM: GrossAmount
grossAmount
- Net value of the billing item including all surcharges and discounts as well as price determination conditions (e.g. freight costs) but without VAT.public void setPricingDate(@Nullable LocalDateTime pricingDate)
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
pricingDate
- The date that determines date-related pricing elements, such as conditions and foreign exchange rate.public void setAbsltPriceDetnExchangeRate(@Nullable BigDecimal absltPriceDetnExchangeRate)
Original property name from the Odata EDM: AbsltPriceDetnExchangeRate
absltPriceDetnExchangeRate
- Exchange rate for price determinationpublic void setPriceDetnExchRateIsIndrctQtan(@Nullable Boolean priceDetnExchRateIsIndrctQtan)
Original property name from the Odata EDM: PriceDetnExchRateIsIndrctQtan
priceDetnExchRateIsIndrctQtan
- Pricing exchange rate quotation is indirectpublic void setTaxAmount(@Nullable BigDecimal taxAmount)
Original property name from the Odata EDM: TaxAmount
taxAmount
- The total sales taxes, expressed in the document currency.public void setDepartureCountry(@Nullable String departureCountry)
Original property name from the Odata EDM: DepartureCountry
You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key tohelp determine the relevant taxes during pricingdetermine important country-specific standards (the length of postal codes and bank account numbers, for example)
departureCountry
- Identifies the country in which the delivery originates.public void setTaxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
taxJurisdiction
- The tax jurisdiction is used for determining the tax rates in the USA. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied.public void setProductTaxClassification1(@Nullable String productTaxClassification1)
Original property name from the Odata EDM: ProductTaxClassification1
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
productTaxClassification1
- Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, state sales taxes).public void setBusinessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
businessArea
- Key that uniquely identifies a business area.public void setProfitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
profitCenter
- Key which together with the controlling area uniquely identifies a profit center.public void setWBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
wBSElement
- Key that identifies a WBS element.public void setControllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
controllingArea
- Uniquely identifies a controlling area.public void setProfitabilitySegment(@Nullable String profitabilitySegment)
Original property name from the Odata EDM: ProfitabilitySegment
Examples:Customer '123'/Product '4710' Profitability segment no. 1Customer '123'/Product '4712' Profitability segment no. 2Country 'USA'/Region 'NORTH' Profitability segment no. 3
profitabilitySegment
- See glossarypublic void setOrderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
orderID
- Key that uniquely identifies an order within a client.public void setCostCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
costCenter
- A key that uniquely identifies a cost center.public void setMatlAccountAssignmentGroup(@Nullable String matlAccountAssignmentGroup)
Original property name from the Odata EDM: MatlAccountAssignmentGroup
Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
matlAccountAssignmentGroup
- Group of materials with the same accounting requirements.public void setReferenceDocument(@Nullable String referenceDocument)
Original property name from the Odata EDM: ReferenceDocument
referenceDocument
- Identifies the sales order to which the delivery refers.public void setReferenceDocumentItem(@Nullable String referenceDocumentItem)
Original property name from the Odata EDM: ReferenceDocumentItem
referenceDocumentItem
- The number of the sales order item to which the delivery item refers.public void setHigherLevelItem(@Nullable String higherLevelItem)
Original property name from the Odata EDM: HigherLevelItem
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.
higherLevelItem
- The number of the higher-level item to which this item belongs in a hierarchy.public void setBillgDocRequestItemInPartSgmt(@Nullable String billgDocRequestItemInPartSgmt)
Original property name from the Odata EDM: BillgDocRequestItemInPartSgmt
billgDocRequestItemInPartSgmt
- Item number in the partner segmentprotected String getEntityCollection()
getEntityCollection
in class VdmEntity<BillingDocumentRequestItem>
protected Map<String,Object> getKey()
getKey
in class VdmObject<BillingDocumentRequestItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<BillingDocumentRequestItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<BillingDocumentRequestItem>
@Nonnull public static <T> BillingDocumentRequestItemField<T> field(@Nonnull String fieldName, @Nonnull 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.@Nonnull public static <T,DomainT> BillingDocumentRequestItemField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.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<BillingDocumentRequestItem>
protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<BillingDocumentRequestItem>
@Nullable public BillingDocumentRequest fetchBillingDocumentRequest() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
null
if an entity is not associated.com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.@Nullable public BillingDocumentRequest getBillingDocumentRequestOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_BillingDocumentRequest of a queried BillingDocumentRequestItem is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.@Nonnull public Optional<BillingDocumentRequest> getBillingDocumentRequestIfPresent()
If the navigation property for an entity BillingDocumentRequestItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setBillingDocumentRequest(BillingDocumentRequest value)
value
- New BillingDocumentRequest entity.@Nonnull public List<BillingDocReqItemPartner> fetchPartner() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.@Nonnull public List<BillingDocReqItemPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried BillingDocumentRequestItem is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.@Nonnull public Optional<List<BillingDocReqItemPartner>> getPartnerIfPresent()
If the navigation property for an entity BillingDocumentRequestItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setPartner(@Nonnull List<BillingDocReqItemPartner> value)
If the navigation property to_Partner of a queried BillingDocumentRequestItem is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of BillingDocReqItemPartner entities.public void addPartner(BillingDocReqItemPartner... entity)
If the navigation property to_Partner of a queried BillingDocumentRequestItem is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of BillingDocReqItemPartner entities.@Nonnull public List<BillingDocReqItemPrcgElmnt> fetchPricingElement() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.@Nonnull public List<BillingDocReqItemPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried BillingDocumentRequestItem is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.@Nonnull public Optional<List<BillingDocReqItemPrcgElmnt>> getPricingElementIfPresent()
If the navigation property for an entity BillingDocumentRequestItem has not been resolved yet, this method will not query further information. Instead its Optional
result state will be empty
.
Optional
with result state empty
is returned.public void setPricingElement(@Nonnull List<BillingDocReqItemPrcgElmnt> value)
If the navigation property to_PricingElement of a queried BillingDocumentRequestItem is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of BillingDocReqItemPrcgElmnt entities.public void addPricingElement(BillingDocReqItemPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried BillingDocumentRequestItem is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of BillingDocReqItemPrcgElmnt entities.public static BillingDocumentRequestItem.BillingDocumentRequestItemBuilder builder()
@Nullable public String getBillingDocumentRequest()
Original property name from the Odata EDM: BillingDocumentRequest
@Nullable public String getBillingDocumentRequestItem()
Original property name from the Odata EDM: BillingDocumentRequestItem
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public LocalTime getCreationTime()
Original property name from the Odata EDM: CreationTime
@Nullable public String getReferenceLogicalSystem()
Original property name from the Odata EDM: ReferenceLogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
@Nullable public String getDivision()
Original property name from the Odata EDM: Division
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 getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getProductHierarchyNode()
Original property name from the Odata EDM: ProductHierarchyNode
In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.Level Number of characters allowed1 52 53 8You define a product hierarchy with the following levels:Level Example Description1 00005 Electrical goods2 00003 Wet appliances3 00000001 Washing machineIn this case, a washing machine belongs to the product hierarchy 000050000300000001.
@Nullable public String getPlant()
Original property name from the Odata EDM: Plant
@Nullable public String getBillingDocumentRequestItemText()
Original property name from the Odata EDM: BillingDocumentRequestItemText
Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations.The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
@Nullable public LocalDateTime getServicesRenderedDate()
Original property name from the Odata EDM: ServicesRenderedDate
If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
@Nullable public BigDecimal getBillingQuantity()
Original property name from the Odata EDM: BillingQuantity
For assets in which a base unit of measure is entered, you can enter a quantity when you post acquisitions and retirements. The system then updates the asset according to this quantity when you post, based on the debit/credit flag of the transaction posted.In addition, you can already specify a quantity when you create a new asset master record. However, any quantity you enter in master data maintenance (such as 1) is added to any quantity that is entered in the acquisition posting.
@Nullable public String getBillingQuantityUnit()
Original property name from the Odata EDM: BillingQuantityUnit
@Nullable public BigDecimal getNetAmount()
Original property name from the Odata EDM: NetAmount
@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 BigDecimal getGrossAmount()
Original property name from the Odata EDM: GrossAmount
@Nullable public LocalDateTime getPricingDate()
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
@Nullable public BigDecimal getAbsltPriceDetnExchangeRate()
Original property name from the Odata EDM: AbsltPriceDetnExchangeRate
@Nullable public Boolean getPriceDetnExchRateIsIndrctQtan()
Original property name from the Odata EDM: PriceDetnExchRateIsIndrctQtan
@Nullable public BigDecimal getTaxAmount()
Original property name from the Odata EDM: TaxAmount
@Nullable public String getDepartureCountry()
Original property name from the Odata EDM: DepartureCountry
You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key tohelp determine the relevant taxes during pricingdetermine important country-specific standards (the length of postal codes and bank account numbers, for example)
@Nullable public String getTaxJurisdiction()
Original property name from the Odata EDM: TaxJurisdiction
@Nullable public String getProductTaxClassification1()
Original property name from the Odata EDM: ProductTaxClassification1
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getBusinessArea()
Original property name from the Odata EDM: BusinessArea
@Nullable public String getProfitCenter()
Original property name from the Odata EDM: ProfitCenter
@Nullable public String getWBSElement()
Original property name from the Odata EDM: WBSElement
@Nullable public String getControllingArea()
Original property name from the Odata EDM: ControllingArea
The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
@Nullable public String getProfitabilitySegment()
Original property name from the Odata EDM: ProfitabilitySegment
Examples:Customer '123'/Product '4710' Profitability segment no. 1Customer '123'/Product '4712' Profitability segment no. 2Country 'USA'/Region 'NORTH' Profitability segment no. 3
@Nullable public String getOrderID()
Original property name from the Odata EDM: OrderID
@Nullable public String getCostCenter()
Original property name from the Odata EDM: CostCenter
@Nullable public String getMatlAccountAssignmentGroup()
Original property name from the Odata EDM: MatlAccountAssignmentGroup
Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
@Nullable public String getReferenceDocument()
Original property name from the Odata EDM: ReferenceDocument
@Nullable public String getReferenceDocumentItem()
Original property name from the Odata EDM: ReferenceDocumentItem
@Nullable public String getHigherLevelItem()
Original property name from the Odata EDM: HigherLevelItem
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.
@Nullable public String getBillgDocRequestItemInPartSgmt()
Original property name from the Odata EDM: BillgDocRequestItemInPartSgmt
@Nullable public ErpConfigContext getErpConfigContext()
public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
setErpConfigContext
in class VdmEntity<BillingDocumentRequestItem>
erpConfigContext
- public String toString()
toString
in class VdmObject<BillingDocumentRequestItem>
public boolean equals(Object o)
equals
in class VdmObject<BillingDocumentRequestItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<BillingDocumentRequestItem>
public int hashCode()
hashCode
in class VdmObject<BillingDocumentRequestItem>
Copyright © 2018 SAP SE. All rights reserved.