ARBA COT (Remito Electrónico) - Argentina

[Former Member]

Hi!!

I am implementing "Remito Electronico" for ARBA (Argentina).

Scenario PROXY -> HTTP_AAE (Method POST with Multipart-Form)

I am getting this error from Legacy (they are answering)

Spanish:

<?xml version="1.0" encoding="UTF-8" ?>

<TBError>

<tipoError>DATO</tipoError>

<codigoError>87</codigoError>

<mensajeError>El formulario multipart enviado es incorrecto. Verifique las especifiaciones para la aplicación cliente.</mensajeError>

</TBError>

English:

<?xml version="1.0" encoding="UTF-8" ?>

<TBError>

<tipoError>DATO</tipoError>

<codigoError>87</codigoError>

<mensajeError>Form sent is incorrect. Check specification from client application</mensajeError>

</TBError>

Channel configuration: (see attachment)

As JDBC has its own structure to work: Does HTTP_AAE has its own too??

Thanks

[Former Member · Accepted solution]

Solved with:

[former_member1173089 · Accepted solution]

with.....?

[Former Member]

Hello Experts,

I am working on one of the cot interface and having somewhat same requirement. Mine is a pass through scenario from PI, But I am getting the same error.

English:

<?xml version="1.0" encoding="UTF-8" ?>

<TBError>

<tipoError>DATO</tipoError>

<codigoError>87</codigoError>

<mensajeError>Form sent is incorrect. Check specification from client application</mensajeError>

</TBError>

Please let me know if there are any changes to be done in Receiver HTTP_AAE adapter.

[Former Member]

Hello,

Please change the Content Type from text/xml to "application/x-www-form-urlencoded" because you are using form based posting.

Please see the below link.

HTTP Requests Supported by the Java HTTP Adapter - Advanced Adapter Engine - SAP Library

Regards,

Farhan

[former_member184720]

Hi Cerbero -

As JDBC has its own structure to work: Does HTTP_AAE has its own too??

Nope.

It could be that the provided form name is being rejected by your target system. May be you can cross verify if it is the correct form name.

More Info : http://scn.sap.com/docs/DOC-44764