2018-07-02 Page 1/9

Incident: 39237 / 2018 - Runtime error TIME_OUT has

occured
ID 012005041000000392372018
Customer 614128 - Pakistan Petroleum Limited
Installation 0020130456 - R/3 mysap.com customer
System PRD - PPLKHIHO24
Component Joint Venture Accounting (CA-JVA-JVA)
Status Customer Action
Priority Very High
Estimated Automatic Confirmation Date 15.07.2018

Communication
29.06.2018 11:38:52 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SY-SYSID ............... PRD SY-MANDT ............... 300 Installation number .... 0020130456 System type
............ Production System SAP version Database ............... Database Server Vendor ................. Name
................... IP address ............. Type ................... CPU type ............... Operating system ....... Message
Server Vendor ................. Name ................... IP address ............. Type ................... CPU type ...............
Operating system ....... Software Component/Release/Support Package Level

29.06.2018 15:20:48 PKT - Problem Description: PPL-SIEMENS Service Desk (S0011787005)

Dear SAP Support, Runtime error TIME_OUT has occurred We have been facing "ABAP Programming
Error" while Reversing or Resetting any financial document using FB08, F.80, FBRA and etc. Could you
please advise the reason / Solution to fix this issue at earliest as we are in the phase of last critical days of
Annual Close. Furthermore the parameter mentioned in the dump
"rdisp/scheduler/prio_[high|normal|low]/max_runtime" was already extended to "1500 seconds" Still the issue
persists. Regards, Shabbir Cell # +92-321-3833218

29.06.2018 15:26:15 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

Dear SAP Support, Runtime error TIME_OUT has occurred We have been facing "ABAP Programming
Error" while Reversing or Resetting any financial document using FB08, F.80, FBRA and etc. Could you
please advise the reason / Solution to fix this issue at earliest as we are in the phase of last critical days of
Annual Close. Furthermore the parameter mentioned in the dump
"rdisp/scheduler/prio_[high|normal|low]/max_runtime" was already extended to "1500 seconds" Still the issue
persists. Regards, Shabbir Cell # +92-321-3833218

29.06.2018 16:05:01 PKT - Call to Customer: SAP

Contact Person: Department PPL-SIEMENS Service Desk Call time: 2018.06.29 / 13:04:00 / CET Contact
Number: +92-321-3833218 Customer reached Y/N: N Call back Y/N: Subject of Call:

29.06.2018 16:11:36 PKT - Reply: SAP

Dear Shabbir, I tried to call you but I failed. To continue processing your incident, it would be useful for me
also to recreate the above-mentioned situation on your test systemvia a remote connection. Therefore I need
open access to your system, where I can do my tests. The system PRD is currently closed. Please confirm
the following logon data and open the related system with the maintenance of the logon informations
according Notes 1773689 and 2281599. - System - Server - Client - User In addition, please provide me a

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 2/9
variant for transaction FBRA. Meanwhile, I would like to ask you to pay attention to the following Notes:
Please check if it is relevant to your release and readit in full before implementing the note. 17831 - Long
runtimes for FBRA, RFKORK00, RFKORD00 and SAPF140 2256654 - FBRA: Clearing Reset transaction
terminated with error TIME_OUT in program SAPF100 Best regards, Ágnes Pistyur-Kocsis SAP Product
Support SAP hotline for urgent issues-> details in note 560499
======================================================================== DID YOU
KNOW? You can find details of common issues, fixes, patches and much more by visiting SAP moderated
forums on: SAP WIKI:http://wiki.sdn.sap.com/wiki/x/KhE SAP
FORUM:https://go.sap.com/community/topic/financials.html Explore our Customer Influence site:
https://www.sap.com/about/customer-involvement/input-beta-testing.html#existingprojects 2172375 - How we
search 2081285 - How to get best results from an SAP search?
======================================================================== SAP is now
offering Expert Chat and Schedule an Expert support for specific product components. Get answers quickly
and conveniently! Try our brand new support services: Expert Chat Schedule an Expert

