public class OperationalAcctgDocItemCube extends VdmEntity<OperationalAcctgDocItemCube>
Original entity name from the Odata EDM: A_OperationalAcctgDocItemCubeType
Modifier and Type | Field and Description |
---|---|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNT_ASSIGNMENT_NUMBER
Use with available fluent helpers to apply the AccountAssignmentNumber field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOC_CREATED_BY_USER
Use with available fluent helpers to apply the AccountingDocCreatedByUser field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT
Use with available fluent helpers to apply the AccountingDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_CATEGORY
Use with available fluent helpers to apply the AccountingDocumentCategory field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_CATEGORY_NAME
Use with available fluent helpers to apply the AccountingDocumentCategoryName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_CLASS
Use with available fluent helpers to apply the AccountingDocumentClass field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
ACCOUNTING_DOCUMENT_CREATION_DATE
Use with available fluent helpers to apply the AccountingDocumentCreationDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_HEADER_TEXT
Use with available fluent helpers to apply the AccountingDocumentHeaderText field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_ITEM
Use with available fluent helpers to apply the AccountingDocumentItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_ITEM_REF
Use with available fluent helpers to apply the AccountingDocumentItemRef field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_ITEM_TYPE
Use with available fluent helpers to apply the AccountingDocumentItemType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_TYPE
Use with available fluent helpers to apply the AccountingDocumentType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTING_DOCUMENT_TYPE_NAME
Use with available fluent helpers to apply the AccountingDocumentTypeName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ACCOUNTS_RECEIVABLE_IS_PLEDGED
Use with available fluent helpers to apply the AccountsReceivableIsPledged field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ADDITIONAL_CURRENCY1
Use with available fluent helpers to apply the AdditionalCurrency1 field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ADDITIONAL_CURRENCY2
Use with available fluent helpers to apply the AdditionalCurrency2 field to query operations.
|
static OperationalAcctgDocItemCubeSelectable |
ALL_FIELDS
Selector for all available fields of OperationalAcctgDocItemCube.
|
static OperationalAcctgDocItemCubeField<String> |
ALTERNATIVE_GL_ACCOUNT
Use with available fluent helpers to apply the AlternativeGLAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ALTERNATIVE_REFERENCE_DOCUMENT
Use with available fluent helpers to apply the AlternativeReferenceDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
AMOUNT_IN_ADDITIONAL_CURRENCY1
Use with available fluent helpers to apply the AmountInAdditionalCurrency1 field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
AMOUNT_IN_ADDITIONAL_CURRENCY2
Use with available fluent helpers to apply the AmountInAdditionalCurrency2 field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
AMOUNT_IN_BALANCE_TRANSAC_CRCY
Use with available fluent helpers to apply the AmountInBalanceTransacCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
AMOUNT_IN_COMPANY_CODE_CURRENCY
Use with available fluent helpers to apply the AmountInCompanyCodeCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
AMOUNT_IN_PAYMENT_CURRENCY
Use with available fluent helpers to apply the AmountInPaymentCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
AMOUNT_IN_TRANSACTION_CURRENCY
Use with available fluent helpers to apply the AmountInTransactionCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ASSET_CONTRACT
Use with available fluent helpers to apply the AssetContract field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ASSET_TRANSACTION_TYPE
Use with available fluent helpers to apply the AssetTransactionType field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
ASSET_VALUE_DATE
Use with available fluent helpers to apply the AssetValueDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ASSIGNMENT_REFERENCE
Use with available fluent helpers to apply the AssignmentReference field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BALANCE_TRANSACTION_CURRENCY
Use with available fluent helpers to apply the BalanceTransactionCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BASE_UNIT
Use with available fluent helpers to apply the BaseUnit field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BATCH_INPUT_SESSION
Use with available fluent helpers to apply the BatchInputSession field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BILL_OF_EXCHANGE_USAGE
Use with available fluent helpers to apply the BillOfExchangeUsage field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BILLING_DOCUMENT
Use with available fluent helpers to apply the BillingDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BP_BANK_ACCOUNT_INTERNAL_ID
Use with available fluent helpers to apply the BPBankAccountInternalID field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BRANCH
Use with available fluent helpers to apply the Branch field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BRANCH_ACCOUNT
Use with available fluent helpers to apply the BranchAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BRANCH_CODE
Use with available fluent helpers to apply the BranchCode field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BUDGET_PERIOD
Use with available fluent helpers to apply the BudgetPeriod field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BUSINESS_AREA
Use with available fluent helpers to apply the BusinessArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BUSINESS_AREA_NAME
Use with available fluent helpers to apply the BusinessAreaName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BUSINESS_PLACE
Use with available fluent helpers to apply the BusinessPlace field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BUSINESS_PROCESS
Use with available fluent helpers to apply the BusinessProcess field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
BUSINESS_TRANSACTION_TYPE
Use with available fluent helpers to apply the BusinessTransactionType field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CASH_DISCOUNT_AMOUNT
Use with available fluent helpers to apply the CashDiscountAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CASH_DISCOUNT_AMT_IN_CO_CODE_CRCY
Use with available fluent helpers to apply the CashDiscountAmtInCoCodeCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CASH_DISCOUNT_BASE_AMOUNT
Use with available fluent helpers to apply the CashDiscountBaseAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CASH_DISCOUNT1_DAYS
Use with available fluent helpers to apply the CashDiscount1Days field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
CASH_DISCOUNT1_DUE_DATE
Use with available fluent helpers to apply the CashDiscount1DueDate field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CASH_DISCOUNT1_PERCENT
Use with available fluent helpers to apply the CashDiscount1Percent field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CASH_DISCOUNT2_DAYS
Use with available fluent helpers to apply the CashDiscount2Days field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
CASH_DISCOUNT2_DUE_DATE
Use with available fluent helpers to apply the CashDiscount2DueDate field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CASH_DISCOUNT2_PERCENT
Use with available fluent helpers to apply the CashDiscount2Percent field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CASH_FLOW_TYPE
Use with available fluent helpers to apply the CashFlowType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CHART_OF_ACCOUNTS
Use with available fluent helpers to apply the ChartOfAccounts field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CLEARING_ACCOUNTING_DOCUMENT
Use with available fluent helpers to apply the ClearingAccountingDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
CLEARING_CREATION_DATE
Use with available fluent helpers to apply the ClearingCreationDate field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
CLEARING_DATE
Use with available fluent helpers to apply the ClearingDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CLEARING_DOC_FISCAL_YEAR
Use with available fluent helpers to apply the ClearingDocFiscalYear field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
CLEARING_IS_REVERSED
Use with available fluent helpers to apply the ClearingIsReversed field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
CLEARING_ITEM
Use with available fluent helpers to apply the ClearingItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COMMITMENT_ITEM
Use with available fluent helpers to apply the CommitmentItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COMPANY_CODE_CURRENCY
Use with available fluent helpers to apply the CompanyCodeCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COMPANY_CODE_CURRENCY_DETN_METHOD
Use with available fluent helpers to apply the CompanyCodeCurrencyDetnMethod field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COMPANY_CODE_NAME
Use with available fluent helpers to apply the CompanyCodeName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CONTROLLING_AREA
Use with available fluent helpers to apply the ControllingArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CONTROLLING_AREA_NAME
Use with available fluent helpers to apply the ControllingAreaName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CORPORATE_GROUP_ACCOUNT
Use with available fluent helpers to apply the CorporateGroupAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COST_CENTER
Use with available fluent helpers to apply the CostCenter field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COST_CENTER_NAME
Use with available fluent helpers to apply the CostCenterName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COST_CTR_ACTIVITY_TYPE
Use with available fluent helpers to apply the CostCtrActivityType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COST_ELEMENT
Use with available fluent helpers to apply the CostElement field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COST_OBJECT
Use with available fluent helpers to apply the CostObject field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
COST_ORIGIN_GROUP
Use with available fluent helpers to apply the CostOriginGroup field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalTime> |
CREATION_TIME
Use with available fluent helpers to apply the CreationTime field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CREDIT_CONTROL_AREA
Use with available fluent helpers to apply the CreditControlArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CREDIT_CONTROL_AREA_CURRENCY
Use with available fluent helpers to apply the CreditControlAreaCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CUSTOMER
Use with available fluent helpers to apply the Customer field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
CUSTOMER_IS_IN_EXECUTION
Use with available fluent helpers to apply the CustomerIsInExecution field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
CUSTOMER_NAME
Use with available fluent helpers to apply the CustomerName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DATA_EXCHANGE_INSTRUCTION1
Use with available fluent helpers to apply the DataExchangeInstruction1 field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DATA_EXCHANGE_INSTRUCTION2
Use with available fluent helpers to apply the DataExchangeInstruction2 field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DATA_EXCHANGE_INSTRUCTION3
Use with available fluent helpers to apply the DataExchangeInstruction3 field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DATA_EXCHANGE_INSTRUCTION4
Use with available fluent helpers to apply the DataExchangeInstruction4 field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DEBIT_CREDIT_CODE
Use with available fluent helpers to apply the DebitCreditCode field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DELIV_OF_GOODS_DEST_COUNTRY
Use with available fluent helpers to apply the DelivOfGoodsDestCountry field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
DOCUMENT_DATE
Use with available fluent helpers to apply the DocumentDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DOCUMENT_ITEM_TEXT
Use with available fluent helpers to apply the DocumentItemText field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DOCUMENT_REFERENCE_ID
Use with available fluent helpers to apply the DocumentReferenceID field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
DUE_CALCULATION_BASE_DATE
Use with available fluent helpers to apply the DueCalculationBaseDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DUNNING_AREA
Use with available fluent helpers to apply the DunningArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DUNNING_BLOCKING_REASON
Use with available fluent helpers to apply the DunningBlockingReason field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DUNNING_KEY
Use with available fluent helpers to apply the DunningKey field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
DUNNING_LEVEL
Use with available fluent helpers to apply the DunningLevel field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
EXCHANGE_RATE
Use with available fluent helpers to apply the ExchangeRate field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
EXCHANGE_RATE_DATE
Use with available fluent helpers to apply the ExchangeRateDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
EXCHANGE_RATE_TYPE
Use with available fluent helpers to apply the ExchangeRateType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FINANCIAL_ACCOUNT_TYPE
Use with available fluent helpers to apply the FinancialAccountType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FINANCIAL_MANAGEMENT_AREA
Use with available fluent helpers to apply the FinancialManagementArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FINANCIAL_TRANSACTION_TYPE
Use with available fluent helpers to apply the FinancialTransactionType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FISCAL_PERIOD
Use with available fluent helpers to apply the FiscalPeriod field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FISCAL_YEAR
Use with available fluent helpers to apply the FiscalYear field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FIXED_ASSET
Use with available fluent helpers to apply the FixedAsset field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FIXED_CASH_DISCOUNT
Use with available fluent helpers to apply the FixedCashDiscount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FOLLOW_ON_DOCUMENT_TYPE
Use with available fluent helpers to apply the FollowOnDocumentType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FUNCTIONAL_AREA
Use with available fluent helpers to apply the FunctionalArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FUNCTIONAL_AREA_NAME
Use with available fluent helpers to apply the FunctionalAreaName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FUND
Use with available fluent helpers to apply the Fund field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FUNDED_PROGRAM
Use with available fluent helpers to apply the FundedProgram field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
FUNDS_CENTER
Use with available fluent helpers to apply the FundsCenter field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
GL_ACCOUNT
Use with available fluent helpers to apply the GLAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
GL_ACCOUNT_LONG_NAME
Use with available fluent helpers to apply the GLAccountLongName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
GL_ACCOUNT_NAME
Use with available fluent helpers to apply the GLAccountName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
GOODS_MOVEMENT_ENTRY_UNIT
Use with available fluent helpers to apply the GoodsMovementEntryUnit field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
GRANT_ID
Use with available fluent helpers to apply the GrantID field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
HAS_PAYMENT_ORDER
Use with available fluent helpers to apply the HasPaymentOrder field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
HEDGED_AMOUNT
Use with available fluent helpers to apply the HedgedAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
HOUSE_BANK
Use with available fluent helpers to apply the HouseBank field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
HOUSE_BANK_ACCOUNT
Use with available fluent helpers to apply the HouseBankAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
INTERCOMPANY_TRANSACTION
Use with available fluent helpers to apply the IntercompanyTransaction field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
INVENTORY_VALUATION_TYPE
Use with available fluent helpers to apply the InventoryValuationType field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
INVOICE_AMOUNT_IN_FRGN_CURRENCY
Use with available fluent helpers to apply the InvoiceAmountInFrgnCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
INVOICE_AMT_IN_CO_CODE_CRCY
Use with available fluent helpers to apply the InvoiceAmtInCoCodeCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
INVOICE_ITEM_REFERENCE
Use with available fluent helpers to apply the InvoiceItemReference field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
INVOICE_LIST
Use with available fluent helpers to apply the InvoiceList field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
INVOICE_RECEIPT_DATE
Use with available fluent helpers to apply the InvoiceReceiptDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
INVOICE_REFERENCE
Use with available fluent helpers to apply the InvoiceReference field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
INVOICE_REFERENCE_FISCAL_YEAR
Use with available fluent helpers to apply the InvoiceReferenceFiscalYear field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_AUTOMATICALLY_CREATED
Use with available fluent helpers to apply the IsAutomaticallyCreated field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_BALANCE_SHEET_ACCOUNT
Use with available fluent helpers to apply the IsBalanceSheetAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_CLEARED
Use with available fluent helpers to apply the IsCleared field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_COMPLETELY_DELIVERED
Use with available fluent helpers to apply the IsCompletelyDelivered field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_EU_TRIANGULAR_DEAL
Use with available fluent helpers to apply the IsEUTriangularDeal field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_NEGATIVE_POSTING
Use with available fluent helpers to apply the IsNegativePosting field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_NOT_CASH_DISCOUNT_LIABLE
Use with available fluent helpers to apply the IsNotCashDiscountLiable field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
IS_OPEN_ITEM_MANAGED
Use with available fluent helpers to apply the IsOpenItemManaged field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_REVERSAL
Use with available fluent helpers to apply the IsReversal field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_REVERSED
Use with available fluent helpers to apply the IsReversed field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_SALES_RELATED
Use with available fluent helpers to apply the IsSalesRelated field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
IS_USED_IN_PAYMENT_TRANSACTION
Use with available fluent helpers to apply the IsUsedInPaymentTransaction field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
JOINT_VENTURE
Use with available fluent helpers to apply the JointVenture field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
JOINT_VENTURE_COST_RECOVERY_CODE
Use with available fluent helpers to apply the JointVentureCostRecoveryCode field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
JOINT_VENTURE_EQUITY_GROUP
Use with available fluent helpers to apply the JointVentureEquityGroup field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
JOINT_VENTURE_EQUITY_TYPE
Use with available fluent helpers to apply the JointVentureEquityType field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
LAST_CHANGE_DATE
Use with available fluent helpers to apply the LastChangeDate field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
LAST_DUNNING_DATE
Use with available fluent helpers to apply the LastDunningDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
LATE_PAYMENT_REASON
Use with available fluent helpers to apply the LatePaymentReason field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
LEDGER
Use with available fluent helpers to apply the Ledger field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
LEDGER_GL_LINE_ITEM
Use with available fluent helpers to apply the LedgerGLLineItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
LEDGER_GROUP
Use with available fluent helpers to apply the LedgerGroup field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
LINE_ITEM_DISPLAY_IS_ENABLED
Use with available fluent helpers to apply the LineItemDisplayIsEnabled field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
LOGICAL_SYSTEM
Use with available fluent helpers to apply the LogicalSystem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
MASTER_FIXED_ASSET
Use with available fluent helpers to apply the MasterFixedAsset field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
MATERIAL
Use with available fluent helpers to apply the Material field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
MATERIAL_PRICE_CONTROL
Use with available fluent helpers to apply the MaterialPriceControl field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
MATERIAL_PRICE_UNIT_QTY
Use with available fluent helpers to apply the MaterialPriceUnitQty field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
NET_DUE_DATE
Use with available fluent helpers to apply the NetDueDate field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
NET_PAYMENT_AMOUNT
Use with available fluent helpers to apply the NetPaymentAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
NET_PAYMENT_DAYS
Use with available fluent helpers to apply the NetPaymentDays field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
NUMBER_OF_ITEMS
Use with available fluent helpers to apply the NumberOfItems field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
OFFSETTING_ACCOUNT
Use with available fluent helpers to apply the OffsettingAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
OFFSETTING_ACCOUNT_TYPE
Use with available fluent helpers to apply the OffsettingAccountType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
OPERATIONAL_GL_ACCOUNT
Use with available fluent helpers to apply the OperationalGLAccount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ORDER_ID
Use with available fluent helpers to apply the OrderID field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ORDER_INT_BILL_OF_OPERATIONS_ITEM
Use with available fluent helpers to apply the OrderIntBillOfOperationsItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ORDER_INTERNAL_BILL_OF_OPERATIONS
Use with available fluent helpers to apply the OrderInternalBillOfOperations field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
ORIGINAL_REFERENCE_DOCUMENT
Use with available fluent helpers to apply the OriginalReferenceDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
ORIGINAL_TAX_BASE_AMOUNT
Use with available fluent helpers to apply the OriginalTaxBaseAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_BUDGET_PERIOD
Use with available fluent helpers to apply the PartnerBudgetPeriod field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_BUSINESS_AREA
Use with available fluent helpers to apply the PartnerBusinessArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_COMPANY
Use with available fluent helpers to apply the PartnerCompany field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_FUNCTIONAL_AREA
Use with available fluent helpers to apply the PartnerFunctionalArea field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_FUND
Use with available fluent helpers to apply the PartnerFund field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_GRANT
Use with available fluent helpers to apply the PartnerGrant field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_PROFIT_CENTER
Use with available fluent helpers to apply the PartnerProfitCenter field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PARTNER_SEGMENT
Use with available fluent helpers to apply the PartnerSegment field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_BLOCKING_REASON
Use with available fluent helpers to apply the PaymentBlockingReason field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_CARD_ITEM
Use with available fluent helpers to apply the PaymentCardItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_CARD_PAYMENT_SETTLEMENT
Use with available fluent helpers to apply the PaymentCardPaymentSettlement field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_CURRENCY
Use with available fluent helpers to apply the PaymentCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_DIFFERENCE_REASON
Use with available fluent helpers to apply the PaymentDifferenceReason field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_METHOD
Use with available fluent helpers to apply the PaymentMethod field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_METHOD_SUPPLEMENT
Use with available fluent helpers to apply the PaymentMethodSupplement field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_REFERENCE
Use with available fluent helpers to apply the PaymentReference field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PAYMENT_TERMS
Use with available fluent helpers to apply the PaymentTerms field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PERSONNEL_NUMBER
Use with available fluent helpers to apply the PersonnelNumber field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
PLANNED_AMT_IN_TRANSACTION_CRCY
Use with available fluent helpers to apply the PlannedAmtInTransactionCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
PLANNED_REVERSAL_DATE
Use with available fluent helpers to apply the PlannedReversalDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PLANNING_LEVEL
Use with available fluent helpers to apply the PlanningLevel field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PLANT
Use with available fluent helpers to apply the Plant field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
POSTING_DATE
Use with available fluent helpers to apply the PostingDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
POSTING_KEY
Use with available fluent helpers to apply the PostingKey field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PRODUCT
Use with available fluent helpers to apply the Product field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PROFIT_CENTER
Use with available fluent helpers to apply the ProfitCenter field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PROFIT_CENTER_NAME
Use with available fluent helpers to apply the ProfitCenterName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PROFIT_LOSS_ACCOUNT_TYPE
Use with available fluent helpers to apply the ProfitLossAccountType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PROFITABILITY_SEGMENT
Use with available fluent helpers to apply the ProfitabilitySegment field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PROJECT
Use with available fluent helpers to apply the Project field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PROJECT_NETWORK
Use with available fluent helpers to apply the ProjectNetwork field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
PURCHASE_ORDER_QTY
Use with available fluent helpers to apply the PurchaseOrderQty field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PURCHASING_DOCUMENT
Use with available fluent helpers to apply the PurchasingDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PURCHASING_DOCUMENT_ITEM
Use with available fluent helpers to apply the PurchasingDocumentItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
PURCHASING_DOCUMENT_PRICE_UNIT
Use with available fluent helpers to apply the PurchasingDocumentPriceUnit field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
QUANTITY
Use with available fluent helpers to apply the Quantity field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
QUANTITY_IN_ENTRY_UNIT
Use with available fluent helpers to apply the QuantityInEntryUnit field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REAL_ESTATE_OBJECT
Use with available fluent helpers to apply the RealEstateObject field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
RECURRING_ACCOUNTING_DOCUMENT
Use with available fluent helpers to apply the RecurringAccountingDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REFERENCE_DOCUMENT_LOGICAL_SYSTEM
Use with available fluent helpers to apply the ReferenceDocumentLogicalSystem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REFERENCE_DOCUMENT_TYPE
Use with available fluent helpers to apply the ReferenceDocumentType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REFERENCE1_I_D_BY_BUSINESS_PARTNER
Use with available fluent helpers to apply the Reference1IDByBusinessPartner field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REFERENCE1_IN_DOCUMENT_HEADER
Use with available fluent helpers to apply the Reference1InDocumentHeader field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REFERENCE2_I_D_BY_BUSINESS_PARTNER
Use with available fluent helpers to apply the Reference2IDByBusinessPartner field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REFERENCE2_IN_DOCUMENT_HEADER
Use with available fluent helpers to apply the Reference2InDocumentHeader field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REFERENCE3_I_D_BY_BUSINESS_PARTNER
Use with available fluent helpers to apply the Reference3IDByBusinessPartner field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REGION
Use with available fluent helpers to apply the Region field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
REVERSAL_IS_PLANNED
Use with available fluent helpers to apply the ReversalIsPlanned field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REVERSAL_REASON
Use with available fluent helpers to apply the ReversalReason field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REVERSE_DOCUMENT
Use with available fluent helpers to apply the ReverseDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
REVERSE_DOCUMENT_FISCAL_YEAR
Use with available fluent helpers to apply the ReverseDocumentFiscalYear field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SALES_DOCUMENT
Use with available fluent helpers to apply the SalesDocument field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SALES_DOCUMENT_CONDITION
Use with available fluent helpers to apply the SalesDocumentCondition field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SALES_DOCUMENT_ITEM
Use with available fluent helpers to apply the SalesDocumentItem field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SCHEDULE_LINE
Use with available fluent helpers to apply the ScheduleLine field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SEGMENT
Use with available fluent helpers to apply the Segment field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SEGMENT_NAME
Use with available fluent helpers to apply the SegmentName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SEPA_MANDATE
Use with available fluent helpers to apply the SEPAMandate field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
SETTLEMENT_REFERENCE_DATE
Use with available fluent helpers to apply the SettlementReferenceDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SOURCE_COMPANY_CODE
Use with available fluent helpers to apply the SourceCompanyCode field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SPECIAL_GL_ACCOUNT_ASSIGNMENT
Use with available fluent helpers to apply the SpecialGLAccountAssignment field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SPECIAL_GL_CODE
Use with available fluent helpers to apply the SpecialGLCode field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SPECIAL_GL_TRANSACTION_TYPE
Use with available fluent helpers to apply the SpecialGLTransactionType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
STATE_CENTRAL_BANK_PAYMENT_REASON
Use with available fluent helpers to apply the StateCentralBankPaymentReason field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SUPPLIER
Use with available fluent helpers to apply the Supplier field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SUPPLIER_NAME
Use with available fluent helpers to apply the SupplierName field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
SUPPLYING_COUNTRY
Use with available fluent helpers to apply the SupplyingCountry field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
TAX_AMOUNT
Use with available fluent helpers to apply the TaxAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
TAX_AMOUNT_IN_CO_CODE_CRCY
Use with available fluent helpers to apply the TaxAmountInCoCodeCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
TAX_BASE_AMOUNT_IN_CO_CODE_CRCY
Use with available fluent helpers to apply the TaxBaseAmountInCoCodeCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
TAX_BASE_AMOUNT_IN_TRANS_CRCY
Use with available fluent helpers to apply the TaxBaseAmountInTransCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
TAX_BASE_AMOUNT_IS_NET_AMOUNT
Use with available fluent helpers to apply the TaxBaseAmountIsNetAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TAX_CODE
Use with available fluent helpers to apply the TaxCode field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
TAX_DETERMINATION_DATE
Use with available fluent helpers to apply the TaxDeterminationDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TAX_DISTRIBUTION_CODE1
Use with available fluent helpers to apply the TaxDistributionCode1 field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TAX_DISTRIBUTION_CODE2
Use with available fluent helpers to apply the TaxDistributionCode2 field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TAX_DISTRIBUTION_CODE3
Use with available fluent helpers to apply the TaxDistributionCode3 field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
TAX_EXCHANGE_RATE
Use with available fluent helpers to apply the TaxExchangeRate field to query operations.
|
static OperationalAcctgDocItemCubeField<Boolean> |
TAX_IS_CALCULATED_AUTOMATICALLY
Use with available fluent helpers to apply the TaxIsCalculatedAutomatically field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TAX_JURISDICTION
Use with available fluent helpers to apply the TaxJurisdiction field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
TAX_REPORTING_DATE
Use with available fluent helpers to apply the TaxReportingDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TAX_SECTION
Use with available fluent helpers to apply the TaxSection field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TAX_TYPE
Use with available fluent helpers to apply the TaxType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TRANSACTION_CODE
Use with available fluent helpers to apply the TransactionCode field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TRANSACTION_CURRENCY
Use with available fluent helpers to apply the TransactionCurrency field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TRANSACTION_TYPE_DETERMINATION
Use with available fluent helpers to apply the TransactionTypeDetermination field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
TREASURY_CONTRACT_TYPE
Use with available fluent helpers to apply the TreasuryContractType field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
VALUATION_AREA
Use with available fluent helpers to apply the ValuationArea field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
VALUATION_DIFF_AMT_IN_ADDL_CRCY1
Use with available fluent helpers to apply the ValuationDiffAmtInAddlCrcy1 field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
VALUATION_DIFF_AMT_IN_ADDL_CRCY2
Use with available fluent helpers to apply the ValuationDiffAmtInAddlCrcy2 field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
VALUATION_DIFF_AMT_IN_CO_CODE_CRCY
Use with available fluent helpers to apply the ValuationDiffAmtInCoCodeCrcy field to query operations.
|
static OperationalAcctgDocItemCubeField<LocalDateTime> |
VALUE_DATE
Use with available fluent helpers to apply the ValueDate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
VAT_REGISTRATION
Use with available fluent helpers to apply the VATRegistration field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
WBS_ELEMENT_INTERNAL_ID
Use with available fluent helpers to apply the WBSElementInternalID field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
WITHHOLDING_TAX_AMOUNT
Use with available fluent helpers to apply the WithholdingTaxAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
WITHHOLDING_TAX_BASE_AMOUNT
Use with available fluent helpers to apply the WithholdingTaxBaseAmount field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
WITHHOLDING_TAX_CERTIFICATE
Use with available fluent helpers to apply the WithholdingTaxCertificate field to query operations.
|
static OperationalAcctgDocItemCubeField<String> |
WITHHOLDING_TAX_CODE
Use with available fluent helpers to apply the WithholdingTaxCode field to query operations.
|
static OperationalAcctgDocItemCubeField<BigDecimal> |
WITHHOLDING_TAX_EXEMPTION_AMT
Use with available fluent helpers to apply the WithholdingTaxExemptionAmt field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
OperationalAcctgDocItemCube() |
Modifier and Type | Method and Description |
---|---|
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> OperationalAcctgDocItemCubeField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getAccountAssignmentNumber()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AccountAssignmentNumber
|
String |
getAccountingDocCreatedByUser()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: AccountingDocCreatedByUser
|
String |
getAccountingDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: AccountingDocumentThe document number is unique per company code and fiscal year.
|
String |
getAccountingDocumentCategory()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: AccountingDocumentCategory
|
String |
getAccountingDocumentCategoryName()
Constraints: Not nullable, Maximum length: 60 Original property name from the Odata EDM: AccountingDocumentCategoryName
|
String |
getAccountingDocumentClass()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: AccountingDocumentClass
|
LocalDateTime |
getAccountingDocumentCreationDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: AccountingDocumentCreationDateNote
The posting date can differ from the entry date (date of entry in the system) and the document date.
|
String |
getAccountingDocumentHeaderText()
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: AccountingDocumentHeaderText
|
String |
getAccountingDocumentItem()
(Key Field) Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: AccountingDocumentItem
|
String |
getAccountingDocumentItemRef()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: AccountingDocumentItemRef
|
String |
getAccountingDocumentItemType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: AccountingDocumentItemTypeFor external purposes, the field content is unimportant and therefore, must not be used in customer reporting.
|
String |
getAccountingDocumentType()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AccountingDocumentTypeAttributes that control the entry of the document, or which are themselves noted in the document, are defined for each document type.
|
String |
getAccountingDocumentTypeName()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: AccountingDocumentTypeName
|
String |
getAccountsReceivableIsPledged()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AccountsReceivableIsPledged
|
String |
getAdditionalCurrency1()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: AdditionalCurrency1
|
String |
getAdditionalCurrency2()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: AdditionalCurrency2
|
String |
getAlternativeGLAccount()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: AlternativeGLAccount
|
String |
getAlternativeReferenceDocument()
Constraints: Not nullable, Maximum length: 26 Original property name from the Odata EDM: AlternativeReferenceDocument
|
BigDecimal |
getAmountInAdditionalCurrency1()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInAdditionalCurrency1
|
BigDecimal |
getAmountInAdditionalCurrency2()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInAdditionalCurrency2
|
BigDecimal |
getAmountInBalanceTransacCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInBalanceTransacCrcy
|
BigDecimal |
getAmountInCompanyCodeCurrency()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInCompanyCodeCurrency
|
BigDecimal |
getAmountInPaymentCurrency()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInPaymentCurrency
|
BigDecimal |
getAmountInTransactionCurrency()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInTransactionCurrency
|
String |
getAssetContract()
Constraints: Not nullable, Maximum length: 13 Original property name from the Odata EDM: AssetContract
|
String |
getAssetTransactionType()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: AssetTransactionType
|
LocalDateTime |
getAssetValueDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: AssetValueDateSince the asset value date can have a direct influence on the amount of depreciation, the system creates a default value when it can.
|
String |
getAssignmentReference()
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: AssignmentReference
|
String |
getBalanceTransactionCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: BalanceTransactionCurrency
|
String |
getBaseUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: BaseUnitYou define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.
|
String |
getBatchInputSession()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BatchInputSession
|
String |
getBillingDocument()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BillingDocument
|
String |
getBillOfExchangeUsage()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BillOfExchangeUsage
|
String |
getBPBankAccountInternalID()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BPBankAccountInternalID
|
String |
getBranch()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: Branch
|
String |
getBranchAccount()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BranchAccount
|
String |
getBranchCode()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: BranchCodeThe system displays this code at the time of posting sales order, MM invoice, or FI invoice.
|
String |
getBudgetPeriod()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BudgetPeriodDuring the budget period, the organization may commit, obligate, and encumber funds (terminology varies).
|
String |
getBusinessArea()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessArea
|
String |
getBusinessAreaName()
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: BusinessAreaName
|
String |
getBusinessPlace()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessPlace
|
String |
getBusinessProcess()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BusinessProcess
|
String |
getBusinessTransactionType()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessTransactionTypeA business transaction is a business event that represents a change in a certain value or quantity for a company and, as a result, needs to be entered in accounting.
|
BigDecimal |
getCashDiscount1Days()
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: CashDiscount1Days
|
LocalDateTime |
getCashDiscount1DueDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CashDiscount1DueDate
|
BigDecimal |
getCashDiscount1Percent()
Constraints: Not nullable, Precision: 5, Scale: 3 Original property name from the Odata EDM: CashDiscount1Percent
|
BigDecimal |
getCashDiscount2Days()
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: CashDiscount2Days
|
LocalDateTime |
getCashDiscount2DueDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CashDiscount2DueDate
|
BigDecimal |
getCashDiscount2Percent()
Constraints: Not nullable, Precision: 5, Scale: 3 Original property name from the Odata EDM: CashDiscount2Percent
|
BigDecimal |
getCashDiscountAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: CashDiscountAmount
|
BigDecimal |
getCashDiscountAmtInCoCodeCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: CashDiscountAmtInCoCodeCrcy
|
BigDecimal |
getCashDiscountBaseAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: CashDiscountBaseAmount
|
String |
getCashFlowType()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CashFlowTypeYou can only use a flow type in connection with a financial transaction if you have assigned the flow typy to the corresponding product type in Customizing.
|
String |
getChartOfAccounts()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ChartOfAccounts
|
String |
getClearingAccountingDocument()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ClearingAccountingDocument
|
LocalDateTime |
getClearingCreationDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ClearingCreationDate
|
LocalDateTime |
getClearingDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ClearingDate
|
String |
getClearingDocFiscalYear()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ClearingDocFiscalYear
|
Boolean |
getClearingIsReversed()
Constraints: noneOriginal property name from the Odata EDM: ClearingIsReversed
|
BigDecimal |
getClearingItem()
Constraints: Not nullable, Precision: 5, Scale: 0 Original property name from the Odata EDM: ClearingItem
|
String |
getCommitmentItem()
Constraints: Not nullable, Maximum length: 24 Original property name from the Odata EDM: CommitmentItem
|
String |
getCompanyCode()
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CompanyCode
|
String |
getCompanyCodeCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: CompanyCodeCurrency
|
String |
getCompanyCodeCurrencyDetnMethod()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: CompanyCodeCurrencyDetnMethod
|
String |
getCompanyCodeName()
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: CompanyCodeName
|
String |
getControllingArea()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ControllingArea
|
String |
getControllingAreaName()
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: ControllingAreaName
|
String |
getCorporateGroupAccount()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CorporateGroupAccount
|
String |
getCostCenter()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostCenter
|
String |
getCostCenterName()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: CostCenterName
|
String |
getCostCtrActivityType()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: CostCtrActivityTypeActivity types describe the activity produced by a cost center and are measured in units of time or quantity.
|
String |
getCostElement()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostElementItems in a chart of accounts that are relevant to cost, are referred to as cost elements.
|
String |
getCostObject()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostObjectCost objects are the activity units of business whose costs are assigned based on the cost origins.
|
String |
getCostOriginGroup()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CostOriginGroupWhen material costs are calculated, each material is given a general ledger account and thus is assigned to a primary cost element.
|
LocalTime |
getCreationTime()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CreationTime
|
String |
getCreditControlArea()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CreditControlAreaYou can also enter the credit control area separately for each posting, if this was marked in the appropriate company code.
|
String |
getCreditControlAreaCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: CreditControlAreaCurrency
|
String |
getCustomer()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Customer
|
Boolean |
getCustomerIsInExecution()
Constraints: noneOriginal property name from the Odata EDM: CustomerIsInExecution
|
String |
getCustomerName()
Constraints: Not nullable, Maximum length: 80 Original property name from the Odata EDM: CustomerName
|
String |
getDataExchangeInstruction1()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction1Instruction key 1 is used in Germany for foreign data medium exchange (field T16).
|
String |
getDataExchangeInstruction2()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction2Instruction key 2 is used in Germany in foreign data medium exchange (field T17).
|
String |
getDataExchangeInstruction3()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction3Instruction key 3 is used in Germany for foreign data medium exchange (field T18).
|
String |
getDataExchangeInstruction4()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction4Instruction key 4 is used in Germany for foreign data medium exchange (field T19).
|
String |
getDebitCreditCode()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DebitCreditCode
|
String |
getDelivOfGoodsDestCountry()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: DelivOfGoodsDestCountryIn the field, the country key of the customer is defaulted.
|
LocalDateTime |
getDocumentDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: DocumentDate
|
String |
getDocumentItemText()
Constraints: Not nullable, Maximum length: 50 Original property name from the Odata EDM: DocumentItemTextLine item texts can be used internally and externally.
|
String |
getDocumentReferenceID()
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: DocumentReferenceID
|
LocalDateTime |
getDueCalculationBaseDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: DueCalculationBaseDate
|
String |
getDunningArea()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DunningAreaIf different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.
|
String |
getDunningBlockingReason()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DunningBlockingReason
|
String |
getDunningKey()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DunningKeyYou define the contents of the text line in Customizing for the dunning key.
|
String |
getDunningLevel()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DunningLevelThe business partner has received the dunning level from the last dunning run.
|
protected String |
getEndpointUrl() |
protected String |
getEntityCollection() |
ErpConfigContext |
getErpConfigContext()
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
BigDecimal |
getExchangeRate()
Constraints: Not nullable, Precision: 9, Scale: 5 Original property name from the Odata EDM: ExchangeRateYour system is configured in such a way that it expects:
No prefix (leading sign) for direct rates
A "" as prefix (leading sign) for direct rates
No prefix for indirect rates
A "" as prefix for indirect rates
|
LocalDateTime |
getExchangeRateDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ExchangeRateDate
|
String |
getExchangeRateType()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ExchangeRateTypeYou enter the exchange rate type to store different exchange rates.
|
String |
getFinancialAccountType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: FinancialAccountType
|
String |
getFinancialManagementArea()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: FinancialManagementAreaAn FM area is an organizational unit which plans, controls and monitors funds and commitment budgets.
|
String |
getFinancialTransactionType()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: FinancialTransactionType
|
String |
getFiscalPeriod()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: FiscalPeriodEvery business transaction is allocated to a fiscal period.
|
String |
getFiscalYear()
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: FiscalYear
|
String |
getFixedAsset()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: FixedAsset
|
String |
getFixedCashDiscount()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: FixedCashDiscount
|
String |
getFollowOnDocumentType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: FollowOnDocumentType
|
String |
getFunctionalArea()
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: FunctionalAreaThe functional area is required in Funds Management in order to fulfill legal reporting requirements subdividing an organization into functions.
|
String |
getFunctionalAreaName()
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: FunctionalAreaName
|
String |
getFund()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: FundIf you assign the budget to a fund, you can obtain a detailed list of origin for the amounts involved.
|
String |
getFundedProgram()
Constraints: Not nullable, Maximum length: 24 Original property name from the Odata EDM: FundedProgramYou create funded programs in the component Funds Management Public Sector.
|
String |
getFundsCenter()
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: FundsCenter
|
String |
getGLAccount()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: GLAccount
|
String |
getGLAccountLongName()
Constraints: Not nullable, Maximum length: 50 Original property name from the Odata EDM: GLAccountLongName
|
String |
getGLAccountName()
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: GLAccountName
|
String |
getGoodsMovementEntryUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: GoodsMovementEntryUnitEnter a unit of measure here only if it differs from the default unit of measure.
|
String |
getGrantID()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: GrantIDA grant may be for any purpose and cover all or only part of the costs of the project in question.
|
Boolean |
getHasPaymentOrder()
Constraints: noneOriginal property name from the Odata EDM: HasPaymentOrderThe lock can be removed by the related program.
|
BigDecimal |
getHedgedAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: HedgedAmount
|
String |
getHouseBank()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: HouseBank
|
String |
getHouseBankAccount()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: HouseBankAccount
|
String |
getIntercompanyTransaction()
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: IntercompanyTransaction
|
String |
getInventoryValuationType()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: InventoryValuationTypeThe valuation types allowed for a material are determined by the valuation category.
|
BigDecimal |
getInvoiceAmountInFrgnCurrency()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: InvoiceAmountInFrgnCurrency
|
BigDecimal |
getInvoiceAmtInCoCodeCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: InvoiceAmtInCoCodeCrcy
|
String |
getInvoiceItemReference()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: InvoiceItemReference
|
String |
getInvoiceList()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: InvoiceList
|
LocalDateTime |
getInvoiceReceiptDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: InvoiceReceiptDate
|
String |
getInvoiceReference()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: InvoiceReference
|
String |
getInvoiceReferenceFiscalYear()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: InvoiceReferenceFiscalYear
|
Boolean |
getIsAutomaticallyCreated()
Constraints: noneOriginal property name from the Odata EDM: IsAutomaticallyCreated
|
Boolean |
getIsBalanceSheetAccount()
Constraints: noneOriginal property name from the Odata EDM: IsBalanceSheetAccount
|
Boolean |
getIsCleared()
Constraints: noneOriginal property name from the Odata EDM: IsCleared
|
Boolean |
getIsCompletelyDelivered()
Constraints: noneOriginal property name from the Odata EDM: IsCompletelyDelivered
|
Boolean |
getIsEUTriangularDeal()
Constraints: noneOriginal property name from the Odata EDM: IsEUTriangularDeal
|
Boolean |
getIsNegativePosting()
Constraints: noneOriginal property name from the Odata EDM: IsNegativePostingIf you set this indicator, you change the way the transaction figures for this account are updated, namely that when you make a debit posting, the credit side of the account is reduced, when you make a credit posting, the debit side of the account is reduced.
|
Boolean |
getIsNotCashDiscountLiable()
Constraints: noneOriginal property name from the Odata EDM: IsNotCashDiscountLiable
|
String |
getIsOpenItemManaged()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsOpenItemManaged
|
Boolean |
getIsReversal()
Constraints: noneOriginal property name from the Odata EDM: IsReversal
|
Boolean |
getIsReversed()
Constraints: noneOriginal property name from the Odata EDM: IsReversed
|
Boolean |
getIsSalesRelated()
Constraints: noneOriginal property name from the Odata EDM: IsSalesRelated
|
Boolean |
getIsUsedInPaymentTransaction()
Constraints: noneOriginal property name from the Odata EDM: IsUsedInPaymentTransaction
|
String |
getJointVenture()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: JointVentureA joint venture is usually lead by an operating authority, who is responsible for the costs incurred.
|
String |
getJointVentureCostRecoveryCode()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: JointVentureCostRecoveryCodeYou can define recovery indicators at three different levels:
o Document type
You can assign a recovery indicator to each document type for the
credit side and for the debit side.
|
String |
getJointVentureEquityGroup()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: JointVentureEquityGroup
|
String |
getJointVentureEquityType()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: JointVentureEquityType
|
protected Map<String,Object> |
getKey() |
LocalDateTime |
getLastChangeDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: LastChangeDate
|
LocalDateTime |
getLastDunningDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: LastDunningDate
|
String |
getLatePaymentReason()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: LatePaymentReason
|
String |
getLedger()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: Ledger
|
String |
getLedgerGLLineItem()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: LedgerGLLineItem
|
String |
getLedgerGroup()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: LedgerGroupIf you do not specify a ledger group, the function (such as posting) is executed for all ledgers, that is, for the leading ledger and all ledgers assigned in the company code.
|
Boolean |
getLineItemDisplayIsEnabled()
Constraints: noneOriginal property name from the Odata EDM: LineItemDisplayIsEnabledFor each line item, an entry is saved in an index table.
|
String |
getLogicalSystem()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: LogicalSystemThe distribution of data between systems requires that each system in the network has a unique identification.
|
String |
getMasterFixedAsset()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: MasterFixedAsset
|
String |
getMaterial()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Material
|
String |
getMaterialPriceControl()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: MaterialPriceControlStandard price
Moving average price
If the material ledger is activated for the material, this indicator, together with the material's price determination indicator, determines at which of the following prices the material is valuated:
Standard price
Moving average price
Periodic unit price
|
BigDecimal |
getMaterialPriceUnitQty()
Constraints: Not nullable, Precision: 5, Scale: 0 Original property name from the Odata EDM: MaterialPriceUnitQtyIf 10 gallons of gasoline cost $12.00, the price unit is 10.
|
LocalDateTime |
getNetDueDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: NetDueDate
|
BigDecimal |
getNetPaymentAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: NetPaymentAmount
|
BigDecimal |
getNetPaymentDays()
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: NetPaymentDays
|
BigDecimal |
getNumberOfItems()
Constraints: Not nullable, Precision: 12, Scale: 0 Original property name from the Odata EDM: NumberOfItems
|
String |
getOffsettingAccount()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: OffsettingAccount
|
String |
getOffsettingAccountType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: OffsettingAccountType
|
String |
getOperationalGLAccount()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: OperationalGLAccount
|
String |
getOrderID()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: OrderID
|
String |
getOrderIntBillOfOperationsItem()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: OrderIntBillOfOperationsItem
|
String |
getOrderInternalBillOfOperations()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: OrderInternalBillOfOperations
|
String |
getOriginalReferenceDocument()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: OriginalReferenceDocument
|
BigDecimal |
getOriginalTaxBaseAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: OriginalTaxBaseAmountThe amount deviates from the actual amount of the line item by automatically determined revised amounts.
|
String |
getPartnerBudgetPeriod()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerBudgetPeriodDuring the budget period, the organization may commit, obligate, and encumber funds (terminology varies).
|
String |
getPartnerBusinessArea()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PartnerBusinessAreaThis relationship enables internal business volume to be eliminated at the business area level (as part of business area consolidation).
|
String |
getPartnerCompany()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: PartnerCompany
|
String |
getPartnerFunctionalArea()
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: PartnerFunctionalAreaUse for Cost-of-Sales Accounting
The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting.
|
String |
getPartnerFund()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerFundIf you assign budget to a fund, you can execute a detailed proof of origin for your funds.
|
String |
getPartnerGrant()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: PartnerGrant
|
String |
getPartnerProfitCenter()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerProfitCenterIn the case of the receiver of a service/delivery, the sending profit center is entered as the partner profit center and vice versa.
|
String |
getPartnerSegment()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerSegment
|
String |
getPaymentBlockingReason()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: PaymentBlockingReason
|
String |
getPaymentCardItem()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PaymentCardItem
|
String |
getPaymentCardPaymentSettlement()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PaymentCardPaymentSettlement
|
String |
getPaymentCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: PaymentCurrency
|
String |
getPaymentDifferenceReason()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PaymentDifferenceReason
|
String |
getPaymentMethod()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: PaymentMethodIf you enter a payment method, then only this payment method can be used in automatic payment transactions.
|
String |
getPaymentMethodSupplement()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PaymentMethodSupplementItems with different payment method supplements are settled individually.
|
String |
getPaymentReference()
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: PaymentReferenceFor vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference.
|
String |
getPaymentTerms()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PaymentTermsIt is used in sales orders, purchase orders, and invoices.
|
String |
getPersonnelNumber()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: PersonnelNumber
|
BigDecimal |
getPlannedAmtInTransactionCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: PlannedAmtInTransactionCrcy
|
LocalDateTime |
getPlannedReversalDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: PlannedReversalDate
|
String |
getPlanningLevel()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PlanningLevelThe following levels could be possible:
Only noted items in the cash position
Only noted items in the liquidity forecast
Purchase orders
Sales orders
Notified incoming payments
FI payment settlements (incoming checks, outgoing checks, bills of exchange, payments)
FI bank transactions (bank statement postings, cashed checks, bill of exchange payments)
You can freely choose the planning levels.
|
String |
getPlant()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: Plant
|
LocalDateTime |
getPostingDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: PostingDate
|
String |
getPostingKey()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PostingKey
|
String |
getProduct()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Product
|
String |
getProfitabilitySegment()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProfitabilitySegmentExamples:
Customer '123'/Product '4710' Profitability segment no. 1
Customer '123'/Product '4712' Profitability segment no. 2
Country 'USA'/Region 'NORTH' Profitability segment no. 3
|
String |
getProfitCenter()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProfitCenter
|
String |
getProfitCenterName()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: ProfitCenterName
|
String |
getProfitLossAccountType()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: ProfitLossAccountType
|
String |
getProject()
Constraints: Not nullable, Maximum length: 24 Original property name from the Odata EDM: Project
|
String |
getProjectNetwork()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: ProjectNetworkNumbers are used to differentiate these project structures.
|
BigDecimal |
getPurchaseOrderQty()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: PurchaseOrderQty
|
String |
getPurchasingDocument()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PurchasingDocument
|
String |
getPurchasingDocumentItem()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: PurchasingDocumentItem
|
String |
getPurchasingDocumentPriceUnit()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PurchasingDocumentPriceUnit100 pc are ordered at a price of 10 $/kg.
|
BigDecimal |
getQuantity()
Constraints: Not nullable, Precision: 23, Scale: 3 Original property name from the Odata EDM: Quantity
|
BigDecimal |
getQuantityInEntryUnit()
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: QuantityInEntryUnit
|
String |
getRealEstateObject()
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: RealEstateObject
|
String |
getRecurringAccountingDocument()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: RecurringAccountingDocument
|
String |
getReference1IDByBusinessPartner()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: Reference1IDByBusinessPartnerAs additional information, for correspondence with the customer/vendor, as a search criterion for items in the customer/vendor account.
|
String |
getReference1InDocumentHeader()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: Reference1InDocumentHeader
|
String |
getReference2IDByBusinessPartner()
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: Reference2IDByBusinessPartnerAs additional information, for correspondence with the customer/vendor, as a search criterion for items in the customer/vendor account.
|
String |
getReference2InDocumentHeader()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: Reference2InDocumentHeader
|
String |
getReference3IDByBusinessPartner()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: Reference3IDByBusinessPartner
|
String |
getReferenceDocumentLogicalSystem()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
|
String |
getReferenceDocumentType()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: ReferenceDocumentType
|
String |
getRegion()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RegionThe automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.
|
Boolean |
getReversalIsPlanned()
Constraints: noneOriginal property name from the Odata EDM: ReversalIsPlanned
|
String |
getReversalReason()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: ReversalReason
|
String |
getReverseDocument()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ReverseDocument
|
String |
getReverseDocumentFiscalYear()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ReverseDocumentFiscalYear
|
String |
getSalesDocument()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesDocument
|
String |
getSalesDocumentCondition()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesDocumentConditionThe purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area.
|
String |
getSalesDocumentItem()
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SalesDocumentItem
|
String |
getScheduleLine()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ScheduleLineWhen an item has more than one schedule line, the system automatically assigns a unique number to each line.
|
String |
getSegment()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Segment
|
String |
getSegmentName()
Constraints: Not nullable, Maximum length: 50 Original property name from the Odata EDM: SegmentName
|
String |
getSEPAMandate()
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: SEPAMandateThe mandate reference can be specified externally or be determined by internal number assignment.
|
LocalDateTime |
getSettlementReferenceDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SettlementReferenceDate
|
String |
getSourceCompanyCode()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SourceCompanyCode
|
String |
getSpecialGLAccountAssignment()
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: SpecialGLAccountAssignment
|
String |
getSpecialGLCode()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SpecialGLCode
|
String |
getSpecialGLTransactionType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SpecialGLTransactionTypeBy using this type, you can select entry screens or use certain calculation procedures, for example.
|
String |
getStateCentralBankPaymentReason()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: StateCentralBankPaymentReasonIn foreign payment transactions, information concerning the reason for payment is needed for the report according to German foreign trade regulations (AWV).
|
String |
getSupplier()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Supplier
|
String |
getSupplierName()
Constraints: Not nullable, Maximum length: 80 Original property name from the Odata EDM: SupplierName
|
String |
getSupplyingCountry()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: SupplyingCountry
|
BigDecimal |
getTaxAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxAmountThe amount serves, together with other values such as the tax code and the tax base amount, as a basis for the automatically created postings for taxes on sales/purchases and therefore also as a base for the advance return for tax on sales/purchases.
|
BigDecimal |
getTaxAmountInCoCodeCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxAmountInCoCodeCrcy
|
BigDecimal |
getTaxBaseAmountInCoCodeCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxBaseAmountInCoCodeCrcyWith the direct entry of tax line items, you must always specify the base amount so that the system can check the tax amount.
|
BigDecimal |
getTaxBaseAmountInTransCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxBaseAmountInTransCrcyWhen directly entering tax items, you always have to specify the base amount so that the system can check that the tax amount is correct.
|
Boolean |
getTaxBaseAmountIsNetAmount()
Constraints: noneOriginal property name from the Odata EDM: TaxBaseAmountIsNetAmountThe rule used to determine the base amount for the calculation of sales tax is subject to the relevant country legislation.
|
String |
getTaxCode()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxCodeThe tax indicators are unique to each country.
|
LocalDateTime |
getTaxDeterminationDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: TaxDeterminationDateThe system determines the date for calculating time-dependent tax (depending on the Customizing settings in the company code) either from the posting date or from the document date.
|
String |
getTaxDistributionCode1()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxDistributionCode1
|
String |
getTaxDistributionCode2()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxDistributionCode2
|
String |
getTaxDistributionCode3()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxDistributionCode3
|
BigDecimal |
getTaxExchangeRate()
Constraints: Not nullable, Precision: 9, Scale: 5 Original property name from the Odata EDM: TaxExchangeRate
|
Boolean |
getTaxIsCalculatedAutomatically()
Constraints: noneOriginal property name from the Odata EDM: TaxIsCalculatedAutomatically
|
String |
getTaxJurisdiction()
Constraints: Not nullable, Maximum length: 15 Original property name from the Odata EDM: TaxJurisdiction
|
LocalDateTime |
getTaxReportingDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: TaxReportingDateThe tax reporting date can be identical to the posting date or the document date; you also can define your own rules to determine the date.
|
String |
getTaxSection()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: TaxSection
|
String |
getTaxType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: TaxType
|
String |
getTransactionCode()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: TransactionCode
|
String |
getTransactionCurrency()
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: TransactionCurrency
|
String |
getTransactionTypeDetermination()
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: TransactionTypeDetermination
|
String |
getTreasuryContractType()
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: TreasuryContractType
|
Class<OperationalAcctgDocItemCube> |
getType() |
String |
getValuationArea()
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ValuationAreaPlant
All plants belonging to a company code, in which case the valuation area is the company code
|
BigDecimal |
getValuationDiffAmtInAddlCrcy1()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: ValuationDiffAmtInAddlCrcy1
|
BigDecimal |
getValuationDiffAmtInAddlCrcy2()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: ValuationDiffAmtInAddlCrcy2
|
BigDecimal |
getValuationDiffAmtInCoCodeCrcy()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: ValuationDiffAmtInCoCodeCrcy
|
LocalDateTime |
getValueDate()
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValueDateThe value date is used in bank accounts and bank sub-accounts.
|
String |
getVATRegistration()
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: VATRegistration
|
String |
getWBSElementInternalID()
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: WBSElementInternalID
|
BigDecimal |
getWithholdingTaxAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: WithholdingTaxAmount
|
BigDecimal |
getWithholdingTaxBaseAmount()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: WithholdingTaxBaseAmount
|
String |
getWithholdingTaxCertificate()
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: WithholdingTaxCertificate
|
String |
getWithholdingTaxCode()
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: WithholdingTaxCode
|
BigDecimal |
getWithholdingTaxExemptionAmt()
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: WithholdingTaxExemptionAmt
|
int |
hashCode() |
void |
setAccountAssignmentNumber(String accountAssignmentNumber)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AccountAssignmentNumber
|
void |
setAccountingDocCreatedByUser(String accountingDocCreatedByUser)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: AccountingDocCreatedByUser
|
void |
setAccountingDocument(String accountingDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: AccountingDocumentThe document number is unique per company code and fiscal year.
|
void |
setAccountingDocumentCategory(String accountingDocumentCategory)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: AccountingDocumentCategory
|
void |
setAccountingDocumentCategoryName(String accountingDocumentCategoryName)
Constraints: Not nullable, Maximum length: 60 Original property name from the Odata EDM: AccountingDocumentCategoryName
|
void |
setAccountingDocumentClass(String accountingDocumentClass)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: AccountingDocumentClass
|
void |
setAccountingDocumentCreationDate(LocalDateTime accountingDocumentCreationDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: AccountingDocumentCreationDateNote
The posting date can differ from the entry date (date of entry in the system) and the document date.
|
void |
setAccountingDocumentHeaderText(String accountingDocumentHeaderText)
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: AccountingDocumentHeaderText
|
void |
setAccountingDocumentItem(String accountingDocumentItem)
(Key Field) Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: AccountingDocumentItem
|
void |
setAccountingDocumentItemRef(String accountingDocumentItemRef)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: AccountingDocumentItemRef
|
void |
setAccountingDocumentItemType(String accountingDocumentItemType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: AccountingDocumentItemTypeFor external purposes, the field content is unimportant and therefore, must not be used in customer reporting.
|
void |
setAccountingDocumentType(String accountingDocumentType)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AccountingDocumentTypeAttributes that control the entry of the document, or which are themselves noted in the document, are defined for each document type.
|
void |
setAccountingDocumentTypeName(String accountingDocumentTypeName)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: AccountingDocumentTypeName
|
void |
setAccountsReceivableIsPledged(String accountsReceivableIsPledged)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: AccountsReceivableIsPledged
|
void |
setAdditionalCurrency1(String additionalCurrency1)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: AdditionalCurrency1
|
void |
setAdditionalCurrency2(String additionalCurrency2)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: AdditionalCurrency2
|
void |
setAlternativeGLAccount(String alternativeGLAccount)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: AlternativeGLAccount
|
void |
setAlternativeReferenceDocument(String alternativeReferenceDocument)
Constraints: Not nullable, Maximum length: 26 Original property name from the Odata EDM: AlternativeReferenceDocument
|
void |
setAmountInAdditionalCurrency1(BigDecimal amountInAdditionalCurrency1)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInAdditionalCurrency1
|
void |
setAmountInAdditionalCurrency2(BigDecimal amountInAdditionalCurrency2)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInAdditionalCurrency2
|
void |
setAmountInBalanceTransacCrcy(BigDecimal amountInBalanceTransacCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInBalanceTransacCrcy
|
void |
setAmountInCompanyCodeCurrency(BigDecimal amountInCompanyCodeCurrency)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInCompanyCodeCurrency
|
void |
setAmountInPaymentCurrency(BigDecimal amountInPaymentCurrency)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInPaymentCurrency
|
void |
setAmountInTransactionCurrency(BigDecimal amountInTransactionCurrency)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: AmountInTransactionCurrency
|
void |
setAssetContract(String assetContract)
Constraints: Not nullable, Maximum length: 13 Original property name from the Odata EDM: AssetContract
|
void |
setAssetTransactionType(String assetTransactionType)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: AssetTransactionType
|
void |
setAssetValueDate(LocalDateTime assetValueDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: AssetValueDateSince the asset value date can have a direct influence on the amount of depreciation, the system creates a default value when it can.
|
void |
setAssignmentReference(String assignmentReference)
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: AssignmentReference
|
void |
setBalanceTransactionCurrency(String balanceTransactionCurrency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: BalanceTransactionCurrency
|
void |
setBaseUnit(String baseUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: BaseUnitYou define the base unit of measure and also alternative units of measure and their conversion factors in the material master record.
|
void |
setBatchInputSession(String batchInputSession)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BatchInputSession
|
void |
setBillingDocument(String billingDocument)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BillingDocument
|
void |
setBillOfExchangeUsage(String billOfExchangeUsage)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: BillOfExchangeUsage
|
void |
setBPBankAccountInternalID(String bPBankAccountInternalID)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BPBankAccountInternalID
|
void |
setBranch(String branch)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: Branch
|
void |
setBranchAccount(String branchAccount)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BranchAccount
|
void |
setBranchCode(String branchCode)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: BranchCodeThe system displays this code at the time of posting sales order, MM invoice, or FI invoice.
|
void |
setBudgetPeriod(String budgetPeriod)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: BudgetPeriodDuring the budget period, the organization may commit, obligate, and encumber funds (terminology varies).
|
void |
setBusinessArea(String businessArea)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessArea
|
void |
setBusinessAreaName(String businessAreaName)
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: BusinessAreaName
|
void |
setBusinessPlace(String businessPlace)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessPlace
|
void |
setBusinessProcess(String businessProcess)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: BusinessProcess
|
void |
setBusinessTransactionType(String businessTransactionType)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: BusinessTransactionTypeA business transaction is a business event that represents a change in a certain value or quantity for a company and, as a result, needs to be entered in accounting.
|
void |
setCashDiscount1Days(BigDecimal cashDiscount1Days)
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: CashDiscount1Days
|
void |
setCashDiscount1DueDate(LocalDateTime cashDiscount1DueDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CashDiscount1DueDate
|
void |
setCashDiscount1Percent(BigDecimal cashDiscount1Percent)
Constraints: Not nullable, Precision: 5, Scale: 3 Original property name from the Odata EDM: CashDiscount1Percent
|
void |
setCashDiscount2Days(BigDecimal cashDiscount2Days)
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: CashDiscount2Days
|
void |
setCashDiscount2DueDate(LocalDateTime cashDiscount2DueDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CashDiscount2DueDate
|
void |
setCashDiscount2Percent(BigDecimal cashDiscount2Percent)
Constraints: Not nullable, Precision: 5, Scale: 3 Original property name from the Odata EDM: CashDiscount2Percent
|
void |
setCashDiscountAmount(BigDecimal cashDiscountAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: CashDiscountAmount
|
void |
setCashDiscountAmtInCoCodeCrcy(BigDecimal cashDiscountAmtInCoCodeCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: CashDiscountAmtInCoCodeCrcy
|
void |
setCashDiscountBaseAmount(BigDecimal cashDiscountBaseAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: CashDiscountBaseAmount
|
void |
setCashFlowType(String cashFlowType)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CashFlowTypeYou can only use a flow type in connection with a financial transaction if you have assigned the flow typy to the corresponding product type in Customizing.
|
void |
setChartOfAccounts(String chartOfAccounts)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ChartOfAccounts
|
void |
setClearingAccountingDocument(String clearingAccountingDocument)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ClearingAccountingDocument
|
void |
setClearingCreationDate(LocalDateTime clearingCreationDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ClearingCreationDate
|
void |
setClearingDate(LocalDateTime clearingDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ClearingDate
|
void |
setClearingDocFiscalYear(String clearingDocFiscalYear)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ClearingDocFiscalYear
|
void |
setClearingIsReversed(Boolean clearingIsReversed)
Constraints: noneOriginal property name from the Odata EDM: ClearingIsReversed
|
void |
setClearingItem(BigDecimal clearingItem)
Constraints: Not nullable, Precision: 5, Scale: 0 Original property name from the Odata EDM: ClearingItem
|
void |
setCommitmentItem(String commitmentItem)
Constraints: Not nullable, Maximum length: 24 Original property name from the Odata EDM: CommitmentItem
|
void |
setCompanyCode(String companyCode)
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CompanyCode
|
void |
setCompanyCodeCurrency(String companyCodeCurrency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: CompanyCodeCurrency
|
void |
setCompanyCodeCurrencyDetnMethod(String companyCodeCurrencyDetnMethod)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: CompanyCodeCurrencyDetnMethod
|
void |
setCompanyCodeName(String companyCodeName)
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: CompanyCodeName
|
void |
setControllingArea(String controllingArea)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ControllingArea
|
void |
setControllingAreaName(String controllingAreaName)
Constraints: Not nullable, Maximum length: 25 Original property name from the Odata EDM: ControllingAreaName
|
void |
setCorporateGroupAccount(String corporateGroupAccount)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CorporateGroupAccount
|
void |
setCostCenter(String costCenter)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostCenter
|
void |
setCostCenterName(String costCenterName)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: CostCenterName
|
void |
setCostCtrActivityType(String costCtrActivityType)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: CostCtrActivityTypeActivity types describe the activity produced by a cost center and are measured in units of time or quantity.
|
void |
setCostElement(String costElement)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: CostElementItems in a chart of accounts that are relevant to cost, are referred to as cost elements.
|
void |
setCostObject(String costObject)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: CostObjectCost objects are the activity units of business whose costs are assigned based on the cost origins.
|
void |
setCostOriginGroup(String costOriginGroup)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CostOriginGroupWhen material costs are calculated, each material is given a general ledger account and thus is assigned to a primary cost element.
|
void |
setCreationTime(LocalTime creationTime)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: CreationTime
|
void |
setCreditControlArea(String creditControlArea)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: CreditControlAreaYou can also enter the credit control area separately for each posting, if this was marked in the appropriate company code.
|
void |
setCreditControlAreaCurrency(String creditControlAreaCurrency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: CreditControlAreaCurrency
|
void |
setCustomer(String customer)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Customer
|
void |
setCustomerIsInExecution(Boolean customerIsInExecution)
Constraints: noneOriginal property name from the Odata EDM: CustomerIsInExecution
|
void |
setCustomerName(String customerName)
Constraints: Not nullable, Maximum length: 80 Original property name from the Odata EDM: CustomerName
|
void |
setDataExchangeInstruction1(String dataExchangeInstruction1)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction1Instruction key 1 is used in Germany for foreign data medium exchange (field T16).
|
void |
setDataExchangeInstruction2(String dataExchangeInstruction2)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction2Instruction key 2 is used in Germany in foreign data medium exchange (field T17).
|
void |
setDataExchangeInstruction3(String dataExchangeInstruction3)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction3Instruction key 3 is used in Germany for foreign data medium exchange (field T18).
|
void |
setDataExchangeInstruction4(String dataExchangeInstruction4)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DataExchangeInstruction4Instruction key 4 is used in Germany for foreign data medium exchange (field T19).
|
void |
setDebitCreditCode(String debitCreditCode)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DebitCreditCode
|
void |
setDelivOfGoodsDestCountry(String delivOfGoodsDestCountry)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: DelivOfGoodsDestCountryIn the field, the country key of the customer is defaulted.
|
void |
setDocumentDate(LocalDateTime documentDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: DocumentDate
|
void |
setDocumentItemText(String documentItemText)
Constraints: Not nullable, Maximum length: 50 Original property name from the Odata EDM: DocumentItemTextLine item texts can be used internally and externally.
|
void |
setDocumentReferenceID(String documentReferenceID)
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: DocumentReferenceID
|
void |
setDueCalculationBaseDate(LocalDateTime dueCalculationBaseDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: DueCalculationBaseDate
|
void |
setDunningArea(String dunningArea)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: DunningAreaIf different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas.
|
void |
setDunningBlockingReason(String dunningBlockingReason)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DunningBlockingReason
|
void |
setDunningKey(String dunningKey)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DunningKeyYou define the contents of the text line in Customizing for the dunning key.
|
void |
setDunningLevel(String dunningLevel)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: DunningLevelThe business partner has received the dunning level from the last dunning run.
|
void |
setErpConfigContext(ErpConfigContext erpConfigContext)
Convienence field for reusing the same ERP system context with multiple queries (e.g. fetching associated entities).
|
void |
setExchangeRate(BigDecimal exchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5 Original property name from the Odata EDM: ExchangeRateYour system is configured in such a way that it expects:
No prefix (leading sign) for direct rates
A "" as prefix (leading sign) for direct rates
No prefix for indirect rates
A "" as prefix for indirect rates
|
void |
setExchangeRateDate(LocalDateTime exchangeRateDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ExchangeRateDate
|
void |
setExchangeRateType(String exchangeRateType)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ExchangeRateTypeYou enter the exchange rate type to store different exchange rates.
|
void |
setFinancialAccountType(String financialAccountType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: FinancialAccountType
|
void |
setFinancialManagementArea(String financialManagementArea)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: FinancialManagementAreaAn FM area is an organizational unit which plans, controls and monitors funds and commitment budgets.
|
void |
setFinancialTransactionType(String financialTransactionType)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: FinancialTransactionType
|
void |
setFiscalPeriod(String fiscalPeriod)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: FiscalPeriodEvery business transaction is allocated to a fiscal period.
|
void |
setFiscalYear(String fiscalYear)
(Key Field) Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: FiscalYear
|
void |
setFixedAsset(String fixedAsset)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: FixedAsset
|
void |
setFixedCashDiscount(String fixedCashDiscount)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: FixedCashDiscount
|
void |
setFollowOnDocumentType(String followOnDocumentType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: FollowOnDocumentType
|
void |
setFunctionalArea(String functionalArea)
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: FunctionalAreaThe functional area is required in Funds Management in order to fulfill legal reporting requirements subdividing an organization into functions.
|
void |
setFunctionalAreaName(String functionalAreaName)
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: FunctionalAreaName
|
void |
setFund(String fund)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: FundIf you assign the budget to a fund, you can obtain a detailed list of origin for the amounts involved.
|
void |
setFundedProgram(String fundedProgram)
Constraints: Not nullable, Maximum length: 24 Original property name from the Odata EDM: FundedProgramYou create funded programs in the component Funds Management Public Sector.
|
void |
setFundsCenter(String fundsCenter)
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: FundsCenter
|
void |
setGLAccount(String gLAccount)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: GLAccount
|
void |
setGLAccountLongName(String gLAccountLongName)
Constraints: Not nullable, Maximum length: 50 Original property name from the Odata EDM: GLAccountLongName
|
void |
setGLAccountName(String gLAccountName)
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: GLAccountName
|
void |
setGoodsMovementEntryUnit(String goodsMovementEntryUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: GoodsMovementEntryUnitEnter a unit of measure here only if it differs from the default unit of measure.
|
void |
setGrantID(String grantID)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: GrantIDA grant may be for any purpose and cover all or only part of the costs of the project in question.
|
void |
setHasPaymentOrder(Boolean hasPaymentOrder)
Constraints: noneOriginal property name from the Odata EDM: HasPaymentOrderThe lock can be removed by the related program.
|
void |
setHedgedAmount(BigDecimal hedgedAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: HedgedAmount
|
void |
setHouseBank(String houseBank)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: HouseBank
|
void |
setHouseBankAccount(String houseBankAccount)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: HouseBankAccount
|
void |
setIntercompanyTransaction(String intercompanyTransaction)
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: IntercompanyTransaction
|
void |
setInventoryValuationType(String inventoryValuationType)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: InventoryValuationTypeThe valuation types allowed for a material are determined by the valuation category.
|
void |
setInvoiceAmountInFrgnCurrency(BigDecimal invoiceAmountInFrgnCurrency)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: InvoiceAmountInFrgnCurrency
|
void |
setInvoiceAmtInCoCodeCrcy(BigDecimal invoiceAmtInCoCodeCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: InvoiceAmtInCoCodeCrcy
|
void |
setInvoiceItemReference(String invoiceItemReference)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: InvoiceItemReference
|
void |
setInvoiceList(String invoiceList)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: InvoiceList
|
void |
setInvoiceReceiptDate(LocalDateTime invoiceReceiptDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: InvoiceReceiptDate
|
void |
setInvoiceReference(String invoiceReference)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: InvoiceReference
|
void |
setInvoiceReferenceFiscalYear(String invoiceReferenceFiscalYear)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: InvoiceReferenceFiscalYear
|
void |
setIsAutomaticallyCreated(Boolean isAutomaticallyCreated)
Constraints: noneOriginal property name from the Odata EDM: IsAutomaticallyCreated
|
void |
setIsBalanceSheetAccount(Boolean isBalanceSheetAccount)
Constraints: noneOriginal property name from the Odata EDM: IsBalanceSheetAccount
|
void |
setIsCleared(Boolean isCleared)
Constraints: noneOriginal property name from the Odata EDM: IsCleared
|
void |
setIsCompletelyDelivered(Boolean isCompletelyDelivered)
Constraints: noneOriginal property name from the Odata EDM: IsCompletelyDelivered
|
void |
setIsEUTriangularDeal(Boolean isEUTriangularDeal)
Constraints: noneOriginal property name from the Odata EDM: IsEUTriangularDeal
|
void |
setIsNegativePosting(Boolean isNegativePosting)
Constraints: noneOriginal property name from the Odata EDM: IsNegativePostingIf you set this indicator, you change the way the transaction figures for this account are updated, namely that when you make a debit posting, the credit side of the account is reduced, when you make a credit posting, the debit side of the account is reduced.
|
void |
setIsNotCashDiscountLiable(Boolean isNotCashDiscountLiable)
Constraints: noneOriginal property name from the Odata EDM: IsNotCashDiscountLiable
|
void |
setIsOpenItemManaged(String isOpenItemManaged)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: IsOpenItemManaged
|
void |
setIsReversal(Boolean isReversal)
Constraints: noneOriginal property name from the Odata EDM: IsReversal
|
void |
setIsReversed(Boolean isReversed)
Constraints: noneOriginal property name from the Odata EDM: IsReversed
|
void |
setIsSalesRelated(Boolean isSalesRelated)
Constraints: noneOriginal property name from the Odata EDM: IsSalesRelated
|
void |
setIsUsedInPaymentTransaction(Boolean isUsedInPaymentTransaction)
Constraints: noneOriginal property name from the Odata EDM: IsUsedInPaymentTransaction
|
void |
setJointVenture(String jointVenture)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: JointVentureA joint venture is usually lead by an operating authority, who is responsible for the costs incurred.
|
void |
setJointVentureCostRecoveryCode(String jointVentureCostRecoveryCode)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: JointVentureCostRecoveryCodeYou can define recovery indicators at three different levels:
o Document type
You can assign a recovery indicator to each document type for the
credit side and for the debit side.
|
void |
setJointVentureEquityGroup(String jointVentureEquityGroup)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: JointVentureEquityGroup
|
void |
setJointVentureEquityType(String jointVentureEquityType)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: JointVentureEquityType
|
void |
setLastChangeDate(LocalDateTime lastChangeDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: LastChangeDate
|
void |
setLastDunningDate(LocalDateTime lastDunningDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: LastDunningDate
|
void |
setLatePaymentReason(String latePaymentReason)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: LatePaymentReason
|
void |
setLedger(String ledger)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: Ledger
|
void |
setLedgerGLLineItem(String ledgerGLLineItem)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: LedgerGLLineItem
|
void |
setLedgerGroup(String ledgerGroup)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: LedgerGroupIf you do not specify a ledger group, the function (such as posting) is executed for all ledgers, that is, for the leading ledger and all ledgers assigned in the company code.
|
void |
setLineItemDisplayIsEnabled(Boolean lineItemDisplayIsEnabled)
Constraints: noneOriginal property name from the Odata EDM: LineItemDisplayIsEnabledFor each line item, an entry is saved in an index table.
|
void |
setLogicalSystem(String logicalSystem)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: LogicalSystemThe distribution of data between systems requires that each system in the network has a unique identification.
|
void |
setMasterFixedAsset(String masterFixedAsset)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: MasterFixedAsset
|
void |
setMaterial(String material)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Material
|
void |
setMaterialPriceControl(String materialPriceControl)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: MaterialPriceControlStandard price
Moving average price
If the material ledger is activated for the material, this indicator, together with the material's price determination indicator, determines at which of the following prices the material is valuated:
Standard price
Moving average price
Periodic unit price
|
void |
setMaterialPriceUnitQty(BigDecimal materialPriceUnitQty)
Constraints: Not nullable, Precision: 5, Scale: 0 Original property name from the Odata EDM: MaterialPriceUnitQtyIf 10 gallons of gasoline cost $12.00, the price unit is 10.
|
void |
setNetDueDate(LocalDateTime netDueDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: NetDueDate
|
void |
setNetPaymentAmount(BigDecimal netPaymentAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: NetPaymentAmount
|
void |
setNetPaymentDays(BigDecimal netPaymentDays)
Constraints: Not nullable, Precision: 3, Scale: 0 Original property name from the Odata EDM: NetPaymentDays
|
void |
setNumberOfItems(BigDecimal numberOfItems)
Constraints: Not nullable, Precision: 12, Scale: 0 Original property name from the Odata EDM: NumberOfItems
|
void |
setOffsettingAccount(String offsettingAccount)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: OffsettingAccount
|
void |
setOffsettingAccountType(String offsettingAccountType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: OffsettingAccountType
|
void |
setOperationalGLAccount(String operationalGLAccount)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: OperationalGLAccount
|
void |
setOrderID(String orderID)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: OrderID
|
void |
setOrderIntBillOfOperationsItem(String orderIntBillOfOperationsItem)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: OrderIntBillOfOperationsItem
|
void |
setOrderInternalBillOfOperations(String orderInternalBillOfOperations)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: OrderInternalBillOfOperations
|
void |
setOriginalReferenceDocument(String originalReferenceDocument)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: OriginalReferenceDocument
|
void |
setOriginalTaxBaseAmount(BigDecimal originalTaxBaseAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: OriginalTaxBaseAmountThe amount deviates from the actual amount of the line item by automatically determined revised amounts.
|
void |
setPartnerBudgetPeriod(String partnerBudgetPeriod)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerBudgetPeriodDuring the budget period, the organization may commit, obligate, and encumber funds (terminology varies).
|
void |
setPartnerBusinessArea(String partnerBusinessArea)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PartnerBusinessAreaThis relationship enables internal business volume to be eliminated at the business area level (as part of business area consolidation).
|
void |
setPartnerCompany(String partnerCompany)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: PartnerCompany
|
void |
setPartnerFunctionalArea(String partnerFunctionalArea)
Constraints: Not nullable, Maximum length: 16 Original property name from the Odata EDM: PartnerFunctionalAreaUse for Cost-of-Sales Accounting
The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting.
|
void |
setPartnerFund(String partnerFund)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerFundIf you assign budget to a fund, you can execute a detailed proof of origin for your funds.
|
void |
setPartnerGrant(String partnerGrant)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: PartnerGrant
|
void |
setPartnerProfitCenter(String partnerProfitCenter)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerProfitCenterIn the case of the receiver of a service/delivery, the sending profit center is entered as the partner profit center and vice versa.
|
void |
setPartnerSegment(String partnerSegment)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PartnerSegment
|
void |
setPaymentBlockingReason(String paymentBlockingReason)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: PaymentBlockingReason
|
void |
setPaymentCardItem(String paymentCardItem)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PaymentCardItem
|
void |
setPaymentCardPaymentSettlement(String paymentCardPaymentSettlement)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PaymentCardPaymentSettlement
|
void |
setPaymentCurrency(String paymentCurrency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: PaymentCurrency
|
void |
setPaymentDifferenceReason(String paymentDifferenceReason)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PaymentDifferenceReason
|
void |
setPaymentMethod(String paymentMethod)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: PaymentMethodIf you enter a payment method, then only this payment method can be used in automatic payment transactions.
|
void |
setPaymentMethodSupplement(String paymentMethodSupplement)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PaymentMethodSupplementItems with different payment method supplements are settled individually.
|
void |
setPaymentReference(String paymentReference)
Constraints: Not nullable, Maximum length: 30 Original property name from the Odata EDM: PaymentReferenceFor vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference.
|
void |
setPaymentTerms(String paymentTerms)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: PaymentTermsIt is used in sales orders, purchase orders, and invoices.
|
void |
setPersonnelNumber(String personnelNumber)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: PersonnelNumber
|
void |
setPlannedAmtInTransactionCrcy(BigDecimal plannedAmtInTransactionCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: PlannedAmtInTransactionCrcy
|
void |
setPlannedReversalDate(LocalDateTime plannedReversalDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: PlannedReversalDate
|
void |
setPlanningLevel(String planningLevel)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PlanningLevelThe following levels could be possible:
Only noted items in the cash position
Only noted items in the liquidity forecast
Purchase orders
Sales orders
Notified incoming payments
FI payment settlements (incoming checks, outgoing checks, bills of exchange, payments)
FI bank transactions (bank statement postings, cashed checks, bill of exchange payments)
You can freely choose the planning levels.
|
void |
setPlant(String plant)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: Plant
|
void |
setPostingDate(LocalDateTime postingDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: PostingDate
|
void |
setPostingKey(String postingKey)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: PostingKey
|
void |
setProduct(String product)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: Product
|
void |
setProfitabilitySegment(String profitabilitySegment)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProfitabilitySegmentExamples:
Customer '123'/Product '4710' Profitability segment no. 1
Customer '123'/Product '4712' Profitability segment no. 2
Country 'USA'/Region 'NORTH' Profitability segment no. 3
|
void |
setProfitCenter(String profitCenter)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ProfitCenter
|
void |
setProfitCenterName(String profitCenterName)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: ProfitCenterName
|
void |
setProfitLossAccountType(String profitLossAccountType)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: ProfitLossAccountType
|
void |
setProject(String project)
Constraints: Not nullable, Maximum length: 24 Original property name from the Odata EDM: Project
|
void |
setProjectNetwork(String projectNetwork)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: ProjectNetworkNumbers are used to differentiate these project structures.
|
void |
setPurchaseOrderQty(BigDecimal purchaseOrderQty)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: PurchaseOrderQty
|
void |
setPurchasingDocument(String purchasingDocument)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: PurchasingDocument
|
void |
setPurchasingDocumentItem(String purchasingDocumentItem)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: PurchasingDocumentItem
|
void |
setPurchasingDocumentPriceUnit(String purchasingDocumentPriceUnit)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: PurchasingDocumentPriceUnit100 pc are ordered at a price of 10 $/kg.
|
void |
setQuantity(BigDecimal quantity)
Constraints: Not nullable, Precision: 23, Scale: 3 Original property name from the Odata EDM: Quantity
|
void |
setQuantityInEntryUnit(BigDecimal quantityInEntryUnit)
Constraints: Not nullable, Precision: 13, Scale: 3 Original property name from the Odata EDM: QuantityInEntryUnit
|
void |
setRealEstateObject(String realEstateObject)
Constraints: Not nullable, Maximum length: 40 Original property name from the Odata EDM: RealEstateObject
|
void |
setRecurringAccountingDocument(String recurringAccountingDocument)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: RecurringAccountingDocument
|
void |
setReference1IDByBusinessPartner(String reference1IDByBusinessPartner)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: Reference1IDByBusinessPartnerAs additional information, for correspondence with the customer/vendor, as a search criterion for items in the customer/vendor account.
|
void |
setReference1InDocumentHeader(String reference1InDocumentHeader)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: Reference1InDocumentHeader
|
void |
setReference2IDByBusinessPartner(String reference2IDByBusinessPartner)
Constraints: Not nullable, Maximum length: 12 Original property name from the Odata EDM: Reference2IDByBusinessPartnerAs additional information, for correspondence with the customer/vendor, as a search criterion for items in the customer/vendor account.
|
void |
setReference2InDocumentHeader(String reference2InDocumentHeader)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: Reference2InDocumentHeader
|
void |
setReference3IDByBusinessPartner(String reference3IDByBusinessPartner)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: Reference3IDByBusinessPartner
|
void |
setReferenceDocumentLogicalSystem(String referenceDocumentLogicalSystem)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
|
void |
setReferenceDocumentType(String referenceDocumentType)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: ReferenceDocumentType
|
void |
setRegion(String region)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: RegionThe automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain.
|
void |
setReversalIsPlanned(Boolean reversalIsPlanned)
Constraints: noneOriginal property name from the Odata EDM: ReversalIsPlanned
|
void |
setReversalReason(String reversalReason)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: ReversalReason
|
void |
setReverseDocument(String reverseDocument)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: ReverseDocument
|
void |
setReverseDocumentFiscalYear(String reverseDocumentFiscalYear)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ReverseDocumentFiscalYear
|
void |
setSalesDocument(String salesDocument)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesDocument
|
void |
setSalesDocumentCondition(String salesDocumentCondition)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: SalesDocumentConditionThe purchasing and sales departments may want to use the same order number for a document even though different conditions may apply in each area.
|
void |
setSalesDocumentItem(String salesDocumentItem)
Constraints: Not nullable, Maximum length: 6 Original property name from the Odata EDM: SalesDocumentItem
|
void |
setScheduleLine(String scheduleLine)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ScheduleLineWhen an item has more than one schedule line, the system automatically assigns a unique number to each line.
|
void |
setSegment(String segment)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Segment
|
void |
setSegmentName(String segmentName)
Constraints: Not nullable, Maximum length: 50 Original property name from the Odata EDM: SegmentName
|
void |
setSEPAMandate(String sEPAMandate)
Constraints: Not nullable, Maximum length: 35 Original property name from the Odata EDM: SEPAMandateThe mandate reference can be specified externally or be determined by internal number assignment.
|
void |
setSettlementReferenceDate(LocalDateTime settlementReferenceDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: SettlementReferenceDate
|
void |
setSourceCompanyCode(String sourceCompanyCode)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: SourceCompanyCode
|
void |
setSpecialGLAccountAssignment(String specialGLAccountAssignment)
Constraints: Not nullable, Maximum length: 18 Original property name from the Odata EDM: SpecialGLAccountAssignment
|
void |
setSpecialGLCode(String specialGLCode)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SpecialGLCode
|
void |
setSpecialGLTransactionType(String specialGLTransactionType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: SpecialGLTransactionTypeBy using this type, you can select entry screens or use certain calculation procedures, for example.
|
void |
setStateCentralBankPaymentReason(String stateCentralBankPaymentReason)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: StateCentralBankPaymentReasonIn foreign payment transactions, information concerning the reason for payment is needed for the report according to German foreign trade regulations (AWV).
|
void |
setSupplier(String supplier)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: Supplier
|
void |
setSupplierName(String supplierName)
Constraints: Not nullable, Maximum length: 80 Original property name from the Odata EDM: SupplierName
|
void |
setSupplyingCountry(String supplyingCountry)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: SupplyingCountry
|
void |
setTaxAmount(BigDecimal taxAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxAmountThe amount serves, together with other values such as the tax code and the tax base amount, as a basis for the automatically created postings for taxes on sales/purchases and therefore also as a base for the advance return for tax on sales/purchases.
|
void |
setTaxAmountInCoCodeCrcy(BigDecimal taxAmountInCoCodeCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxAmountInCoCodeCrcy
|
void |
setTaxBaseAmountInCoCodeCrcy(BigDecimal taxBaseAmountInCoCodeCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxBaseAmountInCoCodeCrcyWith the direct entry of tax line items, you must always specify the base amount so that the system can check the tax amount.
|
void |
setTaxBaseAmountInTransCrcy(BigDecimal taxBaseAmountInTransCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: TaxBaseAmountInTransCrcyWhen directly entering tax items, you always have to specify the base amount so that the system can check that the tax amount is correct.
|
void |
setTaxBaseAmountIsNetAmount(Boolean taxBaseAmountIsNetAmount)
Constraints: noneOriginal property name from the Odata EDM: TaxBaseAmountIsNetAmountThe rule used to determine the base amount for the calculation of sales tax is subject to the relevant country legislation.
|
void |
setTaxCode(String taxCode)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxCodeThe tax indicators are unique to each country.
|
void |
setTaxDeterminationDate(LocalDateTime taxDeterminationDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: TaxDeterminationDateThe system determines the date for calculating time-dependent tax (depending on the Customizing settings in the company code) either from the posting date or from the document date.
|
void |
setTaxDistributionCode1(String taxDistributionCode1)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxDistributionCode1
|
void |
setTaxDistributionCode2(String taxDistributionCode2)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxDistributionCode2
|
void |
setTaxDistributionCode3(String taxDistributionCode3)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: TaxDistributionCode3
|
void |
setTaxExchangeRate(BigDecimal taxExchangeRate)
Constraints: Not nullable, Precision: 9, Scale: 5 Original property name from the Odata EDM: TaxExchangeRate
|
void |
setTaxIsCalculatedAutomatically(Boolean taxIsCalculatedAutomatically)
Constraints: noneOriginal property name from the Odata EDM: TaxIsCalculatedAutomatically
|
void |
setTaxJurisdiction(String taxJurisdiction)
Constraints: Not nullable, Maximum length: 15 Original property name from the Odata EDM: TaxJurisdiction
|
void |
setTaxReportingDate(LocalDateTime taxReportingDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: TaxReportingDateThe tax reporting date can be identical to the posting date or the document date; you also can define your own rules to determine the date.
|
void |
setTaxSection(String taxSection)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: TaxSection
|
void |
setTaxType(String taxType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: TaxType
|
void |
setTransactionCode(String transactionCode)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: TransactionCode
|
void |
setTransactionCurrency(String transactionCurrency)
Constraints: Not nullable, Maximum length: 5 Original property name from the Odata EDM: TransactionCurrency
|
void |
setTransactionTypeDetermination(String transactionTypeDetermination)
Constraints: Not nullable, Maximum length: 3 Original property name from the Odata EDM: TransactionTypeDetermination
|
void |
setTreasuryContractType(String treasuryContractType)
Constraints: Not nullable, Maximum length: 1 Original property name from the Odata EDM: TreasuryContractType
|
void |
setValuationArea(String valuationArea)
Constraints: Not nullable, Maximum length: 4 Original property name from the Odata EDM: ValuationAreaPlant
All plants belonging to a company code, in which case the valuation area is the company code
|
void |
setValuationDiffAmtInAddlCrcy1(BigDecimal valuationDiffAmtInAddlCrcy1)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: ValuationDiffAmtInAddlCrcy1
|
void |
setValuationDiffAmtInAddlCrcy2(BigDecimal valuationDiffAmtInAddlCrcy2)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: ValuationDiffAmtInAddlCrcy2
|
void |
setValuationDiffAmtInCoCodeCrcy(BigDecimal valuationDiffAmtInCoCodeCrcy)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: ValuationDiffAmtInCoCodeCrcy
|
void |
setValueDate(LocalDateTime valueDate)
Constraints: Not nullable, Precision: 0 Original property name from the Odata EDM: ValueDateThe value date is used in bank accounts and bank sub-accounts.
|
void |
setVATRegistration(String vATRegistration)
Constraints: Not nullable, Maximum length: 20 Original property name from the Odata EDM: VATRegistration
|
void |
setWBSElementInternalID(String wBSElementInternalID)
Constraints: Not nullable, Maximum length: 8 Original property name from the Odata EDM: WBSElementInternalID
|
void |
setWithholdingTaxAmount(BigDecimal withholdingTaxAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: WithholdingTaxAmount
|
void |
setWithholdingTaxBaseAmount(BigDecimal withholdingTaxBaseAmount)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: WithholdingTaxBaseAmount
|
void |
setWithholdingTaxCertificate(String withholdingTaxCertificate)
Constraints: Not nullable, Maximum length: 10 Original property name from the Odata EDM: WithholdingTaxCertificate
|
void |
setWithholdingTaxCode(String withholdingTaxCode)
Constraints: Not nullable, Maximum length: 2 Original property name from the Odata EDM: WithholdingTaxCode
|
void |
setWithholdingTaxExemptionAmt(BigDecimal withholdingTaxExemptionAmt)
Constraints: Not nullable, Precision: 24, Scale: 3 Original property name from the Odata EDM: WithholdingTaxExemptionAmt
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getVersionIdentifier, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationProperties
public static final OperationalAcctgDocItemCubeSelectable ALL_FIELDS
public static final OperationalAcctgDocItemCubeField<String> COMPANY_CODE
public static final OperationalAcctgDocItemCubeField<String> FISCAL_YEAR
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_ITEM
public static final OperationalAcctgDocItemCubeField<String> COMPANY_CODE_NAME
public static final OperationalAcctgDocItemCubeField<String> CHART_OF_ACCOUNTS
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_ITEM_TYPE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> CLEARING_DATE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> CLEARING_CREATION_DATE
public static final OperationalAcctgDocItemCubeField<String> CLEARING_ACCOUNTING_DOCUMENT
public static final OperationalAcctgDocItemCubeField<Boolean> IS_CLEARED
public static final OperationalAcctgDocItemCubeField<String> POSTING_KEY
public static final OperationalAcctgDocItemCubeField<String> FINANCIAL_ACCOUNT_TYPE
public static final OperationalAcctgDocItemCubeField<String> SPECIAL_GL_CODE
public static final OperationalAcctgDocItemCubeField<String> SPECIAL_GL_TRANSACTION_TYPE
public static final OperationalAcctgDocItemCubeField<String> DEBIT_CREDIT_CODE
public static final OperationalAcctgDocItemCubeField<String> BUSINESS_AREA
public static final OperationalAcctgDocItemCubeField<String> BUSINESS_AREA_NAME
public static final OperationalAcctgDocItemCubeField<String> PARTNER_BUSINESS_AREA
public static final OperationalAcctgDocItemCubeField<String> TAX_CODE
public static final OperationalAcctgDocItemCubeField<String> WITHHOLDING_TAX_CODE
public static final OperationalAcctgDocItemCubeField<String> TAX_TYPE
public static final OperationalAcctgDocItemCubeField<String> TRANSACTION_TYPE_DETERMINATION
public static final OperationalAcctgDocItemCubeField<LocalDateTime> VALUE_DATE
public static final OperationalAcctgDocItemCubeField<String> ASSIGNMENT_REFERENCE
public static final OperationalAcctgDocItemCubeField<String> DOCUMENT_ITEM_TEXT
public static final OperationalAcctgDocItemCubeField<String> PARTNER_COMPANY
public static final OperationalAcctgDocItemCubeField<String> FINANCIAL_TRANSACTION_TYPE
public static final OperationalAcctgDocItemCubeField<String> CORPORATE_GROUP_ACCOUNT
public static final OperationalAcctgDocItemCubeField<String> PLANNING_LEVEL
public static final OperationalAcctgDocItemCubeField<String> CONTROLLING_AREA
public static final OperationalAcctgDocItemCubeField<String> CONTROLLING_AREA_NAME
public static final OperationalAcctgDocItemCubeField<String> COST_CENTER
public static final OperationalAcctgDocItemCubeField<String> COST_CENTER_NAME
public static final OperationalAcctgDocItemCubeField<String> PROJECT
public static final OperationalAcctgDocItemCubeField<String> ORDER_ID
public static final OperationalAcctgDocItemCubeField<String> BILLING_DOCUMENT
public static final OperationalAcctgDocItemCubeField<String> SALES_DOCUMENT
public static final OperationalAcctgDocItemCubeField<String> SALES_DOCUMENT_ITEM
public static final OperationalAcctgDocItemCubeField<String> SCHEDULE_LINE
public static final OperationalAcctgDocItemCubeField<String> MASTER_FIXED_ASSET
public static final OperationalAcctgDocItemCubeField<String> FIXED_ASSET
public static final OperationalAcctgDocItemCubeField<String> ASSET_TRANSACTION_TYPE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> ASSET_VALUE_DATE
public static final OperationalAcctgDocItemCubeField<String> PERSONNEL_NUMBER
public static final OperationalAcctgDocItemCubeField<Boolean> IS_SALES_RELATED
public static final OperationalAcctgDocItemCubeField<Boolean> LINE_ITEM_DISPLAY_IS_ENABLED
public static final OperationalAcctgDocItemCubeField<String> IS_OPEN_ITEM_MANAGED
public static final OperationalAcctgDocItemCubeField<Boolean> IS_NOT_CASH_DISCOUNT_LIABLE
public static final OperationalAcctgDocItemCubeField<Boolean> IS_AUTOMATICALLY_CREATED
public static final OperationalAcctgDocItemCubeField<Boolean> IS_USED_IN_PAYMENT_TRANSACTION
public static final OperationalAcctgDocItemCubeField<String> OPERATIONAL_GL_ACCOUNT
public static final OperationalAcctgDocItemCubeField<String> GL_ACCOUNT
public static final OperationalAcctgDocItemCubeField<String> GL_ACCOUNT_NAME
public static final OperationalAcctgDocItemCubeField<String> GL_ACCOUNT_LONG_NAME
public static final OperationalAcctgDocItemCubeField<String> CUSTOMER
public static final OperationalAcctgDocItemCubeField<String> CUSTOMER_NAME
public static final OperationalAcctgDocItemCubeField<String> SUPPLIER
public static final OperationalAcctgDocItemCubeField<String> SUPPLIER_NAME
public static final OperationalAcctgDocItemCubeField<String> BRANCH_ACCOUNT
public static final OperationalAcctgDocItemCubeField<Boolean> IS_BALANCE_SHEET_ACCOUNT
public static final OperationalAcctgDocItemCubeField<String> PROFIT_LOSS_ACCOUNT_TYPE
public static final OperationalAcctgDocItemCubeField<String> SPECIAL_GL_ACCOUNT_ASSIGNMENT
public static final OperationalAcctgDocItemCubeField<LocalDateTime> DUE_CALCULATION_BASE_DATE
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_TERMS
public static final OperationalAcctgDocItemCubeField<BigDecimal> CASH_DISCOUNT1_DAYS
public static final OperationalAcctgDocItemCubeField<BigDecimal> CASH_DISCOUNT2_DAYS
public static final OperationalAcctgDocItemCubeField<BigDecimal> NET_PAYMENT_DAYS
public static final OperationalAcctgDocItemCubeField<BigDecimal> CASH_DISCOUNT1_PERCENT
public static final OperationalAcctgDocItemCubeField<BigDecimal> CASH_DISCOUNT2_PERCENT
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_METHOD
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_BLOCKING_REASON
public static final OperationalAcctgDocItemCubeField<String> FIXED_CASH_DISCOUNT
public static final OperationalAcctgDocItemCubeField<String> HOUSE_BANK
public static final OperationalAcctgDocItemCubeField<String> BP_BANK_ACCOUNT_INTERNAL_ID
public static final OperationalAcctgDocItemCubeField<String> TAX_DISTRIBUTION_CODE1
public static final OperationalAcctgDocItemCubeField<String> TAX_DISTRIBUTION_CODE2
public static final OperationalAcctgDocItemCubeField<String> TAX_DISTRIBUTION_CODE3
public static final OperationalAcctgDocItemCubeField<String> INVOICE_REFERENCE
public static final OperationalAcctgDocItemCubeField<String> INVOICE_REFERENCE_FISCAL_YEAR
public static final OperationalAcctgDocItemCubeField<String> INVOICE_ITEM_REFERENCE
public static final OperationalAcctgDocItemCubeField<String> FOLLOW_ON_DOCUMENT_TYPE
public static final OperationalAcctgDocItemCubeField<String> STATE_CENTRAL_BANK_PAYMENT_REASON
public static final OperationalAcctgDocItemCubeField<String> SUPPLYING_COUNTRY
public static final OperationalAcctgDocItemCubeField<String> INVOICE_LIST
public static final OperationalAcctgDocItemCubeField<String> BILL_OF_EXCHANGE_USAGE
public static final OperationalAcctgDocItemCubeField<String> DUNNING_KEY
public static final OperationalAcctgDocItemCubeField<String> DUNNING_BLOCKING_REASON
public static final OperationalAcctgDocItemCubeField<LocalDateTime> LAST_DUNNING_DATE
public static final OperationalAcctgDocItemCubeField<String> DUNNING_LEVEL
public static final OperationalAcctgDocItemCubeField<String> DUNNING_AREA
public static final OperationalAcctgDocItemCubeField<String> WITHHOLDING_TAX_CERTIFICATE
public static final OperationalAcctgDocItemCubeField<String> MATERIAL
public static final OperationalAcctgDocItemCubeField<String> PRODUCT
public static final OperationalAcctgDocItemCubeField<String> PLANT
public static final OperationalAcctgDocItemCubeField<String> PURCHASING_DOCUMENT
public static final OperationalAcctgDocItemCubeField<String> PURCHASING_DOCUMENT_ITEM
public static final OperationalAcctgDocItemCubeField<String> ACCOUNT_ASSIGNMENT_NUMBER
public static final OperationalAcctgDocItemCubeField<Boolean> IS_COMPLETELY_DELIVERED
public static final OperationalAcctgDocItemCubeField<String> MATERIAL_PRICE_CONTROL
public static final OperationalAcctgDocItemCubeField<String> VALUATION_AREA
public static final OperationalAcctgDocItemCubeField<String> INVENTORY_VALUATION_TYPE
public static final OperationalAcctgDocItemCubeField<String> VAT_REGISTRATION
public static final OperationalAcctgDocItemCubeField<String> DELIV_OF_GOODS_DEST_COUNTRY
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_DIFFERENCE_REASON
public static final OperationalAcctgDocItemCubeField<String> PROFIT_CENTER
public static final OperationalAcctgDocItemCubeField<String> PROFIT_CENTER_NAME
public static final OperationalAcctgDocItemCubeField<String> JOINT_VENTURE
public static final OperationalAcctgDocItemCubeField<String> JOINT_VENTURE_COST_RECOVERY_CODE
public static final OperationalAcctgDocItemCubeField<String> JOINT_VENTURE_EQUITY_GROUP
public static final OperationalAcctgDocItemCubeField<String> TREASURY_CONTRACT_TYPE
public static final OperationalAcctgDocItemCubeField<String> ASSET_CONTRACT
public static final OperationalAcctgDocItemCubeField<String> CASH_FLOW_TYPE
public static final OperationalAcctgDocItemCubeField<String> TAX_JURISDICTION
public static final OperationalAcctgDocItemCubeField<String> REAL_ESTATE_OBJECT
public static final OperationalAcctgDocItemCubeField<LocalDateTime> SETTLEMENT_REFERENCE_DATE
public static final OperationalAcctgDocItemCubeField<String> COMMITMENT_ITEM
public static final OperationalAcctgDocItemCubeField<String> COST_OBJECT
public static final OperationalAcctgDocItemCubeField<String> PROJECT_NETWORK
public static final OperationalAcctgDocItemCubeField<String> ORDER_INTERNAL_BILL_OF_OPERATIONS
public static final OperationalAcctgDocItemCubeField<String> ORDER_INT_BILL_OF_OPERATIONS_ITEM
public static final OperationalAcctgDocItemCubeField<String> WBS_ELEMENT_INTERNAL_ID
public static final OperationalAcctgDocItemCubeField<String> PROFITABILITY_SEGMENT
public static final OperationalAcctgDocItemCubeField<String> JOINT_VENTURE_EQUITY_TYPE
public static final OperationalAcctgDocItemCubeField<Boolean> IS_EU_TRIANGULAR_DEAL
public static final OperationalAcctgDocItemCubeField<String> COST_ORIGIN_GROUP
public static final OperationalAcctgDocItemCubeField<String> COMPANY_CODE_CURRENCY_DETN_METHOD
public static final OperationalAcctgDocItemCubeField<Boolean> CLEARING_IS_REVERSED
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_METHOD_SUPPLEMENT
public static final OperationalAcctgDocItemCubeField<String> ALTERNATIVE_GL_ACCOUNT
public static final OperationalAcctgDocItemCubeField<String> FUNDS_CENTER
public static final OperationalAcctgDocItemCubeField<String> FUND
public static final OperationalAcctgDocItemCubeField<String> PARTNER_PROFIT_CENTER
public static final OperationalAcctgDocItemCubeField<String> REFERENCE1_I_D_BY_BUSINESS_PARTNER
public static final OperationalAcctgDocItemCubeField<String> REFERENCE2_I_D_BY_BUSINESS_PARTNER
public static final OperationalAcctgDocItemCubeField<Boolean> IS_NEGATIVE_POSTING
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_CARD_ITEM
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_CARD_PAYMENT_SETTLEMENT
public static final OperationalAcctgDocItemCubeField<String> CREDIT_CONTROL_AREA
public static final OperationalAcctgDocItemCubeField<String> REFERENCE3_I_D_BY_BUSINESS_PARTNER
public static final OperationalAcctgDocItemCubeField<String> DATA_EXCHANGE_INSTRUCTION1
public static final OperationalAcctgDocItemCubeField<String> DATA_EXCHANGE_INSTRUCTION2
public static final OperationalAcctgDocItemCubeField<String> DATA_EXCHANGE_INSTRUCTION3
public static final OperationalAcctgDocItemCubeField<String> DATA_EXCHANGE_INSTRUCTION4
public static final OperationalAcctgDocItemCubeField<String> REGION
public static final OperationalAcctgDocItemCubeField<Boolean> HAS_PAYMENT_ORDER
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_REFERENCE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> TAX_DETERMINATION_DATE
public static final OperationalAcctgDocItemCubeField<BigDecimal> CLEARING_ITEM
public static final OperationalAcctgDocItemCubeField<String> BUSINESS_PLACE
public static final OperationalAcctgDocItemCubeField<String> TAX_SECTION
public static final OperationalAcctgDocItemCubeField<String> COST_CTR_ACTIVITY_TYPE
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTS_RECEIVABLE_IS_PLEDGED
public static final OperationalAcctgDocItemCubeField<String> BUSINESS_PROCESS
public static final OperationalAcctgDocItemCubeField<String> GRANT_ID
public static final OperationalAcctgDocItemCubeField<String> FUNCTIONAL_AREA
public static final OperationalAcctgDocItemCubeField<String> FUNCTIONAL_AREA_NAME
public static final OperationalAcctgDocItemCubeField<Boolean> CUSTOMER_IS_IN_EXECUTION
public static final OperationalAcctgDocItemCubeField<String> FUNDED_PROGRAM
public static final OperationalAcctgDocItemCubeField<String> CLEARING_DOC_FISCAL_YEAR
public static final OperationalAcctgDocItemCubeField<String> LEDGER_GL_LINE_ITEM
public static final OperationalAcctgDocItemCubeField<String> SEGMENT
public static final OperationalAcctgDocItemCubeField<String> SEGMENT_NAME
public static final OperationalAcctgDocItemCubeField<String> PARTNER_SEGMENT
public static final OperationalAcctgDocItemCubeField<String> PARTNER_FUNCTIONAL_AREA
public static final OperationalAcctgDocItemCubeField<String> HOUSE_BANK_ACCOUNT
public static final OperationalAcctgDocItemCubeField<String> COST_ELEMENT
public static final OperationalAcctgDocItemCubeField<String> SEPA_MANDATE
public static final OperationalAcctgDocItemCubeField<String> REFERENCE_DOCUMENT_TYPE
public static final OperationalAcctgDocItemCubeField<String> ORIGINAL_REFERENCE_DOCUMENT
public static final OperationalAcctgDocItemCubeField<String> REFERENCE_DOCUMENT_LOGICAL_SYSTEM
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_ITEM_REF
public static final OperationalAcctgDocItemCubeField<String> FISCAL_PERIOD
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_CATEGORY
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_CATEGORY_NAME
public static final OperationalAcctgDocItemCubeField<LocalDateTime> POSTING_DATE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> DOCUMENT_DATE
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_TYPE
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_TYPE_NAME
public static final OperationalAcctgDocItemCubeField<LocalDateTime> NET_DUE_DATE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> CASH_DISCOUNT1_DUE_DATE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> CASH_DISCOUNT2_DUE_DATE
public static final OperationalAcctgDocItemCubeField<String> OFFSETTING_ACCOUNT
public static final OperationalAcctgDocItemCubeField<String> OFFSETTING_ACCOUNT_TYPE
public static final OperationalAcctgDocItemCubeField<String> PARTNER_FUND
public static final OperationalAcctgDocItemCubeField<String> PARTNER_GRANT
public static final OperationalAcctgDocItemCubeField<String> BUDGET_PERIOD
public static final OperationalAcctgDocItemCubeField<String> PARTNER_BUDGET_PERIOD
public static final OperationalAcctgDocItemCubeField<String> BRANCH_CODE
public static final OperationalAcctgDocItemCubeField<String> COMPANY_CODE_CURRENCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> AMOUNT_IN_COMPANY_CODE_CURRENCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> TAX_AMOUNT_IN_CO_CODE_CRCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> TAX_BASE_AMOUNT_IN_CO_CODE_CRCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> VALUATION_DIFF_AMT_IN_CO_CODE_CRCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> CASH_DISCOUNT_AMT_IN_CO_CODE_CRCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> INVOICE_AMT_IN_CO_CODE_CRCY
public static final OperationalAcctgDocItemCubeField<String> TRANSACTION_CURRENCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> AMOUNT_IN_TRANSACTION_CURRENCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> ORIGINAL_TAX_BASE_AMOUNT
public static final OperationalAcctgDocItemCubeField<BigDecimal> TAX_AMOUNT
public static final OperationalAcctgDocItemCubeField<BigDecimal> TAX_BASE_AMOUNT_IN_TRANS_CRCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> WITHHOLDING_TAX_BASE_AMOUNT
public static final OperationalAcctgDocItemCubeField<BigDecimal> PLANNED_AMT_IN_TRANSACTION_CRCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> CASH_DISCOUNT_BASE_AMOUNT
public static final OperationalAcctgDocItemCubeField<BigDecimal> CASH_DISCOUNT_AMOUNT
public static final OperationalAcctgDocItemCubeField<BigDecimal> NET_PAYMENT_AMOUNT
public static final OperationalAcctgDocItemCubeField<BigDecimal> WITHHOLDING_TAX_AMOUNT
public static final OperationalAcctgDocItemCubeField<BigDecimal> WITHHOLDING_TAX_EXEMPTION_AMT
public static final OperationalAcctgDocItemCubeField<BigDecimal> INVOICE_AMOUNT_IN_FRGN_CURRENCY
public static final OperationalAcctgDocItemCubeField<String> BALANCE_TRANSACTION_CURRENCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> AMOUNT_IN_BALANCE_TRANSAC_CRCY
public static final OperationalAcctgDocItemCubeField<String> ADDITIONAL_CURRENCY1
public static final OperationalAcctgDocItemCubeField<BigDecimal> VALUATION_DIFF_AMT_IN_ADDL_CRCY1
public static final OperationalAcctgDocItemCubeField<BigDecimal> AMOUNT_IN_ADDITIONAL_CURRENCY1
public static final OperationalAcctgDocItemCubeField<String> ADDITIONAL_CURRENCY2
public static final OperationalAcctgDocItemCubeField<BigDecimal> AMOUNT_IN_ADDITIONAL_CURRENCY2
public static final OperationalAcctgDocItemCubeField<BigDecimal> VALUATION_DIFF_AMT_IN_ADDL_CRCY2
public static final OperationalAcctgDocItemCubeField<String> PAYMENT_CURRENCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> AMOUNT_IN_PAYMENT_CURRENCY
public static final OperationalAcctgDocItemCubeField<String> CREDIT_CONTROL_AREA_CURRENCY
public static final OperationalAcctgDocItemCubeField<BigDecimal> HEDGED_AMOUNT
public static final OperationalAcctgDocItemCubeField<String> BASE_UNIT
public static final OperationalAcctgDocItemCubeField<BigDecimal> QUANTITY
public static final OperationalAcctgDocItemCubeField<String> GOODS_MOVEMENT_ENTRY_UNIT
public static final OperationalAcctgDocItemCubeField<BigDecimal> QUANTITY_IN_ENTRY_UNIT
public static final OperationalAcctgDocItemCubeField<String> PURCHASING_DOCUMENT_PRICE_UNIT
public static final OperationalAcctgDocItemCubeField<BigDecimal> PURCHASE_ORDER_QTY
public static final OperationalAcctgDocItemCubeField<BigDecimal> MATERIAL_PRICE_UNIT_QTY
public static final OperationalAcctgDocItemCubeField<BigDecimal> NUMBER_OF_ITEMS
public static final OperationalAcctgDocItemCubeField<LocalDateTime> ACCOUNTING_DOCUMENT_CREATION_DATE
public static final OperationalAcctgDocItemCubeField<LocalTime> CREATION_TIME
public static final OperationalAcctgDocItemCubeField<LocalDateTime> LAST_CHANGE_DATE
public static final OperationalAcctgDocItemCubeField<LocalDateTime> EXCHANGE_RATE_DATE
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOC_CREATED_BY_USER
public static final OperationalAcctgDocItemCubeField<String> TRANSACTION_CODE
public static final OperationalAcctgDocItemCubeField<String> INTERCOMPANY_TRANSACTION
public static final OperationalAcctgDocItemCubeField<String> DOCUMENT_REFERENCE_ID
public static final OperationalAcctgDocItemCubeField<String> RECURRING_ACCOUNTING_DOCUMENT
public static final OperationalAcctgDocItemCubeField<String> REVERSE_DOCUMENT
public static final OperationalAcctgDocItemCubeField<String> REVERSE_DOCUMENT_FISCAL_YEAR
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_HEADER_TEXT
public static final OperationalAcctgDocItemCubeField<BigDecimal> EXCHANGE_RATE
public static final OperationalAcctgDocItemCubeField<String> BUSINESS_TRANSACTION_TYPE
public static final OperationalAcctgDocItemCubeField<String> BATCH_INPUT_SESSION
public static final OperationalAcctgDocItemCubeField<String> FINANCIAL_MANAGEMENT_AREA
public static final OperationalAcctgDocItemCubeField<Boolean> REVERSAL_IS_PLANNED
public static final OperationalAcctgDocItemCubeField<LocalDateTime> PLANNED_REVERSAL_DATE
public static final OperationalAcctgDocItemCubeField<Boolean> TAX_IS_CALCULATED_AUTOMATICALLY
public static final OperationalAcctgDocItemCubeField<Boolean> TAX_BASE_AMOUNT_IS_NET_AMOUNT
public static final OperationalAcctgDocItemCubeField<String> SOURCE_COMPANY_CODE
public static final OperationalAcctgDocItemCubeField<String> LOGICAL_SYSTEM
public static final OperationalAcctgDocItemCubeField<BigDecimal> TAX_EXCHANGE_RATE
public static final OperationalAcctgDocItemCubeField<String> REVERSAL_REASON
public static final OperationalAcctgDocItemCubeField<String> BRANCH
public static final OperationalAcctgDocItemCubeField<String> REFERENCE1_IN_DOCUMENT_HEADER
public static final OperationalAcctgDocItemCubeField<String> REFERENCE2_IN_DOCUMENT_HEADER
public static final OperationalAcctgDocItemCubeField<LocalDateTime> INVOICE_RECEIPT_DATE
public static final OperationalAcctgDocItemCubeField<String> LEDGER
public static final OperationalAcctgDocItemCubeField<String> LEDGER_GROUP
public static final OperationalAcctgDocItemCubeField<String> ALTERNATIVE_REFERENCE_DOCUMENT
public static final OperationalAcctgDocItemCubeField<LocalDateTime> TAX_REPORTING_DATE
public static final OperationalAcctgDocItemCubeField<String> ACCOUNTING_DOCUMENT_CLASS
public static final OperationalAcctgDocItemCubeField<String> EXCHANGE_RATE_TYPE
public static final OperationalAcctgDocItemCubeField<String> LATE_PAYMENT_REASON
public static final OperationalAcctgDocItemCubeField<String> SALES_DOCUMENT_CONDITION
public static final OperationalAcctgDocItemCubeField<Boolean> IS_REVERSAL
public static final OperationalAcctgDocItemCubeField<Boolean> IS_REVERSED
public Class<OperationalAcctgDocItemCube> getType()
getType
in class VdmObject<OperationalAcctgDocItemCube>
public void setCompanyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
companyCode
- Company Codepublic void setFiscalYear(@Nullable String fiscalYear)
Original property name from the Odata EDM: FiscalYear
fiscalYear
- Fiscal Yearpublic void setAccountingDocument(@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.
accountingDocument
- The document number is the key the system uses to access the accounting document.public void setAccountingDocumentItem(@Nullable String accountingDocumentItem)
Original property name from the Odata EDM: AccountingDocumentItem
accountingDocumentItem
- Journal Entry Posting View Itempublic void setCompanyCodeName(@Nullable String companyCodeName)
Original property name from the Odata EDM: CompanyCodeName
companyCodeName
- Company Code Namepublic void setChartOfAccounts(@Nullable String chartOfAccounts)
Original property name from the Odata EDM: ChartOfAccounts
chartOfAccounts
- Chart of Accountspublic void setAccountingDocumentItemType(@Nullable String accountingDocumentItemType)
Original property name from the Odata EDM: AccountingDocumentItemType
For external purposes, the field content is unimportant and therefore, must not be used in customer reporting. In particular, there is no guarantee that the field is always filled (correctly). For internal purposes, a list of the indicators currently used (with no guarantee that it is complete) Use in invoice verification/inventory management Buzid Use 8 " Revaluation A " Asset B " Warehouse stock order C " Warehouse stock order assigned K " Vendor F " Delivery costs G " Assigned delivery costs H " Delivery costs - warehouse stock order I " Delivery costs - assigned warehouse stock order L " Warehouse order M " Material N " Assigned order P " Price difference S " General G/L account T " Tax W " GR/IR item X " Purchase order - assigned asset Y " Delivery costs - assigned asset Z " Cash discount clearing Use in FI: Special feature: Not just used to indicate G/L accounts; also used for special open items BUZID KOART Use A D;K Statistical offsetting posting (Sp.G/L) P D;K Payment requests U S Valuation adjustments for reversal R D;K Residual item transfer posting E D FSCM Biller Direct D S Bill of exchange discounting S D;K Bill of exchange charges W S Bill of exchange tax
accountingDocumentItemType
- Some automatically created line items receive special indicators for further processing.public void setClearingDate(@Nullable LocalDateTime clearingDate)
Original property name from the Odata EDM: ClearingDate
clearingDate
- Clearing Datepublic void setClearingCreationDate(@Nullable LocalDateTime clearingCreationDate)
Original property name from the Odata EDM: ClearingCreationDate
clearingCreationDate
- Clearing Creation Datepublic void setClearingAccountingDocument(@Nullable String clearingAccountingDocument)
Original property name from the Odata EDM: ClearingAccountingDocument
clearingAccountingDocument
- Clearing Entrypublic void setIsCleared(@Nullable Boolean isCleared)
Original property name from the Odata EDM: IsCleared
isCleared
- Clearing Status: Is Clearedpublic void setPostingKey(@Nullable String postingKey)
Original property name from the Odata EDM: PostingKey
postingKey
- Posting Keypublic void setFinancialAccountType(@Nullable String financialAccountType)
Original property name from the Odata EDM: FinancialAccountType
financialAccountType
- The account type determines whether the general ledger or one of the subledgers is used.public void setSpecialGLCode(@Nullable String specialGLCode)
Original property name from the Odata EDM: SpecialGLCode
specialGLCode
- Special G/L Indicatorpublic void setSpecialGLTransactionType(@Nullable String specialGLTransactionType)
Original property name from the Odata EDM: SpecialGLTransactionType
By using this type, you can select entry screens or use certain calculation procedures, for example. The following types must be used : A For all types of down payments as well as down payment requests W For all types of bills of exchange as well as bill of exchange payment requests. You can use any other types except for A and W for all other special G/L transactions.
specialGLTransactionType
- The special G/L transaction type groups together similiar special G/L transactions.public void setDebitCreditCode(@Nullable String debitCreditCode)
Original property name from the Odata EDM: DebitCreditCode
debitCreditCode
- Debit/Credit Codepublic void setBusinessArea(@Nullable String businessArea)
Original property name from the Odata EDM: BusinessArea
businessArea
- Business Areapublic void setBusinessAreaName(@Nullable String businessAreaName)
Original property name from the Odata EDM: BusinessAreaName
businessAreaName
- Business Area Namepublic void setPartnerBusinessArea(@Nullable String partnerBusinessArea)
Original property name from the Odata EDM: PartnerBusinessArea
This relationship enables internal business volume to be eliminated at the business area level (as part of business area consolidation).
partnerBusinessArea
- Business area of the business partner. In each line item, a sender-receiver relationship is established in connection with the business area with which the posting is made.public void setTaxCode(@Nullable String taxCode)
Original property name from the Odata EDM: TaxCode
The tax indicators are unique to each country. For each tax indicator, the tax rate and other properties are stored in the system. For tax-exempt or non-taxable transactions, tax indicators with the percentage 0 should be used if the corresponding transactions are to be entered in the tax returns. When tax rates are changed by legislation, new tax indicators have to be defined. The old indicators with the old tax rates must remain in force until there are no more open items that use this tax indicator.
taxCode
- The sales tax indicator is used in place of a tax category that must be taken into account for tax returns to the tax authorities.public void setWithholdingTaxCode(@Nullable String withholdingTaxCode)
Original property name from the Odata EDM: WithholdingTaxCode
withholdingTaxCode
- Withholding Tax Codepublic void setTaxType(@Nullable String taxType)
Original property name from the Odata EDM: TaxType
taxType
- Indicator for differentiating output tax and input tax.public void setTransactionTypeDetermination(@Nullable String transactionTypeDetermination)
Original property name from the Odata EDM: TransactionTypeDetermination
transactionTypeDetermination
- Transaction Keypublic void setValueDate(@Nullable LocalDateTime valueDate)
Original property name from the Odata EDM: ValueDate
The value date is used in bank accounts and bank sub-accounts.
valueDate
- Value datepublic void setAssignmentReference(@Nullable String assignmentReference)
Original property name from the Odata EDM: AssignmentReference
assignmentReference
- Assignment Referencepublic void setDocumentItemText(@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.
documentItemText
- Contains an explanatory text on the line item.public void setPartnerCompany(@Nullable String partnerCompany)
Original property name from the Odata EDM: PartnerCompany
partnerCompany
- Corporate-wide, unique company ID in your group.public void setFinancialTransactionType(@Nullable String financialTransactionType)
Original property name from the Odata EDM: FinancialTransactionType
financialTransactionType
- Financial Transaction Typepublic void setCorporateGroupAccount(@Nullable String corporateGroupAccount)
Original property name from the Odata EDM: CorporateGroupAccount
corporateGroupAccount
- Corporate Group Accountpublic void setPlanningLevel(@Nullable String planningLevel)
Original property name from the Odata EDM: PlanningLevel
The following levels could be possible: Only noted items in the cash position Only noted items in the liquidity forecast Purchase orders Sales orders Notified incoming payments FI payment settlements (incoming checks, outgoing checks, bills of exchange, payments) FI bank transactions (bank statement postings, cashed checks, bill of exchange payments) You can freely choose the planning levels. You should, however, follow a naming convention: To improve the display of the cash position and liquidity forecast, you should reserve levels that start with "F" or "B" for automatically updating data during posting. F levels should be used for bank accounts, customers, and vendors, and B levels for bank clearing accounts. Examples: F0: bank accounts F1: purchasing/sales (customers/vendors) FF: down payment requests FW: bills of exchange B1: bank clearing accounts, outgoing checks B2: bank clearing accounts, outgoing bank transfers (domestic) B3: bank clearing accounts, outgoing bank transfers (foreign country) B4: bank clearing accounts, bank collection and so on. When displaying the cash position, you can then see because of level F0 that the amounts are posted to the bank account, whereas the other levels show planned bank account transactions, which include entered payment advices or postings to bank clearing accounts. You can then use the display to compare planned date with actual data. In addition, you should reserve levels, for example, all levels beginning with X, to represent postings with payment blocking indicators in the liquidity forecast. When displaying the liquidity forecast, you can then see because of these levels that the displayed amounts are postings with payment blocking indicators. General notes on accounts, or planning groups, and planning levels: Accounts/groups and levels enable you to look at data two different ways. Accounts/groups answer the who question. Which (major) customers or suppliers? Which customer or supplier group? Which bank account or bank clearing account? Levels answer the how question. How information was entered into the system (posting or payment advice or planned item)? How an amount is posted (normal posting or special G/L transaction)? How accurate information is With amounts in the "outgoing transfers" level, you know the exact date on which the account is debited, but with amounts in the "outgoing checks" level, the date on which the account is debited is uncertain. In levels for MM and SD, both the amount and the planning date are more uncertain than the amount and date in FI postings, since the vendor may, for example, deliver only a subset or the delivery may be delayed. In addition, the system always displays MM amounts without taxes in the liquidity forecast (in purchase orders, tax is not displayed if it can be deducted; in purchase requisitions, it is never displayed). Where are cash management levels assigned in the system? In G/L accounts, you define the level in the company-code-specific part of the master record. For accounts receivable and payable, you define a standard level in the cash management and forecast group. At this time, you can define different levels for the following applications and activities: Locked items Special G/L transactions Payment requests Purchase orders and purchase requisitions Orders Agency deals Loans Securities Money market, foreign exchange, derivatives Real estate Earmarked funds The levels defined should be unique - meaning you must not define the same level for more than one application or activity as this may affect the clarity of the display in the cash position or liquidity forecast. It might also adversely affect the function for jumping from these transactions to the correct application or line item display.
planningLevel
- The planning level is used to control displays in Cash Management.public void setControllingArea(@Nullable String controllingArea)
Original property name from the Odata EDM: ControllingArea
controllingArea
- Controlling Areapublic void setControllingAreaName(@Nullable String controllingAreaName)
Original property name from the Odata EDM: ControllingAreaName
controllingAreaName
- Controlling Area Namepublic void setCostCenter(@Nullable String costCenter)
Original property name from the Odata EDM: CostCenter
costCenter
- Cost Centerpublic void setCostCenterName(@Nullable String costCenterName)
Original property name from the Odata EDM: CostCenterName
costCenterName
- Cost Center Namepublic void setProject(@Nullable String project)
Original property name from the Odata EDM: Project
project
- Key identifying a project definition.public void setOrderID(@Nullable String orderID)
Original property name from the Odata EDM: OrderID
orderID
- Order IDpublic void setBillingDocument(@Nullable String billingDocument)
Original property name from the Odata EDM: BillingDocument
billingDocument
- The number that uniquely identifies the billing document (the invoice, for example).public void setSalesDocument(@Nullable String salesDocument)
Original property name from the Odata EDM: SalesDocument
salesDocument
- The number that uniquely identifies the sales document.public void setSalesDocumentItem(@Nullable String salesDocumentItem)
Original property name from the Odata EDM: SalesDocumentItem
salesDocumentItem
- Sales Document Itempublic void setScheduleLine(@Nullable String scheduleLine)
Original property name from the Odata EDM: ScheduleLine
When an item has more than one schedule line, the system automatically assigns a unique number to each line. The number is displayed in the details screens for schedule lines. The schedule line number serves internal purposes and does not, for example, determine the sequence of schedule lines in the overview screen. The schedule lines on the overview screen are sorted by date.
scheduleLine
- The number that uniquely identifies the schedule line in the sales document.public void setMasterFixedAsset(@Nullable String masterFixedAsset)
Original property name from the Odata EDM: MasterFixedAsset
masterFixedAsset
- Fixed Assetpublic void setFixedAsset(@Nullable String fixedAsset)
Original property name from the Odata EDM: FixedAsset
fixedAsset
- Asset Subnumberpublic void setAssetTransactionType(@Nullable String assetTransactionType)
Original property name from the Odata EDM: AssetTransactionType
assetTransactionType
- Asset Transaction Typepublic void setAssetValueDate(@Nullable LocalDateTime assetValueDate)
Original property name from the Odata EDM: AssetValueDate
Since the asset value date can have a direct influence on the amount of depreciation, the system creates a default value when it can. You can specify in Customizing how the the default asset value date is determined by the system.
assetValueDate
- The asset value date is the value date for Asset Accounting. It can deviate from the posting and document date and be in posting periods already closed for Financial Accounting. However, the posting year and asset value date year must be the same.public void setPersonnelNumber(@Nullable String personnelNumber)
Original property name from the Odata EDM: PersonnelNumber
personnelNumber
- The personnel number is the only feature within a client which is unique to an employee. You have to enter a personnel number before you can display and maintain an employee's master data and time data.public void setIsSalesRelated(@Nullable Boolean isSalesRelated)
Original property name from the Odata EDM: IsSalesRelated
isSalesRelated
- Is Sales Relatedpublic void setLineItemDisplayIsEnabled(@Nullable Boolean lineItemDisplayIsEnabled)
Original property name from the Odata EDM: LineItemDisplayIsEnabled
For each line item, an entry is saved in an index table. This entry contains the connection between the line item and the account. In the New General Ledger, line item display is always possible for the general ledger view. You have to set this indicator if you - Also want to see the line items in the entry view - Want open item management You should not set the indicator for accounts where line item display in dialog does not make sense due to the number of postings. These include: Tax accounts Receivables Payables Specific revenue and expense accounts
lineItemDisplayIsEnabled
- Enables line item display for the account.public void setIsOpenItemManaged(@Nullable String isOpenItemManaged)
Original property name from the Odata EDM: IsOpenItemManaged
isOpenItemManaged
- Managed on an Open Item Basispublic void setIsNotCashDiscountLiable(@Nullable Boolean isNotCashDiscountLiable)
Original property name from the Odata EDM: IsNotCashDiscountLiable
isNotCashDiscountLiable
- Is Not Cash Discount Liablepublic void setIsAutomaticallyCreated(@Nullable Boolean isAutomaticallyCreated)
Original property name from the Odata EDM: IsAutomaticallyCreated
isAutomaticallyCreated
- Is Automatically Createdpublic void setIsUsedInPaymentTransaction(@Nullable Boolean isUsedInPaymentTransaction)
Original property name from the Odata EDM: IsUsedInPaymentTransaction
isUsedInPaymentTransaction
- Is Used In Payment Transactionpublic void setOperationalGLAccount(@Nullable String operationalGLAccount)
Original property name from the Odata EDM: OperationalGLAccount
operationalGLAccount
- Operational General Ledger Accountpublic void setGLAccount(@Nullable String gLAccount)
Original property name from the Odata EDM: GLAccount
gLAccount
- G/L Accountpublic void setGLAccountName(@Nullable String gLAccountName)
Original property name from the Odata EDM: GLAccountName
gLAccountName
- G/L Account Namepublic void setGLAccountLongName(@Nullable String gLAccountLongName)
Original property name from the Odata EDM: GLAccountLongName
gLAccountLongName
- G/L Account Long Namepublic void setCustomer(@Nullable String customer)
Original property name from the Odata EDM: Customer
customer
- Gives an alphanumeric key, which clearly identifies the customer or vendor in the SAP system.public void setCustomerName(@Nullable String customerName)
Original property name from the Odata EDM: CustomerName
customerName
- Name of Customerpublic void setSupplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
supplier
- Supplierpublic void setSupplierName(@Nullable String supplierName)
Original property name from the Odata EDM: SupplierName
supplierName
- Name of Supplierpublic void setBranchAccount(@Nullable String branchAccount)
Original property name from the Odata EDM: BranchAccount
branchAccount
- Branch Accountpublic void setIsBalanceSheetAccount(@Nullable Boolean isBalanceSheetAccount)
Original property name from the Odata EDM: IsBalanceSheetAccount
isBalanceSheetAccount
- Is Balance Sheet Accountpublic void setProfitLossAccountType(@Nullable String profitLossAccountType)
Original property name from the Odata EDM: ProfitLossAccountType
profitLossAccountType
- Profit Loss Account Typepublic void setSpecialGLAccountAssignment(@Nullable String specialGLAccountAssignment)
Original property name from the Odata EDM: SpecialGLAccountAssignment
specialGLAccountAssignment
- Assignment Number for Special G/L Accountspublic void setDueCalculationBaseDate(@Nullable LocalDateTime dueCalculationBaseDate)
Original property name from the Odata EDM: DueCalculationBaseDate
dueCalculationBaseDate
- Due Calculation Base Datepublic void setPaymentTerms(@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 management Dunning procedures Payment transactions Data 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 orders header level in purchase orders and invoices Master 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.
paymentTerms
- Key for defining payment terms composed of cash discount percentages and payment periods.public void setCashDiscount1Days(@Nullable BigDecimal cashDiscount1Days)
Original property name from the Odata EDM: CashDiscount1Days
cashDiscount1Days
- Period within which a payment must be made in order to take advantage of the first cash discount terms.public void setCashDiscount2Days(@Nullable BigDecimal cashDiscount2Days)
Original property name from the Odata EDM: CashDiscount2Days
cashDiscount2Days
- Period within which a payment must be made in order to take advantage of the second cash discount terms.public void setNetPaymentDays(@Nullable BigDecimal netPaymentDays)
Original property name from the Odata EDM: NetPaymentDays
netPaymentDays
- Standard settlement period (in days).public void setCashDiscount1Percent(@Nullable BigDecimal cashDiscount1Percent)
Original property name from the Odata EDM: CashDiscount1Percent
cashDiscount1Percent
- Cash Discount Percentage 1public void setCashDiscount2Percent(@Nullable BigDecimal cashDiscount2Percent)
Original property name from the Odata EDM: CashDiscount2Percent
cashDiscount2Percent
- Cash Discount Percentage 2public void setPaymentMethod(@Nullable String paymentMethod)
Original property name from the Odata EDM: PaymentMethod
If you enter a payment method, then only this payment method can be used in automatic payment transactions. If you do not enter a payment method, then one of the payment methods which was allowed in the master record is selected in the payment program according to specified rules. For document entry or document changes, you only enter a payment method if you want to switch off the automatic payment method selection of the payment program.
paymentMethod
- Payment method with which this item is to be paid.public void setPaymentBlockingReason(@Nullable String paymentBlockingReason)
Original property name from the Odata EDM: PaymentBlockingReason
paymentBlockingReason
- Payment Blocking Reasonpublic void setFixedCashDiscount(@Nullable String fixedCashDiscount)
Original property name from the Odata EDM: FixedCashDiscount
fixedCashDiscount
- Fixed Cash Discountpublic void setHouseBank(@Nullable String houseBank)
Original property name from the Odata EDM: HouseBank
houseBank
- All bank data is determined using this key.public void setBPBankAccountInternalID(@Nullable String bPBankAccountInternalID)
Original property name from the Odata EDM: BPBankAccountInternalID
bPBankAccountInternalID
- Business Partner Bank Account Internal IDpublic void setTaxDistributionCode1(@Nullable String taxDistributionCode1)
Original property name from the Odata EDM: TaxDistributionCode1
taxDistributionCode1
- Tax Code 1 for Distributionpublic void setTaxDistributionCode2(@Nullable String taxDistributionCode2)
Original property name from the Odata EDM: TaxDistributionCode2
taxDistributionCode2
- Tax Code 2 for Distributionpublic void setTaxDistributionCode3(@Nullable String taxDistributionCode3)
Original property name from the Odata EDM: TaxDistributionCode3
taxDistributionCode3
- Tax Code 3 for Distributionpublic void setInvoiceReference(@Nullable String invoiceReference)
Original property name from the Odata EDM: InvoiceReference
invoiceReference
- Invoice Referencepublic void setInvoiceReferenceFiscalYear(@Nullable String invoiceReferenceFiscalYear)
Original property name from the Odata EDM: InvoiceReferenceFiscalYear
invoiceReferenceFiscalYear
- Invoice Reference Fiscal Yearpublic void setInvoiceItemReference(@Nullable String invoiceItemReference)
Original property name from the Odata EDM: InvoiceItemReference
invoiceItemReference
- Invoice Item Referencepublic void setFollowOnDocumentType(@Nullable String followOnDocumentType)
Original property name from the Odata EDM: FollowOnDocumentType
followOnDocumentType
- Follow-On Document Typepublic void setStateCentralBankPaymentReason(@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. Austria For 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. Belgium The content of the first text field for this indicator is used in the data medium exchange. Netherlands The 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. Japan For 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.
stateCentralBankPaymentReason
- Germanypublic void setSupplyingCountry(@Nullable String supplyingCountry)
Original property name from the Odata EDM: SupplyingCountry
supplyingCountry
- Supplying Countrypublic void setInvoiceList(@Nullable String invoiceList)
Original property name from the Odata EDM: InvoiceList
invoiceList
- Invoice Listpublic void setBillOfExchangeUsage(@Nullable String billOfExchangeUsage)
Original property name from the Odata EDM: BillOfExchangeUsage
billOfExchangeUsage
- Determines the type of bill of exchange usage.public void setDunningKey(@Nullable String dunningKey)
Original property name from the Odata EDM: DunningKey
You define the contents of the text line in Customizing for the dunning key. If you enter a key in an item, then it can only reach the maximum dunning level defined for this key. Therefore it is possible that an item can contain one dunning notice at the most, although several dunning levels are defined in the dunning procedure.
dunningKey
- Determines that the item can only be dunned with restrictions or is to be displayed with an extra text line on the dunning notice. The keys are freely-definable.public void setDunningBlockingReason(@Nullable String dunningBlockingReason)
Original property name from the Odata EDM: DunningBlockingReason
dunningBlockingReason
- Dunning Blocking Reasonpublic void setLastDunningDate(@Nullable LocalDateTime lastDunningDate)
Original property name from the Odata EDM: LastDunningDate
lastDunningDate
- Date on which the last dunning notice was made.public void setDunningLevel(@Nullable String dunningLevel)
Original property name from the Odata EDM: DunningLevel
The business partner has received the dunning level from the last dunning run. If you use dunning areas, it is the dunning level that the business partner received from the last dunning run in the dunning area assigned. The dunning program sets the dunning level automatically when the customer or vendor receives a dunning notice.
dunningLevel
- Number that specifies how often an item or account has been dunned.public void setDunningArea(@Nullable String dunningArea)
Original property name from the Odata EDM: DunningArea
If different responsibilities or different dunning procedures exist within a company code, you can set up corresponding dunning areas. All dunning notices are made separately according to dunning areas, and if necessary with different dunning procedures. The dunning area must be noted in the line items. As long as documents are copied from preliminary work areas (billing documents), the dunning area can be derived from details such as division or sales area, if necessary.
dunningArea
- The dunning area represents an organizational entity that is responsible for dunning. The dunning areas represent a sub-structure of the company codes.public void setWithholdingTaxCertificate(@Nullable String withholdingTaxCertificate)
Original property name from the Odata EDM: WithholdingTaxCertificate
withholdingTaxCertificate
- Withholding Tax Certificatepublic void setMaterial(@Nullable String material)
Original property name from the Odata EDM: Material
material
- Alphanumeric key uniquely identifying the material.public void setProduct(@Nullable String product)
Original property name from the Odata EDM: Product
product
- Alphanumeric key uniquely identifying the material.public void setPlant(@Nullable String plant)
Original property name from the Odata EDM: Plant
plant
- Key uniquely identifying a plant.public void setPurchasingDocument(@Nullable String purchasingDocument)
Original property name from the Odata EDM: PurchasingDocument
purchasingDocument
- Purchasing Documentpublic void setPurchasingDocumentItem(@Nullable String purchasingDocumentItem)
Original property name from the Odata EDM: PurchasingDocumentItem
purchasingDocumentItem
- Purchasing Document Itempublic void setAccountAssignmentNumber(@Nullable String accountAssignmentNumber)
Original property name from the Odata EDM: AccountAssignmentNumber
accountAssignmentNumber
- Number uniquely defining the account assignment of a purchase document item.public void setIsCompletelyDelivered(@Nullable Boolean isCompletelyDelivered)
Original property name from the Odata EDM: IsCompletelyDelivered
isCompletelyDelivered
- Is completely deliveredpublic void setMaterialPriceControl(@Nullable String materialPriceControl)
Original property name from the Odata EDM: MaterialPriceControl
Standard price Moving average price If the material ledger is activated for the material, this indicator, together with the material's price determination indicator, determines at which of the following prices the material is valuated: Standard price Moving average price Periodic unit price
materialPriceControl
- Indicates the price control used to valuate the stock of a material. You have the following options:public void setValuationArea(@Nullable String valuationArea)
Original property name from the Odata EDM: ValuationArea
Plant All plants belonging to a company code, in which case the valuation area is the company code
valuationArea
- Organizational level at which the material is valuated. A valuation area can be one of the following:public void setInventoryValuationType(@Nullable String inventoryValuationType)
Original property name from the Odata EDM: InventoryValuationType
The valuation types allowed for a material are determined by the valuation category. If a material is valuated according to its origin (valuation category H), you can define the possible countries of origin as valuation types.
inventoryValuationType
- Uniquely identifies separately valuated stocks of a material.public void setVATRegistration(@Nullable String vATRegistration)
Original property name from the Odata EDM: VATRegistration
vATRegistration
- VAT Registrationpublic void setDelivOfGoodsDestCountry(@Nullable String delivOfGoodsDestCountry)
Original property name from the Odata EDM: DelivOfGoodsDestCountry
In the field, the country key of the customer is defaulted. You must change the default value if the country of destination of the goods differs from the reporting country (see field with the same name). The field is currently not used in evaluations but it is planned that this field will be used for processing triangular deals.
delivOfGoodsDestCountry
- Country to which goods are supplied.public void setPaymentDifferenceReason(@Nullable String paymentDifferenceReason)
Original property name from the Odata EDM: PaymentDifferenceReason
paymentDifferenceReason
- Payment Difference Reasonpublic void setProfitCenter(@Nullable String profitCenter)
Original property name from the Odata EDM: ProfitCenter
profitCenter
- Profit Centerpublic void setProfitCenterName(@Nullable String profitCenterName)
Original property name from the Odata EDM: ProfitCenterName
profitCenterName
- Profit Center Namepublic void setJointVenture(@Nullable String jointVenture)
Original property name from the Odata EDM: JointVenture
A joint venture is usually lead by an operating authority, who is responsible for the costs incurred. At the end of a period, all of the costs incurred are split up and allocated to the partners involved. Joint ventures are created to keep costs as low as possible for the operating authority and the partners. This is achieved by distributing the costs incurred to the participants of the joint venture. In the oil industry, new drill-holes are seldomly controlled by the oil companies alone. Instead, contracts are made with other companies. The contract regulates the costs incurred. This enables the risks involved with an unsuccessful drill-hole to be spread out over several companies. Of course, the anticipated profits (from a rich drill-hole) are also distributed to the partners involved. However, the distribution of the profits is not carried out by the SAP Joint Venture Accounting solution.
jointVenture
- A joint venture in the SAP System is a summarization of cost objects whose costs are split up among partners.public void setJointVentureCostRecoveryCode(@Nullable String jointVentureCostRecoveryCode)
Original property name from the Odata EDM: JointVentureCostRecoveryCode
You can define recovery indicators at three different levels: o Document type You can assign a recovery indicator to each document type for the credit side and for the debit side. These recovery indicators are internal recovery indicators and are defined in a separate system table. o Cost element (primary and secondary) o Cost object When you make a posting in one of the feeder systems of the Joint Venture Accounting System, all three levels are evaluated in the sequence defined. The first recovery indicator found is transferred to the Joint Venture Accounting System. o Costs that are 100% allocable o Costs borne 100% by the operator o Overheads applied by the operator o Costs which exceed a contractually agreed price and cannot therefore be allocated o Costs already allocated
jointVentureCostRecoveryCode
- In global companies that belong to joint ventures, incurred costs are usually shared among different recovery indicators which can then be dealt with in different ways using the periodic settlement program.public void setJointVentureEquityGroup(@Nullable String jointVentureEquityGroup)
Original property name from the Odata EDM: JointVentureEquityGroup
jointVentureEquityGroup
- Equity Grouppublic void setTreasuryContractType(@Nullable String treasuryContractType)
Original property name from the Odata EDM: TreasuryContractType
treasuryContractType
- Treasury Contract Typepublic void setAssetContract(@Nullable String assetContract)
Original property name from the Odata EDM: AssetContract
assetContract
- Asset Contractpublic void setCashFlowType(@Nullable String cashFlowType)
Original property name from the Odata EDM: CashFlowType
You can only use a flow type in connection with a financial transaction if you have assigned the flow typy to the corresponding product type in Customizing.
cashFlowType
- The flow type classifies a flow in the cash flow. A flow changes an accounting item (position item, expense or income, and so on).public void setTaxJurisdiction(@Nullable String taxJurisdiction)
Original property name from the Odata EDM: TaxJurisdiction
taxJurisdiction
- Tax Jurisdictionpublic void setRealEstateObject(@Nullable String realEstateObject)
Original property name from the Odata EDM: RealEstateObject
realEstateObject
- Internal Key for Real Estate Objectpublic void setSettlementReferenceDate(@Nullable LocalDateTime settlementReferenceDate)
Original property name from the Odata EDM: SettlementReferenceDate
settlementReferenceDate
- Reference Date for Settlementpublic void setCommitmentItem(@Nullable String commitmentItem)
Original property name from the Odata EDM: CommitmentItem
commitmentItem
- Commitment Itempublic void setCostObject(@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 ID Cost objects represented by objects from other components, such as production orders or sales order items Cost 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.
costObject
- Term identifying the cost object ID.public void setProjectNetwork(@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.
projectNetwork
- A network can structure an entire project or a task within a project.public void setOrderInternalBillOfOperations(@Nullable String orderInternalBillOfOperations)
Original property name from the Odata EDM: OrderInternalBillOfOperations
orderInternalBillOfOperations
- Order Internal Bill of Operations IDpublic void setOrderIntBillOfOperationsItem(@Nullable String orderIntBillOfOperationsItem)
Original property name from the Odata EDM: OrderIntBillOfOperationsItem
orderIntBillOfOperationsItem
- Order Internal Bill of Operations Itempublic void setWBSElementInternalID(@Nullable String wBSElementInternalID)
Original property name from the Odata EDM: WBSElementInternalID
wBSElementInternalID
- Key that indicates a WBS element.public void setProfitabilitySegment(@Nullable String profitabilitySegment)
Original property name from the Odata EDM: ProfitabilitySegment
Examples: Customer '123'/Product '4710' Profitability segment no. 1 Customer '123'/Product '4712' Profitability segment no. 2 Country 'USA'/Region 'NORTH' Profitability segment no. 3
profitabilitySegment
- See glossarypublic void setJointVentureEquityType(@Nullable String jointVentureEquityType)
Original property name from the Odata EDM: JointVentureEquityType
jointVentureEquityType
- Equity Typepublic void setIsEUTriangularDeal(@Nullable Boolean isEUTriangularDeal)
Original property name from the Odata EDM: IsEUTriangularDeal
isEUTriangularDeal
- If you select this field, the system includes this transaction in the EC sales list under the triangular deal section.public void setCostOriginGroup(@Nullable String costOriginGroup)
Original property name from the Odata EDM: CostOriginGroup
When material costs are calculated, each material is given a general ledger account and thus is assigned to a primary cost element. If you enter an origin group for the material, the combination of source group and cost element is updated to the CO component. This means that you can Define calculation bases for determination of overhead rates for particular material groups. Define cost components in product costing for particular material groups. Create rules for activating work in process for each material group. When overhead is calculated, an object is debited with overhead costs and another object (usually a cost center) is credited. For more information on the origin of overhead rates in the credit record, specify an origin group in the credit key. The system then displays the origin group in Cost Center Accounting, as well as the overhead cost element.
costOriginGroup
- Used for subdividing material and overhead costs.public void setCompanyCodeCurrencyDetnMethod(@Nullable String companyCodeCurrencyDetnMethod)
Original property name from the Odata EDM: CompanyCodeCurrencyDetnMethod
companyCodeCurrencyDetnMethod
- Company Code Currency Determination Methodpublic void setClearingIsReversed(@Nullable Boolean clearingIsReversed)
Original property name from the Odata EDM: ClearingIsReversed
clearingIsReversed
- Clearing Is Reversedpublic void setPaymentMethodSupplement(@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.
paymentMethodSupplement
- Characteristic in an open item for the grouping of payments.public void setAlternativeGLAccount(@Nullable String alternativeGLAccount)
Original property name from the Odata EDM: AlternativeGLAccount
alternativeGLAccount
- Alternative G/L Account Number In Company Codepublic void setFundsCenter(@Nullable String fundsCenter)
Original property name from the Odata EDM: FundsCenter
fundsCenter
- Alphanumeric code for the funds center, which you are creating, changing, or displaying, or to which you are assigning budget.public void setFund(@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.
fund
- Key which uniquely identifies the fund.public void setPartnerProfitCenter(@Nullable String partnerProfitCenter)
Original property name from the Odata EDM: PartnerProfitCenter
In the case of the receiver of a service/delivery, the sending profit center is entered as the partner profit center and vice versa.
partnerProfitCenter
- The partner profit center identifies the service and delivery relationships between profit centers.public void setReference1IDByBusinessPartner(@Nullable String reference1IDByBusinessPartner)
Original property name from the Odata EDM: Reference1IDByBusinessPartner
As additional information, for correspondence with the customer/vendor, as a search criterion for items in the customer/vendor account. Enter the customer/vendor details which you need for subsequent processing according to your individual company's regulations. Possible information would be, for example, a customer/vendor branch number, or a transaction number under which a controversial transaction is managed at the customer/vendor.
reference1IDByBusinessPartner
- In this field, you can enter customer/vendor details for the accounting transaction.public void setReference2IDByBusinessPartner(@Nullable String reference2IDByBusinessPartner)
Original property name from the Odata EDM: Reference2IDByBusinessPartner
As additional information, for correspondence with the customer/vendor, as a search criterion for items in the customer/vendor account. Enter the customer/vendor details which you need for subsequent processing according to your individual company's regulations. Possible information would be, for example, a customer/vendor branch number, or a transaction number under which a controversial transaction is managed at the customer/vendor.
reference2IDByBusinessPartner
- In this field, you can enter customer/vendor details for the accounting transaction.public void setIsNegativePosting(@Nullable Boolean isNegativePosting)
Original property name from the Odata EDM: IsNegativePosting
If you set this indicator, you change the way the transaction figures for this account are updated, namely that when you make a debit posting, the credit side of the account is reduced, when you make a credit posting, the debit side of the account is reduced. You use this indicator if the reason for reversal you specified makes negative postings necessary. The system then reverses all the updates of transaction figures caused by the document you reversed. In addition, when you enter documents, individual line items can also be marked as negative postings, provided this is permitted for the document type in question. To reverse transaction figures, set this indicator when entering line items.
isNegativePosting
- Indicates that the transaction figures for this line item are reversed.public void setPaymentCardItem(@Nullable String paymentCardItem)
Original property name from the Odata EDM: PaymentCardItem
paymentCardItem
- Payment Card Itempublic void setPaymentCardPaymentSettlement(@Nullable String paymentCardPaymentSettlement)
Original property name from the Odata EDM: PaymentCardPaymentSettlement
paymentCardPaymentSettlement
- Payment Card Payment Settlementpublic void setCreditControlArea(@Nullable String creditControlArea)
Original property name from the Odata EDM: CreditControlArea
You can also enter the credit control area separately for each posting, if this was marked in the appropriate company code. When entering an order, the credit control area can also be determined from the business area and the sales area segement of the payer's master record or using a user exit. It follows that company codes and credit control areas are not linked. The only thing that you define in the company code table is the default credit control area. This is used either for payments on account to credit these payments, or where you did not enter a credit control area or the system could not determine one. There is also an allocation table of permitted credit control areas per company code which is used to check entries only.
creditControlArea
- The credit control area is an organizational entity which grants and monitors a credit limit for customers. A credit control area can include one or more company codes.public void setReference3IDByBusinessPartner(@Nullable String reference3IDByBusinessPartner)
Original property name from the Odata EDM: Reference3IDByBusinessPartner
reference3IDByBusinessPartner
- ID of Reference 3 by Business Partnerpublic void setDataExchangeInstruction1(@Nullable String dataExchangeInstruction1)
Original property name from the Odata EDM: DataExchangeInstruction1
Instruction key 1 is used in Germany for foreign data medium exchange (field T16). The instruction key informs the bank how the payment is to be carried out. You can find out what each key means in the format descriptions issued by the banks. Instruction key 1 is copied into the instruction key field of the Z1 form and assigned as follows (entries 06/07 are alternatives): SAP field Meaning of instruction Instr. 1 Z1 form in Z1 form 06 1 Advice note to beneficiary's bank 07 1 Advice note to beneficiary's bank 09 2 Advice to beneficiary by telephone 10 3 Advice to beneficiary by fax/telex 04 4 Payment against legitimation - The Netherlands Instruction key 1 is used in the Netherlands as the payment instruction code for foreign bank transfers by data medium exchange. - France In France, this key is used for data medium exchange abroad (field 9 in record 'Enregistrements complementaires') - Brazil In Brazil, instruction key 1 is used for the 'Codigo de Ocorrência' statement. - Denmark In Denmark, this key is used in the format PostGiro Udland. - Finland Instruction key 1 is used in the ULMP and LUM2 formats. The payment method can be determined via the instruction key. - SWIFT MT formats For the SWIFT MT formats, instruction key 1 is converted into a code that is entered in field 72. - Japan Instruction key 1 is used in Japan for data medium exchange abroad. The instruction key informs the bank whether payment should be wired or mailed, or whether a check should be sent. You can find out what each key means in the format descriptions issued by the banks. - Norway In Norway, instruction key 1 is used in Autogiro and Telepay formats. For the Autogiro format, the instruction key can inform the bank if the payer should receive notification. For foreign payments using the Telepay format, instruction key 1 can inform the bank how the payee should be advised.
dataExchangeInstruction1
- - Germanypublic void setDataExchangeInstruction2(@Nullable String dataExchangeInstruction2)
Original property name from the Odata EDM: DataExchangeInstruction2
Instruction key 2 is used in Germany in foreign data medium exchange (field T17). Austria In Austria, instruction key 2 is used for foreign transfers (DME) for the transfer type rapid payment. Netherlands In the Netherlands, instruction key 2 is used as a code for payment instructions when making payments abroad by DME. France In France, instruction key 2 is used for data medium exchange abroad (field 9 in record 'Enregistrements complementaires') Brazil In Brazil, this key can be used as a further specification criteria for instruction key 1 ('Codigo de Ocorrência'). SWIFT MT formats For the SWIFT MT formats, instruction key 2 is converted into a code that is entered in field 72. Japan Instruction key 2 is used in Japan for data medium exchange abroad. The instruction key informs the bank whether the payment should be made according to notification or to an account. You can find out what each key means in the format descriptions issued by the banks.
dataExchangeInstruction2
- Germanypublic void setDataExchangeInstruction3(@Nullable String dataExchangeInstruction3)
Original property name from the Odata EDM: DataExchangeInstruction3
Instruction key 3 is used in Germany for foreign data medium exchange (field T18). Note: If the value 95 is entered, the reporting section of the data medium is issued in the order currency. For the Z1 form, you use the relevant parameter in payment medium program RFFOD__L. Netherlands In the Netherlands, instruction key 3 is used for foreign bank transfers by DME as a code for the payment instructions. Brazil In Brazil, instruction key 3 can be used as an additional selection criteria for instruction key 1 ('Codigo de Ocorrência'). SWIFT MT formats For the SWIFT MT formats, instruction key 3 is converted into a code that is entered in field 72. Japan Instruction key 3 is used in Japan for foreign data medium exchange. The instruction key informs the bank whether the currency translation should be made according to the current rate of exchange or a hedged exchange rate, or whether payment should be made from a foreign exchange account or in Japanese Yen. You will find more details on what the key means in the the format descriptions issued by the bank.
dataExchangeInstruction3
- Germanypublic void setDataExchangeInstruction4(@Nullable String dataExchangeInstruction4)
Original property name from the Odata EDM: DataExchangeInstruction4
Instruction key 4 is used in Germany for foreign data medium exchange (field T19). Netherlands In the Netherlands, key 4 is used as a code for the payment instructions when making transfers abroad by DME. SWIFT MT formats In the case of SWIFT MT formats instruction key 4 is converted into a code that is entered in field 72.
dataExchangeInstruction4
- Germanypublic void setRegion(@Nullable String region)
Original property name from the Odata EDM: Region
The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain. For more information, see the examples in the documentation on the Address Layout Key. Meaning of the regional code in ... Australia -> Province Brazil -> State Canada -> Province Germany -> State Great Britain -> County Italy -> Province Japan -> Prefecture Switzerland -> Canton USA -> State
region
- In some countries, the region forms part of the address. The meaning depends on the country.public void setHasPaymentOrder(@Nullable Boolean hasPaymentOrder)
Original property name from the Odata EDM: HasPaymentOrder
The lock can be removed by the related program.
hasPaymentOrder
- The item can be locked by a payment run using a payment order or a debit memo notification against any further clearing transactions. This indicator provides the reason for the clearing lock.public void setPaymentReference(@Nullable String paymentReference)
Original property name from the Odata EDM: PaymentReference
For vendor line items, the key that the vendor passes on in the invoice is entered in the payment reference. In automatic payment transactions, the payment reference can be passed on again to the payee. When an outgoing payment is made, the payment reference you specify is passed on to the relevant financial institute and from there to the payee. When you are processing your account statement, you can use the payment reference to determine which items you have paid and then clear them. Payment reference numbers are often used in Finland, Norway, and Sweden. These countries also have rules for the structure of the payment reference. Check digit procedures are used to check that these rules are followed. DME Finland: The number '4477' has a check digit of '8' and should be defined as the character string '44778'. DME Norway: The number '12345678' has the check digit '2' when using the Modulo-10 method, and check digit '5' when using the Modulo-11 method. Therefore, 123456782 or 123456785 are permitted as payment references. DME Sweden: The number '1234567890' has the check digit '3' and should be defined as the character string '12345678903'. The Modulo procedure used is a form of Modulo-10 with the key '1212121'.
paymentReference
- The payment reference contains a key for customer line items which is passed on to the customer in the invoice. The customer should refer to the payment reference when making the payment.public void setTaxDeterminationDate(@Nullable LocalDateTime taxDeterminationDate)
Original property name from the Odata EDM: TaxDeterminationDate
The system determines the date for calculating time-dependent tax (depending on the Customizing settings in the company code) either from the posting date or from the document date. If you want to use a date which is neither the posting date nor the document date for calculating tax on sales/purchases, you can enter the alternative date here.
taxDeterminationDate
- This field is significant when determining tax rates.public void setClearingItem(@Nullable BigDecimal clearingItem)
Original property name from the Odata EDM: ClearingItem
clearingItem
- Clearing Itempublic void setBusinessPlace(@Nullable String businessPlace)
Original property name from the Odata EDM: BusinessPlace
businessPlace
- Specifies the business place.public void setTaxSection(@Nullable String taxSection)
Original property name from the Odata EDM: TaxSection
taxSection
- Tax Sectionpublic void setCostCtrActivityType(@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.
costCtrActivityType
- Key uniquely identifying .public void setAccountsReceivableIsPledged(@Nullable String accountsReceivableIsPledged)
Original property name from the Odata EDM: AccountsReceivableIsPledged
accountsReceivableIsPledged
- Accounts Receivable Is Pledgedpublic void setBusinessProcess(@Nullable String businessProcess)
Original property name from the Odata EDM: BusinessProcess
businessProcess
- Key uniquely identifying a business process.public void setGrantID(@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 Draft This is the first stage of a grant. It is a working copy that can be modified as many times as needed. Proposal When the initial draft becomes a formal and complete document, it becomes a proposal. Application When a proposal is routed to the sponsor for approval, it becomes an application. This application might contain changes in the budget or other adjustments. Award If 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. Closing When an award is expiring, a phase of closing is established. Only restricted operations can be performed in this stage. Closed This stage defines an expired and closed grant. No further operations are allowed except archiving.
grantID
- Legal instrument used to establish a funding relationship between a sponsor (grantor) and grantee, in order to carry out a public purpose of support or stimulation in which the sponsor does not expect to be substantially involved.public void setFunctionalArea(@Nullable String functionalArea)
Original property name from the Odata EDM: FunctionalArea
The functional area is required in Funds Management in order to fulfill legal reporting requirements subdividing an organization into functions. You can use the functional area to map global aims and purposes, for example, public safety, town planning, and the expenditures of your organization. For more information on the functional area, see the Implementation Guide of Funds Management Government, section Functional Area in Funds Management Government.
functionalArea
- Used to structure a public organization or enterprise according to functional criteria.public void setFunctionalAreaName(@Nullable String functionalAreaName)
Original property name from the Odata EDM: FunctionalAreaName
functionalAreaName
- Functional Area Namepublic void setCustomerIsInExecution(@Nullable Boolean customerIsInExecution)
Original property name from the Odata EDM: CustomerIsInExecution
customerIsInExecution
- Customer Is In Executionpublic void setFundedProgram(@Nullable String fundedProgram)
Original property name from the Odata EDM: FundedProgram
You create funded programs in the component Funds Management Public Sector. They can be budgeted but not assigned to an account directly. The account assignment is always derived from a different account assignment object when it is posted, for example, from a CO order or WBS element.
fundedProgram
- With funded programs, you can map another functional grouping of you organization's expenditures (FM area) as well as the functional area.public void setClearingDocFiscalYear(@Nullable String clearingDocFiscalYear)
Original property name from the Odata EDM: ClearingDocFiscalYear
clearingDocFiscalYear
- Fiscal Year of Clearing Journal Entrypublic void setLedgerGLLineItem(@Nullable String ledgerGLLineItem)
Original property name from the Odata EDM: LedgerGLLineItem
ledgerGLLineItem
- Ledger Journal Entry Itempublic void setSegment(@Nullable String segment)
Original property name from the Odata EDM: Segment
segment
- Segment for Segmental Reportingpublic void setSegmentName(@Nullable String segmentName)
Original property name from the Odata EDM: SegmentName
segmentName
- Segment Namepublic void setPartnerSegment(@Nullable String partnerSegment)
Original property name from the Odata EDM: PartnerSegment
partnerSegment
- Partner Segment for Segmental Reportingpublic void setPartnerFunctionalArea(@Nullable String partnerFunctionalArea)
Original property name from the Odata EDM: PartnerFunctionalArea
Use for Cost-of-Sales Accounting The functional area is required to create a profit and loss account in Financial Accounting using cost-of-sales accounting. The following are examples of structure criteria: Manufacturing Administration Sales Research and development Use for Government The functional area is needed for Funds Management to meet legal requirements for reporting with functional aspects. You can use the functional area to represent the global targets and goals (such as public safety or city development), in particular the expenses of your organization. Use in cost-of-sales accounting See the documentation on Filling the Functional Area Field. For comprehensive information on cost-of-sales accounting and on the functional area, see the SAP Library under Accounting -> Financial Accounting -> General Ledger -> Cost-of-Sales Accounting. Use in government For more information on the functional area, see the implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
partnerFunctionalArea
- Structure criterion for an enterprise or government based on functional aspects.public void setHouseBankAccount(@Nullable String houseBankAccount)
Original property name from the Odata EDM: HouseBankAccount
houseBankAccount
- House Bank Accountpublic void setCostElement(@Nullable String costElement)
Original property name from the Odata EDM: CostElement
Items in a chart of accounts that are relevant to cost, are referred to as cost elements. They are used for entering all costs within the entire cost accounting system. Cost elements are required to ensure comprehensive reporting and detailed planning.
costElement
- Key uniquely identifying .public void setSEPAMandate(@Nullable String sEPAMandate)
Original property name from the Odata EDM: SEPAMandate
The mandate reference can be specified externally or be determined by internal number assignment. The system determines 12 digit numerical mandate references for the internal number assignment. Whether internal or external number assignment (or both) is possible depends on the application concerned. Once you have created the mandate, you can no longer change its mandate reference. At event 0570, you can implement different logic using your own installation-specific function module. Register the function module in Customizing for Contract Accounts Receivable and Payable under Business Transactions -> Incoming/Outgoing Payment Creation -> Management of SEPA Mandates -> General Settings in the Mandate Reference field. Notes on Assigning Contract Accounts and Contracts to Mandates You can enter a mandate reference in various FI-CA objects (such as, the document item, the contract account, or the contract). The effect of entering a reference is that the system uses the entered mandate for this object during payment. Notes on Using Alternative Payers If you want to enter an alternative payer P1 for business partner B1 with contract account C1, you have to enter the mandate for this alternative payer P1. If the mandate is to be used now exclusively for paying postings on B1, then enter B1 in the field Payment for Alternative Debtor/ID on the lower part of the screen. If you want the mandate to be used only for a certain contract account of B1 (for instance, for C1), then enter the ID of this contract account in the Contract Account field on the upper part of the screen. Example You enter mandate M1 in contract account C1. When items of contract C1 are paid, the system uses mandate M1. Using a mandate for one object does not exclude using it for another object. That means, for example, that you could also enter mandate M1 in contract C2 as the mandate to be used. In that case, no contract account is entered in the mandate itself, so that it can be referenced from multiple objects. Example - Assignment of a mandate to multiple contract accounts Contract account Mandate (in Contract Acct) Meaning C1 M1 Mandate M1 is valid for C1. C2 M1 Mandate M1 is also valid for C2. C3 M2 Mandate M2 is valid for C3. C4 M2 Mandate M2 is also valid for C4. Another alternative is to enter the contract account in the mandate itself. The result of making this assignment, however, is that the mandate can only be used (exclusively) for the payment of items of this one contract account. Example - Assignment of one contract account per mandate Mandate Contract Account (in Mandate) Meaning M1 C1 Mandate M1 is only valid for items of contract account C1. M2 C2 Mandate M2 is only valid for items of contract account C2. If you want a mandate to be used by several FI-CA objects (such as, document, contract account, or contract), enter the mandate only in the given objects. The examples above apply in a similar manner to the assignment of contracts. Even if you do not enter payment data at the contract level in contracts of the various industry components that use Contract Accounts Receivable and Payable, it can be useful to make an assignment between the contract and the mandate. This makes it possible to have the system pay postings assigned to a contract using a specific mandate. If you do not make any assignments between FI-CA objects (such as, document, contract account, or contract) and a mandate, the system determines the mandate from the bank details entered in the payment data of the payer. In doing so, the system compares the IBAN in the mandate with the IBAN of the bank details. If there are several active mandates for the same bank details of the payer, but there are no additional assignments between the mandate and the FI-CA object, you can use event 0653 to specify which of the mandates is used for making the payment. If you do not make any specification, the system uses the first mandate that qualifies for the payment.
sEPAMandate
- Identifies, together with the Creditor Identifier, the mandate uniquely.public void setReferenceDocumentType(@Nullable String referenceDocumentType)
Original property name from the Odata EDM: ReferenceDocumentType
referenceDocumentType
- Reference Document Typepublic void setOriginalReferenceDocument(@Nullable String originalReferenceDocument)
Original property name from the Odata EDM: OriginalReferenceDocument
originalReferenceDocument
- Original Reference Documentpublic void setReferenceDocumentLogicalSystem(@Nullable String referenceDocumentLogicalSystem)
Original property name from the Odata EDM: ReferenceDocumentLogicalSystem
referenceDocumentLogicalSystem
- Logical System of Reference Documentpublic void setAccountingDocumentItemRef(@Nullable String accountingDocumentItemRef)
Original property name from the Odata EDM: AccountingDocumentItemRef
accountingDocumentItemRef
- Journal Entry Line Item Referencepublic void setFiscalPeriod(@Nullable String fiscalPeriod)
Original property name from the Odata EDM: FiscalPeriod
Every business transaction is allocated to a fiscal period. Examples of period classifications: Per calendar month -> 12 fiscal periods Every 4 weeks -> 13 fiscal periods Weekly -> 52 or 53 fiscal periods
fiscalPeriod
- A fiscal period is a self-contained part of a fiscal year.public void setAccountingDocumentCategory(@Nullable String accountingDocumentCategory)
Original property name from the Odata EDM: AccountingDocumentCategory
accountingDocumentCategory
- Journal Entry Categorypublic void setAccountingDocumentCategoryName(@Nullable String accountingDocumentCategoryName)
Original property name from the Odata EDM: AccountingDocumentCategoryName
accountingDocumentCategoryName
- Journal Entry Category Namepublic void setPostingDate(@Nullable LocalDateTime postingDate)
Original property name from the Odata EDM: PostingDate
postingDate
- Posting Datepublic void setDocumentDate(@Nullable LocalDateTime documentDate)
Original property name from the Odata EDM: DocumentDate
documentDate
- Journal Entry Datepublic void setAccountingDocumentType(@Nullable String accountingDocumentType)
Original property name from the Odata EDM: AccountingDocumentType
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.
accountingDocumentType
- The document type classifies the accounting documents. It is stored in the document header.public void setAccountingDocumentTypeName(@Nullable String accountingDocumentTypeName)
Original property name from the Odata EDM: AccountingDocumentTypeName
accountingDocumentTypeName
- Description of the business transaction which is posted using this document type.public void setNetDueDate(@Nullable LocalDateTime netDueDate)
Original property name from the Odata EDM: NetDueDate
netDueDate
- The due date for net payment is calculated from the baseline date for payment and the maximum permissible target dates in the terms of payment. It is not stored in the document line item but is always recalculated during ABAP evaluations via logical data bases (on the basis of the current terms of payment) and displayed in this field.public void setCashDiscount1DueDate(@Nullable LocalDateTime cashDiscount1DueDate)
Original property name from the Odata EDM: CashDiscount1DueDate
cashDiscount1DueDate
- Due Date for Cash Discount 1public void setCashDiscount2DueDate(@Nullable LocalDateTime cashDiscount2DueDate)
Original property name from the Odata EDM: CashDiscount2DueDate
cashDiscount2DueDate
- Cash Discount 2 Due Datepublic void setOffsettingAccount(@Nullable String offsettingAccount)
Original property name from the Odata EDM: OffsettingAccount
offsettingAccount
- Offsetting Accountpublic void setOffsettingAccountType(@Nullable String offsettingAccountType)
Original property name from the Odata EDM: OffsettingAccountType
offsettingAccountType
- Offsetting Account Typepublic void setPartnerFund(@Nullable String partnerFund)
Original property name from the Odata EDM: PartnerFund
If you assign budget to a fund, you can execute a detailed proof of origin for your funds.
partnerFund
- Unique key which identifies a fund.public void setPartnerGrant(@Nullable String partnerGrant)
Original property name from the Odata EDM: PartnerGrant
partnerGrant
- Partner Grantpublic void setBudgetPeriod(@Nullable String budgetPeriod)
Original property name from the Odata EDM: BudgetPeriod
During the budget period, the organization may commit, obligate, and encumber funds (terminology varies). After it, the organization may only post follow-on documents. The budget period always works together with the fund account assignment element in Funds Management (FM). Budget Period A: 2000-2010 Budget Period B: 2005-2015 The actuals and commitments recorded then are differentiated by the period of time on which authority was granted to a particular fund. Fund F1 Budget Period: A Fund F2 Budget Period: A Fund F2 Budget Period: B
budgetPeriod
- Time frame of available budget authority.public void setPartnerBudgetPeriod(@Nullable String partnerBudgetPeriod)
Original property name from the Odata EDM: PartnerBudgetPeriod
During the budget period, the organization may commit, obligate, and encumber funds (terminology varies). After it, the organization may only post follow-on documents. The budget period always works together with the fund account assignment element in Funds Management (FM). Budget Period A: 2000-2010 Budget Period B: 2005-2015 The actuals and commitments recorded then are differentiated by the period of time on which authority was granted to a particular fund. Fund F1 Budget Period: A Fund F2 Budget Period: A Fund F2 Budget Period: B When operations are performed with the fund and the budget, the partner fields help you track the proof of origin for your funds.
partnerBudgetPeriod
- Time frame of available budget authority.public void setBranchCode(@Nullable String branchCode)
Original property name from the Odata EDM: BranchCode
The system displays this code at the time of posting sales order, MM invoice, or FI invoice. Companies not registered with the Revenue Department, must enter the text NVAT in this field. If you enter 0000 or 00000, the system considers this to be the head office of the company. The Advance Return for Tax on Sales/Purchases (RFUMSV00) report reads this value and prints the text Head Office in the Head Office Number field in the list output. If you enter any other value, the RFUMSV00 report prints it in the Branch Office Number field in the list output. If the company is not registered with the Revenue Department, the Head Office Number and the Branch Office Number fields are not filled. The J_1HKORD print program also displays this branch code in the PDF output or script output.
branchCode
- Indicates a unique numeric code (4-digit or 5-digit) that identifies a specific financial institution in Thailand from where the customer or the vendor can claim input VAT or output VAT respectively.public void setCompanyCodeCurrency(@Nullable String companyCodeCurrency)
Original property name from the Odata EDM: CompanyCodeCurrency
companyCodeCurrency
- Company Code Currencypublic void setAmountInCompanyCodeCurrency(@Nullable BigDecimal amountInCompanyCodeCurrency)
Original property name from the Odata EDM: AmountInCompanyCodeCurrency
amountInCompanyCodeCurrency
- Amount in Company Code Currencypublic void setTaxAmountInCoCodeCrcy(@Nullable BigDecimal taxAmountInCoCodeCrcy)
Original property name from the Odata EDM: TaxAmountInCoCodeCrcy
taxAmountInCoCodeCrcy
- Signed Tax Amount in Company Code Currencypublic void setTaxBaseAmountInCoCodeCrcy(@Nullable BigDecimal taxBaseAmountInCoCodeCrcy)
Original property name from the Odata EDM: TaxBaseAmountInCoCodeCrcy
With the direct entry of tax line items, you must always specify the base amount so that the system can check the tax amount. For postings in foreign currency, specifying the amount in foreign currency is sufficient. The local currency amount contained in this field is determined using translation.
taxBaseAmountInCoCodeCrcy
- This field contains the amount for which tax is to be calculated. The amount is taken to be in the local currency of the company code.public void setValuationDiffAmtInCoCodeCrcy(@Nullable BigDecimal valuationDiffAmtInCoCodeCrcy)
Original property name from the Odata EDM: ValuationDiffAmtInCoCodeCrcy
valuationDiffAmtInCoCodeCrcy
- Valuation Difference Amount In Company Code Currencypublic void setCashDiscountAmtInCoCodeCrcy(@Nullable BigDecimal cashDiscountAmtInCoCodeCrcy)
Original property name from the Odata EDM: CashDiscountAmtInCoCodeCrcy
cashDiscountAmtInCoCodeCrcy
- Cash Discount Amount in Company Code Currencypublic void setInvoiceAmtInCoCodeCrcy(@Nullable BigDecimal invoiceAmtInCoCodeCrcy)
Original property name from the Odata EDM: InvoiceAmtInCoCodeCrcy
invoiceAmtInCoCodeCrcy
- Invoice Amount in Company Code Currencypublic void setTransactionCurrency(@Nullable String transactionCurrency)
Original property name from the Odata EDM: TransactionCurrency
transactionCurrency
- Transaction Currencypublic void setAmountInTransactionCurrency(@Nullable BigDecimal amountInTransactionCurrency)
Original property name from the Odata EDM: AmountInTransactionCurrency
amountInTransactionCurrency
- Amount in Transaction Currencypublic void setOriginalTaxBaseAmount(@Nullable BigDecimal originalTaxBaseAmount)
Original property name from the Odata EDM: OriginalTaxBaseAmount
The amount deviates from the actual amount of the line item by automatically determined revised amounts. This is the case, for example, with net document types for which cash discount deductions are calculated non-deductible portions, such as for non-deductible input tax portions of the offsetting entry for additional taxes which can be distributed to expense items.
originalTaxBaseAmount
- Original amount of the line item in document currency.public void setTaxAmount(@Nullable BigDecimal taxAmount)
Original property name from the Odata EDM: TaxAmount
The amount serves, together with other values such as the tax code and the tax base amount, as a basis for the automatically created postings for taxes on sales/purchases and therefore also as a base for the advance return for tax on sales/purchases. During document entry, you specify the tax amount providing it is known. If the tax is distributed between several line items with the same tax code, you can specify the total tax amount for one of these line items. In the case of down payments however, (contrary to this rule) you specify the corresponding tax portion per line item. If only the tax code and not the tax amount is known, you can select 'Calculate tax' for the first item. The tax amount is then calculated by the system.
taxAmount
- Taxes on sales/purchases amount in document currency.public void setTaxBaseAmountInTransCrcy(@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.
taxBaseAmountInTransCrcy
- This field contains the amount on which the tax is to be calculated. The amount is taken to be in the document currency.public void setWithholdingTaxBaseAmount(@Nullable BigDecimal withholdingTaxBaseAmount)
Original property name from the Odata EDM: WithholdingTaxBaseAmount
withholdingTaxBaseAmount
- Withholding Tax Base Amountpublic void setPlannedAmtInTransactionCrcy(@Nullable BigDecimal plannedAmtInTransactionCrcy)
Original property name from the Odata EDM: PlannedAmtInTransactionCrcy
plannedAmtInTransactionCrcy
- Planned Amount in Transaction Currencypublic void setCashDiscountBaseAmount(@Nullable BigDecimal cashDiscountBaseAmount)
Original property name from the Odata EDM: CashDiscountBaseAmount