Sample Files and Coding Techniques
BEA WebLogic Adapter for SAP User’s Guide D-9
<E1KNVPM SEGMENT="1">
<MSGFN>005</MSGFN>
<PARVW>WE</PARVW>
<KUNN2>0000000001</KUNN2>
<DEFPA></DEFPA>
<KNREF></KNREF>
<PARZA>000</PARZA>
</E1KNVPM>
<E1KNVIM SEGMENT="1">
<MSGFN>005</MSGFN>
<ALAND>DE</ALAND>
<TATYP>MWST</TATYP>
<TAXKD>0</TAXKD>
</E1KNVIM>
</E1KNVVM>
</E1KNA1M>
</IDOC>
</DEBMAS01
Collected IDocs
When using collected IDocs on any platform during inbound processing (service mode), if
the DOCNUM field does not have a unique document number for each IDoc, the system
creates an IDoc for each header record in the collected IDoc file and duplicates the data for
each IDoc.
Make sure the DOCNUM field is included in the EDI_DC40 structure and that each IDoc has
a unique sequence number within the collected IDoc file.
Sample RFC Module
After you have configured the SAP event adapter and the RFC destination, you can write
ABAP code to execute calls at your new destination (the event adapter).
The following sample code uses a user-defined RFC module named Z_EVENT_DISPATCH.
FUNCTION Z_01_EVENT_DISPATCH.
CALL FUNCTION 'Z_EVENT_DISPATCH'
DESTINATION 'IWAYDEST'
EXPORTING
EVENT = EVENT
RECTYPE = RECTYPE
OBJTYPE = OBJTYPE
OBJKEY = OBJKEY
TABLES
EVENT_CONTAINER = EVENT_CONTAINER.
ENDFUNCTION.
To Next Page
Loading...