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 "*".
Actual length (duration) of the WBS element.
Unit for duration of actual WBS element dates. Maximum length: 3.
Actual finish date of the WBS element.
Actual start date for the WBS element.
Applicant number. Maximum length: 8.
Applicant. Name of the applicant. Maximum length: 25.
Length (duration) of the basic dates in the WBS element.
Unit for duration of basic WBS element dates. Maximum length: 3.
WBS element: Basic finish date.
WBS element: Basic start date.
Billing Plan Number / Invoicing Plan Number. Maximum length: 10.
Business Area. Key that uniquely identifies a business area. Maximum length: 4.
Company Code. The company code is an organizational unit within financial accounting. Maximum length: 4.
Controlling Area. Uniquely identifies a controlling area. The controlling area is the highest organizational unit in Controlling.Whether controlling area and company code are in a 1:1 relationship or a 1:n relationship, the number of posting periods in both controlling area and company code(s) must be identical. However, special periods may vary. Maximum length: 4.
Object Class. Maximum length: 2.
Cost center to which costs are actually posted. When statistical postings are made to a WBS element, actual postings are also made to the cost center you have entered. This field is only used for statistical WBS elements. Maximum length: 10.
Cost Object. Term identifying the cost object ID. Cost objects are the activity units of business whose costs are assigned based on the cost origins. The R/3 System distinguishes between the following types of cost objects:Cost objects represented by a cost object IDCost objects represented by objects from other components, such as production orders or sales order itemsCost objects in the following areas are represented by cost object IDs:Activity-Based Costing (CO-OM-ABC)In Activity-Based Costing, overhead is first assigned to cost centers and then to business processes. From there, the overhead is assigned to cost objects as process costs.Costs for Intangible Goods and Services (CO-PC-OBJ)In Costs for Intangible Goods and Services, costs can be analyzed on general cost objects.Product Cost by Period (CO-PC-OBJ)In Product Cost by Period you can create a cost object hierarchy to record actual costs that cannot be recorded at the material or order level. You can distribute the costs assigned to the nodes of a cost object hierarchy directly to the individual objects in the lowest cost object nodes at period-end closing (for example, product cost collectors) or you can settle the costs directly from the cost object hierarchy to a price difference account.Product Cost Controlling Information System (CO-PC)You can create further cost object IDs in the Product Cost Controlling Information System for CO product groups. You can create a cost object ID for each group, and assign materials to the cost object ID. The costs of the assigned materials appear in summarized form in the information system by product group.You can use CO product groups for product drilldown reports.The cost object type determines which functions can be used with the cost object. Functions for cost object hierarchies are performed on the assumption that the given cost object indicates the top node of the hierarchy. Maximum length: 12.
Costing Sheet. Controls the calculation of overhead. You must store one costing sheet for each object for which the R/3 System is to determine overhead costs.For orders, you enter the costing sheet in the order master record.For overhead cost orders the costing sheet can be defaulted through a model order.For CO production orders without quantity structure the costing sheet can be defaulted through a planning profile.For production orders, process orders, produc cost collectors, maintenance orders, regular maintenance orders and service orders the costing sheet is defaulted through a valuation variant.The valuation variant is stored in the costing variant. You can store the costing variant as default value per order type and plant.For cost centers you enter the costing sheet in the master data.For buiness processes you enter the costing sheet in the master data.For projects you enter the costing sheet in the project profile.For materials the R/3 System selects the costing sheet through the valuation variant.For base object plannings, enter the costing sheet in the master data of the costing sheet.For cost object IDs the costing sheet is defaulted through the cost object profile.For cost and revenue carrying sales document items the costing sheet is defaulted through the requirements class. Maximum length: 6.
Costing Variant. Key that determines how a cost estimate is performed and valuated. Depending on the object being costed, either the functions of unit costing or product costing can be used.To calculate the costs of producing a material, you create a product cost estimate with or without a quantity structure.In a cost estimate with a quantity structure, the costing variant determines the following:Which dates are valid for the actual cost estimate and for exploding and valuating the quantity structureHow the BOMs and routings are selected to create the quantity structureWhich prices are selected to valuate the quantity structureHow overhead is calculatedYou create a unit cost estimate to cost the following objects:Materials (cost estimate without quantity structure)Materials (additive cost estimate)Production orders in ControllingInternal ordersWBS elementsSales documentsIn unit costing, the costing variant determines the following:Which prices are selected to valuate the individual costing itemsHow overhead is calculatedCosting variants are also used to calculate costs for the following objects:Production ordersNetworksMaintenance ordersProcess ordersSales document itemsAppropriation requestsAd hoc cost estimatesA costing variant is linked to the following control parameters:Costing typeValuation variantDate control (in costing with and without quantity structure)Quantity structure control (in product costing)Transfer control (in product costing). Maximum length: 4.
Name of Person Who Created Object. Maximum length: 12.
Date on Which Record Was Created.
WBS element currency. Costs and payments incurred in a WBS element are managed in controlling area currency and in the object currency for the WBS element. When you create a WBS element, the system defaults the currency entered in the project definition as the object currency. You can change the WBS element object currency in the organization data for the WBS element. However, you cannot change the object currency once costs and/or payments have been posted to the WBS element. When changing the WBS element object currency, you must note the following:If the controlling area and company code are managed in the same currency, you can stipulate a different object currency for the WBS element.When you are conducting cross-company code cost accounting for company codes with different company code currencies, you must always use the object currency as the object currency. You can only change the WBS element object currency indirectly, by changing the company code. Maximum length: 5.
Equipment Number. Number by which a piece of equipment can be clearly identified. Maximum length: 18.
Calendar. Maximum length: 2.
Forecasted length (duration) of the WBS element.
Unit for duration of WBS element planned dates. Maximum length: 3.
Forecast Finish Date of WBS Element.
Forecast Start Date of WBS Element.
1st user field for values (length 10,3) WBS element. User-defined field in which you can enter quantities with a length of up to 10 characters before the decimal point and three characters after it. The names (key words) for user-defined fields depend on the field key.
1st user defined field for value field unit - WBS element. User-defined field where you can maintain the quantity unit. The key words for the user-defined fields depend on the key word ID. Maximum length: 5.
2nd user field for values (length 10,3) -WBS element. User-defined field in which you can enter quantities with a length of up to 10 characters before the decimal point and three characters after it. The names (key words) for user-defined fields depend on the field key.
2nd user defined field for value field unit - WBS element. User-defined field where you can maintain the quantity unit. The key words for the user-defined fields depend on the key word ID. Maximum length: 5.
1st user field for 20 characters - WBS element-. User-defined field in which you can enter general information with a length of up to 20 characters. The names (key words) for user-defined fields depend on the field key. Maximum length: 20.
2nd user field 20 digits - WBS element. User-defined field in which you can enter general information with a length of up to 20 characters. The names (key words) for user-defined fields depend on the field key. Maximum length: 20.
3rd user-defined field 10 digits -WBS element. User-defined field in which you can enter general information with a length of up to 10 characters. The names (key words) for user-defined fields depend on the field key. Maximum length: 10.
4th user-defined field 10 digits -WBS element. User-defined field in which you can enter general information with a length of up to 10 characters. The names (key words) for user-defined fields depend on the field key. Maximum length: 10.
1st user field for date -WBS element. User-defined field in which you can enter a date. The names (key words) for user-defined fields depend on the field key.
2nd user field for date -WBS element. User-defined field in which you can enter a date. The names (key words) for user-defined fields depend on the field key.
1st user field for 'Ind. for evaluations' WBS elem. User-defined field in which you can enter a indicators for evaluations. The names (key words) for user-defined fields depend on the field key.
2nd user field for 'Indicator for eval.s' WBS elemnt. User-defined field in which you can enter a indicators for evaluations. The names (key words) for user-defined fields depend on the field key.
1st user-defined field for quantity(length 10,3) WBS element. User-defined field in which you can enter quantities with a length of up to 10 characters before the decimal point and three characters after it. The names (key words) for user-defined fields depend on the field key.Attention when changing the key fieldIf you have already entered values in the quantity field and then change the key field, the old value remain in the quantity field. The default values and units for formula parameters (if maintained) are not read from Customizing again.
1st user defined field for quantity field unit - WBS element. User-defined field where you can maintain the quantity unit. The key word for the user-defined fields depend on the Key word ID. Maximum length: 3.
2nd use field for quantity (length 10,3) WBS element. User-defined field in which you can enter quantities with a length of up to 10 characters before the decimal point and three characters after it. The names (key words) for user-defined fields depend on the field key.Attention when changing the key fieldIf you have already entered values in the quantity field and then change the key field, the old value remain in the quantity field. The default values and units for formula parameters (if maintained) are not read from Customizing again.
2nd user defined field for quantity field unit - WBS element. User-defined field where you can maintain quantity units. The key words for the user-defined fields depend on the Key word ID. Maximum length: 3.
Key word ID for user-defined fields. Key which determines the key words (field names) for user-defined fields. Maximum length: 7.
Functional Area. Structure criterion for an enterprise or government based on functional aspects. Use for Cost-of-Sales AccountingThe functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting. The following are examples of structure criteria:ManufacturingAdministrationSalesResearch and developmentUse for GovernmentThe functional area is needed for Funds Management to meet legal requirements for reporting with functional aspects. You can use the functional area to represent the global targets and goals (such as public safety or city development), in particular the expenses of your organization.Use in cost-of-sales accountingSee the documentation on Filling the Functional Area Field.For comprehensive information on cost-of-sales accounting and on the functional area, see the SAP Library under Accounting -> Financial Accounting -> General Ledger -> Cost-of-Sales Accounting.Use in governmentFor more information on the functional area, see the implementation Guide for Funds Management Government in the section Activate Account Assignment Elements. Maximum length: 16.
Functional Location. Label that uniquely identifies a functional location. If alternative labels exist for a functional location, you can define in your user profile which label should be displayed in this field. Maximum length: 40.
Valuation of Special Stock. Determines whether sales order stock or project stock is managed on a valuated or nonvaluated basis. In sales-order-related production and engineer-to-order production, you can use valuated stocks or nonvaluated stocks.If you use valuated sales order stock or valuated project stock, the quantity and value flow is the same as that of anonymous make-to-stock production.If you use nonvaluated sales order stock or nonvaluated project stock, you must carry out a results analysis in the course of period closing if you want to determine the stock values of finished and unfinished products.Enter M if you want to use valuated sales order stock or valuated project stock and it should be valuated separately from anonymous warehouse stock.Enter A if you want to use valuated sales order stock and it should be valuated together with anonymous warehouse stock.Leave the field blank if you want to use nonvaluated sales order stock or nonvaluated project stock.If you want to use valuated sales order stock and manage it separately from anonymous warehouse stock (entry M), please note the field Val. strategy.You can display valuated special stocks using report RM07MBWS.If you want to use valuated sales order stock and manage it together with anonymous warehouse stock (entry A), the valuated sales order stock is always valuated in the same way as material produced for anonymous warehouse stock. For materials valuated at a standard price. valuation is generally based on the standard cost estimate for the material. Maximum length: 1.
Investment Measure Profile. Investment profile Important control functions of the investment profile:Automatic creation of an asset under construction when you create an internal order or a work breakdown structure (WBS) elementAsset class for the creation of the asset under constructionAsset class for depreciation simulation. Maximum length: 6.
Deletion Indicator.
Joint Venture. A joint venture in the SAP System is a summarization of cost objects whose costs are split up among partners. A joint venture is usually lead by an operating authority, who is responsible for the costs incurred. At the end of a period, all of the costs incurred are split up and allocated to the partners involved.Joint ventures are created to keep costs as low as possible for the operating authority and the partners. This is achieved by distributing the costs incurred to the participants of the joint venture.In the oil industry, new drill-holes are seldomly controlled by the oil companies alone. Instead, contracts are made with other companies. The contract regulates the costs incurred. This enables the risks involved with an unsuccessful drill-hole to be spread out over several companies.Of course, the anticipated profits (from a rich drill-hole) are also distributed to the partners involved. However, the distribution of the profits is not carried out by the SAP Joint Venture Accounting solution. Maximum length: 6.
JIB/JIBE Class. Maximum length: 3.
Equity Type. Maximum length: 3.
Joint Venture Object Type. Maximum length: 4.
Recovery Indicator. In global companies that belong to joint ventures, incurred costs are usually shared among different recovery indicators which can then be dealt with in different ways using the periodic settlement program. You can define recovery indicators at three different levels:o Document typeYou can assign a recovery indicator to each document type for thecredit side and for the debit side. These recovery indicators areinternal recovery indicators and are defined in a separate systemtable.o Cost element (primary and secondary)o Cost objectWhen you make a posting in one of the feeder systems of the Joint Venture Accounting System, all three levels are evaluated in the sequence defined. The first recovery indicator found is transferred to the Joint Venture Accounting System.o Costs that are 100% allocableo Costs borne 100% by the operatoro Overheads applied by the operatoro Costs which exceed a contractually agreed price and cannot thereforebe allocatedo Costs already allocated. Maximum length: 2.
JIB/JIBE Subclass A. Maximum length: 5.
Language Key. The language key indicates
Date on which object was last changed.
Name of Person Who Changed Object. Maximum length: 12.
Latest scheduled finish date (Forecast).
Latest scheduled start date (forecast).
Location. Key that identifies the location. The location is subordinate entity in a plant. Maximum length: 10.
Overhead Key. Maximum length: 6.
Plant. Key uniquely identifying a plant. Maximum length: 4.
Priority. Use this key to specify the priority. Maximum length: 1.
Profit Center. Key which together with the controlling area uniquely identifies a profit center. Maximum length: 10.
Aggregation weight for POC (PS progress). Weighting for the aggregation of the percentages of completion. You can enter any number for the weighting.
Interest Profile for Project/Order Interest Calculation. The interest profile contains the rules governing the interest calculation for projects. The interest rate and update control are defined when you assign an interest indicator to the interest profile.You also use the profile to define the interest relevance of costs, revenues, and paymentss for the interest profile/interest indicator combination. Maximum length: 7.
Project (internal). Maximum length: 8.
Change Number. Number used to uniquely identify a change master record. If you make a change with reference to a change number, or create an object with a change number, the following functions are at your disposal:The system determines the validity conditionsThe conditions that the change is effective under can be defined in the change master record as follows:Changes with a date validity (valid-from date)Changes with parameter effectivity (for example: serial no. effectivity)Log of the changes madeDocumentation of the changesAssignment of a revision level to a change state of a material or documentRelease of changes for the different areas in the company. Maximum length: 12.
Reference Element PM/PS. Maximum length: 40.
Project type. Maximum length: 2.
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.
Controlling area of requesting cost center. Key of the controlling area to which the requesting cost center belongs. Maximum length: 4.
Requesting cost center. Maximum length: 10.
Responsible Cost Center Controlling Area. Key for the controlling area which is assigned to the cost center of the WBS element. Maximum length: 4.
Responsible Cost Center. Maximum length: 10.
Number of the Responsible Person (Project Manager). Maximum length: 8.
Name of responsible person (Project manager). Maximum length: 25.
Results Analysis Key. Key that defines the valuation of the order during period-end closing. How the results analysis key is used depends on the nature of the order.For orders with revenue (internal orders, sales orders, and projects), the results analysis key determines how results analysis is carried out.Results analysis is recommended in the following situations:When you are using a nonvaluated sales order stock or nonvaluated project stock and you want to valuate the inventories at the end of the periodWhen you are using a valuated sales order stock or valuated project stock and want to valuate goods that have been delivered but not yet invoiced, or when you want to create reserves automaticallyFor orders without reference to a sales order item or WBS element, the results analysis key determines how the work in process is calculated.The production type can be make-to-stock or mass production on the basis of sales orders. The work in process is calculated at the level of the production order, process order, or product cost collector.For capital investment measures, the results analysis key determines how the system calculates the values to be capitalized.For orders with revenue, costs may be incurred before any revenue is received. If you are using a nonvaluated sales order stock, results analysis enables you to report the costs as work in process. After the first revenue has been posted, you can calculate the cost of sales. If the calculated cost of sales is greater than the actual costs incurred to date, the system creates reserves for unrealized costs in the amount of the difference.No revenue is posted in CO for orders without reference to a sales order item. Each goods receipt for these orders is valuated. The work in process for these orders can be calculated with two different methods:Work in process at actual costsThe actual costs for production orders and process orders for which no delivery has taken place are reported as work in process. After a partial delivery, the difference between the debit of the order with actual costs and the credit of the order from goods receipts is reported as work in process. When the order is complete, this work in process is canceled. The difference between the debit and credit of the order is then interpreted by the system as a variance.In Product Cost by Order, the work in process is usually valuated at actual costs.A requirement for the valuation of work in process at actual costs is that the default rule PP1 (full settlement) must be specified in the order.Work in process at target costsA confirmation is made for each operation or at certain reporting points. The system uses the confirmations to determine the quantity of work in process. This quantity is valuated using the strategy sequence specified in the valuation variant for work in process and scrap.In Product Cost by Period, the work in process is always valuated at target costs.A requirement for the valuation of work in process at target costs is that the default rule PP2 (periodic settlement) must be specified in the order.See also: Check default values for order typesThe control parameters for results analysis, for the calculation of work in process, and for the calculation of the values to be capitalized are selected through the results analysis key in the order and a results analysis version. If you have not specified a results analysis key in the order, the order will not be included in the calculation of work in process during period-end closing.The control parameters for the valuation of work in process in Product Cost by Period are defined in Customizing for Product Cost by Period.See also: Define valuation variant for WIP and scrap (target costs). Maximum length: 6.
Earliest Finish Date.
Earliest scheduled start date (Basic). Scheduled start date (basic dates).
Latest scheduled start date (basic).
Earliest scheduled finish date (forecast).
Scheduled start date (Forecast).
Latest scheduled finish date (basic).
Tax Jurisdiction. Maximum length: 15.
Tentative actual finish date for WBS element.
Tentative actual start date for WBS element.
ETag version identifier accessor.
WBS Element Name. Maximum length: 40.
Work Breakdown Structure Element (WBS Element). Key identifying a WBS element. Maximum length: 24.
Indicator: There are activities for the WBS elements.
Level in Project Hierarchy.
WBS Element. Key identifying a WBS element. Maximum length: 8.
Indicator: Billing element. This indicator defines the WBS element as a billing element. If you want to maintain a billing plan for a WBS element, you must set this indicator. If you have maintained a billing plan for the WBS element, you cannot change this indicator.
Indicator: Grouping WBS element. This indicator determines whether a WBS element is used as a grouping WBS element. The indicator has two characteristic values:1 Grouping WBS element for all materials2 Grouping WBS element for selected MRP groupsYou use value 1, if the grouping WBS element should be valid for all material components that are allocated to a WBS element, which is assigned to this grouping WBS element.You use value 2, if you want to have different grouping WBS elements for the material components in a WBS element. This could be the case for instance, if you plan electrical and mechanical parts seperately.Selection of the valid grouping WBS elements is on the basis of the MRP group and the plant for the relevant material.If you have set the Automatic requirements grouping indicator in the project definition, you can only have one WBS element in the project that is the grouping WBS element for all materials (value 1). Maximum length: 1.
Indicator: Planning element. This indicator defines the WBS element as a planning element. If the Planning element indicator has been set in Create/change plan profile, you can only plan costs on those WBS elements that have been designated planning elements.
Indicator: WBS element used in project summarization. Use this indicator to specify that the values for the WBS elements are included in the project summarization.
Object Number. An object (order, project, cost center, ...) is identified uniquely by its object number within a client. The object number is used in tables, which cover all objects, for instance in status administration, cost collection. Maximum length: 22.
WBS element short identification. Short ID of the WBS element. The short ID enables you to find WBS elements by a short string, or to display WBS elements in lists. Once you have defined a short ID for the WBS element, the system will propose it and you can change it, if necessary.For more information on how the system determines the short ID, refer toMask short ID in the project definition. Maximum length: 16.
Indicator: Actual dates from the activities.
Indicator: Actual dates set manually.
Indicator: Basic dates set manually.
Indicator: Expected dates from the activities.
Indicator: Forecast dates set manually.
Indicator: Account assignment element.
Indicator 'Integrated Planning' for Cost Object Category. This indicator determines, if a cost object plays a role in integrated planning or not. This is defined according to cost object categories in customizing. The costs associated with an integrated planning cost object/ activity inputs are updated if 'integrated planning' is activated in the version: maintain plan versions .The planning data is then passed on to the profit center and the general ledger.
Statistical WBS element. Use this indicator to specify whether a WBS element is only for statistical purposes or whether it may carry actual costs. Costs and if required revenues are carried on such a WBS element for statistical purposes. This means that:For business transactions that lead to actual costs/revenues another object is required to carry the actual costs.A statistical WBS element cannot be settled.Additional Restriction:You cannot settle overheads on statistical WBS elements.
Static representation of the actualDuration property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the actualDurationUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the actualEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the actualStartDate 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 applicantCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the applicantName property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the basicDuration property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the basicDurationUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the basicEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the basicStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the billingPlan property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the businessArea 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 controllingArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the controllingObjectClass property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the costingSheet property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the costingVariant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the costCenter property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the costObject 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 currency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the equipment property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the factoryCalendar property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the forecastedDuration property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the forecastedDurationUnit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the forecastedEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the forecastedStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAmount1 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAmount1Currency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAmount2 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAmount2Currency property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAttribute01 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAttribute02 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAttribute03 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedAttribute04 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedDate1 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedDate2 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedIndicator1 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedIndicator2 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedQuantity1 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedQuantity1Unit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedQuantity2 property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedQuantity2Unit property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the freeDefinedTableFieldSemantic property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the functionalArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the functionalLocation property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the inventorySpecialStockValnType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the investmentProfile property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the isMarkedForDeletion property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the jointVenture property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the jointVentureClass property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the jointVentureEquityType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the jointVentureObjectType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the jointVentureRecoveryCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the jointVentureSubClass property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the language property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the lastChangedByUser 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 latestSchedldFcstdEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the latestSchedldFcstdStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the location property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the overheadCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the plant property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the priorityCode property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the profitCenter property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the progressAnlysAggregationWeight property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the projectInternalId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the projectObjectChangeNumber property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the projectObjectReferenceElement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the projectType property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the projInterestCalcProfile property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the reqgCostCenterControllingArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the requestingCostCenter property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the responsibleCostCenter property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the responsiblePerson property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the responsiblePersonName property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the respCostCenterControllingArea property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the resultAnalysisInternalId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedldBasicEarliestEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedldBasicEarliestStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedldBasicLatestStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedldFcstdEarliestEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the schedldFcstdEarliestStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the scheduledBasicLatestEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the taxJurisdiction property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the tentativeActualEndDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the tentativeActualStartDate property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsDescription property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementHasActivities property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementHierarchyLevel property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementInternalId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementIsBillingElement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementIsGroupingWbsElement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementIsPlanningElement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementIsUsedInProjSmmry property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementObject property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElementShortId property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsElmntHasActualDateFromActy property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsHasActualDateSetManually property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsHasBasicDateManuallySet property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsHasFcstdDateFromActivity property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsHasFcstdDateSetManually property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsIsAccountAssignmentElement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsIsMarkedForIntegratedPlng property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
Static representation of the wbsIsStatisticalWbsElement property for query construction. Use to reference this property in query operations such as 'select' in the fluent request API.
All fields of the WbsElementInternalId entity.
Default url path for the according service.
Technical entity name for WbsElementInternalId.
All key fields of the WbsElementInternalId entity.
Mapping of all key field names to the respective static field property WbsElementInternalId.
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 WbsElementInternalId.
A builder that constructs instances of entity type WbsElementInternalId.
Returns a selectable object that allows the selection of custom field in a get request for the entity WbsElementInternalId.
Name of the custom field to select
A builder that constructs instances of entity type WbsElementInternalId.
Returns a request builder to construct requests for operations on the WbsElementInternalId entity type.
A WbsElementInternalId request builder.
This class represents the entity "WBSElementInternalID" of service "API_GRMASTERDATA_SRV". This service is part of the following communication scenarios: Finance - Cloud Consolidation Master Data for Group Reporting Integration (SAP_COM_0336), Finance - Cloud Consolidation Data Collection Integration (SAP_COM_0241). See https://api.sap.com/api/API_GRMASTERDATA_SRV for more information.