ERP SAP

ERP SAP Has a New Blog Location

2010-05-08T14:06:00.000+08:00

Please visit Jessica's Journal for it's new blog location. Thank you for the visits.

ERP SAP Day 20

2009-07-31T10:30:00.002+08:00

Asset Management

Financial Asset Accounting:

Master Data
Asset Transactions
Periodic Processing
Information System

Asset Classes

Asset Management in SAP System:

CREATE ASSET:
Accounting> Financial Accounting> Fixed Asset> Asset

AS01 Create Asset

ASSET ACQUISITION FROM VENDOR:
Accounting> Financial Accounting> Fixed Assets> Posting> Acquisition> Extend Acquisition>

F-90 With Vendor

ERP SAP Day 19

2009-07-30T13:29:00.003+08:00

Accounts Receivable

Customer Master Record in Detail:

Address and Communication
Control Data
Payment Transactions
Accounting Information
Payment Transactions in Accounting
Dunning Data in Accounting
Correspondence in Accounting

Account Groups:

Number Range
One-time Account
Field Status

Manual Payment - Incoming Payment Entry:

Selecting items to be processed
Processing open items
Posting partial payments and outstanding receivables
Clearing between customers and vendors
Clearing manually and reversing the clearing entry/reversal
Incoming payment fast entry
Manual payment advice entry

Manual Payment:

Header DataProcessing
Open Items

Accounts Receivable in SAP System:

CUSTOMER MASTER RECORD:
Accounting> Financial Accounting> Customers> Master Records>

FD01 Create
FD02 Change
FD03 Display

INVOICE:
Accounting> Financial Accounting> Customers> Document Entry>

FB70 Invoice

REVERSAL:
Accounting> Financial Accounting> Customers> Reverse>

FB08 Individual Reverse

PAYMENT (FROM CUSTOMERS):
Accounting> Financial Accounting> Customers> Document Entry>

F-28 Incoming Payments

DISPLAY DEBTORS BALANCES: Accounting> Financial Accounting> Customers> Account>

FD10N Display Balances

ERP SAP Day 18

2009-07-29T09:29:00.004+08:00

Accounts Payable in SAP System:

VENDOR MASTER RECORD:

Accounting> Financial Accounting> Vendors> Master Records>

FK01 Create
FK02 Change
FK03 Display

INVOICE:

Accounting> Financial Accounting> Vendors> Document Entry>

FB60 Invoice

REVERSAL:

Accounting> Financial Accounting> Vendors> Document> Reverse>

FB08 Individual Reversal

PAYMENT (TO VENDOR):

Accounting> Financial Accounting> Vendors> Document Entry> Outgoing Payment>

F-53 Post

DISPLAY CREDITORS BALANCES:

Accounting> Financial Accounting> Vendors> Account>

FK10N Display Balances
FBL1N Display/Change Line Items

ERP SAP Day 17

2009-07-28T14:28:00.004+08:00

Accounts Payable

Vendor Master Records:

KRED Domestic Vendors
KREA Vendors Abroad
VERB Affliated
CPD One-time

Number Ranges:

Number
From Number
To Number
Current Number
Internal or External Number

Main Master Records in FI/CO:

Vendor
Customer
Bank
G/L
Cost Centre

Vendor/Customer One Time - No Customer/Vendor specific information and no Bank Details.

Credit Control Area - If a customer is created in several company codes that are assigned to different credit control areas, a separate credit limit is managed for each of the different credit control areas.

ERP SAP Day 16

2009-07-27T16:28:00.005+08:00

General Ledger in SAP System:

GL ACCOUNT IN COMPANY CODE:
Accounting> Financial Accounting> General Ledger> Master Records> G/L Accounts> Individual Processing>

FSS0 In Company Code

GENERAL EXPENSE POSTING - CREATION:
Accounting> Financial Accounting> Posting>

FB50 Enter G/L Account Document

GENERAL EXPENSE POSTING - DISPLAY:
Accounting> Financial Accounting> General Ledger> Document>

FB03 Display

ERP SAP Day 15

2009-07-24T08:18:00.007+08:00

Dates Used for Posting:

Document Date - Used for Inidvidual Purpose
Posting Date - Update of transaction figures
Translation Date - Exchange Rate for postings in Foreign Currency
Entry Date - Entering Time of the posted document

Currencies Used for Posting:

Transaction Currency - The Currency in which the transaction is posted
Local Currency - The Currency of the Company Code is always updated
1st. Parallel Currency - For example: Group Currency
2nd. Parallel Currency - For example: European Currency

SAP always track Transaction and Local currencies where 2 additional currencies can also be tracked via further configuration settings.

Document Types:

Customer Payment
Vendor Invoice

The Document Types attaches a Number Range to the document. Number Ranges can be externally or internally defined. Authorisation groups can be tied to Document Types for security. Negative postings are controlled by Document Type.

Standard Document Types:

Customer Invoices
Customer Credit Memos
Customer Payment
G/L Account Postings
Vendor Invoices
Vendor Credit Memos
Vendor Payments
Vendor Net Invoices and Credit Memos

Posting a document - Accounts:

Every line item must contain an account. This may be a G/L account or it might be a Subledger Account.
The Account Type of the Posting Key is used to identify whether the account will be a G/L Account or a Subledger Account. Valid Account Types for line item enttry include Customers or Debtors, Vendors or Creditors, G/L Accounts, Assets and Materials.

Foreign Currency Processing:

Every G/L transaction in R/3 is automatically captured in 2 currencies - Transaction Currency (Input at the document header) and Local/Company Currency (Currency of the Company Code in which the document is attached).
It is possible to configure R/3 to capture 2 additional or Parallel Currencies
The user can display the transaction in any of the currencies being stored
Postings to Exchange Rate difference accounts are made automatically (when required)

Exhange Rate Tables:

The 4 possible currencies can be any currency that has rates maintained in the Exchange Rate table.
When entering an entry, the user can key in a Translation Date for determining the exchange rate or let the system use the Posting Date of the transaction to determine the rate.

ERP SAP Day 14

2009-07-23T13:09:00.002+08:00

General Ledger (GL)

Master Data - Before a GL account can be used in a Company Code, the Account Definition at the Chart of Accounts needs to be maintained.

Account Groups - Used to classify G/L accounts into user defined segments within a Chart of Accounts, typically broken down by placement on financial statements. Every Chart of Accounts must have at least one account group defined.

AS Fixed Assets
CASH Liquid Funds
GL General Ledger
MAT Materials Management
PL Income Statement

Field Status Variant - Activate/Deactivate, Mandatory or Suppress

Field Status Group - Available for each Account Group (Mutually Exclusive):

Suppress
Required Entry
Optional Entry
Display

General Ledger Master Record Information - Account Master Record attaches the account to either the Balance Sheet or Profit and Loss Statement. This is required by the Balance Carried Forward program.

General Ledger Master Record Control Data - Controls how the account is used.

General Ledger Master Record consists of 2 segments:

Chart of Accounts
Company Code

1 Chart of Accounts can be used by more than 1 Company Code while the Company Code segment relates to only 1 particular Company Code.

A Reconciliation Account is a G/L account used to attach subledger accounts to the General Ledger.

The Reconciliation Account and Subsidiary Ledger are updated in parallel when posting a transaction:

Line item details are kept in the Subsidiary Ledger
Summary Information is kept in the Reconciliation Account
Reconciliation Accounts cannot be posted to.

Open Item Management - Items posted to accounts maanged on an Open Item basis are indicated as open and cleared. The balance of these types of accounts is always equal to the balance of the Open Items. Reconciliation Accounts are managed on an open item basis at the Subledger Level using the Subledger Open Item feature.

General Ledger - A Collection of all accounts used by a Company Code.

G/L Master Record - Chart of Accounts Segments: Contains data that is common for all Company Codes using this Chart of Accounts.

Creating a G/L Account:

Requirement
Accounts and Company Code
Chart of Accounts Segment
Company Code Segment

Document Number Ranges - X1 and X2 are reserved for sample and recurring entry documents.

ERP SAP Day 13

2009-07-22T12:38:00.004+08:00

FICO - Financial Accounting/Costing

FI Modules:

GL - General Ledger
AP - Accounts Payable
AR - Accounts Receivable
AM - Asset Management

Each Company Code is a separate legal entity with its own Balance Sheet.

1 Plant can only be attached to 1 Company Code.

Chart of Accounts - Lists all Account Names and Numbers used in a Company's General Ledger.

FICO Reporting Needs:

External - Balance Sheet, Profit and Loss (Income Statement), CashFlow Statement, Retained Earnings Statement.
Internal - Product Cost Reports, Cost Centre Reports, Profit Centre Reports, Activity Price Plan.

Organizational Units as used in SAP:

CLIENT - Enterprise
COMPANY CODE, SALES ORGANISATION - Financial Accounting Sales
CONTROLLING AREA - Cost Accounting
PLANT, DISTRIBUTION CHANNEL - Production/Distribution
STORAGE LOCATION - Inventory Management

The SAP R/3 system uses the following Organisational Structures to represent the business processes in Financial and Accounting Management:

Company Code
Group Company
Business Area
Controlling Area
Operating Concern

Controlling Area:

A Controlling Area identifies an independent Organisational Structure for which costs and revenues are collected.
Each Controlling Area can have one or more Company Codes assigned to it.

Operating Concern:

An Operating Concern is the central organisational element in profitable analysis.
Controlling Areas are mapped to 1 and only 1 Operating Concern for internal management segment reporting.

1 Chart of Accounts can be assigned to many Company Codes.

Posting Key Variant (OB41 transaction code): The Posting Key has control functions within the line items. It controls:

The Account Type that the line item can be posted to
If the item is posted as debit or credit
The field status of additional details

SAP Configurations (spro transaction code):

Chart of Accounts (OBY7)
Fiscal Year Variant (OB29)
Posting Period Variant (OBBO)
Company Code (OXO2)
Company Code Global Data (OBY6)
Define Countries (OY01)
Define a ParallelCurrency (OB22)
Validation Maintenance (GGB0)

ERP SAP Day 12

2009-07-21T13:08:00.004+08:00

Material Master Record:

SAP R/3 - Material Master
FICO - Accounting/Costing
MM - Plant
SD - Sales Organisation
PP - MRP (Material Resource Planning)
WM - WM (Warehouse Management)

Materials in SAP System:
Logistics> Materials Management> Material Master> Material>

MM01 Create
MM02 Change
MM03 Display

Material Master Creation:

MM:

Material Basic Data
General Plant Data Storage 1
General Plant Data Storage 2

SD:

