This chapter discusses the loading of data using the NLS Writer. This only concerns loading the data into an InfoCube. There are two ways to load the data: loading via DTP or via an InfoPackage.
This section provides a description of the NLS Writer process for loading data into InfoCubes via a DTP.
Because the DTP load takes place in packages, the data from the locked period is checked separately in each load package. If the package contains locked period data and the NLS Writer is enabled for InfoCubes, this process will pick out the locked records from the package. For the corresponding archiving request, a new package is created, into which new records are inserted. Subsequently, the rest of the records, which are not in a locked period, will be processed using the SAP standard way of loading data into InfoCubes.
This process also works for SPO InfoCubes.
This section provides a description of the NLS Writer process for loading data via an InfoPackage.
The InfoPackage can be connected to several InfoCubes, therefore the NLS Writer process is connected with transfer rules. This process is similar to loading the data via DTPs.
Because the loading takes place in packages, each data package will be checked for records from the locked period. If there are no locked records, the process will continue as the standard process. If there is locked data, then the process will generate a report similar to the transfer rule, but with the NLS Writer functions included. This process will create a new package in the corresponding NLS request, and records that are in a locked period will be moved into this package. The rest of the data will be transferred to the InfoCube using the SAP standard way.
When loading with the NLS Writer is enabled, it is something necessary to delete requests. Data stored in the database table is updated with this information from the loading request. If you decide to delete some requests, all the necessary information is used to find out which packages were created through the loading of these requests. Afterward, the process will delete the corresponding packages, and the process continues to standard deletion, which means the data that is not in the archive will be deleted. If you delete data archived with the NLS Writer, you can only delete loading requests one by one starting with the newest request. If it were possible to delete older requests first, this would lead to the problem that packages from archiving requests would be inconsistent. This would in turn cause a problem during the reloading of the archive.
