Example Log File; Adjusting For Customization; Suggestions For Converting Idocs - Sybase Adapter for SAP R/3 Installation Manual

Example Log File

Adjusting for Customization

Suggestions for Converting IDocs

Installation Guide
CHAPTER 1
Source Control Record: SAP.OF.ABSEN1.CR
Destination Control Record: SAP.OF.ABSEN1.CR
Source Segment Name: SAP.OF.E2ABSE1
Destination Segment Name: SAP.OF.E2ABSE1
Field: SAP.E2ABSE1.BDEGROutMap: InMap: LEG.F1
Field: SAP.E2ABSE1.MOABWOutMap: InMap: LEG.F2
Field: SAP.E2ABSE1.ZEITYOutMap: InMap: LEG.F3
Field: SAP.E2ABSE1.AGRUNOutMap: InMap: LEG.F4
Field: SAP.E2ABSE1.BEGDAOutMap: InMap: LEG.F5
Field: SAP.E2ABSE1.ENDDAOutMap: InMap: LEG.F6
Field: SAP.E2ABSE1.ATEXTOutMap: InMap: LEG.F7
Make sure that the new format contains the correct default values for control
records. (Default values in control records are optional.) The conversion tool
transfers user-defined values and mappings, but it does not transfer default
values.
If the original format specified default values for the partner profile fields
Note
of the control record, then you must manually set the values to those literals.
This applies to the literals named SAP.<IDOC TYPE>.* where * is one of the
following: RCVPOR, RCVPRN, RCVPRT, SNDPOR, SNDPRN, SNDPRT.
• Use descriptive names for the format export files.
• NNFie for 4.x uses the sqlsvses.cfg file, NNFie for 5.x uses the NNFie.cfg
in the local directory (if one was created) or it searches for a copy of
nnsyreg.dat file. The example commands assume the session name is
nnfie.
• Use the which command to be sure that the expected version of nnfie.exe
is being referenced.
Migrating to Adapter for SAP R/3 Version 3.9
11