BillingDocument (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<BillingDocument>
  - - com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.billingdocument.BillingDocument

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

Original entity name from the Odata EDM: A_BillingDocumentType

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class BillingDocument.BillingDocumentBuilder
Helper class to allow for fluent creation of BillingDocument instances.

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

Field Summary

Fields
Modifier and Type	Field and Description
`static BillingDocumentField<BigDecimal>`	`ABSLT_ACCOUNTING_EXCHANGE_RATE` Use with available fluent helpers to apply the AbsltAccountingExchangeRate field to query operations.
`static BillingDocumentField<String>`	`ACCOUNTING_DOCUMENT` Use with available fluent helpers to apply the AccountingDocument field to query operations.
`static BillingDocumentField<Boolean>`	`ACCOUNTING_EXCHANGE_RATE_IS_SET` Use with available fluent helpers to apply the AccountingExchangeRateIsSet field to query operations.
`static BillingDocumentField<String>`	`ACCOUNTING_POSTING_STATUS` Use with available fluent helpers to apply the AccountingPostingStatus field to query operations.
`static BillingDocumentField<String>`	`ACCOUNTING_TRANSFER_STATUS` Use with available fluent helpers to apply the AccountingTransferStatus field to query operations.
`static BillingDocumentField<Boolean>`	`ACCTG_EXCHANGE_RATE_IS_INDRCT_QTAN` Use with available fluent helpers to apply the AcctgExchangeRateIsIndrctQtan field to query operations.
`static BillingDocumentField<String>`	`ADDITIONAL_VALUE_DAYS` Use with available fluent helpers to apply the AdditionalValueDays field to query operations.
`static BillingDocumentSelectable`	`ALL_FIELDS` Selector for all available fields of BillingDocument.
`static BillingDocumentField<String>`	`ASSIGNMENT_REFERENCE` Use with available fluent helpers to apply the AssignmentReference field to query operations.
`static BillingDocumentField<String>`	`BILLING_DOC_COMBINATION_CRITERIA` Use with available fluent helpers to apply the BillingDocCombinationCriteria field to query operations.
`static BillingDocumentField<String>`	`BILLING_DOCUMENT` Use with available fluent helpers to apply the BillingDocument field to query operations.
`static BillingDocumentField<String>`	`BILLING_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the BillingDocumentCategory field to query operations.
`static BillingDocumentField<LocalDateTime>`	`BILLING_DOCUMENT_DATE` Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
`static BillingDocumentField<Boolean>`	`BILLING_DOCUMENT_IS_CANCELLED` Use with available fluent helpers to apply the BillingDocumentIsCancelled field to query operations.
`static BillingDocumentField<LocalDateTime>`	`BILLING_DOCUMENT_LIST_DATE` Use with available fluent helpers to apply the BillingDocumentListDate field to query operations.
`static BillingDocumentField<String>`	`BILLING_DOCUMENT_LIST_TYPE` Use with available fluent helpers to apply the BillingDocumentListType field to query operations.
`static BillingDocumentField<String>`	`BILLING_DOCUMENT_TYPE` Use with available fluent helpers to apply the BillingDocumentType field to query operations.
`static BillingDocumentField<String>`	`BILLING_ISSUE_TYPE` Use with available fluent helpers to apply the BillingIssueType field to query operations.
`static BillingDocumentField<String>`	`CANCELLED_BILLING_DOCUMENT` Use with available fluent helpers to apply the CancelledBillingDocument field to query operations.
`static BillingDocumentField<String>`	`CITY_CODE` Use with available fluent helpers to apply the CityCode field to query operations.
`static BillingDocumentField<String>`	`COMPANY_CODE` Use with available fluent helpers to apply the CompanyCode field to query operations.
`static BillingDocumentField<String>`	`CONTRACT_ACCOUNT` Use with available fluent helpers to apply the ContractAccount field to query operations.
`static BillingDocumentField<String>`	`COUNTRY` Use with available fluent helpers to apply the Country field to query operations.
`static BillingDocumentField<String>`	`COUNTY` Use with available fluent helpers to apply the County field to query operations.
`static BillingDocumentField<LocalDateTime>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static BillingDocumentField<LocalTime>`	`CREATION_TIME` Use with available fluent helpers to apply the CreationTime field to query operations.
`static BillingDocumentField<String>`	`CREDIT_CONTROL_AREA` Use with available fluent helpers to apply the CreditControlArea field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP` Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_GROUP` Use with available fluent helpers to apply the CustomerGroup field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_PAYMENT_TERMS` Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_PRICE_GROUP` Use with available fluent helpers to apply the CustomerPriceGroup field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_REBATE_AGREEMENT` Use with available fluent helpers to apply the CustomerRebateAgreement field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION1` Use with available fluent helpers to apply the CustomerTaxClassification1 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION2` Use with available fluent helpers to apply the CustomerTaxClassification2 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION3` Use with available fluent helpers to apply the CustomerTaxClassification3 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION4` Use with available fluent helpers to apply the CustomerTaxClassification4 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION5` Use with available fluent helpers to apply the CustomerTaxClassification5 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION6` Use with available fluent helpers to apply the CustomerTaxClassification6 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION7` Use with available fluent helpers to apply the CustomerTaxClassification7 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION8` Use with available fluent helpers to apply the CustomerTaxClassification8 field to query operations.
`static BillingDocumentField<String>`	`CUSTOMER_TAX_CLASSIFICATION9` Use with available fluent helpers to apply the CustomerTaxClassification9 field to query operations.
`static BillingDocumentField<String>`	`DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the DistributionChannel field to query operations.
`static BillingDocumentField<String>`	`DIVISION` Use with available fluent helpers to apply the Division field to query operations.
`static BillingDocumentField<String>`	`DOCUMENT_REFERENCE_ID` Use with available fluent helpers to apply the DocumentReferenceID field to query operations.
`static BillingDocumentField<String>`	`DUNNING_AREA` Use with available fluent helpers to apply the DunningArea field to query operations.
`static BillingDocumentField<String>`	`DUNNING_BLOCKING_REASON` Use with available fluent helpers to apply the DunningBlockingReason field to query operations.
`static BillingDocumentField<String>`	`DUNNING_KEY` Use with available fluent helpers to apply the DunningKey field to query operations.
`static BillingDocumentField<LocalDateTime>`	`EXCHANGE_RATE_DATE` Use with available fluent helpers to apply the ExchangeRateDate field to query operations.
`static BillingDocumentField<String>`	`EXCHANGE_RATE_TYPE` Use with available fluent helpers to apply the ExchangeRateType field to query operations.
`static BillingDocumentField<String>`	`FISCAL_YEAR` Use with available fluent helpers to apply the FiscalYear field to query operations.
`static BillingDocumentField<LocalDateTime>`	`FIXED_VALUE_DATE` Use with available fluent helpers to apply the FixedValueDate field to query operations.
`static BillingDocumentField<String>`	`FOREIGN_TRADE` Use with available fluent helpers to apply the ForeignTrade field to query operations.
`static BillingDocumentField<String>`	`HIERARCHY_TYPE_PRICING` Use with available fluent helpers to apply the HierarchyTypePricing field to query operations.
`static BillingDocumentField<String>`	`INCOTERMS_CLASSIFICATION` Use with available fluent helpers to apply the IncotermsClassification field to query operations.
`static BillingDocumentField<String>`	`INCOTERMS_LOCATION1` Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
`static BillingDocumentField<String>`	`INCOTERMS_LOCATION2` Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
`static BillingDocumentField<String>`	`INCOTERMS_TRANSFER_LOCATION` Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
`static BillingDocumentField<String>`	`INCOTERMS_VERSION` Use with available fluent helpers to apply the IncotermsVersion field to query operations.
`static BillingDocumentField<String>`	`INTERNAL_FINANCIAL_DOCUMENT` Use with available fluent helpers to apply the InternalFinancialDocument field to query operations.
`static BillingDocumentField<String>`	`INVOICE_CLEARING_STATUS` Use with available fluent helpers to apply the InvoiceClearingStatus field to query operations.
`static BillingDocumentField<String>`	`INVOICE_LIST_STATUS` Use with available fluent helpers to apply the InvoiceListStatus field to query operations.
`static BillingDocumentField<Boolean>`	`IS_EU_TRIANGULAR_DEAL` Use with available fluent helpers to apply the IsEUTriangularDeal field to query operations.
`static BillingDocumentField<String>`	`IS_EXPORT_DELIVERY` Use with available fluent helpers to apply the IsExportDelivery field to query operations.
`static BillingDocumentField<Boolean>`	`IS_INTRASTAT_REPORTING_EXCLUDED` Use with available fluent helpers to apply the IsIntrastatReportingExcluded field to query operations.
`static BillingDocumentField<Boolean>`	`IS_INTRASTAT_REPORTING_RELEVANT` Use with available fluent helpers to apply the IsIntrastatReportingRelevant field to query operations.
`static BillingDocumentField<Boolean>`	`IS_RELEVANT_FOR_ACCRUAL` Use with available fluent helpers to apply the IsRelevantForAccrual field to query operations.
`static BillingDocumentField<LocalDateTime>`	`LAST_CHANGE_DATE` Use with available fluent helpers to apply the LastChangeDate field to query operations.
`static BillingDocumentField<ZonedDateTime>`	`LAST_CHANGE_DATE_TIME` Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
`static BillingDocumentField<String>`	`LOGICAL_SYSTEM` Use with available fluent helpers to apply the LogicalSystem field to query operations.
`static BillingDocumentField<Boolean>`	`MANUAL_INVOICE_MAINT_IS_RELEVANT` Use with available fluent helpers to apply the ManualInvoiceMaintIsRelevant field to query operations.
`static BillingDocumentField<String>`	`OVERALL_BILLING_STATUS` Use with available fluent helpers to apply the OverallBillingStatus field to query operations.
`static BillingDocumentField<String>`	`OVERALL_PRICING_INCOMPLETION_STS` Use with available fluent helpers to apply the OverallPricingIncompletionSts field to query operations.
`static BillingDocumentField<String>`	`OVERALL_SD_PROCESS_STATUS` Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
`static BillingDocumentField<String>`	`OVRL_ITM_GENERAL_INCOMPLETION_STS` Use with available fluent helpers to apply the OvrlItmGeneralIncompletionSts field to query operations.
`static BillingDocumentField<String>`	`PARTNER_COMPANY` Use with available fluent helpers to apply the PartnerCompany field to query operations.
`static BillingDocumentField<String>`	`PAYER_PARTY` Use with available fluent helpers to apply the PayerParty field to query operations.
`static BillingDocumentField<String>`	`PAYMENT_METHOD` Use with available fluent helpers to apply the PaymentMethod field to query operations.
`static BillingDocumentField<String>`	`PAYMENT_REFERENCE` Use with available fluent helpers to apply the PaymentReference field to query operations.
`static BillingDocumentField<String>`	`PRICE_LIST_TYPE` Use with available fluent helpers to apply the PriceListType field to query operations.
`static BillingDocumentField<String>`	`PURCHASE_ORDER_BY_CUSTOMER` Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
`static BillingDocumentField<String>`	`REGION` Use with available fluent helpers to apply the Region field to query operations.
`static BillingDocumentField<String>`	`SALES_DISTRICT` Use with available fluent helpers to apply the SalesDistrict field to query operations.
`static BillingDocumentField<String>`	`SALES_DOCUMENT_CONDITION` Use with available fluent helpers to apply the SalesDocumentCondition field to query operations.
`static BillingDocumentField<String>`	`SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrganization field to query operations.
`static BillingDocumentField<String>`	`SD_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the SDDocumentCategory field to query operations.
`static BillingDocumentField<String>`	`SD_PRICING_PROCEDURE` Use with available fluent helpers to apply the SDPricingProcedure field to query operations.
`static BillingDocumentField<String>`	`SEPA_MANDATE` Use with available fluent helpers to apply the SEPAMandate field to query operations.
`static BillingDocumentField<String>`	`SHIPPING_CONDITION` Use with available fluent helpers to apply the ShippingCondition field to query operations.
`static BillingDocumentField<String>`	`SOLD_TO_PARTY` Use with available fluent helpers to apply the SoldToParty field to query operations.
`static BillingDocumentField<String>`	`STATISTICS_CURRENCY` Use with available fluent helpers to apply the StatisticsCurrency field to query operations.
`static BillingDocumentField<BigDecimal>`	`TAX_AMOUNT` Use with available fluent helpers to apply the TaxAmount field to query operations.
`static BillingDocumentField<String>`	`TAX_DEPARTURE_COUNTRY` Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
`static BillingDocumentLink<BillingDocumentItem>`	`TO_ITEM` Use with available fluent helpers to apply the to_Item navigation property to query operations.
`static BillingDocumentLink<BillingDocumentPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static BillingDocumentLink<BillingDocumentPrcgElmnt>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static BillingDocumentLink<BillingDocumentText>`	`TO_TEXT` Use with available fluent helpers to apply the to_Text navigation property to query operations.
`static BillingDocumentField<BigDecimal>`	`TOTAL_GROSS_AMOUNT` Use with available fluent helpers to apply the TotalGrossAmount field to query operations.
`static BillingDocumentField<BigDecimal>`	`TOTAL_NET_AMOUNT` Use with available fluent helpers to apply the TotalNetAmount field to query operations.
`static BillingDocumentField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.
`static BillingDocumentField<String>`	`VAT_REGISTRATION` Use with available fluent helpers to apply the VATRegistration field to query operations.
`static BillingDocumentField<String>`	`VAT_REGISTRATION_COUNTRY` Use with available fluent helpers to apply the VATRegistrationCountry field to query operations.
`static BillingDocumentField<String>`	`VAT_REGISTRATION_ORIGIN` Use with available fluent helpers to apply the VATRegistrationOrigin field to query operations.

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

Constructor Summary

Constructors
Constructor and Description
`BillingDocument()`
BillingDocument(String billingDocument, String sDDocumentCategory, String billingDocumentCategory, String billingDocumentType, LocalDateTime creationDate, LocalTime creationTime, LocalDateTime lastChangeDate, ZonedDateTime lastChangeDateTime, String logicalSystem, String salesOrganization, String distributionChannel, String division, LocalDateTime billingDocumentDate, Boolean billingDocumentIsCancelled, String cancelledBillingDocument, String foreignTrade, String isExportDelivery, String billingDocCombinationCriteria, Boolean manualInvoiceMaintIsRelevant, Boolean isIntrastatReportingRelevant, Boolean isIntrastatReportingExcluded, BigDecimal totalNetAmount, String transactionCurrency, String statisticsCurrency, BigDecimal taxAmount, BigDecimal totalGrossAmount, String customerPriceGroup, String priceListType, String taxDepartureCountry, String vATRegistration, String vATRegistrationOrigin, String vATRegistrationCountry, String hierarchyTypePricing, String customerTaxClassification1, String customerTaxClassification2, String customerTaxClassification3, String customerTaxClassification4, String customerTaxClassification5, String customerTaxClassification6, String customerTaxClassification7, String customerTaxClassification8, String customerTaxClassification9, Boolean isEUTriangularDeal, String sDPricingProcedure, String shippingCondition, String incotermsVersion, String incotermsClassification, String incotermsTransferLocation, String incotermsLocation1, String incotermsLocation2, String payerParty, String contractAccount, String customerPaymentTerms, String paymentMethod, String paymentReference, LocalDateTime fixedValueDate, String additionalValueDays, String sEPAMandate, String companyCode, String fiscalYear, String accountingDocument, String customerAccountAssignmentGroup, Boolean accountingExchangeRateIsSet, BigDecimal absltAccountingExchangeRate, Boolean acctgExchangeRateIsIndrctQtan, LocalDateTime exchangeRateDate, String exchangeRateType, String documentReferenceID, String assignmentReference, String dunningArea, String dunningBlockingReason, String dunningKey, String internalFinancialDocument, Boolean isRelevantForAccrual, String soldToParty, String partnerCompany, String purchaseOrderByCustomer, String customerGroup, String country, String cityCode, String salesDistrict, String region, String county, String creditControlArea, String customerRebateAgreement, String salesDocumentCondition, String overallSDProcessStatus, String overallBillingStatus, String accountingPostingStatus, String accountingTransferStatus, String billingIssueType, String invoiceListStatus, String ovrlItmGeneralIncompletionSts, String overallPricingIncompletionSts, String invoiceClearingStatus, String billingDocumentListType, LocalDateTime billingDocumentListDate, List<BillingDocumentItem> toItem, List<BillingDocumentPartner> toPartner, List<BillingDocumentPrcgElmnt> toPricingElement, List<BillingDocumentText> toText)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addItem(BillingDocumentItem... entity)` Adds elements to the list of associated BillingDocumentItem entities.
`void`	`addPartner(BillingDocumentPartner... entity)` Adds elements to the list of associated BillingDocumentPartner entities.
`void`	`addPricingElement(BillingDocumentPrcgElmnt... entity)` Adds elements to the list of associated BillingDocumentPrcgElmnt entities.
`void`	`addText(BillingDocumentText... entity)` Adds elements to the list of associated BillingDocumentText entities.
`void`	`attachToService(String servicePath, HttpDestinationProperties destination)` Sets the service path and destination for the fetch commands of this entity.
`static BillingDocument.BillingDocumentBuilder`	`builder()`
`protected boolean`	`canEqual(Object other)`
`boolean`	`equals(Object o)`
`List<BillingDocumentItem>`	`fetchItem()` Fetches the BillingDocumentItem entities (one to many) associated with this entity.
`List<BillingDocumentPartner>`	`fetchPartner()` Fetches the BillingDocumentPartner entities (one to many) associated with this entity.
`List<BillingDocumentPrcgElmnt>`	`fetchPricingElement()` Fetches the BillingDocumentPrcgElmnt entities (one to many) associated with this entity.
`List<BillingDocumentText>`	`fetchText()` Fetches the BillingDocumentText entities (one to many) associated with this entity.
`static <T> BillingDocumentField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`static <T,DomainT> BillingDocumentField<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)`
`BigDecimal`	`getAbsltAccountingExchangeRate()` Constraints: Not nullable, Precision: 9, Scale: 5
`String`	`getAccountingDocument()` Constraints: Not nullable, Maximum length: 10
`Boolean`	`getAccountingExchangeRateIsSet()` Constraints: none
`String`	`getAccountingPostingStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getAccountingTransferStatus()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getAcctgExchangeRateIsIndrctQtan()` Constraints: none
`String`	`getAdditionalValueDays()` Constraints: Not nullable, Maximum length: 2
`String`	`getAssignmentReference()` Constraints: Not nullable, Maximum length: 18
`String`	`getBillingDocCombinationCriteria()` Constraints: Not nullable, Maximum length: 40
`String`	`getBillingDocument()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getBillingDocumentCategory()` Constraints: Not nullable, Maximum length: 1
`LocalDateTime`	`getBillingDocumentDate()` Constraints: Not nullable, Precision: 0
`Boolean`	`getBillingDocumentIsCancelled()` Constraints: none
`LocalDateTime`	`getBillingDocumentListDate()` Constraints: Not nullable, Precision: 0
`String`	`getBillingDocumentListType()` Constraints: Not nullable, Maximum length: 4
`String`	`getBillingDocumentType()` Constraints: Not nullable, Maximum length: 4
`String`	`getBillingIssueType()` Constraints: Not nullable, Maximum length: 1
`String`	`getCancelledBillingDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getCityCode()` Constraints: Not nullable, Maximum length: 4
`String`	`getCompanyCode()` Constraints: Not nullable, Maximum length: 4
`String`	`getContractAccount()` Constraints: Not nullable, Maximum length: 12
`String`	`getCountry()` Constraints: Not nullable, Maximum length: 3
`String`	`getCounty()` Constraints: Not nullable, Maximum length: 3
`LocalDateTime`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`LocalTime`	`getCreationTime()` Constraints: Not nullable, Precision: 0
`String`	`getCreditControlArea()` Constraints: Not nullable, Maximum length: 4
`String`	`getCustomerAccountAssignmentGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerPaymentTerms()` Constraints: Not nullable, Maximum length: 4
`String`	`getCustomerPriceGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerRebateAgreement()` Constraints: Not nullable, Maximum length: 10
`String`	`getCustomerTaxClassification1()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification2()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification3()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification4()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification5()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification6()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification7()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification8()` Constraints: Not nullable, Maximum length: 1
`String`	`getCustomerTaxClassification9()` Constraints: Not nullable, Maximum length: 1
`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
`String`	`getDocumentReferenceID()` Constraints: Not nullable, Maximum length: 16
`String`	`getDunningArea()` Constraints: Not nullable, Maximum length: 2
`String`	`getDunningBlockingReason()` Constraints: Not nullable, Maximum length: 1
`String`	`getDunningKey()` Constraints: Not nullable, Maximum length: 1
`protected String`	`getEntityCollection()` Used by fluent helpers and navigation property methods to construct OData queries.
`LocalDateTime`	`getExchangeRateDate()` Constraints: Not nullable, Precision: 0
`String`	`getExchangeRateType()` Constraints: Not nullable, Maximum length: 4
`String`	`getFiscalYear()` Constraints: Not nullable, Maximum length: 4
`LocalDateTime`	`getFixedValueDate()` Constraints: Not nullable, Precision: 0
`String`	`getForeignTrade()` Constraints: Not nullable, Maximum length: 10
`String`	`getHierarchyTypePricing()` Constraints: Not nullable, Maximum length: 1
`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
`String`	`getInternalFinancialDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getInvoiceClearingStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getInvoiceListStatus()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getIsEUTriangularDeal()` Constraints: none
`String`	`getIsExportDelivery()` Constraints: Not nullable, Maximum length: 1
`Boolean`	`getIsIntrastatReportingExcluded()` Constraints: none
`Boolean`	`getIsIntrastatReportingRelevant()` Constraints: none
`Boolean`	`getIsRelevantForAccrual()` Constraints: none
`io.vavr.control.Option<List<BillingDocumentItem>>`	`getItemIfPresent()` Retrieval of associated BillingDocumentItem entities (one to many).
`List<BillingDocumentItem>`	`getItemOrFetch()` Retrieval of associated BillingDocumentItem 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
`Boolean`	`getManualInvoiceMaintIsRelevant()` Constraints: none
`String`	`getOverallBillingStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallPricingIncompletionSts()` Constraints: Not nullable, Maximum length: 1
`String`	`getOverallSDProcessStatus()` Constraints: Not nullable, Maximum length: 1
`String`	`getOvrlItmGeneralIncompletionSts()` Constraints: Not nullable, Maximum length: 1
`String`	`getPartnerCompany()` Constraints: Not nullable, Maximum length: 6
`io.vavr.control.Option<List<BillingDocumentPartner>>`	`getPartnerIfPresent()` Retrieval of associated BillingDocumentPartner entities (one to many).
`List<BillingDocumentPartner>`	`getPartnerOrFetch()` Retrieval of associated BillingDocumentPartner entities (one to many).
`String`	`getPayerParty()` Constraints: Not nullable, Maximum length: 10
`String`	`getPaymentMethod()` Constraints: Not nullable, Maximum length: 1
`String`	`getPaymentReference()` Constraints: Not nullable, Maximum length: 30
`String`	`getPriceListType()` Constraints: Not nullable, Maximum length: 2
`io.vavr.control.Option<List<BillingDocumentPrcgElmnt>>`	`getPricingElementIfPresent()` Retrieval of associated BillingDocumentPrcgElmnt entities (one to many).
`List<BillingDocumentPrcgElmnt>`	`getPricingElementOrFetch()` Retrieval of associated BillingDocumentPrcgElmnt entities (one to many).
`String`	`getPurchaseOrderByCustomer()` Constraints: Not nullable, Maximum length: 35
`String`	`getRegion()` Constraints: Not nullable, Maximum length: 3
`String`	`getSalesDistrict()` Constraints: Not nullable, Maximum length: 6
`String`	`getSalesDocumentCondition()` Constraints: Not nullable, Maximum length: 10
`String`	`getSalesOrganization()` Constraints: Not nullable, Maximum length: 4
`String`	`getSDDocumentCategory()` Constraints: Not nullable, Maximum length: 4
`String`	`getSDPricingProcedure()` Constraints: Not nullable, Maximum length: 6
`String`	`getSEPAMandate()` Constraints: Not nullable, Maximum length: 35
`String`	`getShippingCondition()` Constraints: Not nullable, Maximum length: 2
`String`	`getSoldToParty()` Constraints: Not nullable, Maximum length: 10
`String`	`getStatisticsCurrency()` Constraints: Not nullable, Maximum length: 5
`BigDecimal`	`getTaxAmount()` Constraints: Not nullable, Precision: 14, Scale: 3
`String`	`getTaxDepartureCountry()` Constraints: Not nullable, Maximum length: 3
`io.vavr.control.Option<List<BillingDocumentText>>`	`getTextIfPresent()` Retrieval of associated BillingDocumentText entities (one to many).
`List<BillingDocumentText>`	`getTextOrFetch()` Retrieval of associated BillingDocumentText entities (one to many).
`BigDecimal`	`getTotalGrossAmount()` Constraints: Not nullable, Precision: 17, Scale: 3
`BigDecimal`	`getTotalNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5
`Class<BillingDocument>`	`getType()`
`String`	`getVATRegistration()` Constraints: Not nullable, Maximum length: 20
`String`	`getVATRegistrationCountry()` Constraints: Not nullable, Maximum length: 3
`String`	`getVATRegistrationOrigin()` Constraints: Not nullable, Maximum length: 1
`int`	`hashCode()`
`void`	`setAbsltAccountingExchangeRate(BigDecimal absltAccountingExchangeRate)` Constraints: Not nullable, Precision: 9, Scale: 5
`void`	`setAccountingDocument(String accountingDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setAccountingExchangeRateIsSet(Boolean accountingExchangeRateIsSet)` Constraints: none
`void`	`setAccountingPostingStatus(String accountingPostingStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setAccountingTransferStatus(String accountingTransferStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setAcctgExchangeRateIsIndrctQtan(Boolean acctgExchangeRateIsIndrctQtan)` Constraints: none
`void`	`setAdditionalValueDays(String additionalValueDays)` Constraints: Not nullable, Maximum length: 2
`void`	`setAssignmentReference(String assignmentReference)` Constraints: Not nullable, Maximum length: 18
`void`	`setBillingDocCombinationCriteria(String billingDocCombinationCriteria)` Constraints: Not nullable, Maximum length: 40
`void`	`setBillingDocument(String billingDocument)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setBillingDocumentCategory(String billingDocumentCategory)` Constraints: Not nullable, Maximum length: 1
`void`	`setBillingDocumentDate(LocalDateTime billingDocumentDate)` Constraints: Not nullable, Precision: 0
`void`	`setBillingDocumentIsCancelled(Boolean billingDocumentIsCancelled)` Constraints: none
`void`	`setBillingDocumentListDate(LocalDateTime billingDocumentListDate)` Constraints: Not nullable, Precision: 0
`void`	`setBillingDocumentListType(String billingDocumentListType)` Constraints: Not nullable, Maximum length: 4
`void`	`setBillingDocumentType(String billingDocumentType)` Constraints: Not nullable, Maximum length: 4
`void`	`setBillingIssueType(String billingIssueType)` Constraints: Not nullable, Maximum length: 1
`void`	`setCancelledBillingDocument(String cancelledBillingDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setCityCode(String cityCode)` Constraints: Not nullable, Maximum length: 4
`void`	`setCompanyCode(String companyCode)` Constraints: Not nullable, Maximum length: 4
`void`	`setContractAccount(String contractAccount)` Constraints: Not nullable, Maximum length: 12
`void`	`setCountry(String country)` Constraints: Not nullable, Maximum length: 3
`void`	`setCounty(String county)` Constraints: Not nullable, Maximum length: 3
`void`	`setCreationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setCreationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`void`	`setCreditControlArea(String creditControlArea)` Constraints: Not nullable, Maximum length: 4
`void`	`setCustomerAccountAssignmentGroup(String customerAccountAssignmentGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerGroup(String customerGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerPaymentTerms(String customerPaymentTerms)` Constraints: Not nullable, Maximum length: 4
`void`	`setCustomerPriceGroup(String customerPriceGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerRebateAgreement(String customerRebateAgreement)` Constraints: Not nullable, Maximum length: 10
`void`	`setCustomerTaxClassification1(String customerTaxClassification1)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification2(String customerTaxClassification2)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification3(String customerTaxClassification3)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification4(String customerTaxClassification4)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification5(String customerTaxClassification5)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification6(String customerTaxClassification6)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification7(String customerTaxClassification7)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification8(String customerTaxClassification8)` Constraints: Not nullable, Maximum length: 1
`void`	`setCustomerTaxClassification9(String customerTaxClassification9)` Constraints: Not nullable, Maximum length: 1
`void`	`setDistributionChannel(String distributionChannel)` Constraints: Not nullable, Maximum length: 2
`void`	`setDivision(String division)` Constraints: Not nullable, Maximum length: 2
`void`	`setDocumentReferenceID(String documentReferenceID)` Constraints: Not nullable, Maximum length: 16
`void`	`setDunningArea(String dunningArea)` Constraints: Not nullable, Maximum length: 2
`void`	`setDunningBlockingReason(String dunningBlockingReason)` Constraints: Not nullable, Maximum length: 1
`void`	`setDunningKey(String dunningKey)` Constraints: Not nullable, Maximum length: 1
`void`	`setExchangeRateDate(LocalDateTime exchangeRateDate)` Constraints: Not nullable, Precision: 0
`void`	`setExchangeRateType(String exchangeRateType)` Constraints: Not nullable, Maximum length: 4
`void`	`setFiscalYear(String fiscalYear)` Constraints: Not nullable, Maximum length: 4
`void`	`setFixedValueDate(LocalDateTime fixedValueDate)` Constraints: Not nullable, Precision: 0
`void`	`setForeignTrade(String foreignTrade)` Constraints: Not nullable, Maximum length: 10
`void`	`setHierarchyTypePricing(String hierarchyTypePricing)` Constraints: Not nullable, Maximum length: 1
`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`	`setInternalFinancialDocument(String internalFinancialDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setInvoiceClearingStatus(String invoiceClearingStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setInvoiceListStatus(String invoiceListStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setIsEUTriangularDeal(Boolean isEUTriangularDeal)` Constraints: none
`void`	`setIsExportDelivery(String isExportDelivery)` Constraints: Not nullable, Maximum length: 1
`void`	`setIsIntrastatReportingExcluded(Boolean isIntrastatReportingExcluded)` Constraints: none
`void`	`setIsIntrastatReportingRelevant(Boolean isIntrastatReportingRelevant)` Constraints: none
`void`	`setIsRelevantForAccrual(Boolean isRelevantForAccrual)` Constraints: none
`void`	`setItem(List<BillingDocumentItem> value)` Overwrites the list of associated BillingDocumentItem 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`	`setManualInvoiceMaintIsRelevant(Boolean manualInvoiceMaintIsRelevant)` Constraints: none
`void`	`setOverallBillingStatus(String overallBillingStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallPricingIncompletionSts(String overallPricingIncompletionSts)` Constraints: Not nullable, Maximum length: 1
`void`	`setOverallSDProcessStatus(String overallSDProcessStatus)` Constraints: Not nullable, Maximum length: 1
`void`	`setOvrlItmGeneralIncompletionSts(String ovrlItmGeneralIncompletionSts)` Constraints: Not nullable, Maximum length: 1
`void`	`setPartner(List<BillingDocumentPartner> value)` Overwrites the list of associated BillingDocumentPartner entities for the loaded navigation property to_Partner.
`void`	`setPartnerCompany(String partnerCompany)` Constraints: Not nullable, Maximum length: 6
`void`	`setPayerParty(String payerParty)` Constraints: Not nullable, Maximum length: 10
`void`	`setPaymentMethod(String paymentMethod)` Constraints: Not nullable, Maximum length: 1
`void`	`setPaymentReference(String paymentReference)` Constraints: Not nullable, Maximum length: 30
`void`	`setPriceListType(String priceListType)` Constraints: Not nullable, Maximum length: 2
`void`	`setPricingElement(List<BillingDocumentPrcgElmnt> value)` Overwrites the list of associated BillingDocumentPrcgElmnt entities for the loaded navigation property to_PricingElement.
`void`	`setPurchaseOrderByCustomer(String purchaseOrderByCustomer)` Constraints: Not nullable, Maximum length: 35
`void`	`setRegion(String region)` Constraints: Not nullable, Maximum length: 3
`void`	`setSalesDistrict(String salesDistrict)` Constraints: Not nullable, Maximum length: 6
`void`	`setSalesDocumentCondition(String salesDocumentCondition)` Constraints: Not nullable, Maximum length: 10
`void`	`setSalesOrganization(String salesOrganization)` Constraints: Not nullable, Maximum length: 4
`void`	`setSDDocumentCategory(String sDDocumentCategory)` Constraints: Not nullable, Maximum length: 4
`void`	`setSDPricingProcedure(String sDPricingProcedure)` Constraints: Not nullable, Maximum length: 6
`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`	`setShippingCondition(String shippingCondition)` Constraints: Not nullable, Maximum length: 2
`void`	`setSoldToParty(String soldToParty)` Constraints: Not nullable, Maximum length: 10
`void`	`setStatisticsCurrency(String statisticsCurrency)` Constraints: Not nullable, Maximum length: 5
`void`	`setTaxAmount(BigDecimal taxAmount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setTaxDepartureCountry(String taxDepartureCountry)` Constraints: Not nullable, Maximum length: 3
`void`	`setText(List<BillingDocumentText> value)` Overwrites the list of associated BillingDocumentText entities for the loaded navigation property to_Text.
`void`	`setTotalGrossAmount(BigDecimal totalGrossAmount)` Constraints: Not nullable, Precision: 17, Scale: 3
`void`	`setTotalNetAmount(BigDecimal totalNetAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`void`	`setVATRegistration(String vATRegistration)` Constraints: Not nullable, Maximum length: 20
`void`	`setVATRegistrationCountry(String vATRegistrationCountry)` Constraints: Not nullable, Maximum length: 3
`void`	`setVATRegistrationOrigin(String vATRegistrationOrigin)` Constraints: Not nullable, Maximum length: 1
`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 BillingDocumentSelectable ALL_FIELDS
```
    Selector for all available fields of BillingDocument.
  - BILLING_DOCUMENT
```
public static final BillingDocumentField<String> BILLING_DOCUMENT
```
    Use with available fluent helpers to apply the BillingDocument field to query operations.
  - SD_DOCUMENT_CATEGORY
```
public static final BillingDocumentField<String> SD_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the SDDocumentCategory field to query operations.
  - BILLING_DOCUMENT_CATEGORY
```
public static final BillingDocumentField<String> BILLING_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the BillingDocumentCategory field to query operations.
  - BILLING_DOCUMENT_TYPE
```
public static final BillingDocumentField<String> BILLING_DOCUMENT_TYPE
```
    Use with available fluent helpers to apply the BillingDocumentType field to query operations.
  - CREATION_DATE
```
public static final BillingDocumentField<LocalDateTime> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATION_TIME
```
public static final BillingDocumentField<LocalTime> CREATION_TIME
```
    Use with available fluent helpers to apply the CreationTime field to query operations.
  - LAST_CHANGE_DATE
```
public static final BillingDocumentField<LocalDateTime> LAST_CHANGE_DATE
```
    Use with available fluent helpers to apply the LastChangeDate field to query operations.
  - LAST_CHANGE_DATE_TIME
```
public static final BillingDocumentField<ZonedDateTime> LAST_CHANGE_DATE_TIME
```
    Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
  - LOGICAL_SYSTEM
```
public static final BillingDocumentField<String> LOGICAL_SYSTEM
```
    Use with available fluent helpers to apply the LogicalSystem field to query operations.
  - SALES_ORGANIZATION
```
public static final BillingDocumentField<String> SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrganization field to query operations.
  - DISTRIBUTION_CHANNEL
```
public static final BillingDocumentField<String> DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the DistributionChannel field to query operations.
  - DIVISION
```
public static final BillingDocumentField<String> DIVISION
```
    Use with available fluent helpers to apply the Division field to query operations.
  - BILLING_DOCUMENT_DATE
```
public static final BillingDocumentField<LocalDateTime> BILLING_DOCUMENT_DATE
```
    Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
  - BILLING_DOCUMENT_IS_CANCELLED
```
public static final BillingDocumentField<Boolean> BILLING_DOCUMENT_IS_CANCELLED
```
    Use with available fluent helpers to apply the BillingDocumentIsCancelled field to query operations.
  - CANCELLED_BILLING_DOCUMENT
```
public static final BillingDocumentField<String> CANCELLED_BILLING_DOCUMENT
```
    Use with available fluent helpers to apply the CancelledBillingDocument field to query operations.
  - FOREIGN_TRADE
```
public static final BillingDocumentField<String> FOREIGN_TRADE
```
    Use with available fluent helpers to apply the ForeignTrade field to query operations.
  - IS_EXPORT_DELIVERY
```
public static final BillingDocumentField<String> IS_EXPORT_DELIVERY
```
    Use with available fluent helpers to apply the IsExportDelivery field to query operations.
  - BILLING_DOC_COMBINATION_CRITERIA
```
public static final BillingDocumentField<String> BILLING_DOC_COMBINATION_CRITERIA
```
    Use with available fluent helpers to apply the BillingDocCombinationCriteria field to query operations.
  - MANUAL_INVOICE_MAINT_IS_RELEVANT
```
public static final BillingDocumentField<Boolean> MANUAL_INVOICE_MAINT_IS_RELEVANT
```
    Use with available fluent helpers to apply the ManualInvoiceMaintIsRelevant field to query operations.
  - IS_INTRASTAT_REPORTING_RELEVANT
```
public static final BillingDocumentField<Boolean> IS_INTRASTAT_REPORTING_RELEVANT
```
    Use with available fluent helpers to apply the IsIntrastatReportingRelevant field to query operations.
  - IS_INTRASTAT_REPORTING_EXCLUDED
```
public static final BillingDocumentField<Boolean> IS_INTRASTAT_REPORTING_EXCLUDED
```
    Use with available fluent helpers to apply the IsIntrastatReportingExcluded field to query operations.
  - TOTAL_NET_AMOUNT
```
public static final BillingDocumentField<BigDecimal> TOTAL_NET_AMOUNT
```
    Use with available fluent helpers to apply the TotalNetAmount field to query operations.
  - TRANSACTION_CURRENCY
```
public static final BillingDocumentField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - STATISTICS_CURRENCY
```
public static final BillingDocumentField<String> STATISTICS_CURRENCY
```
    Use with available fluent helpers to apply the StatisticsCurrency field to query operations.
  - TAX_AMOUNT
```
public static final BillingDocumentField<BigDecimal> TAX_AMOUNT
```
    Use with available fluent helpers to apply the TaxAmount field to query operations.
  - TOTAL_GROSS_AMOUNT
```
public static final BillingDocumentField<BigDecimal> TOTAL_GROSS_AMOUNT
```
    Use with available fluent helpers to apply the TotalGrossAmount field to query operations.
  - CUSTOMER_PRICE_GROUP
```
public static final BillingDocumentField<String> CUSTOMER_PRICE_GROUP
```
    Use with available fluent helpers to apply the CustomerPriceGroup field to query operations.
  - PRICE_LIST_TYPE
```
public static final BillingDocumentField<String> PRICE_LIST_TYPE
```
    Use with available fluent helpers to apply the PriceListType field to query operations.
  - TAX_DEPARTURE_COUNTRY
```
public static final BillingDocumentField<String> TAX_DEPARTURE_COUNTRY
```
    Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
  - VAT_REGISTRATION
```
public static final BillingDocumentField<String> VAT_REGISTRATION
```
    Use with available fluent helpers to apply the VATRegistration field to query operations.
  - VAT_REGISTRATION_ORIGIN
```
public static final BillingDocumentField<String> VAT_REGISTRATION_ORIGIN
```
    Use with available fluent helpers to apply the VATRegistrationOrigin field to query operations.
  - VAT_REGISTRATION_COUNTRY
```
public static final BillingDocumentField<String> VAT_REGISTRATION_COUNTRY
```
    Use with available fluent helpers to apply the VATRegistrationCountry field to query operations.
  - HIERARCHY_TYPE_PRICING
```
public static final BillingDocumentField<String> HIERARCHY_TYPE_PRICING
```
    Use with available fluent helpers to apply the HierarchyTypePricing field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION1
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION1
```
    Use with available fluent helpers to apply the CustomerTaxClassification1 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION2
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION2
```
    Use with available fluent helpers to apply the CustomerTaxClassification2 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION3
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION3
```
    Use with available fluent helpers to apply the CustomerTaxClassification3 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION4
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION4
```
    Use with available fluent helpers to apply the CustomerTaxClassification4 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION5
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION5
```
    Use with available fluent helpers to apply the CustomerTaxClassification5 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION6
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION6
```
    Use with available fluent helpers to apply the CustomerTaxClassification6 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION7
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION7
```
    Use with available fluent helpers to apply the CustomerTaxClassification7 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION8
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION8
```
    Use with available fluent helpers to apply the CustomerTaxClassification8 field to query operations.
  - CUSTOMER_TAX_CLASSIFICATION9
```
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION9
```
    Use with available fluent helpers to apply the CustomerTaxClassification9 field to query operations.
  - IS_EU_TRIANGULAR_DEAL
```
public static final BillingDocumentField<Boolean> IS_EU_TRIANGULAR_DEAL
```
    Use with available fluent helpers to apply the IsEUTriangularDeal field to query operations.
  - SD_PRICING_PROCEDURE
```
public static final BillingDocumentField<String> SD_PRICING_PROCEDURE
```
    Use with available fluent helpers to apply the SDPricingProcedure field to query operations.
  - SHIPPING_CONDITION
```
public static final BillingDocumentField<String> SHIPPING_CONDITION
```
    Use with available fluent helpers to apply the ShippingCondition field to query operations.
  - INCOTERMS_VERSION
```
public static final BillingDocumentField<String> INCOTERMS_VERSION
```
    Use with available fluent helpers to apply the IncotermsVersion field to query operations.
  - INCOTERMS_CLASSIFICATION
```
public static final BillingDocumentField<String> INCOTERMS_CLASSIFICATION
```
    Use with available fluent helpers to apply the IncotermsClassification field to query operations.
  - INCOTERMS_TRANSFER_LOCATION
```
public static final BillingDocumentField<String> INCOTERMS_TRANSFER_LOCATION
```
    Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
  - INCOTERMS_LOCATION1
```
public static final BillingDocumentField<String> INCOTERMS_LOCATION1
```
    Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
  - INCOTERMS_LOCATION2
```
public static final BillingDocumentField<String> INCOTERMS_LOCATION2
```
    Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
  - PAYER_PARTY
```
public static final BillingDocumentField<String> PAYER_PARTY
```
    Use with available fluent helpers to apply the PayerParty field to query operations.
  - CONTRACT_ACCOUNT
```
public static final BillingDocumentField<String> CONTRACT_ACCOUNT
```
    Use with available fluent helpers to apply the ContractAccount field to query operations.
  - CUSTOMER_PAYMENT_TERMS
```
public static final BillingDocumentField<String> CUSTOMER_PAYMENT_TERMS
```
    Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
  - PAYMENT_METHOD
```
public static final BillingDocumentField<String> PAYMENT_METHOD
```
    Use with available fluent helpers to apply the PaymentMethod field to query operations.
  - PAYMENT_REFERENCE
```
public static final BillingDocumentField<String> PAYMENT_REFERENCE
```
    Use with available fluent helpers to apply the PaymentReference field to query operations.
  - FIXED_VALUE_DATE
```
public static final BillingDocumentField<LocalDateTime> FIXED_VALUE_DATE
```
    Use with available fluent helpers to apply the FixedValueDate field to query operations.
  - ADDITIONAL_VALUE_DAYS
```
public static final BillingDocumentField<String> ADDITIONAL_VALUE_DAYS
```
    Use with available fluent helpers to apply the AdditionalValueDays field to query operations.
  - SEPA_MANDATE
```
public static final BillingDocumentField<String> SEPA_MANDATE
```
    Use with available fluent helpers to apply the SEPAMandate field to query operations.
  - COMPANY_CODE
```
public static final BillingDocumentField<String> COMPANY_CODE
```
    Use with available fluent helpers to apply the CompanyCode field to query operations.
  - FISCAL_YEAR
```
public static final BillingDocumentField<String> FISCAL_YEAR
```
    Use with available fluent helpers to apply the FiscalYear field to query operations.
  - ACCOUNTING_DOCUMENT
```
public static final BillingDocumentField<String> ACCOUNTING_DOCUMENT
```
    Use with available fluent helpers to apply the AccountingDocument field to query operations.
  - CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
```
public static final BillingDocumentField<String> CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
```
    Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
  - ACCOUNTING_EXCHANGE_RATE_IS_SET
```
public static final BillingDocumentField<Boolean> ACCOUNTING_EXCHANGE_RATE_IS_SET
```
    Use with available fluent helpers to apply the AccountingExchangeRateIsSet field to query operations.
  - ABSLT_ACCOUNTING_EXCHANGE_RATE
```
public static final BillingDocumentField<BigDecimal> ABSLT_ACCOUNTING_EXCHANGE_RATE
```
    Use with available fluent helpers to apply the AbsltAccountingExchangeRate field to query operations.
  - ACCTG_EXCHANGE_RATE_IS_INDRCT_QTAN
```
public static final BillingDocumentField<Boolean> ACCTG_EXCHANGE_RATE_IS_INDRCT_QTAN
```
    Use with available fluent helpers to apply the AcctgExchangeRateIsIndrctQtan field to query operations.
  - EXCHANGE_RATE_DATE
```
public static final BillingDocumentField<LocalDateTime> EXCHANGE_RATE_DATE
```
    Use with available fluent helpers to apply the ExchangeRateDate field to query operations.
  - EXCHANGE_RATE_TYPE
```
public static final BillingDocumentField<String> EXCHANGE_RATE_TYPE
```
    Use with available fluent helpers to apply the ExchangeRateType field to query operations.
  - DOCUMENT_REFERENCE_ID
```
public static final BillingDocumentField<String> DOCUMENT_REFERENCE_ID
```
    Use with available fluent helpers to apply the DocumentReferenceID field to query operations.
  - ASSIGNMENT_REFERENCE
```
public static final BillingDocumentField<String> ASSIGNMENT_REFERENCE
```
    Use with available fluent helpers to apply the AssignmentReference field to query operations.
  - DUNNING_AREA
```
public static final BillingDocumentField<String> DUNNING_AREA
```
    Use with available fluent helpers to apply the DunningArea field to query operations.
  - DUNNING_BLOCKING_REASON
```
public static final BillingDocumentField<String> DUNNING_BLOCKING_REASON
```
    Use with available fluent helpers to apply the DunningBlockingReason field to query operations.
  - DUNNING_KEY
```
public static final BillingDocumentField<String> DUNNING_KEY
```
    Use with available fluent helpers to apply the DunningKey field to query operations.
  - INTERNAL_FINANCIAL_DOCUMENT
```
public static final BillingDocumentField<String> INTERNAL_FINANCIAL_DOCUMENT
```
    Use with available fluent helpers to apply the InternalFinancialDocument field to query operations.
  - IS_RELEVANT_FOR_ACCRUAL
```
public static final BillingDocumentField<Boolean> IS_RELEVANT_FOR_ACCRUAL
```
    Use with available fluent helpers to apply the IsRelevantForAccrual field to query operations.
  - SOLD_TO_PARTY
```
public static final BillingDocumentField<String> SOLD_TO_PARTY
```
    Use with available fluent helpers to apply the SoldToParty field to query operations.
  - PARTNER_COMPANY
```
public static final BillingDocumentField<String> PARTNER_COMPANY
```
    Use with available fluent helpers to apply the PartnerCompany field to query operations.
  - PURCHASE_ORDER_BY_CUSTOMER
```
public static final BillingDocumentField<String> PURCHASE_ORDER_BY_CUSTOMER
```
    Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
  - CUSTOMER_GROUP
```
public static final BillingDocumentField<String> CUSTOMER_GROUP
```
    Use with available fluent helpers to apply the CustomerGroup field to query operations.
  - COUNTRY
```
public static final BillingDocumentField<String> COUNTRY
```
    Use with available fluent helpers to apply the Country field to query operations.
  - CITY_CODE
```
public static final BillingDocumentField<String> CITY_CODE
```
    Use with available fluent helpers to apply the CityCode field to query operations.
  - SALES_DISTRICT
```
public static final BillingDocumentField<String> SALES_DISTRICT
```
    Use with available fluent helpers to apply the SalesDistrict field to query operations.
  - REGION
```
public static final BillingDocumentField<String> REGION
```
    Use with available fluent helpers to apply the Region field to query operations.
  - COUNTY
```
public static final BillingDocumentField<String> COUNTY
```
    Use with available fluent helpers to apply the County field to query operations.
  - CREDIT_CONTROL_AREA
```
public static final BillingDocumentField<String> CREDIT_CONTROL_AREA
```
    Use with available fluent helpers to apply the CreditControlArea field to query operations.
  - CUSTOMER_REBATE_AGREEMENT
```
public static final BillingDocumentField<String> CUSTOMER_REBATE_AGREEMENT
```
    Use with available fluent helpers to apply the CustomerRebateAgreement field to query operations.
  - SALES_DOCUMENT_CONDITION
```
public static final BillingDocumentField<String> SALES_DOCUMENT_CONDITION
```
    Use with available fluent helpers to apply the SalesDocumentCondition field to query operations.
  - OVERALL_SD_PROCESS_STATUS
```
public static final BillingDocumentField<String> OVERALL_SD_PROCESS_STATUS
```
    Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
  - OVERALL_BILLING_STATUS
```
public static final BillingDocumentField<String> OVERALL_BILLING_STATUS
```
    Use with available fluent helpers to apply the OverallBillingStatus field to query operations.
  - ACCOUNTING_POSTING_STATUS
```
public static final BillingDocumentField<String> ACCOUNTING_POSTING_STATUS
```
    Use with available fluent helpers to apply the AccountingPostingStatus field to query operations.
  - ACCOUNTING_TRANSFER_STATUS
```
public static final BillingDocumentField<String> ACCOUNTING_TRANSFER_STATUS
```
    Use with available fluent helpers to apply the AccountingTransferStatus field to query operations.
  - BILLING_ISSUE_TYPE
```
public static final BillingDocumentField<String> BILLING_ISSUE_TYPE
```
    Use with available fluent helpers to apply the BillingIssueType field to query operations.
  - INVOICE_LIST_STATUS
```
public static final BillingDocumentField<String> INVOICE_LIST_STATUS
```
    Use with available fluent helpers to apply the InvoiceListStatus field to query operations.
  - OVRL_ITM_GENERAL_INCOMPLETION_STS
```
public static final BillingDocumentField<String> OVRL_ITM_GENERAL_INCOMPLETION_STS
```
    Use with available fluent helpers to apply the OvrlItmGeneralIncompletionSts field to query operations.
  - OVERALL_PRICING_INCOMPLETION_STS
```
public static final BillingDocumentField<String> OVERALL_PRICING_INCOMPLETION_STS
```
    Use with available fluent helpers to apply the OverallPricingIncompletionSts field to query operations.
  - INVOICE_CLEARING_STATUS
```
public static final BillingDocumentField<String> INVOICE_CLEARING_STATUS
```
    Use with available fluent helpers to apply the InvoiceClearingStatus field to query operations.
  - BILLING_DOCUMENT_LIST_TYPE
```
public static final BillingDocumentField<String> BILLING_DOCUMENT_LIST_TYPE
```
    Use with available fluent helpers to apply the BillingDocumentListType field to query operations.
  - BILLING_DOCUMENT_LIST_DATE
```
public static final BillingDocumentField<LocalDateTime> BILLING_DOCUMENT_LIST_DATE
```
    Use with available fluent helpers to apply the BillingDocumentListDate field to query operations.
  - TO_ITEM
```
public static final BillingDocumentLink<BillingDocumentItem> TO_ITEM
```
    Use with available fluent helpers to apply the to_Item navigation property to query operations.
  - TO_PARTNER
```
public static final BillingDocumentLink<BillingDocumentPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final BillingDocumentLink<BillingDocumentPrcgElmnt> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
  - TO_TEXT
```
public static final BillingDocumentLink<BillingDocumentText> TO_TEXT
```
    Use with available fluent helpers to apply the to_Text navigation property to query operations.
- Constructor Detail
  - BillingDocument
```
public BillingDocument()
```
  - BillingDocument
```
public BillingDocument(@Nullable
                       String billingDocument,
                       @Nullable
                       String sDDocumentCategory,
                       @Nullable
                       String billingDocumentCategory,
                       @Nullable
                       String billingDocumentType,
                       @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
                       Boolean billingDocumentIsCancelled,
                       @Nullable
                       String cancelledBillingDocument,
                       @Nullable
                       String foreignTrade,
                       @Nullable
                       String isExportDelivery,
                       @Nullable
                       String billingDocCombinationCriteria,
                       @Nullable
                       Boolean manualInvoiceMaintIsRelevant,
                       @Nullable
                       Boolean isIntrastatReportingRelevant,
                       @Nullable
                       Boolean isIntrastatReportingExcluded,
                       @Nullable
                       BigDecimal totalNetAmount,
                       @Nullable
                       String transactionCurrency,
                       @Nullable
                       String statisticsCurrency,
                       @Nullable
                       BigDecimal taxAmount,
                       @Nullable
                       BigDecimal totalGrossAmount,
                       @Nullable
                       String customerPriceGroup,
                       @Nullable
                       String priceListType,
                       @Nullable
                       String taxDepartureCountry,
                       @Nullable
                       String vATRegistration,
                       @Nullable
                       String vATRegistrationOrigin,
                       @Nullable
                       String vATRegistrationCountry,
                       @Nullable
                       String hierarchyTypePricing,
                       @Nullable
                       String customerTaxClassification1,
                       @Nullable
                       String customerTaxClassification2,
                       @Nullable
                       String customerTaxClassification3,
                       @Nullable
                       String customerTaxClassification4,
                       @Nullable
                       String customerTaxClassification5,
                       @Nullable
                       String customerTaxClassification6,
                       @Nullable
                       String customerTaxClassification7,
                       @Nullable
                       String customerTaxClassification8,
                       @Nullable
                       String customerTaxClassification9,
                       @Nullable
                       Boolean isEUTriangularDeal,
                       @Nullable
                       String sDPricingProcedure,
                       @Nullable
                       String shippingCondition,
                       @Nullable
                       String incotermsVersion,
                       @Nullable
                       String incotermsClassification,
                       @Nullable
                       String incotermsTransferLocation,
                       @Nullable
                       String incotermsLocation1,
                       @Nullable
                       String incotermsLocation2,
                       @Nullable
                       String payerParty,
                       @Nullable
                       String contractAccount,
                       @Nullable
                       String customerPaymentTerms,
                       @Nullable
                       String paymentMethod,
                       @Nullable
                       String paymentReference,
                       @Nullable
                       LocalDateTime fixedValueDate,
                       @Nullable
                       String additionalValueDays,
                       @Nullable
                       String sEPAMandate,
                       @Nullable
                       String companyCode,
                       @Nullable
                       String fiscalYear,
                       @Nullable
                       String accountingDocument,
                       @Nullable
                       String customerAccountAssignmentGroup,
                       @Nullable
                       Boolean accountingExchangeRateIsSet,
                       @Nullable
                       BigDecimal absltAccountingExchangeRate,
                       @Nullable
                       Boolean acctgExchangeRateIsIndrctQtan,
                       @Nullable
                       LocalDateTime exchangeRateDate,
                       @Nullable
                       String exchangeRateType,
                       @Nullable
                       String documentReferenceID,
                       @Nullable
                       String assignmentReference,
                       @Nullable
                       String dunningArea,
                       @Nullable
                       String dunningBlockingReason,
                       @Nullable
                       String dunningKey,
                       @Nullable
                       String internalFinancialDocument,
                       @Nullable
                       Boolean isRelevantForAccrual,
                       @Nullable
                       String soldToParty,
                       @Nullable
                       String partnerCompany,
                       @Nullable
                       String purchaseOrderByCustomer,
                       @Nullable
                       String customerGroup,
                       @Nullable
                       String country,
                       @Nullable
                       String cityCode,
                       @Nullable
                       String salesDistrict,
                       @Nullable
                       String region,
                       @Nullable
                       String county,
                       @Nullable
                       String creditControlArea,
                       @Nullable
                       String customerRebateAgreement,
                       @Nullable
                       String salesDocumentCondition,
                       @Nullable
                       String overallSDProcessStatus,
                       @Nullable
                       String overallBillingStatus,
                       @Nullable
                       String accountingPostingStatus,
                       @Nullable
                       String accountingTransferStatus,
                       @Nullable
                       String billingIssueType,
                       @Nullable
                       String invoiceListStatus,
                       @Nullable
                       String ovrlItmGeneralIncompletionSts,
                       @Nullable
                       String overallPricingIncompletionSts,
                       @Nullable
                       String invoiceClearingStatus,
                       @Nullable
                       String billingDocumentListType,
                       @Nullable
                       LocalDateTime billingDocumentListDate,
                       List<BillingDocumentItem> toItem,
                       List<BillingDocumentPartner> toPartner,
                       List<BillingDocumentPrcgElmnt> toPricingElement,
                       List<BillingDocumentText> toText)
```
- Method Detail
  - getType
```
@Nonnull
public Class<BillingDocument> getType()
```
    Specified by:
    
    getType in class VdmObject<BillingDocument>
    
    Returns:
    
    The class of this object.
  - setBillingDocument
```
public void setBillingDocument(@Nullable
                               String billingDocument)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: BillingDocument
    
    Parameters:
    
    billingDocument - The number that uniquely identifies the billing document (the invoice, for example).
  - setSDDocumentCategory
```
public void setSDDocumentCategory(@Nullable
                                  String sDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SDDocumentCategory
    
    The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
    
    Parameters:
    
    sDDocumentCategory - A classification for the different types of documents that you can process, for example, quotations, sales orders, deliveries, and invoices.
  - setBillingDocumentCategory
```
public void setBillingDocumentCategory(@Nullable
                                       String billingDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillingDocumentCategory
    
    Parameters:
    
    billingDocumentCategory - Indicates whether the billing document refers to a sales order or a delivery.
  - setBillingDocumentType
```
public void setBillingDocumentType(@Nullable
                                   String billingDocumentType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillingDocumentType
    
    When you process billing documents collectively, you can use the billing type as one of the selection criteria.
    
    Parameters:
    
    billingDocumentType - 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
    
    When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, 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. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. 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 - Date on which billing is processed and posted to Accounting.
  - setBillingDocumentIsCancelled
```
public void setBillingDocumentIsCancelled(@Nullable
                                          Boolean billingDocumentIsCancelled)
```
    Constraints: none
    Original property name from the Odata EDM: BillingDocumentIsCancelled
    
    Parameters:
    
    billingDocumentIsCancelled - Billing document is canceled
  - setCancelledBillingDocument
```
public void setCancelledBillingDocument(@Nullable
                                        String cancelledBillingDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CancelledBillingDocument
    
    Parameters:
    
    cancelledBillingDocument - Number of canceled billing document
  - setForeignTrade
```
public void setForeignTrade(@Nullable
                            String foreignTrade)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ForeignTrade
    
    Parameters:
    
    foreignTrade - Internal number for export data.
  - setIsExportDelivery
```
public void setIsExportDelivery(@Nullable
                                String isExportDelivery)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsExportDelivery
    
    Parameters:
    
    isExportDelivery - Indicates whether the delivery will be exported.
  - setBillingDocCombinationCriteria
```
public void setBillingDocCombinationCriteria(@Nullable
                                             String billingDocCombinationCriteria)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BillingDocCombinationCriteria
    
    Parameters:
    
    billingDocCombinationCriteria - Combination criteria in the billing document
  - setManualInvoiceMaintIsRelevant
```
public void setManualInvoiceMaintIsRelevant(@Nullable
                                            Boolean manualInvoiceMaintIsRelevant)
```
    Constraints: none
    Original property name from the Odata EDM: ManualInvoiceMaintIsRelevant
    
    The system proposes the value from the customer master record. You can change the indicator manually in the sales document.
    
    Parameters:
    
    manualInvoiceMaintIsRelevant - Indicates if the invoices for manual post processing should be printed out.
  - setIsIntrastatReportingRelevant
```
public void setIsIntrastatReportingRelevant(@Nullable
                                            Boolean isIntrastatReportingRelevant)
```
    Constraints: none
    Original property name from the Odata EDM: IsIntrastatReportingRelevant
    
    Parameters:
    
    isIntrastatReportingRelevant - Relevant for Intrastat Reporting
  - setIsIntrastatReportingExcluded
```
public void setIsIntrastatReportingExcluded(@Nullable
                                            Boolean isIntrastatReportingExcluded)
```
    Constraints: none
    Original property name from the Odata EDM: IsIntrastatReportingExcluded
    
    Parameters:
    
    isIntrastatReportingExcluded - Exclude from Intrastat Reporting
  - 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).
  - setStatisticsCurrency
```
public void setStatisticsCurrency(@Nullable
                                  String statisticsCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: StatisticsCurrency
    
    Parameters:
    
    statisticsCurrency - Statistics Currency
  - setTaxAmount
```
public void setTaxAmount(@Nullable
                         BigDecimal taxAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: TaxAmount
    
    Parameters:
    
    taxAmount - 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.
  - setCustomerPriceGroup
```
public void setCustomerPriceGroup(@Nullable
                                  String customerPriceGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerPriceGroup
    
    You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.
    
    Parameters:
    
    customerPriceGroup - A grouping of customers who share the same pricing requirements.
  - setPriceListType
```
public void setPriceListType(@Nullable
                             String priceListType)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: PriceListType
    
    You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.
    
    Parameters:
    
    priceListType - Identifies a price list or other condition type (for example, a surcharge or discount).
  - 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.
  - setVATRegistration
```
public void setVATRegistration(@Nullable
                               String vATRegistration)
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: VATRegistration
    
    The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.
    
    Parameters:
    
    vATRegistration - VAT registration number (VAT reg.no.) of the customer, vendor or your company code.
  - setVATRegistrationOrigin
```
public void setVATRegistrationOrigin(@Nullable
                                     String vATRegistrationOrigin)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: VATRegistrationOrigin
    
    Parameters:
    
    vATRegistrationOrigin - Origin of Sales Tax ID Number
  - setVATRegistrationCountry
```
public void setVATRegistrationCountry(@Nullable
                                      String vATRegistrationCountry)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: VATRegistrationCountry
    
    This key is used to check country-specific entries such as the length of the zip code or bank account number.
    
    Parameters:
    
    vATRegistrationCountry - Specifies the key for the country of the VAT registration number.
  - setHierarchyTypePricing
```
public void setHierarchyTypePricing(@Nullable
                                    String hierarchyTypePricing)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: HierarchyTypePricing
    
    Parameters:
    
    hierarchyTypePricing - Hierarchy type for pricing
  - setCustomerTaxClassification1
```
public void setCustomerTaxClassification1(@Nullable
                                          String customerTaxClassification1)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification1
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification1 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification2
```
public void setCustomerTaxClassification2(@Nullable
                                          String customerTaxClassification2)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification2
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification2 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification3
```
public void setCustomerTaxClassification3(@Nullable
                                          String customerTaxClassification3)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification3
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification3 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification4
```
public void setCustomerTaxClassification4(@Nullable
                                          String customerTaxClassification4)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification4
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification4 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification5
```
public void setCustomerTaxClassification5(@Nullable
                                          String customerTaxClassification5)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification5
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification5 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification6
```
public void setCustomerTaxClassification6(@Nullable
                                          String customerTaxClassification6)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification6
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification6 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification7
```
public void setCustomerTaxClassification7(@Nullable
                                          String customerTaxClassification7)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification7
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification7 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification8
```
public void setCustomerTaxClassification8(@Nullable
                                          String customerTaxClassification8)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification8
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification8 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setCustomerTaxClassification9
```
public void setCustomerTaxClassification9(@Nullable
                                          String customerTaxClassification9)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification9
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Parameters:
    
    customerTaxClassification9 - Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - setIsEUTriangularDeal
```
public void setIsEUTriangularDeal(@Nullable
                                  Boolean isEUTriangularDeal)
```
    Constraints: none
    Original property name from the Odata EDM: IsEUTriangularDeal
    
    Parameters:
    
    isEUTriangularDeal - If you select this field, the system includes this transaction in the EC sales list under the triangular deal section.
  - setSDPricingProcedure
```
public void setSDPricingProcedure(@Nullable
                                  String sDPricingProcedure)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SDPricingProcedure
    
    Parameters:
    
    sDPricingProcedure - Determines which condition types can be used in a document and in which sequence they appear.
  - setShippingCondition
```
public void setShippingCondition(@Nullable
                                 String shippingCondition)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingCondition
    
    You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
    
    Parameters:
    
    shippingCondition - General shipping strategy for the delivery of goods from the vendor to the customer.
  - 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:
  - 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.
  - setPaymentReference
```
public void setPaymentReference(@Nullable
                                String paymentReference)
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: PaymentReference
    
    For vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference. In automatic payment transactions, the payment reference can be passed on again to the payee.When an outgoing payment is made, the payment reference you specify is passed on to the relevant financial institute and from there to the payee.When you are processing your account statement, you can use the payment reference to determine which items you have paid and then clear them.Payment reference numbers are often used in Finland, Norway, and Sweden. These countries also have rules for the structure of the payment reference. Check digit procedures are used to check that these rules are followed.DME Finland: The number '4477' has a check digit of '8' and should be defined as the character string '44778'.DME Norway: The number '12345678' has the check digit '2' when using the Modulo-10 method, and check digit '5' when using the Modulo-11 method. Therefore, 123456782 or 123456785 are permitted as payment references.DME Sweden: The number '1234567890' has the check digit '3' and should be defined as the character string '12345678903'. The Modulo procedure used is a form of Modulo-10 with the key '1212121'.
    
    Parameters:
    
    paymentReference - The payment reference contains a key for customer line items which is passed on to the customer in the invoice. The customer should refer to the payment reference when making the payment.
  - setFixedValueDate
```
public void setFixedValueDate(@Nullable
                              LocalDateTime fixedValueDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: FixedValueDate
    
    If you enter a date in this field, you cannot enter a value in the additional value days field.
    
    Parameters:
    
    fixedValueDate - The date on which the terms of payment related to the sales document become effective.
  - setAdditionalValueDays
```
public void setAdditionalValueDays(@Nullable
                                   String additionalValueDays)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: AdditionalValueDays
    
    If you enter a value in this field, you cannot enter a date in the fixed value date field.
    
    Parameters:
    
    additionalValueDays - The number of days between the billing date and the date on which the terms of payment for the sales document become effective.
  - 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.
  - setFiscalYear
```
public void setFiscalYear(@Nullable
                          String fiscalYear)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: FiscalYear
    
    Parameters:
    
    fiscalYear - Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The fiscal year can be the same as the calendar year, but does not have to be.
  - setAccountingDocument
```
public void setAccountingDocument(@Nullable
                                  String accountingDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: AccountingDocument
    
    The document number is unique per company code and fiscal year. When entering an accounting document, you can specify the number manually or it can be determined by the system from a pre-defined area (number range).The relevant area of the document numbers (number range) is determined in each company code per document type.
    
    Parameters:
    
    accountingDocument - The document number is the key the system uses to access the accounting document.
  - setCustomerAccountAssignmentGroup
```
public void setCustomerAccountAssignmentGroup(@Nullable
                                              String customerAccountAssignmentGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerAccountAssignmentGroup
    
    The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
    
    Parameters:
    
    customerAccountAssignmentGroup - The account assignment group to which the system automatically posts the sales document.
  - setAccountingExchangeRateIsSet
```
public void setAccountingExchangeRateIsSet(@Nullable
                                           Boolean accountingExchangeRateIsSet)
```
    Constraints: none
    Original property name from the Odata EDM: AccountingExchangeRateIsSet
    
    The system can propose a value. You can change the value manually in the sales document. If you are allowed to change the exchange rate during billing, the system recalculates prices using the most recent exchange rate.
    
    Parameters:
    
    accountingExchangeRateIsSet - Indicates whether the foreign currency exchange rate that is applied to the sales document is fixed or whether it can be changed during billing.
  - setAbsltAccountingExchangeRate
```
public void setAbsltAccountingExchangeRate(@Nullable
                                           BigDecimal absltAccountingExchangeRate)
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: AbsltAccountingExchangeRate
    
    Parameters:
    
    absltAccountingExchangeRate - Exchange rate from document currency into accounting currency.
  - setAcctgExchangeRateIsIndrctQtan
```
public void setAcctgExchangeRateIsIndrctQtan(@Nullable
                                             Boolean acctgExchangeRateIsIndrctQtan)
```
    Constraints: none
    Original property name from the Odata EDM: AcctgExchangeRateIsIndrctQtan
    
    Parameters:
    
    acctgExchangeRateIsIndrctQtan - Accounting exchange rate quotation is indirect
  - setExchangeRateDate
```
public void setExchangeRateDate(@Nullable
                                LocalDateTime exchangeRateDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ExchangeRateDate
    
    You do not need to enter a date unless the date in question is not the same as the document entry date.
    
    Parameters:
    
    exchangeRateDate - Translation date for determining the exchange rate which is to be used for translation. The exchange rates are stored in the system.
  - setExchangeRateType
```
public void setExchangeRateType(@Nullable
                                String exchangeRateType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ExchangeRateType
    
    You enter the exchange rate type to store different exchange rates.You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
    
    Parameters:
    
    exchangeRateType - Key representing a type of exchange rate in the system.
  - setDocumentReferenceID
```
public void setDocumentReferenceID(@Nullable
                                   String documentReferenceID)
```
    Constraints: Not nullable, Maximum length: 16
    Original property name from the Odata EDM: DocumentReferenceID
    
    The reference document number serves as a search criterion when displaying or changing documents. In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document.
    
    Parameters:
    
    documentReferenceID - The reference document number contains the document number with the business partner
  - setAssignmentReference
```
public void setAssignmentReference(@Nullable
                                   String assignmentReference)
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: AssignmentReference
    
    The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document.
    
    Parameters:
    
    assignmentReference - The allocation is additional information in the customer line item of the journal entry.
  - setDunningArea
```
public void setDunningArea(@Nullable
                           String dunningArea)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DunningArea
    
    If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
    
    Parameters:
    
    dunningArea - The dunning area represents an organizational entity that is responsible for dunning. The dunning areas represent a sub-structure of the company codes.
  - setDunningBlockingReason
```
public void setDunningBlockingReason(@Nullable
                                     String dunningBlockingReason)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DunningBlockingReason
    
    Parameters:
    
    dunningBlockingReason - Key which reflects the reason for a dunning block indicator.
  - setDunningKey
```
public void setDunningKey(@Nullable
                          String dunningKey)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DunningKey
    
    You define the contents of the text line in Customizing for the dunning key.If you enter a key in an item, then it can only reach the maximum dunning level defined for this key. Therefore it is possible that an item can contain one dunning notice at the most, although several dunning levels are defined in the dunning procedure.
    
    Parameters:
    
    dunningKey - Determines that the item can only be dunned with restrictions or is to be displayed with an extra text line on the dunning notice. The keys are freely-definable.
  - setInternalFinancialDocument
```
public void setInternalFinancialDocument(@Nullable
                                         String internalFinancialDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InternalFinancialDocument
    
    You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance.
    
    Parameters:
    
    internalFinancialDocument - Internal number of a financial document that is mapped to a trade finance transaction. The number is assigned by the system.
  - setIsRelevantForAccrual
```
public void setIsRelevantForAccrual(@Nullable
                                    Boolean isRelevantForAccrual)
```
    Constraints: none
    Original property name from the Odata EDM: IsRelevantForAccrual
    
    Parameters:
    
    isRelevantForAccrual - Is relevant for accrual
  - 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.
  - setPartnerCompany
```
public void setPartnerCompany(@Nullable
                              String partnerCompany)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: PartnerCompany
    
    Parameters:
    
    partnerCompany - Company ID standard for the whole group.
  - 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).
  - setCustomerGroup
```
public void setCustomerGroup(@Nullable
                             String customerGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerGroup
    
    Parameters:
    
    customerGroup - Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.
  - setCountry
```
public void setCountry(@Nullable
                       String country)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: Country
    
    As a general rule, it is best to use the existing international standards for identifying vehicles from different countries/regions (for example: USA = United States, I = Italy, and so on).The system uses the country/region key identifier to:Help determine the appropriate taxes during pricingDetermine important country/region-specific standards (the length of postal codes and bank account numbers, for example)When you process billing documents collectively, you can use the destination country as one of the selection criteria.
    
    Parameters:
    
    country - Identifies the destination country/region in which the goods are delivered to the customer.
  - setCityCode
```
public void setCityCode(@Nullable
                        String cityCode)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CityCode
    
    Currently the key is used only in the USA for handling city tax.
    
    Parameters:
    
    cityCode - This key is used for classifying cities from a tax point of view. This is a finer sub-division than the county code.
  - setSalesDistrict
```
public void setSalesDistrict(@Nullable
                             String salesDistrict)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesDistrict
    
    Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
    
    Parameters:
    
    salesDistrict - A geographical sales district or region.
  - setRegion
```
public void setRegion(@Nullable
                      String region)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: Region
    
    The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State
    
    Parameters:
    
    region - In some countries, the region forms part of the address. The meaning depends on the country.
  - setCounty
```
public void setCounty(@Nullable
                      String county)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: County
    
    Currently the county code is used in the USA for handling county tax, and in Denmark to define the municipality number of the employee's first place of residence.
    
    Parameters:
    
    county - Key used to classify cities from the point of view of taxes.
  - setCreditControlArea
```
public void setCreditControlArea(@Nullable
                                 String creditControlArea)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CreditControlArea
    
    You can also enter the credit control area separately for each posting, if this was marked in the appropriate company code.When entering an order, the credit control area can also be determined from the business area and the sales area segement of the payer's master record or using a user exit.It follows that company codes and credit control areas are not linked.The only thing that you define in the company code table is the default credit control area. This is used either for payments on account to credit these payments, or where you did not enter a credit control area or the system could not determine one.There is also an allocation table of permitted credit control areas per company code which is used to check entries only.
    
    Parameters:
    
    creditControlArea - The credit control area is an organizational entity which grants and monitors a credit limit for customers. A credit control area can include one or more company codes.
  - setCustomerRebateAgreement
```
public void setCustomerRebateAgreement(@Nullable
                                       String customerRebateAgreement)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CustomerRebateAgreement
    
    A rebate agreement is an agreement between a customer and a supplier. On the basis of the customer's sales volume during a specified period, the supplier grants the customer a special rebate. A general rebate agreement can consist of numerous individual agreements (condition records) that are based on different factors. For example, an individualagreement may be based on a combination of customer and material or a combination of customer and rebate group, and so on.
    
    Parameters:
    
    customerRebateAgreement - The number that uniquely identifies a rebate agreement.
  - setSalesDocumentCondition
```
public void setSalesDocumentCondition(@Nullable
                                      String salesDocumentCondition)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesDocumentCondition
    
    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:
    
    salesDocumentCondition - The internal number under which the system saves conditions that apply to a sales order, for example.
  - setOverallSDProcessStatus
```
public void setOverallSDProcessStatus(@Nullable
                                      String overallSDProcessStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDProcessStatus
    
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Parameters:
    
    overallSDProcessStatus - The processing status of the entire sales document.
  - setOverallBillingStatus
```
public void setOverallBillingStatus(@Nullable
                                    String overallBillingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallBillingStatus
    
    Parameters:
    
    overallBillingStatus - SD Billing Status
  - setAccountingPostingStatus
```
public void setAccountingPostingStatus(@Nullable
                                       String accountingPostingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: AccountingPostingStatus
    
    The status message tells you whether the billing document must be posted to accounting, and, if so, whether the posting has taken place.
    
    Parameters:
    
    accountingPostingStatus - The accounting status of the billing document.
  - setAccountingTransferStatus
```
public void setAccountingTransferStatus(@Nullable
                                        String accountingTransferStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: AccountingTransferStatus
    
    The status message tells you whether the system has successfully posted the document to accounting or whether posting is blocked because a posting block is set for the billing type.
    
    Parameters:
    
    accountingTransferStatus - The accounting status of the billing document (for example, an invoice).
  - 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
  - setInvoiceListStatus
```
public void setInvoiceListStatus(@Nullable
                                 String invoiceListStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InvoiceListStatus
    
    Parameters:
    
    invoiceListStatus - Invoice list status of billing document
  - setOvrlItmGeneralIncompletionSts
```
public void setOvrlItmGeneralIncompletionSts(@Nullable
                                             String ovrlItmGeneralIncompletionSts)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OvrlItmGeneralIncompletionSts
    
    The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
    
    Parameters:
    
    ovrlItmGeneralIncompletionSts - The incompletion status of general item information in the sales document. General item information includes business, shipping, and billing data.
  - 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)
  - setInvoiceClearingStatus
```
public void setInvoiceClearingStatus(@Nullable
                                     String invoiceClearingStatus)
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InvoiceClearingStatus
    
    Parameters:
    
    invoiceClearingStatus - Clearing Status of Billing Document
  - setBillingDocumentListType
```
public void setBillingDocumentListType(@Nullable
                                       String billingDocumentListType)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillingDocumentListType
    
    Parameters:
    
    billingDocumentListType - Classification that distinguishes between invoice list types that require different processing by the system.
  - setBillingDocumentListDate
```
public void setBillingDocumentListDate(@Nullable
                                       LocalDateTime billingDocumentListDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BillingDocumentListDate
    
    The system automatically proposes the next valid date defined in the customer's factory calendar. You can change the date manually in the header of the invoice list.
    
    Parameters:
    
    billingDocumentListDate - Specifies the billing date of the invoice list.
  - 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<BillingDocument>
    
    Returns:
    
    EDMX name of the entity collection identifier.
  - getKey
```
@Nonnull
protected Map<String,Object> getKey()
```
    Overrides:
    
    getKey in class VdmObject<BillingDocument>
    
    Returns:
    
    The compound key of this object.
  - toMapOfFields
```
@Nonnull
protected Map<String,Object> toMapOfFields()
```
    Overrides:
    
    toMapOfFields in class VdmObject<BillingDocument>
  - fromMap
```
protected void fromMap(Map<String,Object> inputValues)
```
    Overrides:
    
    fromMap in class VdmObject<BillingDocument>
  - field
```
@Nonnull
public static <T> BillingDocumentField<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> BillingDocumentField<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<BillingDocument>
    
    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<BillingDocument>
  - 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<BillingDocument>
    
    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<BillingDocument>
    
    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<BillingDocument>
  - fetchItem
```
@Nonnull
public List<BillingDocumentItem> fetchItem()
                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocumentItem 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 BillingDocumentItem 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<BillingDocumentItem> getItemOrFetch()
                                                  throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocumentItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried BillingDocument 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 BillingDocumentItem 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<BillingDocumentItem>> getItemIfPresent()
```
    Retrieval of associated BillingDocumentItem entities (one to many). This corresponds to the OData navigation property to_Item.
    If the navigation property for an entity BillingDocument 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 BillingDocumentItem entities. If not, an Option with result state empty is returned.
  - setItem
```
public void setItem(@Nonnull
                    List<BillingDocumentItem> value)
```
    Overwrites the list of associated BillingDocumentItem entities for the loaded navigation property to_Item.
    If the navigation property to_Item of a queried BillingDocument 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 BillingDocumentItem entities.
  - addItem
```
public void addItem(BillingDocumentItem... entity)
```
    Adds elements to the list of associated BillingDocumentItem entities. This corresponds to the OData navigation property to_Item.
    If the navigation property to_Item of a queried BillingDocument 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 BillingDocumentItem entities.
  - fetchPartner
```
@Nonnull
public List<BillingDocumentPartner> fetchPartner()
                                                   throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocumentPartner 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 BillingDocumentPartner 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<BillingDocumentPartner> getPartnerOrFetch()
                                                        throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocumentPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried BillingDocument 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 BillingDocumentPartner 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<BillingDocumentPartner>> getPartnerIfPresent()
```
    Retrieval of associated BillingDocumentPartner entities (one to many). This corresponds to the OData navigation property to_Partner.
    If the navigation property for an entity BillingDocument 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 BillingDocumentPartner entities. If not, an Option with result state empty is returned.
  - setPartner
```
public void setPartner(@Nonnull
                       List<BillingDocumentPartner> value)
```
    Overwrites the list of associated BillingDocumentPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried BillingDocument 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 BillingDocumentPartner entities.
  - addPartner
```
public void addPartner(BillingDocumentPartner... entity)
```
    Adds elements to the list of associated BillingDocumentPartner entities. This corresponds to the OData navigation property to_Partner.
    If the navigation property to_Partner of a queried BillingDocument 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 BillingDocumentPartner entities.
  - fetchPricingElement
```
@Nonnull
public List<BillingDocumentPrcgElmnt> fetchPricingElement()
                                                            throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocumentPrcgElmnt 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 BillingDocumentPrcgElmnt 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<BillingDocumentPrcgElmnt> getPricingElementOrFetch()
                                                                 throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocumentPrcgElmnt entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried BillingDocument 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 BillingDocumentPrcgElmnt 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<BillingDocumentPrcgElmnt>> getPricingElementIfPresent()
```
    Retrieval of associated BillingDocumentPrcgElmnt entities (one to many). This corresponds to the OData navigation property to_PricingElement.
    If the navigation property for an entity BillingDocument 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 BillingDocumentPrcgElmnt entities. If not, an Option with result state empty is returned.
  - setPricingElement
```
public void setPricingElement(@Nonnull
                              List<BillingDocumentPrcgElmnt> value)
```
    Overwrites the list of associated BillingDocumentPrcgElmnt entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried BillingDocument 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 BillingDocumentPrcgElmnt entities.
  - addPricingElement
```
public void addPricingElement(BillingDocumentPrcgElmnt... entity)
```
    Adds elements to the list of associated BillingDocumentPrcgElmnt entities. This corresponds to the OData navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried BillingDocument 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 BillingDocumentPrcgElmnt entities.
  - fetchText
```
@Nonnull
public List<BillingDocumentText> fetchText()
                                             throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocumentText entities (one to many) associated with this entity. This corresponds to the OData navigation property to_Text.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    List containing one or more associated BillingDocumentText 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.
  - getTextOrFetch
```
@Nonnull
public List<BillingDocumentText> getTextOrFetch()
                                                  throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocumentText entities (one to many). This corresponds to the OData navigation property to_Text.
    If the navigation property to_Text of a queried BillingDocument 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 BillingDocumentText 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.
  - getTextIfPresent
```
@Nonnull
public io.vavr.control.Option<List<BillingDocumentText>> getTextIfPresent()
```
    Retrieval of associated BillingDocumentText entities (one to many). This corresponds to the OData navigation property to_Text.
    If the navigation property for an entity BillingDocument 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_Text is already loaded, the result will contain the BillingDocumentText entities. If not, an Option with result state empty is returned.
  - setText
```
public void setText(@Nonnull
                    List<BillingDocumentText> value)
```
    Overwrites the list of associated BillingDocumentText entities for the loaded navigation property to_Text.
    If the navigation property to_Text of a queried BillingDocument 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 BillingDocumentText entities.
  - addText
```
public void addText(BillingDocumentText... entity)
```
    Adds elements to the list of associated BillingDocumentText entities. This corresponds to the OData navigation property to_Text.
    If the navigation property to_Text of a queried BillingDocument 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 BillingDocumentText entities.
  - builder
```
public static BillingDocument.BillingDocumentBuilder builder()
```
  - getBillingDocument
```
@Nullable
public String getBillingDocument()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: BillingDocument
    
    Returns:
    
    The number that uniquely identifies the billing document (the invoice, for example).
  - getSDDocumentCategory
```
@Nullable
public String getSDDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: SDDocumentCategory
    
    The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
    
    Returns:
    
    A classification for the different types of documents that you can process, for example, quotations, sales orders, deliveries, and invoices.
  - getBillingDocumentCategory
```
@Nullable
public String getBillingDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillingDocumentCategory
    
    Returns:
    
    Indicates whether the billing document refers to a sales order or a delivery.
  - getBillingDocumentType
```
@Nullable
public String getBillingDocumentType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillingDocumentType
    
    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
    
    When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, 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. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. 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:
    
    Date on which billing is processed and posted to Accounting.
  - getBillingDocumentIsCancelled
```
@Nullable
public Boolean getBillingDocumentIsCancelled()
```
    Constraints: none
    Original property name from the Odata EDM: BillingDocumentIsCancelled
    
    Returns:
    
    Billing document is canceled
  - getCancelledBillingDocument
```
@Nullable
public String getCancelledBillingDocument()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CancelledBillingDocument
    
    Returns:
    
    Number of canceled billing document
  - getForeignTrade
```
@Nullable
public String getForeignTrade()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ForeignTrade
    
    Returns:
    
    Internal number for export data.
  - getIsExportDelivery
```
@Nullable
public String getIsExportDelivery()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: IsExportDelivery
    
    Returns:
    
    Indicates whether the delivery will be exported.
  - getBillingDocCombinationCriteria
```
@Nullable
public String getBillingDocCombinationCriteria()
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BillingDocCombinationCriteria
    
    Returns:
    
    Combination criteria in the billing document
  - getManualInvoiceMaintIsRelevant
```
@Nullable
public Boolean getManualInvoiceMaintIsRelevant()
```
    Constraints: none
    Original property name from the Odata EDM: ManualInvoiceMaintIsRelevant
    
    The system proposes the value from the customer master record. You can change the indicator manually in the sales document.
    
    Returns:
    
    Indicates if the invoices for manual post processing should be printed out.
  - getIsIntrastatReportingRelevant
```
@Nullable
public Boolean getIsIntrastatReportingRelevant()
```
    Constraints: none
    Original property name from the Odata EDM: IsIntrastatReportingRelevant
    
    Returns:
    
    Relevant for Intrastat Reporting
  - getIsIntrastatReportingExcluded
```
@Nullable
public Boolean getIsIntrastatReportingExcluded()
```
    Constraints: none
    Original property name from the Odata EDM: IsIntrastatReportingExcluded
    
    Returns:
    
    Exclude from Intrastat Reporting
  - 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).
  - getStatisticsCurrency
```
@Nullable
public String getStatisticsCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: StatisticsCurrency
    
    Returns:
    
    Statistics Currency
  - getTaxAmount
```
@Nullable
public BigDecimal getTaxAmount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: TaxAmount
    
    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.
  - getCustomerPriceGroup
```
@Nullable
public String getCustomerPriceGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerPriceGroup
    
    You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.
    
    Returns:
    
    A grouping of customers who share the same pricing requirements.
  - getPriceListType
```
@Nullable
public String getPriceListType()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: PriceListType
    
    You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.
    
    Returns:
    
    Identifies a price list or other condition type (for example, a surcharge or discount).
  - 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.
  - getVATRegistration
```
@Nullable
public String getVATRegistration()
```
    Constraints: Not nullable, Maximum length: 20
    Original property name from the Odata EDM: VATRegistration
    
    The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.
    
    Returns:
    
    VAT registration number (VAT reg.no.) of the customer, vendor or your company code.
  - getVATRegistrationOrigin
```
@Nullable
public String getVATRegistrationOrigin()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: VATRegistrationOrigin
    
    Returns:
    
    Origin of Sales Tax ID Number
  - getVATRegistrationCountry
```
@Nullable
public String getVATRegistrationCountry()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: VATRegistrationCountry
    
    This key is used to check country-specific entries such as the length of the zip code or bank account number.
    
    Returns:
    
    Specifies the key for the country of the VAT registration number.
  - getHierarchyTypePricing
```
@Nullable
public String getHierarchyTypePricing()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: HierarchyTypePricing
    
    Returns:
    
    Hierarchy type for pricing
  - getCustomerTaxClassification1
```
@Nullable
public String getCustomerTaxClassification1()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification1
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification2
```
@Nullable
public String getCustomerTaxClassification2()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification2
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification3
```
@Nullable
public String getCustomerTaxClassification3()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification3
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification4
```
@Nullable
public String getCustomerTaxClassification4()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification4
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification5
```
@Nullable
public String getCustomerTaxClassification5()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification5
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification6
```
@Nullable
public String getCustomerTaxClassification6()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification6
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification7
```
@Nullable
public String getCustomerTaxClassification7()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification7
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification8
```
@Nullable
public String getCustomerTaxClassification8()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification8
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getCustomerTaxClassification9
```
@Nullable
public String getCustomerTaxClassification9()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: CustomerTaxClassification9
    
    The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes).
  - getIsEUTriangularDeal
```
@Nullable
public Boolean getIsEUTriangularDeal()
```
    Constraints: none
    Original property name from the Odata EDM: IsEUTriangularDeal
    
    Returns:
    
    If you select this field, the system includes this transaction in the EC sales list under the triangular deal section.
  - getSDPricingProcedure
```
@Nullable
public String getSDPricingProcedure()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SDPricingProcedure
    
    Returns:
    
    Determines which condition types can be used in a document and in which sequence they appear.
  - getShippingCondition
```
@Nullable
public String getShippingCondition()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: ShippingCondition
    
    You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
    
    Returns:
    
    General shipping strategy for the delivery of goods from the vendor to the customer.
  - 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:
  - 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.
  - getPaymentReference
```
@Nullable
public String getPaymentReference()
```
    Constraints: Not nullable, Maximum length: 30
    Original property name from the Odata EDM: PaymentReference
    
    For vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference. In automatic payment transactions, the payment reference can be passed on again to the payee.When an outgoing payment is made, the payment reference you specify is passed on to the relevant financial institute and from there to the payee.When you are processing your account statement, you can use the payment reference to determine which items you have paid and then clear them.Payment reference numbers are often used in Finland, Norway, and Sweden. These countries also have rules for the structure of the payment reference. Check digit procedures are used to check that these rules are followed.DME Finland: The number '4477' has a check digit of '8' and should be defined as the character string '44778'.DME Norway: The number '12345678' has the check digit '2' when using the Modulo-10 method, and check digit '5' when using the Modulo-11 method. Therefore, 123456782 or 123456785 are permitted as payment references.DME Sweden: The number '1234567890' has the check digit '3' and should be defined as the character string '12345678903'. The Modulo procedure used is a form of Modulo-10 with the key '1212121'.
    
    Returns:
    
    The payment reference contains a key for customer line items which is passed on to the customer in the invoice. The customer should refer to the payment reference when making the payment.
  - getFixedValueDate
```
@Nullable
public LocalDateTime getFixedValueDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: FixedValueDate
    
    If you enter a date in this field, you cannot enter a value in the additional value days field.
    
    Returns:
    
    The date on which the terms of payment related to the sales document become effective.
  - getAdditionalValueDays
```
@Nullable
public String getAdditionalValueDays()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: AdditionalValueDays
    
    If you enter a value in this field, you cannot enter a date in the fixed value date field.
    
    Returns:
    
    The number of days between the billing date and the date on which the terms of payment for the sales document become effective.
  - 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.
  - getFiscalYear
```
@Nullable
public String getFiscalYear()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: FiscalYear
    
    Returns:
    
    Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The fiscal year can be the same as the calendar year, but does not have to be.
  - getAccountingDocument
```
@Nullable
public String getAccountingDocument()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: AccountingDocument
    
    The document number is unique per company code and fiscal year. When entering an accounting document, you can specify the number manually or it can be determined by the system from a pre-defined area (number range).The relevant area of the document numbers (number range) is determined in each company code per document type.
    
    Returns:
    
    The document number is the key the system uses to access the accounting document.
  - getCustomerAccountAssignmentGroup
```
@Nullable
public String getCustomerAccountAssignmentGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerAccountAssignmentGroup
    
    The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
    
    Returns:
    
    The account assignment group to which the system automatically posts the sales document.
  - getAccountingExchangeRateIsSet
```
@Nullable
public Boolean getAccountingExchangeRateIsSet()
```
    Constraints: none
    Original property name from the Odata EDM: AccountingExchangeRateIsSet
    
    The system can propose a value. You can change the value manually in the sales document. If you are allowed to change the exchange rate during billing, the system recalculates prices using the most recent exchange rate.
    
    Returns:
    
    Indicates whether the foreign currency exchange rate that is applied to the sales document is fixed or whether it can be changed during billing.
  - getAbsltAccountingExchangeRate
```
@Nullable
public BigDecimal getAbsltAccountingExchangeRate()
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: AbsltAccountingExchangeRate
    
    Returns:
    
    Exchange rate from document currency into accounting currency.
  - getAcctgExchangeRateIsIndrctQtan
```
@Nullable
public Boolean getAcctgExchangeRateIsIndrctQtan()
```
    Constraints: none
    Original property name from the Odata EDM: AcctgExchangeRateIsIndrctQtan
    
    Returns:
    
    Accounting exchange rate quotation is indirect
  - getExchangeRateDate
```
@Nullable
public LocalDateTime getExchangeRateDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: ExchangeRateDate
    
    You do not need to enter a date unless the date in question is not the same as the document entry date.
    
    Returns:
    
    Translation date for determining the exchange rate which is to be used for translation. The exchange rates are stored in the system.
  - getExchangeRateType
```
@Nullable
public String getExchangeRateType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: ExchangeRateType
    
    You enter the exchange rate type to store different exchange rates.You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
    
    Returns:
    
    Key representing a type of exchange rate in the system.
  - getDocumentReferenceID
```
@Nullable
public String getDocumentReferenceID()
```
    Constraints: Not nullable, Maximum length: 16
    Original property name from the Odata EDM: DocumentReferenceID
    
    The reference document number serves as a search criterion when displaying or changing documents. In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document.
    
    Returns:
    
    The reference document number contains the document number with the business partner
  - getAssignmentReference
```
@Nullable
public String getAssignmentReference()
```
    Constraints: Not nullable, Maximum length: 18
    Original property name from the Odata EDM: AssignmentReference
    
    The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document.
    
    Returns:
    
    The allocation is additional information in the customer line item of the journal entry.
  - getDunningArea
```
@Nullable
public String getDunningArea()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: DunningArea
    
    If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
    
    Returns:
    
    The dunning area represents an organizational entity that is responsible for dunning. The dunning areas represent a sub-structure of the company codes.
  - getDunningBlockingReason
```
@Nullable
public String getDunningBlockingReason()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DunningBlockingReason
    
    Returns:
    
    Key which reflects the reason for a dunning block indicator.
  - getDunningKey
```
@Nullable
public String getDunningKey()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: DunningKey
    
    You define the contents of the text line in Customizing for the dunning key.If you enter a key in an item, then it can only reach the maximum dunning level defined for this key. Therefore it is possible that an item can contain one dunning notice at the most, although several dunning levels are defined in the dunning procedure.
    
    Returns:
    
    Determines that the item can only be dunned with restrictions or is to be displayed with an extra text line on the dunning notice. The keys are freely-definable.
  - getInternalFinancialDocument
```
@Nullable
public String getInternalFinancialDocument()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: InternalFinancialDocument
    
    You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance.
    
    Returns:
    
    Internal number of a financial document that is mapped to a trade finance transaction. The number is assigned by the system.
  - getIsRelevantForAccrual
```
@Nullable
public Boolean getIsRelevantForAccrual()
```
    Constraints: none
    Original property name from the Odata EDM: IsRelevantForAccrual
    
    Returns:
    
    Is relevant for accrual
  - 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.
  - getPartnerCompany
```
@Nullable
public String getPartnerCompany()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: PartnerCompany
    
    Returns:
    
    Company ID standard for the whole group.
  - 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).
  - getCustomerGroup
```
@Nullable
public String getCustomerGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: CustomerGroup
    
    Returns:
    
    Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.
  - getCountry
```
@Nullable
public String getCountry()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: Country
    
    As a general rule, it is best to use the existing international standards for identifying vehicles from different countries/regions (for example: USA = United States, I = Italy, and so on).The system uses the country/region key identifier to:Help determine the appropriate taxes during pricingDetermine important country/region-specific standards (the length of postal codes and bank account numbers, for example)When you process billing documents collectively, you can use the destination country as one of the selection criteria.
    
    Returns:
    
    Identifies the destination country/region in which the goods are delivered to the customer.
  - getCityCode
```
@Nullable
public String getCityCode()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CityCode
    
    Currently the key is used only in the USA for handling city tax.
    
    Returns:
    
    This key is used for classifying cities from a tax point of view. This is a finer sub-division than the county code.
  - getSalesDistrict
```
@Nullable
public String getSalesDistrict()
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: SalesDistrict
    
    Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
    
    Returns:
    
    A geographical sales district or region.
  - getRegion
```
@Nullable
public String getRegion()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: Region
    
    The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State
    
    Returns:
    
    In some countries, the region forms part of the address. The meaning depends on the country.
  - getCounty
```
@Nullable
public String getCounty()
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: County
    
    Currently the county code is used in the USA for handling county tax, and in Denmark to define the municipality number of the employee's first place of residence.
    
    Returns:
    
    Key used to classify cities from the point of view of taxes.
  - getCreditControlArea
```
@Nullable
public String getCreditControlArea()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: CreditControlArea
    
    You can also enter the credit control area separately for each posting, if this was marked in the appropriate company code.When entering an order, the credit control area can also be determined from the business area and the sales area segement of the payer's master record or using a user exit.It follows that company codes and credit control areas are not linked.The only thing that you define in the company code table is the default credit control area. This is used either for payments on account to credit these payments, or where you did not enter a credit control area or the system could not determine one.There is also an allocation table of permitted credit control areas per company code which is used to check entries only.
    
    Returns:
    
    The credit control area is an organizational entity which grants and monitors a credit limit for customers. A credit control area can include one or more company codes.
  - getCustomerRebateAgreement
```
@Nullable
public String getCustomerRebateAgreement()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CustomerRebateAgreement
    
    A rebate agreement is an agreement between a customer and a supplier. On the basis of the customer's sales volume during a specified period, the supplier grants the customer a special rebate. A general rebate agreement can consist of numerous individual agreements (condition records) that are based on different factors. For example, an individualagreement may be based on a combination of customer and material or a combination of customer and rebate group, and so on.
    
    Returns:
    
    The number that uniquely identifies a rebate agreement.
  - getSalesDocumentCondition
```
@Nullable
public String getSalesDocumentCondition()
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: SalesDocumentCondition
    
    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.
  - getOverallSDProcessStatus
```
@Nullable
public String getOverallSDProcessStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallSDProcessStatus
    
    The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
    
    Returns:
    
    The processing status of the entire sales document.
  - getOverallBillingStatus
```
@Nullable
public String getOverallBillingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OverallBillingStatus
    
    Returns:
    
    SD Billing Status
  - getAccountingPostingStatus
```
@Nullable
public String getAccountingPostingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: AccountingPostingStatus
    
    The status message tells you whether the billing document must be posted to accounting, and, if so, whether the posting has taken place.
    
    Returns:
    
    The accounting status of the billing document.
  - getAccountingTransferStatus
```
@Nullable
public String getAccountingTransferStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: AccountingTransferStatus
    
    The status message tells you whether the system has successfully posted the document to accounting or whether posting is blocked because a posting block is set for the billing type.
    
    Returns:
    
    The accounting status of the billing document (for example, an invoice).
  - getBillingIssueType
```
@Nullable
public String getBillingIssueType()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: BillingIssueType
    
    Returns:
    
    SD Billing Document Issue
  - getInvoiceListStatus
```
@Nullable
public String getInvoiceListStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InvoiceListStatus
    
    Returns:
    
    Invoice list status of billing document
  - getOvrlItmGeneralIncompletionSts
```
@Nullable
public String getOvrlItmGeneralIncompletionSts()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: OvrlItmGeneralIncompletionSts
    
    The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
    
    Returns:
    
    The incompletion status of general item information in the sales document. General item information includes business, shipping, and billing data.
  - 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)
  - getInvoiceClearingStatus
```
@Nullable
public String getInvoiceClearingStatus()
```
    Constraints: Not nullable, Maximum length: 1
    Original property name from the Odata EDM: InvoiceClearingStatus
    
    Returns:
    
    Clearing Status of Billing Document
  - getBillingDocumentListType
```
@Nullable
public String getBillingDocumentListType()
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BillingDocumentListType
    
    Returns:
    
    Classification that distinguishes between invoice list types that require different processing by the system.
  - getBillingDocumentListDate
```
@Nullable
public LocalDateTime getBillingDocumentListDate()
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: BillingDocumentListDate
    
    The system automatically proposes the next valid date defined in the customer's factory calendar. You can change the date manually in the header of the invoice list.
    
    Returns:
    
    Specifies the billing date of the invoice list.
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<BillingDocument>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<BillingDocument>
  - canEqual
```
protected boolean canEqual(Object other)
```
    Overrides:
    
    canEqual in class VdmObject<BillingDocument>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<BillingDocument>

Class BillingDocument

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

SD_DOCUMENT_CATEGORY

BILLING_DOCUMENT_CATEGORY

BILLING_DOCUMENT_TYPE

CREATION_DATE

CREATION_TIME

LAST_CHANGE_DATE

LAST_CHANGE_DATE_TIME

LOGICAL_SYSTEM

SALES_ORGANIZATION

DISTRIBUTION_CHANNEL

DIVISION

BILLING_DOCUMENT_DATE

BILLING_DOCUMENT_IS_CANCELLED

CANCELLED_BILLING_DOCUMENT

FOREIGN_TRADE

IS_EXPORT_DELIVERY

BILLING_DOC_COMBINATION_CRITERIA

MANUAL_INVOICE_MAINT_IS_RELEVANT

IS_INTRASTAT_REPORTING_RELEVANT

IS_INTRASTAT_REPORTING_EXCLUDED

TOTAL_NET_AMOUNT

TRANSACTION_CURRENCY

STATISTICS_CURRENCY

TAX_AMOUNT

TOTAL_GROSS_AMOUNT

CUSTOMER_PRICE_GROUP

PRICE_LIST_TYPE

TAX_DEPARTURE_COUNTRY

VAT_REGISTRATION

VAT_REGISTRATION_ORIGIN

VAT_REGISTRATION_COUNTRY

HIERARCHY_TYPE_PRICING

CUSTOMER_TAX_CLASSIFICATION1

CUSTOMER_TAX_CLASSIFICATION2

CUSTOMER_TAX_CLASSIFICATION3

CUSTOMER_TAX_CLASSIFICATION4

CUSTOMER_TAX_CLASSIFICATION5

CUSTOMER_TAX_CLASSIFICATION6

CUSTOMER_TAX_CLASSIFICATION7

CUSTOMER_TAX_CLASSIFICATION8

CUSTOMER_TAX_CLASSIFICATION9

IS_EU_TRIANGULAR_DEAL

SD_PRICING_PROCEDURE

SHIPPING_CONDITION

INCOTERMS_VERSION

INCOTERMS_CLASSIFICATION

INCOTERMS_TRANSFER_LOCATION

INCOTERMS_LOCATION1

INCOTERMS_LOCATION2

PAYER_PARTY

CONTRACT_ACCOUNT

CUSTOMER_PAYMENT_TERMS

PAYMENT_METHOD

PAYMENT_REFERENCE

FIXED_VALUE_DATE

ADDITIONAL_VALUE_DAYS

SEPA_MANDATE

COMPANY_CODE

FISCAL_YEAR

ACCOUNTING_DOCUMENT

CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP

ACCOUNTING_EXCHANGE_RATE_IS_SET

ABSLT_ACCOUNTING_EXCHANGE_RATE

ACCTG_EXCHANGE_RATE_IS_INDRCT_QTAN

EXCHANGE_RATE_DATE

EXCHANGE_RATE_TYPE

DOCUMENT_REFERENCE_ID

ASSIGNMENT_REFERENCE