BASIS-05 常用TCODE及TABLE

1.權限table usr02/usr04/ust04/usrbf2

2.BASIS的tcode 非常多, 但主要都在如下的path中
CCMS是Computing Center Management System的簡稱, 很多DB的管理工具都在這下面

Transaction	Program	Function/Remark
Basis administrator
AL08	User list
BD54	Logical systems
RZ04	Maintenance of operation modes
RZ10	Edit profile	改完后要重開
Rz11	Maintenance of profile parameters	改完后不用重開
Rz20	Ccms
saint	Add-on instalation tool
Scc3	Log analysis
Scc4	Display/change "client" view
Scc5	Delete client
Scc7	Post-process client import
Scc8	Client export
Scc9	Client copy
Sccl	Client copy(LOCAL)
Sgen	Sap load generator
Sm04	User list
Sm12	Lock entries
Sm13	Update requests
Sm14	Update administrator
Sm21	Syslog
Sm51	Sap server list
Sm36	Define job
Sm37	Single job selection
Sm49	External operating system command
Sm50	Porcess overview
Sm59	RFC connections
Sm66	所有主機的online porcess
Smicm	ICM monitor
Smlg	Logon group maintenance
Smlt	Language management
Smgw	Gateway monitor
Smms	Message server monitor
Snote	上note
Spam	Support package manager
St22	Abap runtime error
Sp02	List of spool requests
usmm	System measurement	計算SAP license 數
Sfw5	switch on business functions	開起business function
performance
AL12	Buffer monitor
Sm56	Number range buffer
St01	System trace
St02	Sap memory monitor
St03n/st03	System load monitor
St05	Performance analysis
St07	Application monitor
St10	Table access statistics
Db administration and performance
dbacockpit	System configuration manitenane
Db01	Oracle lock monitor
Db02	Db performance
Db03	Patrmeter changes of the db
Db12	Backup logs
Db13	Dba planning calendar
Db14	Dba log display
Db16	Db checks
Db17	Db check conditions
Db20	Table statistics
Db21	Configuration of statistics creation
Db24	Logs of administrative db operations
Db26	Db parameters
Dbco	Db connections
St04	Db performance monitor
Operation system
Al11	Sap directories
Os01	Lan check via ping
Os02	Operation system configuration
Os04
Os05
Os06/st06	Os monitor
Os07	Os monitor(remote)
Sap change and development and trans port
Se01	Transport organizer
Se03	Transport organizer tools
Se06	Processing after installation
Se11	Abap dictionary
Se13	Dictionary technical seetings
Se14	Dictionary db utility
Se93	Transaction maintenance
Stms	Transport management system
ABAP PROGRAM DEVELOPMENT
SE38	abap editor	BTCTRNS1(停job) BTCTRNS2(放job)
SE30	BY 程式看效能
SE37	FUNCATION BUILDER
SE80	abap workbench
BI
Rsa1	Data warehousing workbench
Rsrv	Bi object analysis
Listschema	Schema viewr

BASIS-01 概述

1.SAP NetWeaver AS 可看成一個平台，可以掛相關的應用套件於其上，如SAP ECC6.0/SAP PORTAL/SAP CRM....；且底層可以Support JAVA/ABAP

2.Process type
--UPD/UPD2update(tx:sm13)
--ENQlock(tx:sm12)
--BGDbackground(tx:sm37)
--DIAdialog(tx:sm50)
--SPOspool(tx:sp01)

3.AS ABAP Process
--User 使用Sap GUI時先連到msg server然后再到dispatcher 再由dispatcher分配給dailog

4.SAP 起動順序
--DB >> CS(central instance) >> other instance(安裝時可選擇將DB或CS裝在不同主主機上)
--讀PROFILE順序為 Default >> Startup >> Instance

5.SAP Profile
--路徑(linux) /sapmnt/<SID>/profile
--D(Dailog)/B(Background)/V(update)/M(mesg)/E(lock)/G(gateway)/S(spool)

