Solved: bytes over a period of time - KPRO

tiago_scherer · ‎2008 Dec 19

Hello colleagues!

Could you please help me with this question?

How many bytes over a period of time for a particular document type have been stored in the KPRO system. Is it possible to find this kind of statistics in document management?

Thank you

Former Member · ‎2008 Dec 19

Hi,

ALl the information is stored in tables in R/3. Below is a program that will do it all for you.

This gets the document data based on the selection. Then you can take it to excel for further analysis.

Espen

TYPE-POOLS slis.

TYPES:

BEGIN OF lt_dmsrep,

dokar LIKE draw-dokar,

doknr LIKE draw-doknr,

dokvr LIKE draw-dokvr,

doktl LIKE draw-doktl,

dktxt LIKE drat-dktxt,

phio LIKE dms_ph_cd1-phio_id,

loio LIKE dms_doc2loio-lo_objid,

file_name LIKE dms_phf_cd1-file_name,

mimetype LIKE dms_phf_cd1-mimetype,

stor_cat LIKE dms_ph_cd1-stor_cat,

file_size LIKE dms_phf_cd1-file_size,

crea_time LIKE dms_ph_cd1-crea_time,

crea_user LIKE dms_ph_cd1-crea_user,

END OF lt_dmsrep,

tt_dmsrep TYPE STANDARD TABLE OF lt_dmsrep.

REPORT zdms_info.

INCLUDE zdms_info_top . " global Data

DATA:

g_dmsrep TYPE lt_dmsrep, "1)

g_dokar LIKE draw-dokar, "1)

g_doknr LIKE draw-doknr, "1)

g_dokvr LIKE draw-dokvr, "1)

g_doktl LIKE draw-doktl, "1)

g_sdok_stcat LIKE dms_ph_cd1-stor_cat, "1)

g_user LIKE dms_ph_cd1-crea_user, "1)

g_file_size LIKE dms_phf_cd1-file_size, "1)

g_crea_time LIKE dms_ph_cd1-crea_time, "1)

it_dmsrep TYPE tt_dmsrep. "1)

----

select-options

----

SELECT-OPTIONS:

so_dokar FOR g_dokar, "1)

so_doknr FOR g_doknr, "1)

so_doktl FOR g_doktl, "1)

so_dokvr FOR g_dokvr, "1)

so_stcat FOR g_sdok_stcat, "1)

so_user FOR g_user, "1)

so_size FOR g_file_size DEFAULT 1000000, "1)

so_time FOR g_crea_time DEFAULT sy-datum. "1)

end select-options

----

start-of-selection

----

START-OF-SELECTION.

******Selects all data necessary across the KPro tables for DMS*****
*****THey are: draw, drat, dms_ph_cd1, dms_doc2loio, dms_phf_cd1****

SELECT

draw~dokar

draw~doknr

draw~dokvr

draw~doktl

drat~dktxt

dms_ph_cd1~phio_id

dms_doc2loio~lo_objid

dms_phf_cd1~file_name

dms_phf_cd1~mimetype

dms_ph_cd1~stor_cat

dms_phf_cd1~file_size

dms_ph_cd1~crea_time

dms_ph_cd1~crea_user

FROM

draw INNER JOIN drat

ON draw_{dokar = drat}dokar

AND draw_{doknr = drat}doknr

AND draw_{dokvr = drat}dokvr

AND draw_{doktl = drat}doktl

INNER JOIN dms_doc2loio

ON draw_{dokar = dms_doc2loio}dokar

AND draw_{doknr = dms_doc2loio}doknr

AND draw_{dokvr = dms_doc2loio}dokvr

AND draw_{doktl = dms_doc2loio}doktl

INNER JOIN dms_ph_cd1

ON dms_doc2loio_{lo_objid = dms_ph_cd1}loio_id

INNER JOIN dms_phf_cd1

ON dms_ph_cd1_{phio_id = dms_phf_cd1}phio_id

INTO TABLE

it_dmsrep

WHERE

draw~dokar IN so_dokar

AND draw~doknr IN so_doknr

AND draw~dokvr IN so_dokvr

AND draw~doktl IN so_doktl

AND dms_ph_cd1~stor_cat IN so_stcat

AND dms_ph_cd1~crea_user IN so_user

AND drat~langu = sy-langu

AND dms_phf_cd1~file_size IN so_size.

PERFORM displaygrid.

end start of selection.

----

Form DisplayGrid
Displays the data selected in an ALV.
Firsts create the field catalog, then display.

----

FORM displaygrid.

DATA:

it_fieldcat TYPE slis_t_fieldcat_alv,

l_fieldcat TYPE slis_fieldcat_alv.

l_fieldcat-fieldname = 'DOKAR'.

l_fieldcat-ref_tabname = 'DRAW'.