public static class SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder extends Object
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder supplierInvoice(@Nullable String supplierInvoice)
Original property name from the Odata EDM: SupplierInvoice
The document number is unique per company code and fiscal year. When entering an accounting document, you can specify the number manually or it can be determined by the system from a pre-defined area (number range).The relevant area of the document numbers (number range) is determined in each company code per document type.
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder fiscalYear(@Nullable String fiscalYear)
Original property name from the Odata EDM: FiscalYear
fiscal year can be the same as the calendar year, but does not have to be.public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder supplierInvoiceItem(@Nullable String supplierInvoiceItem)
Original property name from the Odata EDM: SupplierInvoiceItem
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder salesOrder(@Nullable String salesOrder)
Original property name from the Odata EDM: SalesOrder
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder salesOrderItem(@Nullable String salesOrderItem)
Original property name from the Odata EDM: SalesOrderItem
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder businessProcess(@Nullable String businessProcess)
Original property name from the Odata EDM: BusinessProcess
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder wBSElement(@Nullable String wBSElement)
Original property name from the Odata EDM: WBSElement
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder documentCurrency(@Nullable String documentCurrency)
Original property name from the Odata EDM: DocumentCurrency
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder supplierInvoiceItemAmount(@Nullable BigDecimal supplierInvoiceItemAmount)
Original property name from the Odata EDM: SupplierInvoiceItemAmount
During document entry, enter the amount manually. In the last line item, you can specify a '*'. The system will then enter the balance of the line items entered prior to the last item as the amount for the last item.Amounts you enter may be changed automatically by the system if the following postings are made:Tax adjustmentsCash discount adjustments during net postings
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder personnelNumber(@Nullable String personnelNumber)
Original property name from the Odata EDM: PersonnelNumber
enter a personnel number before you can display and maintain an employee's master data and time data.public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder workItem(@Nullable String workItem)
Original property name from the Odata EDM: WorkItem
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder debitCreditCode(@Nullable String debitCreditCode)
Original property name from the Odata EDM: DebitCreditCode
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder supplierInvoiceItemText(@Nullable String supplierInvoiceItemText)
Original property name from the Odata EDM: SupplierInvoiceItemText
Line item texts can be used internally and externally. To be able to distinguish between these, you must begin texts for external use with "*". These texts can then be printed on all correspondence, dunning notices, payment advice notes, etc. The asterisk is removed when the text is printed.This function is only available in the FI component. It cannot be used in Materials Management.
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder assignmentReference(@Nullable String assignmentReference)
Original property name from the Odata EDM: AssignmentReference
The program can display the account line items sorted according to the content of this field.You can either enter the field contents manually, or have the system define them automatically in the master record via the sort key field.You define the rules for the layout of the assignment number field in the Implementation Guide (IMG) under Determine Standard Sorting for Line Items.
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder isNotCashDiscountLiable(@Nullable Boolean isNotCashDiscountLiable)
Original property name from the Odata EDM: IsNotCashDiscountLiable
If a cash discount is not granted for the entire invoiced amount, the system can determine the amount qualifying for cash discount automatically by means of the offsetting entries. To enable the system to do this, you must mark all offsetting entries as being either liable or not liable to cash discount.
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder internalOrder(@Nullable String internalOrder)
Original property name from the Odata EDM: InternalOrder
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder networkActivity(@Nullable String networkActivity)
Original property name from the Odata EDM: NetworkActivity
Determines in which order the operations of a sequence are carried out.
public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder commitmentItem(@Nullable String commitmentItem)
Original property name from the Odata EDM: CommitmentItem
assigning budget.public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder fundsCenter(@Nullable String fundsCenter)
Original property name from the Odata EDM: FundsCenter
are assigning budget.public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder taxBaseAmountInTransCrcy(@Nullable BigDecimal taxBaseAmountInTransCrcy)
Original property name from the Odata EDM: TaxBaseAmountInTransCrcy
When directly entering tax items, you always have to specify the base amount so that the system can check that the tax amount is correct.
document currency.public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder quantityUnit(@Nullable String quantityUnit)
Original property name from the Odata EDM: QuantityUnit
You define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.Since all data is updated in the base unit of measure, your entry is particularly important for the conversion of alternative units of measure. A quantity in the alternative unit of measure can only be shown precisely if its value can be shown with the decimal places available. To ensure this, please note the following:The base unit of measure is the unit satisfying the highest necessary requirement for precision.The conversion of alternative units of measure to the base unit should result in simple decimal fractions (not, for example, 1/3 = 0.333...).Inventory ManagementIn Inventory Management, the base unit of measure is the same as the stockkeeping unit.ServicesServices have units of measure of their own, including the following:Service unitUnit of measure at the higher item level. The precise quantities of the individual services are each at the detailed service line level.BlanketUnit of measure at service line level for services to be provided once only, and for which no precise quantities can or are to be specified.
enter in other units of measure (alternative units of measure) to the base unit of measure.public SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder 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 SupplierInvoiceItemGLAcct.SupplierInvoiceItemGLAcctBuilder partnerBusinessArea(@Nullable String partnerBusinessArea)
Original property name from the Odata EDM: PartnerBusinessArea
This relationship enables the elimination of IC sales at business area level within business area consolidation.
the posting is made, there is a sender/receiver relationship in each line item.public SupplierInvoiceItemGLAcct build()
Copyright © 2020 SAP SE. All rights reserved.