public static final class SupplierCompany.SupplierCompanyBuilder extends Object
Modifier and Type | Method and Description |
---|---|
SupplierCompany.SupplierCompanyBuilder |
accountingClerk(String accountingClerk)
Constraints: Not nullable, Maximum length: 2
|
SupplierCompany.SupplierCompanyBuilder |
accountingClerkFaxNumber(String accountingClerkFaxNumber)
Constraints: Not nullable, Maximum length: 31
|
SupplierCompany.SupplierCompanyBuilder |
accountingClerkPhoneNumber(String accountingClerkPhoneNumber)
Constraints: Not nullable, Maximum length: 30
|
SupplierCompany.SupplierCompanyBuilder |
alternativePayee(String alternativePayee)
Constraints: Not nullable, Maximum length: 10
|
SupplierCompany.SupplierCompanyBuilder |
aPARToleranceGroup(String aPARToleranceGroup)
Constraints: Not nullable, Maximum length: 4
|
SupplierCompany.SupplierCompanyBuilder |
authorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
SupplierCompany.SupplierCompanyBuilder |
billOfExchLmtAmtInCoCodeCrcy(BigDecimal billOfExchLmtAmtInCoCodeCrcy)
Constraints: Not nullable, Precision: 14, Scale: 3
|
SupplierCompany |
build() |
SupplierCompany.SupplierCompanyBuilder |
cashPlanningGroup(String cashPlanningGroup)
Constraints: Not nullable, Maximum length: 10
|
SupplierCompany.SupplierCompanyBuilder |
checkPaidDurationInDays(BigDecimal checkPaidDurationInDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
SupplierCompany.SupplierCompanyBuilder |
clearCustomerSupplier(Boolean clearCustomerSupplier)
Constraints: none
|
SupplierCompany.SupplierCompanyBuilder |
companyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
SupplierCompany.SupplierCompanyBuilder |
companyCodeName(String companyCodeName)
Constraints: Not nullable, Maximum length: 25
|
SupplierCompany.SupplierCompanyBuilder |
deletionIndicator(Boolean deletionIndicator)
Constraints: none
|
SupplierCompany.SupplierCompanyBuilder |
houseBank(String houseBank)
Constraints: Not nullable, Maximum length: 5
|
SupplierCompany.SupplierCompanyBuilder |
interestCalculationCode(String interestCalculationCode)
Constraints: Not nullable, Maximum length: 2
|
SupplierCompany.SupplierCompanyBuilder |
interestCalculationDate(LocalDateTime interestCalculationDate)
Constraints: Not nullable, Precision: 0
|
SupplierCompany.SupplierCompanyBuilder |
intrstCalcFrequencyInMonths(String intrstCalcFrequencyInMonths)
Constraints: Not nullable, Maximum length: 2
|
SupplierCompany.SupplierCompanyBuilder |
isToBeCheckedForDuplicates(Boolean isToBeCheckedForDuplicates)
Constraints: none
|
SupplierCompany.SupplierCompanyBuilder |
isToBeLocallyProcessed(Boolean isToBeLocallyProcessed)
Constraints: none
|
SupplierCompany.SupplierCompanyBuilder |
itemIsToBePaidSeparately(Boolean itemIsToBePaidSeparately)
Constraints: none
|
SupplierCompany.SupplierCompanyBuilder |
layoutSortingRule(String layoutSortingRule)
Constraints: Not nullable, Maximum length: 3
|
SupplierCompany.SupplierCompanyBuilder |
paymentBlockingReason(String paymentBlockingReason)
Constraints: Not nullable, Maximum length: 1
|
SupplierCompany.SupplierCompanyBuilder |
paymentIsToBeSentByEDI(Boolean paymentIsToBeSentByEDI)
Constraints: none
|
SupplierCompany.SupplierCompanyBuilder |
paymentMethodsList(String paymentMethodsList)
Constraints: Not nullable, Maximum length: 10
|
SupplierCompany.SupplierCompanyBuilder |
paymentTerms(String paymentTerms)
Constraints: Not nullable, Maximum length: 4
|
SupplierCompany.SupplierCompanyBuilder |
reconciliationAccount(String reconciliationAccount)
Constraints: Not nullable, Maximum length: 10
|
SupplierCompany.SupplierCompanyBuilder |
supplier(String supplier)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
SupplierCompany.SupplierCompanyBuilder |
supplierAccountGroup(String supplierAccountGroup)
Constraints: Not nullable, Maximum length: 4
|
SupplierCompany.SupplierCompanyBuilder |
supplierAccountNote(String supplierAccountNote)
Constraints: Not nullable, Maximum length: 30
|
SupplierCompany.SupplierCompanyBuilder |
supplierCertificationDate(LocalDateTime supplierCertificationDate)
Constraints: Not nullable, Precision: 0
|
SupplierCompany.SupplierCompanyBuilder |
supplierClerk(String supplierClerk)
Constraints: Not nullable, Maximum length: 15
|
SupplierCompany.SupplierCompanyBuilder |
supplierClerkIDBySupplier(String supplierClerkIDBySupplier)
Constraints: Not nullable, Maximum length: 12
|
SupplierCompany.SupplierCompanyBuilder |
supplierClerkURL(String supplierClerkURL)
Constraints: Not nullable, Maximum length: 130
|
SupplierCompany.SupplierCompanyBuilder |
supplierDunning(SupplierDunning... value)
Navigation property to_SupplierDunning for SupplierCompany to multiple SupplierDunning.
|
SupplierCompany.SupplierCompanyBuilder |
supplierHeadOffice(String supplierHeadOffice)
Constraints: Not nullable, Maximum length: 10
|
SupplierCompany.SupplierCompanyBuilder |
supplierIsBlockedForPosting(Boolean supplierIsBlockedForPosting)
Constraints: none
|
SupplierCompany.SupplierCompanyBuilder |
supplierWithHoldingTax(SupplierWithHoldingTax... value)
Navigation property to_SupplierWithHoldingTax for SupplierCompany to multiple
SupplierWithHoldingTax.
|
String |
toString() |
SupplierCompany.SupplierCompanyBuilder |
withholdingTaxCountry(String withholdingTaxCountry)
Constraints: Not nullable, Maximum length: 3
|
@Nonnull public SupplierCompany.SupplierCompanyBuilder supplierDunning(SupplierDunning... value)
value
- The SupplierDunnings to build this SupplierCompany with.@Nonnull public SupplierCompany.SupplierCompanyBuilder supplierWithHoldingTax(SupplierWithHoldingTax... value)
value
- The SupplierWithHoldingTaxs to build this SupplierCompany with.public SupplierCompany.SupplierCompanyBuilder supplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
public SupplierCompany.SupplierCompanyBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public SupplierCompany.SupplierCompanyBuilder 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 SupplierCompany.SupplierCompanyBuilder companyCodeName(@Nullable String companyCodeName)
Original property name from the Odata EDM: CompanyCodeName
public SupplierCompany.SupplierCompanyBuilder paymentBlockingReason(@Nullable String paymentBlockingReason)
Original property name from the Odata EDM: PaymentBlockingReason
You can use the block key as described below.Automatic Payment TransactionsIn automatic payment transactions, the block takes effect when it is entered in the system as follows:In the master recordIn the documentIf you enter the block in the master record then all open items for this account are contained in the exception list.The following block keys have a special meaning in the master record:The block key * has the effect that all items of the account are skipped in automatic payment transactions.The block key + has the effect that all items are skipped in which a payment method was not entered explicitly.The block key A is always set automatically when a down payment is entered. Therefore, you must not delete the block key A or use it for other purposes.Whether a block key can be set or removed in payment proposal processing depends on the attribute Changeable in payment proposal of the block key.Manual PaymentsManual payments are only affected by a block key in the document if you set the attribute Blocked for manual payments in the block key.A block key that was set in the master record does not have any effect on manual payments. You can have the system issue a warning message in that case. To do so, you have to make system settings. Set up message 671 of work area F5 in message control accordingly.
public SupplierCompany.SupplierCompanyBuilder supplierIsBlockedForPosting(@Nullable Boolean supplierIsBlockedForPosting)
Original property name from the Odata EDM: SupplierIsBlockedForPosting
If you set this indicator, the system prevents users from posting items to this account and issues an error message to inform them that the account is blocked.
public SupplierCompany.SupplierCompanyBuilder accountingClerk(@Nullable String accountingClerk)
Original property name from the Odata EDM: AccountingClerk
The name of the accounting clerk defined by this identification code can be used in the payment program for correspondence and reporting (for example, open item lists).
public SupplierCompany.SupplierCompanyBuilder accountingClerkFaxNumber(@Nullable String accountingClerkFaxNumber)
Original property name from the Odata EDM: AccountingClerkFaxNumber
public SupplierCompany.SupplierCompanyBuilder accountingClerkPhoneNumber(@Nullable String accountingClerkPhoneNumber)
Original property name from the Odata EDM: AccountingClerkPhoneNumber
public SupplierCompany.SupplierCompanyBuilder supplierClerk(@Nullable String supplierClerk)
Original property name from the Odata EDM: SupplierClerk
public SupplierCompany.SupplierCompanyBuilder supplierClerkURL(@Nullable String supplierClerkURL)
Original property name from the Odata EDM: SupplierClerkURL
public SupplierCompany.SupplierCompanyBuilder paymentMethodsList(@Nullable String paymentMethodsList)
Original property name from the Odata EDM: PaymentMethodsList
If you do specify a particular payment method in the item to be paid, this specification has priority over the specifications in the master record. You may also specify payment methods in the item which are not listed in the master record.
you do not specify a payment method in the item to be paid.public SupplierCompany.SupplierCompanyBuilder paymentTerms(@Nullable String paymentTerms)
Original property name from the Odata EDM: PaymentTerms
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.
public SupplierCompany.SupplierCompanyBuilder clearCustomerSupplier(@Nullable Boolean clearCustomerSupplier)
Original property name from the Odata EDM: ClearCustomerSupplier
To use this function in automatic payment transactions, you have toenter the customer account number in the vendor master record,enter the vendor account number in the customer master record, andselect the "Clearing with vendor" indicator in the customer master record.If this indicator is set, items belonging to the customer account will be included in any dunning run.
account, and that during manual clearing procedures, the items of that customer account are also selected.public SupplierCompany.SupplierCompanyBuilder isToBeLocallyProcessed(@Nullable Boolean isToBeLocallyProcessed)
Original property name from the Odata EDM: IsToBeLocallyProcessed
Normally automatic payment transactions and dunning notices are created for the head office.NoteSelect this indicator only if this account is a head office account.
public SupplierCompany.SupplierCompanyBuilder itemIsToBePaidSeparately(@Nullable Boolean itemIsToBePaidSeparately)
Original property name from the Odata EDM: ItemIsToBePaidSeparately
transactions. This means that open items are not grouped together for payment.public SupplierCompany.SupplierCompanyBuilder paymentIsToBeSentByEDI(@Nullable Boolean paymentIsToBeSentByEDI)
Original property name from the Odata EDM: PaymentIsToBeSentByEDI
public SupplierCompany.SupplierCompanyBuilder houseBank(@Nullable String houseBank)
Original property name from the Odata EDM: HouseBank
public SupplierCompany.SupplierCompanyBuilder checkPaidDurationInDays(@Nullable BigDecimal checkPaidDurationInDays)
Original property name from the Odata EDM: CheckPaidDurationInDays
During automatic payment transactions, the system calculates the value date for check payments using this information and stores the date in the line item. The date is calculated as follows:Value date = posting date + check cashing timeIn Cash Management, the value date is used as information about the expected cash outflow.
public SupplierCompany.SupplierCompanyBuilder billOfExchLmtAmtInCoCodeCrcy(@Nullable BigDecimal billOfExchLmtAmtInCoCodeCrcy)
Original property name from the Odata EDM: BillOfExchLmtAmtInCoCodeCrcy
The amount limit is taken into consideration in automatic payment transactions for payments by bill of exchange and bill of exchange payment requests. Several bill of exchange forms are created if the amount to be settled is higher than the maximum amount given here. Each of these bills of exchange is issued for the maximum amount or for a smaller amount.Amount limits for bills of exchange are used in Spain, for example.
the business partner.public SupplierCompany.SupplierCompanyBuilder supplierClerkIDBySupplier(@Nullable String supplierClerkIDBySupplier)
Original property name from the Odata EDM: SupplierClerkIDBySupplier
public SupplierCompany.SupplierCompanyBuilder reconciliationAccount(@Nullable String reconciliationAccount)
Original property name from the Odata EDM: ReconciliationAccount
For special postings (for example, down payment or bill of exchange), this account is replaced by another account (for example, 'down payments received' instead of 'receivables').The replacement takes place due to the special G/L indicator which you must specify for these types of postings.
account for normal postings (for example, invoice or payment).public SupplierCompany.SupplierCompanyBuilder interestCalculationCode(@Nullable String interestCalculationCode)
Original property name from the Odata EDM: InterestCalculationCode
calculation.public SupplierCompany.SupplierCompanyBuilder interestCalculationDate(@Nullable LocalDateTime interestCalculationDate)
Original property name from the Odata EDM: InterestCalculationDate
Generally, this date is automatically maintained by the program (batch input). A manual entry in this field should only be made if an error has occurred or when implementing the interest calculation.
This is generally the upper limit of the last interest run.public SupplierCompany.SupplierCompanyBuilder intrstCalcFrequencyInMonths(@Nullable String intrstCalcFrequencyInMonths)
Original property name from the Odata EDM: IntrstCalcFrequencyInMonths
Date of last interest calculation: 3/31.+ 01 month interest calculation frequency= 4/30 upper limit for the current interest runThe calculation period specified as a report parameter determines whether an account is included in an interest run.The upper limit of the interest run is calculated as in the above example and compared with the upper limit of the calculation entered in the interest run (report parameter). If the calculated upper limit is after the calculation period, the account is not included in interest calculation.If you maintain the interest calculation frequency in the account master record, this entry is used to calculate the upper limit. If not, the interest calculation frequency entered for the interest indicator is used.
automatically for this account (account balance interest calculation). The interest calculation frequency is added to the date of the last interest calculation.public SupplierCompany.SupplierCompanyBuilder supplierHeadOffice(@Nullable String supplierHeadOffice)
Original property name from the Odata EDM: SupplierHeadOffice
You specify this account number only for branch accounts. Items that you post using the branch account number are automatically posted to the head office account. The system records the branch account number in the line items.Neither transactions nor balances are kept in the branch account.
public SupplierCompany.SupplierCompanyBuilder alternativePayee(@Nullable String alternativePayee)
Original property name from the Odata EDM: AlternativePayee
The field is only needed if payments are not to be made directly to the vendor to whom the payable is owed. The same applies to bank collections of receivables.The specification in this field applies only to the company code. There is a further field in which you can enter an alternative payee for each company code. If both fields are filled, the company code specified has priority.
public SupplierCompany.SupplierCompanyBuilder layoutSortingRule(@Nullable String layoutSortingRule)
Original property name from the Odata EDM: LayoutSortingRule
The system uses a standard sort sequence for displaying line items. Among other things, it sorts the items according to the content of the Allocation field. This field can be filled either manually or automatically (by the system) when a document line item is entered.For this purpose, the system requires rules that determine which information is to be taken from the document header or from the document line item and placed in the field. The rules can be stored in the master record of an account which enables you to determine the standard sort sequence on an account-specific basis.NoteField information from another document line item cannot be adopted into the field of a particular item.
public SupplierCompany.SupplierCompanyBuilder aPARToleranceGroup(@Nullable String aPARToleranceGroup)
Original property name from the Odata EDM: APARToleranceGroup
Each tolerance group contains settings that affect cash discount and payment difference processing. These settings become effective during payment entry.
within a company code.public SupplierCompany.SupplierCompanyBuilder supplierCertificationDate(@Nullable LocalDateTime supplierCertificationDate)
Original property name from the Odata EDM: SupplierCertificationDate
Date field in which to enter certification date for small companies run by women or minorities. This certificate must be renewed every two years.
public SupplierCompany.SupplierCompanyBuilder supplierAccountNote(@Nullable String supplierAccountNote)
Original property name from the Odata EDM: SupplierAccountNote
The memo serves only as information on special features of the customer/vendor.
public SupplierCompany.SupplierCompanyBuilder withholdingTaxCountry(@Nullable String withholdingTaxCountry)
Original property name from the Odata EDM: WithholdingTaxCountry
The calculation can depend on the payee's country.A particular country key can be required by law for reporting which may possibly be different to the key used in the address.Examples: Japan, USA (1042), Argentina
public SupplierCompany.SupplierCompanyBuilder deletionIndicator(@Nullable Boolean deletionIndicator)
Original property name from the Odata EDM: DeletionIndicator
To delete this data, you have to run the archiving program for Accounts Receivable or Payable. This program will archive all master records marked for deletion provided that there is no dependent data in them.This deletion flag cannot be used in the program that deletes master data. You should, however, run this program only to delete test data prior to production startup.
public SupplierCompany.SupplierCompanyBuilder cashPlanningGroup(@Nullable String cashPlanningGroup)
Original property name from the Odata EDM: CashPlanningGroup
You can define these planning groups in Customizing or the Implementation Guide (you will need to ensure that they are all the same length). In order to improve the liquidity forecast display for major customers and vendors, it can be advisable to enter their account number as the planning group.For the planning groups themselves a naming convention should be set up to improve liquidity forecasting. In the following examples, the customer planning groups begin with an "R" for receipts, and the vendor planning groups begin with an "E" for expenses.R1 Customers paying by bank collectionR2 Other domestic customersR3 Customers abroadR4 Affiliated company customersR5 High risk customersR6 Major customersR7 Rental incomeR8 Repayment of loans...E1 Domestic vendorsE2 Vendors abroadE3 Affiliated company vendorsE4 Major vendorsE5 Personnel costsE6 TaxesE7 Investments...
the master record.public SupplierCompany.SupplierCompanyBuilder isToBeCheckedForDuplicates(@Nullable Boolean isToBeCheckedForDuplicates)
Original property name from the Odata EDM: IsToBeCheckedForDuplicates
Checking Logistics DocumentsThe system checks whether the invoice documents have already been entered in the Logistics invoice verification. For this, the system checks invoices that have been held or parked or that contain errors, or invoices that were entered for invoice verification in the background. The check is performed only if you specify the reference document number when you enter the invoices.When checking for duplicate invoices, the system compares the following specified characteristics:VendorCurrencyCompany CodeGross Invoice AmountReference Document NumberInvoice Document DateIf all of these characteristics are the same, the system issues a message for which you can change the message type in Customizing.When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.Exception: The exception is the Argentina country version, where the system checks for duplicate invoices and credit memos.No message is issued if you enter a document that has previously been reversed.In Customizing for Logistics Invoice Verification under Incoming Invoice -> Set Check for Duplicate Invoices, you can specify that the following characteristics are not checked:Reference Document NumberInvoice Document DateCompany CodeHaving fewer attributes to check increases the likelihood that the system will find a duplicate invoice.Example:The following document has already been entered and posted:Reference Document Number 333Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: ChicagoYou have set up the check for duplicate invoices as follows in Customizing:The characteristics Reference Document Number and Company Code are not activated. Consequently, these characteristics are not checked.Now you enter the following invoice:Reference Document Number 334Invoice Date: 4/28/2000Gross Invoice Amount 100.00Currency: EURVendor: SpencerCompany Code: FlagstaffResultBecause you entered a reference document when you entered the invoice, the system checks for duplicate invoices. Compared against the invoice entered earlier, the invoice just entered has different values in the characteristics Reference and Company Code. However, these characteristics are not checked due to the settings that you have made in Customizing. All other characteristics are the same. The system issues a message telling you that an invoice has been entered twice.If the characteristic "Reference Document Number" had been selected in Customizing, the system would have checked the reference document number and established that it was different from the invoice entered earlier, and it consequently would not have issued a message.Checking FI DocumentsThe system checks whether there are FI documents that were posted or parked with the Logistics invoice verification or with an FI invoice transaction. Depending on the entry in the Reference field, one of the following checks is performed:If a reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateReference NumberIf no reference number was specified in the sequential invoice/credit memo, the system checks whether an invoice/credit memo has already been posted for which all the following attributes agree:Company CodeVendorCurrencyDocument DateAmount in Document CurrencyIn Materials Management, the system applies the check for duplicate invoices for invoices only, not for credit memos.
checks whether an invoice or credit memo has already been entered for the same date.public SupplierCompany.SupplierCompanyBuilder supplierAccountGroup(@Nullable String supplierAccountGroup)
Original property name from the Odata EDM: SupplierAccountGroup
the number interval for the account number of the vendor,whether the number is assigned by the user or by the system,which specifications are necessary and/or possible in the master record.
public SupplierCompany build()
Copyright © 2019 SAP SE. All rights reserved.