|
|
| Tristan W 2005-01-25, 7:48 am |
| I'm trying to invoke the BAPI_MATERIAL_AVAILABILITY rfc
I get this Error event:
Description:
The adapter failed to transmit message going to send port
"sap://AS:sap/00/100/". It will be retransmitted after the retry interval
specified for this Send Port. Details:"Specified cast is not valid.".
I'don't know if it
My SAP Adapter seem to work correctly whith others RFC like
RFC-CUSTOMER_GET.
The babi seem to be ok since it work in SE37 and using a web Buisness
Connecetor.
does any one know the trouble and the issue?
Other question:
Why is there an alwways greyed check box labeled "BAPI" when gerating IDOC
or RFC shemas in Biztalk.
Thanks
| |
| Tristan W 2005-02-08, 5:51 pm |
| After a long time without working on this trouble I've found the explanation
and the solution
The Explanation:
Some optional numericals fields are expected by the adapter but as there
is no value.
I suppose the adapter try to cast a null or blank value into an integer.
The solution :
I feed those fields with the sap default values
<DEC_FOR_ROUNDING>0</DEC_FOR_ROUNDING>
<ITM_NUMBER>000000</ITM_NUMBER>
"Tristan W" <tristan.walb@gmail.com> wrote in message
news:OH6fjqsAFHA.3504@TK2MSFTNGP12.phx.gbl...
> I'm trying to invoke the BAPI_MATERIAL_AVAILABILITY rfc
> I get this Error event:
>
> Description:
> The adapter failed to transmit message going to send port
> "sap://AS:sap/00/100/". It will be retransmitted after the retry interval
> specified for this Send Port. Details:"Specified cast is not valid.".
>
> I'don't know if it
>
> My SAP Adapter seem to work correctly whith others RFC like
> RFC-CUSTOMER_GET.
> The babi seem to be ok since it work in SE37 and using a web Buisness
> Connecetor.
>
> does any one know the trouble and the issue?
>
> Other question:
> Why is there an alwways greyed check box labeled "BAPI" when gerating IDOC
> or RFC shemas in Biztalk.
>
> Thanks
>
>
>
| |
| Tristan W 2005-02-09, 7:47 am |
| I've now more explanation about this Error.
With an other RFC I've a similar trouble:
The invocation of the RFC is ok but this one return me an Error
telling that a value of an optional field was wrong. But I've never fed this
field.
When a put the Field in the XML message (without value) I do not have this
Error.
My conclusion is : there may be a bug in the adapter that takes wrong value
where some nodes are not present.
My new question is there some other solution than this one because my XMLs
are getting heavy without any interest.
"Tristan W" <tristan.walb@gmail.com> wrote in message
news:OR2vhAgDFHA.1408@TK2MSFTNGP10.phx.gbl...
> After a long time without working on this trouble I've found the
explanation
> and the solution
>
> The Explanation:
> Some optional numericals fields are expected by the adapter but as
there
> is no value.
> I suppose the adapter try to cast a null or blank value into an
integer.
>
> The solution :
> I feed those fields with the sap default values
> <DEC_FOR_ROUNDING>0</DEC_FOR_ROUNDING>
>
> <ITM_NUMBER>000000</ITM_NUMBER>
>
| |
| Scherer, Manfred 2005-02-16, 7:50 am |
| Good Day!
I had a problem like you and I solved it with a different workaround:
In my document schema I replaced the data type TIMS by xs:string for example
as xs_string will work without any value checking.
In my case I had to do that 2 or 3 times in the schemas and that was it for
me concerning that error.
I hope that hint helps for you as well.
Kind regards
Manfred Scherer
"Tristan W" <tristan.walb@gmail.com> wrote in message
news:uOe9CpqDFHA.3972@TK2MSFTNGP15.phx.gbl...
> I've now more explanation about this Error.
>
> With an other RFC I've a similar trouble:
> The invocation of the RFC is ok but this one return me an Error
> telling that a value of an optional field was wrong. But I've never fed
this
> field.
> When a put the Field in the XML message (without value) I do not have this
> Error.
>
> My conclusion is : there may be a bug in the adapter that takes wrong
value
> where some nodes are not present.
>
> My new question is there some other solution than this one because my
XMLs
> are getting heavy without any interest.
>
> "Tristan W" <tristan.walb@gmail.com> wrote in message
> news:OR2vhAgDFHA.1408@TK2MSFTNGP10.phx.gbl...
> explanation
> there
> integer.
>
>
|
|
|
|