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 "*".
Absolute exchange rate for FI postings. Exchange rate from document currency into accounting currency.
Accounting Document Number. The document number is the key the system uses to access the accounting document. The document number is unique per company code and fiscal year. When entering an accounting document, you can specify the number manually or it can be determined by the system from a pre-defined area (number range).The relevant area of the document numbers (number range) is determined in each company code per document type. Maximum length: 10.
ID:Exchange rate setting (no new rate determ.in bill.doc.). Indicates whether the foreign currency exchange rate that is applied to the sales document is fixed or whether it can be changed during billing. The system can propose a value. You can change the value manually in the sales document. If you are allowed to change the exchange rate during billing, the system recalculates prices using the most recent exchange rate.
Posting Status of Billing Document. The accounting status of the billing document. The status message tells you whether the billing document must be posted to accounting, and, if so, whether the posting has taken place. Maximum length: 1.
Status for Transfer to Accounting. The accounting status of the billing document (for example, an invoice). The status message tells you whether the system has successfully posted the document to accounting or whether posting is blocked because a posting block is set for the billing type. Maximum length: 1.
Accounting exchange rate quotation is indirect.
Additional Value Days. The number of days between the billing date and the date on which the terms of payment for the sales document become effective. If you enter a value in this field, you cannot enter a date in the fixed value date field. Maximum length: 2.
Assignment number. The allocation is additional information in the customer line item of the journal entry. The line items of an account are displayed in sort sequence according to the content of the field.The allocation number is set in the billing document in accordance with control in document flow and transferred to the financial journal entry.It is possible to set the customer purchase order number, the customer order number, the delivery number or the external delivery number as allocation numbers.The field is a separating criterion in the billing document. Maximum length: 18.
Combination criteria in the billing document. Maximum length: 40.
Billing Document. The number that uniquely identifies the billing document (the invoice, for example). Maximum length: 10.
Billing Category. Indicates whether the billing document refers to a sales order or a delivery. Maximum length: 1.
Billing Date. The date on which the billing is processed and booked for accounting purposes. You can use the billing date as one of the selection criteria when you process billing documents collectively.If invoice dates are defined for the customer, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date.If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document.If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone.In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
Billing document is canceled.
Billing date for the invoice list. Specifies the billing date of the invoice list. The system automatically proposes the next valid date defined in the customer's factory calendar. You can change the date manually in the header of the invoice list.
Invoice List Type. Classification that distinguishes between invoice list types that require different processing by the system. Maximum length: 4.
Billing Type. Classifies types of billing document that require different processing by the system. When you process billing documents collectively, you can use the billing type as one of the selection criteria. Maximum length: 4.
SD Billing Document Issue. Maximum length: 1.
Number of canceled billing document. Maximum length: 10.
City Code. This key is used for classifying cities from a tax point of view. This is a finer sub-division than the county code. Currently the key is used only in the USA for handling city tax. Maximum length: 4.
Company Code. The company code is an organizational unit within financial accounting. Maximum length: 4.
Contract Account Number. Key that uniquely identifies a contract account per client. The postings in Contract Accounts Receivable and Payable are always assigned to a contract account and a business partner.In the contract account master record, specifically for each business partner, you can define procedures that are to be used for further processing of line items. These include for example, payment methods, dunning procedure, tolerances.NoteFor utility and insurance companies, a contract is assigned to exactly one contract account. However several accounts - depending on contract account type can be assigned to one contract account. Maximum length: 12.
Destination Country. Identifies the destination country in which the goods are delivered to the customer. As a general rule, it is best to use the existing international standards for identifying vehicles from different countries (for example: USA = United States, I = Italy, and so on).The system uses the country key identifier to:Help determine the appropriate taxes during pricingDetermine important country-specific standards (the length of postal codes and bank account numbers, for example)When you process billing documents collectively, you can use the destination country as one of the selection criteria. Maximum length: 3.
County Code. Key used to classify cities from the point of view of taxes. Currently the county code is used in the USA for handling county tax, and in Denmark to define the municipality number of the employee's first place of residence. Maximum length: 3.
Date on Which Record Was Created.
Entry time. The time of day at which the document was posted and stored in the system.
Credit Control Area. The credit control area is an organizational entity which grants and monitors a credit limit for customers. A credit control area can include one or more company codes. You can also enter the credit control area separately for each posting, if this was marked in the appropriate company code.When entering an order, the credit control area can also be determined from the business area and the sales area segement of the payer's master record or using a user exit.It follows that company codes and credit control areas are not linked.The only thing that you define in the company code table is the default credit control area. This is used either for payments on account to credit these payments, or where you did not enter a credit control area or the system could not determine one.There is also an allocation table of permitted credit control areas per company code which is used to check entries only. Maximum length: 4.
Account Assignment Group for this customer. The account assignment group to which the system automatically posts the sales document. The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document. Maximum length: 2.
Customer Group. Identifies a particular group of customers (for example, wholesale or retail) for the purpose of pricing or generating statistics. Maximum length: 2.
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.
Customer Price Group. A grouping of customers who share the same pricing requirements. You can define price groups according to the needs of your organization and create pricing records for each group. You can, for example, define a group of customers to whom you want to give the same kind of discount. You can assign a price group to an individual customer either in the customer master record or in the sales document.The system can propose the price group from the customer master record. You can change the proposed value manually in the sales document at both header and item level. Maximum length: 2.
Agreement (various conditions grouped together). The number that uniquely identifies a rebate agreement. A rebate agreement is an agreement between a customer and a supplier. On the basis of the customer's sales volume during a specified period, the supplier grants the customer a special rebate. A general rebate agreement can consist of numerous individual agreements (condition records) that are based on different factors. For example, an individualagreement may be based on a combination of customer and material or a combination of customer and rebate group, and so on. Maximum length: 10.
Tax Classification 1 for Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax Classification 2 for Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax classification 3 for customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax Classification 4 Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax Classification 5 for Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax Classification 6 for Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax Classification 7 for Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax Classification 8 for Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Tax Classification 9 for Customer. Indicates whether, during pricing, the system takes into account taxes that relate to the customer (for example, state sales taxes). The system copies the tax classification from the tax information stored in the customer master record of the ship-to party. During pricing, the system uses the tax classification together with the country key (identifies where the customer is located) to calculate relevant taxes. Maximum length: 1.
Distribution Channel. The way in which products or services reach the customer. Typical examples of distribution channels are wholesale, retail, or direct sales. You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area. Maximum length: 2.
Division. A way of grouping materials, products, or services. The system uses divisions to determine the sales areas and the business areas for a material, product, or service. A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions. Maximum length: 2.
Reference Document Number. The reference document number contains the document number with the business partner The reference document number serves as a search criterion when displaying or changing documents. In correspondence, the refererence document number is sometimes printed instead of the document number.The reference number is set in the document flow according to control and taken into the financial journal entry.You can set the customer order number, the order number, the delivery number, the billing number or the external delivery number as reference number.The field is a seperation criterion in the billing document. Maximum length: 16.
Dunning Area. The dunning area represents an organizational entity that is responsible for dunning. The dunning areas represent a sub-structure of the company codes. If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures.The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary. Maximum length: 2.
Dunning Block. Key which reflects the reason for a dunning block indicator. Maximum length: 1.
Dunning Key. Determines that the item can only be dunned with restrictions or is to be displayed with an extra text line on the dunning notice. The keys are freely-definable. You define the contents of the text line in Customizing for the dunning key.If you enter a key in an item, then it can only reach the maximum dunning level defined for this key. Therefore it is possible that an item can contain one dunning notice at the most, although several dunning levels are defined in the dunning procedure. Maximum length: 1.
Translation Date. Translation date for determining the exchange rate which is to be used for translation. The exchange rates are stored in the system. You do not need to enter a date unless the date in question is not the same as the document entry date.
Exchange Rate Type. Key representing a type of exchange rate in the system. You enter the exchange rate type to store different exchange rates.You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts. Maximum length: 4.
Fiscal Year. Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The fiscal year can be the same as the calendar year, but does not have to be. Maximum length: 4.
Fixed Value Date. The date on which the terms of payment related to the sales document become effective. If you enter a date in this field, you cannot enter a value in the additional value days field.
Number of foreign trade data in MM and SD documents. Internal number for export data. Maximum length: 10.
Hierarchy type for pricing. Maximum length: 1.
Incoterms (Part 1). Commonly used trading terms that comply with the standards established by the International Chamber of Commerce (ICC). Incoterms specify internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be completed successfully.If goods are shipped through a port of departure, the appropriate Incoterm might be: FOB ("Free On Board"). You can provide further details (for example, the name of the port) in the secondary Incoterm field: FOB Boston, for example. Maximum length: 3.
Incoterms Location 1. Provides additional information for the primary Incoterm. For Incoterms 2010, this field represents:
Incoterms Location 2. Provides additional information for the Incoterms. This field is only available for C-Clauses (if customized appropriately). Note the following for the incoterms versions below: No Version:This field is disabledIncoterm Version 2000This field is disabled as part of standard delivery unless a customer decides to enable it by the way of Customizing for Sales and Distribution under Master Data -> Business Partners -> Customers -> Billing Document -> Incoterms -> Map Incoterms to Versions.Incoterm Version 2010For this version, the field represents:Sea and inland waterway transport - Port of DestinationAny mode of transport - Place of Destination2010 Incoterms are divided as follows:Group 1: Rules for any mode or modes of transport (including by vessel)Incoterms Incoterms Description Location 2CPT Carriage Paid To Place of DestinationCIP Carriage & Insurance Paid To Place of DestinationGroup 2: Rules for sea and inland waterwaysIncoterms Incoterms Description Location 2CFR Cost & Freight Port of DestinationCIF Cost Insurance & Freight Port of Destination. Maximum length: 70.
Incoterms (Part 2). Additional information for the primary Incoterm. If the primary Incoterm is, for example, FOB ("Free on Board"), then the second field provides details of the port from which the delivery leaves (for example, "FOB Boston"). Maximum length: 28.
Incoterms Version. An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC). Maximum length: 4.
Financial doc. processing: Internal financial doc. number. Internal number of a financial document that is mapped to a trade finance transaction. The number is assigned by the system. You want to guarantee the payment of your sales order by using a transaction in Trade Finance (for example, a letter of credit transaction). A trade finance transaction is mapped to a financial document number in SD. To guarantee the payment, you therefore assign a financial document number by selecting its corresponding trade finance transaction.You can navigate to the corresponding trade finance transaction directly from the assigned financial document number. As a prerequisite, you need to have the authorization to display the trade finance transaction.Before you can select a trade finance transaction when assigning a financial document to a sales order, you need to activate the integration with Trade Finance first.For information about how to activate the integration with Trade Finance, see Integration of Trade Finance with S/4HANA Finance on SAP Help Portal under SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Finance -> Treasury and Financial Risk Management -> SAP Treasury and Risk Management (FIN-FSCM-TRM) -> Transaction Manager -> Overview Financial Instruments -> Trade Finance. Maximum length: 10.
Invoice list status of billing document. Maximum length: 1.
Indicator: Triangular Deal Within the EU?. If you select this field, the system includes this transaction in the EC sales list under the triangular deal section.
Export indicator. Indicates whether the delivery will be exported. Maximum length: 1.
Exclude from Intrastat Reporting.
Relevant for Intrastat Reporting.
Is relevant for accrual.
Date of Last Change.
UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun). The UTC timestamp displays date and time according to UTC (Universal Coordinated Time). In order to convert local time into a UTC time stamp, which makes it easier to compare times, the local time must be converted according to your time zone. The ABAP command convert is available for this purpose.Even if the time zone that the conversion is based on can be redetermined from Customizing or master data, we still recommend that you save the time zone.The internal structure of the high-resolution UTC time stamp is logically organized in date and time sections in a packed decimal format (YYYYMMDDhhmmssmmmuuun), which depicts the year, month, day, hour,second, millisecond, microsecond and the first decimal of the nanoseconds. Please note that the hardware that is normally used does not fully support a resolution of 100 nanoseconds, which is available in the structure.See also GET TIME STAMPA UTC time stamp in short form is also available.
Logical System. System in which applications run integrated on a shared data basis. The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system. Maximum length: 10.
Manual Invoice Maintenance. Indicates if the invoices for manual post processing should be printed out. The system proposes the value from the customer master record. You can change the indicator manually in the sales document.
SD Billing Status. Maximum length: 1.
Document is incomplete with respect to pricing. Maximum length: 1.
Overall Processing Status of Document. The processing status of the entire sales document. The system determines the status of the entire sales document by taking into account the status of all header-related information and the status of all individual items. The status message tells you whether processing of the sales document is open, in progress, or complete. Maximum length: 1.
Total incompletion status of all items in general. The incompletion status of general item information in the sales document. General item information includes business, shipping, and billing data. The status tells you if general item information is incomplete. Sales documents where general information is missing cannot be copied into other documents. For example, you cannot copy an incomplete quotation into a sales order.If you try to save a document with missing information, the system tells you that the document is incomplete. You can then list the fields where information is missing and complete them. Alternatively, you can save the incomplete document and enter the missing information later. Maximum length: 1.
Partner Company ID. Company ID standard for the whole group. Maximum length: 6.
Payer. The party who is responsible for actually paying the bill. The payer may differ from the bill-to party who receives the bill. Maximum length: 10.
Payment Method. Payment method with which this item is to be paid. If you enter a payment method, then only this payment method can be used in automatic payment transactions. Unless you enter a payment method, one of the payment methods that was allowed in the master record is selected in the payment program according to specified rules.For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program. Maximum length: 1.
Payment Reference. The payment reference contains a key for customer line items which is passed on to the customer in the invoice. The customer should refer to the payment reference when making the payment. For vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference. In automatic payment transactions, the payment reference can be passed on again to the payee.When an outgoing payment is made, the payment reference you specify is passed on to the relevant financial institute and from there to the payee.When you are processing your account statement, you can use the payment reference to determine which items you have paid and then clear them.Payment reference numbers are often used in Finland, Norway, and Sweden. These countries also have rules for the structure of the payment reference. Check digit procedures are used to check that these rules are followed.DME Finland: The number '4477' has a check digit of '8' and should be defined as the character string '44778'.DME Norway: The number '12345678' has the check digit '2' when using the Modulo-10 method, and check digit '5' when using the Modulo-11 method. Therefore, 123456782 or 123456785 are permitted as payment references.DME Sweden: The number '1234567890' has the check digit '3' and should be defined as the character string '12345678903'. The Modulo procedure used is a form of Modulo-10 with the key '1212121'. Maximum length: 30.
Price List Type. Identifies a price list or other condition type (for example, a surcharge or discount). You can define price list types according to the needs of your own organization. Price list types can be grouped according to:the kind of price list (for example, wholesale or retail)the currency in which the price appearsthe number of the price list typeYou can use price list types to apply conditions during pricing or to generate statistics.In the customer master record, enter one of the values predefined for your system. The system proposes the value automatically during sales order processing. You can change the value manually in the sales document header. Maximum length: 2.
Customer Reference. Number that the customer uses to uniquely identify a purchasing document (e.g. an inquiry or a purchase order). The number creates the link between the customer purchase order and the sales document that you create. You can use the number used by the customer during correspondence with the customer to find certain document information. If the number refers to a purchase order, you can also print it on the documents that you send to the customer (e.g. on the delivery note). Maximum length: 35.
Region (State, Province, County). In some countries, the region forms part of the address. The meaning depends on the country. The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.For more information, see the examples in the documentation on the Address Layout Key.Meaning of the regional code in ...Australia -> ProvinceBrazil -> StateCanada -> ProvinceGermany -> StateGreat Britain -> CountyItaly -> ProvinceJapan -> PrefectureSwitzerland -> CantonUSA -> State. Maximum length: 3.
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.
Sales District. A geographical sales district or region. Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level. Maximum length: 6.
Number of the Document Condition. The internal number under which the system saves conditions that apply to a sales order, for example. The purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area. The system uses the internal number to identify the different conditions. Maximum length: 10.
Sales Organization. An organizational unit responsible for the sale of certain products or services. The responsibility of a sales organization may include legal liability for products and customer claims. You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area. Maximum length: 4.
SD Document Category. A classification for the different types of documents that you can process in the sales and distribution system (for example: quotations, sales orders, deliveries, and invoices). The document category determines how the system stores and keeps track of document data. It enables the system to provide you with status information about delivery processing, billing, and documents that are used for reference (for example, inquiries and quotations). Maximum length: 4.
Pricing Procedure in Pricing. Determines which condition types can be used in a document and in which sequence they appear. Maximum length: 6.
Unique Reference to Mandate for each Payee. Identifies, together with the Creditor Identifier, the mandate uniquely. The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment.Whether internal or external number assignment (or both) is possible depends on the application concerned.Once you have created the mandate, you can no longer change its mandate reference.At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field.Notes on Assigning Contract Accounts and Contracts to MandatesYou can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment.Notes on Using Alternative PayersIf you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen.ExampleYou enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1.Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects.Example - Assignment of a mandate to multiple contract accountsContract account Mandate (in Contract Acct) MeaningC1 M1 Mandate M1 is valid for C1.C2 M1 Mandate M1 is also valid for C2.C3 M2 Mandate M2 is valid for C3.C4 M2 Mandate M2 is also valid for C4.Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account.Example - Assignment of one contract account per mandateMandate Contract Account (in Mandate) MeaningM1 C1 Mandate M1 is only valid for items of contract account C1.M2 C2 Mandate M2 is only valid for items of contract account C2.If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects.The examples above apply in a similar manner to the assignment of contracts.Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate.If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details.If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment.If you do not make any specification, the system uses the first mandate that qualifies for the payment. Maximum length: 35.
Shipping Conditions. General shipping strategy for the delivery of goods from the vendor to the customer. You can define shipping conditions in your system which correspond to the requirements of your company. You can specify a shipping condition in the customer master and in the vendor master.Shipping point determination (outbound delivery):The loading group, the plant and the shipping condition determine the shipping point that will be proposed by the system.Route determination (outbound delivery):Apart from the country and the geographical region of the shipping point, the ship-to party and the transportation group, the shipping condition determines the route that the system proposes in the order for the delivery of the goods. In the delivery, the route proposal also takes the weight group into account.A particular customer always requires immediate delivery. You enter the appropriate shipping condition into the customer master record. This means that when you process orders for this customer, the system automatically proposes the express mail room as a shipping point and the quickest way to the airport as a route.If a shipping condition has been assigned to a sales document type in Customizing, this condition will be proposed by the system in the corresponding sales document. If there is no assignment, the system copies the relevant data from the corresponding customer master record of the sold-to party. You cannot change this value during delivery processing. The shipping condition will not be copied from the delivery into the shipment. The shipping condition is one of several criteria for selecting deliveries when you create a shipment. You can enter a shipping condition manually in the shipment where it only serves as a characteristic for grouping shipments. Maximum length: 2.
Sold-To Party. The customer who orders the goods or services. The sold-to party is contractually responsible for sales orders. Maximum length: 10.
Statistics Currency. Maximum length: 5.
Tax amount in document currency. The total sales taxes, expressed in the document currency.
Tax Departure Country. For tax determination, the country of departure is used as the plant country. A different country needs to be entered for certain internal European transactions (chain transactions). Maximum length: 3.
One-to-many navigation property to the BillingDocumentItem entity.
One-to-many navigation property to the BillingDocumentPartner entity.
One-to-many navigation property to the BillingDocumentPrcgElmnt entity.
Total Gross Amount.
Net Value in Document Currency. Net value of the document item.
SD document currency. The currency that applies to the document (for example, to a sales order or an invoice). The system proposes the document currency from the customer master record of the sold-to party. You can change the currency manually in the document. If you change the currency, the system recalculates prices for the entire document. Maximum length: 5.
VAT Registration Number. VAT registration number (VAT reg.no.) of the customer, vendor or your company code. The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed. Maximum length: 20.
Country of Sales Tax ID Number. Specifies the key for the country of the VAT registration number. This key is used to check country-specific entries such as the length of the zip code or bank account number. Maximum length: 3.
Origin of Sales Tax ID Dumber. Maximum length: 1.
ETag version identifier accessor.
Static representation of the absltAccountingExchangeRate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountingDocument property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountingExchangeRateIsSet property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountingPostingStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the accountingTransferStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the acctgExchangeRateIsIndrctQtan property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the additionalValueDays 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 assignmentReference property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocument property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocumentCategory property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocumentDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocumentIsCancelled property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocumentListDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocumentListType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocumentType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingDocCombinationCriteria property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingIssueType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the cancelledBillingDocument property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the cityCode 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 contractAccount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the country property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the county property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creationDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creationTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the creditControlArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerAccountAssignmentGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerPaymentTerms property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerPriceGroup property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerRebateAgreement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification1 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification2 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification3 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification4 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification5 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification6 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification7 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification8 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the customerTaxClassification9 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the distributionChannel property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the division property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the documentReferenceId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the dunningArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the dunningBlockingReason property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the dunningKey property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the exchangeRateDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the exchangeRateType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the fiscalYear property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the fixedValueDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the foreignTrade property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the hierarchyTypePricing property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsClassification property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsLocation1 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsLocation2 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsTransferLocation property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the incotermsVersion property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the internalFinancialDocument property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the invoiceListStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isEuTriangularDeal property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isExportDelivery property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isIntrastatReportingExcluded property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isIntrastatReportingRelevant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isRelevantForAccrual property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangeDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangeDateTime property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the logicalSystem property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the manualInvoiceMaintIsRelevant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallBillingStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallPricingIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overallSdProcessStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the ovrlItmGeneralIncompletionSts property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the partnerCompany property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the payerParty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the paymentMethod property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the paymentReference property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the priceListType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the purchaseOrderByCustomer property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the region property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the salesDistrict property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the salesDocumentCondition property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the salesOrganization property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the sdDocumentCategory property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the sdPricingProcedure property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the sepaMandate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the shippingCondition property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the soldToParty property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the statisticsCurrency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the taxAmount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the taxDepartureCountry property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the totalGrossAmount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the totalNetAmount 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 toItem 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 toPartner 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 toPricingElement for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the transactionCurrency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the vatRegistration property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the vatRegistrationCountry property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the vatRegistrationOrigin property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the BillingDocument entity.
Default url path for the according service.
Technical entity name for BillingDocument.
All key fields of the BillingDocument entity.
Mapping of all key field names to the respective static field property BillingDocument.
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 BillingDocument
.
A builder that constructs instances of entity type BillingDocument
.
Returns a selectable object that allows the selection of custom field in a get request for the entity BillingDocument
.
Name of the custom field to select
A builder that constructs instances of entity type BillingDocument
.
Returns a request builder to construct requests for operations on the BillingDocument
entity type.
A BillingDocument
request builder.
This class represents the entity "A_BillingDocument" of service "API_BILLING_DOCUMENT_SRV". This service is part of the following communication scenarios: Billing Integration (SAP_COM_0120). See https://api.sap.com/api/API_BILLING_DOCUMENT_SRV for more information.