public class PaymentReleaseListItem extends VdmEntity<PaymentReleaseListItem>
Original entity name from the Odata EDM: PaymentReleaseListItem
| Modifier and Type | Class and Description |
|---|---|
static class |
PaymentReleaseListItem.PaymentReleaseListItemBuilder |
| Modifier and Type | Field and Description |
|---|---|
static PaymentReleaseListItemField<String> |
ACCOUNTBYSHIPPER
Use with available fluent helpers to apply the Accountbyshipper field to query operations.
|
static PaymentReleaseListItemField<String> |
ACCOUNTINGCLERK
Use with available fluent helpers to apply the Accountingclerk field to query operations.
|
static PaymentReleaseListItemField<String> |
ACCOUNTINGDOCUMENT
Use with available fluent helpers to apply the Accountingdocument field to query operations.
|
static PaymentReleaseListItemField<String> |
ACCOUNTINGDOCUMENTITEM
Use with available fluent helpers to apply the Accountingdocumentitem field to query operations.
|
static PaymentReleaseListItemField<String> |
ACCOUNTINGDOCUMENTTYPE
Use with available fluent helpers to apply the Accountingdocumenttype field to query operations.
|
static PaymentReleaseListItemField<Boolean> |
ADDRESSANDBANKISSETMANUALLY
Use with available fluent helpers to apply the Addressandbankissetmanually field to query operations.
|
static PaymentReleaseListItemSelectable |
ALL_FIELDS
Selector for all available fields of PaymentReleaseListItem.
|
static PaymentReleaseListItemField<BigDecimal> |
AMOUNTINBALANCETRANSACCRCY
Use with available fluent helpers to apply the Amountinbalancetransaccrcy field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
AMOUNTINTRANSACTIONCURRENCY
Use with available fluent helpers to apply the Amountintransactioncurrency field to query operations.
|
static PaymentReleaseListItemField<String> |
ASSETCONTRACT
Use with available fluent helpers to apply the Assetcontract field to query operations.
|
static PaymentReleaseListItemField<String> |
ASSIGNMENTREFERENCE
Use with available fluent helpers to apply the Assignmentreference field to query operations.
|
static PaymentReleaseListItemField<String> |
BALANCETRANSACTIONCURRENCY
Use with available fluent helpers to apply the Balancetransactioncurrency field to query operations.
|
static PaymentReleaseListItemField<String> |
BANK
Use with available fluent helpers to apply the Bank field to query operations.
|
static PaymentReleaseListItemField<String> |
BANKACCOUNT
Use with available fluent helpers to apply the Bankaccount field to query operations.
|
static PaymentReleaseListItemField<String> |
BANKACCOUNTHOLDERNAME
Use with available fluent helpers to apply the Bankaccountholdername field to query operations.
|
static PaymentReleaseListItemField<String> |
BANKCONTROLKEY
Use with available fluent helpers to apply the Bankcontrolkey field to query operations.
|
static PaymentReleaseListItemField<String> |
BANKCOUNTRY
Use with available fluent helpers to apply the Bankcountry field to query operations.
|
static PaymentReleaseListItemField<String> |
BANKDETAILREFERENCE
Use with available fluent helpers to apply the Bankdetailreference field to query operations.
|
static PaymentReleaseListItemField<String> |
BANKNUMBER
Use with available fluent helpers to apply the Banknumber field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
BILLOFEXCHANGEDUEDATE
Use with available fluent helpers to apply the Billofexchangeduedate field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
BILLOFEXCHANGEISSUEDATE
Use with available fluent helpers to apply the Billofexchangeissuedate field to query operations.
|
static PaymentReleaseListItemField<String> |
BRANCHACCOUNT
Use with available fluent helpers to apply the Branchaccount field to query operations.
|
static PaymentReleaseListItemField<String> |
BUSINESSAREA
Use with available fluent helpers to apply the Businessarea field to query operations.
|
static PaymentReleaseListItemField<String> |
BUSINESSPLACE
Use with available fluent helpers to apply the Businessplace field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
CASHDISCOUNT1DAYS
Use with available fluent helpers to apply the Cashdiscount1days field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
CASHDISCOUNT1PERCENT
Use with available fluent helpers to apply the Cashdiscount1percent field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
CASHDISCOUNT2DAYS
Use with available fluent helpers to apply the Cashdiscount2days field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
CASHDISCOUNT2PERCENT
Use with available fluent helpers to apply the Cashdiscount2percent field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
CASHDISCOUNTAMOUNT
Use with available fluent helpers to apply the Cashdiscountamount field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
CASHDISCOUNTAMTINTRANSACCRCY
Use with available fluent helpers to apply the Cashdiscountamtintransaccrcy field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
CASHDISCOUNTBASEAMOUNT
Use with available fluent helpers to apply the Cashdiscountbaseamount field to query operations.
|
static PaymentReleaseListItemField<String> |
COMPANYCODE
Use with available fluent helpers to apply the Companycode field to query operations.
|
static PaymentReleaseListItemField<String> |
COSTCENTER
Use with available fluent helpers to apply the Costcenter field to query operations.
|
static PaymentReleaseListItemField<String> |
CREATEDBYUSER
Use with available fluent helpers to apply the Createdbyuser field to query operations.
|
static PaymentReleaseListItemField<String> |
CURRENTPROCESSOR
Use with available fluent helpers to apply the Currentprocessor field to query operations.
|
static PaymentReleaseListItemField<String> |
CUSTOMER
Use with available fluent helpers to apply the Customer field to query operations.
|
static PaymentReleaseListItemField<String> |
DATAEXCHANGEINSTRUCTION1
Use with available fluent helpers to apply the Dataexchangeinstruction1 field to query operations.
|
static PaymentReleaseListItemField<String> |
DATAEXCHANGEINSTRUCTION2
Use with available fluent helpers to apply the Dataexchangeinstruction2 field to query operations.
|
static PaymentReleaseListItemField<String> |
DATAEXCHANGEINSTRUCTION3
Use with available fluent helpers to apply the Dataexchangeinstruction3 field to query operations.
|
static PaymentReleaseListItemField<String> |
DATAEXCHANGEINSTRUCTION4
Use with available fluent helpers to apply the Dataexchangeinstruction4 field to query operations.
|
static PaymentReleaseListItemField<String> |
DATAEXCHANGEINSTRUCTIONKEY
Use with available fluent helpers to apply the Dataexchangeinstructionkey field to query operations.
|
static PaymentReleaseListItemField<String> |
DEBITCREDITCODE
Use with available fluent helpers to apply the Debitcreditcode field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
DOCUMENTDATE
Use with available fluent helpers to apply the Documentdate field to query operations.
|
static PaymentReleaseListItemField<String> |
DOCUMENTITEMTEXT
Use with available fluent helpers to apply the Documentitemtext field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
DUECALCULATIONBASEDATE
Use with available fluent helpers to apply the Duecalculationbasedate field to query operations.
|
static PaymentReleaseListItemField<String> |
EARMARKEDFUNDSDOCUMENT
Use with available fluent helpers to apply the Earmarkedfundsdocument field to query operations.
|
static PaymentReleaseListItemField<String> |
FINANCIALACCOUNTTYPE
Use with available fluent helpers to apply the Financialaccounttype field to query operations.
|
static PaymentReleaseListItemField<String> |
FISCALYEAR
Use with available fluent helpers to apply the Fiscalyear field to query operations.
|
static PaymentReleaseListItemField<String> |
FOLLOWONDOCUMENTTYPE
Use with available fluent helpers to apply the Followondocumenttype field to query operations.
|
static PaymentReleaseListItemField<String> |
FUNCTIONALAREA
Use with available fluent helpers to apply the Functionalarea field to query operations.
|
static PaymentReleaseListItemField<String> |
FUND
Use with available fluent helpers to apply the Fund field to query operations.
|
static PaymentReleaseListItemField<String> |
GLACCOUNT
Use with available fluent helpers to apply the Glaccount field to query operations.
|
static PaymentReleaseListItemField<String> |
GLACCOUNTFORBANKACCOUNT
Use with available fluent helpers to apply the Glaccountforbankaccount field to query operations.
|
static PaymentReleaseListItemField<String> |
GRANTID
Use with available fluent helpers to apply the Grantid field to query operations.
|
static PaymentReleaseListItemField<String> |
HOUSEBANK
Use with available fluent helpers to apply the Housebank field to query operations.
|
static PaymentReleaseListItemField<String> |
HOUSEBANKACCOUNT
Use with available fluent helpers to apply the Housebankaccount field to query operations.
|
static PaymentReleaseListItemField<String> |
INVOICEITEMREFERENCE
Use with available fluent helpers to apply the Invoiceitemreference field to query operations.
|
static PaymentReleaseListItemField<String> |
INVOICEREFERENCE
Use with available fluent helpers to apply the Invoicereference field to query operations.
|
static PaymentReleaseListItemField<String> |
INVOICEREFERENCEFISCALYEAR
Use with available fluent helpers to apply the Invoicereferencefiscalyear field to query operations.
|
static PaymentReleaseListItemField<String> |
LASTCHANGEDBYUSER
Use with available fluent helpers to apply the Lastchangedbyuser field to query operations.
|
static PaymentReleaseListItemField<String> |
NAME
Use with available fluent helpers to apply the Name field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
NETPAYMENTDAYS
Use with available fluent helpers to apply the Netpaymentdays field to query operations.
|
static PaymentReleaseListItemField<String> |
OPERATIONALGLACCOUNT
Use with available fluent helpers to apply the Operationalglaccount field to query operations.
|
static PaymentReleaseListItemField<String> |
ORDERINTERNALBILLOFOPERATIONS
Use with available fluent helpers to apply the Orderinternalbillofoperations field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
PAIDITEMDUEDATE
Use with available fluent helpers to apply the Paiditemduedate field to query operations.
|
static PaymentReleaseListItemField<String> |
PARTNERCOMPANY
Use with available fluent helpers to apply the Partnercompany field to query operations.
|
static PaymentReleaseListItemField<String> |
PARTNERPROFITCENTER
Use with available fluent helpers to apply the Partnerprofitcenter field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEADDITIONALNAME
Use with available fluent helpers to apply the Payeeadditionalname field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEBANK
Use with available fluent helpers to apply the Payeebank field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEBANKACCOUNT
Use with available fluent helpers to apply the Payeebankaccount field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEBANKCONTROLKEY
Use with available fluent helpers to apply the Payeebankcontrolkey field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEBANKCOUNTRY
Use with available fluent helpers to apply the Payeebankcountry field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEBANKIDENTIFIERCODE
Use with available fluent helpers to apply the Payeebankidentifiercode field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEBANKNUMBER
Use with available fluent helpers to apply the Payeebanknumber field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEECITYNAME
Use with available fluent helpers to apply the Payeecityname field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEECOUNTRY
Use with available fluent helpers to apply the Payeecountry field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEIBAN
Use with available fluent helpers to apply the Payeeiban field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEELANGUAGE
Use with available fluent helpers to apply the Payeelanguage field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEPOSTALCODE
Use with available fluent helpers to apply the Payeepostalcode field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYEEREGION
Use with available fluent helpers to apply the Payeeregion field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYERPAYEE
Use with available fluent helpers to apply the Payerpayee field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYINGCOMPANYCODE
Use with available fluent helpers to apply the Payingcompanycode field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTBLOCKINGREASON
Use with available fluent helpers to apply the Paymentblockingreason field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTDOCUMENT
Use with available fluent helpers to apply the Paymentdocument field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
PAYMENTDOCUMENTPOSTINGDATE
Use with available fluent helpers to apply the Paymentdocumentpostingdate field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTMETHODSUPPLEMENT
Use with available fluent helpers to apply the Paymentmethodsupplement field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTORDER
Use with available fluent helpers to apply the Paymentorder field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTREFERENCE
Use with available fluent helpers to apply the Paymentreference field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTRELEASELIST
Use with available fluent helpers to apply the Paymentreleaselist field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTRELEASELISTAPPLICATION
Use with available fluent helpers to apply the Paymentreleaselistapplication field to query operations.
|
static PaymentReleaseListItemField<UUID> |
PAYMENTRELEASELISTITEMUUID
Use with available fluent helpers to apply the Paymentreleaselistitemuuid field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTREQUEST
Use with available fluent helpers to apply the Paymentrequest field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
PAYMENTREQUESTAMOUNTINPAYTCRCY
Use with available fluent helpers to apply the Paymentrequestamountinpaytcrcy field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTREQUESTORIGIN
Use with available fluent helpers to apply the Paymentrequestorigin field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
PAYMENTRUNDATE
Use with available fluent helpers to apply the Paymentrundate field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTRUNID
Use with available fluent helpers to apply the Paymentrunid field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTRUNITEMMESSAGENUMBER
Use with available fluent helpers to apply the Paymentrunitemmessagenumber field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYMENTSTATUS
Use with available fluent helpers to apply the Paymentstatus field to query operations.
|
static PaymentReleaseListItemField<String> |
PAYTRELLISTITEMAPPROVALLEVEL
Use with available fluent helpers to apply the Paytrellistitemapprovallevel field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
POSTINGDATE
Use with available fluent helpers to apply the Postingdate field to query operations.
|
static PaymentReleaseListItemField<String> |
POSTINGKEY
Use with available fluent helpers to apply the Postingkey field to query operations.
|
static PaymentReleaseListItemField<String> |
PROFITCENTER
Use with available fluent helpers to apply the Profitcenter field to query operations.
|
static PaymentReleaseListItemField<String> |
PROJECTNETWORK
Use with available fluent helpers to apply the Projectnetwork field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
PROPOSALRUNDATE
Use with available fluent helpers to apply the Proposalrundate field to query operations.
|
static PaymentReleaseListItemField<String> |
PROPOSALRUNNUMBER
Use with available fluent helpers to apply the Proposalrunnumber field to query operations.
|
static PaymentReleaseListItemField<String> |
PURCHASINGDOCUMENT
Use with available fluent helpers to apply the Purchasingdocument field to query operations.
|
static PaymentReleaseListItemField<String> |
PURCHASINGDOCUMENTITEM
Use with available fluent helpers to apply the Purchasingdocumentitem field to query operations.
|
static PaymentReleaseListItemField<String> |
REFERENCE1IDBYBUSINESSPARTNER
Use with available fluent helpers to apply the Reference1idbybusinesspartner field to query operations.
|
static PaymentReleaseListItemField<String> |
REFERENCE2IDBYBUSINESSPARTNER
Use with available fluent helpers to apply the Reference2idbybusinesspartner field to query operations.
|
static PaymentReleaseListItemField<String> |
REFERENCE3IDBYBUSINESSPARTNER
Use with available fluent helpers to apply the Reference3idbybusinesspartner field to query operations.
|
static PaymentReleaseListItemField<String> |
SALESDOCUMENT
Use with available fluent helpers to apply the Salesdocument field to query operations.
|
static PaymentReleaseListItemField<String> |
SALESDOCUMENTITEM
Use with available fluent helpers to apply the Salesdocumentitem field to query operations.
|
static PaymentReleaseListItemField<String> |
SENDINGCOMPANYCODE
Use with available fluent helpers to apply the Sendingcompanycode field to query operations.
|
static PaymentReleaseListItemField<String> |
SEPAMANDATE
Use with available fluent helpers to apply the Sepamandate field to query operations.
|
static PaymentReleaseListItemField<byte[]> |
SEPAMANDATEUUID
Use with available fluent helpers to apply the Sepamandateuuid field to query operations.
|
static PaymentReleaseListItemField<String> |
SPECIALGLCODE
Use with available fluent helpers to apply the Specialglcode field to query operations.
|
static PaymentReleaseListItemField<String> |
STATECENTRALBANKPAYMENTREASON
Use with available fluent helpers to apply the Statecentralbankpaymentreason field to query operations.
|
static PaymentReleaseListItemField<String> |
SUPPLIER
Use with available fluent helpers to apply the Supplier field to query operations.
|
static PaymentReleaseListItemField<String> |
SUPPLIERFULLNAME
Use with available fluent helpers to apply the Supplierfullname field to query operations.
|
static PaymentReleaseListItemField<String> |
SUPPLIERPAYMENTMETHOD
Use with available fluent helpers to apply the Supplierpaymentmethod field to query operations.
|
static PaymentReleaseListItemField<String> |
SUPPLYINGCOUNTRY
Use with available fluent helpers to apply the Supplyingcountry field to query operations.
|
static PaymentReleaseListItemField<String> |
TAXCODE
Use with available fluent helpers to apply the Taxcode field to query operations.
|
static PaymentReleaseListItemField<String> |
TAXID2
Use with available fluent helpers to apply the Taxid2 field to query operations.
|
static PaymentReleaseListItemField<String> |
TRANSACTIONCURRENCY
Use with available fluent helpers to apply the Transactioncurrency field to query operations.
|
static PaymentReleaseListItemField<LocalDateTime> |
VALUEDATE
Use with available fluent helpers to apply the Valuedate field to query operations.
|
static PaymentReleaseListItemField<String> |
VATREGISTRATION
Use with available fluent helpers to apply the Vatregistration field to query operations.
|
static PaymentReleaseListItemField<BigDecimal> |
WHLDGTAXAMTINTRANSACCRCY
Use with available fluent helpers to apply the Whldgtaxamtintransaccrcy field to query operations.
|
static PaymentReleaseListItemField<String> |
WITHHOLDINGTAXCODE
Use with available fluent helpers to apply the Withholdingtaxcode field to query operations.
|
changedOriginalFields| Constructor and Description |
|---|
PaymentReleaseListItem() |
PaymentReleaseListItem(UUID paymentreleaselistitemuuid,
String paymentreleaselist,
String paymentstatus,
String paytrellistitemapprovallevel,
String createdbyuser,
String lastchangedbyuser,
String paymentreleaselistapplication,
String companycode,
String accountingdocument,
String fiscalyear,
String accountingdocumentitem,
String supplierfullname,
String supplier,
String customer,
String branchaccount,
String payerpayee,
String partnercompany,
String debitcreditcode,
String transactioncurrency,
BigDecimal amountintransactioncurrency,
BigDecimal cashdiscountbaseamount,
BigDecimal cashdiscountamtintransaccrcy,
BigDecimal whldgtaxamtintransaccrcy,
String balancetransactioncurrency,
BigDecimal amountinbalancetransaccrcy,
BigDecimal cashdiscountamount,
String accountingdocumenttype,
LocalDateTime postingdate,
LocalDateTime documentdate,
String financialaccounttype,
String postingkey,
String glaccount,
String operationalglaccount,
String specialglcode,
String businessarea,
String taxcode,
String withholdingtaxcode,
String documentitemtext,
LocalDateTime duecalculationbasedate,
BigDecimal cashdiscount1days,
BigDecimal cashdiscount2days,
BigDecimal netpaymentdays,
BigDecimal cashdiscount1percent,
BigDecimal cashdiscount2percent,
String purchasingdocument,
String purchasingdocumentitem,
String vatregistration,
String statecentralbankpaymentreason,
String supplyingcountry,
String projectnetwork,
String orderinternalbillofoperations,
String assignmentreference,
String assetcontract,
String followondocumenttype,
String costcenter,
String salesdocument,
String salesdocumentitem,
String profitcenter,
String reference1idbybusinesspartner,
String reference2idbybusinesspartner,
String reference3idbybusinesspartner,
String dataexchangeinstruction1,
String dataexchangeinstruction2,
String dataexchangeinstruction3,
String dataexchangeinstruction4,
Boolean addressandbankissetmanually,
String businessplace,
String partnerprofitcenter,
String grantid,
String functionalarea,
String fund,
String paymentrequest,
BigDecimal paymentrequestamountinpaytcrcy,
String paymentrequestorigin,
String currentprocessor,
String earmarkedfundsdocument,
String taxid2,
String paymentrunitemmessagenumber,
String paymentblockingreason,
LocalDateTime paymentrundate,
String paymentrunid,
String paymentdocument,
String paymentorder,
LocalDateTime proposalrundate,
String proposalrunnumber,
String payingcompanycode,
String sendingcompanycode,
String payeeadditionalname,
String payeepostalcode,
String payeecityname,
String payeecountry,
String payeeregion,
String payeelanguage,
String name,
String payeebankcountry,
String payeebank,
String payeebanknumber,
String payeebankaccount,
String payeebankcontrolkey,
String bankdetailreference,
String payeebankidentifiercode,
String payeeiban,
String bankaccountholdername,
String housebankaccount,
String housebank,
String bankcountry,
String bank,
String banknumber,
String bankaccount,
String bankcontrolkey,
String glaccountforbankaccount,
String supplierpaymentmethod,
String paymentmethodsupplement,
String dataexchangeinstructionkey,
LocalDateTime paymentdocumentpostingdate,
LocalDateTime valuedate,
LocalDateTime paiditemduedate,
LocalDateTime billofexchangeduedate,
LocalDateTime billofexchangeissuedate,
String accountingclerk,
String accountbyshipper,
String paymentreference,
byte[] sepamandateuuid,
String sepamandate,
String invoicereference,
String invoicereferencefiscalyear,
String invoiceitemreference) |
| Modifier and Type | Method and Description |
|---|---|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static PaymentReleaseListItem.PaymentReleaseListItemBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
static <T> PaymentReleaseListItemField<T> |
field(String fieldName,
Class<T> fieldType)
Use with available fluent helpers to apply an extension field to query operations.
|
static <T,DomainT> |
field(String fieldName,
TypeConverter<T,DomainT> typeConverter)
Use with available fluent helpers to apply an extension field to query operations.
|
protected void |
fromMap(Map<String,Object> inputValues) |
String |
getAccountbyshipper()
Constraints: Not nullable, Maximum length: 12
|
String |
getAccountingclerk()
Constraints: Not nullable, Maximum length: 2
|
String |
getAccountingdocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getAccountingdocumentitem()
Constraints: Not nullable, Maximum length: 3
|
String |
getAccountingdocumenttype()
Constraints: Not nullable, Maximum length: 2
|
Boolean |
getAddressandbankissetmanually()
Constraints: none
|
BigDecimal |
getAmountinbalancetransaccrcy()
Constraints: Not nullable, Precision: 24, Scale: 3
|
BigDecimal |
getAmountintransactioncurrency()
Constraints: Not nullable, Precision: 24, Scale: 3
|
String |
getAssetcontract()
Constraints: Not nullable, Maximum length: 13
|
String |
getAssignmentreference()
Constraints: Not nullable, Maximum length: 18
|
String |
getBalancetransactioncurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getBank()
Constraints: Not nullable, Maximum length: 15
|
String |
getBankaccount()
Constraints: Not nullable, Maximum length: 18
|
String |
getBankaccountholdername()
Constraints: Not nullable, Maximum length: 60
|
String |
getBankcontrolkey()
Constraints: Not nullable, Maximum length: 2
|
String |
getBankcountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getBankdetailreference()
Constraints: Not nullable, Maximum length: 20
|
String |
getBanknumber()
Constraints: Not nullable, Maximum length: 15
|
LocalDateTime |
getBillofexchangeduedate()
Constraints: Not nullable, Precision: 7
|
LocalDateTime |
getBillofexchangeissuedate()
Constraints: Not nullable, Precision: 7
|
String |
getBranchaccount()
Constraints: Not nullable, Maximum length: 10
|
String |
getBusinessarea()
Constraints: Not nullable, Maximum length: 4
|
String |
getBusinessplace()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getCashdiscount1days()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getCashdiscount1percent()
Constraints: Not nullable, Precision: 5, Scale: 3
|
BigDecimal |
getCashdiscount2days()
Constraints: Not nullable, Precision: 3, Scale: 0
|
BigDecimal |
getCashdiscount2percent()
Constraints: Not nullable, Precision: 5, Scale: 3
|
BigDecimal |
getCashdiscountamount()
Constraints: Not nullable, Precision: 24, Scale: 3
|
BigDecimal |
getCashdiscountamtintransaccrcy()
Constraints: Not nullable, Precision: 24, Scale: 3
|
BigDecimal |
getCashdiscountbaseamount()
Constraints: Not nullable, Precision: 24, Scale: 3
|
String |
getCompanycode()
Constraints: Not nullable, Maximum length: 4
|
String |
getCostcenter()
Constraints: Not nullable, Maximum length: 10
|
String |
getCreatedbyuser()
Constraints: Not nullable, Maximum length: 12
|
String |
getCurrentprocessor()
Constraints: Not nullable, Maximum length: 12
|
String |
getCustomer()
Constraints: Not nullable, Maximum length: 10
|
String |
getDataexchangeinstruction1()
Constraints: Not nullable, Maximum length: 2
|
String |
getDataexchangeinstruction2()
Constraints: Not nullable, Maximum length: 2
|
String |
getDataexchangeinstruction3()
Constraints: Not nullable, Maximum length: 2
|
String |
getDataexchangeinstruction4()
Constraints: Not nullable, Maximum length: 2
|
String |
getDataexchangeinstructionkey()
Constraints: Not nullable, Maximum length: 2
|
String |
getDebitcreditcode()
Constraints: Not nullable, Maximum length: 1
|
protected String |
getDefaultServicePath()
Used by fluent helpers and navigation property methods to construct OData queries.
|
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
LocalDateTime |
getDocumentdate()
Constraints: Not nullable, Precision: 7
|
String |
getDocumentitemtext()
Constraints: Not nullable, Maximum length: 50
|
LocalDateTime |
getDuecalculationbasedate()
Constraints: Not nullable, Precision: 7
|
String |
getEarmarkedfundsdocument()
Constraints: Not nullable, Maximum length: 10
|
protected String |
getEntityCollection()
Used by fluent helpers and navigation property methods to construct OData queries.
|
String |
getFinancialaccounttype()
Constraints: Not nullable, Maximum length: 1
|
String |
getFiscalyear()
Constraints: Not nullable, Maximum length: 4
|
String |
getFollowondocumenttype()
Constraints: Not nullable, Maximum length: 1
|
String |
getFunctionalarea()
Constraints: Not nullable, Maximum length: 16
|
String |
getFund()
Constraints: Not nullable, Maximum length: 10
|
String |
getGlaccount()
Constraints: Not nullable, Maximum length: 10
|
String |
getGlaccountforbankaccount()
Constraints: Not nullable, Maximum length: 10
|
String |
getGrantid()
Constraints: Not nullable, Maximum length: 20
|
String |
getHousebank()
Constraints: Not nullable, Maximum length: 5
|
String |
getHousebankaccount()
Constraints: Not nullable, Maximum length: 5
|
String |
getInvoiceitemreference()
Constraints: Not nullable, Maximum length: 3
|
String |
getInvoicereference()
Constraints: Not nullable, Maximum length: 10
|
String |
getInvoicereferencefiscalyear()
Constraints: Not nullable, Maximum length: 4
|
protected Map<String,Object> |
getKey() |
String |
getLastchangedbyuser()
Constraints: Not nullable, Maximum length: 12
|
String |
getName()
Constraints: Not nullable, Maximum length: 35
|
BigDecimal |
getNetpaymentdays()
Constraints: Not nullable, Precision: 3, Scale: 0
|
String |
getOperationalglaccount()
Constraints: Not nullable, Maximum length: 10
|
String |
getOrderinternalbillofoperations()
Constraints: Not nullable, Maximum length: 10
|
LocalDateTime |
getPaiditemduedate()
Constraints: Not nullable, Precision: 7
|
String |
getPartnercompany()
Constraints: Not nullable, Maximum length: 6
|
String |
getPartnerprofitcenter()
Constraints: Not nullable, Maximum length: 10
|
String |
getPayeeadditionalname()
Constraints: Not nullable, Maximum length: 35
|
String |
getPayeebank()
Constraints: Not nullable, Maximum length: 15
|
String |
getPayeebankaccount()
Constraints: Not nullable, Maximum length: 18
|
String |
getPayeebankcontrolkey()
Constraints: Not nullable, Maximum length: 2
|
String |
getPayeebankcountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getPayeebankidentifiercode()
Constraints: Not nullable, Maximum length: 11
|
String |
getPayeebanknumber()
Constraints: Not nullable, Maximum length: 15
|
String |
getPayeecityname()
Constraints: Not nullable, Maximum length: 35
|
String |
getPayeecountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getPayeeiban()
Constraints: Not nullable, Maximum length: 34
|
String |
getPayeelanguage()
Constraints: Not nullable, Maximum length: 2
|
String |
getPayeepostalcode()
Constraints: Not nullable, Maximum length: 10
|
String |
getPayeeregion()
Constraints: Not nullable, Maximum length: 3
|
String |
getPayerpayee()
Constraints: Not nullable, Maximum length: 10
|
String |
getPayingcompanycode()
Constraints: Not nullable, Maximum length: 4
|
String |
getPaymentblockingreason()
Constraints: Not nullable, Maximum length: 1
|
String |
getPaymentdocument()
Constraints: Not nullable, Maximum length: 10
|
LocalDateTime |
getPaymentdocumentpostingdate()
Constraints: Not nullable, Precision: 7
|
String |
getPaymentmethodsupplement()
Constraints: Not nullable, Maximum length: 2
|
String |
getPaymentorder()
Constraints: Not nullable, Maximum length: 10
|
String |
getPaymentreference()
Constraints: Not nullable, Maximum length: 30
|
String |
getPaymentreleaselist()
Constraints: Not nullable, Maximum length: 10
|
String |
getPaymentreleaselistapplication()
Constraints: Not nullable, Maximum length: 10
|
UUID |
getPaymentreleaselistitemuuid()
(Key Field) Constraints: Not nullable
|
String |
getPaymentrequest()
Constraints: Not nullable, Maximum length: 10
|
BigDecimal |
getPaymentrequestamountinpaytcrcy()
Constraints: Not nullable, Precision: 24, Scale: 3
|
String |
getPaymentrequestorigin()
Constraints: Not nullable, Maximum length: 8
|
LocalDateTime |
getPaymentrundate()
Constraints: Not nullable, Precision: 7
|
String |
getPaymentrunid()
Constraints: Not nullable, Maximum length: 6
|
String |
getPaymentrunitemmessagenumber()
Constraints: Not nullable, Maximum length: 3
|
String |
getPaymentstatus()
Constraints: Not nullable, Maximum length: 3
|
String |
getPaytrellistitemapprovallevel()
Constraints: Not nullable, Maximum length: 2
|
LocalDateTime |
getPostingdate()
Constraints: Not nullable, Precision: 7
|
String |
getPostingkey()
Constraints: Not nullable, Maximum length: 2
|
String |
getProfitcenter()
Constraints: Not nullable, Maximum length: 10
|
String |
getProjectnetwork()
Constraints: Not nullable, Maximum length: 12
|
LocalDateTime |
getProposalrundate()
Constraints: Not nullable, Precision: 7
|
String |
getProposalrunnumber()
Constraints: Not nullable, Maximum length: 6
|
String |
getPurchasingdocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getPurchasingdocumentitem()
Constraints: Not nullable, Maximum length: 5
|
String |
getReference1idbybusinesspartner()
Constraints: Not nullable, Maximum length: 12
|
String |
getReference2idbybusinesspartner()
Constraints: Not nullable, Maximum length: 12
|
String |
getReference3idbybusinesspartner()
Constraints: Not nullable, Maximum length: 20
|
String |
getSalesdocument()
Constraints: Not nullable, Maximum length: 10
|
String |
getSalesdocumentitem()
Constraints: Not nullable, Maximum length: 6
|
String |
getSendingcompanycode()
Constraints: Not nullable, Maximum length: 4
|
String |
getSepamandate()
Constraints: Not nullable, Maximum length: 35
|
byte[] |
getSepamandateuuid()
Constraints: Not nullable
|
String |
getSpecialglcode()
Constraints: Not nullable, Maximum length: 1
|
String |
getStatecentralbankpaymentreason()
Constraints: Not nullable, Maximum length: 3
|
String |
getSupplier()
Constraints: Not nullable, Maximum length: 10
|
String |
getSupplierfullname()
Constraints: Not nullable, Maximum length: 220
|
String |
getSupplierpaymentmethod()
Constraints: Not nullable, Maximum length: 1
|
String |
getSupplyingcountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getTaxcode()
Constraints: Not nullable, Maximum length: 2
|
String |
getTaxid2()
Constraints: Not nullable, Maximum length: 11
|
String |
getTransactioncurrency()
Constraints: Not nullable, Maximum length: 5
|
Class<PaymentReleaseListItem> |
getType() |
LocalDateTime |
getValuedate()
Constraints: Not nullable, Precision: 7
|
String |
getVatregistration()
Constraints: Not nullable, Maximum length: 20
|
BigDecimal |
getWhldgtaxamtintransaccrcy()
Constraints: Not nullable, Precision: 24, Scale: 3
|
String |
getWithholdingtaxcode()
Constraints: Not nullable, Maximum length: 2
|
int |
hashCode() |
void |
setAccountbyshipper(String accountbyshipper)
Constraints: Not nullable, Maximum length: 12
|
void |
setAccountingclerk(String accountingclerk)
Constraints: Not nullable, Maximum length: 2
|
void |
setAccountingdocument(String accountingdocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setAccountingdocumentitem(String accountingdocumentitem)
Constraints: Not nullable, Maximum length: 3
|
void |
setAccountingdocumenttype(String accountingdocumenttype)
Constraints: Not nullable, Maximum length: 2
|
void |
setAddressandbankissetmanually(Boolean addressandbankissetmanually)
Constraints: none
|
void |
setAmountinbalancetransaccrcy(BigDecimal amountinbalancetransaccrcy)
Constraints: Not nullable, Precision: 24, Scale: 3
|
void |
setAmountintransactioncurrency(BigDecimal amountintransactioncurrency)
Constraints: Not nullable, Precision: 24, Scale: 3
|
void |
setAssetcontract(String assetcontract)
Constraints: Not nullable, Maximum length: 13
|
void |
setAssignmentreference(String assignmentreference)
Constraints: Not nullable, Maximum length: 18
|
void |
setBalancetransactioncurrency(String balancetransactioncurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setBank(String bank)
Constraints: Not nullable, Maximum length: 15
|
void |
setBankaccount(String bankaccount)
Constraints: Not nullable, Maximum length: 18
|
void |
setBankaccountholdername(String bankaccountholdername)
Constraints: Not nullable, Maximum length: 60
|
void |
setBankcontrolkey(String bankcontrolkey)
Constraints: Not nullable, Maximum length: 2
|
void |
setBankcountry(String bankcountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setBankdetailreference(String bankdetailreference)
Constraints: Not nullable, Maximum length: 20
|
void |
setBanknumber(String banknumber)
Constraints: Not nullable, Maximum length: 15
|
void |
setBillofexchangeduedate(LocalDateTime billofexchangeduedate)
Constraints: Not nullable, Precision: 7
|
void |
setBillofexchangeissuedate(LocalDateTime billofexchangeissuedate)
Constraints: Not nullable, Precision: 7
|
void |
setBranchaccount(String branchaccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setBusinessarea(String businessarea)
Constraints: Not nullable, Maximum length: 4
|
void |
setBusinessplace(String businessplace)
Constraints: Not nullable, Maximum length: 4
|
void |
setCashdiscount1days(BigDecimal cashdiscount1days)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setCashdiscount1percent(BigDecimal cashdiscount1percent)
Constraints: Not nullable, Precision: 5, Scale: 3
|
void |
setCashdiscount2days(BigDecimal cashdiscount2days)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setCashdiscount2percent(BigDecimal cashdiscount2percent)
Constraints: Not nullable, Precision: 5, Scale: 3
|
void |
setCashdiscountamount(BigDecimal cashdiscountamount)
Constraints: Not nullable, Precision: 24, Scale: 3
|
void |
setCashdiscountamtintransaccrcy(BigDecimal cashdiscountamtintransaccrcy)
Constraints: Not nullable, Precision: 24, Scale: 3
|
void |
setCashdiscountbaseamount(BigDecimal cashdiscountbaseamount)
Constraints: Not nullable, Precision: 24, Scale: 3
|
void |
setCompanycode(String companycode)
Constraints: Not nullable, Maximum length: 4
|
void |
setCostcenter(String costcenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setCreatedbyuser(String createdbyuser)
Constraints: Not nullable, Maximum length: 12
|
void |
setCurrentprocessor(String currentprocessor)
Constraints: Not nullable, Maximum length: 12
|
void |
setCustomer(String customer)
Constraints: Not nullable, Maximum length: 10
|
void |
setDataexchangeinstruction1(String dataexchangeinstruction1)
Constraints: Not nullable, Maximum length: 2
|
void |
setDataexchangeinstruction2(String dataexchangeinstruction2)
Constraints: Not nullable, Maximum length: 2
|
void |
setDataexchangeinstruction3(String dataexchangeinstruction3)
Constraints: Not nullable, Maximum length: 2
|
void |
setDataexchangeinstruction4(String dataexchangeinstruction4)
Constraints: Not nullable, Maximum length: 2
|
void |
setDataexchangeinstructionkey(String dataexchangeinstructionkey)
Constraints: Not nullable, Maximum length: 2
|
void |
setDebitcreditcode(String debitcreditcode)
Constraints: Not nullable, Maximum length: 1
|
void |
setDocumentdate(LocalDateTime documentdate)
Constraints: Not nullable, Precision: 7
|
void |
setDocumentitemtext(String documentitemtext)
Constraints: Not nullable, Maximum length: 50
|
void |
setDuecalculationbasedate(LocalDateTime duecalculationbasedate)
Constraints: Not nullable, Precision: 7
|
void |
setEarmarkedfundsdocument(String earmarkedfundsdocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setFinancialaccounttype(String financialaccounttype)
Constraints: Not nullable, Maximum length: 1
|
void |
setFiscalyear(String fiscalyear)
Constraints: Not nullable, Maximum length: 4
|
void |
setFollowondocumenttype(String followondocumenttype)
Constraints: Not nullable, Maximum length: 1
|
void |
setFunctionalarea(String functionalarea)
Constraints: Not nullable, Maximum length: 16
|
void |
setFund(String fund)
Constraints: Not nullable, Maximum length: 10
|
void |
setGlaccount(String glaccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setGlaccountforbankaccount(String glaccountforbankaccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setGrantid(String grantid)
Constraints: Not nullable, Maximum length: 20
|
void |
setHousebank(String housebank)
Constraints: Not nullable, Maximum length: 5
|
void |
setHousebankaccount(String housebankaccount)
Constraints: Not nullable, Maximum length: 5
|
void |
setInvoiceitemreference(String invoiceitemreference)
Constraints: Not nullable, Maximum length: 3
|
void |
setInvoicereference(String invoicereference)
Constraints: Not nullable, Maximum length: 10
|
void |
setInvoicereferencefiscalyear(String invoicereferencefiscalyear)
Constraints: Not nullable, Maximum length: 4
|
void |
setLastchangedbyuser(String lastchangedbyuser)
Constraints: Not nullable, Maximum length: 12
|
void |
setName(String name)
Constraints: Not nullable, Maximum length: 35
|
void |
setNetpaymentdays(BigDecimal netpaymentdays)
Constraints: Not nullable, Precision: 3, Scale: 0
|
void |
setOperationalglaccount(String operationalglaccount)
Constraints: Not nullable, Maximum length: 10
|
void |
setOrderinternalbillofoperations(String orderinternalbillofoperations)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaiditemduedate(LocalDateTime paiditemduedate)
Constraints: Not nullable, Precision: 7
|
void |
setPartnercompany(String partnercompany)
Constraints: Not nullable, Maximum length: 6
|
void |
setPartnerprofitcenter(String partnerprofitcenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setPayeeadditionalname(String payeeadditionalname)
Constraints: Not nullable, Maximum length: 35
|
void |
setPayeebank(String payeebank)
Constraints: Not nullable, Maximum length: 15
|
void |
setPayeebankaccount(String payeebankaccount)
Constraints: Not nullable, Maximum length: 18
|
void |
setPayeebankcontrolkey(String payeebankcontrolkey)
Constraints: Not nullable, Maximum length: 2
|
void |
setPayeebankcountry(String payeebankcountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setPayeebankidentifiercode(String payeebankidentifiercode)
Constraints: Not nullable, Maximum length: 11
|
void |
setPayeebanknumber(String payeebanknumber)
Constraints: Not nullable, Maximum length: 15
|
void |
setPayeecityname(String payeecityname)
Constraints: Not nullable, Maximum length: 35
|
void |
setPayeecountry(String payeecountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setPayeeiban(String payeeiban)
Constraints: Not nullable, Maximum length: 34
|
void |
setPayeelanguage(String payeelanguage)
Constraints: Not nullable, Maximum length: 2
|
void |
setPayeepostalcode(String payeepostalcode)
Constraints: Not nullable, Maximum length: 10
|
void |
setPayeeregion(String payeeregion)
Constraints: Not nullable, Maximum length: 3
|
void |
setPayerpayee(String payerpayee)
Constraints: Not nullable, Maximum length: 10
|
void |
setPayingcompanycode(String payingcompanycode)
Constraints: Not nullable, Maximum length: 4
|
void |
setPaymentblockingreason(String paymentblockingreason)
Constraints: Not nullable, Maximum length: 1
|
void |
setPaymentdocument(String paymentdocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentdocumentpostingdate(LocalDateTime paymentdocumentpostingdate)
Constraints: Not nullable, Precision: 7
|
void |
setPaymentmethodsupplement(String paymentmethodsupplement)
Constraints: Not nullable, Maximum length: 2
|
void |
setPaymentorder(String paymentorder)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentreference(String paymentreference)
Constraints: Not nullable, Maximum length: 30
|
void |
setPaymentreleaselist(String paymentreleaselist)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentreleaselistapplication(String paymentreleaselistapplication)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentreleaselistitemuuid(UUID paymentreleaselistitemuuid)
(Key Field) Constraints: Not nullable
|
void |
setPaymentrequest(String paymentrequest)
Constraints: Not nullable, Maximum length: 10
|
void |
setPaymentrequestamountinpaytcrcy(BigDecimal paymentrequestamountinpaytcrcy)
Constraints: Not nullable, Precision: 24, Scale: 3
|
void |
setPaymentrequestorigin(String paymentrequestorigin)
Constraints: Not nullable, Maximum length: 8
|
void |
setPaymentrundate(LocalDateTime paymentrundate)
Constraints: Not nullable, Precision: 7
|
void |
setPaymentrunid(String paymentrunid)
Constraints: Not nullable, Maximum length: 6
|
void |
setPaymentrunitemmessagenumber(String paymentrunitemmessagenumber)
Constraints: Not nullable, Maximum length: 3
|
void |
setPaymentstatus(String paymentstatus)
Constraints: Not nullable, Maximum length: 3
|
void |
setPaytrellistitemapprovallevel(String paytrellistitemapprovallevel)
Constraints: Not nullable, Maximum length: 2
|
void |
setPostingdate(LocalDateTime postingdate)
Constraints: Not nullable, Precision: 7
|
void |
setPostingkey(String postingkey)
Constraints: Not nullable, Maximum length: 2
|
void |
setProfitcenter(String profitcenter)
Constraints: Not nullable, Maximum length: 10
|
void |
setProjectnetwork(String projectnetwork)
Constraints: Not nullable, Maximum length: 12
|
void |
setProposalrundate(LocalDateTime proposalrundate)
Constraints: Not nullable, Precision: 7
|
void |
setProposalrunnumber(String proposalrunnumber)
Constraints: Not nullable, Maximum length: 6
|
void |
setPurchasingdocument(String purchasingdocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setPurchasingdocumentitem(String purchasingdocumentitem)
Constraints: Not nullable, Maximum length: 5
|
void |
setReference1idbybusinesspartner(String reference1idbybusinesspartner)
Constraints: Not nullable, Maximum length: 12
|
void |
setReference2idbybusinesspartner(String reference2idbybusinesspartner)
Constraints: Not nullable, Maximum length: 12
|
void |
setReference3idbybusinesspartner(String reference3idbybusinesspartner)
Constraints: Not nullable, Maximum length: 20
|
void |
setSalesdocument(String salesdocument)
Constraints: Not nullable, Maximum length: 10
|
void |
setSalesdocumentitem(String salesdocumentitem)
Constraints: Not nullable, Maximum length: 6
|
void |
setSendingcompanycode(String sendingcompanycode)
Constraints: Not nullable, Maximum length: 4
|
void |
setSepamandate(String sepamandate)
Constraints: Not nullable, Maximum length: 35
|
void |
setSepamandateuuid(byte[] sepamandateuuid)
Constraints: Not nullable
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setSpecialglcode(String specialglcode)
Constraints: Not nullable, Maximum length: 1
|
void |
setStatecentralbankpaymentreason(String statecentralbankpaymentreason)
Constraints: Not nullable, Maximum length: 3
|
void |
setSupplier(String supplier)
Constraints: Not nullable, Maximum length: 10
|
void |
setSupplierfullname(String supplierfullname)
Constraints: Not nullable, Maximum length: 220
|
void |
setSupplierpaymentmethod(String supplierpaymentmethod)
Constraints: Not nullable, Maximum length: 1
|
void |
setSupplyingcountry(String supplyingcountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setTaxcode(String taxcode)
Constraints: Not nullable, Maximum length: 2
|
void |
setTaxid2(String taxid2)
Constraints: Not nullable, Maximum length: 11
|
void |
setTransactioncurrency(String transactioncurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setValuedate(LocalDateTime valuedate)
Constraints: Not nullable, Precision: 7
|
void |
setVatregistration(String vatregistration)
Constraints: Not nullable, Maximum length: 20
|
void |
setWhldgtaxamtintransaccrcy(BigDecimal whldgtaxamtintransaccrcy)
Constraints: Not nullable, Precision: 24, Scale: 3
|
void |
setWithholdingtaxcode(String withholdingtaxcode)
Constraints: Not nullable, Maximum length: 2
|
protected Map<String,Object> |
toMapOfFields() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifiergetChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields, toMapOfNavigationPropertiespublic static final PaymentReleaseListItemSelectable ALL_FIELDS
public static final PaymentReleaseListItemField<UUID> PAYMENTRELEASELISTITEMUUID
public static final PaymentReleaseListItemField<String> PAYMENTRELEASELIST
public static final PaymentReleaseListItemField<String> PAYMENTSTATUS
public static final PaymentReleaseListItemField<String> PAYTRELLISTITEMAPPROVALLEVEL
public static final PaymentReleaseListItemField<String> CREATEDBYUSER
public static final PaymentReleaseListItemField<String> LASTCHANGEDBYUSER
public static final PaymentReleaseListItemField<String> PAYMENTRELEASELISTAPPLICATION
public static final PaymentReleaseListItemField<String> COMPANYCODE
public static final PaymentReleaseListItemField<String> ACCOUNTINGDOCUMENT
public static final PaymentReleaseListItemField<String> FISCALYEAR
public static final PaymentReleaseListItemField<String> ACCOUNTINGDOCUMENTITEM
public static final PaymentReleaseListItemField<String> SUPPLIERFULLNAME
public static final PaymentReleaseListItemField<String> SUPPLIER
public static final PaymentReleaseListItemField<String> CUSTOMER
public static final PaymentReleaseListItemField<String> BRANCHACCOUNT
public static final PaymentReleaseListItemField<String> PAYERPAYEE
public static final PaymentReleaseListItemField<String> PARTNERCOMPANY
public static final PaymentReleaseListItemField<String> DEBITCREDITCODE
public static final PaymentReleaseListItemField<String> TRANSACTIONCURRENCY
public static final PaymentReleaseListItemField<BigDecimal> AMOUNTINTRANSACTIONCURRENCY
public static final PaymentReleaseListItemField<BigDecimal> CASHDISCOUNTBASEAMOUNT
public static final PaymentReleaseListItemField<BigDecimal> CASHDISCOUNTAMTINTRANSACCRCY
public static final PaymentReleaseListItemField<BigDecimal> WHLDGTAXAMTINTRANSACCRCY
public static final PaymentReleaseListItemField<String> BALANCETRANSACTIONCURRENCY
public static final PaymentReleaseListItemField<BigDecimal> AMOUNTINBALANCETRANSACCRCY
public static final PaymentReleaseListItemField<BigDecimal> CASHDISCOUNTAMOUNT
public static final PaymentReleaseListItemField<String> ACCOUNTINGDOCUMENTTYPE
public static final PaymentReleaseListItemField<LocalDateTime> POSTINGDATE
public static final PaymentReleaseListItemField<LocalDateTime> DOCUMENTDATE
public static final PaymentReleaseListItemField<String> FINANCIALACCOUNTTYPE
public static final PaymentReleaseListItemField<String> POSTINGKEY
public static final PaymentReleaseListItemField<String> GLACCOUNT
public static final PaymentReleaseListItemField<String> OPERATIONALGLACCOUNT
public static final PaymentReleaseListItemField<String> SPECIALGLCODE
public static final PaymentReleaseListItemField<String> BUSINESSAREA
public static final PaymentReleaseListItemField<String> TAXCODE
public static final PaymentReleaseListItemField<String> WITHHOLDINGTAXCODE
public static final PaymentReleaseListItemField<String> DOCUMENTITEMTEXT
public static final PaymentReleaseListItemField<LocalDateTime> DUECALCULATIONBASEDATE
public static final PaymentReleaseListItemField<BigDecimal> CASHDISCOUNT1DAYS
public static final PaymentReleaseListItemField<BigDecimal> CASHDISCOUNT2DAYS
public static final PaymentReleaseListItemField<BigDecimal> NETPAYMENTDAYS
public static final PaymentReleaseListItemField<BigDecimal> CASHDISCOUNT1PERCENT
public static final PaymentReleaseListItemField<BigDecimal> CASHDISCOUNT2PERCENT
public static final PaymentReleaseListItemField<String> PURCHASINGDOCUMENT
public static final PaymentReleaseListItemField<String> PURCHASINGDOCUMENTITEM
public static final PaymentReleaseListItemField<String> VATREGISTRATION
public static final PaymentReleaseListItemField<String> STATECENTRALBANKPAYMENTREASON
public static final PaymentReleaseListItemField<String> SUPPLYINGCOUNTRY
public static final PaymentReleaseListItemField<String> PROJECTNETWORK
public static final PaymentReleaseListItemField<String> ORDERINTERNALBILLOFOPERATIONS
public static final PaymentReleaseListItemField<String> ASSIGNMENTREFERENCE
public static final PaymentReleaseListItemField<String> ASSETCONTRACT
public static final PaymentReleaseListItemField<String> FOLLOWONDOCUMENTTYPE
public static final PaymentReleaseListItemField<String> COSTCENTER
public static final PaymentReleaseListItemField<String> SALESDOCUMENT
public static final PaymentReleaseListItemField<String> SALESDOCUMENTITEM
public static final PaymentReleaseListItemField<String> PROFITCENTER
public static final PaymentReleaseListItemField<String> REFERENCE1IDBYBUSINESSPARTNER
public static final PaymentReleaseListItemField<String> REFERENCE2IDBYBUSINESSPARTNER
public static final PaymentReleaseListItemField<String> REFERENCE3IDBYBUSINESSPARTNER
public static final PaymentReleaseListItemField<String> DATAEXCHANGEINSTRUCTION1
public static final PaymentReleaseListItemField<String> DATAEXCHANGEINSTRUCTION2
public static final PaymentReleaseListItemField<String> DATAEXCHANGEINSTRUCTION3
public static final PaymentReleaseListItemField<String> DATAEXCHANGEINSTRUCTION4
public static final PaymentReleaseListItemField<Boolean> ADDRESSANDBANKISSETMANUALLY
public static final PaymentReleaseListItemField<String> BUSINESSPLACE
public static final PaymentReleaseListItemField<String> PARTNERPROFITCENTER
public static final PaymentReleaseListItemField<String> GRANTID
public static final PaymentReleaseListItemField<String> FUNCTIONALAREA
public static final PaymentReleaseListItemField<String> FUND
public static final PaymentReleaseListItemField<String> PAYMENTREQUEST
public static final PaymentReleaseListItemField<BigDecimal> PAYMENTREQUESTAMOUNTINPAYTCRCY
public static final PaymentReleaseListItemField<String> PAYMENTREQUESTORIGIN
public static final PaymentReleaseListItemField<String> CURRENTPROCESSOR
public static final PaymentReleaseListItemField<String> EARMARKEDFUNDSDOCUMENT
public static final PaymentReleaseListItemField<String> TAXID2
public static final PaymentReleaseListItemField<String> PAYMENTRUNITEMMESSAGENUMBER
public static final PaymentReleaseListItemField<String> PAYMENTBLOCKINGREASON
public static final PaymentReleaseListItemField<LocalDateTime> PAYMENTRUNDATE
public static final PaymentReleaseListItemField<String> PAYMENTRUNID
public static final PaymentReleaseListItemField<String> PAYMENTDOCUMENT
public static final PaymentReleaseListItemField<String> PAYMENTORDER
public static final PaymentReleaseListItemField<LocalDateTime> PROPOSALRUNDATE
public static final PaymentReleaseListItemField<String> PROPOSALRUNNUMBER
public static final PaymentReleaseListItemField<String> PAYINGCOMPANYCODE
public static final PaymentReleaseListItemField<String> SENDINGCOMPANYCODE
public static final PaymentReleaseListItemField<String> PAYEEADDITIONALNAME
public static final PaymentReleaseListItemField<String> PAYEEPOSTALCODE
public static final PaymentReleaseListItemField<String> PAYEECITYNAME
public static final PaymentReleaseListItemField<String> PAYEECOUNTRY
public static final PaymentReleaseListItemField<String> PAYEEREGION
public static final PaymentReleaseListItemField<String> PAYEELANGUAGE
public static final PaymentReleaseListItemField<String> NAME
public static final PaymentReleaseListItemField<String> PAYEEBANKCOUNTRY
public static final PaymentReleaseListItemField<String> PAYEEBANK
public static final PaymentReleaseListItemField<String> PAYEEBANKNUMBER
public static final PaymentReleaseListItemField<String> PAYEEBANKACCOUNT
public static final PaymentReleaseListItemField<String> PAYEEBANKCONTROLKEY
public static final PaymentReleaseListItemField<String> BANKDETAILREFERENCE
public static final PaymentReleaseListItemField<String> PAYEEBANKIDENTIFIERCODE
public static final PaymentReleaseListItemField<String> PAYEEIBAN
public static final PaymentReleaseListItemField<String> BANKACCOUNTHOLDERNAME
public static final PaymentReleaseListItemField<String> HOUSEBANKACCOUNT
public static final PaymentReleaseListItemField<String> HOUSEBANK
public static final PaymentReleaseListItemField<String> BANKCOUNTRY
public static final PaymentReleaseListItemField<String> BANK
public static final PaymentReleaseListItemField<String> BANKNUMBER
public static final PaymentReleaseListItemField<String> BANKACCOUNT
public static final PaymentReleaseListItemField<String> BANKCONTROLKEY
public static final PaymentReleaseListItemField<String> GLACCOUNTFORBANKACCOUNT
public static final PaymentReleaseListItemField<String> SUPPLIERPAYMENTMETHOD
public static final PaymentReleaseListItemField<String> PAYMENTMETHODSUPPLEMENT
public static final PaymentReleaseListItemField<String> DATAEXCHANGEINSTRUCTIONKEY
public static final PaymentReleaseListItemField<LocalDateTime> PAYMENTDOCUMENTPOSTINGDATE
public static final PaymentReleaseListItemField<LocalDateTime> VALUEDATE
public static final PaymentReleaseListItemField<LocalDateTime> PAIDITEMDUEDATE
public static final PaymentReleaseListItemField<LocalDateTime> BILLOFEXCHANGEDUEDATE
public static final PaymentReleaseListItemField<LocalDateTime> BILLOFEXCHANGEISSUEDATE
public static final PaymentReleaseListItemField<String> ACCOUNTINGCLERK
public static final PaymentReleaseListItemField<String> ACCOUNTBYSHIPPER
public static final PaymentReleaseListItemField<String> PAYMENTREFERENCE
public static final PaymentReleaseListItemField<byte[]> SEPAMANDATEUUID
public static final PaymentReleaseListItemField<String> SEPAMANDATE
public static final PaymentReleaseListItemField<String> INVOICEREFERENCE
public static final PaymentReleaseListItemField<String> INVOICEREFERENCEFISCALYEAR
public static final PaymentReleaseListItemField<String> INVOICEITEMREFERENCE
public PaymentReleaseListItem()
public PaymentReleaseListItem(@Nullable UUID paymentreleaselistitemuuid, @Nullable String paymentreleaselist, @Nullable String paymentstatus, @Nullable String paytrellistitemapprovallevel, @Nullable String createdbyuser, @Nullable String lastchangedbyuser, @Nullable String paymentreleaselistapplication, @Nullable String companycode, @Nullable String accountingdocument, @Nullable String fiscalyear, @Nullable String accountingdocumentitem, @Nullable String supplierfullname, @Nullable String supplier, @Nullable String customer, @Nullable String branchaccount, @Nullable String payerpayee, @Nullable String partnercompany, @Nullable String debitcreditcode, @Nullable String transactioncurrency, @Nullable BigDecimal amountintransactioncurrency, @Nullable BigDecimal cashdiscountbaseamount, @Nullable BigDecimal cashdiscountamtintransaccrcy, @Nullable BigDecimal whldgtaxamtintransaccrcy, @Nullable String balancetransactioncurrency, @Nullable BigDecimal amountinbalancetransaccrcy, @Nullable BigDecimal cashdiscountamount, @Nullable String accountingdocumenttype, @Nullable LocalDateTime postingdate, @Nullable LocalDateTime documentdate, @Nullable String financialaccounttype, @Nullable String postingkey, @Nullable String glaccount, @Nullable String operationalglaccount, @Nullable String specialglcode, @Nullable String businessarea, @Nullable String taxcode, @Nullable String withholdingtaxcode, @Nullable String documentitemtext, @Nullable LocalDateTime duecalculationbasedate, @Nullable BigDecimal cashdiscount1days, @Nullable BigDecimal cashdiscount2days, @Nullable BigDecimal netpaymentdays, @Nullable BigDecimal cashdiscount1percent, @Nullable BigDecimal cashdiscount2percent, @Nullable String purchasingdocument, @Nullable String purchasingdocumentitem, @Nullable String vatregistration, @Nullable String statecentralbankpaymentreason, @Nullable String supplyingcountry, @Nullable String projectnetwork, @Nullable String orderinternalbillofoperations, @Nullable String assignmentreference, @Nullable String assetcontract, @Nullable String followondocumenttype, @Nullable String costcenter, @Nullable String salesdocument, @Nullable String salesdocumentitem, @Nullable String profitcenter, @Nullable String reference1idbybusinesspartner, @Nullable String reference2idbybusinesspartner, @Nullable String reference3idbybusinesspartner, @Nullable String dataexchangeinstruction1, @Nullable String dataexchangeinstruction2, @Nullable String dataexchangeinstruction3, @Nullable String dataexchangeinstruction4, @Nullable Boolean addressandbankissetmanually, @Nullable String businessplace, @Nullable String partnerprofitcenter, @Nullable String grantid, @Nullable String functionalarea, @Nullable String fund, @Nullable String paymentrequest, @Nullable BigDecimal paymentrequestamountinpaytcrcy, @Nullable String paymentrequestorigin, @Nullable String currentprocessor, @Nullable String earmarkedfundsdocument, @Nullable String taxid2, @Nullable String paymentrunitemmessagenumber, @Nullable String paymentblockingreason, @Nullable LocalDateTime paymentrundate, @Nullable String paymentrunid, @Nullable String paymentdocument, @Nullable String paymentorder, @Nullable LocalDateTime proposalrundate, @Nullable String proposalrunnumber, @Nullable String payingcompanycode, @Nullable String sendingcompanycode, @Nullable String payeeadditionalname, @Nullable String payeepostalcode, @Nullable String payeecityname, @Nullable String payeecountry, @Nullable String payeeregion, @Nullable String payeelanguage, @Nullable String name, @Nullable String payeebankcountry, @Nullable String payeebank, @Nullable String payeebanknumber, @Nullable String payeebankaccount, @Nullable String payeebankcontrolkey, @Nullable String bankdetailreference, @Nullable String payeebankidentifiercode, @Nullable String payeeiban, @Nullable String bankaccountholdername, @Nullable String housebankaccount, @Nullable String housebank, @Nullable String bankcountry, @Nullable String bank, @Nullable String banknumber, @Nullable String bankaccount, @Nullable String bankcontrolkey, @Nullable String glaccountforbankaccount, @Nullable String supplierpaymentmethod, @Nullable String paymentmethodsupplement, @Nullable String dataexchangeinstructionkey, @Nullable LocalDateTime paymentdocumentpostingdate, @Nullable LocalDateTime valuedate, @Nullable LocalDateTime paiditemduedate, @Nullable LocalDateTime billofexchangeduedate, @Nullable LocalDateTime billofexchangeissuedate, @Nullable String accountingclerk, @Nullable String accountbyshipper, @Nullable String paymentreference, @Nullable byte[] sepamandateuuid, @Nullable String sepamandate, @Nullable String invoicereference, @Nullable String invoicereferencefiscalyear, @Nullable String invoiceitemreference)
@Nonnull public Class<PaymentReleaseListItem> getType()
getType in class VdmObject<PaymentReleaseListItem>public void setPaymentreleaselistitemuuid(@Nullable UUID paymentreleaselistitemuuid)
Original property name from the Odata EDM: Paymentreleaselistitemuuid
paymentreleaselistitemuuid - UUID in X form (binary)public void setPaymentreleaselist(@Nullable String paymentreleaselist)
Original property name from the Odata EDM: Paymentreleaselist
paymentreleaselist - Uniquely identifies a list created in the Payment Release List application and is generated by the
application.public void setPaymentstatus(@Nullable String paymentstatus)
Original property name from the Odata EDM: Paymentstatus
paymentstatus - Item Statuspublic void setPaytrellistitemapprovallevel(@Nullable String paytrellistitemapprovallevel)
Original property name from the Odata EDM: Paytrellistitemapprovallevel
Items that are pending approval are always assigned an approval level.If an item is assigned to a payment release list, but has not been approved at any level, the field displays the initial value (0).In the IMG activity Define Approval Levels, you can define:Approval levelsYou can define as many approval levels as you require.A description of each approval levelFinal approval levelsWhen you or another approver approve an item at a final approval level, the item status changes to Released for Payment.The actions that approvers can perform at each approval levelIn the IMG activity Disable Clearing and Reversal for Approval Levels, you can define that approvers are not authorized to clear or reverse documents at certain approval levels.In the IMG activity Disable Document Changes for Approval Levels, you can choose the document fields that approvers are not authorized to change at certain approval levels.
paytrellistitemapprovallevel - This field displays the approval level that an item has reached in the approval process. An item can
only be paid after it has been approved at a final approval level.public void setCreatedbyuser(@Nullable String createdbyuser)
Original property name from the Odata EDM: Createdbyuser
createdbyuser - Created Bypublic void setLastchangedbyuser(@Nullable String lastchangedbyuser)
Original property name from the Odata EDM: Lastchangedbyuser
lastchangedbyuser - Last Changed Bypublic void setPaymentreleaselistapplication(@Nullable String paymentreleaselistapplication)
Original property name from the Odata EDM: Paymentreleaselistapplication
paymentreleaselistapplication - Displays the technical name of the Payment Release List application that is activated for processing
items in the payment release process.public void setCompanycode(@Nullable String companycode)
Original property name from the Odata EDM: Companycode
companycode - The company code is an organizational unit within financial accounting.public 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 setFiscalyear(@Nullable String fiscalyear)
Original property name from the Odata EDM: Fiscalyear
fiscalyear - Period, 12 months as a rule, for which the company is to create its inventory and balance sheet. The
fiscal year can be the same as the calendar year, but does not have to be.public void setAccountingdocumentitem(@Nullable String accountingdocumentitem)
Original property name from the Odata EDM: Accountingdocumentitem
accountingdocumentitem - All line items within an accounting document receive a number with which they can be identified. The
numbers are assigned consecutively by the system when entering the document.public void setSupplierfullname(@Nullable String supplierfullname)
Original property name from the Odata EDM: Supplierfullname
supplierfullname - Supplier Full Namepublic void setSupplier(@Nullable String supplier)
Original property name from the Odata EDM: Supplier
supplier - Specifies an alphanumeric key that uniquely identifies the supplier in the SAP system.public 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 setBranchaccount(@Nullable String branchaccount)
Original property name from the Odata EDM: Branchaccount
branchaccount - For postings to a branch account, the account number of the line item's branch is displayed in this
field.public void setPayerpayee(@Nullable String payerpayee)
Original property name from the Odata EDM: Payerpayee
If payment for the document item is not to be made using the business partner posted to, you can enter the required payer/payee number here. You can only use the account numbers stored in the master record for the business partner posted to.You can specify the permitted account numbers in the master record, independently of the company code or on a company-code-specific basis.Enter the required account number if payment is to be made using a different business partner.
payerpayee - In vendor items, this is the payee's account number; in customer items, it is the payer's account
number. The account specified here is used to process automatic payment transactions (checks, bank
transfers, debit memos and so on).public void setPartnercompany(@Nullable String partnercompany)
Original property name from the Odata EDM: Partnercompany
partnercompany - Company ID standard for the whole group.public void setDebitcreditcode(@Nullable String debitcreditcode)
Original property name from the Odata EDM: Debitcreditcode
debitcreditcode - Shows on which side of the account (S = debit, H = credit) the transaction figures are updated.public void setTransactioncurrency(@Nullable String transactioncurrency)
Original property name from the Odata EDM: Transactioncurrency
transactioncurrency - Currency key for amounts in the system.public void setAmountintransactioncurrency(@Nullable BigDecimal amountintransactioncurrency)
Original property name from the Odata EDM: Amountintransactioncurrency
During document entry, enter the amount manually. In the last line item, you can enter a "*" - the amount of the final line item is then the balance of all the line items previously entered.Amounts you enter may be changed automatically by the system if the following postings are made:Tax adjustmentsCash discount adjustments during net postings.
amountintransactioncurrency - Line item amount in document currency.public void setCashdiscountbaseamount(@Nullable BigDecimal cashdiscountbaseamount)
Original property name from the Odata EDM: Cashdiscountbaseamount
During document entry, the amount qualifying for cash discount can be determined manually or automatically. The amount is determined automatically if no entry is made or a '*' is entered.To determine this amount automatically, the system takes into account the offsetting items relevant to cash discount for the invoice item and the rules assigned for each company code for processing cash discount and taxes.
cashdiscountbaseamount - Part of the invoiced amount for which cash discount is granted. The amount is always in the document
currency.public void setCashdiscountamtintransaccrcy(@Nullable BigDecimal cashdiscountamtintransaccrcy)
Original property name from the Odata EDM: Cashdiscountamtintransaccrcy
For open items, this amount is the cash discount agreed upon (assuming a fixed amount was agreed upon and not a percentage rate).For cleared items, the amount shows the cash discount that was actually taken.During document entry, you only need enter the cash discount amount if this amount is fixed rather than a percentage rate. This amount is no longer changed by the system.
cashdiscountamtintransaccrcy - Cash discount amount in document currency.public void setWhldgtaxamtintransaccrcy(@Nullable BigDecimal whldgtaxamtintransaccrcy)
Original property name from the Odata EDM: Whldgtaxamtintransaccrcy
The amount is continuously calculated by the system on the basis of the withholding tax base amount and the tax percentage rate.
whldgtaxamtintransaccrcy - Withholding tax amount in document currency.public void setBalancetransactioncurrency(@Nullable String balancetransactioncurrency)
Original property name from the Odata EDM: Balancetransactioncurrency
An exception can occur with clearing entries in a third currency. The item currency for a clearing entry is always identical to the item currency of the entry to be cleared and can therefore be different from both the document currency and the local currency.You post an invoice in USD in a company code with EUR as its local currency. Payment is made in CHF. The clearing entry in the payment document has the item currency key USD and is therefore different from the document currency CHF and the local currency EUR.
balancetransactioncurrency - Currency that is used as the update currency for the summary data in the general ledger. The currency
corresponds either to the document currency or to the local currency.public void setAmountinbalancetransaccrcy(@Nullable BigDecimal amountinbalancetransaccrcy)
Original property name from the Odata EDM: Amountinbalancetransaccrcy
amountinbalancetransaccrcy - Amount with which the currency fields are updated in the general ledger. The amount corresponds either
to the amount in document currency or the amount in local currency.public void setCashdiscountamount(@Nullable BigDecimal cashdiscountamount)
Original property name from the Odata EDM: Cashdiscountamount
cashdiscountamount - The cash discount which is taken into account during clearing providing the cash discount has not been
set to inactive. The cash discount displayed here can be changed within the framework of the tolerance
limits for users and customers/vendors.public 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 setPostingdate(@Nullable LocalDateTime postingdate)
Original property name from the Odata EDM: Postingdate
The fiscal year and the period for which an update of the accounts specified in the document or cost elements is made, are derived from the posting date.When entering documents, the system checks whether the posting date entered is allowed by means of the posting period permitted.The posting date can differ from both the entry date (day of entry into the system) and the document date (day of creation of the original document).
postingdate - Date which is used when entering the document in Financial Accounting or Controlling.public void setDocumentdate(@Nullable LocalDateTime documentdate)
Original property name from the Odata EDM: Documentdate
documentdate - The document date is the date on which the original document was issued.public 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 setPostingkey(@Nullable String postingkey)
Original property name from the Odata EDM: Postingkey
For every posting key, you specify properties which control the entry of the line item or are noted in the line item itself.The most important properties which are derived from the posting key are:The account typeThe allocation to the debits or credits sideThe possible or necessary specifications which are to be entered in the line item.
postingkey - The posting key describes the type of transaction which is entered in a line item.public void setGlaccount(@Nullable String glaccount)
Original property name from the Odata EDM: Glaccount
glaccount - This field contains the number of the G/L account to which the transaction figures are updated.public void setOperationalglaccount(@Nullable String operationalglaccount)
Original property name from the Odata EDM: Operationalglaccount
operationalglaccount - The G/L account number identifies the G/L account in a chart of accounts.public void setSpecialglcode(@Nullable String specialglcode)
Original property name from the Odata EDM: Specialglcode
For all line items in customer or vendor accounts that are updated to an alternative reconciliation account, the special G/L indicator determines which account is to be selected.
specialglcode - Indicator that identifies a special G/L transactionpublic void setBusinessarea(@Nullable String businessarea)
Original property name from the Odata EDM: Businessarea
businessarea - Key that uniquely identifies a business area.public void setTaxcode(@Nullable String taxcode)
Original property name from the Odata EDM: Taxcode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
taxcode - The tax code represents a tax category which must be taken into consideration when making a tax return
to the tax authorities.public void setWithholdingtaxcode(@Nullable String withholdingtaxcode)
Original property name from the Odata EDM: Withholdingtaxcode
The tax codes are unique per country. For each tax code, the tax rate, the portion of the invoices to be taxed and further properties are stored in a table.When tax rates are changed due to a new law, new tax codes must be defined. The old codes with the old tax rates must be retained until no more open items exist which use this tax code.
withholdingtaxcode - The withholding tax code can be compared to a tax sub-category which must be taken into consideration
when reporting tax to the tax authorities.public 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 setDuecalculationbasedate(@Nullable LocalDateTime duecalculationbasedate)
Original property name from the Odata EDM: Duecalculationbasedate
For line items in G/L accounts, the item is due immediately on this date because there are no cash discount specifications.During document entry for open item accounts, the date may be defaulted. For this, a terms of payment key must have been specified in the customer's/vendor's master record for which a default value is requested in the document.The proposed date can be overwritten.If the cash discount rates (and days) have not been entered, the baseline date for payment is the same as the due date.
duecalculationbasedate - Date to which the periods for the cash discount deadline and the due date for net payment refer. This
is the case for line items in open item accounts.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 rate applied to the shortest payment period.public void setCashdiscount2percent(@Nullable BigDecimal cashdiscount2percent)
Original property name from the Odata EDM: Cashdiscount2percent
cashdiscount2percent - Cash discount percentage rate applied to the second payment period.public void setPurchasingdocument(@Nullable String purchasingdocument)
Original property name from the Odata EDM: Purchasingdocument
purchasingdocument - Alphanumeric key uniquely identifying the document.public void setPurchasingdocumentitem(@Nullable String purchasingdocumentitem)
Original property name from the Odata EDM: Purchasingdocumentitem
purchasingdocumentitem - Specifies the number that uniquely identifies an item in .public void setVatregistration(@Nullable String vatregistration)
Original property name from the Odata EDM: Vatregistration
The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.
vatregistration - VAT registration number (VAT reg.no.) of the customer, vendor or your company code.public 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.AustriaFor foreign bank transfers, the explanatory text for the OeNB is determined using this indicator on the bank transfer form or in the data medium exchange.BelgiumThe content of the first text field for this indicator is used in the data medium exchange.NetherlandsThe usage of the state central bank indicator, the document type and the texts for this indicator is explained in the detailed documentation for the individual fields.JapanFor foreign bank transfers, the reason for payment is determined by this indicator when reporting to the Japanese ministry of finance.We recommend entering a "J" as the first letter so that you can better distinguish this report from other non-Japanese reports.
statecentralbankpaymentreason - Germanypublic void setSupplyingcountry(@Nullable String supplyingcountry)
Original property name from the Odata EDM: Supplyingcountry
This field contains the country key of the purchasing country in the case of imports or transits (field U4 or field V5 on the data medium) or that of the country of investment in the case of capital transactions (field W7).Together with the German State Central Bank indicator, this specification is needed for creating reports in line with German foreign trade regulations.
supplyingcountry - Germanypublic 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 - Number of the routing or reference operation set used in the order.public void setAssignmentreference(@Nullable String assignmentreference)
Original property name from the Odata EDM: Assignmentreference
The program can display the account line items sorted according to the content of this field.You can either enter the field contents manually, or have the system define them automatically in the master record via the sort key field.You define the rules for the layout of the assignment number field in the Implementation Guide (IMG) under Determine Standard Sorting for Line Items.
assignmentreference - The assignment number is an additional information reference field in the line item.public void setAssetcontract(@Nullable String assetcontract)
Original property name from the Odata EDM: Assetcontract
assetcontract - Unique number that identifies a contract (loan, lease-out, and so on). The contract number can be
assigned externally by the user or internally by the system.public void setFollowondocumenttype(@Nullable String followondocumenttype)
Original property name from the Odata EDM: Followondocumenttype
followondocumenttype - Follow-On Document Typepublic void setCostcenter(@Nullable String costcenter)
Original property name from the Odata EDM: Costcenter
costcenter - A key that uniquely identifies a cost center.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 - The number that uniquely identifies the item in the sales document.public void setProfitcenter(@Nullable String profitcenter)
Original property name from the Odata EDM: Profitcenter
profitcenter - Key which together with the controlling area uniquely identifies a profit center.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 setReference3idbybusinesspartner(@Nullable String reference3idbybusinesspartner)
Original property name from the Odata EDM: Reference3idbybusinesspartner
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.BrazilFor customers, the number of a previously issued boleto is defined here.FinlandIf a forward exchange transaction for hedging has been completed for a foreign currency invoice, you can define the contract number here. If the bank requires a prefix for the contract number, enter this number here. You also have to specify the appropriate house bank ID. This contract number is then copied in the corresponding fields with format LUM2 and ULMP when you create the payment medium with report RFFOFI_U.JapanIf you have concluded a forward exchange transaction for hedging for an invoice in foreign currency you can define the contract number here (no more than 16 characters).For a forward exchange transaction for hedging, you must also enter the relevant house bank ID and the instruction number for the saved exchange rate in instruction 3.The contract number is transferred to the corresponding field in the ZENGINKYO format (accounting information) when the payment medium is generated using report RFFOJP_L.If an invoice in foreign currency is to be split into more than one but no more than three accounting line items, you can enter a "*" here. If a "*" is entered, the system displays a window for additional accounting information for Japan in which you can add necessary information. You can only maintain additional information when changing the document.ProceedThailandIdentification number for the withholding tax certificate. This is either derived from the payment document number and the corresponding line number or can be entered manually.
reference3idbybusinesspartner - In this field, you can enter customer/vendor details for the accounting transaction.public 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 instructionInstr. 1 Z1 form in Z1 form06 1 Advice note to beneficiary's bank07 1 Advice note to beneficiary's bank09 2 Advice to beneficiary by telephone10 3 Advice to beneficiary by fax/telex04 4 Payment against legitimation- The NetherlandsInstruction key 1 is used in the Netherlands as the payment instruction code for foreign bank transfers by data medium exchange.- FranceIn France, this key is used for data medium exchange abroad (field 9 in record 'Enregistrements complementaires')- BrazilIn Brazil, instruction key 1 is used for the 'Codigo de Ocorrência' statement.- DenmarkIn Denmark, this key is used in the format PostGiro Udland.- FinlandInstruction key 1 is used in the ULMP and LUM2 formats. The payment method can be determined via the instruction key.- SWIFT MT formatsFor the SWIFT MT formats, instruction key 1 is converted into a code that is entered in field 72.- JapanInstruction 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.- NorwayIn 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).AustriaIn Austria, instruction key 2 is used for foreign transfers (DME) for the transfer type rapid payment.NetherlandsIn the Netherlands, instruction key 2 is used as a code for payment instructions when making payments abroad by DME.FranceIn France, instruction key 2 is used for data medium exchange abroad (field 9 in record 'Enregistrements complementaires')BrazilIn Brazil, this key can be used as a further specification criteria for instruction key 1 ('Codigo de Ocorrência').SWIFT MT formatsFor the SWIFT MT formats, instruction key 2 is converted into a code that is entered in field 72.JapanInstruction 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.NetherlandsIn the Netherlands, instruction key 3 is used for foreign bank transfers by DME as a code for the payment instructions.BrazilIn Brazil, instruction key 3 can be used as an additional selection criteria for instruction key 1 ('Codigo de Ocorrência').SWIFT MT formatsFor the SWIFT MT formats, instruction key 3 is converted into a code that is entered in field 72.JapanInstruction 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).NetherlandsIn the Netherlands, key 4 is used as a code for the payment instructions when making transfers abroad by DME.SWIFT MT formatsIn the case of SWIFT MT formats instruction key 4 is converted into a code that is entered in field 72.
dataexchangeinstruction4 - Germanypublic void setAddressandbankissetmanually(@Nullable Boolean addressandbankissetmanually)
Original property name from the Odata EDM: Addressandbankissetmanually
Address data is a necessary part of line items in one-time accounts. When posting to other customers or vendors, address data is then entered if the automatic payment transactions are to take place via an alternative customer/vendor, an alternative address or an alternative bank.
addressandbankissetmanually - Indicator that address data is to be or has been entered in the line item.public void setBusinessplace(@Nullable String businessplace)
Original property name from the Odata EDM: Businessplace
businessplace - Specifies the business place.public void setPartnerprofitcenter(@Nullable String partnerprofitcenter)
Original property name from the Odata EDM: Partnerprofitcenter
For a profit center that sends a good or service, the receiver profit center is identified as the partner profit center. For the receiver, the sender is the partner profit center.
partnerprofitcenter - The partner profit center is used to identify exchanges of goods and services between profit centers.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 DraftThis is the first stage of a grant. It is a working copy that can be modified as many times as needed.ProposalWhen the initial draft becomes a formal and complete document, it becomes a proposal.ApplicationWhen a proposal is routed to the sponsor for approval, it becomes an application. This application might contain changes in the budget or other adjustments.AwardIf the sponsor approves an application, an award is created. This is the real operative stage of a grant. The creation and consumption of the grant's budget occurs at this stage. This stage also represents the binding contract between the sponsor and the grantee.ClosingWhen an award is expiring, a phase of closing is established. Only restricted operations can be performed in this stage.ClosedThis stage defines an expired and closed grant. No further operations are allowed except archiving.
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
Use for Cost of Sales AccountingThe functional area is required to create a profit and loss statement in Financial Accounting using cost of sales accounting. The following are examples of structure criteria:ManufacturingAdministrationSalesResearch & DevelopmentUse for GovernmentThe functional area is needed for Funds Management to meet legal requirements for reporting with functional aspects. You can use the functional area to represent the global targets and goals (such as public safety or city development), in particular the expenses of your organization.Use in Cost of Sales AccountingSee the documentation on Filling the Functional Area Field.For more information about cost of sales accounting and functional areas, see the SAP Library under Financials -> Financial Accounting -> General Ledger Accounting -> Cost of Sales AccountingUse in GovernmentFor more information on functional areas, see the Implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
functionalarea - Structure criterion for an enterprise or government based on functional aspects.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 setPaymentrequest(@Nullable String paymentrequest)
Original property name from the Odata EDM: Paymentrequest
paymentrequest - The key number is a unique identification for a payment request. The key number for the payment
request is allocated internally.public void setPaymentrequestamountinpaytcrcy(@Nullable BigDecimal paymentrequestamountinpaytcrcy)
Original property name from the Odata EDM: Paymentrequestamountinpaytcrcy
paymentrequestamountinpaytcrcy - Document item amount in the local currency for the company_code.public void setPaymentrequestorigin(@Nullable String paymentrequestorigin)
Original property name from the Odata EDM: Paymentrequestorigin
R/3 components such as Treasury Management (TR-TM)Loans Administration (TR-LO)
paymentrequestorigin - Uniquely identifies the origin of a payment request.public void setCurrentprocessor(@Nullable String currentprocessor)
Original property name from the Odata EDM: Currentprocessor
currentprocessor - Processorpublic void setEarmarkedfundsdocument(@Nullable String earmarkedfundsdocument)
Original property name from the Odata EDM: Earmarkedfundsdocument
earmarkedfundsdocument - Number uniquely identifying a document.public void setTaxid2(@Nullable String taxid2)
Original property name from the Odata EDM: Taxid2
Enter the appropriate tax number:Country Tax NumberArgentina NIP number or CM numberBelgium VAT numberBrazil CPF numberBulgaria Legal persons: tax numberNatural persons: personal IDCroatia OIB number Czech Republic ICO numberFrance SIREN numberGreece AFM numberIndia TINItaly VAT numberKazakhstan BC (Beneficiary Code)Netherlands BSN numberRussia OKPO codeSlovakia ICO numberSouth Korea VAT registration numberSweden Organization registration numberSwitzerland VAT numberTaiwan, China Tax registration numberUkraine Legal persons: USREOU numberNatural persons: SRNP numberTurkey Tax numberUnited Kingdom NI numberUnited States Employer identification numberVenezuela NIT number
taxid2 - Specifies the tax number.public void setPaymentrunitemmessagenumber(@Nullable String paymentrunitemmessagenumber)
Original property name from the Odata EDM: Paymentrunitemmessagenumber
paymentrunitemmessagenumber - Marking for an exception which was stated for the indicated item. An explanatory long text which is
printed in the key of the payment list or payment proposal list belongs to every indicator.public void setPaymentblockingreason(@Nullable String paymentblockingreason)
Original property name from the Odata EDM: Paymentblockingreason
The following payment blocks exist:Manual payment blockIf you manually select a payment block from the list field to block an invoice for payment, the payment block field in the header of the invoice document is marked with the appropriate indicator.Blocked due to differencesIf invoices are to be blocked automatically due to differences in the invoice items, the system enters the payment block R in the vendor line of the Accounting document. The field in the header of the invoice document remains empty.Random payment blockInvoices that do not show any other blocking reason, can be blocked in accordance with the random principle. In Customizing for the Logistics invoice verification, you can set the probability for the block. The indicator for the logistical payment block is entered in the header of the invoice document.If you have set a manual payment block, and an invoice is blocked automatically due to differences in the invoice items, the system enters the manual payment block in the vendor line of the Accounting document.
paymentblockingreason - Specifies why a document is blocked for payment.public void setPaymentrundate(@Nullable LocalDateTime paymentrundate)
Original property name from the Odata EDM: Paymentrundate
paymentrundate - The run date is used for identifying the parameters. It is the date on which the program is to be
carried out as planned. However, a program run at an earlier or later date is also possible.public void setPaymentrunid(@Nullable String paymentrunid)
Original property name from the Odata EDM: Paymentrunid
paymentrunid - You can use the additional identification to distinguish between several runs with the same
reconciliation key date. You can freely define the identification.public void setPaymentdocument(@Nullable String paymentdocument)
Original property name from the Odata EDM: Paymentdocument
paymentdocument - Document number of the document with which the payment was posted.public void setPaymentorder(@Nullable String paymentorder)
Original property name from the Odata EDM: Paymentorder
Payment orders are generated by the payment program in automatic payment transactions when a payment method is selected which is marked accordingly. Here, the payment program does not post the payment document but just generates a payment order.When the bank shows on the account statement that the payment order has been carried out, the payment is posted. The open items paid can be selected using the number of the payment order.
paymentorder - Number under which a payment order was transmitted to a house bank.public void setProposalrundate(@Nullable LocalDateTime proposalrundate)
Original property name from the Odata EDM: Proposalrundate
proposalrundate - This field is for information purposes only. It displays the date of the proposal run in the payment
program that created the item.public void setProposalrunnumber(@Nullable String proposalrunnumber)
Original property name from the Odata EDM: Proposalrunnumber
proposalrunnumber - This field is for information only. It identifies the payment proposal in the payment program from
which the item was copied.public void setPayingcompanycode(@Nullable String payingcompanycode)
Original property name from the Odata EDM: Payingcompanycode
Postings to the bank accounts or the bank sub-accounts are made in the company code specified here during automatic payment transactions.
payingcompanycode - In this field you find the company code which processes the payment transactions (possibly for other
company codes too).public void setSendingcompanycode(@Nullable String sendingcompanycode)
Original property name from the Odata EDM: Sendingcompanycode
When making cross-company code payments, you can specify the sending company code as well as the paying company code for each company code. If the sending company code is different from the paying company code, the system notes the sending company code in the payment transfer medium or payment advice. This note is information for the business partner.Furthermore, the sending company code affects how the system groups items from different company codes into one payment. Items are only grouped into one payment for company codes with the same paying company code and the same sending company code.If the sending company code is not specified, the system automatically regards the paying company code as the sending company code.Specify the sending company code if you want to pay using a cross-company code transaction but do not want to pay the items of all participating company codes together.Example 1:Company code 0001 pays its own items and the items of company codes 0002 and 0003. All items are grouped into one payment.Company code Paying company code Sending company code0001 0001 00010002 0001 00010003 0001 0001Example 2:Company code 0001 pays its own items and the items of company codes 0002 and 0003. However, a separate payment is created for each company code.Company code Paying company code Sending company code0001 0001 00010002 0001 00020003 0001 0003
sendingcompanycode - The sending company code is the company code that is known to the business partner.public void setPayeeadditionalname(@Nullable String payeeadditionalname)
Original property name from the Odata EDM: Payeeadditionalname
payeeadditionalname - Name of the payeepublic void setPayeepostalcode(@Nullable String payeepostalcode)
Original property name from the Odata EDM: Payeepostalcode
payeepostalcode - Postal Code of the Payeepublic void setPayeecityname(@Nullable String payeecityname)
Original property name from the Odata EDM: Payeecityname
payeecityname - City of the payeepublic void setPayeecountry(@Nullable String payeecountry)
Original property name from the Odata EDM: Payeecountry
payeecountry - Country key for the country in which the payee's business is located.public void setPayeeregion(@Nullable String payeeregion)
Original property name from the Odata EDM: Payeeregion
%EXAMPLE&Meaning of the regional code in ...USA StateItaly ProvinceCanada ProvinceGreat Britain County
payeeregion - In some countries, the regional code constitutes part of the address. Its meaning is country-specific.public void setPayeelanguage(@Nullable String payeelanguage)
Original property name from the Odata EDM: Payeelanguage
payeelanguage - Language key of the payeepublic void setName(@Nullable String name)
Original property name from the Odata EDM: Name
name - Name 1 of the customer/vendor address.public void setPayeebankcountry(@Nullable String payeebankcountry)
Original property name from the Odata EDM: Payeebankcountry
payeebankcountry - The country key specifies the country in which the bank of the payee has its headquarters.public void setPayeebank(@Nullable String payeebank)
Original property name from the Odata EDM: Payeebank
payeebank - Key under which the address of the bank of the payment recipient is stored in the bank file. Depending
on the the bank country, the key can be either the bank number or the bank account number, or some
other kind of key assigned internally or externally.public void setPayeebanknumber(@Nullable String payeebanknumber)
Original property name from the Odata EDM: Payeebanknumber
payeebanknumber - Bank Number of the Payee's Bankpublic void setPayeebankaccount(@Nullable String payeebankaccount)
Original property name from the Odata EDM: Payeebankaccount
payeebankaccount - Bank account number of the payeepublic void setPayeebankcontrolkey(@Nullable String payeebankcontrolkey)
Original property name from the Odata EDM: Payeebankcontrolkey
payeebankcontrolkey - Bank Control Key of the Payee's Bankpublic void setBankdetailreference(@Nullable String bankdetailreference)
Original property name from the Odata EDM: Bankdetailreference
In some countries, in order to be able to use certain payment transactions, extra specifications must be made for the customer/vendor's bank details (bank number, bank account number, name of the account holder). These additional specifications are defined here.If additional data for the bank details is needed for payment transactions in your country (see the following examples), enter the reference information here.If the bank requires the collection authorization reference number for bank collection in Norway or Great Britain, you specify that number here.When making payments to a building society account in Great Britain, you must specify which number the payee has at the building society. You make this entry in the reference field, and the bank key and account number fields are used for the bank details of the building society.In Great Britain, if you enter a building society account number here, its name must already be defined in the system.
bankdetailreference - Additional specification for the customer/vendor bank details.public void setPayeebankidentifiercode(@Nullable String payeebankidentifiercode)
Original property name from the Odata EDM: Payeebankidentifiercode
SWIFT stands for Society for Worldwide Interbank Financial Telecommunication.BIC stands for Bank Identifier Code.This globally unique code can be used in international payment transactions to identify the bank without the need to specify an address or bank number. Specification of the SWIFT code/BIC is mainly relevant for automatic payment transactions.
payeebankidentifiercode - Uniquely identifies a bank throughout the world.public void setPayeeiban(@Nullable String payeeiban)
Original property name from the Odata EDM: Payeeiban
Commitee for Banking Standards) to represent bank details. AN IBANcontains a maximum of 34 alphanumerical symbols and is made up acombination of hte following elements:The bank's country key (ISO code)A two-figure check digitCountry-specific account number (in Germany, for example, this consistsof the bank number and the account number, while in France it consistsof the bank number, the account number and the bank control key).The IBAN simplifies international payments and also provides benefitsfor domestic payments in some countries. In some countries, it alsoprovides advantages with respect to value dates and fees.The IBAN can be stored in parallel with the bank details, but does notreplace them. It is stored under the business partner's master data, and can be used when settings up the payment medium.As only the bank managing the account can generate the IBAN, whichcorresponds to one account number, the SAP system creates a proposalonly. You can either confirm or change this. If the system was not ableto create a proposal, enter the IBAN yourself.In Belgium, an IBAN might look like this:Electronic form:BE62510007547061Printed form, as it appears on the invoice:IBAN BE62 5100 0754 7061
payeeiban - A standard number standardized in accordance with the ECBS (Europeanpublic void setBankaccountholdername(@Nullable String bankaccountholdername)
Original property name from the Odata EDM: Bankaccountholdername
bankaccountholdername - Here you can enter another name that the payment program can use if the name of the account holder is
not the same as the name of the customer or vendor.public void setHousebankaccount(@Nullable String housebankaccount)
Original property name from the Odata EDM: Housebankaccount
housebankaccount - This ID together with the ID for the house bank uniquely defines a bank account.public void setHousebank(@Nullable String housebank)
Original property name from the Odata EDM: Housebank
housebank - All bank data is determined using this key.public void setBankcountry(@Nullable String bankcountry)
Original property name from the Odata EDM: Bankcountry
The country key defines the rules according to which bank data, such as the bank and account numbers, is to be validated.
bankcountry - Identifies the country in which the bank is located.public void setBank(@Nullable String bank)
Original property name from the Odata EDM: Bank
bank - Bank key of our bankpublic void setBanknumber(@Nullable String banknumber)
Original property name from the Odata EDM: Banknumber
banknumber - Bank number of our bankpublic void setBankaccount(@Nullable String bankaccount)
Original property name from the Odata EDM: Bankaccount
bankaccount - Our account number at the bankpublic void setBankcontrolkey(@Nullable String bankcontrolkey)
Original property name from the Odata EDM: Bankcontrolkey
bankcontrolkey - Bank control key at our bankpublic void setGlaccountforbankaccount(@Nullable String glaccountforbankaccount)
Original property name from the Odata EDM: Glaccountforbankaccount
glaccountforbankaccount - G/L Account Number for Our Bank Account / Bank Subaccountpublic void setSupplierpaymentmethod(@Nullable String supplierpaymentmethod)
Original property name from the Odata EDM: Supplierpaymentmethod
Payment methods are entered in the master records of customers and vendors in order to specify how payments are made. If an open item is to be paid using a specific payment method, enter it in the open item. The terms which have been defined for the payment method must be satisfied for the payment.Payment methods are to be defined in the Financial Accounting configuration menu, where the following steps are to be carried out:First of all, make all specifications that are required for a country-specific payment method.Then define per company code the terms under which a payment method can be used.All payment methods are displayed in the customer or vendor master record in the screen for selecting the payment method. Here you select the required payment method by marking it; the system transfers the payment methods to the customer/vendor master record.
supplierpaymentmethod - The payment method determines how payments are to be made, e.g. by check, bank transfer or bill of
exchange.public 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 setDataexchangeinstructionkey(@Nullable String dataexchangeinstructionkey)
Original property name from the Odata EDM: Dataexchangeinstructionkey
Selecting the instruction keyIf data medium exchange is used (as well as in special cases when using document-based payment orders) the instruction key must be maintained in the customer/vendor master record, or in the system configuration for data medium exchange data for the house bank. The following holds regarding the instruction key:If the instruction key is maintained in the master record, then this instruction key is used.If no instruction key exists in the vendor master record, then the default instruction key defined for the house bank is used.Consequently, it is not necessary to provide all business partners with an instruction key; only the exceptions need to be maintained.1If it is necessary to specify an instruction key for a business partner's house bank that differs from the instruction key defined in the master record, this can be done when editing the payment proposal.2The instruction key must be entered in the document for one-time accounts.3The four instruction key fields belonging to the instruction key can be overridden by entering instruction keys in the document (the "Additional Data" screen in the customer or vendor line).
dataexchangeinstructionkey - For automatic payment transactions, this field (along with the house bank country and the payment
method determined by the payment program) controls which statements are given to the participating
banks when carrying out the payment order. This field is used in countries such as Germany, Austria,
the Netherlands, Spain, Norway, Finland, and Japan as well as for the internnational SWIFT format,
MT100.public void setPaymentdocumentpostingdate(@Nullable LocalDateTime paymentdocumentpostingdate)
Original property name from the Odata EDM: Paymentdocumentpostingdate
paymentdocumentpostingdate - Posting date of the payment documentpublic 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 setPaiditemduedate(@Nullable LocalDateTime paiditemduedate)
Original property name from the Odata EDM: Paiditemduedate
paiditemduedate - Due date of the paid itemspublic void setBillofexchangeduedate(@Nullable LocalDateTime billofexchangeduedate)
Original property name from the Odata EDM: Billofexchangeduedate
billofexchangeduedate - Due date, that is entered on the bill of exchange and is stored in the bill of exchange posting.public void setBillofexchangeissuedate(@Nullable LocalDateTime billofexchangeissuedate)
Original property name from the Odata EDM: Billofexchangeissuedate
billofexchangeissuedate - Date of issue as was entered on the bill of exchange form.public void setAccountingclerk(@Nullable String accountingclerk)
Original property name from the Odata EDM: Accountingclerk
The name of the accounting clerk defined by this identification code can be used in the payment program for correspondence and reporting (for example, open item lists).
accountingclerk - Identification code for the accounting clerk.public void setAccountbyshipper(@Nullable String accountbyshipper)
Original property name from the Odata EDM: Accountbyshipper
accountbyshipper - This field contains the account number your company is listed under at the customer or vendor.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 setSepamandateuuid(@Nullable byte[] sepamandateuuid)
Original property name from the Odata EDM: Sepamandateuuid
sepamandateuuid - SEPA Mandate: GUID of Mandatepublic 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 MandatesYou 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 PayersIf 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.ExampleYou 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 accountsContract account Mandate (in Contract Acct) MeaningC1 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 mandateMandate Contract Account (in Mandate) MeaningM1 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 setInvoicereference(@Nullable String invoicereference)
Original property name from the Odata EDM: Invoicereference
Otherwise it displays the document number.You can use this field for sorting and grouping the items concerning the original invoice item and all items referenced to it.
invoicereference - Displays the number of the partner document, when line items are related to another line item.public void setInvoicereferencefiscalyear(@Nullable String invoicereferencefiscalyear)
Original property name from the Odata EDM: Invoicereferencefiscalyear
Otherwise it displays the fiscal year of the document number.
invoicereferencefiscalyear - Displays the fiscal year of the related document, when line items are related to another line item.public void setInvoiceitemreference(@Nullable String invoiceitemreference)
Original property name from the Odata EDM: Invoiceitemreference
Otherwise it displays the document line item.
invoiceitemreference - Displays the document line item of the partner document, when line items are related to another
document line item.protected String getEntityCollection()
VdmEntitygetEntityCollection in class VdmEntity<PaymentReleaseListItem>@Nonnull protected Map<String,Object> getKey()
getKey in class VdmObject<PaymentReleaseListItem>@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields in class VdmObject<PaymentReleaseListItem>protected void fromMap(Map<String,Object> inputValues)
fromMap in class VdmObject<PaymentReleaseListItem>@Nonnull public static <T> PaymentReleaseListItemField<T> field(@Nonnull String fieldName, @Nonnull Class<T> fieldType)
T - The type of the extension field when performing value comparisons.fieldName - The name of the extension field as returned by the OData service.fieldType - The Java type to use for the extension field when performing value comparisons.@Nonnull public static <T,DomainT> PaymentReleaseListItemField<T> field(@Nonnull String fieldName, @Nonnull TypeConverter<T,DomainT> typeConverter)
T - The type of the extension field when performing value comparisons.DomainT - The type of the extension field as returned by the OData service.typeConverter - A TypeConverterfieldName - The name of the extension field as returned by the OData service.@Nullable public HttpDestinationProperties getDestinationForFetch()
VdmEntitygetDestinationForFetch in class VdmEntity<PaymentReleaseListItem>protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntityNote: Use with caution, as this can easily break the fetch call on this entity. See the interface of the corresponding service for the default service path.
setServicePathForFetch in class VdmEntity<PaymentReleaseListItem>public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntityNote: Use with caution, as this can easily break the fetch calls on this entity. See the interface of the corresponding service for the default service path.
attachToService in class VdmEntity<PaymentReleaseListItem>servicePath - Optional parameter. New service path to apply to this entity and any associated entities that were
previously fetched. If a null value is provided and the service path has never been set, then the
service path will be set to the default defined in the corresponding service interface.destination - New destination to apply to this entity and any associated entities that were previously fetched.protected String getDefaultServicePath()
VdmEntitygetDefaultServicePath in class VdmEntity<PaymentReleaseListItem>protocol://hostname:port and the OData resource name (entity set, $metadata, etc.)@Nonnull public static PaymentReleaseListItem.PaymentReleaseListItemBuilder builder()
@Nullable public UUID getPaymentreleaselistitemuuid()
Original property name from the Odata EDM: Paymentreleaselistitemuuid
@Nullable public String getPaymentreleaselist()
Original property name from the Odata EDM: Paymentreleaselist
@Nullable public String getPaymentstatus()
Original property name from the Odata EDM: Paymentstatus
@Nullable public String getPaytrellistitemapprovallevel()
Original property name from the Odata EDM: Paytrellistitemapprovallevel
Items that are pending approval are always assigned an approval level.If an item is assigned to a payment release list, but has not been approved at any level, the field displays the initial value (0).In the IMG activity Define Approval Levels, you can define:Approval levelsYou can define as many approval levels as you require.A description of each approval levelFinal approval levelsWhen you or another approver approve an item at a final approval level, the item status changes to Released for Payment.The actions that approvers can perform at each approval levelIn the IMG activity Disable Clearing and Reversal for Approval Levels, you can define that approvers are not authorized to clear or reverse documents at certain approval levels.In the IMG activity Disable Document Changes for Approval Levels, you can choose the document fields that approvers are not authorized to change at certain approval levels.
@Nullable public String getCreatedbyuser()
Original property name from the Odata EDM: Createdbyuser
@Nullable public String getLastchangedbyuser()
Original property name from the Odata EDM: Lastchangedbyuser
@Nullable public String getPaymentreleaselistapplication()
Original property name from the Odata EDM: Paymentreleaselistapplication
@Nullable public String getCompanycode()
Original property name from the Odata EDM: Companycode
@Nullable public String getAccountingdocument()
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.
@Nullable public String getFiscalyear()
Original property name from the Odata EDM: Fiscalyear
@Nullable public String getAccountingdocumentitem()
Original property name from the Odata EDM: Accountingdocumentitem
@Nullable public String getSupplierfullname()
Original property name from the Odata EDM: Supplierfullname
@Nullable public String getSupplier()
Original property name from the Odata EDM: Supplier
@Nullable public String getCustomer()
Original property name from the Odata EDM: Customer
@Nullable public String getBranchaccount()
Original property name from the Odata EDM: Branchaccount
@Nullable public String getPayerpayee()
Original property name from the Odata EDM: Payerpayee
If payment for the document item is not to be made using the business partner posted to, you can enter the required payer/payee number here. You can only use the account numbers stored in the master record for the business partner posted to.You can specify the permitted account numbers in the master record, independently of the company code or on a company-code-specific basis.Enter the required account number if payment is to be made using a different business partner.
@Nullable public String getPartnercompany()
Original property name from the Odata EDM: Partnercompany
@Nullable public String getDebitcreditcode()
Original property name from the Odata EDM: Debitcreditcode
@Nullable public String getTransactioncurrency()
Original property name from the Odata EDM: Transactioncurrency
@Nullable public BigDecimal getAmountintransactioncurrency()
Original property name from the Odata EDM: Amountintransactioncurrency
During document entry, enter the amount manually. In the last line item, you can enter a "*" - the amount of the final line item is then the balance of all the line items previously entered.Amounts you enter may be changed automatically by the system if the following postings are made:Tax adjustmentsCash discount adjustments during net postings.
@Nullable public BigDecimal getCashdiscountbaseamount()
Original property name from the Odata EDM: Cashdiscountbaseamount
During document entry, the amount qualifying for cash discount can be determined manually or automatically. The amount is determined automatically if no entry is made or a '*' is entered.To determine this amount automatically, the system takes into account the offsetting items relevant to cash discount for the invoice item and the rules assigned for each company code for processing cash discount and taxes.
@Nullable public BigDecimal getCashdiscountamtintransaccrcy()
Original property name from the Odata EDM: Cashdiscountamtintransaccrcy
For open items, this amount is the cash discount agreed upon (assuming a fixed amount was agreed upon and not a percentage rate).For cleared items, the amount shows the cash discount that was actually taken.During document entry, you only need enter the cash discount amount if this amount is fixed rather than a percentage rate. This amount is no longer changed by the system.
@Nullable public BigDecimal getWhldgtaxamtintransaccrcy()
Original property name from the Odata EDM: Whldgtaxamtintransaccrcy
The amount is continuously calculated by the system on the basis of the withholding tax base amount and the tax percentage rate.
@Nullable public String getBalancetransactioncurrency()
Original property name from the Odata EDM: Balancetransactioncurrency
An exception can occur with clearing entries in a third currency. The item currency for a clearing entry is always identical to the item currency of the entry to be cleared and can therefore be different from both the document currency and the local currency.You post an invoice in USD in a company code with EUR as its local currency. Payment is made in CHF. The clearing entry in the payment document has the item currency key USD and is therefore different from the document currency CHF and the local currency EUR.
@Nullable public BigDecimal getAmountinbalancetransaccrcy()
Original property name from the Odata EDM: Amountinbalancetransaccrcy
@Nullable public BigDecimal getCashdiscountamount()
Original property name from the Odata EDM: Cashdiscountamount
@Nullable public String getAccountingdocumenttype()
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.
@Nullable public LocalDateTime getPostingdate()
Original property name from the Odata EDM: Postingdate
The fiscal year and the period for which an update of the accounts specified in the document or cost elements is made, are derived from the posting date.When entering documents, the system checks whether the posting date entered is allowed by means of the posting period permitted.The posting date can differ from both the entry date (day of entry into the system) and the document date (day of creation of the original document).
@Nullable public LocalDateTime getDocumentdate()
Original property name from the Odata EDM: Documentdate
@Nullable public String getFinancialaccounttype()
Original property name from the Odata EDM: Financialaccounttype
@Nullable public String getPostingkey()
Original property name from the Odata EDM: Postingkey
For every posting key, you specify properties which control the entry of the line item or are noted in the line item itself.The most important properties which are derived from the posting key are:The account typeThe allocation to the debits or credits sideThe possible or necessary specifications which are to be entered in the line item.
@Nullable public String getGlaccount()
Original property name from the Odata EDM: Glaccount
@Nullable public String getOperationalglaccount()
Original property name from the Odata EDM: Operationalglaccount
@Nullable public String getSpecialglcode()
Original property name from the Odata EDM: Specialglcode
For all line items in customer or vendor accounts that are updated to an alternative reconciliation account, the special G/L indicator determines which account is to be selected.
@Nullable public String getBusinessarea()
Original property name from the Odata EDM: Businessarea
@Nullable public String getTaxcode()
Original property name from the Odata EDM: Taxcode
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
@Nullable public String getWithholdingtaxcode()
Original property name from the Odata EDM: Withholdingtaxcode
The tax codes are unique per country. For each tax code, the tax rate, the portion of the invoices to be taxed and further properties are stored in a table.When tax rates are changed due to a new law, new tax codes must be defined. The old codes with the old tax rates must be retained until no more open items exist which use this tax code.
@Nullable public String getDocumentitemtext()
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.
@Nullable public LocalDateTime getDuecalculationbasedate()
Original property name from the Odata EDM: Duecalculationbasedate
For line items in G/L accounts, the item is due immediately on this date because there are no cash discount specifications.During document entry for open item accounts, the date may be defaulted. For this, a terms of payment key must have been specified in the customer's/vendor's master record for which a default value is requested in the document.The proposed date can be overwritten.If the cash discount rates (and days) have not been entered, the baseline date for payment is the same as the due date.
@Nullable public BigDecimal getCashdiscount1days()
Original property name from the Odata EDM: Cashdiscount1days
@Nullable public BigDecimal getCashdiscount2days()
Original property name from the Odata EDM: Cashdiscount2days
@Nullable public BigDecimal getNetpaymentdays()
Original property name from the Odata EDM: Netpaymentdays
@Nullable public BigDecimal getCashdiscount1percent()
Original property name from the Odata EDM: Cashdiscount1percent
@Nullable public BigDecimal getCashdiscount2percent()
Original property name from the Odata EDM: Cashdiscount2percent
@Nullable public String getPurchasingdocument()
Original property name from the Odata EDM: Purchasingdocument
@Nullable public String getPurchasingdocumentitem()
Original property name from the Odata EDM: Purchasingdocumentitem
@Nullable public String getVatregistration()
Original property name from the Odata EDM: Vatregistration
The VAT registration number is used within the EU for tax-exempt deliveries for the "EC sales list". The check rules are defined for each EU country and cannot be changed.
@Nullable public String getStatecentralbankpaymentreason()
Original property name from the Odata EDM: Statecentralbankpaymentreason
In foreign payment transactions, information concerning the reason for payment is needed for the report according to German foreign trade regulations (AWV).The possible reasons for payment are defined within configuration for SCB indicators. This includes certain indicators which are the key to the reasons for payment, and an explanatory text.The reasons for payment appear on the reporting form and/or in the corresponding data medium exchange.AustriaFor foreign bank transfers, the explanatory text for the OeNB is determined using this indicator on the bank transfer form or in the data medium exchange.BelgiumThe content of the first text field for this indicator is used in the data medium exchange.NetherlandsThe usage of the state central bank indicator, the document type and the texts for this indicator is explained in the detailed documentation for the individual fields.JapanFor foreign bank transfers, the reason for payment is determined by this indicator when reporting to the Japanese ministry of finance.We recommend entering a "J" as the first letter so that you can better distinguish this report from other non-Japanese reports.
@Nullable public String getSupplyingcountry()
Original property name from the Odata EDM: Supplyingcountry
This field contains the country key of the purchasing country in the case of imports or transits (field U4 or field V5 on the data medium) or that of the country of investment in the case of capital transactions (field W7).Together with the German State Central Bank indicator, this specification is needed for creating reports in line with German foreign trade regulations.
@Nullable public String getProjectnetwork()
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.
@Nullable public String getOrderinternalbillofoperations()
Original property name from the Odata EDM: Orderinternalbillofoperations
@Nullable public String getAssignmentreference()
Original property name from the Odata EDM: Assignmentreference
The program can display the account line items sorted according to the content of this field.You can either enter the field contents manually, or have the system define them automatically in the master record via the sort key field.You define the rules for the layout of the assignment number field in the Implementation Guide (IMG) under Determine Standard Sorting for Line Items.
@Nullable public String getAssetcontract()
Original property name from the Odata EDM: Assetcontract
@Nullable public String getFollowondocumenttype()
Original property name from the Odata EDM: Followondocumenttype
@Nullable public String getCostcenter()
Original property name from the Odata EDM: Costcenter
@Nullable public String getSalesdocument()
Original property name from the Odata EDM: Salesdocument
@Nullable public String getSalesdocumentitem()
Original property name from the Odata EDM: Salesdocumentitem
@Nullable public String getProfitcenter()
Original property name from the Odata EDM: Profitcenter
@Nullable public String getReference1idbybusinesspartner()
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.
@Nullable public String getReference2idbybusinesspartner()
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.
@Nullable public String getReference3idbybusinesspartner()
Original property name from the Odata EDM: Reference3idbybusinesspartner
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.BrazilFor customers, the number of a previously issued boleto is defined here.FinlandIf a forward exchange transaction for hedging has been completed for a foreign currency invoice, you can define the contract number here. If the bank requires a prefix for the contract number, enter this number here. You also have to specify the appropriate house bank ID. This contract number is then copied in the corresponding fields with format LUM2 and ULMP when you create the payment medium with report RFFOFI_U.JapanIf you have concluded a forward exchange transaction for hedging for an invoice in foreign currency you can define the contract number here (no more than 16 characters).For a forward exchange transaction for hedging, you must also enter the relevant house bank ID and the instruction number for the saved exchange rate in instruction 3.The contract number is transferred to the corresponding field in the ZENGINKYO format (accounting information) when the payment medium is generated using report RFFOJP_L.If an invoice in foreign currency is to be split into more than one but no more than three accounting line items, you can enter a "*" here. If a "*" is entered, the system displays a window for additional accounting information for Japan in which you can add necessary information. You can only maintain additional information when changing the document.ProceedThailandIdentification number for the withholding tax certificate. This is either derived from the payment document number and the corresponding line number or can be entered manually.
@Nullable public String getDataexchangeinstruction1()
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 instructionInstr. 1 Z1 form in Z1 form06 1 Advice note to beneficiary's bank07 1 Advice note to beneficiary's bank09 2 Advice to beneficiary by telephone10 3 Advice to beneficiary by fax/telex04 4 Payment against legitimation- The NetherlandsInstruction key 1 is used in the Netherlands as the payment instruction code for foreign bank transfers by data medium exchange.- FranceIn France, this key is used for data medium exchange abroad (field 9 in record 'Enregistrements complementaires')- BrazilIn Brazil, instruction key 1 is used for the 'Codigo de Ocorrência' statement.- DenmarkIn Denmark, this key is used in the format PostGiro Udland.- FinlandInstruction key 1 is used in the ULMP and LUM2 formats. The payment method can be determined via the instruction key.- SWIFT MT formatsFor the SWIFT MT formats, instruction key 1 is converted into a code that is entered in field 72.- JapanInstruction 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.- NorwayIn 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.
@Nullable public String getDataexchangeinstruction2()
Original property name from the Odata EDM: Dataexchangeinstruction2
Instruction key 2 is used in Germany in foreign data medium exchange (field T17).AustriaIn Austria, instruction key 2 is used for foreign transfers (DME) for the transfer type rapid payment.NetherlandsIn the Netherlands, instruction key 2 is used as a code for payment instructions when making payments abroad by DME.FranceIn France, instruction key 2 is used for data medium exchange abroad (field 9 in record 'Enregistrements complementaires')BrazilIn Brazil, this key can be used as a further specification criteria for instruction key 1 ('Codigo de Ocorrência').SWIFT MT formatsFor the SWIFT MT formats, instruction key 2 is converted into a code that is entered in field 72.JapanInstruction 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.
@Nullable public String getDataexchangeinstruction3()
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.NetherlandsIn the Netherlands, instruction key 3 is used for foreign bank transfers by DME as a code for the payment instructions.BrazilIn Brazil, instruction key 3 can be used as an additional selection criteria for instruction key 1 ('Codigo de Ocorrência').SWIFT MT formatsFor the SWIFT MT formats, instruction key 3 is converted into a code that is entered in field 72.JapanInstruction 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.
@Nullable public String getDataexchangeinstruction4()
Original property name from the Odata EDM: Dataexchangeinstruction4
Instruction key 4 is used in Germany for foreign data medium exchange (field T19).NetherlandsIn the Netherlands, key 4 is used as a code for the payment instructions when making transfers abroad by DME.SWIFT MT formatsIn the case of SWIFT MT formats instruction key 4 is converted into a code that is entered in field 72.
@Nullable public Boolean getAddressandbankissetmanually()
Original property name from the Odata EDM: Addressandbankissetmanually
Address data is a necessary part of line items in one-time accounts. When posting to other customers or vendors, address data is then entered if the automatic payment transactions are to take place via an alternative customer/vendor, an alternative address or an alternative bank.
@Nullable public String getBusinessplace()
Original property name from the Odata EDM: Businessplace
@Nullable public String getPartnerprofitcenter()
Original property name from the Odata EDM: Partnerprofitcenter
For a profit center that sends a good or service, the receiver profit center is identified as the partner profit center. For the receiver, the sender is the partner profit center.
@Nullable public String getGrantid()
Original property name from the Odata EDM: Grantid
A grant may be for any purpose and cover all or only part of the costs of the project in question. You must enter a grant type for each grant you create in Grants Management (GM).The grant as an object has a finite lifecycle, divided into stages. Each stage is represented in the GM solution by a system status. The following are the stages of a grant's lifecycle:Initial DraftThis is the first stage of a grant. It is a working copy that can be modified as many times as needed.ProposalWhen the initial draft becomes a formal and complete document, it becomes a proposal.ApplicationWhen a proposal is routed to the sponsor for approval, it becomes an application. This application might contain changes in the budget or other adjustments.AwardIf the sponsor approves an application, an award is created. This is the real operative stage of a grant. The creation and consumption of the grant's budget occurs at this stage. This stage also represents the binding contract between the sponsor and the grantee.ClosingWhen an award is expiring, a phase of closing is established. Only restricted operations can be performed in this stage.ClosedThis stage defines an expired and closed grant. No further operations are allowed except archiving.
@Nullable public String getFunctionalarea()
Original property name from the Odata EDM: Functionalarea
Use for Cost of Sales AccountingThe functional area is required to create a profit and loss statement in Financial Accounting using cost of sales accounting. The following are examples of structure criteria:ManufacturingAdministrationSalesResearch & DevelopmentUse for GovernmentThe functional area is needed for Funds Management to meet legal requirements for reporting with functional aspects. You can use the functional area to represent the global targets and goals (such as public safety or city development), in particular the expenses of your organization.Use in Cost of Sales AccountingSee the documentation on Filling the Functional Area Field.For more information about cost of sales accounting and functional areas, see the SAP Library under Financials -> Financial Accounting -> General Ledger Accounting -> Cost of Sales AccountingUse in GovernmentFor more information on functional areas, see the Implementation Guide for Funds Management Government in the section Activate Account Assignment Elements.
@Nullable public String getFund()
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.
@Nullable public String getPaymentrequest()
Original property name from the Odata EDM: Paymentrequest
@Nullable public BigDecimal getPaymentrequestamountinpaytcrcy()
Original property name from the Odata EDM: Paymentrequestamountinpaytcrcy
@Nullable public String getPaymentrequestorigin()
Original property name from the Odata EDM: Paymentrequestorigin
R/3 components such as Treasury Management (TR-TM)Loans Administration (TR-LO)
@Nullable public String getCurrentprocessor()
Original property name from the Odata EDM: Currentprocessor
@Nullable public String getEarmarkedfundsdocument()
Original property name from the Odata EDM: Earmarkedfundsdocument
@Nullable public String getTaxid2()
Original property name from the Odata EDM: Taxid2
Enter the appropriate tax number:Country Tax NumberArgentina NIP number or CM numberBelgium VAT numberBrazil CPF numberBulgaria Legal persons: tax numberNatural persons: personal IDCroatia OIB number Czech Republic ICO numberFrance SIREN numberGreece AFM numberIndia TINItaly VAT numberKazakhstan BC (Beneficiary Code)Netherlands BSN numberRussia OKPO codeSlovakia ICO numberSouth Korea VAT registration numberSweden Organization registration numberSwitzerland VAT numberTaiwan, China Tax registration numberUkraine Legal persons: USREOU numberNatural persons: SRNP numberTurkey Tax numberUnited Kingdom NI numberUnited States Employer identification numberVenezuela NIT number
@Nullable public String getPaymentrunitemmessagenumber()
Original property name from the Odata EDM: Paymentrunitemmessagenumber
@Nullable public String getPaymentblockingreason()
Original property name from the Odata EDM: Paymentblockingreason
The following payment blocks exist:Manual payment blockIf you manually select a payment block from the list field to block an invoice for payment, the payment block field in the header of the invoice document is marked with the appropriate indicator.Blocked due to differencesIf invoices are to be blocked automatically due to differences in the invoice items, the system enters the payment block R in the vendor line of the Accounting document. The field in the header of the invoice document remains empty.Random payment blockInvoices that do not show any other blocking reason, can be blocked in accordance with the random principle. In Customizing for the Logistics invoice verification, you can set the probability for the block. The indicator for the logistical payment block is entered in the header of the invoice document.If you have set a manual payment block, and an invoice is blocked automatically due to differences in the invoice items, the system enters the manual payment block in the vendor line of the Accounting document.
@Nullable public LocalDateTime getPaymentrundate()
Original property name from the Odata EDM: Paymentrundate
@Nullable public String getPaymentrunid()
Original property name from the Odata EDM: Paymentrunid
@Nullable public String getPaymentdocument()
Original property name from the Odata EDM: Paymentdocument
@Nullable public String getPaymentorder()
Original property name from the Odata EDM: Paymentorder
Payment orders are generated by the payment program in automatic payment transactions when a payment method is selected which is marked accordingly. Here, the payment program does not post the payment document but just generates a payment order.When the bank shows on the account statement that the payment order has been carried out, the payment is posted. The open items paid can be selected using the number of the payment order.
@Nullable public LocalDateTime getProposalrundate()
Original property name from the Odata EDM: Proposalrundate
@Nullable public String getProposalrunnumber()
Original property name from the Odata EDM: Proposalrunnumber
@Nullable public String getPayingcompanycode()
Original property name from the Odata EDM: Payingcompanycode
Postings to the bank accounts or the bank sub-accounts are made in the company code specified here during automatic payment transactions.
@Nullable public String getSendingcompanycode()
Original property name from the Odata EDM: Sendingcompanycode
When making cross-company code payments, you can specify the sending company code as well as the paying company code for each company code. If the sending company code is different from the paying company code, the system notes the sending company code in the payment transfer medium or payment advice. This note is information for the business partner.Furthermore, the sending company code affects how the system groups items from different company codes into one payment. Items are only grouped into one payment for company codes with the same paying company code and the same sending company code.If the sending company code is not specified, the system automatically regards the paying company code as the sending company code.Specify the sending company code if you want to pay using a cross-company code transaction but do not want to pay the items of all participating company codes together.Example 1:Company code 0001 pays its own items and the items of company codes 0002 and 0003. All items are grouped into one payment.Company code Paying company code Sending company code0001 0001 00010002 0001 00010003 0001 0001Example 2:Company code 0001 pays its own items and the items of company codes 0002 and 0003. However, a separate payment is created for each company code.Company code Paying company code Sending company code0001 0001 00010002 0001 00020003 0001 0003
@Nullable public String getPayeeadditionalname()
Original property name from the Odata EDM: Payeeadditionalname
@Nullable public String getPayeepostalcode()
Original property name from the Odata EDM: Payeepostalcode
@Nullable public String getPayeecityname()
Original property name from the Odata EDM: Payeecityname
@Nullable public String getPayeecountry()
Original property name from the Odata EDM: Payeecountry
@Nullable public String getPayeeregion()
Original property name from the Odata EDM: Payeeregion
%EXAMPLE&Meaning of the regional code in ...USA StateItaly ProvinceCanada ProvinceGreat Britain County
@Nullable public String getPayeelanguage()
Original property name from the Odata EDM: Payeelanguage
@Nullable public String getName()
Original property name from the Odata EDM: Name
@Nullable public String getPayeebankcountry()
Original property name from the Odata EDM: Payeebankcountry
@Nullable public String getPayeebank()
Original property name from the Odata EDM: Payeebank
@Nullable public String getPayeebanknumber()
Original property name from the Odata EDM: Payeebanknumber
@Nullable public String getPayeebankaccount()
Original property name from the Odata EDM: Payeebankaccount
@Nullable public String getPayeebankcontrolkey()
Original property name from the Odata EDM: Payeebankcontrolkey
@Nullable public String getBankdetailreference()
Original property name from the Odata EDM: Bankdetailreference
In some countries, in order to be able to use certain payment transactions, extra specifications must be made for the customer/vendor's bank details (bank number, bank account number, name of the account holder). These additional specifications are defined here.If additional data for the bank details is needed for payment transactions in your country (see the following examples), enter the reference information here.If the bank requires the collection authorization reference number for bank collection in Norway or Great Britain, you specify that number here.When making payments to a building society account in Great Britain, you must specify which number the payee has at the building society. You make this entry in the reference field, and the bank key and account number fields are used for the bank details of the building society.In Great Britain, if you enter a building society account number here, its name must already be defined in the system.
@Nullable public String getPayeebankidentifiercode()
Original property name from the Odata EDM: Payeebankidentifiercode
SWIFT stands for Society for Worldwide Interbank Financial Telecommunication.BIC stands for Bank Identifier Code.This globally unique code can be used in international payment transactions to identify the bank without the need to specify an address or bank number. Specification of the SWIFT code/BIC is mainly relevant for automatic payment transactions.
@Nullable public String getPayeeiban()
Original property name from the Odata EDM: Payeeiban
Commitee for Banking Standards) to represent bank details. AN IBANcontains a maximum of 34 alphanumerical symbols and is made up acombination of hte following elements:The bank's country key (ISO code)A two-figure check digitCountry-specific account number (in Germany, for example, this consistsof the bank number and the account number, while in France it consistsof the bank number, the account number and the bank control key).The IBAN simplifies international payments and also provides benefitsfor domestic payments in some countries. In some countries, it alsoprovides advantages with respect to value dates and fees.The IBAN can be stored in parallel with the bank details, but does notreplace them. It is stored under the business partner's master data, and can be used when settings up the payment medium.As only the bank managing the account can generate the IBAN, whichcorresponds to one account number, the SAP system creates a proposalonly. You can either confirm or change this. If the system was not ableto create a proposal, enter the IBAN yourself.In Belgium, an IBAN might look like this:Electronic form:BE62510007547061Printed form, as it appears on the invoice:IBAN BE62 5100 0754 7061
@Nullable public String getBankaccountholdername()
Original property name from the Odata EDM: Bankaccountholdername
@Nullable public String getHousebankaccount()
Original property name from the Odata EDM: Housebankaccount
@Nullable public String getHousebank()
Original property name from the Odata EDM: Housebank
@Nullable public String getBankcountry()
Original property name from the Odata EDM: Bankcountry
The country key defines the rules according to which bank data, such as the bank and account numbers, is to be validated.
@Nullable public String getBank()
Original property name from the Odata EDM: Bank
@Nullable public String getBanknumber()
Original property name from the Odata EDM: Banknumber
@Nullable public String getBankaccount()
Original property name from the Odata EDM: Bankaccount
@Nullable public String getBankcontrolkey()
Original property name from the Odata EDM: Bankcontrolkey
@Nullable public String getGlaccountforbankaccount()
Original property name from the Odata EDM: Glaccountforbankaccount
@Nullable public String getSupplierpaymentmethod()
Original property name from the Odata EDM: Supplierpaymentmethod
Payment methods are entered in the master records of customers and vendors in order to specify how payments are made. If an open item is to be paid using a specific payment method, enter it in the open item. The terms which have been defined for the payment method must be satisfied for the payment.Payment methods are to be defined in the Financial Accounting configuration menu, where the following steps are to be carried out:First of all, make all specifications that are required for a country-specific payment method.Then define per company code the terms under which a payment method can be used.All payment methods are displayed in the customer or vendor master record in the screen for selecting the payment method. Here you select the required payment method by marking it; the system transfers the payment methods to the customer/vendor master record.
@Nullable public String getPaymentmethodsupplement()
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.
@Nullable public String getDataexchangeinstructionkey()
Original property name from the Odata EDM: Dataexchangeinstructionkey
Selecting the instruction keyIf data medium exchange is used (as well as in special cases when using document-based payment orders) the instruction key must be maintained in the customer/vendor master record, or in the system configuration for data medium exchange data for the house bank. The following holds regarding the instruction key:If the instruction key is maintained in the master record, then this instruction key is used.If no instruction key exists in the vendor master record, then the default instruction key defined for the house bank is used.Consequently, it is not necessary to provide all business partners with an instruction key; only the exceptions need to be maintained.1If it is necessary to specify an instruction key for a business partner's house bank that differs from the instruction key defined in the master record, this can be done when editing the payment proposal.2The instruction key must be entered in the document for one-time accounts.3The four instruction key fields belonging to the instruction key can be overridden by entering instruction keys in the document (the "Additional Data" screen in the customer or vendor line).
@Nullable public LocalDateTime getPaymentdocumentpostingdate()
Original property name from the Odata EDM: Paymentdocumentpostingdate
@Nullable public LocalDateTime getValuedate()
Original property name from the Odata EDM: Valuedate
The value date is used in bank accounts and bank sub-accounts.
@Nullable public LocalDateTime getPaiditemduedate()
Original property name from the Odata EDM: Paiditemduedate
@Nullable public LocalDateTime getBillofexchangeduedate()
Original property name from the Odata EDM: Billofexchangeduedate
@Nullable public LocalDateTime getBillofexchangeissuedate()
Original property name from the Odata EDM: Billofexchangeissuedate
@Nullable public String getAccountingclerk()
Original property name from the Odata EDM: Accountingclerk
The name of the accounting clerk defined by this identification code can be used in the payment program for correspondence and reporting (for example, open item lists).
@Nullable public String getAccountbyshipper()
Original property name from the Odata EDM: Accountbyshipper
@Nullable public String getPaymentreference()
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'.
@Nullable public byte[] getSepamandateuuid()
Original property name from the Odata EDM: Sepamandateuuid
@Nullable public String getSepamandate()
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 MandatesYou 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 PayersIf 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.ExampleYou 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 accountsContract account Mandate (in Contract Acct) MeaningC1 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 mandateMandate Contract Account (in Mandate) MeaningM1 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.
@Nullable public String getInvoicereference()
Original property name from the Odata EDM: Invoicereference
Otherwise it displays the document number.You can use this field for sorting and grouping the items concerning the original invoice item and all items referenced to it.
@Nullable public String getInvoicereferencefiscalyear()
Original property name from the Odata EDM: Invoicereferencefiscalyear
Otherwise it displays the fiscal year of the document number.
@Nullable public String getInvoiceitemreference()
Original property name from the Odata EDM: Invoiceitemreference
Otherwise it displays the document line item.
@Nonnull public String toString()
toString in class VdmObject<PaymentReleaseListItem>public boolean equals(@Nullable Object o)
equals in class VdmObject<PaymentReleaseListItem>protected boolean canEqual(@Nullable Object other)
canEqual in class VdmObject<PaymentReleaseListItem>public int hashCode()
hashCode in class VdmObject<PaymentReleaseListItem>Copyright © 2020 SAP SE. All rights reserved.