Handling HL7 messages in SAP EP

Hi all,
In our requirement we have to communicate from EP to external system, which follows HL7 standards.
We found two alternatives these are as follows:
1.HL7 Iway adapter
2.SAP conversion agent.
Is it possible to make our own adapter to convert hl7 to xml?
If yes,
What will be the required resources for that?
Can we handle this approach (without SAP XI) with help java/j2ee?
Please provide required information (any pdf, conversion tools, and sample code) and also guide us how to handle this scenario. Your help will be great for us.
Thanx in advance.
Prashant Krishen &
Deviprasad.

Hello,
Before I answer your question, I want to give you our (SAP) understanding of an HL7 adapter.
An HL7 adapter shall provide the communication among healthcare applications based on healthcare HL7 standard, this means 1) HL7 message conversion e.g. HL7 message v.2.x format to HL7-XML, and 2) all the required protocols to transport the HL7 messages, e.g. MLLP, TCP/IP.
The following information which I can give you is based on SAP knowledge on the Netweaver Process Integration (PI/XI) technology.
So, generally you can do your own HL7 conversion tool. The required resource would be:
1: Person who has HL7 message structure, you may get available HL7-XML from www.hl7.org,
2: HL7 transport knowledge which could be learned from www.hl7.org,
3: Java, J2EE
All these 3 are required even you don't use SAP PI/XI.
I can provide you detailed information based on SAP technology and the one from SAP partner. Here are the link:http://service.sap.com/netweaver
On the left side from there please go to SAP NetWeaver>SAP NetWeaver in Detail>Process Integration>SAP Exchange Infrastructure>SAP XI in Detail>connectivity>Conncetivity SAP Netweaver 7.0 (2004s)/SAP NetWeaver 2004-->
You will then find details about SAP HL7 options e.g. from iWAY, SAP Conversion Agent powered by Informatica.
Again, all these are SAP and Partner's technology are on SAP Netweaver PI.
If you want one without PI, you may also use these 2 options.
I hope this could help you a little bit.
Best regards
Jing

Similar Messages

HL7 message to SAP system

Hi all,
What are different ways to send HL7 message to SAP system. I am thinking about conversion agent, java proxies, iway adapter. Please help me what are the different advantages and disadvantages and any other techniques.
Your help is reward able.
Thanks
Deviprasad Pothireddi.

Hi,
Its better u use Conversion Agent,i have done some POC on Conversion Agent,in that HL7 format can be selected it will come with the software defaultly, u can easly convert the HL7 data into XML format.
Regards,
phani
Reward points if Helpful

Sending HL7 Message from ISH system to External System

Hello Friends,
I am trying do configure our SAP ISH system to send HL7 messages to External 3rd party system. I did my research on SAP HCM module.
I am trying to send HL7 message using SAP XI system. Any help on what version of XI is required and SAP ISH is required would be great help to me. If there is any help document on setup required would also be great help to me.
Thanks for the help.

Hello Vasu
What is the format of message your 3rd part system request and on what protocol?
To my knowledge the Healthcare applications and laboratory information systems require HL7 message format over MLLP protocol.
If this is your requirement then you should use SAP PI 7.1 EHP or PI 7.3 and request to SAP for IAH Adapter. To know more about IAH and its usage in healthcare integration please refer to my blog at http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a00aabd6-a7f8-2d10-1c9e-bdaf085ab075.
Good Luck
Vj

Handling faulty messages in PI 7.0

Hi Gurus,
my interface is 3rd party app->PI->SAP.
i used proxy on sender side and on receiver side I used HTTP adapter.
Each time my PI will ping that application using the URL and get the batch xml file but if there is no data in the 3rd party application,how should i handle the faulty message.
the message if it fails to retreive the new bach,which is coming from the application is not in the xml format how can i handle the message
Thanks,
Jay

