public class BillingDocumentItem extends VdmEntity<BillingDocumentItem>
Original entity name from the Odata EDM: A_BillingDocumentItemType
Modifier and Type | Class and Description |
---|---|
static class |
BillingDocumentItem.BillingDocumentItemBuilder
Helper class to allow for fluent creation of BillingDocumentItem instances.
|
Modifier and Type | Field and Description |
---|---|
static BillingDocumentItemField<BigDecimal> |
ABSLT_PRICE_DETN_EXCHANGE_RATE
Use with available fluent helpers to apply the AbsltPriceDetnExchangeRate field to query operations.
|
static BillingDocumentItemField<BigDecimal> |
ABSLT_STATISTICS_EXCHANGE_RATE
Use with available fluent helpers to apply the AbsltStatisticsExchangeRate field to query operations.
|
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<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static BillingDocumentItemField<LocalTime> |
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<Boolean> |
PRICE_DETN_EXCH_RATE_IS_INDRCT_QTAN
Use with available fluent helpers to apply the PriceDetnExchRateIsIndrctQtan field to query operations.
|
static BillingDocumentItemField<LocalDateTime> |
PRICE_DETN_EXCHANGE_RATE_DATE
Use with available fluent helpers to apply the PriceDetnExchangeRateDate field to query operations.
|
static BillingDocumentItemField<LocalDateTime> |
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_LOGICAL_SYSTEM
Use with available fluent helpers to apply the ReferenceLogicalSystem 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<LocalDateTime> |
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<Boolean> |
STATISTICS_EXCH_RATE_IS_INDRCT_QTAN
Use with available fluent helpers to apply the StatisticsExchRateIsIndrctQtan 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 BillingDocumentItemOneToOneLink<BillingDocument> |
TO_BILLING_DOCUMENT
Use with available fluent helpers to apply the to_BillingDocument navigation property to query operations.
|
static BillingDocumentItemLink<BillingDocumentItemText> |
TO_ITEM_TEXT
Use with available fluent helpers to apply the to_ItemText 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.
|
changedOriginalFields
Constructor and Description |
---|
BillingDocumentItem() |
BillingDocumentItem(String billingDocument,
String billingDocumentItem,
String salesDocumentItemCategory,
String salesDocumentItemType,
String returnItemProcessingType,
String createdByUser,
LocalDateTime creationDate,
LocalTime creationTime,
String referenceLogicalSystem,
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,
LocalDateTime 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,
LocalDateTime pricingDate,
BigDecimal absltPriceDetnExchangeRate,
Boolean priceDetnExchRateIsIndrctQtan,
LocalDateTime priceDetnExchangeRateDate,
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,
BigDecimal absltStatisticsExchangeRate,
Boolean statisticsExchRateIsIndrctQtan,
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,
BillingDocument toBillingDocument,
List<BillingDocumentItemText> toItemText,
List<BillingDocumentItemPartner> toPartner,
List<BillingDocumentItemPrcgElmnt> toPricingElement) |
Modifier and Type | Method and Description |
---|---|
void |
addItemText(BillingDocumentItemText... entity)
Adds elements to the list of associated BillingDocumentItemText entities.
|
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.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static BillingDocumentItem.BillingDocumentItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
BillingDocument |
fetchBillingDocument()
Fetches the BillingDocument entity (one to one) associated with this entity.
|
List<BillingDocumentItemText> |
fetchItemText()
Fetches the BillingDocumentItemText entities (one to many) 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.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
BigDecimal |
getAbsltPriceDetnExchangeRate()
Constraints: Not nullable, Precision: 9, Scale: 5
|
BigDecimal |
getAbsltStatisticsExchangeRate()
Constraints: Not nullable, Precision: 9, Scale: 5
|
String |
getAdditionalCustomerGroup1()
Constraints: Not nullable, Maximum length: 3
|
String |
getAdditionalCustomerGroup2()
Constraints: Not nullable, Maximum length: 3
|
String |
getAdditionalCustomerGroup3()
Constraints: Not nullable, Maximum length: 3
|
String |
getAdditionalCustomerGroup4()
Constraints: Not nullable, Maximum length: 3
|
String |
getAdditionalCustomerGroup5()
Constraints: Not nullable, Maximum length: 3
|
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
|
String |
getBatch()
Constraints: Not nullable, Maximum length: 10
|
String |
getBillingDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
io.vavr.control.Option<BillingDocument> |
getBillingDocumentIfPresent()
Retrieval of associated BillingDocument entity (one to one).
|
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
|
BillingDocument |
getBillingDocumentOrFetch()
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
|
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
|
BigDecimal |
getBillingToBaseQuantityNmrtr()
Constraints: Not nullable, Precision: 5, Scale: 0
|
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
|
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
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
BigDecimal |
getCreditRelatedPrice()
Constraints: Not nullable, Precision: 12, Scale: 3
|
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
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getDepartureCountry()
Constraints: Not nullable, Maximum length: 3
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
String |
getDivision()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getEligibleAmountForCashDiscount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
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
|
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
|
Boolean |
getItemIsRelevantForCredit()
Constraints: none
|
BigDecimal |
getItemNetWeight()
Constraints: Not nullable, Precision: 15, Scale: 3
|
io.vavr.control.Option<List<BillingDocumentItemText>> |
getItemTextIfPresent()
Retrieval of associated BillingDocumentItemText entities (one to many).
|
List<BillingDocumentItemText> |
getItemTextOrFetch()
Retrieval of associated BillingDocumentItemText entities (one to many).
|
BigDecimal |
getItemVolume()
Constraints: Not nullable, Precision: 15, Scale: 3
|
String |
getItemVolumeUnit()
Constraints: Not nullable, Maximum length: 3
|
String |
getItemWeightUnit()
Constraints: Not nullable, Maximum length: 3
|
protected Map<String,Object> |
getKey() |
String |
getMainItemMaterialPricingGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getMainItemPricingRefMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getManualPriceChangeType()
Constraints: Not nullable, Maximum length: 1
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40
|
String |
getMaterialCommissionGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getMaterialDeterminationType()
Constraints: Not nullable, Maximum length: 1
|
String |
getMaterialGroup()
Constraints: Not nullable, Maximum length: 9
|
String |
getMaterialGroupHierarchy1()
Constraints: Not nullable, Maximum length: 18
|
String |
getMaterialGroupHierarchy2()
Constraints: Not nullable, Maximum length: 18
|
String |
getMaterialPricingGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getMatlAccountAssignmentGroup()
Constraints: Not nullable, Maximum length: 2
|
BigDecimal |
getMRPRequiredQuantityInBaseUnit()
Constraints: Not nullable, Precision: 13, Scale: 3
|
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
|
String |
getOriginSDDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getOriginSDDocumentItem()
Constraints: Not nullable, Maximum length: 6
|
io.vavr.control.Option<List<BillingDocumentItemPartner>> |
getPartnerIfPresent()
Retrieval of associated BillingDocumentItemPartner entities (one to many).
|
List<BillingDocumentItemPartner> |
getPartnerOrFetch()
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
|
LocalDateTime |
getPriceDetnExchangeRateDate()
Constraints: Not nullable, Precision: 0
|
Boolean |
getPriceDetnExchRateIsIndrctQtan()
Constraints: none
|
LocalDateTime |
getPricingDate()
Constraints: Not nullable, Precision: 0
|
io.vavr.control.Option<List<BillingDocumentItemPrcgElmnt>> |
getPricingElementIfPresent()
Retrieval of associated BillingDocumentItemPrcgElmnt entities (one to many).
|
List<BillingDocumentItemPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated BillingDocumentItemPrcgElmnt entities (one to many).
|
String |
getPricingReferenceMaterial()
Constraints: Not nullable, Maximum length: 40
|
BigDecimal |
getPricingScaleQuantityInBaseUnit()
Constraints: Not nullable, Precision: 13, Scale: 3
|
String |
getProductHierarchyNode()
Constraints: Not nullable, Maximum length: 18
|
String |
getProductTaxClassification1()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification2()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification3()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification4()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification5()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification6()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification7()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification8()
Constraints: Not nullable, Maximum length: 1
|
String |
getProductTaxClassification9()
Constraints: Not nullable, Maximum length: 1
|
String |
getProfitabilitySegment()
Constraints: Not nullable, Maximum length: 10
|
String |
getProfitCenter()
Constraints: Not nullable, Maximum length: 10
|
BigDecimal |
getRebateBasisAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
String |
getReferenceLogicalSystem()
Constraints: Not nullable, Maximum length: 10
|
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
|
String |
getRetailPromotion()
Constraints: Not nullable, Maximum length: 10
|
String |
getReturnItemProcessingType()
Constraints: Not nullable, Maximum length: 1
|
String |
getSalesDeal()
Constraints: Not nullable, Maximum length: 10
|
Boolean |
getSalesDocIsCreatedFromReference()
Constraints: none
|
String |
getSalesDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesDocumentItem()
Constraints: Not nullable, Maximum length: 6
|
String |
getSalesDocumentItemCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSalesDocumentItemType()
Constraints: Not nullable, Maximum length: 1
|
String |
getSalesGroup()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesOffice()
Constraints: Not nullable, Maximum length: 4
|
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
|
String |
getSalesPromotion()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesSDDocumentCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSDDocumentReason()
Constraints: Not nullable, Maximum length: 3
|
LocalDateTime |
getServicesRenderedDate()
Constraints: Not nullable, Precision: 0
|
String |
getShippingPoint()
Constraints: Not nullable, Maximum length: 4
|
String |
getStatisticalValueControl()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getStatisticsExchRateIsIndrctQtan()
Constraints: none
|
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
|
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
|
int |
hashCode() |
void |
setAbsltPriceDetnExchangeRate(BigDecimal absltPriceDetnExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5
|
void |
setAbsltStatisticsExchangeRate(BigDecimal absltStatisticsExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5
|
void |
setAdditionalCustomerGroup1(String additionalCustomerGroup1)
Constraints: Not nullable, Maximum length: 3
|
void |
setAdditionalCustomerGroup2(String additionalCustomerGroup2)
Constraints: Not nullable, Maximum length: 3
|
void |
setAdditionalCustomerGroup3(String additionalCustomerGroup3)
Constraints: Not nullable, Maximum length: 3
|
void |
setAdditionalCustomerGroup4(String additionalCustomerGroup4)
Constraints: Not nullable, Maximum length: 3
|
void |
setAdditionalCustomerGroup5(String additionalCustomerGroup5)
Constraints: Not nullable, Maximum length: 3
|
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
|
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 billingDocument)
(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
|
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
|
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
|
void |
setBillingToBaseQuantityNmrtr(BigDecimal billingToBaseQuantityNmrtr)
Constraints: Not nullable, Precision: 5, Scale: 0
|
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
|
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(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCreditRelatedPrice(BigDecimal creditRelatedPrice)
Constraints: Not nullable, Precision: 12, Scale: 3
|
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
|
void |
setDivision(String division)
Constraints: Not nullable, Maximum length: 2
|
void |
setEligibleAmountForCashDiscount(BigDecimal eligibleAmountForCashDiscount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
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
|
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
|
void |
setItemIsRelevantForCredit(Boolean itemIsRelevantForCredit)
Constraints: none
|
void |
setItemNetWeight(BigDecimal itemNetWeight)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemText(List<BillingDocumentItemText> value)
Overwrites the list of associated BillingDocumentItemText entities for the loaded navigation property
to_ItemText.
|
void |
setItemVolume(BigDecimal itemVolume)
Constraints: Not nullable, Precision: 15, Scale: 3
|
void |
setItemVolumeUnit(String itemVolumeUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setItemWeightUnit(String itemWeightUnit)
Constraints: Not nullable, Maximum length: 3
|
void |
setMainItemMaterialPricingGroup(String mainItemMaterialPricingGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setMainItemPricingRefMaterial(String mainItemPricingRefMaterial)
Constraints: Not nullable, Maximum length: 40
|
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
|
void |
setMaterialDeterminationType(String materialDeterminationType)
Constraints: Not nullable, Maximum length: 1
|
void |
setMaterialGroup(String materialGroup)
Constraints: Not nullable, Maximum length: 9
|
void |
setMaterialGroupHierarchy1(String materialGroupHierarchy1)
Constraints: Not nullable, Maximum length: 18
|
void |
setMaterialGroupHierarchy2(String materialGroupHierarchy2)
Constraints: Not nullable, Maximum length: 18
|
void |
setMaterialPricingGroup(String materialPricingGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setMatlAccountAssignmentGroup(String matlAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setMRPRequiredQuantityInBaseUnit(BigDecimal mRPRequiredQuantityInBaseUnit)
Constraints: Not nullable, Precision: 13, Scale: 3
|
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
|
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 |
setPriceDetnExchangeRateDate(LocalDateTime priceDetnExchangeRateDate)
Constraints: Not nullable, Precision: 0
|
void |
setPriceDetnExchRateIsIndrctQtan(Boolean priceDetnExchRateIsIndrctQtan)
Constraints: none
|
void |
setPricingDate(LocalDateTime pricingDate)
Constraints: Not nullable, Precision: 0
|
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
|
void |
setPricingScaleQuantityInBaseUnit(BigDecimal pricingScaleQuantityInBaseUnit)
Constraints: Not nullable, Precision: 13, Scale: 3
|
void |
setProductHierarchyNode(String productHierarchyNode)
Constraints: Not nullable, Maximum length: 18
|
void |
setProductTaxClassification1(String productTaxClassification1)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification2(String productTaxClassification2)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification3(String productTaxClassification3)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification4(String productTaxClassification4)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification5(String productTaxClassification5)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification6(String productTaxClassification6)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification7(String productTaxClassification7)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification8(String productTaxClassification8)
Constraints: Not nullable, Maximum length: 1
|
void |
setProductTaxClassification9(String productTaxClassification9)
Constraints: Not nullable, Maximum length: 1
|
void |
setProfitabilitySegment(String profitabilitySegment)
Constraints: Not nullable, Maximum length: 10
|
void |
setProfitCenter(String profitCenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setRebateBasisAmount(BigDecimal rebateBasisAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setReferenceLogicalSystem(String referenceLogicalSystem)
Constraints: Not nullable, Maximum length: 10
|
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
|
void |
setRetailPromotion(String retailPromotion)
Constraints: Not nullable, Maximum length: 10
|
void |
setReturnItemProcessingType(String returnItemProcessingType)
Constraints: Not nullable, Maximum length: 1
|
void |
setSalesDeal(String salesDeal)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesDocIsCreatedFromReference(Boolean salesDocIsCreatedFromReference)
Constraints: none
|
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
|
void |
setSalesDocumentItemType(String salesDocumentItemType)
Constraints: Not nullable, Maximum length: 1
|
void |
setSalesGroup(String salesGroup)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesOffice(String salesOffice)
Constraints: Not nullable, Maximum length: 4
|
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
|
void |
setSalesPromotion(String salesPromotion)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesSDDocumentCategory(String salesSDDocumentCategory)
Constraints: Not nullable, Maximum length: 4
|
void |
setSDDocumentReason(String sDDocumentReason)
Constraints: Not nullable, Maximum length: 3
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setServicesRenderedDate(LocalDateTime servicesRenderedDate)
Constraints: Not nullable, Precision: 0
|
void |
setShippingPoint(String shippingPoint)
Constraints: Not nullable, Maximum length: 4
|
void |
setStatisticalValueControl(String statisticalValueControl)
Constraints: Not nullable, Maximum length: 1
|
void |
setStatisticsExchRateIsIndrctQtan(Boolean statisticsExchRateIsIndrctQtan)
Constraints: none
|
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
|
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
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final BillingDocumentItemSelectable ALL_FIELDS
public static final BillingDocumentItemField<String> BILLING_DOCUMENT
public static final BillingDocumentItemField<String> BILLING_DOCUMENT_ITEM
public static final BillingDocumentItemField<String> SALES_DOCUMENT_ITEM_CATEGORY
public static final BillingDocumentItemField<String> SALES_DOCUMENT_ITEM_TYPE
public static final BillingDocumentItemField<String> RETURN_ITEM_PROCESSING_TYPE
public static final BillingDocumentItemField<String> CREATED_BY_USER
public static final BillingDocumentItemField<LocalDateTime> CREATION_DATE
public static final BillingDocumentItemField<LocalTime> CREATION_TIME
public static final BillingDocumentItemField<String> REFERENCE_LOGICAL_SYSTEM
public static final BillingDocumentItemField<String> ORGANIZATION_DIVISION
public static final BillingDocumentItemField<String> DIVISION
public static final BillingDocumentItemField<String> SALES_OFFICE
public static final BillingDocumentItemField<String> MATERIAL
public static final BillingDocumentItemField<String> ORIGINALLY_REQUESTED_MATERIAL
public static final BillingDocumentItemField<String> INTERNATIONAL_ARTICLE_NUMBER
public static final BillingDocumentItemField<String> PRICING_REFERENCE_MATERIAL
public static final BillingDocumentItemField<String> BATCH
public static final BillingDocumentItemField<String> PRODUCT_HIERARCHY_NODE
public static final BillingDocumentItemField<String> MATERIAL_GROUP
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP1
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP2
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP3
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP4
public static final BillingDocumentItemField<String> ADDITIONAL_MATERIAL_GROUP5
public static final BillingDocumentItemField<String> MATERIAL_COMMISSION_GROUP
public static final BillingDocumentItemField<String> PLANT
public static final BillingDocumentItemField<String> STORAGE_LOCATION
public static final BillingDocumentItemField<String> REPLACEMENT_PART_TYPE
public static final BillingDocumentItemField<String> MATERIAL_GROUP_HIERARCHY1
public static final BillingDocumentItemField<String> MATERIAL_GROUP_HIERARCHY2
public static final BillingDocumentItemField<String> PLANT_REGION
public static final BillingDocumentItemField<String> PLANT_COUNTY
public static final BillingDocumentItemField<String> PLANT_CITY
public static final BillingDocumentItemField<String> BOM_EXPLOSION
public static final BillingDocumentItemField<String> MATERIAL_DETERMINATION_TYPE
public static final BillingDocumentItemField<String> BILLING_DOCUMENT_ITEM_TEXT
public static final BillingDocumentItemField<LocalDateTime> SERVICES_RENDERED_DATE
public static final BillingDocumentItemField<BigDecimal> BILLING_QUANTITY
public static final BillingDocumentItemField<String> BILLING_QUANTITY_UNIT
public static final BillingDocumentItemField<BigDecimal> BILLING_QUANTITY_IN_BASE_UNIT
public static final BillingDocumentItemField<String> BASE_UNIT
public static final BillingDocumentItemField<BigDecimal> MRP_REQUIRED_QUANTITY_IN_BASE_UNIT
public static final BillingDocumentItemField<BigDecimal> BILLING_TO_BASE_QUANTITY_DNMNTR
public static final BillingDocumentItemField<BigDecimal> BILLING_TO_BASE_QUANTITY_NMRTR
public static final BillingDocumentItemField<BigDecimal> ITEM_GROSS_WEIGHT
public static final BillingDocumentItemField<BigDecimal> ITEM_NET_WEIGHT
public static final BillingDocumentItemField<String> ITEM_WEIGHT_UNIT
public static final BillingDocumentItemField<BigDecimal> ITEM_VOLUME
public static final BillingDocumentItemField<String> ITEM_VOLUME_UNIT
public static final BillingDocumentItemField<String> BILL_TO_PARTY_COUNTRY
public static final BillingDocumentItemField<String> BILL_TO_PARTY_REGION
public static final BillingDocumentItemField<String> BILLING_PLAN_RULE
public static final BillingDocumentItemField<String> BILLING_PLAN
public static final BillingDocumentItemField<String> BILLING_PLAN_ITEM
public static final BillingDocumentItemField<BigDecimal> NET_AMOUNT
public static final BillingDocumentItemField<String> TRANSACTION_CURRENCY
public static final BillingDocumentItemField<BigDecimal> GROSS_AMOUNT
public static final BillingDocumentItemField<LocalDateTime> PRICING_DATE
public static final BillingDocumentItemField<BigDecimal> ABSLT_PRICE_DETN_EXCHANGE_RATE
public static final BillingDocumentItemField<Boolean> PRICE_DETN_EXCH_RATE_IS_INDRCT_QTAN
public static final BillingDocumentItemField<LocalDateTime> PRICE_DETN_EXCHANGE_RATE_DATE
public static final BillingDocumentItemField<BigDecimal> PRICING_SCALE_QUANTITY_IN_BASE_UNIT
public static final BillingDocumentItemField<BigDecimal> TAX_AMOUNT
public static final BillingDocumentItemField<BigDecimal> COST_AMOUNT
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL1_AMOUNT
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL2_AMOUNT
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL3_AMOUNT
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL4_AMOUNT
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL5_AMOUNT
public static final BillingDocumentItemField<BigDecimal> SUBTOTAL6_AMOUNT
public static final BillingDocumentItemField<String> STATISTICAL_VALUE_CONTROL
public static final BillingDocumentItemField<Boolean> CASH_DISCOUNT_IS_DEDUCTIBLE
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP1
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP2
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP3
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP4
public static final BillingDocumentItemField<String> CUSTOMER_CONDITION_GROUP5
public static final BillingDocumentItemField<String> MANUAL_PRICE_CHANGE_TYPE
public static final BillingDocumentItemField<String> MATERIAL_PRICING_GROUP
public static final BillingDocumentItemField<BigDecimal> ABSLT_STATISTICS_EXCHANGE_RATE
public static final BillingDocumentItemField<Boolean> STATISTICS_EXCH_RATE_IS_INDRCT_QTAN
public static final BillingDocumentItemField<String> MAIN_ITEM_PRICING_REF_MATERIAL
public static final BillingDocumentItemField<String> MAIN_ITEM_MATERIAL_PRICING_GROUP
public static final BillingDocumentItemField<String> DEPARTURE_COUNTRY
public static final BillingDocumentItemField<String> TAX_JURISDICTION
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION1
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION2
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION3
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION4
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION5
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION6
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION7
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION8
public static final BillingDocumentItemField<String> PRODUCT_TAX_CLASSIFICATION9
public static final BillingDocumentItemField<String> ZERO_VAT_RSN
public static final BillingDocumentItemField<BigDecimal> ELIGIBLE_AMOUNT_FOR_CASH_DISCOUNT
public static final BillingDocumentItemField<String> BUSINESS_AREA
public static final BillingDocumentItemField<String> PROFIT_CENTER
public static final BillingDocumentItemField<String> WBS_ELEMENT
public static final BillingDocumentItemField<String> CONTROLLING_AREA
public static final BillingDocumentItemField<String> PROFITABILITY_SEGMENT
public static final BillingDocumentItemField<String> ORDER_ID
public static final BillingDocumentItemField<String> COST_CENTER
public static final BillingDocumentItemField<String> ORIGIN_SD_DOCUMENT
public static final BillingDocumentItemField<String> ORIGIN_SD_DOCUMENT_ITEM
public static final BillingDocumentItemField<String> MATL_ACCOUNT_ASSIGNMENT_GROUP
public static final BillingDocumentItemField<String> REFERENCE_SD_DOCUMENT
public static final BillingDocumentItemField<String> REFERENCE_SD_DOCUMENT_ITEM
public static final BillingDocumentItemField<String> REFERENCE_SD_DOCUMENT_CATEGORY
public static final BillingDocumentItemField<String> SALES_DOCUMENT
public static final BillingDocumentItemField<String> SALES_DOCUMENT_ITEM
public static final BillingDocumentItemField<String> SALES_SD_DOCUMENT_CATEGORY
public static final BillingDocumentItemField<String> HIGHER_LEVEL_ITEM
public static final BillingDocumentItemField<String> BILLING_DOCUMENT_ITEM_IN_PART_SGMT
public static final BillingDocumentItemField<String> EXTERNAL_REFERENCE_DOCUMENT
public static final BillingDocumentItemField<String> EXTERNAL_REFERENCE_DOCUMENT_ITEM
public static final BillingDocumentItemField<String> SALES_GROUP
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP1
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP2
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP3
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP4
public static final BillingDocumentItemField<String> ADDITIONAL_CUSTOMER_GROUP5
public static final BillingDocumentItemField<String> SD_DOCUMENT_REASON
public static final BillingDocumentItemField<String> RETAIL_PROMOTION
public static final BillingDocumentItemField<BigDecimal> REBATE_BASIS_AMOUNT
public static final BillingDocumentItemField<String> VOLUME_REBATE_GROUP
public static final BillingDocumentItemField<Boolean> ITEM_IS_RELEVANT_FOR_CREDIT
public static final BillingDocumentItemField<BigDecimal> CREDIT_RELATED_PRICE
public static final BillingDocumentItemField<String> SALES_DEAL
public static final BillingDocumentItemField<String> SALES_PROMOTION
public static final BillingDocumentItemField<String> SALES_ORDER_SALES_DISTRICT
public static final BillingDocumentItemField<String> SALES_ORDER_CUSTOMER_GROUP
public static final BillingDocumentItemField<String> SALES_ORDER_CUSTOMER_PRICE_GROUP
public static final BillingDocumentItemField<String> SALES_ORDER_PRICE_LIST_TYPE
public static final BillingDocumentItemField<String> SALES_ORDER_SALES_ORGANIZATION
public static final BillingDocumentItemField<String> SALES_ORDER_DISTRIBUTION_CHANNEL
public static final BillingDocumentItemField<Boolean> SALES_DOC_IS_CREATED_FROM_REFERENCE
public static final BillingDocumentItemField<String> SHIPPING_POINT
public static final BillingDocumentItemField<String> HIGHER_LEVEL_ITEM_USAGE
public static final BillingDocumentItemOneToOneLink<BillingDocument> TO_BILLING_DOCUMENT
public static final BillingDocumentItemLink<BillingDocumentItemText> TO_ITEM_TEXT
public static final BillingDocumentItemLink<BillingDocumentItemPartner> TO_PARTNER
public static final BillingDocumentItemLink<BillingDocumentItemPrcgElmnt> TO_PRICING_ELEMENT
public BillingDocumentItem()
public BillingDocumentItem(@Nullable String billingDocument, @Nullable String billingDocumentItem, @Nullable String salesDocumentItemCategory, @Nullable String salesDocumentItemType, @Nullable String returnItemProcessingType, @Nullable String createdByUser, @Nullable LocalDateTime creationDate, @Nullable LocalTime creationTime, @Nullable String referenceLogicalSystem, @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 LocalDateTime 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 LocalDateTime pricingDate, @Nullable BigDecimal absltPriceDetnExchangeRate, @Nullable Boolean priceDetnExchRateIsIndrctQtan, @Nullable LocalDateTime priceDetnExchangeRateDate, @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 BigDecimal absltStatisticsExchangeRate, @Nullable Boolean statisticsExchRateIsIndrctQtan, @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 BillingDocument toBillingDocument, List<BillingDocumentItemText> toItemText, List<BillingDocumentItemPartner> toPartner, List<BillingDocumentItemPrcgElmnt> toPricingElement)
@Nonnull public Class<BillingDocumentItem> getType()
getType
in class VdmObject<BillingDocumentItem>
public void setBillingDocument(@Nullable String billingDocument)
Original property name from the Odata EDM: BillingDocument
billingDocument
- The number that uniquely identifies the billing document (the invoice, for example).public void setBillingDocumentItem(@Nullable String billingDocumentItem)
Original property name from the Odata EDM: BillingDocumentItem
billingDocumentItem
- The number that uniquely identifies the item in the billing document.public void setSalesDocumentItemCategory(@Nullable String salesDocumentItemCategory)
Original property name from the Odata EDM: SalesDocumentItemCategory
salesDocumentItemCategory
- Sales Document Item Categorypublic void setSalesDocumentItemType(@Nullable String salesDocumentItemType)
Original property name from the Odata EDM: SalesDocumentItemType
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.
salesDocumentItemType
- A way of classifying items that require different kinds of processing by the system.public void setReturnItemProcessingType(@Nullable String returnItemProcessingType)
Original property name from the Odata EDM: ReturnItemProcessingType
returnItemProcessingType
- This item is a returns item if the field is selectedpublic void setCreatedByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
createdByUser
- Name of Person Who Created Objectpublic void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on Which Record Was Createdpublic void setCreationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
creationTime
- The time of day at which the document was posted and stored in the system.public void setReferenceLogicalSystem(@Nullable String referenceLogicalSystem)
Original property name from the Odata EDM: ReferenceLogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
referenceLogicalSystem
- System in which applications run integrated on a shared data basis.public void setOrganizationDivision(@Nullable String organizationDivision)
Original property name from the Odata EDM: OrganizationDivision
organizationDivision
- Division in Sales Order Headerpublic void setDivision(@Nullable String division)
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
division
- A way of grouping materials, products, or services. The system uses divisions to determine the sales
areas and the business areas for a material, product, or service.public void setSalesOffice(@Nullable String salesOffice)
Original property name from the Odata EDM: SalesOffice
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.
salesOffice
- A physical location (for example, a branch office) that has responsibility for the sale of certain
products or services within a given geographical area.public void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setOriginallyRequestedMaterial(@Nullable String originallyRequestedMaterial)
Original property name from the Odata EDM: OriginallyRequestedMaterial
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.
originallyRequestedMaterial
- Material originally requested by the customer.public void setInternationalArticleNumber(@Nullable String internationalArticleNumber)
Original property name from the Odata EDM: InternationalArticleNumber
internationalArticleNumber
- Glossary definitionpublic void setPricingReferenceMaterial(@Nullable String pricingReferenceMaterial)
Original property name from the Odata EDM: PricingReferenceMaterial
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.
pricingReferenceMaterial
- Material master record that the system uses as a reference for pricing purposes.public void setBatch(@Nullable String batch)
Original property name from the Odata EDM: Batch
batch
- Assigns a material that is manufactured in batches or production lots to a specific batch.public void setProductHierarchyNode(@Nullable String productHierarchyNode)
Original property name from the Odata EDM: ProductHierarchyNode
In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.Level Number of characters allowed1 52 53 8You define a product hierarchy with the following levels:Level Example Description1 00005 Electrical goods2 00003 Wet appliances3 00000001 Washing machineIn this case, a washing machine belongs to the product hierarchy 000050000300000001.
productHierarchyNode
- Alphanumeric character string for grouping together materials by combining different characteristics.
It is used for analyses and price determination.public void setMaterialGroup(@Nullable String materialGroup)
Original property name from the Odata EDM: MaterialGroup
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
materialGroup
- Key that you use to group together several materials or services with the same attributes, and to
assign them to a particular material group.public void setAdditionalMaterialGroup1(@Nullable String additionalMaterialGroup1)
Original property name from the Odata EDM: AdditionalMaterialGroup1
additionalMaterialGroup1
- 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.public void setAdditionalMaterialGroup2(@Nullable String additionalMaterialGroup2)
Original property name from the Odata EDM: AdditionalMaterialGroup2
additionalMaterialGroup2
- 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.public void setAdditionalMaterialGroup3(@Nullable String additionalMaterialGroup3)
Original property name from the Odata EDM: AdditionalMaterialGroup3
additionalMaterialGroup3
- 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.public void setAdditionalMaterialGroup4(@Nullable String additionalMaterialGroup4)
Original property name from the Odata EDM: AdditionalMaterialGroup4
additionalMaterialGroup4
- 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.public void setAdditionalMaterialGroup5(@Nullable String additionalMaterialGroup5)
Original property name from the Odata EDM: AdditionalMaterialGroup5
additionalMaterialGroup5
- 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.public void setMaterialCommissionGroup(@Nullable String materialCommissionGroup)
Original property name from the Odata EDM: MaterialCommissionGroup
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. 3A 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.
materialCommissionGroup
- Commission group to which the material is assigned.public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setStorageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
storageLocation
- Number of the storage location in which the material is stored. A plant may contain one or more
storage locations.public void setReplacementPartType(@Nullable String replacementPartType)
Original property name from the Odata EDM: ReplacementPartType
The SD billing application uses this indicator to disclose used-parts VAT.
replacementPartType
- Indicator that specifies whether the material can be a replacement part, must be a replacement part,
or is not a replacement part.public void setMaterialGroupHierarchy1(@Nullable String materialGroupHierarchy1)
Original property name from the Odata EDM: MaterialGroupHierarchy1
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.
materialGroupHierarchy1
- Key, which specifies the grouping of material groups.public void setMaterialGroupHierarchy2(@Nullable String materialGroupHierarchy2)
Original property name from the Odata EDM: MaterialGroupHierarchy2
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.
materialGroupHierarchy2
- Key that specifies the grouping of material groups.public void setPlantRegion(@Nullable String plantRegion)
Original property name from the Odata EDM: PlantRegion
plantRegion
- Region in which plant is locatedpublic void setPlantCounty(@Nullable String plantCounty)
Original property name from the Odata EDM: PlantCounty
plantCounty
- County in which plant is locatedpublic void setPlantCity(@Nullable String plantCity)
Original property name from the Odata EDM: PlantCity
plantCity
- City in which plant is locatedpublic void setBOMExplosion(@Nullable String bOMExplosion)
Original property name from the Odata EDM: BOMExplosion
bOMExplosion
- Number used by the component supplier to identify the production series from which the customer
releases and receives materials.public void setMaterialDeterminationType(@Nullable String materialDeterminationType)
Original property name from the Odata EDM: MaterialDeterminationType
materialDeterminationType
- ID for material determinationpublic void setBillingDocumentItemText(@Nullable String billingDocumentItemText)
Original property name from the Odata EDM: BillingDocumentItemText
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.
billingDocumentItemText
- A short description of the item.public void setServicesRenderedDate(@Nullable LocalDateTime servicesRenderedDate)
Original property name from the Odata EDM: ServicesRenderedDate
If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
servicesRenderedDate
- The date of services rendered that determines when the system calculates taxes (for example, sales
tax) for the material.public void setBillingQuantity(@Nullable BigDecimal billingQuantity)
Original property name from the Odata EDM: BillingQuantity
billingQuantity
- The item quantity that is actually billed.public void setBillingQuantityUnit(@Nullable String billingQuantityUnit)
Original property name from the Odata EDM: BillingQuantityUnit
billingQuantityUnit
- Unit of measure in which the material is sold.public void setBillingQuantityInBaseUnit(@Nullable BigDecimal billingQuantityInBaseUnit)
Original property name from the Odata EDM: BillingQuantityInBaseUnit
billingQuantityInBaseUnit
- Billing quantity in stockkeeping unitpublic void setBaseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: BaseUnit
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 ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit 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.
baseUnit
- 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.public void setMRPRequiredQuantityInBaseUnit(@Nullable BigDecimal mRPRequiredQuantityInBaseUnit)
Original property name from the Odata EDM: MRPRequiredQuantityInBaseUnit
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.
mRPRequiredQuantityInBaseUnit
- 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.public void setBillingToBaseQuantityDnmntr(@Nullable BigDecimal billingToBaseQuantityDnmntr)
Original property name from the Odata EDM: BillingToBaseQuantityDnmntr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe 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.
billingToBaseQuantityDnmntr
- Denominator of the conversion factor that the system uses to convert sales units base units of
measure.public void setBillingToBaseQuantityNmrtr(@Nullable BigDecimal billingToBaseQuantityNmrtr)
Original property name from the Odata EDM: BillingToBaseQuantityNmrtr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe 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.
billingToBaseQuantityNmrtr
- Numerator of the conversion factor that the system uses to convert sales units base units of measure.public void setItemGrossWeight(@Nullable BigDecimal itemGrossWeight)
Original property name from the Odata EDM: ItemGrossWeight
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.
itemGrossWeight
- The total gross weight of all items in the delivery. The gross weight represents the net weight plus
the weight of packaging.public void setItemNetWeight(@Nullable BigDecimal itemNetWeight)
Original property name from the Odata EDM: ItemNetWeight
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.
itemNetWeight
- The total net weight of all items in the delivery.public void setItemWeightUnit(@Nullable String itemWeightUnit)
Original property name from the Odata EDM: ItemWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
itemWeightUnit
- Unit referring to the gross weight or net weight of the material.public void setItemVolume(@Nullable BigDecimal itemVolume)
Original property name from the Odata EDM: ItemVolume
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.
itemVolume
- The total volume of all items in the delivery.public void setItemVolumeUnit(@Nullable String itemVolumeUnit)
Original property name from the Odata EDM: ItemVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
itemVolumeUnit
- Unit referring to the volume of the material.public void setBillToPartyCountry(@Nullable String billToPartyCountry)
Original property name from the Odata EDM: BillToPartyCountry
billToPartyCountry
- Country of destination of sales orderpublic void setBillToPartyRegion(@Nullable String billToPartyRegion)
Original property name from the Odata EDM: BillToPartyRegion
billToPartyRegion
- Region of sales orderpublic void setBillingPlanRule(@Nullable String billingPlanRule)
Original property name from the Odata EDM: BillingPlanRule
Billing plan for a rental contract for a piece of machineryBilling dates: First of the month for 12 monthsBilling amount: 1000 USD per monthEach 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 locationBilling dates: Date delivered 10%Date installed 30%Date turbine goes productive 70%Final invoiceBilling amount: 10,000 USD for entire projectEach 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 USDDate installed 3,000 USDDate turbine goes productive 6,000 USDBilling amount 10,000 USD
billingPlanRule
- Specifies for each billing plan date how the value to be billed is determined.public void setBillingPlan(@Nullable String billingPlan)
Original property name from the Odata EDM: BillingPlan
billingPlan
- Billing Plan Number / Invoicing Plan Numberpublic void setBillingPlanItem(@Nullable String billingPlanItem)
Original property name from the Odata EDM: BillingPlanItem
billingPlanItem
- Item for billing plan/invoice plan/payment cardspublic void setNetAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
netAmount
- The net value of the billing item including discounts, surcharges and other pricing conditions (such
as freight costs), but excluding sales taxes.public void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency
- The currency that applies to the document (for example, to a sales order or an invoice).public void setGrossAmount(@Nullable BigDecimal grossAmount)
Original property name from the Odata EDM: GrossAmount
grossAmount
- Net value of the billing item including all surcharges and discounts as well as price determination
conditions (e.g. freight costs) but without VAT.public void setPricingDate(@Nullable LocalDateTime pricingDate)
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
pricingDate
- The date that determines date-related pricing elements, such as conditions and foreign exchange rate.public void setAbsltPriceDetnExchangeRate(@Nullable BigDecimal absltPriceDetnExchangeRate)
Original property name from the Odata EDM: AbsltPriceDetnExchangeRate
absltPriceDetnExchangeRate
- Exchange rate for price determinationpublic void setPriceDetnExchRateIsIndrctQtan(@Nullable Boolean priceDetnExchRateIsIndrctQtan)
Original property name from the Odata EDM: PriceDetnExchRateIsIndrctQtan
priceDetnExchRateIsIndrctQtan
- Pricing exchange rate quotation is indirectpublic void setPriceDetnExchangeRateDate(@Nullable LocalDateTime priceDetnExchangeRateDate)
Original property name from the Odata EDM: PriceDetnExchangeRateDate
You do not need to enter a date unless the date in question is not the same as the document entry date.
priceDetnExchangeRateDate
- Translation date for determining the exchange rate which is to be used for translation. The exchange
rates are stored in the system.public void setPricingScaleQuantityInBaseUnit(@Nullable BigDecimal pricingScaleQuantityInBaseUnit)
Original property name from the Odata EDM: PricingScaleQuantityInBaseUnit
pricingScaleQuantityInBaseUnit
- Scale Quantity in base unit of measurepublic void setTaxAmount(@Nullable BigDecimal taxAmount)
Original property name from the Odata EDM: TaxAmount
taxAmount
- The total sales taxes, expressed in the document currency.public void setCostAmount(@Nullable BigDecimal costAmount)
Original property name from the Odata EDM: CostAmount
costAmount
- The cost of an item in a delivery-related billing documents. The cost is determined during the posting
of goods issue.public void setSubtotal1Amount(@Nullable BigDecimal subtotal1Amount)
Original property name from the Odata EDM: Subtotal1Amount
subtotal1Amount
- Subtotal 1 from pricing procedure for conditionpublic void setSubtotal2Amount(@Nullable BigDecimal subtotal2Amount)
Original property name from the Odata EDM: Subtotal2Amount
subtotal2Amount
- Subtotal 2 from pricing procedure for conditionpublic void setSubtotal3Amount(@Nullable BigDecimal subtotal3Amount)
Original property name from the Odata EDM: Subtotal3Amount
subtotal3Amount
- Subtotal 3 from pricing procedure for conditionpublic void setSubtotal4Amount(@Nullable BigDecimal subtotal4Amount)
Original property name from the Odata EDM: Subtotal4Amount
subtotal4Amount
- Subtotal 4 from pricing procedure for conditionpublic void setSubtotal5Amount(@Nullable BigDecimal subtotal5Amount)
Original property name from the Odata EDM: Subtotal5Amount
subtotal5Amount
- Subtotal 5 from pricing procedure for conditionpublic void setSubtotal6Amount(@Nullable BigDecimal subtotal6Amount)
Original property name from the Odata EDM: Subtotal6Amount
subtotal6Amount
- Subtotal 6 from pricing procedure for conditionpublic void setStatisticalValueControl(@Nullable String statisticalValueControl)
Original property name from the Odata EDM: StatisticalValueControl
statisticalValueControl
- Indicates whether the system takes the value of an item into account when it determines the total
value of a document.public void setCashDiscountIsDeductible(@Nullable Boolean cashDiscountIsDeductible)
Original property name from the Odata EDM: CashDiscountIsDeductible
cashDiscountIsDeductible
- Indicator that specifies whether this material qualifies for a cash discount.public void setCustomerConditionGroup1(@Nullable String customerConditionGroup1)
Original property name from the Odata EDM: CustomerConditionGroup1
customerConditionGroup1
- 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.public void setCustomerConditionGroup2(@Nullable String customerConditionGroup2)
Original property name from the Odata EDM: CustomerConditionGroup2
customerConditionGroup2
- 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.public void setCustomerConditionGroup3(@Nullable String customerConditionGroup3)
Original property name from the Odata EDM: CustomerConditionGroup3
customerConditionGroup3
- 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.public void setCustomerConditionGroup4(@Nullable String customerConditionGroup4)
Original property name from the Odata EDM: CustomerConditionGroup4
customerConditionGroup4
- 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.public void setCustomerConditionGroup5(@Nullable String customerConditionGroup5)
Original property name from the Odata EDM: CustomerConditionGroup5
customerConditionGroup5
- 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.public void setManualPriceChangeType(@Nullable String manualPriceChangeType)
Original property name from the Odata EDM: ManualPriceChangeType
manualPriceChangeType
- Status manual price changepublic void setMaterialPricingGroup(@Nullable String materialPricingGroup)
Original property name from the Odata EDM: MaterialPricingGroup
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 groupA combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
materialPricingGroup
- A way of grouping materials to which you want to apply the same condition.public void setAbsltStatisticsExchangeRate(@Nullable BigDecimal absltStatisticsExchangeRate)
Original property name from the Odata EDM: AbsltStatisticsExchangeRate
absltStatisticsExchangeRate
- Exchange rate from statistics currency into company currencypublic void setStatisticsExchRateIsIndrctQtan(@Nullable Boolean statisticsExchRateIsIndrctQtan)
Original property name from the Odata EDM: StatisticsExchRateIsIndrctQtan
statisticsExchRateIsIndrctQtan
- Statistics exchange rate quotation is indirectpublic void setMainItemPricingRefMaterial(@Nullable String mainItemPricingRefMaterial)
Original property name from the Odata EDM: MainItemPricingRefMaterial
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.
mainItemPricingRefMaterial
- 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.public void setMainItemMaterialPricingGroup(@Nullable String mainItemMaterialPricingGroup)
Original property name from the Odata EDM: MainItemMaterialPricingGroup
You can create price conditions fora material pricing group (for example, non-food products)a combination of customer and material pricing groupa combination of price group and material pricing group (for example, wholesale customers and all non-food products)
mainItemMaterialPricingGroup
- Enter a grouping of main item materials for which the same price conditions should apply.public void setDepartureCountry(@Nullable String departureCountry)
Original property name from the Odata EDM: DepartureCountry
You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key tohelp determine the relevant taxes during pricingdetermine important country-specific standards (the length of postal codes and bank account numbers, for example)
departureCountry
- Identifies the country in which the delivery originates.public void setTaxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
taxJurisdiction
- The tax jurisdiction is used for determining the tax rates in the USA. It defines to which tax
authorities you must pay your taxes. It is always the city to which the goods are supplied.public void setProductTaxClassification1(@Nullable String productTaxClassification1)
Original property name from the Odata EDM: ProductTaxClassification1
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
productTaxClassification1
- Indicates whether, during sales order processing, the system determines taxes that relate to the
material (for example, state sales taxes).public void setProductTaxClassification2(@Nullable String productTaxClassification2)
Original property name from the Odata EDM: ProductTaxClassification2
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.
productTaxClassification2
- 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).public void setProductTaxClassification3(@Nullable String productTaxClassification3)
Original property name from the Odata EDM: ProductTaxClassification3
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.
productTaxClassification3
- 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).public void setProductTaxClassification4(@Nullable String productTaxClassification4)
Original property name from the Odata EDM: ProductTaxClassification4
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.
productTaxClassification4
- 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).public void setProductTaxClassification5(@Nullable String productTaxClassification5)
Original property name from the Odata EDM: ProductTaxClassification5
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.
productTaxClassification5
- 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).public void setProductTaxClassification6(@Nullable String productTaxClassification6)
Original property name from the Odata EDM: ProductTaxClassification6
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.
productTaxClassification6
- 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).public void setProductTaxClassification7(@Nullable String productTaxClassification7)
Original property name from the Odata EDM: ProductTaxClassification7
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.
productTaxClassification7
- 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).public void setProductTaxClassification8(@Nullable String productTaxClassification8)
Original property name from the Odata EDM: ProductTaxClassification8
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.
productTaxClassification8
- 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).public void setProductTaxClassification9(@Nullable String productTaxClassification9)
Original property name from the Odata EDM: ProductTaxClassification9
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.
productTaxClassification9
- 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).public void setZeroVATRsn(@Nullable String zeroVATRsn)
Original property name from the Odata EDM: ZeroVATRsn
the tax purposes.
zeroVATRsn
- The codes are necessary to describe the different types of zero VAT forpublic void setEligibleAmountForCashDiscount(@Nullable BigDecimal eligibleAmountForCashDiscount)
Original property name from the Odata EDM: EligibleAmountForCashDiscount
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.
eligibleAmountForCashDiscount
- Part of the invoiced amount for which cash discount is granted. The amount is always in the document
currency.public void setBusinessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
businessArea
- Key that uniquely identifies a business area.public void setProfitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
profitCenter
- Key which together with the controlling area uniquely identifies a profit center.public void setWBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
wBSElement
- Key that identifies a WBS element.public void setControllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
controllingArea
- Uniquely identifies a controlling area.public void setProfitabilitySegment(@Nullable String profitabilitySegment)
Original property name from the Odata EDM: ProfitabilitySegment
Examples:Customer '123'/Product '4710' Profitability segment no. 1Customer '123'/Product '4712' Profitability segment no. 2Country 'USA'/Region 'NORTH' Profitability segment no. 3
profitabilitySegment
- See glossarypublic void setOrderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
orderID
- Key that uniquely identifies an order within a client.public void setCostCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
costCenter
- A key that uniquely identifies a cost center.public void setOriginSDDocument(@Nullable String originSDDocument)
Original property name from the Odata EDM: OriginSDDocument
originSDDocument
- Originating Documentpublic void setOriginSDDocumentItem(@Nullable String originSDDocumentItem)
Original property name from the Odata EDM: OriginSDDocumentItem
originSDDocumentItem
- Originating itempublic void setMatlAccountAssignmentGroup(@Nullable String matlAccountAssignmentGroup)
Original property name from the Odata EDM: MatlAccountAssignmentGroup
Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
matlAccountAssignmentGroup
- Group of materials with the same accounting requirements.public void setReferenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
referenceSDDocument
- Identifies the sales order to which the delivery refers.public void setReferenceSDDocumentItem(@Nullable String referenceSDDocumentItem)
Original property name from the Odata EDM: ReferenceSDDocumentItem
referenceSDDocumentItem
- The number of the sales order item to which the delivery item refers.public void setReferenceSDDocumentCategory(@Nullable String referenceSDDocumentCategory)
Original property name from the Odata EDM: ReferenceSDDocumentCategory
referenceSDDocumentCategory
- Reference Document Categorypublic void setSalesDocument(@Nullable String salesDocument)
Original property name from the Odata EDM: SalesDocument
salesDocument
- The number that uniquely identifies the sales document.public void setSalesDocumentItem(@Nullable String salesDocumentItem)
Original property name from the Odata EDM: SalesDocumentItem
salesDocumentItem
- The number that uniquely identifies the item in the sales document.public void setSalesSDDocumentCategory(@Nullable String salesSDDocumentCategory)
Original property name from the Odata EDM: SalesSDDocumentCategory
salesSDDocumentCategory
- Sales Document Categorypublic void setHigherLevelItem(@Nullable String higherLevelItem)
Original property name from the Odata EDM: HigherLevelItem
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.
higherLevelItem
- The number of the higher-level item to which this item belongs in a hierarchy.public void setBillingDocumentItemInPartSgmt(@Nullable String billingDocumentItemInPartSgmt)
Original property name from the Odata EDM: BillingDocumentItemInPartSgmt
billingDocumentItemInPartSgmt
- Item number in the partner segmentpublic void setExternalReferenceDocument(@Nullable String externalReferenceDocument)
Original property name from the Odata EDM: ExternalReferenceDocument
externalReferenceDocument
- Identifies the sales order to which the delivery refers.public void setExternalReferenceDocumentItem(@Nullable String externalReferenceDocumentItem)
Original property name from the Odata EDM: ExternalReferenceDocumentItem
externalReferenceDocumentItem
- The number of the sales order item to which the delivery item refers.public void setSalesGroup(@Nullable String salesGroup)
Original property name from the Odata EDM: SalesGroup
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.
salesGroup
- A group of sales people who are responsible for processing sales of certain products or services.public void setAdditionalCustomerGroup1(@Nullable String additionalCustomerGroup1)
Original property name from the Odata EDM: AdditionalCustomerGroup1
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.
additionalCustomerGroup1
- Specifies a customer-defined group of customers.public void setAdditionalCustomerGroup2(@Nullable String additionalCustomerGroup2)
Original property name from the Odata EDM: AdditionalCustomerGroup2
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.
additionalCustomerGroup2
- Specifies a customer-defined group of customers.public void setAdditionalCustomerGroup3(@Nullable String additionalCustomerGroup3)
Original property name from the Odata EDM: AdditionalCustomerGroup3
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.
additionalCustomerGroup3
- Specifies a customer-defined group of customers.public void setAdditionalCustomerGroup4(@Nullable String additionalCustomerGroup4)
Original property name from the Odata EDM: AdditionalCustomerGroup4
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.
additionalCustomerGroup4
- Specifies a customer-defined group of customers.public void setAdditionalCustomerGroup5(@Nullable String additionalCustomerGroup5)
Original property name from the Odata EDM: AdditionalCustomerGroup5
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.
additionalCustomerGroup5
- Specifies a customer-defined group of customers.public void setSDDocumentReason(@Nullable String sDDocumentReason)
Original property name from the Odata EDM: SDDocumentReason
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.
sDDocumentReason
- Indicates the reason for creating the sales document.public void setRetailPromotion(@Nullable String retailPromotion)
Original property name from the Odata EDM: RetailPromotion
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.
retailPromotion
- Number identifying a promotion for which procurement is to take place.public void setRebateBasisAmount(@Nullable BigDecimal rebateBasisAmount)
Original property name from the Odata EDM: RebateBasisAmount
rebateBasisAmount
- Specifies the amount of sales revenue that the system uses as a basis to calculate percentage rebates.public void setVolumeRebateGroup(@Nullable String volumeRebateGroup)
Original property name from the Odata EDM: VolumeRebateGroup
volumeRebateGroup
- Group definition that can be used for rebate settlement.public void setItemIsRelevantForCredit(@Nullable Boolean itemIsRelevantForCredit)
Original property name from the Odata EDM: ItemIsRelevantForCredit
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.ExampleYou 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.
itemIsRelevantForCredit
- Specifies whether the credit management functions (credit checks and update statistics) for order,
delivery, or invoice items are active.public void setCreditRelatedPrice(@Nullable BigDecimal creditRelatedPrice)
Original property name from the Odata EDM: CreditRelatedPrice
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.
creditRelatedPrice
- Specifies the credit-related price in a sales, shipping, or billing document.public void setSalesDeal(@Nullable String salesDeal)
Original property name from the Odata EDM: SalesDeal
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).
salesDeal
- The number that uniquely identifies the sales deal.public void setSalesPromotion(@Nullable String salesPromotion)
Original property name from the Odata EDM: SalesPromotion
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).
salesPromotion
- The number that uniquely identifies the promotion.public void setSalesOrderSalesDistrict(@Nullable String salesOrderSalesDistrict)
Original property name from the Odata EDM: SalesOrderSalesDistrict
salesOrderSalesDistrict
- Sales district of sales orderpublic void setSalesOrderCustomerGroup(@Nullable String salesOrderCustomerGroup)
Original property name from the Odata EDM: SalesOrderCustomerGroup
salesOrderCustomerGroup
- Identifies a particular group of customers (for example, wholesale or retail) for the purpose of
pricing or generating statistics.public void setSalesOrderCustomerPriceGroup(@Nullable String salesOrderCustomerPriceGroup)
Original property name from the Odata EDM: SalesOrderCustomerPriceGroup
salesOrderCustomerPriceGroup
- Price group of sales orderpublic void setSalesOrderPriceListType(@Nullable String salesOrderPriceListType)
Original property name from the Odata EDM: SalesOrderPriceListType
salesOrderPriceListType
- Specifies the price list type or other condition type(such as a surcharge or discount) which has been
defined in the sales document.public void setSalesOrderSalesOrganization(@Nullable String salesOrderSalesOrganization)
Original property name from the Odata EDM: SalesOrderSalesOrganization
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.
salesOrderSalesOrganization
- Specifies the sales organization responsible for processing the sales order.public void setSalesOrderDistributionChannel(@Nullable String salesOrderDistributionChannel)
Original property name from the Odata EDM: SalesOrderDistributionChannel
salesOrderDistributionChannel
- Distribution channel of sales orderpublic void setSalesDocIsCreatedFromReference(@Nullable Boolean salesDocIsCreatedFromReference)
Original property name from the Odata EDM: SalesDocIsCreatedFromReference
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).
salesDocIsCreatedFromReference
- Indicates whether a sales document (a sales order, for example) was created from a reference document.public void setShippingPoint(@Nullable String shippingPoint)
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.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.
shippingPoint
- The physical location (for example, a warehouse or collection of loading ramps) from which you ship
the item.public void setHigherLevelItemUsage(@Nullable String higherLevelItemUsage)
Original property name from the Odata EDM: HigherLevelItemUsage
higherLevelItemUsage
- ID for higher-level item usageprotected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<BillingDocumentItem>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<BillingDocumentItem>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<BillingDocumentItem>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<BillingDocumentItem>
@Nonnull public static <T> BillingDocumentItemField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> BillingDocumentItemField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<BillingDocumentItem>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<BillingDocumentItem>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<BillingDocumentItem>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntity
getDefaultServicePath
in class VdmEntity<BillingDocumentItem>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<BillingDocumentItem>
@Nullable public BillingDocument fetchBillingDocument() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
null
if an entity is not associated.com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nullable public BillingDocument getBillingDocumentOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
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.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<BillingDocument> getBillingDocumentIfPresent()
If the navigation property for an entity BillingDocumentItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setBillingDocument(BillingDocument value)
value
- New BillingDocument entity.@Nonnull public List<BillingDocumentItemText> fetchItemText() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<BillingDocumentItemText> getItemTextOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_ItemText 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.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<BillingDocumentItemText>> getItemTextIfPresent()
If the navigation property for an entity BillingDocumentItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setItemText(@Nonnull List<BillingDocumentItemText> value)
If the navigation property to_ItemText 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.
value
- List of BillingDocumentItemText entities.public void addItemText(BillingDocumentItemText... entity)
If the navigation property to_ItemText 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.
entity
- Array of BillingDocumentItemText entities.@Nonnull public List<BillingDocumentItemPartner> fetchPartner() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<BillingDocumentItemPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
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.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<BillingDocumentItemPartner>> getPartnerIfPresent()
If the navigation property for an entity BillingDocumentItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result state
empty
is returned.public void setPartner(@Nonnull List<BillingDocumentItemPartner> value)
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.
value
- List of BillingDocumentItemPartner entities.public void addPartner(BillingDocumentItemPartner... entity)
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.
entity
- Array of BillingDocumentItemPartner entities.@Nonnull public List<BillingDocumentItemPrcgElmnt> fetchPricingElement() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<BillingDocumentItemPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
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.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<BillingDocumentItemPrcgElmnt>> getPricingElementIfPresent()
If the navigation property for an entity BillingDocumentItem has not been resolved yet, this method will
not query further information. Instead its Option
result state will be empty
.
Option
with result
state empty
is returned.public void setPricingElement(@Nonnull List<BillingDocumentItemPrcgElmnt> value)
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.
value
- List of BillingDocumentItemPrcgElmnt entities.public void addPricingElement(BillingDocumentItemPrcgElmnt... entity)
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.
entity
- Array of BillingDocumentItemPrcgElmnt entities.public static BillingDocumentItem.BillingDocumentItemBuilder builder()
@Nullable public String getBillingDocument()
Original property name from the Odata EDM: BillingDocument
@Nullable public String getBillingDocumentItem()
Original property name from the Odata EDM: BillingDocumentItem
@Nullable public String getSalesDocumentItemCategory()
Original property name from the Odata EDM: SalesDocumentItemCategory
@Nullable public String getSalesDocumentItemType()
Original property name from the Odata EDM: SalesDocumentItemType
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.
@Nullable public String getReturnItemProcessingType()
Original property name from the Odata EDM: ReturnItemProcessingType
@Nullable public String getCreatedByUser()
Original property name from the Odata EDM: CreatedByUser
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public LocalTime getCreationTime()
Original property name from the Odata EDM: CreationTime
@Nullable public String getReferenceLogicalSystem()
Original property name from the Odata EDM: ReferenceLogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
@Nullable public String getOrganizationDivision()
Original property name from the Odata EDM: OrganizationDivision
@Nullable public String getDivision()
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
@Nullable public String getSalesOffice()
Original property name from the Odata EDM: SalesOffice
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.
@Nullable public String getMaterial()
Original property name from the Odata EDM: Material
@Nullable public String getOriginallyRequestedMaterial()
Original property name from the Odata EDM: OriginallyRequestedMaterial
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.
@Nullable public String getInternationalArticleNumber()
Original property name from the Odata EDM: InternationalArticleNumber
@Nullable public String getPricingReferenceMaterial()
Original property name from the Odata EDM: PricingReferenceMaterial
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.
@Nullable public String getBatch()
Original property name from the Odata EDM: Batch
@Nullable public String getProductHierarchyNode()
Original property name from the Odata EDM: ProductHierarchyNode
In the standard SAP System, the product hierarchy can have up to 3 levels, each with a specific number of characters.Level Number of characters allowed1 52 53 8You define a product hierarchy with the following levels:Level Example Description1 00005 Electrical goods2 00003 Wet appliances3 00000001 Washing machineIn this case, a washing machine belongs to the product hierarchy 000050000300000001.
@Nullable public String getMaterialGroup()
Original property name from the Odata EDM: MaterialGroup
You can use material groups to:Restrict the scope of analysesSearch specifically for material master records via search helps
@Nullable public String getAdditionalMaterialGroup1()
Original property name from the Odata EDM: AdditionalMaterialGroup1
@Nullable public String getAdditionalMaterialGroup2()
Original property name from the Odata EDM: AdditionalMaterialGroup2
@Nullable public String getAdditionalMaterialGroup3()
Original property name from the Odata EDM: AdditionalMaterialGroup3
@Nullable public String getAdditionalMaterialGroup4()
Original property name from the Odata EDM: AdditionalMaterialGroup4
@Nullable public String getAdditionalMaterialGroup5()
Original property name from the Odata EDM: AdditionalMaterialGroup5
@Nullable public String getMaterialCommissionGroup()
Original property name from the Odata EDM: MaterialCommissionGroup
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. 3A 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.
@Nullable public String getPlant()
Original property name from the Odata EDM: Plant
@Nullable public String getStorageLocation()
Original property name from the Odata EDM: StorageLocation
@Nullable public String getReplacementPartType()
Original property name from the Odata EDM: ReplacementPartType
The SD billing application uses this indicator to disclose used-parts VAT.
@Nullable public String getMaterialGroupHierarchy1()
Original property name from the Odata EDM: MaterialGroupHierarchy1
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.
@Nullable public String getMaterialGroupHierarchy2()
Original property name from the Odata EDM: MaterialGroupHierarchy2
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.
@Nullable public String getPlantRegion()
Original property name from the Odata EDM: PlantRegion
@Nullable public String getPlantCounty()
Original property name from the Odata EDM: PlantCounty
@Nullable public String getPlantCity()
Original property name from the Odata EDM: PlantCity
@Nullable public String getBOMExplosion()
Original property name from the Odata EDM: BOMExplosion
@Nullable public String getMaterialDeterminationType()
Original property name from the Odata EDM: MaterialDeterminationType
@Nullable public String getBillingDocumentItemText()
Original property name from the Odata EDM: BillingDocumentItemText
Short texts are used throughout sales order processing, shipping, and billing. They also appear on printed order confirmations.The system proposes the short text from the material master record. If you have included a short text in a customer-material info record, it replaces the material master text during sales document processing. You can change the text at the item level in the sales document or during delivery processing.
@Nullable public LocalDateTime getServicesRenderedDate()
Original property name from the Odata EDM: ServicesRenderedDate
If you deliver products, the date of services rendered corresponds to the goods issue date and you do not have to enter a date in this field. If you provide a service, however, and you are billing hours, you can enter a date manually. You can use the date of services rendered as one of the selection criteria when you process billing documents collectively.
@Nullable public BigDecimal getBillingQuantity()
Original property name from the Odata EDM: BillingQuantity
@Nullable public String getBillingQuantityUnit()
Original property name from the Odata EDM: BillingQuantityUnit
@Nullable public BigDecimal getBillingQuantityInBaseUnit()
Original property name from the Odata EDM: BillingQuantityInBaseUnit
@Nullable public String getBaseUnit()
Original property name from the Odata EDM: BaseUnit
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 ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit 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.
@Nullable public BigDecimal getMRPRequiredQuantityInBaseUnit()
Original property name from the Odata EDM: MRPRequiredQuantityInBaseUnit
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.
@Nullable public BigDecimal getBillingToBaseQuantityDnmntr()
Original property name from the Odata EDM: BillingToBaseQuantityDnmntr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe 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.
@Nullable public BigDecimal getBillingToBaseQuantityNmrtr()
Original property name from the Odata EDM: BillingToBaseQuantityNmrtr
Many material processing functions, such as the generation of production requirements, may require that sales units are converted into base units of measureYou store a certain beverage in casks, but sell it in 1-liter bottles. The conversion factor is as follows:100 bt <=> 1 caThe 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.
@Nullable public BigDecimal getItemGrossWeight()
Original property name from the Odata EDM: ItemGrossWeight
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.
@Nullable public BigDecimal getItemNetWeight()
Original property name from the Odata EDM: ItemNetWeight
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.
@Nullable public String getItemWeightUnit()
Original property name from the Odata EDM: ItemWeightUnit
If you specify a weight, you must enter the corresponding unit of weight here.
@Nullable public BigDecimal getItemVolume()
Original property name from the Odata EDM: ItemVolume
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.
@Nullable public String getItemVolumeUnit()
Original property name from the Odata EDM: ItemVolumeUnit
If you specify a volume, you have to enter the corresponding volume unit here.
@Nullable public String getBillToPartyCountry()
Original property name from the Odata EDM: BillToPartyCountry
@Nullable public String getBillToPartyRegion()
Original property name from the Odata EDM: BillToPartyRegion
@Nullable public String getBillingPlanRule()
Original property name from the Odata EDM: BillingPlanRule
Billing plan for a rental contract for a piece of machineryBilling dates: First of the month for 12 monthsBilling amount: 1000 USD per monthEach 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 locationBilling dates: Date delivered 10%Date installed 30%Date turbine goes productive 70%Final invoiceBilling amount: 10,000 USD for entire projectEach 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 USDDate installed 3,000 USDDate turbine goes productive 6,000 USDBilling amount 10,000 USD
@Nullable public String getBillingPlan()
Original property name from the Odata EDM: BillingPlan
@Nullable public String getBillingPlanItem()
Original property name from the Odata EDM: BillingPlanItem
@Nullable public BigDecimal getNetAmount()
Original property name from the Odata EDM: NetAmount
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable public BigDecimal getGrossAmount()
Original property name from the Odata EDM: GrossAmount
@Nullable public LocalDateTime getPricingDate()
Original property name from the Odata EDM: PricingDate
You can use the pricing date as a selection criterion when you process billing documents collectively.The system proposes the current date. You can change it manually in the document. If you change the pricing date, the system recalculates pricing for the entire document. If the date is in the past, you receive a warning before you can continue.Determining the ProposalIn the order: You can customize the order type to determine a proposal, such as the current date or the requested delivery date as the pricing date.In the billing document: The billing date is proposed as the pricing date.
@Nullable public BigDecimal getAbsltPriceDetnExchangeRate()
Original property name from the Odata EDM: AbsltPriceDetnExchangeRate
@Nullable public Boolean getPriceDetnExchRateIsIndrctQtan()
Original property name from the Odata EDM: PriceDetnExchRateIsIndrctQtan
@Nullable public LocalDateTime getPriceDetnExchangeRateDate()
Original property name from the Odata EDM: PriceDetnExchangeRateDate
You do not need to enter a date unless the date in question is not the same as the document entry date.
@Nullable public BigDecimal getPricingScaleQuantityInBaseUnit()
Original property name from the Odata EDM: PricingScaleQuantityInBaseUnit
@Nullable public BigDecimal getTaxAmount()
Original property name from the Odata EDM: TaxAmount
@Nullable public BigDecimal getCostAmount()
Original property name from the Odata EDM: CostAmount
@Nullable public BigDecimal getSubtotal1Amount()
Original property name from the Odata EDM: Subtotal1Amount
@Nullable public BigDecimal getSubtotal2Amount()
Original property name from the Odata EDM: Subtotal2Amount
@Nullable public BigDecimal getSubtotal3Amount()
Original property name from the Odata EDM: Subtotal3Amount
@Nullable public BigDecimal getSubtotal4Amount()
Original property name from the Odata EDM: Subtotal4Amount
@Nullable public BigDecimal getSubtotal5Amount()
Original property name from the Odata EDM: Subtotal5Amount
@Nullable public BigDecimal getSubtotal6Amount()
Original property name from the Odata EDM: Subtotal6Amount
@Nullable public String getStatisticalValueControl()
Original property name from the Odata EDM: StatisticalValueControl
@Nullable public Boolean getCashDiscountIsDeductible()
Original property name from the Odata EDM: CashDiscountIsDeductible
@Nullable public String getCustomerConditionGroup1()
Original property name from the Odata EDM: CustomerConditionGroup1
@Nullable public String getCustomerConditionGroup2()
Original property name from the Odata EDM: CustomerConditionGroup2
@Nullable public String getCustomerConditionGroup3()
Original property name from the Odata EDM: CustomerConditionGroup3
@Nullable public String getCustomerConditionGroup4()
Original property name from the Odata EDM: CustomerConditionGroup4
@Nullable public String getCustomerConditionGroup5()
Original property name from the Odata EDM: CustomerConditionGroup5
@Nullable public String getManualPriceChangeType()
Original property name from the Odata EDM: ManualPriceChangeType
@Nullable public String getMaterialPricingGroup()
Original property name from the Odata EDM: MaterialPricingGroup
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 groupA combination of customer price group and material price group (for example, all wholesale customers and all non-food products)
@Nullable public BigDecimal getAbsltStatisticsExchangeRate()
Original property name from the Odata EDM: AbsltStatisticsExchangeRate
@Nullable public Boolean getStatisticsExchRateIsIndrctQtan()
Original property name from the Odata EDM: StatisticsExchRateIsIndrctQtan
@Nullable public String getMainItemPricingRefMaterial()
Original property name from the Odata EDM: MainItemPricingRefMaterial
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.
@Nullable public String getMainItemMaterialPricingGroup()
Original property name from the Odata EDM: MainItemMaterialPricingGroup
You can create price conditions fora material pricing group (for example, non-food products)a combination of customer and material pricing groupa combination of price group and material pricing group (for example, wholesale customers and all non-food products)
@Nullable public String getDepartureCountry()
Original property name from the Odata EDM: DepartureCountry
You can define the country key in a table. As a rule, it is a good idea to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on). The system uses the key tohelp determine the relevant taxes during pricingdetermine important country-specific standards (the length of postal codes and bank account numbers, for example)
@Nullable public String getTaxJurisdiction()
Original property name from the Odata EDM: TaxJurisdiction
@Nullable public String getProductTaxClassification1()
Original property name from the Odata EDM: ProductTaxClassification1
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification2()
Original property name from the Odata EDM: ProductTaxClassification2
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification3()
Original property name from the Odata EDM: ProductTaxClassification3
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification4()
Original property name from the Odata EDM: ProductTaxClassification4
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification5()
Original property name from the Odata EDM: ProductTaxClassification5
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification6()
Original property name from the Odata EDM: ProductTaxClassification6
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification7()
Original property name from the Odata EDM: ProductTaxClassification7
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification8()
Original property name from the Odata EDM: ProductTaxClassification8
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getProductTaxClassification9()
Original property name from the Odata EDM: ProductTaxClassification9
The system copies the tax classification from the tax information stored in the material master record. During pricing, the system uses the tax classification to calculate relevant taxes.
@Nullable public String getZeroVATRsn()
Original property name from the Odata EDM: ZeroVATRsn
the tax purposes.
@Nullable public BigDecimal getEligibleAmountForCashDiscount()
Original property name from the Odata EDM: EligibleAmountForCashDiscount
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.
@Nullable public String getBusinessArea()
Original property name from the Odata EDM: BusinessArea
@Nullable public String getProfitCenter()
Original property name from the Odata EDM: ProfitCenter
@Nullable public String getWBSElement()
Original property name from the Odata EDM: WBSElement
@Nullable public String getControllingArea()
Original property name from the Odata EDM: ControllingArea
The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary.
@Nullable public String getProfitabilitySegment()
Original property name from the Odata EDM: ProfitabilitySegment
Examples:Customer '123'/Product '4710' Profitability segment no. 1Customer '123'/Product '4712' Profitability segment no. 2Country 'USA'/Region 'NORTH' Profitability segment no. 3
@Nullable public String getOrderID()
Original property name from the Odata EDM: OrderID
@Nullable public String getCostCenter()
Original property name from the Odata EDM: CostCenter
@Nullable public String getOriginSDDocument()
Original property name from the Odata EDM: OriginSDDocument
@Nullable public String getOriginSDDocumentItem()
Original property name from the Odata EDM: OriginSDDocumentItem
@Nullable public String getMatlAccountAssignmentGroup()
Original property name from the Odata EDM: MatlAccountAssignmentGroup
Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
@Nullable public String getReferenceSDDocument()
Original property name from the Odata EDM: ReferenceSDDocument
@Nullable public String getReferenceSDDocumentItem()
Original property name from the Odata EDM: ReferenceSDDocumentItem
@Nullable public String getReferenceSDDocumentCategory()
Original property name from the Odata EDM: ReferenceSDDocumentCategory
@Nullable public String getSalesDocument()
Original property name from the Odata EDM: SalesDocument
@Nullable public String getSalesDocumentItem()
Original property name from the Odata EDM: SalesDocumentItem
@Nullable public String getSalesSDDocumentCategory()
Original property name from the Odata EDM: SalesSDDocumentCategory
@Nullable public String getHigherLevelItem()
Original property name from the Odata EDM: HigherLevelItem
Items can be organized hierarchically. When you assign a sub-item to another item, the other item becomes a higher-level item.Enter the number of a higher-level item.
@Nullable public String getBillingDocumentItemInPartSgmt()
Original property name from the Odata EDM: BillingDocumentItemInPartSgmt
@Nullable public String getExternalReferenceDocument()
Original property name from the Odata EDM: ExternalReferenceDocument
@Nullable public String getExternalReferenceDocumentItem()
Original property name from the Odata EDM: ExternalReferenceDocumentItem
@Nullable public String getSalesGroup()
Original property name from the Odata EDM: SalesGroup
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.
@Nullable public String getAdditionalCustomerGroup1()
Original property name from the Odata EDM: AdditionalCustomerGroup1
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.
@Nullable public String getAdditionalCustomerGroup2()
Original property name from the Odata EDM: AdditionalCustomerGroup2
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.
@Nullable public String getAdditionalCustomerGroup3()
Original property name from the Odata EDM: AdditionalCustomerGroup3
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.
@Nullable public String getAdditionalCustomerGroup4()
Original property name from the Odata EDM: AdditionalCustomerGroup4
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.
@Nullable public String getAdditionalCustomerGroup5()
Original property name from the Odata EDM: AdditionalCustomerGroup5
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.
@Nullable public String getSDDocumentReason()
Original property name from the Odata EDM: SDDocumentReason
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.
@Nullable public String getRetailPromotion()
Original property name from the Odata EDM: RetailPromotion
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.
@Nullable public BigDecimal getRebateBasisAmount()
Original property name from the Odata EDM: RebateBasisAmount
@Nullable public String getVolumeRebateGroup()
Original property name from the Odata EDM: VolumeRebateGroup
@Nullable public Boolean getItemIsRelevantForCredit()
Original property name from the Odata EDM: ItemIsRelevantForCredit
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.ExampleYou 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.
@Nullable public BigDecimal getCreditRelatedPrice()
Original property name from the Odata EDM: CreditRelatedPrice
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.
@Nullable public String getSalesDeal()
Original property name from the Odata EDM: SalesDeal
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).
@Nullable public String getSalesPromotion()
Original property name from the Odata EDM: SalesPromotion
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).
@Nullable public String getSalesOrderSalesDistrict()
Original property name from the Odata EDM: SalesOrderSalesDistrict
@Nullable public String getSalesOrderCustomerGroup()
Original property name from the Odata EDM: SalesOrderCustomerGroup
@Nullable public String getSalesOrderCustomerPriceGroup()
Original property name from the Odata EDM: SalesOrderCustomerPriceGroup
@Nullable public String getSalesOrderPriceListType()
Original property name from the Odata EDM: SalesOrderPriceListType
@Nullable public String getSalesOrderSalesOrganization()
Original property name from the Odata EDM: SalesOrderSalesOrganization
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.
@Nullable public String getSalesOrderDistributionChannel()
Original property name from the Odata EDM: SalesOrderDistributionChannel
@Nullable public Boolean getSalesDocIsCreatedFromReference()
Original property name from the Odata EDM: SalesDocIsCreatedFromReference
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).
@Nullable public String getShippingPoint()
Original property name from the Odata EDM: ShippingPoint
You can predefine shipping/receiving points in the system, based on different combinations ofPlantsShipping conditionsLoading groupsDuring delivery processing, the shipping/receiving point is the most important criterion that you use to select deliveries.A delivery can be shipped from only one shipping point or received at only one receiving point.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.
@Nullable public String getHigherLevelItemUsage()
Original property name from the Odata EDM: HigherLevelItemUsage
public String toString()
toString
in class VdmObject<BillingDocumentItem>
public boolean equals(Object o)
equals
in class VdmObject<BillingDocumentItem>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<BillingDocumentItem>
public int hashCode()
hashCode
in class VdmObject<BillingDocumentItem>
Copyright © 2020 SAP SE. All rights reserved.