public static final class PersonnelCompensationElement.PersonnelCompensationElementBuilder extends Object
@Nonnull public PersonnelCompensationElement.PersonnelCompensationElementBuilder persCompnElmntCostAssgmt(PersCompnElmntCostAssgmt... value)
value - The PersCompnElmntCostAssgmts to build this PersonnelCompensationElement with.public PersonnelCompensationElement.PersonnelCompensationElementBuilder personnelSettlementDocument(@Nullable String personnelSettlementDocument)
Original property name from the Odata EDM: PersonnelSettlementDocument
public PersonnelCompensationElement.PersonnelCompensationElementBuilder settlmtDocType(@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.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder settlmtDocCat(@Nullable String settlmtDocCat)
Original property name from the Odata EDM: SettlmtDocCat
and invoices).public PersonnelCompensationElement.PersonnelCompensationElementBuilder companyCode(@Nullable String companyCode)
Original property name from the Odata EDM: CompanyCode
public PersonnelCompensationElement.PersonnelCompensationElementBuilder companyCodeCountry(@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.
postal code or bank account number.public PersonnelCompensationElement.PersonnelCompensationElementBuilder companyCodeCountryISOCode(@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.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder countryThreeDigitISOCode(@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.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder personWorkAgreement(@Nullable String personWorkAgreement)
Original property name from the Odata EDM: PersonWorkAgreement
enter a personnel number before you can display and maintain an employee's master data and time data.public PersonnelCompensationElement.PersonnelCompensationElementBuilder personWorkAgreementExternalID(@Nullable String personWorkAgreementExternalID)
Original property name from the Odata EDM: PersonWorkAgreementExternalID
public PersonnelCompensationElement.PersonnelCompensationElementBuilder settlmtCompensationReason(@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.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder postingDate(@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.
receivable or payable.public PersonnelCompensationElement.PersonnelCompensationElementBuilder documentDate(@Nullable LocalDateTime documentDate)
Original property name from the Odata EDM: DocumentDate
date of an external document.public PersonnelCompensationElement.PersonnelCompensationElementBuilder actualSettlmtDate(@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.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder totalNetAmount(@Nullable BigDecimal totalNetAmount)
Original property name from the Odata EDM: TotalNetAmount
Item value = billing document quantity x gross price of item
public PersonnelCompensationElement.PersonnelCompensationElementBuilder persSettlmtDocCurrency(@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.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder persSettlmtDocCurrencyISOCode(@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.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder documentReferenceID(@Nullable String documentReferenceID)
Original property name from the Odata EDM: DocumentReferenceID
The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number.Enter the number specified by the business partner. If the document was created in-house and you do not know the business partner document number, you can copy the document number into the reference number field by entering "*".
contain a different value.public PersonnelCompensationElement.PersonnelCompensationElementBuilder assignmentReference(@Nullable String assignmentReference)
Original property name from the Odata EDM: AssignmentReference
The program can display the account line items sorted according to the content of this field.You can either enter the field contents manually, or have the system define them automatically in the master record via the sort key field.You define the rules for the layout of the assignment number field in the Implementation Guide (IMG) under Determine Standard Sorting for Line Items.
public PersonnelCompensationElement.PersonnelCompensationElementBuilder paymentReference(@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'.
invoice. The customer should refer to the payment reference when making the payment.public PersonnelCompensationElement.PersonnelCompensationElementBuilder persSettlmtDocIsReversed(@Nullable Boolean persSettlmtDocIsReversed)
Original property name from the Odata EDM: PersSettlmtDocIsReversed
public PersonnelCompensationElement.PersonnelCompensationElementBuilder rvsdPersSettlmtDoc(@Nullable String rvsdPersSettlmtDoc)
Original property name from the Odata EDM: RvsdPersSettlmtDoc
public PersonnelCompensationElement.PersonnelCompensationElementBuilder journalEntryCreationDate(@Nullable LocalDateTime journalEntryCreationDate)
Original property name from the Odata EDM: JournalEntryCreationDate
public PersonnelCompensationElement.PersonnelCompensationElementBuilder journalEntryCreationTime(@Nullable LocalTime journalEntryCreationTime)
Original property name from the Odata EDM: JournalEntryCreationTime
public PersonnelCompensationElement.PersonnelCompensationElementBuilder journalEntryCreationDateTime(@Nullable ZonedDateTime journalEntryCreationDateTime)
Original property name from the Odata EDM: JournalEntryCreationDateTime
as a UTC timestamp.public PersonnelCompensationElement build()
Copyright © 2019 SAP SE. All rights reserved.