Your sender is abap proxy and receiver is HTTP and the mode is synchronous.
>what should i do with this message.do i need to use the fault message type to hold this message but I need not send this to >anyone or..Can I configure alerts so that PI users will understand
Yes you can pass the fault mesg from reciever(third party) to sender (proxy). That woud be helpful.
If the receiver (third party) is sending fault message as response then create fault message on the sender side and map the response of third party to sender side (proxy) proxy message. So that proxy will interpret that message as fault message.
Basically you will have request, response and fault messages for both sender interface (proxy ) and reciver interface (third party http). As you know, Fault messages are useful to provide meaningful application errors.
Refer this [link|http://help.sap.com/saphelp_nwpi711/helpdata/en/48/5946db5f693912e10000000a42189b/content.htm] for constructing fault message structure.

Handling Fault Messages

Hi,
I have this synchronous scenario : RFC > (XI without Integration Process) > SOAP.
Imagine that there is a problem with SOAP System and i get (don't worry about the error itself):
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:
invalid content type for SOAP:
TEXT/PLAIN; HTTP 400 Bad Request</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried to add ExchangeFaultData into SOAP Interface, and mapping it but it didn't work.
Can i get this exception mapped into RFC exception?

The usage of your fault message is not correct, since it is designed to handle application error, in your case, it is technical error, it should be handled by alert framework.
Liang
===========SAP Definition================
Fault message types are designed for application-specific errors that occur on the inbound side and that are reported back to the sender or persisted in monitoring.
u2022 In the synchronous case, when an application-specific error occurs on the inbound side, instead of sending a response message back to the sender, the application can send a fault message to handle the error.
u2022 The fault message of the application for an asynchronous ABAP server proxy is persisted for monitoring. In the case asynchronous of Java server proxies, the fault message is part of a negative application acknowledgement (see Acknowledgments).
Application-specific means that the application on the inbound side triggers the error itself because, for example, the request message did not contain sufficient information.
========= End of SAP Definition================

Exception Handling in Message Mapping and Alert

Hello,
1. Pls let me know the concept of Exception Handling and Alerts.
2. Pls provide some blogs for Exception Handling in Message Mapping.
3.What are Alerts and how it help us in XI. Pls provide some blogs for Alert
4.How are Alerts and Exception Handling can be related say for some scenario
Regards

Hi,
Plz check out these blogs of Sravya on Error Handling:
/people/sravya.talanki2/blog/2006/11/22/error-handling-framework-xiout-of-the-box-episode-1
/people/sravya.talanki2/blog/2006/11/23/error-handling-framework-xiout-of-the-box-episode-2
Also check this SAP Presentation:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9418d690-0201-0010-85bb-e9b2c1af895b
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
Error Handling :
http://help.sap.com/saphelp_nw04/helpdata/en/56/b46c3c8bb3d73ee10000000a114084/frameset.htm
Alerts:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
http://help.sap.com/saphelp_nw04/helpdata/en/56/d5b54020c6792ae10000000a155106/content.htm
BPM:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Working with acknowledgements
regards

Handling large messages with MQ JMS sender adapter

Hi.
Im having trouble handling large messages with a MQ JMS sender adapter.
The messages are around 35-40MB.
Are there any settings I can ajust to make the communication channel work?
Error message is:
A channel error occurred. The detailed error (if any) : JMS error:MQJMS2002: failed to get message from MQ queue, Linked error:MQJE001: Completion Code 2, Reason 2010, Error Code:MQJMS2002
The communication channel works fine with small messages!
Im on SAP PI 7.11, MQ Driver is version 6.
Best Regards...
Peter

The problem solved itself, when the MQ server crashed and restarted.
I did find a note that might could have been useful:
Note 1258335 - Tuning the JMS service for large messages or many consumers
A relevant post as well: http://forums.sdn.sap.com/thread.jspa?threadID=1550399

Axis adapter receiver handle fault message

Hi
We have a Sync interface which makes a Proxy call from ECC to PI 7.3 and then PI makes Soap(Axis) Sync call to Web sevice. We are having issues when handling SOAP 1.2 fault message.
Below is the actual fault response from Webserver:
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Header/>
   <env:Body>
      <env:Fault>
         <env:Code>
            <env:Value>env:Receiver</env:Value>
         </env:Code>
         <env:Reason>
            <env:Text xml:lang="en">FaultMsg</env:Text>
         </env:Reason>
         <env:Detail>
            <ns2:servicefault xmlns:ns2="https://hostname.de/webservice/0400-0005">
            </ns2:servicefault>
         </env:Detail>
      </env:Fault>
   </env:Body>
</env:Envelope>
But PI receives this response like system error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: FaultMsg</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checked this way http://scn.sap.com/thread/1675917 but it doesn't fit for Axis adapter.
Please let me for any clues how to handle this fault response.
Regards, Dzmitry

Hi,
I'm working with Dzmitry on the issue since last week. After analyzing the implementation and checking some SAP notes I came to the following conclusion:
According to note 856597 the fault behavior of axis adapter is as follows:
" A: The receiver adapter expects a SOAP message as response. For
synchrnous calls, a successful response should be returned with
HTTP 200. In this case, the content of the SOAP body will be
returned to the caller as the response payload. When some error
occurs, the SOAP message may contain the SOAP fault element. In
this case, when the fault detail element is not empty, its
content will be returned as the fault payload in an application
error message. For others, a system error message will be
returned to the caller."
The example shows a SOAP 1.1 fault message with a "detail" node being mapped to an application fault.
As we are using SOAP 1.2 the namespace as well as structure of the fault defers. I assume that the module responsible for the transformation from AXIS message to XI message within the module chain does not recognize the detail node on out soap 1.2 fault.
Therefore the solution would be to insert a custom AXIS handler before com.sap.aii.axis.xi.XI30OutboundHandle mapping the soap 1.2 fault to a soap 1.1 fault.
Is there something like a short how to on how to implement Axis handler and how to deploy it. Sap help only says to package it into sda file....
Thanks a lot in advance!!!
BR,
Eugen

Handling inbound messages

Hi,
We would like to handle incoming messages. The problem appears when we send an e-mail to SAP system. I can see some of SMTP transaction traces in log file, but some of them are not. Also, I cannot see any e-mail notification in SOIN transaction. I applied all the steps respectfully, indicated in OSS note# 455140, but couldn't help us. Please find the handler table, below;
E-posta * * ZCL_MAIL_INBOUND_SYS_CHECK 1
E-posta * ICS CL_APPOINTMENT_REPLY 3
Can anyone give a suggestion about it? Why I cannot see incoming e-mails on SOIN?
Thank you
Orkun Gedik

I found the solution. Just need a patch.
Best regards,
Orkun Gedik

Is JMS adapter can handle text message ?

Hi all,
In my scenario we have to take the data from Mainframe, CIS the data will come may in the form of text. If the data comes with text format ,is our JMS (DB2 drivers) can handle the messages in queue if yes is there any explicit configuration need to done. Till now we did message processsing of xml files but if the queue contains text message how to handle if it is not possible what procedure need to do any adpater module we have to write explicitly can some body explain?

Hi,
Refer these links
http://static.springframework.org/spring/docs/2.5.x/reference/jms.html
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
http://help.sap.com/bp_bpmv130/Documentation/Planning/XIUnicodeGuide030411.pdf
http://help.sap.com/saphelp_nw04s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a05b2347-01e7-2910-ceac-c45577e574e0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/482aae19-0301-0010-3485-8efd618818d0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/604e2b64-e689-2910-64b3-ffd650f83756
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00982670-748c-2a10-3985-cdd42fb43e50
and also blogs
Triggering XI Alerts from a User Defined Function
How to send any data (even binary) through XI, without using the Integration Repository
Regards,
Surya

Event Handling for messages

I would like to know how to handle events for messages i maintained in zmesg01.
messages are follow:    when gv_spfli is initial
                             "No such flight available.
                            when gv_scarr is initial.
                              "Flight name not available          with help of raise event ?
pls suggest.
*       CLASS lcl_mytestclass DEFINITION
class lcl_mytestclass definition.
public section.
   data: gt_spfli type table of spfli initial size 20,
           gt_scarr type table of scarr initial size 20.
   methods: get_data.
   events: data_not_found.
endclass.                    "lcl_mytestclass DEFINITION
*       CLASS lcl_mytestclass IMPLEMENTATION
class lcl_mytestclass implementation.
method: get_data.
   select * from spfli into table gt_spfli.
   if ( sy-subrc <> 0 ).
     raise event data_not_found.
     endif.
select * from scarr into gt_scarr
for all entries in gt_flight where carrname = gt_spfli-carrname.
if sy-subrc <> 0.
" How to call event for flight_name_not_found ?"
raise event flight_name_not_found.
endmethod.                    "get_data
endclass.                    "lcl_mytestclass IMPLEMENTATION
*       CLASS handler DEFINITION
class handler definition.
public section.
   methods handle_event
           for event data_not_found of lcl_mytestclass.
endclass.                    "handler DEFINITION
*       CLASS handler IMPLEMENTATION
class handler implementation.
method handle_event.
   write: / 'Data not found'.
endmethod.                    "handle_excess
endclass.                    "handler IMPLEMENTATION
data: oref type ref to lcl_mytestclass,
     h1   type ref to handler.
start-of-selection.
create object: oref, h1.
set handler h1->handle_event for all instances.
call method oref->get_data.
Thanks in advance.
Anee.

Hello Anee
Events are not used for this kind of message handling.
If you want to collect all messages then use a message handler (see sample report ZUS_SDN_ABAP_OO_MSG_HANDLING ).
Alternatively, you may define an exception class and raise a class-based exception which contains the detailed error message.
The following sample report is based on the more elaborate Wiki posting
[Message Handling - Finding the Needle in the Haystack|https://wiki.sdn.sap.com/wiki/display/profile/2007/07/09/MessageHandling-FindingtheNeedleintheHaystack]
*& Report ZUS_SDN_ABAP_OO_MSG_HANDLING
*& Thread: Event Handling for messages
*& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1052131"></a>
REPORT zus_sdn_abap_oo_msg_handling.
TYPE-POOLS: abap.
*       CLASS lcl_mytestclass DEFINITION
CLASS lcl_mytestclass DEFINITION.
PUBLIC SECTION.
    DATA: gt_spfli TYPE TABLE OF spfli INITIAL SIZE 20,
            gt_scarr TYPE TABLE OF scarr INITIAL SIZE 20.
    METHODS: constructor.
    METHODS: get_data
                   IMPORTING
                 value(id_carrid) TYPE s_carr_id.
    METHODS: has_messages
               RETURNING value(rd_result) TYPE abap_bool.
    METHODS: display_messages.
    EVENTS: data_not_found.
PROTECTED SECTION.
    DATA: mo_msglist    TYPE REF TO if_reca_message_list.
ENDCLASS.                    "lcl_mytestclass DEFINITION
*       CLASS lcl_mytestclass IMPLEMENTATION
CLASS lcl_mytestclass IMPLEMENTATION.
METHOD constructor.
    me->mo_msglist = cf_reca_message_list=>create( ).
ENDMETHOD.                    "constructor
METHOD has_messages.
    IF ( me->mo_msglist->is_empty( ) = abap_false ).
      rd_result = abap_true.
    ENDIF.
ENDMETHOD.                    "has_messages
METHOD display_messages.
* define local data
    DATA:
      ld_handle           TYPE balloghndl,
      lt_log_handles      TYPE bal_t_logh,
      ls_profile          TYPE bal_s_prof.
    " Get log handle of collected message list
    ld_handle = me->mo_msglist->get_handle( ).
    APPEND ld_handle TO lt_log_handles.
*   get a display profile which describes how to display messages
    CALL FUNCTION 'BAL_DSP_PROFILE_DETLEVEL_GET'
      IMPORTING
        e_s_display_profile = ls_profile. " tree & ALV List
*   set report to allow saving of variants
    ls_profile-disvariant-report = sy-repid.
*     when you use also other ALV lists in your report,
*     please specify a handle to distinguish between the display
*     variants of these different lists, e.g:
    ls_profile-disvariant-handle = 'LOG'.
    CALL FUNCTION 'BAL_DSP_LOG_DISPLAY'
      EXPORTING
        i_s_display_profile          = ls_profile
        i_t_log_handle               = lt_log_handles
*       I_T_MSG_HANDLE               =
*       I_S_LOG_FILTER               =
*       I_S_MSG_FILTER               =
*       I_T_LOG_CONTEXT_FILTER       =
*       I_T_MSG_CONTEXT_FILTER       =
*       I_AMODAL                     = ' '
*     IMPORTING
*       E_S_EXIT_COMMAND             =
      EXCEPTIONS
        profile_inconsistent         = 1
        internal_error               = 2
        no_data_available            = 3
        no_authority                 = 4
        OTHERS                       = 5.
    IF sy-subrc <> 0.
*   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
ENDMETHOD.                    "display_messages
METHOD: get_data.
    SELECT * FROM spfli INTO TABLE gt_spfli
      WHERE ( carrid = id_carrid ).
    IF ( sy-subrc NE 0 ).
**      RAISE EVENT data_not_found.
      IF 1 = 2. MESSAGE e154(bc_datamodel_service). ENDIF.
*   Flight not found (table SFLIGHT)
      CALL METHOD me->mo_msglist->add
        EXPORTING
*          is_message   =
          id_msgty     = 'E'
          id_msgid     = 'BC_DATAMODEL_SERVICE'
          id_msgno     = '154'
*          id_msgv1     =
*          id_msgv2     =
*          id_msgv3     =
*          id_msgv4     =
          id_detlevel = '1'
*        IMPORTING
*          es_message   =
    ENDIF.
    IF ( gt_spfli IS INITIAL ).
    ELSE.
      SELECT * FROM scarr INTO TABLE gt_scarr
      FOR ALL ENTRIES IN gt_spfli
        WHERE carrid = gt_spfli-carrid.
    ENDIF.
    IF ( gt_scarr is initial ).
      " How to call event for flight_name_not_found ?"
**        RAISE EVENT flight_name_not_found.
      IF 1 = 2. MESSAGE e159(bc_datamodel_service) WITH '&all'. ENDIF.
*   Airline & not found
      CALL METHOD me->mo_msglist->add
EXPORTING
*          is_message   =
    id_msgty     = 'E'
    id_msgid     = 'BC_DATAMODEL_SERVICE'
    id_msgno     = '159'
    id_msgv1     = '&all'
*          id_msgv2     =
*          id_msgv3     =
*          id_msgv4     =
    id_detlevel = '2'
*        IMPORTING
*          es_message   =
    ENDIF.
ENDMETHOD.                    "get_data
ENDCLASS.                    "lcl_mytestclass IMPLEMENTATION
*       CLASS handler DEFINITION
CLASS handler DEFINITION.
PUBLIC SECTION.
    METHODS handle_event
            FOR EVENT data_not_found OF lcl_mytestclass.
ENDCLASS.                    "handler DEFINITION
*       CLASS handler IMPLEMENTATION
CLASS handler IMPLEMENTATION.
METHOD handle_event.
    WRITE: / 'Data not found'.
ENDMETHOD.                    "handle_excess
ENDCLASS.                    "handler IMPLEMENTATION
DATA: oref TYPE REF TO lcl_mytestclass,
     h1   TYPE REF TO handler.
PARAMETER:
p_carrid    TYPE s_carr_id DEFAULT 'AA'.
START-OF-SELECTION.
START-OF-SELECTION.
CREATE OBJECT: oref, h1.
** SET HANDLER h1->handle_event FOR ALL INSTANCES.
CALL METHOD oref->get_data( p_carrid ).
IF ( oref->has_messages( ) = abap_true ).
    oref->display_messages( ).
ENDIF.
END-OF-SELECTION.
Regards
Uwe

How to log in to Service Desk to create sample message to SAP?

Dear all,
How to log in to Service Desk under my Solution Manager server to create sample message to SAP under Component: SV-SMG-SUP?
Regards
GN

Hi GN,
You have different options to create messages in test component SV-SMG-SUP-TST:
1. if you are on 7.1 you can create message using CRM_UI
2. If you are using lower vrsion then either you can create message using Workcenter or using transaction NOTIF_CREATE or using menu --> Help --> Create support message.
Thanks
Regards,
Vikram

SR Log Error - | Message : com.sap.esi.uddi.sr.api.exceptions.SRException

Hi,
We are getting below errors in /nwa/logs. We have our PI (7.11) and Service Registry configured on the same server. And have out CE (7.2) system connected to this service registry. Does any one has similar experience? Please let me know if you have any solution for the same.
SR Log Error
| 11-Nov-11 14:10:45.568
| Method   : getClassificationSystems()
| Class    : com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean
| ThreadID : 146
| Message : com.sap.esi.uddi.sr.api.exceptions.SRException: No classification system found for ID 'QName: Namespace= http://uddi.sap.com/classification; Name= ConfigurationFlags'
|
|       com.sap.esi.uddi.sr.impl.common.Utility.cs2srException(Utility.java:122)
|       com.sap.esi.uddi.sr.impl.ejb.ServicesRegistryBean.getClassificationSystems(ServicesRegistryBean.java:242)
|       sun.reflect.GeneratedMethodAccessor1325.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
|       $Proxy1087.getClassificationSystems(Unknown Source)
|       com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean.getClassificationSystems(ServicesRegistrySiImplBean.java:456)
|       sun.reflect.GeneratedMethodAccessor1324.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:512)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:486)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:256)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
|       SoapServlet.doPost(SoapServlet.java:51)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
|       com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:245)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
|       com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
|       com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
|       com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
|

