ERP SAP Installation Concepts for ABAP

ERP SAP Installation Concepts for ABAP are basics that we are going to deal with basic options of installations.As a result of open know-how of R/3 and thus the variety of supported hardware platforms, working techniques,and databases, it is past the scope of this chapter to cowl all installation variants. For a single SAP system or group of related methods, customers don't often set up completely different operating systems and databases, except for performing benchmarks and comparisons. Nevertheless, a mixture and match of various hardware methods and even working methods are supported (for instance, UNIX techniques as database servers and Windows NT as utility servers, OS/390 as standalone database servers, and AIX as utility servers). Official SAP set up guides contain detailed directions on how one can proceed in these environments.

Buyer choices about hardware platforms are quite variable, however UNIX and Windows NT are the two main working programs selected. ORACLE is amongst the preferred databases, with Informix, Microsoft SQL−Server, and ADABAS D as different choices.Installing the SAP R/3 software program successfully, offering all requirements are met, is a course of which will last from one to two days, relying on the options and processing energy of the hardware chosen. This estimated time does not embody post installation steps or basis customization.An excellent level of expertise with working techniques (UNIX or Windows NT) and management of database techniques will ease your means into quick and successful installations. Also, be sure you know the hotline numbers of your nearest SAP subsidiary and your hardware vendor.

Parts in a SAP R/3 Set up

When an organization decides to implement a SAP R/3 system to fulfill its business data wants, it must be aware that it's most likely more difficult to customise the useful features of the enterprise, nevertheless, all the technical elements concerned have to be seriously thought-about to beat the availability issue. SAP defines availability because the fraction of time the system can be used to perform the capabilities for which it was designed.It does not outline it as an remoted hardware or software component, but as a property of the whole information system.

In a SAP R/3 installation, you could encounter the following hardware elements: ¨ One or a quantity of server computers with sufficient predominant reminiscence and arduous disk space ¨ An acceptable network infrastructure ¨ Many presentation servers, generally personal computer systems, with network interface playing cards ¨ LAN servers, which are wanted ninety nine % of the time ¨ One or a number of printers The next software elements may also be present:

¨ Server computer systems operating system and base software kits.
Graphical operating surroundings for the non-public computers and a supported network operating system.
¨
¨ SAP R/3 software kits.
A relational database administration system as the SAP information container. This normally comes bundled with the SAP kit. ¨
All previous plus other extra requirements you might need are described within the SAP brochure, "Test list Installation requirements," which comes bundled in the installation kit.The third and most necessary element, which is rare and sometimes scarce, is people. Though the system is complicated, managing the SAP R/3 system in not so troublesome if the proper support lines and procedures are in place.

This stuff usually are not a SAP necessities record, but are the set of components that needs to be considered when beginning a SAP technical implementation project. Every factor is vital, and the suitable configuration of every onepeople configuration was often identified as trainingis what makes the technical implementation a Installation Steps.The next installation steps cover the general technique of R/three system installation from the very first section of sizing to the non-compulsory post installation choices. The next sections clarify the steps, concepts, and all the details extensively. Note that the order of some of these installation steps may be totally different relying on whether or not the installation is NT based or UNIX based. Differences are indicated within the corresponding paragraphs. A quick description of each step follows:
Measurement your SAP system. Sizing is the process of deciding on the dimensions of the system in phrases of computing energy, bodily area needed, community infrastructure, and so forth. Size is a operate of the number of customers and which R/3 business modules they are going to work on, how massive the database will be, and what the processing energy or availability required to satisfy the system demands is. Notice Sizing isn't really an installation step, but slightly a technical implementation issue. However,since calculating and deciding the system's size is a requirement or fundamental step for any installation, it has been included here.

