How to identify who has imported a transport request in SAP system?

This article answers following queries:

• How to identify who has imported a transport request in SAP system?
• How to determine user id with which a transport is imported in SAP system?
• What transaction is used for checking who has imported a transport request?
• How to identify which user imported a transport request in SAP system?
• How to identify which user was used for importing a transport request?

====================================================

Sometimes, there might be requirement to determine who has imported a particular transport request.

Example Scenarios:

1) Transports were not imported in defined sequence

2) Wrong transport was imported

3) You want to determine which user id was used for transport import

In similar scenarios as mentioned above, while troubleshooting an issue, we may require to identify who has performed that transport import. Please proceed as follows to identify that

1) Login to respective SAP system, in which there is requirement to identify the user who has imported a transport request

2) Goto transaction STMS_IMPORT, which displays import queue of system (as shown below)

3)   In this screen, navigate to Goto menu and select Import History  (as shown below) to display import history of the system

4)   In that screen, Go to “Edit” menu and select “Display More” option

5)  It displays similar screen as shown below. Column “User” indicates user id with which particular transport got imported. Using that user id, we should be able to identify person, imported that transport

New SAP standard basis reorganization jobs

SAP has introduced 2 new standard reorganization jobs as per SAP note 1440439:

1. Job name: SAP_ADS_SPOOL_CONSISTENCY_CHECK

              Report: RSPO1042

              Description: Delete "orphaned" ADS spool files

              Note: 1493058

2. Job name: SAP_BTC_TABLE_CONSISTENCY_CHECK

              Report: RSBTCCNS

              Description: Check batch table consistency

              Note: 1549293

Implementation Process:

1. Implement note 1440439 using SNOTE transaction
2. Call transaction SM36 and select “Goto -> Standard Jobs” to schedule these reorganization jobs with a daily frequency 

     Please click below link for all the notes related to new standard reorganization jobs:

New Standard Basis Reorganization related notes

SAP Basis Standard House keeping Jobs

This article answers following queries:

• What are the standard sap background jobs to be scheduled?
• What are the standard SAP basis housekeeping jobs?
• Explain standard basis jobs, run frequency and their purpose?
• What are the standard jobs that should run in SAP system?
• What are the ABAP programs underlying in SAP standard jobs?
• What are SAP reorganization jobs?

=================================================

There are few background jobs that must run regularly in a production system, to, for example, delete old ABAP dumps, jobs and other obsolete entries. We need to should schedule following jobs periodically in the job definition transaction SM36, so that they are automatically triggered at the specified frequency

Sno	Job	Program	Description	Variant	interval
1	SAP_REORG_JOBS	RSBTCDEL2	Deletes old background jobs	Yes	Daily
2	SAP_REORG_SPOOL	RSPO0041/1041	Deletes obsolete spool requests to reduce system load	Yes	Daily
3	SAP_REORG_BATCHINPUT	RSBDCREO	Deletes Old Batch input Files	Yes	Daily
4	SAP_REORG_ABAPDUMPS	RSSNAPDL	Deletes Old ABAP Dumps	Yes	Daily
5	SAP_REORG_JOBSTATISTIC	RSBPSTDE	Deletes old job statistics	Yes	Monthly
6	SAP_COLLECTOR_FOR_JOBSTATISTIC	RSBPCOLL	Creates job statistics	No	Daily
7	SAP_COLLECTOR_FOR_PERFMONITOR	RSCOLL00	Starts data collectors for ABAP statistics records	No	Hourly
8	SAP_COLLECTOR_FOR_NONE_R3_STAT	RSN3_STAT_COLLECTOR	Starts data collectors for non-ABAP statistics records (Distributed Statistics Records, DSRs)	No	Hourly
9	SAP_REORG_PRIPARAMS	RSBTCPRIDEL	Reorganizes the print parameters across clients	Yes	Monthly
10	SAP_REORG_XMILOG	RSXMILOGREORG	Deletes obsolete entries in the XMI log	Yes	Weekly
11	SAP_CCMS_MONI_BATCH_DP	RSAL_BATCH_TOOL_DISPATCHING	Starts long-running data collectors that report application-specific values to the monitoring architecture	No	Hourly
12	SAP_SPOOL_CONSISTENCY_CHECK	RSPO1043	Checks the consistency of the spooler and of the TemSe and evaluates the results if necessary.	Yes	Daily
13	SAP_REORG_ORPHANED_JOBLOGS	RSTS0024	Delete "orphaned" job logs (joblogs that do not belong to any job)	Yes	Weekly
14	SAP_CHECK_ACTIVE_JOBS	BTCAUX07	This report the jobs that remain in ‘active’ status after the background work process terminates or after database connection problems occur	Yes	Hourly
15	SAP_DELETE_ORPHANED_IVARIS	BTC_DELETE_ORPHANED_IVARIS	Delete "Orphaned" Temporary Variants	Yes	Weekly
16	SAP_REORG_ORPHANED_TEMSE_FILES	RSTS0043	This job deletes orphaned Temse files. The job logs that cannot be deleted by RSBTCDEL will remain in the system as ‘orphans’. To delete these orphaned jobs, we schedule this program.	Yes	Weekly

