public static class TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder extends Object
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder trsyAccountingDocumentUUID(@Nullable UUID trsyAccountingDocumentUUID)
Original property name from the Odata EDM: TrsyAccountingDocumentUUID
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder accountingDocumentItemRef(@Nullable String accountingDocumentItemRef)
Original property name from the Odata EDM: AccountingDocumentItemRef
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder trsyPositionContextUUID(@Nullable UUID trsyPositionContextUUID)
Original property name from the Odata EDM: TrsyPositionContextUUID
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryBusinessTransStatus(@Nullable String treasuryBusinessTransStatus)
Original property name from the Odata EDM: TreasuryBusinessTransStatus
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryBusTransStatusName(@Nullable String treasuryBusTransStatusName)
Original property name from the Odata EDM: TreasuryBusTransStatusName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryUpdateType(@Nullable String treasuryUpdateType)
Original property name from the Odata EDM: TreasuryUpdateType
You define update types in Customizing, and then assign them to various usages. An update type can be assigned to several usages. For some usages, the update types must carry specific information that is required by the usage to process the update types.This characteristic is only displayed for the area of validity of the architecture of the parallel valuation areas.This characteristic is only displayed for the area of validity of the architecture of the parallel valuation areas. This means that this characteristic is empty for the area Loans (CML) Operative (valuation area 001 in integrated reporting).
management for the securities area.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryUpdateTypeName(@Nullable String treasuryUpdateTypeName)
Original property name from the Odata EDM: TreasuryUpdateTypeName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder isUsedInPaymentTransaction(@Nullable Boolean isUsedInPaymentTransaction)
Original property name from the Odata EDM: IsUsedInPaymentTransaction
The user either sets or doesn't set the indicator for the triggering business transaction (for example the purchase of a secuity). It can be changed for business partner payment details.
the payment transaction indicator. This enables you to define both a subledger posting and a bank or G/L account posing for an update type.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryGLAccountAssignmentRef(@Nullable String treasuryGLAccountAssignmentRef)
Original property name from the Odata EDM: TreasuryGLAccountAssignmentRef
The account assignment reference determines the general ledger account in which the position is to be managed.The account assignment references are independent of the valuation areas. The account assignment references are assigned to positions based on the valuation area and/or you control the account determination based on valuation area and account assignment reference.This characteristic is only displayed for the validity area of the architecture of the parallel valuation areas. That means that this characteristic is empty for the loans (CML) operative area (valuation area 001 in integrated reporting).
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryGLAccountAssignRefName(@Nullable String treasuryGLAccountAssignRefName)
Original property name from the Odata EDM: TreasuryGLAccountAssignRefName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryPostingCategory(@Nullable Short treasuryPostingCategory)
Original property name from the Odata EDM: TreasuryPostingCategory
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryPostingCategoryName(@Nullable String treasuryPostingCategoryName)
Original property name from the Odata EDM: TreasuryPostingCategoryName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryGLAccountSymbol(@Nullable String treasuryGLAccountSymbol)
Original property name from the Odata EDM: TreasuryGLAccountSymbol
You use the account symbols to define posting specifications, which you then assign to the update types. 1:n assignment is possible, that is, you can assign a set of posting specifications to n different update types.Afterwards, you assign the G/L accounts to the account symbols. You can make this G/L account assignment dependent on the following factors: valuation area, account assignment reference and currency.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryGLAccountSymbolName(@Nullable String treasuryGLAccountSymbolName)
Original property name from the Odata EDM: TreasuryGLAccountSymbolName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder postingKey(@Nullable String postingKey)
Original property name from the Odata EDM: PostingKey
For every posting key, you specify properties which control the entry of the line item or are noted in the line item itself.The most important properties which are derived from the posting key are:The account typeThe allocation to the debits or credits sideThe possible or necessary specifications which are to be entered in the line item.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder postingKeyName(@Nullable String postingKeyName)
Original property name from the Odata EDM: PostingKeyName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder gLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder positionCurrency(@Nullable String positionCurrency)
Original property name from the Odata EDM: PositionCurrency
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder amountInPositionCurrency(@Nullable BigDecimal amountInPositionCurrency)
Original property name from the Odata EDM: AmountInPositionCurrency
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder companyCodeCurrency(@Nullable String companyCodeCurrency)
Original property name from the Odata EDM: CompanyCodeCurrency
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder amountInCompanyCodeCurrency(@Nullable BigDecimal amountInCompanyCodeCurrency)
Original property name from the Odata EDM: AmountInCompanyCodeCurrency
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryTransactionFlow(@Nullable Integer treasuryTransactionFlow)
Original property name from the Odata EDM: TreasuryTransactionFlow
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder accountingDocument(@Nullable String accountingDocument)
Original property name from the Odata EDM: AccountingDocument
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 TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder reverseDocument(@Nullable String reverseDocument)
Original property name from the Odata EDM: ReverseDocument
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder journalEntryType(@Nullable String journalEntryType)
Original property name from the Odata EDM: JournalEntryType
Attributes that control the entry of the document, or which are themselves noted in the document, are defined for each document type. In particular, the number range assigned to the associated documents is defined on the basis of the document type.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder accountingDocumentTypeName(@Nullable String accountingDocumentTypeName)
Original property name from the Odata EDM: AccountingDocumentTypeName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentDate(@Nullable LocalDateTime paymentDate)
Original property name from the Odata EDM: PaymentDate
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder customer(@Nullable String customer)
Original property name from the Odata EDM: Customer
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentTerms(@Nullable String paymentTerms)
Original property name from the Odata EDM: PaymentTerms
It is used in sales orders, purchase orders, and invoices. Terms of payment provide information for:Cash managementDunning proceduresPayment transactionsData can be entered in the field for the terms of payment key in various ways as you enter a business transaction:In most business transactions, the system defaults the key specified in the master record of the customer/vendor in question.In some transactions (for example, credit memos), however, the system does not default the key from the master record. Despite this, you can use the key from the customer/vendor master record by entering "*" in the field.Regardless of whether or not a key is defaulted from the master record, you can manually enter a key during document entry at:item level in sales ordersheader level in purchase orders and invoicesMaster records have separate areas for Financial Accounting, Sales, and Purchasing. You can specify different terms of payment keys in each of these areas. When you then enter a business transaction, the application in question will use the key specified in its area of the master record.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentMethod(@Nullable String paymentMethod)
Original property name from the Odata EDM: PaymentMethod
Payment methods are entered in the master records of customers and vendors in order to specify how payments are made. If an open item is to be paid using a specific payment method, enter it in the open item. The terms which have been defined for the payment method must be satisfied for the payment.Payment methods are to be defined in the Financial Accounting configuration menu, where the following steps are to be carried out:First of all, make all specifications that are required for a country-specific payment method.Then define per company code the terms under which a payment method can be used.All payment methods are displayed in the customer or vendor master record in the screen for selecting the payment method. Here you select the required payment method by marking it; the system transfers the payment methods to the customer/vendor master record.
exchange.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentMethodName(@Nullable String paymentMethodName)
Original property name from the Odata EDM: PaymentMethodName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentMethodSupplement(@Nullable String paymentMethodSupplement)
Original property name from the Odata EDM: PaymentMethodSupplement
Items with different payment method supplements are settled individually. When printing a form, it is possible to print separately according to payment method supplement. Checks can thus be divided into several groups that are then subject to a number of different checking procedures in the company before being mailed, for example.When entering invoices, the payment method supplement is defaulted from the master record of the customer/vendor. You can overwrite this supplement.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentMethodSupplementName(@Nullable String paymentMethodSupplementName)
Original property name from the Odata EDM: PaymentMethodSupplementName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentBlockingReason(@Nullable String paymentBlockingReason)
Original property name from the Odata EDM: PaymentBlockingReason
The following payment blocks exist:Manual payment blockIf you manually select a payment block from the list field to block an invoice for payment, the payment block field in the header of the invoice document is marked with the appropriate indicator.Blocked due to differencesIf invoices are to be blocked automatically due to differences in the invoice items, the system enters the payment block R in the vendor line of the Accounting document. The field in the header of the invoice document remains empty.Random payment blockInvoices that do not show any other blocking reason, can be blocked in accordance with the random principle. In Customizing for the Logistics invoice verification, you can set the probability for the block. The indicator for the logistical payment block is entered in the header of the invoice document.If you have set a manual payment block, and an invoice is blocked automatically due to differences in the invoice items, the system enters the manual payment block in the vendor line of the Accounting document.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder paymentBlockingReasonName(@Nullable String paymentBlockingReasonName)
Original property name from the Odata EDM: PaymentBlockingReasonName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder payerPayeeFullName(@Nullable String payerPayeeFullName)
Original property name from the Odata EDM: PayerPayeeFullName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder houseBank(@Nullable String houseBank)
Original property name from the Odata EDM: HouseBank
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder stateCentralBankPaymentReason(@Nullable String stateCentralBankPaymentReason)
Original property name from the Odata EDM: StateCentralBankPaymentReason
In foreign payment transactions, information concerning the reason for payment is needed for the report according to German foreign trade regulations (AWV).The possible reasons for payment are defined within configuration for SCB indicators. This includes certain indicators which are the key to the reasons for payment, and an explanatory text.The reasons for payment appear on the reporting form and/or in the corresponding data medium exchange.AustriaFor foreign bank transfers, the explanatory text for the OeNB is determined using this indicator on the bank transfer form or in the data medium exchange.BelgiumThe content of the first text field for this indicator is used in the data medium exchange.NetherlandsThe usage of the state central bank indicator, the document type and the texts for this indicator is explained in the detailed documentation for the individual fields.JapanFor foreign bank transfers, the reason for payment is determined by this indicator when reporting to the Japanese ministry of finance.We recommend entering a "J" as the first letter so that you can better distinguish this report from other non-Japanese reports.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder supplyingCountry(@Nullable String supplyingCountry)
Original property name from the Odata EDM: SupplyingCountry
This field contains the country key of the purchasing country in the case of imports or transits (field U4 or field V5 on the data medium) or that of the country of investment in the case of capital transactions (field W7).Together with the German State Central Bank indicator, this specification is needed for creating reports in line with German foreign trade regulations.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder countryName(@Nullable String countryName)
Original property name from the Odata EDM: CountryName
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 TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder 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 TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder journalEntryItemText(@Nullable String journalEntryItemText)
Original property name from the Odata EDM: JournalEntryItemText
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder businessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder businessAreaName(@Nullable String businessAreaName)
Original property name from the Odata EDM: BusinessAreaName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder costCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialTransactionType(@Nullable String financialTransactionType)
Original property name from the Odata EDM: FinancialTransactionType
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialTransactionTypeName(@Nullable String financialTransactionTypeName)
Original property name from the Odata EDM: FinancialTransactionTypeName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder partnerCompany(@Nullable String partnerCompany)
Original property name from the Odata EDM: PartnerCompany
Within the framework of consolidation, for example, elimination of IC sales takes place using this company ID. Affiliated companies are displayed separately in the reports for the German foreign trade regulations.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder companyName(@Nullable String companyName)
Original property name from the Odata EDM: CompanyName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder counterparty(@Nullable String counterparty)
Original property name from the Odata EDM: Counterparty
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder counterpartyFullName(@Nullable String counterpartyFullName)
Original property name from the Odata EDM: CounterpartyFullName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder issuer(@Nullable String issuer)
Original property name from the Odata EDM: Issuer
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder issuerFullName(@Nullable String issuerFullName)
Original property name from the Odata EDM: IssuerFullName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder specialGLCode(@Nullable String specialGLCode)
Original property name from the Odata EDM: SpecialGLCode
For all line items in customer or vendor accounts that are updated to an alternative reconciliation account, the special G/L indicator determines which account is to be selected.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder specialGLCodeName(@Nullable String specialGLCodeName)
Original property name from the Odata EDM: SpecialGLCodeName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryBusinessTransaction(@Nullable UUID treasuryBusinessTransaction)
Original property name from the Odata EDM: TreasuryBusinessTransaction
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryValuationArea(@Nullable String treasuryValuationArea)
Original property name from the Odata EDM: TreasuryValuationArea
per different accounting regulations.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryValuationAreaName(@Nullable String treasuryValuationAreaName)
Original property name from the Odata EDM: TreasuryValuationAreaName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder referenceDocument(@Nullable String referenceDocument)
Original property name from the Odata EDM: ReferenceDocument
See also:Reference transactionReference organization unitLogical system for the source document
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder 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 TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder 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 TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder fiscalPeriod(@Nullable String fiscalPeriod)
Original property name from the Odata EDM: FiscalPeriod
You might choose, for example, to divide your fiscal year into 12 periods (per calendar month) or 13 periods (every four weeks).If you define fewer than 16 periods, the remaining periods (for example, 13-16 or 14-16) can be used as special periods.In the case of accounting documents, the period to be updated is either taken from the posting date or, if a special period is to be updated instead of the last period of a fiscal year, entered manually.
updated. You define how a fiscal year is divided into periods per company code.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder 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 TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder reversalReferenceDocument(@Nullable String reversalReferenceDocument)
Original property name from the Odata EDM: ReversalReferenceDocument
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder reversalReferenceDocumentCntxt(@Nullable String reversalReferenceDocumentCntxt)
Original property name from the Odata EDM: ReversalReferenceDocumentCntxt
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder reverseDocumentPostingDate(@Nullable LocalDateTime reverseDocumentPostingDate)
Original property name from the Odata EDM: ReverseDocumentPostingDate
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder reverseDocumentFiscalPeriod(@Nullable String reverseDocumentFiscalPeriod)
Original property name from the Odata EDM: ReverseDocumentFiscalPeriod
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder reverseDocumentFiscalYear(@Nullable String reverseDocumentFiscalYear)
Original property name from the Odata EDM: ReverseDocumentFiscalYear
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder ledger(@Nullable String ledger)
Original property name from the Odata EDM: Ledger
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder documentDate(@Nullable LocalDateTime documentDate)
Original property name from the Odata EDM: DocumentDate
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder accountingPrinciple(@Nullable String accountingPrinciple)
Original property name from the Odata EDM: AccountingPrinciple
Examples of accounting principles are:IAS ("International Accounting Standard") andUS GAAP ("Generally Accepted Accounting Principle").The characteristic "accounting principle" serves to simplify depiction of parallel accounting in the system.Use in R/3In Customizing for Finance, a ledger or ledger group can be assigned to an accounting principle: If an assignment of this kind is made, documents that are posted in this accounting principle will only be posted to the assigned special ledger.Documents where the characteristic "accounting principle" has not been filled will be posted to all ledgers and all then posted on to all other Accounting applications.For performance reasons, you can summarize several different accounting principles in one entry, for example, you create one accounting principle for IAS/US GAAP. This can be useful if, in an application, you have to create the data for each accounting principle, even if the postings derived from the data are identical for each accounting principle.If, for example, you reflect both IAS and US GAAP in your system, in the application Manual Accruals, you have to create one accrual item for each accounting principle. However, the accruals are identical for IAS and US GAAP. You therefore only have to create one accounting principle in the system, for example IAS/US GAAP for Accruals.
statements are drawn up and rendered.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryAcctgPostingCategory(@Nullable String treasuryAcctgPostingCategory)
Original property name from the Odata EDM: TreasuryAcctgPostingCategory
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryBusinessTransCategory(@Nullable String treasuryBusinessTransCategory)
Original property name from the Odata EDM: TreasuryBusinessTransCategory
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryBusTransCategoryName(@Nullable String treasuryBusTransCategoryName)
Original property name from the Odata EDM: TreasuryBusTransCategoryName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder documentHeaderText(@Nullable String documentHeaderText)
Original property name from the Odata EDM: DocumentHeaderText
not only for certain line items.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder documentReferenceID(@Nullable String documentReferenceID)
Original property name from the Odata EDM: DocumentReferenceID
The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number.Enter the number specified by the business partner. If the document was created in-house and you do not know the business partner document number, you can copy the document number into the reference number field by entering "*".
contain a different value.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrValuationClass(@Nullable String financialInstrValuationClass)
Original property name from the Odata EDM: FinancialInstrValuationClass
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrValClassName(@Nullable String financialInstrValClassName)
Original property name from the Odata EDM: FinancialInstrValClassName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryValuationClass(@Nullable String treasuryValuationClass)
Original property name from the Odata EDM: TreasuryValuationClass
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryValuationClassName(@Nullable String treasuryValuationClassName)
Original property name from the Odata EDM: TreasuryValuationClassName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrumentProductType(@Nullable String financialInstrumentProductType)
Original property name from the Odata EDM: FinancialInstrumentProductType
Examples:Stocks: Domestic and foreign stocksBonds: Fixed-rate bonds, variable-rate bonds and zero bonds
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrProdTypeName(@Nullable String financialInstrProdTypeName)
Original property name from the Odata EDM: FinancialInstrProdTypeName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder securityAccount(@Nullable String securityAccount)
Original property name from the Odata EDM: SecurityAccount
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder securityAccountName(@Nullable String securityAccountName)
Original property name from the Odata EDM: SecurityAccountName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder securityClass(@Nullable String securityClass)
Original property name from the Odata EDM: SecurityClass
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder securityClassName(@Nullable String securityClassName)
Original property name from the Odata EDM: SecurityClassName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder securityClassDescription(@Nullable String securityClassDescription)
Original property name from the Odata EDM: SecurityClassDescription
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder differentiationPortfolio(@Nullable String differentiationPortfolio)
Original property name from the Odata EDM: DifferentiationPortfolio
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder differentiationPortfolioName(@Nullable String differentiationPortfolioName)
Original property name from the Odata EDM: DifferentiationPortfolioName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder securityAccountGroup(@Nullable String securityAccountGroup)
Original property name from the Odata EDM: SecurityAccountGroup
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder securityAccountGroupName(@Nullable String securityAccountGroupName)
Original property name from the Odata EDM: SecurityAccountGroupName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder loanContract(@Nullable String loanContract)
Original property name from the Odata EDM: LoanContract
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder loanContractName(@Nullable String loanContractName)
Original property name from the Odata EDM: LoanContractName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryPositionAccount(@Nullable String treasuryPositionAccount)
Original property name from the Odata EDM: TreasuryPositionAccount
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryPositionAccountName(@Nullable String treasuryPositionAccountName)
Original property name from the Odata EDM: TreasuryPositionAccountName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder treasuryPositionLongShortCode(@Nullable String treasuryPositionLongShortCode)
Original property name from the Odata EDM: TreasuryPositionLongShortCode
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder fund(@Nullable String fund)
Original property name from the Odata EDM: Fund
If you assign the budget to a fund, you can generate a detailed origin statement for your funds.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder 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 TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder centralClearingAccount(@Nullable String centralClearingAccount)
Original property name from the Odata EDM: CentralClearingAccount
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder centralClearingAccountName(@Nullable String centralClearingAccountName)
Original property name from the Odata EDM: CentralClearingAccountName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder activityFinancialTransaction(@Nullable String activityFinancialTransaction)
Original property name from the Odata EDM: ActivityFinancialTransaction
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialTransaction(@Nullable String financialTransaction)
Original property name from the Odata EDM: FinancialTransaction
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder createdByUser(@Nullable String createdByUser)
Original property name from the Odata EDM: CreatedByUser
entered here for tables which have a history per key definition.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder creationDate(@Nullable LocalDateTime creationDate)
Original property name from the Odata EDM: CreationDate
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder lastChangedByUser(@Nullable String lastChangedByUser)
Original property name from the Odata EDM: LastChangedByUser
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder lastChangeDate(@Nullable LocalDateTime lastChangeDate)
Original property name from the Odata EDM: LastChangeDate
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder gLAccountLongName(@Nullable String gLAccountLongName)
Original property name from the Odata EDM: GLAccountLongName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder costCenterName(@Nullable String costCenterName)
Original property name from the Odata EDM: CostCenterName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrTransactionType(@Nullable String financialInstrTransactionType)
Original property name from the Odata EDM: FinancialInstrTransactionType
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrTransTypeName(@Nullable String financialInstrTransTypeName)
Original property name from the Odata EDM: FinancialInstrTransTypeName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrCharacteristic(@Nullable String financialInstrCharacteristic)
Original property name from the Odata EDM: FinancialInstrCharacteristic
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrumentReference(@Nullable String financialInstrumentReference)
Original property name from the Odata EDM: FinancialInstrumentReference
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialInstrumentAssignment(@Nullable String financialInstrumentAssignment)
Original property name from the Odata EDM: FinancialInstrumentAssignment
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder portfolio(@Nullable String portfolio)
Original property name from the Odata EDM: Portfolio
purposes.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder letterOfCredit(@Nullable String letterOfCredit)
Original property name from the Odata EDM: LetterOfCredit
enquiry, and amendment.public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder hedgingClassification(@Nullable String hedgingClassification)
Original property name from the Odata EDM: HedgingClassification
You define the hedging classifications in the Configure Your Solution app under Finance -> Treasury and Risk Management -> General Settings -> Define Hedging Classifications.The freely definable hedging classifications are used in the following way:In the definition of your hedging areas you assign the relevant hedging classifications on the General Settings tab.You can assign n hedging classifications to a hedging area.A hedging classification that is active for hedge accounting can only be assigned to one hedging area that is relevant for hedge accounting.Hedging classifications that are inactive for hedge accounting can be assigned to n hedging areas.On tab Hedge Accounting II you can assign the hedging profiles as a function of the hedging classification.You assign the hedging classifications to your hedging instruments in the financial transaction data on the Administration tab.If the hedging classification is active for hedge accounting, this information is relevant for the automated designation process. Using the data from the financial transaction including the hedging classification the system can identify the relevant hedging area version and the relevant exposure item so the hedged item, hedging instrument, hedging relationship and the planned designation flows can be created according to your settings for the hedging area.For more information, see the product assistance for Treasury and Risk Management on SAP Help Portal for SAP S/4 HANA Cloud.
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder hedgingClassificationName(@Nullable String hedgingClassificationName)
Original property name from the Odata EDM: HedgingClassificationName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialExposureItem(@Nullable String financialExposureItem)
Original property name from the Odata EDM: FinancialExposureItem
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialExposureItemName(@Nullable String financialExposureItemName)
Original property name from the Odata EDM: FinancialExposureItemName
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialExposureSubItem(@Nullable String financialExposureSubItem)
Original property name from the Odata EDM: FinancialExposureSubItem
public TrsyPostgJrnlEntrItm.TrsyPostgJrnlEntrItmBuilder financialExposureSubItemName(@Nullable String financialExposureSubItemName)
Original property name from the Odata EDM: FinancialExposureSubItemName
public TrsyPostgJrnlEntrItm build()
Copyright © 2019 SAP SE. All rights reserved.