6.SAP Kernel
--ECC 6.0只support Unicode
--路徑(linux) /usr/sap/<SID>/SYS/exe/uc/
--系統被下達startsap指令時會將kernel從/sapmnt/<SID>/exe/uc/ 複制一份到/usr/sap/<SID>/SYS/exe/uc/ 或是/usr/sap/<SID>/SYS/exe/ruc/uc/下

7.CLIENT
--CLIENT有自己的user master data/application data(主檔及交易資料)/customizing data/但也有部份資料是跨client的如IMG/程式..
--將DEV/QAS/PRD裝在同一台並用不同的client no區分開來稱為1-system landscape
--將DEV/QAS裝在同一台並用不同的client no區分開來,而PRD自己一台主機稱為2-system landscape
--將DEV/QAS/PRD各裝在不同台主機稱為3-system landscape
--若將DEV/QAS裝在同一台且用二個不同的client no等於裝二次sap軟體,即有二組的os帳號如devadm/oradev及qasadm/oraqas裝了二套的sap軟體各為DEV及QAS
7.1 SAP裝好后預設有3個client 000/001/006
--000 通常被當做一個reference client; The client receives new Customizing through upgrades, legal change packagers, support packages, and language imports.
--001 通常被當做一個template client; SAP安裝完后001是000的COPY版
--066 EarlyWatch client;SAP用來收集系統效能的client.
7.2 Client Role
--若是要變更IMG設定的client,請選customizing
--若是要測試變更相關設定后的資料情形,請選test
--若是要做教育訓練,請選training
--正式區就選prd

8.系統預設帳號
--sap*==>sap所有的功能(所有的client 都有此帳號)
--ddic==>data dictionary control(所有的client 都有此帳號,但066除外) 
--profile中,若將login/no_automatic_user_sapstar設為0表示允許sap*登入
--裝機時會去指定sap*及ddic的密碼 但這個密碼只會for 000/001/066 生效
--若新建的client則會用ddic/sap*的預設密碼(sap*密碼預設pass) ides==>sap*/DIIC 19920706 /06071992
--若sap*的密碼忘了可進db砍sap*的資料讓其重建密碼,但ddic不行
SQL>delete from SAPSR3.usr02 where bname = 'SAP*' and mandt = '000'; (mandt=000指的是Client部份) commit;
SQL>exit;

9.SAP LOG
--tx:al11會顥示系統所有的SAP Directories的路徑
--SAPLOC refers to /usr/sap
--SAPMNT refers to /sapmnt/SID
--log路徑/usr/sap/DEV/DVEBMGS00/work;檔案命名為dev_功能(w表示workprocess/ms表示mesg server/disp表示dispatcher);如dev_ms
--sap起動的log會放在此目錄下,故可在此查到相關起動的問題;查的順序為dev_ms>>dev_disp>>dev_w0(同開機起動原理)

10.Change Request(CR)
--在se01/se09/se10下, 會看到SAP將cr分為workbench及customizing, Workbench代表跨client, customizing代表沒有跨client

BASIS-04 User Authorization

1.權限建立基本觀念

2.TX:SU01 使用者建立與權限對應觀念

3.權限建立STEP --先建立Role,即建立一個Authorization profile --將tcode/authorization object..等等指派給Role --修正Organization/Activity等參數 --將Role及帳號做一指派 (於pfcg做完設定后請記得要按 user comparison(使用者比較))

BASIS-03 TMS & OSS

1.Change and Transport System(CTS)
--Workbench organizer(TX:SE09))
--Customeizing organizer(TX:SE10))
--Transport Organizer(TX:SE01))
--Transport Management System(TX:STMS))
--其底層是用os的tp及r3trans去執行其log會寫到/usr/sap/trans/log,其檔名為xxxx.)
--一個Transport Domain 存在一個Domain controler,其設定檔在/usr/sap/trans/bin/DOMAIN.CFG ), transport domain 可以含多個或一個transport group; 同一domain 下的group可以互相傳cr, 但不同domain下的group要傳cr就需建domain link.
--修正或是設定STMS一定要在Client 000下做;即設定domain controller需login 000去操作/建立CPIC類的user TMSADM(系統自建))
--建立route后系統會自動建立TMSADM並用此user 自動建立rfc(sm59),如TMSADM@.DOMAIN_DEV )
--transport layer 建立后在新建develope class會指定transport layer )
--TX:SCC4可以去設定任何改變是否要包cr)
--同一instance下的cr要傳不同client要用scc1;若是不同instance下的client要用stms