Sales Organisation Data 1
Sales Organisation Data 2
Foreign Trade: Export Data
Sales: General/Plant Data
Sales Order Text

FI:

Accounting Data 1
Accounting Data 2

WM:

Warehouse Management 1
Warehouse Management 2

MMBE - Stock Overview

MB1C - Post Stock

VK11 - Create Pricing Master Data

ERP SAP Day 11

2009-07-20T10:53:00.004+08:00

In Materials Management Procurement Cycle, it starts with Requisition Document and ends with Invoice Verification.

In Sales and Distribution Sales Cycle, it starts with Inquiry Document and ends with Billing (Invoice).

Purchase Requisitions are internal document you use to request the Purchasing department to procure a particular quantity of a material or a service for a particular date.

Billing Methods:

Periodically
Milestones

Purchase Order is a formal request to be a vendor to supply goods to the company.

Goods Receipt:

When you post a goods receipt to the warehouse, the system create a material document containing information such as material delivered and the quantity delivered. The system also records the Storage Location in which you place the material into the stock in the Plant concerned.

Vendor's Partner Functions:

Order Receivers
Contact Person
Goods Supplier
Vendor
Invoicing Party

Invoice Processing:

In Material Management, the procurement process is concluded by the Invoice Verification process, during which invoices and credit memos are entered and the contents and prices are checked for accuracy. However, payment and evaluation of invoices is not part of the Invoice Verification. The appropriate information for these tasks are passed on to other departments. Invoice Verification therefore creates a link between Material Management and external or internal accounting.

ERP SAP Day 10

2009-07-17T12:43:00.002+08:00

Purchasing in SAP System:

VENDOR MASTER RECORD - Central:
Logistics> Materials Management> Master Data> Vendor>

XK01 Create
XK02 Change
XK03 Display

VENDOR MASTER RECORD - Purchasing:
Logistics> Materials Management> Master Data> Vendor>

MK01 Create
MK02 Change (Current)
MK03 Display
MK12 Change (Planned)

REQUISITION:
Logistics> Materials Management> Purchase Requisition>

ME51N Create
ME52N Change
ME53N Display

RFQ - REQUEST FOR QUOTATION:
Logistics> Materials Management> Request For Quotation>

PURCHASE ORDER:
Logistics> Materials Management> Purchasing> Purchase Order>

ME21N Create
ME22N Change
ME23N Display

RELEASE PURCHASE ORDER:
Logistics> Materials Management> Purchasing> Purchase Order>

ME29N Individual Release

GOODS RECEIPT:
Logistics> Materials Management> Purchasing> Inventory Management>

MIGO Goods Movement

INVOICE VERIFICATION:
Logistics> Materials Management> Logistics Invoice Verification>

MIRO Invoice Verification

ERP SAP Day 9

2009-07-16T09:19:00.004+08:00

Organization Levels in the Procurement Process:

Client
Company Code
Plant (Production Area)
Storage Location
Purchase Organisation/Purchase Group

Plant:

A Plant is an organizational logistics unit that structures the enterprise from the perspective of production procurement, plant maintenance and materials planning.
A Plant is a manufacturing facility or branch within a company.

Storage Location:

Storage Location is an organizational unit that allows the differentiation of material stocks within a plant.
Inventory Management on a quantity basis is carried out at Storage Location level in a Plant.
Physical Inventory is carried out at Storage Location level.

1 Plant can ony be assigned to 1 Company Code.

Valuation Levels:

Company Code
Plant (with a more precise valuation)

Valuation Area:

The Valuation Area is the organisational level at which material is valuated. Plant and Company Code are 2 possible Valuation Areas in the R/3 system.
When stock is valuated at Plant level, you can valuate a material in different plants at different prices.
When you valuate stock at Company Code level, the valuation price of a material is the same in all of a Company's plant (ie., in a Company Code).

Purchase Organisation/Group:

A Purchasing Organisation is an organisational level that negotiates conditions of purchase with vendors for one or more plants. It is legally responsible for completing purchasing contracts.
A Purchasing Group is the key for a buyer or group of buyers responsible for certain processing activities.

Master Data in Procurement Process:

Material Master Record
Purchase Order
Vendor Master Record
Purchasing Information Record

The Material Master Record and Vendor Master Record are the most important master data in the procurement process.

Vendor Master Record Organizational Level:

General Data - Address, Communication Data, Control Data, Bank Details
Company Code Data - Account Management, Payment Transactions, Correspondence, Witholding Tax
Purchasing Organization Data - Purchasing Data, Partner Roles

Procurement Cycle:

Determination of Requirements
Source Determination
Vendor Selection
Purchase Order Processing
Purchase Order Monitoring
Goods Receipt
Invoice Verification
Payment Processing

ERP SAP Day 8

2009-07-15T14:15:00.000+08:00

Sales Order Types:

OR - Normal Order
VB/CS - Cash Order (Pick and Pay)
RO - Rush Order (Deliver As Soon As Possible)

Consignment Process:
(Delivery first and only receives payment after goods are sold)

Fill-Up
Issue
Pick-Up
Return

Contract includes information such as Item Quantity and Item Value.

ERP SAP Day 7

2009-07-14T11:02:00.002+08:00

Sales Distribution:

Pre-Sales Activities
Sales Order Processing
Inventory Sourcing
Shipping - Pick, Pack and Delivery
Billing - Item details are based on Delivery

Financial Accounting/Costing:

Payment

Sales Cycle:

IN Inquiry
QT Quotation (Price, Material, Validity Period)
Contract
LF Delivery (Delivery Note and Post Goods Issue)
F2 Billing (Invoice)

Sales Document Flow:

Sales Inquiry
Sales Quotation
Sales Order - Contract - Schedule Agreement
Delivery Note (Outbound Delivery)
Goods Issue
Billing Document

Sales Document:

Header
Item (Schedule LIne - Delivery Date and Quantity)

Delivery and Billing Documents:

Header
Item

ERP SAP Day 6

2009-07-13T10:36:00.003+08:00

Sales and Distributions in SAP System:

CUSTOMER MASTER RECORD - Centrally Company Code:
Logistics> Sales Distribution> Master Data> Business Partner> Customer>

XD01 Create
XD02 Change
XD03 Display

CUSTOMER MASTER RECORD - Sales Area Specific:
Logistics> Sales Distribution> Master Data> Business Partner> Customer>

VD01 Create
VD02 Change
VD03 Display

INQUIRY:
Logistics> Sales Distribution> Sales> Inquiry>

VA11 Create
VA12 Change
VA13 Display

QUOTATION:
Logistics> Sales Distribution> Sales> Quotation>

VA21 Create
VA22 Change
VA23 Display

SALES ORDER:
Logistics> Sales Distribution> Sales> Order>

VA01 Create
VA02 Change
VA03 Display

DELIVERY:
Logistics> Sales Distribution> Shipping and Transportations> Outbound Delivery> Create> Single Document>

VL01N Create
VL02N Change
VL03N Display

BILLING:
Logistics> Billing> Billing Document>

VF01 Create
VF02 Change
VF03 Display

ERP SAP Day 5

2009-07-10T08:03:00.002+08:00

Materials Management Stock Movement:

Inward - Receives Raw Materials from Vendors
Outward - Deliver Finished Goods to Customers

Master Data Records:

Customer Master
Material Master
Pricing Condition
Output Condition

Customer Master Record:

General - Name, Address, Communication Data
Company Code - Reconciliation Account, Terms of Payment, Items Sorting, Dunning Procedure
Sales Area

Sales Distribution Partner Functions:

Sold_To_Party [Who places the order?]
Ship_To_Party [Who receives the goods?]
Bill_To_Party [Who receives the bill?]
Pay_To_Party [Who pats the bill?]

SAP System - Organization Units Definitions:

spro transaction code> SAP Reference IMG> Enterprise Structure OR Menu Path> SAP Customizing Implementation Guide> Enterprise Structure

ERP SAP Day 4

2009-07-09T12:03:00.002+08:00

Commercial ERP Packages:

SAP
Oracle
JD Edwards
BAAN
PeopleSoft
Microsoft CRM

Client is the largest Organisational Unit in SAP system. A maximum of 6 window sessions per Client is allowed.

Sales Distribution Organisation Units:

Sales Organisation
Distribution Channel
Division
Sales Office
Sales Group
Shipping Point

Sales Line ==> Sales Organisation - Distribution Channel- Plant

Sales Pushing Strategy ==> Market or move products to customer

Safety Stock ==> Stock stored for unexpected events

SAP R/3 is a Client System. The client concept enables the joint operation in one system by several enterprises that are independent of each other in business terms. During each user session, you can only access the data of the client selected during logon.

ERP SAP Day 3

2009-07-08T11:48:00.003+08:00

ABAP stands for Advanced Business Applications Programming.

SAP roles are divided into 3 sections:

Functional - FI/CO, SD, MM and etc
Technical - ABAP and Java
Administration - BASIS

SAP Installation Platforms:

Windows 2000/2003 Server
Linux
Sun Solaris
IBM AS/400

SAP Database:

Oracle
IBM DB2
Microsoft SQL
Informix
MaxDB

ERP SAP Versions:

SAP R/3
ECC 6.0 (Enterprise Core Components)
ECC 5.0
R/3 4.7 EE
R/3 4.6c
R/3 4.5b
R/3 4.0b

SAP Installation Default Clients:

000 Master Client (Authourised to the whole system)
001 Support Client
066 Early Watch (Used bySAP for monitoring)

SAP Login IDs:

SAP* 07061992
DDIC 19920706

SAP Landscapes:

Single-System (All in 1-box)
2 Tiers
3 Tiers
Multi Tiers

SAP Servers:

Development
Quality
Production

SID (System Identifier) starts with a character and ends with a character or digits. For example: CNN, CCC, CCN and CNC.

System Number consists of 2 digits (00..99) whre 98 and 99 are reserved for SAP use only.

SAP Work Process:

Dialog (DIA) - Online Transactions
Background (BTC) - Offline Transactions
Update (UPD/UP2) - Database Update
Spool (SPO) - Printing
Enque (ENQ) - Object Lock

SAP Services:

Gateway
Message Server

Minimum Work Process Requirements for 1 Server:

2 Dialogs
2 Backgrounds
1 Update
1 Spool
Only 1 Enque

ECC 6.0 supports unicode by default.

ERP SAP Day 2

2009-07-07T23:40:00.000+08:00

Sales Cycle:

Presales Activity
Sales Order
Inventory Sourcing
Delivery
Billing
Payment

Purchasing/Procurement Cycle:

Requisition
Vendor Selection
Purchase Order
Goods Receipt
Invoice Verification
Vendor Payment

Production Cycle:

SOP
MPS
MRP
Planned Order
Production Order
Shop Floor Control

Manufacturing Cycle:

Forecast
Sales Order Planning
MPS
MRP
Manufacturing Execution
Order Settlement

Sales Order is a document that specifies the product's material and quantity required by the customer.

MRP (Material Requirement Planning) is the generation of dependent requirements through BOM (Bill of Material) explosion.

Planned Order Processing is the conversion of the planned orders generated by MRP.

Purchase Requisition documents the request to purchase goods or services and it can be created manually or automatically through MRP process.

Purchase Order is a contract binding with a vendor to supply certain materials or services based on certain terms and conditions.

Goods Receipt is the recording of materials movement into the warehouse.

Goods Issue is the process where the material is issued from the warehouse to a production centre.

Invoice Receipt and Verification is the process of receiving the vendor invouce, comparing it with the purchase order and goods receipt. It also records the corresponding liability to the vendor.

Payment process reduces the liability to a vendor and a company's cash balance, records discounts taken and disburses payment.

Production Order (Proof of Order) is the authorisation for the shop floor to produce a material.

Completion Confirmation of the Production Order is the recording of actual results from production.

Production Order Receipt is the issuance of goods receipt into the warehouse which includes the quantity of the material produced (finished goods).

Customer Delivery is the transfer of goods of ownership by:

Creating a delivery document
Picking the goods for shipment
Physically trnasferring the goods to customer
Financially records goods issued

Customer Billing is the process of billing and invoicing the customer for goods delivered.

Payment Processing is the process of recording the customer's payment, increasing the customer's available credit, reducing receivables and recording cash discounts given.

Financial/Management Accounting and Reporting is a flexible set of toolds to record and analyze financial and management performance.

ERP SAP Day 1

2009-07-06T23:35:00.001+08:00

ERP (Enterprise Resource Planning) is a process management software on how to control business resources where the modules are tightly integrated.

SAP stands for System Application Products in Data Processing while R/3 means Real Time 3-tiers architecture, namely Database, Application and Presentation.

The 5 Ms that are required in operation a business are:

Money
Men
Machine
Methods
Materials

SAP Application Modules ( > 24 modules):

FI/CO - Financial Accounting/Controlling
MM - Materials Management
SD - Sales Distribution
PP - Production Planning
PM - Plant Management
HR - Human Resource
WM - Warehouse Management
PS - Project System
AM - Asset Management
WF - Workflow

SAP Social Lists ERP SAP

2009-06-11T15:38:00.001+08:00

SAP Social lists SAP ABAP blog as Jessica's SAP ABAP Blog under its ABAP category. Check out the website and many other SAP related topics such as BI-BW, CRM, ABAP, Basis, Finance & Controlling, Sales And Distribution, Materials Management, Production Planning, Human Capital Management and Quality Management.

Basic ABAP Languages Elements

2009-06-10T08:03:00.036+08:00

Work with Elementary Data Objects:

A Data Type is a formal variable description. SAP has 2 sets of ABAP Standard Types, namely Complete Type (Fixed Length) and Incomplete Type.

Complete ABAP Standard Types:

D - Date format: YYYYMMDD, length 8
T - Time format: HHMMSS, length 6
I - Integer type: length 4
F - Floating Point Number, length 8
STRING - Dynamic length character string type
XSTRING - Dynamic length byte sequence (HeXadecimal string)

Incomplete ABAP Standard Types:

C - Character string
N - Numeric string
X - HeXadecimal string
P - Packed number

The ABAP Standard Types can be used to define Local Data Type (defined in a program) or Global Data Type (defined in Data Dictionary).

Local Data Type Source Code Example:

*&---------------------------------------------------------------------*
*& Report YJN0301
*&
*&---------------------------------------------------------------------*
REPORT YJN0301.
*& Declaration of Local Data Types
TYPES my_char_type(8) TYPE c.
TYPES my_numeric_type(5) TYPE n.
TYPES my_packed_type(3) TYPE p DECIMALS 2.

In total, there are 3 categories of types, namely, Standard, Local and Global.

Define elementary data objects (simple variables):
A Data Object is a variable defined by means of a Data Type, ie. Standard, Local or Global. It can also refer to an existing Data Object using the LIKE addition when defining additional variables. VALUE keyword is used to pre-assign the Data Object Elementary value.

Data Object Source Code Example:

*&---------------------------------------------------------------------*
*& Report YJN0302
*&
*&---------------------------------------------------------------------*
REPORT YJN0302.
*& Declaration of Data Objects
DATA: my_percentage TYPE t_percentage,
my_number TYPE i VALUE 18,
group_number TYPE LIKE number,
my_city(15) TYPE c,
carrid TYPE s_carrid_id.

Fixed Data Object has fixed value such as Literals (Numeric and Text) and Constants (CONSTANTS and VALUE keywords).

Advantages of Global Standard Types as compared to Local Data Types:

System-wide Usability as defined in Data Dictionary
Can generate the where-used list which lists all the Repository Objects use the Data Object
Contains Data Element (Semantic information) and Domain (Technical information) of the Data Object

Use basic ABAP statements with elementary data objects:

Basic ABAP statements:

MOVE - Transfer a Data Object content to another Data Object
CLEAR - Resets the Data Object content to the type-specific initial value
CONDITIONAL LOOP - IF... ELSEIF... ENDIF; CASE... WHEN... ENDCASE
UNCONDITIONAL/INDEX-CONTROLED LOOP - DO... ENDDO; DO n TIMES... ENDO
HEADER-CONTROLED LOOP - WHILE... ENDWHILE
READ LOOP - SELECT... FROM ENDSELECT; LOOP AT... ENDSELECT
Arithmetic Expressions - +, -, *, /, ** (Exponentiation), DIV (Integral division without remainder), MOD (Remainder after integral division)

SY-INDEX System field contains the current loop pass.

The general rule in arithmetic processing sequence: Parenthesis, Powers, Multiplication, Division, Addition and Substraction.

MESSAGE statement sends Dailog Message to program users. The syntax is MESSAGE tnnn (message_class) [WITH v1 [v2] [v3] [v4]] ) .

Dialog Message Types (tnnn):

i - Information (Program continues after interruption at Modal Dialog Box)
s - Set (Program continues without interruption at Status Bar Next Screen)
w - Warning (Context-dependent at Status Bar or Modal Dialog Box)
e - Error (Context-dependent at Status Bar or Modal Dialog Box)
a - Termination (Program Cancelled at Modal Dialog Box)
x - Short Dump (Runtime error MESSAGE_TYPE_X triggered at Short Dump)

SAP provide DEMO-MESSAGES program for us to test the various behaviours of dialog messages.

Execute and analyse programs in debugging mode:

Ways to start a program in debugging mode:

While editing the Source Code via Object Navigator screen, access Exceute> Debugging OR Set/Delete breakpoint icon and Execute> Direct option. This is only valid for Active Source texts.
When the program is executed, either access System> Utilities> Debugging ABAP from Menu OR key in /h on the Command field and press Enter key.

ABAP Debugger can display up to 8 data objects at a time and set up to 10 Watchpoints at a time. Breakpoints can also be easily set.

Working with Structures:

Define structured data objects (structure variables):
Structured Data Object combines a set of logical values. A defined Data Object can refers to a Dictionary Structure, a Transparent Table or a locally declared Structure Type in a program.

A Locally Declared Structure Type Example:

*&---------------------------------------------------------------------*
*& Report YJN0303
*&
*&---------------------------------------------------------------------*
REPORT YJN0303.
*& Declaration of Locally Declared Structure Type
TYPES: BEGIN OF my_flight_info,
carrid TYPE s_carr_id,
connid TYPE s_conn_id,
fldate TYPE s_fldate,
END OF my_flight_info.

A Locally Defined Structured Data Object Example:

*&---------------------------------------------------------------------*
*& Report YJN0304
*&
*&---------------------------------------------------------------------*
REPORT YJN0304.
*& Declaration of Locally Defined Structured Data Object
DATA wa_scarr TYPE scarr.
wa_scarr-carrid = 'LH'.
SELECT SINGLE *
FROM scarr into wa_scarr
WHERE carrid = wa_scarr-carrid.
WRITE: / wa_scarr-carrid,
wa_scarr-carrname,
wa_scarr-url.

Structure fields are accessed using a hypen (-), ie. structure_name-component_name . Hence, a hypen should not be used as part of names.

Use basic ABAP statements for structured data objects:
MOVE-CORRESPONDING statement copies the source structure fields content to the target structure fields with the same fieldnames. All other structure fields remain unchanged. MOVE statement copy individual field.

Analyze structured data objects in debugging mode:
Structured Data Object field value can be seen in the ABAP Debugger.

Working with Internal Tables:

Define internal tables:
An Internal Table is a Data Object with identical Structured data records are stored at program runtime. The Internal Table size is managed dynamically by ABAP runtime system.

Internal Table Properties:

Line Type - Describes the structure of the table rows
Key - It can be either Unique or Non-Unique
Table Type - Either Standard, Sorted or Hashed

Index access means table record is accessed by specifying the corresponding row number while Key access means table record is accessed by entering a key value.

Standard Table can be accessed via Index or Key. It's Keys are Non-Unique and it is Primarily Index Access. Normally used when Index is mainly used to access the Internal Table.

Sorted Table can be accessed via Index or Key. It's Keys can be Unique and Non-Unique. It is Primarily Key Access. Normally used when Key is used to access the Internal Table and needs to be sorted by Key.

Hashed Table's Keys are Unique and it is Exclusively Key Access. Normally used in large Internal Table and needs to access by Key only.

Table Type is the type of an Internal Table which can be described globally (Data Dictionary) or locally.

A Table Type declared in Data Dictionary with Program-Internal definition of a table variable with reference to the Table Type:

*&---------------------------------------------------------------------*
*& Report YJN0305
*&
*&---------------------------------------------------------------------*
REPORT YJN0305.
*& Declaration of Internal Table with Local Types
TYPES my_flightinfo
TYPE STANDARD TABLE OF sbc400focc
WITH NON-UNIQUE KEY carrid connid fldate.
DATA company_flightinfo TYPE my_flightinfo.

Directly define an Internal Table (without referring to Data Dictionary) Example:

*&---------------------------------------------------------------------*
*& Report YJN0306
*&
*&---------------------------------------------------------------------*
REPORT YJN0306.
*& Declaration of an Internal Table Definition
TYPES: BEGIN OF my_strtype,
carrid TYPE s_carr_id,
connid TYPE s_conn_id,
...
END OF my_strtype.
DATA my_table TYPE SORTED TABLE OF my_strtype
WITH ... KEY ...

