Many times after loading the file from the application server to BW targets, we need to move it in a separate folder such as archive folder to avoid the same file being repeatedly processed. Also the archive folder will serve as a storage for history of all the files that were already loaded.This helps in referencing them at a later point in time if required.
We can write a program in the infopackage in BW to pick up a certain file based on its name from the application server and load it. This is required if there are multiple files in the same folder and only a certain file needs to be loaded out of those.
Suppose we have a scenario like this: Business uploads the files for multiple sales division in a folder in the application server – /usr/SAP/DEV/Reports/target_sales.csv.
SAP BW Modeling:
Multiproviders must always be used as a base for the query.
Every MultiProvider includes a characteristic called InfoProvider (0INFOPROV) in the data package dimension.
Queries can filter on this characteristic to restrict access to one or more specific underlying InfoProviders.
If your MultiProvider definition includes a large number of underlying InfoProviders (such as one per year, one per division, etc.) you can improve query performance by dynamically filtering on the 0INFOPROV characteristic.
A customer exit variable provides a flexible way to Continue reading “BW Development Standards Part 3: Data Modeling in Multiproviders and Infocubes”