30.06.2018 07:11:50 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 30.06.2018 07:06:14 Dear SAP Consultant: Thanks for the support. My
Cell # +923213833218 was available at your called time but I have no idea why you could not connect.
However, our SAP PRD OSS connection could be opened for READ access with the very special
permission. Do we have any other option like TeamViwer or ay other screen sharing software where we can
have a joint session and we can browse the required screens or run the required transactions of SAP PRD
system for you?? Addtionally, I have gone through the SAP notes you referred and found them irrelevant in
current situation. Referring SAP note 17831, tabe count of BKORM is around 5 lacs, which is quite low as i
have experienced in our system. Even reversal / reset works very quickly when this count is around 3-4
milions. Regarding 2256654, crrently ABAP Dump is referring to SAPMF05A or include LGJVIF2K. Extract of
ABAP Dump: "Information on where terminated The termination occurred in ABAP program "SAPLGJVI", in
"REVERS_FIDOC". The main program was "SAPMF05A". In the source code, the termination point is in line
315 of (Include) program "LGJVIF2K". Error occurred during batch input processing" Please advise Regards,
Shabbir Hussain Contact: +923213833218

30.06.2018 09:06:49 PKT - Call to Customer: SAP

Contact Person: Department PPL-SIEMENS Service Desk Call time: 2018.06.30 / 12:05:48 / UTC+8 Contact
Number: 923213833218 Customer reached Y/N: Y Call back Y/N: Subject of Call: the remote connection to
system PRD is closed, customer will confirm if SAP can logon, if yes, customer will open it and provide the
logon information.

30.06.2018 09:08:34 PKT - Reply: SAP

Dear Shabbir , Thank you for answering the phone. As we talked, we can not use TEAMVIEWER to check in
your production system. Please confirm from your side if you can open the R/3 remote connection to PRD
system. If yes, please open the connection and provide the logon data accordingly. Thank you very much.
Best regards, Lingyun Cong SAP Product Support

30.06.2018 10:23:41 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 30.06.2018 07:06:14 Dear SAP Consultant: Thanks for the support. My
Cell # +923213833218 was available at your called time but I have no idea why you could not connect.
However, our SAP PRD OSS connection could be opened for READ access with the very special
permission. Do we have any other option like TeamViwer or ay other screen sharing software where we can
have a joint session and we can browse the required screens or run the required transactions of SAP PRD
system for you?? Addtionally, I have gone through the SAP notes you referred and found them irrelevant in
current situation. Referring SAP note 17831, tabe count of BKORM is around 5 lacs, which is quite low as i
have experienced in our system. Even reversal / reset works very quickly when this count is around 3-4

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 3/9
milions. Regarding 2256654, crrently ABAP Dump is referring to SAPMF05A or include LGJVIF2K. Extract of
ABAP Dump: "Information on where terminated The termination occurred in ABAP program "SAPLGJVI", in
"REVERS_FIDOC". The main program was "SAPMF05A". In the source code, the termination point is in line
315 of (Include) program "LGJVIF2K". Error occurred during batch input processing" Please advise Regards,
Shabbir Hussain Contact: +923213833218

30.06.2018 12:26:50 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 30.06.2018 12:21:13 Dear SAP Consultant: Thanks for the support SAP
OSS connection of our SAP PRD system has been opened. You may use the below information to connect
the SAP PRD system. User credentials maintained under secure area of the message: Client: 300 SYS No:
00 Application Server: PPLKHIHO24 User ID: FI_OSS Password : maintained under secure area of the
message. Connection type : R/3 Steps for documents reversal: 1- Execute transansaction FB08 and input
following information: a- Document number: 1006898 b- Company Code: PPL c- Fiscal Year: 2018 d-
Reversal Reason: 02 e- Posting Date: 30.06.2018 2- Press enter and then press save button to post the
reversal document. You may also use this list of documents for any further investigation: 1006898 / PPL /
2018 1006915 / PPL / 2018 1007014 / PPL / 2018 1007093 / PPL / 2018 1007046 / PPL / 2018 1007076 /
PPL / 2018 1007237 / PPL / 2018 1007109 / PPL / 2018 Please go head, start your investigation and in case
you need any other SAP Authorizations, please let me know with all the required details. Waiting for your
urgent posstive response please. Regards, Shabbir Contact #: +923213833218

