public class PersonnelCompensationElement extends VdmEntity<PersonnelCompensationElement>
Original entity name from the Odata EDM: PersonnelCompensationElementType
Modifier and Type | Class and Description |
---|---|
static class |
PersonnelCompensationElement.PersonnelCompensationElementBuilder
Helper class to allow for fluent creation of PersonnelCompensationElement instances.
|
Modifier and Type | Field and Description |
---|---|
static PersonnelCompensationElementField<LocalDateTime> |
ACTUAL_SETTLMT_DATE
Use with available fluent helpers to apply the ActualSettlmtDate field to query operations.
|
static PersonnelCompensationElementSelectable |
ALL_FIELDS
Selector for all available fields of PersonnelCompensationElement.
|
static PersonnelCompensationElementField<String> |
ASSIGNMENT_REFERENCE
Use with available fluent helpers to apply the AssignmentReference field to query operations.
|
static PersonnelCompensationElementField<String> |
COMPANY_CODE
Use with available fluent helpers to apply the CompanyCode field to query operations.
|
static PersonnelCompensationElementField<String> |
COMPANY_CODE_COUNTRY
Use with available fluent helpers to apply the CompanyCodeCountry field to query operations.
|
static PersonnelCompensationElementField<String> |
COMPANY_CODE_COUNTRY_ISO_CODE
Use with available fluent helpers to apply the CompanyCodeCountryISOCode field to query operations.
|
static PersonnelCompensationElementField<String> |
COUNTRY_THREE_DIGIT_ISO_CODE
Use with available fluent helpers to apply the CountryThreeDigitISOCode field to query operations.
|
static PersonnelCompensationElementField<LocalDateTime> |
DOCUMENT_DATE
Use with available fluent helpers to apply the DocumentDate field to query operations.
|
static PersonnelCompensationElementField<String> |
DOCUMENT_REFERENCE_ID
Use with available fluent helpers to apply the DocumentReferenceID field to query operations.
|
static PersonnelCompensationElementField<LocalDateTime> |
JOURNAL_ENTRY_CREATION_DATE
Use with available fluent helpers to apply the JournalEntryCreationDate field to query operations.
|
static PersonnelCompensationElementField<ZonedDateTime> |
JOURNAL_ENTRY_CREATION_DATE_TIME
Use with available fluent helpers to apply the JournalEntryCreationDateTime field to query operations.
|
static PersonnelCompensationElementField<LocalTime> |
JOURNAL_ENTRY_CREATION_TIME
Use with available fluent helpers to apply the JournalEntryCreationTime field to query operations.
|
static PersonnelCompensationElementField<String> |
PAYMENT_REFERENCE
Use with available fluent helpers to apply the PaymentReference field to query operations.
|
static PersonnelCompensationElementField<String> |
PERS_SETTLMT_DOC_CURRENCY
Use with available fluent helpers to apply the PersSettlmtDocCurrency field to query operations.
|
static PersonnelCompensationElementField<String> |
PERS_SETTLMT_DOC_CURRENCY_ISO_CODE
Use with available fluent helpers to apply the PersSettlmtDocCurrencyISOCode field to query operations.
|
static PersonnelCompensationElementField<Boolean> |
PERS_SETTLMT_DOC_IS_REVERSED
Use with available fluent helpers to apply the PersSettlmtDocIsReversed field to query operations.
|
static PersonnelCompensationElementField<String> |
PERSON_WORK_AGREEMENT
Use with available fluent helpers to apply the PersonWorkAgreement field to query operations.
|
static PersonnelCompensationElementField<String> |
PERSON_WORK_AGREEMENT_EXTERNAL_ID
Use with available fluent helpers to apply the PersonWorkAgreementExternalID field to query operations.
|
static PersonnelCompensationElementField<String> |
PERSONNEL_SETTLEMENT_DOCUMENT
Use with available fluent helpers to apply the PersonnelSettlementDocument field to query operations.
|
static PersonnelCompensationElementField<LocalDateTime> |
POSTING_DATE
Use with available fluent helpers to apply the PostingDate field to query operations.
|
static PersonnelCompensationElementField<String> |
RVSD_PERS_SETTLMT_DOC
Use with available fluent helpers to apply the RvsdPersSettlmtDoc field to query operations.
|
static PersonnelCompensationElementField<String> |
SETTLMT_COMPENSATION_REASON
Use with available fluent helpers to apply the SettlmtCompensationReason field to query operations.
|
static PersonnelCompensationElementField<String> |
SETTLMT_DOC_CAT
Use with available fluent helpers to apply the SettlmtDocCat field to query operations.
|
static PersonnelCompensationElementField<String> |
SETTLMT_DOC_TYPE
Use with available fluent helpers to apply the SettlmtDocType field to query operations.
|
static PersonnelCompensationElementLink<PersCompnElmntCostAssgmt> |
TO_PERS_COMPN_ELMNT_COST_ASSGMT
Use with available fluent helpers to apply the to_PersCompnElmntCostAssgmt navigation property to query
operations.
|
static PersonnelCompensationElementField<BigDecimal> |
TOTAL_NET_AMOUNT
Use with available fluent helpers to apply the TotalNetAmount field to query operations.
|
changedOriginalFields
Constructor and Description |
---|
PersonnelCompensationElement() |
PersonnelCompensationElement(String personnelSettlementDocument,
String settlmtDocType,
String settlmtDocCat,
String companyCode,
String companyCodeCountry,
String companyCodeCountryISOCode,
String countryThreeDigitISOCode,
String personWorkAgreement,
String personWorkAgreementExternalID,
String settlmtCompensationReason,
LocalDateTime postingDate,
LocalDateTime documentDate,
LocalDateTime actualSettlmtDate,
BigDecimal totalNetAmount,
String persSettlmtDocCurrency,
String persSettlmtDocCurrencyISOCode,
String documentReferenceID,
String assignmentReference,
String paymentReference,
Boolean persSettlmtDocIsReversed,
String rvsdPersSettlmtDoc,
LocalDateTime journalEntryCreationDate,
LocalTime journalEntryCreationTime,
ZonedDateTime journalEntryCreationDateTime,
List<PersCompnElmntCostAssgmt> toPersCompnElmntCostAssgmt) |
Modifier and Type | Method and Description |
---|---|
void |
addPersCompnElmntCostAssgmt(PersCompnElmntCostAssgmt... entity)
Adds elements to the list of associated PersCompnElmntCostAssgmt entities.
|
void |
attachToService(String servicePath,
HttpDestinationProperties destination)
Sets the service path and destination for the fetch commands of this entity.
|
static PersonnelCompensationElement.PersonnelCompensationElementBuilder |
builder() |
protected boolean |
canEqual(Object other) |
boolean |
equals(Object o) |
List<PersCompnElmntCostAssgmt> |
fetchPersCompnElmntCostAssgmt()
Fetches the PersCompnElmntCostAssgmt entities (one to many) associated with this entity.
|
static <T> PersonnelCompensationElementField<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) |
LocalDateTime |
getActualSettlmtDate()
Constraints: Not nullable, Precision: 0
|
String |
getAssignmentReference()
Constraints: Not nullable, Maximum length: 18
|
String |
getCompanyCode()
Constraints: Not nullable, Maximum length: 4
|
String |
getCompanyCodeCountry()
Constraints: Not nullable, Maximum length: 3
|
String |
getCompanyCodeCountryISOCode()
Constraints: Not nullable, Maximum length: 3
|
String |
getCountryThreeDigitISOCode()
Constraints: Not nullable, Maximum length: 3
|
protected String |
getDefaultServicePath() |
HttpDestinationProperties |
getDestinationForFetch()
Convienence field for reusing the same destination with multiple queries (e.g.
|
LocalDateTime |
getDocumentDate()
Constraints: Not nullable, Precision: 0
|
String |
getDocumentReferenceID()
Constraints: Not nullable, Maximum length: 16
|
protected String |
getEntityCollection() |
LocalDateTime |
getJournalEntryCreationDate()
Constraints: Not nullable, Precision: 0
|
ZonedDateTime |
getJournalEntryCreationDateTime()
Constraints: Not nullable, Precision: 0
|
LocalTime |
getJournalEntryCreationTime()
Constraints: Not nullable, Precision: 0
|
protected Map<String,Object> |
getKey() |
String |
getPaymentReference()
Constraints: Not nullable, Maximum length: 30
|
io.vavr.control.Option<List<PersCompnElmntCostAssgmt>> |
getPersCompnElmntCostAssgmtIfPresent()
Retrieval of associated PersCompnElmntCostAssgmt entities (one to many).
|
List<PersCompnElmntCostAssgmt> |
getPersCompnElmntCostAssgmtOrFetch()
Retrieval of associated PersCompnElmntCostAssgmt entities (one to many).
|
String |
getPersonnelSettlementDocument()
(Key Field) Constraints: Not nullable, Maximum length: 10
|
String |
getPersonWorkAgreement()
Constraints: Not nullable, Maximum length: 8
|
String |
getPersonWorkAgreementExternalID()
Constraints: Not nullable, Maximum length: 20
|
String |
getPersSettlmtDocCurrency()
Constraints: Not nullable, Maximum length: 5
|
String |
getPersSettlmtDocCurrencyISOCode()
Constraints: Not nullable, Maximum length: 3
|
Boolean |
getPersSettlmtDocIsReversed()
Constraints: none
|
LocalDateTime |
getPostingDate()
Constraints: Not nullable, Precision: 0
|
String |
getRvsdPersSettlmtDoc()
Constraints: Not nullable, Maximum length: 10
|
String |
getSettlmtCompensationReason()
Constraints: Not nullable, Maximum length: 4
|
String |
getSettlmtDocCat()
Constraints: Not nullable, Maximum length: 2
|
String |
getSettlmtDocType()
Constraints: Not nullable, Maximum length: 4
|
BigDecimal |
getTotalNetAmount()
Constraints: Not nullable, Precision: 16, Scale: 3
|
Class<PersonnelCompensationElement> |
getType() |
int |
hashCode() |
void |
setActualSettlmtDate(LocalDateTime actualSettlmtDate)
Constraints: Not nullable, Precision: 0
|
void |
setAssignmentReference(String assignmentReference)
Constraints: Not nullable, Maximum length: 18
|
void |
setCompanyCode(String companyCode)
Constraints: Not nullable, Maximum length: 4
|
void |
setCompanyCodeCountry(String companyCodeCountry)
Constraints: Not nullable, Maximum length: 3
|
void |
setCompanyCodeCountryISOCode(String companyCodeCountryISOCode)
Constraints: Not nullable, Maximum length: 3
|
void |
setCountryThreeDigitISOCode(String countryThreeDigitISOCode)
Constraints: Not nullable, Maximum length: 3
|
void |
setDocumentDate(LocalDateTime documentDate)
Constraints: Not nullable, Precision: 0
|
void |
setDocumentReferenceID(String documentReferenceID)
Constraints: Not nullable, Maximum length: 16
|
void |
setJournalEntryCreationDate(LocalDateTime journalEntryCreationDate)
Constraints: Not nullable, Precision: 0
|
void |
setJournalEntryCreationDateTime(ZonedDateTime journalEntryCreationDateTime)
Constraints: Not nullable, Precision: 0
|
void |
setJournalEntryCreationTime(LocalTime journalEntryCreationTime)
Constraints: Not nullable, Precision: 0
|
void |
setPaymentReference(String paymentReference)
Constraints: Not nullable, Maximum length: 30
|
void |
setPersCompnElmntCostAssgmt(List<PersCompnElmntCostAssgmt> value)
Overwrites the list of associated PersCompnElmntCostAssgmt entities for the loaded navigation property
to_PersCompnElmntCostAssgmt.
|
void |
setPersonnelSettlementDocument(String personnelSettlementDocument)
(Key Field) Constraints: Not nullable, Maximum length: 10
|
void |
setPersonWorkAgreement(String personWorkAgreement)
Constraints: Not nullable, Maximum length: 8
|
void |
setPersonWorkAgreementExternalID(String personWorkAgreementExternalID)
Constraints: Not nullable, Maximum length: 20
|
void |
setPersSettlmtDocCurrency(String persSettlmtDocCurrency)
Constraints: Not nullable, Maximum length: 5
|
void |
setPersSettlmtDocCurrencyISOCode(String persSettlmtDocCurrencyISOCode)
Constraints: Not nullable, Maximum length: 3
|
void |
setPersSettlmtDocIsReversed(Boolean persSettlmtDocIsReversed)
Constraints: none
|
void |
setPostingDate(LocalDateTime postingDate)
Constraints: Not nullable, Precision: 0
|
void |
setRvsdPersSettlmtDoc(String rvsdPersSettlmtDoc)
Constraints: Not nullable, Maximum length: 10
|
protected void |
setServicePathForFetch(String servicePathForFetch)
The service path only used for the fetch commands of this entity.
|
void |
setSettlmtCompensationReason(String settlmtCompensationReason)
Constraints: Not nullable, Maximum length: 4
|
void |
setSettlmtDocCat(String settlmtDocCat)
Constraints: Not nullable, Maximum length: 2
|
void |
setSettlmtDocType(String settlmtDocType)
Constraints: Not nullable, Maximum length: 4
|
void |
setTotalNetAmount(BigDecimal totalNetAmount)
Constraints: Not nullable, Precision: 16, Scale: 3
|
protected Map<String,Object> |
toMapOfFields() |
protected Map<String,Object> |
toMapOfNavigationProperties() |
String |
toString() |
getServicePathForFetch, getVersionIdentifier, setDestinationForFetch, setVersionIdentifier
getChangedFields, getCustomField, getCustomField, getCustomFieldNames, getCustomFields, getSetOfCustomFields, getSetOfFields, getSetOfNavigationProperties, hasCustomField, hasCustomField, rememberChangedField, resetChangedFields, setCustomField, setCustomField, toMap, toMapOfCustomFields
public static final PersonnelCompensationElementSelectable ALL_FIELDS
public static final PersonnelCompensationElementField<String> PERSONNEL_SETTLEMENT_DOCUMENT
public static final PersonnelCompensationElementField<String> SETTLMT_DOC_TYPE
public static final PersonnelCompensationElementField<String> SETTLMT_DOC_CAT
public static final PersonnelCompensationElementField<String> COMPANY_CODE
public static final PersonnelCompensationElementField<String> COMPANY_CODE_COUNTRY
public static final PersonnelCompensationElementField<String> COMPANY_CODE_COUNTRY_ISO_CODE
public static final PersonnelCompensationElementField<String> COUNTRY_THREE_DIGIT_ISO_CODE
public static final PersonnelCompensationElementField<String> PERSON_WORK_AGREEMENT
public static final PersonnelCompensationElementField<String> PERSON_WORK_AGREEMENT_EXTERNAL_ID
public static final PersonnelCompensationElementField<String> SETTLMT_COMPENSATION_REASON
public static final PersonnelCompensationElementField<LocalDateTime> POSTING_DATE
public static final PersonnelCompensationElementField<LocalDateTime> DOCUMENT_DATE
public static final PersonnelCompensationElementField<LocalDateTime> ACTUAL_SETTLMT_DATE
public static final PersonnelCompensationElementField<BigDecimal> TOTAL_NET_AMOUNT
public static final PersonnelCompensationElementField<String> PERS_SETTLMT_DOC_CURRENCY
public static final PersonnelCompensationElementField<String> PERS_SETTLMT_DOC_CURRENCY_ISO_CODE
public static final PersonnelCompensationElementField<String> DOCUMENT_REFERENCE_ID
public static final PersonnelCompensationElementField<String> ASSIGNMENT_REFERENCE
public static final PersonnelCompensationElementField<String> PAYMENT_REFERENCE
public static final PersonnelCompensationElementField<Boolean> PERS_SETTLMT_DOC_IS_REVERSED
public static final PersonnelCompensationElementField<String> RVSD_PERS_SETTLMT_DOC
public static final PersonnelCompensationElementField<LocalDateTime> JOURNAL_ENTRY_CREATION_DATE
public static final PersonnelCompensationElementField<LocalTime> JOURNAL_ENTRY_CREATION_TIME
public static final PersonnelCompensationElementField<ZonedDateTime> JOURNAL_ENTRY_CREATION_DATE_TIME
public static final PersonnelCompensationElementLink<PersCompnElmntCostAssgmt> TO_PERS_COMPN_ELMNT_COST_ASSGMT
public PersonnelCompensationElement()
public PersonnelCompensationElement(@Nullable String personnelSettlementDocument, @Nullable String settlmtDocType, @Nullable String settlmtDocCat, @Nullable String companyCode, @Nullable String companyCodeCountry, @Nullable String companyCodeCountryISOCode, @Nullable String countryThreeDigitISOCode, @Nullable String personWorkAgreement, @Nullable String personWorkAgreementExternalID, @Nullable String settlmtCompensationReason, @Nullable LocalDateTime postingDate, @Nullable LocalDateTime documentDate, @Nullable LocalDateTime actualSettlmtDate, @Nullable BigDecimal totalNetAmount, @Nullable String persSettlmtDocCurrency, @Nullable String persSettlmtDocCurrencyISOCode, @Nullable String documentReferenceID, @Nullable String assignmentReference, @Nullable String paymentReference, @Nullable Boolean persSettlmtDocIsReversed, @Nullable String rvsdPersSettlmtDoc, @Nullable LocalDateTime journalEntryCreationDate, @Nullable LocalTime journalEntryCreationTime, @Nullable ZonedDateTime journalEntryCreationDateTime, List<PersCompnElmntCostAssgmt> toPersCompnElmntCostAssgmt)
@Nonnull public Class<PersonnelCompensationElement> getType()
getType
in class VdmObject<PersonnelCompensationElement>
public void setPersonnelSettlementDocument(@Nullable String personnelSettlementDocument)
Original property name from the Odata EDM: PersonnelSettlementDocument
personnelSettlementDocument
- Personnel Settlement Document Numberpublic void setSettlmtDocType(@Nullable String settlmtDocType)
Original property name from the Odata EDM: SettlmtDocType
The settlement document type determines how the system processes a document in Settlement Management.
settlmtDocType
- Classifies various types of documents in Settlement Management.public void setSettlmtDocCat(@Nullable String settlmtDocCat)
Original property name from the Odata EDM: SettlmtDocCat
settlmtDocCat
- Classification of different document categories which you can process in the system (e.g. credit notes
and invoices).public void setCompanyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
companyCode
- Company Codepublic void setCompanyCodeCountry(@Nullable String companyCodeCountry)
Original property name from the Odata EDM: CompanyCodeCountry
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country-code or a typical country key, for example, in Germany the Federal statistics office key.The country keys are determined at system installation in the global settings.The definition of the country key in the SAP system does not have to match political or government entities.Since the country key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country key cannot query the country key T005-LAND1, but have to program based on the ISO code T005 INTCA.
companyCodeCountry
- The country key contains information which the system uses to check entries such as the length of the
postal code or bank account number.public void setCompanyCodeCountryISOCode(@Nullable String companyCodeCountryISOCode)
Original property name from the Odata EDM: CompanyCodeCountryISOCode
The key is used, e.g. for data exchange with banks via OFX (Open Financial Exchange).It is not the same as the more commonly used 2-character ISO country code or the 3-character numeric INTRASTAT country code.Enter the 3-character ISO country code for all countries if you want to exchange data with banks via OFX.
companyCodeCountryISOCode
- International standardized 3-character country keypublic void setCountryThreeDigitISOCode(@Nullable String countryThreeDigitISOCode)
Original property name from the Odata EDM: CountryThreeDigitISOCode
This 3-character numeric ISO country code is listed for all countries, for example, in the Internet under the address http://www.un.org/Depts/unsd/methods/m49alpha.htm.The code is not to be confused with the 2-character ISO country code, which is more frequently used, the 3-character numeric INTRASTAT country code, or the 3-character non-numeric ISO country code.The use of this 3-character numeric ISO code is required by law in countries such as Romania and Croatia.
countryThreeDigitISOCode
- 3-character numeric ISO country codepublic void setPersonWorkAgreement(@Nullable String personWorkAgreement)
Original property name from the Odata EDM: PersonWorkAgreement
personWorkAgreement
- The personnel number is the only feature within a client which is unique to an employee. You have to
enter a personnel number before you can display and maintain an employee's master data and time data.public void setPersonWorkAgreementExternalID(@Nullable String personWorkAgreementExternalID)
Original property name from the Odata EDM: PersonWorkAgreementExternalID
personWorkAgreementExternalID
- Work Agreement External IDpublic void setSettlmtCompensationReason(@Nullable String settlmtCompensationReason)
Original property name from the Odata EDM: SettlmtCompensationReason
The designated use of the compensation reason is to differentiate - otherwise identical - personnel settlement documents with regard to the business reason for the compensation to an employee. However, you can also use this differentiation parameter for other kinds of Settlement Management documents.Usually, you also use the compensation reason to differentiate the wage types in a subsequent payroll processing of personnel settlement documents.You use different compensation reasons to distinguish regular bonus or commission payments and special awards and to distinguish payments for single employees and teams.
settlmtCompensationReason
- Provides a more detailed information on the business reason for a Settlement Management document.public void setPostingDate(@Nullable LocalDateTime postingDate)
Original property name from the Odata EDM: PostingDate
The system uses the day's date as the posting date. You can change this date manually in the document.When processing documents, you can use the posting date as a selection criterion.
postingDate
- Date on which billing was carried out and posted in Financial Accounting. Billing leads to creation of
a receivable or payable.public void setDocumentDate(@Nullable LocalDateTime documentDate)
Original property name from the Odata EDM: DocumentDate
documentDate
- The document date contains the date on which a settlement management document is created or the
document date of an external document.public void setActualSettlmtDate(@Nullable LocalDateTime actualSettlmtDate)
Original property name from the Odata EDM: ActualSettlmtDate
For final and partial settlements it is equal to the settlement date.For delta settlements it is equal to the reference settlement date.For delta accruals before the final settlement, it is equal to the settlement date.For delta accruals after the final settlement, it is equal to the reference settlement date.
actualSettlmtDate
- The actual settlement date is the end date of the settlement period.public void setTotalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
Item value = billing document quantity x gross price of item
totalNetAmount
- Value of document item (without deductions or additions).public void setPersSettlmtDocCurrency(@Nullable String persSettlmtDocCurrency)
Original property name from the Odata EDM: PersSettlmtDocCurrency
The system uses a default document currency from thecustomer master record of the invoicing party. You can change the currency manually in the document. If you change the currency, the system determines a new price for the whole document.
persSettlmtDocCurrency
- The currency valid for the settlement document or supplier billing document.public void setPersSettlmtDocCurrencyISOCode(@Nullable String persSettlmtDocCurrencyISOCode)
Original property name from the Odata EDM: PersSettlmtDocCurrencyISOCode
Enter the ISO codeif you do not already use the global standard currency key as the currency keyif you use the EDI application. Here the ISO code is used for exchanging information.
persSettlmtDocCurrencyISOCode
- International standardized currency keypublic void setDocumentReferenceID(@Nullable String documentReferenceID)
Original property name from the Odata EDM: DocumentReferenceID
The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number.Enter the number specified by the business partner. If the document was created in-house and you do not know the business partner document number, you can copy the document number into the reference number field by entering "*".
documentReferenceID
- The reference document number can contain the document number of the customer/vendor. However it may
contain a different value.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 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 setPersSettlmtDocIsReversed(@Nullable Boolean persSettlmtDocIsReversed)
Original property name from the Odata EDM: PersSettlmtDocIsReversed
persSettlmtDocIsReversed
- Settlement Document is Reversedpublic void setRvsdPersSettlmtDoc(@Nullable String rvsdPersSettlmtDoc)
Original property name from the Odata EDM: RvsdPersSettlmtDoc
rvsdPersSettlmtDoc
- Document which has been reversed.public void setJournalEntryCreationDate(@Nullable LocalDateTime journalEntryCreationDate)
Original property name from the Odata EDM: JournalEntryCreationDate
journalEntryCreationDate
- Specifies the date in UTC on which a settlement document was released to accounting.public void setJournalEntryCreationTime(@Nullable LocalTime journalEntryCreationTime)
Original property name from the Odata EDM: JournalEntryCreationTime
journalEntryCreationTime
- Specifies the time in UTC at which a settlement document was released to accounting.public void setJournalEntryCreationDateTime(@Nullable ZonedDateTime journalEntryCreationDateTime)
Original property name from the Odata EDM: JournalEntryCreationDateTime
journalEntryCreationDateTime
- Specifies the date and time at which the journal entry was created for a settlement document,
expressed as a UTC timestamp.protected String getEntityCollection()
getEntityCollection
in class VdmEntity<PersonnelCompensationElement>
@Nonnull protected Map<String,Object> getKey()
getKey
in class VdmObject<PersonnelCompensationElement>
@Nonnull protected Map<String,Object> toMapOfFields()
toMapOfFields
in class VdmObject<PersonnelCompensationElement>
protected void fromMap(Map<String,Object> inputValues)
fromMap
in class VdmObject<PersonnelCompensationElement>
@Nonnull public static <T> PersonnelCompensationElementField<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> PersonnelCompensationElementField<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()
VdmEntity
getDestinationForFetch
in class VdmEntity<PersonnelCompensationElement>
protected void setServicePathForFetch(@Nullable String servicePathForFetch)
VdmEntity
Note: 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<PersonnelCompensationElement>
public void attachToService(@Nullable String servicePath, @Nonnull HttpDestinationProperties destination)
VdmEntity
Note: 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<PersonnelCompensationElement>
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()
getDefaultServicePath
in class VdmEntity<PersonnelCompensationElement>
@Nonnull protected Map<String,Object> toMapOfNavigationProperties()
toMapOfNavigationProperties
in class VdmObject<PersonnelCompensationElement>
@Nonnull public List<PersCompnElmntCostAssgmt> fetchPersCompnElmntCostAssgmt() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
Please note: This method will not cache or persist the query results.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public List<PersCompnElmntCostAssgmt> getPersCompnElmntCostAssgmtOrFetch() throws com.sap.cloud.sdk.odatav2.connectivity.ODataException
If the navigation property to_PersCompnElmntCostAssgmt of a queried PersonnelCompensationElement is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
com.sap.cloud.sdk.odatav2.connectivity.ODataException
- If the entity is unmanaged, i.e. it has not been retrieved using the OData VDM's services and
therefore has no ERP configuration context assigned. An entity is managed if it has been either
retrieved using the VDM's services or returned from the VDM's services as the result of a CREATE or
UPDATE call.@Nonnull public io.vavr.control.Option<List<PersCompnElmntCostAssgmt>> getPersCompnElmntCostAssgmtIfPresent()
If the navigation property for an entity PersonnelCompensationElement has not been resolved yet, this
method will not query further information. Instead its Option
result state will be
empty
.
Option
with
result state empty
is returned.public void setPersCompnElmntCostAssgmt(@Nonnull List<PersCompnElmntCostAssgmt> value)
If the navigation property to_PersCompnElmntCostAssgmt of a queried PersonnelCompensationElement is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
value
- List of PersCompnElmntCostAssgmt entities.public void addPersCompnElmntCostAssgmt(PersCompnElmntCostAssgmt... entity)
If the navigation property to_PersCompnElmntCostAssgmt of a queried PersonnelCompensationElement is operated lazily, an ODataException can be thrown in case of an OData query error.
Please note: Lazy loading of OData entity associations is the process of asynchronous retrieval and persisting of items from a navigation property. If a lazy property is requested by the application for the first time and it has not yet been loaded, an OData query will be run in order to load the missing information and its result will get cached for future invocations.
entity
- Array of PersCompnElmntCostAssgmt entities.public static PersonnelCompensationElement.PersonnelCompensationElementBuilder builder()
@Nullable public String getPersonnelSettlementDocument()
Original property name from the Odata EDM: PersonnelSettlementDocument
@Nullable public String getSettlmtDocType()
Original property name from the Odata EDM: SettlmtDocType
The settlement document type determines how the system processes a document in Settlement Management.
@Nullable public String getSettlmtDocCat()
Original property name from the Odata EDM: SettlmtDocCat
@Nullable public String getCompanyCode()
Original property name from the Odata EDM: CompanyCode
@Nullable public String getCompanyCodeCountry()
Original property name from the Odata EDM: CompanyCodeCountry
The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used.It could also be the vehicle license plate country-code or a typical country key, for example, in Germany the Federal statistics office key.The country keys are determined at system installation in the global settings.The definition of the country key in the SAP system does not have to match political or government entities.Since the country key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country key cannot query the country key T005-LAND1, but have to program based on the ISO code T005 INTCA.
@Nullable public String getCompanyCodeCountryISOCode()
Original property name from the Odata EDM: CompanyCodeCountryISOCode
The key is used, e.g. for data exchange with banks via OFX (Open Financial Exchange).It is not the same as the more commonly used 2-character ISO country code or the 3-character numeric INTRASTAT country code.Enter the 3-character ISO country code for all countries if you want to exchange data with banks via OFX.
@Nullable public String getCountryThreeDigitISOCode()
Original property name from the Odata EDM: CountryThreeDigitISOCode
This 3-character numeric ISO country code is listed for all countries, for example, in the Internet under the address http://www.un.org/Depts/unsd/methods/m49alpha.htm.The code is not to be confused with the 2-character ISO country code, which is more frequently used, the 3-character numeric INTRASTAT country code, or the 3-character non-numeric ISO country code.The use of this 3-character numeric ISO code is required by law in countries such as Romania and Croatia.
@Nullable public String getPersonWorkAgreement()
Original property name from the Odata EDM: PersonWorkAgreement
@Nullable public String getPersonWorkAgreementExternalID()
Original property name from the Odata EDM: PersonWorkAgreementExternalID
@Nullable public String getSettlmtCompensationReason()
Original property name from the Odata EDM: SettlmtCompensationReason
The designated use of the compensation reason is to differentiate - otherwise identical - personnel settlement documents with regard to the business reason for the compensation to an employee. However, you can also use this differentiation parameter for other kinds of Settlement Management documents.Usually, you also use the compensation reason to differentiate the wage types in a subsequent payroll processing of personnel settlement documents.You use different compensation reasons to distinguish regular bonus or commission payments and special awards and to distinguish payments for single employees and teams.
@Nullable public LocalDateTime getPostingDate()
Original property name from the Odata EDM: PostingDate
The system uses the day's date as the posting date. You can change this date manually in the document.When processing documents, you can use the posting date as a selection criterion.
@Nullable public LocalDateTime getDocumentDate()
Original property name from the Odata EDM: DocumentDate
@Nullable public LocalDateTime getActualSettlmtDate()
Original property name from the Odata EDM: ActualSettlmtDate
For final and partial settlements it is equal to the settlement date.For delta settlements it is equal to the reference settlement date.For delta accruals before the final settlement, it is equal to the settlement date.For delta accruals after the final settlement, it is equal to the reference settlement date.
@Nullable public BigDecimal getTotalNetAmount()
Original property name from the Odata EDM: TotalNetAmount
Item value = billing document quantity x gross price of item
@Nullable public String getPersSettlmtDocCurrency()
Original property name from the Odata EDM: PersSettlmtDocCurrency
The system uses a default document currency from thecustomer master record of the invoicing party. You can change the currency manually in the document. If you change the currency, the system determines a new price for the whole document.
@Nullable public String getPersSettlmtDocCurrencyISOCode()
Original property name from the Odata EDM: PersSettlmtDocCurrencyISOCode
Enter the ISO codeif you do not already use the global standard currency key as the currency keyif you use the EDI application. Here the ISO code is used for exchanging information.
@Nullable public String getDocumentReferenceID()
Original property name from the Odata EDM: DocumentReferenceID
The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number.Enter the number specified by the business partner. If the document was created in-house and you do not know the business partner document number, you can copy the document number into the reference number field by entering "*".
@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 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 Boolean getPersSettlmtDocIsReversed()
Original property name from the Odata EDM: PersSettlmtDocIsReversed
@Nullable public String getRvsdPersSettlmtDoc()
Original property name from the Odata EDM: RvsdPersSettlmtDoc
@Nullable public LocalDateTime getJournalEntryCreationDate()
Original property name from the Odata EDM: JournalEntryCreationDate
@Nullable public LocalTime getJournalEntryCreationTime()
Original property name from the Odata EDM: JournalEntryCreationTime
@Nullable public ZonedDateTime getJournalEntryCreationDateTime()
Original property name from the Odata EDM: JournalEntryCreationDateTime
public String toString()
toString
in class VdmObject<PersonnelCompensationElement>
public boolean equals(Object o)
equals
in class VdmObject<PersonnelCompensationElement>
protected boolean canEqual(Object other)
canEqual
in class VdmObject<PersonnelCompensationElement>
public int hashCode()
hashCode
in class VdmObject<PersonnelCompensationElement>
Copyright © 2019 SAP SE. All rights reserved.