SAP ABAP IMG Activity /J7L/REA_T_CONNECTOR (BAdI: Determine Transaction Data (Universal Data Collector))
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ IS-REA-COR-DEC (Application Component) Recycling Administration: Declaration
     ⤷ /J7L/REA_T_CONNECTOR (Package) Universal Data Collector (Interface/Examples)
IMG Activity
ID /J7L/REA_T_CONNECTOR BAdI: Determine Transaction Data (Universal Data Collector)  
Transaction Code /J7L/85000094   (empty) 
Created on 20101018    
Customizing Attributes /J7L/REA_T_CONNECTOR   BAdI: Determine Transaction Data (Universal Data Collector) 
Customizing Activity /J7L/REA_T_CONNECTOR   BAdI: Determine Transaction Data (Universal Data Collector) 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /J7L/REA_T_CONNECTOR    

Use

You can use this Business Add-In (BAdI) to determine transaction data from various data sources that are used in the processes of the Recycling Administration component.

The interface /J7L/IF_REA_T_CONNECTOR provides the following methods:

  • GET_NEXT_KVFM_PACKAGE   

    This method provides the next data package for articles of the size that was defined in the method GET_PACKAGE_SIZE.

  • GET_NEXT_KMVD_PACKAGE   

    This method provides the next data package for consumed packaging of the size that was defined in the method GET_PACKAGE_SIZE.

  • HAS_NEXT

    This method returns ABAP_TRUE if an additional data package can be read via the method GET_NEXT_KVFM_PACKAGE.

  • SET_SELECTION_CRITERIA   

    This method passes the selection criteria from the respective application (transaction) to the BAdI instance.

  • GET_PACKAGE_SIZE   

    This method defines the total size of the expected data records.

  • GET_INSTANCE_NAMING   

    You can use this method in the transaction J7LMS to specify the field label for the indicator that you use to activate the determination of transaction data via this BAdI.

  • GET_CONCURRENT_PROCESSORS   

    This method specifies the number of parallel processes with which the data packages read can be processed. Asynchronous RFC calls are used to enable parallel processing. Each process occupies a work process. It is recommended that you make a distinction between a dialog process and background processing using sy-batch (system variable).

  • GET_PROCESS_STATE

    This method specifies whether the called context is to be retained after processing the data package in parallel processing.

  • GET_LOGON_GROUP

    This method returns the logical group to application servers that can be used for parallel processing. If no logical group is returned and the method GET_CONCURRENT_PROCESSORS returns a value > 1, the logical group DEFAULT is used.

  • IS_DATA_FILTERED   

    This method returns the information whether the data filter from Customizing (exception: countries) was applied.

  • IS_COUNTRY_SET   

    This method returns the information whether the determination of country of origin and country of destination included the determination of the transaction type (import/export).

  • IS_SPLITTING_EVALUATED   

    This method returns the information whether splitting filters (including trade levels) were applied during the determination of transaction data and whether the required logical keys were stored in the data package.

  • IS_TIMEFRAME_CONDENSED   

    This method returns the information whether the validity periods of articles were taken into account when aggregating transaction data (DATAB and DATBI fields in the table OUT_KVFM_TAB). If the validity periods were not taken into account, only the DATAB field is filled (date of transaction).

  • WRITE_PROTOCOL_HEADER

    This method is called to write the log header to the spool request if a single record log was requested. The log header determines the column layout in the log.

Requirements

Standard settings

If no BAdI implementation is active, the system uses the fallback class /J7L/CL_REA_T_CONNECTOR_FALLB. This fallback class issues a message that no BAdI implementation is active.

The BAdI implementation /J7L/CL_BILLING_DOC_01 determines billing documents. It also changes the field label for the indicator that you use to activate the determination of transaction data via this BAdI in the transaction J7LMS. The following restrictions apply for this implementation:

  • Country of origin and country of destination are not determined
  • Splitting filters are not applied (so no customer hierarchies are taken into account)
  • Time periods are not combined

Respective processing is therefore done in the master program.

Fields that are marked as not relevant via data filters are given the value ' - ' for aggregated output.

Activities

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG /J7L/REA_T_CONNECTOR 0 /J7L/REN0000003 Recycling Administration Core Functions 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20101018 
SAP Release Created in 606