30.06.2018 19:18:55 PKT - Reply: SAP

Dear Customer, The R/3 connection to PRD is closed. PRD SAP Product Vers. SAP ERP 6.0                         
                         PROD       -  Connections             R/3 Support                 Closed             Windows Terminal
Server     Closed I have adjusted the component to CA-JVA-JVA. Best regards, Linda Homoki SAP Product
Support SAP hotline for urgent issues-> details in note 560499
======================================================================== DID YOU
KNOW? You can find details of common issues, fixes, patches and much more by visiting SAP moderated
forums on: SAP WIKI: http://wiki.sdn.sap.com/wiki/x/KhE SAP
FORUM:https://go.sap.com/community/topic/financials.html 2081285 - How to get best results from an SAP
search? ======================================================================== SAP
is now offering Expert Chat support for specific product components. Please check the following link to get
more information about chat support and steps on how to start an Expert Chat session:
https://launchpad.support.sap.com/#/notes/2213344/E
========================================================================

30.06.2018 19:18:56 PKT - Call to Customer: SAP

Contact Person: Department PPL-SIEMENS Service Desk Call time: 2018.06.30 / 16:18:42 / CET Contact
Number: +923213833218 Customer reached Y/N: n Call back Y/N: Subject of Call:

30.06.2018 21:11:44 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 30.06.2018 21:06:06 Dear SAP Consultant: We have checked with our
BASIS team and they have responded that the connection is quite open (screen shot enclosed). Please do
let us know how we can assisit you in reaching our SAP PRD system. Please note that the communication
through SAP SOLMAN via SAP partner is a very slow process and if we will keep on communicating this way
then we would have to extend our Annual close, which is very bad on our part, SAP partner and SAP itself. If
possible, kindly communicate directly via email, which would help all of us in resolving this CRITICAL issue.
Regards, Shabbir Hussain Contact # +923213833218 Email: [email protected]

30.06.2018 23:47:32 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 30.06.2018 21:06:06 Dear SAP Consultant: We have checked with our
BASIS team and they have responded that the connection is quite open (screen shot enclosed). Please do

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 4/9
let us know how we can assisit you in reaching our SAP PRD system. Please note that the communication
through SAP SOLMAN via SAP partner is a very slow process and if we will keep on communicating this way
then we would have to extend our Annual close, which is very bad on our part, SAP partner and SAP itself. If
possible, kindly communicate directly via email, which would help all of us in resolving this CRITICAL issue.
Regards, Shabbir Hussain Contact # +923213833218 Email: [email protected]

01.07.2018 00:27:12 PKT - Call from Customer: SAP

Mr. Shabbir Hussain called to request speed up Contact:+923213833218

01.07.2018 00:43:09 PKT - Info for Customer: SAP

Dear Shabbir, The Experts needed to troubleshoot this case are going to be available on Monday, please
expect an update by then. Sincerely, Guilherme Leipnitz - Manager on Duty / SAP Product Support / For
contact information, please see Note 560499

01.07.2018 14:52:42 PKT - Call from Customer: SAP

Mr. JAN, Abdullah 11:56:49 / CET Contact Number: +923213833218 Customer reached Y/N: Y Dear
customer, As just discussed over the phone, the remote connection is currently closed. Please open it up
and make sure the crendentials are maintained properly in the secure store while we are identifying the right
expert to troubleshoot the issue. Thank you and best regards, Fouad LOTFI SAP Backoffice EMEA

01.07.2018 22:35:08 PKT - Call to Customer: SAP

Contact Person: Shabbir Hussain Call time: 2018.07.01 / 19:28:08 / CET Contact Number: - +92 321 383
3218 Customer reached Y/N: Yes Call back Y/N: No Subject of Call: Dear Customer, I am assigned as
De-Escalation Architect (DEA) during US time zone to support you in decreasing the business impact caused
by this issue. From functional perspective my collegues have looked into this issue and I am
technically analyzing the issue in detail. However, as we discussed I need Debug/Developer authorization
inorder to proceed. Kindly coordinate with your BASIS and provide necessary authorizations to sapsupport
'FI_OSS' user. Kind regards, Sabyasachi Dutta SAP BO

