Forms - Understanding LiveCycle form, Data Source and S/4H Data

[former_member567784]

Hi there,

    I am currently trying to understand the relation between the Form (in my case the Sales Invoice), the Data Source (which we assign to the form) and the underlying S/4H data (or maybe CDS?). At the moment I can see the relationship between the form and the data source in Adobe LiveCycle (ie the binding) but I am struggling to find a definitive answer for where this data resides in S/4H (ie where the data source is finding the data). I appreciate that some of this data is self explanatory and I could assume but ultimately I'd like to be definitive.

Can anyone help?

Kind regards

Simon

[Amith_Nair · Accepted solution]

Hi Simon,

In terms of the where the data resides, the answer is that the data of an application is distributed across several database tables and using the CDS views, you can rearrange the table fields, describe the metadata of the fields, that belong to one object but are located in different databases, and define the consumption of the data on the UI, in analytics or in other systems and if you ask me where does the Data source comes into picture: Storage from which a read data stream takes its data. In the context of this app a data source can be a pre-delivered CDS view. To avoid possible confusion, the input of the app is called data source and the output - custom CDS view.

Hope this helps!

Thank you! Amith Nair

[Feras_Al-Basha]

Hi Simon,

In addition to Amith's remarks, thanks to the framework he explained, key-users are enabled to easily extend data sources and maintain these extensions on form templates. Below please find two links that are related to your use-case for the sales invoice.

Extensibility for Output Forms and Email Templates of Billing Documents:

https://help.sap.com/viewer/a376cd9ea00d476b96f18dea1247e6a5/1811.500/en-US/0b6ec00b397349b09ec69ec7...

Process Extensibility for Sales and Billing Documents:

https://help.sap.com/viewer/a376cd9ea00d476b96f18dea1247e6a5/1811.500/en-US/b36541588ea81f60e1000000...

Please do mind that custom fields extended to the form template may not appear during preview but rather at final output.

Hope this is helpful,

Thank you!

Feras