1. Determine on the set up type. This step solutions the query, how will we implement the SAP R/3 shopper/server method?
2. Test the installation requirements. R/three will only set up if sure minimum necessities are met.Install and configure the hardware, base software program, and network. As soon as we get our computer server, we have to get it up and running. You'll not less than want to put in the server working system, the extra required base software, and configure your network.
3. Get the R/3 installation notes. The R/three installation notes at all times embody final−minute information important to profitable installations. If you do not have entry or a person account for entering SAP−internet, you may request the required notes from your nearest SAP subsidiary by fax.
4. Set up preparations: adapt methods to SAP requirements. UNIX systems would require adapting some kernel parameters, swapping space, and typically putting in extra software. Home windows NT requires the set up of merchandise such as the Microsoft Administration Console (MMC), and adjustments in NT cache, paging space, NT domain, and other parameters.
5. Design the layout of file methods and set them up. Relying upon your system sizing and available sources, you have to design one of the perfect ways to implement the required file systems.
6. Install the R3SETUP tool. R3SETUP is the R/3 installation program that have to be first put in with the use of a SAP−provided script file.The order of the following two points differs between UNIX and Windows NT systems. On UNIX programs,install the R/three cases first after which the database system; in Home windows NT, first install the database software program after which the R/3 instances.
7. Set up the SAP R/three central instance. The R/3 central occasion is the primary piece of SAP software program that the installation utility creates and configures. It routinely creates the SAP directory structure and a set of providers (work processes) of all available types: dialog, background, update, spool, enqueue, message server, and gateway server.
8. Set up the database system. That is the method of installing the underlying R/three database program and creating the run−time and directory construction of the database in line with user inputs.
9. Build and cargo the database. As soon as the database engine is installed from the previous step, the set up utility creates the database structure, and lets you insert the SAP default database knowledge into the system. At this point, you may determine to import the data from one other system (buyer system).
10. Installation is kind of full, and you would even begin the R/three system, however the system won't be quite ready. First, you have to apply for your license key or set up a brief license till you get your ultimate one.There are some non-obligatory post installation directions which needs to be taken into consideration. Amongst them,if your customers will not be German− or English−talking people, or when you belong to a world firm with subsidiaries in international locations with different languages, you'll need to import additional language texts into the system.

Now, let's get a more in-depth have a look at each of those steps.

Step 1: Sizing the System

Sizing may have an effect on the overall set up process. But, when you simply want to carry out a simple set up check, you may skip this part so long as you would possibly have a system with minimal hardware requirements. Sizing is a complex and inaccurate procedure that entails a couple of totally different individuals and organizations. A SAP customer usually requires the help of the chosen hardware vendor and of SAP itself. On the same time, these suppliers go on to the shoppers lengthy questionnaires, with information that is fed right into a sizing application to calculate the estimated measurement of the system. The objective of the sizing course of is to define three crucial figures: how much CPU power is needed (type and variety of processors, reminiscence, variety of servers), how large the database might be (disk house essential), and what the minimal beneficial community infrastructure to assist the SAP R/3 site visitors is. The standard of the sizing is just as good as the standard of the data equipped by the customer.

Sizing SAP techniques is based on a unit referred to as the SAP Utility Benchmark Performance Customary (SAPS). one hundred SAPSs are equal to 2000 order line objects processed in an hour (SD module) or 6000 dialog steps with 2000 postings in an hour (FI module).Usually the CPU and memory requirements are calculated contemplating the estimated consumer inhabitants per application module and an approach of transaction volumes at peak times. Each SAP software module can have a different processor energy consumption depending on the depth of the transactions, and due to this fact they are assigned a load factor. Bear in mind that each SAP launch and even the hardware partners could use different factors relying on their technology. Further data similar to requested common CPU and memory utilization and scalability of the platforms further defines the wanted hardware.Database sizing requires more in−depth enterprise information to have the ability to fill out the prolonged questionnaires equipped by SAP. Often customers are unable to produce this knowledge accurately. In these instances, the method normally is to produce a reasonable quantity of disk space based on related configurations and later monitor the system growth and add more disk space when needed. This, nonetheless, might need some drawbacks including file system redesigns or time−consuming database reorganizations.