01.07.2018 22:37:55 PKT - Call to Customer: SAP

Contact Person: Shabbir Hussain Call time: 2018.07.01 / 19:28:08 / CET Contact Number: - +92 321 383
3218 Customer reached Y/N: Yes Call back Y/N: No Subject of Call: Provide Debug developer authorization
to technically analyse the issue. Dear Customer, I am assigned as De-Escalation Architect (DEA) during US
time zone to support you in decreasing the business impact caused by this issue. From functional
perspective my collegues have looked into this issue and I am technically analyzing the issue in detail.
However, as we discussed I need Debug/Developer authorization inorder to proceed. Kindly coordinate with
your BASIS and provide necessary authorizations to sapsupport 'FI_OSS' user. Kind regards, Sabyasachi
Dutta SAP BO

01.07.2018 22:48:17 PKT - Reply: SAP

Dear Shabbir, From functional perspective my collegues have looked into this issue and I am
technically analyzing the issue in detail. However, as we discussed over the phone call, I need
Debug/Developer authorization inorder to start analysing. Kindly coordinate with your BASIS
team and assign Developer Role to sapsupport 'FI_OSS' user. Apart from debug rights, please
provide authorizations for transactions such as ST22, SM13, SE80, SE37, SE38, SE24 etc. Thanks and best
regards, Sabyasachi Dutta SAP BO

01.07.2018 22:50:23 PKT - Info for Customer: SAP

Dear Shabbir, Please provide authorizations to ABAP dictionary transactions - SE11, SE16 etc. Best regards,
Sabyasachi Dutta SAP BO

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 5/9
01.07.2018 23:04:16 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 01.07.2018 22:58:33 Dear SAP Consultant: Thanks for the support. We
have updated the SAP authorization profile of SAP user "FI_OSS" and included the devloper trasactions in it.
Kindly update us with the list of transactions, if any further required. Regards, Shabbir Hussain Contact:
+923213833218 Email: [email protected]

01.07.2018 23:31:45 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 01.07.2018 23:26:04 Dear SAP Consultant: We have further updated the
authorization profile of "FI_OSS" and added these transactions. ST22 SM13 SE80 SE37 SE38 SE24 SE11
SE16 Regards, Shabbir Hussain Contact: +923213833218 Email: [email protected]

02.07.2018 01:12:48 PKT - Info for Customer: SAP

Dear Shabbir, As discussed in our meeting, my recommendation for you would be to create a secondary
index with the where clause fields REFDOCNR, REFRYEAR, REFDOCCT, RBUKRS, RRCTY, RVERS,
KTOSL, AWORG and BUDAT to support the select query that causes the 'Timeout' dump. Please implement
and share us the results if you are able to reverse the FI documents successfully. Thanks and best regards,
Sabyasachi Dutta SAP BO

02.07.2018 05:50:10 PKT - Call to Customer: SAP

Contact Person:  Mr. Shabbir Hussain Call time: 2018.07.02 / 02:47:23 / CET Contact
Number: +923213833218 Customer reached Y/N: Call back Y/N: Y Subject of Call: 1. Check if the secodnary
index is implmented. 2. Recomend to adjust the paramenter rdisp/max_wprun_time from 1500 to 7200.

02.07.2018 06:05:15 PKT - Info for Customer: SAP

Dear  Mr. Shabbir Hussain, Nice talking with you. As checked, firstly we should try to avoid the TIME_OUT
short dump, the dump is caused byThe maximum runtime of a program is set by system profile parameter
 "rdisp/scheduler/prio_[high|normal|low]/max_runtime". The current setting is  1500 seconds. Once this limit
