Exception x_error raised in a FM :SO_NEW_DOCUMENT_ATT_SEND_API1

Hi All,
when FM : SO_NEW_DOCUMENT_ATT_SEND_API1 is called from another custom defined function module EX : Z_SEND_MAIL by exporting subject and attachment name and by passing tables for email address,body and attachment
to send an email message report for post goods issue failures it is raising an exception (X_ERROR : Internal error or database inconsistency) when an empty attachment is sent and it is working fine when attachment contains some content.Please help me out in this regard as i'm not able to find the suitable solution. thanks in advance.
Regards,
akanksha.

Hi,
Please see the function module documentation for sample code.
I recommend you check the following blogs also.
<a href="/people/thomas.jung3/blog/2004/09/08/sending-e-mail-from-abap--version-610-and-higher--bcs-interface">Sending E-Mail from ABAP - Version 610 and Higher - BCS Interface</a>
<a href="/people/gregor.wolf3/blog/2006/05/25/extend-thomas-jung146s-simple-mail-function-with-attachment-filename Thomas Jungs simple mail function with Attachment Filename</a>
<a href="/people/thomas.jung3/blog/2004/09/07/sending-e-mail-from-abap--version-46d-and-lower--api-interface">Sending E-Mail from ABAP - Version 46D and Lower - API Interface</a>
Cheers,
Ramki Maley.

Similar Messages

RFC Send could not be resolved against SAP system because its metadata could not be obtained...EXCEPTION FU_NOT_FOUND RAISED

Hello,
I am getting the following error in sending IDOC to SAP via WCF-SAP adapter in BizTalk Server 2009. I have the SOAP header in the adapter mentioned below. Also, wondering what is the convension for Action URL? Is it always "http://Microsoft.LobServices.Sap/2007/03/Rfc/"
+ Operation name mentioned in the Orchestration? I would appreciate if anyone could help me resolve this error.
The adapter failed to transmit message going to send port "SendReceive_PO_IDOC_TO_SAP" with URL "sap://CLIENT=111;LANG=EN;@a/123.456.789.101/00?GWHOST=123.456.789.101&GWSERV=sapgw00&ListenerProgramId=ABCDEF111&RfcSdkTrace=False&AbapDebug=False".
It will be retransmitted after the retry interval specified for this Send Port. Details:"Microsoft.ServiceModel.Channels.Common.MetadataException: RFC Send could not be resolved against SAP system because its metadata could not be obtained. ---> Microsoft.Adapters.SAP.RFCException:
Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=EXCEPTION FU_NOT_FOUND RAISED. AdapterErrorMessage=An error occurred while determining the function interface of the RFC Send.
at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
at Microsoft.Adapters.SAP.InternalRfcMetadata..ctor(String originalRfcName, SAPConnection sapConnection)
at Microsoft.Adapters.SAP.SAPMetadataContract.ResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
at Microsoft.ServiceModel.Channels.Common.Design.MetadataCache.GetOperationMetadata(String uniqueId, Guid clientId, TimeSpan timeout)
at Microsoft.ServiceModel.Channels.Common.MetadataLookup.GetOperationDefinition(String operationId, TimeSpan timeout)
at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper
timeoutHelper)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
SOAP Header:
<BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Operation Name="Send" Action="http://Microsoft.LobServices.Sap/2007/03/Rfc/Send" />
</BtsActionMapping>
Thanks,
Tarun

Hello Morten,
The Send is actually just the name of the operation in Orchestration and it does not exist in SAP. Hence, do I really need to have the SOAP header in WCF-SAP adapter or can I send the IDOC without any SOAP header info? When I try to send without
SOAP header I get the following error. Can you help me resolve this?
The adapter failed to transmit message going to send port "SendReceive_PO_IDOC_TO_SAP" with URL "sap://CLIENT=111;LANG=EN;@a/123.456.789.101/00?GWHOST=123.456.789.101&GWSERV=sapgw00&ListenerProgramId=ABCDEF111&RfcSdkTrace=False&AbapDebug=False". It
will be retransmitted after the retry interval specified for this Send Port. Details:"System.ArgumentNullException: Value cannot be null.
Parameter name: key
at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.CreateChannelFactory[TChannel](IBaseMessage bizTalkMessage)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.InitializeValues(IBaseMessage message)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2..ctor(IBaseMessage message, WcfTransmitter`2 transmitter)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfTransmitter`2.GetClientFromCache(String spid, IBaseMessage message)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfAsyncBatch`2.BatchWorker(List`1 messages)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Thanks,
Tarun

MDDataSetBW.GetCellData EXCEPTION FUNCTION_NOT_FOUND RAISED. (WIS 10901)

