Appendix A - Installing the SAP ABAP Function Modules
Details of the ABAP Function Modules used by ERP/CRM Integrator to extract metadata
If extraction of metadata from SAP, SAP BW or SAP BW HANA via ABAP has been chosen, then it will be necessary to install an ABAP Function Module on each SAP system from which metadata is to be extracted.
These Function Modules are supplied as SAP Transports and will be made available to customers for installation.
There is a separate Transport for each of the four types of SAP system that ERP/CRM Integrator can work with. These correspond to the ‘Source System Type’ specified on Step 3 of the Repository Wizard ( see ‘Using the Repository Manager to configure ERP/CRM Integrator’ earlier in this manual).
ERP/CRM Integrator is supplied with four additional ABAP Function Modules (one each for SAP ERP, SAP ERP CDS, SAP BW and SAP BW HANA) that can be used to run the ‘main’ ABAP Function Modules from within the SAP environment. These may be used to run the extraction process and create text files if it is not possible to access the SAP system via RFC calls.
The SAP Objects installed are described in the following table. Each transport, includes an SAP Package, Function Group and two Function Modules.
The ‘Main’ Function Module is the one normally called by ERP/CRM Integrator to extract metadata from the SAP system. The ‘All’ Function Module can be used when invocation by RFC is either not possible or not permitted by the SAP team. The All Function Module runs the ‘main’ Function Module to create a set of text files. These files can then be imported to ERP/CRM Integrator.
|
System Type |
System without CDS prior to ABAP 7.4 SP5 |
CDS ABAP 7.4 SP5 or later |
BW 'Classic' |
BW HANA (BW7.4 or greater) |
|---|---|---|---|---|
|
Namespace |
/SILWOOD/ |
/SILWOOD/ |
/SILWBW/ |
/SILWBW/ |
|
Main Function Module |
ERP_NONCDS |
ERP_CDS |
BWCLASSIC |
BWHANA |
|
ALL Function Module |
ERP_NONCDS_ALL |
ERP_CDS_ALL |
BWCLASSIC_ALL |
BWHANA_ALL |
|
Function Group |
ERP_NONCDS_FGRP |
ERP_CDS_FGRP |
BWCLASSIC_FGRP |
BWHANA_FGRP |
|
Package |
ERP_NONCDS_PACKAGE |
ERP_CDS_PACKAGE |
BWCLASSIC_PACKAGE |
BWHANA_PACKAGE |
Using the ABAP ALL Function Module
The ALL Function Module calls the main ABAP Function Module to extract metadata from the SAP, SAP CDS, SAP BW or SAP BW HANA system. The Function Module can be run in two different ways:
- To create the files on the ‘local’ PC. The generated ABAP files will be directly available to ERP/CRM Integrator so they can be processed by ERP/CRM Integrator to populate the ERP/CRM Integrator repository. This method uses an SAP feature called GUI_DOWNLOAD. GUI_DOWNLOAD moves files from the server onto a local PC and this cannot be run in ‘batch’ mode.
- To create the files on the SAP server. The generated ABAP files will be created on a local SAP Server drive and will need to be copied to a drive visible to ERP/CRM Integrator before they can be processed by ERP/CRM Integrator to populate the ERP/CRM Integrator repository. This method does not use GUI_DOWNLOAD and can therefore be run in ‘batch’ mode. It is the responsibility of the ERP/CRM Integrator user to create a suitable batch program for scheduling the ABAP Function Module when it has been decided to run in batch mode.
Running the ‘ALL’ Function Module creates a set of text files. These will need to be processed by ERP/CRM Integrator to complete the metadata load. This can be accomplished by running the Extraction Wizard as normal, and selecting ‘Import Repository from Load Files’ on the SAP Extract Options dialog. For more details see the chapter ‘Extracting Metadata from SAP and SAP BW’.
Running the ABAP ALL Function Module
The ALL Function Modules use 4 parameters. These are:
P_EXP_FILE_PATH: enter a suitable location for the files created by the Function Module
P_LANGUAGE_LIST: Enter a valid SAP language code
P_TRIAL_MODE: Enter ‘Y’ to run the Function Module without exporting actual data, enter ‘N’ to create the data files.
P_EXP_TARGET: Set this to ‘G’ to create files via GUIDOWNLOAD onto a PC, or ‘S’ to create the files on an SAP Server (using Dataset transfer).