Showing posts with label SAP. Show all posts
Showing posts with label SAP. Show all posts

Wednesday, June 24, 2009

SAP Netweaver Capabilities

SAP Jave AS supports J2EE standard, version 1.3 and 1.4


SAP Web Application Server


ABAP WorkBench
- ABAP Editor
- ABAP Dictionary
- Screen Painter
- Menu Painter
- Function Builder
- Class Builder

ABAP Categories
- Screens (With ABAP Dictionary integrated inthe system, automatic consistency checks for screen input fields (type, foreign key, fixed value checks).
- Lists (display data using minimum programming effort)
- Classes (similar to a function group but multiple instances. contains data objects (attributes) and functions (methods))
- Function modules (actively integrated modularization units with an interface. They can be called primarily from within programs or other function modules. elements are: import paramenters, Export parameters, Changing parameters, Exceptions)



Features of SAP Web AS Platform
- Server-based and Client-based Web Applications
- ABAP
- Java
- Business Communication Services
- Connectivity
- Database and Operating Systems
- SAP Knowledghe Warehouse

SAP Exchange Infrastructure (XI)


SAP Integration Builder
- Central development environment for the development of all design objects for theintegration Repository at design time.
- Defines all configuration objects for the integration Directory at configuration time


Prerequisites to Design


Business Process Components


Business processes are initially designed in the Integration Builder and only utilize abstract messages. The processes are finalized and configured in the Integration Directory. At the execution time, the processes are executed within the Business Process Engine (BPE)

Cross-Component Business Process Management
- Provides integrated capability to design, model, and execute complex distributed interfacing scenarios involving homogenous and heterogeneous systems


Components of BW
- Enterprise-wide data warehousing
- Business intelligence platform
- Business Intelligence Tools

Technical Components of SAP NetWeaver Master Data Management
- SAP EP
- SAP MDME Console
- SAP MDME Client
- SAP MDME Importy Manager
- SAP MDME Syndicator
- SAP Exchange Infrastructure
- SAP Business Warehouse

Architecture of SAP NetWeaver MDM


Master Data Management

Core Components of SAP NW MDM
- Master-data consolidation
- Master-data harmonization
- Central master-data management
Developing Portal Content
-SAP EP Portal Content Studio
- SAP NetWeaver Visual iComposer
- SAP NetWeaver Developer Studio (Web Dynpro)
- SAP NetWaver Developer Studio (Java + PDK Perspective)

Tuesday, March 24, 2009

Business Objects Crystal Enterprise 10 Business Views

Business Views Overview
Business Views is a multi-tier system that enables companies to build comprehensive and specific Business Views objects that help report designers and end users access the information they require.

Using Business Views, you can integrate data from disparate sources. You can bring together data from multiple data collection platforms across application boundaries so that the differences in data resolution, coverage, and structure between collection methods are eliminated.

Business Views objects consist of the following:
• Data Connections
• Dynamic Data Connections
• Data Foundations
• Business Elements


Architecture



















Business Views is comprised of three tiers:
the client tier, the business tier, and the data tier.
• Client tier
The client tier consists of any Crystal client application that accesses the Business Views that are stored and organized in the business tier.

• Business tier
Business Views objects—a collection that includes Data Connections, Dynamic Data Connections, Data Foundations, Business Elements, and Business Views—are a part of this tier. Using the Business View Manager, you specify the settings and conditions for the various objects so that the client tier has access only to specific information from the data tier.

Business View Manager
The Business View Manager enables you to create and modify Business Views and the various objects that make up these Business Views. The administrator uses this designer to specify different Data Connections, to set security, and to control access to the data found within the different data sources in the data tier. This thick-client designer is the only part of Business Views that administrators interact with directly. End users access the data specified within the Business View Manager through their Crystal client application, such as Crystal Reports (via the Crystal Repository) or through the Report Application Server.

Business Views objects
Business Views objects include the following: Data Connections, Dynamic Data Connections, Data Foundations, Business Elements, and Business Views.

Data Connection
Data Connections specify and define the data sources for a Business View; they define how these data sources are made available to users. Thus, a Data Connection is a connection object, and an administrator can apply security to this object. Each Data Connection contains information that describes the physical data source, such as the server and data being accessed, the logon credentials, and the type of server being accessed.

Dynamic Data Connection
A Dynamic Data Connection is a collection of pointers to various Data Connections. An administrator or user is able to select which Data Connection to use through a parameter.
A typical scenario involves the migration of data from a development system to a test system, and finally, to a production system. In this scenario, a report is run against a development system, and then, when the data is migrated to a test system, the same report is run against the test system’s data. The only change required is that the Dynamic Data Connection’s settings must be updated so that it points to the test system’s Data Connection. Finally, when the test system’s data is migrated to the production system, the same report can again be run against the production system.
Note: When users refresh reports that are based on a Dynamic Data Connection, they are prompted to specify which of the available Data Connections to use.

Data Foundation
A Data Foundation consists of collections of tables and fields. Default table joins are defined at this level. Administrators can secure Data Foundations using the standard Crystal Enterprise security model, which includes View and Edit rights. The primary use of Data Foundations is for data abstraction: administrators control which tables and fields users can or cannot access when these users are designing or viewing a report.

Business Element
A Business Element is roughly equivalent to an OLAP dimension or logical view; that is, this object is a logically related collection of data fields that are based on a Data Foundation. These fields can be organized into a hierarchical structure within the Business Element. The most common example is a hierarchical structure that contains the following fields: Country, State or Province, and City. Business Fields in Business Elements can be aliased to support data abstraction and to facilitate report design. Administrators can secure Business Elements through the standard View and Edit rights.


Business View
A Business View is a logical collection of Business Elements. A Business View provides the highest level of data abstraction for end users. Users see Business Views as abstract database connections, and the contained Business Elements as virtual tables that, in turn, contain Business Fields. Administrators can secure Business Views through the standard View and Edit rights.
A Business View consists of the following objects:
• One or more Data Connections
• One optional Dynamic Data Connection
• One Data Foundation
• One or more Business Elements
Note:
• End users can access Business Views through applications such as Crystal Reports and the Report Application Server.


• Data tier
The data tier consists of data sources, such as multiple databases on different machines that provide the data for the business tier.
Usage Scenario


















Architectural workflow

Saturday, March 21, 2009

Business Object XI R2 Recommended Settings for WebLogic

The recommendations in this guide are based on a multi-tier architecture.














Windows XP Professional
Environment
Windows XP Professional Edition Service Pack 2
MDAC 2.8 is required.
Acrobat Reader 7.0

Hardware component
Number of CPUs - 1
Type of CPU - Pentium III 733MHz minimum
Memory - 256 MB recommended minimum
Disk (Size) - 3 GB of free space minimum, 30 GB for IDE
Network Desktop to RDBMS - 100Mbps
Network Card Type - Ethernet
Network Card Number - 1
File System Type - FAT32 or NTFS
Swap Space - Default

Internet Explorer
Environment
Internet Explorer 6.0

SP1
SUN Java Runtime
Environment 1.4.2.05
No Microsoft JVM supported.
Internet Explorer 6.0

SP2
SUN Java Runtime
Environment 1.4.2.05
No Microsoft JVM supported.

Parameters
Security Settings

To access the Security Settings in Internet Explorer:
1. Select Tools > Internet Options > Security.
2. Click Custom Level.
3. In the Security Settings box, set the following parameters:
Advanced Settings
To access the Advanced Settings in Internet Explorer:
1. Select Tools > Internet Options > Advanced.
2. Select the following options:
• Under Printing, select Print background colors and images.
• Under Browsing, select Always send URLs as UTF-8 (requires
restart).

Server Tier Architecture
WebLogic application server


Environment details
WebLogic 8.1 Service Pack 4 with JDK 1.4.2_06
If installed on HP-UX, the following patches must be
installed:
• PHNE_30367 Cumulative STREAMS patch
• PHNE_31247 Cumulative ARPA Transport patch

Parameter Recommended setting/ value
Thread Count 45
Socket Readers 50
Stuck Thread Max Time Set this value to the Maximum active time
specified for the Web Intelligence cluster.
Stuck Thread Timer Interval 60
Threads Increase

BusinessObjects Enterprise Server operating
system

Solaris
Solaris 10 minimum installation with the following patchs:
• SUNWgzip (The GNU Zip (gzip) compression utility)
• SUNWzlib (The Zip compression library)
• SUNWscpu (Source compatibility)
• SUNWbash (GNU Bourne-Again shell (bash))
• SUNWbcp (SunOS 4.x Binary Compatibility)
• SUNWxcu4 XCU4 utilities
• SUNWxwfnt (W Window System required fonts)
• SUNWxwplt (X Window System platform software)
• SUNWlibC (Sun Workshop Compilers Bundled libC)
• SUNWuiu8 Iconv modules for UTF-8 Locale
• SUNWulcf UTF-8 Locale Environment Common Files
• SUNWmfrun (Motif RunTime Kit)
• SUNWxwice (ICE package)
Use J2SE SDK 1.4.2 (1.4.2.02 or later is recommended).
bash installed
To check the OS version, use the following command:
uname -a
To check the patch level, use the following command:
showrev -p egrep "108528108827108434109147"

Parameter Value
Shell /bin/sh or /bin/ksh or bash
User account Recommended use of a non-root, dedicated user
account for Administration tasks.
user setting (limit,
ulimit)
• data segment unlimited
• file size unlimited
• open file = 1024
• stack size = 8192
• virtual memory unlimited
• cpu time unlimited
LD_LIBRARY_PATH LD_LIBRARY_PATH should be empty to avoid
conflicts with Business Objects server settings
(defined in the MyWebiEnv.sh file).
PATH PATH should be restricted to /usr/bin to avoid
conflicts with Business Objects server settings
(defined in the MyWebiEnv.sh file).

Database Tier Architecture
Oracle
OracleServer 9.2.06 Enterprise Edition
OracleServer 10.1.0.3 Enterprise Edition

Hardware component Value
Number of CPU’s 4
Type of CPU 750 MHz minimum
System bus: 150Mhz min
Memory 4 GB
Disk (Size) 18 GB x 8
Disk (Type)
Note: This specific
configuration of disk
controllers is not
required. It is an
example of how to
configure your disks.
SCSI controller #1: Operating system, database
server software, paging file
SCSI controller #2: Database server journal files
SCSI controller #3: Dedicated to CMS tables
SCSI controller #4: Dedicated to CMS tables
SCSI controller #5: Dedicated to Data source
SCSI controller #6: Dedicated to Data source
SCSI controller #7: Dedicated to Database server
dictionary, undo information and sort space
SCSI controller #8: Dedicated to Database server
dictionary, undo information and sort space
Network (middle-tier to
database)
100 Mbps
File System Type RAW
Swap Space 4GB
Network Card Type Ethernet
Network Card Number 1

Parameter Definition "Oracle 9" "Oracle 10"
db_block_size These parameters set
the RDBMS cache size
8192
db_block_buffers 183500 n/a
db_file_multiblo
ck_read_count
Facilitates the “full
table scan”
64 n/a
shared_pool_size Storage area for
parsed SQL
67108864 n/a
log_checkpoint_
interval
Accelerates log 10000 n/a
Processes Maximum number of
clients
512
log_buffer Accelerates log 163840 n/a
sort_area_size 3 MB n/a
TCP/IP Port 1521 n/a
sga_target n/a 384 MB
pga_aggregate_
target
n/a 128 MB
undo_management n/a Undo
undo_tablespace n/a Undo

Friday, March 20, 2009

SAP EP

What is an Enterprise Portal
- The portal offers a single point of access to SAP and non-SAP information sources, enterprise applications, information repositories, databases and services in and outside your organization—all integrated into a single user experience.
- Via SAP Portal Organizations can provide their employees, supply chain partners, customers, and other communities with immediate, secure, and role-based access to key information and applications across the extended enterprise.
- Enterprise Portal is a web based business-critical system
-- Integrated information view and business applications
-- Unifies and aligns people, information and business processes with Knowledge Management Systems and collaboration.
-- A collaborative environment
Classes of Portals
- Information Portals
- Functional Portals
- Industry Specific Portals
- Enterprise Portals
SAP Enterprise Portal Architecture & Technology
The portal platform contains the following components:
- Portal Server
- Content Management and Text Retrieval and Information Extraction (TREX) component of the Knowledge Management platform
- Connector Framework
- Unification Server































Entrprise Portal Building Blocks












Enterprise Portal – Functional Components


SAP CRM

Customer Relationship Management is
- a basic approach which makes the customer the focal point of the company and its business processes.
- a carefully thought out strategy and company philosophy combined with supportive technical tools and software, in order to identify possible customers, acquire customers and retain customers.

Business Architecture
















- OLTP = On-line Transaction Processing
- BW = Business warehouse
- APO = Advanced Planner and Optimizer

System Architecture






















Security Architecture











Master Data
- Products are differentiated according to product categories
- Products catalogs are used in SAP internet sales.

Business Transactions
Activity
– An activity is a transaction type used to record information resulting from interaction between business partners, undertaken at any time during the customer relationship life cycle. (e.g. telephone call, customer visits)
– Activities can be planned, tracked, documented, or administered by user or user group.
– Activities can be created and changed in the calendar. The calendar can be synchronized with MS-Outlook.

Lead Management
–Lead generation
–Lead qualification
–Lead reporting

Opportunity Management
–Can serve as a central shell for the entire sales process
–To generate as many orders as possible
–To make sales process more transparent

Sales orders
–Product pricing and product configuration via the Internet Pricing and Configurator (IPC) is supported.
–Real-time Available-to-Promise (ATP) checks by using SAP Advanced Planner and Optimizer (APO) is possible.

Contracts
–To increase customer loyalty
–Sales contracts; Service contracts; Leasing contracts

Wednesday, March 18, 2009

SAP BPM

Process Integration Challenges
- System Landscapes – Separate business units with independent IT systems in heterogeneous landscapes
- End-User Integration – Role-based access to actions (tasks) and interaction (collaborative processes)
- Enterprise Application Integration – Interacting business applications within and across enterprise boundaries
- B2B Integration – Interacting organizations, business partners, customers, vendors, and suppliers across the value chain

BPM Components for modeling and implementation
- ARIS Process Modeling – Company value chain; Process design and analysis; SAP Reference processes - Service Infrastructure
– BPM operational services; Solution monitoring; Service level reporting; SAP process content - Process Integration
– Model and execute automated processes across and within applications; SAP and non-SAP process integration content
- SAP Applications – Components; Composites; Engines; Business objects BPM Components

BPM Components
















ARIS House
- Organizational units/Organizational chart
- Data/Technical terms model
- Function/Function tree
- Control/Process
- Output (Product/Service)/Product tree

ARIS Modeling Levels
- Overview models
- Rough models
- Detail models















SAP Solution Manager Functions












SAP Business Workflow













SAP Workflow Architecture













ccBPM Architecture: Relationship Among Objects













- Business Process Engine located in Integration Server executes the integration processes
- Design Time - (Integration Builder)
- Runtime – (Integration Server)


ccBPM Integration in SAP Exchange Infrastructure


SAP Enterprise Data Management

Overview
Improved Business Efficiencies occur when Governance is combined with Strategy.














Enterprise Data Management Strategy

















EDM Architecture




SAP XI / PI Create Inside-Out Services


Overview



- Business application in java (POService.java) to handling purchase order requests
- Two Java bean classes for purchase order and purchase order line item (purchaseOrder.java, purchaseOrderLineItem.java)
- New->Project->Java->Java Project (yes to java perspective)
- Package: com.wavecross.sn.bl New->Package

Create a new Java class

Name: POService.java

package com.wavecross.sn.bl;
public class POService {
public POService() { }
public void handlePORequest(PurchaseOrder po) {
// process purchase data // ..
}
}

PurchaseOrderLineItem.java
public class PurchaseOrder implements java.io.Serializable { private String id;
private PurchaseOrderLineItem [] items;
private String buyer;
private String seller;
}

PurchaseOrder.java
package com.wavecross.sn.bl;
public class PurchaseOrderLineItem implements java.io.Serializable {
private String id;
private String product;
private String amount;
}

Both implement
java.io.Serializable
for Web Service usage.
The getter and setter methods
can be generated using the
context menu

Generating the Web Service
- Change Web Services Perspective: Window->Open Perspective->Java Explorer
- In context menu of POService.java, New->Web Service
- Enter WS name, modify config (SOAP)
- Wizard Created:
- Virtual Interface (VI)
- Web Service Configuration (WSC)
- Web Service Definition (WSD)

Activating and Deploying Web Service
- To deploy WS app to SAP WAS, first ensure connectivity info for J2EE engine is correctly set up.
- Window->Preference->SAP J2EE Engine
- The app can now be
- Deployed using the
- Deploy option in the
- Context menu of
- InsideOut.ear

Develop the Mediated Web Service
- Capture the WS metadata into SAP XI and then expose the metadata as a mediated Web Service
- Download WSDL using WebServices Navigator (used to view a listing of deployed WS in SAP WAS)
- Open: http://[hostname]:[port]wsnavigator/enterwsdl.html
- Click POWebService to see a overview
- Standard WSDL for all WS frameworks. SAP WSDL has additional features

Create Namespace in XI
- Design objects are built in Integration Builder: Design tool
- http://:/rep/start/index.jsp
- XI uses namespaces to avid naming conflicts. All design objects be part of Software Component Version (SCV)
- This is the only way by which the XI design objects can be shipped or moved from a dev system to a test system (SRM SERVER 5.5 SCV used)
- New namespace: http://yourcompany.com/xi/XI/InsideOut
- SCV context menu->Open

Create External Definition in XI
- SAP SRM SERVER->http://yourcompany.com/xi/XI/InsideOut->Interface Objects->External Definition
- Context menu->New->Enter SRM2SN_POService
- Select imported wsdl for Category (porttypes/POWSConfig_POWebServiceVi_document.wsdl
- Save and make a note of messages

Activate changes
- Objects edited or saved are not available for XI Integration Directory
- Changes must be activated
- Changed objects are organized by SCV in Change Lists tab

Create Message Interfaces in XI
- Message interfaces are the standard and platform-independent format for representing interfaces in XI
- XI is the broker, needs inbound and outbound interfaces. Modes: Synchronous or Asynchronous; types: Inbound, Outbound, Abstract
- InterfaceObjects->Message" hyperlinktype="url">InterfaceObjects->Message" target=_parent>http://yourcompany.com/xi/XI/InsideOut->InterfaceObjects->Message Interface
- New and enter name, select Category and Mode (Outbound)

Generate WSDL for Mediated Web Service
- All message interfaces can be exposed as mediated Web Services
- WSDL can then be used by clients to consume the Web Service
- Configuration objects are built in XI’s Integration Builder:Configuration tool
- http://[hostname]:[port]/rep/start/index.jsp
- Configuration objects to be built: sender and receiver Communication Channels, Receiver Determination, Interface Determination, and Receiver Agreement.
- After this, the Web Service Wizard can be used to generate the WSDL for mediated Web Service
- Tools->Define Web Service menu

- Specify the URL of Web Service
- http://[hostname]:[port]/XISOAPAdapter/MessageServlet/channel=[party]:[ServiceName]:[ChannelName]

- Make the selection
- Enter: Service-POService; Interface Name – SN_POService_Out; Interface Namespace – http://yourcompany.com/xi/XI/InsideOut

Tuesday, March 17, 2009

SAP MDM Modeling

Data Management Strategy
Formal architecture toward a common context for data to be viewed and managed as any other asset within the enterprise











MDM Repository Stucture
- Main table – One for each repository. In product repository, be the product including a field for each general valid piece of information
- Sub-tables – Lookup tables (value/customizing)
- Object tables – Images/text blocks and PDFs
- Special tables – Masks, families, image variants, relationships, roles, users, data groups

Main Table (flat table)
- A repository must only have one main table
- All other tables support it (directly-flat lookup or qualified lookup; / indirectly-tables linked to qualifier table & qualifier table linked to main T)
- Main table fields reference tables:
-- Flat lookup
-- Qualified lookup
-- Hierarchy
-- Taxonomy
-- Image, sound, video, PDF, and external binary object
-- Text block, copy blocks, and text HTML
-- Special tables

Flat & Qualified Lookup Table
- Flat tables (sub-table) can be multi-valued
- Qualified tables- Stores lookup records; Supports qualifiers; Is always multi-valued. Can be used for search

Hierarchy and Taxonomy Tables
- Hierarchy - sub-table orgainzing infor in a hierarchy (record related to parent/sibling record; contains lookup info for fields in main T; ordered sequence)
- Taxonomy- classification scheme that defines categories and subcategories.

Special Tables
- Families – Further partition records in taxonomy into smaller groups based upon values of other fields and/or attributes
- Relationships – Define different product-level relationships

Keep in mind...
- Many table and fields properties cannot be changed after creation (Table type; field type; multilingual option; Lookup table)
- Null values are not blank values
- Maintainable properties: (Name, code, Description, Display fields; Unique fields; Key mapping)

Repository Objects
- Taxonomies - general term classification scheme (hierarchy table, special lookup table) – created and managed using MDM Data Manager in Taxonomy mode.
- Attributes – characteristics in category (is a field applied to a subset of the records in a table)
- Product is assigned to category - Typical categorization of products is reflected in a taxonomy

- Flat / hierarchy lookup tables
- Taxonomy Lookup tables
- Qualified link tables – larger number of records
- Non-lookup sub-table = Relationship functionality (used for one-to-many relationship between main table records and sub table records

Relationship in Data Manager
- Parent/Child Relationship – Relates a group of records that are not equivalent (eg. Assembly)
- Sibling relationship – Relates a group of main table product records that are equivalent (eg. Cross sells)

Field Types & Properties
- Each table must have at least one Display Field (Display Field - value used as lookup field value; node name for the record; name of record in Product Relationships dialog box)
- Multiple Display Fields value is combination values separated by a comma
- Each field name must be unique within a table
- Items can be re-ordered

Field Details
- Variety of compond and structured data type (table types) specifically suited for managing info in a product repository
- Text Normalized – stores the actual text value, but uses normalized value for sorting and searching (upper-case with non-alphanumeric removed)

SAP BI / BW

What is Business Intelligence
BI solutions consolidate enterprise data and information including supply-chain and customers, enable reporting and management of key metrics, and analyze data to optimize your business

BI is used at the enterprise level and in departments/functions
- supply-chain
- sales and marketing
- customer service
- finance
- product development
- business operations
- partner relationships

SAP Business Intelligence

Data Warehousing
- It supports the complete process from data load, transformation, data integration, consolidation and cleansing to data provision for analysis and interpretation of consistent information. Includes the following areas:
−- Extraction, Transformation and Load (ETL)
−- Data Warehouse Management
−- Data Modeling

Business Intelligence Platform
- Serves as the technological infrastructure to support information access and comprehensive analytics. It includes the following areas:
−- OLAP
−- Alerting
−- Data mining
−- Open Analysis Interfaces

Business Intelligence Reporting Tools
- It provides a comprehensive set of tools such as query, reporting and multi-dimensional (OLAP) analyses to support collaborative decision-making for analysts, executives and information consumer. It includes the following areas:
−- Query design
−- Reporting and Analysis
−- Web Application Design

Multidimensional model: Classic Star Schema
- Multi-dimensional data models are needed for the creation of data warehousing or OLAP applications, in other words, for analytical applications.
- The classic star schema is the most frequently used multi-dimensional model for relational databases. This database schema classifies two groups of data: facts (sales or quantity, for example) and dimension attributes (customer, material, time, for example).

Example:
Fact table can be associated to multiple Dimention Tables (Customer Dimension Table, Material Dimension Table, Time-Dimension Table)

The SAP BW Star Schema
The multi-dimensional model in SAP BW is based on the SAP BW star schema, which was developed as an enhanced (refined) star schema as a response to problems experienced with the classic star schema. Each dimension table has an SID.

InfoObject
- InfoObjects are the "smallest available information modules" (=fields) In SAP BW: These can be uniquely identified with their technical name.
- As components of the Metadata Repository, InfoObjects contain the technical and specialist information for master- and transaction data in SAP BW.
- InfoObjects are used throughout the system to create structures and tables. These enable information to be modeled in a structured form in SAP BW.
- InfoObjects are used for the definition of reports, to evaluate master and transaction data.


InfoObjects are divided into the following classes:
Key Figures

Key figure InfoObjects provide the values to be evaluated.
Examples:
Quantity ( 0QUANTITY)
Amount(0AMOUNT)

Characteristics
Characteristic InfoObjects are business reference objects, which are used to analyze key figures.
Examples:
Costcenter(0COSTCENTER)
Material (0MATERIAL)

Time Characteristics
Time characteristics form the time reference frame for many data analyses and evaluations. They are delivered with Business Content. It it not possible to define your own time characteristics.
Examples:
Calendar Day (0CALDAY)
Calendar Year (0CALYEAR) or Fiscal Year (0FISCYEAR)

Units
Unit InfoObjects can be specified alongside the key figures. They enable key figure values to be partnered with their corresponding units in evaluations.
Examples:
Currency unit ( 0CURRENCY)
Value unit ( 0UNIT)

Technical Characteristics
These characteristics have an organizational function within SAP BW.
Examples:
Request ID (0REQUID)
Change ID (0CHNGID)

DataStore Object (DSO)
- DataStore Object serves as a storage location for consolidated and cleansed data on a atomic level.
- Unlike multidimensional data storage using InfoCubes, the data in DataStore is stored in transparent, flat database tables.

Types of DSO
- Standard
- Direct Update
- Write-Optimized

InfoCubes
- InfoCubes are the central objects of the multi-dimensional model in SAP BW. Reports and analyses are based on these. An InfoCube describes a self-enclosed dataset for a business area from a reporting view, that is, for the reporting end user. Queries can be defined and/or executed in the basis of an InfoCube.

Types of InfoCube:
- Basic Cube
- Virtual Cube

Basic Cube
- A Basic Cube consists of a quantity of relational tables arranged together in a star schema.
- Fact table:
-- A Basic Cube consists of precisely one fact table, in which key figure values are stored. A fact table can contains a maximum of 233 key figures.
- Dimension tables:
-- A Basic Cube usually has at least three dimension tables.
−-- Units dimension table
−-- Data package dimension table
−-- Time dimension Table.


- Data package and time dimension tables are always present in a Basic Cube.
- The units dimension table only exists if at least one key figure is of type "amount" or "quantity“.
- The dimension tables do not contain the characteristic values but the corresponding SID keys/values.

Business Content
- SAP offers a predefined information model that helps to control and optimize the individual process areas.
- It collects and structures information and prepares it for further use. In doing so, Business Content is based on an information model that is preconfigured and based on roles and tasks stemming from consistent metadata.

Business Content consists of the following objects:
- Extractors
- DataSources (extraction structures)
- InfoObjects
- InfoSources
- InfoProviders (for example, InfoCubes and DSO objects)
- Queries
- Templates (Web-based reporting)
- Roles

SAP BI Enterprise Architecture
- Application & External Reports Layer
- Data Mart Layer
- EDW - Data Staging Layer
- EDW - Data Source Layer
- Sources (SAP R/3, ECC, Legacy Systems)



SAP XI / PI

What is SAP XI / PI
Exchange Infrastructure/Process Integration in SAP NetWeaver (SAP NetWeaver XI/PI) enables you to implement cross-system processes. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other. SAP Exchange Infrastructure/Process Integration is based on an open architecture, uses open standards (in particular those from the XML and Java environments) and offers those services that are essential in a heterogeneous and complex system landscape:
- Modeling and design of messages, transformations, and cross-component integration processes
- Configuration options for managing collaborative processes and message flow
- Runtime for message and process management
- Adapter Engine for integrating heterogeneous system components
- Central monitoring for monitoring message flow and processes
SAP NetWeaver XI/PI supports internal company scenarios and cross-company scenarios.














Current Version: SAP PI 7.1



Position on SAP NetWeaver Technology Map (End-to-End Process Integration)













Adapter Architecture
Integration Server
- Business Process Engine
- Integration Engine
- Central Adapter Engine (Adapter Framewor, Resource Adapter)

Partner Connectivity Kit
- PCK Configuration and Monitoring
- Adapter Framework, Resource Adapter

Adapter Framework
Supports J2EE Connector Architecture (JCA)
- JCA is standard architecture for connecting the J2EE platform to Enterprise Information System (EIS), eg. ERP, DBMS, etc.
- A Resource Adapter plugs into an application server, providing connectivity between the EIS and a Java application
- JCA enabled Adapter Framnework provides defined interfaces to which both SAP adapters and 3rd party adapters can conform
- JCA is a widely accepted standard that 3rd party adapter providers are familiar with



Adapterdelivered by SAP
Technical Adapters
- File/FTP (File Systems / FTP Servers)
- JDBC (RDBMS systems)
- JMS (Messaging systems, e.g. MQSeries, SonicMQ)
- SOAP (wEB sERVICES)
- Plain HTTP
- Mail (Mail Servers via SMTP, IMAP4, POP3)
- SAP Business Connector (SAP BC)
- Marketplace (mySAP Marketplaces)

Application Adapters
- RFC
- IDoc

Industry Standard Adapters
- RNIF 2.0 (RosettaNet)
- RNIF 1.1 (RoseTTaNet)
- CIDX (RNIF 1.1)

Proxies vs. Adapters
Proxies
- Outside-in development approach
- Interfaces designed centrally in Integration Repository
- Connect new SAP applications
- Native connectivity to Application system (adapter-less)

Adapters
- Inside-out development approach
- Interface semantics externally pre-defined
- Connect existing (legacy) systems
- Specific wire protocol

XI / PI BPM Process Model






Monday, March 16, 2009

SAP - FI

FI Overview
- FI is concerned with accounting for what a company buys, sells, owes, and owns
- FI is the cohesive force, or backbone, that ties together all other modules
- All other modules integrate in some way with FI, and it requires cross-functional processing
- Options within the configuration set-up of SAP provide FI with a lot of flexibility


















Financial Accounting is primarily concerned with:
•General Ledger Accounting
•Financial Reporting
•Processing of financial data from other modules with which it is integrated
•Accounts Payable
•Accounts Receivable

FI Terms in SAP (vs. Industry)
Posting Peroid = Accounting Period
Incoming Payment = Cash Allocation
Cross-Company Transaction = Inter-company Posting
Vendor = Supplier
Document = Voucher/Journal

FI Concepts
- FI is used in the process of accounting for money moving into and out of the company
- FI provides and supports external reporting requirements (e.g., legal, shareholders, government)
- FI’s primary goal is producing the financial statements for the company (e.g., balance sheet, income statement)


Financial Accounting is concerned with:
- What is bought, sold, owed, and owned
- The inflow and outflow of funds, as well as the net result of those flows
Financial Accounting does not keep records of:
- Where money is spent (e.g., to which cost center or work order)

General Ledger Accounting
- Used to record the business activities of a company
- Used to identify the “what” aspect of financial accounting (e.g., salary expense, buildings, sales revenue, etc.)
- Each account represents a unique type of business event, obligation , or asset
- Each account in SAP is represented by a number (e.g., salary expense = 500,000)
- In SAP the assignment of General Ledger account numbers follows a logical structure


•In order to distinguish between the various FI documents, document types are used. Each document is assigned to one document type, and this is entered in the document header. Document numbers are provided by the document number ranges assigned to one or more document types.
•For G/L account postings, document type SA is used, although other document types are possible (such as accrual/deferral documents, valuation documents, and so on).

For each company code, you have to specify one General Ledger Accounting for the general ledger. This General Ledger Accounting is assigned to the company code. A General Ledger Accounting can be used by multiple company codes (Chart of accounts -> Company code is one-to-many relationship). This means that the general ledgers of these company codes have the identical structure.

General Ledger Book (Chart of Accounts)
- Called the Chart of Accounts in SAP
- Is the official list of all the General Ledger accounts
- Supports the legal reporting and record keeping requirements of the company
- Is independently auditable
- Is used as the basis for producing Financial Statements

Organizational Data
- Company Code
- Chart of Accounts
- Fiscal Year Variant
- Credit Control Area
- Business Area & Functional Area

Company Code
- An Organizational unit in SAP that normally represents a legal entity
- May also be based on external reporting requirements (e.g., a utility company may be one legal entity for tax purposes but must also provide reports to support regulatory statutes, dictating that more than one Company Code may be set up)
- Level at which Financial Statements are created in FI (several Company Codes can be consolidated)
- May be one or more per Client

Chart of Accounts- List of all General Ledger accounts that may be used by a Company Code
- May be one or more per Client
-- Statutory reasons may dictate more than one is necessary (e.g., Belgium determines the account numbers a company must use for reporting, these will usually not match current numbering logic used by the rest of the corporation)
- Each Company Code must be assigned to a Chart of Accounts
- A single Chart of Accounts can be shared by various Company Codes


Fiscal Year Variant
- Defines the number of posting periods allowed in one fiscal year
- Allows the definition of a fiscal year that is different from a calendar year (i.e., a fiscal year which runs from April 1st through March 30th)

Credit Control Area- Credit is managed in SAP within Credit Control Areas. Once set, individual credit details are managed at the customer master level through the Credit Management function
- The following parameters are set at the customer master record level:
-- Total: Maximum credit for a Customer across all Credit Control Areas
-- Maximum Per Credit Control Area: Maximum credit limit for any one Credit Control Area
-- Credit Limit: Amount of credit extended to a Customer at this point in time. It cannot exceed the Maximum Per Credit Control Area

Business Area
- Business areas represent separate areas of operation within an organization
- Can be used across company codes.
- They are balancing entities which are able to create their own set of financial statements for internal purposes.
- The use of business areas is optional.


Master Data
G/L Accounts
Account Groups


Transactional Data
- Document Types and Number Ranges
- Posting Periods
- Financial Tolerance Groups
- Taxes
- Financial Posting/Document Entry

Document Types and Number Ranges
- Document Types: Classifies accounting documents (e.g., Inventory Document, G/L Account Posting) as to their purpose. SA is the standard G/L Document Type
- Document Number Ranges: Each Document Type is assigned to a specific Number Range within the entire range available in SAP
- Both Document Types and Number Ranges enable organization of documents and permit easy recognition on reports and displays

Posting Periods
- Periods opened/closed via simple table changes to enable/disable posting for a particular month
- Can open/close periods by G/L Account or Account Type (e.g., payables can close before G/L)
- Posting in the current month is usually carried forward a few days into the new month to allow for month-end processing
- Special periods are available for year-end adjustments as an option to re-opening closes periods
- Adjustments made to prior year will automatically revise the opening balance of the current fiscal year as reflected on the balance sheet


Financial Processes
Define Tolerances for Groups of SAP Users

- Prescribe maximum dollar amount a user can post in an FI document (e.g., sum of all debits or credits)
-- A different dollar amount can be specified for Customer/Vendor Accounts and G/L postings
-- Maximum allowable cash discounts may also be set for tolerance groups
- Define permitted payment differences on vendor and customer invoices

Taxes
- Tax Categories
-- Identified on the G/L master record, they specify to the system whether the account is pertinent to Input or Output taxes
--- Input taxes are taxes which the company pays on purchases
--- Output taxes are taxes which the company pays on purchases customers on behalf of the tax authorities
- Tax Codes
-- Two-digit code that represents the specifications used for calculating and displaying tax
-- Configured in the IMG, tax codes identify the breakdown of the Input or Output tax
-- Identified on the G/L document at the time of posting, based on the Tax Category of the G/L account
- Tax Codes, continued
-- Examples of tax codes might include l1, l2, O1, O2, etc.
--- Examples of tax breakdown might include 7% PST/7% GST, 0% PST/7% GST, etc.
- Automatic Tax Posting
-- The process by which SAP automatically determines the tax amount and the correct G/L account to post taxes to
-- Via an IMG process, the correct G/L accounts are identified, and tax line items are automatically generated based on the tax code entered on the document

Financial Posting / Document Entry
- Often called a Journal Entry or FI Posting
- Posting is a financial entry to a General Ledger account
- Each posting produces a Financial Document
- All postings must be balanced where debit and credit dollar amounts are equal

- SAP financial documents consist of:
-- Header: Posting Date, Company code, Currency, Document Type, User ID
-- Line Items: Post Key, G/L Account Number, Amount, Quantity
- Every financial document has an associated Document Type and a Document Number
- The posting key (PK) has a control function pertaining to the document line items.
- It determines the following:
-- Account type for the posting of the line item
-- Posting of line items as debit or credit postings
-- Field status of additional information

Analyzing Account Data
The following tools are available to aid in account analysis:
- Account balance Display
- Line items: Open, cleared, special G/L
- Selection criteria (allows the user to narrowly define search criteria)
- Line layouts: Customize display of line item details (columns)
- The drill down feature allows users to quickly navigate from high level view to source item view by double clicking on each item

Account Payable & Account Receivable Concepts- Sub-Ledgers are the individual master records unique to each customer and vendor, where the details of all transactions are recorded
- The financial data recorded in each sub-ledger is summarized in the general ledger, in an account called a Reconciliation Account
-- A/P: Summarizes the amounts owed to vendors
-- A/R: Summarizes the amounts due from customers

- Posting:
-- Reconciliation Accounts are updated internally each time the sub-ledger is posted to, by way of the Three-Way Posting
-- All direct postings (i.e., invoice entry) are done directly at the sub-ledger level

Master Data
- Is static data which represents things, rather than events (which would be transaction data)
- Is input to SAP transactions
- Is a central repository shared across SAP modules

- Customjer Master Records
- Vendor Master Records

Transaction Data
- Is dynamic data, meaning that it is typically changed or created many times in one day
- Records a business activity or event

- Invoice Entry

FI Transactions Overview- FI Documents are generated through one of three methods:
-- Manual entries executed from within the module itself
-- The effect of other SAP processes outside of FI which automatically generate financial postings
--- Usually includes “automatic account assignment”
--External, non-SAP systems interfaces
-In all cases the system automatically generates an FI document with its own unique number

SAP - MDM

Master data is the information that describes core business entities such as Customers, products, locations, suppliers,…. Master data typically is non-transactional data, shared by several applications, static in nature.

Master data management is the development and maintenance of the required organizations, processes and tools to ensure that every master data element …

Is captured once, on time, accurately, completely, correctly and consistently thus enabling master data quality;

Is stored in a way that guarantees integrity and a single place of reference

Is made available to those who need it, whenever they need it, both internally and externally.’

Business Drives:
- Single Version of the Truth
- Business Intelligence
- Operational Efficiencies
- Application Integration
- Compliance

Master Data Layers:
- Combined Master Data
- Master Data
- Reference Data
- Meta Data


History and Positioning at SAP
- Pre 2004: SAP MDM 3.0
- July 2004: SAP MDM-E (SAP acquires A2i)
- 2005: MDM 5.5 SP03
- 2006-2007: MDM 5.5 SP04, SP05, SP06
- 2008: MDM 7.1 (Q3)

Core MDM Scenarios
- Master Data Consolidation
- Master Data Harmonization
- Central Master Data Management

Horizontal Scenarios
- Customer Data Integration
- Product Information Management
- Improved Business Intelligence

Industry Scenbarios
- Global Data Synchronization

Embedded Scenarios
- SRM/MDM Catalog

Building Blocks












MDM Fun ctional Overview

MDM Integration
- Exchange Information between MDM and various syswtems
- Extract Data, Load Data, Distribute Data (ETL)
- Service Enabled Integration

MDM Integration Flows
















MDM Integration APIs
- ABAP, Java and COM
- Administrate MDM Servers and model repositories
- Access and modify master data
- Exposes MDM matching capabilities and workflow

MDM Web Services
- Based on SOAP and WSDL
- Provide data management capabilities (CRUD)


MDM Operations
- Toolset to Manage Master Data (Search-Edit-Change)
- Governance through Workflow


Role-based Access
- Access data stored MDM using UI

Drilldown Seach
- Powerful and efficient search capabilities
- Allows users to start with all of the items in the repository and then effortlessly zoom in on items of interest

Creation and Maintenance
- Manage data in the repositmory. (maint table and sub tables records)
- Leverage built in data management workflows to manage compliance process

Catalog Management
- Centrally manage catalogs (upload, consolidate, search) and publish the information to business processes

MDM Quality
- Toolset to Enhance Data Quality
- Normalization, Standardization, Enrichment, De-Duplication


Normalization
- Field Mapping (map an individual source field to an individual destination field)
- Value Mapping (value level mapping against the legal destination)
- Conversion (Each source value can manually or automatically be converted or reformatted)

Validations
Matching and Merging
Key Mapping (cross-system identification to ensure enterprise-wide data quality)
Enrichment (MDM sends data elements to an external data enrichment provider and receives a response containing data to be updated or inserted in a repository.)