ALE - Data Distribution Model

One of the challenges in designing distributed applications is the data distribution model, which consists of all participating systems and the messages to be exchanged by the system. Data distribution in R/3 to R/3 environment is easily achieved but there are several bottlenecks in R/3 to non-R/3 scenarios – for example data mapping - as non-R/3 systems seldom have as rich an organizational representation as R/3 has. The following figure illustrates the concept of data distribution using ALE.

Figure 1: ALE FRAMEWORK

Enterprise business objects of a SAP system are distributed with the help of BAPIs (Business Application Programming Interfaces). ALE acts as a layer that incorporates the inter-linking of business objects at the application level. The ALE layer provides the following services:
Applications services: this layer provides ALE with an interface (for instance: BAPI) to R/3 to facilitate data exchange to or from external R/3 systems.
Distribution services: the onus of filtering and converting messages exchanged between SAP and non-SAP systems is on the distribution layer of ALE. This service is the core service and acts as a sandwich layer between application and communication layers.
Communications services: ALE supports synchronous as well asynchronous communication. Synchronous messaging is used for the direct reading of control data, while asynchronous messaging is used for transmitting or receiving application data.
The implementation of ALE is achieved with the help of external converters (ALE converters), which connect SAP applications to non-SAP applications. In simple words, external converters are generic-format conversion programs, which contain specific converter functions. The capabilities of the external converter will be discussed later in this article.

read more...

ALE - Introduction

ALE - Introduction
Enterprises are increasingly looking to deliver real business benefits by integrating their systems and processes both within their organizations and between organizations. ng processes in this way, which requires tight integration, frequent communication and data exchange.
Highly integrated and inter-dependent SAP and non-SAP systems require frequent communication, tight integration and (usually) high levels of data exchange. In order to achieve this interoperability, SAP has come up with the concept of ALE (Application Linking and Enabling).
The idea behind ALE is to provide a more rigid integration service while allowing a high degree of independence to the individual SAP com
ge of business information across SAP and non-SAP systems. Applications are integrated by using synchronous and asynchronous communication without implementing a central database.

In this 6 article tutorial we will cover subjects such as:
Data Distribution Model
ALE process
IDOCS
Converters
Configuring ALE
Other concepts

read more...

Performance Tuning

Need for Performance Tuning

In this world of SAP programming, ABAP is the universal language. In most of the projects, the focus is on getting a team of ABAP programmers as soon as possible, handing over the technical specifications to them and asking them to churn out the ABAP programs within the “given deadlines”.
Often due to this pressure of schedules and deliveries, the main focus of making a efficient program takes a back seat. An efficient ABAP program is one which delivers the required output to the user in a finite time as per the complexity of the program, rather than hearing the comment “I put the program to run, have my lunch and come back to check the results”.
Leaving aside the hyperbole, a performance optimized ABAP program saves the time of the end user, thus increasing the productivity of the user, and in turn keeping the user and the management happy.
This tutorial focuses on presenting various performance tuning tips and tricks to make the ABAP programs efficient in doing their work. This tutorial also assumes that the reader is well versed in all the concepts and syntax of ABAP programming.
NOTE: Performance of a program is also often limited due to hardware restrictions, which is out of the scope of this article.

read more...

SAP Quality Management

SAP QM Tips and Quality Management Discussion Forum
Practical and helpful SAP QM Stuff to assist those supporting the SAP Quality Management Modules. If you have any SAP Quality Management question, please feel free to raise it in the SAP QM Forum.
The integration of the QM application component in the R/3 System allows quality management tasks to be combined with those in other applications (such as materials management, production, sales and distribution and cost accounting). SAP has developed and implemented three quality management systems certified according to ISO 9001:2000
SAP Global Development -- Ensures that SAP solutions meet the highest possible standards
SAP Active Global Support -- Provides tailored services to maintain the quality of installed solutions
SAP IT -- Ensures the stability and quality of SAP's internal IT infrastructure; SAP IT is certified according to the requirements specified in ISO 27001:2005 Each system defines standardized, certified processes for its domain. And use of a system enables employees to share and apply best practices within their domain.These three quality management systems merge their common information (management review, document control, record control, audits, corrective and preventive action, and personnel development), thereby ensuring the consistent application of this information across SAP.

