cancel
Showing results for 
Search instead for 
Did you mean: 

C4C SDK - Mandatory parameter form xml data is missing

gayathri_ramachandran
Participant
0 Kudos

Hello Experts,

We have an error in thrown when we try to preview a PDF document only for a specific customer. This is in PROD tenant.

My assumption is, this is because of some specific data and such data is not rightly handled in the code.

The problem is, we are not able to replicate the issue in Test and when we raised an incident with SAP, they mention this is custom solution.

Now we are left with no idea / clue how this could be resolved.

I have checked all the settings and data combination and no idea. if you had a similar error. I checked an other similar question, but there was no proper answer --> https://archive.sap.com/discussions/thread/3951632

Please some one share me some clue on this..

Accepted Solutions (0)

Answers (1)

Answers (1)

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Gayathri,

What is the exact error?

Bye,
. Horst

gayathri_ramachandran
Participant
0 Kudos

Sorry for not being clear. The error is

No PDF found.

BAdI not implemented

Output Service processing error

Mandatory parameter form xml data is missing.

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Gayathri,

I would agree to your assumption 🙂

WRT the incident and the statement "custom solution":

  • Can you add the same PDF to a SAP BO like Task or Appointment within the standard?
  • If it is shown there the incident must be handled by SDK
  • If the problem persist, the standard must take care of it.

HTH,
. Horst

gayathri_ramachandran
Participant
0 Kudos

Hello Horst,

Thanks for your response...

Yes, currently the PDF is for a standard BO only, Account BO, but a Custom solution to generate PDF document for an account. Here we get this error, only for a few customer and not for all.

So do you suggest, that we should claim SAP to help on this. Because the last time we raised an incident, they mentioned, it is custom solution and there was no further support.

Thanks

Gayathri.R

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Gayathri,

I understand that you have a custom solution which is creating the PDF.
Is this correct?
How do you create the PDF? Can the error be found here?

Bye,
. Horst

Former Member
0 Kudos

Hi Horst,

I am also facing same kind of issue with this error of PDF on TEST tenant,

No PDF found.
XML transformation failed
Output Service processing error
Mandatory parameter form xml data is missing.

It is working fine on DEV tenant but the same patch is moved to TEST tenant, then I am facing this issue.

I have created the PDF on custom BO.

Please suggest me how can I solve this issue.

Thanks and Regards,

Deepak

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Deepak,

How do you create the PDF in the first place?
Some coding, retrieve via Web Service, ...

Bye,
. Horst

Former Member
0 Kudos

Hello Horst,

Thank you for replying.

I followed the link to create :https://archive.sap.com/documents/docs/DOC-69441

I did not use any code or Web Service to create PDF.

I have created PDF directly from BO, after clicking right click on BO and option "Create print form" will be shown, using that option only I have created.

Regards,

Deepak

HorstSchaude
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Deepak,

Have you checked your ABSL coding if the data is retrieved from the SAP BO and filled correctly in the resp. elements of Custom BO?

Sometimes there is an issue if the format of the date is wrong or if comma vs. dot is used as decimal point.

HTH,
. Horst

Former Member
0 Kudos

Hi Horst,

That is true, I have faced the data format issue into the DEV tenant and fixed, so it was working fine in DEV tenant and I never faced this issue with all types of data . After moving the same thing into the TEST tenant for some accounts data I am facing the issue.

Thanks and Regards,

Deepak

Former Member
0 Kudos

Hi Horst,

Thank you for your valuable reply.

This issue has been fixed.

There was a problem with datatype defined in custom BO, datatype which "field" had not able store all value "number of characters" coming from the standard BO.

Regards,

Deepak