public static final class BillingDocument.BillingDocumentBuilder extends Object
Modifier and Type | Method and Description |
---|---|
BillingDocument.BillingDocumentBuilder |
absltAccountingExchangeRate(BigDecimal absltAccountingExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5
|
BillingDocument.BillingDocumentBuilder |
accountingDocument(String accountingDocument)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
accountingExchangeRateIsSet(Boolean accountingExchangeRateIsSet)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
accountingPostingStatus(String accountingPostingStatus)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
accountingTransferStatus(String accountingTransferStatus)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
acctgExchangeRateIsIndrctQtan(Boolean acctgExchangeRateIsIndrctQtan)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
additionalValueDays(String additionalValueDays)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
assignmentReference(String assignmentReference)
Constraints: Not nullable, Maximum length: 18
|
BillingDocument.BillingDocumentBuilder |
billingDocCombinationCriteria(String billingDocCombinationCriteria)
Constraints: Not nullable, Maximum length: 40
|
BillingDocument.BillingDocumentBuilder |
billingDocument(String billingDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
billingDocumentCategory(String billingDocumentCategory)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
billingDocumentDate(LocalDateTime billingDocumentDate)
Constraints: Not nullable, Precision: 0
|
BillingDocument.BillingDocumentBuilder |
billingDocumentIsCancelled(Boolean billingDocumentIsCancelled)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
billingDocumentListDate(LocalDateTime billingDocumentListDate)
Constraints: Not nullable, Precision: 0
|
BillingDocument.BillingDocumentBuilder |
billingDocumentListType(String billingDocumentListType)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
billingDocumentType(String billingDocumentType)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
billingIssueType(String billingIssueType)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument |
build() |
BillingDocument.BillingDocumentBuilder |
cancelledBillingDocument(String cancelledBillingDocument)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
cityCode(String cityCode)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
companyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
contractAccount(String contractAccount)
Constraints: Not nullable, Maximum length: 12
|
BillingDocument.BillingDocumentBuilder |
country(String country)
Constraints: Not nullable, Maximum length: 3
|
BillingDocument.BillingDocumentBuilder |
county(String county)
Constraints: Not nullable, Maximum length: 3
|
BillingDocument.BillingDocumentBuilder |
creationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
BillingDocument.BillingDocumentBuilder |
creationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
BillingDocument.BillingDocumentBuilder |
creditControlArea(String creditControlArea)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
customerAccountAssignmentGroup(String customerAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
customerGroup(String customerGroup)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
customerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
customerPriceGroup(String customerPriceGroup)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
customerRebateAgreement(String customerRebateAgreement)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification1(String customerTaxClassification1)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification2(String customerTaxClassification2)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification3(String customerTaxClassification3)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification4(String customerTaxClassification4)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification5(String customerTaxClassification5)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification6(String customerTaxClassification6)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification7(String customerTaxClassification7)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification8(String customerTaxClassification8)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
customerTaxClassification9(String customerTaxClassification9)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
distributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
division(String division)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
documentReferenceID(String documentReferenceID)
Constraints: Not nullable, Maximum length: 16
|
BillingDocument.BillingDocumentBuilder |
dunningArea(String dunningArea)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
dunningBlockingReason(String dunningBlockingReason)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
dunningKey(String dunningKey)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
exchangeRateDate(LocalDateTime exchangeRateDate)
Constraints: Not nullable, Precision: 0
|
BillingDocument.BillingDocumentBuilder |
exchangeRateType(String exchangeRateType)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
fiscalYear(String fiscalYear)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
fixedValueDate(LocalDateTime fixedValueDate)
Constraints: Not nullable, Precision: 0
|
BillingDocument.BillingDocumentBuilder |
foreignTrade(String foreignTrade)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
hierarchyTypePricing(String hierarchyTypePricing)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
incotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
BillingDocument.BillingDocumentBuilder |
incotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
BillingDocument.BillingDocumentBuilder |
incotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
BillingDocument.BillingDocumentBuilder |
incotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
BillingDocument.BillingDocumentBuilder |
incotermsVersion(String incotermsVersion)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
internalFinancialDocument(String internalFinancialDocument)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
invoiceClearingStatus(String invoiceClearingStatus)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
invoiceListStatus(String invoiceListStatus)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
isEUTriangularDeal(Boolean isEUTriangularDeal)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
isExportDelivery(String isExportDelivery)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
isIntrastatReportingExcluded(Boolean isIntrastatReportingExcluded)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
isIntrastatReportingRelevant(Boolean isIntrastatReportingRelevant)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
isRelevantForAccrual(Boolean isRelevantForAccrual)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
item(BillingDocumentItem... value)
Navigation property to_Item for BillingDocument to multiple BillingDocumentItem.
|
BillingDocument.BillingDocumentBuilder |
lastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
BillingDocument.BillingDocumentBuilder |
lastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
BillingDocument.BillingDocumentBuilder |
logicalSystem(String logicalSystem)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
manualInvoiceMaintIsRelevant(Boolean manualInvoiceMaintIsRelevant)
Constraints: none
|
BillingDocument.BillingDocumentBuilder |
overallBillingStatus(String overallBillingStatus)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
overallPricingIncompletionSts(String overallPricingIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
overallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
ovrlItmGeneralIncompletionSts(String ovrlItmGeneralIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
partner(BillingDocumentPartner... value)
Navigation property to_Partner for BillingDocument to multiple BillingDocumentPartner.
|
BillingDocument.BillingDocumentBuilder |
partnerCompany(String partnerCompany)
Constraints: Not nullable, Maximum length: 6
|
BillingDocument.BillingDocumentBuilder |
payerParty(String payerParty)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
paymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
BillingDocument.BillingDocumentBuilder |
paymentReference(String paymentReference)
Constraints: Not nullable, Maximum length: 30
|
BillingDocument.BillingDocumentBuilder |
priceListType(String priceListType)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
pricingElement(BillingDocumentPrcgElmnt... value)
Navigation property to_PricingElement for BillingDocument to multiple
BillingDocumentPrcgElmnt.
|
BillingDocument.BillingDocumentBuilder |
purchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
BillingDocument.BillingDocumentBuilder |
region(String region)
Constraints: Not nullable, Maximum length: 3
|
BillingDocument.BillingDocumentBuilder |
salesDistrict(String salesDistrict)
Constraints: Not nullable, Maximum length: 6
|
BillingDocument.BillingDocumentBuilder |
salesDocumentCondition(String salesDocumentCondition)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
salesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
sDDocumentCategory(String sDDocumentCategory)
Constraints: Not nullable, Maximum length: 4
|
BillingDocument.BillingDocumentBuilder |
sDPricingProcedure(String sDPricingProcedure)
Constraints: Not nullable, Maximum length: 6
|
BillingDocument.BillingDocumentBuilder |
sEPAMandate(String sEPAMandate)
Constraints: Not nullable, Maximum length: 35
|
BillingDocument.BillingDocumentBuilder |
shippingCondition(String shippingCondition)
Constraints: Not nullable, Maximum length: 2
|
BillingDocument.BillingDocumentBuilder |
soldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
BillingDocument.BillingDocumentBuilder |
statisticsCurrency(String statisticsCurrency)
Constraints: Not nullable, Maximum length: 5
|
BillingDocument.BillingDocumentBuilder |
taxAmount(BigDecimal taxAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
BillingDocument.BillingDocumentBuilder |
taxDepartureCountry(String taxDepartureCountry)
Constraints: Not nullable, Maximum length: 3
|
BillingDocument.BillingDocumentBuilder |
text(BillingDocumentText... value)
Navigation property to_Text for BillingDocument to multiple BillingDocumentText.
|
String |
toString() |
BillingDocument.BillingDocumentBuilder |
totalGrossAmount(BigDecimal totalGrossAmount)
Constraints: Not nullable, Precision: 17, Scale: 3
|
BillingDocument.BillingDocumentBuilder |
totalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
BillingDocument.BillingDocumentBuilder |
transactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
BillingDocument.BillingDocumentBuilder |
vATRegistration(String vATRegistration)
Constraints: Not nullable, Maximum length: 20
|
BillingDocument.BillingDocumentBuilder |
vATRegistrationCountry(String vATRegistrationCountry)
Constraints: Not nullable, Maximum length: 3
|
BillingDocument.BillingDocumentBuilder |
vATRegistrationOrigin(String vATRegistrationOrigin)
Constraints: Not nullable, Maximum length: 1
|
@Nonnull public BillingDocument.BillingDocumentBuilder item(BillingDocumentItem... value)
value
- The BillingDocumentItems to build this BillingDocument with.@Nonnull public BillingDocument.BillingDocumentBuilder partner(BillingDocumentPartner... value)
value
- The BillingDocumentPartners to build this BillingDocument with.@Nonnull public BillingDocument.BillingDocumentBuilder pricingElement(BillingDocumentPrcgElmnt... value)
value
- The BillingDocumentPrcgElmnts to build this BillingDocument with.@Nonnull public BillingDocument.BillingDocumentBuilder text(BillingDocumentText... value)
value
- The BillingDocumentTexts to build this BillingDocument with.public BillingDocument.BillingDocumentBuilder billingDocument(@Nullable String billingDocument)
Original property name from the Odata EDM: BillingDocument
this
.public BillingDocument.BillingDocumentBuilder sDDocumentCategory(@Nullable String sDDocumentCategory)
Original property name from the Odata EDM: SDDocumentCategory
The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations).
sales orders, deliveries, and invoices.this
.public BillingDocument.BillingDocumentBuilder billingDocumentCategory(@Nullable String billingDocumentCategory)
Original property name from the Odata EDM: BillingDocumentCategory
this
.public BillingDocument.BillingDocumentBuilder billingDocumentType(@Nullable String billingDocumentType)
Original property name from the Odata EDM: BillingDocumentType
When you process billing documents collectively, you can use the billing type as one of the selection criteria.
this
.public BillingDocument.BillingDocumentBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this
.public BillingDocument.BillingDocumentBuilder creationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
this
.public BillingDocument.BillingDocumentBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
this
.public BillingDocument.BillingDocumentBuilder lastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
this
.public BillingDocument.BillingDocumentBuilder logicalSystem(@Nullable String logicalSystem)
Original property name from the Odata EDM: LogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
this
.public BillingDocument.BillingDocumentBuilder salesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
sales organization may include legal liability for products and customer claims.this
.public BillingDocument.BillingDocumentBuilder distributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
wholesale, retail, or direct sales.this
.public BillingDocument.BillingDocumentBuilder 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 BillingDocument.BillingDocumentBuilder billingDocumentDate(@Nullable LocalDateTime billingDocumentDate)
Original property name from the Odata EDM: BillingDocumentDate
When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
this
.public BillingDocument.BillingDocumentBuilder billingDocumentIsCancelled(@Nullable Boolean billingDocumentIsCancelled)
Original property name from the Odata EDM: BillingDocumentIsCancelled
this
.public BillingDocument.BillingDocumentBuilder cancelledBillingDocument(@Nullable String cancelledBillingDocument)
Original property name from the Odata EDM: CancelledBillingDocument
this
.public BillingDocument.BillingDocumentBuilder foreignTrade(@Nullable String foreignTrade)
Original property name from the Odata EDM: ForeignTrade
this
.public BillingDocument.BillingDocumentBuilder isExportDelivery(@Nullable String isExportDelivery)
Original property name from the Odata EDM: IsExportDelivery
this
.public BillingDocument.BillingDocumentBuilder billingDocCombinationCriteria(@Nullable String billingDocCombinationCriteria)
Original property name from the Odata EDM: BillingDocCombinationCriteria
this
.public BillingDocument.BillingDocumentBuilder manualInvoiceMaintIsRelevant(@Nullable Boolean manualInvoiceMaintIsRelevant)
Original property name from the Odata EDM: ManualInvoiceMaintIsRelevant
The system proposes the value from the customer master record. You can change the indicator manually in the sales document.
this
.public BillingDocument.BillingDocumentBuilder isIntrastatReportingRelevant(@Nullable Boolean isIntrastatReportingRelevant)
Original property name from the Odata EDM: IsIntrastatReportingRelevant
this
.public BillingDocument.BillingDocumentBuilder isIntrastatReportingExcluded(@Nullable Boolean isIntrastatReportingExcluded)
Original property name from the Odata EDM: IsIntrastatReportingExcluded
this
.public BillingDocument.BillingDocumentBuilder totalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
this
.public BillingDocument.BillingDocumentBuilder 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 BillingDocument.BillingDocumentBuilder statisticsCurrency(@Nullable String statisticsCurrency)
Original property name from the Odata EDM: StatisticsCurrency
this
.public BillingDocument.BillingDocumentBuilder taxAmount(@Nullable BigDecimal taxAmount)
Original property name from the Odata EDM: TaxAmount
this
.public BillingDocument.BillingDocumentBuilder totalGrossAmount(@Nullable BigDecimal totalGrossAmount)
Original property name from the Odata EDM: TotalGrossAmount
this
.public BillingDocument.BillingDocumentBuilder customerPriceGroup(@Nullable String customerPriceGroup)
Original property name from the Odata EDM: CustomerPriceGroup
You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level.
this
.public BillingDocument.BillingDocumentBuilder priceListType(@Nullable String priceListType)
Original property name from the Odata EDM: PriceListType
You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header.
this
.public BillingDocument.BillingDocumentBuilder taxDepartureCountry(@Nullable String taxDepartureCountry)
Original property name from the Odata EDM: TaxDepartureCountry
A different country needs to be entered for certain internal European transactions (chain transactions).
this
.public BillingDocument.BillingDocumentBuilder vATRegistration(@Nullable String vATRegistration)
Original property name from the Odata EDM: VATRegistration
The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.
this
.public BillingDocument.BillingDocumentBuilder vATRegistrationOrigin(@Nullable String vATRegistrationOrigin)
Original property name from the Odata EDM: VATRegistrationOrigin
this
.public BillingDocument.BillingDocumentBuilder vATRegistrationCountry(@Nullable String vATRegistrationCountry)
Original property name from the Odata EDM: VATRegistrationCountry
This key is used to check country-specific entries such as the length of the zip code or bank account number.
this
.public BillingDocument.BillingDocumentBuilder hierarchyTypePricing(@Nullable String hierarchyTypePricing)
Original property name from the Odata EDM: HierarchyTypePricing
this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification1(@Nullable String customerTaxClassification1)
Original property name from the Odata EDM: CustomerTaxClassification1
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification2(@Nullable String customerTaxClassification2)
Original property name from the Odata EDM: CustomerTaxClassification2
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification3(@Nullable String customerTaxClassification3)
Original property name from the Odata EDM: CustomerTaxClassification3
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification4(@Nullable String customerTaxClassification4)
Original property name from the Odata EDM: CustomerTaxClassification4
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification5(@Nullable String customerTaxClassification5)
Original property name from the Odata EDM: CustomerTaxClassification5
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification6(@Nullable String customerTaxClassification6)
Original property name from the Odata EDM: CustomerTaxClassification6
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification7(@Nullable String customerTaxClassification7)
Original property name from the Odata EDM: CustomerTaxClassification7
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification8(@Nullable String customerTaxClassification8)
Original property name from the Odata EDM: CustomerTaxClassification8
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder customerTaxClassification9(@Nullable String customerTaxClassification9)
Original property name from the Odata EDM: CustomerTaxClassification9
The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes.
example, state sales taxes).this
.public BillingDocument.BillingDocumentBuilder isEUTriangularDeal(@Nullable Boolean isEUTriangularDeal)
Original property name from the Odata EDM: IsEUTriangularDeal
deal section.this
.public BillingDocument.BillingDocumentBuilder sDPricingProcedure(@Nullable String sDPricingProcedure)
Original property name from the Odata EDM: SDPricingProcedure
this
.public BillingDocument.BillingDocumentBuilder shippingCondition(@Nullable String shippingCondition)
Original property name from the Odata EDM: ShippingCondition
You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments.
this
.public BillingDocument.BillingDocumentBuilder incotermsVersion(@Nullable String incotermsVersion)
Original property name from the Odata EDM: IncotermsVersion
defined by the International Chamber of Commerce (ICC).this
.public BillingDocument.BillingDocumentBuilder incotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
Commerce (ICC).this
.public BillingDocument.BillingDocumentBuilder incotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
this
.public BillingDocument.BillingDocumentBuilder incotermsLocation1(@Nullable String incotermsLocation1)
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
this
.public BillingDocument.BillingDocumentBuilder incotermsLocation2(@Nullable String incotermsLocation2)
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
customized appropriately). Note the following for the incoterms versions below:this
.public BillingDocument.BillingDocumentBuilder payerParty(@Nullable String payerParty)
Original property name from the Odata EDM: PayerParty
The payer may differ from the bill-to party who receives the bill.
this
.public BillingDocument.BillingDocumentBuilder contractAccount(@Nullable String contractAccount)
Original property name from the Odata EDM: ContractAccount
The postings in Contract Accounts Receivable and Payable are always assigned to a contract account and a business partner.In the contract account master record, specifically for each business partner, you can define procedures that are to be used for further processing of line items. These include for example, payment methods, dunning procedure, tolerances.NoteFor utility and insurance companies, a contract is assigned to exactly one contract account. However several accounts - depending on contract account type can be assigned to one contract account.
this
.public BillingDocument.BillingDocumentBuilder customerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
this
.public BillingDocument.BillingDocumentBuilder paymentMethod(@Nullable String paymentMethod)
Original property name from the Odata EDM: PaymentMethod
If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
this
.public BillingDocument.BillingDocumentBuilder paymentReference(@Nullable String paymentReference)
Original property name from the Odata EDM: PaymentReference
For vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference. In automatic payment transactions, the payment reference can be passed on again to the payee.When an outgoing payment is made, the payment reference you specify is passed on to the relevant financial institute and from there to the payee.When you are processing your account statement, you can use the payment reference to determine which items you have paid and then clear them.Payment reference numbers are often used in Finland, Norway, and Sweden. These countries also have rules for the structure of the payment reference. Check digit procedures are used to check that these rules are followed.DME Finland: The number '4477' has a check digit of '8' and should be defined as the character string '44778'.DME Norway: The number '12345678' has the check digit '2' when using the Modulo-10 method, and check digit '5' when using the Modulo-11 method. Therefore, 123456782 or 123456785 are permitted as payment references.DME Sweden: The number '1234567890' has the check digit '3' and should be defined as the character string '12345678903'. The Modulo procedure used is a form of Modulo-10 with the key '1212121'.
invoice. The customer should refer to the payment reference when making the payment.this
.public BillingDocument.BillingDocumentBuilder fixedValueDate(@Nullable LocalDateTime fixedValueDate)
Original property name from the Odata EDM: FixedValueDate
If you enter a date in this field, you cannot enter a value in the additional value days field.
this
.public BillingDocument.BillingDocumentBuilder additionalValueDays(@Nullable String additionalValueDays)
Original property name from the Odata EDM: AdditionalValueDays
If you enter a value in this field, you cannot enter a date in the fixed value date field.
document become effective.this
.public BillingDocument.BillingDocumentBuilder sEPAMandate(@Nullable String sEPAMandate)
Original property name from the Odata EDM: SEPAMandate
The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment.Whether internal or external number assignment (or both) is possible depends on the application concerned.Once you have created the mandate, you can no longer change its mandate reference.At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field.Notes on Assigning Contract Accounts and Contracts to MandatesYou can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment.Notes on Using Alternative PayersIf you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen.ExampleYou enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1.Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects.Example - Assignment of a mandate to multiple contract accountsContract account Mandate (in Contract Acct) MeaningC1 M1 Mandate M1 is valid for C1.C2 M1 Mandate M1 is also valid for C2.C3 M2 Mandate M2 is valid for C3.C4 M2 Mandate M2 is also valid for C4.Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account.Example - Assignment of one contract account per mandateMandate Contract Account (in Mandate) MeaningM1 C1 Mandate M1 is only valid for items of contract account C1.M2 C2 Mandate M2 is only valid for items of contract account C2.If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects.The examples above apply in a similar manner to the assignment of contracts.Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate.If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details.If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment.If you do not make any specification, the system uses the first mandate that qualifies for the payment.
this
.public BillingDocument.BillingDocumentBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
this
.public BillingDocument.BillingDocumentBuilder fiscalYear(@Nullable String fiscalYear)
Original property name from the Odata EDM: FiscalYear
fiscal year can be the same as the calendar year, but does not have to be.this
.public BillingDocument.BillingDocumentBuilder accountingDocument(@Nullable String accountingDocument)
Original property name from the Odata EDM: AccountingDocument
The document number is unique per company code and fiscal year. When entering an accounting document, you can specify the number manually or it can be determined by the system from a pre-defined area (number range).The relevant area of the document numbers (number range) is determined in each company code per document type.
this
.public BillingDocument.BillingDocumentBuilder customerAccountAssignmentGroup(@Nullable String customerAccountAssignmentGroup)
Original property name from the Odata EDM: CustomerAccountAssignmentGroup
The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
this
.public BillingDocument.BillingDocumentBuilder accountingExchangeRateIsSet(@Nullable Boolean accountingExchangeRateIsSet)
Original property name from the Odata EDM: AccountingExchangeRateIsSet
The system can propose a value. You can change the value manually in the sales document. If you are allowed to change the exchange rate during billing, the system recalculates prices using the most recent exchange rate.
whether it can be changed during billing.this
.public BillingDocument.BillingDocumentBuilder absltAccountingExchangeRate(@Nullable BigDecimal absltAccountingExchangeRate)
Original property name from the Odata EDM: AbsltAccountingExchangeRate
this
.public BillingDocument.BillingDocumentBuilder acctgExchangeRateIsIndrctQtan(@Nullable Boolean acctgExchangeRateIsIndrctQtan)
Original property name from the Odata EDM: AcctgExchangeRateIsIndrctQtan
this
.public BillingDocument.BillingDocumentBuilder exchangeRateDate(@Nullable LocalDateTime exchangeRateDate)
Original property name from the Odata EDM: ExchangeRateDate
You do not need to enter a date unless the date in question is not the same as the document entry date.
rates are stored in the system.this
.public BillingDocument.BillingDocumentBuilder exchangeRateType(@Nullable String exchangeRateType)
Original property name from the Odata EDM: ExchangeRateType
You enter the exchange rate type to store different exchange rates.You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
this
.public BillingDocument.BillingDocumentBuilder documentReferenceID(@Nullable String documentReferenceID)
Original property name from the Odata EDM: DocumentReferenceID
The reference document number serves as a search criterion when displaying or changing documents. In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document.
this
.public BillingDocument.BillingDocumentBuilder assignmentReference(@Nullable String assignmentReference)
Original property name from the Odata EDM: AssignmentReference
The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document.
this
.public BillingDocument.BillingDocumentBuilder dunningArea(@Nullable String dunningArea)
Original property name from the Odata EDM: DunningArea
If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
represent a sub-structure of the company codes.this
.public BillingDocument.BillingDocumentBuilder dunningBlockingReason(@Nullable String dunningBlockingReason)
Original property name from the Odata EDM: DunningBlockingReason
this
.public BillingDocument.BillingDocumentBuilder dunningKey(@Nullable String dunningKey)
Original property name from the Odata EDM: DunningKey
You define the contents of the text line in Customizing for the dunning key.If you enter a key in an item, then it can only reach the maximum dunning level defined for this key. Therefore it is possible that an item can contain one dunning notice at the most, although several dunning levels are defined in the dunning procedure.
line on the dunning notice. The keys are freely-definable.this
.public BillingDocument.BillingDocumentBuilder internalFinancialDocument(@Nullable String internalFinancialDocument)
Original property name from the Odata EDM: InternalFinancialDocument
You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance.
assigned by the system.this
.public BillingDocument.BillingDocumentBuilder isRelevantForAccrual(@Nullable Boolean isRelevantForAccrual)
Original property name from the Odata EDM: IsRelevantForAccrual
this
.public BillingDocument.BillingDocumentBuilder soldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
orders.this
.public BillingDocument.BillingDocumentBuilder partnerCompany(@Nullable String partnerCompany)
Original property name from the Odata EDM: PartnerCompany
this
.public BillingDocument.BillingDocumentBuilder purchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
order).this
.public BillingDocument.BillingDocumentBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.this
.public BillingDocument.BillingDocumentBuilder country(@Nullable String country)
Original property name from the Odata EDM: Country
As a general rule, it is best to use the existing international standards for identifying vehicles from different countries/regions (for example: USA = United States, I = Italy, and so on).The system uses the country/region key identifier to:Help determine the appropriate taxes during pricingDetermine important country/region-specific standards (the length of postal codes and bank account numbers, for example)When you process billing documents collectively, you can use the destination country as one of the selection criteria.
this
.public BillingDocument.BillingDocumentBuilder cityCode(@Nullable String cityCode)
Original property name from the Odata EDM: CityCode
Currently the key is used only in the USA for handling city tax.
county code.this
.public BillingDocument.BillingDocumentBuilder salesDistrict(@Nullable String salesDistrict)
Original property name from the Odata EDM: SalesDistrict
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
this
.public BillingDocument.BillingDocumentBuilder region(@Nullable String region)
Original property name from the Odata EDM: Region
The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State
this
.public BillingDocument.BillingDocumentBuilder county(@Nullable String county)
Original property name from the Odata EDM: County
Currently the county code is used in the USA for handling county tax, and in Denmark to define the municipality number of the employee's first place of residence.
this
.public BillingDocument.BillingDocumentBuilder creditControlArea(@Nullable String creditControlArea)
Original property name from the Odata EDM: CreditControlArea
You can also enter the credit control area separately for each posting, if this was marked in the appropriate company code.When entering an order, the credit control area can also be determined from the business area and the sales area segement of the payer's master record or using a user exit.It follows that company codes and credit control areas are not linked.The only thing that you define in the company code table is the default credit control area. This is used either for payments on account to credit these payments, or where you did not enter a credit control area or the system could not determine one.There is also an allocation table of permitted credit control areas per company code which is used to check entries only.
customers. A credit control area can include one or more company codes.this
.public BillingDocument.BillingDocumentBuilder customerRebateAgreement(@Nullable String customerRebateAgreement)
Original property name from the Odata EDM: CustomerRebateAgreement
A rebate agreement is an agreement between a customer and a supplier. On the basis of the customer's sales volume during a specified period, the supplier grants the customer a special rebate. A general rebate agreement can consist of numerous individual agreements (condition records) that are based on different factors. For example, an individualagreement may be based on a combination of customer and material or a combination of customer and rebate group, and so on.
this
.public BillingDocument.BillingDocumentBuilder salesDocumentCondition(@Nullable String salesDocumentCondition)
Original property name from the Odata EDM: SalesDocumentCondition
The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area. The system uses the internal number to identify the different conditions.
this
.public BillingDocument.BillingDocumentBuilder overallSDProcessStatus(@Nullable String overallSDProcessStatus)
Original property name from the Odata EDM: OverallSDProcessStatus
The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete.
this
.public BillingDocument.BillingDocumentBuilder overallBillingStatus(@Nullable String overallBillingStatus)
Original property name from the Odata EDM: OverallBillingStatus
this
.public BillingDocument.BillingDocumentBuilder accountingPostingStatus(@Nullable String accountingPostingStatus)
Original property name from the Odata EDM: AccountingPostingStatus
The status message tells you whether the billing document must be posted to accounting, and, if so, whether the posting has taken place.
this
.public BillingDocument.BillingDocumentBuilder accountingTransferStatus(@Nullable String accountingTransferStatus)
Original property name from the Odata EDM: AccountingTransferStatus
The status message tells you whether the system has successfully posted the document to accounting or whether posting is blocked because a posting block is set for the billing type.
this
.public BillingDocument.BillingDocumentBuilder billingIssueType(@Nullable String billingIssueType)
Original property name from the Odata EDM: BillingIssueType
this
.public BillingDocument.BillingDocumentBuilder invoiceListStatus(@Nullable String invoiceListStatus)
Original property name from the Odata EDM: InvoiceListStatus
this
.public BillingDocument.BillingDocumentBuilder ovrlItmGeneralIncompletionSts(@Nullable String ovrlItmGeneralIncompletionSts)
Original property name from the Odata EDM: OvrlItmGeneralIncompletionSts
The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later.
includes business, shipping, and billing data.this
.public BillingDocument.BillingDocumentBuilder overallPricingIncompletionSts(@Nullable String overallPricingIncompletionSts)
Original property name from the Odata EDM: OverallPricingIncompletionSts
this
.public BillingDocument.BillingDocumentBuilder invoiceClearingStatus(@Nullable String invoiceClearingStatus)
Original property name from the Odata EDM: InvoiceClearingStatus
this
.public BillingDocument.BillingDocumentBuilder billingDocumentListType(@Nullable String billingDocumentListType)
Original property name from the Odata EDM: BillingDocumentListType
system.this
.public BillingDocument.BillingDocumentBuilder billingDocumentListDate(@Nullable LocalDateTime billingDocumentListDate)
Original property name from the Odata EDM: BillingDocumentListDate
The system automatically proposes the next valid date defined in the customer's factory calendar. You can change the date manually in the header of the invoice list.
this
.public BillingDocument build()
Copyright © 2020 SAP SE. All rights reserved.