public class CustProjSlsOrdItmBillgPlnItm extends VdmEntity<CustProjSlsOrdItmBillgPlnItm>
Original entity name from the Odata EDM: A_CustProjSlsOrdItmBillgPlnItmType
| Modifier and Type | Class and Description |
|---|---|
static class |
CustProjSlsOrdItmBillgPlnItm.CustProjSlsOrdItmBillgPlnItmBuilder |
| Modifier and Type | Field and Description |
|---|---|
static CustProjSlsOrdItmBillgPlnItmSelectable |
ALL_FIELDS
Selector for all available fields of CustProjSlsOrdItmBillgPlnItm.
|
static CustProjSlsOrdItmBillgPlnItmField<BigDecimal> |
BILLING_PLAN_AMOUNT
Use with available fluent helpers to apply the BillingPlanAmount field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<LocalDateTime> |
BILLING_PLAN_BILLING_DATE
Use with available fluent helpers to apply the BillingPlanBillingDate field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
BILLING_PLAN_ITEM
Use with available fluent helpers to apply the BillingPlanItem field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
BILLING_PLAN_ITEM_DESCRIPTION
Use with available fluent helpers to apply the BillingPlanItemDescription field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
BILLING_PLAN_ITEM_USAGE
Use with available fluent helpers to apply the BillingPlanItemUsage field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
BILLING_PLAN_RELATED_BILLG_STATUS
Use with available fluent helpers to apply the BillingPlanRelatedBillgStatus field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<LocalDateTime> |
BILLING_PLAN_SERVICE_END_DATE
Use with available fluent helpers to apply the BillingPlanServiceEndDate field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<LocalDateTime> |
BILLING_PLAN_SERVICE_START_DATE
Use with available fluent helpers to apply the BillingPlanServiceStartDate field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
CUSTOMER_PROJECT
Use with available fluent helpers to apply the CustomerProject field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
SALES_ORDER
Use with available fluent helpers to apply the SalesOrder field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
SALES_ORDER_ITEM
Use with available fluent helpers to apply the SalesOrderItem field to query operations.
|
static CustProjSlsOrdItmBillgPlnItmField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
changedOriginalFields| Constructor and Description |
|---|
CustProjSlsOrdItmBillgPlnItm() |
CustProjSlsOrdItmBillgPlnItm(String customerProject,
String salesOrderItem,
String billingPlanItem,
String salesOrder,
LocalDateTime billingPlanBillingDate,
String billingPlanRelatedBillgStatus,
BigDecimal billingPlanAmount,
String transactionCurrency,
String billingPlanItemUsage,
String billingPlanItemDescription,
LocalDateTime billingPlanServiceStartDate,
LocalDateTime billingPlanServiceEndDate) |
| Modifier and Type | Method and Description |
|---|---|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static CustProjSlsOrdItmBillgPlnItm.CustProjSlsOrdItmBillgPlnItmBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> CustProjSlsOrdItmBillgPlnItmField<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) |
BigDecimal |
getBillingPlanAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
LocalDateTime |
getBillingPlanBillingDate()
Constraints: Not nullable, Precision: 0
|
String |
getBillingPlanItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getBillingPlanItemDescription()
Constraints: Not nullable, Maximum length: 255
|
String |
getBillingPlanItemUsage()
Constraints: Not nullable, Maximum length: 2
|
String |
getBillingPlanRelatedBillgStatus()
Constraints: Not nullable, Maximum length: 1
|
LocalDateTime |
getBillingPlanServiceEndDate()
Constraints: Not nullable, Precision: 0
|
LocalDateTime |
getBillingPlanServiceStartDate()
Constraints: Not nullable, Precision: 0
|
String |
getCustomerProject()
(Key Field) Constraints: Not nullable, Maximum length: 40
|
protected String |
getDefaultServicePath() |
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
protected String |
getEntityCollection() |
protected Map<String,Object> |
getKey() |
String |
getSalesOrder()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesOrderItem()
(Key Field) Constraints: Not nullable, Maximum length: 6
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<CustProjSlsOrdItmBillgPlnItm> |
getType() |
int |
hashCode() |
void |
setBillingPlanAmount(BigDecimal billingPlanAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
void |
setBillingPlanBillingDate(LocalDateTime billingPlanBillingDate)
Constraints: Not nullable, Precision: 0
|
void |
setBillingPlanItem(String billingPlanItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
void |
setBillingPlanItemDescription(String billingPlanItemDescription)
Constraints: Not nullable, Maximum length: 255
|
void |
setBillingPlanItemUsage(String billingPlanItemUsage)
Constraints: Not nullable, Maximum length: 2
|
void |
setBillingPlanRelatedBillgStatus(String billingPlanRelatedBillgStatus)
Constraints: Not nullable, Maximum length: 1
|
void |
setBillingPlanServiceEndDate(LocalDateTime billingPlanServiceEndDate)
Constraints: Not nullable, Precision: 0
|
void |
setBillingPlanServiceStartDate(LocalDateTime billingPlanServiceStartDate)
Constraints: Not nullable, Precision: 0
|
void |
setCustomerProject(String customerProject)
(Key Field) Constraints: Not nullable, Maximum length: 40
|
void |
setSalesOrder(String salesOrder)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesOrderItem(String salesOrderItem)
(Key Field) Constraints: Not nullable, Maximum length: 6
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifiergetChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationPropertiespublic static final CustProjSlsOrdItmBillgPlnItmSelectable ALL_FIELDS
public static final CustProjSlsOrdItmBillgPlnItmField<String> CUSTOMER_PROJECT
public static final CustProjSlsOrdItmBillgPlnItmField<String> SALES_ORDER_ITEM
public static final CustProjSlsOrdItmBillgPlnItmField<String> BILLING_PLAN_ITEM
public static final CustProjSlsOrdItmBillgPlnItmField<String> SALES_ORDER
public static final CustProjSlsOrdItmBillgPlnItmField<LocalDateTime> BILLING_PLAN_BILLING_DATE
public static final CustProjSlsOrdItmBillgPlnItmField<String> BILLING_PLAN_RELATED_BILLG_STATUS
public static final CustProjSlsOrdItmBillgPlnItmField<BigDecimal> BILLING_PLAN_AMOUNT
public static final CustProjSlsOrdItmBillgPlnItmField<String> TRANSACTION_CURRENCY
public static final CustProjSlsOrdItmBillgPlnItmField<String> BILLING_PLAN_ITEM_USAGE
public static final CustProjSlsOrdItmBillgPlnItmField<String> BILLING_PLAN_ITEM_DESCRIPTION
public static final CustProjSlsOrdItmBillgPlnItmField<LocalDateTime> BILLING_PLAN_SERVICE_START_DATE
public static final CustProjSlsOrdItmBillgPlnItmField<LocalDateTime> BILLING_PLAN_SERVICE_END_DATE
public CustProjSlsOrdItmBillgPlnItm()
public CustProjSlsOrdItmBillgPlnItm(@Nullable String customerProject, @Nullable String salesOrderItem, @Nullable String billingPlanItem, @Nullable String salesOrder, @Nullable LocalDateTime billingPlanBillingDate, @Nullable String billingPlanRelatedBillgStatus, @Nullable BigDecimal billingPlanAmount, @Nullable String transactionCurrency, @Nullable String billingPlanItemUsage, @Nullable String billingPlanItemDescription, @Nullable LocalDateTime billingPlanServiceStartDate, @Nullable LocalDateTime billingPlanServiceEndDate)
@Nonnull public Class<CustProjSlsOrdItmBillgPlnItm> getType()
getType in class VdmObject<CustProjSlsOrdItmBillgPlnItm>public void setCustomerProject(@Nullable String customerProject)
Original property name from the Odata EDM: CustomerProject
customerProject - Identifies a master project.public void setSalesOrderItem(@Nullable String salesOrderItem)
Original property name from the Odata EDM: SalesOrderItem
salesOrderItem - Sales Order Itempublic void setBillingPlanItem(@Nullable String billingPlanItem)
Original property name from the Odata EDM: BillingPlanItem
billingPlanItem - Item for billing plan/invoice plan/payment cardspublic void setSalesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
salesOrder - Sales Orderpublic void setBillingPlanBillingDate(@Nullable LocalDateTime billingPlanBillingDate)
Original property name from the Odata EDM: BillingPlanBillingDate
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.
billingPlanBillingDate - Date on which billing is processed and posted to Accounting.public void setBillingPlanRelatedBillgStatus(@Nullable String billingPlanRelatedBillgStatus)
Original property name from the Odata EDM: BillingPlanRelatedBillgStatus
The statuses are as follows:Not relevantThe item is not relevant for billing. An authorization is not used in billing when the request for authorization is denied.Not processedThe authorization has not yet been used in a billing document.Partially billedThe system has not used all of the authorized amount. It holds this remaining amount for future use.Fully billedThe system has used the authorization in a billing document.This field is for information purposes and cannot be maintained.
billingPlanRelatedBillgStatus - Indicates the billing status of the authorization amount.public void setBillingPlanAmount(@Nullable BigDecimal billingPlanAmount)
Original property name from the Odata EDM: BillingPlanAmount
In the case of a contract, this is a total amount. For a project, this is a partial amount of the overall billing value which is determined on the basis of a percentage.
billingPlanAmount - Specifies the value to be billed which the system determines for the billing date on the basis of the
billing rule assigned to it.public void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
transactionCurrency - Currency key for amounts in the system.public void setBillingPlanItemUsage(@Nullable String billingPlanItemUsage)
Original property name from the Odata EDM: BillingPlanItemUsage
billingPlanItemUsage - Billing Plan Item Usagepublic void setBillingPlanItemDescription(@Nullable String billingPlanItemDescription)
Original property name from the Odata EDM: BillingPlanItemDescription
billingPlanItemDescription - Billing Plan Item Descriptionpublic void setBillingPlanServiceStartDate(@Nullable LocalDateTime billingPlanServiceStartDate)
Original property name from the Odata EDM: BillingPlanServiceStartDate
This date is used in periodic billing when time-dependent prices are defined.Billing plan for a rental contract for a piece of machineryBilling is to be carried out in advance on the first of the month for the entire month. The following price condition has been defined for the contract:Scale Quantity PriceAs of 1 month Rent for machinery per month 1000 USDAs of 12 months Rent for machinery per month 1100 USDThe following billing values are determined on the basis of the settlement period and the price condition.Settlement periodSettl.from date Settl.to date Billing date Billing value06/01/95 06/30/95 06/01/95 100007/01/95 07/31/95 07/01/95 100008/01/95 08/31/95 08/01/95 100006/01/96 06/30/96 06/01/96 1100In the example, the settlement-to date is the end of settlement period date because billing is to be performed in advance, that is, the indicator 'In advance' is set in the billing plan. If billing is to be performed in arrears, that is, the indicator 'In advance' is not set, the settlement-to date is the start of settlement period date.
billingPlanServiceStartDate - Depending on whether billing is to be carried out in advance or in arrears, this is either the start
or end date of the settlement period for a specific billing plan date.public void setBillingPlanServiceEndDate(@Nullable LocalDateTime billingPlanServiceEndDate)
Original property name from the Odata EDM: BillingPlanServiceEndDate
This date is used if time-dependent prices are defined.Billing plan for the rental contract for a piece of equipment.Billing is to take place a month in advance on the first of each month. The following pricing condition is defined for the contract:Scale Quantity PriceAs of 1 Month Rent for one piece of equipment per month 1000 DMAs of 12 Months Rent for one piece of equipment per month 1100 DMThe following billing values are defined on the basis of the settlement period and the pricing condition:Settlement periodSettlement date from Settlement date to Billing date Billing value01.06.95 30.06.95 01.06.95 100001.07.95 31.07.95 01.07.95 100001.08.95 31.08.95 01.08.95 100001.06.96 30.06.96 01.06.95 1100Since billing is to be carried out in advance, the settlement date is proposed as the billing date.In the example, the settlement date is from the start date of the settlement period, becuase billing is to be carried out in advance (the 'in advance' indicator is marked in the billing plan). If billing is to be carried out retrospectivey (the indicator is not set), the settlement date is from the end date of the settlement period.
billingPlanServiceEndDate - Depending on whether the billing was carried out in advance or retrospectively, this is either the
start date or the end date for the settlement period of a deadline in the billing plan.protected String getEntityCollection()
getEntityCollection in class VdmEntity<CustProjSlsOrdItmBillgPlnItm>@Nonnull protected Map<String,Object> getKey()
getKey in class VdmObject<CustProjSlsOrdItmBillgPlnItm>@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields in class VdmObject<CustProjSlsOrdItmBillgPlnItm>protected void fromMap(Map<String,Object> inputValues)
fromMap in class VdmObject<CustProjSlsOrdItmBillgPlnItm>@Nonnull public static <T> CustProjSlsOrdItmBillgPlnItmField<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> CustProjSlsOrdItmBillgPlnItmField<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()
VdmEntitygetDestinationForFetch in class VdmEntity<CustProjSlsOrdItmBillgPlnItm>protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntityNote: 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<CustProjSlsOrdItmBillgPlnItm>public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntityNote: 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<CustProjSlsOrdItmBillgPlnItm>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()
getDefaultServicePath in class VdmEntity<CustProjSlsOrdItmBillgPlnItm>public static CustProjSlsOrdItmBillgPlnItm.CustProjSlsOrdItmBillgPlnItmBuilder builder()
@Nullable public String getCustomerProject()
Original property name from the Odata EDM: CustomerProject
@Nullable public String getSalesOrderItem()
Original property name from the Odata EDM: SalesOrderItem
@Nullable public String getBillingPlanItem()
Original property name from the Odata EDM: BillingPlanItem
@Nullable public String getSalesOrder()
Original property name from the Odata EDM: SalesOrder
@Nullable public LocalDateTime getBillingPlanBillingDate()
Original property name from the Odata EDM: BillingPlanBillingDate
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 String getBillingPlanRelatedBillgStatus()
Original property name from the Odata EDM: BillingPlanRelatedBillgStatus
The statuses are as follows:Not relevantThe item is not relevant for billing. An authorization is not used in billing when the request for authorization is denied.Not processedThe authorization has not yet been used in a billing document.Partially billedThe system has not used all of the authorized amount. It holds this remaining amount for future use.Fully billedThe system has used the authorization in a billing document.This field is for information purposes and cannot be maintained.
@Nullable public BigDecimal getBillingPlanAmount()
Original property name from the Odata EDM: BillingPlanAmount
In the case of a contract, this is a total amount. For a project, this is a partial amount of the overall billing value which is determined on the basis of a percentage.
@Nullable public String getTransactionCurrency()
Original property name from the Odata EDM: TransactionCurrency
@Nullable public String getBillingPlanItemUsage()
Original property name from the Odata EDM: BillingPlanItemUsage
@Nullable public String getBillingPlanItemDescription()
Original property name from the Odata EDM: BillingPlanItemDescription
@Nullable public LocalDateTime getBillingPlanServiceStartDate()
Original property name from the Odata EDM: BillingPlanServiceStartDate
This date is used in periodic billing when time-dependent prices are defined.Billing plan for a rental contract for a piece of machineryBilling is to be carried out in advance on the first of the month for the entire month. The following price condition has been defined for the contract:Scale Quantity PriceAs of 1 month Rent for machinery per month 1000 USDAs of 12 months Rent for machinery per month 1100 USDThe following billing values are determined on the basis of the settlement period and the price condition.Settlement periodSettl.from date Settl.to date Billing date Billing value06/01/95 06/30/95 06/01/95 100007/01/95 07/31/95 07/01/95 100008/01/95 08/31/95 08/01/95 100006/01/96 06/30/96 06/01/96 1100In the example, the settlement-to date is the end of settlement period date because billing is to be performed in advance, that is, the indicator 'In advance' is set in the billing plan. If billing is to be performed in arrears, that is, the indicator 'In advance' is not set, the settlement-to date is the start of settlement period date.
@Nullable public LocalDateTime getBillingPlanServiceEndDate()
Original property name from the Odata EDM: BillingPlanServiceEndDate
This date is used if time-dependent prices are defined.Billing plan for the rental contract for a piece of equipment.Billing is to take place a month in advance on the first of each month. The following pricing condition is defined for the contract:Scale Quantity PriceAs of 1 Month Rent for one piece of equipment per month 1000 DMAs of 12 Months Rent for one piece of equipment per month 1100 DMThe following billing values are defined on the basis of the settlement period and the pricing condition:Settlement periodSettlement date from Settlement date to Billing date Billing value01.06.95 30.06.95 01.06.95 100001.07.95 31.07.95 01.07.95 100001.08.95 31.08.95 01.08.95 100001.06.96 30.06.96 01.06.95 1100Since billing is to be carried out in advance, the settlement date is proposed as the billing date.In the example, the settlement date is from the start date of the settlement period, becuase billing is to be carried out in advance (the 'in advance' indicator is marked in the billing plan). If billing is to be carried out retrospectivey (the indicator is not set), the settlement date is from the end date of the settlement period.
public String toString()
toString in class VdmObject<CustProjSlsOrdItmBillgPlnItm>public boolean equals(Object o)
equals in class VdmObject<CustProjSlsOrdItmBillgPlnItm>protected boolean canEqual(Object other)
canEqual in class VdmObject<CustProjSlsOrdItmBillgPlnItm>public int hashCode()
hashCode in class VdmObject<CustProjSlsOrdItmBillgPlnItm>Copyright © 2019 SAP SE. All rights reserved.