read more...

Important Tables in SAP

FI-AA-AA Asset Accounting: Basic Functions – Master Data
(AA)

ANKA Asset Classes: General Data ANLKL
ANKP Asset Classes: Fld Cont Dpndnt ANLKL / AFAPL
on Chart of Depreciation
ANKT Asset Classes: Description SPRAS / ANLKL
ANKV Asset Classes: Insurance Types ANLKL / VRSLFD
ANLA Asset Master Record Segment BUKRS / ANLN1 / ANLN2
ANLB Depreciation Terms BUKRS / ANLN1 / ANLN2 /
AFABE / BDATU
ANLT Asset Texts SPRAS / BUKRS / ANLN1 /
ANLN2
ANLU Asset Master Record User Fields .INCLUDE / BUKRS /
ANLN1 / ANLN2
ANLW Insurable Values BUKRS / ANLN1 / ANLN2 /
(Year Dependent) VRSLFD /GJAHR
ANLX Asset Master Record Segment BUKRS / ANLN1 / ANLN2
ANLZ Time Dependent Asset BUKRS / ANLN1 / ANLN2 /
Allocations BDATUFI-AA-AA Asset Accounting: Basic Functions – Master Data 2.0
(AA2)
ANAR Asset Types ANLAR
ANAT Asset Type Text SPRAS / ANLAR
FI-AA-AA Asset Accounting: Basic
(AB) Functions –Asset Accounting

ANEK Document Header Asset Posting BUKRS / ANLN1 / ANLN2 /
GJAHR /
LNRAN
ANEP Asset Line Items BUKRS / ANLN1 / ANLN2 /
GJAHR /LNRAN / AFABE

ANEV Asset Downpymt Settlement BUKRS / ANLN1 / ANLN2 /
GJAHR / LNRANS

ANKB Asset Class: Depreciation ANLKL / AFAPL / AFABE /
Area BDATU
ANLC Asset value Fields BUKRS / ANLN1 / ANLN2 /
GJAHR / AFABE
ANLH Main Asset Number BUKRS / ANLN1
ANLP Asset Periodic Values BUKRS / GJAHR / PERAF /
AFBNR /ANLN1 / ANLN2 /
AFABERFI-SL-VSR Special Purpose Ledger: Validation, Substitution
(GVAL) and Rules
GB03 Validation / Substitution User VALUSER
GB92 Substitutions SUBSTID
GB93 Validation VALID

read more...

Important Tables for SAP CO

