This appendix includes the following sections:
The update path for the ODI SAP Components depends on which ODI SAP Adapter version had been used for installation.
Installations of ODI SAP Adapter prior to v32
For ODI SAP Adapter versions prior to v32 (= SAP package name is ZODIBW_PCKG
, ZODIERP_PCKG
, or ZODI_DEVCLASS
, or the SAP function group is ZODI_FGR
, then please contact Oracle support for details on upgrading, particularly on how to uninstall the existing ODI SAP Components and how to handle any SAP function modules and reports for existing ODI SAP mappings or interfaces.
To check the SAP package name, log in to SAP system >Go to transaction SE80
> provide package name as above.
Installations of ODI SAP Adapter v32 or later
For any SAP systems, which have been installed using the ODI SAP Adapter v32 or later, there is no need for uninstallation. The new ODI SAP Components can be installed on top of an existing installation following the instructions in Installing ODI SAP Components.
If you have any queries, please contact Oracle Technical Support.
Installation of the ODI SAP components is done through the use of TRs (SAP Transport Requests). These transport requests also contain the SAP user profiles. This section describes how to import the ODI SAP components and grant the required authorizations to the ODI SAP user by assigning the ODI SAP profiles.
This section includes the following topics:
Installation of SAP Transport Request requires downloading the TRs from Bristlecone e-delivery website.
This section includes the following topics:
Perform the following steps to download the TR files:
Go to the following Download URL:
http://www.bristleconelabs.com/edel/showdownload.html?product=odi_sap_km_transport
Select the required file and click Download. You will be redirected to Login Page.
If you are a registered user, log in with the registered Email Id as user name and the password received.
If you are a new user, perform the following steps to register:
Go to the following URL:
Click Register.
Fill in the details in the registration form.
In the Email ID field, provide a valid business email address. This will be used to email your password.
Reopen the download link mentioned in step 1.
Select the appropriate SAP version of the TR and download.
Perform the following steps to install the TR files:
Caution:
Artefacts of TR Files: Naming convention used is R<6 digits>.<source system> and K<6 digits>.<source system>.
The Source system is the developers source system.
K Type Transport : Cofile (1 - 3 KB in size)
R Type Transport : Datafile (size more than the Cofile)
K file is a Cofile: All transport requests' control and metadata attributes gets stored in this file, which are in the format of R<T.RNo>.<SID>. These are command or change request information files that include information about the transport type, object classes, required import steps, and post-processing exit codes.
R file is a Datafile: All transport requests' data gets stored in this file, which are in the format of K<T.RNo>.<SID>. This contains the actual data for the Transport i.e. what changes will be made in your system.
Log in to the SAP system and perform the following steps to create transport request for ODI SAP Production Objects.
Perform the following steps to install and assign SAP user profile:
Execute PFCG, on the menu, click Role and then select Upload.
Click Continue on the Information dialog.
Specify the path where you have saved the .SAP file and then click Open.
Scroll down the drop down list and provide the appropriate input and click Allow.
Click Continue on the subsequent screen.
Role is successfully uploaded.
Type the name of uploaded role and click the Edit icon as shown below.
Click the Roles tab.
Perform the following steps to activate each role:
Double click the role Z:ODI_ANU_LBU
.
Click the Authorizations tab.
Click the Change Authorization Data icon shown below.
Click Generate and then click Back.
Note:
The status of Authorizations and User tab must be green.
Repeat these steps to activate for all roles inside Z:ODI_COMPOSITE
.
Click Save.
Once the import process is done successfully, assign the imported profile to the SAP ODI user.
Request and assign SAP Developer License Key to ODI SAP User as described in section SAP ABAP BW Required Privileges or SAP ABAP ERP Required Privileges. This is mandatory for the ODI SAP Adapter to work.
Note:
In a few use-cases (use in production) the developer key can be omitted. For details refer to SAP ABAP BW Required Privileges or SAP ABAP ERP Required Privileges.
This section describes some basic validation steps for the SAP administrators. Executing these steps ensures that previous installation steps were successful.
This section includes the following topics:
Validating a shared folder setup applies only if you plan to transfer data using a Shared Directory. This section can be skipped, if the FTP transfer is used. The validation of the shared folder setup needs to be performed before any subsequent steps in this guide can be performed. This validation is typically performed by your SAP Basis team.
Step 1: Validating folder access from the SAP application server
Start the SAPGUI.
Use the ODI SAP user and password to connect to the SAP system and client.
Go to transaction AL11.
Select the shared folder.
Double-click the shared folder to test the directory declaration.
This should report a successful connection. If not, please contact your SAP basis team. Do not continue until this test passes.
Note:
SAP uses the OS user <sid>adm to connect to the directories declared in AL11.
Print screen.
Step 2: Validating folder access from the ODI agent machine
Validating an FTP setup applies only, if you plan to transfer data using FTP. This section can be skipped, if you use a Shared Directory for the data transfer. The validation of the FTP setup needs to be performed before any subsequent steps in this guide can be performed. This validation is typically performed by your SAP Basis team.
Step 1: Validating SAPFTPA destination
Start the SAPGUI.
Use the ODI SAP user and password to connect to the SAP system and client.
Go to transaction SM59.
Expand TCP/IP connections.
Open the SAPFTPA destination.
Click Test connection.
This should report a successful connection. If not, please contact your SAP basis team. Do not continue until this test passes.
Print screen.
Step 2: Testing FTP connection
This section describes how to test some of the key SAP privileges. Proceed with the subsequent steps in this guide only after successful validation of these tests. This validation is typically performed by your SAP Basis team.
Perform the following steps to validate whether a SAP user has appropriate dev rights and owns a dev license key:
If a transaction allows the creation of a program without asking for any key or other authorization message, then the SAP user has validated that it has the appropriate dev rights and license key. Otherwise your SAP basis team needs to register the SAP user in service.sap.com to get the license key and a Basis person can help him with dev rights.
As the SAP connector creates SAP objects, such as, for example, function modules, into the SAP development system, these changes need to be transported into QA and production systems once the development is done. The SAP's change and transport system uses the SAP Transport Layer Name to identify the route a change has to take. A transport layer is assigned to each development class and thus to all objects in that class. The transport layer determines:
In which SAP System developments or changes to the repository objects are made
If objects are transported to other systems within the group when development work has been completed
A consolidation route is created from the development system to the quality assurance system through the transport layer Z<SID>
. It then becomes the standard transport layer for customer development and customizing.
A consolidation route is created from the development system to the quality assurance system through the transport layer SAP
for the transport of SAP Standard objects.
It is important to specify the correct transport layer name before running the RKM SAP ERP for the first time.
Perform the following steps to identify the list of defined transport layers in your SAP landscape:
By default, the RKM option SAP_TRANSPORT_LAYER_NAME is set to SAP
. Ask your SAP basis admin which transport layer you should use. This transport layer name must be set on the SAP_TRANSPORT_LAYER_NAME RKM option. A wrong or invalid transport layer name will cause serious delays during the installation process.
This section describes how to remove the ODI SAP Components from an SAP system. In case you plan to update to a newer ODI SAP Component version, please see Updating ODI SAP Components to identify whether the uninstallation step is required or can be skipped.
Perform the following steps to uninstall ODI SAP components:
If any of the objects is not deleted, then go to SU53
and check missing privileges. Try to grant the same to that SAP user and then continue with deleting that object.
See Validating Uninstallation of ODI SAP Components for information on how to validate uninstallation of ODI SAP components.