Hello Guru,
I am facing one issue when i try to execute one Webi Report. I created Universe on top of 0PP_C14 Infocube. I am using Basic Finish Date, Production Order, Group Finish Date as Dimension and Number of Manufacturing orders as Keyfigures and executed the query. I get error "MDDataSetBW.GetCellData EXCEPTION FUNCTION_NOT_FOUND RAISED ()WIS 10901)".
I search on SDN but didn't find anything that helped me. i tried to refresh the univere, Re-export it again but not helped me. I have only 20,000 records in my infocube so data is not huge. We have support pack level SAPKW70021 at BW side and 12.3.0.601 on BOBJ side (Service pack 3 and fix paxk 0)
Can anyone help me to find the solution ?
Regards,
Rishit Kamdar

Are all the required transports included in the integraiton Kit XI 3.1 SP3 imported in your SAP BW system?
Regards,
Stratos

PageFlowScope lost when some exception is raised

Hi all,
I store a flag in the pageflowscope programatically
RequestContext rq = RequestContext.getCurrentInstance();
rq.getPageFlowScope().put("LoadedFlag","loaded");
I have a jspx page using a backing bean for its values. I load data for the first time and set the LoadedFlag.
However, if any exception is raised (in my case a POPUP for a required field exception), the pageflowscope values are lost.
How to handle it ? .. I want the pageFlowScope to be set even if any exception is raised.
Any suggestions ?
Thanks.
Edited by: user9138987 on Jul 2, 2010 2:19 PM

Yes it is true, the popup definitely has a new pageflowscope but the pageflowscope is retained when we get back to the page (i.e after closing the popup)
It works.
Thanks frank for the quick reply
Edited by: user9138987 on Jul 9, 2010 9:02 AM

Exception CX_SY_RANGE_OUT_OF_BOUNDS raised while executing a Web Report

Hi Gurus,
When I executed a Web Report, I got the following Exception
CX_SY_RANGE_OUT_OF_BOUNDS
when it is filtered for September month report is working fine, but when filtered for October month got the following message
Messages:
An exception with the type CX_SY_RANGE_OUT_OF_BOUNDS occurred, but was neither handled locally, nor declared in a RAISING
Part-field access (offset = 4, length = 2) to a data object of the size 3 exceeds valid boundaries.
Could anyone please tell me how to solve this issue.
Thanks in advance.
Madhusudhan

Good afternoon,
The following SAP Notes may be helpful for you ...
1240222   Filter value from compound characteristic is not displayed
1266170   Exception CX_SY_RANGE_OUT_OF_BOUNDS
1100955   RS_EXCEPTION000 in parallel query execution
Regards,
Karen

Exception handling raised in named subprograms

Hi,
I would like to call three procedures from a when button pressed trigger and deal with them individually.
I tried naming the exception in the procedure, not to handle it there, and get it to propagate in the calling trigger.
Here is the code for the When-Button-Pressed Trigger:
declare
     too_much exception;
     begin
          p_valider_total_ht;
     :b_utils.f_nom := 'Everythingsfine' ;
     go_item( 'B_UTILS.F_NOM' );
exception
when others then
lib_alert(' Exc en pb valider ' || to_char(sqlcode) || 'xxx' || sqlerrm );
end;
Here is the code for the procedure:
PROCEDURE p_valider_total_ht
IS
     too_much exception;
BEGIN
     if :jbm_contrat.total_ht > 900 then
          raise too_much;
     end if;
     exception
          when too_much then
          raise;
when others then
lib_alert(' Exc en f_valider_total_ht ' || to_char(sqlcode) || 'yyy' || sqlerrm );
END;
It works, but the sqlcode contains: 1, wich means I can't distinguish between exceptions cases.
I tried the pragma exception init approach, but then Forms became really cross and threw a very big error message.
Many thanks for your help.

Hi,
It looks like pragma exception_init only works for existing Oracle error codes and messages.
I have written a function that returns 'OK' or KO' and the calling trigger raises an exception if 'KO' is returned.
Many thanks.

How to display which exception Is Raised?

