Application Developer

Certainly. You can run BW without R/3 implementation. You can use pre-defined business content in BW using your non-SAP data. Here you simply need to map the transfer structures associated with BW data sources (InfoCubes, ODS tables) to the inbound data files or use 3rd part tool to connect your flat files and other data sources and load data in BW. Several third party ETL products such as Acta, Infomatica, DataStage and others will have been certified to load data in BW.

International Demonstration and Education System. A sample application provided for faster learning and implementation.

There are number of technical reasons numbers of companies are planning to implement SAP. It's highly configurable, highly secure data handling, min data redundancy, max data consistency, you can capitalize on economics of sales like purchasing, tight integration-cross function.

Internal table:

It is a standard data type object, which exists only during the runtime of the program.

Check table:

Check table will be at field level checking. Value table: Value table will be at domain level checking ex: scarr table is check table for carried. Transparent table:

Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

The sequential files (processed on application server) are called datasets. They are used for file handling in SAP.

Convert the legacy system data to a flat file and convert flat file into internal table. Transfer the flat file into sap system called "sap data transfer". Call transaction(Write the program explicitly) or create sessions (sessions are created and processed ,if success data will transfer).

Performance - Heavy reporting along with regular OLTP transactions can produce a lot of load both on the R/3 and the database (cpu, memory, disks, etc). Just take a look at the load put on your system during a month end, quarter end, or year-end - now imagine that occurring even more frequently. Data analysis - BW uses a Data Warehouse and OLAP concepts for storing and analyzing data, where R/3 was designed for transaction processing. With a lot of work you can get the same analysis out of R/3 but most likely would be easier from a BW.

In order to use an ERP system, a business person must understand the business processes and how they work together from one functional area to the other. This knowledge gives the student a much deeper understanding of how a business operates. Using SAP as a tool to learn about ERP systems will require that the people understand the business processes and how they integrate.

OLAP - On line Analytical processing is a reporting tool configured to understand your database schema ,composition facts and dimensions . By simple point-n-clicking, a user can run any number of canned or user-designed reports without having to know anything of SQL or the schema. Because of that prior configuration, the OLAP engine "builds" and executes the appropriate SQL.

Mining is to build the application to specifically look at detailed analysis, often algorithmic; even more often misappropriate called "reporting.

Interfaces are huge problem, Determine where master data resides, Expensive, very complex, demands highly trained staff, lengthy implementation time.

Meta Data:

Data that describes the structure of data or MetaObjects is called Metadata. In other words data about data is known as Meta Data.

Master Data:

Master data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. Characteristics can bear master data in BW. With master data you are dealing with attributes, texts or hierarchies.

Transaction data:

Data relating to the day-to-day transactions is the Transaction data.

The Star Schema consists of the Dimension Tables and the Fact Table. The Master Data related tables are kept in separate tables, which has reference to the characteristics in the dimension table(s). These separate tables for master data is termed as the Extended Star Schema.

AWB stands for Administrator WorkBench. AWB is a tool for controlling, monitoring and maintaining all the processes connected with data staging and processing in the business information whearhousing.

Variables are parameters of a query that are set in the parameter query definition and are not filled with values until the queries are inserted into workbooks. There are different types of variables which are used in different application: Characteristics variables, Hierarchies and hierarchy node, Texts, Formulas, Processing types, User entry/Default type, Replacment Path.

Bex stands for Business Explorer. Bex enables end user to locate reports, view reports, analyze information and can execute queries.

The queries in workbook can be saved to there respective roles in the Bex browser. Bex has the following components: Bex Browser, Bex analyzer, Bex Map, Bex Web.

An ODS Object serves to store consolidated and debugged transaction data on a document level (atomic level). It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzed with a BEx Query or InfoSet Query. The data of an ODS Object can be updated with a delta update into InfoCubes and/or other ODS Objects in the same system or across systems. In contrast to multi-dimensional data storage with InfoCubes, the data in ODS Objects is stored in transparent, flat database tables.

1. natutal account while creating Ap invoice should be

Asset clearing account

2. Enable track as asset in AP invoice line distributions

3. The Invoice should be validated, accounted and transfered

to GL.

Note- mass additions will work only if transfer to run

program is run and ap invoice is transfered to GL.

SAP R/3 Source Systems, SAP BW, Flat Files and External Systems.

Create new code combination at General Ledger Super User -

Settup - Accounts - Combinations

Not possible.