There are additional data fields (like the full name of the user who changed the object the last time) which shall be displayed at ECTR objects e.g. document or material master.
Show a special classification fields in ECTR level 1 data.
Show plant related or storage related data from several views in ECTR.
In the Backend a BAdI has to be implemented to determine that special data and return it to the frontend. This can be done with the following BAdI.
The value which should be added to an object has to be appended to the table out_customer_data.
Please see the example below how to fill this return table.
If you decide to use customer fields for a type of object in ECTR, you have to fill these fields for all instances of this object. E.g. it will have strange side effects if you fill a customer field key only for documents of dtype "PINT", but not for dtype "PEXT".
Example code for document info records:
DISCLAIMER: This is an example to show how to use the BAdI Interface. The usage of the "fat" BAPI_DOCUMENT_GETDETAIL2 to read the classification in a loop will slow down performance of ECTR.
If you know what you have to do, better make a direct select from AUSP table to read the classification values with "FOR ALL ENTRIES IN".
Please don't open an SAP Incident complaining about performance issues if the cause is an implementation of this BAdI. The bad BAdI performance can be identified in apilog which e.g. looks like that:
332160873 => 332160 ms => 332 s => more then 5 min !
Example code for materials:
The additional data are read in the backend and returned to the frontend with the upper BAdI.
Now the frontend has to be configured how to show this additional data in ECTR. In the configuration a mapping for customer_data has to be defined.
In the customer dictionary file must be defined how the fields of the returned structure should be named in ECTR:
There are other data which is send from backend without any need to implement a BAdI. E.g. the append structure to the table AENR or the append structure to table STPO (via CI_STPO).
This data can be addressed in this way for materials and change numbers.
Adding a new property to materials (screenshots)
- Implement the example code for material as described above.
Now ECTR has a new field:
If this is the display, you have forgotten to add a specific name into the dictionary.
Fill the customer.txt to name the field
- Open the Preferences in the Object Browser:
The name has changed as intended
- Select your value, add it to displayed columns and press 'Apply':
- Now ECTR shows your value in the Object Browser: