Error during attachment transfer from C4C to ECC

[florian2636]

Hi,

maybe someone can help me on this one. During the execution of "Replicate Sales Order Attachment to SAP Business Suite" something goes wrong.

Trace on HCI shows:

Invoked endpoint{

      Cxf.EndpointAddress = /COD/ERP/ReplicateSalesOrderAttachment

      Error = Inbound processing in endpoint at /COD/ERP/ReplicateSalesOrderAttachment failed with message "SoapFault:faultstring= RABAX occurred on server side ; faultcode={http://schemas.xmlsoap.org/soap/envelope/}Server"

In ST22 on ECC I see:

ategory               ABAP Programming Error

untime Errors         UNCAUGHT_EXCEPTION

xcept.                CX_SOAP_SEQ_SCD_ERROR

BAP Program           CL_SOAP_QUEUE_BGRFC===========CP

pplication Component  BC-ESI-WS-ABA-RT

Exception 'CX_SOAP_SEQ_SCD_ERROR' was raised, but it was not caught anywhere

along the

call hierarchy.

Maybe I missed something? Any help is highly appreciated.

Best Regards

Florian

[former_member408848 · Accepted solution]

Hi Florian,

unfortunately I have no experience with this particular WebService.

According to the error message, it failed in ECC, so the connection itself works fine.

As an option, you can try to debug this WebService in ECC.

You may try to find the responsible WebService in ECC, it is normally implemented as an ABAP FM. You may set a breakpoint there to debug it.

Normally integration processes will be started in ECC with communication user. There could be the following options how it can be configured:

- Basic authentication: the WebService in ECC is called with username/password, so this user is used as a processing user

- Certificate-based authentication: request comes signed with a certificate, the certificate is mapped with the communication user in table VUSREXTID

Normally you cannot debug with your communication user itself, but in a test system you may try to temporary change user to a normal ECC user with debugging authorization.

In this case you set the breakpoint for this user and it will be triggered when you call the web service.

In debugger you will be able to see more.

Regards,

Maxim

[florian2636 · Accepted solution]

Hi Maxim,

all the other integrations work very well. Only the attachment is ending with a dump on the ECC side. The systems iteself are plain standard C4C as well as ECC on EHP7 without custom developments.

Best Regards

Florian

[former_member408848 · Accepted solution]

Hi Florian,

I see. Than debugging (as described above) may be a good way to find out what the reason for the failure is.

As soon as you have not changed anything, you may also open an incident.

Best Regards,

Maxim

[former_member210407 · Accepted solution]

Hi Florian,

I have exactly the same issue.

Did you find a resolution?

Best regards,

Benjamin

[florian2636 · Accepted solution]

Hi Benjamin,

so far did not continue to check on this one. Sorry.

Best Regards

Florian

[Former Member · Accepted solution]

Hi,

I am also having similar issue on ECC system when trying integration service from Dell Boomi middle-ware...

any help and inputs please...

Thanks

Subbu

[former_member210407 · Accepted solution]

Hello,

I implemented SAP note 1043195 and I have no dump anymore.

I hope this can help you also.

Best regards,

Benjamin

[florian2636 · Accepted solution]

Hi Benjamin, thx for sharing. Works like charm now.

Best Regards

Florian

[former_member210407 · Accepted solution]

Hi Florian,

That's great!

I'm still facing issues with this interface even after implementing the note.

The WS is working fine but I can't find my attachments in my sales doc (service for object > attachement list).

Am I looking at the right place?

Are you using DMS?

Best regards,

Benjamin

[florian2636 · Accepted solution]

Hi Benjamin,

we just use the standard GOS. Our basis implemented the note. First I only saw the messages in SRT_MONI in status "Waiting for scheudler". They were not processed. We then defined the "Supervisor destination" and it started to work.

The report RSWSMANAGEMENT was then used to get the data manually processed. Normally the job  SAP_SOAP_RUNTIME_MANAGEMENT is handling the processing periodically.

Best Regards

Florian

[former_member210407 · Accepted solution]

Thanks a lot Florian, it was the missing step to make it all work correctly.

Best regards,

Benjamin