public static final class BillingDocumentItem.BillingDocumentItemBuilder extends Object
@Nonnull public BillingDocumentItem.BillingDocumentItemBuilder billingDocument(BillingDocument value)
value - The BillingDocument to build this BillingDocumentItem with.@Nonnull public BillingDocumentItem.BillingDocumentItemBuilder billingDocument(String value)
Original property name from the Odata EDM: BillingDocument
value - The billingDocument to build this BillingDocumentItem with.@Nonnull public BillingDocumentItem.BillingDocumentItemBuilder itemText(BillingDocumentItemText... value)
value - The BillingDocumentItemTexts to build this BillingDocumentItem with.@Nonnull public BillingDocumentItem.BillingDocumentItemBuilder partner(BillingDocumentItemPartner... value)
value - The BillingDocumentItemPartners to build this BillingDocumentItem with.@Nonnull public BillingDocumentItem.BillingDocumentItemBuilder pricingElement(BillingDocumentItemPrcgElmnt... value)
value - The BillingDocumentItemPrcgElmnts to build this BillingDocumentItem with.public BillingDocumentItem.BillingDocumentItemBuilder billingDocumentItem(@Nullable String billingDocumentItem)
Original property name from the Odata EDM: BillingDocumentItem
this.public BillingDocumentItem.BillingDocumentItemBuilder salesDocumentItemCategory(@Nullable String salesDocumentItemCategory)
Original property name from the Odata EDM: SalesDocumentItemCategory
this.public BillingDocumentItem.BillingDocumentItemBuilder salesDocumentItemType(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder returnItemProcessingType(@Nullable String returnItemProcessingType)
Original property name from the Odata EDM: ReturnItemProcessingType
this.public BillingDocumentItem.BillingDocumentItemBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this.public BillingDocumentItem.BillingDocumentItemBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this.public BillingDocumentItem.BillingDocumentItemBuilder creationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
this.public BillingDocumentItem.BillingDocumentItemBuilder referenceLogicalSystem(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder organizationDivision(@Nullable String organizationDivision)
Original property name from the Odata EDM: OrganizationDivision
this.public BillingDocumentItem.BillingDocumentItemBuilder division(@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.
areas and the business areas for a material, product, or service.this.public BillingDocumentItem.BillingDocumentItemBuilder salesOffice(@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.
products or services within a given geographical area.this.public BillingDocumentItem.BillingDocumentItemBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
this.public BillingDocumentItem.BillingDocumentItemBuilder originallyRequestedMaterial(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder internationalArticleNumber(@Nullable String internationalArticleNumber)
Original property name from the Odata EDM: InternationalArticleNumber
this.public BillingDocumentItem.BillingDocumentItemBuilder pricingReferenceMaterial(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder batch(@Nullable String batch)
Original property name from the Odata EDM: Batch
this.public BillingDocumentItem.BillingDocumentItemBuilder productHierarchyNode(@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.
is used for analyses and price determination.this.public BillingDocumentItem.BillingDocumentItemBuilder materialGroup(@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
them to a particular material group.this.public BillingDocumentItem.BillingDocumentItemBuilder additionalMaterialGroup1(@Nullable String additionalMaterialGroup1)
Original property name from the Odata EDM: AdditionalMaterialGroup1
not used in the standard SAP System, you can use them as required, for example, for analyses.this.public BillingDocumentItem.BillingDocumentItemBuilder additionalMaterialGroup2(@Nullable String additionalMaterialGroup2)
Original property name from the Odata EDM: AdditionalMaterialGroup2
not used in the standard SAP System, you can use them as required, for example, for analyses.this.public BillingDocumentItem.BillingDocumentItemBuilder additionalMaterialGroup3(@Nullable String additionalMaterialGroup3)
Original property name from the Odata EDM: AdditionalMaterialGroup3
not used in the standard SAP System, you can use them as required, for example, for analyses.this.public BillingDocumentItem.BillingDocumentItemBuilder additionalMaterialGroup4(@Nullable String additionalMaterialGroup4)
Original property name from the Odata EDM: AdditionalMaterialGroup4
not used in the standard SAP System, you can use them as required, for example, for analyses.this.public BillingDocumentItem.BillingDocumentItemBuilder additionalMaterialGroup5(@Nullable String additionalMaterialGroup5)
Original property name from the Odata EDM: AdditionalMaterialGroup5
not used in the standard SAP System, you can use them as required, for example, for analyses.this.public BillingDocumentItem.BillingDocumentItemBuilder materialCommissionGroup(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this.public BillingDocumentItem.BillingDocumentItemBuilder storageLocation(@Nullable String storageLocation)
Original property name from the Odata EDM: StorageLocation
locations.this.public BillingDocumentItem.BillingDocumentItemBuilder replacementPartType(@Nullable String replacementPartType)
Original property name from the Odata EDM: ReplacementPartType
The SD billing application uses this indicator to disclose used-parts VAT.
is not a replacement part.this.public BillingDocumentItem.BillingDocumentItemBuilder materialGroupHierarchy1(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder materialGroupHierarchy2(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder plantRegion(@Nullable String plantRegion)
Original property name from the Odata EDM: PlantRegion
this.public BillingDocumentItem.BillingDocumentItemBuilder plantCounty(@Nullable String plantCounty)
Original property name from the Odata EDM: PlantCounty
this.public BillingDocumentItem.BillingDocumentItemBuilder plantCity(@Nullable String plantCity)
Original property name from the Odata EDM: PlantCity
this.public BillingDocumentItem.BillingDocumentItemBuilder bOMExplosion(@Nullable String bOMExplosion)
Original property name from the Odata EDM: BOMExplosion
and receives materials.this.public BillingDocumentItem.BillingDocumentItemBuilder materialDeterminationType(@Nullable String materialDeterminationType)
Original property name from the Odata EDM: MaterialDeterminationType
this.public BillingDocumentItem.BillingDocumentItemBuilder billingDocumentItemText(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder servicesRenderedDate(@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.
for the material.this.public BillingDocumentItem.BillingDocumentItemBuilder billingQuantity(@Nullable BigDecimal billingQuantity)
Original property name from the Odata EDM: BillingQuantity
this.public BillingDocumentItem.BillingDocumentItemBuilder billingQuantityUnit(@Nullable String billingQuantityUnit)
Original property name from the Odata EDM: BillingQuantityUnit
this.public BillingDocumentItem.BillingDocumentItemBuilder billingQuantityInBaseUnit(@Nullable BigDecimal billingQuantityInBaseUnit)
Original property name from the Odata EDM: BillingQuantityInBaseUnit
this.public BillingDocumentItem.BillingDocumentItemBuilder baseUnit(@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.
enter in other units of measure (alternative units of measure) to the base unit of measure.this.public BillingDocumentItem.BillingDocumentItemBuilder mRPRequiredQuantityInBaseUnit(@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.
planning (MRP). The quantity corresponds to the confirmed quantity and is expressed in base units.this.public BillingDocumentItem.BillingDocumentItemBuilder billingToBaseQuantityDnmntr(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder billingToBaseQuantityNmrtr(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder itemGrossWeight(@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.
weight of packaging.this.public BillingDocumentItem.BillingDocumentItemBuilder itemNetWeight(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder itemWeightUnit(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder itemVolume(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder itemVolumeUnit(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder billToPartyCountry(@Nullable String billToPartyCountry)
Original property name from the Odata EDM: BillToPartyCountry
this.public BillingDocumentItem.BillingDocumentItemBuilder billToPartyRegion(@Nullable String billToPartyRegion)
Original property name from the Odata EDM: BillToPartyRegion
this.public BillingDocumentItem.BillingDocumentItemBuilder billingPlanRule(@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
this.public BillingDocumentItem.BillingDocumentItemBuilder billingPlan(@Nullable String billingPlan)
Original property name from the Odata EDM: BillingPlan
this.public BillingDocumentItem.BillingDocumentItemBuilder billingPlanItem(@Nullable String billingPlanItem)
Original property name from the Odata EDM: BillingPlanItem
this.public BillingDocumentItem.BillingDocumentItemBuilder netAmount(@Nullable BigDecimal netAmount)
Original property name from the Odata EDM: NetAmount
freight costs), but excluding sales taxes.this.public BillingDocumentItem.BillingDocumentItemBuilder transactionCurrency(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder grossAmount(@Nullable BigDecimal grossAmount)
Original property name from the Odata EDM: GrossAmount
conditions (e.g. freight costs) but without VAT.this.public BillingDocumentItem.BillingDocumentItemBuilder pricingDate(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder absltPriceDetnExchangeRate(@Nullable BigDecimal absltPriceDetnExchangeRate)
Original property name from the Odata EDM: AbsltPriceDetnExchangeRate
this.public BillingDocumentItem.BillingDocumentItemBuilder priceDetnExchRateIsIndrctQtan(@Nullable Boolean priceDetnExchRateIsIndrctQtan)
Original property name from the Odata EDM: PriceDetnExchRateIsIndrctQtan
this.public BillingDocumentItem.BillingDocumentItemBuilder priceDetnExchangeRateDate(@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.
rates are stored in the system.this.public BillingDocumentItem.BillingDocumentItemBuilder pricingScaleQuantityInBaseUnit(@Nullable BigDecimal pricingScaleQuantityInBaseUnit)
Original property name from the Odata EDM: PricingScaleQuantityInBaseUnit
this.public BillingDocumentItem.BillingDocumentItemBuilder taxAmount(@Nullable BigDecimal taxAmount)
Original property name from the Odata EDM: TaxAmount
this.public BillingDocumentItem.BillingDocumentItemBuilder costAmount(@Nullable BigDecimal costAmount)
Original property name from the Odata EDM: CostAmount
goods issue.this.public BillingDocumentItem.BillingDocumentItemBuilder subtotal1Amount(@Nullable BigDecimal subtotal1Amount)
Original property name from the Odata EDM: Subtotal1Amount
this.public BillingDocumentItem.BillingDocumentItemBuilder subtotal2Amount(@Nullable BigDecimal subtotal2Amount)
Original property name from the Odata EDM: Subtotal2Amount
this.public BillingDocumentItem.BillingDocumentItemBuilder subtotal3Amount(@Nullable BigDecimal subtotal3Amount)
Original property name from the Odata EDM: Subtotal3Amount
this.public BillingDocumentItem.BillingDocumentItemBuilder subtotal4Amount(@Nullable BigDecimal subtotal4Amount)
Original property name from the Odata EDM: Subtotal4Amount
this.public BillingDocumentItem.BillingDocumentItemBuilder subtotal5Amount(@Nullable BigDecimal subtotal5Amount)
Original property name from the Odata EDM: Subtotal5Amount
this.public BillingDocumentItem.BillingDocumentItemBuilder subtotal6Amount(@Nullable BigDecimal subtotal6Amount)
Original property name from the Odata EDM: Subtotal6Amount
this.public BillingDocumentItem.BillingDocumentItemBuilder statisticalValueControl(@Nullable String statisticalValueControl)
Original property name from the Odata EDM: StatisticalValueControl
of a document.this.public BillingDocumentItem.BillingDocumentItemBuilder cashDiscountIsDeductible(@Nullable Boolean cashDiscountIsDeductible)
Original property name from the Odata EDM: CashDiscountIsDeductible
this.public BillingDocumentItem.BillingDocumentItemBuilder customerConditionGroup1(@Nullable String customerConditionGroup1)
Original property name from the Odata EDM: CustomerConditionGroup1
used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.this.public BillingDocumentItem.BillingDocumentItemBuilder customerConditionGroup2(@Nullable String customerConditionGroup2)
Original property name from the Odata EDM: CustomerConditionGroup2
used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.this.public BillingDocumentItem.BillingDocumentItemBuilder customerConditionGroup3(@Nullable String customerConditionGroup3)
Original property name from the Odata EDM: CustomerConditionGroup3
used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.this.public BillingDocumentItem.BillingDocumentItemBuilder customerConditionGroup4(@Nullable String customerConditionGroup4)
Original property name from the Odata EDM: CustomerConditionGroup4
used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.this.public BillingDocumentItem.BillingDocumentItemBuilder customerConditionGroup5(@Nullable String customerConditionGroup5)
Original property name from the Odata EDM: CustomerConditionGroup5
used during subsequent processing (order, delivery, billing document...) for condition determination and pricing.this.public BillingDocumentItem.BillingDocumentItemBuilder manualPriceChangeType(@Nullable String manualPriceChangeType)
Original property name from the Odata EDM: ManualPriceChangeType
this.public BillingDocumentItem.BillingDocumentItemBuilder materialPricingGroup(@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)
this.public BillingDocumentItem.BillingDocumentItemBuilder absltStatisticsExchangeRate(@Nullable BigDecimal absltStatisticsExchangeRate)
Original property name from the Odata EDM: AbsltStatisticsExchangeRate
this.public BillingDocumentItem.BillingDocumentItemBuilder statisticsExchRateIsIndrctQtan(@Nullable Boolean statisticsExchRateIsIndrctQtan)
Original property name from the Odata EDM: StatisticsExchRateIsIndrctQtan
this.public BillingDocumentItem.BillingDocumentItemBuilder mainItemPricingRefMaterial(@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.
should base its calculations for pricing for the main item.this.public BillingDocumentItem.BillingDocumentItemBuilder mainItemMaterialPricingGroup(@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)
this.public BillingDocumentItem.BillingDocumentItemBuilder departureCountry(@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)
this.public BillingDocumentItem.BillingDocumentItemBuilder taxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
authorities you must pay your taxes. It is always the city to which the goods are supplied.this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification1(@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.
(for example, state sales taxes).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification2(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification3(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification4(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification5(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification6(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification7(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification8(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder productTaxClassification9(@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.
(for example, VAT in the UK or state sales taxes in the USA).this.public BillingDocumentItem.BillingDocumentItemBuilder zeroVATRsn(@Nullable String zeroVATRsn)
Original property name from the Odata EDM: ZeroVATRsn
the tax purposes.
this.public BillingDocumentItem.BillingDocumentItemBuilder eligibleAmountForCashDiscount(@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.
currency.this.public BillingDocumentItem.BillingDocumentItemBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
this.public BillingDocumentItem.BillingDocumentItemBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
this.public BillingDocumentItem.BillingDocumentItemBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
this.public BillingDocumentItem.BillingDocumentItemBuilder controllingArea(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder profitabilitySegment(@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
this.public BillingDocumentItem.BillingDocumentItemBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
this.public BillingDocumentItem.BillingDocumentItemBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
this.public BillingDocumentItem.BillingDocumentItemBuilder originSDDocument(@Nullable String originSDDocument)
Original property name from the Odata EDM: OriginSDDocument
this.public BillingDocumentItem.BillingDocumentItemBuilder originSDDocumentItem(@Nullable String originSDDocumentItem)
Original property name from the Odata EDM: OriginSDDocumentItem
this.public BillingDocumentItem.BillingDocumentItemBuilder matlAccountAssignmentGroup(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder referenceSDDocument(@Nullable String referenceSDDocument)
Original property name from the Odata EDM: ReferenceSDDocument
this.public BillingDocumentItem.BillingDocumentItemBuilder referenceSDDocumentItem(@Nullable String referenceSDDocumentItem)
Original property name from the Odata EDM: ReferenceSDDocumentItem
this.public BillingDocumentItem.BillingDocumentItemBuilder referenceSDDocumentCategory(@Nullable String referenceSDDocumentCategory)
Original property name from the Odata EDM: ReferenceSDDocumentCategory
this.public BillingDocumentItem.BillingDocumentItemBuilder salesDocument(@Nullable String salesDocument)
Original property name from the Odata EDM: SalesDocument
this.public BillingDocumentItem.BillingDocumentItemBuilder salesDocumentItem(@Nullable String salesDocumentItem)
Original property name from the Odata EDM: SalesDocumentItem
this.public BillingDocumentItem.BillingDocumentItemBuilder salesSDDocumentCategory(@Nullable String salesSDDocumentCategory)
Original property name from the Odata EDM: SalesSDDocumentCategory
this.public BillingDocumentItem.BillingDocumentItemBuilder higherLevelItem(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder billingDocumentItemInPartSgmt(@Nullable String billingDocumentItemInPartSgmt)
Original property name from the Odata EDM: BillingDocumentItemInPartSgmt
this.public BillingDocumentItem.BillingDocumentItemBuilder externalReferenceDocument(@Nullable String externalReferenceDocument)
Original property name from the Odata EDM: ExternalReferenceDocument
this.public BillingDocumentItem.BillingDocumentItemBuilder externalReferenceDocumentItem(@Nullable String externalReferenceDocumentItem)
Original property name from the Odata EDM: ExternalReferenceDocumentItem
this.public BillingDocumentItem.BillingDocumentItemBuilder salesGroup(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder additionalCustomerGroup1(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder additionalCustomerGroup2(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder additionalCustomerGroup3(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder additionalCustomerGroup4(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder additionalCustomerGroup5(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder sDDocumentReason(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder retailPromotion(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder rebateBasisAmount(@Nullable BigDecimal rebateBasisAmount)
Original property name from the Odata EDM: RebateBasisAmount
this.public BillingDocumentItem.BillingDocumentItemBuilder volumeRebateGroup(@Nullable String volumeRebateGroup)
Original property name from the Odata EDM: VolumeRebateGroup
this.public BillingDocumentItem.BillingDocumentItemBuilder itemIsRelevantForCredit(@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.
delivery, or invoice items are active.this.public BillingDocumentItem.BillingDocumentItemBuilder creditRelatedPrice(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder salesDeal(@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).
this.public BillingDocumentItem.BillingDocumentItemBuilder salesPromotion(@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).
this.public BillingDocumentItem.BillingDocumentItemBuilder salesOrderSalesDistrict(@Nullable String salesOrderSalesDistrict)
Original property name from the Odata EDM: SalesOrderSalesDistrict
this.public BillingDocumentItem.BillingDocumentItemBuilder salesOrderCustomerGroup(@Nullable String salesOrderCustomerGroup)
Original property name from the Odata EDM: SalesOrderCustomerGroup
or generating statistics.this.public BillingDocumentItem.BillingDocumentItemBuilder salesOrderCustomerPriceGroup(@Nullable String salesOrderCustomerPriceGroup)
Original property name from the Odata EDM: SalesOrderCustomerPriceGroup
this.public BillingDocumentItem.BillingDocumentItemBuilder salesOrderPriceListType(@Nullable String salesOrderPriceListType)
Original property name from the Odata EDM: SalesOrderPriceListType
defined in the sales document.this.public BillingDocumentItem.BillingDocumentItemBuilder salesOrderSalesOrganization(@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.
this.public BillingDocumentItem.BillingDocumentItemBuilder salesOrderDistributionChannel(@Nullable String salesOrderDistributionChannel)
Original property name from the Odata EDM: SalesOrderDistributionChannel
this.public BillingDocumentItem.BillingDocumentItemBuilder salesDocIsCreatedFromReference(@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).
this.public BillingDocumentItem.BillingDocumentItemBuilder shippingPoint(@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.
item.this.public BillingDocumentItem.BillingDocumentItemBuilder higherLevelItemUsage(@Nullable String higherLevelItemUsage)
Original property name from the Odata EDM: HigherLevelItemUsage
this.public BillingDocumentItem build()
Copyright © 2020 SAP SE. All rights reserved.