has been exceeded, the system attempts to interrupt the SQL statement or to instruct the ABAP processor to
terminate the program. It waits for a maximum of 60 seconds. If the program is then still active, the
work process is restarted. Here we can dynamically increase the parameter rdisp/max_wprun_time via
transaction rz11,  set  rdisp/max_wprun_time = 7200. Please implement and share us the result. As
mentioned by you that the Test system with same condition, but without issue. Please let us know once you
are able to open the connection. If any questions, please feel free to reach me. Thanks and Best Regards,
Laura Zhang [email protected] De-Escalation Architect MaxAttention Critical Situation Team Mission
Critical Center APJ

02.07.2018 08:02:16 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 02.07.2018 01:07:45 Dear Sabyasachi Dutta, First of all thanks alot for
such an extended discussion regarding the issue and i appreciate your support and efforts. Regarding the
reversal of FI doc 0001005898 / PPL / 2018 and its JV document 0001142168 / PPL / 2018 in our SAP TEST
system (PPLKHIHOV16), the document got reversed in a second (screen attached). Now the point is that
why these docuements are easily getting reversed in our TEST environment and out lanscape systems but
not in SAP Production system??? This needs further investigation at SAP part and in the mean time we will
try to give you access of our SAP TEST system as well for better investigation and understanding of the real
issue. Regards, Shabbir

02.07.2018 09:00:00 PKT - Info for Customer: SAP

Dear Shabbir, Thanks for the update. Even the landscape for Test and Prod environment are the same,
however the Data volume, concurrency and CPU usage might be difference, that will also impact the
performance. Based on previous analysis, we would recommend firstly try to avoid the dump and let the

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 6/9
reverse finish, by : 1. add secondary index with the where clause fields REFDOCNR, REFRYEAR,
REFDOCCT, RBUKRS, RRCTY, RVERS, KTOSL, AWORG and BUDAT 2. adjust the parameter
rdisp/max_wprun_time to 7200 Please let us know if the recommendation works from your side, if this not
working, we will need to further analysis. Thanks, Laura Zhang

02.07.2018 10:19:37 PKT - Call to Customer: SAP

Contact Person:Mr. Shabbir Hussain Call time: 2018.07.02 / 07:17:36 / CET Contact
Number:  +923213833218 Customer reached Y/N: Call back Y/N: Y Subject of Call: Check the
implementation status. Adding secodary index is in progress, customer will transport to PROD shortly and
update the incident. Thanks, Laura

02.07.2018 13:46:10 PKT - Info for SAP: PPL-SIEMENS Service Desk (S0011787005)

SHABBIR HUSSAIN (0000000289) 02.07.2018 13:40:26 Dear SAP Consultant: We are pleased to inform
that after implementing the first recommendation, reversal of FI documents became smooth. We have
created the secondary index on JVSO1 with the required fields and found it working fine for documents
reversal. We are observing the SAP production and will keep this incident open during the observation time
period. In the meantime we are closing the OSS connections of our SAP PRD & TEST systems. We will
update you shortly via this incident. Thanks for the support please. Regards, Shabbir Hussain

Contacts

Secondary
Role Name Time Zone Primary Phone E-Mail
Phone

PPL-SIEMENS 
+92-2111156856
Reporter Service Desk CET
8
(S0011787005)

Attachments

File Name Description File Type File Size Created By Created On

PPL-SIEMENS
Reversal Reversal 30.06.2018
PDF 1.9 MB Service Desk
Dump.pdf Dump.pdf 12:48:01 PKT
(S0011787005)

PPL-SIEMENS
connection connection 30.06.2018
JPG 97.4 KB Service Desk
01.jpg 01.jpg 21:11:52 PKT
(S0011787005)

PPL-SIEMENS
connection connection 30.06.2018
PNG 183.3 KB Service Desk
02.png 02.png 21:11:52 PKT
(S0011787005)

remote remote
01.07.2018
connection connection PNG 48.5 KB SAP
14:59:15 PKT
closed.PNG closed.PNG

LGJVIF2K from LGJVIF2K from PPL-SIEMENS

02.07.2018
SAP TEST SAP TEST TXT 55.3 KB Service Desk
08:04:27 PKT
system.txt system.txt (S0011787005)