Use basic ABAP statements with internal tables:

Basic ABAP Keywords:

APPEND - Append a Structure content to an Internal Table and can only be used in the Standard Tables.
INSERT - Inserts a Structure content to an Internal Table. In a Standard Table, the content is appended. In a Sorted Table, it is inserted according to the Key. In a Hashed Table, it is inserted to the Hash Algorithm.
READ - Copies the a table row to a Structure
MODIFY - Overwrites a table row with the structure content
DELETE - Deletes a table row
COLLECT - Accumulates the structure content to a table that has the same Key and can only be used for tables whose non-key fields are all numeric.
LOOP... ENDLOOP - Places the rows of a table into a structure
DELETE - Deletes the table rows

In the LOOP... ENDLOOP statement, sy-tabix system field contains the current table entry row number. FROM.. TO... keyword is used to access certain rows in a table. Code example: LOOP AT my_flughtinfo INTO wa_flightinfo FROM 1 TO 8.

READ TABLE statement is used to read a single record and the INDEX keyword is used to specify the row number of the required record. Code example: READ TABLE my_flightinfo INTO wa_flightinfo INDEX 6.

In the LOOP... ENDLOOP statement, WHERE keyword is used to access certain rows of a table. Code Example: LOOP AT my_flughtinfo INTO wa_flightinfo WHERE carrid = 'LH'.

In READ TABLE statement, WITH TABLE KEY keyword is used to read a certain row of a table based on Keys. All Key fields need to be filled. Sy-subrc system field is set to 0 if the READ result is successful. Code Example: LOOP AT my_flughtinfo INTO wa_flightinfo WITH TABLE KEY carrid = 'LH' connid = 1234.

SORT statement is used to sort a table in ascending (default) or descending order by table keys or columns. AS TEXT keyword is used to implement lexicographical sorting. STABLE keyword ensures the relative order of data records which has identical sort keys to remain intact during sorting.

ABAP Statements in deleting the Table Contents:

REFRESH - Deletes the entire table contents
CLEAR - In a table without header line, it deletes the entire table contents (same as REFRESH) while in a table with header line, it only initializes the header line.
FREE - Deletes the entire table contents and releases previously used memory.

HEADER LINE is obselete! So, do not use TABLE with header-line.

Analyze internal tables in debugging mode:

Internal Table field value can be seen in the ABAP Debugger.

SAP Social Links ERP SAP

2009-06-09T08:46:00.001+08:00

SAP Social is a website by Eddai who assembles all SAP related articles into a single page. ERP SAP is linked as an SAP Blog site in SAP Social website. Thanks Eddai for the link!

" 6.If you want to practise yourself for SAP, widely recommended tip is to install SAP Netweaver Trial on to your own pc. Its license last for 4 weeks, but Jessica shows you how to extend your SAP Netweaver Trial Version on her site."

Introduction to ABAP Workbench

2009-06-08T15:42:00.012+08:00

Repository and Object Navigator:

Describe the structure of the Repository:
Repository consists of all development objects of the system, namely programs, function modules, database tables definitions and many other objects. It is in the Database layer and is always independent of the system client.

Name and use the search tools of the Repository:
Repository Information System is a big container for random search of Repository Objects which is accessed via transaction code SE84. The Tree Structure include Development Coordination, Business Engineering, ABAP Dictionary, Program Library, Class Library, Web Dynpro, BSP Library, Enterprise Services, Enhancements, Test Objects and Other Objects.

Use the Object Navigator for displaying Repository objects:
Object Navigator includes all the tools required for creating and editing Repository Objects via transaction code SE80. The tools cover the whole SDLC (Software Development Life Cycle) which include ABAP Editor, ABAP Dictionary, Screen Painter, Menu Painter, Function Builder and Class Builder. Important areas on the Object Navigator screen include Navigation Area (in the middle), Tools Area (top toolbar) and Context Menu (left-hand side that displays the relevant functions to the selected Object). Navigation in the Navigation Area is independent in the Tools Area.

Developing Programs and Orginizing Developments:

Name the use the utilities for orderly software development:

An Orderly Software Development Organization:

Project Manager creates Change Request
Assigns to Project Developer in the Transport Organiser of directly in the ABAP Workbench
A Task is auto-created by the Transaport Organiser to work on the assigned work
Project Developer assigns all development objects created or edited into the assigned Change Request and Task which ensures all relevant objects are transported to the live environment upon project completion
Upon completion of development task, Project Developer releases his/her task within the Change Request. All objects from the Task will be automatically transferred from Task to Change Request level. Project members can still edit the Objects
Project Manager releases the Change Request when all tasks related to the Change Request have been released by all Project Developers.
This concludes the project. All Object locks will be released. Copies of the developed objects are exported to the System's Own Transport directory until the System Administrator imports them to the intended target system.

Create packages:
Object Navigator via transaction code SE80 is used to create Package. Package is assigned to Change Request.

Create programs:

Use transaction code SE38 (ABAP Editor) or SE80 (Object Navigator) to create ABAP programs. ABAP program needs to be assigned to a Package. Pretty Printer applies cosmetic changes to the ABAP source code.

Characteristics of ABAP Programs:

Is Typed (type-specific data processing, type conversion and type casting)
Is especially designed for dialog-based business applications
Is not case-sensitive
Enables multi-language applications via text elements
Enables SQL access via CLOSED SQL or OPEN SQL
Enhanced to include Object Oriented features (ABAP Objects)
Is Platform independent
Is upwared-compatible which is able to run in future releases
Needs to be activated before it is visible system-wide

ABAP program Activation includes:

Saving the Object as an inactive version
Syntax or Consistency Check of the inactive version
Overwrites the previous active version(only after a successful check)
Generates the respective runtime objects for later executions

Create transactions:
Use transaction code SE80 (Object Navigator) to create transaction. Only transactions can be included in a Role Menu or as Favourites of a User. Transactions need to be assigned to a Package.

Day 6 The Data Dictionary, Part 4 Questions

2009-06-07T09:31:00.002+08:00

Q. How can the storage parameter of an activated table within the SAP system be modified?
It is done via transaction code SE14 and the Storage Parameters button.

Q. Is it possible for the definition of a table and the data elements and domains be out of sync?
Yes, it is possible. That explains why any changes to a domain needs the domain and table to be reactivated. A consistency check should also be performed.

Day 6 The Data Dictionary, Part 4

2009-06-06T09:28:00.004+08:00

Changes like insert, update or delete to data in a table can be logged and normally known as Automatic Table History. We just need to tick the Log data changes checkbox on the Data Dictionary - Technical Settings screen. DBTABPRT table stores the data changes history. Automatic Table History is normally used for table that contains critical information and the changes need to be tracked.

Active version is when the Activate button is pressed while Revised version is when the Save button is pressed without the Activate button. In the Revised situation, the last Active version is still valid and used.

We can modify or examine tables at database level via transaction code sE14 (ABAP Dictionary - Database Utility). The comparison between Data Dictionary and database can be made. The utility also support viewing of the table activation log, storage parameters and to drop and re-create a table in the database.

Day 5 The Data Dictionary, Part 3 Questions

2009-06-05T10:52:00.005+08:00

Q. When transaction code ST02 is used to display table buffers, there are a lot of other buffers shown. What are they?
Table buffers are 2 of the buffer types bufferred in the Application Server. Other buffered types are nametabs (table runtime objects), program, CUA, Screen, Calendar, OTR, Export/Import and Exp. / Imp. SHM.

Q. Can I create Secondary Indexes on SAP tables?
Yes. However it needs a modification key from SAP via the SAP Service Marketplace.

Q. Can I compare the differences of a program in terms of using buffered table and not using a buffered table?
Yes. It can be done via the Runtime Analysis Tool (transaction code ST02 - Detail Analysis Meny button).

Day 5 The Data Dictionary, Part 3

2009-06-04T13:50:00.015+08:00

A Table Primary Index is a mechanism used to locate table records faster because table records are traditionally stored in the arrival sequence. The table index is a sorted key that consists of 1 or more table columns. It is stored together with the record number in the table for easy retrieval.

A Table Secondary Index allows us to search table records based on columns other than the Primary Key fields. In other words, it supports a where clause on a non-primary key field.

Considerations in Creating Indexes for Records to be Found:

Specify the fields in the where clause in the same order as they appear in the table index
If a table begins with the mandt field (SAP Client Number), the index needs to include the mandt field too

Transaction code SE11 (ABAP Dictionary) is used to display the Table Primary Index and Secondary Index (Indexes button).

SQL Trace is used to check the performance of a SQL statement. Only 1 person can perform an SQL Trace at a time. Transaction code ST05 is used to access the Performance Analysis - SQL Trace option.

Transaction code SE13 (Dictionary: Technical Settings) is used to display the table technical settings.

Data Class is used to determine the tablespace (such as Oracle or DB2) that the table is assigned to. The main data classes are APPL0 - Master Data, Transparent Tables; APPL1 - Transaction Data, Transparent Tables and APLL2 - Organization and customizing.

APPL0 - Master Data, Transparent tables data class is not often updated and grow slowly. Examples of the APPL0 data class are Customer master table and Vendor master table.

APPL1 - Transaction Data, Transparent Tables data class is often updated and grows pretty fast. Tables that contain orders from customers are examples of APPL1 data class.

APLL2 - Organization and customizing data class is where table's contents are pre-determined before implementation and do not change regularly after the implementation. Examples of the APPL2 data class are Check tables and their associated Text tables.

Size Category specifies the number of records that a table holds. It specifies the initial extent and the next extents as well as the maximum number of records. It is better to be over-estimate the table size than to under-estimate.

Buffering enables data to be accessed faster from the application server than the database, provided data exists in the Buffer. Transaction code ST02 displays the buffers and usage statistics.

Buffer Synchronization is a process that occurs at a period interval (as set by SAP BASIS consultant) to synchronize the data in buffer with the database. Use bypassing buffer on the select statement when the buffer data needs to be ignored and the most recent data from the database needs to be obtained.

3 types of Buffering Types:

Single records buffering - Only select a single record into the Buffer using the select single statement. Even no record is selected, an entry is still made into the Single Record Buffer which simply means the record doesn't exist in the Buffer. It is suitable for large table but only a small percentage of the table records are selected.
Generic Area Buffered - A group of records are loaded into the Buffer. No. of key fields field indicates how many left-most fields in the primary key will be used to group the records. For example, if the No. of key fields field is filled with 2, it simply means all records having the same value in the first 2 fields of the primary key will be loaded into the Buffer. It is suitable for tables in which records are accessed as a group. During Buffering Synchronization, if a record is invalidated in the Buffer, all records in the group will be invalidated.
Fully Buffered - Any attempt to read data from the table brings all the table records from the database into the Buffer. The whole table is still loaded to the Buffer eventhough no record matches the select statement. It is normally used for small table that seldom change. During Buffering Synchronization, the entire table is invalidated if any record within it changes.

