Ariba cXML Purchase orders with attachment throws 500 internal server error at CIG

[former_member49]

Hello All,

We have done integration for cXML Purchase orders with attachment(PDF) to receive at CPI via CIG from Ariba

Message flow is like Ariba --> CIG --> CPI --> ECC

We have done many test cases and all were successfully processed via CPI and all of a sudden cXML POs with attachment getting 500 internal server errors at the CIG side as a response from the CPI system

What could be the possible reason that on the CPI side, the first Iflow step is MIME multipart Decoder and CPI is expecting a message of type MIME multipart where cXML message with attachment included, which might not be receiving in the above format from CIG, or some changes could have done on CIG hence CPI is rejecting it with 500 internal server error and on the other side cXML POs without attachment are processing through CPI hence there is no connectivity issue either.

Note:

When we trigger test cases with an attachment from testing tools, it's processing through CPI

Moreover, messages were processed successfully with attachments before from Ariba

No changes done on the CPI side either design or configuration level except invoice

Please suggest to us how and where to correct that the message format receiving of type MIME multipart from CIG

Regards

CPI Technical Team

[Francois-Xavier]

Hello Nayeem

We are experiencing the same issue in my company in the productive environment. This is a CRITICAL issue for us as it impact key business elements contained in the attachment of the orders... OSS message 704301 / 2021 has been opened with HIGH priority since last week but still not good answer from SAP. No fix provided...

Maybe would be nice that you open an OSS message as well on your side and refers the one we have created also.

Best regards

[former_member49]

Hi Yuri,

Is there any fix on the issue? Please let us know the update

Thank you

Regards

Nayeem

CPI

[yuri_ziryukin]

Sorry, Nayeem, that it took so long to resolve it. The fix was implemented and as far as I know this scenario should be working by now.

[former_member49]

Hi Yuri

Thank you so much for your response with inputs. Forwarded to our CIG colleagues to check further

Moreover FYI ., CIG to CPI we used HTTPS sender adapter because it was somehow missed to mention in my initial error description

Regards

Nayeem

CPI Technical

[yuri_ziryukin]

Dear customers,

the issue seems to be related to the "Tab" character (not allowed) that was added to the Content-Type HTTP header right in front of "boundary" word. This is happening on Ariba CIG side when forming HTTP request to CPI. I have forwarded one of the customer cases (704301) to the right colleagues with my analysis. I hope they will provide a fix as soon as possible.

Best regards,
Yuri Ziryukin
Technical Core Competence team
SAP SE

[Francois-Xavier]

Thanks 🙂 Let's hope we can have a fix resolution as it is a major issue currently in our production environment...

[former_member49]

Hi Francois,

OSS is already opened with high priority and still waiting for a resolution by SAP

will update you once the issue is fixed

Regards

Nayeem