Document Document
PPL-SIEMENS

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 7/9
reversal result in reversal result in DOCX 208.4 KB Service Desk 02.07.2018
SAP TEST SAP TEST (S0011787005) 08:04:27 PKT
System.docx System.docx

Action Log

Changed On Changed At Changed By Action Old Value New Value

Friday 29.06.201 Memo/Text
15:23:07 PKT SAP Info for SAP
8 changed

  15:23:07 PKT SAP Status Not Sent to SAP Sent to SAP

  15:23:07 PKT SAP Priority changed Medium Very High

0120050410
  15:23:07 PKT SAP Incident created 0000039237
2018

  15:23:07 PKT SAP Component FI-GL-GL-N

Memo/Text
  16:13:29 PKT SAP Reply
changed

  16:13:29 PKT SAP Status Sent to SAP Customer Action

Memo/Text
Sat. 30.06.2018 07:08:11 PKT SAP Info for SAP
changed

In Processing by
  07:08:11 PKT SAP Status Customer Action
SAP

Memo/Text
  09:10:17 PKT SAP Reply
changed

In Processing by
  09:10:17 PKT SAP Status Customer Action
SAP

Memo/Text
  10:20:24 PKT SAP Info for SAP
changed

In Processing by
  10:20:24 PKT SAP Status Customer Action
SAP

PPL-SIEMENS
Memo/Text
  12:26:50 PKT Service Desk Info for SAP
changed
(S0011787005)

Memo/Text
  19:20:08 PKT SAP Reply
changed

In Processing by
  19:20:08 PKT SAP Status Customer Action
SAP

  19:20:08 PKT SAP Component FI-GL-GL-N CA-JVA-JVA

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 8/9
PPL-SIEMENS Memo/Text
  21:11:44 PKT Info for SAP
Service Desk changed
(S0011787005)

Memo/Text
  23:43:12 PKT SAP Info for SAP
changed

In Processing by
  23:43:12 PKT SAP Status Customer Action
SAP

Sunday 01.07.20 Memo/Text Call from

00:27:12 PKT SAP
18 changed Customer

Memo/Text Info for

  00:43:09 PKT SAP
changed Customer

Memo/Text Call from

  14:52:42 PKT SAP
changed Customer

Memo/Text
  14:58:26 PKT SAP Call to Customer
changed

Memo/Text
  22:35:08 PKT SAP Call to Customer
changed

Memo/Text
  22:37:55 PKT SAP Call to Customer
changed

Memo/Text
  22:50:18 PKT SAP Reply
changed

In Processing by
  22:50:18 PKT SAP Status Customer Action
SAP

Memo/Text Info for

  22:50:23 PKT SAP
changed Customer

PPL-SIEMENS
Memo/Text
  23:04:16 PKT Service Desk Info for SAP
changed
(S0011787005)

PPL-SIEMENS
Memo/Text
  23:31:45 PKT Service Desk Info for SAP
changed
(S0011787005)

Monday 02.07.2 Memo/Text Info for

01:12:48 PKT SAP
018 changed Customer

Memo/Text
  05:50:10 PKT SAP Call to Customer
changed

Memo/Text Info for

  06:05:15 PKT SAP
changed Customer

PPL-SIEMENS
Memo/Text
  08:02:16 PKT Service Desk Info for SAP
changed
(S0011787005)

© 2018 SAP SE or an SAP affiliate company. All rights reserved

2018-07-02 Page 9/9
  09:00:00 PKT SAP Memo/Text Info for
changed Customer

Memo/Text
  10:19:37 PKT SAP Call to Customer
changed

PPL-SIEMENS
Memo/Text
  13:46:10 PKT Service Desk Info for SAP
changed
(S0011787005)

Action Plan

Planned Compl.
Step Responsible Step Status Creation Date
Date

analysis started,
need system Access SAP Product
In Progress 29.06.2018 16:12:11
for further Support
investigations

02.07.2018 14:50:02 PKT

© 2018 SAP SE or an SAP affiliate company. All rights reserved