on 05-02-2023 1:17 PM
Dear all,
in our S/4HANA Cloud (public edition), we've obviously exceeded the limit of Adobe form complexity for output management. If the document data is too much (esp. too many line items), the integrated ADS issues an error and the form cannot be rendered successfully.
Now the idea is to move some of the logic from the Adobe form to the BADI which is called before. In a public cloud system, there's one for header data (SD_BIL_PRINT_STANDARD_HEAD) and one for item data (SD_BIL_PRINT_STANDARD_ITEM), however,
For the amount of required information to be printed on the form, only some "flat fields" won't be sufficient in our case.
Has anyone experienced this issue and has a hint for me?
Thanks & regards
Wolfgang
Hi Zhehui,
as mentioned in my first post, we're already using the provided BAdIs (before Adobe form is rendered) but they lack some features that we'd need.
Thanks & regards
Wolfgang
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Wolfgang,
I met an issue before but I'm not sure if it can really help you. Just give an example.
We received a requirement from our customer that our customer wants to merge duplicate rows in Adobe Forms. We found there were some BAdIs can help us realize our requirement. It is only used for the APP "Create Correspondence". We can use this BAdI to set a logic to change the data before rendering to Adobe Forms. You can know more information from the link below.
App Extensibility: Create Correspondence | SAP Help Portal
Best Regards,
Zhehui
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.