Ansicht
Dokumentation

BADI_INDEX_ORIGINALS - BAdI: Indexing of Document Originals in Enterprise Search

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the PLM Document Management (PLM-DMS) component.

You can use this BAdI to filter/restrict the indexing of document originals. This BAdI is called when indexing starts for document object (DOCUM_INFO_REC) in enterprise search.

This BAdI definition uses the standard interface IF_EX_DIR_INDX_ORIGINALS.

You can implement the method INDEX_ORIGINALS and set the following export parameters:

• EV_INDEX_ORIGINALS

This is a flag that indicates if the originals need to be indexed or not. If this flag is set to ABAP_TRUE, then the originals are indexed--that is, the content search for the original documents in enterprise search is enabled; else it is not.

• ET_APPL_TYPE

This is a range table, and it supplies the valid application types. So, the indexing of originals will be based on the supplied application types. The workstation applications are defined in Customizing under Cross-Application Components-->Document Management-->General Data--> Define Workstation Application (Transaction Code: DC30)

• ET_STORAGE_CATEGORY

This is a range table, and it supplies the valid storage locations. So, the indexing of originals will be based on the supplied storage locations. The storage locations are defined in Customizing under Cross-Application Components--> Document Management--> General Data--> Settings for Storage Systems--> Maintain Storage Category (Transaction Code: OACT)

For more information about the standard settings (filters, single use, or multiple use), see the Spot Element Definitions tab in the BAdI Builder (transaction SE18).

This BAdI is not active in the standard system.

This BAdI is designed for single use.

This BAdI is filter independent.

If there is no active implementation in the system, then all the originals get indexed by default via enterprise search indexing mechanism.

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.

Example BAdI implementation class is CL_EX_IM_ESH_INDEX_ORIGINALS.

TXBHW - Original Tax Base Amount in Local Currency   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4716 Date: 20240524 Time: 011954     sap01-206 ( 73 ms )