BillingDocumentRequest (SAP Cloud SDK - Parent POM 3.22.0 API)

java.lang.Object
- com.sap.cloud.sdk.datamodel.odata.helper.VdmObject<EntityT>
- - com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity<BillingDocumentRequest>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.billingdocumentrequest.BillingDocumentRequest

```
public class BillingDocumentRequest
extends VdmEntity<BillingDocumentRequest>
```
Billing Document Request (API)

Original entity name from the Odata EDM: A_BillingDocumentRequestType

Nested Class Summary

Nested Classes
Modifier and Type	Class and Description
`static class`	`BillingDocumentRequest.BillingDocumentRequestBuilder` Helper class to allow for fluent creation of BillingDocumentRequest instances.

Field Summary

Fields
Modifier and Type	Field and Description
`static BillingDocumentRequestSelectable`	`ALL_FIELDS` Selector for all available fields of BillingDocumentRequest.
`static BillingDocumentRequestField<LocalDateTime>`	`BILLING_DOCUMENT_DATE` Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
`static BillingDocumentRequestField<String>`	`BILLING_DOCUMENT_REQUEST` Use with available fluent helpers to apply the BillingDocumentRequest field to query operations.
`static BillingDocumentRequestField<String>`	`BILLING_DOCUMENT_REQUEST_TYPE` Use with available fluent helpers to apply the BillingDocumentRequestType field to query operations.
`static BillingDocumentRequestField<String>`	`BILLING_ISSUE_TYPE` Use with available fluent helpers to apply the BillingIssueType field to query operations.
`static BillingDocumentRequestField<String>`	`COMPANY_CODE` Use with available fluent helpers to apply the CompanyCode field to query operations.
`static BillingDocumentRequestField<String>`	`CONTRACT_ACCOUNT` Use with available fluent helpers to apply the ContractAccount field to query operations.
`static BillingDocumentRequestField<LocalDateTime>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static BillingDocumentRequestField<LocalTime>`	`CREATION_TIME` Use with available fluent helpers to apply the CreationTime field to query operations.
`static BillingDocumentRequestField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static BillingDocumentRequestField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static BillingDocumentRequestField<String>`	`DIVISION` Use with available fluent helpers to apply the Division field to query operations.
`static BillingDocumentRequestField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static BillingDocumentRequestField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static BillingDocumentRequestField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static BillingDocumentRequestField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static BillingDocumentRequestField<String>`	`INCOTERMS_VERSION` Use with available fluent helpers to apply the IncotermsVersion field to query operations.
`static BillingDocumentRequestField<LocalDateTime>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static BillingDocumentRequestField<ZonedDateTime>`	`LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
`static BillingDocumentRequestField<String>`	`LOGICAL_SYSTEM` Use with available fluent helpers to apply the LogicalSystem field to query operations.
`static BillingDocumentRequestField<String>`	`OVERALL_BILLING_DOC_REQ_STATUS` Use with available fluent helpers to apply the OverallBillingDocReqStatus field to query operations.
`static BillingDocumentRequestField<String>`	`OVERALL_PRICING_INCOMPLETION_STS` Use with available fluent helpers to apply the OverallPricingIncompletionSts field to query operations.
`static BillingDocumentRequestField<String>`	`PAYER_PARTY` Use with available fluent helpers to apply the PayerParty field to query operations.
`static BillingDocumentRequestField<String>`	`PAYMENT_METHOD` Use with available fluent helpers to apply the PaymentMethod field to query operations.
`static BillingDocumentRequestField<String>`	`PRICING_DOCUMENT` Use with available fluent helpers to apply the PricingDocument field to query operations.
`static BillingDocumentRequestField<String>`	`PROPOSED_BILLING_DOCUMENT_TYPE` Use with available fluent helpers to apply the ProposedBillingDocumentType field to query operations.
`static BillingDocumentRequestField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static BillingDocumentRequestField<String>`	`REFERENCE_DOC_SD_DOC_CATEGORY` Use with available fluent helpers to apply the ReferenceDocSDDocCategory field to query operations.
`static BillingDocumentRequestField<String>`	`REFERENCE_DOCUMENT` Use with available fluent helpers to apply the ReferenceDocument field to query operations.
`static BillingDocumentRequestField<String>`	`REFERENCE_DOCUMENT_LOGICAL_SYSTEM` Use with available fluent helpers to apply the ReferenceDocumentLogicalSystem field to query operations.
`static BillingDocumentRequestField<String>`	`SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrganization field to query operations.
`static BillingDocumentRequestField<String>`	`SEPA_MANDATE` Use with available fluent helpers to apply the SEPAMandate field to query operations.
`static BillingDocumentRequestField<String>`	`SOLD_TO_PARTY` Use with available fluent helpers to apply the SoldToParty field to query operations.
`static BillingDocumentRequestField<String>`	`TAX_DEPARTURE_COUNTRY` Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
`static BillingDocumentRequestLink<BillingDocumentRequestItem>`	`TO_ITEM` Use with available fluent helpers to apply the to_Item navigation property to query operations.
`static BillingDocumentRequestLink<BillingDocReqPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static BillingDocumentRequestLink<BillingDocReqPrcgElmnt>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static BillingDocumentRequestField<BigDecimal>`	`TOTAL_GROSS_AMOUNT` Use with available fluent helpers to apply the TotalGrossAmount field to query operations.
`static BillingDocumentRequestField<BigDecimal>`	`TOTAL_NET_AMOUNT` Use with available fluent helpers to apply the TotalNetAmount field to query operations.
`static BillingDocumentRequestField<BigDecimal>`	`TOTAL_TAX_AMOUNT` Use with available fluent helpers to apply the TotalTaxAmount field to query operations.
`static BillingDocumentRequestField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
changedOriginalFields

Constructor Summary

Constructors
Constructor and Description
`BillingDocumentRequest()`
BillingDocumentRequest(String billingDocumentRequest, String billingDocumentRequestType, String proposedBillingDocumentType, LocalDateTime creationDate, LocalTime creationTime, LocalDateTime lastChangeDate, ZonedDateTime lastChangeDateTime, String logicalSystem, String salesOrganization, String distributionChannel, String division, LocalDateTime billingDocumentDate, BigDecimal totalNetAmount, String transactionCurrency, BigDecimal totalTaxAmount, BigDecimal totalGrossAmount, String taxDepartureCountry, String payerParty, String contractAccount, String customerPaymentTerms, String paymentMethod, String sEPAMandate, String companyCode, String referenceDocument, String referenceDocumentLogicalSystem, String referenceDocSDDocCategory, String soldToParty, String purchaseOrderByCustomer, String pricingDocument, String billingIssueType, String incotermsVersion, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String overallBillingDocReqStatus, String overallPricingIncompletionSts, List<BillingDocumentRequestItem> toItem, List<BillingDocReqPartner> toPartner, List<BillingDocReqPrcgElmnt> toPricingElement)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addItem(BillingDocumentRequestItem... entity)` Adds elements to the list of associated BillingDocumentRequestItem entities.
`void`	`addPartner(BillingDocReqPartner... entity)` Adds elements to the list of associated BillingDocReqPartner entities.
`void`	`addPricingElement(BillingDocReqPrcgElmnt... entity)` Adds elements to the list of associated BillingDocReqPrcgElmnt entities.
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static BillingDocumentRequest.BillingDocumentRequestBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`List<BillingDocumentRequestItem>`	`fetchItem()` Fetches the BillingDocumentRequestItem entities (one to many) associated with this entity.
`List<BillingDocReqPartner>`	`fetchPartner()` Fetches the BillingDocReqPartner entities (one to many) associated with this entity.
`List<BillingDocReqPrcgElmnt>`	`fetchPricingElement()` Fetches the BillingDocReqPrcgElmnt entities (one to many) associated with this entity.
`static <T> BillingDocumentRequestField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> BillingDocumentRequestField<T>`	`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)`
`LocalDateTime`	`getBillingDocumentDate()` Constraints: Not nullable, Precision: 0
`String`	`getBillingDocumentRequest()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getBillingDocumentRequestType()` Constraints: Not nullable, Maximum length: 4
`String`	`getBillingIssueType()` Constraints: Not nullable, Maximum length: 1
`String`	`getCompanyCode()` Constraints: Not nullable, Maximum length: 4
`String`	`getContractAccount()` Constraints: Not nullable, Maximum length: 12
`LocalDateTime`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`LocalTime`	`getCreationTime()` Constraints: Not nullable, Precision: 0
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`protected String`	`getDefaultServicePath()` Used by fluent helpers and navigation property methods to construct OData queries.
`HttpDestinationProperties`	`getDestinationForFetch()` Convienence field for reusing the same destination with multiple queries (e.g.
`String`	`getDistributionChannel()` Constraints: Not nullable, Maximum length: 2
`String`	`getDivision()` Constraints: Not nullable, Maximum length: 2
`protected String`	`getEntityCollection()` Used by fluent helpers and navigation property methods to construct OData queries.
`String`	`getIncotermsClassification()` Constraints: Not nullable, Maximum length: 3
`String`	`getIncotermsLocation1()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsLocation2()` Constraints: Not nullable, Maximum length: 70
`String`	`getIncotermsTransferLocation()` Constraints: Not nullable, Maximum length: 28
`String`	`getIncotermsVersion()` Constraints: Not nullable, Maximum length: 4
`io.vavr.control.Option<List<BillingDocumentRequestItem>>`	`getItemIfPresent()` Retrieval of associated BillingDocumentRequestItem entities (one to many).
`List<BillingDocumentRequestItem>`	`getItemOrFetch()` Retrieval of associated BillingDocumentRequestItem entities (one to many).
`protected Map<String,Object>`	`getKey()`
`LocalDateTime`	`getLastChangeDate()` Constraints: Not nullable, Precision: 0
`ZonedDateTime`	`getLastChangeDateTime()` Constraints: Not nullable, Precision: 7
`String`	`getLogicalSystem()` Constraints: Not nullable, Maximum length: 10
`String`	`getOverallBillingDocReqStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallPricingIncompletionSts()` Constraints: Not nullable, Maximum length: 1
`io.vavr.control.Option<List<BillingDocReqPartner>>`	`getPartnerIfPresent()` Retrieval of associated BillingDocReqPartner entities (one to many).
`List<BillingDocReqPartner>`	`getPartnerOrFetch()` Retrieval of associated BillingDocReqPartner entities (one to many).
`String`	`getPayerParty()` Constraints: Not nullable, Maximum length: 10
`String`	`getPaymentMethod()` Constraints: Not nullable, Maximum length: 1
`String`	`getPricingDocument()` Constraints: Not nullable, Maximum length: 10
`io.vavr.control.Option<List<BillingDocReqPrcgElmnt>>`	`getPricingElementIfPresent()` Retrieval of associated BillingDocReqPrcgElmnt entities (one to many).
`List<BillingDocReqPrcgElmnt>`	`getPricingElementOrFetch()` Retrieval of associated BillingDocReqPrcgElmnt entities (one to many).
`String`	`getProposedBillingDocumentType()` Constraints: Not nullable, Maximum length: 4
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35
`String`	`getReferenceDocSDDocCategory()` Constraints: Not nullable, Maximum length: 4
`String`	`getReferenceDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getReferenceDocumentLogicalSystem()` Constraints: Not nullable, Maximum length: 10
`String`	`getSalesOrganization()` Constraints: Not nullable, Maximum length: 4
`String`	`getSEPAMandate()` Constraints: Not nullable, Maximum length: 35
`String`	`getSoldToParty()` Constraints: Not nullable, Maximum length: 10
`String`	`getTaxDepartureCountry()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getTotalGrossAmount()` Constraints: Not nullable, Precision: 17, Scale: 3
`BigDecimal`	`getTotalNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`BigDecimal`	`getTotalTaxAmount()` Constraints: Not nullable, Precision: 14, Scale: 3
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5
`Class<BillingDocumentRequest>`	`getType()`
`int`	`hashCode()`
`void`	`setBillingDocumentDate(LocalDateTime billingDocumentDate)` Constraints: Not nullable, Precision: 0
`void`	`setBillingDocumentRequest(String billingDocumentRequest)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setBillingDocumentRequestType(String billingDocumentRequestType)` Constraints: Not nullable, Maximum length: 4
`void`	`setBillingIssueType(String billingIssueType)` Constraints: Not nullable, Maximum length: 1
`void`	`setCompanyCode(String companyCode)` Constraints: Not nullable, Maximum length: 4
`void`	`setContractAccount(String contractAccount)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setCreationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`void`	`setDistributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2
`void`	`setDivision(String division)` Constraints: Not nullable, Maximum length: 2
`void`	`setIncotermsClassification(String incotermsClassification)` Constraints: Not nullable, Maximum length: 3
`void`	`setIncotermsLocation1(String incotermsLocation1)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsLocation2(String incotermsLocation2)` Constraints: Not nullable, Maximum length: 70
`void`	`setIncotermsTransferLocation(String incotermsTransferLocation)` Constraints: Not nullable, Maximum length: 28
`void`	`setIncotermsVersion(String incotermsVersion)` Constraints: Not nullable, Maximum length: 4
`void`	`setItem(List<BillingDocumentRequestItem> value)` Overwrites the list of associated BillingDocumentRequestItem entities for the loaded navigation property to_Item.
`void`	`setLastChangeDate(LocalDateTime lastChangeDate)` Constraints: Not nullable, Precision: 0
`void`	`setLastChangeDateTime(ZonedDateTime lastChangeDateTime)` Constraints: Not nullable, Precision: 7
`void`	`setLogicalSystem(String logicalSystem)` Constraints: Not nullable, Maximum length: 10
`void`	`setOverallBillingDocReqStatus(String overallBillingDocReqStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallPricingIncompletionSts(String overallPricingIncompletionSts)` Constraints: Not nullable, Maximum length: 1
`void`	`setPartner(List<BillingDocReqPartner> value)` Overwrites the list of associated BillingDocReqPartner entities for the loaded navigation property to_Partner.
`void`	`setPayerParty(String payerParty)` Constraints: Not nullable, Maximum length: 10
`void`	`setPaymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`void`	`setPricingDocument(String pricingDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setPricingElement(List<BillingDocReqPrcgElmnt> value)` Overwrites the list of associated BillingDocReqPrcgElmnt entities for the loaded navigation property to_PricingElement.
`void`	`setProposedBillingDocumentType(String proposedBillingDocumentType)` Constraints: Not nullable, Maximum length: 4
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`void`	`setReferenceDocSDDocCategory(String referenceDocSDDocCategory)` Constraints: Not nullable, Maximum length: 4
`void`	`setReferenceDocument(String referenceDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setReferenceDocumentLogicalSystem(String referenceDocumentLogicalSystem)` Constraints: Not nullable, Maximum length: 10
`void`	`setSalesOrganization(String salesOrganization)` Constraints: Not nullable, Maximum length: 4
`void`	`setSEPAMandate(String sEPAMandate)` Constraints: Not nullable, Maximum length: 35
`protected void`	`setServicePathForFetch(String servicePathForFetch)` The service path only used for the fetch commands of this entity.
`void`	`setSoldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`void`	`setTaxDepartureCountry(String taxDepartureCountry)` Constraints: Not nullable, Maximum length: 3
`void`	`setTotalGrossAmount(BigDecimal totalGrossAmount)` Constraints: Not nullable, Precision: 17, Scale: 3
`void`	`setTotalNetAmount(BigDecimal totalNetAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setTotalTaxAmount(BigDecimal totalTaxAmount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`protected Map<String,Object>`	`toMapOfFields()`
`protected Map<String,Object>`	`toMapOfNavigationProperties()`
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields

Methods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, wait

- Field Detail
  - ALL_FIELDS
```
public static final BillingDocumentRequestSelectable ALL_FIELDS
```
    Selector for all available fields of BillingDocumentRequest.
  - BILLING_DOCUMENT_REQUEST
```
public static final BillingDocumentRequestField<String> BILLING_DOCUMENT_REQUEST
```
    Use with available fluent helpers to apply the BillingDocumentRequest field to query operations.
  - BILLING_DOCUMENT_REQUEST_TYPE
```
public static final BillingDocumentRequestField<String> BILLING_DOCUMENT_REQUEST_TYPE
```
    Use with available fluent helpers to apply the BillingDocumentRequestType field to query operations.
  - PROPOSED_BILLING_DOCUMENT_TYPE
```
public static final BillingDocumentRequestField<String> PROPOSED_BILLING_DOCUMENT_TYPE
```
    Use with available fluent helpers to apply the ProposedBillingDocumentType field to query operations.
  - CREATION_DATE
```
public static final BillingDocumentRequestField<LocalDateTime> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATION_TIME
```
public static final BillingDocumentRequestField<LocalTime> CREATION_TIME
```
    Use with available fluent helpers to apply the CreationTime field to query operations.
  - LAST_CHANGE_DATE
```
public static final BillingDocumentRequestField<LocalDateTime> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - LAST_CHANGE_DATE_TIME
```
public static final BillingDocumentRequestField<ZonedDateTime> LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
  - LOGICAL_SYSTEM
```
public static final BillingDocumentRequestField<String> LOGICAL_SYSTEM
```
    Use with available fluent helpers to apply the LogicalSystem field to query operations.
  - SALES_ORGANIZATION
```
public static final BillingDocumentRequestField<String> SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrganization field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final BillingDocumentRequestField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - DIVISION
```
public static final BillingDocumentRequestField<String> DIVISION
```
    Use with available fluent helpers to apply the Division field to query operations.
  - BILLING_DOCUMENT_DATE
```
public static final BillingDocumentRequestField<LocalDateTime> BILLING_DOCUMENT_DATE
```
    Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
  - TOTAL_NET_AMOUNT
```
public static final BillingDocumentRequestField<BigDecimal> TOTAL_NET_AMOUNT
```
    Use with available fluent helpers to apply the TotalNetAmount field to query operations.
  - TRANSACTION_CURRENCY
```
public static final BillingDocumentRequestField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - TOTAL_TAX_AMOUNT
```
public static final BillingDocumentRequestField<BigDecimal> TOTAL_TAX_AMOUNT
```
    Use with available fluent helpers to apply the TotalTaxAmount field to query operations.
  - TOTAL_GROSS_AMOUNT
```
public static final BillingDocumentRequestField<BigDecimal> TOTAL_GROSS_AMOUNT
```
    Use with available fluent helpers to apply the TotalGrossAmount field to query operations.
  - TAX_DEPARTURE_COUNTRY
```
public static final BillingDocumentRequestField<String> TAX_DEPARTURE_COUNTRY
```
    Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
  - PAYER_PARTY
```
public static final BillingDocumentRequestField<String> PAYER_PARTY
```
    Use with available fluent helpers to apply the PayerParty field to query operations.
  - CONTRACT_ACCOUNT
```
public static final BillingDocumentRequestField<String> CONTRACT_ACCOUNT
```
    Use with available fluent helpers to apply the ContractAccount field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final BillingDocumentRequestField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - PAYMENT_METHOD
```
public static final BillingDocumentRequestField<String> PAYMENT_METHOD
```
    Use with available fluent helpers to apply the PaymentMethod field to query operations.
  - SEPA_MANDATE
```
public static final BillingDocumentRequestField<String> SEPA_MANDATE
```
    Use with available fluent helpers to apply the SEPAMandate field to query operations.
  - COMPANY_CODE
```
public static final BillingDocumentRequestField<String> COMPANY_CODE
```
    Use with available fluent helpers to apply the CompanyCode field to query operations.
  - REFERENCE_DOCUMENT
```
public static final BillingDocumentRequestField<String> REFERENCE_DOCUMENT
```
    Use with available fluent helpers to apply the ReferenceDocument field to query operations.
  - REFERENCE_DOCUMENT_LOGICAL_SYSTEM
```
public static final BillingDocumentRequestField<String> REFERENCE_DOCUMENT_LOGICAL_SYSTEM
```
    Use with available fluent helpers to apply the ReferenceDocumentLogicalSystem field to query operations.
  - REFERENCE_DOC_SD_DOC_CATEGORY
```
public static final BillingDocumentRequestField<String> REFERENCE_DOC_SD_DOC_CATEGORY
```
    Use with available fluent helpers to apply the ReferenceDocSDDocCategory field to query operations.
  - SOLD_TO_PARTY
```
public static final BillingDocumentRequestField<String> SOLD_TO_PARTY
```
    Use with available fluent helpers to apply the SoldToParty field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final BillingDocumentRequestField<String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - PRICING_DOCUMENT
```
public static final BillingDocumentRequestField<String> PRICING_DOCUMENT
```
    Use with available fluent helpers to apply the PricingDocument field to query operations.
  - BILLING_ISSUE_TYPE
```
public static final BillingDocumentRequestField<String> BILLING_ISSUE_TYPE
```
    Use with available fluent helpers to apply the BillingIssueType field to query operations.
  - INCOTERMS_VERSION
```
public static final BillingDocumentRequestField<String> INCOTERMS_VERSION
```
    Use with available fluent helpers to apply the IncotermsVersion field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final BillingDocumentRequestField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final BillingDocumentRequestField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final BillingDocumentRequestField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final BillingDocumentRequestField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - OVERALL_BILLING_DOC_REQ_STATUS
```
public static final BillingDocumentRequestField<String> OVERALL_BILLING_DOC_REQ_STATUS
```
    Use with available fluent helpers to apply the OverallBillingDocReqStatus field to query operations.
  - OVERALL_PRICING_INCOMPLETION_STS
```
public static final BillingDocumentRequestField<String> OVERALL_PRICING_INCOMPLETION_STS
```
    Use with available fluent helpers to apply the OverallPricingIncompletionSts field to query operations.
  - TO_ITEM
```
public static final BillingDocumentRequestLink<BillingDocumentRequestItem> TO_ITEM
```
    Use with available fluent helpers to apply the to_Item navigation property to query operations.
  - TO_PARTNER
```
public static final BillingDocumentRequestLink<BillingDocReqPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final BillingDocumentRequestLink<BillingDocReqPrcgElmnt> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
- Constructor Detail
  - BillingDocumentRequest
```
public BillingDocumentRequest()
```
  - BillingDocumentRequest
```
public BillingDocumentRequest(@Nullable
                              String billingDocumentRequest,
                              @Nullable
                              String billingDocumentRequestType,
                              @Nullable
                              String proposedBillingDocumentType,
                              @Nullable
                              LocalDateTime creationDate,
                              @Nullable
                              LocalTime creationTime,
                              @Nullable
                              LocalDateTime lastChangeDate,
                              @Nullable
                              ZonedDateTime lastChangeDateTime,
                              @Nullable
                              String logicalSystem,
                              @Nullable
                              String salesOrganization,
                              @Nullable
                              String distributionChannel,
                              @Nullable
                              String division,
                              @Nullable
                              LocalDateTime billingDocumentDate,
                              @Nullable
                              BigDecimal totalNetAmount,
                              @Nullable
                              String transactionCurrency,
                              @Nullable
                              BigDecimal totalTaxAmount,
                              @Nullable
                              BigDecimal totalGrossAmount,
                              @Nullable
                              String taxDepartureCountry,
                              @Nullable
                              String payerParty,
                              @Nullable
                              String contractAccount,
                              @Nullable
                              String customerPaymentTerms,
                              @Nullable
                              String paymentMethod,
                              @Nullable
                              String sEPAMandate,
                              @Nullable
                              String companyCode,
                              @Nullable
                              String referenceDocument,
                              @Nullable
                              String referenceDocumentLogicalSystem,
                              @Nullable
                              String referenceDocSDDocCategory,
                              @Nullable
                              String soldToParty,
                              @Nullable
                              String purchaseOrderByCustomer,
                              @Nullable
                              String pricingDocument,
                              @Nullable
                              String billingIssueType,
                              @Nullable
                              String incotermsVersion,
                              @Nullable
                              String incotermsClassification,
                              @Nullable
                              String incotermsTransferLocation,
                              @Nullable
                              String incotermsLocation1,
                              @Nullable
                              String incotermsLocation2,
                              @Nullable
                              String overallBillingDocReqStatus,
                              @Nullable
                              String overallPricingIncompletionSts,
                              List<BillingDocumentRequestItem> toItem,
                              List<BillingDocReqPartner> toPartner,
                              List<BillingDocReqPrcgElmnt> toPricingElement)
```
- Method Detail
  - getType
```
@Nonnull
public Class<BillingDocumentRequest> getType()
```
    Specified by:
    
    getType in class VdmObject<BillingDocumentRequest>
    
    Returns:
    
    The class of this object.
  - setBillingDocumentRequest
```
public void setBillingDocumentRequest(@Nullable
                                      String billingDocumentRequest)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: BillingDocumentRequest
    
    Parameters:
    
    billingDocumentRequest - Billing Document Request
  - setBillingDocumentRequestType
```
public void setBillingDocumentRequestType(@Nullable
                                          String billingDocumentRequestType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillingDocumentRequestType
    
    When you process billing documents collectively, you can use the billing type as one of the selection criteria.
    
    Parameters:
    
    billingDocumentRequestType - Classifies types of billing document that require different processing by the system.
  - setProposedBillingDocumentType
```
public void setProposedBillingDocumentType(@Nullable
                                           String proposedBillingDocumentType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProposedBillingDocumentType
    
    When you process billing documents collectively, you can use the billing type as one of the selection criteria.
    
    Parameters:
    
    proposedBillingDocumentType - Classifies types of billing document that require different processing by the system.
  - setCreationDate
```
public void setCreationDate(@Nullable
                            LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Parameters:
    
    creationDate - Date on Which Record Was Created
  - setCreationTime
```
public void setCreationTime(@Nullable
                            LocalTime creationTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Parameters:
    
    creationTime - The time of day at which the document was posted and stored in the system.
  - setLastChangeDate
```
public void setLastChangeDate(@Nullable
                              LocalDateTime lastChangeDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Parameters:
    
    lastChangeDate - Date of Last Change
  - setLastChangeDateTime
```
public void setLastChangeDateTime(@Nullable
                                  ZonedDateTime lastChangeDateTime)
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Parameters:
    
    lastChangeDateTime - The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - setLogicalSystem
```
public void setLogicalSystem(@Nullable
                             String logicalSystem)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: LogicalSystem
    
    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.
    
    Parameters:
    
    logicalSystem - System in which applications run integrated on a shared data basis.
  - setSalesOrganization
```
public void setSalesOrganization(@Nullable
                                 String salesOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Parameters:
    
    salesOrganization - An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.
  - setDistributionChannel
```
public void setDistributionChannel(@Nullable
                                   String distributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    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.
    
    Parameters:
    
    distributionChannel - The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.
  - setDivision
```
public void setDivision(@Nullable
                        String division)
```
    Constraints: Not nullable, Maximum length: 2
    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.
    
    Parameters:
    
    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.
  - setBillingDocumentDate
```
public void setBillingDocumentDate(@Nullable
                                   LocalDateTime billingDocumentDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BillingDocumentDate
    
    You can use the billing date as one of the selection criteria when you process billing documents collectively.If invoice dates are defined for the customer, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date.If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document.If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone.In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
    
    Parameters:
    
    billingDocumentDate - The date on which the billing is processed and booked for accounting purposes.
  - setTotalNetAmount
```
public void setTotalNetAmount(@Nullable
                              BigDecimal totalNetAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    
    Parameters:
    
    totalNetAmount - Net value of the document item.
  - setTransactionCurrency
```
public void setTransactionCurrency(@Nullable
                                   String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    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.
    
    Parameters:
    
    transactionCurrency - The currency that applies to the document (for example, to a sales order or an invoice).
  - setTotalTaxAmount
```
public void setTotalTaxAmount(@Nullable
                              BigDecimal totalTaxAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: TotalTaxAmount
    
    Parameters:
    
    totalTaxAmount - The total sales taxes, expressed in the document currency.
  - setTotalGrossAmount
```
public void setTotalGrossAmount(@Nullable
                                BigDecimal totalGrossAmount)
```
    Constraints: Not nullable, Precision: 17, Scale: 3
    Original property name from the Odata EDM: TotalGrossAmount
    
    Parameters:
    
    totalGrossAmount - The totalGrossAmount to set.
  - setTaxDepartureCountry
```
public void setTaxDepartureCountry(@Nullable
                                   String taxDepartureCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: TaxDepartureCountry
    
    A different country needs to be entered for certain internal European transactions (chain transactions).
    
    Parameters:
    
    taxDepartureCountry - For tax determination, the country of departure is used as the plant country.
  - setPayerParty
```
public void setPayerParty(@Nullable
                          String payerParty)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PayerParty
    
    The payer may differ from the bill-to party who receives the bill.
    
    Parameters:
    
    payerParty - The party who is responsible for actually paying the bill.
  - setContractAccount
```
public void setContractAccount(@Nullable
                               String contractAccount)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ContractAccount
    
    The postings in Contract Accounts Receivable and Payable are always assigned to a contract account and a business partner.In the contract account master record, specifically for each business partner, you can define procedures that are to be used for further processing of line items. These include for example, payment methods, dunning procedure, tolerances.NoteFor utility and insurance companies, a contract is assigned to exactly one contract account. However several accounts - depending on contract account type can be assigned to one contract account.
    
    Parameters:
    
    contractAccount - Key that uniquely identifies a contract account per client.
  - setCustomerPaymentTerms
```
public void setCustomerPaymentTerms(@Nullable
                                    String customerPaymentTerms)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Parameters:
    
    customerPaymentTerms - Key for defining payment terms composed of cash discount percentages and payment periods.
  - setPaymentMethod
```
public void setPaymentMethod(@Nullable
                             String paymentMethod)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
    
    Parameters:
    
    paymentMethod - Payment method with which this item is to be paid.
  - setSEPAMandate
```
public void setSEPAMandate(@Nullable
                           String sEPAMandate)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: SEPAMandate
    
    The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment.Whether internal or external number assignment (or both) is possible depends on the application concerned.Once you have created the mandate, you can no longer change its mandate reference.At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field.Notes on Assigning Contract Accounts and Contracts to MandatesYou can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment.Notes on Using Alternative PayersIf you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen.ExampleYou enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1.Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects.Example - Assignment of a mandate to multiple contract accountsContract account Mandate (in Contract Acct) MeaningC1 M1 Mandate M1 is valid for C1.C2 M1 Mandate M1 is also valid for C2.C3 M2 Mandate M2 is valid for C3.C4 M2 Mandate M2 is also valid for C4.Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account.Example - Assignment of one contract account per mandateMandate Contract Account (in Mandate) MeaningM1 C1 Mandate M1 is only valid for items of contract account C1.M2 C2 Mandate M2 is only valid for items of contract account C2.If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects.The examples above apply in a similar manner to the assignment of contracts.Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate.If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details.If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment.If you do not make any specification, the system uses the first mandate that qualifies for the payment.
    
    Parameters:
    
    sEPAMandate - Identifies, together with the Creditor Identifier, the mandate uniquely.
  - setCompanyCode
```
public void setCompanyCode(@Nullable
                           String companyCode)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CompanyCode
    
    Parameters:
    
    companyCode - The company code is an organizational unit within financial accounting.
  - setReferenceDocument
```
public void setReferenceDocument(@Nullable
                                 String referenceDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceDocument
    
    Parameters:
    
    referenceDocument - Source document on which a billing document request is based
  - setReferenceDocumentLogicalSystem
```
public void setReferenceDocumentLogicalSystem(@Nullable
                                              String referenceDocumentLogicalSystem)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
    
    Parameters:
    
    referenceDocumentLogicalSystem - Logical system containing source document of BDR
  - setReferenceDocSDDocCategory
```
public void setReferenceDocSDDocCategory(@Nullable
                                         String referenceDocSDDocCategory)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ReferenceDocSDDocCategory
    
    Parameters:
    
    referenceDocSDDocCategory - SD document category of BDR source document
  - setSoldToParty
```
public void setSoldToParty(@Nullable
                           String soldToParty)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
    
    Parameters:
    
    soldToParty - The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.
  - setPurchaseOrderByCustomer
```
public void setPurchaseOrderByCustomer(@Nullable
                                       String purchaseOrderByCustomer)
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Parameters:
    
    purchaseOrderByCustomer - Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - setPricingDocument
```
public void setPricingDocument(@Nullable
                               String pricingDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PricingDocument
    
    The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area. The system uses the internal number to identify the different conditions.
    
    Parameters:
    
    pricingDocument - The internal number under which the system saves conditions that apply to a sales order, for example.
  - setBillingIssueType
```
public void setBillingIssueType(@Nullable
                                String billingIssueType)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillingIssueType
    
    Parameters:
    
    billingIssueType - SD Billing Document Issue
  - setIncotermsVersion
```
public void setIncotermsVersion(@Nullable
                                String incotermsVersion)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: IncotermsVersion
    
    Parameters:
    
    incotermsVersion - An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).
  - setIncotermsClassification
```
public void setIncotermsClassification(@Nullable
                                       String incotermsClassification)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Parameters:
    
    incotermsClassification - Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - setIncotermsTransferLocation
```
public void setIncotermsTransferLocation(@Nullable
                                         String incotermsTransferLocation)
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Parameters:
    
    incotermsTransferLocation - Additional information for the primary Incoterm.
  - setIncotermsLocation1
```
public void setIncotermsLocation1(@Nullable
                                  String incotermsLocation1)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Parameters:
    
    incotermsLocation1 - Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - setIncotermsLocation2
```
public void setIncotermsLocation2(@Nullable
                                  String incotermsLocation2)
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Parameters:
    
    incotermsLocation2 - Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:
  - setOverallBillingDocReqStatus
```
public void setOverallBillingDocReqStatus(@Nullable
                                          String overallBillingDocReqStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallBillingDocReqStatus
    
    Parameters:
    
    overallBillingDocReqStatus - Billing Document Request Status
  - setOverallPricingIncompletionSts
```
public void setOverallPricingIncompletionSts(@Nullable
                                             String overallPricingIncompletionSts)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallPricingIncompletionSts
    
    Parameters:
    
    overallPricingIncompletionSts - Pricing Incompletion Status (All Items)
  - getEntityCollection
```
protected String getEntityCollection()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Specified by:
    
    getEntityCollection in class VdmEntity<BillingDocumentRequest>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<BillingDocumentRequest>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<BillingDocumentRequest>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<BillingDocumentRequest>
  - field
```
@Nonnull
public static <T> BillingDocumentRequestField<T> field(@Nonnull
                                                                String fieldName,
                                                                @Nonnull
                                                                Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    Parameters:
    
    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.
    
    Returns:
    
    A representation of an extension field from this entity.
  - field
```
@Nonnull
public static <T,DomainT> BillingDocumentRequestField<T> field(@Nonnull
                                                                        String fieldName,
                                                                        @Nonnull
                                                                        TypeConverter<T,DomainT> typeConverter)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    Type Parameters:
    
    T - The type of the extension field when performing value comparisons.
    
    DomainT - The type of the extension field as returned by the OData service.
    
    Parameters:
    
    typeConverter - A TypeConverter instance whose first generic type matches the Java type of the field
    
    fieldName - The name of the extension field as returned by the OData service.
    
    Returns:
    
    A representation of an extension field from this entity, holding a reference to the given TypeConverter.
  - getDestinationForFetch
```
@Nullable
public HttpDestinationProperties getDestinationForFetch()
```
    Description copied from class: VdmEntity
    
    Convienence field for reusing the same destination with multiple queries (e.g. fetching associated entities). New destination to apply to this entity
    
    Overrides:
    
    getDestinationForFetch in class VdmEntity<BillingDocumentRequest>
    
    Returns:
    
    The stored destination for executing queries, or null if no such context has been set.
  - setServicePathForFetch
```
protected void setServicePathForFetch(@Nullable
                                      String servicePathForFetch)
```
    Description copied from class: VdmEntity
    
    The service path only used for the fetch commands of this entity.
    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.
    
    Overrides:
    
    setServicePathForFetch in class VdmEntity<BillingDocumentRequest>
  - attachToService
```
public void attachToService(@Nullable
                            String servicePath,
                            @Nonnull
                            HttpDestinationProperties destination)
```
    Description copied from class: VdmEntity
    
    Sets the service path and destination for the fetch commands of this entity. Also applies to any associated entities (navigation properties) that were previously fetched.
    Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
    
    Overrides:
    
    attachToService in class VdmEntity<BillingDocumentRequest>
    
    Parameters:
    
    servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were previously fetched. If a null value is provided and the service path has never been set, then the service path will be set to the default defined in the corresponding service interface.
    
    destination - New destination to apply to this entity and any associated entities that were previously fetched.
  - getDefaultServicePath
```
protected String getDefaultServicePath()
```
    Description copied from class: VdmEntity
    
    Used by fluent helpers and navigation property methods to construct OData queries.
    
    Overrides:
    
    getDefaultServicePath in class VdmEntity<BillingDocumentRequest>
    
    Returns:
    
    Default context path to the OData service. In other words, everything in between the protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)
  - toMapOfNavigationProperties
```
@Nonnull
protected Map<String,Object> toMapOfNavigationProperties()
```
    Overrides:
    
    toMapOfNavigationProperties in class VdmObject<BillingDocumentRequest>
  - fetchItem
```
@Nonnull
public List<BillingDocumentRequestItem> fetchItem()
                                                    throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocumentRequestItem entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Item.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated BillingDocumentRequestItem entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    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.
  - getItemOrFetch
```
@Nonnull
public List<BillingDocumentRequestItem> getItemOrFetch()
                                                         throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocumentRequestItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried BillingDocumentRequest 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.
    
    Returns:
    
    List of associated BillingDocumentRequestItem entities.
    
    Throws:
    
    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.
  - getItemIfPresent
```
@Nonnull
public io.vavr.control.Option<List<BillingDocumentRequestItem>> getItemIfPresent()
```
    Retrieval of associated BillingDocumentRequestItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property for an entity BillingDocumentRequest has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Item is already loaded, the result will contain the BillingDocumentRequestItem entities. If not, an Option with result state empty is returned.
  - setItem
```
public void setItem(@Nonnull
                    List<BillingDocumentRequestItem> value)
```
    Overwrites the list of associated BillingDocumentRequestItem entities for the loaded navigation property to_Item.
    If the navigation property to_Item of a queried BillingDocumentRequest 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.
    
    Parameters:
    
    value - List of BillingDocumentRequestItem entities.
  - addItem
```
public void addItem(BillingDocumentRequestItem... entity)
```
    Adds elements to the list of associated BillingDocumentRequestItem entities. This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried BillingDocumentRequest 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.
    
    Parameters:
    
    entity - Array of BillingDocumentRequestItem entities.
  - fetchPartner
```
@Nonnull
public List<BillingDocReqPartner> fetchPartner()
                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocReqPartner entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Partner.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated BillingDocReqPartner entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    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.
  - getPartnerOrFetch
```
@Nonnull
public List<BillingDocReqPartner> getPartnerOrFetch()
                                                      throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocReqPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried BillingDocumentRequest 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.
    
    Returns:
    
    List of associated BillingDocReqPartner entities.
    
    Throws:
    
    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.
  - getPartnerIfPresent
```
@Nonnull
public io.vavr.control.Option<List<BillingDocReqPartner>> getPartnerIfPresent()
```
    Retrieval of associated BillingDocReqPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property for an entity BillingDocumentRequest has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_Partner is already loaded, the result will contain the BillingDocReqPartner entities. If not, an Option with result state empty is returned.
  - setPartner
```
public void setPartner(@Nonnull
                       List<BillingDocReqPartner> value)
```
    Overwrites the list of associated BillingDocReqPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried BillingDocumentRequest 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.
    
    Parameters:
    
    value - List of BillingDocReqPartner entities.
  - addPartner
```
public void addPartner(BillingDocReqPartner... entity)
```
    Adds elements to the list of associated BillingDocReqPartner entities. This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried BillingDocumentRequest 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.
    
    Parameters:
    
    entity - Array of BillingDocReqPartner entities.
  - fetchPricingElement
```
@Nonnull
public List<BillingDocReqPrcgElmnt> fetchPricingElement()
                                                          throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocReqPrcgElmnt entities (one to many) associated with this entity. This corresponds to the OData navigation property to_PricingElement.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated BillingDocReqPrcgElmnt entities. If no entities are associated then an empty list is returned.
    
    Throws:
    
    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.
  - getPricingElementOrFetch
```
@Nonnull
public List<BillingDocReqPrcgElmnt> getPricingElementOrFetch()
                                                               throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocReqPrcgElmnt entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried BillingDocumentRequest 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.
    
    Returns:
    
    List of associated BillingDocReqPrcgElmnt entities.
    
    Throws:
    
    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.
  - getPricingElementIfPresent
```
@Nonnull
public io.vavr.control.Option<List<BillingDocReqPrcgElmnt>> getPricingElementIfPresent()
```
    Retrieval of associated BillingDocReqPrcgElmnt entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property for an entity BillingDocumentRequest has not been resolved yet, this method will not query further information. Instead its Option result state will be empty.
    
    Returns:
    
    If the information for navigation property to_PricingElement is already loaded, the result will contain the BillingDocReqPrcgElmnt entities. If not, an Option with result state empty is returned.
  - setPricingElement
```
public void setPricingElement(@Nonnull
                              List<BillingDocReqPrcgElmnt> value)
```
    Overwrites the list of associated BillingDocReqPrcgElmnt entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried BillingDocumentRequest 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.
    
    Parameters:
    
    value - List of BillingDocReqPrcgElmnt entities.
  - addPricingElement
```
public void addPricingElement(BillingDocReqPrcgElmnt... entity)
```
    Adds elements to the list of associated BillingDocReqPrcgElmnt entities. This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried BillingDocumentRequest 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.
    
    Parameters:
    
    entity - Array of BillingDocReqPrcgElmnt entities.
  - builder
```
public static BillingDocumentRequest.BillingDocumentRequestBuilder builder()
```
  - getBillingDocumentRequest
```
@Nullable
public String getBillingDocumentRequest()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: BillingDocumentRequest
    
    Returns:
    
    Billing Document Request
  - getBillingDocumentRequestType
```
@Nullable
public String getBillingDocumentRequestType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillingDocumentRequestType
    
    When you process billing documents collectively, you can use the billing type as one of the selection criteria.
    
    Returns:
    
    Classifies types of billing document that require different processing by the system.
  - getProposedBillingDocumentType
```
@Nullable
public String getProposedBillingDocumentType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ProposedBillingDocumentType
    
    When you process billing documents collectively, you can use the billing type as one of the selection criteria.
    
    Returns:
    
    Classifies types of billing document that require different processing by the system.
  - getCreationDate
```
@Nullable
public LocalDateTime getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
    
    Returns:
    
    Date on Which Record Was Created
  - getCreationTime
```
@Nullable
public LocalTime getCreationTime()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
    
    Returns:
    
    The time of day at which the document was posted and stored in the system.
  - getLastChangeDate
```
@Nullable
public LocalDateTime getLastChangeDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: LastChangeDate
    
    Returns:
    
    Date of Last Change
  - getLastChangeDateTime
```
@Nullable
public ZonedDateTime getLastChangeDateTime()
```
    Constraints: Not nullable, Precision: 7
    Original property name from the Odata EDM: LastChangeDateTime
    
    In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
    
    Returns:
    
    The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).
  - getLogicalSystem
```
@Nullable
public String getLogicalSystem()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: LogicalSystem
    
    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.
    
    Returns:
    
    System in which applications run integrated on a shared data basis.
  - getSalesOrganization
```
@Nullable
public String getSalesOrganization()
```
    Constraints: Not nullable, Maximum length: 4
    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.
    
    Returns:
    
    An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims.
  - getDistributionChannel
```
@Nullable
public String getDistributionChannel()
```
    Constraints: Not nullable, Maximum length: 2
    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.
    
    Returns:
    
    The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales.
  - getDivision
```
@Nullable
public String getDivision()
```
    Constraints: Not nullable, Maximum length: 2
    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.
    
    Returns:
    
    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.
  - getBillingDocumentDate
```
@Nullable
public LocalDateTime getBillingDocumentDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BillingDocumentDate
    
    You can use the billing date as one of the selection criteria when you process billing documents collectively.If invoice dates are defined for the customer, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date.If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document.If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone.In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
    
    Returns:
    
    The date on which the billing is processed and booked for accounting purposes.
  - getTotalNetAmount
```
@Nullable
public BigDecimal getTotalNetAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: TotalNetAmount
    
    Returns:
    
    Net value of the document item.
  - getTransactionCurrency
```
@Nullable
public String getTransactionCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    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.
    
    Returns:
    
    The currency that applies to the document (for example, to a sales order or an invoice).
  - getTotalTaxAmount
```
@Nullable
public BigDecimal getTotalTaxAmount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: TotalTaxAmount
    
    Returns:
    
    The total sales taxes, expressed in the document currency.
  - getTotalGrossAmount
```
@Nullable
public BigDecimal getTotalGrossAmount()
```
    Constraints: Not nullable, Precision: 17, Scale: 3
    Original property name from the Odata EDM: TotalGrossAmount
    
    Returns:
    
    The totalGrossAmount contained in this entity.
  - getTaxDepartureCountry
```
@Nullable
public String getTaxDepartureCountry()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: TaxDepartureCountry
    
    A different country needs to be entered for certain internal European transactions (chain transactions).
    
    Returns:
    
    For tax determination, the country of departure is used as the plant country.
  - getPayerParty
```
@Nullable
public String getPayerParty()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PayerParty
    
    The payer may differ from the bill-to party who receives the bill.
    
    Returns:
    
    The party who is responsible for actually paying the bill.
  - getContractAccount
```
@Nullable
public String getContractAccount()
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: ContractAccount
    
    The postings in Contract Accounts Receivable and Payable are always assigned to a contract account and a business partner.In the contract account master record, specifically for each business partner, you can define procedures that are to be used for further processing of line items. These include for example, payment methods, dunning procedure, tolerances.NoteFor utility and insurance companies, a contract is assigned to exactly one contract account. However several accounts - depending on contract account type can be assigned to one contract account.
    
    Returns:
    
    Key that uniquely identifies a contract account per client.
  - getCustomerPaymentTerms
```
@Nullable
public String getCustomerPaymentTerms()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CustomerPaymentTerms
    
    It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
    
    Returns:
    
    Key for defining payment terms composed of cash discount percentages and payment periods.
  - getPaymentMethod
```
@Nullable
public String getPaymentMethod()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: PaymentMethod
    
    If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
    
    Returns:
    
    Payment method with which this item is to be paid.
  - getSEPAMandate
```
@Nullable
public String getSEPAMandate()
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: SEPAMandate
    
    The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment.Whether internal or external number assignment (or both) is possible depends on the application concerned.Once you have created the mandate, you can no longer change its mandate reference.At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field.Notes on Assigning Contract Accounts and Contracts to MandatesYou can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment.Notes on Using Alternative PayersIf you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen.ExampleYou enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1.Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects.Example - Assignment of a mandate to multiple contract accountsContract account Mandate (in Contract Acct) MeaningC1 M1 Mandate M1 is valid for C1.C2 M1 Mandate M1 is also valid for C2.C3 M2 Mandate M2 is valid for C3.C4 M2 Mandate M2 is also valid for C4.Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account.Example - Assignment of one contract account per mandateMandate Contract Account (in Mandate) MeaningM1 C1 Mandate M1 is only valid for items of contract account C1.M2 C2 Mandate M2 is only valid for items of contract account C2.If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects.The examples above apply in a similar manner to the assignment of contracts.Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate.If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details.If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment.If you do not make any specification, the system uses the first mandate that qualifies for the payment.
    
    Returns:
    
    Identifies, together with the Creditor Identifier, the mandate uniquely.
  - getCompanyCode
```
@Nullable
public String getCompanyCode()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CompanyCode
    
    Returns:
    
    The company code is an organizational unit within financial accounting.
  - getReferenceDocument
```
@Nullable
public String getReferenceDocument()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceDocument
    
    Returns:
    
    Source document on which a billing document request is based
  - getReferenceDocumentLogicalSystem
```
@Nullable
public String getReferenceDocumentLogicalSystem()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
    
    Returns:
    
    Logical system containing source document of BDR
  - getReferenceDocSDDocCategory
```
@Nullable
public String getReferenceDocSDDocCategory()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ReferenceDocSDDocCategory
    
    Returns:
    
    SD document category of BDR source document
  - getSoldToParty
```
@Nullable
public String getSoldToParty()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SoldToParty
    
    Returns:
    
    The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.
  - getPurchaseOrderByCustomer
```
@Nullable
public String getPurchaseOrderByCustomer()
```
    Constraints: Not nullable, Maximum length: 35
    Original property name from the Odata EDM: PurchaseOrderByCustomer
    
    The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
    
    Returns:
    
    Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order).
  - getPricingDocument
```
@Nullable
public String getPricingDocument()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: PricingDocument
    
    The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area. The system uses the internal number to identify the different conditions.
    
    Returns:
    
    The internal number under which the system saves conditions that apply to a sales order, for example.
  - getBillingIssueType
```
@Nullable
public String getBillingIssueType()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillingIssueType
    
    Returns:
    
    SD Billing Document Issue
  - getIncotermsVersion
```
@Nullable
public String getIncotermsVersion()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: IncotermsVersion
    
    Returns:
    
    An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC).
  - getIncotermsClassification
```
@Nullable
public String getIncotermsClassification()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: IncotermsClassification
    
    Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
    
    Returns:
    
    Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC).
  - getIncotermsTransferLocation
```
@Nullable
public String getIncotermsTransferLocation()
```
    Constraints: Not nullable, Maximum length: 28
    Original property name from the Odata EDM: IncotermsTransferLocation
    
    If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
    
    Returns:
    
    Additional information for the primary Incoterm.
  - getIncotermsLocation1
```
@Nullable
public String getIncotermsLocation1()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation1
    
    1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
    
    Returns:
    
    Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
  - getIncotermsLocation2
```
@Nullable
public String getIncotermsLocation2()
```
    Constraints: Not nullable, Maximum length: 70
    Original property name from the Odata EDM: IncotermsLocation2
    
    No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
    
    Returns:
    
    Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below:
  - getOverallBillingDocReqStatus
```
@Nullable
public String getOverallBillingDocReqStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallBillingDocReqStatus
    
    Returns:
    
    Billing Document Request Status
  - getOverallPricingIncompletionSts
```
@Nullable
public String getOverallPricingIncompletionSts()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallPricingIncompletionSts
    
    Returns:
    
    Pricing Incompletion Status (All Items)
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<BillingDocumentRequest>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<BillingDocumentRequest>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<BillingDocumentRequest>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<BillingDocumentRequest>

Class BillingDocumentRequest

Nested Class Summary

Field Summary

Fields inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Constructor Summary

Method Summary

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmEntity

Methods inherited from class com.sap.cloud.sdk.datamodel.odata.helper.VdmObject

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

BILLING_DOCUMENT_REQUEST

BILLING_DOCUMENT_REQUEST_TYPE

PROPOSED_BILLING_DOCUMENT_TYPE

CREATION_DATE

CREATION_TIME

LAST_CHANGE_DATE

LAST_CHANGE_DATE_TIME

LOGICAL_SYSTEM

SALES_ORGANIZATION

DISTRIBUTION_CHANNEL

DIVISION

BILLING_DOCUMENT_DATE

TOTAL_NET_AMOUNT

TRANSACTION_CURRENCY

TOTAL_TAX_AMOUNT

TOTAL_GROSS_AMOUNT

TAX_DEPARTURE_COUNTRY

PAYER_PARTY

CONTRACT_ACCOUNT

CUSTOMER_PAYMENT_TERMS

PAYMENT_METHOD

SEPA_MANDATE

COMPANY_CODE

REFERENCE_DOCUMENT

REFERENCE_DOCUMENT_LOGICAL_SYSTEM

REFERENCE_DOC_SD_DOC_CATEGORY

SOLD_TO_PARTY

PURCHASE_ORDER_BY_CUSTOMER

PRICING_DOCUMENT

BILLING_ISSUE_TYPE

INCOTERMS_VERSION

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

OVERALL_BILLING_DOC_REQ_STATUS

OVERALL_PRICING_INCOMPLETION_STS

TO_ITEM

TO_PARTNER

TO_PRICING_ELEMENT

Constructor Detail

BillingDocumentRequest

BillingDocumentRequest

Method Detail

getType

setBillingDocumentRequest

setBillingDocumentRequestType

setProposedBillingDocumentType

setCreationDate

setCreationTime

setLastChangeDate

setLastChangeDateTime

setLogicalSystem

setSalesOrganization

setDistributionChannel

setDivision

setBillingDocumentDate

setTotalNetAmount

setTransactionCurrency

setTotalTaxAmount

setTotalGrossAmount

setTaxDepartureCountry

setPayerParty

setContractAccount

setCustomerPaymentTerms

setPaymentMethod

setSEPAMandate

setCompanyCode

setReferenceDocument