BillingDocumentItem (SAP S/4HANA Cloud SDK

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

public class BillingDocumentItem
extends VdmEntity<BillingDocumentItem>

Billing Document Item Partners (API)

Nested Class Summary

Nested Classes
Modifier and Type Class and Description

static class BillingDocumentItem.BillingDocumentItemBuilder

Nested Classes
Modifier and Type	Class and Description
`static class`	`BillingDocumentItem.BillingDocumentItemBuilder`

Field Summary

Fields
Modifier and Type	Field and Description
`static BillingDocumentItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP1` Use with available fluent helpers to apply the AdditionalCustomerGroup1 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP2` Use with available fluent helpers to apply the AdditionalCustomerGroup2 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP3` Use with available fluent helpers to apply the AdditionalCustomerGroup3 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP4` Use with available fluent helpers to apply the AdditionalCustomerGroup4 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_CUSTOMER_GROUP5` Use with available fluent helpers to apply the AdditionalCustomerGroup5 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_MATERIAL_GROUP1` Use with available fluent helpers to apply the AdditionalMaterialGroup1 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_MATERIAL_GROUP2` Use with available fluent helpers to apply the AdditionalMaterialGroup2 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_MATERIAL_GROUP3` Use with available fluent helpers to apply the AdditionalMaterialGroup3 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_MATERIAL_GROUP4` Use with available fluent helpers to apply the AdditionalMaterialGroup4 field to query operations.
`static BillingDocumentItemField<String>`	`ADDITIONAL_MATERIAL_GROUP5` Use with available fluent helpers to apply the AdditionalMaterialGroup5 field to query operations.
`static BillingDocumentItemSelectable`	`ALL_FIELDS` Selector for all available fields of BillingDocumentItem.
`static BillingDocumentItemField<String>`	`BASE_UNIT` Use with available fluent helpers to apply the BaseUnit field to query operations.
`static BillingDocumentItemField<String>`	`BATCH` Use with available fluent helpers to apply the Batch field to query operations.
`static BillingDocumentItemField<String>`	`BILL_TO_PARTY_COUNTRY` Use with available fluent helpers to apply the BillToPartyCountry field to query operations.
`static BillingDocumentItemField<String>`	`BILL_TO_PARTY_REGION` Use with available fluent helpers to apply the BillToPartyRegion field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_DOCUMENT` Use with available fluent helpers to apply the BillingDocument field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_DOCUMENT_ITEM` Use with available fluent helpers to apply the BillingDocumentItem field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_DOCUMENT_ITEM_IN_PART_SGMT` Use with available fluent helpers to apply the BillingDocumentItemInPartSgmt field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_DOCUMENT_ITEM_TEXT` Use with available fluent helpers to apply the BillingDocumentItemText field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_PLAN` Use with available fluent helpers to apply the BillingPlan field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_PLAN_ITEM` Use with available fluent helpers to apply the BillingPlanItem field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_PLAN_RULE` Use with available fluent helpers to apply the BillingPlanRule field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`BILLING_QUANTITY` Use with available fluent helpers to apply the BillingQuantity field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`BILLING_QUANTITY_IN_BASE_UNIT` Use with available fluent helpers to apply the BillingQuantityInBaseUnit field to query operations.
`static BillingDocumentItemField<String>`	`BILLING_QUANTITY_UNIT` Use with available fluent helpers to apply the BillingQuantityUnit field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`BILLING_TO_BASE_QUANTITY_DNMNTR` Use with available fluent helpers to apply the BillingToBaseQuantityDnmntr field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`BILLING_TO_BASE_QUANTITY_NMRTR` Use with available fluent helpers to apply the BillingToBaseQuantityNmrtr field to query operations.
`static BillingDocumentItemField<String>`	`BOM_EXPLOSION` Use with available fluent helpers to apply the BOMExplosion field to query operations.
`static BillingDocumentItemField<String>`	`BUSINESS_AREA` Use with available fluent helpers to apply the BusinessArea field to query operations.
`static BillingDocumentItemField<Boolean>`	`CASH_DISCOUNT_IS_DEDUCTIBLE` Use with available fluent helpers to apply the CashDiscountIsDeductible field to query operations.
`static BillingDocumentItemField<String>`	`CONTROLLING_AREA` Use with available fluent helpers to apply the ControllingArea field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`COST_AMOUNT` Use with available fluent helpers to apply the CostAmount field to query operations.
`static BillingDocumentItemField<String>`	`COST_CENTER` Use with available fluent helpers to apply the CostCenter field to query operations.
`static BillingDocumentItemField<String>`	`CREATED_BY_USER` Use with available fluent helpers to apply the CreatedByUser field to query operations.
`static BillingDocumentItemField<Calendar>`	`CREATION_DATE` Use with available fluent helpers to apply the CreationDate field to query operations.
`static BillingDocumentItemField<Calendar>`	`CREATION_TIME` Use with available fluent helpers to apply the CreationTime field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`CREDIT_RELATED_PRICE` Use with available fluent helpers to apply the CreditRelatedPrice field to query operations.
`static BillingDocumentItemField<String>`	`CUSTOMER_CONDITION_GROUP1` Use with available fluent helpers to apply the CustomerConditionGroup1 field to query operations.
`static BillingDocumentItemField<String>`	`CUSTOMER_CONDITION_GROUP2` Use with available fluent helpers to apply the CustomerConditionGroup2 field to query operations.
`static BillingDocumentItemField<String>`	`CUSTOMER_CONDITION_GROUP3` Use with available fluent helpers to apply the CustomerConditionGroup3 field to query operations.
`static BillingDocumentItemField<String>`	`CUSTOMER_CONDITION_GROUP4` Use with available fluent helpers to apply the CustomerConditionGroup4 field to query operations.
`static BillingDocumentItemField<String>`	`CUSTOMER_CONDITION_GROUP5` Use with available fluent helpers to apply the CustomerConditionGroup5 field to query operations.
`static BillingDocumentItemField<String>`	`DEPARTURE_COUNTRY` Use with available fluent helpers to apply the DepartureCountry field to query operations.
`static BillingDocumentItemField<String>`	`DIVISION` Use with available fluent helpers to apply the Division field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`ELIGIBLE_AMOUNT_FOR_CASH_DISCOUNT` Use with available fluent helpers to apply the EligibleAmountForCashDiscount field to query operations.
`static BillingDocumentItemField<String>`	`EXTERNAL_REFERENCE_DOCUMENT` Use with available fluent helpers to apply the ExternalReferenceDocument field to query operations.
`static BillingDocumentItemField<String>`	`EXTERNAL_REFERENCE_DOCUMENT_ITEM` Use with available fluent helpers to apply the ExternalReferenceDocumentItem field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`GROSS_AMOUNT` Use with available fluent helpers to apply the GrossAmount field to query operations.
`static BillingDocumentItemField<String>`	`HIGHER_LEVEL_ITEM` Use with available fluent helpers to apply the HigherLevelItem field to query operations.
`static BillingDocumentItemField<String>`	`HIGHER_LEVEL_ITEM_USAGE` Use with available fluent helpers to apply the HigherLevelItemUsage field to query operations.
`static BillingDocumentItemField<String>`	`INTERNATIONAL_ARTICLE_NUMBER` Use with available fluent helpers to apply the InternationalArticleNumber field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`ITEM_GROSS_WEIGHT` Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
`static BillingDocumentItemField<Boolean>`	`ITEM_IS_RELEVANT_FOR_CREDIT` Use with available fluent helpers to apply the ItemIsRelevantForCredit field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`ITEM_NET_WEIGHT` Use with available fluent helpers to apply the ItemNetWeight field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`ITEM_VOLUME` Use with available fluent helpers to apply the ItemVolume field to query operations.
`static BillingDocumentItemField<String>`	`ITEM_VOLUME_UNIT` Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
`static BillingDocumentItemField<String>`	`ITEM_WEIGHT_UNIT` Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
`static BillingDocumentItemField<String>`	`MAIN_ITEM_MATERIAL_PRICING_GROUP` Use with available fluent helpers to apply the MainItemMaterialPricingGroup field to query operations.
`static BillingDocumentItemField<String>`	`MAIN_ITEM_PRICING_REF_MATERIAL` Use with available fluent helpers to apply the MainItemPricingRefMaterial field to query operations.
`static BillingDocumentItemField<String>`	`MANUAL_PRICE_CHANGE_TYPE` Use with available fluent helpers to apply the ManualPriceChangeType field to query operations.
`static BillingDocumentItemField<String>`	`MATERIAL` Use with available fluent helpers to apply the Material field to query operations.
`static BillingDocumentItemField<String>`	`MATERIAL_COMMISSION_GROUP` Use with available fluent helpers to apply the MaterialCommissionGroup field to query operations.
`static BillingDocumentItemField<String>`	`MATERIAL_DETERMINATION_TYPE` Use with available fluent helpers to apply the MaterialDeterminationType field to query operations.
`static BillingDocumentItemField<String>`	`MATERIAL_GROUP` Use with available fluent helpers to apply the MaterialGroup field to query operations.
`static BillingDocumentItemField<String>`	`MATERIAL_GROUP_HIERARCHY1` Use with available fluent helpers to apply the MaterialGroupHierarchy1 field to query operations.
`static BillingDocumentItemField<String>`	`MATERIAL_GROUP_HIERARCHY2` Use with available fluent helpers to apply the MaterialGroupHierarchy2 field to query operations.
`static BillingDocumentItemField<String>`	`MATERIAL_PRICING_GROUP` Use with available fluent helpers to apply the MaterialPricingGroup field to query operations.
`static BillingDocumentItemField<String>`	`MATL_ACCOUNT_ASSIGNMENT_GROUP` Use with available fluent helpers to apply the MatlAccountAssignmentGroup field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`MRP_REQUIRED_QUANTITY_IN_BASE_UNIT` Use with available fluent helpers to apply the MRPRequiredQuantityInBaseUnit field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`NET_AMOUNT` Use with available fluent helpers to apply the NetAmount field to query operations.
`static BillingDocumentItemField<String>`	`ORDER_ID` Use with available fluent helpers to apply the OrderID field to query operations.
`static BillingDocumentItemField<String>`	`ORGANIZATION_DIVISION` Use with available fluent helpers to apply the OrganizationDivision field to query operations.
`static BillingDocumentItemField<String>`	`ORIGIN_SD_DOCUMENT` Use with available fluent helpers to apply the OriginSDDocument field to query operations.
`static BillingDocumentItemField<String>`	`ORIGIN_SD_DOCUMENT_ITEM` Use with available fluent helpers to apply the OriginSDDocumentItem field to query operations.
`static BillingDocumentItemField<String>`	`ORIGINALLY_REQUESTED_MATERIAL` Use with available fluent helpers to apply the OriginallyRequestedMaterial field to query operations.
`static BillingDocumentItemField<String>`	`PLANT` Use with available fluent helpers to apply the Plant field to query operations.
`static BillingDocumentItemField<String>`	`PLANT_CITY` Use with available fluent helpers to apply the PlantCity field to query operations.
`static BillingDocumentItemField<String>`	`PLANT_COUNTY` Use with available fluent helpers to apply the PlantCounty field to query operations.
`static BillingDocumentItemField<String>`	`PLANT_REGION` Use with available fluent helpers to apply the PlantRegion field to query operations.
`static BillingDocumentItemField<Calendar>`	`PRICING_DATE` Use with available fluent helpers to apply the PricingDate field to query operations.
`static BillingDocumentItemField<String>`	`PRICING_REFERENCE_MATERIAL` Use with available fluent helpers to apply the PricingReferenceMaterial field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`PRICING_SCALE_QUANTITY_IN_BASE_UNIT` Use with available fluent helpers to apply the PricingScaleQuantityInBaseUnit field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_HIERARCHY_NODE` Use with available fluent helpers to apply the ProductHierarchyNode field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION1` Use with available fluent helpers to apply the ProductTaxClassification1 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION2` Use with available fluent helpers to apply the ProductTaxClassification2 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION3` Use with available fluent helpers to apply the ProductTaxClassification3 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION4` Use with available fluent helpers to apply the ProductTaxClassification4 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION5` Use with available fluent helpers to apply the ProductTaxClassification5 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION6` Use with available fluent helpers to apply the ProductTaxClassification6 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION7` Use with available fluent helpers to apply the ProductTaxClassification7 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION8` Use with available fluent helpers to apply the ProductTaxClassification8 field to query operations.
`static BillingDocumentItemField<String>`	`PRODUCT_TAX_CLASSIFICATION9` Use with available fluent helpers to apply the ProductTaxClassification9 field to query operations.
`static BillingDocumentItemField<String>`	`PROFIT_CENTER` Use with available fluent helpers to apply the ProfitCenter field to query operations.
`static BillingDocumentItemField<String>`	`PROFITABILITY_SEGMENT` Use with available fluent helpers to apply the ProfitabilitySegment field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`REBATE_BASIS_AMOUNT` Use with available fluent helpers to apply the RebateBasisAmount field to query operations.
`static BillingDocumentItemField<String>`	`REFERENCE_SD_DOCUMENT` Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
`static BillingDocumentItemField<String>`	`REFERENCE_SD_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
`static BillingDocumentItemField<String>`	`REFERENCE_SD_DOCUMENT_ITEM` Use with available fluent helpers to apply the ReferenceSDDocumentItem field to query operations.
`static BillingDocumentItemField<String>`	`REPLACEMENT_PART_TYPE` Use with available fluent helpers to apply the ReplacementPartType field to query operations.
`static BillingDocumentItemField<String>`	`RETAIL_PROMOTION` Use with available fluent helpers to apply the RetailPromotion field to query operations.
`static BillingDocumentItemField<String>`	`RETURN_ITEM_PROCESSING_TYPE` Use with available fluent helpers to apply the ReturnItemProcessingType field to query operations.
`static BillingDocumentItemField<String>`	`SALES_DEAL` Use with available fluent helpers to apply the SalesDeal field to query operations.
`static BillingDocumentItemField<Boolean>`	`SALES_DOC_IS_CREATED_FROM_REFERENCE` Use with available fluent helpers to apply the SalesDocIsCreatedFromReference field to query operations.
`static BillingDocumentItemField<String>`	`SALES_DOCUMENT` Use with available fluent helpers to apply the SalesDocument field to query operations.
`static BillingDocumentItemField<String>`	`SALES_DOCUMENT_ITEM` Use with available fluent helpers to apply the SalesDocumentItem field to query operations.
`static BillingDocumentItemField<String>`	`SALES_DOCUMENT_ITEM_CATEGORY` Use with available fluent helpers to apply the SalesDocumentItemCategory field to query operations.
`static BillingDocumentItemField<String>`	`SALES_DOCUMENT_ITEM_TYPE` Use with available fluent helpers to apply the SalesDocumentItemType field to query operations.
`static BillingDocumentItemField<String>`	`SALES_GROUP` Use with available fluent helpers to apply the SalesGroup field to query operations.
`static BillingDocumentItemField<String>`	`SALES_OFFICE` Use with available fluent helpers to apply the SalesOffice field to query operations.
`static BillingDocumentItemField<String>`	`SALES_ORDER_CUSTOMER_GROUP` Use with available fluent helpers to apply the SalesOrderCustomerGroup field to query operations.
`static BillingDocumentItemField<String>`	`SALES_ORDER_CUSTOMER_PRICE_GROUP` Use with available fluent helpers to apply the SalesOrderCustomerPriceGroup field to query operations.
`static BillingDocumentItemField<String>`	`SALES_ORDER_DISTRIBUTION_CHANNEL` Use with available fluent helpers to apply the SalesOrderDistributionChannel field to query operations.
`static BillingDocumentItemField<String>`	`SALES_ORDER_PRICE_LIST_TYPE` Use with available fluent helpers to apply the SalesOrderPriceListType field to query operations.
`static BillingDocumentItemField<String>`	`SALES_ORDER_SALES_DISTRICT` Use with available fluent helpers to apply the SalesOrderSalesDistrict field to query operations.
`static BillingDocumentItemField<String>`	`SALES_ORDER_SALES_ORGANIZATION` Use with available fluent helpers to apply the SalesOrderSalesOrganization field to query operations.
`static BillingDocumentItemField<String>`	`SALES_PROMOTION` Use with available fluent helpers to apply the SalesPromotion field to query operations.
`static BillingDocumentItemField<String>`	`SALES_SD_DOCUMENT_CATEGORY` Use with available fluent helpers to apply the SalesSDDocumentCategory field to query operations.
`static BillingDocumentItemField<String>`	`SD_DOCUMENT_REASON` Use with available fluent helpers to apply the SDDocumentReason field to query operations.
`static BillingDocumentItemField<Calendar>`	`SERVICES_RENDERED_DATE` Use with available fluent helpers to apply the ServicesRenderedDate field to query operations.
`static BillingDocumentItemField<String>`	`SHIPPING_POINT` Use with available fluent helpers to apply the ShippingPoint field to query operations.
`static BillingDocumentItemField<String>`	`STATISTICAL_VALUE_CONTROL` Use with available fluent helpers to apply the StatisticalValueControl field to query operations.
`static BillingDocumentItemField<String>`	`STORAGE_LOCATION` Use with available fluent helpers to apply the StorageLocation field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`SUBTOTAL1_AMOUNT` Use with available fluent helpers to apply the Subtotal1Amount field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`SUBTOTAL2_AMOUNT` Use with available fluent helpers to apply the Subtotal2Amount field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`SUBTOTAL3_AMOUNT` Use with available fluent helpers to apply the Subtotal3Amount field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`SUBTOTAL4_AMOUNT` Use with available fluent helpers to apply the Subtotal4Amount field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`SUBTOTAL5_AMOUNT` Use with available fluent helpers to apply the Subtotal5Amount field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`SUBTOTAL6_AMOUNT` Use with available fluent helpers to apply the Subtotal6Amount field to query operations.
`static BillingDocumentItemField<BigDecimal>`	`TAX_AMOUNT` Use with available fluent helpers to apply the TaxAmount field to query operations.
`static BillingDocumentItemField<String>`	`TAX_JURISDICTION` Use with available fluent helpers to apply the TaxJurisdiction field to query operations.
`static BillingDocumentItemLink<BillingDocument>`	`TO_BILLING_DOCUMENT` Use with available fluent helpers to apply the to_BillingDocument navigation property to query operations.
`static BillingDocumentItemLink<BillingDocumentItemPartner>`	`TO_PARTNER` Use with available fluent helpers to apply the to_Partner navigation property to query operations.
`static BillingDocumentItemLink<BillingDocumentItemPrcgElmnt>`	`TO_PRICING_ELEMENT` Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
`static BillingDocumentItemField<String>`	`TRANSACTION_CURRENCY` Use with available fluent helpers to apply the TransactionCurrency field to query operations.
`static BillingDocumentItemField<String>`	`VOLUME_REBATE_GROUP` Use with available fluent helpers to apply the VolumeRebateGroup field to query operations.
`static BillingDocumentItemField<String>`	`WBS_ELEMENT` Use with available fluent helpers to apply the WBSElement field to query operations.
`static BillingDocumentItemField<String>`	`ZERO_VAT_RSN` Use with available fluent helpers to apply the ZeroVATRsn field to query operations.

Constructor Summary

Constructors
Constructor and Description
`BillingDocumentItem()`
BillingDocumentItem(String billingDocument, String billingDocumentItem, String salesDocumentItemCategory, String salesDocumentItemType, String returnItemProcessingType, String createdByUser, Calendar creationDate, Calendar creationTime, String organizationDivision, String division, String salesOffice, String material, String originallyRequestedMaterial, String internationalArticleNumber, String pricingReferenceMaterial, String batch, String productHierarchyNode, String materialGroup, String additionalMaterialGroup1, String additionalMaterialGroup2, String additionalMaterialGroup3, String additionalMaterialGroup4, String additionalMaterialGroup5, String materialCommissionGroup, String plant, String storageLocation, String replacementPartType, String materialGroupHierarchy1, String materialGroupHierarchy2, String plantRegion, String plantCounty, String plantCity, String bOMExplosion, String materialDeterminationType, String billingDocumentItemText, Calendar servicesRenderedDate, BigDecimal billingQuantity, String billingQuantityUnit, BigDecimal billingQuantityInBaseUnit, String baseUnit, BigDecimal mRPRequiredQuantityInBaseUnit, BigDecimal billingToBaseQuantityDnmntr, BigDecimal billingToBaseQuantityNmrtr, BigDecimal itemGrossWeight, BigDecimal itemNetWeight, String itemWeightUnit, BigDecimal itemVolume, String itemVolumeUnit, String billToPartyCountry, String billToPartyRegion, String billingPlanRule, String billingPlan, String billingPlanItem, BigDecimal netAmount, String transactionCurrency, BigDecimal grossAmount, Calendar pricingDate, BigDecimal pricingScaleQuantityInBaseUnit, BigDecimal taxAmount, BigDecimal costAmount, BigDecimal subtotal1Amount, BigDecimal subtotal2Amount, BigDecimal subtotal3Amount, BigDecimal subtotal4Amount, BigDecimal subtotal5Amount, BigDecimal subtotal6Amount, String statisticalValueControl, Boolean cashDiscountIsDeductible, String customerConditionGroup1, String customerConditionGroup2, String customerConditionGroup3, String customerConditionGroup4, String customerConditionGroup5, String manualPriceChangeType, String materialPricingGroup, String mainItemPricingRefMaterial, String mainItemMaterialPricingGroup, String departureCountry, String taxJurisdiction, String productTaxClassification1, String productTaxClassification2, String productTaxClassification3, String productTaxClassification4, String productTaxClassification5, String productTaxClassification6, String productTaxClassification7, String productTaxClassification8, String productTaxClassification9, String zeroVATRsn, BigDecimal eligibleAmountForCashDiscount, String businessArea, String profitCenter, String wBSElement, String controllingArea, String profitabilitySegment, String orderID, String costCenter, String originSDDocument, String originSDDocumentItem, String matlAccountAssignmentGroup, String referenceSDDocument, String referenceSDDocumentItem, String referenceSDDocumentCategory, String salesDocument, String salesDocumentItem, String salesSDDocumentCategory, String higherLevelItem, String billingDocumentItemInPartSgmt, String externalReferenceDocument, String externalReferenceDocumentItem, String salesGroup, String additionalCustomerGroup1, String additionalCustomerGroup2, String additionalCustomerGroup3, String additionalCustomerGroup4, String additionalCustomerGroup5, String sDDocumentReason, String retailPromotion, BigDecimal rebateBasisAmount, String volumeRebateGroup, Boolean itemIsRelevantForCredit, BigDecimal creditRelatedPrice, String salesDeal, String salesPromotion, String salesOrderSalesDistrict, String salesOrderCustomerGroup, String salesOrderCustomerPriceGroup, String salesOrderPriceListType, String salesOrderSalesOrganization, String salesOrderDistributionChannel, Boolean salesDocIsCreatedFromReference, String shippingPoint, String higherLevelItemUsage, ErpConfigContext erpConfigContext, BillingDocument toBillingDocument, List<BillingDocumentItemPartner> toPartner, List<BillingDocumentItemPrcgElmnt> toPricingElement)

Method Summary

All Methods Static Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`void`	`addPartner(BillingDocumentItemPartner... entity)` Adds elements to the list of associated BillingDocumentItemPartner entities.
`void`	`addPricingElement(BillingDocumentItemPrcgElmnt... entity)` Adds elements to the list of associated BillingDocumentItemPrcgElmnt entities.
`static BillingDocumentItem.BillingDocumentItemBuilder`	`builder()`
`boolean`	`equals(Object o)`
`BillingDocument`	`fetchBillingDocument()` Fetches the BillingDocument entity (one to one) associated with this entity.
`List<BillingDocumentItemPartner>`	`fetchPartner()` Fetches the BillingDocumentItemPartner entities (one to many) associated with this entity.
`List<BillingDocumentItemPrcgElmnt>`	`fetchPricingElement()` Fetches the BillingDocumentItemPrcgElmnt entities (one to many) associated with this entity.
`static <T> BillingDocumentItemField<T>`	`field(String fieldName, Class<T> fieldType)` Use with available fluent helpers to apply an extension field to query operations.
`String`	`getAdditionalCustomerGroup1()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup2()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup3()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup4()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalCustomerGroup5()` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`String`	`getAdditionalMaterialGroup1()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup2()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup3()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup4()` Constraints: Not nullable, Maximum length: 3
`String`	`getAdditionalMaterialGroup5()` Constraints: Not nullable, Maximum length: 3
`String`	`getBaseUnit()` Constraints: Not nullable, Maximum length: 3 You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.
`String`	`getBatch()` Constraints: Not nullable, Maximum length: 10
`String`	`getBillingDocument()` (Key Field) Constraints: Not nullable, Maximum length: 10
`String`	`getBillingDocumentItem()` (Key Field) Constraints: Not nullable, Maximum length: 6
`String`	`getBillingDocumentItemInPartSgmt()` Constraints: Not nullable, Maximum length: 6
`String`	`getBillingDocumentItemText()` Constraints: Not nullable, Maximum length: 40 Short texts are used throughout sales order processing, shipping, and billing.
`BillingDocument`	`getBillingDocumentOrFetch()` Retrieval of associated BillingDocument entity (one to one).
`com.google.common.base.Optional<BillingDocument>`	`getBillingDocumentOrNull()` Retrieval of associated BillingDocument entity (one to one).
`String`	`getBillingPlan()` Constraints: Not nullable, Maximum length: 10
`String`	`getBillingPlanItem()` Constraints: Not nullable, Maximum length: 6
`String`	`getBillingPlanRule()` Constraints: Not nullable, Maximum length: 1 Billing plan for a rental contract for a piece of machinery Billing dates: First of the month for 12 months Billing amount: 1000 USD per month Each date requires a billing rule which determines this fixed amount as the amount to be billed.
`BigDecimal`	`getBillingQuantity()` Constraints: Not nullable, Precision: 13, Scale: 3
`BigDecimal`	`getBillingQuantityInBaseUnit()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getBillingQuantityUnit()` Constraints: Not nullable, Maximum length: 3
`BigDecimal`	`getBillingToBaseQuantityDnmntr()` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`BigDecimal`	`getBillingToBaseQuantityNmrtr()` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`String`	`getBillToPartyCountry()` Constraints: Not nullable, Maximum length: 3
`String`	`getBillToPartyRegion()` Constraints: Not nullable, Maximum length: 3
`String`	`getBOMExplosion()` Constraints: Not nullable, Maximum length: 8
`String`	`getBusinessArea()` Constraints: Not nullable, Maximum length: 4
`Boolean`	`getCashDiscountIsDeductible()` Constraints: none
`String`	`getControllingArea()` Constraints: Not nullable, Maximum length: 4 The controlling area is the highest organizational unit in Controlling.
`BigDecimal`	`getCostAmount()` Constraints: Not nullable, Precision: 14, Scale: 3
`String`	`getCostCenter()` Constraints: Not nullable, Maximum length: 10
`String`	`getCreatedByUser()` Constraints: Not nullable, Maximum length: 12
`Calendar`	`getCreationDate()` Constraints: Not nullable, Precision: 0
`Calendar`	`getCreationTime()` Constraints: Not nullable, Precision: 0
`BigDecimal`	`getCreditRelatedPrice()` Constraints: Not nullable, Precision: 12, Scale: 3 The system multiplies the price you specify (for example, the net price) by the item quantity of an open sales, shipping, or billing document to calculate the value for credit management purposes.
`String`	`getCustomerConditionGroup1()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerConditionGroup2()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerConditionGroup3()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerConditionGroup4()` Constraints: Not nullable, Maximum length: 2
`String`	`getCustomerConditionGroup5()` Constraints: Not nullable, Maximum length: 2
`String`	`getDepartureCountry()` Constraints: Not nullable, Maximum length: 3 You can define the country key in a table.
`String`	`getDivision()` Constraints: Not nullable, Maximum length: 2 A product or service is always assigned to just one division.
`BigDecimal`	`getEligibleAmountForCashDiscount()` Constraints: Not nullable, Precision: 14, Scale: 3 During document entry, the amount qualifying for cash discount can be determined manually or automatically.
`ErpConfigContext`	`getErpConfigContext()` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`String`	`getExternalReferenceDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getExternalReferenceDocumentItem()` Constraints: Not nullable, Maximum length: 6
`BigDecimal`	`getGrossAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`String`	`getHigherLevelItem()` Constraints: Not nullable, Maximum length: 6 Items can be organized hierarchically.
`String`	`getHigherLevelItemUsage()` Constraints: Not nullable, Maximum length: 1
`String`	`getInternationalArticleNumber()` Constraints: Not nullable, Maximum length: 18
`BigDecimal`	`getItemGrossWeight()` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order.
`Boolean`	`getItemIsRelevantForCredit()` Constraints: noneSelect this field if the values of the item type in the total liability are to be updated.
`BigDecimal`	`getItemNetWeight()` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order.
`BigDecimal`	`getItemVolume()` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order.
`String`	`getItemVolumeUnit()` Constraints: Not nullable, Maximum length: 3 If you specify a volume, you have to enter the corresponding volume unit here.
`String`	`getItemWeightUnit()` Constraints: Not nullable, Maximum length: 3 If you specify a weight, you must enter the corresponding unit of weight here.
`String`	`getMainItemMaterialPricingGroup()` Constraints: Not nullable, Maximum length: 2 You can create price conditions for a material pricing group (for example, non-food products) a combination of customer and material pricing group a combination of price group and material pricing group (for example, wholesale customers and all non-food products)
`String`	`getMainItemPricingRefMaterial()` Constraints: Not nullable, Maximum length: 40 The pricing reference material is stored in the master record of the main item material.
`String`	`getManualPriceChangeType()` Constraints: Not nullable, Maximum length: 1
`String`	`getMaterial()` Constraints: Not nullable, Maximum length: 40
`String`	`getMaterialCommissionGroup()` Constraints: Not nullable, Maximum length: 2 You can assign two materials to the same commission group as long as each representative who sells these materials receives the same commission percentage for both materials.
`String`	`getMaterialDeterminationType()` Constraints: Not nullable, Maximum length: 1
`String`	`getMaterialGroup()` Constraints: Not nullable, Maximum length: 9 You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
`String`	`getMaterialGroupHierarchy1()` Constraints: Not nullable, Maximum length: 18 Material group hierarchy levels can be put together into groups.
`String`	`getMaterialGroupHierarchy2()` Constraints: Not nullable, Maximum length: 18 Material group hierarchy levels can be put together into groups.
`String`	`getMaterialPricingGroup()` Constraints: Not nullable, Maximum length: 2 You can create condition records for a material price group using the following condition types: Material price group (for example, all non-food products) A combination of customer and material price group A combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
`String`	`getMatlAccountAssignmentGroup()` Constraints: Not nullable, Maximum length: 2 Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
`BigDecimal`	`getMRPRequiredQuantityInBaseUnit()` Constraints: Not nullable, Precision: 13, Scale: 3 The system uses this quantity during the availability check to guarantee that the confirmed quantity cannot be used for another sales order.
`BigDecimal`	`getNetAmount()` Constraints: Not nullable, Precision: 16, Scale: 3
`String`	`getOrderID()` Constraints: Not nullable, Maximum length: 12
`String`	`getOrganizationDivision()` Constraints: Not nullable, Maximum length: 2
`String`	`getOriginallyRequestedMaterial()` Constraints: Not nullable, Maximum length: 40 If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
`String`	`getOriginSDDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getOriginSDDocumentItem()` Constraints: Not nullable, Maximum length: 6
`List<BillingDocumentItemPartner>`	`getPartnerOrFetch()` Retrieval of associated BillingDocumentItemPartner entities (one to many).
`com.google.common.base.Optional<List<BillingDocumentItemPartner>>`	`getPartnerOrNull()` Retrieval of associated BillingDocumentItemPartner entities (one to many).
`String`	`getPlant()` Constraints: Not nullable, Maximum length: 4
`String`	`getPlantCity()` Constraints: Not nullable, Maximum length: 4
`String`	`getPlantCounty()` Constraints: Not nullable, Maximum length: 3
`String`	`getPlantRegion()` Constraints: Not nullable, Maximum length: 3
`Calendar`	`getPricingDate()` Constraints: Not nullable, Precision: 0 You can use the pricing date as a selection criterion when you process billing documents collectively.
`List<BillingDocumentItemPrcgElmnt>`	`getPricingElementOrFetch()` Retrieval of associated BillingDocumentItemPrcgElmnt entities (one to many).
`com.google.common.base.Optional<List<BillingDocumentItemPrcgElmnt>>`	`getPricingElementOrNull()` Retrieval of associated BillingDocumentItemPrcgElmnt entities (one to many).
`String`	`getPricingReferenceMaterial()` Constraints: Not nullable, Maximum length: 40 The conditions that apply to the pricing reference material also apply to the material in whose material master record the pricing reference material is stored.
`BigDecimal`	`getPricingScaleQuantityInBaseUnit()` Constraints: Not nullable, Precision: 13, Scale: 3
`String`	`getProductHierarchyNode()` Constraints: Not nullable, Maximum length: 18 In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.
`String`	`getProductTaxClassification1()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification2()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification3()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification4()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification5()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification6()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification7()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification8()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProductTaxClassification9()` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`String`	`getProfitabilitySegment()` Constraints: Not nullable, Maximum length: 10 Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
`String`	`getProfitCenter()` Constraints: Not nullable, Maximum length: 10
`BigDecimal`	`getRebateBasisAmount()` Constraints: Not nullable, Precision: 14, Scale: 3
`String`	`getReferenceSDDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getReferenceSDDocumentCategory()` Constraints: Not nullable, Maximum length: 4
`String`	`getReferenceSDDocumentItem()` Constraints: Not nullable, Maximum length: 6
`String`	`getReplacementPartType()` Constraints: Not nullable, Maximum length: 1 The SD billing application uses this indicator to disclose used-parts VAT.
`String`	`getRetailPromotion()` Constraints: Not nullable, Maximum length: 10 For each item of a purchasing document, you can specify the promotion to which the item belongs.
`String`	`getReturnItemProcessingType()` Constraints: Not nullable, Maximum length: 1
`String`	`getSalesDeal()` Constraints: Not nullable, Maximum length: 10 When creating a new sales deal, you can either enter a number manually or let the system automatically assign an internal number.
`Boolean`	`getSalesDocIsCreatedFromReference()` Constraints: noneYou create a sales order from a quotation.
`String`	`getSalesDocument()` Constraints: Not nullable, Maximum length: 10
`String`	`getSalesDocumentItem()` Constraints: Not nullable, Maximum length: 6
`String`	`getSalesDocumentItemCategory()` Constraints: Not nullable, Maximum length: 4 The system proposes an item category.
`String`	`getSalesDocumentItemType()` Constraints: Not nullable, Maximum length: 1 The system processes items that refer to a specific material differently than items that do not refer to a material.
`String`	`getSalesGroup()` Constraints: Not nullable, Maximum length: 3 By using sales groups you can designate different areas of responsibility within a sales office.
`String`	`getSalesOffice()` Constraints: Not nullable, Maximum length: 4 When you create sales statistics, you can use a sales office as one of the selection criteria.
`String`	`getSalesOrderCustomerGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getSalesOrderCustomerPriceGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getSalesOrderDistributionChannel()` Constraints: Not nullable, Maximum length: 2
`String`	`getSalesOrderPriceListType()` Constraints: Not nullable, Maximum length: 2
`String`	`getSalesOrderSalesDistrict()` Constraints: Not nullable, Maximum length: 6
`String`	`getSalesOrderSalesOrganization()` Constraints: Not nullable, Maximum length: 4 When you create condition records to define prices for inter-company billing, you specify the sales organization that is responsible for processing the sales order.
`String`	`getSalesPromotion()` Constraints: Not nullable, Maximum length: 10 When creating a new promotion, you can either enter a number manually or let the system automatically assign an internal number.
`String`	`getSalesSDDocumentCategory()` Constraints: Not nullable, Maximum length: 4 The document category determines how the system stores and keeps track of document data.
`String`	`getSDDocumentReason()` Constraints: Not nullable, Maximum length: 3 You can freely define order reasons according to the needs of your organization.
`Calendar`	`getServicesRenderedDate()` Constraints: Not nullable, Precision: 0 If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field.
`String`	`getShippingPoint()` Constraints: Not nullable, Maximum length: 4 You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.
`String`	`getStatisticalValueControl()` Constraints: Not nullable, Maximum length: 1
`String`	`getStorageLocation()` Constraints: Not nullable, Maximum length: 4
`BigDecimal`	`getSubtotal1Amount()` Constraints: Not nullable, Precision: 14, Scale: 3
`BigDecimal`	`getSubtotal2Amount()` Constraints: Not nullable, Precision: 14, Scale: 3
`BigDecimal`	`getSubtotal3Amount()` Constraints: Not nullable, Precision: 14, Scale: 3
`BigDecimal`	`getSubtotal4Amount()` Constraints: Not nullable, Precision: 14, Scale: 3
`BigDecimal`	`getSubtotal5Amount()` Constraints: Not nullable, Precision: 14, Scale: 3
`BigDecimal`	`getSubtotal6Amount()` Constraints: Not nullable, Precision: 14, Scale: 3
`BigDecimal`	`getTaxAmount()` Constraints: Not nullable, Precision: 14, Scale: 3
`String`	`getTaxJurisdiction()` Constraints: Not nullable, Maximum length: 15
`String`	`getTransactionCurrency()` Constraints: Not nullable, Maximum length: 5 The system proposes the document currency from the customer master record of the sold-to party.
`Class<BillingDocumentItem>`	`getType()`
`String`	`getVolumeRebateGroup()` Constraints: Not nullable, Maximum length: 2
`String`	`getWBSElement()` Constraints: Not nullable, Maximum length: 24
`String`	`getZeroVATRsn()` Constraints: Not nullable, Maximum length: 1 the tax purposes.
`int`	`hashCode()`
`void`	`setAdditionalCustomerGroup1(String additionalCustomerGroup1)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup2(String additionalCustomerGroup2)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup3(String additionalCustomerGroup3)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup4(String additionalCustomerGroup4)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalCustomerGroup5(String additionalCustomerGroup5)` Constraints: Not nullable, Maximum length: 3 You can define up to five different groups of customers, according to the needs of your organization.
`void`	`setAdditionalMaterialGroup1(String additionalMaterialGroup1)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup2(String additionalMaterialGroup2)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup3(String additionalMaterialGroup3)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup4(String additionalMaterialGroup4)` Constraints: Not nullable, Maximum length: 3
`void`	`setAdditionalMaterialGroup5(String additionalMaterialGroup5)` Constraints: Not nullable, Maximum length: 3
`void`	`setBaseUnit(String baseUnit)` Constraints: Not nullable, Maximum length: 3 You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.
`void`	`setBatch(String batch)` Constraints: Not nullable, Maximum length: 10
`void`	`setBillingDocument(BillingDocument value)` Overwrites the associated BillingDocument entity for the loaded navigation property to_BillingDocument.
`void`	`setBillingDocument(String value)` (Key Field) Constraints: Not nullable, Maximum length: 10
`void`	`setBillingDocumentItem(String billingDocumentItem)` (Key Field) Constraints: Not nullable, Maximum length: 6
`void`	`setBillingDocumentItemInPartSgmt(String billingDocumentItemInPartSgmt)` Constraints: Not nullable, Maximum length: 6
`void`	`setBillingDocumentItemText(String billingDocumentItemText)` Constraints: Not nullable, Maximum length: 40 Short texts are used throughout sales order processing, shipping, and billing.
`void`	`setBillingPlan(String billingPlan)` Constraints: Not nullable, Maximum length: 10
`void`	`setBillingPlanItem(String billingPlanItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setBillingPlanRule(String billingPlanRule)` Constraints: Not nullable, Maximum length: 1 Billing plan for a rental contract for a piece of machinery Billing dates: First of the month for 12 months Billing amount: 1000 USD per month Each date requires a billing rule which determines this fixed amount as the amount to be billed.
`void`	`setBillingQuantity(BigDecimal billingQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBillingQuantityInBaseUnit(BigDecimal billingQuantityInBaseUnit)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setBillingQuantityUnit(String billingQuantityUnit)` Constraints: Not nullable, Maximum length: 3
`void`	`setBillingToBaseQuantityDnmntr(BigDecimal billingToBaseQuantityDnmntr)` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`void`	`setBillingToBaseQuantityNmrtr(BigDecimal billingToBaseQuantityNmrtr)` Constraints: Not nullable, Precision: 5, Scale: 0 Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles.
`void`	`setBillToPartyCountry(String billToPartyCountry)` Constraints: Not nullable, Maximum length: 3
`void`	`setBillToPartyRegion(String billToPartyRegion)` Constraints: Not nullable, Maximum length: 3
`void`	`setBOMExplosion(String bOMExplosion)` Constraints: Not nullable, Maximum length: 8
`void`	`setBusinessArea(String businessArea)` Constraints: Not nullable, Maximum length: 4
`void`	`setCashDiscountIsDeductible(Boolean cashDiscountIsDeductible)` Constraints: none
`void`	`setControllingArea(String controllingArea)` Constraints: Not nullable, Maximum length: 4 The controlling area is the highest organizational unit in Controlling.
`void`	`setCostAmount(BigDecimal costAmount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setCostCenter(String costCenter)` Constraints: Not nullable, Maximum length: 10
`void`	`setCreatedByUser(String createdByUser)` Constraints: Not nullable, Maximum length: 12
`void`	`setCreationDate(Calendar creationDate)` Constraints: Not nullable, Precision: 0
`void`	`setCreationTime(Calendar creationTime)` Constraints: Not nullable, Precision: 0
`void`	`setCreditRelatedPrice(BigDecimal creditRelatedPrice)` Constraints: Not nullable, Precision: 12, Scale: 3 The system multiplies the price you specify (for example, the net price) by the item quantity of an open sales, shipping, or billing document to calculate the value for credit management purposes.
`void`	`setCustomerConditionGroup1(String customerConditionGroup1)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerConditionGroup2(String customerConditionGroup2)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerConditionGroup3(String customerConditionGroup3)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerConditionGroup4(String customerConditionGroup4)` Constraints: Not nullable, Maximum length: 2
`void`	`setCustomerConditionGroup5(String customerConditionGroup5)` Constraints: Not nullable, Maximum length: 2
`void`	`setDepartureCountry(String departureCountry)` Constraints: Not nullable, Maximum length: 3 You can define the country key in a table.
`void`	`setDivision(String division)` Constraints: Not nullable, Maximum length: 2 A product or service is always assigned to just one division.
`void`	`setEligibleAmountForCashDiscount(BigDecimal eligibleAmountForCashDiscount)` Constraints: Not nullable, Precision: 14, Scale: 3 During document entry, the amount qualifying for cash discount can be determined manually or automatically.
`void`	`setErpConfigContext(ErpConfigContext erpConfigContext)` Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
`void`	`setExternalReferenceDocument(String externalReferenceDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setExternalReferenceDocumentItem(String externalReferenceDocumentItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setGrossAmount(BigDecimal grossAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setHigherLevelItem(String higherLevelItem)` Constraints: Not nullable, Maximum length: 6 Items can be organized hierarchically.
`void`	`setHigherLevelItemUsage(String higherLevelItemUsage)` Constraints: Not nullable, Maximum length: 1
`void`	`setInternationalArticleNumber(String internationalArticleNumber)` Constraints: Not nullable, Maximum length: 18
`void`	`setItemGrossWeight(BigDecimal itemGrossWeight)` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order.
`void`	`setItemIsRelevantForCredit(Boolean itemIsRelevantForCredit)` Constraints: noneSelect this field if the values of the item type in the total liability are to be updated.
`void`	`setItemNetWeight(BigDecimal itemNetWeight)` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order.
`void`	`setItemVolume(BigDecimal itemVolume)` Constraints: Not nullable, Precision: 15, Scale: 3 The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order.
`void`	`setItemVolumeUnit(String itemVolumeUnit)` Constraints: Not nullable, Maximum length: 3 If you specify a volume, you have to enter the corresponding volume unit here.
`void`	`setItemWeightUnit(String itemWeightUnit)` Constraints: Not nullable, Maximum length: 3 If you specify a weight, you must enter the corresponding unit of weight here.
`void`	`setMainItemMaterialPricingGroup(String mainItemMaterialPricingGroup)` Constraints: Not nullable, Maximum length: 2 You can create price conditions for a material pricing group (for example, non-food products) a combination of customer and material pricing group a combination of price group and material pricing group (for example, wholesale customers and all non-food products)
`void`	`setMainItemPricingRefMaterial(String mainItemPricingRefMaterial)` Constraints: Not nullable, Maximum length: 40 The pricing reference material is stored in the master record of the main item material.
`void`	`setManualPriceChangeType(String manualPriceChangeType)` Constraints: Not nullable, Maximum length: 1
`void`	`setMaterial(String material)` Constraints: Not nullable, Maximum length: 40
`void`	`setMaterialCommissionGroup(String materialCommissionGroup)` Constraints: Not nullable, Maximum length: 2 You can assign two materials to the same commission group as long as each representative who sells these materials receives the same commission percentage for both materials.
`void`	`setMaterialDeterminationType(String materialDeterminationType)` Constraints: Not nullable, Maximum length: 1
`void`	`setMaterialGroup(String materialGroup)` Constraints: Not nullable, Maximum length: 9 You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
`void`	`setMaterialGroupHierarchy1(String materialGroupHierarchy1)` Constraints: Not nullable, Maximum length: 18 Material group hierarchy levels can be put together into groups.
`void`	`setMaterialGroupHierarchy2(String materialGroupHierarchy2)` Constraints: Not nullable, Maximum length: 18 Material group hierarchy levels can be put together into groups.
`void`	`setMaterialPricingGroup(String materialPricingGroup)` Constraints: Not nullable, Maximum length: 2 You can create condition records for a material price group using the following condition types: Material price group (for example, all non-food products) A combination of customer and material price group A combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
`void`	`setMatlAccountAssignmentGroup(String matlAccountAssignmentGroup)` Constraints: Not nullable, Maximum length: 2 Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
`void`	`setMRPRequiredQuantityInBaseUnit(BigDecimal mRPRequiredQuantityInBaseUnit)` Constraints: Not nullable, Precision: 13, Scale: 3 The system uses this quantity during the availability check to guarantee that the confirmed quantity cannot be used for another sales order.
`void`	`setNetAmount(BigDecimal netAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`void`	`setOrderID(String orderID)` Constraints: Not nullable, Maximum length: 12
`void`	`setOrganizationDivision(String organizationDivision)` Constraints: Not nullable, Maximum length: 2
`void`	`setOriginallyRequestedMaterial(String originallyRequestedMaterial)` Constraints: Not nullable, Maximum length: 40 If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
`void`	`setOriginSDDocument(String originSDDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setOriginSDDocumentItem(String originSDDocumentItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setPartner(List<BillingDocumentItemPartner> value)` Overwrites the list of associated BillingDocumentItemPartner entities for the loaded navigation property to_Partner.
`void`	`setPlant(String plant)` Constraints: Not nullable, Maximum length: 4
`void`	`setPlantCity(String plantCity)` Constraints: Not nullable, Maximum length: 4
`void`	`setPlantCounty(String plantCounty)` Constraints: Not nullable, Maximum length: 3
`void`	`setPlantRegion(String plantRegion)` Constraints: Not nullable, Maximum length: 3
`void`	`setPricingDate(Calendar pricingDate)` Constraints: Not nullable, Precision: 0 You can use the pricing date as a selection criterion when you process billing documents collectively.
`void`	`setPricingElement(List<BillingDocumentItemPrcgElmnt> value)` Overwrites the list of associated BillingDocumentItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
`void`	`setPricingReferenceMaterial(String pricingReferenceMaterial)` Constraints: Not nullable, Maximum length: 40 The conditions that apply to the pricing reference material also apply to the material in whose material master record the pricing reference material is stored.
`void`	`setPricingScaleQuantityInBaseUnit(BigDecimal pricingScaleQuantityInBaseUnit)` Constraints: Not nullable, Precision: 13, Scale: 3
`void`	`setProductHierarchyNode(String productHierarchyNode)` Constraints: Not nullable, Maximum length: 18 In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.
`void`	`setProductTaxClassification1(String productTaxClassification1)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification2(String productTaxClassification2)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification3(String productTaxClassification3)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification4(String productTaxClassification4)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification5(String productTaxClassification5)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification6(String productTaxClassification6)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification7(String productTaxClassification7)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification8(String productTaxClassification8)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProductTaxClassification9(String productTaxClassification9)` Constraints: Not nullable, Maximum length: 1 The system copies the tax classification from the tax information stored in the material master record.
`void`	`setProfitabilitySegment(String profitabilitySegment)` Constraints: Not nullable, Maximum length: 10 Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
`void`	`setProfitCenter(String profitCenter)` Constraints: Not nullable, Maximum length: 10
`void`	`setRebateBasisAmount(BigDecimal rebateBasisAmount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setReferenceSDDocument(String referenceSDDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setReferenceSDDocumentCategory(String referenceSDDocumentCategory)` Constraints: Not nullable, Maximum length: 4
`void`	`setReferenceSDDocumentItem(String referenceSDDocumentItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setReplacementPartType(String replacementPartType)` Constraints: Not nullable, Maximum length: 1 The SD billing application uses this indicator to disclose used-parts VAT.
`void`	`setRetailPromotion(String retailPromotion)` Constraints: Not nullable, Maximum length: 10 For each item of a purchasing document, you can specify the promotion to which the item belongs.
`void`	`setReturnItemProcessingType(String returnItemProcessingType)` Constraints: Not nullable, Maximum length: 1
`void`	`setSalesDeal(String salesDeal)` Constraints: Not nullable, Maximum length: 10 When creating a new sales deal, you can either enter a number manually or let the system automatically assign an internal number.
`void`	`setSalesDocIsCreatedFromReference(Boolean salesDocIsCreatedFromReference)` Constraints: noneYou create a sales order from a quotation.
`void`	`setSalesDocument(String salesDocument)` Constraints: Not nullable, Maximum length: 10
`void`	`setSalesDocumentItem(String salesDocumentItem)` Constraints: Not nullable, Maximum length: 6
`void`	`setSalesDocumentItemCategory(String salesDocumentItemCategory)` Constraints: Not nullable, Maximum length: 4 The system proposes an item category.
`void`	`setSalesDocumentItemType(String salesDocumentItemType)` Constraints: Not nullable, Maximum length: 1 The system processes items that refer to a specific material differently than items that do not refer to a material.
`void`	`setSalesGroup(String salesGroup)` Constraints: Not nullable, Maximum length: 3 By using sales groups you can designate different areas of responsibility within a sales office.
`void`	`setSalesOffice(String salesOffice)` Constraints: Not nullable, Maximum length: 4 When you create sales statistics, you can use a sales office as one of the selection criteria.
`void`	`setSalesOrderCustomerGroup(String salesOrderCustomerGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setSalesOrderCustomerPriceGroup(String salesOrderCustomerPriceGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setSalesOrderDistributionChannel(String salesOrderDistributionChannel)` Constraints: Not nullable, Maximum length: 2
`void`	`setSalesOrderPriceListType(String salesOrderPriceListType)` Constraints: Not nullable, Maximum length: 2
`void`	`setSalesOrderSalesDistrict(String salesOrderSalesDistrict)` Constraints: Not nullable, Maximum length: 6
`void`	`setSalesOrderSalesOrganization(String salesOrderSalesOrganization)` Constraints: Not nullable, Maximum length: 4 When you create condition records to define prices for inter-company billing, you specify the sales organization that is responsible for processing the sales order.
`void`	`setSalesPromotion(String salesPromotion)` Constraints: Not nullable, Maximum length: 10 When creating a new promotion, you can either enter a number manually or let the system automatically assign an internal number.
`void`	`setSalesSDDocumentCategory(String salesSDDocumentCategory)` Constraints: Not nullable, Maximum length: 4 The document category determines how the system stores and keeps track of document data.
`void`	`setSDDocumentReason(String sDDocumentReason)` Constraints: Not nullable, Maximum length: 3 You can freely define order reasons according to the needs of your organization.
`void`	`setServicesRenderedDate(Calendar servicesRenderedDate)` Constraints: Not nullable, Precision: 0 If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field.
`void`	`setShippingPoint(String shippingPoint)` Constraints: Not nullable, Maximum length: 4 You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.
`void`	`setStatisticalValueControl(String statisticalValueControl)` Constraints: Not nullable, Maximum length: 1
`void`	`setStorageLocation(String storageLocation)` Constraints: Not nullable, Maximum length: 4
`void`	`setSubtotal1Amount(BigDecimal subtotal1Amount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setSubtotal2Amount(BigDecimal subtotal2Amount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setSubtotal3Amount(BigDecimal subtotal3Amount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setSubtotal4Amount(BigDecimal subtotal4Amount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setSubtotal5Amount(BigDecimal subtotal5Amount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setSubtotal6Amount(BigDecimal subtotal6Amount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setTaxAmount(BigDecimal taxAmount)` Constraints: Not nullable, Precision: 14, Scale: 3
`void`	`setTaxJurisdiction(String taxJurisdiction)` Constraints: Not nullable, Maximum length: 15
`void`	`setTransactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5 The system proposes the document currency from the customer master record of the sold-to party.
`void`	`setVolumeRebateGroup(String volumeRebateGroup)` Constraints: Not nullable, Maximum length: 2
`void`	`setWBSElement(String wBSElement)` Constraints: Not nullable, Maximum length: 24
`void`	`setZeroVATRsn(String zeroVATRsn)` Constraints: Not nullable, Maximum length: 1 the tax purposes.
`String`	`toString()`

Methods inherited from class com.sap.cloud.sdk.s4hana.datamodel.odata.helper.VdmObject
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField

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

- Field Detail
  - ALL_FIELDS
```
public static final BillingDocumentItemSelectable ALL_FIELDS
```
    Selector for all available fields of BillingDocumentItem.
  - BILLING_DOCUMENT
```
public static final BillingDocumentItemField<String> BILLING_DOCUMENT
```
    Use with available fluent helpers to apply the BillingDocument field to query operations.
  - BILLING_DOCUMENT_ITEM
```
public static final BillingDocumentItemField<String> BILLING_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the BillingDocumentItem field to query operations.
  - SALES_DOCUMENT_ITEM_CATEGORY
```
public static final BillingDocumentItemField<String> SALES_DOCUMENT_ITEM_CATEGORY
```
    Use with available fluent helpers to apply the SalesDocumentItemCategory field to query operations.
  - SALES_DOCUMENT_ITEM_TYPE
```
public static final BillingDocumentItemField<String> SALES_DOCUMENT_ITEM_TYPE
```
    Use with available fluent helpers to apply the SalesDocumentItemType field to query operations.
  - RETURN_ITEM_PROCESSING_TYPE
```
public static final BillingDocumentItemField<String> RETURN_ITEM_PROCESSING_TYPE
```
    Use with available fluent helpers to apply the ReturnItemProcessingType field to query operations.
  - CREATED_BY_USER
```
public static final BillingDocumentItemField<String> CREATED_BY_USER
```
    Use with available fluent helpers to apply the CreatedByUser field to query operations.
  - CREATION_DATE
```
public static final BillingDocumentItemField<Calendar> CREATION_DATE
```
    Use with available fluent helpers to apply the CreationDate field to query operations.
  - CREATION_TIME
```
public static final BillingDocumentItemField<Calendar> CREATION_TIME
```
    Use with available fluent helpers to apply the CreationTime field to query operations.
  - ORGANIZATION_DIVISION
```
public static final BillingDocumentItemField<String> ORGANIZATION_DIVISION
```
    Use with available fluent helpers to apply the OrganizationDivision field to query operations.
  - DIVISION
```
public static final BillingDocumentItemField<String> DIVISION
```
    Use with available fluent helpers to apply the Division field to query operations.
  - SALES_OFFICE
```
public static final BillingDocumentItemField<String> SALES_OFFICE
```
    Use with available fluent helpers to apply the SalesOffice field to query operations.
  - MATERIAL
```
public static final BillingDocumentItemField<String> MATERIAL
```
    Use with available fluent helpers to apply the Material field to query operations.
  - ORIGINALLY_REQUESTED_MATERIAL
```
public static final BillingDocumentItemField<String> ORIGINALLY_REQUESTED_MATERIAL
```
    Use with available fluent helpers to apply the OriginallyRequestedMaterial field to query operations.
  - INTERNATIONAL_ARTICLE_NUMBER
```
public static final BillingDocumentItemField<String> INTERNATIONAL_ARTICLE_NUMBER
```
    Use with available fluent helpers to apply the InternationalArticleNumber field to query operations.
  - PRICING_REFERENCE_MATERIAL
```
public static final BillingDocumentItemField<String> PRICING_REFERENCE_MATERIAL
```
    Use with available fluent helpers to apply the PricingReferenceMaterial field to query operations.
  - BATCH
```
public static final BillingDocumentItemField<String> BATCH
```
    Use with available fluent helpers to apply the Batch field to query operations.
  - PRODUCT_HIERARCHY_NODE
```
public static final BillingDocumentItemField<String> PRODUCT_HIERARCHY_NODE
```
    Use with available fluent helpers to apply the ProductHierarchyNode field to query operations.
  - MATERIAL_GROUP
```
public static final BillingDocumentItemField<String> MATERIAL_GROUP
```
    Use with available fluent helpers to apply the MaterialGroup field to query operations.
  - ADDITIONAL_MATERIAL_GROUP1
```
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP1
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup1 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP2
```
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP2
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup2 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP3
```
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP3
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup3 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP4
```
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP4
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup4 field to query operations.
  - ADDITIONAL_MATERIAL_GROUP5
```
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP5
```
    Use with available fluent helpers to apply the AdditionalMaterialGroup5 field to query operations.
  - MATERIAL_COMMISSION_GROUP
```
public static final BillingDocumentItemField<String> MATERIAL_COMMISSION_GROUP
```
    Use with available fluent helpers to apply the MaterialCommissionGroup field to query operations.
  - PLANT
```
public static final BillingDocumentItemField<String> PLANT
```
    Use with available fluent helpers to apply the Plant field to query operations.
  - STORAGE_LOCATION
```
public static final BillingDocumentItemField<String> STORAGE_LOCATION
```
    Use with available fluent helpers to apply the StorageLocation field to query operations.
  - REPLACEMENT_PART_TYPE
```
public static final BillingDocumentItemField<String> REPLACEMENT_PART_TYPE
```
    Use with available fluent helpers to apply the ReplacementPartType field to query operations.
  - MATERIAL_GROUP_HIERARCHY1
```
public static final BillingDocumentItemField<String> MATERIAL_GROUP_HIERARCHY1
```
    Use with available fluent helpers to apply the MaterialGroupHierarchy1 field to query operations.
  - MATERIAL_GROUP_HIERARCHY2
```
public static final BillingDocumentItemField<String> MATERIAL_GROUP_HIERARCHY2
```
    Use with available fluent helpers to apply the MaterialGroupHierarchy2 field to query operations.
  - PLANT_REGION
```
public static final BillingDocumentItemField<String> PLANT_REGION
```
    Use with available fluent helpers to apply the PlantRegion field to query operations.
  - PLANT_COUNTY
```
public static final BillingDocumentItemField<String> PLANT_COUNTY
```
    Use with available fluent helpers to apply the PlantCounty field to query operations.
  - PLANT_CITY
```
public static final BillingDocumentItemField<String> PLANT_CITY
```
    Use with available fluent helpers to apply the PlantCity field to query operations.
  - BOM_EXPLOSION
```
public static final BillingDocumentItemField<String> BOM_EXPLOSION
```
    Use with available fluent helpers to apply the BOMExplosion field to query operations.
  - MATERIAL_DETERMINATION_TYPE
```
public static final BillingDocumentItemField<String> MATERIAL_DETERMINATION_TYPE
```
    Use with available fluent helpers to apply the MaterialDeterminationType field to query operations.
  - BILLING_DOCUMENT_ITEM_TEXT
```
public static final BillingDocumentItemField<String> BILLING_DOCUMENT_ITEM_TEXT
```
    Use with available fluent helpers to apply the BillingDocumentItemText field to query operations.
  - SERVICES_RENDERED_DATE
```
public static final BillingDocumentItemField<Calendar> SERVICES_RENDERED_DATE
```
    Use with available fluent helpers to apply the ServicesRenderedDate field to query operations.
  - BILLING_QUANTITY
```
public static final BillingDocumentItemField<BigDecimal> BILLING_QUANTITY
```
    Use with available fluent helpers to apply the BillingQuantity field to query operations.
  - BILLING_QUANTITY_UNIT
```
public static final BillingDocumentItemField<String> BILLING_QUANTITY_UNIT
```
    Use with available fluent helpers to apply the BillingQuantityUnit field to query operations.
  - BILLING_QUANTITY_IN_BASE_UNIT
```
public static final BillingDocumentItemField<BigDecimal> BILLING_QUANTITY_IN_BASE_UNIT
```
    Use with available fluent helpers to apply the BillingQuantityInBaseUnit field to query operations.
  - BASE_UNIT
```
public static final BillingDocumentItemField<String> BASE_UNIT
```
    Use with available fluent helpers to apply the BaseUnit field to query operations.
  - MRP_REQUIRED_QUANTITY_IN_BASE_UNIT
```
public static final BillingDocumentItemField<BigDecimal> MRP_REQUIRED_QUANTITY_IN_BASE_UNIT
```
    Use with available fluent helpers to apply the MRPRequiredQuantityInBaseUnit field to query operations.
  - BILLING_TO_BASE_QUANTITY_DNMNTR
```
public static final BillingDocumentItemField<BigDecimal> BILLING_TO_BASE_QUANTITY_DNMNTR
```
    Use with available fluent helpers to apply the BillingToBaseQuantityDnmntr field to query operations.
  - BILLING_TO_BASE_QUANTITY_NMRTR
```
public static final BillingDocumentItemField<BigDecimal> BILLING_TO_BASE_QUANTITY_NMRTR
```
    Use with available fluent helpers to apply the BillingToBaseQuantityNmrtr field to query operations.
  - ITEM_GROSS_WEIGHT
```
public static final BillingDocumentItemField<BigDecimal> ITEM_GROSS_WEIGHT
```
    Use with available fluent helpers to apply the ItemGrossWeight field to query operations.
  - ITEM_NET_WEIGHT
```
public static final BillingDocumentItemField<BigDecimal> ITEM_NET_WEIGHT
```
    Use with available fluent helpers to apply the ItemNetWeight field to query operations.
  - ITEM_WEIGHT_UNIT
```
public static final BillingDocumentItemField<String> ITEM_WEIGHT_UNIT
```
    Use with available fluent helpers to apply the ItemWeightUnit field to query operations.
  - ITEM_VOLUME
```
public static final BillingDocumentItemField<BigDecimal> ITEM_VOLUME
```
    Use with available fluent helpers to apply the ItemVolume field to query operations.
  - ITEM_VOLUME_UNIT
```
public static final BillingDocumentItemField<String> ITEM_VOLUME_UNIT
```
    Use with available fluent helpers to apply the ItemVolumeUnit field to query operations.
  - BILL_TO_PARTY_COUNTRY
```
public static final BillingDocumentItemField<String> BILL_TO_PARTY_COUNTRY
```
    Use with available fluent helpers to apply the BillToPartyCountry field to query operations.
  - BILL_TO_PARTY_REGION
```
public static final BillingDocumentItemField<String> BILL_TO_PARTY_REGION
```
    Use with available fluent helpers to apply the BillToPartyRegion field to query operations.
  - BILLING_PLAN_RULE
```
public static final BillingDocumentItemField<String> BILLING_PLAN_RULE
```
    Use with available fluent helpers to apply the BillingPlanRule field to query operations.
  - BILLING_PLAN
```
public static final BillingDocumentItemField<String> BILLING_PLAN
```
    Use with available fluent helpers to apply the BillingPlan field to query operations.
  - BILLING_PLAN_ITEM
```
public static final BillingDocumentItemField<String> BILLING_PLAN_ITEM
```
    Use with available fluent helpers to apply the BillingPlanItem field to query operations.
  - NET_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> NET_AMOUNT
```
    Use with available fluent helpers to apply the NetAmount field to query operations.
  - TRANSACTION_CURRENCY
```
public static final BillingDocumentItemField<String> TRANSACTION_CURRENCY
```
    Use with available fluent helpers to apply the TransactionCurrency field to query operations.
  - GROSS_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> GROSS_AMOUNT
```
    Use with available fluent helpers to apply the GrossAmount field to query operations.
  - PRICING_DATE
```
public static final BillingDocumentItemField<Calendar> PRICING_DATE
```
    Use with available fluent helpers to apply the PricingDate field to query operations.
  - PRICING_SCALE_QUANTITY_IN_BASE_UNIT
```
public static final BillingDocumentItemField<BigDecimal> PRICING_SCALE_QUANTITY_IN_BASE_UNIT
```
    Use with available fluent helpers to apply the PricingScaleQuantityInBaseUnit field to query operations.
  - TAX_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> TAX_AMOUNT
```
    Use with available fluent helpers to apply the TaxAmount field to query operations.
  - COST_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> COST_AMOUNT
```
    Use with available fluent helpers to apply the CostAmount field to query operations.
  - SUBTOTAL1_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL1_AMOUNT
```
    Use with available fluent helpers to apply the Subtotal1Amount field to query operations.
  - SUBTOTAL2_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL2_AMOUNT
```
    Use with available fluent helpers to apply the Subtotal2Amount field to query operations.
  - SUBTOTAL3_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL3_AMOUNT
```
    Use with available fluent helpers to apply the Subtotal3Amount field to query operations.
  - SUBTOTAL4_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL4_AMOUNT
```
    Use with available fluent helpers to apply the Subtotal4Amount field to query operations.
  - SUBTOTAL5_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL5_AMOUNT
```
    Use with available fluent helpers to apply the Subtotal5Amount field to query operations.
  - SUBTOTAL6_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL6_AMOUNT
```
    Use with available fluent helpers to apply the Subtotal6Amount field to query operations.
  - STATISTICAL_VALUE_CONTROL
```
public static final BillingDocumentItemField<String> STATISTICAL_VALUE_CONTROL
```
    Use with available fluent helpers to apply the StatisticalValueControl field to query operations.
  - CASH_DISCOUNT_IS_DEDUCTIBLE
```
public static final BillingDocumentItemField<Boolean> CASH_DISCOUNT_IS_DEDUCTIBLE
```
    Use with available fluent helpers to apply the CashDiscountIsDeductible field to query operations.
  - CUSTOMER_CONDITION_GROUP1
```
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP1
```
    Use with available fluent helpers to apply the CustomerConditionGroup1 field to query operations.
  - CUSTOMER_CONDITION_GROUP2
```
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP2
```
    Use with available fluent helpers to apply the CustomerConditionGroup2 field to query operations.
  - CUSTOMER_CONDITION_GROUP3
```
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP3
```
    Use with available fluent helpers to apply the CustomerConditionGroup3 field to query operations.
  - CUSTOMER_CONDITION_GROUP4
```
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP4
```
    Use with available fluent helpers to apply the CustomerConditionGroup4 field to query operations.
  - CUSTOMER_CONDITION_GROUP5
```
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP5
```
    Use with available fluent helpers to apply the CustomerConditionGroup5 field to query operations.
  - MANUAL_PRICE_CHANGE_TYPE
```
public static final BillingDocumentItemField<String> MANUAL_PRICE_CHANGE_TYPE
```
    Use with available fluent helpers to apply the ManualPriceChangeType field to query operations.
  - MATERIAL_PRICING_GROUP
```
public static final BillingDocumentItemField<String> MATERIAL_PRICING_GROUP
```
    Use with available fluent helpers to apply the MaterialPricingGroup field to query operations.
  - MAIN_ITEM_PRICING_REF_MATERIAL
```
public static final BillingDocumentItemField<String> MAIN_ITEM_PRICING_REF_MATERIAL
```
    Use with available fluent helpers to apply the MainItemPricingRefMaterial field to query operations.
  - MAIN_ITEM_MATERIAL_PRICING_GROUP
```
public static final BillingDocumentItemField<String> MAIN_ITEM_MATERIAL_PRICING_GROUP
```
    Use with available fluent helpers to apply the MainItemMaterialPricingGroup field to query operations.
  - DEPARTURE_COUNTRY
```
public static final BillingDocumentItemField<String> DEPARTURE_COUNTRY
```
    Use with available fluent helpers to apply the DepartureCountry field to query operations.
  - TAX_JURISDICTION
```
public static final BillingDocumentItemField<String> TAX_JURISDICTION
```
    Use with available fluent helpers to apply the TaxJurisdiction field to query operations.
  - PRODUCT_TAX_CLASSIFICATION1
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION1
```
    Use with available fluent helpers to apply the ProductTaxClassification1 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION2
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION2
```
    Use with available fluent helpers to apply the ProductTaxClassification2 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION3
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION3
```
    Use with available fluent helpers to apply the ProductTaxClassification3 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION4
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION4
```
    Use with available fluent helpers to apply the ProductTaxClassification4 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION5
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION5
```
    Use with available fluent helpers to apply the ProductTaxClassification5 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION6
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION6
```
    Use with available fluent helpers to apply the ProductTaxClassification6 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION7
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION7
```
    Use with available fluent helpers to apply the ProductTaxClassification7 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION8
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION8
```
    Use with available fluent helpers to apply the ProductTaxClassification8 field to query operations.
  - PRODUCT_TAX_CLASSIFICATION9
```
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION9
```
    Use with available fluent helpers to apply the ProductTaxClassification9 field to query operations.
  - ZERO_VAT_RSN
```
public static final BillingDocumentItemField<String> ZERO_VAT_RSN
```
    Use with available fluent helpers to apply the ZeroVATRsn field to query operations.
  - ELIGIBLE_AMOUNT_FOR_CASH_DISCOUNT
```
public static final BillingDocumentItemField<BigDecimal> ELIGIBLE_AMOUNT_FOR_CASH_DISCOUNT
```
    Use with available fluent helpers to apply the EligibleAmountForCashDiscount field to query operations.
  - BUSINESS_AREA
```
public static final BillingDocumentItemField<String> BUSINESS_AREA
```
    Use with available fluent helpers to apply the BusinessArea field to query operations.
  - PROFIT_CENTER
```
public static final BillingDocumentItemField<String> PROFIT_CENTER
```
    Use with available fluent helpers to apply the ProfitCenter field to query operations.
  - WBS_ELEMENT
```
public static final BillingDocumentItemField<String> WBS_ELEMENT
```
    Use with available fluent helpers to apply the WBSElement field to query operations.
  - CONTROLLING_AREA
```
public static final BillingDocumentItemField<String> CONTROLLING_AREA
```
    Use with available fluent helpers to apply the ControllingArea field to query operations.
  - PROFITABILITY_SEGMENT
```
public static final BillingDocumentItemField<String> PROFITABILITY_SEGMENT
```
    Use with available fluent helpers to apply the ProfitabilitySegment field to query operations.
  - ORDER_ID
```
public static final BillingDocumentItemField<String> ORDER_ID
```
    Use with available fluent helpers to apply the OrderID field to query operations.
  - COST_CENTER
```
public static final BillingDocumentItemField<String> COST_CENTER
```
    Use with available fluent helpers to apply the CostCenter field to query operations.
  - ORIGIN_SD_DOCUMENT
```
public static final BillingDocumentItemField<String> ORIGIN_SD_DOCUMENT
```
    Use with available fluent helpers to apply the OriginSDDocument field to query operations.
  - ORIGIN_SD_DOCUMENT_ITEM
```
public static final BillingDocumentItemField<String> ORIGIN_SD_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the OriginSDDocumentItem field to query operations.
  - MATL_ACCOUNT_ASSIGNMENT_GROUP
```
public static final BillingDocumentItemField<String> MATL_ACCOUNT_ASSIGNMENT_GROUP
```
    Use with available fluent helpers to apply the MatlAccountAssignmentGroup field to query operations.
  - REFERENCE_SD_DOCUMENT
```
public static final BillingDocumentItemField<String> REFERENCE_SD_DOCUMENT
```
    Use with available fluent helpers to apply the ReferenceSDDocument field to query operations.
  - REFERENCE_SD_DOCUMENT_ITEM
```
public static final BillingDocumentItemField<String> REFERENCE_SD_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the ReferenceSDDocumentItem field to query operations.
  - REFERENCE_SD_DOCUMENT_CATEGORY
```
public static final BillingDocumentItemField<String> REFERENCE_SD_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the ReferenceSDDocumentCategory field to query operations.
  - SALES_DOCUMENT
```
public static final BillingDocumentItemField<String> SALES_DOCUMENT
```
    Use with available fluent helpers to apply the SalesDocument field to query operations.
  - SALES_DOCUMENT_ITEM
```
public static final BillingDocumentItemField<String> SALES_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the SalesDocumentItem field to query operations.
  - SALES_SD_DOCUMENT_CATEGORY
```
public static final BillingDocumentItemField<String> SALES_SD_DOCUMENT_CATEGORY
```
    Use with available fluent helpers to apply the SalesSDDocumentCategory field to query operations.
  - HIGHER_LEVEL_ITEM
```
public static final BillingDocumentItemField<String> HIGHER_LEVEL_ITEM
```
    Use with available fluent helpers to apply the HigherLevelItem field to query operations.
  - BILLING_DOCUMENT_ITEM_IN_PART_SGMT
```
public static final BillingDocumentItemField<String> BILLING_DOCUMENT_ITEM_IN_PART_SGMT
```
    Use with available fluent helpers to apply the BillingDocumentItemInPartSgmt field to query operations.
  - EXTERNAL_REFERENCE_DOCUMENT
```
public static final BillingDocumentItemField<String> EXTERNAL_REFERENCE_DOCUMENT
```
    Use with available fluent helpers to apply the ExternalReferenceDocument field to query operations.
  - EXTERNAL_REFERENCE_DOCUMENT_ITEM
```
public static final BillingDocumentItemField<String> EXTERNAL_REFERENCE_DOCUMENT_ITEM
```
    Use with available fluent helpers to apply the ExternalReferenceDocumentItem field to query operations.
  - SALES_GROUP
```
public static final BillingDocumentItemField<String> SALES_GROUP
```
    Use with available fluent helpers to apply the SalesGroup field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP1
```
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP1
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup1 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP2
```
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP2
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup2 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP3
```
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP3
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup3 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP4
```
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP4
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup4 field to query operations.
  - ADDITIONAL_CUSTOMER_GROUP5
```
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP5
```
    Use with available fluent helpers to apply the AdditionalCustomerGroup5 field to query operations.
  - SD_DOCUMENT_REASON
```
public static final BillingDocumentItemField<String> SD_DOCUMENT_REASON
```
    Use with available fluent helpers to apply the SDDocumentReason field to query operations.
  - RETAIL_PROMOTION
```
public static final BillingDocumentItemField<String> RETAIL_PROMOTION
```
    Use with available fluent helpers to apply the RetailPromotion field to query operations.
  - REBATE_BASIS_AMOUNT
```
public static final BillingDocumentItemField<BigDecimal> REBATE_BASIS_AMOUNT
```
    Use with available fluent helpers to apply the RebateBasisAmount field to query operations.
  - VOLUME_REBATE_GROUP
```
public static final BillingDocumentItemField<String> VOLUME_REBATE_GROUP
```
    Use with available fluent helpers to apply the VolumeRebateGroup field to query operations.
  - ITEM_IS_RELEVANT_FOR_CREDIT
```
public static final BillingDocumentItemField<Boolean> ITEM_IS_RELEVANT_FOR_CREDIT
```
    Use with available fluent helpers to apply the ItemIsRelevantForCredit field to query operations.
  - CREDIT_RELATED_PRICE
```
public static final BillingDocumentItemField<BigDecimal> CREDIT_RELATED_PRICE
```
    Use with available fluent helpers to apply the CreditRelatedPrice field to query operations.
  - SALES_DEAL
```
public static final BillingDocumentItemField<String> SALES_DEAL
```
    Use with available fluent helpers to apply the SalesDeal field to query operations.
  - SALES_PROMOTION
```
public static final BillingDocumentItemField<String> SALES_PROMOTION
```
    Use with available fluent helpers to apply the SalesPromotion field to query operations.
  - SALES_ORDER_SALES_DISTRICT
```
public static final BillingDocumentItemField<String> SALES_ORDER_SALES_DISTRICT
```
    Use with available fluent helpers to apply the SalesOrderSalesDistrict field to query operations.
  - SALES_ORDER_CUSTOMER_GROUP
```
public static final BillingDocumentItemField<String> SALES_ORDER_CUSTOMER_GROUP
```
    Use with available fluent helpers to apply the SalesOrderCustomerGroup field to query operations.
  - SALES_ORDER_CUSTOMER_PRICE_GROUP
```
public static final BillingDocumentItemField<String> SALES_ORDER_CUSTOMER_PRICE_GROUP
```
    Use with available fluent helpers to apply the SalesOrderCustomerPriceGroup field to query operations.
  - SALES_ORDER_PRICE_LIST_TYPE
```
public static final BillingDocumentItemField<String> SALES_ORDER_PRICE_LIST_TYPE
```
    Use with available fluent helpers to apply the SalesOrderPriceListType field to query operations.
  - SALES_ORDER_SALES_ORGANIZATION
```
public static final BillingDocumentItemField<String> SALES_ORDER_SALES_ORGANIZATION
```
    Use with available fluent helpers to apply the SalesOrderSalesOrganization field to query operations.
  - SALES_ORDER_DISTRIBUTION_CHANNEL
```
public static final BillingDocumentItemField<String> SALES_ORDER_DISTRIBUTION_CHANNEL
```
    Use with available fluent helpers to apply the SalesOrderDistributionChannel field to query operations.
  - SALES_DOC_IS_CREATED_FROM_REFERENCE
```
public static final BillingDocumentItemField<Boolean> SALES_DOC_IS_CREATED_FROM_REFERENCE
```
    Use with available fluent helpers to apply the SalesDocIsCreatedFromReference field to query operations.
  - SHIPPING_POINT
```
public static final BillingDocumentItemField<String> SHIPPING_POINT
```
    Use with available fluent helpers to apply the ShippingPoint field to query operations.
  - HIGHER_LEVEL_ITEM_USAGE
```
public static final BillingDocumentItemField<String> HIGHER_LEVEL_ITEM_USAGE
```
    Use with available fluent helpers to apply the HigherLevelItemUsage field to query operations.
  - TO_BILLING_DOCUMENT
```
public static final BillingDocumentItemLink<BillingDocument> TO_BILLING_DOCUMENT
```
    Use with available fluent helpers to apply the to_BillingDocument navigation property to query operations.
  - TO_PARTNER
```
public static final BillingDocumentItemLink<BillingDocumentItemPartner> TO_PARTNER
```
    Use with available fluent helpers to apply the to_Partner navigation property to query operations.
  - TO_PRICING_ELEMENT
```
public static final BillingDocumentItemLink<BillingDocumentItemPrcgElmnt> TO_PRICING_ELEMENT
```
    Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
- Constructor Detail
  - BillingDocumentItem
```
public BillingDocumentItem()
```
  - BillingDocumentItem
```
public BillingDocumentItem(@Nullable
                           String billingDocument,
                           @Nullable
                           String billingDocumentItem,
                           @Nullable
                           String salesDocumentItemCategory,
                           @Nullable
                           String salesDocumentItemType,
                           @Nullable
                           String returnItemProcessingType,
                           @Nullable
                           String createdByUser,
                           @Nullable
                           Calendar creationDate,
                           @Nullable
                           Calendar creationTime,
                           @Nullable
                           String organizationDivision,
                           @Nullable
                           String division,
                           @Nullable
                           String salesOffice,
                           @Nullable
                           String material,
                           @Nullable
                           String originallyRequestedMaterial,
                           @Nullable
                           String internationalArticleNumber,
                           @Nullable
                           String pricingReferenceMaterial,
                           @Nullable
                           String batch,
                           @Nullable
                           String productHierarchyNode,
                           @Nullable
                           String materialGroup,
                           @Nullable
                           String additionalMaterialGroup1,
                           @Nullable
                           String additionalMaterialGroup2,
                           @Nullable
                           String additionalMaterialGroup3,
                           @Nullable
                           String additionalMaterialGroup4,
                           @Nullable
                           String additionalMaterialGroup5,
                           @Nullable
                           String materialCommissionGroup,
                           @Nullable
                           String plant,
                           @Nullable
                           String storageLocation,
                           @Nullable
                           String replacementPartType,
                           @Nullable
                           String materialGroupHierarchy1,
                           @Nullable
                           String materialGroupHierarchy2,
                           @Nullable
                           String plantRegion,
                           @Nullable
                           String plantCounty,
                           @Nullable
                           String plantCity,
                           @Nullable
                           String bOMExplosion,
                           @Nullable
                           String materialDeterminationType,
                           @Nullable
                           String billingDocumentItemText,
                           @Nullable
                           Calendar servicesRenderedDate,
                           @Nullable
                           BigDecimal billingQuantity,
                           @Nullable
                           String billingQuantityUnit,
                           @Nullable
                           BigDecimal billingQuantityInBaseUnit,
                           @Nullable
                           String baseUnit,
                           @Nullable
                           BigDecimal mRPRequiredQuantityInBaseUnit,
                           @Nullable
                           BigDecimal billingToBaseQuantityDnmntr,
                           @Nullable
                           BigDecimal billingToBaseQuantityNmrtr,
                           @Nullable
                           BigDecimal itemGrossWeight,
                           @Nullable
                           BigDecimal itemNetWeight,
                           @Nullable
                           String itemWeightUnit,
                           @Nullable
                           BigDecimal itemVolume,
                           @Nullable
                           String itemVolumeUnit,
                           @Nullable
                           String billToPartyCountry,
                           @Nullable
                           String billToPartyRegion,
                           @Nullable
                           String billingPlanRule,
                           @Nullable
                           String billingPlan,
                           @Nullable
                           String billingPlanItem,
                           @Nullable
                           BigDecimal netAmount,
                           @Nullable
                           String transactionCurrency,
                           @Nullable
                           BigDecimal grossAmount,
                           @Nullable
                           Calendar pricingDate,
                           @Nullable
                           BigDecimal pricingScaleQuantityInBaseUnit,
                           @Nullable
                           BigDecimal taxAmount,
                           @Nullable
                           BigDecimal costAmount,
                           @Nullable
                           BigDecimal subtotal1Amount,
                           @Nullable
                           BigDecimal subtotal2Amount,
                           @Nullable
                           BigDecimal subtotal3Amount,
                           @Nullable
                           BigDecimal subtotal4Amount,
                           @Nullable
                           BigDecimal subtotal5Amount,
                           @Nullable
                           BigDecimal subtotal6Amount,
                           @Nullable
                           String statisticalValueControl,
                           @Nullable
                           Boolean cashDiscountIsDeductible,
                           @Nullable
                           String customerConditionGroup1,
                           @Nullable
                           String customerConditionGroup2,
                           @Nullable
                           String customerConditionGroup3,
                           @Nullable
                           String customerConditionGroup4,
                           @Nullable
                           String customerConditionGroup5,
                           @Nullable
                           String manualPriceChangeType,
                           @Nullable
                           String materialPricingGroup,
                           @Nullable
                           String mainItemPricingRefMaterial,
                           @Nullable
                           String mainItemMaterialPricingGroup,
                           @Nullable
                           String departureCountry,
                           @Nullable
                           String taxJurisdiction,
                           @Nullable
                           String productTaxClassification1,
                           @Nullable
                           String productTaxClassification2,
                           @Nullable
                           String productTaxClassification3,
                           @Nullable
                           String productTaxClassification4,
                           @Nullable
                           String productTaxClassification5,
                           @Nullable
                           String productTaxClassification6,
                           @Nullable
                           String productTaxClassification7,
                           @Nullable
                           String productTaxClassification8,
                           @Nullable
                           String productTaxClassification9,
                           @Nullable
                           String zeroVATRsn,
                           @Nullable
                           BigDecimal eligibleAmountForCashDiscount,
                           @Nullable
                           String businessArea,
                           @Nullable
                           String profitCenter,
                           @Nullable
                           String wBSElement,
                           @Nullable
                           String controllingArea,
                           @Nullable
                           String profitabilitySegment,
                           @Nullable
                           String orderID,
                           @Nullable
                           String costCenter,
                           @Nullable
                           String originSDDocument,
                           @Nullable
                           String originSDDocumentItem,
                           @Nullable
                           String matlAccountAssignmentGroup,
                           @Nullable
                           String referenceSDDocument,
                           @Nullable
                           String referenceSDDocumentItem,
                           @Nullable
                           String referenceSDDocumentCategory,
                           @Nullable
                           String salesDocument,
                           @Nullable
                           String salesDocumentItem,
                           @Nullable
                           String salesSDDocumentCategory,
                           @Nullable
                           String higherLevelItem,
                           @Nullable
                           String billingDocumentItemInPartSgmt,
                           @Nullable
                           String externalReferenceDocument,
                           @Nullable
                           String externalReferenceDocumentItem,
                           @Nullable
                           String salesGroup,
                           @Nullable
                           String additionalCustomerGroup1,
                           @Nullable
                           String additionalCustomerGroup2,
                           @Nullable
                           String additionalCustomerGroup3,
                           @Nullable
                           String additionalCustomerGroup4,
                           @Nullable
                           String additionalCustomerGroup5,
                           @Nullable
                           String sDDocumentReason,
                           @Nullable
                           String retailPromotion,
                           @Nullable
                           BigDecimal rebateBasisAmount,
                           @Nullable
                           String volumeRebateGroup,
                           @Nullable
                           Boolean itemIsRelevantForCredit,
                           @Nullable
                           BigDecimal creditRelatedPrice,
                           @Nullable
                           String salesDeal,
                           @Nullable
                           String salesPromotion,
                           @Nullable
                           String salesOrderSalesDistrict,
                           @Nullable
                           String salesOrderCustomerGroup,
                           @Nullable
                           String salesOrderCustomerPriceGroup,
                           @Nullable
                           String salesOrderPriceListType,
                           @Nullable
                           String salesOrderSalesOrganization,
                           @Nullable
                           String salesOrderDistributionChannel,
                           @Nullable
                           Boolean salesDocIsCreatedFromReference,
                           @Nullable
                           String shippingPoint,
                           @Nullable
                           String higherLevelItemUsage,
                           @Nullable
                           ErpConfigContext erpConfigContext,
                           @Nullable
                           BillingDocument toBillingDocument,
                           List<BillingDocumentItemPartner> toPartner,
                           List<BillingDocumentItemPrcgElmnt> toPricingElement)
```
- Method Detail
  - getType
```
public Class<BillingDocumentItem> getType()
```
    Specified by:
    
    getType in class VdmObject<BillingDocumentItem>
    
    Returns:
    
    The class of this object.
  - field
```
public static <T> BillingDocumentItemField<T> field(String fieldName,
                                                    Class<T> fieldType)
```
    Use with available fluent helpers to apply an extension field to query operations.
    
    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.
  - fetchBillingDocument
```
public BillingDocument fetchBillingDocument()
                                     throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocument entity (one to one) associated with this entity. This corresponds to the OData navigation property to_BillingDocument.
    Please note: This method will not cache or persist the query results.
    
    Returns:
    
    The single associated BillingDocument entity, or null if an entity is not associated.
    
    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.
  - getBillingDocumentOrFetch
```
public BillingDocument getBillingDocumentOrFetch()
                                          throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocument entity (one to one).
    If the navigation property to_BillingDocument of a queried BillingDocumentItem 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 BillingDocument entity.
    
    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.
  - getBillingDocumentOrNull
```
public com.google.common.base.Optional<BillingDocument> getBillingDocumentOrNull()
```
    Retrieval of associated BillingDocument entity (one to one).
    If the navigation property to_BillingDocument for an entity BillingDocumentItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_BillingDocument is already loaded, the result will contain the BillingDocument entity. If not, a null value state is returned.
  - setBillingDocument
```
public void setBillingDocument(BillingDocument value)
```
    Overwrites the associated BillingDocument entity for the loaded navigation property to_BillingDocument.
    
    Parameters:
    
    value - New BillingDocument entity.
  - setBillingDocument
```
public void setBillingDocument(String value)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    value - billingDocument
  - fetchPartner
```
public List<BillingDocumentItemPartner> fetchPartner()
                                              throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocumentItemPartner 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 BillingDocumentItemPartner 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
```
public List<BillingDocumentItemPartner> getPartnerOrFetch()
                                                   throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocumentItemPartner entities (one to many).
    If the navigation property to_Partner of a queried BillingDocumentItem 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 BillingDocumentItemPartner 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.
  - getPartnerOrNull
```
public com.google.common.base.Optional<List<BillingDocumentItemPartner>> getPartnerOrNull()
```
    Retrieval of associated BillingDocumentItemPartner entities (one to many).
    If the navigation property to_Partner for an entity BillingDocumentItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_Partner is already loaded, the result will contain the BillingDocumentItemPartner entities. If not, a null value state is returned.
  - setPartner
```
public void setPartner(@NonNull
                       List<BillingDocumentItemPartner> value)
```
    Overwrites the list of associated BillingDocumentItemPartner entities for the loaded navigation property to_Partner.
    If the navigation property to_Partner of a queried BillingDocumentItem 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 BillingDocumentItemPartner entities.
  - addPartner
```
public void addPartner(BillingDocumentItemPartner... entity)
```
    Adds elements to the list of associated BillingDocumentItemPartner entities.
    If the navigation property to_Partner of a queried BillingDocumentItem 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 BillingDocumentItemPartner entities.
  - fetchPricingElement
```
public List<BillingDocumentItemPrcgElmnt> fetchPricingElement()
                                                       throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Fetches the BillingDocumentItemPrcgElmnt 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 BillingDocumentItemPrcgElmnt 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
```
public List<BillingDocumentItemPrcgElmnt> getPricingElementOrFetch()
                                                            throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
```
    Retrieval of associated BillingDocumentItemPrcgElmnt entities (one to many).
    If the navigation property to_PricingElement of a queried BillingDocumentItem 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 BillingDocumentItemPrcgElmnt 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.
  - getPricingElementOrNull
```
public com.google.common.base.Optional<List<BillingDocumentItemPrcgElmnt>> getPricingElementOrNull()
```
    Retrieval of associated BillingDocumentItemPrcgElmnt entities (one to many).
    If the navigation property to_PricingElement for an entity BillingDocumentItem has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
    
    Returns:
    
    If the information for navigation property to_PricingElement is already loaded, the result will contain the BillingDocumentItemPrcgElmnt entities. If not, a null value state is returned.
  - setPricingElement
```
public void setPricingElement(@NonNull
                              List<BillingDocumentItemPrcgElmnt> value)
```
    Overwrites the list of associated BillingDocumentItemPrcgElmnt entities for the loaded navigation property to_PricingElement.
    If the navigation property to_PricingElement of a queried BillingDocumentItem 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 BillingDocumentItemPrcgElmnt entities.
  - addPricingElement
```
public void addPricingElement(BillingDocumentItemPrcgElmnt... entity)
```
    Adds elements to the list of associated BillingDocumentItemPrcgElmnt entities.
    If the navigation property to_PricingElement of a queried BillingDocumentItem 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 BillingDocumentItemPrcgElmnt entities.
  - builder
```
public static BillingDocumentItem.BillingDocumentItemBuilder builder()
```
  - getBillingDocument
```
@Nullable
public String getBillingDocument()
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    The number that uniquely identifies the billing document (the invoice, for example).
  - getBillingDocumentItem
```
@Nullable
public String getBillingDocumentItem()
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    The number that uniquely identifies the item in the billing document.
  - getSalesDocumentItemCategory
```
@Nullable
public String getSalesDocumentItemCategory()
```
    Constraints: Not nullable, Maximum length: 4
    The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document. If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
    
    Returns:
    
    A classification that distinguishes between different types of item (for example, free of charge items and text items) and determines how the system processes the item.
  - getSalesDocumentItemType
```
@Nullable
public String getSalesDocumentItemType()
```
    Constraints: Not nullable, Maximum length: 1
    The system processes items that refer to a specific material differently than items that do not refer to a material. For example, text items do not require processing for pricing, taxes, and weight calculations.
    
    Returns:
    
    A way of classifying items that require different kinds of processing by the system.
  - getReturnItemProcessingType
```
@Nullable
public String getReturnItemProcessingType()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    This item is a returns item if the field is selected
  - getCreatedByUser
```
@Nullable
public String getCreatedByUser()
```
    Constraints: Not nullable, Maximum length: 12
    
    Returns:
    
    Name of Person Who Created Object
  - getCreationDate
```
@Nullable
public Calendar getCreationDate()
```
    Constraints: Not nullable, Precision: 0
    
    Returns:
    
    Date on Which Record Was Created
  - getCreationTime
```
@Nullable
public Calendar getCreationTime()
```
    Constraints: Not nullable, Precision: 0
    
    Returns:
    
    The time of day at which the document was posted and stored in the system.
  - getOrganizationDivision
```
@Nullable
public String getOrganizationDivision()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Division for order header
  - getDivision
```
@Nullable
public String getDivision()
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - getSalesOffice
```
@Nullable
public String getSalesOffice()
```
    Constraints: Not nullable, Maximum length: 4
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Returns:
    
    A physical location (for example, a branch office) that has responsibility for the sale of certain products or services within a given geographical area.
  - getMaterial
```
@Nullable
public String getMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    
    Returns:
    
    Alphanumeric key uniquely identifying the material.
  - getOriginallyRequestedMaterial
```
@Nullable
public String getOriginallyRequestedMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
    
    Returns:
    
    Material originally requested by the customer.
  - getInternationalArticleNumber
```
@Nullable
public String getInternationalArticleNumber()
```
    Constraints: Not nullable, Maximum length: 18
    
    Returns:
    
    Glossary definition
  - getPricingReferenceMaterial
```
@Nullable
public String getPricingReferenceMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    The conditions that apply to the pricing reference material also apply to the material in whose material master record the pricing reference material is stored. A pricing reference material must always have its own material master record.
    
    Returns:
    
    Material master record that the system uses as a reference for pricing purposes.
  - getBatch
```
@Nullable
public String getBatch()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Assigns a material that is manufactured in batches or production lots to a specific batch.
  - getProductHierarchyNode
```
@Nullable
public String getProductHierarchyNode()
```
    Constraints: Not nullable, Maximum length: 18
    In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters. Level Number of characters allowed 1 5 2 5 3 8 You define a product hierarchy with the following levels: Level Example Description 1 00005 Electrical goods 2 00003 Wet appliances 3 00000001 Washing machine In this case, a washing machine belongs to the product hierarchy 000050000300000001.
    
    Returns:
    
    Alphanumeric character string for grouping together materials by combining different characteristics. It is used for analyses and price determination.
  - getMaterialGroup
```
@Nullable
public String getMaterialGroup()
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Returns:
    
    Key that you use to group together several materials or services with the same attributes, and to assign them to a particular material group.
  - getAdditionalMaterialGroup1
```
@Nullable
public String getAdditionalMaterialGroup1()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup2
```
@Nullable
public String getAdditionalMaterialGroup2()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup3
```
@Nullable
public String getAdditionalMaterialGroup3()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup4
```
@Nullable
public String getAdditionalMaterialGroup4()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getAdditionalMaterialGroup5
```
@Nullable
public String getAdditionalMaterialGroup5()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    You can use material groups when maintaining a material master record. Since these material groups are not used in the standard SAP System, you can use them as required, for example, for analyses.
  - getMaterialCommissionGroup
```
@Nullable
public String getMaterialCommissionGroup()
```
    Constraints: Not nullable, Maximum length: 2
    You can assign two materials to the same commission group as long as each representative who sells these materials receives the same commission percentage for both materials. In other words, the commission percentages within a commission group are always the same for any one representative but may vary for different representatives. Material Rep. 1 Rep. 2 Rep. 3 A 5 % 10 % 11 % B 5 % 10 % 11 % Materials A and B are sold by these three representatives only. You can therefore assign them to the same commission group.
    
    Returns:
    
    Commission group to which the material is assigned.
  - getPlant
```
@Nullable
public String getPlant()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Key uniquely identifying a plant.
  - getStorageLocation
```
@Nullable
public String getStorageLocation()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Number of the storage location in which the material is stored. A plant may contain one or more storage locations.
  - getReplacementPartType
```
@Nullable
public String getReplacementPartType()
```
    Constraints: Not nullable, Maximum length: 1
    The SD billing application uses this indicator to disclose used-parts VAT.
    
    Returns:
    
    Indicator that specifies whether the material can be a replacement part, must be a replacement part, or is not a replacement part.
  - getMaterialGroupHierarchy1
```
@Nullable
public String getMaterialGroupHierarchy1()
```
    Constraints: Not nullable, Maximum length: 18
    Material group hierarchy levels can be put together into groups. In this way the goods group with its higher-level material group hierarchy levels can be made into a clear material group hierarchy valid for a sinlge client. Prices and conditions can be stored at material group level and at the first of the two higher-level material group hierarchy levels.
    
    Returns:
    
    Key, which specifies the grouping of material groups.
  - getMaterialGroupHierarchy2
```
@Nullable
public String getMaterialGroupHierarchy2()
```
    Constraints: Not nullable, Maximum length: 18
    Material group hierarchy levels can be put together into groups. In this way the goods group with its higher-level material group hierarchy levels can be made into a clear material group hierarchy valid for a single client. Prices and conditions can be stored at material group level and at the first of the two higher level material group hierarchy levels.
    
    Returns:
    
    Key that specifies the grouping of material groups.
  - getPlantRegion
```
@Nullable
public String getPlantRegion()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Region in which plant is located
  - getPlantCounty
```
@Nullable
public String getPlantCounty()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    County in which plant is located
  - getPlantCity
```
@Nullable
public String getPlantCity()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    City in which plant is located
  - getBOMExplosion
```
@Nullable
public String getBOMExplosion()
```
    Constraints: Not nullable, Maximum length: 8
    
    Returns:
    
    Number used by the component supplier to identify the production series from which the customer releases and receives materials.
  - getMaterialDeterminationType
```
@Nullable
public String getMaterialDeterminationType()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    ID for material determination
  - getBillingDocumentItemText
```
@Nullable
public String getBillingDocumentItemText()
```
    Constraints: Not nullable, Maximum length: 40
    Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations. The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
    
    Returns:
    
    A short description of the item.
  - getServicesRenderedDate
```
@Nullable
public Calendar getServicesRenderedDate()
```
    Constraints: Not nullable, Precision: 0
    If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
    
    Returns:
    
    The date of services rendered that determines when the system calculates taxes (for example, sales tax) for the material.
  - getBillingQuantity
```
@Nullable
public BigDecimal getBillingQuantity()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Returns:
    
    The item quantity that is actually billed.
  - getBillingQuantityUnit
```
@Nullable
public String getBillingQuantityUnit()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Unit of measure in which the material is sold.
  - getBillingQuantityInBaseUnit
```
@Nullable
public BigDecimal getBillingQuantityInBaseUnit()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Returns:
    
    Billing quantity in stockkeeping unit
  - getBaseUnit
```
@Nullable
public String getBaseUnit()
```
    Constraints: Not nullable, Maximum length: 3
    You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record. Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following: The base unit of measure is the unit satisfying the highest necessary requirement for precision. The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...). Inventory Management In Inventory Management, the base unit of measure is the same as the stockkeeping unit. Services Services have units of measure of their own, including the following: Service unit Unit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level. Blanket Unit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
    
    Returns:
    
    Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure.
  - getMRPRequiredQuantityInBaseUnit
```
@Nullable
public BigDecimal getMRPRequiredQuantityInBaseUnit()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    The system uses this quantity during the availability check to guarantee that the confirmed quantity cannot be used for another sales order. If you change the material requirements quantity manually, the system automatically adjusts the conversion factor that converts sales units to base units.
    
    Returns:
    
    The quantity that the system transfers as requirements from the schedule line to material requirements planning (MRP). The quantity corresponds to the confirmed quantity and is expressed in base units.
  - getBillingToBaseQuantityDnmntr
```
@Nullable
public BigDecimal getBillingToBaseQuantityDnmntr()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Returns:
    
    Denominator of the conversion factor that the system uses to convert sales units base units of measure.
  - getBillingToBaseQuantityNmrtr
```
@Nullable
public BigDecimal getBillingToBaseQuantityNmrtr()
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Returns:
    
    Numerator of the conversion factor that the system uses to convert sales units base units of measure.
  - getItemGrossWeight
```
@Nullable
public BigDecimal getItemGrossWeight()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order. If there is no related sales order, the system uses the gross weight from the material master record. You can change the gross weight manually in the delivery document.
    
    Returns:
    
    The total gross weight of all items in the delivery. The gross weight represents the net weight plus the weight of packaging.
  - getItemNetWeight
```
@Nullable
public BigDecimal getItemNetWeight()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record. You can change the net weight manually in the delivery document.
    
    Returns:
    
    The total net weight of all items in the delivery.
  - getItemWeightUnit
```
@Nullable
public String getItemWeightUnit()
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a weight, you must enter the corresponding unit of weight here.
    
    Returns:
    
    Unit referring to the gross weight or net weight of the material.
  - getItemVolume
```
@Nullable
public BigDecimal getItemVolume()
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order. If there is no related sales order, the system uses the volume from the material master record. You can change the volume manually in the delivery document.
    
    Returns:
    
    The total volume of all items in the delivery.
  - getItemVolumeUnit
```
@Nullable
public String getItemVolumeUnit()
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a volume, you have to enter the corresponding volume unit here.
    
    Returns:
    
    Unit referring to the volume of the material.
  - getBillToPartyCountry
```
@Nullable
public String getBillToPartyCountry()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Country of destination of sales order
  - getBillToPartyRegion
```
@Nullable
public String getBillToPartyRegion()
```
    Constraints: Not nullable, Maximum length: 3
    
    Returns:
    
    Region of sales order
  - getBillingPlanRule
```
@Nullable
public String getBillingPlanRule()
```
    Constraints: Not nullable, Maximum length: 1
    Billing plan for a rental contract for a piece of machinery Billing dates: First of the month for 12 months Billing amount: 1000 USD per month Each date requires a billing rule which determines this fixed amount as the amount to be billed. Billing plan for the installation of a turbine at a customer location Billing dates: Date delivered 10% Date installed 30% Date turbine goes productive 70% Final invoice Billing amount: 10,000 USD for entire project Each date requires a billing rule which determines a percentage of the overall billing value of the project as the amount to be billed. In the second example, the billing values for each date could equally be fixed partial amounts rather than percentages. For example: Billing dates: Date delivered 1,000 USD Date installed 3,000 USD Date turbine goes productive 6,000 USD Billing amount 10,000 USD
    
    Returns:
    
    Specifies for each billing plan date how the value to be billed is determined.
  - getBillingPlan
```
@Nullable
public String getBillingPlan()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Billing Plan Number / Invoicing Plan Number
  - getBillingPlanItem
```
@Nullable
public String getBillingPlanItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    Item for billing plan/invoice plan/payment cards
  - getNetAmount
```
@Nullable
public BigDecimal getNetAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Returns:
    
    The net value of the billing item including discounts, surcharges and other pricing conditions (such as freight costs), but excluding sales taxes.
  - getTransactionCurrency
```
@Nullable
public String getTransactionCurrency()
```
    Constraints: Not nullable, Maximum length: 5
    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).
  - getGrossAmount
```
@Nullable
public BigDecimal getGrossAmount()
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Returns:
    
    Net value of the billing item including all surcharges and discounts as well as price determination conditions (e.g. freight costs) but without VAT.
  - getPricingDate
```
@Nullable
public Calendar getPricingDate()
```
    Constraints: Not nullable, Precision: 0
    You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
    
    Returns:
    
    The date that determines date-related pricing elements, such as conditions and foreign exchange rate.
  - getPricingScaleQuantityInBaseUnit
```
@Nullable
public BigDecimal getPricingScaleQuantityInBaseUnit()
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Returns:
    
    Scale Quantity in base unit of measure
  - getTaxAmount
```
@Nullable
public BigDecimal getTaxAmount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    The total sales taxes, expressed in the document currency.
  - getCostAmount
```
@Nullable
public BigDecimal getCostAmount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    The cost of an item in a delivery-related billing documents. The cost is determined during the posting of goods issue.
  - getSubtotal1Amount
```
@Nullable
public BigDecimal getSubtotal1Amount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    Subtotal 1 from pricing procedure for condition
  - getSubtotal2Amount
```
@Nullable
public BigDecimal getSubtotal2Amount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    Subtotal 2 from pricing procedure for condition
  - getSubtotal3Amount
```
@Nullable
public BigDecimal getSubtotal3Amount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    Subtotal 3 from pricing procedure for condition
  - getSubtotal4Amount
```
@Nullable
public BigDecimal getSubtotal4Amount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    Subtotal 4 from pricing procedure for condition
  - getSubtotal5Amount
```
@Nullable
public BigDecimal getSubtotal5Amount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    Subtotal 5 from pricing procedure for condition
  - getSubtotal6Amount
```
@Nullable
public BigDecimal getSubtotal6Amount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    Subtotal 6 from pricing procedure for condition
  - getStatisticalValueControl
```
@Nullable
public String getStatisticalValueControl()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Indicates whether the system takes the value of an item into account when it determines the total value of a document.
  - getCashDiscountIsDeductible
```
@Nullable
public Boolean getCashDiscountIsDeductible()
```
    Constraints: none
    
    Returns:
    
    Indicator that specifies whether this material qualifies for a cash discount.
  - getCustomerConditionGroup1
```
@Nullable
public String getCustomerConditionGroup1()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Using condition groups 1 - 5 from the customer record, a customer can be assigned to a group that can be used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.
  - getCustomerConditionGroup2
```
@Nullable
public String getCustomerConditionGroup2()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Using condition groups 1 - 5 from the customer record, a customer can be assigned to a group that can be used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.
  - getCustomerConditionGroup3
```
@Nullable
public String getCustomerConditionGroup3()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Using condition groups 1 - 5 from the customer record, a customer can be assigned to a group that can be used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.
  - getCustomerConditionGroup4
```
@Nullable
public String getCustomerConditionGroup4()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Using condition groups 1 - 5 from the customer record, a customer can be assigned to a group that can be used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.
  - getCustomerConditionGroup5
```
@Nullable
public String getCustomerConditionGroup5()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Using condition groups 1 - 5 from the customer record, a customer can be assigned to a group that can be used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.
  - getManualPriceChangeType
```
@Nullable
public String getManualPriceChangeType()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    Status manual price change
  - getMaterialPricingGroup
```
@Nullable
public String getMaterialPricingGroup()
```
    Constraints: Not nullable, Maximum length: 2
    You can create condition records for a material price group using the following condition types: Material price group (for example, all non-food products) A combination of customer and material price group A combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
    
    Returns:
    
    A way of grouping materials to which you want to apply the same condition.
  - getMainItemPricingRefMaterial
```
@Nullable
public String getMainItemPricingRefMaterial()
```
    Constraints: Not nullable, Maximum length: 40
    The pricing reference material is stored in the master record of the main item material. All pricing conditions which apply to reference material apply to the material in the main item. You must first of all create a material master record for the pricing reference material.
    
    Returns:
    
    Enter the number of the material master record for the pricing reference material on which the system should base its calculations for pricing for the main item.
  - getMainItemMaterialPricingGroup
```
@Nullable
public String getMainItemMaterialPricingGroup()
```
    Constraints: Not nullable, Maximum length: 2
    You can create price conditions for a material pricing group (for example, non-food products) a combination of customer and material pricing group a combination of price group and material pricing group (for example, wholesale customers and all non-food products)
    
    Returns:
    
    Enter a grouping of main item materials for which the same price conditions should apply.
  - getDepartureCountry
```
@Nullable
public String getDepartureCountry()
```
    Constraints: Not nullable, Maximum length: 3
    You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key to help determine the relevant taxes during pricing determine important country-specific standards (the length of postal codes and bank account numbers, for example)
    
    Returns:
    
    Identifies the country in which the delivery originates.
  - getTaxJurisdiction
```
@Nullable
public String getTaxJurisdiction()
```
    Constraints: Not nullable, Maximum length: 15
    
    Returns:
    
    The tax jurisdiction is used for determining the tax rates in the USA. It defines to which tax authorities you must pay your taxes. It is always the city to which the goods are supplied.
  - getProductTaxClassification1
```
@Nullable
public String getProductTaxClassification1()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, state sales taxes).
  - getProductTaxClassification2
```
@Nullable
public String getProductTaxClassification2()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getProductTaxClassification3
```
@Nullable
public String getProductTaxClassification3()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getProductTaxClassification4
```
@Nullable
public String getProductTaxClassification4()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getProductTaxClassification5
```
@Nullable
public String getProductTaxClassification5()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getProductTaxClassification6
```
@Nullable
public String getProductTaxClassification6()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getProductTaxClassification7
```
@Nullable
public String getProductTaxClassification7()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getProductTaxClassification8
```
@Nullable
public String getProductTaxClassification8()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getProductTaxClassification9
```
@Nullable
public String getProductTaxClassification9()
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Returns:
    
    Indicates whether, during sales order processing, the system determines taxes that relate to the material (for example, VAT in the UK or state sales taxes in the USA).
  - getZeroVATRsn
```
@Nullable
public String getZeroVATRsn()
```
    Constraints: Not nullable, Maximum length: 1
    the tax purposes.
    
    Returns:
    
    The codes are necessary to describe the different types of zero VAT for
  - getEligibleAmountForCashDiscount
```
@Nullable
public BigDecimal getEligibleAmountForCashDiscount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    During document entry, the amount qualifying for cash discount can be determined manually or automatically. The amount is determined automatically if no entry is made or a '*' is entered. To determine this amount automatically, the system takes into account the offsetting items relevant to cash discount for the invoice item and the rules assigned for each company code for processing cash discount and taxes.
    
    Returns:
    
    Part of the invoiced amount for which cash discount is granted. The amount is always in the document currency.
  - getBusinessArea
```
@Nullable
public String getBusinessArea()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Key that uniquely identifies a business area.
  - getProfitCenter
```
@Nullable
public String getProfitCenter()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Key which together with the controlling area uniquely identifies a profit center.
  - getWBSElement
```
@Nullable
public String getWBSElement()
```
    Constraints: Not nullable, Maximum length: 24
    
    Returns:
    
    Key that identifies a WBS element.
  - getControllingArea
```
@Nullable
public String getControllingArea()
```
    Constraints: Not nullable, Maximum length: 4
    The controlling area is the highest organizational unit in Controlling. Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
    
    Returns:
    
    Uniquely identifies a controlling area.
  - getProfitabilitySegment
```
@Nullable
public String getProfitabilitySegment()
```
    Constraints: Not nullable, Maximum length: 10
    Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
    
    Returns:
    
    See glossary
  - getOrderID
```
@Nullable
public String getOrderID()
```
    Constraints: Not nullable, Maximum length: 12
    
    Returns:
    
    Key that uniquely identifies an order within a client.
  - getCostCenter
```
@Nullable
public String getCostCenter()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    A key that uniquely identifies a cost center.
  - getOriginSDDocument
```
@Nullable
public String getOriginSDDocument()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Originating Document
  - getOriginSDDocumentItem
```
@Nullable
public String getOriginSDDocumentItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    Originating item
  - getMatlAccountAssignmentGroup
```
@Nullable
public String getMatlAccountAssignmentGroup()
```
    Constraints: Not nullable, Maximum length: 2
    Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
    
    Returns:
    
    Group of materials with the same accounting requirements.
  - getReferenceSDDocument
```
@Nullable
public String getReferenceSDDocument()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Identifies the sales order to which the delivery refers.
  - getReferenceSDDocumentItem
```
@Nullable
public String getReferenceSDDocumentItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    The number of the sales order item to which the delivery item refers.
  - getReferenceSDDocumentCategory
```
@Nullable
public String getReferenceSDDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 4
    
    Returns:
    
    Specifies the sales document category of the preceding sales, delivery, or billing document.
  - getSalesDocument
```
@Nullable
public String getSalesDocument()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    The number that uniquely identifies the sales document.
  - getSalesDocumentItem
```
@Nullable
public String getSalesDocumentItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    The number that uniquely identifies the item in the sales document.
  - getSalesSDDocumentCategory
```
@Nullable
public String getSalesSDDocumentCategory()
```
    Constraints: Not nullable, Maximum length: 4
    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 in the sales and distribution system (for example: quotations, sales orders, deliveries, and invoices).
  - getHigherLevelItem
```
@Nullable
public String getHigherLevelItem()
```
    Constraints: Not nullable, Maximum length: 6
    Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
    
    Returns:
    
    The number of the higher-level item to which this item belongs in a hierarchy.
  - getBillingDocumentItemInPartSgmt
```
@Nullable
public String getBillingDocumentItemInPartSgmt()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    Item number in the partner segment
  - getExternalReferenceDocument
```
@Nullable
public String getExternalReferenceDocument()
```
    Constraints: Not nullable, Maximum length: 10
    
    Returns:
    
    Identifies the sales order to which the delivery refers.
  - getExternalReferenceDocumentItem
```
@Nullable
public String getExternalReferenceDocumentItem()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    The number of the sales order item to which the delivery item refers.
  - getSalesGroup
```
@Nullable
public String getSalesGroup()
```
    Constraints: Not nullable, Maximum length: 3
    By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria. If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market. You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
    
    Returns:
    
    A group of sales people who are responsible for processing sales of certain products or services.
  - getAdditionalCustomerGroup1
```
@Nullable
public String getAdditionalCustomerGroup1()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup2
```
@Nullable
public String getAdditionalCustomerGroup2()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup3
```
@Nullable
public String getAdditionalCustomerGroup3()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup4
```
@Nullable
public String getAdditionalCustomerGroup4()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getAdditionalCustomerGroup5
```
@Nullable
public String getAdditionalCustomerGroup5()
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Returns:
    
    Specifies a customer-defined group of customers.
  - getSDDocumentReason
```
@Nullable
public String getSDDocumentReason()
```
    Constraints: Not nullable, Maximum length: 3
    You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria. Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason. If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
    
    Returns:
    
    Indicates the reason for creating the sales document.
  - getRetailPromotion
```
@Nullable
public String getRetailPromotion()
```
    Constraints: Not nullable, Maximum length: 10
    For each item of a purchasing document, you can specify the promotion to which the item belongs. Depending on your system settings, special prices and conditions that are maintained in the IS-R system (Retail) for this promotion are applied when a promotion number is entered. This field also allows you to create purchasing documents on a selective basis for a certain promotion. For example, you can create a purchase order containing only those items that are to be procured for one promotion.
    
    Returns:
    
    Number identifying a promotion for which procurement is to take place.
  - getRebateBasisAmount
```
@Nullable
public BigDecimal getRebateBasisAmount()
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Returns:
    
    Specifies the amount of sales revenue that the system uses as a basis to calculate percentage rebates.
  - getVolumeRebateGroup
```
@Nullable
public String getVolumeRebateGroup()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Group definition that can be used for rebate settlement.
  - getItemIsRelevantForCredit
```
@Nullable
public Boolean getItemIsRelevantForCredit()
```
    Constraints: none
    Select this field if the values of the item type in the total liability are to be updated. In the documentary payments (letter of credit), only those item types that have this field selected are included. Example You do not want a credit check to be executed for an adjustment (item type L2N) and have therefore not activated the credit check for transation type L2. You nevertheless want the values of the adjustment to be updated in the total liability. In this case, you need to select the field ActiveReceivable/Credit-Relevant. for thisitem type.
    
    Returns:
    
    Specifies whether the credit management functions (credit checks and update statistics) for order, delivery, or invoice items are active.
  - getCreditRelatedPrice
```
@Nullable
public BigDecimal getCreditRelatedPrice()
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    The system multiplies the price you specify (for example, the net price) by the item quantity of an open sales, shipping, or billing document to calculate the value for credit management purposes. This price is freely definable in the pricing procedure. You can specify, for example, that either the gross price or the net price can be used for processing credit checks. In the standard system, the credit-related price is the net price, inclusive of sales tax.
    
    Returns:
    
    Specifies the credit-related price in a sales, shipping, or billing document.
  - getSalesDeal
```
@Nullable
public String getSalesDeal()
```
    Constraints: Not nullable, Maximum length: 10
    When creating a new sales deal, you can either enter a number manually or let the system automatically assign an internal number. If you enter a number manually, it must lie within the allocated number range (press F4 to see the range).
    
    Returns:
    
    The number that uniquely identifies the sales deal.
  - getSalesPromotion
```
@Nullable
public String getSalesPromotion()
```
    Constraints: Not nullable, Maximum length: 10
    When creating a new promotion, you can either enter a number manually or let the system automatically assign an internal number. If you enter a number manually, it must lie within the allocated number range (press F4 to see the range).
    
    Returns:
    
    The number that uniquely identifies the promotion.
  - getSalesOrderSalesDistrict
```
@Nullable
public String getSalesOrderSalesDistrict()
```
    Constraints: Not nullable, Maximum length: 6
    
    Returns:
    
    Sales district of sales order
  - getSalesOrderCustomerGroup
```
@Nullable
public String getSalesOrderCustomerGroup()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics.
  - getSalesOrderCustomerPriceGroup
```
@Nullable
public String getSalesOrderCustomerPriceGroup()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Price group of sales order
  - getSalesOrderPriceListType
```
@Nullable
public String getSalesOrderPriceListType()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Specifies the price list type or other condition type(such as a surcharge or discount) which has been defined in the sales document.
  - getSalesOrderSalesOrganization
```
@Nullable
public String getSalesOrderSalesOrganization()
```
    Constraints: Not nullable, Maximum length: 4
    When you create condition records to define prices for inter-company billing, you specify the sales organization that is responsible for processing the sales order.
    
    Returns:
    
    Specifies the sales organization responsible for processing the sales order.
  - getSalesOrderDistributionChannel
```
@Nullable
public String getSalesOrderDistributionChannel()
```
    Constraints: Not nullable, Maximum length: 2
    
    Returns:
    
    Distribution channel of sales order
  - getSalesDocIsCreatedFromReference
```
@Nullable
public Boolean getSalesDocIsCreatedFromReference()
```
    Constraints: none
    You create a sales order from a quotation. The sales order results in an invoice. The order reference indicator in the invoice shows that the sales order was created from a reference document (in this case, the quotation).
    
    Returns:
    
    Indicates whether a sales document (a sales order, for example) was created from a reference document.
  - getShippingPoint
```
@Nullable
public String getShippingPoint()
```
    Constraints: Not nullable, Maximum length: 4
    You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries. A delivery can be shipped from one shipping point only or received at one receiving point only. If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps). If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars. The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually. You can define a user-specific default value for the shipping point in the user parameter VST.
    
    Returns:
    
    The physical location (for example, a warehouse or collection of loading ramps) from which you ship the item.
  - getHigherLevelItemUsage
```
@Nullable
public String getHigherLevelItemUsage()
```
    Constraints: Not nullable, Maximum length: 1
    
    Returns:
    
    ID for higher-level item usage
  - getErpConfigContext
```
@Nullable
public ErpConfigContext getErpConfigContext()
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Returns:
    
    The stored ERP system context for executing queries, or null if no such context has been set.
  - setBillingDocumentItem
```
public void setBillingDocumentItem(@Nullable
                                   String billingDocumentItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    billingDocumentItem -
  - setSalesDocumentItemCategory
```
public void setSalesDocumentItemCategory(@Nullable
                                         String salesDocumentItemCategory)
```
    Constraints: Not nullable, Maximum length: 4
    The system proposes an item category. If alternatives are defined for your system, you can change the item category manually in the sales document. If, for example, you identify an item as a free or charge item, you tell the system, in this case, to ignore normal pricing procedures.
    
    Parameters:
    
    salesDocumentItemCategory -
  - setSalesDocumentItemType
```
public void setSalesDocumentItemType(@Nullable
                                     String salesDocumentItemType)
```
    Constraints: Not nullable, Maximum length: 1
    The system processes items that refer to a specific material differently than items that do not refer to a material. For example, text items do not require processing for pricing, taxes, and weight calculations.
    
    Parameters:
    
    salesDocumentItemType -
  - setReturnItemProcessingType
```
public void setReturnItemProcessingType(@Nullable
                                        String returnItemProcessingType)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    returnItemProcessingType -
  - setCreatedByUser
```
public void setCreatedByUser(@Nullable
                             String createdByUser)
```
    Constraints: Not nullable, Maximum length: 12
    
    Parameters:
    
    createdByUser -
  - setCreationDate
```
public void setCreationDate(@Nullable
                            Calendar creationDate)
```
    Constraints: Not nullable, Precision: 0
    
    Parameters:
    
    creationDate -
  - setCreationTime
```
public void setCreationTime(@Nullable
                            Calendar creationTime)
```
    Constraints: Not nullable, Precision: 0
    
    Parameters:
    
    creationTime -
  - setOrganizationDivision
```
public void setOrganizationDivision(@Nullable
                                    String organizationDivision)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    organizationDivision -
  - setDivision
```
public void setDivision(@Nullable
                        String division)
```
    Constraints: Not nullable, Maximum length: 2
    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 -
  - setSalesOffice
```
public void setSalesOffice(@Nullable
                           String salesOffice)
```
    Constraints: Not nullable, Maximum length: 4
    When you create sales statistics, you can use a sales office as one of the selection criteria. When you print out order confirmations, you can include the address of the sales office. You can assign each customer to a sales office in the customer master record. Within a sales office you can establish sales groups (for example, departments) with specific sales responsibilities. Each person who works in the sales office can be assigned to a sales group in his or her user master record. Each customer can also be assigned to a particular sales group in the customer master record.
    
    Parameters:
    
    salesOffice -
  - setMaterial
```
public void setMaterial(@Nullable
                        String material)
```
    Constraints: Not nullable, Maximum length: 40
    
    Parameters:
    
    material -
  - setOriginallyRequestedMaterial
```
public void setOriginallyRequestedMaterial(@Nullable
                                           String originallyRequestedMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    If, for some reason, you have to send a substitute material instead of the material originally requested, you can see which product the customer originally ordered.
    
    Parameters:
    
    originallyRequestedMaterial -
  - setInternationalArticleNumber
```
public void setInternationalArticleNumber(@Nullable
                                          String internationalArticleNumber)
```
    Constraints: Not nullable, Maximum length: 18
    
    Parameters:
    
    internationalArticleNumber -
  - setPricingReferenceMaterial
```
public void setPricingReferenceMaterial(@Nullable
                                        String pricingReferenceMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    The conditions that apply to the pricing reference material also apply to the material in whose material master record the pricing reference material is stored. A pricing reference material must always have its own material master record.
    
    Parameters:
    
    pricingReferenceMaterial -
  - setBatch
```
public void setBatch(@Nullable
                     String batch)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    batch -
  - setProductHierarchyNode
```
public void setProductHierarchyNode(@Nullable
                                    String productHierarchyNode)
```
    Constraints: Not nullable, Maximum length: 18
    In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters. Level Number of characters allowed 1 5 2 5 3 8 You define a product hierarchy with the following levels: Level Example Description 1 00005 Electrical goods 2 00003 Wet appliances 3 00000001 Washing machine In this case, a washing machine belongs to the product hierarchy 000050000300000001.
    
    Parameters:
    
    productHierarchyNode -
  - setMaterialGroup
```
public void setMaterialGroup(@Nullable
                             String materialGroup)
```
    Constraints: Not nullable, Maximum length: 9
    You can use material groups to: Restrict the scope of analyses Search specifically for material master records via search helps
    
    Parameters:
    
    materialGroup -
  - setAdditionalMaterialGroup1
```
public void setAdditionalMaterialGroup1(@Nullable
                                        String additionalMaterialGroup1)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup1 -
  - setAdditionalMaterialGroup2
```
public void setAdditionalMaterialGroup2(@Nullable
                                        String additionalMaterialGroup2)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup2 -
  - setAdditionalMaterialGroup3
```
public void setAdditionalMaterialGroup3(@Nullable
                                        String additionalMaterialGroup3)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup3 -
  - setAdditionalMaterialGroup4
```
public void setAdditionalMaterialGroup4(@Nullable
                                        String additionalMaterialGroup4)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup4 -
  - setAdditionalMaterialGroup5
```
public void setAdditionalMaterialGroup5(@Nullable
                                        String additionalMaterialGroup5)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    additionalMaterialGroup5 -
  - setMaterialCommissionGroup
```
public void setMaterialCommissionGroup(@Nullable
                                       String materialCommissionGroup)
```
    Constraints: Not nullable, Maximum length: 2
    You can assign two materials to the same commission group as long as each representative who sells these materials receives the same commission percentage for both materials. In other words, the commission percentages within a commission group are always the same for any one representative but may vary for different representatives. Material Rep. 1 Rep. 2 Rep. 3 A 5 % 10 % 11 % B 5 % 10 % 11 % Materials A and B are sold by these three representatives only. You can therefore assign them to the same commission group.
    
    Parameters:
    
    materialCommissionGroup -
  - setPlant
```
public void setPlant(@Nullable
                     String plant)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    plant -
  - setStorageLocation
```
public void setStorageLocation(@Nullable
                               String storageLocation)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    storageLocation -
  - setReplacementPartType
```
public void setReplacementPartType(@Nullable
                                   String replacementPartType)
```
    Constraints: Not nullable, Maximum length: 1
    The SD billing application uses this indicator to disclose used-parts VAT.
    
    Parameters:
    
    replacementPartType -
  - setMaterialGroupHierarchy1
```
public void setMaterialGroupHierarchy1(@Nullable
                                       String materialGroupHierarchy1)
```
    Constraints: Not nullable, Maximum length: 18
    Material group hierarchy levels can be put together into groups. In this way the goods group with its higher-level material group hierarchy levels can be made into a clear material group hierarchy valid for a sinlge client. Prices and conditions can be stored at material group level and at the first of the two higher-level material group hierarchy levels.
    
    Parameters:
    
    materialGroupHierarchy1 -
  - setMaterialGroupHierarchy2
```
public void setMaterialGroupHierarchy2(@Nullable
                                       String materialGroupHierarchy2)
```
    Constraints: Not nullable, Maximum length: 18
    Material group hierarchy levels can be put together into groups. In this way the goods group with its higher-level material group hierarchy levels can be made into a clear material group hierarchy valid for a single client. Prices and conditions can be stored at material group level and at the first of the two higher level material group hierarchy levels.
    
    Parameters:
    
    materialGroupHierarchy2 -
  - setPlantRegion
```
public void setPlantRegion(@Nullable
                           String plantRegion)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    plantRegion -
  - setPlantCounty
```
public void setPlantCounty(@Nullable
                           String plantCounty)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    plantCounty -
  - setPlantCity
```
public void setPlantCity(@Nullable
                         String plantCity)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    plantCity -
  - setBOMExplosion
```
public void setBOMExplosion(@Nullable
                            String bOMExplosion)
```
    Constraints: Not nullable, Maximum length: 8
    
    Parameters:
    
    bOMExplosion -
  - setMaterialDeterminationType
```
public void setMaterialDeterminationType(@Nullable
                                         String materialDeterminationType)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    materialDeterminationType -
  - setBillingDocumentItemText
```
public void setBillingDocumentItemText(@Nullable
                                       String billingDocumentItemText)
```
    Constraints: Not nullable, Maximum length: 40
    Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations. The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
    
    Parameters:
    
    billingDocumentItemText -
  - setServicesRenderedDate
```
public void setServicesRenderedDate(@Nullable
                                    Calendar servicesRenderedDate)
```
    Constraints: Not nullable, Precision: 0
    If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
    
    Parameters:
    
    servicesRenderedDate -
  - setBillingQuantity
```
public void setBillingQuantity(@Nullable
                               BigDecimal billingQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Parameters:
    
    billingQuantity -
  - setBillingQuantityUnit
```
public void setBillingQuantityUnit(@Nullable
                                   String billingQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    billingQuantityUnit -
  - setBillingQuantityInBaseUnit
```
public void setBillingQuantityInBaseUnit(@Nullable
                                         BigDecimal billingQuantityInBaseUnit)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Parameters:
    
    billingQuantityInBaseUnit -
  - setBaseUnit
```
public void setBaseUnit(@Nullable
                        String baseUnit)
```
    Constraints: Not nullable, Maximum length: 3
    You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record. Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following: The base unit of measure is the unit satisfying the highest necessary requirement for precision. The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...). Inventory Management In Inventory Management, the base unit of measure is the same as the stockkeeping unit. Services Services have units of measure of their own, including the following: Service unit Unit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level. Blanket Unit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
    
    Parameters:
    
    baseUnit -
  - setMRPRequiredQuantityInBaseUnit
```
public void setMRPRequiredQuantityInBaseUnit(@Nullable
                                             BigDecimal mRPRequiredQuantityInBaseUnit)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    The system uses this quantity during the availability check to guarantee that the confirmed quantity cannot be used for another sales order. If you change the material requirements quantity manually, the system automatically adjusts the conversion factor that converts sales units to base units.
    
    Parameters:
    
    mRPRequiredQuantityInBaseUnit -
  - setBillingToBaseQuantityDnmntr
```
public void setBillingToBaseQuantityDnmntr(@Nullable
                                           BigDecimal billingToBaseQuantityDnmntr)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Parameters:
    
    billingToBaseQuantityDnmntr -
  - setBillingToBaseQuantityNmrtr
```
public void setBillingToBaseQuantityNmrtr(@Nullable
                                          BigDecimal billingToBaseQuantityNmrtr)
```
    Constraints: Not nullable, Precision: 5, Scale: 0
    Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measure You store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows: 100 bt <=> 1 ca The first number (the denominator) represents the sales units, in this case, bottles. The second number (the numerator) represents the equivalent quantity in base units of measure, in this case, casks.
    
    Parameters:
    
    billingToBaseQuantityNmrtr -
  - setItemGrossWeight
```
public void setItemGrossWeight(@Nullable
                               BigDecimal itemGrossWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the gross weight of each item by multiplying the delivery quantity by the gross weight per unit that comes from the sales order. If there is no related sales order, the system uses the gross weight from the material master record. You can change the gross weight manually in the delivery document.
    
    Parameters:
    
    itemGrossWeight -
  - setItemNetWeight
```
public void setItemNetWeight(@Nullable
                             BigDecimal itemNetWeight)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the net weight of each item by multiplying the delivery quantity by the net weight per unit that comes from the sales order. If there is no related sales order, the system uses the net weight from the material master record. You can change the net weight manually in the delivery document.
    
    Parameters:
    
    itemNetWeight -
  - setItemWeightUnit
```
public void setItemWeightUnit(@Nullable
                              String itemWeightUnit)
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a weight, you must enter the corresponding unit of weight here.
    
    Parameters:
    
    itemWeightUnit -
  - setItemVolume
```
public void setItemVolume(@Nullable
                          BigDecimal itemVolume)
```
    Constraints: Not nullable, Precision: 15, Scale: 3
    The system calculates the volume for each item by multiplying the delivery quantity by the volume per unit that comes from the sales order. If there is no related sales order, the system uses the volume from the material master record. You can change the volume manually in the delivery document.
    
    Parameters:
    
    itemVolume -
  - setItemVolumeUnit
```
public void setItemVolumeUnit(@Nullable
                              String itemVolumeUnit)
```
    Constraints: Not nullable, Maximum length: 3
    If you specify a volume, you have to enter the corresponding volume unit here.
    
    Parameters:
    
    itemVolumeUnit -
  - setBillToPartyCountry
```
public void setBillToPartyCountry(@Nullable
                                  String billToPartyCountry)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    billToPartyCountry -
  - setBillToPartyRegion
```
public void setBillToPartyRegion(@Nullable
                                 String billToPartyRegion)
```
    Constraints: Not nullable, Maximum length: 3
    
    Parameters:
    
    billToPartyRegion -
  - setBillingPlanRule
```
public void setBillingPlanRule(@Nullable
                               String billingPlanRule)
```
    Constraints: Not nullable, Maximum length: 1
    Billing plan for a rental contract for a piece of machinery Billing dates: First of the month for 12 months Billing amount: 1000 USD per month Each date requires a billing rule which determines this fixed amount as the amount to be billed. Billing plan for the installation of a turbine at a customer location Billing dates: Date delivered 10% Date installed 30% Date turbine goes productive 70% Final invoice Billing amount: 10,000 USD for entire project Each date requires a billing rule which determines a percentage of the overall billing value of the project as the amount to be billed. In the second example, the billing values for each date could equally be fixed partial amounts rather than percentages. For example: Billing dates: Date delivered 1,000 USD Date installed 3,000 USD Date turbine goes productive 6,000 USD Billing amount 10,000 USD
    
    Parameters:
    
    billingPlanRule -
  - setBillingPlan
```
public void setBillingPlan(@Nullable
                           String billingPlan)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    billingPlan -
  - setBillingPlanItem
```
public void setBillingPlanItem(@Nullable
                               String billingPlanItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    billingPlanItem -
  - setNetAmount
```
public void setNetAmount(@Nullable
                         BigDecimal netAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Parameters:
    
    netAmount -
  - setTransactionCurrency
```
public void setTransactionCurrency(@Nullable
                                   String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    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 -
  - setGrossAmount
```
public void setGrossAmount(@Nullable
                           BigDecimal grossAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    
    Parameters:
    
    grossAmount -
  - setPricingDate
```
public void setPricingDate(@Nullable
                           Calendar pricingDate)
```
    Constraints: Not nullable, Precision: 0
    You can use the pricing date as a selection criterion when you process billing documents collectively. The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue. Determining the Proposal In the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date. In the billing document: The billing date is proposed as the pricing date.
    
    Parameters:
    
    pricingDate -
  - setPricingScaleQuantityInBaseUnit
```
public void setPricingScaleQuantityInBaseUnit(@Nullable
                                              BigDecimal pricingScaleQuantityInBaseUnit)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    
    Parameters:
    
    pricingScaleQuantityInBaseUnit -
  - setTaxAmount
```
public void setTaxAmount(@Nullable
                         BigDecimal taxAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    taxAmount -
  - setCostAmount
```
public void setCostAmount(@Nullable
                          BigDecimal costAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    costAmount -
  - setSubtotal1Amount
```
public void setSubtotal1Amount(@Nullable
                               BigDecimal subtotal1Amount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    subtotal1Amount -
  - setSubtotal2Amount
```
public void setSubtotal2Amount(@Nullable
                               BigDecimal subtotal2Amount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    subtotal2Amount -
  - setSubtotal3Amount
```
public void setSubtotal3Amount(@Nullable
                               BigDecimal subtotal3Amount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    subtotal3Amount -
  - setSubtotal4Amount
```
public void setSubtotal4Amount(@Nullable
                               BigDecimal subtotal4Amount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    subtotal4Amount -
  - setSubtotal5Amount
```
public void setSubtotal5Amount(@Nullable
                               BigDecimal subtotal5Amount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    subtotal5Amount -
  - setSubtotal6Amount
```
public void setSubtotal6Amount(@Nullable
                               BigDecimal subtotal6Amount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    subtotal6Amount -
  - setStatisticalValueControl
```
public void setStatisticalValueControl(@Nullable
                                       String statisticalValueControl)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    statisticalValueControl -
  - setCashDiscountIsDeductible
```
public void setCashDiscountIsDeductible(@Nullable
                                        Boolean cashDiscountIsDeductible)
```
    Constraints: none
    
    Parameters:
    
    cashDiscountIsDeductible -
  - setCustomerConditionGroup1
```
public void setCustomerConditionGroup1(@Nullable
                                       String customerConditionGroup1)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    customerConditionGroup1 -
  - setCustomerConditionGroup2
```
public void setCustomerConditionGroup2(@Nullable
                                       String customerConditionGroup2)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    customerConditionGroup2 -
  - setCustomerConditionGroup3
```
public void setCustomerConditionGroup3(@Nullable
                                       String customerConditionGroup3)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    customerConditionGroup3 -
  - setCustomerConditionGroup4
```
public void setCustomerConditionGroup4(@Nullable
                                       String customerConditionGroup4)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    customerConditionGroup4 -
  - setCustomerConditionGroup5
```
public void setCustomerConditionGroup5(@Nullable
                                       String customerConditionGroup5)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    customerConditionGroup5 -
  - setManualPriceChangeType
```
public void setManualPriceChangeType(@Nullable
                                     String manualPriceChangeType)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    manualPriceChangeType -
  - setMaterialPricingGroup
```
public void setMaterialPricingGroup(@Nullable
                                    String materialPricingGroup)
```
    Constraints: Not nullable, Maximum length: 2
    You can create condition records for a material price group using the following condition types: Material price group (for example, all non-food products) A combination of customer and material price group A combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
    
    Parameters:
    
    materialPricingGroup -
  - setMainItemPricingRefMaterial
```
public void setMainItemPricingRefMaterial(@Nullable
                                          String mainItemPricingRefMaterial)
```
    Constraints: Not nullable, Maximum length: 40
    The pricing reference material is stored in the master record of the main item material. All pricing conditions which apply to reference material apply to the material in the main item. You must first of all create a material master record for the pricing reference material.
    
    Parameters:
    
    mainItemPricingRefMaterial -
  - setMainItemMaterialPricingGroup
```
public void setMainItemMaterialPricingGroup(@Nullable
                                            String mainItemMaterialPricingGroup)
```
    Constraints: Not nullable, Maximum length: 2
    You can create price conditions for a material pricing group (for example, non-food products) a combination of customer and material pricing group a combination of price group and material pricing group (for example, wholesale customers and all non-food products)
    
    Parameters:
    
    mainItemMaterialPricingGroup -
  - setDepartureCountry
```
public void setDepartureCountry(@Nullable
                                String departureCountry)
```
    Constraints: Not nullable, Maximum length: 3
    You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key to help determine the relevant taxes during pricing determine important country-specific standards (the length of postal codes and bank account numbers, for example)
    
    Parameters:
    
    departureCountry -
  - setTaxJurisdiction
```
public void setTaxJurisdiction(@Nullable
                               String taxJurisdiction)
```
    Constraints: Not nullable, Maximum length: 15
    
    Parameters:
    
    taxJurisdiction -
  - setProductTaxClassification1
```
public void setProductTaxClassification1(@Nullable
                                         String productTaxClassification1)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification1 -
  - setProductTaxClassification2
```
public void setProductTaxClassification2(@Nullable
                                         String productTaxClassification2)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification2 -
  - setProductTaxClassification3
```
public void setProductTaxClassification3(@Nullable
                                         String productTaxClassification3)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification3 -
  - setProductTaxClassification4
```
public void setProductTaxClassification4(@Nullable
                                         String productTaxClassification4)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification4 -
  - setProductTaxClassification5
```
public void setProductTaxClassification5(@Nullable
                                         String productTaxClassification5)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification5 -
  - setProductTaxClassification6
```
public void setProductTaxClassification6(@Nullable
                                         String productTaxClassification6)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification6 -
  - setProductTaxClassification7
```
public void setProductTaxClassification7(@Nullable
                                         String productTaxClassification7)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification7 -
  - setProductTaxClassification8
```
public void setProductTaxClassification8(@Nullable
                                         String productTaxClassification8)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification8 -
  - setProductTaxClassification9
```
public void setProductTaxClassification9(@Nullable
                                         String productTaxClassification9)
```
    Constraints: Not nullable, Maximum length: 1
    The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
    
    Parameters:
    
    productTaxClassification9 -
  - setZeroVATRsn
```
public void setZeroVATRsn(@Nullable
                          String zeroVATRsn)
```
    Constraints: Not nullable, Maximum length: 1
    the tax purposes.
    
    Parameters:
    
    zeroVATRsn -
  - setEligibleAmountForCashDiscount
```
public void setEligibleAmountForCashDiscount(@Nullable
                                             BigDecimal eligibleAmountForCashDiscount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    During document entry, the amount qualifying for cash discount can be determined manually or automatically. The amount is determined automatically if no entry is made or a '*' is entered. To determine this amount automatically, the system takes into account the offsetting items relevant to cash discount for the invoice item and the rules assigned for each company code for processing cash discount and taxes.
    
    Parameters:
    
    eligibleAmountForCashDiscount -
  - setBusinessArea
```
public void setBusinessArea(@Nullable
                            String businessArea)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    businessArea -
  - setProfitCenter
```
public void setProfitCenter(@Nullable
                            String profitCenter)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    profitCenter -
  - setWBSElement
```
public void setWBSElement(@Nullable
                          String wBSElement)
```
    Constraints: Not nullable, Maximum length: 24
    
    Parameters:
    
    wBSElement -
  - setControllingArea
```
public void setControllingArea(@Nullable
                               String controllingArea)
```
    Constraints: Not nullable, Maximum length: 4
    The controlling area is the highest organizational unit in Controlling. Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
    
    Parameters:
    
    controllingArea -
  - setProfitabilitySegment
```
public void setProfitabilitySegment(@Nullable
                                    String profitabilitySegment)
```
    Constraints: Not nullable, Maximum length: 10
    Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
    
    Parameters:
    
    profitabilitySegment -
  - setOrderID
```
public void setOrderID(@Nullable
                       String orderID)
```
    Constraints: Not nullable, Maximum length: 12
    
    Parameters:
    
    orderID -
  - setCostCenter
```
public void setCostCenter(@Nullable
                          String costCenter)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    costCenter -
  - setOriginSDDocument
```
public void setOriginSDDocument(@Nullable
                                String originSDDocument)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    originSDDocument -
  - setOriginSDDocumentItem
```
public void setOriginSDDocumentItem(@Nullable
                                    String originSDDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    originSDDocumentItem -
  - setMatlAccountAssignmentGroup
```
public void setMatlAccountAssignmentGroup(@Nullable
                                          String matlAccountAssignmentGroup)
```
    Constraints: Not nullable, Maximum length: 2
    Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
    
    Parameters:
    
    matlAccountAssignmentGroup -
  - setReferenceSDDocument
```
public void setReferenceSDDocument(@Nullable
                                   String referenceSDDocument)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    referenceSDDocument -
  - setReferenceSDDocumentItem
```
public void setReferenceSDDocumentItem(@Nullable
                                       String referenceSDDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    referenceSDDocumentItem -
  - setReferenceSDDocumentCategory
```
public void setReferenceSDDocumentCategory(@Nullable
                                           String referenceSDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    
    Parameters:
    
    referenceSDDocumentCategory -
  - setSalesDocument
```
public void setSalesDocument(@Nullable
                             String salesDocument)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    salesDocument -
  - setSalesDocumentItem
```
public void setSalesDocumentItem(@Nullable
                                 String salesDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    salesDocumentItem -
  - setSalesSDDocumentCategory
```
public void setSalesSDDocumentCategory(@Nullable
                                       String salesSDDocumentCategory)
```
    Constraints: Not nullable, Maximum length: 4
    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:
    
    salesSDDocumentCategory -
  - setHigherLevelItem
```
public void setHigherLevelItem(@Nullable
                               String higherLevelItem)
```
    Constraints: Not nullable, Maximum length: 6
    Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item. Enter the number of a higher-level item.
    
    Parameters:
    
    higherLevelItem -
  - setBillingDocumentItemInPartSgmt
```
public void setBillingDocumentItemInPartSgmt(@Nullable
                                             String billingDocumentItemInPartSgmt)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    billingDocumentItemInPartSgmt -
  - setExternalReferenceDocument
```
public void setExternalReferenceDocument(@Nullable
                                         String externalReferenceDocument)
```
    Constraints: Not nullable, Maximum length: 10
    
    Parameters:
    
    externalReferenceDocument -
  - setExternalReferenceDocumentItem
```
public void setExternalReferenceDocumentItem(@Nullable
                                             String externalReferenceDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    externalReferenceDocumentItem -
  - setSalesGroup
```
public void setSalesGroup(@Nullable
                          String salesGroup)
```
    Constraints: Not nullable, Maximum length: 3
    By using sales groups you can designate different areas of responsibility within a sales office. When you generate sales statistics, you can use the sales group as one of the selection criteria. If sales office personnel service both retail and wholesale markets, you can assign a sales group to each market. You assign each salesperson to a sales group in his or her user master record. You assign each customer to a particular sales group in the customer's master record.
    
    Parameters:
    
    salesGroup -
  - setAdditionalCustomerGroup1
```
public void setAdditionalCustomerGroup1(@Nullable
                                        String additionalCustomerGroup1)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup1 -
  - setAdditionalCustomerGroup2
```
public void setAdditionalCustomerGroup2(@Nullable
                                        String additionalCustomerGroup2)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup2 -
  - setAdditionalCustomerGroup3
```
public void setAdditionalCustomerGroup3(@Nullable
                                        String additionalCustomerGroup3)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup3 -
  - setAdditionalCustomerGroup4
```
public void setAdditionalCustomerGroup4(@Nullable
                                        String additionalCustomerGroup4)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup4 -
  - setAdditionalCustomerGroup5
```
public void setAdditionalCustomerGroup5(@Nullable
                                        String additionalCustomerGroup5)
```
    Constraints: Not nullable, Maximum length: 3
    You can define up to five different groups of customers, according to the needs of your organization. You specify the groups in the customer master record under "Additional data". If you assign a particular customer to one or more groups, the system automatically displays the groups in the header data of corresponding sales orders. You can define customer groups in Tables TVV1 through TVV5 and assign them to specific languages in Tables TVV1T through TVV5T.
    
    Parameters:
    
    additionalCustomerGroup5 -
  - setSDDocumentReason
```
public void setSDDocumentReason(@Nullable
                                String sDDocumentReason)
```
    Constraints: Not nullable, Maximum length: 3
    You can freely define order reasons according to the needs of your organization. When you generate sales statistics, you can use the order reason as one of the selection criteria. Enter one of the values predefined for your system. If you are creating a credit or debit memo request, you must enter an order reason. If the order reason specifies, for example, that a customer placed a sales order as a result of contact at a trade fair, you can later generate statistics for all sales orders that were placed at trade fairs.
    
    Parameters:
    
    sDDocumentReason -
  - setRetailPromotion
```
public void setRetailPromotion(@Nullable
                               String retailPromotion)
```
    Constraints: Not nullable, Maximum length: 10
    For each item of a purchasing document, you can specify the promotion to which the item belongs. Depending on your system settings, special prices and conditions that are maintained in the IS-R system (Retail) for this promotion are applied when a promotion number is entered. This field also allows you to create purchasing documents on a selective basis for a certain promotion. For example, you can create a purchase order containing only those items that are to be procured for one promotion.
    
    Parameters:
    
    retailPromotion -
  - setRebateBasisAmount
```
public void setRebateBasisAmount(@Nullable
                                 BigDecimal rebateBasisAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    
    Parameters:
    
    rebateBasisAmount -
  - setVolumeRebateGroup
```
public void setVolumeRebateGroup(@Nullable
                                 String volumeRebateGroup)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    volumeRebateGroup -
  - setItemIsRelevantForCredit
```
public void setItemIsRelevantForCredit(@Nullable
                                       Boolean itemIsRelevantForCredit)
```
    Constraints: none
    Select this field if the values of the item type in the total liability are to be updated. In the documentary payments (letter of credit), only those item types that have this field selected are included. Example You do not want a credit check to be executed for an adjustment (item type L2N) and have therefore not activated the credit check for transation type L2. You nevertheless want the values of the adjustment to be updated in the total liability. In this case, you need to select the field ActiveReceivable/Credit-Relevant. for thisitem type.
    
    Parameters:
    
    itemIsRelevantForCredit -
  - setCreditRelatedPrice
```
public void setCreditRelatedPrice(@Nullable
                                  BigDecimal creditRelatedPrice)
```
    Constraints: Not nullable, Precision: 12, Scale: 3
    The system multiplies the price you specify (for example, the net price) by the item quantity of an open sales, shipping, or billing document to calculate the value for credit management purposes. This price is freely definable in the pricing procedure. You can specify, for example, that either the gross price or the net price can be used for processing credit checks. In the standard system, the credit-related price is the net price, inclusive of sales tax.
    
    Parameters:
    
    creditRelatedPrice -
  - setSalesDeal
```
public void setSalesDeal(@Nullable
                         String salesDeal)
```
    Constraints: Not nullable, Maximum length: 10
    When creating a new sales deal, you can either enter a number manually or let the system automatically assign an internal number. If you enter a number manually, it must lie within the allocated number range (press F4 to see the range).
    
    Parameters:
    
    salesDeal -
  - setSalesPromotion
```
public void setSalesPromotion(@Nullable
                              String salesPromotion)
```
    Constraints: Not nullable, Maximum length: 10
    When creating a new promotion, you can either enter a number manually or let the system automatically assign an internal number. If you enter a number manually, it must lie within the allocated number range (press F4 to see the range).
    
    Parameters:
    
    salesPromotion -
  - setSalesOrderSalesDistrict
```
public void setSalesOrderSalesDistrict(@Nullable
                                       String salesOrderSalesDistrict)
```
    Constraints: Not nullable, Maximum length: 6
    
    Parameters:
    
    salesOrderSalesDistrict -
  - setSalesOrderCustomerGroup
```
public void setSalesOrderCustomerGroup(@Nullable
                                       String salesOrderCustomerGroup)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    salesOrderCustomerGroup -
  - setSalesOrderCustomerPriceGroup
```
public void setSalesOrderCustomerPriceGroup(@Nullable
                                            String salesOrderCustomerPriceGroup)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    salesOrderCustomerPriceGroup -
  - setSalesOrderPriceListType
```
public void setSalesOrderPriceListType(@Nullable
                                       String salesOrderPriceListType)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    salesOrderPriceListType -
  - setSalesOrderSalesOrganization
```
public void setSalesOrderSalesOrganization(@Nullable
                                           String salesOrderSalesOrganization)
```
    Constraints: Not nullable, Maximum length: 4
    When you create condition records to define prices for inter-company billing, you specify the sales organization that is responsible for processing the sales order.
    
    Parameters:
    
    salesOrderSalesOrganization -
  - setSalesOrderDistributionChannel
```
public void setSalesOrderDistributionChannel(@Nullable
                                             String salesOrderDistributionChannel)
```
    Constraints: Not nullable, Maximum length: 2
    
    Parameters:
    
    salesOrderDistributionChannel -
  - setSalesDocIsCreatedFromReference
```
public void setSalesDocIsCreatedFromReference(@Nullable
                                              Boolean salesDocIsCreatedFromReference)
```
    Constraints: none
    You create a sales order from a quotation. The sales order results in an invoice. The order reference indicator in the invoice shows that the sales order was created from a reference document (in this case, the quotation).
    
    Parameters:
    
    salesDocIsCreatedFromReference -
  - setShippingPoint
```
public void setShippingPoint(@Nullable
                             String shippingPoint)
```
    Constraints: Not nullable, Maximum length: 4
    You can predefine shipping/receiving points in the system, based on different combinations of plants shipping conditions loading groups During delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries. A delivery can be shipped from one shipping point only or received at one receiving point only. If you want to provide more detailed information about a shipping point you can specify a loading point (for example, one of a number of different loading ramps). If, for example, you want to ship refrigerated goods to a certain customer by rail, the system proposes a shipping point with a suitable location and equipment for loading refrigerated goods onto rail cars. The system can propose a shipping/receiving point. If valid alternatives are predefined in your system, you can change the shipping/receiving point manually. You can define a user-specific default value for the shipping point in the user parameter VST.
    
    Parameters:
    
    shippingPoint -
  - setHigherLevelItemUsage
```
public void setHigherLevelItemUsage(@Nullable
                                    String higherLevelItemUsage)
```
    Constraints: Not nullable, Maximum length: 1
    
    Parameters:
    
    higherLevelItemUsage -
  - setErpConfigContext
```
public void setErpConfigContext(@Nullable
                                ErpConfigContext erpConfigContext)
```
    Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
    
    Parameters:
    
    erpConfigContext -
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class VdmObject<BillingDocumentItem>
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class VdmObject<BillingDocumentItem>
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class VdmObject<BillingDocumentItem>

Class BillingDocumentItem

Nested Class Summary

Field Summary

Constructor Summary

Method Summary

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

Methods inherited from class java.lang.Object

Field Detail

ALL_FIELDS

BILLING_DOCUMENT

BILLING_DOCUMENT_ITEM

SALES_DOCUMENT_ITEM_CATEGORY

SALES_DOCUMENT_ITEM_TYPE

RETURN_ITEM_PROCESSING_TYPE

CREATED_BY_USER

CREATION_DATE

CREATION_TIME

ORGANIZATION_DIVISION

DIVISION

SALES_OFFICE

MATERIAL

ORIGINALLY_REQUESTED_MATERIAL

INTERNATIONAL_ARTICLE_NUMBER

PRICING_REFERENCE_MATERIAL

BATCH

PRODUCT_HIERARCHY_NODE

MATERIAL_GROUP

ADDITIONAL_MATERIAL_GROUP1

ADDITIONAL_MATERIAL_GROUP2

ADDITIONAL_MATERIAL_GROUP3

ADDITIONAL_MATERIAL_GROUP4

ADDITIONAL_MATERIAL_GROUP5

MATERIAL_COMMISSION_GROUP

PLANT

STORAGE_LOCATION

REPLACEMENT_PART_TYPE

MATERIAL_GROUP_HIERARCHY1

MATERIAL_GROUP_HIERARCHY2

PLANT_REGION

PLANT_COUNTY

PLANT_CITY

BOM_EXPLOSION

MATERIAL_DETERMINATION_TYPE

BILLING_DOCUMENT_ITEM_TEXT

SERVICES_RENDERED_DATE

BILLING_QUANTITY

BILLING_QUANTITY_UNIT

BILLING_QUANTITY_IN_BASE_UNIT

BASE_UNIT

MRP_REQUIRED_QUANTITY_IN_BASE_UNIT

BILLING_TO_BASE_QUANTITY_DNMNTR

BILLING_TO_BASE_QUANTITY_NMRTR

ITEM_GROSS_WEIGHT

ITEM_NET_WEIGHT

ITEM_WEIGHT_UNIT

ITEM_VOLUME

ITEM_VOLUME_UNIT

BILL_TO_PARTY_COUNTRY

BILL_TO_PARTY_REGION

BILLING_PLAN_RULE

BILLING_PLAN

BILLING_PLAN_ITEM

NET_AMOUNT

TRANSACTION_CURRENCY

GROSS_AMOUNT

PRICING_DATE

PRICING_SCALE_QUANTITY_IN_BASE_UNIT

TAX_AMOUNT

COST_AMOUNT

SUBTOTAL1_AMOUNT

SUBTOTAL2_AMOUNT

SUBTOTAL3_AMOUNT

SUBTOTAL4_AMOUNT

SUBTOTAL5_AMOUNT

SUBTOTAL6_AMOUNT

STATISTICAL_VALUE_CONTROL

CASH_DISCOUNT_IS_DEDUCTIBLE

CUSTOMER_CONDITION_GROUP1

CUSTOMER_CONDITION_GROUP2

CUSTOMER_CONDITION_GROUP3