SAP BASIS Concept

(1)

Basis Concept and Manual for x23 SAP system

Version 0.91

Date 9/18/2013

Author Dohotari Paul

© Continental AG

Click on the bellow titles for going to the desired page:

Basis Concept

(2)

for best viewing recommended resolution is 1920x1080

Basis Concept and Manual for x23 SAP system

Click on the bellow titles for going to the desired page:

(3)

x23 SAP Basis Concepts

Transport

Printers

Connections

Title

Transport Concept Transport import rules Transport Naming Rules

Printers Concept Printers naming

RFC connections

(4)

Authorizations

Risk / Emergency

Folders

Authorization concept Authorization Tools Emergency Concept Risk Map Folders System architecture

(5)

Jobs

Jobs Evidence

(6)

Confidential

Prepared by Dohotari Paul 08/26/2015 Page 6 of 142

Emergency Procedure SAP P23

In case that in P23 we experience one of the following: - big performance issues - corrupted tables

- other issues that makes working impossible for one or more companies;

Notes:

Emergency Plan: is the responsibility of each company to have an emergency plan in case that SAP or WAN line is down and no outside communication is possible - this should already exists in every location.

Concepts

(7)

Confidential

Emergency Procedure SAP P23

Useful Telephone list:

P23 BASIS Team

Andrei Dumitras Europe +40 744 799122 [email protected]

Michael Magurk America +1 603 8410955 [email protected]

Paul Dohotari Europe +40 744 799684 [email protected]

P23 Buku Experts

Freddy Mosquera Team Logistics +49 170 4542208 [email protected]

Sergej Schaefer Team Technical Applications +49 151 14570587 [email protected]

Eric Knobbe Team Financials +49 160 96348463 [email protected]

Reinhard Schulz Team Purchasing Sales +49 170 637 5227 [email protected] Paul Dohotari Team Basis Applications +40 744 799684 [email protected]

Corporate IT - Headquarters

Heiko Woeste Manager SAP Basis +49 151 58406477 [email protected]

Benjamin Stangneth Manager EDI and Data Communications +49 15110847824 [email protected] Frank Sündermann Head of Business Systems ContiTech +49 175 5759581 [email protected] Markus Juhnke Head of IT Management Fluid Technology +49 170 3351863 [email protected]

Dr. Bierbrauer CIO Contitech +49 511 9381396 [email protected]

Regional IT Managers

Andy Choi Asia +82 63 710 3730 [email protected]

Oscar González America [email protected]

Karsten Lippeke West and Central Europe +49 151 42100341 [email protected]

Paul Dohotari Eastern Europe +40 744 799684 [email protected]

Local IT - Location Responsible

Thomas Schmidt 007 - TCH KARBEN +49 160-90811167 [email protected]

Augustin Martinez 024 - ANOFLEX +33 6 1311 3726 [email protected] Karsten Lippeke 041 - CT SCHLAUCH +49 151 42100341 [email protected]

Andrea Singer 115 - KÜHNER +49 172 7487425 [email protected]

Rade Seslija 148 - SERBIA +381 64 6594410 [email protected]

Oscar González 175 - MEXICANA [email protected]

Oscar González 186 - CT NAFTA-MTY [email protected]

Haiyin Fang 194 - CHINA GRAND OCEAN +86 13610708950 [email protected]

Miron Gasparella 222 - KALUGA +7 965 707 1180 [email protected]

Paul Dohotari 249 - ROMANIA +40 744 799684 [email protected]

Michael Magurk 343 - THERMOPOL L.L.C +1 603 8410955 [email protected]

Andy Choi 344 - CT KOREA +82 63 710 3730 [email protected]

Alonso Shi 473 - CHINA RUBBER & PLASTICS TECHNOL +86 512 52352880 [email protected]

Carlos Vazquez 496 - CT NORTH AMERICA INC. +52 8262630013 [email protected] Carlos Vazquez 497 - CT NORTH AMERICA INC. +52 8262630013 [email protected]

Frank Gortler 812 - MGW GMBH +49 175 5759515 [email protected]

Michael Magurk 883 - BEATTIE CORP. +1 603 8410955 [email protected] +52 155 18658665

+52 155 18658665 +52 155 18658665

(8)

Confidential

(9)

Confidential

(10)

Always ask Frank Suendermann for any new connection between the systems

