Sybase Adapter for SAP R/3 User Manual
Converting IDoc Formats
12
Adapter for SAP R/3
•
The conversion tool can only convert one format at a time, so each export
file must contain only one top-level format. (For example,
SAP.OC.DEBMAS04)
file must contain only one top-level format. (For example,
SAP.OC.DEBMAS04)
•
The easiest way to provide the information necessary for a user to log into
the SAP system is to use a functioning configuration file for the inbound
IDoc process. The value of SAPInConfig key should be the name of this
file. (For example, the Schema mode configuration file used to load the
IDoc with Version 3.9. It should be in the SAP-3_9/bin folder.)
the SAP system is to use a functioning configuration file for the inbound
IDoc process. The value of SAPInConfig key should be the name of this
file. (For example, the Schema mode configuration file used to load the
IDoc with Version 3.9. It should be in the SAP-3_9/bin folder.)
•
The saprfc.ini file is required. The file is in the location pointed to by the
RFC_INI environment variable.
RFC_INI environment variable.
•
The log file created by running the conversion tool reports errors and
conversion information. The conversion information is a summary of error
messages and a list of items that have been converted. It should indicate
that some field mappings were preserved; for example, see the log file at
the end of this section (sample log for a run of the conversion tool that
preserves mappings).
conversion information. The conversion information is a summary of error
messages and a list of items that have been converted. It should indicate
that some field mappings were preserved; for example, see the log file at
the end of this section (sample log for a run of the conversion tool that
preserves mappings).
•
The import of the format generated by the conversion tool should use the
-g option to ignore the conflicts that are reported when the same
components are loaded in multiple converted format files. For example,
the Input/Output Control “SAP.Length.3” or the control for some other
length value may exist in multiple format definitions. The definitions are
identical, so there is no need to reload the component. The NNFie.log
reports instances that were ignored.
-g option to ignore the conflicts that are reported when the same
components are loaded in multiple converted format files. For example,
the Input/Output Control “SAP.Length.3” or the control for some other
length value may exist in multiple format definitions. The definitions are
identical, so there is no need to reload the component. The NNFie.log
reports instances that were ignored.
Example Conversion Tool Configuration File
#--------------------------------------------------
# File Name: ConvTool.cfg
# Sample configuration file for running the IDoc
# format conversion tool.
# The format of this file is important. Session names
# MUST begin at the beginning of the line, the
# associated keys MUST be below the session name
# and indented by spaces or tabs. Comments are
# preceded by #.
#--------------------------------------------------
NNConv
# name of original format as seen in formatter