Hi
Experts.
I am trying to connect my webDynpro with oracle.
I had already included Jar at both places.
now I want to display in exception that which error is coming?
I had already written <b> ex.printStackTrace(); </b>
but it is not working.
Code Is given Below.
Connection conn=null;
          try
          wdComponentAPI.getMessageManager().reportException("after 0",false);
          Class.forName("oracle.jdbc.driver.OracleDriver");
          wdComponentAPI.getMessageManager().reportException("after 1st",false);
          DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
          wdComponentAPI.getMessageManager().reportException("after 2nd",false);
          conn =DriverManager.getConnection ("jdbc:oracle:thin:@Server IP:1521:adaniinframs","scott", "tiger");
          wdComponentAPI.getMessageManager().reportException("after 3",false);
          Statement stmt=conn.createStatement();
          wdComponentAPI.getMessageManager().reportException("after 4",false);
          ResultSet rs=stmt.executeQuery("select ename from emp where empno=7369"); // select statment
          wdComponentAPI.getMessageManager().reportException("after 5",false);
          while(rs.next())
          wdComponentAPI.getMessageManager().reportException("after 6",false);
          IPrivateDatabaseConnectView.INodeEmpElement a = wdContext.createNodeEmpElement();
          a.setEmpName(rs.getString(1));
          a.setEmpJob(rs.getString(2));
          wdContext.nodeNodeEmp().addElement(a);
          catch(Exception ex)
                ex.printStackTrace();
          finally
           try
          conn.close(); // closing the connection
          catch(Exception e)
          ex.printStackTrace();
Regards
Sunny.

I don't think the user may see anything if you execute e.printStackTrace(); so what you have to do is report an exception with the text of the stack trace:
IWDMessageManager manager = wdComponentApi().getMessageManager();
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
e.printStackTrace(pw);
String message = sw.toString();
manager.reportException("Excepcition raised: " + message, false);
With this you will report the whole stack trace. If you want to get only the cause you will have to parse the message string. e.getMessage() should do this for you but if doesn't return anything quite often.

Exception "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE"

Hi All,
We have the Java web dynpro applications running smoothly in development system.
But in Quality system we are getting the following issue.
Exception condition "CNTL_ERROR" raised., error key: RFC_ERROR_SYSTEM_FAILURE"
All users are created with same authorization as in development system.
Still getting the problem.
Any idea how to solve this problem.
Thanks in advance.
Regards,
Sumangala.

Hi ,
CNTL_ERROR" raised is something related to backend system . ask backend consultants to check any dumps related to this error.
Regards,
Koti Reddy

Exception CNTL_ERROR raised when using REUSE_ALV_GRID_DISPLAY

Hi,
I would like to ask your help concerning the following issue. I have a program called ZBAL_ZSTOCK2 which uses the following FM :
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_interface_check       = 'X'
      i_buffer_active            = space
      i_callback_program    = g_program
      is_layout                   = gs_layout
      it_fieldcat                  = gt_fieldcat[]
      it_sort                       = gt_sort[]
      i_save                       = 'A'
      is_variant                  = gs_variant
      it_events                   = gt_events[]
      is_print                     = gs_print
    IMPORTING
      e_exit_caused_by_caller   = g_exit_caused_by_caller
      es_exit_caused_by_user   = gs_exit_caused_by_user
    TABLES
      t_outtab                    = it_alv[]
    EXCEPTIONS
      program_error            = 1
      OTHERS                   = 2.
It works fine when I run it in foreground.
This program is called from another program, using the statement:
SUBMIT zbal_zstock2
      USING SELECTION-SET varianta
      WITH SELECTION-TABLE rspar
      EXPORTING LIST TO MEMORY AND RETURN.
In this last case, the program ZBAL_ZSTOC2 short dumps during of execution of FM - 'REUSE_ALV_GRID_DISPLAY', method SET_VISIBLE, with following explanation:
Error analysis
    A RAISE statement in the program "CL_GUI_CONTROL================CP" raised the
     exception
    condition "CNTL_ERROR".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
The line where the error is raised into method SET_VISIBLE is:
16 * check handle
17   IF ME->H_CONTROL IS INITIAL.
>>>>     RAISE CNTL_ERROR.
19   ENDIF.
Do you have any idea how to avoid this short dump?
I appreciate any suggestion.
Thank you in advance,
M

You cannot use ALV GRID in background. You need to go for ALV LIST Function Module.
PLease search with ALV GRID BACKGROUND in the search field of SCN. You will get lot many posts related to this and solutions are given.
regards,
Padma

Exception not raised

heloo...
i had 1 procedure for inserting value. when i call that procedure it doesnot raise exception evenif there is error.
any one can help me out ...........................

>>Passing that many parameters across is looking for problems. It is very easy to
transpose parameters when there are more than 3 or 4 parameters. This proc has 14.Can you explain this sir in detail
When a programmer needs to call you stored proc with 14 parameters, he must be very careful in placing his variables and values in the right sequence to ensure that the right variable/value is passed to the right parameter.
A good programmer will not take a chance and code 14+ lines of code for this procedure call, e.g.
begin
... code ..
SPINSERTATTRIBUTE(
AttributeId => var1,
Name => var2,
Label => var3,
Description => var4,
Category => var5,
Datatype => var6,
MinValue => var7,
MaxValue=> var8,
DefaultValue => var9,
AllowNull => var10,
Enumeration => var11,
Len => var12,
Scale => var13,
Values=> var14,
Result => var15
.. code...
end;Now this is a lot of code to write. Easy to get the sequence wrong. A not-so-good programmer will be lazy and will instead code this - which is even more dangerous as it is a lot easier to get the parameter sequence wrong:
begin
..code..
SPINSERTATTRIBUTE( var1, var2, var3, var5, var6, var8, var7, var9, var10, var11, var12, var13, var14 );
.. code..
end;Do not make it complex and difficult for others (and yourself) to call a procedure/function.method that you have written.
> Is there possible to pass any number of argument while calling the procedure with
argument type as %rowtype?
Do not understand the question... A procedure can in theory contain unlimited parameters (there could be some pratical limitations in PL/SQL though).
%ROWTYPE is no different that a C struct definition or a Pascal/Delphi record definition.
%ROWTYPE is a special definition that tells the PL/SQL engine that the variable is a record structure that matches the layout of a specific SQL table.
It is easy to use as the definition of the structure is defined once - it is the definition of the SQL table. If the DBA adds a column or drops a column, your record structure definition in PL/SQL does not need to be manually changed.
Typically a caller will call the sample stored procedure InsertAttribute I wrote as follows:
attrRow attributes%ROWTYPE;
begin
-- create a new attribute
attrRow.Name := 'SHIPPING COSTS';
attrRow.Datatype := 'NUMBER';
.. etc..
InsertAttribute( attrRow );
.. code ..
end;

PL SQL with multiple inserts, how to continue after exception is raised

Hi,
I have a simple PL SQL function with various inserts. ex:
Insert Into "DI01"."DUA_DIM_UNITE_ADMIN" (Ide_Unite_Admin_Sk, Num_Unite_Admin, Des_Unite_Admin) Values ('-1', '00000000', 'Défaut');
INSERT INTO "DI01"."DUA_DIM_UNITE_ADMIN" (IDE_UNITE_ADMIN_SK, NUM_UNITE_ADMIN, DES_UNITE_ADMIN) VALUES ('-2', 'S. O.', 'Sans Objet');
Insert Into "DI01"."DCU_DIM_CATGR_UNSPS" (Ide_Catgr_Sk, Num_Code, Des_Code, Num_Catgr, Des_C.........
I want to be able to run the function multiple times, and have all the inserts executed everytime, even if I get a ORA-00001 unique constraint (string.string) violated error in on of the inserts. That means that if I get an error in the first insert, I want the function to continue running and executing the consecutive inserts.
I though of including each insert in a different block, like:
BEGIN
Insert......
When Exception then null;
END;
BEGIN
Insert......
When Exception then null;
END;
But I have at least 50 inserts, so the final code becomes huge.
Another solution is to use merge inseat of insert, but the code seems too complex for such a simple task.
Is there any other solution for this that I am not seeing?
Thank you for your time,
Joao Moreira

You can use DML error logging approach or FORALL SAVE EXCEPTIONS.
Since you didn't mention the version I assume you are using 11g.
Below is the sample code for DML error logging mechanism
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL> DROP TABLE tableA;
Table dropped.
SQL> DROP TABLE Err$_tableA;
Table dropped.
SQL>
SQL> CREATE TABLE tableA
2 (
3     col1   NUMBER PRIMARY KEY,
4     col2   NUMBER,
5     col3   VARCHAR2 (10)
6 );
Table created.
SQL>
SQL> -- Create error log table
SQL>
SQL> BEGIN
2     DBMS_ERRLOG.create_error_log (dml_table_name => 'TABLEA');
3 END;
4 /
PL/SQL procedure successfully completed.
SQL>
SQL> BEGIN
2     FOR i IN (SELECT 1 AS col1 FROM DUAL
3               UNION ALL
4               SELECT 1 FROM DUAL)
5     LOOP
6        INSERT INTO tableA (col1)
7             VALUES (i.col1)
8                LOG ERRORS INTO Err$_tableA REJECT LIMIT UNLIMITED;
9     END LOOP;
10
11     COMMIT;
12 END;
13 /
PL/SQL procedure successfully completed.
SQL> column column_name format a30
SQL> set linesize 300
SQL> select * from tableA;
SQL> select * from err$_tablea;
Thanks,
GPU

While i am starting a Managed server some security Exception is raised

JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
WLS Start Mode=Development
CLASSPATH=:/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/jdk160_05/lib/tools.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic_sp.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.jar:/home/durgasoft/HDFC_bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/webservices.jar:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/durgasoft/HDFC_bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/durgasoft/HDFC_bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/xqrl.jar::
PATH=/home/durgasoft/HDFC_bea/wlserver_10.3/server/bin:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/bin:/home/durgasoft/HDFC_bea/jdk160_05/jre/bin:/home/durgasoft/HDFC_bea/jdk160_05/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/durgasoft/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
Starting WLS with line:
/home/durgasoft/HDFC_bea/jdk160_05/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=/home/durgasoft/HDFC_bea/wlserver_10.3 -Dwls.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=Admin_URL -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sysext_manifest_classpath -Dweblogic.Name=hdfc_mng6_1 -Djava.security.policy=/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
<Jun 24, 2012 5:31:42 AM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://Admin_URL.>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file /home/durgasoft/HDFC_bea/domains/HDFC_DOV_Domain/servers/hdfc_mng6_1/logs/hdfc_mng6_1.log is opened. All server side log events will be written to this file.>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters..
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unknown Source)
at weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(Unknown Source)
Truncated. see log file for complete stacktrace
com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unknown Source)
Truncated. see log file for complete stacktrace
com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
at com.bea.common.ldap.properties.LDAPStoreServicePropertiesConfigurator.convertStoreProperties(LDAPStoreServicePropertiesConfigurator.java:53)
at com.bea.common.security.internal.service.StoreServiceImpl.initJDOProperties(StoreServiceImpl.java:101)
at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:73)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
Truncated. see log file for complete stacktrace
>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Hi,
Please remember to mark the answers accordingly... Helpful or correct... You will be helping the forum community by doing that.
First thing to fix is the Admin_URL, there should be something like:
-Dweblogic.management.server=http://localhost:7001How are you starting this managed server? Node manager or command line? Try both options and see if they bring up the same error.
Cheers,
Vlad

