Unable to parse the OData service in JSON
Hi,
Need to parse the OData Service in JSON format.Able to successfully get Service and MetaData documents. After that, when try to parse OData service returning response in JSON.
Below code is throwing exception.
Server Used:SMP3.0
ODATA SDK Used:SMP3.0 ODATA SDK
Service Used: http://services.odata.org/v2/Odata/Odata.svc/Products?$format=json
Code Snippet:
@try {
ODataCollection *collc = [[self.serviceDocument getSchema] getCollectionByName:_srvcInfo.serviceEntityName];
ODataEntitySchema *schema = [collc getEntitySchema];
//Instantiate parser for Carrier entity
ODataDataParser *dataParser=[[ODataDataParser alloc] initWithEntitySchema:schemaandServiceDocument:self.serviceDocument];
//Parses a feed or an entry xml or json
[dataParser parse:entriesData];
results = dataParser.entries;
@catch(NSException *e) {
NSLog(@"Exception:%@, %@", e.description, e.debugDescription);
Exception:
-[__NSCFArray objectForKey:]: unrecognized selector sent to instance
However Service Used:http://services.odata.org/V3/Northwind/Northwind.svc/Products?$format=json. Not
throwing any exception, but dataParser.entries is returning 0 objects
Please let us know, is the same API is used for parsing JSON.
What can be the reason of issue and what are possible resolution.
Thanks,
Parveen.
My expert area is not IOS but you can check this IOS Odata development tutorial that might help you,Getting started with SMP3 Native OData iOS apps
Midhun VP
Similar Messages
-
Hi I am unable to open some psd file that i created . I get this message "could not complete your request ,unable to parse the path data" I am curently using cs6. Any idea how to fix it. I tried opening on other computer with photoshop but no luck yet.
Is Vista a supported CS6 system????
Photoshop CS6 / Tech specs
System requirements
Windows
Intel® Pentium® 4 or AMD Athlon® 64 processor
Microsoft® Windows® XP with Service Pack 3 or Windows 7 with Service Pack 1. Adobe® Creative Suite® 5.5 and CS6 applications also support Windows 8. Refer to the CS6 FAQ for more information about Windows 8 support.*
1GB of RAM
1GB of available hard-disk space for installation; additional free space required during installation (cannot install on removable flash storage devices)
1024x768 display (1280x800 recommended) with 16-bit color and 256MB (512MB recommended) of VRAM
OpenGL 2.0–capable system
DVD-ROM drive
This software will not operate without activation. Broadband Internet connection and registration are required for software activation, validation of subscriptions, and access to online services.† Phone activation is not available. -
Calling the odata service from UI
Hi Everyone,
From the below document I have executed all operations of the odata service
Let’s code CRUDQ and Function Import operations in OData service!
But I want that from an UI I will provide the data which will create or update or get deleted. Is it possible? If yes, then How to do that and if No, then what is the use of this odata service which I created? How to create an odata service which can be called from a browser? For that RFCs and BAPIs are required?
Regards,
SoumyaHi Chandra,
Following I am giving the code where I got stuck. When I am pressing the create button the dialog is opening but during fetching and getting the request it is showing the alert of the 1st err function which I have made bold. But why the code is going there I am not able to uderstand.Please help.
Code:
OData.request
requestUri: "http://server:host/sap/opu/odata/sap/ZGW638785_EMPLOYEE_TEST_SRV/EmployeeCollection/",
method: "GET",
headers: {
"X-Requested-With": "XMLHttpRequest",
"Content-Type": "application/atom+xml",
"DataServiceVersion": "2.0",
"X-CSRF-Token":"Fetch" }
function (data, response)
alert("1st func "+mandt_var+" "+employeeID_var +" "+ address_var+" " + datejoining_var + " " + yearexp_var);
header_xcsrf_token = response.headers['X-CSRF-TOKEN'];
OData.request
requestUri: "http://server:host/sap/opu/odata/sap/ZGW638785_EMPLOYEE_TEST_SRV/",
method: "POST",
headers: {
"X-Requested-With": "XMLHttpRequest",
"Content-Type": "application/atom+xml",
"DataServiceVersion": "2.0",
"Accept": "application/atom+xml,application/atomsvc+xml,application/xml",
"X-CSRF-Token": header_xcsrf_token
data:
mandt: mandt_var,
employeeID:employeeID_var,
address:address_var,
dateOfJoining: datejoining_var,
yearOfExp: yearexp_var,
function (data, response)
alert("2nd Func "+mandt_var+" "+employeeID_var+" "+address_var+" "
+ datejoining_var+" "+yearexp_var);
document.location.reload(true);
$("<div>Returned data " + window.JSON.stringify(data) + "</div>").appendTo($("#MessageDiv"));
function (err)
alert("1st err func "+mandt_var+" "+employeeID_var+" "+address_var+" "
+ datejoining_var+" "+yearexp_var);
$("<div>Returned error " + window.JSON.stringify(err.response) + "</div>").appendTo($("#MessageDiv"));
function (err)
alert("2nd err func "+mandt_var+" "+employeeID_var+" "+address_var+" "
+ datejoining_var+" "+yearexp_var);
var request = err.request; // the request that was sent.
var response = err.response; // the response that was received.
alert("Error in Get -- Request "+request+" Response "+response); -
INSTALLED ITUNES AND THE ERROR-MAPI WAS UNABLE TO LOAD THE INFORMATION SERVICE APLZOD-OCCURS. WHAT DO I DO.
Is this on a Windows XP, Vista or 7 system?
-
Unable to convert the sender service to an ALE logical system
Hello,
file adapter > XI 3.0 > Idoc adapter > r/3 system
In sxmb_moni I receive "Unable to convert the sender service to an ALE logical system".
In we05 in r/3 system no Idocs are arrving. I have no problem with idoc > XI > idoc scenario to this same r/3 system (using same sld business system)
I read other topics on this error but it seems they all talk about an IDOC outbound interface.
What should I check?
Thanks
BoazI do have the same problem as Boaz Paz
When I try :
file adapter > XI 3.0 > Idoc adapter > r/3 system
> This is a B2B scenario where "AVTItalia" is the external party trying to send via its "AwayOrders" business service (a file pickup) an idoc to business system "UPG" (non party service)
I get an error while XI tries to call its IDoc Adapter:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>AwayOrders</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service AwayOrders to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
With the following trace logs :
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = AVTItalie</Trace>
<Trace level="1" type="T">Sender party normalized = AVTItalie</Trace>
I ve tried to (cf. /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc ):
1. add a logical system name "ACYAVTFBC1" in "Adapter specifier Id" of "AwayOrders"
In the runtime cache > services an entry appears for " ... Logical System | AVTItalia | ACYAVTFBC1...".
2. declare "AVTItalia" as a business partner in SLD with the logical system name
Plz help! -
File-idoc Unable to convert the sender service to an ALE logical syste
Hi experts
iam working on file-idoc scenario ,iam getting the below error in sxmb_moni and RWB
"Unable to convert the sender service to an ALE logical system"
i checked the partnetr profile, RFC(sm59) and IDX1 t codes.
the connection is ok. but still i could figureout the problem.
please suggest me
Thanks
vasaviHi,
Have u checked the logical system is added in the Sender Business service in the Integration Directory?
Open the Buiness Service/System --> EDIT-ADAPTER SPECIFIC IDENTIFIERS
then specify the logical system name.
Go throgh the following link
Troubleshooting File-to-IDOC Scenario in XI.
Regards
Sridhar Goli -
Hi All,
File to IDoc scenario.
1. Business system is correct because its working for other scenarios.
2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
3. Refreshed cache.
But still... its showing the below error.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BS_PARTNER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea what might be wrong?
Regards
Deepthi.Hi Experts,
Could you please help me to fix this.
SCENARIO: SAP - IDOC -
> XI -
> SOAP Adapter (Webservice)
Workaround:
1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
3. Identifier Tab in comm channel details: Its empty - no values.
SXMB_MONI :
Error Details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>CAPTOR3_PRU</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Sunil. -
Unable to convert the sender service PPG to an ALE logical system
Hello all,
maybe anybody can help or give me further information.
I have set up a scenario to send IDOC from a business system ( ERP ) to a business service ( EXT ).
Receiver is a linux system so I use the FTP-FILE adapter as communication channel.
The send-process is so far ok.
Here my tests:
1) exclude the specific IDOC in IDXNOALE table ( means no technical acknowledgment for this IDOC )
result :
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: not in use
b) message in RWB-Monitor: Sender ERP --> Receiver EXT ok
2) But I would like to have a system status..... here now the problem
add specific IDOC into IDXNOALE table ( for request acknowledgments )
result:
a) message in SXMB_MONI: status-flag: processed, acknowledgment-flag: acknowledgment not possible
--> error message: unable to convert the sender service EXT to an ALE logical system
b) message in RWB-Monitor: there are now two message,
first: Sender ERP --> Receiver EXT = ok
second: Sender EXT ---> Receiver ERP = system error
Receiver-Interface is : http/ww.ahlstrom.com/EXT/ MI_IN
3) furhter tests:
a) change FTP apdapter channel ( put some wrong settings )
message in SXMB_MONI: status-flag: processed, acknowledgment-flag: contains system errors
message in RWB-Monitor 3 messages ( one ok, and two error messages )
b) changed only the receiver communication channel to HTTP ( other extisting scenario )
then the acknowledgment works fine wihout errors.
I'm wondering, but here Receiver-Interface is: http://sap.com/xi/xI/Message/30/Acknowledgment
Summary: The process works, but strange:
message in SXMB_MONI: unable to convert the sender service EXT to an ALE logical system
message in RWB: system error
No problems with HTTP adapter
Regards,
Reinhard DoekerHi,
Addition to the above said by Udo...
for routing the ack back to the sender system you need to create communication channel of type idoc with name as Ack.....
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
Check the above link section 3.2
HTH
Rajesh -
Unable to convert the sender service ABC_Service to an ALE logical system
Hi,
I have a JMS (Party) --> PI --> IDOC scenario.
Party: ABC_Party
Service: ABC_Service
I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
I have already done the below settings:
1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
Have already seen:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
Thank you,
Pankaj.You need to create party if its a B2B scenario
Under Identifiers
under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
Please refer this for more details
http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
Re: Party Configuration
In case of cross company process it is required
Regards
Ninad
Edited by: Ninad Sane on Nov 18, 2010 11:17 AM -
I have a Nikon D600 and D800 and I shoot everything in Raw. I use Photoshop Elements 9 for processing but I have been unable to convert any RAW files to open in PSE. Says unable to parse the file. What does this mean and how do I fix it?
Since pse 9 can only use up to camera raw 6.5 and the d600 needs at least 7.3 and the d800 needs at least 6.7, you can use the
8.6 adobe dng converter to convert those files to dng copies, which then pse 9 should open.
8.6 dng converter
windows
Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.6
mac
Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Adobe DNG Converter 8.6
Note:
If you have windows xp or vista or mac os x 10.6, then you'll need to use the 8.3 dng converter instead
windows
Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.3
mac
Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Adobe DNG Converter 8.3
how to use the dng converter
Camera Raw: How to use Adobe DNG Converter - YouTube
more info on supported cameras and camera raw plugins required
Camera Raw plug-in | Supported cameras
Camera Raw-compatible Adobe applications -
I am running Photoshop CS6 on a Mac OS X 10.9.3 and every time I save a large eps I can not open it again. I get this message when I try. "Could not complete your request because Photoshop was unable to parse the PostScript."
Oh, dear.
If you use PSE as your external editor for iphoto, you need to save the images back to iphoto by using Save, not Save As and not changing anything like the name or format that would bring up the Save As window. (You may need to adjust the editor prefs>saving files>on first save to save over existing.)
OR you can export the photos from iphoto to the desktop, use file>open in the editor and then change whatever you want and either import the saved image to the organizer or import it back to iphoto as a new file. What you are doing is extremely risky, particularly to the iphoto library which you may easily damage by your workflow.
I would start the organizer holding down the shift key, then create a new catalog and switch to the new one. Then try opening the editor without opening an image and see if you get any farther.
PSE and iphoto are not designed to be used as you've been doing. You are trying to write to the iphoto library from outside iphoto, which is the fastest known way to corrupt the library and lose all your photos. -
Problem Unable to convert the sender service to an ALE logical system
Hi to All..
I'm facing a problem in one scenario File to Idoc .. I got this problem
"Unable to convert the sender service to an ALE logical system" in pipeline Call Adapter.
I check this blog but the problem persist . /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Also I have another scenario in other Software Component Version SCW and the Idoc works correctly..
I wonder if I miss something
this the trace
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
<Trace level="1" type="T">Sender service Sys_XXX</Trace>
<Trace level="1" type="T">Receiver service Sys_EDV_XXX</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Edited by: Luis Ortiz on Jan 25, 2010 3:37 PMHi,
in order to use only one logical system (PI's) in we20 in ECC and not as many as you have sender systems
Regards,
Michal Krawczyk -
Unable to convert the sender service to an ALE logical syst
Hi,
My scenario is IDOC to File.
SLD:Configured Correctly ,ABAP Business System.
Imported the same in ID,under Adapter specific Identifiers gava the Logical system as in WE20.
In the Receiver Agreement,Header mapping tried giving the sender service,Receiver service.
Still the Error "Unable to convert the sender service to an ALE logical syst" is seen in SMQ2.
The file is getting generated at receiver directory mentioned in the receive CC.
There is no error seen in SXMB_MONI.
Did any one had a problem as this.
Thanks,
SrinivasaHi,
You need to specify the Logical Name of Business System under Adapter specific identifiers for your Receiver Business System.
The specified item was not found.
Secondly you can use Header Mapping in Receiver Agreement. Or
If you are taking your control records from payload then tick the check box "Apply Control Records from Payload".
Regards, -
Unable to convert the sender service
Hi,
On my new system XI 7.0, I try to configurate a simple "File -> Idoc" scenario without BPM, but I have still a classical dump:
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:Stack>Unable to convert the sender service to an ALE logical system</SAP:Stack>
Note: My Business Service's (of ECC) doesn't appeared between "sender service" and "to an ALE".
Moreover, in my payload, my IDoc has an <u>EMPTY</u> EDI_DC40 segment. Is it normal ?
I have checked:
1) the Logical System name in the SLD
2) the port definition in WE20 compared to this one of CC
3) the RFC destination in SM59 compared to this one of CC
4) the Adapter specific identifier of my Business System
5) then played with sxi_cache...
I'm a few dissapointed... I beleived to have check everything. Maybe not!
MickaelHi Udo,
Here's the result:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>EDB7E1C839603FB9B04057583BE29980</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>BS__TESTXID_1</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>ECB_BS_MDT720</SAP:ToServiceName>
<SAP:ToInterfaceName>DEBMAS.DEBMAS06</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">ECB_BS_MDT720</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CCR_ECBMDT720_IDOC</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">B38BCD00E47111D7AFACDE420A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>interfaceVersion</SAP:Name>
<SAP:Value>3</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passControlSetValues</SAP:Name>
<SAP:Value>1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passReceiverValue</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passSenderValue</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>SAPECB</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>queueing</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>restoreOriginalParty</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>rfcDestination</SAP:Name>
<SAP:Value>ECBCLNT720</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>sapRelease</SAP:Name>
<SAP:Value>640</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>segmentVersion</SAP:Name>
<SAP:Value />
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
it seems it's ok: receiver, sender, port, rfc destination are found. But my EDI_DC40 is still empty
<?xml version="1.0" encoding="UTF-8" ?>
- <DEBMAS06>
- <IDOC BEGIN="">
- <EDI_DC40 SEGMENT="1">
<TABNAM />
<DIRECT />
<IDOCTYP />
<MESTYP />
<SNDPOR />
<SNDPRT />
<SNDPRN />
<RCVPOR />
<RCVPRN />
</EDI_DC40>
- <E1KNA1M SEGMENT="1">
<KUNNR>123777</KUNNR>
<NAME1>Adams</NAME1>
<NAME2>James</NAME2>
</E1KNA1M>
</IDOC>
Mickael -
JMS Adapter: Unable to parse the scema error in step 7
Hi
I get unable to parse the schema error in step 7 of JMS Adapter partner link definition (in Type Chooser window). I am using RosettaNet 3b2 Schema converted from DTD by Tibco tools.
Any help greatly appreciated.forwarded to the JMS adapter team. It would be nice if you could provide more context around the input you provided in the first 6 step (could you please post the schema or if there are a set of them, zip them up, rename the file .zap and email to collaxa_support_us at oracle.com). Thank you. -Edwin
Maybe you are looking for
-
Use of field 'StartPoint' in work order operation's 'Dates' tab
Hi, Can someone please explain me on the uase of field 'StartPoint' on work order operation's Dates tab. Regards.
-
Phone just stopped working...
The earpiece stopped working. I've never dropped it. It's been in my pocket all day...I used it this morning fine...then tonight it stopped working. People can hear me but I can't hear them unless I put it on speakerphone. I can't even hear the ringi
-
Adobe flash cs4 uninstall problems
I am unable to uninstall the adobe flash cs4 trial. i go to add/remove and it just don't load, nothing pops up or anything ! please help me, I need to uninstall it! D: im on windows xp
-
Firefox 3.6.12, Reader 9.4, (reinstalled). Firefox downloads a pdf file rather than opening it. Adobe Acrobat Document is not listed as an application (Tools>Options>Applications from FF menu). FF support page suggests opening profile, then File>Exit
-
Hi, I want to create about 600 new users to my portal site. How can I do it? I have read SSO, LDAP...etc. But I am still confused. Is anyone can help me?? Thanks