search

tian-zhihui / cordyssapcon

Automatically exported from code.google.com/p/cordyssapcon
Apache License 2.0
0 stars 0 forks source link

SAP Connector considers only first input #48

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system? On
what BOP version? On what SAP release?

Please provide any additional information below.

Everything detailed in attached document.

Original issue reported on code.google.com by sanjay.p...@gmail.com on 13 Aug 2012 at 12:04

Attachments:

GoogleCodeExporter commented 8 years ago 
You explain in the attached document what you get as response but I do not 
understand where your problem is. I assume, the result does not correspond with 
your expectation. However since you use a custom RFC I do not know what you 
expect and how that is different from the real response.

Original comment by te...@cordys.com on 13 Aug 2012 at 12:24

GoogleCodeExporter commented 8 years ago 
Hi,
Please go theorugh the document again. The expected behaviour is explained 
earlier and then the behaviour observed in cordys (4 cases). The cordys 
behaviour is not normal. it is omitting the second input parameter irrespective 
of whether it is table or parameter.

Original comment by sanjay.p...@gmail.com on 14 Aug 2012 at 6:17

GoogleCodeExporter commented 8 years ago 
Hi, if I got it right, it is about the fact that all records are returned 
irrespective of the date provided. If this is the case, try to provide the date 
in different format. An RFC might require the date to be provided in a 
different format than on the GUI.

Common formats are:
YYYY-MM-DD
DD-MM-YYYY

If the date is not provided in the proper format SAP sometimes does not throw 
an error but just ignores the parameter.

Original comment by te...@cordys.com on 14 Aug 2012 at 8:11

GoogleCodeExporter commented 8 years ago 
Yes - That solved the problem. In fact, the date was not being accepted at all. 
But becuase the date parameter in the response was same as the date we were 
trying and we thought that only date is being accepted. With wrong date format, 
further inputs were rejected. When tried to give date later, the parameter 
prior to date were accepted correctly. 

Sorry for all confusions and misunderstandings.

Original comment by sanjay.p...@gmail.com on 19 Aug 2012 at 1:08