public static class PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder extends Object
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder purchaseOrder(@Nullable String purchaseOrder)
Original property name from the Odata EDM: PurchaseOrder
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder purchaseOrderItem(@Nullable String purchaseOrderItem)
Original property name from the Odata EDM: PurchaseOrderItem
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder accountAssignmentNumber(@Nullable String accountAssignmentNumber)
Original property name from the Odata EDM: AccountAssignmentNumber
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder isDeleted(@Nullable Boolean isDeleted)
Original property name from the Odata EDM: IsDeleted
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder quantity(@Nullable BigDecimal quantity)
Original property name from the Odata EDM: Quantity
The quantity entered determines which portion of the costs you wish to distribute to this account assignment item.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder multipleAcctAssgmtDistrPercent(@Nullable BigDecimal multipleAcctAssgmtDistrPercent)
Original property name from the Odata EDM: MultipleAcctAssgmtDistrPercent
The percentage entered determines what percentage of the costs are to be distributed to this account assignment item.The total of the percentages must equal 100%.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder purgDocNetAmount(@Nullable BigDecimal purgDocNetAmount)
Original property name from the Odata EDM: PurgDocNetAmount
Order value = order quantity X order price.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder salesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder salesOrderItem(@Nullable String salesOrderItem)
Original property name from the Odata EDM: SalesOrderItem
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder salesOrderScheduleLine(@Nullable String salesOrderScheduleLine)
Original property name from the Odata EDM: SalesOrderScheduleLine
When an item has more than one schedule line, the system automatically assigns a unique number to each line. The number is displayed in the details screens for schedule lines.The schedule line number serves internal purposes and does not, for example, determine the sequence of schedule lines in the overview screen. The schedule lines on the overview screen are sorted by date.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder masterFixedAsset(@Nullable String masterFixedAsset)
Original property name from the Odata EDM: MasterFixedAsset
Accounting.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder fixedAsset(@Nullable String fixedAsset)
Original property name from the Odata EDM: FixedAsset
Using the asset sub-number, you can:Provide for separate management of later acquisitions to assets.Represent complex fixed assets with their component parts.In contrast to the main asset number, the asset sub-number must be numerical.
Accounting.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder goodsRecipientName(@Nullable String goodsRecipientName)
Original property name from the Odata EDM: GoodsRecipientName
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder unloadingPointName(@Nullable String unloadingPointName)
Original property name from the Odata EDM: UnloadingPointName
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder 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.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder 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.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder projectNetwork(@Nullable String projectNetwork)
Original property name from the Odata EDM: ProjectNetwork
Numbers are used to differentiate these project structures.When you specify a network, for example, when you are entering attendances, you can define that the network is debited when the sender cost center is credited.Use the possible entries pushbutton to select the network number for the required project structure.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder realEstateObject(@Nullable String realEstateObject)
Original property name from the Odata EDM: RealEstateObject
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder partnerAccountNumber(@Nullable String partnerAccountNumber)
Original property name from the Odata EDM: PartnerAccountNumber
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder commitmentItem(@Nullable String commitmentItem)
Original property name from the Odata EDM: CommitmentItem
assigning budget.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder 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.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder fundsCenter(@Nullable String fundsCenter)
Original property name from the Odata EDM: FundsCenter
are assigning budget.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder fund(@Nullable String fund)
Original property name from the Odata EDM: Fund
If you assign the budget to a fund, you can obtain a detailed list of origin for the amounts involved.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder 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 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.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder settlementReferenceDate(@Nullable LocalDateTime settlementReferenceDate)
Original property name from the Odata EDM: SettlementReferenceDate
have to enter the reference date when making postings on settlement units.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder taxCode(@Nullable String taxCode)
Original property name from the Odata EDM: TaxCode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
the tax authorities.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder taxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
authorities you must pay your taxes. It is always the city to which the goods are supplied.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder costCtrActivityType(@Nullable String costCtrActivityType)
Original property name from the Odata EDM: CostCtrActivityType
Activity types describe the activity produced by a cost center and are measured in units of time or quantity.In activity type planning, control data determines whether the activity price for evaluation of the activity type is manually set or is derived iteratively through activity price calculation.
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder businessProcess(@Nullable String businessProcess)
Original property name from the Odata EDM: BusinessProcess
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder earmarkedFundsDocument(@Nullable String earmarkedFundsDocument)
Original property name from the Odata EDM: EarmarkedFundsDocument
public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder grantID(@Nullable String grantID)
Original property name from the Odata EDM: GrantID
A grant may be for any purpose and cover all or only part of the costs of the project in question. You must enter a grant type for each grant you create in Grants Management (GM).The grant as an object has a finite lifecycle, divided into stages. Each stage is represented in the GM solution by a system status. The following are the stages of a grant's lifecycle:Initial DraftThis is the first stage of a grant. It is a working copy that can be modified as many times as needed.ProposalWhen the initial draft becomes a formal and complete document, it becomes a proposal.ApplicationWhen a proposal is routed to the sponsor for approval, it becomes an application. This application might contain changes in the budget or other adjustments.AwardIf the sponsor approves an application, an award is created. This is the real operative stage of a grant. The creation and consumption of the grant's budget occurs at this stage. This stage also represents the binding contract between the sponsor and the grantee.ClosingWhen an award is expiring, a phase of closing is established. Only restricted operations can be performed in this stage.ClosedThis stage defines an expired and closed grant. No further operations are allowed except archiving.
order to carry out a public purpose of support or stimulation in which the sponsor does not expect to be substantially involved.public PurOrdAccountAssignment.PurOrdAccountAssignmentBuilder budgetPeriod(@Nullable String budgetPeriod)
Original property name from the Odata EDM: BudgetPeriod
During the budget period, the organization may commit, obligate, and encumber funds (terminology varies). After it, the organization may only post follow-on documents.The budget period always works together with the fund account assignment element in Funds Management (FM).Budget Period A: 2000-2010Budget Period B: 2005-2015The actuals and commitments recorded then are differentiated by the period of time on which authority was granted to a particular fund.Fund F1 Budget Period: AFund F2 Budget Period: AFund F2 Budget Period: B
public PurOrdAccountAssignment build()
Copyright © 2019 SAP SE. All rights reserved.