(NLW-2.43) FAQ - NLS Writer

Contact

DataVard Ltd. was founded in London by a group of IT professionals with extensive knowledge of the SAP market and practical experience with implementing SAP products on a national and international scale. They noticed a growing gap as organizations where struggling to overcome issues created from using SAP Systems. As a result, DataVard was created and is growing dynamically, broadening its business to three different locations. We are constantly developing new tools and training more consultants to help more customers.
In addition to NLS for BW, DataVard also engages in System Landscape Optimization (SLO) and Data Quality Optimization for SAP systems.
DataVard Services
If your questions are not addressed in this manual, or you do not have access to our Customer Support Center, please contact us at OutBoard@datavard.com.

Customer Support

You can log into the Customer Support Center with the login and password you've received when you purchased OutBoard. If you have purchased OutBoard, but cannot find your data, send us an e-mail to support@datavard.com, you will be contacted by DataVard shortly and provided with a password.

Glossary of Terms

This glossary refers to SAP-related terminology dealing specifically with DataVard OutBoard.

DAP	Data Archiving Process, the process to archive data into an InfoCube and create a master table which contains the location of the individual archived tables.
RSA1	The Administrator Workbench for SAP BW (AWB) is the main tool for tasks in the data warehousing process. It provides data modeling functions as well as functions for control, monitoring and maintenance of all processes in SAP BW having to do with data procurement, data retention and data processing.
InfoCube	An InfoCube is a quantity of relational tables arranged according to the star schema: a large fact table in the middle surrounded by several dimension tables. Can function as both a data target and an InfoProvider.
InfoProvider	InfoProviders that contain real-time InfoCubes provide the data basis for BI Integrated Planning. Aggregation levels are a type of virtual InfoProvider and are created on the basis of a real-time InfoCube or a MultiProvider that contains InfoCubes of this type. Aggregation levels are specifically designed so that you can plan data manually or change it using planning functions.
DSO	Data Store Objects serve for storing of data from multiple sources to make analyses of data and simplifying reporting. Since data is coming from different sources data needs to be cleansed (e.g. redundancy) and consolidated (e.g. from business point of view). ODS/DSO objects store data in detailed level (atomic). There is a bigger portion of data available as opposite to data warehouse's cubes. ODS/DSO is combining key field (e.g. business document or its item) with data field (e.g. business document status and other properties) as a key figures. There is nothing multidimensional (no dimension neither fact tables) with ODS/DSO as with cubes. Data in ODS/DSO is stored in transparent (flat) database tables. ODS/DSO objects are reportable.
PSA	The Persistent Staging Area (PSA) is the inbound storage area for data from the source systems in the SAP Business Information Warehouse. The requested data is saved, unchanged from the source system.
Change Log	Change Log (CHLG) contains the change history for delta updating from the ODS Object into other data targets, such as ODS Objects or InfoCubes for example.
OutBoarding	OutBoarding is a process archiving data via OutBoard. Occurs in 3 phases and can be executed manually or included in a process chain. Near antonym: InBoarding.
InBoarding	InBoarding, or loading data from an archive into an InfoProvider – either their original InfoProvider, or a different one. Near antonym: OutBoarding.
Data Packet	Data Objects can be grouped into Data Packets. Data from different Data Packets can be processed in parallel.
InfoSource	In BW, an InfoSource describes the quantity of all the data available for a business transaction or a type of business transaction (for example, cost center accounting). An InfoSource is a quantity of information that logically belongs together, summarized into a single unit. It prepares consolidated data for updating to the data targets. InfoSources contain either transaction data or master data (attributes, texts and hierarchies). An InfoSource is always a quantity of InfoObjects that logically belong together in the form of the communication structure. There are two types of InfoSources: InfoSources with flexible updating and InfoSources with direct updating.