Re: Raising Exceptions Vs returning erro[Ref:C809787]

Hi Steve !
Probably the following explanation might help in resolving the issue raised by
you:
At a more abstract level, there is only one thing, i.e. the EVENT. According to
it's definition, an event is a relatively infrequent occurrence in one portion (lets
call it event raiser) of the application, which some other portion (or portions,
lets call them event handlers) (of the same application) are interested to respond
to it. Now there are two scenarios:
(A) Event raiser and Event handler(s) are being executed under different threads
of control (Asynchronous) and
(B) Event raiser and Event Handler(s) are being executed under same thread of
control (Synchronous).
So, Exception Handling belongs to scenario B where the method raising the
exception (Event Raiser or exception raiser) and the method handling it (Event
Handler or exception block) are under the same thread of control. More ever it has
to be insured that at a time only one handler (first the inner most one) receives
the message.
Forté provides a generic Event handling mechanism (Post Event and Event Loop) to
handle the scenario A (which is the more generic one). But it also provides a
specialized Event Handling mechanism (Raise Exception and Exception block) to
efficiently handle the relatively simple scenario B. Why I am saying that the later
is efficient because it won't be needing to register the event queue address of the
interested task (after all there is only one task involved) and put the event
message in queue.
Finally let me mentioned that it is just my view based on the understanding I
have and it may not be true. Only a person from forté can confirm it. I will really
appreciate if somebody correct and or refine it.
Wish a Very Very Happy New Year to all Forté Users
Regard,
Kailash.
[email protected] wrote:
I would agree with Eric entirely. Exceptions seem to me to be a much more
complete solution to the problem of error handling. A little bit of effort up
front in making clear the strategy for exception handling and specifying the
exceptions that can be raised by a class\method will provide an excellent method
for error handling.
In the case of ensuring exceptions are always handled, a top level handler for
GenericException will usually do the job, allowing you to write error
information out to logs, screen, etc, and then shut down gracefully.
The only issue I would raise with exceptions is that they are not propagated
outside an asynchronous task. If an exception is not handled within an
asynchronous, it will not propagate to the task that started that asynchronous
task. Forte provides return and exception events when starting asynchronous
tasks to cope with this, but it seems a shame to have one method of dealing with
errors (exceptions) for synchronous behaviour, and another (events) for
asynchronous behaviour.
Steve Elvin
Systems Developer
Frontline Ltd.
UK
Mark,
The problem with return codes is that there is an underlying assumption
that the receiver will always catch and interpret that error code. This
may or may not be good thing, depending on how you architect your
application. If, on the other hand, you want to ensure that an error is
always handled, if not by the receiver then by the Forte, Exceptions are
the way to go. To extend this mechanism further, I would subclass
GenericException and created my own error code attribute on that
subclass. That way the receiver has the choice of interpreting the
exception based on that error code, and wrapping it in a
MessageDialog/window or do the usual 'errormgr.showerrors()'.
Exceptions seem a more flexible approach to me. That is, if you can live
with the fact that by using it, you're violating the 'exceptions for
behavioral anomalies' software engineering principle !
Best wishes.
Eric Pereira
Forte Consultant
----Original Message Follows----
From: "Kallambella, Ajith" <[email protected]>
To: "'Mark Sundsten'" <[email protected]>, [email protected]
Cc: [email protected]
Subject: RE: Raising Exceptions Vs returning error codes
Date: Wed, 30 Dec 1998 08:52:39 -0500
Reply-To: "Kallambella, Ajith" <[email protected]>
Mark,
Identifying conditions where you would rather use an exception
to an error_code ( and vice-versa ) normally depends on
your application design. Usually exceptions
are used to handle behavioral anomalies which are
not expected during the normal course of execution of
the program, and which would affect the continuity of
your algorithm if ignored. Examples would be a fatal
error, a semantically invalid( but syntactically-valid
token ) etc.
Error_codes and return status's can be used to handle
anticipated and recoverable errors. Example would
be presentation layer validations. In any normal
UI system, the user is expected to make errors and it
would be annoying to throw an exception( and to handle
it ), every time user enters wrong data. A well
modeled client layer should not only handle
data-validation errors , but should be smart enough
to encourage users to input correct or
"near-correct" data. Examples could be
making use of look-up windows etc. Interestingly,
Express uses exceptions to handle data-validations.
As you see, exceptions fit well into your processing
logic where severity of damage caused by an error
is more. Where as error_codes fit well into presentation
logic( and some not-so-critical processing logic ) where
errors are usually recoverable and normal path of
execution can be easily restored.
Hope this helps. I would be very interested to hear
what others have to say.
Ajith Kallambella. M
Forte Systems Engineer,
International Business Corporation.
-----Original Message-----
From: Mark Sundsten [mailto:[email protected]]
Sent: Tuesday, December 29, 1998 2:10 PM
To: [email protected]
Cc: [email protected]
Subject: Raising Exceptions vs returning error codes
When dealing with error handling, I find myself struggling with the
choice
of
raising exceptions (and handling them) from the caller
vs returning an error code of somekind.
When would you want to use one over the other?
Should you always use exception handling?
Any discussion would be appreciated.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi Steve !
Probably the following explanation might help in resolving the issue raised by
you:
At a more abstract level, there is only one thing, i.e. the EVENT. According to
it's definition, an event is a relatively infrequent occurrence in one portion (lets
call it event raiser) of the application, which some other portion (or portions,
lets call them event handlers) (of the same application) are interested to respond
to it. Now there are two scenarios:
(A) Event raiser and Event handler(s) are being executed under different threads
of control (Asynchronous) and
(B) Event raiser and Event Handler(s) are being executed under same thread of
control (Synchronous).
So, Exception Handling belongs to scenario B where the method raising the
exception (Event Raiser or exception raiser) and the method handling it (Event
Handler or exception block) are under the same thread of control. More ever it has
to be insured that at a time only one handler (first the inner most one) receives
the message.
Forté provides a generic Event handling mechanism (Post Event and Event Loop) to
handle the scenario A (which is the more generic one). But it also provides a
specialized Event Handling mechanism (Raise Exception and Exception block) to
efficiently handle the relatively simple scenario B. Why I am saying that the later
is efficient because it won't be needing to register the event queue address of the
interested task (after all there is only one task involved) and put the event
message in queue.
Finally let me mentioned that it is just my view based on the understanding I
have and it may not be true. Only a person from forté can confirm it. I will really
appreciate if somebody correct and or refine it.
Wish a Very Very Happy New Year to all Forté Users
Regard,
Kailash.
[email protected] wrote:
I would agree with Eric entirely. Exceptions seem to me to be a much more
complete solution to the problem of error handling. A little bit of effort up
front in making clear the strategy for exception handling and specifying the
exceptions that can be raised by a class\method will provide an excellent method
for error handling.
In the case of ensuring exceptions are always handled, a top level handler for
GenericException will usually do the job, allowing you to write error
information out to logs, screen, etc, and then shut down gracefully.
The only issue I would raise with exceptions is that they are not propagated
outside an asynchronous task. If an exception is not handled within an
asynchronous, it will not propagate to the task that started that asynchronous
task. Forte provides return and exception events when starting asynchronous
tasks to cope with this, but it seems a shame to have one method of dealing with
errors (exceptions) for synchronous behaviour, and another (events) for
asynchronous behaviour.
Steve Elvin
Systems Developer
Frontline Ltd.
UK
Mark,
The problem with return codes is that there is an underlying assumption
that the receiver will always catch and interpret that error code. This
may or may not be good thing, depending on how you architect your
application. If, on the other hand, you want to ensure that an error is
always handled, if not by the receiver then by the Forte, Exceptions are
the way to go. To extend this mechanism further, I would subclass
GenericException and created my own error code attribute on that
subclass. That way the receiver has the choice of interpreting the
exception based on that error code, and wrapping it in a
MessageDialog/window or do the usual 'errormgr.showerrors()'.
Exceptions seem a more flexible approach to me. That is, if you can live
with the fact that by using it, you're violating the 'exceptions for
behavioral anomalies' software engineering principle !
Best wishes.
Eric Pereira
Forte Consultant
----Original Message Follows----
From: "Kallambella, Ajith" <[email protected]>
To: "'Mark Sundsten'" <[email protected]>, [email protected]
Cc: [email protected]
Subject: RE: Raising Exceptions Vs returning error codes
Date: Wed, 30 Dec 1998 08:52:39 -0500
Reply-To: "Kallambella, Ajith" <[email protected]>
Mark,
Identifying conditions where you would rather use an exception
to an error_code ( and vice-versa ) normally depends on
your application design. Usually exceptions
are used to handle behavioral anomalies which are
not expected during the normal course of execution of
the program, and which would affect the continuity of
your algorithm if ignored. Examples would be a fatal
error, a semantically invalid( but syntactically-valid
token ) etc.
Error_codes and return status's can be used to handle
anticipated and recoverable errors. Example would
be presentation layer validations. In any normal
UI system, the user is expected to make errors and it
would be annoying to throw an exception( and to handle
it ), every time user enters wrong data. A well
modeled client layer should not only handle
data-validation errors , but should be smart enough
to encourage users to input correct or
"near-correct" data. Examples could be
making use of look-up windows etc. Interestingly,
Express uses exceptions to handle data-validations.
As you see, exceptions fit well into your processing
logic where severity of damage caused by an error
is more. Where as error_codes fit well into presentation
logic( and some not-so-critical processing logic ) where
errors are usually recoverable and normal path of
execution can be easily restored.
Hope this helps. I would be very interested to hear
what others have to say.
Ajith Kallambella. M
Forte Systems Engineer,
International Business Corporation.
-----Original Message-----
From: Mark Sundsten [mailto:[email protected]]
Sent: Tuesday, December 29, 1998 2:10 PM
To: [email protected]
Cc: [email protected]
Subject: Raising Exceptions vs returning error codes
When dealing with error handling, I find myself struggling with the
choice
of
raising exceptions (and handling them) from the caller
vs returning an error code of somekind.
When would you want to use one over the other?
Should you always use exception handling?
Any discussion would be appreciated.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Error when testing a webservice - Exception raised in class CL_SOAP_REGIST

