BillingDocumentRequestItem.BillingDocumentRequestItemBuilder (SAP Cloud SDK

java.lang.Object
- com.sap.cloud.sdk.s4hana.datamodel.odata.namespaces.billingdocumentrequest.BillingDocumentRequestItem.BillingDocumentRequestItemBuilder

Enclosing class:

BillingDocumentRequestItem
```
public static final class BillingDocumentRequestItem.BillingDocumentRequestItemBuilder
extends Object
```
Helper class to allow for fluent creation of BillingDocumentRequestItem instances.

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`absltPriceDetnExchangeRate(BigDecimal absltPriceDetnExchangeRate)` Constraints: Not nullable, Precision: 9, Scale: 5
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`billgDocRequestItemInPartSgmt(String billgDocRequestItemInPartSgmt)` Constraints: Not nullable, Maximum length: 6
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`billingDocumentRequest(BillingDocumentRequest value)` Navigation property to_BillingDocumentRequest for BillingDocumentRequestItem to single BillingDocumentRequest.
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`billingDocumentRequest(String value)` (Key Field) Constraints: Not nullable, Maximum length: 10
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`billingDocumentRequestItem(String billingDocumentRequestItem)` (Key Field) Constraints: Not nullable, Maximum length: 6
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`billingDocumentRequestItemText(String billingDocumentRequestItemText)` Constraints: Not nullable, Maximum length: 40
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`billingQuantity(BigDecimal billingQuantity)` Constraints: Not nullable, Precision: 13, Scale: 3
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`billingQuantityUnit(String billingQuantityUnit)` Constraints: Not nullable, Maximum length: 3
`BillingDocumentRequestItem`	`build()`
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`businessArea(String businessArea)` Constraints: Not nullable, Maximum length: 4
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`controllingArea(String controllingArea)` Constraints: Not nullable, Maximum length: 4
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`costCenter(String costCenter)` Constraints: Not nullable, Maximum length: 10
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`creationDate(LocalDateTime creationDate)` Constraints: Not nullable, Precision: 0
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`creationTime(LocalTime creationTime)` Constraints: Not nullable, Precision: 0
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`departureCountry(String departureCountry)` Constraints: Not nullable, Maximum length: 3
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`division(String division)` Constraints: Not nullable, Maximum length: 2
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`grossAmount(BigDecimal grossAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`higherLevelItem(String higherLevelItem)` Constraints: Not nullable, Maximum length: 6
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`material(String material)` Constraints: Not nullable, Maximum length: 40
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`matlAccountAssignmentGroup(String matlAccountAssignmentGroup)` Constraints: Not nullable, Maximum length: 2
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`netAmount(BigDecimal netAmount)` Constraints: Not nullable, Precision: 16, Scale: 3
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`orderID(String orderID)` Constraints: Not nullable, Maximum length: 12
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`partner(BillingDocReqItemPartner... value)` Navigation property to_Partner for BillingDocumentRequestItem to multiple BillingDocReqItemPartner.
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`plant(String plant)` Constraints: Not nullable, Maximum length: 4
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`priceDetnExchRateIsIndrctQtan(Boolean priceDetnExchRateIsIndrctQtan)` Constraints: none
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`pricingDate(LocalDateTime pricingDate)` Constraints: Not nullable, Precision: 0
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`pricingElement(BillingDocReqItemPrcgElmnt... value)` Navigation property to_PricingElement for BillingDocumentRequestItem to multiple BillingDocReqItemPrcgElmnt.
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`productHierarchyNode(String productHierarchyNode)` Constraints: Not nullable, Maximum length: 18
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`productTaxClassification1(String productTaxClassification1)` Constraints: Not nullable, Maximum length: 1
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`profitabilitySegment(String profitabilitySegment)` Constraints: Not nullable, Maximum length: 10
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`profitCenter(String profitCenter)` Constraints: Not nullable, Maximum length: 10
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`referenceDocument(String referenceDocument)` Constraints: Not nullable, Maximum length: 10
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`referenceDocumentItem(String referenceDocumentItem)` Constraints: Not nullable, Maximum length: 6
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`referenceLogicalSystem(String referenceLogicalSystem)` Constraints: Not nullable, Maximum length: 10
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`servicesRenderedDate(LocalDateTime servicesRenderedDate)` Constraints: Not nullable, Precision: 0
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`taxAmount(BigDecimal taxAmount)` Constraints: Not nullable, Precision: 14, Scale: 3
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`taxJurisdiction(String taxJurisdiction)` Constraints: Not nullable, Maximum length: 15
`String`	`toString()`
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`transactionCurrency(String transactionCurrency)` Constraints: Not nullable, Maximum length: 5
`BillingDocumentRequestItem.BillingDocumentRequestItemBuilder`	`wBSElement(String wBSElement)` Constraints: Not nullable, Maximum length: 24

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

- Method Detail
  - billingDocumentRequest
```
@Nonnull
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder billingDocumentRequest(BillingDocumentRequest value)
```
    Navigation property to_BillingDocumentRequest for BillingDocumentRequestItem to single BillingDocumentRequest.
    
    Parameters:
    
    value - The BillingDocumentRequest to build this BillingDocumentRequestItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - billingDocumentRequest
```
@Nonnull
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder billingDocumentRequest(String value)
```
    (Key Field) Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: BillingDocumentRequest
    
    Parameters:
    
    value - The billingDocumentRequest to build this BillingDocumentRequestItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - partner
```
@Nonnull
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder partner(BillingDocReqItemPartner... value)
```
    Navigation property to_Partner for BillingDocumentRequestItem to multiple BillingDocReqItemPartner.
    
    Parameters:
    
    value - The BillingDocReqItemPartners to build this BillingDocumentRequestItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - pricingElement
```
@Nonnull
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder pricingElement(BillingDocReqItemPrcgElmnt... value)
```
    Navigation property to_PricingElement for BillingDocumentRequestItem to multiple BillingDocReqItemPrcgElmnt.
    
    Parameters:
    
    value - The BillingDocReqItemPrcgElmnts to build this BillingDocumentRequestItem with.
    
    Returns:
    
    This Builder to allow for a fluent interface.
  - billingDocumentRequestItem
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder billingDocumentRequestItem(@Nullable
                                                                                               String billingDocumentRequestItem)
```
    (Key Field) Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: BillingDocumentRequestItem
  - creationDate
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder creationDate(@Nullable
                                                                                 LocalDateTime creationDate)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationDate
  - creationTime
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder creationTime(@Nullable
                                                                                 LocalTime creationTime)
```
    Constraints: Not nullable, Precision: 0
    Original property name from the Odata EDM: CreationTime
  - referenceLogicalSystem
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder referenceLogicalSystem(@Nullable
                                                                                           String referenceLogicalSystem)
```
    Constraints: Not nullable, Maximum length: 10
    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.
  - division
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder division(@Nullable
                                                                             String division)
```
    Constraints: Not nullable, Maximum length: 2
    Original property name from the Odata EDM: Division
    
    A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
    areas and the business areas for a material, product, or service.
  - material
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder material(@Nullable
                                                                             String material)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: Material
  - productHierarchyNode
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder productHierarchyNode(@Nullable
                                                                                         String productHierarchyNode)
```
    Constraints: Not nullable, Maximum length: 18
    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.
  - plant
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder plant(@Nullable
                                                                          String plant)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: Plant
  - billingDocumentRequestItemText
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder billingDocumentRequestItemText(@Nullable
                                                                                                   String billingDocumentRequestItemText)
```
    Constraints: Not nullable, Maximum length: 40
    Original property name from the Odata EDM: BillingDocumentRequestItemText
    
    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.
  - servicesRenderedDate
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder servicesRenderedDate(@Nullable
                                                                                         LocalDateTime servicesRenderedDate)
```
    Constraints: Not nullable, Precision: 0
    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.
  - billingQuantity
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder billingQuantity(@Nullable
                                                                                    BigDecimal billingQuantity)
```
    Constraints: Not nullable, Precision: 13, Scale: 3
    Original property name from the Odata EDM: BillingQuantity
    
    For assets in which a base unit of measure is entered, you can enter a quantity when you post acquisitions and retirements. The system then updates the asset according to this quantity when you post, based on the debit/credit flag of the transaction posted.In addition, you can already specify a quantity when you create a new asset master record. However, any quantity you enter in master data maintenance (such as 1) is added to any quantity that is entered in the acquisition posting.
  - billingQuantityUnit
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder billingQuantityUnit(@Nullable
                                                                                        String billingQuantityUnit)
```
    Constraints: Not nullable, Maximum length: 3
    Original property name from the Odata EDM: BillingQuantityUnit
  - netAmount
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder netAmount(@Nullable
                                                                              BigDecimal netAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: NetAmount
    freight costs), but excluding sales taxes.
  - transactionCurrency
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder transactionCurrency(@Nullable
                                                                                        String transactionCurrency)
```
    Constraints: Not nullable, Maximum length: 5
    Original property name from the Odata EDM: TransactionCurrency
    
    The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
  - grossAmount
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder grossAmount(@Nullable
                                                                                BigDecimal grossAmount)
```
    Constraints: Not nullable, Precision: 16, Scale: 3
    Original property name from the Odata EDM: GrossAmount
    conditions (e.g. freight costs) but without VAT.
  - pricingDate
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder pricingDate(@Nullable
                                                                                LocalDateTime pricingDate)
```
    Constraints: Not nullable, Precision: 0
    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.
  - absltPriceDetnExchangeRate
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder absltPriceDetnExchangeRate(@Nullable
                                                                                               BigDecimal absltPriceDetnExchangeRate)
```
    Constraints: Not nullable, Precision: 9, Scale: 5
    Original property name from the Odata EDM: AbsltPriceDetnExchangeRate
  - priceDetnExchRateIsIndrctQtan
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder priceDetnExchRateIsIndrctQtan(@Nullable
                                                                                                  Boolean priceDetnExchRateIsIndrctQtan)
```
    Constraints: none
    Original property name from the Odata EDM: PriceDetnExchRateIsIndrctQtan
  - taxAmount
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder taxAmount(@Nullable
                                                                              BigDecimal taxAmount)
```
    Constraints: Not nullable, Precision: 14, Scale: 3
    Original property name from the Odata EDM: TaxAmount
  - departureCountry
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder departureCountry(@Nullable
                                                                                     String departureCountry)
```
    Constraints: Not nullable, Maximum length: 3
    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)
  - taxJurisdiction
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder taxJurisdiction(@Nullable
                                                                                    String taxJurisdiction)
```
    Constraints: Not nullable, Maximum length: 15
    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.
  - productTaxClassification1
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder productTaxClassification1(@Nullable
                                                                                              String productTaxClassification1)
```
    Constraints: Not nullable, Maximum length: 1
    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).
  - businessArea
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder businessArea(@Nullable
                                                                                 String businessArea)
```
    Constraints: Not nullable, Maximum length: 4
    Original property name from the Odata EDM: BusinessArea
  - profitCenter
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder profitCenter(@Nullable
                                                                                 String profitCenter)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ProfitCenter
  - wBSElement
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder wBSElement(@Nullable
                                                                               String wBSElement)
```
    Constraints: Not nullable, Maximum length: 24
    Original property name from the Odata EDM: WBSElement
  - controllingArea
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder controllingArea(@Nullable
                                                                                    String controllingArea)
```
    Constraints: Not nullable, Maximum length: 4
    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.
  - profitabilitySegment
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder profitabilitySegment(@Nullable
                                                                                         String profitabilitySegment)
```
    Constraints: Not nullable, Maximum length: 10
    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
  - orderID
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder orderID(@Nullable
                                                                            String orderID)
```
    Constraints: Not nullable, Maximum length: 12
    Original property name from the Odata EDM: OrderID
  - costCenter
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder costCenter(@Nullable
                                                                               String costCenter)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: CostCenter
  - matlAccountAssignmentGroup
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder matlAccountAssignmentGroup(@Nullable
                                                                                               String matlAccountAssignmentGroup)
```
    Constraints: Not nullable, Maximum length: 2
    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.
  - referenceDocument
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder referenceDocument(@Nullable
                                                                                      String referenceDocument)
```
    Constraints: Not nullable, Maximum length: 10
    Original property name from the Odata EDM: ReferenceDocument
  - referenceDocumentItem
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder referenceDocumentItem(@Nullable
                                                                                          String referenceDocumentItem)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: ReferenceDocumentItem
  - higherLevelItem
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder higherLevelItem(@Nullable
                                                                                    String higherLevelItem)
```
    Constraints: Not nullable, Maximum length: 6
    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.
  - billgDocRequestItemInPartSgmt
```
public BillingDocumentRequestItem.BillingDocumentRequestItemBuilder billgDocRequestItemInPartSgmt(@Nullable
                                                                                                  String billgDocRequestItemInPartSgmt)
```
    Constraints: Not nullable, Maximum length: 6
    Original property name from the Odata EDM: BillgDocRequestItemInPartSgmt
  - build
```
public BillingDocumentRequestItem build()
```
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class Object

Class BillingDocumentRequestItem.BillingDocumentRequestItemBuilder

Method Summary

Methods inherited from class java.lang.Object

Method Detail

billingDocumentRequest

billingDocumentRequest

partner

pricingElement

billingDocumentRequestItem

creationDate

creationTime

referenceLogicalSystem

division

material

productHierarchyNode

plant

billingDocumentRequestItemText

servicesRenderedDate

billingQuantity

billingQuantityUnit

netAmount

transactionCurrency

grossAmount

pricingDate

absltPriceDetnExchangeRate

priceDetnExchRateIsIndrctQtan

taxAmount

departureCountry

taxJurisdiction

productTaxClassification1

businessArea

profitCenter

wBSElement

controllingArea

profitabilitySegment

orderID

costCenter

matlAccountAssignmentGroup

referenceDocument

referenceDocumentItem

higherLevelItem

billgDocRequestItemInPartSgmt

build

toString