public class BillingDocument extends VdmEntity<BillingDocument>
| Modifier and Type | Class and Description |
|---|---|
static class |
BillingDocument.BillingDocumentBuilder |
| Modifier and Type | Field and Description |
|---|---|
static BillingDocumentField<String> |
ACCOUNTING_DOCUMENT
Use with available fluent helpers to apply the AccountingDocument field to query operations.
|
static BillingDocumentField<String> |
ACCOUNTING_POSTING_STATUS
Use with available fluent helpers to apply the AccountingPostingStatus field to query operations.
|
static BillingDocumentField<String> |
ACCOUNTING_TRANSFER_STATUS
Use with available fluent helpers to apply the AccountingTransferStatus field to query operations.
|
static BillingDocumentField<String> |
ADDITIONAL_VALUE_DAYS
Use with available fluent helpers to apply the AdditionalValueDays field to query operations.
|
static EntityFieldAll<BillingDocument> |
ALL_FIELDS
Selector for all available fields of BillingDocument.
|
static BillingDocumentField<String> |
ASSIGNMENT_REFERENCE
Use with available fluent helpers to apply the AssignmentReference field to query operations.
|
static BillingDocumentField<String> |
BILLING_DOC_COMBINATION_CRITERIA
Use with available fluent helpers to apply the BillingDocCombinationCriteria field to query operations.
|
static BillingDocumentField<String> |
BILLING_DOCUMENT
Use with available fluent helpers to apply the BillingDocument field to query operations.
|
static BillingDocumentField<String> |
BILLING_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the BillingDocumentCategory field to query operations.
|
static BillingDocumentField<Calendar> |
BILLING_DOCUMENT_DATE
Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
|
static BillingDocumentField<Boolean> |
BILLING_DOCUMENT_IS_CANCELLED
Use with available fluent helpers to apply the BillingDocumentIsCancelled field to query operations.
|
static BillingDocumentField<Calendar> |
BILLING_DOCUMENT_LIST_DATE
Use with available fluent helpers to apply the BillingDocumentListDate field to query operations.
|
static BillingDocumentField<String> |
BILLING_DOCUMENT_LIST_TYPE
Use with available fluent helpers to apply the BillingDocumentListType field to query operations.
|
static BillingDocumentField<String> |
BILLING_DOCUMENT_TYPE
Use with available fluent helpers to apply the BillingDocumentType field to query operations.
|
static BillingDocumentField<String> |
BILLING_ISSUE_TYPE
Use with available fluent helpers to apply the BillingIssueType field to query operations.
|
static BillingDocumentField<String> |
CANCELLED_BILLING_DOCUMENT
Use with available fluent helpers to apply the CancelledBillingDocument field to query operations.
|
static BillingDocumentField<String> |
CITY_CODE
Use with available fluent helpers to apply the CityCode field to query operations.
|
static BillingDocumentField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static BillingDocumentField<String> |
CONTRACT_ACCOUNT
Use with available fluent helpers to apply the ContractAccount field to query operations.
|
static BillingDocumentField<String> |
COUNTRY
Use with available fluent helpers to apply the Country field to query operations.
|
static BillingDocumentField<String> |
COUNTY
Use with available fluent helpers to apply the County field to query operations.
|
static BillingDocumentField<Calendar> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static BillingDocumentField<Calendar> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static BillingDocumentField<String> |
CREDIT_CONTROL_AREA
Use with available fluent helpers to apply the CreditControlArea field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
Use with available fluent helpers to apply the CustomerAccountAssignmentGroup field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_GROUP
Use with available fluent helpers to apply the CustomerGroup field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_PRICE_GROUP
Use with available fluent helpers to apply the CustomerPriceGroup field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_REBATE_AGREEMENT
Use with available fluent helpers to apply the CustomerRebateAgreement field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION1
Use with available fluent helpers to apply the CustomerTaxClassification1 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION2
Use with available fluent helpers to apply the CustomerTaxClassification2 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION3
Use with available fluent helpers to apply the CustomerTaxClassification3 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION4
Use with available fluent helpers to apply the CustomerTaxClassification4 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION5
Use with available fluent helpers to apply the CustomerTaxClassification5 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION6
Use with available fluent helpers to apply the CustomerTaxClassification6 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION7
Use with available fluent helpers to apply the CustomerTaxClassification7 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION8
Use with available fluent helpers to apply the CustomerTaxClassification8 field to query operations.
|
static BillingDocumentField<String> |
CUSTOMER_TAX_CLASSIFICATION9
Use with available fluent helpers to apply the CustomerTaxClassification9 field to query operations.
|
static BillingDocumentField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static BillingDocumentField<String> |
DIVISION
Use with available fluent helpers to apply the Division field to query operations.
|
static BillingDocumentField<String> |
DOCUMENT_REFERENCE_ID
Use with available fluent helpers to apply the DocumentReferenceID field to query operations.
|
static BillingDocumentField<String> |
DUNNING_AREA
Use with available fluent helpers to apply the DunningArea field to query operations.
|
static BillingDocumentField<String> |
DUNNING_BLOCKING_REASON
Use with available fluent helpers to apply the DunningBlockingReason field to query operations.
|
static BillingDocumentField<String> |
DUNNING_KEY
Use with available fluent helpers to apply the DunningKey field to query operations.
|
static BillingDocumentField<String> |
FISCAL_YEAR
Use with available fluent helpers to apply the FiscalYear field to query operations.
|
static BillingDocumentField<Calendar> |
FIXED_VALUE_DATE
Use with available fluent helpers to apply the FixedValueDate field to query operations.
|
static BillingDocumentField<String> |
FOREIGN_TRADE
Use with available fluent helpers to apply the ForeignTrade field to query operations.
|
static BillingDocumentField<String> |
HIERARCHY_TYPE_PRICING
Use with available fluent helpers to apply the HierarchyTypePricing field to query operations.
|
static BillingDocumentField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static BillingDocumentField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static BillingDocumentField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static BillingDocumentField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static BillingDocumentField<String> |
INCOTERMS_VERSION
Use with available fluent helpers to apply the IncotermsVersion field to query operations.
|
static BillingDocumentField<String> |
INTERNAL_FINANCIAL_DOCUMENT
Use with available fluent helpers to apply the InternalFinancialDocument field to query operations.
|
static BillingDocumentField<String> |
INVOICE_LIST_STATUS
Use with available fluent helpers to apply the InvoiceListStatus field to query operations.
|
static BillingDocumentField<Boolean> |
IS_EU_TRIANGULAR_DEAL
Use with available fluent helpers to apply the IsEUTriangularDeal field to query operations.
|
static BillingDocumentField<String> |
IS_EXPORT_DELIVERY
Use with available fluent helpers to apply the IsExportDelivery field to query operations.
|
static BillingDocumentField<Boolean> |
IS_INTRASTAT_REPORTING_EXCLUDED
Use with available fluent helpers to apply the IsIntrastatReportingExcluded field to query operations.
|
static BillingDocumentField<Boolean> |
IS_INTRASTAT_REPORTING_RELEVANT
Use with available fluent helpers to apply the IsIntrastatReportingRelevant field to query operations.
|
static BillingDocumentField<Boolean> |
IS_RELEVANT_FOR_ACCRUAL
Use with available fluent helpers to apply the IsRelevantForAccrual field to query operations.
|
static BillingDocumentField<Calendar> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static BillingDocumentField<Calendar> |
LAST_CHANGE_DATE_TIME
Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
|
static BillingDocumentField<String> |
LOGICAL_SYSTEM
Use with available fluent helpers to apply the LogicalSystem field to query operations.
|
static BillingDocumentField<Boolean> |
MANUAL_INVOICE_MAINT_IS_RELEVANT
Use with available fluent helpers to apply the ManualInvoiceMaintIsRelevant field to query operations.
|
static BillingDocumentField<String> |
OVERALL_BILLING_STATUS
Use with available fluent helpers to apply the OverallBillingStatus field to query operations.
|
static BillingDocumentField<String> |
OVERALL_PRICING_INCOMPLETION_STS
Use with available fluent helpers to apply the OverallPricingIncompletionSts field to query operations.
|
static BillingDocumentField<String> |
OVERALL_SD_PROCESS_STATUS
Use with available fluent helpers to apply the OverallSDProcessStatus field to query operations.
|
static BillingDocumentField<String> |
OVRL_ITM_GENERAL_INCOMPLETION_STS
Use with available fluent helpers to apply the OvrlItmGeneralIncompletionSts field to query operations.
|
static BillingDocumentField<String> |
PARTNER_COMPANY
Use with available fluent helpers to apply the PartnerCompany field to query operations.
|
static BillingDocumentField<String> |
PAYER_PARTY
Use with available fluent helpers to apply the PayerParty field to query operations.
|
static BillingDocumentField<String> |
PAYMENT_METHOD
Use with available fluent helpers to apply the PaymentMethod field to query operations.
|
static BillingDocumentField<String> |
PAYMENT_REFERENCE
Use with available fluent helpers to apply the PaymentReference field to query operations.
|
static BillingDocumentField<String> |
PRICE_LIST_TYPE
Use with available fluent helpers to apply the PriceListType field to query operations.
|
static BillingDocumentField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static BillingDocumentField<String> |
REGION
Use with available fluent helpers to apply the Region field to query operations.
|
static BillingDocumentField<String> |
SALES_DISTRICT
Use with available fluent helpers to apply the SalesDistrict field to query operations.
|
static BillingDocumentField<String> |
SALES_DOCUMENT_CONDITION
Use with available fluent helpers to apply the SalesDocumentCondition field to query operations.
|
static BillingDocumentField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static BillingDocumentField<String> |
SD_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the SDDocumentCategory field to query operations.
|
static BillingDocumentField<String> |
SD_PRICING_PROCEDURE
Use with available fluent helpers to apply the SDPricingProcedure field to query operations.
|
static BillingDocumentField<String> |
SEPA_MANDATE
Use with available fluent helpers to apply the SEPAMandate field to query operations.
|
static BillingDocumentField<String> |
SHIPPING_CONDITION
Use with available fluent helpers to apply the ShippingCondition field to query operations.
|
static BillingDocumentField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static BillingDocumentField<String> |
STATISTICS_CURRENCY
Use with available fluent helpers to apply the StatisticsCurrency field to query operations.
|
static BillingDocumentField<BigDecimal> |
TAX_AMOUNT
Use with available fluent helpers to apply the TaxAmount field to query operations.
|
static BillingDocumentField<String> |
TAX_DEPARTURE_COUNTRY
Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
|
static BillingDocumentLink<BillingDocumentItem> |
TO_ITEM
Use with available fluent helpers to apply the to_Item navigation property to query operations.
|
static BillingDocumentLink<BillingDocumentPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static BillingDocumentLink<BillingDocumentPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static BillingDocumentField<BigDecimal> |
TOTAL_GROSS_AMOUNT
Use with available fluent helpers to apply the TotalGrossAmount field to query operations.
|
static BillingDocumentField<BigDecimal> |
TOTAL_NET_AMOUNT
Use with available fluent helpers to apply the TotalNetAmount field to query operations.
|
static BillingDocumentField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
static BillingDocumentField<String> |
VAT_REGISTRATION
Use with available fluent helpers to apply the VATRegistration field to query operations.
|
static BillingDocumentField<String> |
VAT_REGISTRATION_COUNTRY
Use with available fluent helpers to apply the VATRegistrationCountry field to query operations.
|
static BillingDocumentField<String> |
VAT_REGISTRATION_ORIGIN
Use with available fluent helpers to apply the VATRegistrationOrigin field to query operations.
|
| Constructor and Description |
|---|
BillingDocument() |
BillingDocument(String billingDocument,
String sDDocumentCategory,
String billingDocumentCategory,
String billingDocumentType,
Calendar creationDate,
Calendar creationTime,
Calendar lastChangeDate,
Calendar lastChangeDateTime,
String logicalSystem,
String salesOrganization,
String distributionChannel,
String division,
Calendar billingDocumentDate,
Boolean billingDocumentIsCancelled,
String cancelledBillingDocument,
String foreignTrade,
String isExportDelivery,
String billingDocCombinationCriteria,
Boolean manualInvoiceMaintIsRelevant,
Boolean isIntrastatReportingRelevant,
Boolean isIntrastatReportingExcluded,
BigDecimal totalNetAmount,
String transactionCurrency,
String statisticsCurrency,
BigDecimal taxAmount,
BigDecimal totalGrossAmount,
String customerPriceGroup,
String priceListType,
String taxDepartureCountry,
String vATRegistration,
String vATRegistrationOrigin,
String vATRegistrationCountry,
String hierarchyTypePricing,
String customerTaxClassification1,
String customerTaxClassification2,
String customerTaxClassification3,
String customerTaxClassification4,
String customerTaxClassification5,
String customerTaxClassification6,
String customerTaxClassification7,
String customerTaxClassification8,
String customerTaxClassification9,
Boolean isEUTriangularDeal,
String sDPricingProcedure,
String shippingCondition,
String incotermsVersion,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String payerParty,
String contractAccount,
String customerPaymentTerms,
String paymentMethod,
String paymentReference,
Calendar fixedValueDate,
String additionalValueDays,
String sEPAMandate,
String companyCode,
String fiscalYear,
String accountingDocument,
String customerAccountAssignmentGroup,
String documentReferenceID,
String assignmentReference,
String dunningArea,
String dunningBlockingReason,
String dunningKey,
String internalFinancialDocument,
Boolean isRelevantForAccrual,
String soldToParty,
String partnerCompany,
String purchaseOrderByCustomer,
String customerGroup,
String country,
String cityCode,
String salesDistrict,
String region,
String county,
String creditControlArea,
String customerRebateAgreement,
String salesDocumentCondition,
String overallSDProcessStatus,
String overallBillingStatus,
String accountingPostingStatus,
String accountingTransferStatus,
String billingIssueType,
String invoiceListStatus,
String ovrlItmGeneralIncompletionSts,
String overallPricingIncompletionSts,
String billingDocumentListType,
Calendar billingDocumentListDate,
ErpConfigContext erpConfigContext,
List<BillingDocumentItem> toItem,
List<BillingDocumentPartner> toPartner,
List<BillingDocumentPrcgElmnt> toPricingElement) |
| Modifier and Type | Method and Description |
|---|---|
void |
addItem(BillingDocumentItem... entity)
Adds elements to the list of associated BillingDocumentItem entities.
|
void |
addPartner(BillingDocumentPartner... entity)
Adds elements to the list of associated BillingDocumentPartner entities.
|
void |
addPricingElement(BillingDocumentPrcgElmnt... entity)
Adds elements to the list of associated BillingDocumentPrcgElmnt entities.
|
static BillingDocument.BillingDocumentBuilder |
builder() |
boolean |
equals(Object o) |
List<BillingDocumentItem> |
fetchItem()
Fetches the BillingDocumentItem entities (one to many) associated with this entity.
|
List<BillingDocumentPartner> |
fetchPartner()
Fetches the BillingDocumentPartner entities (one to many) associated with this entity.
|
List<BillingDocumentPrcgElmnt> |
fetchPricingElement()
Fetches the BillingDocumentPrcgElmnt entities (one to many) associated with this entity.
|
static <T> BillingDocumentField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getAccountingDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getAccountingPostingStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getAccountingTransferStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getAdditionalValueDays()
Constraints: Not nullable, Maximum length: 2
|
String |
getAssignmentReference()
Constraints: Not nullable, Maximum length: 18
|
String |
getBillingDocCombinationCriteria()
Constraints: Not nullable, Maximum length: 40
|
String |
getBillingDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getBillingDocumentCategory()
Constraints: Not nullable, Maximum length: 1
|
Calendar |
getBillingDocumentDate()
Constraints: Not nullable, Precision: 0
|
Boolean |
getBillingDocumentIsCancelled()
Constraints: none
|
Calendar |
getBillingDocumentListDate()
Constraints: Not nullable, Precision: 0
|
String |
getBillingDocumentListType()
Constraints: Not nullable, Maximum length: 4
|
String |
getBillingDocumentType()
Constraints: Not nullable, Maximum length: 4
|
String |
getBillingIssueType()
Constraints: Not nullable, Maximum length: 1
|
String |
getCancelledBillingDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getCityCode()
Constraints: Not nullable, Maximum length: 4
|
String |
getCompanyCode()
Constraints: Not nullable, Maximum length: 4
|
String |
getContractAccount()
Constraints: Not nullable, Maximum length: 12
|
String |
getCountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getCounty()
Constraints: Not nullable, Maximum length: 3
|
Calendar |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
Calendar |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCreditControlArea()
Constraints: Not nullable, Maximum length: 4
|
String |
getCustomerAccountAssignmentGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getCustomerGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
String |
getCustomerPriceGroup()
Constraints: Not nullable, Maximum length: 2
|
String |
getCustomerRebateAgreement()
Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerTaxClassification1()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification2()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification3()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification4()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification5()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification6()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification7()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification8()
Constraints: Not nullable, Maximum length: 1
|
String |
getCustomerTaxClassification9()
Constraints: Not nullable, Maximum length: 1
|
String |
getDistributionChannel()
Constraints: Not nullable, Maximum length: 2
|
String |
getDivision()
Constraints: Not nullable, Maximum length: 2
|
String |
getDocumentReferenceID()
Constraints: Not nullable, Maximum length: 16
|
String |
getDunningArea()
Constraints: Not nullable, Maximum length: 2
|
String |
getDunningBlockingReason()
Constraints: Not nullable, Maximum length: 1
|
String |
getDunningKey()
Constraints: Not nullable, Maximum length: 1
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getFiscalYear()
Constraints: Not nullable, Maximum length: 4
|
Calendar |
getFixedValueDate()
Constraints: Not nullable, Precision: 0
|
String |
getForeignTrade()
Constraints: Not nullable, Maximum length: 10
|
String |
getHierarchyTypePricing()
Constraints: Not nullable, Maximum length: 1
|
String |
getIncotermsClassification()
Constraints: Not nullable, Maximum length: 3
|
String |
getIncotermsLocation1()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsLocation2()
Constraints: Not nullable, Maximum length: 70
|
String |
getIncotermsTransferLocation()
Constraints: Not nullable, Maximum length: 28
|
String |
getIncotermsVersion()
Constraints: Not nullable, Maximum length: 4
|
String |
getInternalFinancialDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getInvoiceListStatus()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getIsEUTriangularDeal()
Constraints: none
|
String |
getIsExportDelivery()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getIsIntrastatReportingExcluded()
Constraints: none
|
Boolean |
getIsIntrastatReportingRelevant()
Constraints: none
|
Boolean |
getIsRelevantForAccrual()
Constraints: none
|
List<BillingDocumentItem> |
getItemOrFetch()
Retrieval of associated BillingDocumentItem entities (one to many).
|
com.google.common.base.Optional<List<BillingDocumentItem>> |
getItemOrNull()
Retrieval of associated BillingDocumentItem entities (one to many).
|
Calendar |
getLastChangeDate()
Constraints: Not nullable, Precision: 0
|
Calendar |
getLastChangeDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getLogicalSystem()
Constraints: Not nullable, Maximum length: 10
|
Boolean |
getManualInvoiceMaintIsRelevant()
Constraints: none
|
String |
getOverallBillingStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallPricingIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallSDProcessStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOvrlItmGeneralIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
String |
getPartnerCompany()
Constraints: Not nullable, Maximum length: 6
|
List<BillingDocumentPartner> |
getPartnerOrFetch()
Retrieval of associated BillingDocumentPartner entities (one to many).
|
com.google.common.base.Optional<List<BillingDocumentPartner>> |
getPartnerOrNull()
Retrieval of associated BillingDocumentPartner entities (one to many).
|
String |
getPayerParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getPaymentMethod()
Constraints: Not nullable, Maximum length: 1
|
String |
getPaymentReference()
Constraints: Not nullable, Maximum length: 30
|
String |
getPriceListType()
Constraints: Not nullable, Maximum length: 2
|
List<BillingDocumentPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated BillingDocumentPrcgElmnt entities (one to many).
|
com.google.common.base.Optional<List<BillingDocumentPrcgElmnt>> |
getPricingElementOrNull()
Retrieval of associated BillingDocumentPrcgElmnt entities (one to many).
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getRegion()
Constraints: Not nullable, Maximum length: 3
|
String |
getSalesDistrict()
Constraints: Not nullable, Maximum length: 6
|
String |
getSalesDocumentCondition()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
String |
getSDDocumentCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getSDPricingProcedure()
Constraints: Not nullable, Maximum length: 6
|
String |
getSEPAMandate()
Constraints: Not nullable, Maximum length: 35
|
String |
getShippingCondition()
Constraints: Not nullable, Maximum length: 2
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getStatisticsCurrency()
Constraints: Not nullable, Maximum length: 5
|
BigDecimal |
getTaxAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
String |
getTaxDepartureCountry()
Constraints: Not nullable, Maximum length: 3
|
BigDecimal |
getTotalGrossAmount()
Constraints: Not nullable, Precision: 17, Scale: 3
|
BigDecimal |
getTotalNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<BillingDocument> |
getType() |
String |
getVATRegistration()
Constraints: Not nullable, Maximum length: 20
|
String |
getVATRegistrationCountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getVATRegistrationOrigin()
Constraints: Not nullable, Maximum length: 1
|
int |
hashCode() |
void |
setAccountingDocument(String accountingDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setAccountingPostingStatus(String accountingPostingStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setAccountingTransferStatus(String accountingTransferStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setAdditionalValueDays(String additionalValueDays)
Constraints: Not nullable, Maximum length: 2
|
void |
setAssignmentReference(String assignmentReference)
Constraints: Not nullable, Maximum length: 18
|
void |
setBillingDocCombinationCriteria(String billingDocCombinationCriteria)
Constraints: Not nullable, Maximum length: 40
|
void |
setBillingDocument(String billingDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setBillingDocumentCategory(String billingDocumentCategory)
Constraints: Not nullable, Maximum length: 1
|
void |
setBillingDocumentDate(Calendar billingDocumentDate)
Constraints: Not nullable, Precision: 0
|
void |
setBillingDocumentIsCancelled(Boolean billingDocumentIsCancelled)
Constraints: none
|
void |
setBillingDocumentListDate(Calendar billingDocumentListDate)
Constraints: Not nullable, Precision: 0
|
void |
setBillingDocumentListType(String billingDocumentListType)
Constraints: Not nullable, Maximum length: 4
|
void |
setBillingDocumentType(String billingDocumentType)
Constraints: Not nullable, Maximum length: 4
|
void |
setBillingIssueType(String billingIssueType)
Constraints: Not nullable, Maximum length: 1
|
void |
setCancelledBillingDocument(String cancelledBillingDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setCityCode(String cityCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setCompanyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setContractAccount(String contractAccount)
Constraints: Not nullable, Maximum length: 12
|
void |
setCountry(String country)
Constraints: Not nullable, Maximum length: 3
|
void |
setCounty(String county)
Constraints: Not nullable, Maximum length: 3
|
void |
setCreationDate(Calendar creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreationTime(Calendar creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCreditControlArea(String creditControlArea)
Constraints: Not nullable, Maximum length: 4
|
void |
setCustomerAccountAssignmentGroup(String customerAccountAssignmentGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setCustomerGroup(String customerGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setCustomerPriceGroup(String customerPriceGroup)
Constraints: Not nullable, Maximum length: 2
|
void |
setCustomerRebateAgreement(String customerRebateAgreement)
Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerTaxClassification1(String customerTaxClassification1)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification2(String customerTaxClassification2)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification3(String customerTaxClassification3)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification4(String customerTaxClassification4)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification5(String customerTaxClassification5)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification6(String customerTaxClassification6)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification7(String customerTaxClassification7)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification8(String customerTaxClassification8)
Constraints: Not nullable, Maximum length: 1
|
void |
setCustomerTaxClassification9(String customerTaxClassification9)
Constraints: Not nullable, Maximum length: 1
|
void |
setDistributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
void |
setDivision(String division)
Constraints: Not nullable, Maximum length: 2
|
void |
setDocumentReferenceID(String documentReferenceID)
Constraints: Not nullable, Maximum length: 16
|
void |
setDunningArea(String dunningArea)
Constraints: Not nullable, Maximum length: 2
|
void |
setDunningBlockingReason(String dunningBlockingReason)
Constraints: Not nullable, Maximum length: 1
|
void |
setDunningKey(String dunningKey)
Constraints: Not nullable, Maximum length: 1
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setFiscalYear(String fiscalYear)
Constraints: Not nullable, Maximum length: 4
|
void |
setFixedValueDate(Calendar fixedValueDate)
Constraints: Not nullable, Precision: 0
|
void |
setForeignTrade(String foreignTrade)
Constraints: Not nullable, Maximum length: 10
|
void |
setHierarchyTypePricing(String hierarchyTypePricing)
Constraints: Not nullable, Maximum length: 1
|
void |
setIncotermsClassification(String incotermsClassification)
Constraints: Not nullable, Maximum length: 3
|
void |
setIncotermsLocation1(String incotermsLocation1)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsLocation2(String incotermsLocation2)
Constraints: Not nullable, Maximum length: 70
|
void |
setIncotermsTransferLocation(String incotermsTransferLocation)
Constraints: Not nullable, Maximum length: 28
|
void |
setIncotermsVersion(String incotermsVersion)
Constraints: Not nullable, Maximum length: 4
|
void |
setInternalFinancialDocument(String internalFinancialDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setInvoiceListStatus(String invoiceListStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsEUTriangularDeal(Boolean isEUTriangularDeal)
Constraints: none
|
void |
setIsExportDelivery(String isExportDelivery)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsIntrastatReportingExcluded(Boolean isIntrastatReportingExcluded)
Constraints: none
|
void |
setIsIntrastatReportingRelevant(Boolean isIntrastatReportingRelevant)
Constraints: none
|
void |
setIsRelevantForAccrual(Boolean isRelevantForAccrual)
Constraints: none
|
void |
setItem(List<BillingDocumentItem> value)
Overwrites the list of associated BillingDocumentItem entities for the loaded navigation property to_Item.
|
void |
setLastChangeDate(Calendar lastChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setLastChangeDateTime(Calendar lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setLogicalSystem(String logicalSystem)
Constraints: Not nullable, Maximum length: 10
|
void |
setManualInvoiceMaintIsRelevant(Boolean manualInvoiceMaintIsRelevant)
Constraints: none
|
void |
setOverallBillingStatus(String overallBillingStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallPricingIncompletionSts(String overallPricingIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallSDProcessStatus(String overallSDProcessStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOvrlItmGeneralIncompletionSts(String ovrlItmGeneralIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setPartner(List<BillingDocumentPartner> value)
Overwrites the list of associated BillingDocumentPartner entities for the loaded navigation property to_Partner.
|
void |
setPartnerCompany(String partnerCompany)
Constraints: Not nullable, Maximum length: 6
|
void |
setPayerParty(String payerParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
void |
setPaymentReference(String paymentReference)
Constraints: Not nullable, Maximum length: 30
|
void |
setPriceListType(String priceListType)
Constraints: Not nullable, Maximum length: 2
|
void |
setPricingElement(List<BillingDocumentPrcgElmnt> value)
Overwrites the list of associated BillingDocumentPrcgElmnt entities for the loaded navigation property to_PricingElement.
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setRegion(String region)
Constraints: Not nullable, Maximum length: 3
|
void |
setSalesDistrict(String salesDistrict)
Constraints: Not nullable, Maximum length: 6
|
void |
setSalesDocumentCondition(String salesDocumentCondition)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
void |
setSDDocumentCategory(String sDDocumentCategory)
Constraints: Not nullable, Maximum length: 4
|
void |
setSDPricingProcedure(String sDPricingProcedure)
Constraints: Not nullable, Maximum length: 6
|
void |
setSEPAMandate(String sEPAMandate)
Constraints: Not nullable, Maximum length: 35
|
void |
setShippingCondition(String shippingCondition)
Constraints: Not nullable, Maximum length: 2
|
void |
setSoldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setStatisticsCurrency(String statisticsCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setTaxAmount(BigDecimal taxAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setTaxDepartureCountry(String taxDepartureCountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setTotalGrossAmount(BigDecimal totalGrossAmount)
Constraints: Not nullable, Precision: 17, Scale: 3
|
void |
setTotalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setVATRegistration(String vATRegistration)
Constraints: Not nullable, Maximum length: 20
|
void |
setVATRegistrationCountry(String vATRegistrationCountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setVATRegistrationOrigin(String vATRegistrationOrigin)
Constraints: Not nullable, Maximum length: 1
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final EntityFieldAll<BillingDocument> ALL_FIELDS
public static final BillingDocumentField<String> BILLING_DOCUMENT
public static final BillingDocumentField<String> SD_DOCUMENT_CATEGORY
public static final BillingDocumentField<String> BILLING_DOCUMENT_CATEGORY
public static final BillingDocumentField<String> BILLING_DOCUMENT_TYPE
public static final BillingDocumentField<Calendar> CREATION_DATE
public static final BillingDocumentField<Calendar> CREATION_TIME
public static final BillingDocumentField<Calendar> LAST_CHANGE_DATE
public static final BillingDocumentField<Calendar> LAST_CHANGE_DATE_TIME
public static final BillingDocumentField<String> LOGICAL_SYSTEM
public static final BillingDocumentField<String> SALES_ORGANIZATION
public static final BillingDocumentField<String> DISTRIBUTION_CHANNEL
public static final BillingDocumentField<String> DIVISION
public static final BillingDocumentField<Calendar> BILLING_DOCUMENT_DATE
public static final BillingDocumentField<Boolean> BILLING_DOCUMENT_IS_CANCELLED
public static final BillingDocumentField<String> CANCELLED_BILLING_DOCUMENT
public static final BillingDocumentField<String> FOREIGN_TRADE
public static final BillingDocumentField<String> IS_EXPORT_DELIVERY
public static final BillingDocumentField<String> BILLING_DOC_COMBINATION_CRITERIA
public static final BillingDocumentField<Boolean> MANUAL_INVOICE_MAINT_IS_RELEVANT
public static final BillingDocumentField<Boolean> IS_INTRASTAT_REPORTING_RELEVANT
public static final BillingDocumentField<Boolean> IS_INTRASTAT_REPORTING_EXCLUDED
public static final BillingDocumentField<BigDecimal> TOTAL_NET_AMOUNT
public static final BillingDocumentField<String> TRANSACTION_CURRENCY
public static final BillingDocumentField<String> STATISTICS_CURRENCY
public static final BillingDocumentField<BigDecimal> TAX_AMOUNT
public static final BillingDocumentField<BigDecimal> TOTAL_GROSS_AMOUNT
public static final BillingDocumentField<String> CUSTOMER_PRICE_GROUP
public static final BillingDocumentField<String> PRICE_LIST_TYPE
public static final BillingDocumentField<String> TAX_DEPARTURE_COUNTRY
public static final BillingDocumentField<String> VAT_REGISTRATION
public static final BillingDocumentField<String> VAT_REGISTRATION_ORIGIN
public static final BillingDocumentField<String> VAT_REGISTRATION_COUNTRY
public static final BillingDocumentField<String> HIERARCHY_TYPE_PRICING
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION1
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION2
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION3
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION4
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION5
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION6
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION7
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION8
public static final BillingDocumentField<String> CUSTOMER_TAX_CLASSIFICATION9
public static final BillingDocumentField<Boolean> IS_EU_TRIANGULAR_DEAL
public static final BillingDocumentField<String> SD_PRICING_PROCEDURE
public static final BillingDocumentField<String> SHIPPING_CONDITION
public static final BillingDocumentField<String> INCOTERMS_VERSION
public static final BillingDocumentField<String> INCOTERMS_CLASSIFICATION
public static final BillingDocumentField<String> INCOTERMS_TRANSFER_LOCATION
public static final BillingDocumentField<String> INCOTERMS_LOCATION1
public static final BillingDocumentField<String> INCOTERMS_LOCATION2
public static final BillingDocumentField<String> PAYER_PARTY
public static final BillingDocumentField<String> CONTRACT_ACCOUNT
public static final BillingDocumentField<String> CUSTOMER_PAYMENT_TERMS
public static final BillingDocumentField<String> PAYMENT_METHOD
public static final BillingDocumentField<String> PAYMENT_REFERENCE
public static final BillingDocumentField<Calendar> FIXED_VALUE_DATE
public static final BillingDocumentField<String> ADDITIONAL_VALUE_DAYS
public static final BillingDocumentField<String> SEPA_MANDATE
public static final BillingDocumentField<String> COMPANY_CODE
public static final BillingDocumentField<String> FISCAL_YEAR
public static final BillingDocumentField<String> ACCOUNTING_DOCUMENT
public static final BillingDocumentField<String> CUSTOMER_ACCOUNT_ASSIGNMENT_GROUP
public static final BillingDocumentField<String> DOCUMENT_REFERENCE_ID
public static final BillingDocumentField<String> ASSIGNMENT_REFERENCE
public static final BillingDocumentField<String> DUNNING_AREA
public static final BillingDocumentField<String> DUNNING_BLOCKING_REASON
public static final BillingDocumentField<String> DUNNING_KEY
public static final BillingDocumentField<String> INTERNAL_FINANCIAL_DOCUMENT
public static final BillingDocumentField<Boolean> IS_RELEVANT_FOR_ACCRUAL
public static final BillingDocumentField<String> SOLD_TO_PARTY
public static final BillingDocumentField<String> PARTNER_COMPANY
public static final BillingDocumentField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final BillingDocumentField<String> CUSTOMER_GROUP
public static final BillingDocumentField<String> COUNTRY
public static final BillingDocumentField<String> CITY_CODE
public static final BillingDocumentField<String> SALES_DISTRICT
public static final BillingDocumentField<String> REGION
public static final BillingDocumentField<String> COUNTY
public static final BillingDocumentField<String> CREDIT_CONTROL_AREA
public static final BillingDocumentField<String> CUSTOMER_REBATE_AGREEMENT
public static final BillingDocumentField<String> SALES_DOCUMENT_CONDITION
public static final BillingDocumentField<String> OVERALL_SD_PROCESS_STATUS
public static final BillingDocumentField<String> OVERALL_BILLING_STATUS
public static final BillingDocumentField<String> ACCOUNTING_POSTING_STATUS
public static final BillingDocumentField<String> ACCOUNTING_TRANSFER_STATUS
public static final BillingDocumentField<String> BILLING_ISSUE_TYPE
public static final BillingDocumentField<String> INVOICE_LIST_STATUS
public static final BillingDocumentField<String> OVRL_ITM_GENERAL_INCOMPLETION_STS
public static final BillingDocumentField<String> OVERALL_PRICING_INCOMPLETION_STS
public static final BillingDocumentField<String> BILLING_DOCUMENT_LIST_TYPE
public static final BillingDocumentField<Calendar> BILLING_DOCUMENT_LIST_DATE
public static final BillingDocumentLink<BillingDocumentItem> TO_ITEM
public static final BillingDocumentLink<BillingDocumentPartner> TO_PARTNER
public static final BillingDocumentLink<BillingDocumentPrcgElmnt> TO_PRICING_ELEMENT
@Generated(value="lombok") public BillingDocument()
@ConstructorProperties(value={"billingDocument","sDDocumentCategory","billingDocumentCategory","billingDocumentType","creationDate","creationTime","lastChangeDate","lastChangeDateTime","logicalSystem","salesOrganization","distributionChannel","division","billingDocumentDate","billingDocumentIsCancelled","cancelledBillingDocument","foreignTrade","isExportDelivery","billingDocCombinationCriteria","manualInvoiceMaintIsRelevant","isIntrastatReportingRelevant","isIntrastatReportingExcluded","totalNetAmount","transactionCurrency","statisticsCurrency","taxAmount","totalGrossAmount","customerPriceGroup","priceListType","taxDepartureCountry","vATRegistration","vATRegistrationOrigin","vATRegistrationCountry","hierarchyTypePricing","customerTaxClassification1","customerTaxClassification2","customerTaxClassification3","customerTaxClassification4","customerTaxClassification5","customerTaxClassification6","customerTaxClassification7","customerTaxClassification8","customerTaxClassification9","isEUTriangularDeal","sDPricingProcedure","shippingCondition","incotermsVersion","incotermsClassification","incotermsTransferLocation","incotermsLocation1","incotermsLocation2","payerParty","contractAccount","customerPaymentTerms","paymentMethod","paymentReference","fixedValueDate","additionalValueDays","sEPAMandate","companyCode","fiscalYear","accountingDocument","customerAccountAssignmentGroup","documentReferenceID","assignmentReference","dunningArea","dunningBlockingReason","dunningKey","internalFinancialDocument","isRelevantForAccrual","soldToParty","partnerCompany","purchaseOrderByCustomer","customerGroup","country","cityCode","salesDistrict","region","county","creditControlArea","customerRebateAgreement","salesDocumentCondition","overallSDProcessStatus","overallBillingStatus","accountingPostingStatus","accountingTransferStatus","billingIssueType","invoiceListStatus","ovrlItmGeneralIncompletionSts","overallPricingIncompletionSts","billingDocumentListType","billingDocumentListDate","erpConfigContext","toItem","toPartner","toPricingElement"}) @Generated(value="lombok") public BillingDocument(@Nullable String billingDocument, @Nullable String sDDocumentCategory, @Nullable String billingDocumentCategory, @Nullable String billingDocumentType, @Nullable Calendar creationDate, @Nullable Calendar creationTime, @Nullable Calendar lastChangeDate, @Nullable Calendar lastChangeDateTime, @Nullable String logicalSystem, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String division, @Nullable Calendar billingDocumentDate, @Nullable Boolean billingDocumentIsCancelled, @Nullable String cancelledBillingDocument, @Nullable String foreignTrade, @Nullable String isExportDelivery, @Nullable String billingDocCombinationCriteria, @Nullable Boolean manualInvoiceMaintIsRelevant, @Nullable Boolean isIntrastatReportingRelevant, @Nullable Boolean isIntrastatReportingExcluded, @Nullable BigDecimal totalNetAmount, @Nullable String transactionCurrency, @Nullable String statisticsCurrency, @Nullable BigDecimal taxAmount, @Nullable BigDecimal totalGrossAmount, @Nullable String customerPriceGroup, @Nullable String priceListType, @Nullable String taxDepartureCountry, @Nullable String vATRegistration, @Nullable String vATRegistrationOrigin, @Nullable String vATRegistrationCountry, @Nullable String hierarchyTypePricing, @Nullable String customerTaxClassification1, @Nullable String customerTaxClassification2, @Nullable String customerTaxClassification3, @Nullable String customerTaxClassification4, @Nullable String customerTaxClassification5, @Nullable String customerTaxClassification6, @Nullable String customerTaxClassification7, @Nullable String customerTaxClassification8, @Nullable String customerTaxClassification9, @Nullable Boolean isEUTriangularDeal, @Nullable String sDPricingProcedure, @Nullable String shippingCondition, @Nullable String incotermsVersion, @Nullable String incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable String incotermsLocation1, @Nullable String incotermsLocation2, @Nullable String payerParty, @Nullable String contractAccount, @Nullable String customerPaymentTerms, @Nullable String paymentMethod, @Nullable String paymentReference, @Nullable Calendar fixedValueDate, @Nullable String additionalValueDays, @Nullable String sEPAMandate, @Nullable String companyCode, @Nullable String fiscalYear, @Nullable String accountingDocument, @Nullable String customerAccountAssignmentGroup, @Nullable String documentReferenceID, @Nullable String assignmentReference, @Nullable String dunningArea, @Nullable String dunningBlockingReason, @Nullable String dunningKey, @Nullable String internalFinancialDocument, @Nullable Boolean isRelevantForAccrual, @Nullable String soldToParty, @Nullable String partnerCompany, @Nullable String purchaseOrderByCustomer, @Nullable String customerGroup, @Nullable String country, @Nullable String cityCode, @Nullable String salesDistrict, @Nullable String region, @Nullable String county, @Nullable String creditControlArea, @Nullable String customerRebateAgreement, @Nullable String salesDocumentCondition, @Nullable String overallSDProcessStatus, @Nullable String overallBillingStatus, @Nullable String accountingPostingStatus, @Nullable String accountingTransferStatus, @Nullable String billingIssueType, @Nullable String invoiceListStatus, @Nullable String ovrlItmGeneralIncompletionSts, @Nullable String overallPricingIncompletionSts, @Nullable String billingDocumentListType, @Nullable Calendar billingDocumentListDate, @Nullable ErpConfigContext erpConfigContext, List<BillingDocumentItem> toItem, List<BillingDocumentPartner> toPartner, List<BillingDocumentPrcgElmnt> toPricingElement)
public Class<BillingDocument> getType()
getType in class VdmObject<BillingDocument>public static <T> BillingDocumentField<T> field(String fieldName, Class<T> fieldType)
fieldName - The name of the extension field as returned by the OData service.fieldType - The Java type to use for the extension field when performing value comparisons.public List<BillingDocumentItem> fetchItem() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public List<BillingDocumentItem> getItemOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Item of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public com.google.common.base.Optional<List<BillingDocumentItem>> getItemOrNull()
If the navigation property to_Item for an entity BillingDocument has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setItem(@NonNull
List<BillingDocumentItem> value)
If the navigation property to_Item of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of BillingDocumentItem entities.public void addItem(BillingDocumentItem... entity)
If the navigation property to_Item of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of BillingDocumentItem entities.public List<BillingDocumentPartner> fetchPartner() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public List<BillingDocumentPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public com.google.common.base.Optional<List<BillingDocumentPartner>> getPartnerOrNull()
If the navigation property to_Partner for an entity BillingDocument has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setPartner(@NonNull
List<BillingDocumentPartner> value)
If the navigation property to_Partner of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of BillingDocumentPartner entities.public void addPartner(BillingDocumentPartner... entity)
If the navigation property to_Partner of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of BillingDocumentPartner entities.public List<BillingDocumentPrcgElmnt> fetchPricingElement() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public List<BillingDocumentPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public com.google.common.base.Optional<List<BillingDocumentPrcgElmnt>> getPricingElementOrNull()
If the navigation property to_PricingElement for an entity BillingDocument has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setPricingElement(@NonNull
List<BillingDocumentPrcgElmnt> value)
If the navigation property to_PricingElement of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of BillingDocumentPrcgElmnt entities.public void addPricingElement(BillingDocumentPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried BillingDocument is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of BillingDocumentPrcgElmnt entities.@Generated(value="lombok") public static BillingDocument.BillingDocumentBuilder builder()
@Nullable @Generated(value="lombok") public String getBillingDocument()
@Nullable @Generated(value="lombok") public String getSDDocumentCategory()
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).
@Nullable @Generated(value="lombok") public String getBillingDocumentCategory()
@Nullable @Generated(value="lombok") public String getBillingDocumentType()
When you process billing documents collectively, you can use the billing type as one of the selection criteria.
@Nullable @Generated(value="lombok") public Calendar getCreationDate()
@Nullable @Generated(value="lombok") public Calendar getCreationTime()
@Nullable @Generated(value="lombok") public Calendar getLastChangeDate()
@Nullable @Generated(value="lombok") public Calendar getLastChangeDateTime()
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 STAMP A UTC time stamp in short form is also available.
@Nullable @Generated(value="lombok") public String getLogicalSystem()
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose. In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail). The logical system is relevant in the following SAP areas: ALE general: two or more logical systems communicate with one another. ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example. Workflow objects: the logical system in which the object is located is always included in an object's key. When maintaining the logical system, note the following: The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
@Nullable @Generated(value="lombok") public String getSalesOrganization()
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.
@Nullable @Generated(value="lombok") public String getDistributionChannel()
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.
@Nullable @Generated(value="lombok") public String getDivision()
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
@Nullable @Generated(value="lombok") public Calendar getBillingDocumentDate()
You can use the billing date as one of the selection criteria when you process billing documents collectively. If invoice dates are defined for the customer, 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. If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document. If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone. 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.
@Nullable @Generated(value="lombok") public Boolean getBillingDocumentIsCancelled()
@Nullable @Generated(value="lombok") public String getCancelledBillingDocument()
@Nullable @Generated(value="lombok") public String getForeignTrade()
@Nullable @Generated(value="lombok") public String getIsExportDelivery()
@Nullable @Generated(value="lombok") public String getBillingDocCombinationCriteria()
@Nullable @Generated(value="lombok") public Boolean getManualInvoiceMaintIsRelevant()
The system proposes the value from the customer master record. You can change the indicator manually in the sales document.
@Nullable @Generated(value="lombok") public Boolean getIsIntrastatReportingRelevant()
@Nullable @Generated(value="lombok") public Boolean getIsIntrastatReportingExcluded()
@Nullable @Generated(value="lombok") public BigDecimal getTotalNetAmount()
@Nullable @Generated(value="lombok") public String getTransactionCurrency()
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable @Generated(value="lombok") public String getStatisticsCurrency()
@Nullable @Generated(value="lombok") public BigDecimal getTaxAmount()
@Nullable @Generated(value="lombok") public BigDecimal getTotalGrossAmount()
@Nullable @Generated(value="lombok") public String getCustomerPriceGroup()
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.
@Nullable @Generated(value="lombok") public String getPriceListType()
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 appears the number of the price list type You 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.
@Nullable @Generated(value="lombok") public String getTaxDepartureCountry()
A different country needs to be entered for certain internal European transactions (chain transactions).
@Nullable @Generated(value="lombok") public String getVATRegistration()
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.
@Nullable @Generated(value="lombok") public String getVATRegistrationOrigin()
@Nullable @Generated(value="lombok") public String getVATRegistrationCountry()
This key is used to check country-specific entries such as the length of the zip code or bank account number.
@Nullable @Generated(value="lombok") public String getHierarchyTypePricing()
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification1()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification2()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification3()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification4()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification5()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification6()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification7()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification8()
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.
@Nullable @Generated(value="lombok") public String getCustomerTaxClassification9()
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.
@Nullable @Generated(value="lombok") public Boolean getIsEUTriangularDeal()
@Nullable @Generated(value="lombok") public String getSDPricingProcedure()
@Nullable @Generated(value="lombok") public String getShippingCondition()
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.
@Nullable @Generated(value="lombok") public String getIncotermsVersion()
@Nullable @Generated(value="lombok") public String getIncotermsClassification()
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.
@Nullable @Generated(value="lombok") public String getIncotermsTransferLocation()
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").
@Nullable @Generated(value="lombok") public String getIncotermsLocation1()
1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms 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 Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If 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.
@Nullable @Generated(value="lombok") public String getIncotermsLocation2()
No Version: This field is disabled Incoterm Version 2000 This 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 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
@Nullable @Generated(value="lombok") public String getPayerParty()
The payer may differ from the bill-to party who receives the bill.
@Nullable @Generated(value="lombok") public String getContractAccount()
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. Note For 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.
@Nullable @Generated(value="lombok") public String getCustomerPaymentTerms()
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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.
@Nullable @Generated(value="lombok") public String getPaymentMethod()
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.
@Nullable @Generated(value="lombok") public String getPaymentReference()
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'.
@Nullable @Generated(value="lombok") public Calendar getFixedValueDate()
If you enter a date in this field, you cannot enter a value in the additional value days field.
@Nullable @Generated(value="lombok") public String getAdditionalValueDays()
If you enter a value in this field, you cannot enter a date in the fixed value date field.
@Nullable @Generated(value="lombok") public String getSEPAMandate()
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 Mandates You 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 Payers If 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. Example You 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 accounts Contract account Mandate (in Contract Acct) Meaning C1 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 mandate Mandate Contract Account (in Mandate) Meaning M1 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.
@Nullable @Generated(value="lombok") public String getCompanyCode()
@Nullable @Generated(value="lombok") public String getFiscalYear()
@Nullable @Generated(value="lombok") public String getAccountingDocument()
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.
@Nullable @Generated(value="lombok") public String getCustomerAccountAssignmentGroup()
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.
@Nullable @Generated(value="lombok") public String getDocumentReferenceID()
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.
@Nullable @Generated(value="lombok") public String getAssignmentReference()
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.
@Nullable @Generated(value="lombok") public String getDunningArea()
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.
@Nullable @Generated(value="lombok") public String getDunningBlockingReason()
@Nullable @Generated(value="lombok") public String getDunningKey()
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.
@Nullable @Generated(value="lombok") public String getInternalFinancialDocument()
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.
@Nullable @Generated(value="lombok") public Boolean getIsRelevantForAccrual()
@Nullable @Generated(value="lombok") public String getSoldToParty()
@Nullable @Generated(value="lombok") public String getPartnerCompany()
@Nullable @Generated(value="lombok") public String getPurchaseOrderByCustomer()
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).
@Nullable @Generated(value="lombok") public String getCustomerGroup()
@Nullable @Generated(value="lombok") public String getCountry()
The system uses the country key identifier to: Help determine the appropriate taxes during pricing Determine important country-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.
@Nullable @Generated(value="lombok") public String getCityCode()
Currently the key is used only in the USA for handling city tax.
@Nullable @Generated(value="lombok") public String getSalesDistrict()
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.
@Nullable @Generated(value="lombok") public String getRegion()
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 -> Province Brazil -> State Canada -> Province Germany -> State Great Britain -> County Italy -> Province Japan -> Prefecture Switzerland -> Canton USA -> State
@Nullable @Generated(value="lombok") public String getCounty()
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.
@Nullable @Generated(value="lombok") public String getCreditControlArea()
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.
@Nullable @Generated(value="lombok") public String getCustomerRebateAgreement()
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.
@Nullable @Generated(value="lombok") public String getSalesDocumentCondition()
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.
@Nullable @Generated(value="lombok") public String getOverallSDProcessStatus()
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.
@Nullable @Generated(value="lombok") public String getOverallBillingStatus()
@Nullable @Generated(value="lombok") public String getAccountingPostingStatus()
The status message tells you whether the billing document must be posted to accounting, and, if so, whether the posting has taken place.
@Nullable @Generated(value="lombok") public String getAccountingTransferStatus()
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.
@Nullable @Generated(value="lombok") public String getBillingIssueType()
@Nullable @Generated(value="lombok") public String getInvoiceListStatus()
@Nullable @Generated(value="lombok") public String getOvrlItmGeneralIncompletionSts()
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.
@Nullable @Generated(value="lombok") public String getOverallPricingIncompletionSts()
@Nullable @Generated(value="lombok") public String getBillingDocumentListType()
@Nullable @Generated(value="lombok") public Calendar getBillingDocumentListDate()
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.
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setBillingDocument(@Nullable String billingDocument)
billingDocument - @Generated(value="lombok") public void setSDDocumentCategory(@Nullable String 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).
sDDocumentCategory - @Generated(value="lombok") public void setBillingDocumentCategory(@Nullable String billingDocumentCategory)
billingDocumentCategory - @Generated(value="lombok") public void setBillingDocumentType(@Nullable String billingDocumentType)
When you process billing documents collectively, you can use the billing type as one of the selection criteria.
billingDocumentType - @Generated(value="lombok") public void setCreationDate(@Nullable Calendar creationDate)
creationDate - @Generated(value="lombok") public void setCreationTime(@Nullable Calendar creationTime)
creationTime - @Generated(value="lombok") public void setLastChangeDate(@Nullable Calendar lastChangeDate)
lastChangeDate - @Generated(value="lombok") public void setLastChangeDateTime(@Nullable Calendar 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 STAMP A UTC time stamp in short form is also available.
lastChangeDateTime - @Generated(value="lombok") public void setLogicalSystem(@Nullable String 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.
logicalSystem - @Generated(value="lombok") public void setSalesOrganization(@Nullable String 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.
salesOrganization - @Generated(value="lombok") public void setDistributionChannel(@Nullable String 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.
distributionChannel - @Generated(value="lombok") public void setDivision(@Nullable String division)
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise. If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
division - @Generated(value="lombok") public void setBillingDocumentDate(@Nullable Calendar billingDocumentDate)
You can use the billing date as one of the selection criteria when you process billing documents collectively. If invoice dates are defined for the customer, 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. If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document. If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone. 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.
billingDocumentDate - @Generated(value="lombok") public void setBillingDocumentIsCancelled(@Nullable Boolean billingDocumentIsCancelled)
billingDocumentIsCancelled - @Generated(value="lombok") public void setCancelledBillingDocument(@Nullable String cancelledBillingDocument)
cancelledBillingDocument - @Generated(value="lombok") public void setForeignTrade(@Nullable String foreignTrade)
foreignTrade - @Generated(value="lombok") public void setIsExportDelivery(@Nullable String isExportDelivery)
isExportDelivery - @Generated(value="lombok") public void setBillingDocCombinationCriteria(@Nullable String billingDocCombinationCriteria)
billingDocCombinationCriteria - @Generated(value="lombok") public void setManualInvoiceMaintIsRelevant(@Nullable Boolean manualInvoiceMaintIsRelevant)
The system proposes the value from the customer master record. You can change the indicator manually in the sales document.
manualInvoiceMaintIsRelevant - @Generated(value="lombok") public void setIsIntrastatReportingRelevant(@Nullable Boolean isIntrastatReportingRelevant)
isIntrastatReportingRelevant - @Generated(value="lombok") public void setIsIntrastatReportingExcluded(@Nullable Boolean isIntrastatReportingExcluded)
isIntrastatReportingExcluded - @Generated(value="lombok") public void setTotalNetAmount(@Nullable BigDecimal totalNetAmount)
totalNetAmount - @Generated(value="lombok") public void setTransactionCurrency(@Nullable String transactionCurrency)
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency - @Generated(value="lombok") public void setStatisticsCurrency(@Nullable String statisticsCurrency)
statisticsCurrency - @Generated(value="lombok") public void setTaxAmount(@Nullable BigDecimal taxAmount)
taxAmount - @Generated(value="lombok") public void setTotalGrossAmount(@Nullable BigDecimal totalGrossAmount)
totalGrossAmount - @Generated(value="lombok") public void setCustomerPriceGroup(@Nullable String 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.
customerPriceGroup - @Generated(value="lombok") public void setPriceListType(@Nullable String 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 appears the number of the price list type You 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.
priceListType - @Generated(value="lombok") public void setTaxDepartureCountry(@Nullable String taxDepartureCountry)
A different country needs to be entered for certain internal European transactions (chain transactions).
taxDepartureCountry - @Generated(value="lombok") public void setVATRegistration(@Nullable String 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.
vATRegistration - @Generated(value="lombok") public void setVATRegistrationOrigin(@Nullable String vATRegistrationOrigin)
vATRegistrationOrigin - @Generated(value="lombok") public void setVATRegistrationCountry(@Nullable String vATRegistrationCountry)
This key is used to check country-specific entries such as the length of the zip code or bank account number.
vATRegistrationCountry - @Generated(value="lombok") public void setHierarchyTypePricing(@Nullable String hierarchyTypePricing)
hierarchyTypePricing - @Generated(value="lombok") public void setCustomerTaxClassification1(@Nullable String 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.
customerTaxClassification1 - @Generated(value="lombok") public void setCustomerTaxClassification2(@Nullable String 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.
customerTaxClassification2 - @Generated(value="lombok") public void setCustomerTaxClassification3(@Nullable String 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.
customerTaxClassification3 - @Generated(value="lombok") public void setCustomerTaxClassification4(@Nullable String 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.
customerTaxClassification4 - @Generated(value="lombok") public void setCustomerTaxClassification5(@Nullable String 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.
customerTaxClassification5 - @Generated(value="lombok") public void setCustomerTaxClassification6(@Nullable String 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.
customerTaxClassification6 - @Generated(value="lombok") public void setCustomerTaxClassification7(@Nullable String 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.
customerTaxClassification7 - @Generated(value="lombok") public void setCustomerTaxClassification8(@Nullable String 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.
customerTaxClassification8 - @Generated(value="lombok") public void setCustomerTaxClassification9(@Nullable String 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.
customerTaxClassification9 - @Generated(value="lombok") public void setIsEUTriangularDeal(@Nullable Boolean isEUTriangularDeal)
isEUTriangularDeal - @Generated(value="lombok") public void setSDPricingProcedure(@Nullable String sDPricingProcedure)
sDPricingProcedure - @Generated(value="lombok") public void setShippingCondition(@Nullable String 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.
shippingCondition - @Generated(value="lombok") public void setIncotermsVersion(@Nullable String incotermsVersion)
incotermsVersion - @Generated(value="lombok") public void setIncotermsClassification(@Nullable String 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.
incotermsClassification - @Generated(value="lombok") public void setIncotermsTransferLocation(@Nullable String 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").
incotermsTransferLocation - @Generated(value="lombok") public void setIncotermsLocation1(@Nullable String incotermsLocation1)
1. For sea and inland waterway transport - Port of Shipment 2. For any mode of transport - Place of Delivery 2010 Incoterms 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 Delivery FCA Free Carrier Place of Delivery CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination DAF Delivered at Frontier Place of Delivery DDP Delivered Duty Paid Place of Destination DDU Delivered Duty Unpaid Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of Shipment FOB Free On Board Port of Shipment CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination DEQ Delivered Eq Quay (Duty Paid) Port of Destination DES Delivered Ex Ship Port of Destination If 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.
incotermsLocation1 - @Generated(value="lombok") public void setIncotermsLocation2(@Nullable String incotermsLocation2)
No Version: This field is disabled Incoterm Version 2000 This 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 2010 For this version, the field represents: Sea and inland waterway transport - Port of Destination Any mode of transport - Place of Destination 2010 Incoterms are divided as follows: Group 1: Rules for any mode or modes of transport (including by vessel) Incoterms Incoterms Description Location 2 CPT Carriage Paid To Place of Destination CIP Carriage & Insurance Paid To Place of Destination Group 2: Rules for sea and inland waterways Incoterms Incoterms Description Location 2 CFR Cost & Freight Port of Destination CIF Cost Insurance & Freight Port of Destination
incotermsLocation2 - @Generated(value="lombok") public void setPayerParty(@Nullable String payerParty)
The payer may differ from the bill-to party who receives the bill.
payerParty - @Generated(value="lombok") public void setContractAccount(@Nullable String 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. Note For 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.
contractAccount - @Generated(value="lombok") public void setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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.
customerPaymentTerms - @Generated(value="lombok") public void setPaymentMethod(@Nullable String 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.
paymentMethod - @Generated(value="lombok") public void setPaymentReference(@Nullable String 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'.
paymentReference - @Generated(value="lombok") public void setFixedValueDate(@Nullable Calendar fixedValueDate)
If you enter a date in this field, you cannot enter a value in the additional value days field.
fixedValueDate - @Generated(value="lombok") public void setAdditionalValueDays(@Nullable String additionalValueDays)
If you enter a value in this field, you cannot enter a date in the fixed value date field.
additionalValueDays - @Generated(value="lombok") public void setSEPAMandate(@Nullable String 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 Mandates You 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 Payers If 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. Example You 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 accounts Contract account Mandate (in Contract Acct) Meaning C1 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 mandate Mandate Contract Account (in Mandate) Meaning M1 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.
sEPAMandate - @Generated(value="lombok") public void setCompanyCode(@Nullable String companyCode)
companyCode - @Generated(value="lombok") public void setFiscalYear(@Nullable String fiscalYear)
fiscalYear - @Generated(value="lombok") public void setAccountingDocument(@Nullable String 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.
accountingDocument - @Generated(value="lombok") public void setCustomerAccountAssignmentGroup(@Nullable String 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.
customerAccountAssignmentGroup - @Generated(value="lombok") public void setDocumentReferenceID(@Nullable String 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.
documentReferenceID - @Generated(value="lombok") public void setAssignmentReference(@Nullable String 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.
assignmentReference - @Generated(value="lombok") public void setDunningArea(@Nullable String 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.
dunningArea - @Generated(value="lombok") public void setDunningBlockingReason(@Nullable String dunningBlockingReason)
dunningBlockingReason - @Generated(value="lombok") public void setDunningKey(@Nullable String 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.
dunningKey - @Generated(value="lombok") public void setInternalFinancialDocument(@Nullable String 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.
internalFinancialDocument - @Generated(value="lombok") public void setIsRelevantForAccrual(@Nullable Boolean isRelevantForAccrual)
isRelevantForAccrual - @Generated(value="lombok") public void setSoldToParty(@Nullable String soldToParty)
soldToParty - @Generated(value="lombok") public void setPartnerCompany(@Nullable String partnerCompany)
partnerCompany - @Generated(value="lombok") public void setPurchaseOrderByCustomer(@Nullable String 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).
purchaseOrderByCustomer - @Generated(value="lombok") public void setCustomerGroup(@Nullable String customerGroup)
customerGroup - @Generated(value="lombok") public void setCountry(@Nullable String country)
The system uses the country key identifier to: Help determine the appropriate taxes during pricing Determine important country-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.
country - @Generated(value="lombok") public void setCityCode(@Nullable String cityCode)
Currently the key is used only in the USA for handling city tax.
cityCode - @Generated(value="lombok") public void setSalesDistrict(@Nullable String 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.
salesDistrict - @Generated(value="lombok") public void setRegion(@Nullable String 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 -> Province Brazil -> State Canada -> Province Germany -> State Great Britain -> County Italy -> Province Japan -> Prefecture Switzerland -> Canton USA -> State
region - @Generated(value="lombok") public void setCounty(@Nullable String 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.
county - @Generated(value="lombok") public void setCreditControlArea(@Nullable String 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.
creditControlArea - @Generated(value="lombok") public void setCustomerRebateAgreement(@Nullable String 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.
customerRebateAgreement - @Generated(value="lombok") public void setSalesDocumentCondition(@Nullable String 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.
salesDocumentCondition - @Generated(value="lombok") public void setOverallSDProcessStatus(@Nullable String 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.
overallSDProcessStatus - @Generated(value="lombok") public void setOverallBillingStatus(@Nullable String overallBillingStatus)
overallBillingStatus - @Generated(value="lombok") public void setAccountingPostingStatus(@Nullable String accountingPostingStatus)
The status message tells you whether the billing document must be posted to accounting, and, if so, whether the posting has taken place.
accountingPostingStatus - @Generated(value="lombok") public void setAccountingTransferStatus(@Nullable String 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.
accountingTransferStatus - @Generated(value="lombok") public void setBillingIssueType(@Nullable String billingIssueType)
billingIssueType - @Generated(value="lombok") public void setInvoiceListStatus(@Nullable String invoiceListStatus)
invoiceListStatus - @Generated(value="lombok") public void setOvrlItmGeneralIncompletionSts(@Nullable String 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.
ovrlItmGeneralIncompletionSts - @Generated(value="lombok") public void setOverallPricingIncompletionSts(@Nullable String overallPricingIncompletionSts)
overallPricingIncompletionSts - @Generated(value="lombok") public void setBillingDocumentListType(@Nullable String billingDocumentListType)
billingDocumentListType - @Generated(value="lombok") public void setBillingDocumentListDate(@Nullable Calendar 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.
billingDocumentListDate - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<BillingDocument>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<BillingDocument>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<BillingDocument>Copyright © 2017 SAP SE. All rights reserved.