Application Settings

The Application Settings section of the master data configuration allows you to configure the following:

  • Number Range: Number ranges are used to define the IDs that are automatically assigned to objects, such as master agreements (MLA), contracts, lease components, activation groups, units, and sub-units. For applications operating in standalone and hybrid modes, number ranges must also be configured to define unique document numbers for generated documents. The number ranges can be set up by year, lease area, and company code (except for MLAs, which does not have company code as a required field).
    • If the field "Manual ID Assignment" is set to true, then users can manually enter the ID themselves (but the ID must still be in the configured range). Manual ID assignment can only be used for MLAs, contracts, and lease components. For all other object types, IDs cannot be entered manually because there is no option to enter these IDs in the application UI.
    • The Asset number range can also be based on the asset class, but this option must first be enabled on the Other UI Customizations page. Otherwise, the Asset Class To and From fields will be ignored.
    • All of the number ranges can be assigned based on individual Company Codes and/or Lease Areas, by enabling switches on the General Settings page. If the switches are enabled, the Lease Area To and Company Code To fields are ignored.
    • If a user creates a new contract and the user selects a year for which there is no configured range, the application will generate an ID using the configuration for the next closest year to the current year. Note that the year is available in the list because a range does exist for it in another company code.
    • Note that if a number range is not configured for Migration documents, the application uses the range defined for Asset Capitalization documents.

    Warning: Whenever you deploy a new build after the initial deployment, you should make sure to update your number range configuration so that the same IDs are not generated again. Otherwise, you will have multiple documents posted to the same ID in SAP. You can either assign a new number range, or update the Last Generated ID.

  • Questionnaire: Defines the questions displayed on the Contract Determination page in the application, to determine the lease type.

    Warning: The wording can be modified, but the ID and order of the questions cannot be changed and new questions cannot be added.

  • Lease Type: Defines the lease types supported in the application.

    Warning: Do not modify any of the lease types. Processes are linked to the lease types.

  • Asset Class Mapping: Defines the asset classes used in Nakisa Lease Administration. These classes must be mapped to ERP classes per company code and accounting standard.
    • The straight-line asset depreciation calculation method for finance leases can be configured in this table. The "Daily" option will divide the total asset value by the number of days in the lease, whereas the "Period" option will divide the total asset value by the number of periods in the lease.
  • Reason Code: Reason codes are used to identify why a contract change was done. Additional reason codes can be added.
  • Remeasurement Reason: Remeasurement reasons are used to identify why an activation group reassessment was done. Additional remeasurement reasons can be added, but existing ones should not be modified. Some processes are linked to specific codes.
  • Notification: Define the email and system notification settings for MLAs, contracts, assessment, and classification approvals. When users define the user notifications on the Partner pages for MLAs and contracts, only users who have the assigned role (and who have access to the MLA/contract via authorization profiles) will be available for each responsibility. If no role is defined for the user responsibility, then all roles are available.

    Note: To send email notifications, you must enable the switch "Email Notifications" and configure the settings on the Notification Settings page.

  • Unit Status: Defines the statuses associated to each individual unit. The status represents the current stage the unit is in during its life-cycle.

    Warning: Do not modify any of the statuses or add new ones.

  • Internal Language: Contains the languages available in master agreements, and the associated ISO 639-1 codes. Only "Active" languages are available to be used.
  • Internal Currency: Contains all of the currencies available in the application, and the associated ISO 4217 code. Only "Active" currencies are available to be used.
  • Uploaded Document Type: Contains a list of document types that can be assigned to a PDF that is attached to a master agreement or contract object.

To configure the number ranges:

  1. Click Application Menu > Master Data Configuration.
  2. Navigate to Application ConfigsApplication Settings > Number Range.
  3. To edit an existing number range, click for the required row.
    • Whenever you deploy a new build after the initial deployment, you must ensure that the same IDs are not re-used by following one of the these options:
      • Update your number range in the fields Range From and Range To so that the same IDs are not generated again.
      • Update the Last Generated field with the last ID that was generated for this Number Range in the previous build.
  4. To create a new number range, click Menu > Add.
  5. Enter or modify the required information. Note that the Description field indicates to which object the number range applies. Nakisa recommends limiting the IDs to 12 characters.

    Note: If connected to an SAP ERP, the Contract ID must not be greater than 15 characters long.

  6. Click Submit.

To configure the questionnaire:

  1. Navigate to Application ConfigsApplication Settings > Questionnaire.
  2. To edit an existing question, click for the required row.
  3. Edit the wording.

    Warning: Do not modify the ID or the order of the questions.

  4. Click Submit.

To configure the asset class mapping:

  1. Navigate to Application ConfigsApplication Settings > Asset Class Mapping.
  2. To edit an existing asset class mapping, click for the required row.
  3. To create a new mapping, click Menu > Add.
  4. Enter the InternalAssetClass value that the user will see in the application, and the InternalAssetClassId that will be used in the asset class mapping in the System Config.
  5. Click Submit.

To configure the reason codes:

  1. Navigate to Application ConfigsApplication Settings > Reason Codes.
  2. To edit an existing reason code, click for the required row.
  3. To create a code, click Menu > Add.
  4. Enter the Description that the user will see in the application, and the ReasonCode.
  5. Click Submit.

To configure the remeasurement reasons:

  1. Navigate to Application ConfigsApplication Settings > Remeasurement Reason.
  2. To edit an existing remeasurement reason, click for the required row.
  3. To create a reason, click Menu > Add.
  4. Enter the Description that the user will see in the application, and the RemeasurementReasonCode.
  5. Click Submit.

To configure the internal languages:

  1. Navigate to Application ConfigsApplication Settings > Internal Language.
  2. To edit an existing language, click for the required row.
  3. To add a language, click Menu > Add.
  4. Modify or define the fields as required. Select the Active checkbox to make it available in the application.
  5. Click Submit.

To configure the currencies:

  1. Navigate to Application ConfigsApplication Settings > Internal Currencies.
  2. To edit an existing currency, click for the required row.
  3. To add a currency, click Menu > Add.
  4. Modify or define the fields as required. Select the Active checkbox to make it available in the application.
  5. Click Submit.

To configure the uploaded document types:

  1. Navigate to Application ConfigsApplication Settings > Uploaded Document Type.
  2. To edit an existing document type, click for the required row.
  3. To add a document type, click Menu > Add.
  4. Modify or define the fields as required.
  5. Click Submit.

To configure data retention periods:

  1. Navigate to Application ConfigsApplication Settings > Data Retention Period.
  2. To edit an existing data retention period, click for the required row.
  3. To add a new data retention period, click Menu > Add.
  4. Modify or define the fields as required.
  5. Click Submit.

To configure object deactivation:

  1. Navigate to Application ConfigsApplication Settings > Object Deactivation.
  2. To edit an existing object deactivation, click for the required row.
  3. To add a new object deactivation, click Menu > Add.
  4. Modify or define the fields as required.
  5. Click Submit.

To configure retention exception object:

  1. Navigate to Application ConfigsApplication Settings > Retention Exception Object.
  2. To edit an existing retention exception object, click for the required row.
  3. To add a new retention exception object, click Menu > Add.
  4. Modify or define the fields as required.
  5. Click Submit.

Nakisa Lease Administration 2022.R2-SP1 © 2023

 

 

Nakisa Inc. All rights reserved worldwide.