Getting Error in SO_DOCUMENT_SEND_API1 while sending email in HTML with PDF attachment.

[rmz01]

Hi All,

I have developed a custom program and I'm using SO_DOCUMENT_SEND_API1 to send email in HTML format with PDF attachment of SMARTFORM. My program was working fine. Doing everything Converting SMARTFORM to PDF and then to OTF etc. And this program has been working perfectly for almost 1 year, but now suddenly it starts giving this error.

• Error calling FM <SBCOMS_SEND_REQUEST_CREATE> in <SO_DOCUMENT_SEND_API1> with SY-SUBRC <>

Found a similar question and it was answered by the author it self that it was because of some kind of issue on the BASIS side. And I think i'm having similar issue as it was working fine for a year, and also normal email are going out perfectly just issue with attachment.
If anyone can tell a little more, what should I tell or ask my BASIS team to check or correct.

Or if there is any other solution to it.

Thanks,

Regards,
Rameez

[rmz01]

This error could be caused by the configuration of where SAPoffice documents will be stored, the content repository to be used for this usually cannot be reached or is not configured correctly and due to this SAPoffice documents cannot be stored to this repository.

1. Check transaction SKPR08 to find the category assigned to document class SOFFPHIO (Storing physical information object for SAPoffice)

2. Then check the category assigned to SOFFPHIO in transaction OACT, here you will be able to see the content repository linked to this category which is causing the issue

3. There are 2 options now to resolve the issue, (1) change the content repository assigned to SOFFPHIO in OACT to SOFFDB, or (2) find the route cause of the problem with content repository

4. The reason change the content repository assigned to SOFFPHIO to SOFFDB is that this is the default storage location for SAPoffice documents, however please note now all documents will be usually stored to table SOFFCONT1, this can be checked in repository SOFFDB in OAC0.

5. To find the route cause of the problem with content repository, you should first check the configuration and connection of the content repository in OAC0, then check with your Network team if there are problems with connectivity. If there are still problems please run report RSCMST for the content repository in question and check the output.

[Sandra_Rossi]

The messages I saw were talking about looking into the SAP notes. Did you find anything?

[rmz01]

Yes, I also saw that message It was SAP Note 1569245. But no luck, it is giving this on Support Launchpad.

[DavidLY]

This error could be caused by the configuration of where SAPoffice documents will be stored, the content repository to be used for this usually cannot be reached or is not configured correctly and due to this SAPoffice documents cannot be stored to this repository.

1. Check transaction SKPR08 to find the category assigned to document class SOFFPHIO (Storing physical information object for SAPoffice)

2. Then check the category assigned to SOFFPHIO in transaction OACT, here you will be able to see the content repository linked to this category which is causing the issue

3. There are 2 options now to resolve the issue, (1) change the content repository assigned to SOFFPHIO in OACT to SOFFDB, or (2) find the route cause of the problem with content repository

4. The reason change the content repository assigned to SOFFPHIO to SOFFDB is that this is the default storage location for SAPoffice documents, however please note now all documents will be usually stored to table SOFFCONT1, this can be checked in repository SOFFDB in OAC0.

5. To find the route cause of the problem with content repository, you should first check the configuration and connection of the content repository in OAC0, then check with your Network team if there are problems with connectivity. If there are still problems please run report RSCMST for the content repository in question and check the output.

[rmz01]

Hello David,

Thankyou for the detailed explanation of every point, I don't think this is any connection issue as normal emails (without attachment) are send successfully. I will try all your suggestion, hopefully this will solve my issue. I do have one question though, does the content repository changed itself ? Because as I have mentioned, this was working fine for a year, emails/attachment were sent without any error. I'm sure the BASIS team didn't change any connectivity or configuration setting. So can there be any other reason that is just stops working ? Until and unless someone changed it.
Anyways Much appreciated, will connect with my network team. Will let you know about the result

[nitinm_10]

Hi @rmz01 ,

Is it resolved? What are steps you took for this

[rmz01]

I used CL_BCS class instead of FM