In this scenario we have a file in XML Message Type format as sender that will be converted in a MATMAS.MATMAS05 IDoc as receiver in ECC.
In setup activity are involved several environments: SAP ECC, SAP PI Configuration and Repository, Netweaver Administrator (NWA) and System Landscape Directory (SLD).
Setup ECC side
Here we enable the COMPANY_A partner to receive a MATMAS IDoc.
[BD64] Distribution Model
![Distribution model for MATMAS](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img29.png)
Distribution model for MATMAS
[WE20] Partner Profile
![Partner profile for COMPANY_A](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img30.png)
Partner profile for COMPANY_A
![Detail for partner profile for COMPANY_A and MATMAS IDoc in inbound](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img31.png)
Detail for partner profile for COMPANY_A and MATMAS IDoc in inbound
Setup SAP PI Configuration side
Here we define the channels enabling the protocols to read from a file and to write and send an IDoc to ECC. Furthermore we define the routing from the sender to the receiver and the transformation from the file structure format to the IDoc one.
![Configuration scenario overview](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img1.png)
Configuration scenario overview
Communication Channel sender
![File sender communication channel: Source tab](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img2.png)
File sender communication channel: Source tab
Communication Channel name | File_to_Idoc_Sender_00_A |
Filename | file_idoc_00.xml ![]() |
![File sender communication channel: Processing tab](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img3.png)
File sender communication channel: Processing tab
![File sender communication channel: Advanced tab](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img4.png)
File sender communication channel: Advanced tab
Communication Channel receiver
![IDoc receiver communication channel](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img5.png)
IDoc receiver communication channel
We can set up the ECC references by a destination instead of inside to the channel.
Interface determination
![Interface Determination](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img6.png)
Interface Determination
Setup Netweaver Administration side
Destinations
![Netweaver Administration Configuration page](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img7.png)
Netweaver Administration Configuration page
![Netweaver Administration: Destination definition](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img8.png)
Netweaver Administration: Destination definition
Defining a destination allow you to ping the destination before to define the communication channel.
Setup Repository side
Message Mapping
Control Record mapping
![MT_Material vs MATMAS: control record mapping overview](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img12.png)
MT_Material vs MATMAS: control record mapping overview
![]() |
IDoc type: according on Partner profile |
![]() |
Message type: according on Partner Profile |
![]() |
Sender SAP Port: according on rule: “SAP”+System ID |
![]() |
Sender Partner type: Logical System, according on Partner Profile |
![]() |
Receiver SAP Port: according on rule: “SAP”+System ID |
![]() |
Receiver Partner type: Logical System |
![]() |
Receiver Partner: ECC System ID |
Coupling Business System – Logical System
![Adapter-Specific Identifiers](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img10.png)
Adapter-Specific Identifiers
![System Landscape Directory: Business System definition](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img9.png)
System Landscape Directory: Business System definition
![]() |
|
![]() |
|
![]() |
![Fixed-Values table](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img25.png)
Fixed-Values table
![Conversion from MaterialID to MATNR supported by UDF](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img23.png)
Conversion from MaterialID to MATNR supported by UDF
![MT_Material vs MATMAS: payload mapping overview](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img21.png)
MT_Material vs MATMAS: payload mapping overview
![Operation mapping](https://www.nick4name.eu/wp-content/uploads/2016/09/fileidoc_img11.png)
Operation mapping