public static class WBSElementInternalID.WBSElementInternalIDBuilder extends Object
@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementInternalID(@Nullable String wBSElementInternalID)
Original property name from the Odata EDM: WBSElementInternalID
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder projectInternalID(@Nullable String projectInternalID)
Original property name from the Odata EDM: ProjectInternalID
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSDescription(@Nullable String wBSDescription)
Original property name from the Odata EDM: WBSDescription
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementObject(@Nullable String wBSElementObject)
Original property name from the Odata EDM: WBSElementObject
The object number is used in tables, which cover all objects, for instance in status administration, cost collection.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder lastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder responsiblePerson(@Nullable String responsiblePerson)
Original property name from the Odata EDM: ResponsiblePerson
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder responsiblePersonName(@Nullable String responsiblePersonName)
Original property name from the Odata EDM: ResponsiblePersonName
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder applicantCode(@Nullable String applicantCode)
Original property name from the Odata EDM: ApplicantCode
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder applicantName(@Nullable String applicantName)
Original property name from the Odata EDM: ApplicantName
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder projectType(@Nullable String projectType)
Original property name from the Odata EDM: ProjectType
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementIsPlanningElement(@Nullable Boolean wBSElementIsPlanningElement)
Original property name from the Odata EDM: WBSElementIsPlanningElement
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSIsAccountAssignmentElement(@Nullable Boolean wBSIsAccountAssignmentElement)
Original property name from the Odata EDM: WBSIsAccountAssignmentElement
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementIsBillingElement(@Nullable Boolean wBSElementIsBillingElement)
Original property name from the Odata EDM: WBSElementIsBillingElement
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder costingSheet(@Nullable String costingSheet)
Original property name from the Odata EDM: CostingSheet
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder requestingCostCenter(@Nullable String requestingCostCenter)
Original property name from the Odata EDM: RequestingCostCenter
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder responsibleCostCenter(@Nullable String responsibleCostCenter)
Original property name from the Odata EDM: ResponsibleCostCenter
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder factoryCalendar(@Nullable String factoryCalendar)
Original property name from the Odata EDM: FactoryCalendar
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder priorityCode(@Nullable String priorityCode)
Original property name from the Odata EDM: PriorityCode
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder currency(@Nullable String currency)
Original property name from the Odata EDM: Currency
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.
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.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedTableFieldSemantic(@Nullable String freeDefinedTableFieldSemantic)
Original property name from the Odata EDM: FreeDefinedTableFieldSemantic
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSIsStatisticalWBSElement(@Nullable Boolean wBSIsStatisticalWBSElement)
Original property name from the Odata EDM: WBSIsStatisticalWBSElement
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.
carry actual costs.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder taxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSIsMarkedForIntegratedPlng(@Nullable Boolean wBSIsMarkedForIntegratedPlng)
Original property name from the Odata EDM: WBSIsMarkedForIntegratedPlng
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.
according to cost object categories in customizing.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder functionalArea(@Nullable String functionalArea)
Original property name from the Odata EDM: FunctionalArea
Use for Cost of Sales AccountingThe functional area is required to create a profit and loss statement in Financial Accounting using cost of sales accounting. The following are examples of structure criteria:ManufacturingAdministrationSalesResearch & 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 more information about cost of sales accounting and functional areas, see the SAP Library under Financials -> Financial Accounting -> General Ledger Accounting -> Cost of Sales AccountingUse in GovernmentFor more information on functional areas, see the Implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder location(@Nullable String location)
Original property name from the Odata EDM: Location
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder equipment(@Nullable String equipment)
Original property name from the Odata EDM: Equipment
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder functionalLocation(@Nullable String functionalLocation)
Original property name from the Odata EDM: FunctionalLocation
If alternative labels exist for a functional location, you can define in your user profile which label should be displayed in this field.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder projectObjectChangeNumber(@Nullable String projectObjectChangeNumber)
Original property name from the Odata EDM: ProjectObjectChangeNumber
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
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder projectObjectReferenceElement(@Nullable String projectObjectReferenceElement)
Original property name from the Odata EDM: ProjectObjectReferenceElement
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder projInterestCalcProfile(@Nullable String projInterestCalcProfile)
Original property name from the Odata EDM: ProjInterestCalcProfile
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder investmentProfile(@Nullable String investmentProfile)
Original property name from the Odata EDM: InvestmentProfile
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
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder basicStartDate(@Nullable LocalDateTime basicStartDate)
Original property name from the Odata EDM: BasicStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder forecastedStartDate(@Nullable LocalDateTime forecastedStartDate)
Original property name from the Odata EDM: ForecastedStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder actualStartDate(@Nullable LocalDateTime actualStartDate)
Original property name from the Odata EDM: ActualStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder basicEndDate(@Nullable LocalDateTime basicEndDate)
Original property name from the Odata EDM: BasicEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder forecastedEndDate(@Nullable LocalDateTime forecastedEndDate)
Original property name from the Odata EDM: ForecastedEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder actualEndDate(@Nullable LocalDateTime actualEndDate)
Original property name from the Odata EDM: ActualEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder actualDurationUnit(@Nullable String actualDurationUnit)
Original property name from the Odata EDM: ActualDurationUnit
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder forecastedDurationUnit(@Nullable String forecastedDurationUnit)
Original property name from the Odata EDM: ForecastedDurationUnit
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder basicDurationUnit(@Nullable String basicDurationUnit)
Original property name from the Odata EDM: BasicDurationUnit
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder basicDuration(@Nullable BigDecimal basicDuration)
Original property name from the Odata EDM: BasicDuration
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder forecastedDuration(@Nullable BigDecimal forecastedDuration)
Original property name from the Odata EDM: ForecastedDuration
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder actualDuration(@Nullable BigDecimal actualDuration)
Original property name from the Odata EDM: ActualDuration
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder schedldBasicEarliestStartDate(@Nullable LocalDateTime schedldBasicEarliestStartDate)
Original property name from the Odata EDM: SchedldBasicEarliestStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder scheduledBasicLatestEndDate(@Nullable LocalDateTime scheduledBasicLatestEndDate)
Original property name from the Odata EDM: ScheduledBasicLatestEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder schedldFcstdEarliestStartDate(@Nullable LocalDateTime schedldFcstdEarliestStartDate)
Original property name from the Odata EDM: SchedldFcstdEarliestStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder latestSchedldFcstdEndDate(@Nullable LocalDateTime latestSchedldFcstdEndDate)
Original property name from the Odata EDM: LatestSchedldFcstdEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder tentativeActualStartDate(@Nullable LocalDateTime tentativeActualStartDate)
Original property name from the Odata EDM: TentativeActualStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder tentativeActualEndDate(@Nullable LocalDateTime tentativeActualEndDate)
Original property name from the Odata EDM: TentativeActualEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder schedldBasicLatestStartDate(@Nullable LocalDateTime schedldBasicLatestStartDate)
Original property name from the Odata EDM: SchedldBasicLatestStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder schedldBasicEarliestEndDate(@Nullable LocalDateTime schedldBasicEarliestEndDate)
Original property name from the Odata EDM: SchedldBasicEarliestEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder latestSchedldFcstdStartDate(@Nullable LocalDateTime latestSchedldFcstdStartDate)
Original property name from the Odata EDM: LatestSchedldFcstdStartDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder schedldFcstdEarliestEndDate(@Nullable LocalDateTime schedldFcstdEarliestEndDate)
Original property name from the Odata EDM: SchedldFcstdEarliestEndDate
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementHierarchyLevel(@Nullable Short wBSElementHierarchyLevel)
Original property name from the Odata EDM: WBSElementHierarchyLevel
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder overheadCode(@Nullable String overheadCode)
Original property name from the Odata EDM: OverheadCode
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder resultAnalysisInternalID(@Nullable String resultAnalysisInternalID)
Original property name from the Odata EDM: ResultAnalysisInternalID
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)
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder progressAnlysAggregationWeight(@Nullable BigDecimal progressAnlysAggregationWeight)
Original property name from the Odata EDM: ProgressAnlysAggregationWeight
You can enter any number for the weighting.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementShortID(@Nullable String wBSElementShortID)
Original property name from the Odata EDM: WBSElementShortID
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder reqgCostCenterControllingArea(@Nullable String reqgCostCenterControllingArea)
Original property name from the Odata EDM: ReqgCostCenterControllingArea
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder respCostCenterControllingArea(@Nullable String respCostCenterControllingArea)
Original property name from the Odata EDM: RespCostCenterControllingArea
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder language(@Nullable String language)
Original property name from the Odata EDM: Language
- the language in which texts are displayed,- the language in which you enter texts,- the language in which the system prints texts.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
This field is only used for statistical WBS elements.
have entered.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder costObject(@Nullable String costObject)
Original property name from the Odata EDM: CostObject
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementIsUsedInProjSmmry(@Nullable Boolean wBSElementIsUsedInProjSmmry)
Original property name from the Odata EDM: WBSElementIsUsedInProjSmmry
summarization.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder isMarkedForDeletion(@Nullable Boolean isMarkedForDeletion)
Original property name from the Odata EDM: IsMarkedForDeletion
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder inventorySpecialStockValnType(@Nullable String inventorySpecialStockValnType)
Original property name from the Odata EDM: InventorySpecialStockValnType
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.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder billingPlan(@Nullable String billingPlan)
Original property name from the Odata EDM: BillingPlan
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementIsGroupingWBSElement(@Nullable String wBSElementIsGroupingWBSElement)
Original property name from the Odata EDM: WBSElementIsGroupingWBSElement
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).
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder costingVariant(@Nullable String costingVariant)
Original property name from the Odata EDM: CostingVariant
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)
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder jointVenture(@Nullable String jointVenture)
Original property name from the Odata EDM: JointVenture
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.
partners.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder jointVentureRecoveryCode(@Nullable String jointVentureRecoveryCode)
Original property name from the Odata EDM: JointVentureRecoveryCode
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
recovery indicators which can then be dealt with in different ways using the periodic settlement program.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder jointVentureEquityType(@Nullable String jointVentureEquityType)
Original property name from the Odata EDM: JointVentureEquityType
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder jointVentureObjectType(@Nullable String jointVentureObjectType)
Original property name from the Odata EDM: JointVentureObjectType
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder jointVentureClass(@Nullable String jointVentureClass)
Original property name from the Odata EDM: JointVentureClass
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder jointVentureSubClass(@Nullable String jointVentureSubClass)
Original property name from the Odata EDM: JointVentureSubClass
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElementHasActivities(@Nullable Boolean wBSElementHasActivities)
Original property name from the Odata EDM: WBSElementHasActivities
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSHasFcstdDateFromActivity(@Nullable Boolean wBSHasFcstdDateFromActivity)
Original property name from the Odata EDM: WBSHasFcstdDateFromActivity
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSHasFcstdDateSetManually(@Nullable Boolean wBSHasFcstdDateSetManually)
Original property name from the Odata EDM: WBSHasFcstdDateSetManually
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSHasBasicDateManuallySet(@Nullable Boolean wBSHasBasicDateManuallySet)
Original property name from the Odata EDM: WBSHasBasicDateManuallySet
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSHasActualDateSetManually(@Nullable Boolean wBSHasActualDateSetManually)
Original property name from the Odata EDM: WBSHasActualDateSetManually
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder wBSElmntHasActualDateFromActy(@Nullable Boolean wBSElmntHasActualDateFromActy)
Original property name from the Odata EDM: WBSElmntHasActualDateFromActy
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder controllingObjectClass(@Nullable String controllingObjectClass)
Original property name from the Odata EDM: ControllingObjectClass
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAttribute01(@Nullable String freeDefinedAttribute01)
Original property name from the Odata EDM: FreeDefinedAttribute01
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAttribute02(@Nullable String freeDefinedAttribute02)
Original property name from the Odata EDM: FreeDefinedAttribute02
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAttribute03(@Nullable String freeDefinedAttribute03)
Original property name from the Odata EDM: FreeDefinedAttribute03
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAttribute04(@Nullable String freeDefinedAttribute04)
Original property name from the Odata EDM: FreeDefinedAttribute04
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedQuantity1(@Nullable BigDecimal freeDefinedQuantity1)
Original property name from the Odata EDM: FreeDefinedQuantity1
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.
decimal point and three characters after it.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedQuantity1Unit(@Nullable String freeDefinedQuantity1Unit)
Original property name from the Odata EDM: FreeDefinedQuantity1Unit
The key word for the user-defined fields depend on the Key word ID
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedQuantity2(@Nullable BigDecimal freeDefinedQuantity2)
Original property name from the Odata EDM: FreeDefinedQuantity2
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.
decimal point and three characters after it.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedQuantity2Unit(@Nullable String freeDefinedQuantity2Unit)
Original property name from the Odata EDM: FreeDefinedQuantity2Unit
The key words for the user-defined fields depend on the Key word ID
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAmount1(@Nullable BigDecimal freeDefinedAmount1)
Original property name from the Odata EDM: FreeDefinedAmount1
The names (key words) for user-defined fields depend on the field key.
decimal point and three characters after it.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAmount1Currency(@Nullable String freeDefinedAmount1Currency)
Original property name from the Odata EDM: FreeDefinedAmount1Currency
The key words for the user-defined fields depend on the key word ID
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAmount2(@Nullable BigDecimal freeDefinedAmount2)
Original property name from the Odata EDM: FreeDefinedAmount2
The names (key words) for user-defined fields depend on the field key.
decimal point and three characters after it.this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedAmount2Currency(@Nullable String freeDefinedAmount2Currency)
Original property name from the Odata EDM: FreeDefinedAmount2Currency
The key words for the user-defined fields depend on the key word ID
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedDate1(@Nullable LocalDateTime freeDefinedDate1)
Original property name from the Odata EDM: FreeDefinedDate1
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedDate2(@Nullable LocalDateTime freeDefinedDate2)
Original property name from the Odata EDM: FreeDefinedDate2
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedIndicator1(@Nullable Boolean freeDefinedIndicator1)
Original property name from the Odata EDM: FreeDefinedIndicator1
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID.WBSElementInternalIDBuilder freeDefinedIndicator2(@Nullable Boolean freeDefinedIndicator2)
Original property name from the Odata EDM: FreeDefinedIndicator2
The names (key words) for user-defined fields depend on the field key.
this
.@Nonnull public WBSElementInternalID build()
Copyright © 2020 SAP SE. All rights reserved.