Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Create a program documentation dynamically

Former Member
0 Likes
603

Hi abap-gurus,

we have a big report-collection (> 1500 reports) which are not documentated.

But the customer now want to have for each report that there is a small documentation (blue Info-Button in selection-screen).

At least date of the last change of the report, author, short-description and so on - all that what I can select out of system tables.

The problem is: I know how I can create this doumentation via dialog, but how I can create program documentation (sapscript) dynamically in background?

I know the tables DOKIL, DOKHL and DOKTL but no way to create a documenation via automatism.

Any idea for my problem?

Best regards,

Christian

1 ACCEPTED SOLUTION
Read only

ThomasZloch
Active Contributor
0 Likes
453

I don't know a proper (i.e. "official" or SAP released) way to do this. An ST12 trace showed that a call to function module DOCU_UPDATE does the actual update of the tables you mentioned.

You could check the where-used-list to find out how this needs to be called and maybe wrap your own Z-function or method around it.

Thomas

2 REPLIES 2
Read only

ThomasZloch
Active Contributor
0 Likes
454

I don't know a proper (i.e. "official" or SAP released) way to do this. An ST12 trace showed that a call to function module DOCU_UPDATE does the actual update of the tables you mentioned.

You could check the where-used-list to find out how this needs to be called and maybe wrap your own Z-function or method around it.

Thomas

Read only

0 Likes
453

Hi Thomas.

Thanks for your answer.

I have played around and are currently testing, but it seems that I can create / modify the documentation with the FB "DOCU_DATEUP"

The template of the documentation in sapscript I get via "DOCU_READ" - also if it doesn't exist.

Then I could expand the documentation with my content and update (insert) it through "DOCU_DATEUP".

The tranport I would organise over "RS_CORR_INSERT" with e071 entry...