System Configuration

Functional Administrators must set up the master data configuration for each system as follows:

  1. Set up the mode of operation and connection type for the system.
  2. If the system is connected to SAP, sync the system to pull master data from SAP.
  3. Configure the Module management table.
  4. Complete the Tax Configuration if it is used.
  5. Set up the configuration that is valid for all company codes in the system in Cross Company Code Configuration.
  6. Define or complete the configuration for each company code, as well as all of the configuration tables below it.

For more information about how to initially configure the System Configuration via SAP syncs and Excel, see Setting up Configuration for Systems Fully Connected to SAP and Setting up Configuration for Hybrid Systems.

Each system configured in the application can be configured with one of the following modes:

  • Fully connected mode: the application is fully integrated with an SAP ERP system, syncing master data from SAP and posting directly to SAP. Assets are maintained in FI-AA.
    • In this mode, there is an option of setting a future posting start date. The application syncs master data from SAP, but generates internal postings until the date is reached, at which time the application starts posting to SAP.
  • Hybrid connection: the application syncs master data from SAP, fetches certain live data from SAP (e.g., exchange rates and tax amounts), but only generates internal posting documents. All entries (including those for assets) are maintained in GL accounts.
  • Standalone mode: the application acts as a general ledger, using manually configured master data and generating internal posting documents. Note that Nakisa APIs can be called to update the master data.

If the application is connected to an SAP ERP, the systems must been synced. Subsequently, certain tables require you to attach values that you want to associate to each company (e.g., Unit of Measure), whereas other tables are automatically attached (e.g., Controlling Area). Note that for systems that are fully integrated with SAP where assets are maintained in FI-AA, the GL accounts are synced. If the system is operating in hybrid mode, the GL accounts for the assets must be manually configured.

Warning: Do not change tables that are synced with SAP. All of your modifications will be lost the next time the system is synced, and any manually added items will cause errors because they do not exist in SAP. For the tables that are auto-attached to systems and company codes, any changes will also be lost the next time the system is synced.

If the application has a system operating in standalone mode, the system configuration will have to be done completely manually (either directly in the Nakisa AdminConsole, or via Excel uploads). The actual configuration and the choice of which optional tables to use will depend entirely on the ERP system.

Tip: Use the search at the top of the configuration tree to find table names.

To modify the configuration, ensure that you are working in the Configure mode (at the top of the configuration tree). To see the flat view of all the configuration tables, use the View mode.

Note: The IDs of objects in the configuration tree cannot contain a comma, otherwise the object cannot be modified or deleted in the application.

Nakisa Lease Administration 2022.R2-SP1 © 2023



Nakisa Inc. All rights reserved worldwide.