public static class BusinessPartnerNamespace.CustomerDunning extends Object
Constructor and Description |
---|
BusinessPartnerNamespace.CustomerDunning() |
Modifier and Type | Method and Description |
---|---|
boolean |
equals(Object o) |
String |
getCompanyCode()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getCustomer()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getDunningArea()
(Key Field) Constraints: Not nullable, Maximum length: 2
|
String |
getDunningBlock()
Constraints: Not nullable, Maximum length: 1
|
String |
getDunningClerk()
Constraints: Not nullable, Maximum length: 2
|
String |
getDunningLevel()
Constraints: Not nullable, Maximum length: 1
|
String |
getDunningProcedure()
Constraints: Not nullable, Maximum length: 4
|
String |
getDunningRecipient()
Constraints: Not nullable, Maximum length: 10
|
Calendar |
getLastDunnedOn()
Constraints: Not nullable, Precision: 0
|
Calendar |
getLegDunningProcedureOn()
Constraints: Not nullable, Precision: 0
|
int |
hashCode() |
BusinessPartnerNamespace.CustomerDunning |
setCompanyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
BusinessPartnerNamespace.CustomerDunning |
setCustomer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
BusinessPartnerNamespace.CustomerDunning |
setDunningArea(String dunningArea)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
BusinessPartnerNamespace.CustomerDunning |
setDunningBlock(String dunningBlock)
Constraints: Not nullable, Maximum length: 1
|
BusinessPartnerNamespace.CustomerDunning |
setDunningClerk(String dunningClerk)
Constraints: Not nullable, Maximum length: 2
|
BusinessPartnerNamespace.CustomerDunning |
setDunningLevel(String dunningLevel)
Constraints: Not nullable, Maximum length: 1
|
BusinessPartnerNamespace.CustomerDunning |
setDunningProcedure(String dunningProcedure)
Constraints: Not nullable, Maximum length: 4
|
BusinessPartnerNamespace.CustomerDunning |
setDunningRecipient(String dunningRecipient)
Constraints: Not nullable, Maximum length: 10
|
BusinessPartnerNamespace.CustomerDunning |
setErpConfigContext(ErpConfigContext erpConfigContext) |
BusinessPartnerNamespace.CustomerDunning |
setLastDunnedOn(Calendar lastDunnedOn)
Constraints: Not nullable, Precision: 0
|
BusinessPartnerNamespace.CustomerDunning |
setLegDunningProcedureOn(Calendar legDunningProcedureOn)
Constraints: Not nullable, Precision: 0
|
String |
toString() |
public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> CUSTOMER
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the Customer field to query operations.public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> DUNNING_CLERK
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the DunningClerk field to query operations.public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> COMPANY_CODE
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the CompanyCode field to query operations.public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> DUNNING_AREA
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the DunningArea field to query operations.public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> DUNNING_BLOCK
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the DunningBlock field to query operations.public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> DUNNING_LEVEL
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the DunningLevel field to query operations.public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> DUNNING_PROCEDURE
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the DunningProcedure field to query operations.public static EntityField<String,BusinessPartnerNamespace.CustomerDunning> DUNNING_RECIPIENT
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the DunningRecipient field to query operations.public static EntityField<Calendar,BusinessPartnerNamespace.CustomerDunning> LAST_DUNNED_ON
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the LastDunnedOn field to query operations.public static EntityField<Calendar,BusinessPartnerNamespace.CustomerDunning> LEG_DUNNING_PROCEDURE_ON
CustomerDunningFluentHelper
and CustomerDunningByKeyFluentHelper
to apply the LegDunningProcedureOn field to query operations.@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning()
@Generated(value="lombok") public String toString()
@Generated(value="lombok") public boolean equals(Object o)
@Generated(value="lombok") public int hashCode()
@Generated(value="lombok") public String getCustomer()
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setCustomer(String customer)
customer
- @Generated(value="lombok") 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.
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setDunningClerk(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
- @Generated(value="lombok") public String getCompanyCode()
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setCompanyCode(String companyCode)
companyCode
- @Generated(value="lombok") public String getDunningArea()
If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas. All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures. The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setDunningArea(String dunningArea)
If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas. All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures. The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
dunningArea
- @Generated(value="lombok") public String getDunningBlock()
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setDunningBlock(String dunningBlock)
dunningBlock
- @Generated(value="lombok") 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.
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setDunningLevel(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
- @Generated(value="lombok") public String getDunningProcedure()
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setDunningProcedure(String dunningProcedure)
dunningProcedure
- @Generated(value="lombok") public String getDunningRecipient()
The account number is only needed if dunning letters are not sent to the customer who owes the receivables.
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setDunningRecipient(String dunningRecipient)
The account number is only needed if dunning letters are not sent to the customer who owes the receivables.
dunningRecipient
- @Generated(value="lombok") public Calendar getLastDunnedOn()
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setLastDunnedOn(Calendar lastDunnedOn)
lastDunnedOn
- @Generated(value="lombok") 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.
@Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setLegDunningProcedureOn(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
- @Generated(value="lombok") public BusinessPartnerNamespace.CustomerDunning setErpConfigContext(ErpConfigContext erpConfigContext)
Copyright © 2017 SAP SE. All rights reserved.