Hi,
Refer Error:Service Registyr Configuration PI 7.11
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8071b1b8-3c5c-2e10-e7af-8cadbc49d711?QuickLink=index&overridelayout=true
Thanks,
Chandra

Service Desk: error while sending message to SAP

Hello Gurus,
I have configured Service Desk in Solution Manager. When i create a message in one of my Satellite Systems the message appears in Solman but when i try ro send the message to SAP i get the following error.
"You do not have authorization to Send or Compare a notification"
The user has SAP_ALL and NEW and the same has been maintained in AISUSER table. After i get the error i executed SU53 but there are no missing authorization.
Can someone please tell me what the problem could be?
Regards
Anil Verma B

Hi,
Apart from the SAPOSS, SAP-OSS, SAP-OSS-LIST-01 rfcs, pls ensure the basic authorizations for solman has been verified and given.
SAP_SUPPDESK_ADMIN
SAP_SUPPDESK_CREATE
SAP_SV_FDB_NOTIF_BC_ADMIN
Please also verify if you had the BADI settings done correctly as per note
1140822 SAP customer number for installation number &1 unkn
Hope this helps.
Cheers
Sh

Message on SAP login screen

Hi all,
How to add a system message on the SAP logon screen.
I just want to put display some content and links on screen where we enter client and username and password.
regards,
helpful answers are surely rewarded.

