ERP Master Data

Accounting standards associated to the system.

When a lease component is created, the Standard Type is stored (and also copied to the activation group Classification). If this table configuration is changed, it only applies to newly created lease components.

Contains the defined alternative exchange rates.

Contains the defined assets.

The main criterion for classifying fixed assets according to legal and management requirements.

Separate areas of operations or responsibilities within an organization, and can be used for reporting purposes.

This table must configured correctly to be able to correctly sync GL accounts from SAP.

Contains the defined depreciation areas.

Contains the defined company codes.

An organizational unit within a company that can be used to represent a closed system for cost accounting purposes.

An organizational unit within a controlling area that represents a defined location where cost was incurred. Note that this table can only be synced once Controlling Area has been synced.

If a Cost Center is blocked in SAP, during an SAP sync the application updates the blocked Cost Center in the Cost Center table by setting the status to "Decommissioned" and the field Blocked to "true". The application will not allow users to add decommissioned Cost Centers to new contracts. If the Cost Center is unblocked on a subsequent SAP sync, the status is updated to "Active" and the field Blocked is set to "false". If the Cost Center is not blocked in SAP, then its status can be changed from "Active" to "Decommissioned".

Contains the countries configured in the application.

Contains the currencies available in the application.

Contains the defined depreciation areas.

The SAP Document Types that will be used to classify postings must be assigned to each company.

Contains the exchange rates used in the application for schedule generation, postings, and reports, based on the Exchange Rate Type table.

Use the Nakisa SAP Sync Bot to regularly sync this table to maintain the latest rates.

A key representing a type of exchange rate, which is used when translating or converting currency amounts for payments, accrual, charge, and depreciation amounts. This table also determines what is synced in the Exchange Rate table.

If the Translation Date Type is set to TRANSLATION_DATE, the application uses ROU Start Date for inception documents, the Modification Date for event documents, and the Posting Date for payment, accrual, and charges.

Note that you must always have the following entries:

• A row to define CONTRACT_CURRENCY to COMPANY_CURRENCY.
• A row to define a month-end Exchange Rate Type. The Source Currency Type and Translation Date Type can be set to N/A, and no Target Currency is required, as the Exchange Rate table will be synched with month-end rates for all valid currency conversions in the Exchange Rate Type table.

If parallel currencies are enabled in the System Financial Settings table, you must configure one exchange rate type entry per local currency (group currency). Note the following:

• You can add entries for SECOND_LOCAL_CURRENCY and THIRD_LOCAL_CURRENCY conversions.
• For group currency conversion, the source currency can be COMPANY_CURRENCY or CONTRACT_CURRENCY.

If required, you can configure additional reporting currencies for use only in Disclosure Reports. You can configure the following exchange rate types:

• CONTRACT_CURRENCY to REPORT_CURRENCY
• COMPANY_CURRENCY to REPORT_CURRENCY

Certain entries of this table are stored at different points in the contract life cycle: 

• When a contract is approved, the CONTRACT_CURRENCY to COMPANY_CURRENCY entry is stored.
• Whenever the financial schedules are generated during activation group inception, the entries for SECOND_LOCAL_CURRENCY and THIRD_LOCAL_CURRENCY are stored. If the financial schedules are regenerated in an activation group draft, the stored value is used.

For information on how exchange rates are used, refer to the Nakisa Lease Administration User Guide.

Contains the defined fiscal periods, that are then attached to Fiscal Variant. Note the following:

• Year can be set to a specific year, or set to 0 to indicate the period is year independent. If the associated Fiscal Variant has the field Year Dependent set to "false", then the Year field is ignored for schedule generation. If the Year Dependent field is set to t "true", make sure you define an extra period at the beginning, which ends one day before the desired start of date of the first period.
• Month and Day indicate the last day of the period.
• Year Shift can be set to -1 (the Fiscal Year is the year before the Posting Date), 0 (no year shift), or 1 (the Fiscal Year is the year after the Posting Date).

Contains the fiscal variants defined for the system.

In the Relations section of the page:

• Assign all of the Fiscal Periods for this Fiscal Variant.
• Assign the selected Fiscal Variant to one or multiple Companies, but note that a Company can only have one Fiscal Variant assigned.

The application compares the Posting Date to the different Posting Periods to determine the Fiscal Year and Fiscal Period (where the Month and Day fields identify the last day of the period).

The column Year Dependent indicates if the schedule generation uses the Year field in the Fiscal Period definition or not. It does not affect the Fiscal Year used in postings.

Note that the column Is Calendar Year is not used. To use a regular calendar, users can select "Regular Calendar" Calendar Type on the contract Accounting page. Otherwise, if users must select "Fiscal Variant" for contracts, you must assign NAK1 to the Company with every Fiscal Period defined to account for leap years, or create and assign Fiscal Periods to your regular calendar Fiscal Variant.

When a contract is approved, this configuration is stored. If this table configuration is changed, it only applies to newly approved contracts.

Costs are grouped into the functional areas where they were incurred.

The General Ledger (GL) accounts to which the application will post.

Internal orders are used to monitor costs of an organization. These internal orders must be statistical. An internal order type must be selected for each internal order.

Contains the defined locations.

Note: This table is reserved for future use.

Used for cost collecting within the project.

The list of vendors to whom amounts are payable for goods delivered or services performed.

Used to block an open item for payment transactions.

Specifies how payments are to be made.

Note: The Display ID shows the Payment Method type and the country it is associated to.

The payment arrangements required by the supplier.

Contains the defined plants.

An organizational unit that is used for internal control. One Profit Center object is created per Controlling Area (where the same ID is allowed).

Note that this table can only be synced once Controlling Area has been synced.

A set of interrelated tasks and subtasks that define an initiative. The tasks and sub-tasks in a project are synonymous with network activities and work breakdown structure (WBS) elements.

The list of purchase orders that are attached to the company code.

An organizational unit that procures materials and services, negotiates purchasing conditions, and is responsible for purchasing transactions.

Contains the defined regions.

Information as to why the document was reversed.

A division of a company that can create its own financial statements for external reporting.

Contains the defined tax codes.

A jurisdiction is the taxation authority that imposes the tax. Each jurisdiction is identified by a tax jurisdiction code. This code provides the location for the transaction to be taxed. The tax jurisdiction code is a key, which together with the tax code and other parameters, determines the tax amount and the way in which payment of the entire tax amount is divided between different tax authorities.

Contains the list of Transaction Types that are used in the Transaction Type Determination table (configured per company code and accounting standard).

Contains the defined transfer variants.

Contains the defined unit of measures.