public static final class JournalEntryItemBasic.JournalEntryItemBasicBuilder extends Object
@Nonnull public JournalEntryItemBasic.JournalEntryItemBasicBuilder companyCode(CompanyCode value)
value
- The CompanyCode to build this JournalEntryItemBasic with.@Nonnull public JournalEntryItemBasic.JournalEntryItemBasicBuilder companyCode(String value)
Original property name from the Odata EDM: CompanyCode
value
- The companyCode to build this JournalEntryItemBasic with.@Nonnull public JournalEntryItemBasic.JournalEntryItemBasicBuilder currentCostCenter(CostCenter value)
value
- The CostCenter to build this JournalEntryItemBasic with.@Nonnull public JournalEntryItemBasic.JournalEntryItemBasicBuilder currentProfitCenter(ProfitCenter value)
value
- The ProfitCenter to build this JournalEntryItemBasic with.@Nonnull public JournalEntryItemBasic.JournalEntryItemBasicBuilder glAccountInChartOfAccounts(GLAccountInChartOfAccounts value)
value
- The GLAccountInChartOfAccounts to build this JournalEntryItemBasic with.public JournalEntryItemBasic.JournalEntryItemBasicBuilder iD(@Nullable String iD)
Original property name from the Odata EDM: ID
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder ledger(@Nullable String ledger)
Original property name from the Odata EDM: Ledger
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder ledgerName(@Nullable String ledgerName)
Original property name from the Odata EDM: LedgerName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder ledgerFiscalYear(@Nullable String ledgerFiscalYear)
Original property name from the Odata EDM: LedgerFiscalYear
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder controllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder controllingAreaName(@Nullable String controllingAreaName)
Original property name from the Odata EDM: ControllingAreaName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder companyCodeName(@Nullable String companyCodeName)
Original property name from the Odata EDM: CompanyCodeName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder gLAccountName(@Nullable String gLAccountName)
Original property name from the Odata EDM: GLAccountName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder costCenterName(@Nullable String costCenterName)
Original property name from the Odata EDM: CostCenterName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder profitCenterName(@Nullable String profitCenterName)
Original property name from the Odata EDM: ProfitCenterName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder functionalAreaName(@Nullable String functionalAreaName)
Original property name from the Odata EDM: FunctionalAreaName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder businessAreaName(@Nullable String businessAreaName)
Original property name from the Odata EDM: BusinessAreaName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder segment(@Nullable String segment)
Original property name from the Odata EDM: Segment
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder segmentName(@Nullable String segmentName)
Original property name from the Odata EDM: SegmentName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerCostCenterName(@Nullable String partnerCostCenterName)
Original property name from the Odata EDM: PartnerCostCenterName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerProfitCenterName(@Nullable String partnerProfitCenterName)
Original property name from the Odata EDM: PartnerProfitCenterName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerFunctionalAreaName(@Nullable String partnerFunctionalAreaName)
Original property name from the Odata EDM: PartnerFunctionalAreaName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerBusinessAreaName(@Nullable String partnerBusinessAreaName)
Original property name from the Odata EDM: PartnerBusinessAreaName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerCompany(@Nullable String partnerCompany)
Original property name from the Odata EDM: PartnerCompany
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerCompanyName(@Nullable String partnerCompanyName)
Original property name from the Odata EDM: PartnerCompanyName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerSegment(@Nullable String partnerSegment)
Original property name from the Odata EDM: PartnerSegment
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerSegmentName(@Nullable String partnerSegmentName)
Original property name from the Odata EDM: PartnerSegmentName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder amountInTransactionCurrency(@Nullable BigDecimal amountInTransactionCurrency)
Original property name from the Odata EDM: AmountInTransactionCurrency
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder companyCodeCurrency(@Nullable String companyCodeCurrency)
Original property name from the Odata EDM: CompanyCodeCurrency
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder amountInCompanyCodeCurrency(@Nullable BigDecimal amountInCompanyCodeCurrency)
Original property name from the Odata EDM: AmountInCompanyCodeCurrency
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder globalCurrency(@Nullable String globalCurrency)
Original property name from the Odata EDM: GlobalCurrency
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder amountInGlobalCurrency(@Nullable BigDecimal amountInGlobalCurrency)
Original property name from the Odata EDM: AmountInGlobalCurrency
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder costSourceUnit(@Nullable String costSourceUnit)
Original property name from the Odata EDM: CostSourceUnit
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder valuationQuantity(@Nullable BigDecimal valuationQuantity)
Original property name from the Odata EDM: ValuationQuantity
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder fiscalYearVariant(@Nullable String fiscalYearVariant)
Original property name from the Odata EDM: FiscalYearVariant
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder fiscalYearPeriod(@Nullable String fiscalYearPeriod)
Original property name from the Odata EDM: FiscalYearPeriod
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder chartOfAccounts(@Nullable String chartOfAccounts)
Original property name from the Odata EDM: ChartOfAccounts
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder plantName(@Nullable String plantName)
Original property name from the Odata EDM: PlantName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customerName(@Nullable String customerName)
Original property name from the Odata EDM: CustomerName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder controllingDebitCreditCode(@Nullable String controllingDebitCreditCode)
Original property name from the Odata EDM: ControllingDebitCreditCode
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder project(@Nullable String project)
Original property name from the Odata EDM: Project
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder projectDescription(@Nullable String projectDescription)
Original property name from the Odata EDM: ProjectDescription
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder wBSElementDescription(@Nullable String wBSElementDescription)
Original property name from the Odata EDM: WBSElementDescription
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerCompanyCode(@Nullable String partnerCompanyCode)
Original property name from the Odata EDM: PartnerCompanyCode
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerCompanyCodeName(@Nullable String partnerCompanyCodeName)
Original property name from the Odata EDM: PartnerCompanyCodeName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder costCtrActivityTypeName(@Nullable String costCtrActivityTypeName)
Original property name from the Odata EDM: CostCtrActivityTypeName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerOrder(@Nullable String partnerOrder)
Original property name from the Odata EDM: PartnerOrder
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerCostCtrActivityType(@Nullable String partnerCostCtrActivityType)
Original property name from the Odata EDM: PartnerCostCtrActivityType
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerCostCtrActivityTypeName(@Nullable String partnerCostCtrActivityTypeName)
Original property name from the Odata EDM: PartnerCostCtrActivityTypeName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerProject(@Nullable String partnerProject)
Original property name from the Odata EDM: PartnerProject
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerProjectDescription(@Nullable String partnerProjectDescription)
Original property name from the Odata EDM: PartnerProjectDescription
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerWBSElement(@Nullable String partnerWBSElement)
Original property name from the Odata EDM: PartnerWBSElement
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder partnerWBSElementDescription(@Nullable String partnerWBSElementDescription)
Original property name from the Odata EDM: PartnerWBSElementDescription
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder salesOrganizationName(@Nullable String salesOrganizationName)
Original property name from the Odata EDM: SalesOrganizationName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder distributionChannelName(@Nullable String distributionChannelName)
Original property name from the Odata EDM: DistributionChannelName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder organizationDivision(@Nullable String organizationDivision)
Original property name from the Odata EDM: OrganizationDivision
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.this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder divisionName(@Nullable String divisionName)
Original property name from the Odata EDM: DivisionName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder soldMaterial(@Nullable String soldMaterial)
Original property name from the Odata EDM: SoldMaterial
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder soldMaterialName(@Nullable String soldMaterialName)
Original property name from the Odata EDM: SoldMaterialName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder materialGroupName(@Nullable String materialGroupName)
Original property name from the Odata EDM: MaterialGroupName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customerGroupName(@Nullable String customerGroupName)
Original property name from the Odata EDM: CustomerGroupName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customerSupplierCountry(@Nullable String customerSupplierCountry)
Original property name from the Odata EDM: CustomerSupplierCountry
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customerSupplierCountryName(@Nullable String customerSupplierCountryName)
Original property name from the Odata EDM: CustomerSupplierCountryName
The country description is used in the address format and on the user interface instead of the country key, or in addition to the country key.There are two fields for the country description. This fifty-character field, and a shorter fifteen-character field.Both fields contain the short description of the country, according to ISO 3166-1.For some countries, the fifteen-character field contains only a shortened form of the description, due to the field length.The fifty-character field contains the short description without abbreviations (but not the official, complete country name).
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customerSupplierIndustry(@Nullable String customerSupplierIndustry)
Original property name from the Odata EDM: CustomerSupplierIndustry
The industry field belongs to the general data area of customer and vendor master records.
used in selecting data for evaluations (for example, a vendor master data list). You can specify industries such as trade, banking, service, manufacturing, health care, public service, media and so on.this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder customerSupplierIndustryName(@Nullable String customerSupplierIndustryName)
Original property name from the Odata EDM: CustomerSupplierIndustryName
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder 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.
this
.public JournalEntryItemBasic.JournalEntryItemBasicBuilder salesDistrictName(@Nullable String salesDistrictName)
Original property name from the Odata EDM: SalesDistrictName
this
.public JournalEntryItemBasic build()
Copyright © 2020 SAP SE. All rights reserved.