18+8

Front 1

Workitem을 archiving할때 Target file의 이름으로 맞는것은(싱글)

Back 1

-->/usr/sap/<SID>/SYS/global/workITEM_20030721_110000.ARCHIVE

Front 2

* MCOD(Multi Component)와 UNICODE중 맞는것은(멀티)

Back 2

--> Migration of no MCOD systems to MCOD systems are possible
--> UNICODE is supported since SAP WAS 610

Front 3

* NON UNICODE를 UNICODE 시스템으로 등록하는 방법

Back 3

--> export the entire Database, Install a new unicode based database, import the data into the new database

Front 4

* SAP GUI 종류(멀티)

Back 4

--> Windows, Java, HTML

Hint 4

그냥 외우시면 될것 같네요

Front 5

* 초기 SAP system hardware sizing 할때 도움을 줄 수 있는 방법(멀티)

Back 5

--> service.sap.com/sizing
--> your hardware supplier can help you in finding an install sizing
--> you find sum minimum hardware requirement with in the installation guide

Hint 5

None

Front 6

* Which of the following statement are correct in System Installation process?(멀티)

Back 6

--> The installation can be continued from the failed step without repeating previous steps
--> The SAPINST xml files can be easily modified ~~~~~~~~
--> The SAPINST does not abort the installation in earlier situation

Hint 6

2주차 19페이지 advantage, 108페이지에서 sapinst xml 파일들 봐주세요.

Front 7

* Which of the following statements are correct in SAPINST?(멀티)

Back 7

--> SAPINST always used the next freeport for communication between SAPINST GUI ans SAPINST Server
--> SAPINST requires JAVA runtime enviroument
--> SAPINST can be used to perform a remote installation

Hint 7

None

Front 8

* Buffering 된 Data를 접근하고자 할때 지켜야 할 룰은?

Back 8

--> You need to use select single statement to access partial buffered
--> Native SQL은 버퍼링을 안하므로
--> The statements select by-passing buffer does not make uses of the SAP buffer

Hint 8

-partial buffered는 'Single recored bufferd'를 의미합니다

Front 9

* Please, Identify the collect statement dealing with some answer time component 설명중 맞는 것은?

Back 9

--> High RFC + CPIC time indicate that either the network connection to the remote component is WEAK or ~~~~~
--> High GUI time may indicate either a slow network connection to the frontend or ~~~~
--> Roll wait time is counted as a sub-component of RFC + CPIC time that is majored during synchronousRFC(sRFC) communication

Hint 9

H:- RFC + CPIC time = Rollout Time + Rollwait Time + Rollin Time으로 RFC 통신할때 request~return까지의 총시간입니다.
- GUI Time = Network Time + Rollout Time + Rollwait Time + Rollin Time으로 SAP GUI에서 SAP System으로 request~return까지의 총시간입니다.
- 모두 synchronousRFC(sRFC)에만 있읍니다.
- 높은 GUI time은 네트워크나 frontend의 문제일 수 있으며, low speed 옵션이나, classic mode, SAP Menu 축소 등의 방법이 있습니다.

Front 10

* expensiveSQL 문장을 어떻게 인식(recorgnize) 하는가?

Back 10

--> High database request time caused by many buffer request on the database
--> High database request time as part of the response time

Hint 10

None

Front 11

* SM50에서 얻을수 있는 정보?(멀티)

Back 11

--> The database table accessed by running program
--> The current status of the workprocess

Hint 11

None

Front 12

* CUA 구현후 Central하게 유지 관리할 수 있는 정보

Back 12

--> Initial password
--> Complete definitions of user role
--> Authorization profile can be replicated to other systems
--> The Lock status of a users

Hint 12

1주차 교체 443페이지
CUA에서 관리 할수 있는 DATA
- user master records : address, logon data, user defaults, and user parameters
- Users are assigned the associated single and composite roles and profiles for all child systems. Using CUA has the advantage that you no loger need to log on to each inidividual client to maintain these assignments locally.
- Initial Password : When users are newly created, an initail password is trasferred to the child systems. This can be changed in the usual way.
- Lock status : In addition to the familiar lock reasons (faied logon attemps or locked by an administrator) there is a noew general lock. This takes effect in all child systems in which the affected user is permitted and can be removed either centrally or in an individual child system

Front 13

* SAP system과 Directory Server 사이의 Sync를 위해 어떤 스텝이 수행되어져야 하나?

Back 13

--> Creation of a system user that is used by the SAP system to log on to the directory server
--> Creation of RFC destination type "T" to the LDAP connector
--> Maintenance of host name, port number and product name of the directory server inside SAP system

Hint 13

None

Front 14

* SMTP를 이용하여 mailing 수행시 해당 클라이언트에 반드시 있어야 되는 Setting은 ?

Back 14

--> Schedule a periodic send process for address type "INT"
--> Maintenance of parameter fro SMTP
--> Maintenance and activation of the SMTP host in teansaction SICF(아리까리 SMTP host인가 SMTP service인가)

Hint 14

None

Front 15

* SAP 시스템과 Directory 서버 시스템과의 UserData는 어디서 동기화가 이루어져야 하나?

Back 15

--> The synchronization should be started from the SAP system independent on the direction in which the data are synchronized

Hint 15

None

Front 16