Transaction code /$tab is used to clear the table buffer.

ABAP Program Process

2009-06-03T10:32:00.010+08:00

System Architecture and ABAP Program Using Example of Selection Screen and List:

Describe the architecture of the SAP Application Server:
SAP Application Server follows the software-oriented client/server modular architecture. The layers that serve as the basis for system scalability in SAP Application Server are Database, Application Server and Presentation Server.

Describe how a simple dialog program is executed by the ABAP runtime system:

PRESENTATION LAYER - User logs on to the SAP system and a screen is displayed. User then selects an ABAP program via the menu.
APPLICATION LAYER - System loads the program context data from Database Repository into the Application Server layer. Then the ABAP runtime system controls the subsequent program flow. It displays the selection screen (selected menu program has a selecttion screen) back to the Presentation layer.
PRESENTATION LAYER - User keys in selection criteria and choose the Execute button. Control is now at the Application Server layer. Entered criteria is stored and ABAP runtime system resumes the control of processing and pass the control to the Database layer for a read command in the ABAP program.
DATABASE LAYER - Database gains control and fetch the database records as stated by the ABAP program.
APPLICATION LAYER - ABAP runtime system receive the database records and process the data layout. ABAP runtime system then passes the data list to the Presentation layer.
PRESENTATION LAYER - Presentation layer displays the list onto the screen.

Sources of Information for Developers

2009-06-02T20:53:00.005+08:00

SAP Service Marketplace:

SAP Service Marketplace (formerly known as OSS user or SAPNet user) is catered specifically for SAP's customers and partners.

List some of the services provided on the SAP Service Marketplace:

Administrating SAP Service Marketplace Users
Requests Developer Key to create or change SAP Objects
Notes Database
Note Assistant tool that automatically import corrections to ABAP code from SAP Notes into SAP system (SNOTE transaction code)
Corrections can be downloaded as patches while Messages can be sent to SAP Support for assistance
Allow SAP Support Staff to access to your company's SAP system to troubleshoot an issue using Service Connection (/serviceconnection). Known services include Remote Consulting (/removeconsulting) and Early Watch (/earlywatch). Other available services are listed under Service Catalog (/servicecat)
Locate SAP Software Requirements for specific releases (/platforms)
Latest development on SAP. For example, SAP Netweaver area under /netweaver
Plan for Hardware Investments using Quick Sizer (/quicksizer)
Locate SAP related contacts. For example, SAP Partner contact is under Partner Directory (/partnerdir)
Locate and book SAP Training under Education Services (/education)

Find and use SAP Notes in the SAP Service Marketplace

SAP Developer Network:

SAP Developer Network (SDN) is an online community for SAP developers, consultants, Architects and Intergrators. Registered members can access more technical information.

List some of the services of the SAP Developer Network:

Access to technical articles and reviews
Access to e-learning material
SDN online forum
Weblogs
Webinars
Netweaver business content such as portal business content
SDN Newsletter (mail out every 2 months)
Access to download zones

Find development news in the SAP Developer Network

Communication and Integration Technologies

2009-06-01T09:48:00.017+08:00

Cross-System Business Processes:

Name various cross-system business process:
Cross-System Business Process occurs when more than 1 system exists in a company setup. For example, a company may have Human Resource (HR) and Finance systems. Every month, employee salary may need to be transferred from the Finance system to the HR system. Hence, a certain business processes agreement need to exist.

Explain the ideas behind the ALE concept:
ALE (Application Link Enabling) enables distributed applications to be able to talk to each other via a method. It uses business-controlled message exchange method and integrated through Synchronous and Asynchronous communications. Issues pertaining to the data need to be identified, namely Who, Which, When, With Whom and By What means.

Remote Function Calls and BAPIs:

List various interface technologies used by the SAP systems:

ALE - Application Link Enabling
BAPI - Business Application Programming Interface
CPI-C - Common Program Interface Communication
EDI - Electronic Data Interchange
HTTP - HyperText Transfer Protocol
LU 6.2 - Logical Unit Type 6.2
RFC - Remote Function Call
OLE - Object Linking and Embedding
SMTP - Simple Mail Transfer Protocol
SOAP - Simple Object Access Protocol
TCP/IP - Transmission Control Protocol / Internet Protocol
XML - Extensible Markup Language

Describe the process for a Remote Function Call:
Remote Function Call (RFC) is an SAP interface protocol based on CPI-C and TCP/IP. Calling system needs to identify an RFC Connection or an RFC Destination and the Import & Export parameters as defined in the Function Builder. Transaction code SM59 is used to manage the RFC connections. Every RFC interface is bidirectional.

In ABAP program, RFCs are used to call another function module in another system:

CALL FUNCTION
DESTINATION
EXPORTING .....
IMPORTING .....

Explain the significance and use of business objects and their BAPIs:
The SAP Business Object Repository (BOR) contains Business Object (BO) which include Business Application Programming Interface (BAPI) methods. Transaction code SWO1 is used to view the available BAPIs in BO while BAPIs are created and tested via transaction code SE37, just like any other function modules. BOR (BAPI Explorer screen) can be directly accessed via transaction code BAPI. BAPIs are typically used to link business processes across systems; to connect SAP system to the internet or to connect to external programs.

Make a Remote Function Call

Web Services:

Explain Web Services:

A Web Service makes the individual application function available as a service over the internet. The basic Web Service standards in the SAP Web Application Server are eXtensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Service Desccription Language (WSDL) and Universal Description, Discovery and Integration (UDDI).

Describe UDDI and WSDL:
UDDI is a directory service for dynamic Web Services which is provided via a SOAP interface.

WSDL is a meta language used to describe the function of a Web Service. Functions, Parameters and Return Codes of a Web Service will be described in a machine-readable form.

SAP Business Workflow:

Describe the SAP Business Workflow concept:

A Business Workflow model breaks a business process into individual steps which are then assigned to respective people or roles. Its purpose is to increase the speed and transparency of business processes.

Explain the flow of a workflow process:
A Workflow process involves 2 views, namely Workflow Participants view and the Technical view used to clarify the system process. A Workflow process contains events and decisions that need to be made by participants.

Submit a leave request within the SAP Business Workflow:

TRIGGER - Employee requests for leave
EVENT - A leave request event is triggered
DECISION - Surpervisor decisdes on the leave approval
EVENT - Approval granted or rejected
DECISION - Employee decides whether to change or cancel the request
EVENT - Employee decides on a change or a cancellation

Describe additional application areas for the SAP Business Workflow concept:

SAP Business Workflow is mainly used in SAP CRM (Curtomer Relationship) or SCM (Supply Chain Management) modules which include:

Facilitating communication
Controlling and monitoring simple processes
Controlling complex processes
Automating the information distribution on work in progress to all parties
To trigger cross-system activities in remote systems

SAP NetWeaver 7.01 SR1 ABAP Trial License Installation

2009-05-31T09:19:00.002+08:00

I had lots of funs installing the New License Key e-mailed by SAP License Auditing Services team. The SAP NetWeaver 7.01 SR1 ABAP Trial Version period extension wasn't a smooth sailing. This is what I did:

I keyed in SLICENSE transaction code on the SAP GUI System
On the SAP License Administration screen, I selected the New Licenses button and the SAP License Administration # Digitally-Signed License Keys screen was displayed
I selected the Install button in the middle of the screen
I browsed to the NSP.TXT file that was received from SAP License Auditing Services team. I hit a problem! I received an error message (This system's system number is "333333333333333333", but there is a license key for system number "888888888888888888" in the license key file). It hit me that I might need to delete the old license before the new license could be installed. So, I went ahead and deleted the old license. Then, I logged off and tried to login again using BCUSER User ID. I couldn't!! Then, I logged in using SAP* User ID and I could. After spending time searching for solutions on the net, I found a workable solution. I edited the NSP.TXT file and changed the SYSTEM-NR number provided by SAP team to my current System Number, as stated on the SAP Licence Administration screen. Then I tried the new license key installation and it worked!!! A successful message was displayed (1 SAP license key(s) successfully installed).

Now, the SAP NetWeaver 7.01 SR1 ABAP Trial Version has been extended for another 90 days.

Extending SAP NetWeaver 7.01 SR1 ABAP Trial Version Period

2009-05-30T13:48:00.007+08:00

SAP NetWeaver 7.01 SR1 ABAP Trial Version lasts for 4 weeks. If we like to extend the trial version usage period, we can do so by requesting for a License Key from SAP:

Access the SAP Sneak Preview License Key Request website
On the SAP Sneak Preview License Key Request webpage, fill in the required data (Personal Data and System Info) and Select the I Agree checkbox. You need to be a Software Developer Network (SDN) member to have the SDN User id. Select NSP - SAP NetWeaver 7.0/2004s (SP9 and higher) as the System ID. Hardware key (HWID) can be obtained by keying in SLICENSE (SAP License Administration) transaction code on the SAP GUI Command Field. The Active Hardware Key is the required Hardware key (HWID). Click on the Submit button to submit the completed form.
Upon completion of the form submission, a notification message will be displayed (Your request has been successfully submitted. You will receive an email with your license key information)

I received the License key notification DEMOSYSTEM / NSP‏ e-mail in less than 5 minutes upon submission of the above form.

The System Kernel

2009-05-29T12:04:00.015+08:00

Principal Architecture of the SAP Web Application Server:

Outline simple client/server configuration:

Single-Tier> All processing tasks (database, application and presentation processes) are performed in a single computer
Two-Tier> Presentation process performed in separate layer as compared to database and application layer
Three-Tier> Each process has its own layer
Multi-Tier> An additional layer (eg. Web Server) is added on top of the Three-Tier confirguration

ABAP Applications Architecture: Client-Side Presentation (Browser or SAP GUI), Server-Side Presentation Logic/Application Logic (BSP - Business Server Pages, Screen and Functions, ABAP Programs, BAPIs) and Database. Server-Side Presentation Logic/Application Logic is also known as ABAP Application Server.

Java Applications Architecture: Client-Side Presentation (Browser - Plain HTML or Java Applet), Server-Side Presentation (Web Container - JSP and Servlets), Application Logic (EJB Container - EJB) and Database. Server-Side Presentation and Application Logic is also known as J2EE Application Server.

Name the most important processes on an SAP Web Application Server:

ABAP Environment:

ABAP Dispatcher
Dialog work process
Spool work process
Update work process
Background work process
Enqueue work process
Message Server (MS)
Gateway Server (GW)
Internet Communication Manager (ICM)

Java Environment:

Java Server Process
Java Message Service Process
SAP Java Connector (JCo) Process

Define the term instance and recognize the characteristics of a central instance:

An Instance (Application Server) is an administrative unit that combines SAP system components providing 1 or more services.

A Central Instance is a collection of processes that are distinguished from other instances within the SAP system. The Message Server (MS) is used as a communication among the instances (ABAP Dispatcher).

Describe the processing flow for user requests in the SAP systems:

Processing User Requests by the SAP GUI:

User Logon via SAP GUI (Presentation Layer)
ABAP Dispatcher allocate the Work Process for the User Logon request (Application Layer) based on the First-In-First-Out principle. Buffer is used to speed up the processing.
Work Process connects to the ABAP Schema of the database if data is required for reading or update (Database Layer).
Once the above process is complete, the Work Process sents the result via ABAP Dispatcher back to the SAP GUI. SAP GUI interprets the received data and display onto the screen.

Processing Web Requests:

Internet Communication Manager (ICM) accepts web requests which can either be processed by ABAP Work Process or SAP Web Application Server Java. ICM uses the URL to decide on its destination.
If it is a Java runtime environment request, it is sent to the Java Dispatcher which will forward to the Java Server Process. If database data is required, the Java Schema of the database will be accessed. The result will then be passed back to the Java Dispacther and reply is sent to the ICM. ICM will forward the result back to the user.

Dialog Processing in the SAP System:

Outline the processing flow for a dialog step in the SAP system:

User sends a dialog request to the SAP system
SAP Web Application Server receives the user request
Request is placed in a Request Queue
Work Dispatcher distributes the Request Queue requests to the available Dialog Work Process on a First-In-First-Out basis
The selected Work Process rolls in the User Context and process the User Request
Once completed, the Dialog Work Process returns the results to the Dispatcher and rolls out the Context back to the Shared Memory
Dispatcher returns the results back to the SAP GUI for display

Describe the concept for work process multiplexing:

Work Process Multiplexing occurs when individual dialog steps for a program consisting of multiple screeens are executed by different Dialog Work Process during program runtime.

Communication with the Database:

Describe how the SAP system communicates with the database:

ABAP Interpreter sends a request to the database
The Database Interface reads the data from the SAP Web Application Server's local buffer
If required data is not present in the local buffer, the Database Interface converts the OPEN SQL in ABAP program to NATIVE SQL
NATVE SQL is then used to retrieve data from the Database

NATIVE SQL statements can be used in ABAP program by including the commands in a EXEC SQL - END EXEC bracket.

List the advantages of open SQL statements:

It allows ABAP program to be database-independent

Day 4 The Data Dictionary, Part 2 Questions

2009-05-28T16:30:00.004+08:00

Q. Can Data Referential Integrity be enforced via the Integrity Constraints creation at the DBMS (Database Management System) level?
No. Don't update the DBMS level directly as it will cause inconsistency between SAP Data Dictionary and DBMS. Always use the Data Dictionary to update the data definitons.

Q. Can Structures have Foreign Key definitions?
Yes. It is normally done because a table that includes a structure can inherit foreign key definitions as well. However, the Inheritance can be turned off when the structure is included in a table.

Day 4 The Data Dictionary, Part 2

2009-05-27T08:43:00.011+08:00

A Foreign Key is a table field that is connected to another table via a foreign key relationship which is used to validate the data entered by checking against a valid set of values in another table. Foreign Key Table stores the foreign key. Check Table contains the valid set of values.

Foreign keys are checked via user interface only and do not exist in the database. Therefore a database update statement can easily violate the database referential integrity because referential integrity constraints are not kept in the database. An User Interface validation (BDC - Batch Data Communication or BAPIs - Business Application Interfaces) is required if an ABAP program needs to update the database whose data are from outside source.

Technical Requirements for Creating a Foreign Key:

The Foreign Key must be checked against a field within the Check Table's Primary Key

The Foreign Key Field's domain names must be the same as the Check Table Field

Transaction Code se11 - ABAP Dictionary is used to create Tables and Structures while se16 - Data Browser is used to create, edit or view data in tables.

A Compound Foreign Key is a foreign key that composed of 2 or more fields.

In a Compound Foreign Key, the Check Field is the field where it is defined as the foreign key. Hence, a filled Check Field triggers the check against the Check Table. Other filled fields within the Compound Foreign Key will not trigger the validation.

Cardinality of the Foreign Key Relationship describes how many rows of data are allowed in the Foreign Key Table for each row in the Check Table. Cardinality is described as X:Y where X refers to the Check Table while Y refers to the Foreign Key Table.

X Values:

1 - A deletion in the Check Table always triggers a deletion of the corresponding data in the Foreign Key Table
C - A deletion in the Check Table may occur without a deletion in the corresponding data in the Foreign Key Table

Y Values:

1 - There is always 1 and only 1 row in the Foreign Key Table for each row in the Check Table
C - There is, at the most, 1 row in the Foreign Key Table for each row in the Check Table
N - There is always at least 1 row in the Foreign Key Table for each row in the Check Table
CN - There might or might not be rows in the Foreign Key Table for each row in the Check Table

Cardinality is optional in SAP system and it is not used to determined if data can be updated into the a table. It is only used when an Aggregate Object is created in Data Dictionary. An Aggregate Object is a Data Dictionary object that has more than 1 table such as a View.

A Text Table is a table that contains spoken-language descriptions of values in a Check Table. These descriptions are stored in multiple languages. Text Table and Chek Table have the same Primary Key with an additional Language field in the Text Table.

A Generic Foreign Key is a Foreign Key in one the Check Table's Primary Key Fields which is marked as Generic. It simply means it doesn't have a counterpart in the Foreign Key Table and it is not part of the validation keys.

Constant Foreign Key are Compound Foreign Keys where one of the Check Table Field Names is replaced by a Constant value which is shown under the Create Foreign Key screen.

Adapted Foreign Key is where not all the Foreign Key Fields of a Compound Foreign Table reside in the same table.

Value Table Field in the a domain is used for the following purposes:

It is automatically proposed as the Check Table when creating a Foreign Key
It provides a list of values for F4 (Possible Entries) without the validation

Currency Fields have 2 fields, namely Currency Field (Amount) and Currency Key Field (Currency Code). Currency Field has 2 requirements: 1) The Domain Data Type must be CURR 2) It must be linked to a Field of Type CURKY which holds the Currency Key.

Quantity Field is a field that contains numeric measurement with 2 requirements: 1) The Domain Data Type must be QUAN 2) It must be linked to a Field of Type UNIT.

A Structure is a series of fields grouped together under a common name. It is very similar to a table. It can be used within a program on the table statement to define a work area. A same name for both Structure and Table cannot be created.

Differences between a Structure and a Table:

A Structure doesn't have a Primary Key
A Structure doesn't havetechnical Attributes (Data Class or Bufferring)

A Nested Struture is possible. .INCLUDE field is used to include a structure within another structure or table. Include Chain is including a Structure within a Structure. The maximum nesting depth is 9 and only 1 tablecan be included in an Include Chain. A Table cannot be included within a Table.

The same Structure can be included many times in a Struture by using .INCLUDE-XXX where XXX represents a 3 alphabets to make the included structure unique.

Day 3 The Data Dictionary, Part 1 Questions

2009-05-26T15:42:00.004+08:00

Q. How to locate all the tables that are using a domain?
Use the Where-Used List button on the Application Toolbar.

Q. What will happen to the current table fields with data that use an existing domain which data length has been shortened?
When the changed domain is activated, the system will attempt to activate the current tables that are dependent upon the changed domain. Tables with lost data will fail and will be shown. If we proceed with the tables activation, the system will automatically convert the data which fields are referenced by the changed domain. Hence, data will be truncated.

Q. For fields of type DEC (Decimal), is the decimal point stored as part of the field value?
No. The decimal point location is part of the field description, It is stored in the domain.

Q. Among the 4 data browsers (se16, se17, sm30 and sm31), which transaction code cannot be used to update data?
se17 - General Table Display

Day 3 The Data Dictionary, Part 1

2009-05-26T12:34:00.017+08:00

Table Types in SAP Data Dictionary:

Transparent Table
Pooled Table
Cluster Table

Transparent Table:

Reflects the actual table in a database such as Oracle
One-To-One relationship with the database
Has the same table name, same number of fields and same fieldnames with the database
Normally holds Application Data (Master and Transation Data)
Used by customers

Pooled Table and Cluster Table:

Many-To-One relationships with the database
Has the different table name, different number of fields and different fieldnames with the database
Normally holds System Data (System Configuration Information and Historical Data)
Used by SAP with an SAP proprietory format

Pooled Table has many tables in SAP but only 1 table (Table Pool) in SAP Data Dictionary. Tables in SAP may or may not have primary key fields in common.

Cluster Table has a few tables in SAP but only 1 table (Table Cluster) in SAP Data Dictionary. Tables in SAP must have at least 1 primary key field in common and the tables are usually all read at the same time.

A Table Pool is a database table with a special structures that enables the data of many SAP tables (Pooled Tables) to be stored in it. Then the Table Pool is reflected as a table in the database. Table Pool reduces the amount of database resources needed when small tables (Pooled Tables) need to be open at the same time. For eg. customizing data.

A Table Cluster holds Cluster Tables which have similar primary key fields and the data of the tables are accessed sumultaneously. For eg. Order table and Detail table are cluster tables which is assigned to a single table (Table Cluster).

Table Cluster has fewer tables than Table Pool and rows are combined based on the common primary keys in cluster tables. Only a single I/O is needed when a row is read from any of the tables in the cluster.

Pooled and Cluster Tables Limitations:

Secondary indexes cannot be created
Cannot use ABAP select distinct or group by statements
Cannot use Native SQL
Cannot specify fieldnames after the order by clause with only the order by primary key clause permitted

A table is composed of fields that are composed of data elements, which in turn, are composed of domains.

Data Elements contains the semantic characteristics of the fields with field labels and online documentation (F1 help).

Domain contains the technical characteristics of a field such as field length and data type.

Use the forward-navigation creation method to create the Data Elements and Domains of a Table, starting with the Table definition.

In order to determine if a new data element/domain needs to be created or to reuse the existing data element/domain, check if the field is dependable on the respective SAP data element/domain. For eg. a vendor id field in a new table is dependable on the vendor id in the SAP with the same data element and domain. Hence, as change in future on the SAP vendor id (data element/domain) will be automatically reflected on the table vendor id.