Nr. Crt System/connection

1 SEAL

2 Fax server 3 TIMPE

4 Archive link CT Schlauch 5 ADS Adobe Document Ser

(11)

Description Priority

1

Used for sending faxes from SAP 2

??

go to RFC Connections for details

Dedicated server for printing production orders

It is using the TCP/IP RFC :SEAL-CONNC-FRAVM097015 set up by Thomas Schmidt - SID: P23 - Client: 008 - Benutzer: CSCPIC - Logisches System: TCHP23008 - Gateway-Host: ctcp23ci.tiretech.contiwan.com - GW-Service: sapgw60 - LU: ctcp23ci.tiretech.contiwan.com - TP: sapdp60

(12)

Plants using this Located Responsible from Conti

007 Karben Karben Thomas Schmidt

all Karben Thomas Schmidt

812, 041 Hann Muenden

041 Korbach Lippeke

(13)

Responsble from consultants ? Brinkmann - BASF Vogel Juergen: [email protected] Office: +49 6151 492800-10 Mobile: +49 162 2573443

(14)

Emergency Documentation Open an incident with Priority 1 and then send an email to

inform : Florian Fauth/te1/te/cag, Otto

Tomaschek/te1/te/cag, Axel Tacke/te1/te/cag, Falk Seefeldt/te1/te/cag, Joel Ripamonti/te1/te/cag, Markus Juhnke/te1/te/cag, Thomas09 Schmidt/te1/te/cag,

(15)

Printers concept

Responsibilities

Local IT responsible Basis Team

Creation of printers Assigning naming ranges for locations Maintaining a printer settings Verifing / maintaining the print server Reacting for local printer problems Reacting for global printer problems

* for any new locations, the IT responsible should ask for the printers naming range that should be used

** all printers names should have ONLY CAPITAL LETTERS

Creation/ change/ deletion of a printer 1

2 In the change the below form must be attached In the file

there is an example for printer

Example:

Concept Printers naming convention

Local IT opens a change in HPSM assigning to CI: vg_tech_sap_P23_gh

(16)

(17)

Assigning naming ranges for locations Verifing / maintaining the print server Reacting for global printer problems

(18)

(19)

(20)

(21)

Printer Naming Convention for P23:

Naming Range Naming DigitReserved Range

0* - 9* 4 yes

special A001 - A999 4 yes

ABC1 - ABC4 4 AK* 4 yes AS01 - AS07 4 AZ* 4 yes B000 - B021 4 BMW1 4 CN* 4 yes CR* 4 yes CTH0 4 FF* - FF19 4 FI01 4 FRP1* 8 IE01-IE10 4 IQ52 4 J* 4 Yes K0* 4 yes K46A 4 K500 4 K7-01 5 RK* 4 KWH1 4 LOCL 4

NO* 4 and more Yes

O100-O137 4

OP* 4 and 5 yes

OVS1-OVS2 4 P103-P523 4 PABL 4 PDF1 - PDF2 4 R012 - R498 4 RHE1-RHE4 4 RO* 4 yes RW01-RW26 4 Rekl 4 S001-S013 4 SAP1 4 SB* 4 yes

(22)

SCR1-SCR5 4 SK01-SK02 4 TI04 4 TL* 4 yes US* 4 yes XI10 4 XIHH 4 XIHM 4

(23)

Location Location Code Karben 007 all Karben 007 Anoflex Anoflex Anoflex Karben Karben Changchun 194 Chanshu 473 Hannover ??? Romania ??? Karben 007 Karben 007 Karben 007

BIS OMS Team ?

Koreea Karben 007 Karben 007 Karben 007 Karben 007 Kaluga 222 Karben 007 Local Printing Northeim 041 Oppenweiler 115 Oppenweiler 115 Emergency Printers ??? Hamburg Berlin ??? PDF printers HannMuenden 812? Hannover Romania 249 Karben 007 ?? Karben 007 ? ? Subotica

(24)

Karben 007 ??? Romania 249 Mexico 175 Somersworth 343 Karben 007 Karben 007 Karben 007

(25)

Comment

reserverd range for short naming - see second sheet

must be investigated

must be investigated must be investigated

small letters in name!!!! must be investigated

(26)

must be investigated

only this one, should be changed

must be investigated must be investigated must be investigated

(27)

