I have <b>deleted</b> and <b>recreated</b> the ABAP-Proxy "CO_FLIGHT_SEAT_AVAILABILITY" for the Outbound-Interface "FlightSeatAvailabilityQuery_Out". Since then I can't execute the demo example. Everytime I call the application I get an error that there is an Syntax error in program CL_SXIDEMO_AGCY_BSP. What am I doing wrong?
Goto the Class Builder(SE24) and just check for error in the class CL_SXIDEMO_AGCY_BSP where u r getting and just try to solve it or else give me the details...
The message type SXIDAG_FSA_QUERY_MT has been not created, Check whether this is available in If not available once try Activating In IR and Refresh cache and then goto sproxy and check once again and if u can see just double click it and let me know what message u r getting...
<b>Have u Checked in tcode Sproxy --> SAP BASIS 6.40 --> http://sap.com/xi/XI/Demo/Agency --> Message Type -->FlightSeatAvailabilityQuery -->under this check SXIDAG_FSA_QUERY_MT is available or not...
I can't find a message type "SXIDAG_FSA_QUERY_MT" in the transaction "SPROXY" nor in the Integration Repository. There are only message types such as BookingOrderConfirmation, BookingOrderInformation, FlightSeatAvailabilityQuery, ...
How can I find/activate "SXIDAG_FSA_QUERY_MT" in the Integration Repository?
As u told that u can not find <b>SXIDAG_FSA_QUERY_MT</b>.
Also look for the associated data type, (it could be <b>SXIDAG_FSA_QUERY_DT</b>). Look for them in the <b>change list</b>, activate them if they are not activated. If they are not in the <b>change list</b>, I think u will have to create.
Please inform when the problem is solved. And close the thread.
thank you for your help so far. Unfortunately I can't find a message type <b>SXIDAG_FSA_QUERY_MT</b> nor a data type <b>SXIDAG_FSA_QUERY_DT</b> and I'm pretty sure that I have never had those types in my integration scenarios. I only deleted the generated ABAP-Proxy and not the corresponding message interface.
By the way, is there a chance to easily revoke the changes I made?
what do you mean with "messing up with 2 different contexts" and why are there 2 places for the message interface <b>FlightSeatAvailabilityQuery_Out</b> in the repository?
CO_SXIDAG_FSA_QUERY is the generated proxy class for MI <b>FlightSeatAvailabilityQuery_Out</b>. But I guess u have given some other class in ur previous messages.
That means, there is problem with some other MI which is associated with CL_SXIDEMO_AGCY_BSP, find MT, DT for this MI.
my generated proxy class for the MI <b>FlightSeatAvailabilityQuery_Out</b> is CO_FLIGHT_SEAT_AVAILABILITY_QU. Is this the reason for my problem? Does it help when I regenerate the proxy and try to call the class CO_SXIDAG_FSA_QUERY?
@Moorthy
Since I use Proxy-to-Proxy communication I don't understand why I have to configure a rfc-destination! And do really have to install the XI Add-On in each of these business systems?
<i>Since I use Proxy-to-Proxy communication I don't understand why I have to configure a rfc-destination! And do really have to install the XI Add-On in each of these business systems?</i>
All logical destinations(SM59 entry) refer to an actual physical destination...
I want to delete the generated proxy again in order to name the new class CO_SXIDAG_FSA_QUERY. I hope to solve the problem in this way.
When I choose delete in the context menu of the MI FlightSeatAvailabilityQuery_Out there is a popup suggesting two possibilities: Deleting this object only or deleting this object and referenced objects.
<i>my generated proxy class for the MI FlightSeatAvailabilityQuery_Out is CO_FLIGHT_SEAT_AVAILABILITY_QU. Is this the reason for my problem? Does it help when I regenerate the proxy and try to call the class CO_SXIDAG_FSA_QUERY?</i>
Marc,
Give it a shot.I think this should solve the problem.
In short, look for all the associated classes, MIs, MTs, DTs. Earlier we were mismatching one class to someother MIs and things like that.
Please have a look and let us know if that worked.
When I choose delete in the context menu of the MI
FlightSeatAvailabilityQuery_Out there is a popup
suggesting two possibilities: Deleting this object
only or deleting this object and referenced objects.
What shall I do?
Marc,
I think earlier also u might have had these 2 options and u might have selected the second option, resulting in deleting all the ref objects and that is the reason ur not able to find the MT.
to be honest, I don't know what to do next! Could you please answer some essential questions?
At what time are the proxies generated? Are they generated directly after the activation in the change list (Integration Builder)? If so, how can I achieve that the proxy objects (structures for MT, DT) are named correctly?
> Marc,
> I think earlier also u might have had these 2 options
> and u might have selected the second option,
> resulting in deleting all the ref objects and that is
> the reason ur not able to find the MT.
Why is this a problem? The needed ref objects should be created when I create a proxy, shouldn't they? And does it help when I rename the generated objects, in order to get names which fit to those which I need. If so, can you please send me the right names for the following objects
Class CO_SXIDAG_FSA_QUERY Proxy Class (generated)
Exception Class CX_FLIGHT_NOT_FOUND Flight not found (only for use in XI Demo)
Structure FLIGHT_SEAT_AVAILABILITY_QUER1 Flight seat availability query (only for use in XI Demo)
<i>At what time are the proxies generated? Are they generated directly after the activation in the change list (Integration Builder)? </i>
No, you need to go to SPROXY transaction in the SAP Application Systems,and need to find the SWCV->message Interface(inbound/outbound)->then right click and generate proxy ...
<i>
If so, how can I achieve that the proxy objects (structures for MT, DT) are named correctly?</i>
Whenever you change your message Interfaces (inturn Message Type and data type) , it is preferred to generate proxy once again.and activae once again..
Regenerating and Activating the proxy once again may solve your problems..
when I generate the proxy in the SPROXY transaction, "wrong" names are given to the message and data types. I get <b>FLIGHT_SEAT_AVAILABILITY_QUERY</b> instead of SXIDAG_FSA_QUERY_MT for example. And when I try to chance the names manually there is error messages which says that I'm not allowed to do this! Do I have to chance the type names in the implementing class on the "Airline"-Side?
> Can you tell from Which SWCV you are generating this
> proxy ? for which Message Interface you need to
> generate the proxy..
I generate the proxy for the Outbound-Interface <b>FlightSeatAvailabilityQuery_Out</b> of the SWCV <b>SAP BASIS 6.40</b>.
> <i>SXIDAG_FSA_QUERY_MT</i> is this message type is
> custom message type generated by you ??
Yes and no! When I generate the proxy for the above mentioned Message-Interface, several message types (e.g. <b>FLIGHT_SEAT_AVAILABILITY_QUER1</b>) and data types are created automatically. Since message types like <b>SXIDAG_FSA_QUERY_MT, SXIDAG_FSA_RESPONSE_MT ...</b> are used in the class <b>CL_SXIDEMO_AGCY_BSP</b> which is called when I execute the demo examples, I thought it would help to rename the message types as <b>SXIDAG_FSA_QUERY_MT, SXIDAG_FSA_RESPONSE_MT ...</b>. If I let the names as they are I get an error which says that a specific message type (in my case <b>SXIDAG_FSA_QUERY_MT</b>) is unknown!
By the way can I please ask you one question in order to understand the whole procedure. When I call the demo application one of the business server pages of the BSP application <b>SXIDEMO_AGCY_UI</b> is called and within this bsp a method of the application class <b>CL_SXIDEMO_AGCY_BSP</b> is called which sets up the connection to the proxy, right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.