All table, Data Element and Domain names must begin with y or z. Fieldnames can begin with any character but not using the SAP reserved words. TRESE table contains all the reserved words.

All Data Dictionary Objects need to be activated before they can be used, inclusive of changes.

Use se16, se17, sm30 and sm31 for data update, delete or browsing. se16 is more complex than se17 and sm31 is an older version of sm30 with less functionalities. Use se17 if you need to specify multiple sort criterias. Use se16 for daily data dsiplay or update. Use sm31 for table that has a standard maintenance dialog. Transaction Codes use sequence is se16, sm31, sm30.

Create your own ABAP program to display a table (ZJN0301 Source Code):

*&---------------------------------------------------------------------*
*& Report ZJN0301
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT ZJN0301.
tables sflight.
select * from sflight.
write: / sflight-carrid,
sflight-connid,
sflight-fldate,
sflight-price.
endselect.
if sy-subrc <> 0.
write 'Table is empty.'.
endif.

Use Documentation button on the Dictionary: Data Element Display screen to add F1 Help to a Field. Use menu path Include> Link on the Documentation screen to add hyperlinks to F1 Help.

Navigation

2009-05-25T21:34:00.003+08:00

Navigation in General:

Log on to the system successfully

List some variants of the SAP GUI:

SAP GUI for Windows environment
SAP GUI for Java environment
SAP GUI for HTML

Name and use elements of a SAP GUI screen:

Menu bar
Standard toolbar
Title bar
Application toolbar
Command field
Tab page
Input fields
Checkboxes
Radio buttons
Status bar

Log off from the system successfully

Advanced Navigation in the SAP GUI:

Use various methods to start SAP system functions:

Enter Transaction Code in Command field
Access Role-based menu

Create a list of favourites

Use the help functions:

F1 - Application and Technical information
F4 - Possible Entries
SAP Library

Carry out complex, selective searches (Selection Options):

Search for individual values
Search for value areas
Search using selection options
Excluding individual values
Exclusion from value ranges
Exclusion via the corressponding selection options
Multiple selection

Sort and filter listed data

Execute a where-used list:

Find out the use of a program element

Describe the standard menus System and Help:

Standard menu in all SAP screens

Appendix - Personalizing the User Interface:

Options for personalizing the appearance of SAP GUI:

Standard Toolbar> Customize Local Layout (Alt-F12)
System menu> User Profile> Own Data

SAP Solutions

2009-05-25T15:10:00.005+08:00

mySAP Business and mySAP ERP:

Name the options for using mySAP Business Suite and mySAP ERP:

SAP Netweaver
mySAP Business Suite - links people, information and processes.
SAP Smart Business Solutions - mySAP All-In-One & SAP Business One
SAP xApps (SAP Collaborative Cross Applications)
Industry Solutions

Cross-enterprise processes integration include various technologies such as ALE, EDI through XML, xApps and Web Serives

SAP Internet sites:

SAP Netweaver - An Overview:

Name the integration aspects of SAP Netweaver:

People Integration
Information Integration
Process Integration
Application Platform

Explains the concepts of the individual integration levels of SAP Netweaver:
People Integration:

Enterprise Portal functions include single sign-on, iviews, search and collaboration
Enterpirse Portal roles include iView, Page and Workset
Business Package provides standard content with target groups for Users (ESS - Employee Self Service), Managers (MSS - Manager Self Service) and Specialists
Mobile Infrastructure

Information Integration:

Business Intelligence, Business Process Management, Master Data Management
OLTP (Online Transaction Processing) and OLAP (Online Analysis Processing)
3 level of SAP BW architecture: Data Sources, BW Server and Reporting

Process Integration:

SAP Exchange Infrastructure (SAP XI) for integrations of business-to-business communication and cross-system business process management

To Populate Flight Model Tables

2009-05-24T15:38:00.000+08:00

Upon completion of the SAP NetWeaver 7.01 SR1 ABAP Trial Version installation, the Flight Model Tables (SPFLI, SFLIGHT and SBOOK) are empty. If we try to access the tables data, a message (No table entries found for specified key) will be displayed at the bottom of the screen. Hence, we need to populate the tables with default data if we would like to use them in our programs:

Access SAPBC_DATA_GENERATOR program source code via ABAP Editor (se38 transaction code)
Select the Direct Processing (F8) on the source code screen
Accept the the default option (Standard Data Record) on the Create Data for Flight Data Model screen and Select the Execute (F8) option
Click on the Yes button when a warning message is displayed (Caution: Old table entries will be deleted and regenerated. Is this OK?)
Access Data Browser screen (se16 transaction code) to confirm that the Flight Model Tables have been populated, SPFLI=26 records, SFLIGHT=400 records and SBOOK=98830 records

SAP Certified Development Consultant SAP NetWeaver 2004 - Application Development Focus ABAP

2009-05-24T09:48:00.007+08:00

Booking Code: C_TAW12_04
Software: Software components: SAP Web Application Server 6.40
Number of Questions: 80
Duration: 3 Hours

Competency Areas:

ABAP Objects (11-20%):

Classes and objects
Events
Exception handling
Global classes and interfaces
Inheritance
Interfaces
Polymorphism (casting)
Shared objects

ABAP Dictionary (11-20%):

Consistency by means of input check (foreign key dependency)
Database tables
Dependency for ABAP Dictionary objects
Performance for table accesses
Search helps
Views

ABAP Workbench Basics (11-20%):

Data retrieval (authorization check)
Data types and data objects (declaration)
Function groups and function modules
Internal tables
Program calls and memory management
Subroutines

Advanced ABAP (11-20%):

ABAP runtime
Data types and data objects (usage)
Dynamic programming
Open SQL (high-performance programming)

Database Changes (Less Than 10%):

Change document creation
Complex LUW processing
Database updates with open SQL
LUWs and client/server architecture
Number assignment
Organize database changes
SAP locking concept

Dialog Programming (11-20%):