Dear coleagues,
I've got an issue concerning the AS ABAP SOAP Runtime. The system is an ERP 6.0 with SP13.
If I try to test the service in WSADMIN by using the test-button, I just get an exception after the internet browser opens:
A Soap Core Exception was raised in Method CL_SOAP_REGISTRY::generate_wsdl(6)
Technical Details of Soap Core Exception
Message Text: SRT: ASSERT failed: object reference not bound
Class: CL_SOAP_REGISTRY
Method: generate_wsdl
LocationID: 6
Program: CL_SOAP_REGISTRY==============CP
Include: CL_SOAP_REGISTRY==============CM00J
Line: 59
I did a look into the coding and think that the exception is raised since the methode
Hi folks,
I've got an issue concerning the AS ABAP SOAP Runtime. The system is an ERP 6.0 with SP13.
At first I create a Web Service by using the context menue of an existing rfc-enabled function module. Afterwards the service is visible in SICF. If I try to test the service in WSADMIN by using the test-button I only get an exception in the opening internet browser:
Cannot download WSDL from http://serverurl:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1: Invalid Response Code: (400) Bad Request. The requested URL was:"http://ciswi.sap.swm.de:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1"
If I go onto the used url I get the following message:
Your request could not be processed
SRT: ASSERT failed: object reference not bound
What has happened?
A Soap Core Exception was raised in Method CL_SOAP_REGISTRY::generate_wsdl(6)
Technical Details of Soap Core Exception
Message Text: SRT: ASSERT failed: object reference not bound
Class: CL_SOAP_REGISTRY
Method: generate_wsdl
LocationID: 6
Program: CL_SOAP_REGISTRY==============CP
Include: CL_SOAP_REGISTRY==============CM00J
Line: 59
I did a look into the coding and found out that the exception is raised since
Hi folks,
I've got an issue concerning the AS ABAP SOAP Runtime. The system is an ERP 6.0 with SP13.
At first I create a Web Service by using the context menue of an existing rfc-enabled function module. Afterwards the service is visible in SICF. If I try to test the service in WSADMIN by using the test-button I only get an exception in the opening internet browser:
Cannot download WSDL from http://serverurl:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1: Invalid Response Code: (400) Bad Request. The requested URL was:"http://ciswi.sap.swm.de:8027/sap/bc/srt/rfc/sap/ZSTMA_FUNKTIONSTEST2?sap-client=100&wsdl=1.1"
If I go onto the used url I get the following message:
Your request could not be processed
SRT: ASSERT failed: object reference not bound
What has happened?
A Soap Core Exception was raised in Method CL_SOAP_REGISTRY::generate_wsdl(6)
Technical Details of Soap Core Exception
Message Text: SRT: ASSERT failed: object reference not bound
Class: CL_SOAP_REGISTRY
Method: generate_wsdl
LocationID: 6
Program: CL_SOAP_REGISTRY==============CP
Include: CL_SOAP_REGISTRY==============CM00J
Line: 59
I found out that the exception is raised since CL_SRT_WSDL_GEN_FACTORY=>GET_WSDL_GENERATOR doesn't return an instance of the class referring to the interface IF_SRT_WSDL_GEN.
If I test that method in SE24 using the name of the service definition in SE80 for the parameter WSD, the value '1' fpr the parameters TYPE and STYLE, an instance of the class CL_SRT_WSDL11_GEN is rendered.
Could you give any hints how I could debug that issue to verify the import parameters when the static method CL_SRT_WSDL_GEN_FACTORY=>GET_WSDL_GENERATOR is called in the body of the browser call ?
Or any other hints?
Thank you very much and best regards
Stefan

