Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
peter_atkin
Active Contributor

I was asked to investigate why some drill-down options in the standard PM/CS multi-level reports don't work.


 

For example, why can't I drill-down into the component or material documents in the order multi-level report IW40.


 


I traced the issue back to missing entries in tables T354S and T354T.


 

I found an old OSS Note (OSS Note 78365) which indicates how these tables should be populated.


 

Here are the entries I added via transaction SM30:


 


T354S: Set parameter for calling master data transactions


















































Field Name Sequence SetPID Reference Field
DIAUFM-MATNR (for component)
1 MAT
DIAUFM-MATNR
DIAUFM-MATNR (for component) 2 WRK DIAUFM-WERKS
RIHRESB-MATNR (for component) 1 MAT RIHRESB-MATNR
RIHRESB-MATNR (for component) 2 WRK RIHRESB-WERKS
DIAUFM-MBLNR (for material document) 1 MBN DIAUFM-MBLNR
DIAUFM-MBLNR (for material document) 2 MJA DIAUFM-MJAHR

 

 

T354T: Transaction branching by dynpro field
























Field Name Transaction
RIHRESB-MATNR (for component) MM03
DIAUFM-MATNR (for component) MM03
DIAUFM-MBLNR (for material document) MB03

 

Additional multil-level report notes:

  1. You can use BADI_EAM_STRUCTURE_LIST (SE18) to manuipulate the list. For example we have used this BADI to change the colours in the list to better identify objects.You can also use this BADI to add new objects into the list


 

   



2 Comments
Labels in this area