| Author |
Message
|
| smdavies99 |
 Posted: Wed Oct 12, 2011 3:39 am Post subject: SAP Adapter funny |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'm loading some data into SAP using a SAPRequest node.
(6.1.0.9 Windows)
In the UserTrace output I see this.
| Code: |
2011-10-12 11:59:52.656742 8764 UserTrace BIP3484E: ''An error occurred while Setting property [Edate] value=Sun Sep 30 00:00:00 BST 2012''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2011-10-12 11:59:52.657009 8764 UserTrace BIP3484E: ''CWYAP2046:An error occurred while setting the Edate BAPI property with value Sun Sep 30 00:00:00 BST 2012. Error Message: null. Explanation=The metadata for the Edate property is either missing or incorrect. UserAction=Refer to the exception message for more details.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
|
The data is ending in SAP in the right place but I've never see this sort of hiccup before.
Has anyone any thoughts on it?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Oct 12, 2011 5:42 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
what does the RFC Trace tells....
I dont have any idea or not even encountered this kind of error before 
good that you pointed out
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 12, 2011 7:29 am Post subject: Re: SAP Adapter funny |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| smdavies99 wrote: |
I'm loading some data into SAP using a SAPRequest node.
(6.1.0.9 Windows)
In the UserTrace output I see this.
| Code: |
2011-10-12 11:59:52.656742 8764 UserTrace BIP3484E: ''An error occurred while Setting property [Edate] value=Sun Sep 30 00:00:00 BST 2012''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
2011-10-12 11:59:52.657009 8764 UserTrace BIP3484E: ''CWYAP2046:An error occurred while setting the Edate BAPI property with value Sun Sep 30 00:00:00 BST 2012. Error Message: null. Explanation=The metadata for the Edate property is either missing or incorrect. UserAction=Refer to the exception message for more details.''
An adapter component has written the diagnostic message included here.
Refer to the appropriate WebSphere Adapters message in the WebSphere Brokers documentation.
|
The data is ending in SAP in the right place but I've never see this sort of hiccup before.
Has anyone any thoughts on it? |
My guess is that the date might get written to the field, but the date format being used is not right.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Oct 12, 2011 8:04 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I thought about the date type not being right.
The discovered message set says that the type is indeed xs:date.
Giving it a DATE type variable makes SAP throw some more serious errors.
So far, the only data I can give it that will actually get stored inside SAP is CHARACTER...
This is a very old SAP/R3 instance (V4.3 I think). I'll need to do some more digging when I get time.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 12, 2011 11:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| smdavies99 wrote: |
I thought about the date type not being right.
The discovered message set says that the type is indeed xs:date.
Giving it a DATE type variable makes SAP throw some more serious errors.
So far, the only data I can give it that will actually get stored inside SAP is CHARACTER...
This is a very old SAP/R3 instance (V4.3 I think). I'll need to do some more digging when I get time. |
Well with those very old versions you might have to use an old SAP adapter based on a compatible JCO version.... or just assign the right character value to the field...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
