public class SupplierCompany extends VdmEntity<SupplierCompany>
| Modifier and Type | Class and Description |
|---|---|
static class |
SupplierCompany.SupplierCompanyBuilder |
| Modifier and Type | Field and Description |
|---|---|
static SupplierCompanyField<String> |
ACCOUNTING_CLERK
Use with available fluent helpers to apply the AccountingClerk field to query operations.
|
static SupplierCompanyField<String> |
ACCOUNTING_CLERK_FAX_NUMBER
Use with available fluent helpers to apply the AccountingClerkFaxNumber field to query operations.
|
static SupplierCompanyField<String> |
ACCOUNTING_CLERK_PHONE_NUMBER
Use with available fluent helpers to apply the AccountingClerkPhoneNumber field to query operations.
|
static SupplierCompanySelectable |
ALL_FIELDS
Selector for all available fields of SupplierCompany.
|
static SupplierCompanyField<String> |
ALTERNATIVE_PAYEE
Use with available fluent helpers to apply the AlternativePayee field to query operations.
|
static SupplierCompanyField<String> |
APAR_TOLERANCE_GROUP
Use with available fluent helpers to apply the APARToleranceGroup field to query operations.
|
static SupplierCompanyField<String> |
AUTHORIZATION_GROUP
Use with available fluent helpers to apply the AuthorizationGroup field to query operations.
|
static SupplierCompanyField<BigDecimal> |
BILL_OF_EXCH_LMT_AMT_IN_CO_CODE_CRCY
Use with available fluent helpers to apply the BillOfExchLmtAmtInCoCodeCrcy field to query operations.
|
static SupplierCompanyField<String> |
CASH_PLANNING_GROUP
Use with available fluent helpers to apply the CashPlanningGroup field to query operations.
|
static SupplierCompanyField<BigDecimal> |
CHECK_PAID_DURATION_IN_DAYS
Use with available fluent helpers to apply the CheckPaidDurationInDays field to query operations.
|
static SupplierCompanyField<Boolean> |
CLEAR_CUSTOMER_SUPPLIER
Use with available fluent helpers to apply the ClearCustomerSupplier field to query operations.
|
static SupplierCompanyField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static SupplierCompanyField<String> |
COMPANY_CODE_NAME
Use with available fluent helpers to apply the CompanyCodeName field to query operations.
|
static SupplierCompanyField<Boolean> |
DELETION_INDICATOR
Use with available fluent helpers to apply the DeletionIndicator field to query operations.
|
static SupplierCompanyField<String> |
HOUSE_BANK
Use with available fluent helpers to apply the HouseBank field to query operations.
|
static SupplierCompanyField<String> |
INTEREST_CALCULATION_CODE
Use with available fluent helpers to apply the InterestCalculationCode field to query operations.
|
static SupplierCompanyField<Calendar> |
INTEREST_CALCULATION_DATE
Use with available fluent helpers to apply the InterestCalculationDate field to query operations.
|
static SupplierCompanyField<String> |
INTRST_CALC_FREQUENCY_IN_MONTHS
Use with available fluent helpers to apply the IntrstCalcFrequencyInMonths field to query operations.
|
static SupplierCompanyField<String> |
IS_BUSINESS_PURPOSE_COMPLETED
Use with available fluent helpers to apply the IsBusinessPurposeCompleted field to query operations.
|
static SupplierCompanyField<Boolean> |
IS_TO_BE_CHECKED_FOR_DUPLICATES
Use with available fluent helpers to apply the IsToBeCheckedForDuplicates field to query operations.
|
static SupplierCompanyField<Boolean> |
IS_TO_BE_LOCALLY_PROCESSED
Use with available fluent helpers to apply the IsToBeLocallyProcessed field to query operations.
|
static SupplierCompanyField<Boolean> |
ITEM_IS_TO_BE_PAID_SEPARATELY
Use with available fluent helpers to apply the ItemIsToBePaidSeparately field to query operations.
|
static SupplierCompanyField<String> |
LAYOUT_SORTING_RULE
Use with available fluent helpers to apply the LayoutSortingRule field to query operations.
|
static SupplierCompanyField<String> |
PAYMENT_BLOCKING_REASON
Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
|
static SupplierCompanyField<Boolean> |
PAYMENT_IS_TO_BE_SENT_BY_EDI
Use with available fluent helpers to apply the PaymentIsToBeSentByEDI field to query operations.
|
static SupplierCompanyField<String> |
PAYMENT_METHODS_LIST
Use with available fluent helpers to apply the PaymentMethodsList field to query operations.
|
static SupplierCompanyField<String> |
PAYMENT_TERMS
Use with available fluent helpers to apply the PaymentTerms field to query operations.
|
static SupplierCompanyField<String> |
RECONCILIATION_ACCOUNT
Use with available fluent helpers to apply the ReconciliationAccount field to query operations.
|
static SupplierCompanyField<String> |
SUPPLIER
Use with available fluent helpers to apply the Supplier field to query operations.
|
static SupplierCompanyField<String> |
SUPPLIER_ACCOUNT_GROUP
Use with available fluent helpers to apply the SupplierAccountGroup field to query operations.
|
static SupplierCompanyField<String> |
SUPPLIER_ACCOUNT_NOTE
Use with available fluent helpers to apply the SupplierAccountNote field to query operations.
|
static SupplierCompanyField<Calendar> |
SUPPLIER_CERTIFICATION_DATE
Use with available fluent helpers to apply the SupplierCertificationDate field to query operations.
|
static SupplierCompanyField<String> |
SUPPLIER_CLERK
Use with available fluent helpers to apply the SupplierClerk field to query operations.
|
static SupplierCompanyField<String> |
SUPPLIER_CLERK_ID_BY_SUPPLIER
Use with available fluent helpers to apply the SupplierClerkIDBySupplier field to query operations.
|
static SupplierCompanyField<String> |
SUPPLIER_CLERK_URL
Use with available fluent helpers to apply the SupplierClerkURL field to query operations.
|
static SupplierCompanyField<String> |
SUPPLIER_HEAD_OFFICE
Use with available fluent helpers to apply the SupplierHeadOffice field to query operations.
|
static SupplierCompanyField<Boolean> |
SUPPLIER_IS_BLOCKED_FOR_POSTING
Use with available fluent helpers to apply the SupplierIsBlockedForPosting field to query operations.
|
static SupplierCompanyLink<SupplierDunning> |
TO_SUPPLIER_DUNNING
Use with available fluent helpers to apply the to_SupplierDunning navigation property to query operations.
|
static SupplierCompanyLink<SupplierWithHoldingTax> |
TO_SUPPLIER_WITH_HOLDING_TAX
Use with available fluent helpers to apply the to_SupplierWithHoldingTax navigation property to query operations.
|
static SupplierCompanyField<String> |
WITHHOLDING_TAX_COUNTRY
Use with available fluent helpers to apply the WithholdingTaxCountry field to query operations.
|
| Constructor and Description |
|---|
SupplierCompany() |
SupplierCompany(String supplier,
String companyCode,
String authorizationGroup,
String companyCodeName,
String paymentBlockingReason,
Boolean supplierIsBlockedForPosting,
String accountingClerk,
String accountingClerkFaxNumber,
String accountingClerkPhoneNumber,
String supplierClerk,
String supplierClerkURL,
String paymentMethodsList,
String paymentTerms,
Boolean clearCustomerSupplier,
Boolean isToBeLocallyProcessed,
Boolean itemIsToBePaidSeparately,
Boolean paymentIsToBeSentByEDI,
String houseBank,
BigDecimal checkPaidDurationInDays,
BigDecimal billOfExchLmtAmtInCoCodeCrcy,
String supplierClerkIDBySupplier,
String reconciliationAccount,
String interestCalculationCode,
Calendar interestCalculationDate,
String intrstCalcFrequencyInMonths,
String supplierHeadOffice,
String alternativePayee,
String layoutSortingRule,
String aPARToleranceGroup,
Calendar supplierCertificationDate,
String supplierAccountNote,
String withholdingTaxCountry,
Boolean deletionIndicator,
String cashPlanningGroup,
Boolean isToBeCheckedForDuplicates,
String supplierAccountGroup,
String isBusinessPurposeCompleted,
ErpConfigContext erpConfigContext,
List<SupplierDunning> toSupplierDunning,
List<SupplierWithHoldingTax> toSupplierWithHoldingTax) |
| Modifier and Type | Method and Description |
|---|---|
void |
addSupplierDunning(SupplierDunning... entity)
Adds elements to the list of associated SupplierDunning entities.
|
void |
addSupplierWithHoldingTax(SupplierWithHoldingTax... entity)
Adds elements to the list of associated SupplierWithHoldingTax entities.
|
static SupplierCompany.SupplierCompanyBuilder |
builder() |
boolean |
equals(Object o) |
List<SupplierDunning> |
fetchSupplierDunning()
Fetches the SupplierDunning entities (one to many) associated with this entity.
|
List<SupplierWithHoldingTax> |
fetchSupplierWithHoldingTax()
Fetches the SupplierWithHoldingTax entities (one to many) associated with this entity.
|
static <T> SupplierCompanyField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
String |
getAccountingClerk()
Constraints: Not nullable, Maximum length: 2
|
String |
getAccountingClerkFaxNumber()
Constraints: Not nullable, Maximum length: 31
|
String |
getAccountingClerkPhoneNumber()
Constraints: Not nullable, Maximum length: 30
|
String |
getAlternativePayee()
Constraints: Not nullable, Maximum length: 10
|
String |
getAPARToleranceGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getAuthorizationGroup()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getBillOfExchLmtAmtInCoCodeCrcy()
Constraints: Not nullable, Precision: 14, Scale: 3
|
String |
getCashPlanningGroup()
Constraints: Not nullable, Maximum length: 10
|
BigDecimal |
getCheckPaidDurationInDays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
Boolean |
getClearCustomerSupplier()
Constraints: none
|
String |
getCompanyCode()
(Key Field) Constraints: Not nullable, Maximum length: 4
|
String |
getCompanyCodeName()
Constraints: Not nullable, Maximum length: 25
|
Boolean |
getDeletionIndicator()
Constraints: none
|
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
String |
getHouseBank()
Constraints: Not nullable, Maximum length: 5
|
String |
getInterestCalculationCode()
Constraints: Not nullable, Maximum length: 2
|
Calendar |
getInterestCalculationDate()
Constraints: Not nullable, Precision: 0
|
String |
getIntrstCalcFrequencyInMonths()
Constraints: Not nullable, Maximum length: 2
|
String |
getIsBusinessPurposeCompleted()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getIsToBeCheckedForDuplicates()
Constraints: none
|
Boolean |
getIsToBeLocallyProcessed()
Constraints: none
|
Boolean |
getItemIsToBePaidSeparately()
Constraints: none
|
String |
getLayoutSortingRule()
Constraints: Not nullable, Maximum length: 3
|
String |
getPaymentBlockingReason()
Constraints: Not nullable, Maximum length: 1
|
Boolean |
getPaymentIsToBeSentByEDI()
Constraints: none
|
String |
getPaymentMethodsList()
Constraints: Not nullable, Maximum length: 10
|
String |
getPaymentTerms()
Constraints: Not nullable, Maximum length: 4
|
String |
getReconciliationAccount()
Constraints: Not nullable, Maximum length: 10
|
String |
getSupplier()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getSupplierAccountGroup()
Constraints: Not nullable, Maximum length: 4
|
String |
getSupplierAccountNote()
Constraints: Not nullable, Maximum length: 30
|
Calendar |
getSupplierCertificationDate()
Constraints: Not nullable, Precision: 0
|
String |
getSupplierClerk()
Constraints: Not nullable, Maximum length: 15
|
String |
getSupplierClerkIDBySupplier()
Constraints: Not nullable, Maximum length: 12
|
String |
getSupplierClerkURL()
Constraints: Not nullable, Maximum length: 130
|
List<SupplierDunning> |
getSupplierDunningOrFetch()
Retrieval of associated SupplierDunning entities (one to many).
|
com.google.common.base.Optional<List<SupplierDunning>> |
getSupplierDunningOrNull()
Retrieval of associated SupplierDunning entities (one to many).
|
String |
getSupplierHeadOffice()
Constraints: Not nullable, Maximum length: 10
|
Boolean |
getSupplierIsBlockedForPosting()
Constraints: none
|
List<SupplierWithHoldingTax> |
getSupplierWithHoldingTaxOrFetch()
Retrieval of associated SupplierWithHoldingTax entities (one to many).
|
com.google.common.base.Optional<List<SupplierWithHoldingTax>> |
getSupplierWithHoldingTaxOrNull()
Retrieval of associated SupplierWithHoldingTax entities (one to many).
|
Class<SupplierCompany> |
getType() |
String |
getWithholdingTaxCountry()
Constraints: Not nullable, Maximum length: 3
|
int |
hashCode() |
void |
setAccountingClerk(String accountingClerk)
Constraints: Not nullable, Maximum length: 2
|
void |
setAccountingClerkFaxNumber(String accountingClerkFaxNumber)
Constraints: Not nullable, Maximum length: 31
|
void |
setAccountingClerkPhoneNumber(String accountingClerkPhoneNumber)
Constraints: Not nullable, Maximum length: 30
|
void |
setAlternativePayee(String alternativePayee)
Constraints: Not nullable, Maximum length: 10
|
void |
setAPARToleranceGroup(String aPARToleranceGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setAuthorizationGroup(String authorizationGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setBillOfExchLmtAmtInCoCodeCrcy(BigDecimal billOfExchLmtAmtInCoCodeCrcy)
Constraints: Not nullable, Precision: 14, Scale: 3
|
void |
setCashPlanningGroup(String cashPlanningGroup)
Constraints: Not nullable, Maximum length: 10
|
void |
setCheckPaidDurationInDays(BigDecimal checkPaidDurationInDays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setClearCustomerSupplier(Boolean clearCustomerSupplier)
Constraints: none
|
void |
setCompanyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4
|
void |
setCompanyCodeName(String companyCodeName)
Constraints: Not nullable, Maximum length: 25
|
void |
setDeletionIndicator(Boolean deletionIndicator)
Constraints: none
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g.
|
void |
setHouseBank(String houseBank)
Constraints: Not nullable, Maximum length: 5
|
void |
setInterestCalculationCode(String interestCalculationCode)
Constraints: Not nullable, Maximum length: 2
|
void |
setInterestCalculationDate(Calendar interestCalculationDate)
Constraints: Not nullable, Precision: 0
|
void |
setIntrstCalcFrequencyInMonths(String intrstCalcFrequencyInMonths)
Constraints: Not nullable, Maximum length: 2
|
void |
setIsBusinessPurposeCompleted(String isBusinessPurposeCompleted)
Constraints: Not nullable, Maximum length: 1
|
void |
setIsToBeCheckedForDuplicates(Boolean isToBeCheckedForDuplicates)
Constraints: none
|
void |
setIsToBeLocallyProcessed(Boolean isToBeLocallyProcessed)
Constraints: none
|
void |
setItemIsToBePaidSeparately(Boolean itemIsToBePaidSeparately)
Constraints: none
|
void |
setLayoutSortingRule(String layoutSortingRule)
Constraints: Not nullable, Maximum length: 3
|
void |
setPaymentBlockingReason(String paymentBlockingReason)
Constraints: Not nullable, Maximum length: 1
|
void |
setPaymentIsToBeSentByEDI(Boolean paymentIsToBeSentByEDI)
Constraints: none
|
void |
setPaymentMethodsList(String paymentMethodsList)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentTerms(String paymentTerms)
Constraints: Not nullable, Maximum length: 4
|
void |
setReconciliationAccount(String reconciliationAccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setSupplier(String supplier)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setSupplierAccountGroup(String supplierAccountGroup)
Constraints: Not nullable, Maximum length: 4
|
void |
setSupplierAccountNote(String supplierAccountNote)
Constraints: Not nullable, Maximum length: 30
|
void |
setSupplierCertificationDate(Calendar supplierCertificationDate)
Constraints: Not nullable, Precision: 0
|
void |
setSupplierClerk(String supplierClerk)
Constraints: Not nullable, Maximum length: 15
|
void |
setSupplierClerkIDBySupplier(String supplierClerkIDBySupplier)
Constraints: Not nullable, Maximum length: 12
|
void |
setSupplierClerkURL(String supplierClerkURL)
Constraints: Not nullable, Maximum length: 130
|
void |
setSupplierDunning(List<SupplierDunning> value)
Overwrites the list of associated SupplierDunning entities for the loaded navigation property to_SupplierDunning.
|
void |
setSupplierHeadOffice(String supplierHeadOffice)
Constraints: Not nullable, Maximum length: 10
|
void |
setSupplierIsBlockedForPosting(Boolean supplierIsBlockedForPosting)
Constraints: none
|
void |
setSupplierWithHoldingTax(List<SupplierWithHoldingTax> value)
Overwrites the list of associated SupplierWithHoldingTax entities for the loaded navigation property to_SupplierWithHoldingTax.
|
void |
setWithholdingTaxCountry(String withholdingTaxCountry)
Constraints: Not nullable, Maximum length: 3
|
String |
toString() |
getCustomField, getCustomField, getCustomFieldNames, getCustomFields, hasCustomField, hasCustomField, setCustomField, setCustomFieldpublic static final SupplierCompanySelectable ALL_FIELDS
public static final SupplierCompanyField<String> SUPPLIER
public static final SupplierCompanyField<String> COMPANY_CODE
public static final SupplierCompanyField<String> AUTHORIZATION_GROUP
public static final SupplierCompanyField<String> COMPANY_CODE_NAME
public static final SupplierCompanyField<String> PAYMENT_BLOCKING_REASON
public static final SupplierCompanyField<Boolean> SUPPLIER_IS_BLOCKED_FOR_POSTING
public static final SupplierCompanyField<String> ACCOUNTING_CLERK
public static final SupplierCompanyField<String> ACCOUNTING_CLERK_FAX_NUMBER
public static final SupplierCompanyField<String> ACCOUNTING_CLERK_PHONE_NUMBER
public static final SupplierCompanyField<String> SUPPLIER_CLERK
public static final SupplierCompanyField<String> SUPPLIER_CLERK_URL
public static final SupplierCompanyField<String> PAYMENT_METHODS_LIST
public static final SupplierCompanyField<String> PAYMENT_TERMS
public static final SupplierCompanyField<Boolean> CLEAR_CUSTOMER_SUPPLIER
public static final SupplierCompanyField<Boolean> IS_TO_BE_LOCALLY_PROCESSED
public static final SupplierCompanyField<Boolean> ITEM_IS_TO_BE_PAID_SEPARATELY
public static final SupplierCompanyField<Boolean> PAYMENT_IS_TO_BE_SENT_BY_EDI
public static final SupplierCompanyField<String> HOUSE_BANK
public static final SupplierCompanyField<BigDecimal> CHECK_PAID_DURATION_IN_DAYS
public static final SupplierCompanyField<BigDecimal> BILL_OF_EXCH_LMT_AMT_IN_CO_CODE_CRCY
public static final SupplierCompanyField<String> SUPPLIER_CLERK_ID_BY_SUPPLIER
public static final SupplierCompanyField<String> RECONCILIATION_ACCOUNT
public static final SupplierCompanyField<String> INTEREST_CALCULATION_CODE
public static final SupplierCompanyField<Calendar> INTEREST_CALCULATION_DATE
public static final SupplierCompanyField<String> INTRST_CALC_FREQUENCY_IN_MONTHS
public static final SupplierCompanyField<String> SUPPLIER_HEAD_OFFICE
public static final SupplierCompanyField<String> ALTERNATIVE_PAYEE
public static final SupplierCompanyField<String> LAYOUT_SORTING_RULE
public static final SupplierCompanyField<String> APAR_TOLERANCE_GROUP
public static final SupplierCompanyField<Calendar> SUPPLIER_CERTIFICATION_DATE
public static final SupplierCompanyField<String> SUPPLIER_ACCOUNT_NOTE
public static final SupplierCompanyField<String> WITHHOLDING_TAX_COUNTRY
public static final SupplierCompanyField<Boolean> DELETION_INDICATOR
public static final SupplierCompanyField<String> CASH_PLANNING_GROUP
public static final SupplierCompanyField<Boolean> IS_TO_BE_CHECKED_FOR_DUPLICATES
public static final SupplierCompanyField<String> SUPPLIER_ACCOUNT_GROUP
public static final SupplierCompanyField<String> IS_BUSINESS_PURPOSE_COMPLETED
public static final SupplierCompanyLink<SupplierDunning> TO_SUPPLIER_DUNNING
public static final SupplierCompanyLink<SupplierWithHoldingTax> TO_SUPPLIER_WITH_HOLDING_TAX
@Generated(value="lombok") public SupplierCompany()
@ConstructorProperties(value={"supplier","companyCode","authorizationGroup","companyCodeName","paymentBlockingReason","supplierIsBlockedForPosting","accountingClerk","accountingClerkFaxNumber","accountingClerkPhoneNumber","supplierClerk","supplierClerkURL","paymentMethodsList","paymentTerms","clearCustomerSupplier","isToBeLocallyProcessed","itemIsToBePaidSeparately","paymentIsToBeSentByEDI","houseBank","checkPaidDurationInDays","billOfExchLmtAmtInCoCodeCrcy","supplierClerkIDBySupplier","reconciliationAccount","interestCalculationCode","interestCalculationDate","intrstCalcFrequencyInMonths","supplierHeadOffice","alternativePayee","layoutSortingRule","aPARToleranceGroup","supplierCertificationDate","supplierAccountNote","withholdingTaxCountry","deletionIndicator","cashPlanningGroup","isToBeCheckedForDuplicates","supplierAccountGroup","isBusinessPurposeCompleted","erpConfigContext","toSupplierDunning","toSupplierWithHoldingTax"}) @Generated(value="lombok") public SupplierCompany(@Nullable String supplier, @Nullable String companyCode, @Nullable String authorizationGroup, @Nullable String companyCodeName, @Nullable String paymentBlockingReason, @Nullable Boolean supplierIsBlockedForPosting, @Nullable String accountingClerk, @Nullable String accountingClerkFaxNumber, @Nullable String accountingClerkPhoneNumber, @Nullable String supplierClerk, @Nullable String supplierClerkURL, @Nullable String paymentMethodsList, @Nullable String paymentTerms, @Nullable Boolean clearCustomerSupplier, @Nullable Boolean isToBeLocallyProcessed, @Nullable Boolean itemIsToBePaidSeparately, @Nullable Boolean paymentIsToBeSentByEDI, @Nullable String houseBank, @Nullable BigDecimal checkPaidDurationInDays, @Nullable BigDecimal billOfExchLmtAmtInCoCodeCrcy, @Nullable String supplierClerkIDBySupplier, @Nullable String reconciliationAccount, @Nullable String interestCalculationCode, @Nullable Calendar interestCalculationDate, @Nullable String intrstCalcFrequencyInMonths, @Nullable String supplierHeadOffice, @Nullable String alternativePayee, @Nullable String layoutSortingRule, @Nullable String aPARToleranceGroup, @Nullable Calendar supplierCertificationDate, @Nullable String supplierAccountNote, @Nullable String withholdingTaxCountry, @Nullable Boolean deletionIndicator, @Nullable String cashPlanningGroup, @Nullable Boolean isToBeCheckedForDuplicates, @Nullable String supplierAccountGroup, @Nullable String isBusinessPurposeCompleted, @Nullable ErpConfigContext erpConfigContext, List<SupplierDunning> toSupplierDunning, List<SupplierWithHoldingTax> toSupplierWithHoldingTax)
public Class<SupplierCompany> getType()
getType in class VdmObject<SupplierCompany>public static <T> SupplierCompanyField<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 List<SupplierDunning> fetchSupplierDunning() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public List<SupplierDunning> getSupplierDunningOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SupplierDunning of a queried SupplierCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public com.google.common.base.Optional<List<SupplierDunning>> getSupplierDunningOrNull()
If the navigation property to_SupplierDunning for an entity SupplierCompany has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setSupplierDunning(@NonNull
List<SupplierDunning> value)
If the navigation property to_SupplierDunning of a queried SupplierCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of SupplierDunning entities.public void addSupplierDunning(SupplierDunning... entity)
If the navigation property to_SupplierDunning of a queried SupplierCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of SupplierDunning entities.public List<SupplierWithHoldingTax> fetchSupplierWithHoldingTax() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public List<SupplierWithHoldingTax> getSupplierWithHoldingTaxOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_SupplierWithHoldingTax of a queried SupplierCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException - If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and therefore has no ERP configuration context assigned. An entity is managed if it has been either retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or UPDATE call.public com.google.common.base.Optional<List<SupplierWithHoldingTax>> getSupplierWithHoldingTaxOrNull()
If the navigation property to_SupplierWithHoldingTax for an entity SupplierCompany has not been resolved yet, this method will not query further information. Instead its Optional result state will be null.
public void setSupplierWithHoldingTax(@NonNull
List<SupplierWithHoldingTax> value)
If the navigation property to_SupplierWithHoldingTax of a queried SupplierCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value - List of SupplierWithHoldingTax entities.public void addSupplierWithHoldingTax(SupplierWithHoldingTax... entity)
If the navigation property to_SupplierWithHoldingTax of a queried SupplierCompany is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity - Array of SupplierWithHoldingTax entities.@Generated(value="lombok") public static SupplierCompany.SupplierCompanyBuilder builder()
@Nullable @Generated(value="lombok") public String getSupplier()
@Nullable @Generated(value="lombok") public String getCompanyCode()
@Nullable @Generated(value="lombok") public String getAuthorizationGroup()
@Nullable @Generated(value="lombok") public String getCompanyCodeName()
@Nullable @Generated(value="lombok") public String getPaymentBlockingReason()
You can use the block key as described below. Automatic Payment Transactions In automatic payment transactions, the block takes effect when it is entered in the system as follows: In the master record In the document If 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 Payments Manual 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.
@Nullable @Generated(value="lombok") public Boolean getSupplierIsBlockedForPosting()
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.
@Nullable @Generated(value="lombok") public String getAccountingClerk()
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).
@Nullable @Generated(value="lombok") public String getAccountingClerkFaxNumber()
@Nullable @Generated(value="lombok") public String getAccountingClerkPhoneNumber()
@Nullable @Generated(value="lombok") public String getSupplierClerk()
@Nullable @Generated(value="lombok") public String getSupplierClerkURL()
@Nullable @Generated(value="lombok") public String getPaymentMethodsList()
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.
@Nullable @Generated(value="lombok") public String getPaymentTerms()
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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.
@Nullable @Generated(value="lombok") public Boolean getClearCustomerSupplier()
To use this function in automatic payment transactions, you have to enter the customer account number in the vendor master record, enter the vendor account number in the customer master record, and select 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.
@Nullable @Generated(value="lombok") public Boolean getIsToBeLocallyProcessed()
Normally automatic payment transactions and dunning notices are created for the head office. Note Select this indicator only if this account is a head office account.
@Nullable @Generated(value="lombok") public Boolean getItemIsToBePaidSeparately()
@Nullable @Generated(value="lombok") public Boolean getPaymentIsToBeSentByEDI()
@Nullable @Generated(value="lombok") public String getHouseBank()
@Nullable @Generated(value="lombok") public BigDecimal getCheckPaidDurationInDays()
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 time In Cash Management, the value date is used as information about the expected cash outflow.
@Nullable @Generated(value="lombok") public BigDecimal getBillOfExchLmtAmtInCoCodeCrcy()
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.
@Nullable @Generated(value="lombok") public String getSupplierClerkIDBySupplier()
@Nullable @Generated(value="lombok") public String getReconciliationAccount()
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.
@Nullable @Generated(value="lombok") public String getInterestCalculationCode()
@Nullable @Generated(value="lombok") public Calendar getInterestCalculationDate()
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.
@Nullable @Generated(value="lombok") public String getIntrstCalcFrequencyInMonths()
Date of last interest calculation: 3/31. + 01 month interest calculation frequency = 4/30 upper limit for the current interest run The 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.
@Nullable @Generated(value="lombok") public String getSupplierHeadOffice()
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.
@Nullable @Generated(value="lombok") public String getAlternativePayee()
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.
@Nullable @Generated(value="lombok") public String getLayoutSortingRule()
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. Note Field information from another document line item cannot be adopted into the field of a particular item.
@Nullable @Generated(value="lombok") public String getAPARToleranceGroup()
Each tolerance group contains settings that affect cash discount and payment difference processing. These settings become effective during payment entry.
@Nullable @Generated(value="lombok") public Calendar getSupplierCertificationDate()
Date field in which to enter certification date for small companies run by women or minorities. This certificate must be renewed every two years.
@Nullable @Generated(value="lombok") public String getSupplierAccountNote()
The memo serves only as information on special features of the customer/vendor.
@Nullable @Generated(value="lombok") public String getWithholdingTaxCountry()
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
@Nullable @Generated(value="lombok") public Boolean getDeletionIndicator()
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.
@Nullable @Generated(value="lombok") public String getCashPlanningGroup()
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 collection R2 Other domestic customers R3 Customers abroad R4 Affiliated company customers R5 High risk customers R6 Major customers R7 Rental income R8 Repayment of loans ... E1 Domestic vendors E2 Vendors abroad E3 Affiliated company vendors E4 Major vendors E5 Personnel costs E6 Taxes E7 Investments ...
@Nullable @Generated(value="lombok") public Boolean getIsToBeCheckedForDuplicates()
Checking Logistics Documents The 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: Vendor Currency Company Code Gross Invoice Amount Reference Document Number Invoice Document Date If 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 Number Invoice Document Date Company Code Having 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 333 Invoice Date: 4/28/2000 Gross Invoice Amount 100.00 Currency: EUR Vendor: Spencer Company Code: Chicago You 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 334 Invoice Date: 4/28/2000 Gross Invoice Amount 100.00 Currency: EUR Vendor: Spencer Company Code: Flagstaff Result Because 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 Documents The 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 Code Vendor Currency Document Date Reference Number If 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 Code Vendor Currency Document Date Amount in Document Currency In Materials Management, the system applies the check for duplicate invoices for invoices only, not for credit memos.
@Nullable @Generated(value="lombok") public String getSupplierAccountGroup()
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.
@Nullable @Generated(value="lombok") public String getIsBusinessPurposeCompleted()
@Nullable @Generated(value="lombok") public ErpConfigContext getErpConfigContext()
@Generated(value="lombok") public void setSupplier(@Nullable String supplier)
supplier - @Generated(value="lombok") public void setCompanyCode(@Nullable String companyCode)
companyCode - @Generated(value="lombok") public void setAuthorizationGroup(@Nullable String authorizationGroup)
authorizationGroup - @Generated(value="lombok") public void setCompanyCodeName(@Nullable String companyCodeName)
companyCodeName - @Generated(value="lombok") public void setPaymentBlockingReason(@Nullable String paymentBlockingReason)
You can use the block key as described below. Automatic Payment Transactions In automatic payment transactions, the block takes effect when it is entered in the system as follows: In the master record In the document If 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 Payments Manual 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.
paymentBlockingReason - @Generated(value="lombok") public void setSupplierIsBlockedForPosting(@Nullable Boolean 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.
supplierIsBlockedForPosting - @Generated(value="lombok") public void setAccountingClerk(@Nullable String 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).
accountingClerk - @Generated(value="lombok") public void setAccountingClerkFaxNumber(@Nullable String accountingClerkFaxNumber)
accountingClerkFaxNumber - @Generated(value="lombok") public void setAccountingClerkPhoneNumber(@Nullable String accountingClerkPhoneNumber)
accountingClerkPhoneNumber - @Generated(value="lombok") public void setSupplierClerk(@Nullable String supplierClerk)
supplierClerk - @Generated(value="lombok") public void setSupplierClerkURL(@Nullable String supplierClerkURL)
supplierClerkURL - @Generated(value="lombok") public void setPaymentMethodsList(@Nullable String 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.
paymentMethodsList - @Generated(value="lombok") public void setPaymentTerms(@Nullable String paymentTerms)
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for: Cash management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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.
paymentTerms - @Generated(value="lombok") public void setClearCustomerSupplier(@Nullable Boolean clearCustomerSupplier)
To use this function in automatic payment transactions, you have to enter the customer account number in the vendor master record, enter the vendor account number in the customer master record, and select 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.
clearCustomerSupplier - @Generated(value="lombok") public void setIsToBeLocallyProcessed(@Nullable Boolean isToBeLocallyProcessed)
Normally automatic payment transactions and dunning notices are created for the head office. Note Select this indicator only if this account is a head office account.
isToBeLocallyProcessed - @Generated(value="lombok") public void setItemIsToBePaidSeparately(@Nullable Boolean itemIsToBePaidSeparately)
itemIsToBePaidSeparately - @Generated(value="lombok") public void setPaymentIsToBeSentByEDI(@Nullable Boolean paymentIsToBeSentByEDI)
paymentIsToBeSentByEDI - @Generated(value="lombok") public void setHouseBank(@Nullable String houseBank)
houseBank - @Generated(value="lombok") public void setCheckPaidDurationInDays(@Nullable BigDecimal 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 time In Cash Management, the value date is used as information about the expected cash outflow.
checkPaidDurationInDays - @Generated(value="lombok") public void setBillOfExchLmtAmtInCoCodeCrcy(@Nullable BigDecimal 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.
billOfExchLmtAmtInCoCodeCrcy - @Generated(value="lombok") public void setSupplierClerkIDBySupplier(@Nullable String supplierClerkIDBySupplier)
supplierClerkIDBySupplier - @Generated(value="lombok") public void setReconciliationAccount(@Nullable String 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.
reconciliationAccount - @Generated(value="lombok") public void setInterestCalculationCode(@Nullable String interestCalculationCode)
interestCalculationCode - @Generated(value="lombok") public void setInterestCalculationDate(@Nullable Calendar 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.
interestCalculationDate - @Generated(value="lombok") public void setIntrstCalcFrequencyInMonths(@Nullable String intrstCalcFrequencyInMonths)
Date of last interest calculation: 3/31. + 01 month interest calculation frequency = 4/30 upper limit for the current interest run The 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.
intrstCalcFrequencyInMonths - @Generated(value="lombok") public void setSupplierHeadOffice(@Nullable String 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.
supplierHeadOffice - @Generated(value="lombok") public void setAlternativePayee(@Nullable String 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.
alternativePayee - @Generated(value="lombok") public void setLayoutSortingRule(@Nullable String 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. Note Field information from another document line item cannot be adopted into the field of a particular item.
layoutSortingRule - @Generated(value="lombok") public void setAPARToleranceGroup(@Nullable String aPARToleranceGroup)
Each tolerance group contains settings that affect cash discount and payment difference processing. These settings become effective during payment entry.
aPARToleranceGroup - @Generated(value="lombok") public void setSupplierCertificationDate(@Nullable Calendar 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.
supplierCertificationDate - @Generated(value="lombok") public void setSupplierAccountNote(@Nullable String supplierAccountNote)
The memo serves only as information on special features of the customer/vendor.
supplierAccountNote - @Generated(value="lombok") public void setWithholdingTaxCountry(@Nullable String 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
withholdingTaxCountry - @Generated(value="lombok") public void setDeletionIndicator(@Nullable Boolean 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.
deletionIndicator - @Generated(value="lombok") public void setCashPlanningGroup(@Nullable String 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 collection R2 Other domestic customers R3 Customers abroad R4 Affiliated company customers R5 High risk customers R6 Major customers R7 Rental income R8 Repayment of loans ... E1 Domestic vendors E2 Vendors abroad E3 Affiliated company vendors E4 Major vendors E5 Personnel costs E6 Taxes E7 Investments ...
cashPlanningGroup - @Generated(value="lombok") public void setIsToBeCheckedForDuplicates(@Nullable Boolean isToBeCheckedForDuplicates)
Checking Logistics Documents The 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: Vendor Currency Company Code Gross Invoice Amount Reference Document Number Invoice Document Date If 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 Number Invoice Document Date Company Code Having 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 333 Invoice Date: 4/28/2000 Gross Invoice Amount 100.00 Currency: EUR Vendor: Spencer Company Code: Chicago You 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 334 Invoice Date: 4/28/2000 Gross Invoice Amount 100.00 Currency: EUR Vendor: Spencer Company Code: Flagstaff Result Because 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 Documents The 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 Code Vendor Currency Document Date Reference Number If 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 Code Vendor Currency Document Date Amount in Document Currency In Materials Management, the system applies the check for duplicate invoices for invoices only, not for credit memos.
isToBeCheckedForDuplicates - @Generated(value="lombok") public void setSupplierAccountGroup(@Nullable String 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.
supplierAccountGroup - @Generated(value="lombok") public void setIsBusinessPurposeCompleted(@Nullable String isBusinessPurposeCompleted)
isBusinessPurposeCompleted - @Generated(value="lombok") public void setErpConfigContext(@Nullable ErpConfigContext erpConfigContext)
erpConfigContext - @Generated(value="lombok") public String toString()
toString in class VdmObject<SupplierCompany>@Generated(value="lombok") public boolean equals(Object o)
equals in class VdmObject<SupplierCompany>@Generated(value="lombok") public int hashCode()
hashCode in class VdmObject<SupplierCompany>Copyright © 2018 SAP SE. All rights reserved.