Authorizations Concept:

double click to open

scroll down for remarks!!!!

Remarks

External users - should be approve by the local IT check once per year their approval

X- alerts IT manager is responsible in front of KPMG for the documentation of the process

steps: 1 It manager is providing the info to the local Key users 2 key users are checking and cleaning

3 Head of the department approve in written the results of the key users 4 It manager performs the changes

5 It manager creates the summary and the financial management signs 6 Once per year IT manager sends the report to the central team.

Remark: also the corporate users should be included in this checks (they should not be out filtered by the key users) !!!!

!!!! In case of missing X-Alerts, then an inventory must be performed once per year with the users and their rights analyzed by the cost center leaders KPMG decides what location will get the X-Alerts, small companies should not get it since there is big administrative effort

Rolls

1 every 2 years should be a check of the activities and organizations elements of all rolls

2 cross checking of modules: by example check all the MM roles if they have transactions starting with F*…. Restrict access to the table views - maximum key users can have access, no normal users

(28)

ZBC_WORKLOAD_MONITOR existis in P52 client 100

with this we check the transactions used by user in one year and how often - good for removing rolls from the users assignment Matthias Gramm-Schwarze Matthias Gramm-Schwarze/ti1/ti/cag,

Authorization checks / helpers

1 Users that left must have the rolls deleted.

(29)

IT manager is responsible in front of KPMG for the documentation of the process

Head of the department approve in written the results of the key users It manager creates the summary and the financial management signs Once per year IT manager sends the report to the central team.

also the corporate users should be included in this checks (they should not be out filtered by the key users) !!!!

In case of missing X-Alerts, then an inventory must be performed once per year with the users and their rights analyzed by the cost center leaders KPMG decides what location will get the X-Alerts, small companies should not get it since there is big administrative effort

every 2 years should be a check of the activities and organizations elements of all rolls

cross checking of modules: by example check all the MM roles if they have transactions starting with F*…. Restrict access to the table views - maximum key users can have access, no normal users

(30)

with this we check the transactions used by user in one year and how often - good for removing rolls from the users assignment Matthias Gramm-Schwarze/ti1/ti/cag,

(31)

Users Tools:

double click to open _{Special SAP Transactions}

ZUSEREXECEL

Z_USER_EXCEL_FILE

Rolls tools:

double click to open _{Special SAP Transactions}

ZWELLROLE ZBCROLES Z_USER_ROLE

Mass user creation

1 Use transaction ZUSEREXCEL and the predefined excel "Template Users Creation"

Rolls Creation Steps:

1 Organizational objects for the new plant have to be filled in the excel "Execute for role generator" on the sheet "Data"

2 Derived Rolls are created with the transation ZWELLROLE and using the object values from the excel "Execute for role generator" from the sheet "Info"

3 Derive and Master Rolls must be generated using transaction PFCG

Allocation of the Rolls to users based on the neccesary transactions

1 Single roll alocation: Excel "Authorization_Roles" is used for finding the correct rolls 2 Mass rolls allocation: tranzaction Z_USER_ROLE is used

Mass user rolls allocation

(32)

1 Use transaction Z_USER_EXCEL_FILE

ZBC_WORKLOAD_MONITOR existis in P52 client 100

with this we check the transactions used by user in one year and how often - good for removing rolls from the users assignment Matthias Gramm-Schwarze Matthias Gramm-Schwarze/ti1/ti/cag,

Authorization

Users that left must have the rolls deleted.

(33)

Special SAP Transactions

Z_USER_EXCEL_FILE

Special SAP Transactions

Use transaction ZUSEREXCEL and the predefined excel "Template Users Creation"

Organizational objects for the new plant have to be filled in the excel "Execute for role generator" on the sheet "Data"

Derived Rolls are created with the transation ZWELLROLE and using the object values from the excel "Execute for role generator" from the sheet "Info"

Derive and Master Rolls must be generated using transaction PFCG

Allocation of the Rolls to users based on the neccesary transactions

(34)

with this we check the transactions used by user in one year and how often - good for removing rolls from the users assignment Matthias Gramm-Schwarze/ti1/ti/cag,

(35)

(36)

(37)

1 Get the below info from the partner: technical interface description data flow chart

business process description

2 With this info you need the approval of Mr. Frank Suendermann

