public class CustomerDunning extends VdmEntity<CustomerDunning>
Modifier and Type | Class and Description |
---|---|
static class |
CustomerDunning.CustomerDunningBuilder |
Modifier and Type | Field and Description |
---|---|
static CustomerDunningSelectable |
ALL_FIELDS
Selector for all available fields of CustomerDunning.
|
static CustomerDunningField<String> |
AUTHORIZATION_GROUP
Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
|
static CustomerDunningField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static CustomerDunningField<String> |
CUSTOMER
Use with available fluent helpers to apply the Customer field to query operations.
|
static CustomerDunningField<String> |
CUSTOMER_ACCOUNT_GROUP
Use with available fluent helpers to apply the CustomerAccountGroup field to query operations.
|
static CustomerDunningField<String> |
DUNNING_AREA
Use with available fluent helpers to apply the DunningArea field to query operations.
|
static CustomerDunningField<String> |
DUNNING_BLOCK
Use with available fluent helpers to apply the DunningBlock field to query operations.
|
static CustomerDunningField<String> |
DUNNING_CLERK
Use with available fluent helpers to apply the DunningClerk field to query operations.
|
static CustomerDunningField<String> |
DUNNING_LEVEL
Use with available fluent helpers to apply the DunningLevel field to query operations.
|
static CustomerDunningField<String> |
DUNNING_PROCEDURE
Use with available fluent helpers to apply the DunningProcedure field to query operations.
|
static CustomerDunningField<String> |
DUNNING_RECIPIENT
Use with available fluent helpers to apply the DunningRecipient field to query operations.
|
static CustomerDunningField<Calendar> |
LAST_DUNNED_ON
Use with available fluent helpers to apply the LastDunnedOn field to query operations.
|
static CustomerDunningField<Calendar> |
LEG_DUNNING_PROCEDURE_ON
Use with available fluent helpers to apply the LegDunningProcedureOn field to query operations.
|
Constructor and Description |
---|
CustomerDunning() |
CustomerDunning(String customer,
String companyCode,
String dunningArea,
String dunningBlock,
String dunningLevel,
String dunningProcedure,
String dunningRecipient,
Calendar lastDunnedOn,
Calendar legDunningProcedureOn,
String dunningClerk,
String authorizationGroup,
String customerAccountGroup,
ErpConfigContext erpConfigContext) |
Modifier and Type | Method and Description |
---|---|
static CustomerDunning.CustomerDunningBuilder |
builder() |
boolean |
equals(Object o) |
static <T> CustomerDunningField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getAuthorizationGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getCompanyCode()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getCustomer()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getCustomerAccountGroup()
Constraints: Not nullable, Maximum length: 4 in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
|
String |
getDunningArea()
(Key Field) Constraints: Not nullable, Maximum length: 2 If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items.
|
String |
getDunningBlock()
Constraints: Not nullable, Maximum length: 1
|
String |
getDunningClerk()
Constraints: Not nullable, Maximum length: 2 Using this identification code, the accounting clerk whose name is printed on the dunning letters is determined.If this field is not filled, then the entry from the Accounting clerk field is used.
|
String |
getDunningLevel()
Constraints: Not nullable, Maximum length: 1 The business partner has received the dunning level from the last dunning run.If you use dunning areas, it is the dunning level that the business partner received from the last dunning run in the dunning area assigned.The dunning program sets the dunning level automatically when the customer or vendor receives a dunning notice.
|
String |
getDunningProcedure()
Constraints: Not nullable, Maximum length: 4
|
String |
getDunningRecipient()
Constraints: Not nullable, Maximum length: 10 The account number is only needed if dunning letters are not sent to the customer who owes the receivables.
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
Calendar |
getLastDunnedOn()
Constraints: Not nullable, Precision: 0
|
Calendar |
getLegDunningProcedureOn()
Constraints: Not nullable, Precision: 0 The printing of dunning notices in the legal dunning procedure generates an internal notice about any further account movements.
|
Class<CustomerDunning> |
getType() |
int |
hashCode() |
void |
setAuthorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setCompanyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setCustomer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setCustomerAccountGroup(String customerAccountGroup)
Constraints: Not nullable, Maximum length: 4 in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
|
void |
setDunningArea(String dunningArea)
(Key Field) Constraints: Not nullable, Maximum length: 2 If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items.
|
void |
setDunningBlock(String dunningBlock)
Constraints: Not nullable, Maximum length: 1
|
void |
setDunningClerk(String dunningClerk)
Constraints: Not nullable, Maximum length: 2 Using this identification code, the accounting clerk whose name is printed on the dunning letters is determined.If this field is not filled, then the entry from the Accounting clerk field is used.
|
void |
setDunningLevel(String dunningLevel)
Constraints: Not nullable, Maximum length: 1 The business partner has received the dunning level from the last dunning run.If you use dunning areas, it is the dunning level that the business partner received from the last dunning run in the dunning area assigned.The dunning program sets the dunning level automatically when the customer or vendor receives a dunning notice.
|
void |
setDunningProcedure(String dunningProcedure)
Constraints: Not nullable, Maximum length: 4
|
void |
setDunningRecipient(String dunningRecipient)
Constraints: Not nullable, Maximum length: 10 The account number is only needed if dunning letters are not sent to the customer who owes the receivables.
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setLastDunnedOn(Calendar lastDunnedOn)
Constraints: Not nullable, Precision: 0
|
void |
setLegDunningProcedureOn(Calendar legDunningProcedureOn)
Constraints: Not nullable, Precision: 0 The printing of dunning notices in the legal dunning procedure generates an internal notice about any further account movements.
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomField
public static final CustomerDunningSelectable ALL_FIELDS
public static final CustomerDunningField<String> CUSTOMER
public static final CustomerDunningField<String> COMPANY_CODE
public static final CustomerDunningField<String> DUNNING_AREA
public static final CustomerDunningField<String> DUNNING_BLOCK
public static final CustomerDunningField<String> DUNNING_LEVEL
public static final CustomerDunningField<String> DUNNING_PROCEDURE
public static final CustomerDunningField<String> DUNNING_RECIPIENT
public static final CustomerDunningField<Calendar> LAST_DUNNED_ON
public static final CustomerDunningField<Calendar> LEG_DUNNING_PROCEDURE_ON
public static final CustomerDunningField<String> DUNNING_CLERK
public static final CustomerDunningField<String> AUTHORIZATION_GROUP
public static final CustomerDunningField<String> CUSTOMER_ACCOUNT_GROUP
public CustomerDunning()
public CustomerDunning(@Nullable String customer, @Nullable String companyCode, @Nullable String dunningArea, @Nullable String dunningBlock, @Nullable String dunningLevel, @Nullable String dunningProcedure, @Nullable String dunningRecipient, @Nullable Calendar lastDunnedOn, @Nullable Calendar legDunningProcedureOn, @Nullable String dunningClerk, @Nullable String authorizationGroup, @Nullable String customerAccountGroup, @Nullable ErpConfigContext erpConfigContext)
public Class<CustomerDunning> getType()
getType
in class VdmObject<CustomerDunning>
public static <T> CustomerDunningField<T> field(String fieldName, Class<T> fieldType)
fieldName
- The name of the extension field as returned by the OData service.fieldType
- The Java type to use for the extension field when performing value comparisons.public static CustomerDunning.CustomerDunningBuilder builder()
@Nullable public String getCustomer()
@Nullable public String getCompanyCode()
@Nullable public String getDunningArea()
If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
@Nullable public String getDunningBlock()
@Nullable public String getDunningLevel()
The business partner has received the dunning level from the last dunning run.If you use dunning areas, it is the dunning level that the business partner received from the last dunning run in the dunning area assigned.The dunning program sets the dunning level automatically when the customer or vendor receives a dunning notice.
@Nullable public String getDunningProcedure()
@Nullable public String getDunningRecipient()
The account number is only needed if dunning letters are not sent to the customer who owes the receivables.
@Nullable public Calendar getLastDunnedOn()
@Nullable public Calendar getLegDunningProcedureOn()
The printing of dunning notices in the legal dunning procedure generates an internal notice about any further account movements. A dunning notice is not created for the customer.If the Legal dunning procedure field in the master record contains a date, this means that the account is involved in a legal dunning procedure. The relationship between this date and the dunning date does not affect how the account is processed.The printing of account movements in the legal dunning procedure differs from the normal printing of dunning notices as follows:You must specify a separate form for your dunning procedure in Customizing. For more information, see Customizing (IMG) under Dunning Forms.The dunning program also displays text element 520 "Legal dunning procedure". This makes it possible to display the date of the legal dunning procedure from the master record.The program also displays the documents blocked for dunning and those with a payment method (automatic debit, bank direct debit).Although dunning notices are printed, the dunning level does not change in the master record or in the items. New dunning level = old dunning level.The program only updates the date of the last dunning run.Enter the date manually.
@Nullable public String getDunningClerk()
Using this identification code, the accounting clerk whose name is printed on the dunning letters is determined.If this field is not filled, then the entry from the Accounting clerk field is used.
@Nullable public String getAuthorizationGroup()
@Nullable public String getCustomerAccountGroup()
in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
@Nullable public ErpConfigContext getErpConfigContext()
public void setCustomer(@Nullable String customer)
customer
- public void setCompanyCode(@Nullable String companyCode)
companyCode
- public void setDunningArea(@Nullable String dunningArea)
If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
dunningArea
- public void setDunningBlock(@Nullable String dunningBlock)
dunningBlock
- public void setDunningLevel(@Nullable String dunningLevel)
The business partner has received the dunning level from the last dunning run.If you use dunning areas, it is the dunning level that the business partner received from the last dunning run in the dunning area assigned.The dunning program sets the dunning level automatically when the customer or vendor receives a dunning notice.
dunningLevel
- public void setDunningProcedure(@Nullable String dunningProcedure)
dunningProcedure
- public void setDunningRecipient(@Nullable String dunningRecipient)
The account number is only needed if dunning letters are not sent to the customer who owes the receivables.
dunningRecipient
- public void setLastDunnedOn(@Nullable Calendar lastDunnedOn)
lastDunnedOn
- public void setLegDunningProcedureOn(@Nullable Calendar legDunningProcedureOn)
The printing of dunning notices in the legal dunning procedure generates an internal notice about any further account movements. A dunning notice is not created for the customer.If the Legal dunning procedure field in the master record contains a date, this means that the account is involved in a legal dunning procedure. The relationship between this date and the dunning date does not affect how the account is processed.The printing of account movements in the legal dunning procedure differs from the normal printing of dunning notices as follows:You must specify a separate form for your dunning procedure in Customizing. For more information, see Customizing (IMG) under Dunning Forms.The dunning program also displays text element 520 "Legal dunning procedure". This makes it possible to display the date of the legal dunning procedure from the master record.The program also displays the documents blocked for dunning and those with a payment method (automatic debit, bank direct debit).Although dunning notices are printed, the dunning level does not change in the master record or in the items. New dunning level = old dunning level.The program only updates the date of the last dunning run.Enter the date manually.
legDunningProcedureOn
- public void setDunningClerk(@Nullable String dunningClerk)
Using this identification code, the accounting clerk whose name is printed on the dunning letters is determined.If this field is not filled, then the entry from the Accounting clerk field is used.
dunningClerk
- public void setAuthorizationGroup(@Nullable String authorizationGroup)
authorizationGroup
- public void setCustomerAccountGroup(@Nullable String customerAccountGroup)
in which number range the customer account number should be;whether the number is assigned by the user or by the system;which specifications are necessary or possible in the master record.
customerAccountGroup
- public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext
- public String toString()
toString
in class VdmObject<CustomerDunning>
public boolean equals(Object o)
equals
in class VdmObject<CustomerDunning>
public int hashCode()
hashCode
in class VdmObject<CustomerDunning>
Copyright © 2018 SAP SE. All rights reserved.