X hits on this document

359 views

0 shares

1 downloads

0 comments

101 / 131

Work Schema: <undefined>; this path is left blank, as data files are never accessed directly from the FTP server's file system.

Please note that data files will be downloaded to the ODI Agent. The default directory for download is the system's temp directory. On UNIX this is usually /tmp and on Windows c:\Documents and Settings\<user>\Local Settings\Temp. This directory can be overriden by setting redefining the KM option TEMP_DIR.

Controling ABAP Uploading in Development and in Production

During development, ABAP code is uploaded to the SAP system with every interface execution. This upload can be explicitely turned off by setting the LKM option UPLOAD_ABAP_CODE to No.

Once an Interface or Package has been unit tested and is ready to be migrated out of the development environment, ODI should no longer upload ABAP code, as the ABAP code will be transported by SAP's CTS (Change and Transport System).

Alternatively, the upload can be turned off using the FlexField SAP Allow ABAP Upload defined on the SAP data server in the Topology: The ABAP code is only uploaded, if the LKM option UPLOAD_ABAP_CODE and the Flexfield SAP Allow ABAPUpload are both set to Yes. So for disabling upload for non-development systems the user must set the Flexfield SAP Allow ABAPUpload to 0 in Topology.

Note: Before starting the extraction process, ODI verifies that the interface/scenario matches the code installed in SAP. Otherwise an exception is thrown.

Log Files

During the RKM and LKM execution several log files are created. These log files may contain valuable details for troubleshooting.The list below describes the different log files and their usage:

KM / Phase

Content

RKM

Execution Log of metadata retrieval

RKM

Information about first time installation of SAP RFC for RKM

LKM – Generation Time

Information about code generation for ABAP extractor.

LKM - Runtime

Information about installation of ABAP extractor.

LKM – Runtime

SQLLDR log file

LKM – Runtime

OS std output during SQLLDR execution, may contain information, e.g. when SQLLDR is not installed

LKM - Runtime

OS error output during SQLLDR execution, may contain information, e.g. when SQLLDR is

Default Log File Name

<System Temp Dir>/sap rkm erp <ODI Session Number>.log _ _ _

<System Temp Dir>/sap_rkm_erp_<ODI Session Number>.log.opentool.log

<System Temp Dir>/ODI <Interface Id>_<SrcSet>.genlog _

<System Temp Dir>SAPAbapExecuteOpenTool_<Interface Id>.log <System Temp Dir or local FTP dir>/ ZODI_<Interface Id>_<SrcSet>_<Context>.log <System Temp Dir or local FTP dir>/ ZODI_<Interface Id>_<SrcSet>_<Context>.out

<System Temp Dir or local FTP dir>/ ZODI_<Interface Id>_<SrcSet>_<Context>.err

Knowledge Modules Reference Guide

101/131

Document info
Document views359
Page views362
Page last viewedMon Dec 05 15:18:38 UTC 2016
Pages131
Paragraphs3942
Words42855

Comments