SAP has and provides its partners with a sizing instrument to assist calculate the amount of disk space needed based mostly on a enterprise questionnaire.This sizing tool also helps to calculate the estimated tablespace sizes and the most important tables it's going to include.This data is especially useful when buyer installations are defined as having a really massive database (VLDB). Within the R/3 atmosphere a VLDB will be considered a database bigger than 30 GB. That is, nevertheless, a subjective strategy that could be assorted as new R/three or database releases appear.The section entitled "Issues for VLDBs" later in this chapter contains some essential notes on preparing an set up for a VLDB.A simple and first approach to sizing can be the QuickSizer instrument offered by SAP by SAPnet (sapnet.sap−ag.de/quicksizer). With the quick sizing service, SAP prospects can make an initial and categorized calculation of CPU, reminiscence, and disk assets, primarily based either on customers by software module or on a transaction load profile. The outcomes when it comes to SAPSs and common disk quantity requirements are immediately available, and customers can determine to cross on this information to the hardware accomplice straight from the QuickSizer form.

This self−service tool can be utilized within the initial mission part to gain an approximate idea for planning the methods infrastructure. Because the mission progresses, and extra usage information is on the market, a double verify must be completed, either by using the Quicksizer device again or by directing the data to the chosen hardware partner.A 3rd and generally underestimated issue for an accurate sizing is the anticipated network traffic. Usually there are two types of community connections which require acceptable bandwidths: from the application servers to the database server (server community) and from the presentation servers (usually PCs) to the applying servers (entry network).The rule of thumb establishes an approximate determine of 1.5 to 2.5 Kbits/sec between presentation servers to software servers. This determine does not consider other community traffic, each R/3 associated (printing, downloading, graphics) and non−R/three associated (mail, web, different consumer/server applications).The load between utility server and database server (when on totally different servers) will depend on the general system load, however a minimal of 10 Mbits/sec ought to be guaranteed. To calculate the network bandwidth, customers should know the number of websites and the number of users per web site and per module. SAP hardware and expertise partners will help on this process. A formula primarily based on benchmark is available for an approximate sizing .

Related Posts

SAP ABAP Syntax for Start of Selection
Related Posts

SAP Financial and Controlling Overview
SAP Controlling Information System

SAP Financial Payment Cards
SAP Financial and Controlling Overview
SAP Financial Profit Center Analysis
SAP Financial Information System
SAP Financial Legacy Data Transfer

Complete Lessons

SAP ABAP All Topics Complete Courses
SAP CRM All Topics Complete Courses
ABAP 51 Days Complete Course
MySAP and ERP
SAP Financial and Controlling Complete Lessons

What is MySAP Technology

SAP security infrastructure for data production
SAP safety infrastructure
SAP Network Level Security
Mysap web application server
SAP web application and business server pages
SAP project introduction in the best ERP
SAP project migration

SAP Financial Cost Management
SAP Financial Dunning
SAP Financial Lock Box
SAP Financial Interest Calculation
SAP Financial Payment Cards

SAP Full Form,Meaning and Introduction to ABAP Syntax for START OF SELECTION

SAP has full form of syntax and programming language named as ABAP and here in this post we are going to see the introduction to sap syntax for the keyword START OF SELECTION in its programming language.

Basic form

START-OF-SELECTION.

Effect

This is an event key word. Before the first logical database table access, it introduces any initial processing to be executed prior to the block specified under the next event key word .

The REPORT statement automatically starts the START-OFSELECTION processing. Any processing between the REPORT statement and the subsequent event key word is executed at START-OF-SELECTION .

Immediately after, the processing block introduced by an explicit START-OF-SELECTION is executed.

STATICS


Variants
1. STATICS f.
2. STATICS f(len).
3. STATICS: BEGIN OF rec,
...
END OF rec.
4. STATICS: BEGIN OF itab OCCURS n,
...
END OF itab.
Effect

