public class BillingDocumentRequest extends VdmEntity<BillingDocumentRequest>
Original entity name from the Odata EDM: A_BillingDocumentRequestType
Modifier and Type | Class and Description |
---|---|
static class |
BillingDocumentRequest.BillingDocumentRequestBuilder
Helper class to allow for fluent creation of BillingDocumentRequest instances.
|
Modifier and Type | Field and Description |
---|---|
static BillingDocumentRequestSelectable |
ALL_FIELDS
Selector for all available fields of BillingDocumentRequest.
|
static BillingDocumentRequestField<LocalDateTime> |
BILLING_DOCUMENT_DATE
Use with available fluent helpers to apply the BillingDocumentDate field to query operations.
|
static BillingDocumentRequestField<String> |
BILLING_DOCUMENT_REQUEST
Use with available fluent helpers to apply the BillingDocumentRequest field to query operations.
|
static BillingDocumentRequestField<String> |
BILLING_DOCUMENT_REQUEST_TYPE
Use with available fluent helpers to apply the BillingDocumentRequestType field to query operations.
|
static BillingDocumentRequestField<String> |
BILLING_ISSUE_TYPE
Use with available fluent helpers to apply the BillingIssueType field to query operations.
|
static BillingDocumentRequestField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static BillingDocumentRequestField<String> |
CONTRACT_ACCOUNT
Use with available fluent helpers to apply the ContractAccount field to query operations.
|
static BillingDocumentRequestField<LocalDateTime> |
CREATION_DATE
Use with available fluent helpers to apply the CreationDate field to query operations.
|
static BillingDocumentRequestField<LocalTime> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static BillingDocumentRequestField<String> |
CUSTOMER_PAYMENT_TERMS
Use with available fluent helpers to apply the CustomerPaymentTerms field to query operations.
|
static BillingDocumentRequestField<String> |
DISTRIBUTION_CHANNEL
Use with available fluent helpers to apply the DistributionChannel field to query operations.
|
static BillingDocumentRequestField<String> |
DIVISION
Use with available fluent helpers to apply the Division field to query operations.
|
static BillingDocumentRequestField<String> |
INCOTERMS_CLASSIFICATION
Use with available fluent helpers to apply the IncotermsClassification field to query operations.
|
static BillingDocumentRequestField<String> |
INCOTERMS_LOCATION1
Use with available fluent helpers to apply the IncotermsLocation1 field to query operations.
|
static BillingDocumentRequestField<String> |
INCOTERMS_LOCATION2
Use with available fluent helpers to apply the IncotermsLocation2 field to query operations.
|
static BillingDocumentRequestField<String> |
INCOTERMS_TRANSFER_LOCATION
Use with available fluent helpers to apply the IncotermsTransferLocation field to query operations.
|
static BillingDocumentRequestField<String> |
INCOTERMS_VERSION
Use with available fluent helpers to apply the IncotermsVersion field to query operations.
|
static BillingDocumentRequestField<LocalDateTime> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static BillingDocumentRequestField<ZonedDateTime> |
LAST_CHANGE_DATE_TIME
Use with available fluent helpers to apply the LastChangeDateTime field to query operations.
|
static BillingDocumentRequestField<String> |
LOGICAL_SYSTEM
Use with available fluent helpers to apply the LogicalSystem field to query operations.
|
static BillingDocumentRequestField<String> |
OVERALL_BILLING_DOC_REQ_STATUS
Use with available fluent helpers to apply the OverallBillingDocReqStatus field to query operations.
|
static BillingDocumentRequestField<String> |
OVERALL_PRICING_INCOMPLETION_STS
Use with available fluent helpers to apply the OverallPricingIncompletionSts field to query operations.
|
static BillingDocumentRequestField<String> |
PAYER_PARTY
Use with available fluent helpers to apply the PayerParty field to query operations.
|
static BillingDocumentRequestField<String> |
PAYMENT_METHOD
Use with available fluent helpers to apply the PaymentMethod field to query operations.
|
static BillingDocumentRequestField<String> |
PRICING_DOCUMENT
Use with available fluent helpers to apply the PricingDocument field to query operations.
|
static BillingDocumentRequestField<String> |
PROPOSED_BILLING_DOCUMENT_TYPE
Use with available fluent helpers to apply the ProposedBillingDocumentType field to query operations.
|
static BillingDocumentRequestField<String> |
PURCHASE_ORDER_BY_CUSTOMER
Use with available fluent helpers to apply the PurchaseOrderByCustomer field to query operations.
|
static BillingDocumentRequestField<String> |
REFERENCE_DOC_SD_DOC_CATEGORY
Use with available fluent helpers to apply the ReferenceDocSDDocCategory field to query operations.
|
static BillingDocumentRequestField<String> |
REFERENCE_DOCUMENT
Use with available fluent helpers to apply the ReferenceDocument field to query operations.
|
static BillingDocumentRequestField<String> |
REFERENCE_DOCUMENT_LOGICAL_SYSTEM
Use with available fluent helpers to apply the ReferenceDocumentLogicalSystem field to query operations.
|
static BillingDocumentRequestField<String> |
SALES_ORGANIZATION
Use with available fluent helpers to apply the SalesOrganization field to query operations.
|
static BillingDocumentRequestField<String> |
SEPA_MANDATE
Use with available fluent helpers to apply the SEPAMandate field to query operations.
|
static BillingDocumentRequestField<String> |
SOLD_TO_PARTY
Use with available fluent helpers to apply the SoldToParty field to query operations.
|
static BillingDocumentRequestField<String> |
TAX_DEPARTURE_COUNTRY
Use with available fluent helpers to apply the TaxDepartureCountry field to query operations.
|
static BillingDocumentRequestLink<BillingDocumentRequestItem> |
TO_ITEM
Use with available fluent helpers to apply the to_Item navigation property to query operations.
|
static BillingDocumentRequestLink<BillingDocReqPartner> |
TO_PARTNER
Use with available fluent helpers to apply the to_Partner navigation property to query operations.
|
static BillingDocumentRequestLink<BillingDocReqPrcgElmnt> |
TO_PRICING_ELEMENT
Use with available fluent helpers to apply the to_PricingElement navigation property to query operations.
|
static BillingDocumentRequestField<BigDecimal> |
TOTAL_GROSS_AMOUNT
Use with available fluent helpers to apply the TotalGrossAmount field to query operations.
|
static BillingDocumentRequestField<BigDecimal> |
TOTAL_NET_AMOUNT
Use with available fluent helpers to apply the TotalNetAmount field to query operations.
|
static BillingDocumentRequestField<BigDecimal> |
TOTAL_TAX_AMOUNT
Use with available fluent helpers to apply the TotalTaxAmount field to query operations.
|
static BillingDocumentRequestField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
BillingDocumentRequest() |
BillingDocumentRequest(String billingDocumentRequest,
String billingDocumentRequestType,
String proposedBillingDocumentType,
LocalDateTime creationDate,
LocalTime creationTime,
LocalDateTime lastChangeDate,
ZonedDateTime lastChangeDateTime,
String logicalSystem,
String salesOrganization,
String distributionChannel,
String division,
LocalDateTime billingDocumentDate,
BigDecimal totalNetAmount,
String transactionCurrency,
BigDecimal totalTaxAmount,
BigDecimal totalGrossAmount,
String taxDepartureCountry,
String payerParty,
String contractAccount,
String customerPaymentTerms,
String paymentMethod,
String sEPAMandate,
String companyCode,
String referenceDocument,
String referenceDocumentLogicalSystem,
String referenceDocSDDocCategory,
String soldToParty,
String purchaseOrderByCustomer,
String pricingDocument,
String billingIssueType,
String incotermsVersion,
String incotermsClassification,
String incotermsTransferLocation,
String incotermsLocation1,
String incotermsLocation2,
String overallBillingDocReqStatus,
String overallPricingIncompletionSts,
List<BillingDocumentRequestItem> toItem,
List<BillingDocReqPartner> toPartner,
List<BillingDocReqPrcgElmnt> toPricingElement) |
Modifier and Type | Method and Description |
---|---|
void |
addItem(BillingDocumentRequestItem... entity)
Adds elements to the list of associated BillingDocumentRequestItem entities.
|
void |
addPartner(BillingDocReqPartner... entity)
Adds elements to the list of associated BillingDocReqPartner entities.
|
void |
addPricingElement(BillingDocReqPrcgElmnt... entity)
Adds elements to the list of associated BillingDocReqPrcgElmnt entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static BillingDocumentRequest.BillingDocumentRequestBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<BillingDocumentRequestItem> |
fetchItem()
Fetches the BillingDocumentRequestItem entities (one to many) associated with this entity.
|
List<BillingDocReqPartner> |
fetchPartner()
Fetches the BillingDocReqPartner entities (one to many) associated with this entity.
|
List<BillingDocReqPrcgElmnt> |
fetchPricingElement()
Fetches the BillingDocReqPrcgElmnt entities (one to many) associated with this entity.
|
static <T> BillingDocumentRequestField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
LocalDateTime |
getBillingDocumentDate()
Constraints: Not nullable, Precision: 0
|
String |
getBillingDocumentRequest()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getBillingDocumentRequestType()
Constraints: Not nullable, Maximum length: 4
|
String |
getBillingIssueType()
Constraints: Not nullable, Maximum length: 1
|
String |
getCompanyCode()
Constraints: Not nullable, Maximum length: 4
|
String |
getContractAccount()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getCreationDate()
Constraints: Not nullable, Precision: 0
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
String |
getDistributionChannel()
Constraints: Not nullable, Maximum length: 2
|
String |
getDivision()
Constraints: Not nullable, Maximum length: 2
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
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
|
io.vavr.control.Option<List<BillingDocumentRequestItem>> |
getItemIfPresent()
Retrieval of associated BillingDocumentRequestItem entities (one to many).
|
List<BillingDocumentRequestItem> |
getItemOrFetch()
Retrieval of associated BillingDocumentRequestItem entities (one to many).
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getLastChangeDate()
Constraints: Not nullable, Precision: 0
|
ZonedDateTime |
getLastChangeDateTime()
Constraints: Not nullable, Precision: 7
|
String |
getLogicalSystem()
Constraints: Not nullable, Maximum length: 10
|
String |
getOverallBillingDocReqStatus()
Constraints: Not nullable, Maximum length: 1
|
String |
getOverallPricingIncompletionSts()
Constraints: Not nullable, Maximum length: 1
|
io.vavr.control.Option<List<BillingDocReqPartner>> |
getPartnerIfPresent()
Retrieval of associated BillingDocReqPartner entities (one to many).
|
List<BillingDocReqPartner> |
getPartnerOrFetch()
Retrieval of associated BillingDocReqPartner entities (one to many).
|
String |
getPayerParty()
Constraints: Not nullable, Maximum length: 10
|
String |
getPaymentMethod()
Constraints: Not nullable, Maximum length: 1
|
String |
getPricingDocument()
Constraints: Not nullable, Maximum length: 10
|
io.vavr.control.Option<List<BillingDocReqPrcgElmnt>> |
getPricingElementIfPresent()
Retrieval of associated BillingDocReqPrcgElmnt entities (one to many).
|
List<BillingDocReqPrcgElmnt> |
getPricingElementOrFetch()
Retrieval of associated BillingDocReqPrcgElmnt entities (one to many).
|
String |
getProposedBillingDocumentType()
Constraints: Not nullable, Maximum length: 4
|
String |
getPurchaseOrderByCustomer()
Constraints: Not nullable, Maximum length: 35
|
String |
getReferenceDocSDDocCategory()
Constraints: Not nullable, Maximum length: 4
|
String |
getReferenceDocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getReferenceDocumentLogicalSystem()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesOrganization()
Constraints: Not nullable, Maximum length: 4
|
String |
getSEPAMandate()
Constraints: Not nullable, Maximum length: 35
|
String |
getSoldToParty()
Constraints: Not nullable, Maximum length: 10
|
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
|
BigDecimal |
getTotalTaxAmount()
Constraints: Not nullable, Precision: 14, Scale: 3
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<BillingDocumentRequest> |
getType() |
int |
hashCode() |
void |
setBillingDocumentDate(LocalDateTime billingDocumentDate)
Constraints: Not nullable, Precision: 0
|
void |
setBillingDocumentRequest(String billingDocumentRequest)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setBillingDocumentRequestType(String billingDocumentRequestType)
Constraints: Not nullable, Maximum length: 4
|
void |
setBillingIssueType(String billingIssueType)
Constraints: Not nullable, Maximum length: 1
|
void |
setCompanyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setContractAccount(String contractAccount)
Constraints: Not nullable, Maximum length: 12
|
void |
setCreationDate(LocalDateTime creationDate)
Constraints: Not nullable, Precision: 0
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerPaymentTerms(String customerPaymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setDistributionChannel(String distributionChannel)
Constraints: Not nullable, Maximum length: 2
|
void |
setDivision(String division)
Constraints: Not nullable, Maximum length: 2
|
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 |
setItem(List<BillingDocumentRequestItem> value)
Overwrites the list of associated BillingDocumentRequestItem entities for the loaded navigation property
to_Item.
|
void |
setLastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0
|
void |
setLastChangeDateTime(ZonedDateTime lastChangeDateTime)
Constraints: Not nullable, Precision: 7
|
void |
setLogicalSystem(String logicalSystem)
Constraints: Not nullable, Maximum length: 10
|
void |
setOverallBillingDocReqStatus(String overallBillingDocReqStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setOverallPricingIncompletionSts(String overallPricingIncompletionSts)
Constraints: Not nullable, Maximum length: 1
|
void |
setPartner(List<BillingDocReqPartner> value)
Overwrites the list of associated BillingDocReqPartner entities for the loaded navigation property
to_Partner.
|
void |
setPayerParty(String payerParty)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1
|
void |
setPricingDocument(String pricingDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setPricingElement(List<BillingDocReqPrcgElmnt> value)
Overwrites the list of associated BillingDocReqPrcgElmnt entities for the loaded navigation property
to_PricingElement.
|
void |
setProposedBillingDocumentType(String proposedBillingDocumentType)
Constraints: Not nullable, Maximum length: 4
|
void |
setPurchaseOrderByCustomer(String purchaseOrderByCustomer)
Constraints: Not nullable, Maximum length: 35
|
void |
setReferenceDocSDDocCategory(String referenceDocSDDocCategory)
Constraints: Not nullable, Maximum length: 4
|
void |
setReferenceDocument(String referenceDocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setReferenceDocumentLogicalSystem(String referenceDocumentLogicalSystem)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesOrganization(String salesOrganization)
Constraints: Not nullable, Maximum length: 4
|
void |
setSEPAMandate(String sEPAMandate)
Constraints: Not nullable, Maximum length: 35
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setSoldToParty(String soldToParty)
Constraints: Not nullable, Maximum length: 10
|
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 |
setTotalTaxAmount(BigDecimal totalTaxAmount)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final BillingDocumentRequestSelectable ALL_FIELDS
public static final BillingDocumentRequestField<String> BILLING_DOCUMENT_REQUEST
public static final BillingDocumentRequestField<String> BILLING_DOCUMENT_REQUEST_TYPE
public static final BillingDocumentRequestField<String> PROPOSED_BILLING_DOCUMENT_TYPE
public static final BillingDocumentRequestField<LocalDateTime> CREATION_DATE
public static final BillingDocumentRequestField<LocalTime> CREATION_TIME
public static final BillingDocumentRequestField<LocalDateTime> LAST_CHANGE_DATE
public static final BillingDocumentRequestField<ZonedDateTime> LAST_CHANGE_DATE_TIME
public static final BillingDocumentRequestField<String> LOGICAL_SYSTEM
public static final BillingDocumentRequestField<String> SALES_ORGANIZATION
public static final BillingDocumentRequestField<String> DISTRIBUTION_CHANNEL
public static final BillingDocumentRequestField<String> DIVISION
public static final BillingDocumentRequestField<LocalDateTime> BILLING_DOCUMENT_DATE
public static final BillingDocumentRequestField<BigDecimal> TOTAL_NET_AMOUNT
public static final BillingDocumentRequestField<String> TRANSACTION_CURRENCY
public static final BillingDocumentRequestField<BigDecimal> TOTAL_TAX_AMOUNT
public static final BillingDocumentRequestField<BigDecimal> TOTAL_GROSS_AMOUNT
public static final BillingDocumentRequestField<String> TAX_DEPARTURE_COUNTRY
public static final BillingDocumentRequestField<String> PAYER_PARTY
public static final BillingDocumentRequestField<String> CONTRACT_ACCOUNT
public static final BillingDocumentRequestField<String> CUSTOMER_PAYMENT_TERMS
public static final BillingDocumentRequestField<String> PAYMENT_METHOD
public static final BillingDocumentRequestField<String> SEPA_MANDATE
public static final BillingDocumentRequestField<String> COMPANY_CODE
public static final BillingDocumentRequestField<String> REFERENCE_DOCUMENT
public static final BillingDocumentRequestField<String> REFERENCE_DOCUMENT_LOGICAL_SYSTEM
public static final BillingDocumentRequestField<String> REFERENCE_DOC_SD_DOC_CATEGORY
public static final BillingDocumentRequestField<String> SOLD_TO_PARTY
public static final BillingDocumentRequestField<String> PURCHASE_ORDER_BY_CUSTOMER
public static final BillingDocumentRequestField<String> PRICING_DOCUMENT
public static final BillingDocumentRequestField<String> BILLING_ISSUE_TYPE
public static final BillingDocumentRequestField<String> INCOTERMS_VERSION
public static final BillingDocumentRequestField<String> INCOTERMS_CLASSIFICATION
public static final BillingDocumentRequestField<String> INCOTERMS_TRANSFER_LOCATION
public static final BillingDocumentRequestField<String> INCOTERMS_LOCATION1
public static final BillingDocumentRequestField<String> INCOTERMS_LOCATION2
public static final BillingDocumentRequestField<String> OVERALL_BILLING_DOC_REQ_STATUS
public static final BillingDocumentRequestField<String> OVERALL_PRICING_INCOMPLETION_STS
public static final BillingDocumentRequestLink<BillingDocumentRequestItem> TO_ITEM
public static final BillingDocumentRequestLink<BillingDocReqPartner> TO_PARTNER
public static final BillingDocumentRequestLink<BillingDocReqPrcgElmnt> TO_PRICING_ELEMENT
public BillingDocumentRequest()
public BillingDocumentRequest(@Nullable String billingDocumentRequest, @Nullable String billingDocumentRequestType, @Nullable String proposedBillingDocumentType, @Nullable LocalDateTime creationDate, @Nullable LocalTime creationTime, @Nullable LocalDateTime lastChangeDate, @Nullable ZonedDateTime lastChangeDateTime, @Nullable String logicalSystem, @Nullable String salesOrganization, @Nullable String distributionChannel, @Nullable String division, @Nullable LocalDateTime billingDocumentDate, @Nullable BigDecimal totalNetAmount, @Nullable String transactionCurrency, @Nullable BigDecimal totalTaxAmount, @Nullable BigDecimal totalGrossAmount, @Nullable String taxDepartureCountry, @Nullable String payerParty, @Nullable String contractAccount, @Nullable String customerPaymentTerms, @Nullable String paymentMethod, @Nullable String sEPAMandate, @Nullable String companyCode, @Nullable String referenceDocument, @Nullable String referenceDocumentLogicalSystem, @Nullable String referenceDocSDDocCategory, @Nullable String soldToParty, @Nullable String purchaseOrderByCustomer, @Nullable String pricingDocument, @Nullable String billingIssueType, @Nullable String incotermsVersion, @Nullable String incotermsClassification, @Nullable String incotermsTransferLocation, @Nullable String incotermsLocation1, @Nullable String incotermsLocation2, @Nullable String overallBillingDocReqStatus, @Nullable String overallPricingIncompletionSts, List<BillingDocumentRequestItem> toItem, List<BillingDocReqPartner> toPartner, List<BillingDocReqPrcgElmnt> toPricingElement)
@Nonnull public Class<BillingDocumentRequest> getType()
getType
in class VdmObject<BillingDocumentRequest>
public void setBillingDocumentRequest(@Nullable String billingDocumentRequest)
Original property name from the Odata EDM: BillingDocumentRequest
billingDocumentRequest
- Billing Document Requestpublic void setBillingDocumentRequestType(@Nullable String billingDocumentRequestType)
Original property name from the Odata EDM: BillingDocumentRequestType
billingDocumentRequestType
- Billing Document Request Typepublic void setProposedBillingDocumentType(@Nullable String proposedBillingDocumentType)
Original property name from the Odata EDM: ProposedBillingDocumentType
proposedBillingDocumentType
- When a billable document (for example, an outbound delivery or billing document request) is billed,
the system per default creates a billing document of the proposed billing type.public void setCreationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
creationDate
- Date on Which Record Was Createdpublic void setCreationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
creationTime
- The time of day at which the document was posted and stored in the system.public void setLastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
lastChangeDate
- Date of Last Changepublic void setLastChangeDateTime(@Nullable ZonedDateTime lastChangeDateTime)
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
lastChangeDateTime
- The UTC timestamp displays date and time according to UTC (Universal Coordinated Time).public void setLogicalSystem(@Nullable String logicalSystem)
Original property name from the Odata EDM: LogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
logicalSystem
- System in which applications run integrated on a shared data basis.public void setSalesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
salesOrganization
- An organizational unit responsible for the sale of certain products or services. The responsibility of
a sales organization may include legal liability for products and customer claims.public void setDistributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
distributionChannel
- The way in which products or services reach the customer. Typical examples of distribution channels
are wholesale, retail, or direct sales.public void setDivision(@Nullable String division)
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
division
- A way of grouping materials, products, or services. The system uses divisions to determine the sales
areas and the business areas for a material, product, or service.public void setBillingDocumentDate(@Nullable LocalDateTime billingDocumentDate)
Original property name from the Odata EDM: BillingDocumentDate
When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
billingDocumentDate
- Date on which billing is processed and posted to Accounting.public void setTotalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
totalNetAmount
- Net value of the document item.public void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
transactionCurrency
- The currency that applies to the document (for example, to a sales order or an invoice).public void setTotalTaxAmount(@Nullable BigDecimal totalTaxAmount)
Original property name from the Odata EDM: TotalTaxAmount
totalTaxAmount
- The total sales taxes, expressed in the document currency.public void setTotalGrossAmount(@Nullable BigDecimal totalGrossAmount)
Original property name from the Odata EDM: TotalGrossAmount
totalGrossAmount
- The totalGrossAmount to set.public void setTaxDepartureCountry(@Nullable String taxDepartureCountry)
Original property name from the Odata EDM: TaxDepartureCountry
A different country needs to be entered for certain internal European transactions (chain transactions).
taxDepartureCountry
- For tax determination, the country of departure is used as the plant country.public void setPayerParty(@Nullable String payerParty)
Original property name from the Odata EDM: PayerParty
The payer may differ from the bill-to party who receives the bill.
payerParty
- The party who is responsible for actually paying the bill.public void setContractAccount(@Nullable String contractAccount)
Original property name from the Odata EDM: ContractAccount
The postings in Contract Accounts Receivable and Payable are always assigned to a contract account and a business partner.In the contract account master record, specifically for each business partner, you can define procedures that are to be used for further processing of line items. These include for example, payment methods, dunning procedure, tolerances.NoteFor utility and insurance companies, a contract is assigned to exactly one contract account. However several accounts - depending on contract account type can be assigned to one contract account.
contractAccount
- Key that uniquely identifies a contract account per client.public void setCustomerPaymentTerms(@Nullable String customerPaymentTerms)
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
customerPaymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setPaymentMethod(@Nullable String paymentMethod)
Original property name from the Odata EDM: PaymentMethod
If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
paymentMethod
- Payment method with which this item is to be paid.public void setSEPAMandate(@Nullable String sEPAMandate)
Original property name from the Odata EDM: SEPAMandate
The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment.Whether internal or external number assignment (or both) is possible depends on the application concerned.Once you have created the mandate, you can no longer change its mandate reference.At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field.Notes on Assigning Contract Accounts and Contracts to MandatesYou can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment.Notes on Using Alternative PayersIf you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen.ExampleYou enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1.Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects.Example - Assignment of a mandate to multiple contract accountsContract account Mandate (in Contract Acct) MeaningC1 M1 Mandate M1 is valid for C1.C2 M1 Mandate M1 is also valid for C2.C3 M2 Mandate M2 is valid for C3.C4 M2 Mandate M2 is also valid for C4.Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account.Example - Assignment of one contract account per mandateMandate Contract Account (in Mandate) MeaningM1 C1 Mandate M1 is only valid for items of contract account C1.M2 C2 Mandate M2 is only valid for items of contract account C2.If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects.The examples above apply in a similar manner to the assignment of contracts.Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate.If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details.If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment.If you do not make any specification, the system uses the first mandate that qualifies for the payment.
sEPAMandate
- Identifies, together with the Creditor Identifier, the mandate uniquely.public void setCompanyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
companyCode
- The company code is an organizational unit within financial accounting.public void setReferenceDocument(@Nullable String referenceDocument)
Original property name from the Odata EDM: ReferenceDocument
referenceDocument
- Source document of data contained in billing doc. requestpublic void setReferenceDocumentLogicalSystem(@Nullable String referenceDocumentLogicalSystem)
Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
referenceDocumentLogicalSystem
- Source system of the data contained in the billing doc. req.public void setReferenceDocSDDocCategory(@Nullable String referenceDocSDDocCategory)
Original property name from the Odata EDM: ReferenceDocSDDocCategory
referenceDocSDDocCategory
- Source Document Categorypublic void setSoldToParty(@Nullable String soldToParty)
Original property name from the Odata EDM: SoldToParty
soldToParty
- The customer who orders the goods or services. The sold-to party is contractually responsible for
sales orders.public void setPurchaseOrderByCustomer(@Nullable String purchaseOrderByCustomer)
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
purchaseOrderByCustomer
- Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a
purchase order).public void setPricingDocument(@Nullable String pricingDocument)
Original property name from the Odata EDM: PricingDocument
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.
pricingDocument
- The internal number under which the system saves conditions that apply to a sales order, for example.public void setBillingIssueType(@Nullable String billingIssueType)
Original property name from the Odata EDM: BillingIssueType
billingIssueType
- Billing Issue Typepublic void setIncotermsVersion(@Nullable String incotermsVersion)
Original property name from the Odata EDM: IncotermsVersion
incotermsVersion
- An incoterms version is an edition containing a list of international terms for transportation that is
defined by the International Chamber of Commerce (ICC).public void setIncotermsClassification(@Nullable String incotermsClassification)
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
incotermsClassification
- Commonly used trading terms that comply with the standards established by the International Chamber of
Commerce (ICC).public void setIncotermsTransferLocation(@Nullable String incotermsTransferLocation)
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
incotermsTransferLocation
- Additional information for the primary Incoterm.public void setIncotermsLocation1(@Nullable String incotermsLocation1)
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
incotermsLocation1
- Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:public void setIncotermsLocation2(@Nullable String incotermsLocation2)
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
incotermsLocation2
- Provides additional information for the Incoterms. This field is only available for C-Clauses (if
customized appropriately). Note the following for the incoterms versions below:public void setOverallBillingDocReqStatus(@Nullable String overallBillingDocReqStatus)
Original property name from the Odata EDM: OverallBillingDocReqStatus
overallBillingDocReqStatus
- Billing Document Request Statuspublic void setOverallPricingIncompletionSts(@Nullable String overallPricingIncompletionSts)
Original property name from the Odata EDM: OverallPricingIncompletionSts
overallPricingIncompletionSts
- Pricing Incompletion Status (All Items)protected String getEntityCollection()
VdmEntity
getEntityCollection
in class VdmEntity<BillingDocumentRequest>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<BillingDocumentRequest>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<BillingDocumentRequest>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<BillingDocumentRequest>
@Nonnull public static <T> BillingDocumentRequestField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T
- The type of the extension field when performing value comparisons.fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> BillingDocumentRequestField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T
- The type of the extension field when performing value comparisons.DomainT
- The type of the extension field as returned by the OData service.typeConverter
- A TypeConverterfieldName
- The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntity
getDestinationForFetch
in class VdmEntity<BillingDocumentRequest>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch
in class VdmEntity<BillingDocumentRequest>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService
in class VdmEntity<BillingDocumentRequest>
servicePath
- Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination
- New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntity
getDefaultServicePath
in class VdmEntity<BillingDocumentRequest>
protocol://hostname:port
and the OData resource name (entity set, $metadata
, etc.)@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<BillingDocumentRequest>
@Nonnull public List<BillingDocumentRequestItem> 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.@Nonnull public List<BillingDocumentRequestItem> getItemOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Item of a queried BillingDocumentRequest is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<BillingDocumentRequestItem>> getItemIfPresent()
If the navigation property for an entity BillingDocumentRequest has not been resolved yet, this method
will not query further information. Instead its Option
result state will be
empty
.
Option
with result state
empty
is returned.public void setItem(@Nonnull List<BillingDocumentRequestItem> value)
If the navigation property to_Item of a queried BillingDocumentRequest 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 BillingDocumentRequestItem entities.public void addItem(BillingDocumentRequestItem... entity)
If the navigation property to_Item of a queried BillingDocumentRequest 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 BillingDocumentRequestItem entities.@Nonnull public List<BillingDocReqPartner> fetchPartner() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<BillingDocReqPartner> getPartnerOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_Partner of a queried BillingDocumentRequest is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<BillingDocReqPartner>> getPartnerIfPresent()
If the navigation property for an entity BillingDocumentRequest has not been resolved yet, this method
will not query further information. Instead its Option
result state will be
empty
.
Option
with result state
empty
is returned.public void setPartner(@Nonnull List<BillingDocReqPartner> value)
If the navigation property to_Partner of a queried BillingDocumentRequest 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 BillingDocReqPartner entities.public void addPartner(BillingDocReqPartner... entity)
If the navigation property to_Partner of a queried BillingDocumentRequest 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 BillingDocReqPartner entities.@Nonnull public List<BillingDocReqPrcgElmnt> fetchPricingElement() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<BillingDocReqPrcgElmnt> getPricingElementOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PricingElement of a queried BillingDocumentRequest is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<BillingDocReqPrcgElmnt>> getPricingElementIfPresent()
If the navigation property for an entity BillingDocumentRequest has not been resolved yet, this method
will not query further information. Instead its Option
result state will be
empty
.
Option
with result state
empty
is returned.public void setPricingElement(@Nonnull List<BillingDocReqPrcgElmnt> value)
If the navigation property to_PricingElement of a queried BillingDocumentRequest 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 BillingDocReqPrcgElmnt entities.public void addPricingElement(BillingDocReqPrcgElmnt... entity)
If the navigation property to_PricingElement of a queried BillingDocumentRequest 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 BillingDocReqPrcgElmnt entities.@Nonnull public static BillingDocumentRequest.BillingDocumentRequestBuilder builder()
@Nullable public String getBillingDocumentRequest()
Original property name from the Odata EDM: BillingDocumentRequest
@Nullable public String getBillingDocumentRequestType()
Original property name from the Odata EDM: BillingDocumentRequestType
@Nullable public String getProposedBillingDocumentType()
Original property name from the Odata EDM: ProposedBillingDocumentType
@Nullable public LocalDateTime getCreationDate()
Original property name from the Odata EDM: CreationDate
@Nullable public LocalTime getCreationTime()
Original property name from the Odata EDM: CreationTime
@Nullable public LocalDateTime getLastChangeDate()
Original property name from the Odata EDM: LastChangeDate
@Nullable public ZonedDateTime getLastChangeDateTime()
Original property name from the Odata EDM: LastChangeDateTime
In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
@Nullable public String getLogicalSystem()
Original property name from the Odata EDM: LogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
@Nullable public String getSalesOrganization()
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
@Nullable public String getDistributionChannel()
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
@Nullable public String getDivision()
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
@Nullable public LocalDateTime getBillingDocumentDate()
Original property name from the Odata EDM: BillingDocumentDate
When you process billing documents in collective processing, you can use the billing date as a selection criterion.If invoice dates are defined for customers, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date. When billing services, the system proposes the date of services rendered. You can change the date in the sales document manually.If you use a billing plan to bill a project, the system can use the planned and actual dates to propose billing dates for the billing plan in the corresponding partial billing. In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
@Nullable public BigDecimal getTotalNetAmount()
Original property name from the Odata EDM: TotalNetAmount
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document.
@Nullable public BigDecimal getTotalTaxAmount()
Original property name from the Odata EDM: TotalTaxAmount
@Nullable public BigDecimal getTotalGrossAmount()
Original property name from the Odata EDM: TotalGrossAmount
@Nullable public String getTaxDepartureCountry()
Original property name from the Odata EDM: TaxDepartureCountry
A different country needs to be entered for certain internal European transactions (chain transactions).
@Nullable public String getPayerParty()
Original property name from the Odata EDM: PayerParty
The payer may differ from the bill-to party who receives the bill.
@Nullable public String getContractAccount()
Original property name from the Odata EDM: ContractAccount
The postings in Contract Accounts Receivable and Payable are always assigned to a contract account and a business partner.In the contract account master record, specifically for each business partner, you can define procedures that are to be used for further processing of line items. These include for example, payment methods, dunning procedure, tolerances.NoteFor utility and insurance companies, a contract is assigned to exactly one contract account. However several accounts - depending on contract account type can be assigned to one contract account.
@Nullable public String getCustomerPaymentTerms()
Original property name from the Odata EDM: CustomerPaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
@Nullable public String getPaymentMethod()
Original property name from the Odata EDM: PaymentMethod
If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
@Nullable public String getSEPAMandate()
Original property name from the Odata EDM: SEPAMandate
The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment.Whether internal or external number assignment (or both) is possible depends on the application concerned.Once you have created the mandate, you can no longer change its mandate reference.At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field.Notes on Assigning Contract Accounts and Contracts to MandatesYou can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment.Notes on Using Alternative PayersIf you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen.ExampleYou enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1.Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects.Example - Assignment of a mandate to multiple contract accountsContract account Mandate (in Contract Acct) MeaningC1 M1 Mandate M1 is valid for C1.C2 M1 Mandate M1 is also valid for C2.C3 M2 Mandate M2 is valid for C3.C4 M2 Mandate M2 is also valid for C4.Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account.Example - Assignment of one contract account per mandateMandate Contract Account (in Mandate) MeaningM1 C1 Mandate M1 is only valid for items of contract account C1.M2 C2 Mandate M2 is only valid for items of contract account C2.If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects.The examples above apply in a similar manner to the assignment of contracts.Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate.If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details.If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment.If you do not make any specification, the system uses the first mandate that qualifies for the payment.
@Nullable public String getCompanyCode()
Original property name from the Odata EDM: CompanyCode
@Nullable public String getReferenceDocument()
Original property name from the Odata EDM: ReferenceDocument
@Nullable public String getReferenceDocumentLogicalSystem()
Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
@Nullable public String getReferenceDocSDDocCategory()
Original property name from the Odata EDM: ReferenceDocSDDocCategory
@Nullable public String getSoldToParty()
Original property name from the Odata EDM: SoldToParty
@Nullable public String getPurchaseOrderByCustomer()
Original property name from the Odata EDM: PurchaseOrderByCustomer
The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note).
@Nullable public String getPricingDocument()
Original property name from the Odata EDM: PricingDocument
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 public String getBillingIssueType()
Original property name from the Odata EDM: BillingIssueType
@Nullable public String getIncotermsVersion()
Original property name from the Odata EDM: IncotermsVersion
@Nullable public String getIncotermsClassification()
Original property name from the Odata EDM: IncotermsClassification
Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example.
@Nullable public String getIncotermsTransferLocation()
Original property name from the Odata EDM: IncotermsTransferLocation
If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston").
@Nullable public String getIncotermsLocation1()
Original property name from the Odata EDM: IncotermsLocation1
1. For sea and inland waterway transport - Port of Shipment2. For any mode of transport - Place of Delivery 2010Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 1 EXW Ex Works Place of DeliveryFCA Free Carrier Place of DeliveryCPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationDAF Delivered at Frontier Place of DeliveryDDP Delivered Duty Paid Place of DestinationDDU Delivered Duty Unpaid Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 1 FAS Free Alongside Ship Port of ShipmentFOB Free On Board Port of ShipmentCFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of DestinationDEQ Delivered Eq Quay (Duty Paid) Port of DestinationDES Delivered Ex Ship Port of DestinationIf the primary incoterm is specified as FOB “Free on Board”, the second field provides details of the port from which the delivery leaves, such as FOB Boston.
@Nullable public String getIncotermsLocation2()
Original property name from the Odata EDM: IncotermsLocation2
No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination
@Nullable public String getOverallBillingDocReqStatus()
Original property name from the Odata EDM: OverallBillingDocReqStatus
@Nullable public String getOverallPricingIncompletionSts()
Original property name from the Odata EDM: OverallPricingIncompletionSts
@Nonnull public String toString()
toString
in class VdmObject<BillingDocumentRequest>
public boolean equals(@Nullable Object o)
equals
in class VdmObject<BillingDocumentRequest>
protected boolean canEqual(@Nullable Object other)
canEqual
in class VdmObject<BillingDocumentRequest>
public int hashCode()
hashCode
in class VdmObject<BillingDocumentRequest>
Copyright © 2021 SAP SE. All rights reserved.