Related Link: 

 New Standard Basis Reorganization Jobs

SAP Innovation - Quick answers to support questions with Expert Chat

Glad to inform you that, as part of SAP’s commitment to improve support experience, innovated and came up with “Expert Chat” functionality to support its customers by quickly answering support questions through expert chat.

The Expert chat program is built right into the incident form, which we use for creating OSS message to SAP.

To get started, just begin the process of incident submission by filling all relevant details like Product, Installation and System details (as shown below):

After providing above details, system prompts to enter few more details like priority, subject and details of the incident and component to which your issue belongs to (as shown below)

If a support engineer is available for the selected “component”, a green “Start Chat” button will be visible next to “Submit” button in the incident screen (as shown below)

If “Start Chat” button is clicked, a separate screen pops up (as shown below) and you will wait in queue

Once your turn comes, you will get opportunity to interact with SAP support expert who will understand query and provide answers right away. The information entered in the incident field will be transferred to support engineer to help in resolving issue

If unable to answer query immediately, the support representative will create an incident for you containing chat transcript and take it further to provide resolution. Therefore, no duplication of effort for the customer. The chat transcript will always be captured and recorded in your incident log for your convenience.

Please note, in case you don’t see “Start Chat” button in your incident form, either there is no support person available at that time for selected component or Expert Chat has not yet rolled out for selected component.

This “Expert Chat” functionality can be used to get assistance for any technical problem that can’t be answered by an SAP note or Knowledge Base Article (KBA).

If you wish to speed up or escalate request via chat, the best way is to contact the Customer Interaction Center (CIC). SAP recommends to start ONLY one chat session per problem that you have.

Please take advantage of this new Expert Chat functionality. 

How to identify recent parameter changes in SAP system?

This article answers following queries:

• How to identify recent parameter changes in SAP system?
• Which tcode is used to identify recent parameter changes of SAP system?
• How to identify changes done to sap parameters after a given period?
• How to view active parameters of SAP system?
• How to determine the date on which sap parameter values were recently changed?

==================================================

Sometimes, while troubleshooting, we may have requirement to identify SAP parameters that were modified recently.

 Example Scenario: Customers might be encountering performance issues (or any other accessibility issue) in SAP system. In those cases, we can check with customers from which date/time they are encountering this issue and we can check in system if any SAP parameters were modified during that time resulting in this issue.

1) To identify recent parameter(s) changes, TU02 tcode can be used.

Login to SAP ABAP system and execute transaction code TU02 which results in below screen

Screen 1:

In above screen, we can identify the date of most recent SAPSYSTEM parameter changes.

For example: In the above screenshot, we can determine that most recent SAP parameter changes were done on 02/12/2016 on mentioned host (highlighted in red)

2)  If you would like to know what SAP parameters were modified after a given date, click on “Select Period” push button in the above screen (highlighted in blue)

This results in below screen. Please enter date from which you want to know modifications done to SAP parameters and click on tick button

Screen 2:

This results in screen, similar to below, which lists date on which parameters were changed, parameter that was changed and new parameter value.

Screen 3:

3)   If you would like to know SAP active parameters, please click on “Active Parameters” pushbutton on Screen1 (highlighted in yellow). This will result in below screen, which shows parameter and its current (or active) value

Screen 4:

4) If you would like to know history of SAP parameters, please click on “History of File” pushbutton on Screen1 (highlighted in white). This will result in below screen, which shows parameter name, latest modified date and its new value

Screen 5: