Errors while Sending Packages from OLTP to BI (One of Error at the Time of Data Loads through Process Chains)

Transcription

1 Errors while Sending Packages from OLTP to BI (One of Error at the Time of Data Loads through Process Chains) Applies to: SAP NetWeaver Business Warehouse (Formerly BI), Will also work on SAP BI 3.5. For more information, visit the EDW homepage Summary This article gives clear picture about how to correct the one of the data load error in process chains, i.e. If you are using Process Chains for daily Data loads and if you get an Error called Errors while sending packages from OLTP to BI, after reading this article you can correct your self the above error. Author: Surendra Kumar Reddy Koduru Company: ITC Infotech India Ltd. (Bangalore/INDIA) Created on: 20 June 2011 Author Bio Surendra Kumar Reddy Koduru is a SAP BI Lead Consultant currently working with ITC Infotech India Ltd (Bangalore/INDIA). He has got rich experience and worked on various BW/BI Implementation/Support Projects and he is the author for various Articles and Blogs (SAP-BW/BI) in SAP Community Network SAP AG 1

2 Table of Contents Introduction:... 3 Live Scenarios:... 3 How to correct:... 3 Errors Message:... 6 Related Content Disclaimer and Liability Notice SAP AG 2

3 Introduction: This article gives tells about the how to correct the one of the data load error in process chains, i.e. If you are using Process Chains for daily Data loads and if you get an Error called Errors while sending packages from OLTP to BI, after reading this article you can correct your self the above error. Here in this case I taken Master data Loads as an example and, and which I was faced the real situation in BW Production System. Live Scenarios: We are having various Process chains for Data Loads, i.e. Master Data Loads, Transactional Data Loads, and Meta Chains, i.e. I summarized the process chains into Two Meta Process Chains, one is for Master Data (which is having 5 normal Master Data Loads process chains) and another is for Transactional DataLoads (which is having 4 normal Transactional Data Loads Process Chains) This is a sample for Master Data Meta Process Chain is struck up because of one of the normal Process chain is failed, and we will see how to correct the same. Note: Here I m not showing the Meta Data Process Chain, the above one is just normal Process chain and which is included in Meta Chain. How to correct: If you see the above Log for Process chain in RSPC, we got an error on , the chain is included in Meta Chain, just follow the below step by step screens and explanations, then correct the above error SAP AG 3

4 See the error log for 0BILL_CAT_TEXT Master Data in RSPC Tcode. See the same in below screen. Errors while sending packages from OLTP to BI Diagnosis No IDocs could be sent to BI using RFC. System Response There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI. Further analysis: Check the TRFC log. You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system". Error handling: If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system SAP AG 4

5 Goto the Indiv.Messages Tab and open/see the complete text message SAP AG 5

6 Errors Message: Errors while sending packages from OLTP to BI: Message no. RSM2011 Diagnosis No IDocs could be sent to BI using RFC. System Response There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI. Further analysis: Check the TRFC log. You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system". Error handling: If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system. Click on Backg Tab and see the below message. Click on Batch Monitor Button 2011 SAP AG 6

7 See the Job status in below Job Overview Screen. Click on Job Log Button SAP AG 7

8 See the complete log. After above step, close the above screens and Click on Chain Tab in main Process chain error log Dialog Box. Click on Process Tab, it will display the actual error message like below. Click on Process Monitor Button SAP AG 8

9 It will takes to you to Monitor screen and it will popup Request Status Changes Window, you just say NO. You just note down the request number like below and follow the steps given below SAP AG 9

10 Goto SM37 in ECC Source System and give the above request id and check the log SAP AG 10

11 If you see the log, the job is already Finished and Success. So there is no problem in job execution. So go back to the Monitor screen in BW/BI, see the below screen which is having the error message SAP AG 11

12 Expand and see the Error log in Details Tab. Go to the Status Tab and then see the error message and click on Transaction RFC button. So with this we understand that there is problem with trfc SAP AG 12

13 Once you click on Transaction RFC button, it will takes to you Source System, so give ID and Password. See the below screen. After giving ID and Password, it will takes to you into Transactional RFC screen, and you also can see directly using SM58 in Source System SAP AG 13

14 Just give Date and User Name as * and then execute and see the below LUW s which are struck at trfc location. Execute the LUW s manually like below. See the below screen and give the inputs to the below parameters as per your System names and Dates etc. Here I given inputs based on my System details and dates SAP AG 14

15 Keep Cursor on Each Check Button and then Press F1 and see the help text. Once you execute LUW s manually you will get the message in bottom of the screen, like below SAP AG 15

16 If you see/monitor the screen continuously the messages will change, for example see the below screen with different message, like that it will execute/run and finally it will clear all LUW s in trfc. Now come back to RSPC in BW/BI i.e. open the error Process chain log in BW/BI using RSPC Tcode SAP AG 16

17 Just right click on Error Node and repeat the process, E.g it will ask waiting time in seconds, so just give 5 or 6 and continue. So like that you can correct all similar kind of Data Loads error in Process Chains. After correcting all error nodes the process chain will becomes to Green SAP AG 17

18 Related Content For all Articles and Blogs by Surendra Kumar Reddy, Please visit this URL Using Customer Exit Variables in BW Reports Part - 5 Using Customer Exit Variables in BW Reports Part - 6 Using Customer Exit Variables in BW Reports: Part - 8 Using Customer Exit Variables in BW Reports: Part - 9 Using Customer Exit Variables in BW Reports: Part - 10 Using Customer Exit Variables in BW Reports: Part - 11 Using Customer Exit Variables in BW Reports: Part - 12 Using Customer Exit Variables in BW Reports: Part - 13 Using Customer Exit Variables in BW Reports: Part - 14 Using Customer Exit Variables in BW Reports: Part - 15 Using Customer Exit Variables in BW Reports: Part - 16 Using Customer Exit Variables in BW Reports: Part - 17 Using Customer Exit Variables in BW Reports: Part - 18 Using Text Variables with Customer Exits in Report Headings Using Text Variables with Customer Exits in Report Headings Variables of Type Customer Exit For more information, visit the EDW homepage 2011 SAP AG 18

19 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 19