SAP Lease Administration by Nakisa 4.0 Connected vs Disconnected mode.
As per the product architecture SAP Lease Administration by Nakisa was designed to run in two modes: Connected mode and Stand alone.
- Connected mode. The solution uses native integration with SAP ECC or SAP S4/HANA systems calling standard RFCs and BAPIs which are externally exposed (remote enabled). As per design it is not required to install add-ons in SAP backend system. However, in order to perform all actions from the solution, as it is explained in the solution guides, it is required to expose a specific BAPI in SAP backend, especially for Asset transfer process. In SAP ECC there is an interface available BAPI_ASSET_TRANSFER_POST which is not remote enabled, therefore it is explained in the guides how to enable it and used it in the configuration.
In order to consolidate the information from multiple systems the solution was designed in a way so to propagate everywhere the relationship between business system and company code, as well as the follow-on relationships between company code and other master data used.
System definition is very important task as part of the configuration process. It drives how data will be stored in the solution as well as internal procedures for master data generation and transaction data generation.
Current design supports creation of multiple systems.
There is no technical limit how many systems can be created. However, if the number of systems is too big it means data volume expected will be too big so big data management processes/ tools should be considered as part of the implementation (i.e. usage of HANA DB).
In case of connected mode, the system provides an option to sync master data from your backend system using RFC/BAPI calls. Keep in mind there are other options available as well such as: excel upload and manual data creation.
- Stand Alone mode. If during system setup, system type is selected to be NAK, it means this particular system will run in disconnected mode or so-called stand-alone mode. In this case master data sync is not available because there is no RFC destination setup. This is a mode used very often in order to quickly setup the system and run calculations without posting to any backend systems. Moving from connected to disconnected mode is easy but vice versa is required couple of actions mainly related to master data used in the process. In stand alone mode the system is creating own master data (i.e. assets) and stores all transaction data in so called TH/TI tables (i.e. TH_AssetCapitalization). This data can be easily exported to excel using transaction data reports.
- Hybrid mode. It is a way to use the system during transition period. During this period, it is possible to connect SAP Lease Administration by Nakisa 4.0 to a backend system in order to sync master data but at the same time all postings to this backend system can be blocked. Posting control is done at company code level using posting start date. If the date is setup in future, all postings for this company code will be only locally registered. Nothing will be send to SAP backend. This allows companies to do gradual onboarding for the initial system conversion process.
