fss bw operations - infopackage failure due to unupdated idoc in r3 or bw

8/22/2019 FSS BW Operations - Infopackage Failure Due to Unupdated IDOC in R3 or BW

1/7

Info-Package Failure Due to Un-Updated IDOC in R3 or BW

Document Version / Dtails : Ver 1.0 / 16-Feb-2011

Record Of Release

VersionNo.

Created/Modified By Reviewed By Release Date Modifications Done

1.0 Sanjay Dubey /Saurabh Gupta

Pawan KChaturvedi

16/02/2011

Project ID: E6806 Project Name: FSS BW Operation


2/7

Info-Package Failure Due to

Un-Updated IDOC in R3 or BW

4PM-03-04

Ver 1.0/16-Feb-2011

Page 2 of 7

Scope of Document: This document helps us to understand the steps to be followed in case of Info-Package Failure Due to Un-Updated IDOC in R3 or BW.

We have two type of IDOC, one for data and other for information. Data IDOC brings the data inn thesap system in the form of ALE mechanism, Information IDOCs carries the information regarding thetransfer of data e.g. following number of data are successfully transferred.

Step1: Log in the SAP.Enter below details:Connection Type: Custom Application serverDescription: GRPApplication server: 155.111.150.189 (we can use from 187 to 194)System ID: GRPClient: 400

Step 2: User have to enter user name and password.


3/7



4PM-03-04

Ver 1.0/16-Feb-2011

Page 3 of 7

Step 3: Run the transaction SA38.

Step4: Run the program /SSA/BWT.

Step 5: After clicking execution, below screen will appear having radio button for process chain alreadyclicked. Click on execute.


4/7



4PM-03-04

Ver 1.0/16-Feb-2011

Page 4 of 7

Step6: After executing, click on process chain. Below screen will appear. Enter the corresponding time

and date for process chains. You can create a variant also in this case. Click on execute. Afterexecution all process chains under that time and date selection will appear.

Step 7: In this Info package is Stuck due to Un-Updated IDOC in BW.


5/7



4PM-03-04

Ver 1.0/16-Feb-2011

Page 5 of 7

Step 8: Now we will find out the root cause of info-package failure, Right click on the stuck info-package and then click on Process Monitor.

Step 9: Go to details Tab and see the details.

Step 10: Here in detail tab it will ask whether you want detail about the IDOCs or Not. Then click on

YES.


6/7



4PM-03-04

Ver 1.0/16-Feb-2011

Page 6 of 7

Step 11: In below screen it is clearly shown that Info IDoc 2 is not moving forward. Copy the IDocnumber and go to transaction BD87 (Process inbound IDocs.)

Step 12: In transaction BD87 enter the IDoc Number and execute it.


7/7



4PM-03-04

Ver 1.0/16-Feb-2011

Page 7 of 7

Step 13: Here click on the IDoc and then click on the Process.

Step 14: Here it is clearly shown that IDoc has been successfully transferred to the monitoringUpdating.

fss bw operations - infopackage failure due to unupdated idoc in r3 or bw

Documents