3 After the approval of Mr. Suendermann, initiate the request for connection ( BASF Change - in attention of Mr. Brinkmann)

(38)

(39)

RFC Connections Nr Direction From 1 Incoming ? K12 / CSE 2 Outgoing ADS D23/008 Q23/008 3 Outgoing ADS P23/008 4 Incoming *SNP 5 Incoming D19CL230 D19 6 Incoming D19CLNT220 D19 7 Incoming Q19CL230 Q19 8 Incoming Q19CL220 Q19 9 Incoming CHJCL230 CHJ

Concept

Connection name ( only for outgoing)

(40)

10 Incoming CHJCL220 CHJ 11 Incoming

12 Incoming 13 Incoming

(41)

To Conection Type User used in x23 system

Q23/008 P23/008 3 ALECPIC_CSE

ctcdasci.conti.de : 53300 G

ctcpasci.conti.de : 53500 G

used for migration SNP_TB_RFC

Q23 C_Q23008_Q19

(42)

P23 C_P23008_CHJ D/Q/P23 RFC_TANGRO Q23 RFC_PLM P23 RFC_PLM TMSADM DIA_P23_PSR

(43)

Password User used in external system 6ZHNMJU7 -c0ntisap ADSUSER c0ntisap ADSUSER INIT01 INIT01 INIT01 INIT01 INIT01 INIT01

(44)

INIT01 INIT01 INIT01 PLMrfc1! 8SYSTX19

(45)

Contact person in the external system

Andreas Einfeld

Mitja Bamberger ( former Aytach Alpman) Andreas Einfeld Andreas Einfeld Andreas Einfeld Andreas Einfeld Andreas Einfeld Bruno Hellstern A IT BA CA BA

Continental Automotive Systems Division Ludwig-Erhard Strasse 28 65760 Eschborn Germany Telefon/Phone: +49 69 7603 3126 Telefax: +49 69 7603 3830 E-Mail: [email protected]

(46)

Andreas Einfeld Michaela Uzelac

Morgan, Laurence <[email protected]> Morgan, Laurence <[email protected]> T-systems

(47)

Requested by date

Andreas Kirsch/fr/eu/au/cag@CONTI07 6/13/2013

Mitja Bamberger ( former Aytach Alpman) 9/1/2014 Andreas Einfeld

Andreas Einfeld Andreas Einfeld Andreas Einfeld Andreas Einfeld

(48)

Andreas Einfeld Michaela Uzelac Thomas09 Schimdt Thomas09 Schimdt System

(49)

Description

used for data migration between the systems HR development system Serbia

HR development system Kaluga HR test system Serbia

HR test system Kaluga

HR productive system Serbia

Check if the system is working by running the report FP_TEST_00

http://ctcdasci.conti.de:53300 user r and password from column J and I

Transport concept

Actual Situation

Rules of transport:

1 Transport is created and released by consultants/BUKU 2 BUKU should import first in Q23

3 BUKU should import also in M23

4 BUKU/ Key user should test in Q23/ M23

5 If OK, then transport will be imported into P23 by the BASIS Team, based on the written email from BUKU

Desired Situation

Implementing the tranport gates

Cleaning the transport requests after 1 year

(55)

(56)

Transport Naming Rules

When you create a new Transport Request ( SE10) please follow the below 2 rules:

1 "Short Description" naming convention

In the short description we should be able to have a clear view of the scope of this transport request. In order to achive this, the "Short Description" field must follow the below format!

"ZZZ_XX_Y_Description"

where ZZZ is the company identification, XX is the module identification and Y is the request type identification MHP request created by MHP consultants

CTF request created by Contitech Fluid internal users EXT request created by external consultants

BC Basis CO Controlling DE Desing ED EDI FI Financials IE Industrial engineering MM Material Management PM Plant Maintenance PP Production Planning PU Purchasing QM Quality Concepts ZZZ can be: XX can be:

(57)

SD Sales and Distribution WM Warehouse Management C Customizing Request W Workbech Request

Examples: Translation:

"MHP_PP_C_Update of the production orders" - MHP created a customizing request affecting the PP module: Update of the Production Orders "MHP_FI_W_Invoices" - MHP created a workbench request affecting the FI module: Invoices

"CTF_ED_C_Ale Connection" -Contitech created a customizing request affecting the EDI module: ALE Connection

2 Choosing the Project