The STATICS statement is a variation of the DATA statement. It allows you to define variables in a procedure (i.e. a FORM or FUNCTION ) with local visibility, but static validity. Static validity means that, unlike normal local variables, the life of static variables does not depend on the defining procedure, but on the program at runtime. Static variables are thus not redefined on the stack each time the defining procedure is called, but exist independently of this in the program and keep their value, regardless of calls to the defining procedure.

Like all other data objects , static variables always have a particular data type. Data types and data objects are important components of the ABAP/4 type concept .

Example

DATA RESULT TYPE I.
PERFORM RANDOM CHANGING RESULT.
FORM RANDOM CHANGING P_RESULT TYPE I.
STATICS L_STATE TYPE I.
L_STATE = ( L_STATE * 113 + 34 ) MOD 256.
P_RESULT = L_STATE.
ENDFORM.

STOP


Basic form

STOP.

Effect

Cancels all data selection. No further tables are read.

STOP is followed immediately by the END-OF-SELECTION processing. If you do not want this, you may have to use EXIT instead.

SUBMIT

Basic form

SUBMIT rep.

Additions

1. ... LINE-SIZE col
2. ... LINE-COUNT lin
3. ... TO SAP-SPOOL
4. ... VIA SELECTION-SCREEN
5. ... AND RETURN
6. ... EXPORTING LIST TO MEMORY
7. ... USER user VIA JOB job NUMBER n

Effect

Calls the report rep . Leaves the active program and starts the new report rep .

Addition 1
... LINE-SIZE col

Effect

Prints the report with the line width col .

Addition 2

... LINE-COUNT lin

Effect

Prints the report with lin lines (per page).

Addition 4

... VIA SELECTION-SCREEN

Effect

Displays the selection screen for the user. In this case, the selection screen is redisplayed after return from the report list display - the user's entries are retained.

Addition 6

... EXPORTING LIST TO MEMORY

Effect

Does not display the output list of the called report, but saves it in SAP memory and leaves the called report immediately. Since the calling program can read the list from memory and process it further, you need to use the addition ... AND RETURN . Also, since the called report cannot be requested for printing, the addition ... TO SAP-SPOOL is not allowed here. You can read the saved list from SAP memory with the function module 'LIST_FROM_MEMORY' and then (for example) store it in the database with EXPORT . You can process this list further with the function modules
'WRITE_LIST' , 'DISPLAY_LIST' ... of the function group "SLST" .

Addition 7


... USER user VIA JOB job NUMBER n

Effect

