public static class CustomerDunning.CustomerDunningBuilder extends Object
Modifier and Type | Method and Description |
---|---|
CustomerDunning.CustomerDunningBuilder |
authorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
CustomerDunning |
build() |
CustomerDunning.CustomerDunningBuilder |
companyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
CustomerDunning.CustomerDunningBuilder |
customer(String customer)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
CustomerDunning.CustomerDunningBuilder |
customerAccountGroup(String customerAccountGroup)
Constraints: Not nullable, Maximum length: 4
|
CustomerDunning.CustomerDunningBuilder |
dunningArea(String dunningArea)
(Key Field) Constraints: Not nullable, Maximum length: 2
|
CustomerDunning.CustomerDunningBuilder |
dunningBlock(String dunningBlock)
Constraints: Not nullable, Maximum length: 1
|
CustomerDunning.CustomerDunningBuilder |
dunningClerk(String dunningClerk)
Constraints: Not nullable, Maximum length: 2
|
CustomerDunning.CustomerDunningBuilder |
dunningLevel(String dunningLevel)
Constraints: Not nullable, Maximum length: 1
|
CustomerDunning.CustomerDunningBuilder |
dunningProcedure(String dunningProcedure)
Constraints: Not nullable, Maximum length: 4
|
CustomerDunning.CustomerDunningBuilder |
dunningRecipient(String dunningRecipient)
Constraints: Not nullable, Maximum length: 10
|
CustomerDunning.CustomerDunningBuilder |
lastDunnedOn(LocalDateTime lastDunnedOn)
Constraints: Not nullable, Precision: 0
|
CustomerDunning.CustomerDunningBuilder |
legDunningProcedureOn(LocalDateTime legDunningProcedureOn)
Constraints: Not nullable, Precision: 0
|
String |
toString() |
public CustomerDunning.CustomerDunningBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public CustomerDunning.CustomerDunningBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public CustomerDunning.CustomerDunningBuilder dunningArea(@Nullable String dunningArea)
Original property name from the Odata EDM: 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.
represent a sub-structure of the company codes.public CustomerDunning.CustomerDunningBuilder dunningBlock(@Nullable String dunningBlock)
Original property name from the Odata EDM: DunningBlock
public CustomerDunning.CustomerDunningBuilder dunningLevel(@Nullable String dunningLevel)
Original property name from the Odata EDM: 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.
public CustomerDunning.CustomerDunningBuilder dunningProcedure(@Nullable String dunningProcedure)
Original property name from the Odata EDM: DunningProcedure
public CustomerDunning.CustomerDunningBuilder dunningRecipient(@Nullable String dunningRecipient)
Original property name from the Odata EDM: DunningRecipient
The account number is only needed if dunning letters are not sent to the customer who owes the receivables.
public CustomerDunning.CustomerDunningBuilder lastDunnedOn(@Nullable LocalDateTime lastDunnedOn)
Original property name from the Odata EDM: LastDunnedOn
public CustomerDunning.CustomerDunningBuilder legDunningProcedureOn(@Nullable LocalDateTime legDunningProcedureOn)
Original property name from the Odata EDM: 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.
public CustomerDunning.CustomerDunningBuilder dunningClerk(@Nullable String dunningClerk)
Original property name from the Odata EDM: 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.
public CustomerDunning.CustomerDunningBuilder authorizationGroup(@Nullable String authorizationGroup)
Original property name from the Odata EDM: AuthorizationGroup
authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity.public CustomerDunning.CustomerDunningBuilder customerAccountGroup(@Nullable String customerAccountGroup)
Original property name from the Odata EDM: 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.
public CustomerDunning build()
Copyright © 2019 SAP SE. All rights reserved.