Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9760

Re: Unable to replicate material from ecc to srm sysfail for DNL_CUST_PROD0

$
0
0

Erro tempo execução MESSAGE_TYPE_X 
Data e hora 26.06.2014 00:34:51 
  

   

Texto breve 
   The current application triggered a termination with a short dump. 


   

O que aconteceu ? 
   The current application program detected a situation which really 
   should not occur. Therefore, a termination with a short dump was 
   triggered on purpose by the key word MESSAGE (type X). 


   

O que pode ser feito? 
   Note down which actions and inputs caused the error. 
  
  
   To process the problem further, contact you SAP system 
   administrator. 
  
   Using Transaction ST22 for ABAP Dump Analysis, you can look 
   at and manage termination messages, and you can also 
   keep them for a long time. 


   

Análise do erro 
   Short text of error message: 
   No external system (such as CRM) connected 
  
   Long text of error message: 
   Diagnóstico 
     " " " " " " 
   Atividades do sistema 
   Procedimento 
   Procedimento para administração do sistema 
  
   Technical information about the message: 
   Message class....... "C_" 
   Number.............. 050 
   Variable 1.......... "No external system (such as CRM) connected" 
   Variable 2.......... " " 
   Variable 3.......... " " 
   Variable 4.......... " " 

 

Notas p/eliminação de erros 
   Probably the only way to eliminate the error is to correct the program. 
  
   If the error occures in a non-modified SAP program, you may be able to 
   find an interim solution in an SAP Note. 
   If you have access to SAP Notes, carry out a search with the following 
   keywords: 
  
   "MESSAGE_TYPE_X" " " 
   "SAPLCRM0" or "LCRM0U68" 
   "CRM_FIRST_CALL_OPERATIONS" 
  
   If you cannot solve the problem yourself and want to send an error 
   notification to SAP, include the following information: 
  
   1. The description of the current problem (short dump) 
  
     To save the description, choose "System->List->Save->Local File 
   (Unconverted)". 
  
   2. Corresponding system log 
  
     Display the system log by calling transaction SM21. 
     Restrict the time interval to 10 minutes before and five minutes 
   after the short dump. Then choose "System->List->Save->Local File 
   (Unconverted)". 
  
   3. If the problem occurs in a problem of your own or a modified SAP 
   program: The source code of the program 
     In the editor, choose "Utilities->More 
   Utilities->Upload/Download->Download". 
  
   4. Details about the conditions under which the error occurred or which 
   actions and input led to the error. 
  

 

   

Ambiente de sistema 
   SAP-Release 700 
  
   Application server... "vwbranssap009" 
   Network address...... "10.135.7.192" 
   Operating system..... "Windows NT" 
   Release.............. "5.2" 
   Hardware type........ "8x AMD64 Level" 
   Character length.... 16 Bits 
   Pointer length....... 64 Bits 
   Work process number.. 0 
   Shortdump setting.... "full" 
  
   Database server... "VWBRANSSAP009" 
   Database type..... "ORACLE" 
   Database name..... "Q02" 
   Database user ID.. "SAPR3" 
  
   Terminal................. "VWVICKLPUC16" 
  
   Char.set.... "C" 
  
   SAP kernel....... 700 
   created (date)... "Mar 14 2011 22:32:10" 
   create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00" 
   Database version. "OCI_10201_SHARE (10.2.0.4.0) " 
  
   Patch level. 293 
   Patch text.. " " 
  
   Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" 
   SAP database version. 700 
   Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows 
   NT 6.0, Windows NT 6.1" 
  
   Memory consumption 
   Roll.... 16192 
   EM...... 29328880 
   Heap.... 0 
   Page.... 16384 

   MM Used. 25215808 


 

  Client.............. 305 
   User................ "RFC_KSQ_100" 
   Language Key........ "E" 
   Transaction......... " " 
   Transactions ID..... "53A3A354429639D1E10000000ABA717D" 
  
   Program............. "SAPLCRM0" 
   Screen.............. "SAPMSSY1 3004" 
   Screen Line......... 2 
  
   Information on caller of Remote Function Call (RFC): 
   System.............. "KSQ" 
   Database Release.... 740 
   Kernel Release...... 740 
   Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) 
   Call Type........... "synchron and transactional (emode 0, imode 0)" 
   Inbound TID.........." " 
   Inbound Queue Name..." " 
   Outbound TID........."0ABA717D39D153AB946706DD" 
   Outbound Queue Name.."R3AI_DNL_CUST_BASIS3" 
  
   Client.............. 100 
   User................ "DVIDM4K" 
   Transaction......... " " 
   Call Program........."SAPLERFC" 
   Function Module..... "ARFC_DEST_SHIP" 
   Call Destination.... "LOGQ02305" 
   Source Server....... "sapit4_KSQ_03" 
   Source IP Address... "10.186.113.125" 
  
   Additional information on RFC logon: 
   Trusted Relationship " " 
   Logon Return Code... 0 
   Trusted Return Code. 0 
  
   Note: For releases < 4.0, information on the RFC caller are often 
   only partially available. 

 

   