Controlling Table Name Description Important FieldsAUSP Characteristic Values MANDT / OBJEK / ATINN / ATZHLCO-KBAS Overhead Cost Controlling
A132 Price per Cost Center MANDT / KAPPL / KSCHL / KOKRS
A136 Price per Controlling Area MANDT / KAPPL / KSCHL / KOKRS
A137 Price per Country / Region MANDT / KAPPL / KSCHL / KOKRS
COSC CO Objects: Assignment of Origina MANDT / OBJNR / SCTYP / VERSN
CSSK Cost Center / Cost Element MANDT / VERSN / KOKRS / GJAHR
CSSL Cost Center / Activity Type MANDT / KOKRS / KOSTL / LSTAR
KAPS CO Period Locks MANDT / KOKRS / GJAHR / VERSN
CO-KBASCORE Overhead Cost Controlling: General Services
CSKA Cost Elements (Data Dependent on MANDT / KTOPL / KSTAR
CSKB Cost Elements (Data Dependent on MANDT / KOKRS / KSTAR / DATBI
CSKS Cost Center Master Data MANDT / KOKRS / KOSTL / DATBI
CSLA Activity Master MANDT / KOKRS / LSTAR / DATBICO-OM (KACC) Overhead Cost Controlling
COBK CO Object: Document Header MANDT / KOKRS / BELNR
COEJ CO Object: Line Items (by Fiscal MANDT / KOKRS / BELNR / BUZEI
COEJL CO Object: Line Items for Activit MANDT / KOKRS / BELNR / BUZEI
COEJR CO Object: Line Items for SKF (by MANDT / KOKRS / BELNR / BUZEI
COEJT CO Object: Line Items for Prices MANDT / KOKRS / BELNR / BUZEI
COEP CO Object: Line Items (by Period) MANDT / KOKRS / BELNR / BUZEI
COEPL CO Object: Line Items for Activit MANDT / KOKRS / BELNR / BUZEI
COEPR CO Object: Line Items for SKF (by MANDT / KOKRS / BELNR / BUZEI
COEPT CO Object: Line Items for Prices MANDT / KOKRS / BELNR / BUZEI
COKA CO Object: Control Data for Cost MANDT / OBJNR / GJAHR / KSTAR
COKL CO Object: Control Data for Activ MANDT / LEDNR / OBJNR / GJAHR
COKP CO Object: Control Data for Prima MANDT / LEDNR / OBJNR / GJAHR
COKR CO Object: Control Data for Stati MANDT / LEDNR / OBJNR / GJAHR
COKS CO Object: Control Data for Secon MANDT / LEDNR / OBJNR / GJAHRCO-OM-CEL (KKAL) Cost Element Accounting (Reconciliation Ledger)
COFI01 Object Table for Reconciliation L MANDT / OBJNR
COFI02 Transaction Dependent Fields for MANDT / OBJNR
COFIP Single Plan Items for Reconciliat RCLNT / GL_SIRID
COFIS Actual Line Items for Reconciliat RCLNT / GL_SIRID
CO-OM-CCA Cost Center Accounting (Cost Accounting Planning RK-S)
– What is RK-S
A138 Price per Company Code MANDT / KAPPL / KSCHL / KOKRS
A139 Price per Profit Center MANDT / KAPPL / KSCHL / KOKRSCO-OM-OPA (KABR) Overhead Orders: Application Development R/3
Cost Accounting Settlement
AUAA Settlement Document: Receiver Seg MANDT / BELNR / LFDNR
AUAB Settlement Document: Distribution MANDT / BELNR / BUREG / LFDNR
AUAI Settlement Rules per Depreciation MANDT / BELNR / LFDNR / AFABE
AUAK Document Header for Settlement MANDT / BELNR
AUAO Document Segment: CO Objects to b MANDT / BELNR / LFDNR
AUAV Document Segment: Transactions MANDT / BELNR / LFDNR
COBRA Settlement Rule for Order Settlem MANDT / OBJNR
COBRB Distribution Rules Settlement Rul MANDT / OBJNR / BUREG / LFDNRCO-OM-OPA (KAUF) Overhead Orders: Cost Accounting Orders
AUFK Order Master Data MANDT / AUFNR
AUFLAY0 Enttity Table: Order Layouts MANDT / LAYOUTEC-PCA (KE1) Profit Center Accounting
CEPC Profit Center Master Data Table MANDT / PRCTR / DATBI / KOKRS
CEPCT Texts for Profit Center Master Da MANDT / SPRAS / PRCTR / DATBI
CEPC_BUKRS Assignment of Profit Center to a MANDT / KOKRS / PRCTR / BUKRS
GLPCA EC-PCA: Actual Line Items RCLNT / GL_SIRID
GLPCC EC-PCA: Transaction Attributes MANDT / OBJNR
GLPCO EC-PCA: Object Table for Account MANDT / OBJNR
GLPCP EC-PCA: Plan Line Items RCLNT / GL_SIRID
EC-PCA BS (KE1C) PCA Basic Settings: Customizing for
Profit Center Accounting
A141 Dependent on Material and Receive MANDT / KAPPL / KSCHL / KOKRS
A142 Dependent on Material MANDT / KAPPL / KSCHL / WERKS
A143 Dependent on Material Group MANDT / KAPPL / KSCHL / WERKS

read more...

Important Tables for SAP FI

Financial Accounting Table Name Description Important FieldsFinancial AccountingFBAS Financial Accounting “Basis”
BKPF Accounting Document Header BUKRS / BELNR / GJAHR
BSEG Accounting Document Segment BUKRS / BELNR / GJAHR / BUZEI
BSIP Index for Vendor Validation BUKRS / LIFNR / WAERS / BLDAT /
of Double Documents XBLNR / WRBTR / BELNR / GJAHR
/ BUZEI
BVOR Inter Company Posting BVORG / BUKRS / GJAHR / BELNR
Procedure
EBKPF Accounting Document Header GLSBK / BELNR / GJHAR / GLEBK
(docs from External Systems)
FRUN Run Date of a Program PRGID
KLPA Customer / Vendor Linking NKULI / NBUKR / NKOAR / PNTYP
/ VKULI / VBUKR / VKOAR
KNB4 Customer Payment History KUNNR / BUKRS
KNB5 Customer Master Dunning Data KUNNR / BUKRS / MABER
KNBK Customer Master Bank Details KUNNR / BANKS / BANKL / BANKN
KNC1 Customer Master Transaction KUNNR / BUKRS / GJHAR
Figures
KNC3 Customer Master Special KUNNR / BUKRS / GJAHR / SHBKZ
GL Transactions Figures
LFB5 Vendor Master Dunning Data LIFNR / BUKRS / MABER
LFBK Vendor Master Bank Details LIFNR / BANKS / BANKL / BANKN
LFC1 Vendor Master Transaction LIFNR / BUKRS / GJHAR
Figures
LFC3 Vendor Master Special LIFNR / BUKRS / GJHAR / SHBKZ
GL Transactions Figures
VBKPF Document Header for AUSBK / BUKRS / BELNR / GJHAR
Document ParkingFBASCORE Financial Accounting General Services “Basis”KNB1 Customer Master (Company Code) KUNNR / BUKRS
LFA1 Vendor Master (General Section) LIFNR
LFB1 Vendor Master (company Code Section) LIFNR / BUKRS
SKA1 G/L Account Master (Chart of Accounts) KTOPL / SAKNR
SKAT G/L Account Master (Chart of Accounts – SPRAS / KTOPL / SAKNR
Description)
MAHNS Accounts Blocked by Dunning KOART / BUKRS / KONKO / MABER
Selection
MHNK Dunning Data LAUFD / LAUFI / KOART / BUKRS /
(Account Entries) KUNNR / LIFNR / CPDKY / SKNRZE /
SMABER / SMAHSK / BUSABFI-GL-GL (FBS) General Ledger Accounting: Basic Functions-
G/L AccountsSKAS G/L Account Master – SPRAS / KTOPL / SAKNR / SCHLW
(Chart of Accounts Key Word list)
SKB1 G/L Account Master (Company Code) BUKRS / SAKNR
FI-GL-GL (FBSC) General Ledger Accounting: Basic
Functions - R/3 Customizing for G/L Accounts
FIGLREP Settings for G/L Posting Reports MANDT
TSAKR Create G/L account with reference BUKRS / SAKNR
FI-GL-GL FFE) General Ledger Accounting: Basic
Functions - Fast Data Entry
KOMU Account Assignment Templates for G/L KMNAM / KMZEI
Account itemsFI-AR-AR (FBD) Accounts Receivable: Basic Functions - Customers

KNKA Customer Master Credit Management : KUNNR
Central Data
KNKK Customer Master Credit Management : KUNNR / KKBER
Control Area Data
KNKKF1 Credit Management : LOGSYS / KUNNR / KKBER / REGUL
FI Status data
RFRR Accounting Data – A/R and A/P RELID / SRTFD / SRTF2
Information SystemFI-BL-PT Bank Accounting: Payment (BFIBL_CHECK_D)
Transactions – General SectionsPAYR Payment Medium File ZBUKR / HBKID / HKTID / RZAWE /
CHECT
PCEC Pre-numbered Check ZBUKR / HBKID / HKTID / STAPLFI-BL-PT-AP(FMZA)Bank Accounting: Payment
Transactions – Automatic Payments

F111G Global Settings for Payment Program for MANDT
Payment Requests
FDZA Cash Management Line Items in Payment KEYNO
Requests
PAYRQ Payment Requests KEYNO
What is the table name for G/L Master data, when we create centrally (T.Code - FS00)?
As far as general ledger master data is concerned, the following tables are involved : Table name : SKB1 : G/L Account Master ( Company Code) Fields: BUKRS : Company Code SAKNR : G/L Account Table name : SKA1 : G/L Account Master ( Chart of Accounts ) Fields: KTOPL : Char of Accounts SAKNR : G/L Account Table name : SKAT : G/L Account Master Record ( Chart of Accounts : Description ) Fields: SPRAS : Language KTOPL : Char of Accounts SAKNR : G/L Account

read more...