Ansicht
Dokumentation

W_FIP_020 - BAdI: Access Customer Data

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

This technical Business Add-In (BAdI) is part of a business abstraction layer used internally by SAP. It is not intended for reuse by customers. This technology enables individual functionality or complete applications to be called either by back-end functions or enterprise services. It is used to read customer information using some selection criteria.

This BAdI uses the following method:

• READ_BY_ELEMENTS

Returns a list of customers with its details from ERP DB tables, using the parameters of the method as search criteria. The partial result of selection by each criterion is merged into the final results. The parameters are optional; they allow you to make your search flexible.

When implementation of this BAdI is enabled, the application can retrieve the data from the back-end.

As for all BAdIs in the ES_FIP_BAL enhancement spot, a developer should never use the GET_BADIcall to create an instance of this BAdI. Rather, the developer should first get an instance of the CL_FIP_BAL_FACTORY class and then use its GET_BADImethod to instantiate the needed BAdI.

Example - Instantiation of the FIP_BADI_CUSTOMER_BALBAdI

DATA:

lo_bal_factory   TYPE REF TO cl_fip_bal_factory,

lo_badi_customer TYPE REF TO fip_badi_customer

  " Get instance of the BAL factory

  cl_fip_bal_factory=>get_instance(

    IMPORTING eo_factory = lo_bal_factory ).

  " Instantiate the FIP_BADI_CUSTOMER_BAL BAdI

  lo_badi_customerg ?= lo_bal_factory->get_badi(

    cl_fip_const=>co_customer_bal).

This BAdI was designed to run only one BAdI implementation. It uses a filter named ACCESS_TYPE to determine which implementation is to be executed. Each implementation must have a different filter. In the GET_BADIcall to the BAL factory, the value of ACCESS_TYPE is automatically determined and set.

All possible values of ACCESS_TYPE:

• 0BA

Implementation using BAPIs and/or direct database access

• 0ES

Implementation using enterprise services, which allows access to different back-ends in case used functionalities are available in different systems.

• Cnn (where nn is a one-digit or two-digit number)

Customer implementation

The BAL factory class determines the value of the ACCESS_TYPE filter by going through the following process:

1. Get the value from the FIP_C_BAL_BADI client-specific customizing table.
2. If a value was not yet obtained, get the value from the FIP_C_BAL_CONF client-specific customizing table.
3. If a value was not yet obtained, the default value as determined by the BAL factory will be used. In ERP 6.0 EHP4, this value is 0BA.

As of ERP 6.0 EHP4, 0BA and 0ES implementations exist for each BAdI that belongs to the ES_FIP_BAL enhancement spot.

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

You want to retrieve all customers for a given set of materials (lt_material_id) and limit the results to a specific customer (lt_customer):

CALL BADI lo_badi_customer->read_by_elements

          EXPORTING

,,it_material_id,,,,,,,,=,,lt_material_id.

            iv_query_hits_maximum_number = ,,100000

            it_customers_id              = ,,,,,,lt_customer

            iv_retail_active             = ,,,,,,lv_is_retail

          IMPORTING

            ev_more_elements_available   =,,,, lv_more_avail

            et_recipients                = l,,,,,,lt_customer_info

          CHANGING

            co_logger                    = ,,,,,,lo_logger.

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

Length: 7893 Date: 20240523 Time: 214401     sap01-206 ( 137 ms )