* SAPphone에 대한 설명

Back 16

--> By customizing the SAP system so that a direct RFC destination from SAPsystem to SAPphone~~~
--> By using the SAPphone server that is delivered by SAP and a TAPI connection to the telephony server

Hint 16

None

Front 17

* Which of following eCATT에 대한 설명중 맞는것은?

Back 17

--> Test data aer stored in test data container
--> System data container from a connection between command in the test scripts and RFC
--> A test scripts can use different system data container at the same time

Hint 17

eCATT(extended Computer Aided Test Tool) to create and execute functional tests for software. The primary aim is the automatic testing of SAP business processes. Each test generates a detailed log that documents the test process and results.

eCATT enables automatic testing in SAP GUI for Windows and SAP GUI for Java. In order to offer a complete test solution that covers other GUIs, eCATT has interfaces to third party tools.

Front 18

* Processing time 과 관련되어서 SAP가 권장하는 것은?(멀티)

Back 18

--> Processing time should not be higher than two times the CPU times
--> Processing time이 Response time 40(45%)%(아리까리)

Hint 18

None

Front 19

* ACID?

Back 19

--> Atomicity, Consistency, Isolation, Durability

Hint 19

- ACID: Transaction의 속성

Front 20

Variant

Back 20

Backgroung Job 등을 수행하는 ABAP program의 경우 Dialog program과 달리 조건값을
입력할 수없기 때문에 조건 값을 입력할 수 있도록 SAP는 Variant를 사용합니당.

Hint 20

따로 설명이 필요없을 듯... 외우세요.

Front 21

SAP Technology Component

Back 21

SAP GUI, WAS, ITS, SAP DB(=ADABAS), DCOM Connector, SAP Library Cache, Business
Connector 등

Hint 21

None

Front 22

SAP Connector

Back 22

SAP와 External System(i.g. FAX server, mail server를 지원하는 Web Server etc)등과의
Communication시 사용되는 Interface.
Notes] WAS Version에 와서 SMTP, HTTP가 Plug-in 되어 있어 Web을 지원
SAP Connector는 기본적으로 RFC를 사용하며, 각 Instance별 Gateway Service를
기반으로 합니당.

Hint 22

None

Front 23

Memory Allocation

Back 23

********** ---> 1) ztta/roll_first(default : 1) : Work Process의 일부만 사용하도록 지정
********** 2) ztta/roll_extension : extended memory에서 User별 Qarter지정
* * (한 User당 memory 할당량 지정)
* * 3) ztta/roll_area : 나머지 memory부분을 모두 사용
**********
-Work Pro- 4) ztta/heap_area_dia : heap memory 사용
Notes] . 위의 사항은 Dialog Process에 해당되는 memory allocation 이며, Non_Dialog는 다름.
. 1)-4)까지의 allocation의 범위를 넘어서면 Dump 떨어짐.

Hint 23

H:
[Dialog 기준]
1) ztta/roll_first(default : 1) : Work Process의 일부만 사용하도록 지정
2) ztta/roll_extension : extended memory에서 User별 Qarter지정(한 User당 memory 할당량 지정)
or EM Exhausted(em/initial_size_MB)
3) ztta/roll_area : 나머지 memory부분을 모두 사용
4) ztta/heap_area_dia : heap memory 사용
or EM Exhausted(em/initial_size_MB)

Front 24

Solution Manager

Back 24

: 모든 Application solution들을 Central로 관리를 하도록 지원하는 Tool.
해당 시스템들에 대한 early watch service 및 Monitoring service 등을 지원하며,
Customer에 맞게끔 해당 company의 환경에 맞춰 IT Report등을 출력할 수 있도록 지원합니당.

Hint 24

None

Front 25

Instance 기동순서

Back 25

. NT : MMC를 이용해서 Start -> sapstartsrv 구동 -> start profile write
. UNIX : sapstart

-> start profile내의 정의된 순서대로 DB -> MS(Message Server) -> dispatcher
(NT:disp+work.exe) -> dispatcher가 work process의 수를 정의해둔 Instance profile을
읽어서 Work Process들을 구동시키고 ICM service도 생성, 구동시킨다.
Notes] ICM은 Work process가 아닙니당.

Hint 25

None

Front 26

RFC Destination

Back 26

SM59에서 확인할 수 있는 것을 교재를 보고 참조하기 바래용.

Hint 26

교재 1주차 457쪽 실습 참고

Front 27

Interface Monitoring

Back 27

: STAD에 들어가보면 아래에 Fronted end라는 GUI time을 보여주는 란이 있음.
Q] GUI Time(R/3 App로부터 SAP GUI로 Request에 대해 Confirm하는데 걸리는 시간.
Synchronous RFC에서는 Roll wait time과 같은 말)이 길어지는 이유는?
-> 주로, Network이 느리거나, GUI가 실행중인 Client의 사양이 주요 원인이 됩니당.
이러한 원인을 해결하기 위해 Client에서 처리할 수 있는 방법으로는,
. SAP assistant configuration에서 Graphic mode를 Classic mode로 변환하여
memory 부하를 줄이거나, SAP GUI설정에서 property->Advanced 에서
low speed connection을 Check.
Notes] . Synchronous RFC, Asynchronous RFC 참조하세용..

Hint 27

None