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 "*".
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.
Base Unit of Measure. Unit of measure in which stocks of the material are managed. The system converts all the quantities you enter in other units of measure (alternative units of measure) to the base unit of measure. You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified. Maximum length: 3.
Maximum number of sales orders per condition record. Specifies - up to a maximum of three - the number of sales orders that can benefit from this condition record. You introduce a new product for which you offer an introductory discount. The customer gets this discount only on the first two orders - the initial order and the first replenishment order. Thereafter, the discount is inactive. In this case, you enter '2' in this field.To see how many orders have already benefitted from a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record. Maximum length: 2.
Condition Currency (for Cumulation Fields). Maximum length: 5.
Application. Subdivides the usage of a condition (for example, pricing) for use in different application areas (for example, sales & distribution or purchasing). Maximum length: 2.
Calculation Type for Condition. Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight. The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record. Maximum length: 1.
Condition exclusion indicator. Indicates whether the system automatically excludes the discounts that are proposed during pricing. You can set this indicator in two ways:For a particular condition record (the field appears on the Details screen)For all records of a particular condition type (the field appears on the screen where you define the condition type)If you set the indicator to exclude conditions, there are several things to consider:The system will still take into account any condition supplements that are part of the condition record for the price (condition type PR00, for example)You can allow for exceptions where you want to include discounts in spite of the condition exclusion indicator (for a particular discount condition you can specify a requirement that applies the discount ONLY when the indicator is set). Maximum length: 1.
Deletion Indicator for Condition Record. Indicates whether the condition is no longer taken into account during document processing. The condition is deleted during the next reorganization run.
Lower limit of the condition rate/amount. Indicates whether, during document processing, the system checks if manual changes fall short of the lower limit allowed for the corresponding condition record. When you maintain the scales in a condition record, the system checks whether the scale value falls below the lower limit.
Condition Pricing Unit. The quantity on which the amount or percentage is based. The quantity is expressed in sales units (for example, bottles). You want to create a condition record for a material price of US$8 for 1 piece. You enter "8" in the Rate field, "USD" in the Unit field, and "1" as the condition pricing unit in this field.You create a condition record that gives a fixed discount of $10 to a customer who buys 1000 bottles. In this case, the condition pricing unit is 1000.
Condition Unit. Quantity unit to which the condition amount refers. Maximum length: 3.
Condition amount or percentage where no scale exists. The rate that determines how the system calculates pricing using this condition. Depending on the condition type, the rate can be a fixed amount or a percentage. If the condition includes a pricing scale, the rate displays the first line of the scale. The following examples illustrate how you can use the rate in different condition types:If you create a condition that includes prices (for example, prices for a material), you enter an amount.If you are creating a condition based on percentage discounts or surcharges (for example, a customer-specific discount), you enter the value of a percentage. If the condition is a discount, the system automatically enters a minus sign behind the amount and a percent sign in the Rate unit field.
Condition unit (currency or percentage). The unit that determines whether the condition for a material is based on a percentage or on an amount in a particular currency. The use of the condition unit depends on the condition type (for example, whether the condition is a material price or a customer discount). The following examples illustrate what you can do when using different condition types.If you create a condition that includes prices (for example, prices for a material), you enter the currency that applies to the condition (for example, "USD" for US dollars)If you are creating a condition based on percentage discounts or surcharges (for example, a customer-specific discount), you cannot enter a value in the Condition unit field. Instead, the system automatically enters a percent sign as the condition unit when you enter a value in the Condition Amount field. Maximum length: 5.
Number of the Condition Record. Number that uniquely identifies a condition record. The system uses the condition record number to store and retrieve information during processing (pricing, for example). Maximum length: 10.
Release status. The release status controls in which scenarios the condition records are found. If the status is set at 'B', for example, then the corresponding records are taken into account during a pricing simulation, but are not used in current documents.The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status for conditions. Maximum length: 1.
Scale value. A value that is part of a pricing scale. The value is an amount in a particular currency.
Scale Currency. Specifies a currency for a pricing scale in a condition record. If a pricing scale is based on a value instead of a quantity, you can specify a currency for the value. In the standard version of the SAP System, this field is only relevant in condition records for the following discounts:Price groupPrice group/Material pricing groupYou apply a price group discount to customers in a particular foreign country. When you create a condition record for this discount and enter values in the pricing scale, you can also enter the corresponding foreign currency. During pricing, the system then calculates discounts based on scale values in the foreign currency. The discount amount is then converted into the currency you are using in the sales document.After you enter a currency in this field and save the condition record, you cannot change the currency without deleting the record and creating it again. Maximum length: 5.
Condition scale quantity. Scale quantity (for example, number of pieces) to which a scale refers.
Condition Scale Unit of Measure. Unit of measure to which the quantity scale refers. Maximum length: 3.
Sequential number of the condition. The sequential number that uniquely identifies the condition if a condition supplement exists. If you have assigned a condition supplement to the condition, the system automatically assigns the number. Maximum length: 2.
Condition Table. Maximum length: 3.
Number of texts. Maximum length: 10.
Denominator for converting condition units to base units. The denominator of the conversion factor that the system uses to convert condition units into base units of measure. Many material processing functions, such as the creation of production requirements, may require that sales units are converted into base units of measure.You produce a soft-drink in gallons, but sell it in 1 pint bottles. The conversion factor looks like this:8 Pt <=> 1 GThe first number (the denominator) represents the sales units, in this case, pints. The second number (the numerator) represents the equivalent quantity of base units of measure, in this case, gallons.
Numerator for converting condition units to base units. The numerator of the conversion factor that the system uses to convert condition units into base units of measure. Many material processing functions, such as creating production requirements, may require that sales units are converted into base units.You store a soft drink in gallons, but sell it in 1 pint bottles. The conversion factor looks like this:8 Pt <=> 1 GThe first number (the denominator) represents the sales units, in this case, pints. The second number (the numerator) represents the equivalent quantity of base units, in this case, gallons.
Condition Type. The key that uniquely identifies the condition. The condition type indicates, for example, whether, during pricing, the system applies a price, a discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these pricing elements, there is a condition type defined in the system. Maximum length: 4.
Upper limit for the condition rate. Indicates, during document processing, whether a manually entered price exceeds the upper limit allowed for the corresponding condition record and/or the condition type. When you maintain a condition record, the system checks automatically whether the scale value exceeds the upper limit.
Valid To Date. Date indicating up to when an entry is valid.
Valid-From Date. Date indicating as of when an entry is valid.
Name of Person Who Created Object. Maximum length: 12.
Date on Which Record Was Created.
E Tag. Maximum length: 40.
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 incremental scale. Maximum length: 4.
Maximum condition value. Specifies the maximum condition value for this condition record. You use this field to limit the use of a particular condition record to a specified total value.You offer a customer a special discount on a certain product but want to limit this discount to a specified total amount. You enter the maximum amount (for example, 1000 USD) in this field. As you process orders that use this condition record, the system updates the cumulative value. When the maximum value is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative value for a particular condition record, you select Details -> Cumulative values in the overview screen of the condition record.
Maximum condition base value. Specifies the maximum condition base value for this condition record. You use this field to specify a maximum cumulative quantity, weight, or volume for a condition record.You offer a customer a special discount on a certain product but want to limit this discount to a specified total number of cases. You enter the maximum number of cases in this field. As you process orders that use this condition record, the system updates the cumulative quantity. When the maximum quantity is reached, the system automatically deactivates the condition record in subsequent orders.To see the current cumulative condition base value for a particular condition record, you select Extras -> Cumulative values in the overview screen of the condition record.
Minimum condition base value.
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.
Scale Basis Indicator. Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume. Maximum length: 1.
Scale number for pricing. Maximum length: 4.
Scale Type. Indicator that controls the validity of the scale value or percentage: From a certain quantity or value (base scale)Up to a certain quantity or value (to-scale)Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing. Maximum length: 1.
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 SlsPrcgCndnRecdValidity entity.
One-to-many navigation property to the SlsPrcgCndnRecordScale entity.
One-to-one navigation property to the SlsPrcgConditionRecord entity.
ETag version identifier accessor.
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 baseUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the cndnMaxNumberOfSalesOrders property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionAlternativeCurrency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionApplication property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionCalculationType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionExclusion property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionIsDeleted property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionLowerLimit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionQuantity property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionQuantityUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionRateValue property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionRateValueUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionRecord property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionReleaseStatus property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionScaleAmount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionScaleAmountCurrency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionScaleQuantity property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionScaleQuantityUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionSequentialNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionTable property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionTextId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionToBaseQtyDnmntr property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionToBaseQtyNmrtr property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionUpperLimit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionValidityEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the conditionValidityStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the createdByUser 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 eTag 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 incrementalScale property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the maximumConditionAmount property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the maximumConditionBasisValue property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the minimumConditionBasisValue 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 pricingScaleBasis property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the pricingScaleLine property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the pricingScaleType 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 toSlsPrcgCndnRecdValidity 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 toSlsPrcgCndnRecordScale 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-one navigation property toSlsPrcgConditionRecord for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the SlsPrcgCndnRecdSuplmnt entity.
Default url path for the according service.
Technical entity name for SlsPrcgCndnRecdSuplmnt.
All key fields of the SlsPrcgCndnRecdSuplmnt entity.
Mapping of all key field names to the respective static field property SlsPrcgCndnRecdSuplmnt.
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 SlsPrcgCndnRecdSuplmnt
.
A builder that constructs instances of entity type SlsPrcgCndnRecdSuplmnt
.
Returns a selectable object that allows the selection of custom field in a get request for the entity SlsPrcgCndnRecdSuplmnt
.
Name of the custom field to select
A builder that constructs instances of entity type SlsPrcgCndnRecdSuplmnt
.
Returns a request builder to construct requests for operations on the SlsPrcgCndnRecdSuplmnt
entity type.
A SlsPrcgCndnRecdSuplmnt
request builder.
This class represents the entity "A_SlsPrcgCndnRecdSuplmnt" of service "API_SLSPRICINGCONDITIONRECORD_SRV". This service is part of the following communication scenarios: Pricing Data Integration (SAP_COM_0294). See https://api.sap.com/api/API_SLSPRICINGCONDITIONRECORD_SRV for more information.