CL_EXM_IM_EHSRC_TRACK_PROC - Example Impl.: Generation and Display of Detail Data

ROGBILLS - Synchronize billing plans   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Functionality

This is an example implementation for the BAdI BADI_EHSRC_TRACK_PROC.

This example implementation supplements the standard behavior during the data transfer of logisticsdocuments in substance volume tracking. Additional detailed data for confirmed quantities is storedin the corresponding database table. At the same time, a reference between the logistics documents andthe related quantity is produced and written into the database. For the scenarios EXP/SO and IMP/PUR,a reference to the corresponding material documents is created. For the scenarios CON and PRO, a reference for the relevant production orders or process orders is created.

You can display this data in the transaction SubstanceVolume Tracking: Monitoring (CBRC20) by choosing the pushbutton on the hit list. The requirementfor this is an active implementation of the BAdI BADI_EHSRC_TRACK_PROC in the system. The active implementationmust have a menu enhancement for the function code +MX1 implemented. Thismenu enhancement should have the function text Detail Data. Ifthe active implementation is available for the menu enhancement, the Detail Data pushbutton is then provided in the toolbar of the hit list in transaction Substance Volume Tracking: Monitoring (CBRC20).By choosing a single hit list result, you can display further detail data for the corresponding substance.In particular, there is data about the quantities tracked, in each case with reference to the corresponding material document, production order, or process order. The displayed data is the following:

• Object entry (for example, MSEG)

• Object entry attribute (for example, MBLNR-ZEILE-MJAHR)

• Key value

• Regulatory list

• Company code

• Year

• Plant

• Material

• Specification

• Monitored substance

• Determination date

• Tracked quantity

• Unit for Specifying Quantities

The display occurs using SAP ALV Grid Control (just like in the hit list).

The following methods of the BAdI are implemented:

DATA_FILL_CONFIRMED_SINGLE

DATA_FILL

MENU_EXIT_CALL

Relationships

Example

Notes

If an active BAdI implementation was created by copying this example implementation class to the BAdIBADI_EHSRC_TRACK_PROC, be aware that the corresponding detail data is only created, stored in the database, and displayed during monitoring when the switch for the business function LOG_EHS_CI_2 is switched on.

The functions related to detail data apply exclusively to confirmed quantities.

Displaying detail data is only possible from the substance view and the material view.

You can display detail data for one entry in the hit list at a time.

The created detail data are automatically deleted every three months or after 90 days during the datatransfer into the substance volume tracking tables. This means, the detail data that you created can be displayed for 90 days. After that, the data is no longer available.

The detail data that is determined during substance volume tracking is stored in the following tables:

• CCRCT_COLO EHS: Reference to confirmed consumed quantities

• CCRCT_PRLO EHS: Reference to confirmed produced quantities

• CCRCT_PRLO EHS: Reference to confirmed purchased quantities

• CCRCT_PRLO EHS: Reference to confirmed sold quantities

Further information

CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.


Length: 4519 Date: 20120526 Time: 121306     triton ( 170 ms )