public static final class GRTransactionDataResult.GRTransactionDataResultBuilder extends Object
@Nonnull public GRTransactionDataResult.GRTransactionDataResultBuilder parameters(GRTransactionDataParameters value)
value
- The GRTransactionDataParameters to build this GRTransactionDataResult with.public GRTransactionDataResult.GRTransactionDataResultBuilder iD(@Nullable String iD)
Original property name from the Odata EDM: ID
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationLedger(@Nullable String consolidationLedger)
Original property name from the Odata EDM: ConsolidationLedger
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationLedger_Text(@Nullable String consolidationLedger_Text)
Original property name from the Odata EDM: ConsolidationLedger_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder consolidationDocumentNumber(@Nullable String consolidationDocumentNumber)
Original property name from the Odata EDM: ConsolidationDocumentNumber
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 GRTransactionDataResult.GRTransactionDataResultBuilder consolidationPostingItem(@Nullable String consolidationPostingItem)
Original property name from the Odata EDM: ConsolidationPostingItem
public GRTransactionDataResult.GRTransactionDataResultBuilder gLRecordType(@Nullable String gLRecordType)
Original property name from the Odata EDM: GLRecordType
public GRTransactionDataResult.GRTransactionDataResultBuilder gLRecordType_Text(@Nullable String gLRecordType_Text)
Original property name from the Odata EDM: GLRecordType_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationVersion(@Nullable String consolidationVersion)
Original property name from the Odata EDM: ConsolidationVersion
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationVersion_Text(@Nullable String consolidationVersion_Text)
Original property name from the Odata EDM: ConsolidationVersion_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder transactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
public GRTransactionDataResult.GRTransactionDataResultBuilder localCurrency(@Nullable String localCurrency)
Original property name from the Odata EDM: LocalCurrency
public GRTransactionDataResult.GRTransactionDataResultBuilder groupCurrency(@Nullable String groupCurrency)
Original property name from the Odata EDM: GroupCurrency
public GRTransactionDataResult.GRTransactionDataResultBuilder baseUnit(@Nullable String baseUnit)
Original property name from the Odata EDM: BaseUnit
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 GRTransactionDataResult.GRTransactionDataResultBuilder baseUnit_Text(@Nullable String baseUnit_Text)
Original property name from the Odata EDM: BaseUnit_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder fiscalPeriod(@Nullable String fiscalPeriod)
Original property name from the Odata EDM: FiscalPeriod
public GRTransactionDataResult.GRTransactionDataResultBuilder fiscalYearPeriod(@Nullable String fiscalYearPeriod)
Original property name from the Odata EDM: FiscalYearPeriod
public GRTransactionDataResult.GRTransactionDataResultBuilder fiscalYearVariant(@Nullable String fiscalYearVariant)
Original property name from the Odata EDM: FiscalYearVariant
public GRTransactionDataResult.GRTransactionDataResultBuilder periodMode(@Nullable String periodMode)
Original property name from the Odata EDM: PeriodMode
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationDocumentType(@Nullable String consolidationDocumentType)
Original property name from the Odata EDM: ConsolidationDocumentType
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationDocumentType_Text(@Nullable String consolidationDocumentType_Text)
Original property name from the Odata EDM: ConsolidationDocumentType_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder debitCreditCode(@Nullable String debitCreditCode)
Original property name from the Odata EDM: DebitCreditCode
public GRTransactionDataResult.GRTransactionDataResultBuilder debitCreditCode_Text(@Nullable String debitCreditCode_Text)
Original property name from the Odata EDM: DebitCreditCode_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder company(@Nullable String company)
Original property name from the Odata EDM: Company
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationUnit(@Nullable String consolidationUnit)
Original property name from the Odata EDM: ConsolidationUnit
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationUnit_Text(@Nullable String consolidationUnit_Text)
Original property name from the Odata EDM: ConsolidationUnit_Text
Describes an object with a maximum of 40 characters.
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationUnitForElim(@Nullable String consolidationUnitForElim)
Original property name from the Odata EDM: ConsolidationUnitForElim
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationUnitForElim_Text(@Nullable String consolidationUnitForElim_Text)
Original property name from the Odata EDM: ConsolidationUnitForElim_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationChartOfAccounts(@Nullable String consolidationChartOfAccounts)
Original property name from the Odata EDM: ConsolidationChartOfAccounts
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationChartOfAccounts_Text(@Nullable String consolidationChartOfAccounts_Text)
Original property name from the Odata EDM: ConsolidationChartOfAccounts_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder financialStatementItem(@Nullable String financialStatementItem)
Original property name from the Odata EDM: FinancialStatementItem
public GRTransactionDataResult.GRTransactionDataResultBuilder financialStatementItem_Text(@Nullable String financialStatementItem_Text)
Original property name from the Odata EDM: FinancialStatementItem_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerConsolidationUnit(@Nullable String partnerConsolidationUnit)
Original property name from the Odata EDM: PartnerConsolidationUnit
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerConsolidationUnit_Text(@Nullable String partnerConsolidationUnit_Text)
Original property name from the Odata EDM: PartnerConsolidationUnit_Text
Describes an object with a maximum of 20 characters.
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationGroup(@Nullable String consolidationGroup)
Original property name from the Odata EDM: ConsolidationGroup
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationGroup_Text(@Nullable String consolidationGroup_Text)
Original property name from the Odata EDM: ConsolidationGroup_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public GRTransactionDataResult.GRTransactionDataResultBuilder companyCode_Text(@Nullable String companyCode_Text)
Original property name from the Odata EDM: CompanyCode_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder subItemCategory(@Nullable String subItemCategory)
Original property name from the Odata EDM: SubItemCategory
public GRTransactionDataResult.GRTransactionDataResultBuilder subItemCategory_Text(@Nullable String subItemCategory_Text)
Original property name from the Odata EDM: SubItemCategory_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder subItem(@Nullable String subItem)
Original property name from the Odata EDM: SubItem
public GRTransactionDataResult.GRTransactionDataResultBuilder subItem_Text(@Nullable String subItem_Text)
Original property name from the Odata EDM: SubItem_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder postingLevel(@Nullable String postingLevel)
Original property name from the Odata EDM: PostingLevel
public GRTransactionDataResult.GRTransactionDataResultBuilder postingLevel_Text(@Nullable String postingLevel_Text)
Original property name from the Odata EDM: PostingLevel_Text
SeeTask-Oriented InstructionsReference Documentation for Semantic Properties of Domains
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationApportionment(@Nullable String consolidationApportionment)
Original property name from the Odata EDM: ConsolidationApportionment
Apportionment entries are generated during proportional consolidation by the tasks concerning apportionments and two-sided elimination (interunit elimination or elimination of profit/loss).The apportioned value is the sum from the original record and and the apportionment adjustment.
original record or as an apportionment record.public GRTransactionDataResult.GRTransactionDataResultBuilder currencyConversionsDiffType(@Nullable String currencyConversionsDiffType)
Original property name from the Odata EDM: CurrencyConversionsDiffType
The details in posting currency translation mentioned above make the system transparent in the various characteristic values of the translation indicator. This characteristic indicates the group currency values of a data record of consolidation as reference values or as the delta between the group value and the reference value.If currency translation discloses temporal translation differences, the system uses the various values of this translation indicator for dispersing temporal differences and transaction differences. This is performed for both the reference value as well as the delta between the group value and the reference value.The group value posted by the currency translation results from the total of the four relevant values of the translation indicator. These are as follows:Value 4 - Group value for reference exchange rate, (line items)Value 1 - Delta between group value and group value for reference exchange rateValue 2 - Group value for reference exchange rate, translation differenceValue 3 - Delta between group value and group value for reference exchange rateThe data records with value 0 (group value for reference exchange rate) for the translation indicator are the source data for the currency translation. They always contain values in local currency, as well as values in the group currency if you have defined a sender field for group currency for the respective consolidation unit. That is, in general, the group value for reference exchange rate is the total of the data records with value 0 and 4 for the translation indicator.
accordance with the reference translation defined in the currency translation method. Additionally, the system calculates the target value in the group currency in accordance with the specific translation of the respective method step for each step of the currency translation method (with the exception of rounding steps) for the data records selected in the step. For some translation types, you can activate the separate display of translation differences in the method step.public GRTransactionDataResult.GRTransactionDataResultBuilder currencyConversionsDiffType_Text(@Nullable String currencyConversionsDiffType_Text)
Original property name from the Odata EDM: CurrencyConversionsDiffType_Text
SeeTask-Oriented InstructionsReference Documentation for Semantic Properties of Domains
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationAcquisitionYear(@Nullable String consolidationAcquisitionYear)
Original property name from the Odata EDM: ConsolidationAcquisitionYear
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationAcquisitionPeriod(@Nullable String consolidationAcquisitionPeriod)
Original property name from the Odata EDM: ConsolidationAcquisitionPeriod
public GRTransactionDataResult.GRTransactionDataResultBuilder investeeConsolidationUnit(@Nullable String investeeConsolidationUnit)
Original property name from the Odata EDM: InvesteeConsolidationUnit
public GRTransactionDataResult.GRTransactionDataResultBuilder investeeConsolidationUnit_Text(@Nullable String investeeConsolidationUnit_Text)
Original property name from the Odata EDM: InvesteeConsolidationUnit_Text
Describes an object with a maximum of 40 characters.
public GRTransactionDataResult.GRTransactionDataResultBuilder amountInTransactionCurrency(@Nullable BigDecimal amountInTransactionCurrency)
Original property name from the Odata EDM: AmountInTransactionCurrency
public GRTransactionDataResult.GRTransactionDataResultBuilder amountInLocalCurrency(@Nullable BigDecimal amountInLocalCurrency)
Original property name from the Odata EDM: AmountInLocalCurrency
public GRTransactionDataResult.GRTransactionDataResultBuilder amountInGroupCurrency(@Nullable BigDecimal amountInGroupCurrency)
Original property name from the Odata EDM: AmountInGroupCurrency
public GRTransactionDataResult.GRTransactionDataResultBuilder quantityInBaseUnit(@Nullable BigDecimal quantityInBaseUnit)
Original property name from the Odata EDM: QuantityInBaseUnit
public GRTransactionDataResult.GRTransactionDataResultBuilder documentItemText(@Nullable String documentItemText)
Original property name from the Odata EDM: DocumentItemText
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 GRTransactionDataResult.GRTransactionDataResultBuilder consolidationPostgItemAutoFlag(@Nullable String consolidationPostgItemAutoFlag)
Original property name from the Odata EDM: ConsolidationPostgItemAutoFlag
Indicator '1': Retained earningsIndicator '2': Deferred taxation
income postings for the retained earnings and the adjustment postings of the deferred taxation.public GRTransactionDataResult.GRTransactionDataResultBuilder businessTransactionType(@Nullable String businessTransactionType)
Original property name from the Odata EDM: BusinessTransactionType
If an application calls up direct posting in accounting, data is transferred with an appropriate transaction. Depending on the transaction, you can process this transferred data in different ways (for example, with ledger selection, field movement).
views.public GRTransactionDataResult.GRTransactionDataResultBuilder postingDate(@Nullable LocalDateTime postingDate)
Original property name from the Odata EDM: PostingDate
The fiscal year and the period for which an update of the accounts specified in the document or cost elements is made, are derived from the posting date.When entering documents, the system checks whether the posting date entered is allowed by means of the posting period permitted.The posting date can differ from both the entry date (day of entry into the system) and the document date (day of creation of the original document).
public GRTransactionDataResult.GRTransactionDataResultBuilder currencyTranslationDate(@Nullable LocalDateTime currencyTranslationDate)
Original property name from the Odata EDM: CurrencyTranslationDate
public GRTransactionDataResult.GRTransactionDataResultBuilder refConsolidationDocumentNumber(@Nullable String refConsolidationDocumentNumber)
Original property name from the Odata EDM: RefConsolidationDocumentNumber
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 GRTransactionDataResult.GRTransactionDataResultBuilder referenceFiscalYear(@Nullable String referenceFiscalYear)
Original property name from the Odata EDM: ReferenceFiscalYear
The original fiscal year is only relevant for consolidation units to which you have assigned the Read from Universal Document and transfer methods.
public GRTransactionDataResult.GRTransactionDataResultBuilder refConsolidationPostingItem(@Nullable String refConsolidationPostingItem)
Original property name from the Odata EDM: RefConsolidationPostingItem
system assigns the numbers continuously during document entry.public GRTransactionDataResult.GRTransactionDataResultBuilder refConsolidationDocumentType(@Nullable String refConsolidationDocumentType)
Original property name from the Odata EDM: RefConsolidationDocumentType
Document type AApplications which use the FI-SL structures, but work autonomously (Profit center, Reconciliation ledger,...) under certain circumstances assign a document number and therefore must also assign a document type - A -. As with document type S, the reference document number is also usually W or K in this case.Document type BDocuments from FI-GL. MM and SD documents are posted to FI-SL indirectly via FI and therefore also have document type B.As of Release 3.0, FI documents are posted to FI-SL via the RW structure and therefore have document type S or W.Document type KDocuments from CO.Document type GDocument from general ledger for global postings.Document type TReverse documents for G (with the same document number)Document type LDocuments from general ledger for local postingsDocument type UReverse documents for L (with the same document number)Document type SDocuments for which FI-SL assigns a separate document number for direct posting. For example, for the billing interface or CO documents without line items. As of Release 3,0, a separate document number is generally assigned so that the original document type is S and the reference document type is W or K.Document type JJoint Venture documentsDocument type RConsolidation documents (EC-CS)Document type RDocuments which were generated by a rollup.Document type WAs of Release 3.0, documents that are posted to FI-SL via the accounting document have document type W. These are all documents that come from SD, MM, or FI.Document type W is generally used as the reference document type, since in this case a separate document number with the document type S is assigned by FI-SL.Document type *If you enter an asterisk in the document type, the system displays all the selected documents, irrespective of the document type.
public GRTransactionDataResult.GRTransactionDataResultBuilder refBusinessTransactionType(@Nullable String refBusinessTransactionType)
Original property name from the Odata EDM: RefBusinessTransactionType
If an application calls up direct posting in accounting, data is transferred with an appropriate transaction. Depending on the transaction, you can process this transferred data in different ways (for example, with ledger selection, field movement).
views.public GRTransactionDataResult.GRTransactionDataResultBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
NoteThe posting date can differ from the entry date (date of entry in the system) and the document date.
public GRTransactionDataResult.GRTransactionDataResultBuilder creationTime(@Nullable LocalTime creationTime)
Original property name from the Odata EDM: CreationTime
public GRTransactionDataResult.GRTransactionDataResultBuilder userID(@Nullable String userID)
Original property name from the Odata EDM: UserID
public GRTransactionDataResult.GRTransactionDataResultBuilder reverseDocument(@Nullable String reverseDocument)
Original property name from the Odata EDM: ReverseDocument
The field is filled by the system during reversal.public GRTransactionDataResult.GRTransactionDataResultBuilder reversedDocument(@Nullable String reversedDocument)
Original property name from the Odata EDM: ReversedDocument
public GRTransactionDataResult.GRTransactionDataResultBuilder investmentActivityType(@Nullable String investmentActivityType)
Original property name from the Odata EDM: InvestmentActivityType
InvestmentsEquity capitalMinority interest in investments and equity capitalGoodwillFair value adjustmentsThe following types of activities are distinguished:Acquisition, sale, transfer and merger of ownership and the change in indirect investment resulting from itIncrease and decrease in book value of investmentsIncrease and decrease in stockholders' equityDisclosing minorities to the retained stockholders' equityAmortization and/or elimination of goodwill and recorded fair value adjustmentsChange of the consolidation of investments methodActivities which can be entered and executed are distinguished as follows:Activities can be entered by changes in investment or changes in equity, by entering a first consolidation period or a divestiture accounting period in the maintenance of consolidation groups or by changing the method assignment. There are activities which cannot be entered, for example changes in indirect investment.The entered activities are interpreted and executed in the context of a consolidation group and the consolidation units contained in it and its methods. All activities which can be entered can also be executed; activities which cannot be entered are triggered by activities which can be entered.One document is posted per activity.
items are dealt with:public GRTransactionDataResult.GRTransactionDataResultBuilder investmentActivity(@Nullable String investmentActivity)
Original property name from the Odata EDM: InvestmentActivity
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationDocReversalYear(@Nullable String consolidationDocReversalYear)
Original property name from the Odata EDM: ConsolidationDocReversalYear
For a reversed document, the field shows the fiscal year in which the reversal document was posted.For a reversal document, the field shows the fiscal year of the original document was posted.
public GRTransactionDataResult.GRTransactionDataResultBuilder referenceDocumentType(@Nullable String referenceDocumentType)
Original property name from the Odata EDM: ReferenceDocumentType
Example: 1000007899 00011996Reference Reference organizational unitdocument no. client and fiscal yearThe object type contains a note on storing the original document.
unique reference. It consists of object key and object type. The object key consists of a reference document number and a reference organizational unit.public GRTransactionDataResult.GRTransactionDataResultBuilder referenceDocumentContext(@Nullable String referenceDocumentContext)
Original property name from the Odata EDM: ReferenceDocumentContext
number range ID as well as the reference document number. This occurs in the reference organization unit.public GRTransactionDataResult.GRTransactionDataResultBuilder logicalSystem(@Nullable String logicalSystem)
Original property name from the Odata EDM: LogicalSystem
The distribution of data between systems requires that each system in the network has a unique identification. The logical system is used for this purpose.In the SAP System the client corresponds to a logical system. You can assign a logical system to a client in the client maintenance (choose Goto -> Detail).The logical system is relevant in the following SAP areas:ALE general: two or more logical systems communicate with one another.ALE - ALE business processes (for example, cost center accounting): definition of a system where a specific application runs. Changes to master data can only be made in this system, for example.Workflow objects: the logical system in which the object is located is always included in an object's key.When maintaining the logical system, note the following:The logical system must be unique company-wide. It must not be used by any other system in the ALE integrated group. In a production system, the logical system must not be changed. If the logical system of a document reference is not set to initial and does not match your own, the system assumes the document is located in a different system.
public GRTransactionDataResult.GRTransactionDataResultBuilder chartOfAccounts(@Nullable String chartOfAccounts)
Original property name from the Odata EDM: ChartOfAccounts
public GRTransactionDataResult.GRTransactionDataResultBuilder chartOfAccounts_Text(@Nullable String chartOfAccounts_Text)
Original property name from the Odata EDM: ChartOfAccounts_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
Note the following:If no data submit request has been raised for this period, the value in this column is 'FirstRaise’ (if currency translation is in BPC). If currency translation is being done in S/4HANA, it is ‘NeedRaise’.If a data submit request has already been raised for this period, this column contains the account numbers of the new documents posted in the universal journal, table ACDOCA, after the last data submit request date (if currency translation is in BPC).The column is always ‘NeedRaise’ if new data has been posted to the consolidation journal ACDOCC after the last data submit request date and time (if currency translation is in S/4HANA).
public GRTransactionDataResult.GRTransactionDataResultBuilder gLAccount_Text(@Nullable String gLAccount_Text)
Original property name from the Odata EDM: GLAccount_Text
for the long text.public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public GRTransactionDataResult.GRTransactionDataResultBuilder costCenter_Text(@Nullable String costCenter_Text)
Original property name from the Odata EDM: CostCenter_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder profitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
public GRTransactionDataResult.GRTransactionDataResultBuilder profitCenter_Text(@Nullable String profitCenter_Text)
Original property name from the Odata EDM: ProfitCenter_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationPrftCtrForElim(@Nullable String consolidationPrftCtrForElim)
Original property name from the Odata EDM: ConsolidationPrftCtrForElim
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationPrftCtrForElim_Text(@Nullable String consolidationPrftCtrForElim_Text)
Original property name from the Odata EDM: ConsolidationPrftCtrForElim_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder functionalArea_Text(@Nullable String functionalArea_Text)
Original property name from the Odata EDM: FunctionalArea_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
public GRTransactionDataResult.GRTransactionDataResultBuilder businessArea_Text(@Nullable String businessArea_Text)
Original property name from the Odata EDM: BusinessArea_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder controllingArea_Text(@Nullable String controllingArea_Text)
Original property name from the Odata EDM: ControllingArea_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder segment(@Nullable String segment)
Original property name from the Odata EDM: Segment
public GRTransactionDataResult.GRTransactionDataResultBuilder segment_Text(@Nullable String segment_Text)
Original property name from the Odata EDM: Segment_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationSegmentForElim(@Nullable String consolidationSegmentForElim)
Original property name from the Odata EDM: ConsolidationSegmentForElim
public GRTransactionDataResult.GRTransactionDataResultBuilder consolidationSegmentForElim_Text(@Nullable String consolidationSegmentForElim_Text)
Original property name from the Odata EDM: ConsolidationSegmentForElim_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder partnerCostCenter_Text(@Nullable String partnerCostCenter_Text)
Original property name from the Odata EDM: PartnerCostCenter_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerProfitCenter(@Nullable String partnerProfitCenter)
Original property name from the Odata EDM: PartnerProfitCenter
For a profit center that sends a good or service, the receiver profit center is identified as the partner profit center. For the receiver, the sender is the partner profit center.
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerProfitCenter_Text(@Nullable String partnerProfitCenter_Text)
Original property name from the Odata EDM: PartnerProfitCenter_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder partnerFunctionalArea_Text(@Nullable String partnerFunctionalArea_Text)
Original property name from the Odata EDM: PartnerFunctionalArea_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder partnerBusinessArea_Text(@Nullable String partnerBusinessArea_Text)
Original property name from the Odata EDM: PartnerBusinessArea_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerCompany(@Nullable String partnerCompany)
Original property name from the Odata EDM: PartnerCompany
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerCompany_Text(@Nullable String partnerCompany_Text)
Original property name from the Odata EDM: PartnerCompany_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerSegment(@Nullable String partnerSegment)
Original property name from the Odata EDM: PartnerSegment
public GRTransactionDataResult.GRTransactionDataResultBuilder partnerSegment_Text(@Nullable String partnerSegment_Text)
Original property name from the Odata EDM: PartnerSegment_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder orderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
public GRTransactionDataResult.GRTransactionDataResultBuilder orderID_Text(@Nullable String orderID_Text)
Original property name from the Odata EDM: OrderID_Text
You can enter longer language-dependent texts, using the "Long text" function.
public GRTransactionDataResult.GRTransactionDataResultBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public GRTransactionDataResult.GRTransactionDataResultBuilder customer_Text(@Nullable String customer_Text)
Original property name from the Odata EDM: Customer_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder supplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
public GRTransactionDataResult.GRTransactionDataResultBuilder supplier_Text(@Nullable String supplier_Text)
Original property name from the Odata EDM: Supplier_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder material(@Nullable String material)
Original property name from the Odata EDM: Material
public GRTransactionDataResult.GRTransactionDataResultBuilder material_Text(@Nullable String material_Text)
Original property name from the Odata EDM: Material_Text
You can enter one material description in each of any number of languages.In principle, you enter the material description on the data screen of the first user department for which you enter data, and in your logon language. You can overwrite the material description on the Basic Data screen.
public GRTransactionDataResult.GRTransactionDataResultBuilder plant(@Nullable String plant)
Original property name from the Odata EDM: Plant
public GRTransactionDataResult.GRTransactionDataResultBuilder plant_Text(@Nullable String plant_Text)
Original property name from the Odata EDM: Plant_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder financialTransactionType(@Nullable String financialTransactionType)
Original property name from the Odata EDM: FinancialTransactionType
public GRTransactionDataResult.GRTransactionDataResultBuilder financialTransactionType_Text(@Nullable String financialTransactionType_Text)
Original property name from the Odata EDM: FinancialTransactionType_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder wBSElementInternalID(@Nullable String wBSElementInternalID)
Original property name from the Odata EDM: WBSElementInternalID
public GRTransactionDataResult.GRTransactionDataResultBuilder wBSDescription(@Nullable String wBSDescription)
Original property name from the Odata EDM: WBSDescription
public GRTransactionDataResult.GRTransactionDataResultBuilder wBSElementExternalID(@Nullable String wBSElementExternalID)
Original property name from the Odata EDM: WBSElementExternalID
public GRTransactionDataResult.GRTransactionDataResultBuilder wBSElementExternalID_Text(@Nullable String wBSElementExternalID_Text)
Original property name from the Odata EDM: WBSElementExternalID_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder project(@Nullable String project)
Original property name from the Odata EDM: Project
public GRTransactionDataResult.GRTransactionDataResultBuilder project_Text(@Nullable String project_Text)
Original property name from the Odata EDM: Project_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder billingDocumentType(@Nullable String billingDocumentType)
Original property name from the Odata EDM: BillingDocumentType
When you process billing documents collectively, you can use the billing type as one of the selection criteria.
public GRTransactionDataResult.GRTransactionDataResultBuilder billingDocumentType_Text(@Nullable String billingDocumentType_Text)
Original property name from the Odata EDM: BillingDocumentType_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder salesOrganization_Text(@Nullable String salesOrganization_Text)
Original property name from the Odata EDM: SalesOrganization_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder distributionChannel_Text(@Nullable String distributionChannel_Text)
Original property name from the Odata EDM: DistributionChannel_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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.public GRTransactionDataResult.GRTransactionDataResultBuilder organizationDivision_Text(@Nullable String organizationDivision_Text)
Original property name from the Odata EDM: OrganizationDivision_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder materialGroup(@Nullable String materialGroup)
Original property name from the Odata EDM: MaterialGroup
This can differ from the product sold group, for example if the material consumed for a project differs from the product sold of the sales order related to the project.
public GRTransactionDataResult.GRTransactionDataResultBuilder materialGroup_Text(@Nullable String materialGroup_Text)
Original property name from the Odata EDM: MaterialGroup_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder soldProduct(@Nullable String soldProduct)
Original property name from the Odata EDM: SoldProduct
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 GRTransactionDataResult.GRTransactionDataResultBuilder soldProduct_Text(@Nullable String soldProduct_Text)
Original property name from the Odata EDM: SoldProduct_Text
You can enter one material description in each of any number of languages.In principle, you enter the material description on the data screen of the first user department for which you enter data, and in your logon language. You can overwrite the material description on the Basic Data screen.
public GRTransactionDataResult.GRTransactionDataResultBuilder soldProductGroup(@Nullable String soldProductGroup)
Original property name from the Odata EDM: SoldProductGroup
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 GRTransactionDataResult.GRTransactionDataResultBuilder soldProductGroup_Text(@Nullable String soldProductGroup_Text)
Original property name from the Odata EDM: SoldProductGroup_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder customerGroup(@Nullable String customerGroup)
Original property name from the Odata EDM: CustomerGroup
or generating statistics.public GRTransactionDataResult.GRTransactionDataResultBuilder customerGroup_Text(@Nullable String customerGroup_Text)
Original property name from the Odata EDM: CustomerGroup_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder customerSupplierCountry(@Nullable String customerSupplierCountry)
Original property name from the Odata EDM: CustomerSupplierCountry
public GRTransactionDataResult.GRTransactionDataResultBuilder customerSupplierCountry_Text(@Nullable String customerSupplierCountry_Text)
Original property name from the Odata EDM: CustomerSupplierCountry_Text
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).
public GRTransactionDataResult.GRTransactionDataResultBuilder 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.public GRTransactionDataResult.GRTransactionDataResultBuilder customerSupplierIndustry_Text(@Nullable String customerSupplierIndustry_Text)
Original property name from the Odata EDM: CustomerSupplierIndustry_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder 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 GRTransactionDataResult.GRTransactionDataResultBuilder salesDistrict_Text(@Nullable String salesDistrict_Text)
Original property name from the Odata EDM: SalesDistrict_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder billToParty(@Nullable String billToParty)
Original property name from the Odata EDM: BillToParty
public GRTransactionDataResult.GRTransactionDataResultBuilder billToParty_Text(@Nullable String billToParty_Text)
Original property name from the Odata EDM: BillToParty_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder shipToParty(@Nullable String shipToParty)
Original property name from the Odata EDM: ShipToParty
public GRTransactionDataResult.GRTransactionDataResultBuilder shipToParty_Text(@Nullable String shipToParty_Text)
Original property name from the Odata EDM: ShipToParty_Text
public GRTransactionDataResult.GRTransactionDataResultBuilder customerSupplierCorporateGroup(@Nullable String customerSupplierCorporateGroup)
Original property name from the Odata EDM: CustomerSupplierCorporateGroup
If you create a matchcode using this group key, group evaluations are possible.
assignable.public GRTransactionDataResult build()
Copyright © 2019 SAP SE. All rights reserved.