Thursday 15 September 2011

Implement new data class in SAP(Oracle and DB2 UDB)

The table's location in the database is determined by its data class when you create it. If you now reserve a new memory area in the database for a group of tables, you can ensure that the new table is generated in the new memory area when you create it by implementing a new data class.


You must assign the new data class to a table (in the technical settings) to ensure that the data class is active (or usable) for
the table. You must do this in the 'Technical Settings Maintenance', which you can access by calling transaction SE11 (table maintenance).

First create a new memory area, for example, a tablespace, in the database. This tablespace must be made known the R/3 System by entering it in the following tables

Oracle: TSORA
DB2 UDB for UNIX and Windows: TSDB6


You must now define a data class for the memory area maintained
Add the new data class or classes to the table DDART.

This table is independent of the database.

If it is a new data class in the standard SAP System, you can choose any five-character name.

DDART-DDCLASS = 'STD'

If it is a customer-specific data class, select a data class from the
following name range:

USER2, USER3,..., USER9 or Z*, Y*.
DDART-DDCLASS = 'USR',


Describe the new data classes in the corresponding text table
DARTT

After the new data classes and the memory areas have been made known to the R/3 System, the link between these sizes must now be defined. You do this with entries in the following tables:

Oracle: TAORA
TAORA-TABART = <Name of data class>
TAORA-TABSPACE = <Name of table memory area>
TAORA-PCTINC = '0000'
TAORA-OFREELIST = '001'
TAORA-OFREEGROUP = '01'
TAORA-OPCTFREE = '10'
TAORA-OPCTUSED = '40'

IAORA
IAORA-TABART = <Name of data class>
IAORA-TABSPACE = <Name of index memory area>
IAORA-PCTINC = '0000'
IAORA-OFREELIST = '01'
IAORA-OPCTFREE = '10'


DB2 UDB for UNIX and Windows: TADB6 and IADB6
TADB6-TABART = <Name of data class>
TADB6-TABSPACE = <Name of table memory area>
IADB6-TABART = <Name data class>
IADB6-TABSPACE = <Name of index memory area>


Transport the table entries that you added if you also want to use the data class in other systems.

Source : Note number 46272

Wednesday 14 September 2011

Extended Transport Control

Extended transport control has the following functions:

·  As well as specifying an SAP System as the transport target of a consolidation or delivery route, you can also specify a client. This means that you can configure the transport of client-specific objects just as securely as the transport of cross-client objects.
·  You can set the standard transport layer that you use to define the transport target of Customizing requests, among other things, as client-specific.

You can make use of the following extended functions when you configure transport routes in Transport Management.

·  Client-specific standard transport layer
·  Client-specific transport targets
·  Target groups
·  Client-specific consolidation routes
·  Client-specific delivery routes
·  Improved import controls

To activate extended transport control:
  1. Log onto the R/3 System functioning as the transport domain controller.
  2. Call transaction STMS.
  3. Choose Overview ® Systems.
The System Overview appears.
  1. Position the cursor on the R/3 System you want to change.
  2. Choose R/3 System ® Change.
The TMS Configuration screen: System <system name> appears.
  1. Choose the tab Transport tool.
  2. Enter the parameter CTC=1 .
  3. Save and distribute the configuration.
Set this parameter globally in all the systems which are there in the transport group.

Tuesday 13 September 2011

New Monitoring for Long-Running jobs - CCMS_LONGRUNNING_JOB_COLLECT

This is really interesting .. Because when my manager asked me to setup an alert for long running jobs i was just searching in RZ20 for monitors and i found this ..

By giving the monitor name in Service market place i found a wonderful note which clearly explains the Setup and Usage of this monitor ..

CCMS_LONGRUNNING_JOB_COLLECT
This is available in the following support packs and EHPs

SAP_BASIS 620 SAPKB62068
SAP_BASIS 640 SAPKB64026
SAP_BASIS 700 SAPKB70022

The data supplier uses method CCMS_LONGRUNNING_JOB_COLLECT which calls
function module SALK_REPORT_LONGRUNNING_JOBS. The method definition
defines the static parameters:
MAX_RUNTIME_IN_MIN 360
TRACE X
AUTO_COMPLETE_ALERTS
With MAX_RUNTIME_IN_MIN you can set the number of minutes a job is allowed
to run before an alert is generated for it. If AUTO_COMPLETE_ALERTS is
set, then the data supplier automatically completes alerts when the job for
which the alert was generated is completed. Such alerts remain visible in
the Alert History.

The data supplier adds the MTE (Monitoring Tree Element) 'Long-Running
Jobs' to the system-wide batch monitor, visible in RZ20, SAP CCMS Monitor
Templates -> Background Processing.

By default, the data supplier alerts for all jobs that exceed the time
limit. You can modify this behavior by adding entries to the table
ALLONGJOB_CTRL. In this table, you can either 1) restrict monitoring to a
positive list of jobs. Only these jobs will be monitored, if positive
customizing entries are added. Or 2) you can subtract jobs that belong to a
negative list of job names from the default 'monitor-all-jobs' behavior.

Note : source SAP NOTE 1138223

Introduction


History of SAP ..

It will be great to know about SAP first before going into technical things ..

So i have decided to tell you about the history first then i will go into details ...

SAP was started in 1972 by 5 former IBM employees in Mannheim,Germany.

The original name for SAP was German: Systeme, Anwendungen, Produkte, German for "Systems Applications and Products." The original SAP idea was to provide customers with the ability to interact with a common corporate database for a comprehensive range of applications

We can say its a software which will allow business to track customers and business processes. It is well known as Enterprise resource planning (ERP) and data management programs which will be used by  customers to track their business by using different kind of modules like Warehouse Management, Material Management, Sales and Distribution, Finance and Human Resource.

Its being used by all sizes of business .. small, mid-level and large.

What is an SAP System ?

SAP consists of one database and one or more instances

The instace togethe with database forms a runnable SAP system and is called Central Instance.

A system ID must be assigned to the central instance which should not be identical to other systems.

 Elements of a SAP system

  • Database (with Abap and Java Schema)
  • ABAP Central Instance
  • In ABAP - Message Server, Gateway,Internet Communication Manager(ICM)(optional).
  • Java Central Instance - which ontains dispatcher and at least one server
  • Java Services Instance - which contains Message server and enque processes
  • Java Software Deployment Manager(SDM)




Note: Sources from internet and SAP Certification documents ...