Context menu
Lists in dialog programming
Program interface (GUI title, GUI status)
Screen (basics)
Screen elements for input/output
Screen elements for output (text fields, status icons, and group
Subscreen and tabstrip control
Table control

Enhancements and Modifications (Less Than 10%):

Business Add-Ins
Business Transaction Events
Changes to the standard SAP system
Enhancements to ABAP Dictionary elements
Enhancements via customer exits
Modifications
Personalization

List Creation Techniques (11-20%):

Data output in lists
Interactive lists
List creation with the ALV grid control:
Logical database
Selection screen

SAP Technologies (Less Than 10%):

SAP systems (mySAP Business Suite and SAP NetWeaver)
Technical structure of an SAP Web Application Server

TAW12 - ABAP Workbench Concepts

2009-05-23T11:28:00.003+08:00

TAW12 Objectives:

Describe the concepts behind the ABAP programming language
Use the ABAP programming languages and the tools of ABAP Workbench to develop your own business applications or make adjustments to the standard SAP software
Put your knowledge as a junior to practical use

TAW12_1 Units:

Course Overview
Introduction to Screen Programming
The Program Interface
Output Elements
Input/Output Elements
Subscreens and Tabstrips Controls Elements
Table Control Elements
Context Menus
Lists on Screens

TAW12_2 Units:

Course Overview
Changing the SAP Standard
Personalization
Enhancements to ABAP Dictionary Elements
Enhancements Using Customer Exits
Business Transaction Events
Business Add-Ins
Modifications
Conclusion

TAW10 ABAP Workbench Fundamentals

2009-05-23T08:53:00.008+08:00

TAW10 Objectives:

Describe the data structure of SAP systems
Use the ABAP Workbench tools
Create lists using classic reports
Create and call function groups and function modules
Work with the ABAP Dictionary
Program in a performance-sensitive manner
Describe the concepts behind object-oriented programming
Create lists using ALV Grid Control

TAW10_1 Units:

SAP Solutions
Navigation
The System Kernel
Communication and Integration Technologies
Sources of Information for Developers
ABAP Program Process
Introduction to ABAP Workbench
Basic ABAP Languages Elements
Data Retrieval
Subprograms in ABAP
Introduction to ABAP Events
Classic List Processing
Creating and Calling Function Groups and Function Modules
Program Calls and Data Storage Management

TAW10_2 Units:

ABAP Dictionary
Tables in ABAP Dictionary
Performance When Accessing Tables
Input Checks
Dependencies with ABAP Dictionary Objects
Changing Tables
Views and Maintenance Dialogs
Search Help
ABAP Runtime
ABAP Types and Data Objects
Analysis Tools for Programs
ABAP Open SQL
Dynamic Programming

TAW10_3 Units:

Introduction to Object-Oriented Programming
Object-Oriented Concepts and Programming Techniques
Object-Oriented Repository Objects
ALV Grid Control
Exception Handling and RTTS
Shared Objects
Case Study
ABAP Certification

Day 2 Your First ABAP/4 Program Questions

2009-05-22T20:08:00.004+08:00

Q. Can a program has nested select statements (a select statement inside a select statement)?
Yes, it can but it will be very inefficient in terms of performance. It is advisable to use a database view.

Q. Is there an Autosave feature in the ABAP Editor as in Microsoft Word?
No, there isn't any. Therefore, it is advisable to save periodically.

Q. If a write statement does not contain a slash, will the output be written to the same line as the previous write statement of written to a new line?
The output will be written to a new line.

Day 2 Your First ABAP/4 Program

2009-05-22T08:12:00.003+08:00

ABAP Development Tools:

Program Editor - Create and Modify ABAP Programs
Data Dictionary - Create Tables, Structures and Views
Data Modeler - Document Tables Relationships
Function Library - Create Global ABAP Function Modules
Screen and Menu Painters - Create Programs User Interface
ABAP Debugger
SQL Trace Tool - SQL Statements Tuning
Runtime Analyzer - Optimizing Program's Performance
Computer-Aided Test Tool (CATT) - Regression Test
Repository Search Tool

Program Types:

Reports - Simple program that normally reads data from database and write it out
Dialog Program - Complex but flexible programs

ABAP reports consist of 5 components, namely Source Code, Variants, Attributes, Documentation and Text Elements with only Source Code and Attributes being mandatory

ABAP Programs are interpreted (not compiled) - Souce Code> Runtime Object, which requires an SAP system to interpret it.

Program Naming Convention:

SAP Programs - Starts with a through x
Customer Programs - Starts with y or z

Create a Package:

Access Object Navigator (se80)
Select Package with YABAP21 as the Object Name and Click on the Display button
Select Yes button to the Create Object? warning message
Key in a text for the Short Description field and select the Save(Enter) button
A successful message will be displayed

Create a HelloWorld ABAP Program:

Activate ABAP Editor (se38)
Enter YJN0201 on the Program Input field and click on Create button
Enter HelloWorld on the Title field
Select Executable program as the Type option
Tick the Editor lock to prevent changes by others (other than creator) to the HelloWorld Program
Accept others as default and click on the Save button
Key in YABAP21 as the Package field and click on the Save(Enter) button
Accept the default Workbench Request Number by clicking on the Green Tick button
In the YJN0201 source editor, key in write 'Hello SAP World!'. on the next line
Select the Save button to save the YJN0201 source code
Select Direct Processing (F8) to execute the YJN0201 program
Hello SAP World! will be displayed successfully on the output screen

YJN0201 Source Code:

*&---------------------------------------------------------------------*
*& Report YJN0201
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*
REPORT YJN0201.
write 'Hello SAP World!'.

Data Dictionary (DDIC) is used to create objects such as tables, structures and views. It is invoked via se11 transaction code. When the table definition in the data dictionary is activated, the actual table is created in database such as Oracle or DB2.

Use se16 transaction code (Data Browser) to display the tables content. Settings> Fields Selection is used to determine the visibility of the fields to be displayed

select Statement Syntax:

select * from t1 [into wa] [where f1 op v1 and/or f2 op v2 ...].
[order by f1].
(other ABAP statements)
endselect.
where t1 = tables names; wa = work area name that matches the table structure; f1 is the table fieldname; op is the logical operators; v1 is literal or variable

System Variables (prefix is either sy- or syst- ):

sy-datum - current system date
sy-uzeit - current time
sy-subrc - return value of an ABAP statement
sy-dbcnt - processed database table rows

SYST structure shows all the ABAP System Fields

Chain Operator (colon : ) is used to combine lines of code that begin with the same keyword

For example:

write sy-subrc.
write sy-dbcnt.
becomes write: / sy-subrc, sy-dbcnt.

select single Statement:

Syntax: select * from t1 [into wa] [where f1 op v1 and/or f2 op v2 ...].
Does not begin a loop because it only returns 1 row of record. Hence endselect statement is not required.
All Primary Keys must be specified at the where clause to make it a unique record, else a warning message will be displayed.

Source Code Comments:

* (Asterisk) - Indicates the whole line is a comment
" (double quotes) - Indicates the remainder line is a comment

To Access SAP System

2009-05-21T16:10:00.000+08:00

Windows users need to logon to the nspadm User Account which was created during SAP NetWeaver 7.01 SR1 ABAP Trial Version installation for the SAP System access. Once logged on, we will need to start the SAP Application Server and logon via SAP Logon:

SAP Application Server:

Double-Click on the SAP Management Console icon on the Windows Desktop
Select the SAP Systems node on the left section
Select Action Menu> Start option
Key in the default password set during installation on the WebService Authentication window and press OK button. The SAP Systems node will change from grey (inactive) to green (active)

SAP Logon:

Double-Click on the SAP Logon icon on the Windows Desktop
Select NSP Local node and click on the Log On button
Signon to the system using User ID=BCUSER and Password=minisap
The SAP Easy Access Initial Menu will be displayed

First time access to the applications, programs or transaction codes will be slow. The delays are due to compilations. However, subsequent access will be much faster.

To Install and Setup SAP GUI for Windows

2009-05-21T08:50:00.002+08:00

SAP GUI for Windows needs to be installed and setup in order to access the SAP System:

Access the SAP_GUI_7.10_C3_Trial_2009217_1034.exe file in the SAPNWABAP701SR1_TRIAL> SAPGUI710C3 folder
Upon completion of the SAP GUI for Windows installation, a SAP Logon icon will be created on the windows desktop
Double-Click on the SAP Logon icon
Create a new entry for the NSP system: New Item button> User Specified System and Next button> On the System Connection Parameters window, key in Description=NSP local; Application Server=localhost; System Number=00 and System ID=NSP and click on the Finish button

Day 1 The Development Environment Questions

2009-05-20T15:00:00.006+08:00

Q. Can an existing client be duplicated to another new client?
Yes, it can be done by Basis Consultant by using a client copy utility.

Q. Can a program be used to read data from a client other than the client that the developer is logged on?
Yes, it can be done by using the CLIENT SPECIFIED keywords in an OPEN SQL Statement.
For example: select * from scarr client specified where mandt = "600"

Q. What is OPEN SQL?
OPEN SQL is SAP's equivalent to ANSI SQL.

SAP NetWeaver 7.01 SR1 ABAP Trial Version Uninstallation

2009-05-20T12:34:00.000+08:00

SAP NetWeaver 7.01 SR1 ABAP Trial Version uninstallation can be performed via the following steps:

Logon to the Windows Operating System with the nspadm User Account created during installation
Ensure that the Application Server is inactive
Access the sapinst.exe file in SAPNWABAP701SR1_TRIAL\SAP_NetWeaver701SR1_2008_Installation_Master\IM_WINDOWS_I386\ folder
Select the SAP Netweaver 7.0 SR1 Including Enhancement Package1> Software Life-Cycle Options> Uninstall> Uninstall - System/Standalone Engine/Optional Standalone Unit> path on the left section
Press the Next button to proceed and follow the subsequent instructions
A successful uninstallation message will be displayed
Access the Registry Clean Tool (RegistryClean.cmd) file in SAPNWABAP701SR1_TRIAL>Additional Tools> RegCleanTool folder to remove existing registry entries from old installations
Delete the sapinst_instdir folder in C:>Program Files> folder for a cleaner uninstallation

Day 1 The Development Environment

2009-05-19T14:12:00.006+08:00

SAP Conceptual Areas:

Application Area (Menu> Logistics Accounting Human Resources Information Systems)
Basis Area (Menu> Tools> Administration)
Development Area (Menu> Tools> Development Workbench)

SAP Screen Elements:

Title Bar
Menu Bar
Command Field
Standard Toolbar
Application Toolbar
Interface Menu
Screen Area
Status Bar
Quick Info

Transaction Code (tcode) is a 3 or 4 characters that ties to a transaction (program). Access Menu> System> Status> Transaction Field value to access a screen transaction code.

SAP R/2 - Mainframe environment
SAP R/3 - Client-Server environment
SAP - Service Oriented Architecture (SOA)

Client Server environment:

One -tiered (All in One System)
Two-tiered (Presentation server in one system while Appplication Server and Database Server in one system)
Three-tiered (All 3 servers exist in separate systems)

Dispatcher handles all requests from Presentation Server and assigns to the first available Work Process. A Work Process has 2 special memory areas, User Context and Program Roll Area.

User Context contains user information that has just logged on which includes User's Current Settings, User's Authourisations and Program Name that the User is currently executing. It is freed when the user log off.

Program Roll Area is allocated by a work process when a program is initiated which include program information such as Variables Values, the Dynamic Memory Allocation and the Current Program Pointer.

A dialog step is the processing needed to get from one screen to the next screen.

An ABAP program occupies 1 Work Process for 1 dialog step. When the dialog step begins, the Roll Area and User Context are rolled in to the work process. When the dialog step ends, they are rolled out.

A Work Process consists:

A Task Handler
An ABAP Interpreter
A Screen Interpreter
A Database Interface

Work Process Types:

D (Dialog)
V (Update)
B (Background)
S (Spool)
E (Enqueue)
M (Message)
G (Gateway)

Tables which are Client-Dependent has CLNT type as it's first field.

OPEN SQL Advantages:

Portable
Data Bufferring
Automatic Client Handling

Database Interface in a Work Process converts OPEN SQL to native database SQL.

ABAP/4 in 21 Days

2009-05-19T13:12:00.004+08:00

21 Days:

The Development Environment
Your First ABAP/4 Program
The Data Dictionary, Part 1
The Data Dictionary, Part 2
The Data Dictionary, Part 3
The Data Dictionary, Part 4
Defining Data in ABAP/4, Part 1
Defining Data in ABAP/4, Part 2
Assignments, Conversions and Calculations
Common Control Statements
Internal Tables
Advanced Internal Tables, Part 1
Advanced Internal Tables, Part 2
The Write Statement
Formatting Techniques, Part 1
Formatting Techniques, Part 2
Modularization: Events and Subroutines
ModularizationL Passing Parameters to Subroutines
Modularization: Function Modules, Part 1
Modularization: Function Modules, Part 2
Selection Screen

SAP NetWeaver 7.01 SR1 ABAP Trial Version Installation

2009-05-19T11:52:00.017+08:00

SAP NetWeaver 7.01 SR1 ABAP Trial Version installation can be performed via the following steps:

Download SAP NetWeaver 7.01 SR1 ABAP Trial Version which is more than 3GB
Move the downloaded zip files (SAPNW7.0ABAPTrialSP12.part1.rar and SAPNW7.0ABAPTrialSP12.part2.rar) into a folder and unzip the SAPNW7.0ABAPTrialSP12.part1.rar file. All the files will be extracted into the SAPNWABAP701SR1_TRIAL folder.
Execute the start.htm file in the SAPNWABAP701SR1_TRIAL folder to display the Welcome webpage
Check that the computer system meets the System Requirements specification
Select the Installation/Uninstallation link on the right section
Start the Installer in SAPNWABAP701SR1_TRIAL\SAP_NetWeaver701SR1_2008_Installation_Master\IM_WINDOWS_I386\sapinst.exe path
Select the SAP Netweaver 7.0 SR1 Including Enhancement Package1> SAP Application Server ABAP> MaxDB> Central System> Central System path on the right section
Follow the instructions as requested including system reboot. User the Next button to proceed
Browse for the Java Runtime Environment (JRE) installation directory as requested such as at C drive> Program Files> Java> j2re1.4.2_18 folder (C:\Program Files\Java\jre1.6.0_03). Note that SAP NetWeaver 7.01 SR1 ABAP Trial Version seems to work with JRE 1.4.x version. There was a problem when I was using jre1.6.x as the installation seems to stuck at Import ABAP phase.
Do not set the SAP System Domain Name by unticking the Set FQDN for SAP System checkbox
Key in a default password for all users of this SAP system with a 9 maximum characters
Ignore the Your system does not meet some prerequisites or SAPinst could not evaluate them message by selecting the Cancel button
Untick the Install the SAP Cryptographic Library checkbox which is used for SSL encryption
Confirm on the Summary settings list and click on the Next button to proceed with the installation
A successful installation message will be displayed

The SAP Netweaver - Software Delivery Tool installation is divided into 5 sections, namely Choose Option, Define Parameters, Summary, Execute and Complete. It took more than 6 hours for the SAP NetWeaver 7.01 SR1 ABAP Trial Version installation to be completed.