Hi,
Personalization of your SAP system logon screen, splash screen etc
1) Adding text to the SAP logon screen. This is very handy for identifying which SAP system the user is about to log onto, especially non production boxes. You can also warn them here of pending changes, updates or outages. Because it is up while they are typing in their userid and password, they can't claim they missed the system message. SAP icons like the stop sign and warning signs can also be displayed. Details can be found in OSS note #205487. Here are the guts:
Go to Transaction SE61 and select the document 'General text' (selection via F4 help), and create a text with the name ZLOGIN_SCREEN_INFO in the language defined with profile parameter zcsa/system_language.
If the text does not exist in the system language, no output is made.
Note that there is space for 16 lines with 45 fixed-font characters each or for approximately 60 proportional space font characters on the logon screen.
Title lines (can be recognized by means of format keys starting with a 'U') are highlighted in the display.
You may also output icons at the beginning of lines by using an icon code (for example, @1D@ for the STOP icon). You can get a list of icon codes from Report RSTXICON. Pay attention to the codes with two '@' symbols displayed by the report. You cannot include text symbols. The 'include indicator' cannot be used for this function. SUBHINT here. These can be used on system messages as well.
Creating/changing this text requires a changeable system. Therefore, for production systems, SAP recommends maintaining the text in the upstream system and then transporting it. To do this, select a transportable (customer) development class when you create the text and save the active version prior to the export. The transport is done via the transport object R3TR DOCT ZLOGIN_SCREEN_INFO The text can be changed in the original system only (see TADIR entry R3TR DOCT ZLOGIN_SCREEN_INFO). When making a change in a non-original system, a modified text would be generated which cannot be represented sensefully on the initial screen.
2) Changing the splash screen on the main menu can add some pizzazz to the otherwise boring screen. It can also be changed easily on a regular basis. For production systems a company logo and/or company mission statement might be appropriate. Here are the instructions:
First, in transaction SMW0 (SAP Web Repository), select "Binary data for WebRFC applications. The logo must be in a .gif format. From this transaction, create a new object, then choose to IMPORT. You must then specify the path to the .gif object you have saved, and select the option to TRANSFER.
Then, maintain table SSM_CUST via SM30. Change the field START_IMAGE to the name of the object you created in SMW0.
3) Changing the rippling water on the top right on all is easy but tedious and requires no change to the SAP system. The file name is 'sapalogo.bmp' and resided in the directory "SAPpcsapguithemesdefault". Looking at this file you can see how it works. Use an editor like Paint and replace each of the SAP ripple images with a morphing image of your own. Make sure the new image is the same size as the original. There are 33 images in the original but you don't need that many. One idea for a morphing image would be to take your company logo and have it build its way across the screen and then off again.
4) Changing the startup movie is even easier. Replace the file 'sapss.avi' with a short avi of your own. This file resides in the same directory as 'sapalogo.bmp
Pls reward points,
Regards,
Ameet

Handling HL7 messages in SAP EP

Similar Messages

Maybe you are looking for