A mapper representing custom fields in an entity. Custom fields are represented by their field names and the corresponding values. A custom field can be added or updated using setCustomField method.
The current ETag version of the entity in the remote system. The ETag identified the version of the in the remote system. It will be automatically set in the "if-match" header of update requests and can be set as a custom header for delete requests. When no ETag is provided by the remote system the value of this variable defaults to "*".
Our account number at customer. This field contains the account number the company is listed under at the customer. Maximum length: 12.
Accounting Clerk Abbreviation. Identification code for the accounting clerk. 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). Maximum length: 2.
Accounting clerk's fax number at the customer/vendor. Maximum length: 31.
Internet address of partner company clerk. Maximum length: 130.
Accounting clerk's telephone number at business partner. Maximum length: 30.
Account number of an alternative payer. Account number of the customer for whom automatic payment transactions are to be carried out.The account number is only needed if bank collections are not to be made via the customer who owes the receivables. The same applies to refunds of payables.The specification in this field only applies to this company code. There is another field in which you can enter an alternative payee for all company codes. If both fields are filled, the specification for the company code has priority. Maximum length: 10.
Tolerance Group for Business Partner/G/L Account. Freely definable group code for customers and vendors, or G/L accounts. Tolerance groups are unique within a company code. Each tolerance group contains settings that affect cash discount and payment difference processing. These settings become effective during payment entry. Maximum length: 4.
Authorization Group. The authorization group allows extended authorization protection for particular objects. The authorization groups are freely definable. The authorization groups usually occur in authorization objects together with an activity. Maximum length: 4.
Collective Invoice Variant. Indicator which specifies at what intervals the collective invoices are to be created for the customer. Maximum length: 1.
Company Code. The company code is an organizational unit within financial accounting. Maximum length: 4.
Customer Number. Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system. Maximum length: 10.
Customer Account Group. The account group is a classifying feature within customer master records. The account group determines: 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. Maximum length: 4.
Memo. Internal memo of the accounting department. The memo serves only as information on special features of the customer/vendor. Maximum length: 30.
Head office account number (in branch accounts). This field contains the account number of the head office. This account number is only specified for branch accounts. All postings for which the account number of the branch is specified, are automatically posted to the head office account. The account number of the branch affected is noted in the line items.No line items or balances are managed in the branch account. Maximum length: 10.
Indicator: Clearing between customer and vendor ?. Indicates that during automatic payment transactions clearing is made with the corresponding vendor account, and that during manual clearing procedures, the items of that vendor account are also selected. To use this function in automatic payment transactions, you have toenter the vendor account number in the customer master record,enter the customer account number in the vendor master record, andselect the "Clearing with customer" indicator in the vendor master record.If you set this indicator, the system will also include items of the vendor account in customer dunning.
Deletion Flag for Master Record (Company Code Level). Indicates that the company code data in this master record is to be deleted. 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.
Short Key for a House Bank. All bank data is determined using this key. Maximum length: 5.
Interest calculation indicator. Enter an interest calculation indicator here if the account is to be included in automatic interest calculation. Maximum length: 2.
Key Date of Last Interest Calculation. The date in this field displays the last time the interest calculation program processed this account. This is generally the upper limit of the last interest run. 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.
Interest Calculation Frequency in Months. An entry in this field determines the intervals (in months) at which interest is to be calculated automatically for this account (account balance interest calculation). The interest calculation frequency is added to the date of the last interest calculation. 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. Maximum length: 2.
Indicator: Local Processing?. Indicates that payment transactions and dunning notices are created for the branch. 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.
Indicator: Pay All Items Separately?. If this indicator is set, every customer/vendor open item is paid separately during automatic payment transactions. This means that open items are not grouped together for payment.
Key for Sorting According to Assignment Numbers. Indicates the layout rule for the Allocation field in the document line item. 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. Maximum length: 3.
Block Key for Payment. Block key (enqueue key) that is used to block an open item or an account to payment transactions. 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. Maximum length: 1.
List of Respected Payment Methods. List of payment methods which may be used in automatic payment transactions with this customer/vendor if you do not specify a payment method in the item to be paid. 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. Maximum length: 10.
Terms of Payment Key. Key for defining payment terms composed of cash discount percentages and payment periods. 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. Maximum length: 4.
Indicator: Send Payment Advices by EDI. This indicator specifies that the customer/vendor should be sent all payment advice information by EDI.
Posting block for company code. Indicates that the account is blocked for posting in the specified company code. 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.
Reconciliation Account in General Ledger. The reconciliation account in G/L accounting is the account which is updated parallel to the subledger account for normal postings (for example, invoice or payment). 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. Maximum length: 10.
Indicator: Record Payment History ?. Indicator that the payment history of the customer is to be recorded. The amount and number of payments are then recorded per calendar month, as well as the average days in arrears.Information about cash discount payments and net payments is recorded separately.The indicator should not be set for one-time accounts and accounts which are paid automatically (bank collection or bank bill in Germany, bill of exchange payment request in France).You can only carry out evaluation of the payment history, for example, with the report for customer evaluation with OI listing, if you have selected this field.
The remote state of the entity. Remote state refers to the last known state of the entity on the remote system from which it has been retrieved or to which it has been posted. It is stored as map, where the keys are stored in the format of VDM properties.
One-to-many navigation property to the CustomerDunning entity.
One-to-many navigation property to the CustomerWithHoldingTax entity.
User at customer. Name or identification code of the accounting clerk at the customer. Maximum length: 15.
ETag version identifier accessor.
Static representation of the accountingClerk property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountingClerkFaxNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountingClerkInternetAddress property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountingClerkPhoneNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountByCustomer property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields selector.
Static representation of the alternativePayerAccount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the aparToleranceGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the authorizationGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the collectiveInvoiceVariant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the companyCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customer property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerAccountGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerAccountNote property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerHeadOffice property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerSupplierClearingIsUsed property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the deletionIndicator property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the houseBank property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the interestCalculationCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the interestCalculationDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the intrstCalcFrequencyInMonths property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isToBeLocallyProcessed property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the itemIsToBePaidSeparately property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the layoutSortingRule property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the paymentBlockingReason property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the paymentMethodsList property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the paymentTerms property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the paytAdviceIsSentbyEdi property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the physicalInventoryBlockInd property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the reconciliationAccount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the recordPaymentHistoryIndicator property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the one-to-many navigation property toCustomerDunning for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the one-to-many navigation property toWithHoldingTax for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the userAtCustomer property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the CustomerCompany entity.
Default url path for the according service.
Technical entity name for CustomerCompany.
All key fields of the CustomerCompany entity.
Mapping of all key field names to the respective static field property CustomerCompany.
Returns a map of all defined fields in entity to their current values.
Entity with all defined entity fields
Custom field value getter.
The name of the custom field
The value of the corresponding custom field
Returns a map that contains all entity custom fields.
A map of all defined custom fields in the entity
Returns all updated custom field properties compared to the last known remote state.
A map containing all updated custom properties, with their new values
Returns all changed properties compared to the last known remote state. The returned properties does not include custom fields. Use getUpdatedCustomFields, if updated custom fields are needed.
Entity with all properties that changed
Validates whether a custom field exists in the entity.
The name of the custom field to update
A boolean value, that indicates whether a custom field is defined in entity
Sets all retrieved custom fields in entity.
Extracted custom fields from a retrieved entity
A boolean value, that indicates the existence of the field in entity
Validates whether a field name does not conflict with an original field name and thus can be defined as custom fields.
Field name to check
Boolean value that describes whether a field name can be defined as custom field
Sets a new custom field in the entity or updates it. Throws an error, if the provided custom field name is already defined by an original field in entity.
The name of the custom field to update
The value of the field
The entity itself, to facilitate method chaining
Initializes or sets the remoteState of the entity. This function is called on all read, create and update requests. This function should be called after initializeCustomFields, if custom fields are defined.
State to be set as remote state
The entity itself, to facilitate method chaining
Set the ETag version identifier of the retrieved entity.
The returned ETag version of the entity
The entity itself, to facilitate method chaining
Overwrites the default toJSON method so that all instance variables as well as all custom fields of the entity are returned.
An object containing all instance variables + custom fields.
Returns an entity builder to construct instances CustomerCompany.
A builder that constructs instances of entity type CustomerCompany.
Returns a selectable object that allows the selection of custom field in a get request for the entity CustomerCompany.
Name of the custom field to select
A builder that constructs instances of entity type CustomerCompany.
Returns a request builder to construct requests for operations on the CustomerCompany entity type.
A CustomerCompany request builder.
This class represents the entity "A_CustomerCompany" of service "API_BUSINESS_PARTNER". This service is part of the following communication scenarios: Business Partner, Customer and Supplier Integration (SAP_COM_0008). See https://api.sap.com/api/API_BUSINESS_PARTNER for more information.