public static class FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder extends Object
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder iD(@Nullable String iD)
Original property name from the Odata EDM: ID
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder ledger(@Nullable String ledger)
Original property name from the Odata EDM: Ledger
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder planningCategory(@Nullable String planningCategory)
Original property name from the Odata EDM: PlanningCategory
You can create categories for different purposes, for example, for optimistic or pessimistic plan scenarios, for top-down or bottom-up planning, or any other purpose. You can also use plan categories to store budgets instead of plan data.
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder ledgerFiscalYear(@Nullable String ledgerFiscalYear)
Original property name from the Odata EDM: LedgerFiscalYear
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder financialTransactionType(@Nullable String financialTransactionType)
Original property name from the Odata EDM: FinancialTransactionType
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder functionalArea(@Nullable String functionalArea)
Original property name from the Odata EDM: FunctionalArea
The functional area is required in Funds Management in order to fulfill legal reporting requirements subdividing an organization into functions. You can use the functional area to map global aims and purposes, for example, public safety, town planning, and the expenditures of your organization.For more information on the functional area, see the Implementation Guide of Funds Management Government, section Functional Area in Funds Management Government.
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder segment(@Nullable String segment)
Original property name from the Odata EDM: Segment
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerCostCenter(@Nullable String partnerCostCenter)
Original property name from the Odata EDM: PartnerCostCenter
This cost center is credited with the amount of incurred costs using a cost element.
cost centers or orders.public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerProfitCenter(@Nullable String partnerProfitCenter)
Original property name from the Odata EDM: PartnerProfitCenter
In the case of the receiver of a service/delivery, the sending profit center is entered as the partner profit center and vice versa.
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerFunctionalArea(@Nullable String partnerFunctionalArea)
Original property name from the Odata EDM: PartnerFunctionalArea
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 FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerBusinessArea(@Nullable String partnerBusinessArea)
Original property name from the Odata EDM: PartnerBusinessArea
This relationship enables internal business volume to be eliminated at the business area level (as part of business area consolidation).
in connection with the business area with which the posting is made.public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerCompany(@Nullable String partnerCompany)
Original property name from the Odata EDM: PartnerCompany
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerSegment(@Nullable String partnerSegment)
Original property name from the Odata EDM: PartnerSegment
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder amountInTransactionCurrency(@Nullable BigDecimal amountInTransactionCurrency)
Original property name from the Odata EDM: AmountInTransactionCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder companyCodeCurrency(@Nullable String companyCodeCurrency)
Original property name from the Odata EDM: CompanyCodeCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder amountInCompanyCodeCurrency(@Nullable BigDecimal amountInCompanyCodeCurrency)
Original property name from the Odata EDM: AmountInCompanyCodeCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder globalCurrency(@Nullable String globalCurrency)
Original property name from the Odata EDM: GlobalCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder amountInGlobalCurrency(@Nullable BigDecimal amountInGlobalCurrency)
Original property name from the Odata EDM: AmountInGlobalCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder controllingObjectCurrency(@Nullable String controllingObjectCurrency)
Original property name from the Odata EDM: ControllingObjectCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder amountInObjectCurrency(@Nullable BigDecimal amountInObjectCurrency)
Original property name from the Odata EDM: AmountInObjectCurrency
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder costSourceUnit(@Nullable String costSourceUnit)
Original property name from the Odata EDM: CostSourceUnit
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder valuationQuantity(@Nullable BigDecimal valuationQuantity)
Original property name from the Odata EDM: ValuationQuantity
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder fiscalPeriod(@Nullable String fiscalPeriod)
Original property name from the Odata EDM: FiscalPeriod
Every business transaction is allocated to a fiscal period.Examples of period classifications:Per calendar month -> 12 fiscal periodsEvery 4 weeks -> 13 fiscal periodsWeekly -> 52 or 53 fiscal periods
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder fiscalYearVariant(@Nullable String fiscalYearVariant)
Original property name from the Odata EDM: FiscalYearVariant
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder fiscalYearPeriod(@Nullable String fiscalYearPeriod)
Original property name from the Odata EDM: FiscalYearPeriod
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder chartOfAccounts(@Nullable String chartOfAccounts)
Original property name from the Odata EDM: ChartOfAccounts
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder controllingDebitCreditCode(@Nullable String controllingDebitCreditCode)
Original property name from the Odata EDM: ControllingDebitCreditCode
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder project(@Nullable String project)
Original property name from the Odata EDM: Project
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerCompanyCode(@Nullable String partnerCompanyCode)
Original property name from the Odata EDM: PartnerCompanyCode
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder 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 FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerOrder(@Nullable String partnerOrder)
Original property name from the Odata EDM: PartnerOrder
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerCostCtrActivityType(@Nullable String partnerCostCtrActivityType)
Original property name from the Odata EDM: PartnerCostCtrActivityType
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerProject(@Nullable String partnerProject)
Original property name from the Odata EDM: PartnerProject
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder partnerWBSElement(@Nullable String partnerWBSElement)
Original property name from the Odata EDM: PartnerWBSElement
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder salesOrganization(@Nullable String salesOrganization)
Original property name from the Odata EDM: SalesOrganization
You can assign any number of distribution channels and divisions to a sales organization. A particular combination of sales organization, distribution channel, and division is known as a sales area.
sales organization may include legal liability for products and customer claims.public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder distributionChannel(@Nullable String distributionChannel)
Original property name from the Odata EDM: DistributionChannel
You can maintain information about customers and materials by sales organization and distribution channel. Within a sales organization you can deliver goods to a given customer through more than one distribution channel.You can assign a distribution channel to one or more sales organizations. If, for example, you have numerous sales organizations, each sales organization may use the "Wholesale" distribution channel.For each combination of sales organization and distribution channel, you can further assign one or more of the divisions that are defined for the sales organization. You can, for example, assign "Food" and "Non-food" divisions to the "Wholesale" distribution channel. A particular combination of sales organization, distribution channel, and division is known as a sales area.
wholesale, retail, or direct sales.public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder division(@Nullable String division)
Original property name from the Odata EDM: Division
A product or service is always assigned to just one division. From the point of view of sales and distribution, the use of divisions lets you organize your sales structure around groups of similar products or product lines. This allows the people in a division who process orders and service customers to specialize within a manageable area of expertise.If a sales organization sells food and non-food products through both retail and wholesaledistribution channels each distribution channel could then be further split into food and non-food divisions.
areas and the business areas for a material, product, or service.public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder soldMaterial(@Nullable String soldMaterial)
Original property name from the Odata EDM: SoldMaterial
This can differ from the material moved or service rendered, for example if the material consumed for a project differs from the product sold of the sales order related to the project.
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder materialGroup(@Nullable String materialGroup)
Original property name from the Odata EDM: MaterialGroup
This can differ from the material group of the material moved or service rendered, for example if the material consumed for a project differs from the product sold of the sales order related to the project.
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder customerSupplierCountry(@Nullable String customerSupplierCountry)
Original property name from the Odata EDM: CustomerSupplierCountry
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder customerSupplierIndustry(@Nullable String customerSupplierIndustry)
Original property name from the Odata EDM: CustomerSupplierIndustry
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder salesDistrict(@Nullable String salesDistrict)
Original property name from the Odata EDM: SalesDistrict
Each customer can be assigned to a sales district. You can use sales districts to apply pricing conditions. When you want to generate sales statistics, you can use sales districts as a selection criteria.The system can propose a value from the customer master record of the sold-to party. You can change the value manually in the document at the header or item level.
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder financialManagementArea(@Nullable String financialManagementArea)
Original property name from the Odata EDM: FinancialManagementArea
An FM area is an organizational unit which plans, controls and monitors funds and commitment budgets.
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder 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 FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder 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 FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder 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 FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder budgetProcess(@Nullable String budgetProcess)
Original property name from the Odata EDM: BudgetProcess
public FinPlanningEntryItemTP.FinPlanningEntryItemTPBuilder budgetingType(@Nullable String budgetingType)
Original property name from the Odata EDM: BudgetingType
The budget type relates to the plan category in the relevance of a budget subcategory.
public FinPlanningEntryItemTP build()
Copyright © 2019 SAP SE. All rights reserved.