There is a project created for each plant that will join this year. Please select each time the correct project!!

(58)

When you create a new Transport Request ( SE10) please follow the below 2 rules:

In the short description we should be able to have a clear view of the scope of this transport request. In order to achive this, the "Short Description" field must follow the below format!

where ZZZ is the company identification, XX is the module identification and Y is the request type identification

(59)

Translation:

- MHP created a customizing request affecting the PP module: Update of the Production Orders - MHP created a workbench request affecting the FI module: Invoices

(60)

(61)

(62)

Concept

Central instance

Server: ctcp23ci_P23_60 OS: HP-UX B.11.31 IP: 10.250.172.211 A1 application instance Server: ctcp23a1_P23_62 OS: Linux x86_64 IP: 10.250.172.212 Database ORACLE 11.2.0.3.0 Host: fh007131 OS: HP-UX B.11.31

(63)

A1 application instance Server: ctcp23a1_P23_62 OS: Linux x86_64 IP: 10.250.172.212 A2 Application instance Server: ctcp23a2_P23_60 OS: Linux X86_63 IP: 10.216.11.196

(64)

ALLE logon group

A2 Application instance

Server: ctcp23a2_P23_60 OS: Linux X86_63 IP: 10.216.11.196

(65)

Nr.Crt Job Name 1 2 3 4 5 6

000_BASIS_DELETE OLD BATCH INPUT

Variant: ALL30OLD

Concept Up

000_BASIS_DELETE OLD BATCH INPUT 000_BASIS_ZBC_LOCK_USER

000_BC_PFCG_ROLECOMPARISON

000_BC_DELETE_ROLES_INACTIVE_USR 000_BC_PROFIL_ROLE_COMP

(66)

000_BASIS_ZBC_LOCK_USER

1 job 000_BASIS_ZBC_LOCK_USER was created to automatically lock all the users that have not loged into the system in the last 90 days create in P23 and M23 2 We used the ZBC_LOCK_USER report, variant 90_DAYS_LOCK

(67)

3 In SM30 table ZBCD_SAVE_USER we added an exception list

000_BC_PFCG_ROLECOMPARISON

1 We create job 000_BC_PFCG_ROLECOMPARISON using the PFCG_TIME_DEPENDENCY report 2 This job rans one a week (on Sunday )and deactivates the expired roles of the user

(68)

000_BC_DELETE_ROLES_INACTIVE_USR

1 Job was created using the report ZBS_ROLE_DEL with the 120DAYS variant

(69)

000_BC_PROFIL_ROLE_COMP

1 Job was created using the program RHAUTUPD_NEW (PFCG mass comparison ), variant 000_ROLE_COMP 2 It rans every Saturday and does a mass comparison of the users from every role

(70)

1 Job was created using the program ZBC_JOB_LIST with the 000_ADD_ALL variant

2

This report has 3 options:

a) DB append this will upload the data into the ZBC_JLIST table

b) DB ZBC_JLIST list,displays all the entries from the ZBC_JLIST

c) DB ZBC_JLIST delete: this will delete all the data from the ZBC_JLIST table. After you execute the this option you will receive the warning:

ACHTUNG Table ZBC_JLIST will be initialized Press Enter to start the deletion process

(71)

Job Description

Clears all Batch Inputs older then 30 days

Locks all the users that have not loged into the system in the last 90 days Deactivates the expired roles of the user

Deletes roles from users that have not loged into the system for more then Does a mass comparison of the user's authorization profiles

(72)

job 000_BASIS_ZBC_LOCK_USER was created to automatically lock all the users that have not loged into the system in the last 90 days create in P23 and M23 We used the ZBC_LOCK_USER report, variant 90_DAYS_LOCK

(73)

In SM30 table ZBCD_SAVE_USER we added an exception list

We create job 000_BC_PFCG_ROLECOMPARISON using the PFCG_TIME_DEPENDENCY report This job rans one a week (on Sunday )and deactivates the expired roles of the user

(74)

Job was created using the report ZBS_ROLE_DEL with the 120DAYS variant

(75)

Job was created using the program RHAUTUPD_NEW (PFCG mass comparison ), variant 000_ROLE_COMP It rans every Saturday and does a mass comparison of the users from every role

(76)

(77)

