on 2026 Feb 06 1:26 AM
Hello Experts,
I am facing an issue with Order Confirmation output in SAP S/4HANA Cloud (Public Edition).
Scenario:
Created a custom field using the Custom Fields and Logic app
Extended the custom field to Sales Order Document Item
Enabled the field for:
Forms
Analytics
Created a custom Adobe Form template
Used the same data source as standard:
FDP_V1_ORDER_CONFIRM_SRV
Updated the Adobe form and uploaded it into the custom form template
Assigned the form template in:
Output Parameter Determination
General Settings (IMG)
Issue:
When creating a Sales Order, the custom field value is correctly displayed in the Order Confirmation PDF while the output item is in “In-Preparation” status
Once the output item is Completed, the custom field value is missing (blank) in the PDF
Question:
Is it possible to display custom fields in the Completed Order Confirmation PDF in S/4HANA Cloud?
If not, is there any SAP-supported workaround or official documentation confirming this limitation?
Any guidance or SAP references would be appreciated.
Thanks in advance.
Request clarification before answering.
Dear @Ragunath_Selvam74,
Yes it’s possible but only if your custom field is available in the CDS-based data retrieval that SAP uses when the output item is Completed. What you’re seeing is a standard design difference in Pubic Cloud output control for sales documents:
SAP Notes below:
https://userapps.support.sap.com/sap/support/knowledge/en/3632762
https://userapps.support.sap.com/sap/support/knowledge/en/3440654
What to do:
1. Verify you did NOT accidentally mismatch the extended data source vs. the form data source
Practical check:
2. Ensure the field is available in the CDS-based rendering path
In practice that means the field must be part of the form data provider (FDP) data source / its underlying CDS view used at completion time. If your field only exists in the opened document runtime structures, it can show in In Preparation but disappear in Completed
3. SAP supported workaround if the needed data source can’t be extended
SAP supported workaround like in SAP Note above is:
This is SAP recommended path when the exact required data source isn’t extensible for your original field
Summary:
SAP documents your exact symptom in SAP Note 3632762 (link above)
Best Regards,
Dawid
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 39 | |
| 23 | |
| 19 | |
| 6 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.