Basis Concept and Manual for x23 SAP system
Version Date
Author
0.91 9/18/2013
Dohotari Paul
© Continental AG
Click on the bellow titles for going to the desired page:
Basis Concept
for best viewing recommended resolution is 1920x1080
for x23 SAP system
o the desired page:
Basis Tasks
Title
x23 SAP Basis Concepts Transport
Transport Concept Transport import rules Transport Naming Rules
Printers
Printers Concept Printers naming
Connections RFC connections
New Connections Procedure
Authorizations
Authorization concept
Authorization Tools
Risk / Emergency
Emergency Concept Risk Map
Folders Folders System architecture
Jobs
Jobs Evidence Batch Input Procedure
Confidential
Concepts
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 comp
Then the below procedure will be executed by the P23 BASIS team:
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.
Prepared by Dohotari Paul 08/26/2015
Page 6 of 142
Confidential
Emergency Procedure SAP P23 Useful Telephone list: P23 BASIS Team Andrei Dumitras Michael Magurk Paul Dohotari
Europe America Europe
+40 744 799122 +1 603 8410955 +40 744 799684
[email protected] [email protected] [email protected]
+49 170 4542208 +49 151 14570587 +49 160 96348463 +49 170 637 5227 +40 744 799684
[email protected] [email protected] [email protected] [email protected] [email protected]
+49 +49 +49 +49 +49
151 58406477 15110847824 175 5759581 170 3351863 511 9381396
heiko.woeste@contitech benjamin.stangneth@co frank.suendermann@con
[email protected] gerold.bierbrauer@conti
+82 +52 +49 +40
63 710 3730 155 18658665 151 42100341 744 799684
[email protected] [email protected] [email protected] [email protected]
+49 160-90811167 +33 6 1311 3726 +49 151 42100341 +49 172 7487425 +381 64 6594410 +52 155 18658665 +52 155 18658665 +86 13610708950 +7 965 707 1180 +40 744 799684 +1 603 8410955 +82 63 710 3730 +86 512 52352880 +52 8262630013 +52 8262630013 +49 175 5759515 +1 603 8410955
thomas09.schmidt@fluid augustin.martinez@fluid
[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] miron.gasparella@conti.
[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
P23 Buku Experts Freddy Mosquera Sergej Schaefer Eric Knobbe Reinhard Schulz Paul Dohotari
Team Team Team Team Team
Logistics Technical Applications Financials Purchasing Sales Basis Applications
Corporate IT - Headquarters Heiko Woeste Benjamin Stangneth Frank Sündermann Markus Juhnke Dr. Bierbrauer
Manager SAP Basis Manager EDI and Data Communications Head of Business Systems ContiTech Head of IT Management Fluid Technology CIO Contitech
Regional IT Managers Andy Choi Oscar González Karsten Lippeke Paul Dohotari
Asia America West and Central Europe Eastern Europe
Local IT - Location Responsible Thomas Schmidt Augustin Martinez Karsten Lippeke Andrea Singer Rade Seslija Oscar González Oscar González Haiyin Fang Miron Gasparella Paul Dohotari Michael Magurk Andy Choi Alonso Shi Carlos Vazquez Carlos Vazquez Frank Gortler Michael Magurk
007 024 041 115 148 175 186 194 222 249 343 344 473 496 497 812 883
-
TCH KARBEN ANOFLEX CT SCHLAUCH KÜHNER SERBIA MEXICANA CT NAFTA-MTY CHINA GRAND OCEAN KALUGA ROMANIA THERMOPOL L.L.C CT KOREA CHINA RUBBER & PLASTICS TECHNOL CT NORTH AMERICA INC. CT NORTH AMERICA INC. MGW GMBH BEATTIE CORP.
Prepared by Dohotari Paul 08/26/2015
Page 7 of 142
Confidential
e or more companies;
Prepared by Dohotari Paul 08/26/2015
Page 8 of 142
Confidential
[email protected] [email protected] [email protected]
[email protected] [email protected] [email protected] [email protected] [email protected]
[email protected] [email protected] [email protected] [email protected] [email protected]
[email protected] [email protected] [email protected] [email protected]
[email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Prepared by Dohotari Paul 08/26/2015
Page 9 of 142
Concepts 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
k Suendermann for any new connection between the systems Description
Dedicated server for printing production orders It is using the TCP/IP RFC :SEAL-CONNC-FRAVM097015 set up by Thomas Schmidt
Used for sending faxes from SAP ?? -
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
go to RFC Connections for details
Priority
1
2
Plants using this
Located
Responsible from Conti
007 Karben
Karben
Thomas Schmidt
all 812, 041
Karben Hann Muenden
Thomas Schmidt
041 all
Korbach
Lippeke Einfeld Andreas
Responsble from consultants
? Vogel Juergen:
[email protected] Office: +49 6151 492800-10 Mobile: +49 162 2573443
Brinkmann - BASF
Emergency 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,
Documentation
Concept
Printers naming convention
Printers concept
Responsibilities Local IT responsible Creation of printers Maintaining a printer settings Reacting for local printer problems
Basis Team Assigning naming ranges for locations Verifing / maintaining the print server Reacting for global printer problems
* for any new locations, the IT responsible should ask for the printers naming range that ** all printers names should have ONLY CAPITAL LETTERS Creation/ change/ deletion of a printer 1 Local IT opens a change in HPSM assigning to CI: vg_tech_sap_P23_gh 2 In the change the below form must be attached
Document
Example:
In the file there is an example for printer
ges for locations the print server ter problems
nters naming range that should be used
Concept
Printers concept
Printer Naming Convention for P23: special
Naming Range 0* - 9* A001 - A999 ABC1 - ABC4 AK* AS01 - AS07 AZ* B000 - B021 BMW1 CN* CR* CTH0 FF* - FF19 FI01 FRP1* IE01-IE10 IQ52 J* K0* K46A K500 K7-01 RK* KWH1 LOCL NO* O100-O137 OP* OVS1-OVS2 P103-P523 PABL PDF1 - PDF2 R012 - R498 RHE1-RHE4 RO* RW01-RW26 Rekl S001-S013 SAP1 SB*
Naming DigitReserved Range 4 yes 4 yes 4 4 yes 4 4 yes 4 4 4 yes 4 yes 4 4 4 8 4 4 4 Yes 4 yes 4 4 5 4 4 4 4 and more Yes 4 4 and 5 yes 4 4 4 4 4 4 4 yes 4 4 4 4 4 yes
SCR1-SCR5 SK01-SK02 TI04 TL* US* XI10 XIHH XIHM
4 4 4 4 yes 4 yes 4 4 4
Location Karben all Karben Anoflex Anoflex Anoflex Karben Karben Changchun Chanshu Hannover Romania Karben Karben Karben BIS OMS Team Koreea Karben Karben Karben Karben Kaluga Karben Local Printing Northeim Oppenweiler Oppenweiler Emergency Printers Hamburg Berlin PDF printers HannMuenden Hannover Romania Karben ?? Karben ? Subotica
Location Code 007 007
194 473 ??? ??? 007 007 007 ? 007 007 007 007 222 007 041 115 115 ??? ??? 812? 249 007 007 ?
Karben ??? Romania Mexico Somersworth Karben Karben Karben
007 249 175 343 007 007 007
Comment reserverd range for short naming - see second sheet
must be investigated
must be investigated
must be investigated
must be investigated must be investigated
small letters in name!!!! must be investigated
must be investigated only this one, should be changed
must be investigated must be investigated must be investigated
Concepts
Authorization Tools
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 steps:
Remark: !!!!
IT manager is responsible in front of KPMG for the documenta 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 user 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.
also the corporate users should be included in this checks (they should not be o
In case of missing X-Alerts, then an inventory must be performed once per year with the us KPMG decides what location will get the X-Alerts, small companies should not ge Rolls
1 every 2 years should be a check of the activities and organizations el 2 cross checking of modules: by example check all the MM roles if they
Restrict access to the table views - maximum key users can have access, no nor
ZBC_WORKLOAD_MONITOR existis in P52 client 100 with this we check the transactions used by user in one year and how often - go Matthias Gramm-Schwarze Matthias Gramm-Schwarze/ti1/ti/cag,
Authorization checks / helpers 1 Users that left must have the rolls deleted. 2 External users must have a different user group, so it can easely recognized.
MG for the documentation of the process
he results of the key users
ancial management signs o the central team.
ks (they should not be out filtered by the key users) !!!!
once per year with the users and their rights analyzed by the cost center leaders companies should not get it since there is big administrative effort
ties and organizations elements of all rolls k all the MM roles if they have transactions starting with F*…. can have access, no normal users
year and how often - good for removing rolls from the users assignment arze/ti1/ti/cag,
an easely recognized.
Concepts
Authorization Concept
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 Creatio
Rolls Creation Steps:
1 Organizational objects for the new plant have to be filled in the excel "Execute f 2 Derived Rolls are created with the transation ZWELLROLE and using the object v
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 r 2 Mass rolls allocation: tranzaction Z_USER_ROLE is used
Mass user rolls allocation
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 - go Matthias Gramm-Schwarze Matthias Gramm-Schwarze/ti1/ti/cag,
Authorization Users that left must have the rolls deleted. External users must have a different user group, so it can easely recognized.
Transactions
CEL_FILE
Transactions
"Template Users Creation"
d in the excel "Execute for role generator" on the sheet "Data" LE and using the object values from the excel "Execute for role generator" from the sheet "Info"
action PFCG
y transactions
d for finding the correct rolls
year and how often - good for removing rolls from the users assignment arze/ti1/ti/cag,
an easely recognized.
Concept Always ask Frank Suendermann for any new connection between the systems
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 ( BA
he systems
uest for connection ( BASF Change - in attention of Mr. Brinkmann)
Concept RFC Connections
Nr
Direction
Connection name ( only for outgoing)
From
1 Incoming
?
K12 / CSE
2 Outgoing
ADS
D23/008 Q23/008
3 Outgoing
ADS
P23/008
4 Incoming 5 Incoming 6 Incoming 7 Incoming 8 Incoming 9 Incoming
*SNP D19CL230 D19CLNT220 Q19CL230 Q19CL220 CHJCL230
D19 D19 Q19 Q19 CHJ
10 Incoming 11 Incoming 12 Incoming 13 Incoming
CHJCL220
CHJ
To
Conection Type
Q23/008 P23/008
3 ALECPIC_CSE
ctcdasci.conti.de : 53300
G
ctcpasci.conti.de : 53500
G
used for migration Q23 Q23 Q23 Q23 P23
User used in x23 system
SNP_TB_RFC C_Q23008_Q19 C_Q23008_Q19 C_Q23008_Q19 C_Q23008_Q19 C_P23008_CHJ
P23 D/Q/P23 Q23 P23
C_P23008_CHJ RFC_TANGRO RFC_PLM RFC_PLM TMSADM DIA_P23_PSR
Password
User used in external system
6ZHNMJU7
-
c0ntisap
ADSUSER
c0ntisap
ADSUSER
INIT01 INIT01 INIT01 INIT01 INIT01 INIT01
INIT01 INIT01 INIT01 PLMrfc1! 8SYSTX19
Contact person in the external system 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]
Andreas Einfeld
Andreas Einfeld Mitja Bamberger ( former Aytach Alpman) Andreas Einfeld Andreas Einfeld Andreas Einfeld Andreas Einfeld Andreas Einfeld
Andreas Einfeld Michaela Uzelac Morgan, Laurence Morgan, Laurence T-systems
Requested by
Andreas Kirsch/fr/eu/au/cag@CONTI07
Mitja Bamberger ( former Aytach Alpman) Andreas Einfeld Andreas Einfeld Andreas Einfeld Andreas Einfeld Andreas Einfeld
date
6/13/2013
9/1/2014
Andreas Einfeld Michaela Uzelac Thomas09 Schimdt Thomas09 Schimdt System
Description
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 See also SAP Note 944221
Check if the system is working by running the report FP_TEST_00 http://ctcpasci.conti.de:53500 user r and password from column J and I See also SAP Note 944221 Password for ADSUSER in SM59 corrected according to java system DAS. ADSAGENT created in Q23 / 000 and password for ADSAGENT maintained also in DAS 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
HR test productive Kaluga RFC user for the Tangro project RFC user for the PLM project RFC user for the PLM project TMS user from client 008, NOT used for the transport system
Concept
Nr. Crt
AL11 name 1 2 DIR_FTPFIDES 2 DIR_FTPFIDES 2 DIR_FTPFIDES
Folder name /usr/sap/austausch /usr/sap/interfaces/TECH/Z23/FIDES/IN /usr/sap/interfaces/TECH/Q23/FIDES/IN usr/sap/interfaces/TECH/P23/FIDES/IN
FTP user
Requested by
FTPFIDES/Start123 FTPFIDES/Start123 FTPFIDES/Start123
Thomas09 Schmidt Thomas09 Schmidt Thomas09 Schmidt
Used for Production To transfer To transfer To transfer
MGW files between the Fides application and the Z23 SAP system files between the Fides application and the Q23 SAP system files between the Fides application and the P23 SAP system
Concepts
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
Desired Situation Implementing the tranport gates
Cleaning the transport requests after 1 year
ASIS Team, based on the written email from BUKU
Concepts
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 transpor 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 reque ZZZ can be:
MHP CTF EXT
request created by MHP consultants request created by Contitech Fluid internal users request created by external consultants
XX can be:
BC CO DE ED FI IE MM PM PP PU QM
Basis Controlling Desing EDI Financials Industrial engineering Material Management Plant Maintenance Production Planning Purchasing Quality
Y can be:
SD WM
Sales and Distribution Warehouse Management
C W
Customizing Request Workbech Request
Examples:
Translation: "MHP_PP_C_Update of the production orders" "MHP_FI_W_Invoices" "CTF_ED_C_Ale Connection"
- MHP created a customizing - MHP created a workbench re -Contitech created a customiz
2 Choosing the Project
There is a project created for each plant that will join this year. Please select each time the correct project!!
w the below 2 rules:
of the scope of this transport request. the below format!
ntification and Y is the request type identification
d internal users
ranslation:
MHP created a customizing request affecting the PP module: Update of the Production Orders MHP created a workbench request affecting the FI module: Invoices Contitech created a customizing request affecting the EDI module: ALE Connection
Concept
Central instance
Server: ctcp23ci_P23_60 OS: HP-UX B.11.31 IP: 10.250.172.211
Database ORACLE 11.2.0.3.0 Host: fh007131 OS: HP-UX B.11.31
A1 application Server: ctcp23a OS: Linux x8 IP: 10.250.17
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
e 0
ALLE logon group
Concept Up Nr.Crt
Job Name 1 000_BASIS_DELETE OLD BATCH INPUT 2 000_BASIS_ZBC_LOCK_USER 3 000_BC_PFCG_ROLECOMPARISON 4 000_BC_DELETE_ROLES_INACTIVE_USR 5 000_BC_PROFIL_ROLE_COMP 6 000_BC_JOB_ADD_DAILY_DATA
000_BASIS_DELETE OLD BATCH INPUT
Variant:
ALL30OLD
000_BASIS_ZBC_LOCK_USER
1 job 000_BASIS_ZBC_LOCK_USER was created to automatically lock all the users that hav 2 We used the ZBC_LOCK_USER report, variant 90_DAYS_LOCK
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 rep 2 This job rans one a week (on Sunday )and deactivates the expired roles of the user
000_BC_DELETE_ROLES_INACTIVE_USR
1 Job was created using the report ZBS_ROLE_DEL with the 120DAYS variant 2 This job rans every Sunday from 23:00 and deletes the roles from the users that have no
000_BC_PROFIL_ROLE_COMP
1 Job was created using the program RHAUTUPD_NEW (PFCG mass comparison ), variant 0 2 It rans every Saturday and does a mass comparison of the users from every role
000_BC_JOB_ADD_DAILY_DATA
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
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 Creates a list with all the background jobs from the system
created to automatically lock all the users that have not loged into the system in the last 90 days create in P
variant 90_DAYS_LOCK
added an exception list
MPARISON using the PFCG_TIME_DEPENDENCY report and deactivates the expired roles of the user
ROLE_DEL with the 120DAYS variant 0 and deletes the roles from the users that have not logged into the system in the last 120 days
HAUTUPD_NEW (PFCG mass comparison ), variant 000_ROLE_COMP ss comparison of the users from every role
C_JOB_LIST with the 000_ADD_ALL variant
Frequency Weekly ( Sunday) Weekly ( Sunday) Weekly ( Sunday) Weekly ( Sunday) Weekly ( Saturday) Daily
Start Time Running Time( seconds) 11:00 23:30 1:00 23:00 20:00 4:00
57 2 590
800
em in the last 90 days create in P23 and M23
in the last 120 days
Concept
Title
x23 SAP Basis Tasks Nr. Crt
Frequency 1 Daily 2 Daily 3 Daily 4 Daily 5 Daily 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
systems
P23
future
once / ongoing
future future
SE64
create table groups so access is not given to all the ta
What Check instances status Check work processes Check tablespaces status Check db jobs Check canceled jobs Check canceled batch Memory check SAPOSCOL indicators Check system log Check System Dumps Check Idocs Interfaces Check RFC
Transaction SM51 SM50 DB02OLD DB14 SM37 SM35 ST02 ST06 SM21 ST22 BD87
Check Lock entries
SM12
Check Aborted Updates
SM13
SMQ1 / SMQ2 / SM58
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 Check printers for correct location and description
SPAD
Job list
Transport management - quality assurance Concept for Aborted Update
e table groups so access is not given to all the tables !!!!
SM13
$DICBERBCLS
How? see how see how see how see how see how see how see how see how see how see how see how SMQ2 / SM58
SAP Note
Select one week before
Action
Annouce the responsible users
Check the Idocs (inbound and outbound)
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 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
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 that is the moment when we can implement the Quality Assurance diagrama verifica pe SAP.com - fa analiza cu ce tranzactii au fost/ pivot
Responsible BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team BASIS team EDI BUKU
Comments
All BUKU
delete the old updates set up a time line!!!
HR + local IT
This is a INSTANCE DEPENDENT transaction, repeat this operation for ev
This is a INSTANCE DEPENDENT transaction, repeat this operation for ev
This is a INSTANCE DEPENDENT transaction, repeat this operation for ev
t this operation for every instance of the system
t this operation for every instance of the system
t this operation for every instance of the system
BACK
1 Go to in SM37 2 Select like below and as date choose the last 3 days 3 Execute
4 See the result
5 If there are any jobs that more than once canceled, please write email to the user who crea
mail to the user who created for investigating the reason
BACK
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
4 If the number of dumps is bigger then 70, then press on the today button and in 4.1 see if there is a users that is produceing this, then is a user problem 4.2 see if there is the same type of error to different users - then we hav
DBIF_RSQL_SQL they are related to the db
n the today button and investigate , then is a user problem - call user rent users - then we have a program problme, possible created by a transport - ask BUKU
BACK
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
4 Execute 5 On the result window, analyze if there is the same printer or the same user and see the rea
and select only "Problem"
ame user and see the reason why!
BACK
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 fo
the local EDI key users for solving them
BACK
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 here you go to the user and select the sesions that are WITHOUT any value on th
7 then press the "Sessions" button, click on the empty line and press then "End Se
8 repeat this until all entries from that user are cleared ( only the ones without tra 9 go back in the window with SM 66 and press refresh 10 do this for every user that have times with red
WITHOUT any value on the Transaction column
e and press then "End Sesion" button
only the ones without transaction values)
BACK 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
BACK 1 Go to transaction SM51 2 Check that all instances are up and have a green/active status
BACK 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 run
5 Double click on the session and select the empty value and press end session
6 repeat this until all entries from that user are cleared ( only the ones without transaction va
which the dialog wp is running and does not have a value on the transaction column, in the above example WIEG
end session
es without transaction values)
the above example WIEGANDS,
BACK 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 tablespa
4 Create a ticket to T-systems if the tablespaces have a used procentuaje of more than 95%
gnore the UNDO tablespace as this is a circular tablespace
tuaje of more than 95%
BACK 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
5 The warnings/errors will appear with a colored background
r red backgound)
BACK 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 o 5 Press the Goto tab, Performance database, This server history
6 The values cumulative value for each day will appear
7 Check that since the previous day no more than 10000 swaps were made
ld exceed 50%
ay, for this double click on the value of the swaps
BACK 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
emory availble
or every instance
BACK
1 Go to SM21 transaction 2 This an instance dependent transaction, in order to see the logs from all the system instan 3 Select the time interval
om all the system instances, go to System log-> Choose-> All remote system logs
Concepts Rules for importing transports in P23 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 like before.
ed ones per week,
ill be suspended
e planned to start ot be affected
of the transports
will be kicked
y will be unlocked
nary changes one by one before
stomizing transport n be imported