Infos p/ponto de cancelamento 
   Termination occurred in the ABAP program "SAPLCRM0" - in 
   "CRM_FIRST_CALL_OPERATIONS". 
   The main program was "SAPMSSY1 ". 
  
   In the source code you have the termination point in line 75 
   of the (Include) program "LCRM0U68". 

 

    

Segmento texto fonte 
LinhaTxt.fonte 
  45  OTHERS = 1. 
  46  
  47  IF sy-subrc = 0 AND lv_arfctid IS INITIAL. 
  48  CALL FUNCTION 'CRM0_UPDATEINFO_CRMRELEASE'. 
  49* exceptions 
  50* others = 1. 
  51  ENDIF. 
  52* Get the parameters for the RFC conection. 
  53  c_stshd-mass_queue = c_stshd-mass_data. 
  54  PERFORM get_download_params_and_queue 
  55  TABLES t_bapistructures 
  56  USING c_stshd-objname 
  57  c_stshd-objclass 
  58  gv_destination 
  59  gv_rfc_queue 
  60  gv_server_release 
  61  i_bapicrmdh2 
  62  c_stshd-mass_queue 
  63  c_stshd 
  64  i_transfer_data 
  65  i_crmrfcpar 
  66  e_rfcoltp. 
  67  
  68* Set variables 
  69  e_synchronous_call = gv_synchronous_call. 
  70  
  71* Raise an error if the destination of the foreign system could not be 
  72* found. (Only during Initial Load, Upload, Compare and Requests). 
  73  IF gt_rfcdest[] IS INITIAL AND 
  74  NOT i_bapicrmdh2-ref_id IS INITIAL. 
>>>>>  MESSAGE x050(c_) WITH 
  76  'No external system (such as CRM) connected'(007). 
  77  ELSE. 
  78  t_rfcdest[] = gt_rfcdest[]. 
  79  ENDIF. 
  80  
  81  IF i_bapicrmdh2-dwnloadtyp EQ chard OR 
  82  i_bapicrmdh2-dwnloadtyp EQ chare OR 
  83  NOT c_stshd-objclass IS INITIAL. 
  84  gv_obj_class = c_stshd-objclass. 
  85  ENDIF. 
  86* In case of missing object class, fill it with the default object name 
  87  IF c_stshd-objclass IS INITIAL. 
  88  c_stshd-objclass = c_stshd-objname. 
  89  gv_obj_class = c_stshd-objclass. 
  90  ENDIF. 
  91  ELSE. 
  92  t_rfcdest[] = gt_rfcdest[]. 
  93  ENDIF. 
  94  
   MM Free. 4109104 



Viewing all articles
Browse latest Browse all 9760

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>