Schedules the specified report in the job specified by the job name job and the job number n . The job runs under the user name user and you can omit the addition USER user . The assignment of the job number occurs via the function module JOB_OPEN (see also the documentation for the function modules JOB_CLOSE and JOB_SUBMIT . This addition can only be used with the addition ...AND RETURN .

When scheduling a report with the SUBMIT ... VIA JOB job NUMBER n statement, you should always use the addition ...TO SAP-SPOOL to pass print and/or archive parameters. Otherwise, default values are used to generate the list and this disturbs operations in a production environment.

Addition 9

... USING SELECTION-SETS OF PROGRAM prog Effect Uses variants of the program prog when executing the program rep .

Related Posts:


SAP definition,full form,over veiw and introduction
SAP Full form of planning and distribution of goods
SAP full form for mrp,sales and materiel planning
What is SAP and Why do we are in need of It
What is SAP Full form and its definition part one
SAP Full form and introduction part two
SAP FULL FORM syntax for keyword SPLIT

SAP Reporting Syntax for SET and Full Form

SAP reporting has a programming language called ABAP and here in this post we are going to explore the keyword SET complete usage in the syntax.

SET BLANK LINES ON.
SET BLANKS LINES OFF.

Effect

These statements allow you to specify whether you want to output blank lines or not. Use SET BLANK LINES ON to output blank lines or SET BLANK LINES OFF to suppress them. The default setting is SET BLANK LINES OFF .

Example

When outputting texts, include blank lines:

DATA: BEGIN OF TEXTTAB OCCURS 100,
LINE(72),
END OF TEXTTAB.
SET BLANK LINES ON.
LOOP AT TEXTTAB.
WRITE / TEXTTAB-LINE.
ENDLOOP.
Suppress blank lines again with the statement:
SET BLANK LINES OFF.

SET COUNTRY f.

Effect

Displays the decimal point and date in all subsequent output ( WRITE ) according to the settings specified in the table T005X for the country ID f .The return code value is set as follows:

SY-SUBRC = 0 The statement was successful.
SY_SUBRC = 4 The country ID was not found in table T005X .

The country must exist in table T005X . Otherwise, the formats used are "." for the decimal point and "MM/DD/YYYY" for the date.The special form SET COUNTRY SPACE (or f contains SPACE ) resets the decimal point and date display formats to the setting contained in the current user's master record. In this case, table T005X is not read and the return code value is always 0. The effect of SET COUNTRY is not restricted to the current program, but applies at once to all programs in the current roll area.

Example

When outputting documents, display the decimal point and date in the format specified for the country of the recipient:

DATA: RECEIVER_COUNTRY LIKE T005X-LAND,
DATE LIKE SY-DATUM,
AMOUNT TYPE P DECIMALS 2.
...
SET COUNTRY RECEIVER_COUNTRY.
IF SY-SUBRC = 4.
WRITE: / RECEIVER COUNTRY, ' is unknown'.
ENDIF.
WRITE: / DATE, AMOUNT.

Then, you can say SET COUNTRY SPACE. to display the decimal point and date according to the
specification for the user again.

SET EXTENDED CHECK OFF.
SET EXTENDED CHECK ON.

Effect

You use these statements tot switch the extended syntax check off or on. If the extended syntax check (Transaction SLIN ) reports errors which you do not consider to be errors, and you want to suppress them in future, you can insert the above statements at the appropriate places in the program. A " SET EXTENDED CHECK OFF. " should be followed as soon as possible by a " SET EXTENDED CHECK ON. ", so that the check is only switched off for a short time.

These statements are not interpreted at runtime. You use them only to mark the source code. During the extended syntax check, you can ignore these statements by using the additional function Include suppressed fields.

SET LANGUAGE lg.

Effect

Initializes all text elements TEXT-nnn and all languagespecific text literals 'abcd.....'(nnn) ( nnn = text number) in the specified language. If the text pool does not exist in the desired language, searches in the system language. If the text pool does not exist in the system language either, searches in the secondary language.

SET PARAMETER ID pid FIELD f.

Effect

Writes the contents of the field f to the global SAP memory under the key pid . If the key already contains a value, it is overwritten.The key pid must consist of three characters. You can find a list of the keys (parameters) used in the SAP system description or in the ABAP/4 Development Workbench. The global SAP memory remains available to the user during the entire terminal session. This means that set values are retained when you leave a program. You should not use the SAP memory for temporary storage of values because other modes use the same global memory. If you need a new key (parameter), you can create this in the ABAP/4 Development Workbench.


DATA: REPID(8) VALUE 'RFSCHU01'.
SET PARAMETER ID 'RID' FIELD REPID.

Sets the program name, e.g. for transfer to another program.

Related Posts:

sap abap list notifications and task programming with screen shots

SAP ABAP Sample Program for Order Cost Element Display

ABAP Programming Report for Stock Requirement List

abap sales order management business process


Billing and payment process in erp sap abap

ABAP Reports Syntax for Select Options

Here in this post we are going to have a look at the abap programming language syntax for a key word select optoins.Basic form for this key word is SELECT-OPTIONS sel FOR f.

Effect

Declares a variable selection option. This statement only makes sense in reports, i.e. in programs defined as type 1 in the attributes. You can execute reports with the SUBMIT statement. The statements SELECTOPTIONS and PARAMETERS determine the technical interface and the user interface. The parameters and selection options you specify are displayed on the selection screen for the user to enter values

sel must be 1 - 8 characters long.

This statement defines an internal table sel with a fixed structure which consists of the fields sel-SIGN , sel-OPTION , sel-LOW and sel-HIGH . · A report can be assigned to a logical database ldb . This means that both the logical database ldb and the report can define selection options and parameters. You define the database-specific selection options in an ABAP/4 include program DBldbSEL . The system then imports this include program into the actual logical database access program SAPDBldb and into the report. As a result, the database-specific selection options relevant to the report are available both to the database program SAPDBldb and to the report. The 'report-specific' selection options are known only in the report Some SELECT-OPTIONS additions are allowed only in DBldbSEL . The addition 'NO DATABASE SELECTION' can only be used in the report.

· Each line of the internal table sel formulates a condition. If you require precise details about how to formulate these conditions, see the section on the IN operator under Logical expressions .

If the user enters a value set on the selection screen, the internal table sel is automatically filled.
You can use normal ABAP/4 statements to read and manipulate the internal table sel .

The values you enter for the database-specific selection options are passed directly to the database for data selection . This also applies to report-specific SELECT-OPTIONS that refer to a field in a logical database table defined for dynamic selections .You must check report-specific selections that refer to other fields with the CHECK statement . This process is therefore not as efficient as the process described above.

· Under "Text elements/selection texts", you should enter a description for each selection criterion sel . This description is displayed on the selection screen. If no such text exists, the name sel of the selection option is displayed instead.

· The LOW and HIGH fields of a selection option are displayed in a length up to 18 bytes long (scrollable up to 45 bytes). If you define a length longer than 45, fields are truncated on the selection screen after the 45th character. This affects the first line of the SELECT-OPTIONS table. You can, however, pass longer selection options to a report if they are specified with the addition NO-DISPLAY and thus do not appear on the selection screen. Without NO-DISPLAY , the fields are then truncated whenever the selection screen is processed in the background .

Field attributes on the selection screen.The input/output fields displayed on the selection screen for entry of upper and lower limits have the same attributes for type, length or conversion exits as the field f specified after FOR . If f is a Dictionary field, the selection screen is regenerated automatically after most changes to its attributes. The attributes 'Check table' and 'Fixed values' are exceptions to this rule. If these are changed, you have to generate the program in the ABAP/4 Editor. This also generates the selection screen.

Addition 1

... DEFAULT g

Effect

Proposes the single value g as the default selection when the report is called.


· For each SELECT-OPTION , you can only specify one DEFAULT .
· You must specify the default value g in its internal format, e.g. " SELECT-OPTIONS DATE FOR SYDATUM DEFAULT '19931224' ", not " ... DEFAULT '24.12.1993' ".
· The default value g should normally be a literal because, at runtime, it is transferred to the selection options table sel so early that no value can be assigned to the field g . System fields are an exception here because the system usually assigns values to them as soon as the report processing starts.

· On the "Multiple Selection" screen, you can also enter ranges for selection options with " NO INTERVALS ".

· By combining this addition with " NO-EXTENSION ", you can restrict the user to entry of a single value for the selection option, but with the possibility of also choosing single value options like 'Greater than' or 'Less than or equal'.

Addition

... NO DATABASE SELECTION

Effect

This addition is allowed only for report-specific SELECTOPTIONS which refer to a field f belonging to a table dbtab of the logical database. Here, the selections entered by the user are not passed directly to the logical database unless the logical database supports dynamic selections for dbtab if dynamic selections for dbtab are not supported, the addition has no effect.
This addition can be useful if you only want the selections entered by the user for this SELECT-OPTION to be effective under certain conditions. However, you should be careful when using it: Since the selections have to be checked with CHECK after the records have been read, this has a
considerable effect on performance.

ABAP Programming Report for Stock Requirement List
programming report on produciton order for abap

Shop floor info system report with screen shots
Programming report on multi level bill of meterial