Scribd
Upload
71 views

Technical Know To

The document discusses technical details related to customizing and configuring SAP R/3 systems, including useful ABAP programs, payroll programs and schemas, function modules, and tables. It provides tips for various administrative tasks like reinitializing the R/3 system, client copying, transporting features between systems, and analyzing transport return codes. The effects of changes may vary depending on the version of the R/3 kernel, database, functional and basis configurations being used. Proper authorizations are required when making changes to avoid breaking security or corrupting data.

Uploaded by

pal singh
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
71 views

Technical Know To

The document discusses technical details related to customizing and configuring SAP R/3 systems, including useful ABAP programs, payroll programs and schemas, function modules, and tables. It provides tips for various administrative tasks like reinitializing the R/3 system, client copying, transporting features between systems, and analyzing transport return codes. The effects of changes may vary depending on the version of the R/3 kernel, database, functional and basis configurations being used. Proper authorizations are required when making changes to avoid breaking security or corrupting data.

Uploaded by

pal singh
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 9

7. Some technical stuff...

The following bits of information have proved useful to me.

If they are useful to you, that's nice.

The effects may vary from site to site based on what version of the R/3 kernel you
may be running, as well as based on the version of whatever database, as well as
based on your site's functional and Basis configurations.

If you're not sure whether doing any of these things may break security requirements,
take you to the wrong transaction, or delete or corrupt data, then you should probably
not use this information, or use an R/3 system...

7.1. R/3 Platforms


 HP-UX
 IBM AIX
 Compaq NT
 Digital Unix
 SNI Reliant Unix
 Sun Solaris
 SNI NT
 HP NT
 Digital NT
 IBM OS/400
 IBM NT
 Bull AIX
 NCR NT
 Sequent Dynix
 IBM S/390
 DG-UX
 DG NT
 NCR Unix
 ZDS
 Intergraph
 Hitachi
 AST
 Dell
 Fujitsu
 NEC NT

7.2. Reinitialize R/3


 Check authorizations for SAP using SU02.
 Delete SAP* user under Oracle:

connect internal
delete from sapr3.utab
where tabname = 'USR02'
and varkey = '000SAP*';
commit;
 Log in as SAP*, password 06071992. (The default password for DDIC is
19920706; the default password for SAPR3 is SAP)
 Use txn SU01 to recreate authorizations in SAP* user record:
o SAP_ALL
o SAP_NEW
o S_USER_ALL
o S_TSKH_ALL

7.3. Useful ABAPS


 RSREGEN

This program regenerates all ABAP programs. It must be run as user SAP*.

 SAPMSOS0
This program can be used to somewhat interactively execute programs at the
operating system level. It appears to have been omitted in version 3 and
above...

 RSQAPIDF

Job Queue API

 RSBDCSUB

BDC API

 RSCLRCMP

This program compares tables between the client you are logged into, and
another client you specify for client independent tables.

 RSCLIIND

Compare client-dependent tables.

 RPUMKG00

Regenerate features

Transport of a "feature" (heaven only knows what a feature actually is) is


indicated by transport of an object of type R3TR and PMKC.

Activation ("regeneration") of features is not handled automatically at the time


of transport; this is likely something that will be added to CTS functionality
some day by SAP AG. Thus the need to run program RPUMKG00. The
appropriate argument to pass in seems usually be to generate all features, with
a Type of generation value of "2."

 RSCCPROT

Client Copy Log Analysis

See when/where client copies have taken place.

7.3.1. Fiddling with Internal Tables


Here's a utility showing how one fiddles with an internal table in a dynamic fashion...
form test.
data:
typ(1) type c,
n type i.
field-symbols: <f>.

do.
assign component sy-index of structure itab to <f>.
if sy-subrc <> 0. exit. endif.
write <f>.
enddo.
endform.

7.4. Payroll Programs


 RPCLST**

Examine cluster **.

 Function Module Z_LGART_RPT.

Pass in the payroll class and info on desired values

Passes back a variety of tables representing breakdowns of spending for the

 ZHPYRPTS - Example template for Retro Net wagetype reporting

Must have FORM Z800_ACCUMULATE_DATA, which collects data from


internal table NETRT into whatever program structure is defined to accumulate
data for later use in reporting. Called from INCLUDE ZHPYI012.

7.5. Schemas
A little "rule language" for representing pay calculation rules as used in programs
RPCALC*. The US Payroll calculation program is RPCALCU0.

The U000 scheme is used to estimate payroll calculations; it is run repeatedly on a


group of employees until no exceptions are found.

7.6. Payroll Run: RPCALC*0


One can characterize the calculations for scheme U000 as doing the following:

 Validate Basic information ( e.g. infotypes 0001 thru 0009)


 Read payroll account for the period last processed
 Read time data
 Build up individual and aggregate gross income
 Filter out deductions
 Deduct previously calculated amounts (what shall be "type P" records) so as to
determine the "net" amount. They must be deducted "twice" rather than once...
 Determine the amount that must be turned into a "bank transfer."

Once the data is correct, use scheme U500 to create an FI export to be used to account
for the payroll activity in the G/L.

There are three "input files" used to calculate payroll:

 Pnnnn ( nnnn is the infotype number)

Personnel master record info

 PCL1 - Primary data - time events


o B1 - Time events/pdC

o G1 - Group incentive wages


o L1 - Individual incentive wages
o PC - Personal Calendar
o TE - Travel expenses/payroll results
o TS - Travel Expenses/master data
o TX - Infotype texts
o ZI - PDC interface for cost accounting/materials management
 PCL2 - Secondary data - derived from Pnnnn and PCL1 for previous months
o B2 - Time accounting results
o CD - Cluster Directory
o PS - Generated schemas
o PT - Texts for Generated schemas
o RX - Payroll results - int'l
o Rn - Payroll results - country specific
o ZL - Personal work schedule
 PCL3
o AP - Applicant actions
o TY - Texts for applicant data infotypes

RPCALC*0 is used to turn these into a new PCL2 record containing current period
payroll data; the Pnnnn data is archived for future reference...

While working, the following internal tables are used:

 IT - Input Table - containing wage types


 OT - Output Table - contains results of processing; gets fed back into IT after
each processing step
 RT - Results Table for the accounted period

After completion, this data is stored in cluster RX of PCL2.

 ORT - Old Results Table - the contents of RT in the previous period's run

7.7. Useful Function Modules


 POPUP_TO_SELECT_MONTH

Nice month selector

 POPUP_UNIT_CONVERSION

Guess?

 POPUP_WITH_WARNING

No useful interaction

 POPUP_TO_DECIDE_WITH_MESSAGE

Guess?

 WS_DOWNLOAD
App server to presentation server

 WS_UPLOAD

Presentation server to app server

 EDITOR_TABLE

Allows interactive editing of the contents of a table.

7.8. Interactive Reporting - useful elements of SY


 SY-UCOMM

User command ID

 SY-LINCT

Num of lines per page

 SY-LINSZ

Num of columns per page

 SY-PAGNO

Current page (list generation time)

 SY-LINNO

Current line (list generation time)

 SY-COLNO

Current column (list generation time)

 SY-CUROW

Cursor Position

 SY-CUCOL

Cursor Position

 SY-CPAGE
Page currently displayed
 SY-STACO

List displayed starting at column


 SY-STARO

List displayed starting at row


 SY-LSIND

List level displayed


 SY-LISTI

List level selected


 SY-LILLI

Number of seleted line


 SY-LISEL

String containing the line selected

7.9. Finding User-Exits


Transaction SMOD can list R/3 user exits; use the second screen to specify a range,
from 11111111 to zzzzzzzz.

Most user exits are function modules containing EXIT_.

7.10. Useful Tables


7.10.1. Transport Tables

 T000 - Contains a list of all clients in the systems


 TRBAT - contains staging information on return codes from various steps in
the import process.

If a transport "goes bad," a system can get snarled up, and it will be necessary
to purge the entries in this table, kill the relevant TP processes, and restart.
 TADIR - contains info on the ownership of objects.

If objects were modified in system HD2, and development has moved to HD1,
then it may be necessary to run the following SQL update in order to move
ownership to HD1...
select count(*) from sapr3.tadir where SRCSYSTEM='HD2';

You might also like