public static final class FinPlanningEntryItem.FinPlanningEntryItemBuilder extends Object
@Nonnull public FinPlanningEntryItem.FinPlanningEntryItemBuilder companyCode(CompanyCode value)
value
- The CompanyCode to build this FinPlanningEntryItem with.@Nonnull public FinPlanningEntryItem.FinPlanningEntryItemBuilder companyCode(String value)
Original property name from the Odata EDM: CompanyCode
value
- The companyCode to build this FinPlanningEntryItem with.@Nonnull public FinPlanningEntryItem.FinPlanningEntryItemBuilder currentCostCenter(CostCenter value)
value
- The CostCenter to build this FinPlanningEntryItem with.@Nonnull public FinPlanningEntryItem.FinPlanningEntryItemBuilder currentProfitCenter(ProfitCenter value)
value
- The ProfitCenter to build this FinPlanningEntryItem with.public FinPlanningEntryItem.FinPlanningEntryItemBuilder iD(@Nullable String iD)
Original property name from the Odata EDM: ID
public FinPlanningEntryItem.FinPlanningEntryItemBuilder ledger(@Nullable String ledger)
Original property name from the Odata EDM: Ledger
public FinPlanningEntryItem.FinPlanningEntryItemBuilder ledgerName(@Nullable String ledgerName)
Original property name from the Odata EDM: LedgerName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder planningCategory(@Nullable String planningCategory)
Original property name from the Odata EDM: PlanningCategory
Categories from SAP Business Planning & Consolidation are mapped in Real-Time Consolidation to consolidation versions. This mapping is defined in the Model transaction (RTCMD) under the Version tab.
public FinPlanningEntryItem.FinPlanningEntryItemBuilder ledgerFiscalYear(@Nullable String ledgerFiscalYear)
Original property name from the Odata EDM: LedgerFiscalYear
public FinPlanningEntryItem.FinPlanningEntryItemBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
public FinPlanningEntryItem.FinPlanningEntryItemBuilder gLAccountName(@Nullable String gLAccountName)
Original property name from the Odata EDM: GLAccountName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder companyCodeName(@Nullable String companyCodeName)
Original property name from the Odata EDM: CompanyCodeName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public FinPlanningEntryItem.FinPlanningEntryItemBuilder costCenterName(@Nullable String costCenterName)
Original property name from the Odata EDM: CostCenterName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
public FinPlanningEntryItem.FinPlanningEntryItemBuilder profitCenterName(@Nullable String profitCenterName)
Original property name from the Odata EDM: ProfitCenterName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder functionalAreaName(@Nullable String functionalAreaName)
Original property name from the Odata EDM: FunctionalAreaName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
public FinPlanningEntryItem.FinPlanningEntryItemBuilder businessAreaName(@Nullable String businessAreaName)
Original property name from the Odata EDM: BusinessAreaName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
public FinPlanningEntryItem.FinPlanningEntryItemBuilder controllingAreaName(@Nullable String controllingAreaName)
Original property name from the Odata EDM: ControllingAreaName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder segment(@Nullable String segment)
Original property name from the Odata EDM: Segment
public FinPlanningEntryItem.FinPlanningEntryItemBuilder segmentName(@Nullable String segmentName)
Original property name from the Odata EDM: SegmentName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerCostCenterName(@Nullable String partnerCostCenterName)
Original property name from the Odata EDM: PartnerCostCenterName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerProfitCenterName(@Nullable String partnerProfitCenterName)
Original property name from the Odata EDM: PartnerProfitCenterName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerFunctionalArea(@Nullable String partnerFunctionalArea)
Original property name from the Odata EDM: PartnerFunctionalArea
Use for Cost-of-Sales Accounting The 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: Manufacturing Administration Sales Research and development Use for Government The 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 accounting See 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 government For more information on the functional area, see the implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerFunctionalAreaName(@Nullable String partnerFunctionalAreaName)
Original property name from the Odata EDM: PartnerFunctionalAreaName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerBusinessAreaName(@Nullable String partnerBusinessAreaName)
Original property name from the Odata EDM: PartnerBusinessAreaName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerCompany(@Nullable String partnerCompany)
Original property name from the Odata EDM: PartnerCompany
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerCompanyName(@Nullable String partnerCompanyName)
Original property name from the Odata EDM: PartnerCompanyName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerSegment(@Nullable String partnerSegment)
Original property name from the Odata EDM: PartnerSegment
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerSegmentName(@Nullable String partnerSegmentName)
Original property name from the Odata EDM: PartnerSegmentName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
public FinPlanningEntryItem.FinPlanningEntryItemBuilder amountInTransactionCurrency(@Nullable BigDecimal amountInTransactionCurrency)
Original property name from the Odata EDM: AmountInTransactionCurrency
public FinPlanningEntryItem.FinPlanningEntryItemBuilder companyCodeCurrency(@Nullable String companyCodeCurrency)
Original property name from the Odata EDM: CompanyCodeCurrency
public FinPlanningEntryItem.FinPlanningEntryItemBuilder amountInCompanyCodeCurrency(@Nullable BigDecimal amountInCompanyCodeCurrency)
Original property name from the Odata EDM: AmountInCompanyCodeCurrency
public FinPlanningEntryItem.FinPlanningEntryItemBuilder globalCurrency(@Nullable String globalCurrency)
Original property name from the Odata EDM: GlobalCurrency
public FinPlanningEntryItem.FinPlanningEntryItemBuilder amountInGlobalCurrency(@Nullable BigDecimal amountInGlobalCurrency)
Original property name from the Odata EDM: AmountInGlobalCurrency
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 periods Every 4 weeks -> 13 fiscal periods Weekly -> 52 or 53 fiscal periods
public FinPlanningEntryItem.FinPlanningEntryItemBuilder fiscalYearVariant(@Nullable String fiscalYearVariant)
Original property name from the Odata EDM: FiscalYearVariant
public FinPlanningEntryItem.FinPlanningEntryItemBuilder fiscalYearPeriod(@Nullable String fiscalYearPeriod)
Original property name from the Odata EDM: FiscalYearPeriod
public FinPlanningEntryItem.FinPlanningEntryItemBuilder chartOfAccounts(@Nullable String chartOfAccounts)
Original property name from the Odata EDM: ChartOfAccounts
public FinPlanningEntryItem.FinPlanningEntryItemBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
public FinPlanningEntryItem.FinPlanningEntryItemBuilder plantName(@Nullable String plantName)
Original property name from the Odata EDM: PlantName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public FinPlanningEntryItem.FinPlanningEntryItemBuilder customerName(@Nullable String customerName)
Original property name from the Odata EDM: CustomerName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder controllingDebitCreditCode(@Nullable String controllingDebitCreditCode)
Original property name from the Odata EDM: ControllingDebitCreditCode
public FinPlanningEntryItem.FinPlanningEntryItemBuilder project(@Nullable String project)
Original property name from the Odata EDM: Project
public FinPlanningEntryItem.FinPlanningEntryItemBuilder projectDescription(@Nullable String projectDescription)
Original property name from the Odata EDM: ProjectDescription
public FinPlanningEntryItem.FinPlanningEntryItemBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
public FinPlanningEntryItem.FinPlanningEntryItemBuilder wBSElementDescription(@Nullable String wBSElementDescription)
Original property name from the Odata EDM: WBSElementDescription
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerCompanyCode(@Nullable String partnerCompanyCode)
Original property name from the Odata EDM: PartnerCompanyCode
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerCompanyCodeName(@Nullable String partnerCompanyCodeName)
Original property name from the Odata EDM: PartnerCompanyCodeName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder costCtrActivityTypeName(@Nullable String costCtrActivityTypeName)
Original property name from the Odata EDM: CostCtrActivityTypeName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerOrder(@Nullable String partnerOrder)
Original property name from the Odata EDM: PartnerOrder
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerCostCtrActivityType(@Nullable String partnerCostCtrActivityType)
Original property name from the Odata EDM: PartnerCostCtrActivityType
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerCostCtrActivityTypeName(@Nullable String partnerCostCtrActivityTypeName)
Original property name from the Odata EDM: PartnerCostCtrActivityTypeName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerProject(@Nullable String partnerProject)
Original property name from the Odata EDM: PartnerProject
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerProjectDescription(@Nullable String partnerProjectDescription)
Original property name from the Odata EDM: PartnerProjectDescription
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerWBSElement(@Nullable String partnerWBSElement)
Original property name from the Odata EDM: PartnerWBSElement
public FinPlanningEntryItem.FinPlanningEntryItemBuilder partnerWBSElementDescription(@Nullable String partnerWBSElementDescription)
Original property name from the Odata EDM: PartnerWBSElementDescription
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder salesOrganizationName(@Nullable String salesOrganizationName)
Original property name from the Odata EDM: SalesOrganizationName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder distributionChannelName(@Nullable String distributionChannelName)
Original property name from the Odata EDM: DistributionChannelName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder divisionName(@Nullable String divisionName)
Original property name from the Odata EDM: DivisionName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder soldMaterialName(@Nullable String soldMaterialName)
Original property name from the Odata EDM: SoldMaterialName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder materialGroupName(@Nullable String materialGroupName)
Original property name from the Odata EDM: MaterialGroupName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.public FinPlanningEntryItem.FinPlanningEntryItemBuilder customerGroupName(@Nullable String customerGroupName)
Original property name from the Odata EDM: CustomerGroupName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder customerSupplierCountry(@Nullable String customerSupplierCountry)
Original property name from the Odata EDM: CustomerSupplierCountry
public FinPlanningEntryItem.FinPlanningEntryItemBuilder customerSupplierCountryName(@Nullable String customerSupplierCountryName)
Original property name from the Odata EDM: CustomerSupplierCountryName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder customerSupplierIndustry(@Nullable String customerSupplierIndustry)
Original property name from the Odata EDM: CustomerSupplierIndustry
public FinPlanningEntryItem.FinPlanningEntryItemBuilder customerSupplierIndustryName(@Nullable String customerSupplierIndustryName)
Original property name from the Odata EDM: CustomerSupplierIndustryName
public FinPlanningEntryItem.FinPlanningEntryItemBuilder 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 FinPlanningEntryItem.FinPlanningEntryItemBuilder salesDistrictName(@Nullable String salesDistrictName)
Original property name from the Odata EDM: SalesDistrictName
public FinPlanningEntryItem build()
Copyright © 2019 SAP SE. All rights reserved.