Frequency Start Time Running Time( seconds) Weekly ( Sunday) 11:00 57 Weekly ( Sunday) 23:30 2 Weekly ( Sunday) 1:00 590 Weekly ( Sunday) 23:00 Weekly ( Saturday) 20:00 Daily 4:00 800

(78)

(79)

(80)

(81)

(82)

(83)

(84)

(85)

(86)

(87)

x23 SAP Basis Tasks

Nr. Crt Frequency systems 1 Daily 2 Daily 3 Daily 4 Daily 5 Daily P23 6 Daily 7 Daily 8 Daily 9 Daily 10 Daily 11 Daily 12 Daily 13 Daily 14 Daily 15 Daily 16 Weekly 17 Quarterly 18 Monthly 19 Quarterly 20 Quarterly 21 Quarterly 22 Quarterly 23 Quarterly

Title

(88)

future once / ongoing

future future

(89)

What Transaction

Check instances status SM51

Check work processes SM50

Check tablespaces status DB02OLD

Check db jobs DB14

Check canceled jobs SM37

Check canceled batch SM35

Memory check ST02

SAPOSCOL indicators ST06

Check system log SM21

Check System Dumps ST22

Check Idocs BD87

Interfaces

Check RFC SMQ1 / SMQ2 / SM58

Check Lock entries SM12

Check Aborted Updates SM13

Check users with initial password

Check users with over 60 days not logged HR send a list with leavers to the IT manager Check users without e-mail address

Check users without phone number Check users without fax number Check users expire date

(90)

Job list

Transport management - quality assurance

Concept for Aborted Update SM13

(91)

How?

SMQ1 / SMQ2 / SM58

SAP Note

Select one week before

see how see how see how see how see how see how see how see how see how see how see how

(92)

(93)

Action

Annouce the responsible users

Check the Idocs (inbound and outbound)

IT manager double check if all the users in the list are locked in SAP Add email adress

Add phone number Add fax number Add expire date

remove it from all the rolls!!!!! Check is ok, but deletinng not!!!!! Ovidiu NOTE: 552289

Analyze the transactions/ users - see if we have repeting transactions or repeating users and start investigate

Lock the unused users and set validity date to past and delete the assigned rolls

(94)

