Kontakt

Ansicht
Dokumentation

W_FIP_018 - BAdI: Access Change Document

W_FIP_018 - BAdI: Access Change Document

rdisp/max_wprun_time - Maximum work process run time   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

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.

This BAdI uses the following methods:

  • FIND_CHANGED_DOCUMENTS
Returns a list of order headers for which a change was carried out in the timeframe defined by the IT_AEDAT_RANGEimport table. The list is related to the order IDs enclosed in the IT_ORDER_ID_RANGEimport table.

You must first create and set up change pointers for all applications that might change order documents. This must be done in the corresponding ERP system.

As for all BAdIs in the ES_FIP_BAL enhancement spot, a developer should never use the GET_BADI call 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_BADI method to instantiate the needed BAdI.

Example - Instantiation of the FIP_BADI_CHANGE_DOC_BAL BAdI

DATA:

lo_bal_factory   TYPE REF TO cl_fip_bal_factory,

lo_badi_change_doc TYPE REF TO fip_badi_change_doc_bal.

  " Get instance of the BAL factory

  cl_fip_bal_factory=>get_instance(

    IMPORTING eo_factory = lo_bal_factory ).

  " Instantiate the FIP_BADI_CHANGE_DOC_BAL BAdI

  lo_badi_change_doc ?= lo_bal_factory->get_badi(

    cl_fip_const=>co_change_doc_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_BADI call 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 exists for each BAdI that belongs to the ES_FIP_BALenhancement 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.






PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 5589 Date: 20240523 Time: 191030     sap01-206 ( 122 ms )