1.1/usr/sap/trans 下的檔案結構
--data下的檔案命名R+CR#+<.SID>
--cofile下的檔案命名K+CR#+<.SID>
1.2在同一個Landscape下(即cr要互相傳輸的系統), /usr/sap/trans 這個路徑所有的主機都能有讀寫權限, 建議是將此path放到storeage上

bin	This directory contains the configuration files the tp(tp_<domainname>.PFL) and for trnasport domain(domain.cfg)
buffer	This directoy contains an import buffer for each connected system. This buffer lists all request that are to be imported or are pending import, including all import steps.
Cofiles	All control files for transport requests are stored here. These files list the transport type, object class, import steps, return values, and the import status.
Data	This directory contains all data files for transport requests. The format of the data files written by R3trans is also known as the R3trans format. It is platform and release-independent and can therefore be exchanged between SAP system with different DB and operating systems.
Log	This directory can be searched for log files for transports, trace files, and statistics.
Sapnames	All information related to transport activity for eatch user in an SAP system using the CTS is stored here.(即依帳號去記錄各cr的log)
tmp	Temporary log files and semaphores are stored in this directory
olddata	data files from the data subdirectory are moved here once they have exceeded a specificed storeage period.

1.3 cr在release后(se01/se09/se10),會把資料從DB捉出變成file 寫到transport directory下(即會產生data及control file 各寫到data/cofile/buffer 目錄)

1.4 若要刪除過舊的cr可用prd<SID>登入os后,執行如下指令
tp testold all pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL(此指令是先測試)
tp clearold all pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL(此指令才是真正執行)

2.OSS
--note==>用snote
--support pkg==>用spam 但addon plugin需用saint
--EHP用==>sfw5(可以deactive)
--將system landscape的資料給slm==>用sdccn

BASIS-02 Process flow

 

1.A GUI sends a request to the SAP system

2.If necessary, the Dispatcher places the request in the Dispatcher Queue.

3.The Dispatcher assigns the request to a dialog work process and transfers the data.

4.The Dynpro processor rolls in the respective user context.

5.The Dynpro processor transfer the extracted data and the respective ABAP program to the ABAP processor

6.Assumeing that the ABAP program is already contained in the ABAP buffer, the ABAP interpreter reads the ABAP program from the ABAP buffer and executes it.

7.When processing the ABAP program, data is queried from the database. For this purpose, a request is sent to the database interface.

8.The database interface detects that the data is partly contained in the table buffer. From there, the data is loaded and returned to the ABAP interpreter.

9.Data that is not contained in the table buffer is requested form the DBMS via the database interface. For this purpose, the query is translated from Open SQL into Native SQL. After being properly formatted, the results from the DBMS are forwarded to the ABAP interpreter via the database interface.

10.The ABAP program also contains write operations, which are transferred to the database interface.

11.The database interface checks whether the data to be written is in the table buffer, and invalidates it respectively.

12.The database interface transfers the write operation translated into Native SQL to the DBMS which executes the corresponding operations.

13.The ABAP processor transfers results to displayed to the Dynpro processor.

14.The Dynpro processor rolls out the user context.

15.The Dynpro processor prepaers the next screen and sends it to the GUI.

	ITS:Internet Transaction Server
	TX: SM04==>可看到user logon SM50==>WORK PROCESS LIST SM37==>BACKGROUND PROCESS SM13==>UPDATE PORCESS SM12==>ENQUEUE PROCESS SP01==>SPOOL PROCESS