diagrama verifica pe SAP.com - fa analiza cu ce tranzactii au fost/ pivot Optimizing of jobs ( choosing the "good" time for running them

Excel with all the jobs running - search for SE38: -> BTCAUX* Transaction RZ01 !!!!

NOTE 997328 NOTE 1439806

2 - 3 approval steps in Q23 ( developer - key users - basis guy) an the the transport goes to the queue of P23

Define a time after the Anoflex go live when all the transports can be deleted

(95)

Responsible Comments BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team EDI BUKU

All BUKU delete the old updates set up a time line!!!

HR + local IT

This is a INSTANCE DEPENDENT transaction, repeat this operation for every instance of the system

This is a INSTANCE DEPENDENT transaction, repeat this operation for every instance of the system This is a INSTANCE DEPENDENT transaction, repeat this operation for every instance of the system

(96)

(97)

transaction, repeat this operation for every instance of the system

transaction, repeat this operation for every instance of the system transaction, repeat this operation for every instance of the system

(98)

(99)

1 Go to in SM37

2 Select like below and as date choose the last 3 days 3 Execute

4 See the result

(100)

(101)

(102)

(103)

1 Go to in ST22 2 Check the dumps

3 Pay special attention to the short dumps that start with DBIF_RSQL_SQL they are related to the db 4 If the number of dumps is bigger then 70, then press on the today button and investigate

4.1 see if there is a users that is produceing this, then is a user problem - call user

4.2 see if there is the same type of error to different users - then we have a program problme, possible created by a transport - ask BUKU

(104)

Pay special attention to the short dumps that start with DBIF_RSQL_SQL they are related to the db If the number of dumps is bigger then 70, then press on the today button and investigate

see if there is a users that is produceing this, then is a user problem - call user

(105)

1 Go to in SP01

2 On the button "Further Selection criteria.." choos Extended

3 Select like below: leave the current date, choose * on "Created By" and select only "Problem"

(106)

4 Execute

(107)

(108)

(109)

1 Go to in BD87

2 Execute with the default seeting, this will show the info for the current day

3 Analize all what is red, by expanding the lists and send the info to the local EDI key users for solving them

(110)

(111)

(112)

(113)

1 Go to in SM66

2 Check visualy which times are with red and on which server

3 open another window and go to SM51

4 click there on the app server on which there are high times

5 then press the button: 6

BACK

(114)

7 then press the "Sessions" button, click on the empty line and press then "End Sesion" button

8 repeat this until all entries from that user are cleared ( only the ones without transaction values) 9 go back in the window with SM 66 and press refresh

(115)

(116)

then press the "Sessions" button, click on the empty line and press then "End Sesion" button

(117)

verifica zilnic

limiteaza drepturile userilor la tranzactie - only one rolle!

not tell sterge tot ce e mai vechi de …

Basis is asking the user for reason of error

if no reaction an this repeteas, then the rights will be removed Ask the key user - who locke the BATCehes

(118)

1 Go to transaction SM51

2 Check that all instances are up and have a green/active status

(119)

(120)

1 Go to SM50 transaction

2 Check that at least 25% of every type of work processes is free

3 Check visualy which times are with red and running for more than 3600 sec

4 Go to transaction SM04 and check for the session of user under which the dialog wp is running and does not have a value on the transaction column, in the above example WIEGANDS,

5 Double click on the session and select the empty value and press end session

(121)

(122)

Go to transaction SM04 and check for the session of user under which the dialog wp is running and does not have a value on the transaction column, in the above example WIEGANDS,

(123)

(124)

(125)

(126)

1 Go to DB02OLD transaction 2 Select the current sizes tabe

3 check that the tablespaces have at least 5% free space, you can ignore the UNDO tablespace as this is a circular tablespace

4 Create a ticket to T-systems if the tablespaces have a used procentuaje of more than 95%

(127)

check that the tablespaces have at least 5% free space, you can ignore the UNDO tablespace as this is a circular tablespace

(128)

(129)

1 Go to DB14 transaction

2 Double click on the job that have warnings or errors(has a yellow or red backgound) 3 Press the Detail Log buttton

4 All the warnings/errors will be shown with a color backgroung

5 Create a ticket to T-systems for them

(130)

(131)

(132)

(133)

1 Go to transaction ST02

2 Check the SAP Memory fields, none of the values shown here should exceed 50%

3 Check the program swaps, be aware that this is a CUMULATIVE value

4 Check the number of swaps that were made since the previuous day, for this double click on the value of the swaps 5 Press the Goto tab, Performance database, This server history

6 The values cumulative value for each day will appear

(134)

(135)

Check the SAP Memory fields, none of the values shown here should exceed 50%

(136)

(137)

1 Go to ST06 transaction, this will show the usage of the host resources

2 Select a instance,check for the idle time of the CPU and the free memory availble

3 The CPU idle time should not go under 50%

4 If the system has a more than one instance repeat the operation for every instance

(138)

Select a instance,check for the idle time of the CPU and the free memory availble

(139)

1 Go to SM21 transaction

2 This an instance dependent transaction, in order to see the logs from all the system instances, go to System log-> Choose-> All remote system logs 3 Select the time interval

(140)

(141)

Rules for importing transports in P23

like before.

Concepts

1. All transports that contain data dictionary changes will only be imported ones per week, every Thursday from 07:30 CET until 08:00 CET

2. During this perioad all users will be locked and all background jobs will be suspended 3. At 07:20 CET we will proceed to suspend all background jobs that are planned to start between 07:30 CET and 08:00 CET, jobs that are already running will not be affected 4. The users will be warned by a system message that during the import of the transports no user interaction will be possible on P23

4. At 07:30 all users will be locked, and the ones that are logged on P23 will be kicked out the system.

5. After the transports are imported ,all users that were locked previously will be unlocked 6. All Jobs that were suspended previously will be released again

7. TechMahindra will schedule their transports that contain data dictionary changes to start at 07:50 CET only on Thursdays . Basis team will import them one by one before their planned start time to avoid any problems.

7. All transports that are imported in the test systems M/Q23 and the customizing transport that are imported in P23 will not be affected by the rules above. They can be imported

(142)

will only be imported ones per week,

all background jobs will be suspended suspend all background jobs that are planned to start

already running will not be affected import of the transports

, and the ones that are logged on P23 will be kicked

that were locked previously will be unlocked

ata dictionary changes one by one before

customizing transport by the rules above. They can be imported