How to add delivery date in track sales order app

[vontuelff]

Hello,

i would like to add the field delivery date (ETDAT) in the "track sales order" app and the "sales order items confirmed as requested" app.

What is the easiest way to do so? Is it only possible by creating custom cds views, queries and custom KPI?

It would be so great if somebody could help me.

Thank you and Best Regards,

Charlotte

[Webster_Cui]

We helped you to accept the answer, since there were no updates after 7 days.

You can unaccept it anytime if you have further questions.

[BjörnKorioth · Accepted solution]

Hi Charlotte,

as "sales order items confirmed as requested" is a Smart Business app you have the option to replicate the app with a custom CDS view, cube and query.

Regarding the "track sales order" app. This is a FIORI Elements app, which means you only have the options to enhance the app with custom fields. However I see that the app already includes the requested delivery date. Which delivery date are you talking about exactly? Please keep in mind that the track sales order app is only providing information on sales order header level and cannot be enhanced with information from the item and schedule line.

In case you would like to requests changes to the standard, please use the customer influence portal to raise a request.

Best regards

Björn

[vontuelff]

Hi Björn,

thank you for your response.

Regarding the track sales order app i already suspected that it will not be possible. But with the custom cds view creation for the other app i had some problems with the association. Could you recommend a helpful learning or help page that has a closer look on associations and keys? For my case it seems that more than one association is necessary since the delivery date is included in the data source I_SalesDocumentScheduleLine and can not be linked with a proper key to the data source of the app I_SLSOrdConfAnalyticsCube. I have to link a sales order with a sales document as key and it seems not to be possible by creating only one association.

Maybe you can help me further?

Best Regards,

Charlotte

[BjörnKorioth]

Hi Charlotte,

I guess the big questions is on which level do you want your report to be, on schedule line level, or do you want to aggregate the schedule line information on item or header level.

If you want to stay on schedule line level, I would suggest to take the schedule line view as your basis and then just join the the cube over the header and item key fields, to get a cardinality of 0-1.

In an aggregation case, you can first create a custom CDS that aggregates the information of the schedule line on the appropriate level and then join that new view with the cube. Here again your cardinality will be 0-1.

Sadly I could not find a tutorial that shows how the joins work in the custom CDS app, but I hope you can understand my answer anyways, but this blog post might help you.

Best regards

Björn