The issue was due to missing authorizations of the RFC-user (type 'Communication') calling the webservice. The RFC-user itsself has been assigned before to the webservice in the http-service tree (transaction SICF). RFC-User needs (at least) the role SAP_BC_WEBSERVICE.

Exception condition "INTERNAL_ERROR" raised

Runtime Errors         RAISE_EXCEPTION
Date and Time          21.08.2014 21:53:43
What happened?
     The current ABAP/4 program encountered an unexpected
     situation.
What can you do?
     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.
Error analysis
     A RAISE statement in the program "SAPLCEI0" raised the exception
     condition "INTERNAL_ERROR".
     Since the exception was not intercepted by a superior
     program, processing was terminated.
     Short description of exception condition:
     For detailed documentation of the exception condition, use
     Transaction SE37 (Function Library). You can take the called
     function module from the display of active calls.
How to correct the error
    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:
    "RAISE_EXCEPTION" " "
    "SAPLCEI0" or "LCEI0U30"
    "VC_I_GET_CONFIGURATION"
    or
    "SAPLCEI0" "INTERNAL_ERROR"
    or
    "SAPMSSY1 " "INTERNAL_ERROR"
    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.
System environment
    SAP-Release 700
    Application server... "sap01717"
    Network address...... "10.61.89.105"
    Operating system..... "Linux"
    Release.............. "2.6.40-0.8-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 15
    Shortdump setting.... "full"
    Database server... "sap01716"
    Database type..... "ORACLE"
    Database name..... "QWT"
    Database user ID.. "SAPDAT"
    Terminal................. "10.61.31.114"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Mar 17 2013 18:46:25"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr121116"
    Database version. "OCI_102, 11.2.0.3.0, V1, default"
    Patch level. 420
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 16759232
    Heap.... 0
    Page.... 16384
    MM Used. 14978448
    MM Free. 1777544
User and Transaction
    Client.............. 500
    User................ "RFC_TAULIA"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "53F6515E320E5BBBE10000000A3D5969"
    Program............. "SAPLCEI0"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "########"
    Database Release.... 720
    Kernel Release...... 720
    Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. "###"
    User................ "############"
    Transaction......... " "
    Call Program........."SAPJCo30"
    Function Module..... "/TAULIA/CT_RFC_BUS_DOC_GET"
    Call Destination.... "SAPR3"
    Source Server....... "SWDETDOLPHPODD"
    Source IP Address... "10.61.31.114"
    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.
Information on where terminated
    Termination occurred in the ABAP program "SAPLCEI0" - in
     "VC_I_GET_CONFIGURATION".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 259
    of the (Include) program "LCEI0U30".

Hi Arun,
the exception INTERNAL_ERROR of function module VC_I_GET_CONFIGURATION hasn't been caught, which leads to a short dump.
Check, where INTERNAL_ERROR is raised in your system In our system the only remaining code is after call of function module CUCQ_GET_CONFIGURATION_PARAMS.
Please try to debug, why this exception is raised.
Regards,
Klaus

Exception x_error raised in a FM :SO_NEW_DOCUMENT_ATT_SEND_API1

Similar Messages

Maybe you are looking for