All steps can also be found under transaction /nSALE

A number range for the IDOCs must be created with trans. SNRO before any IDOCs can be sent/received

A number range for the ports must also be created with trans. SNUM before a port can be created.

1. Define logical system

Add the relevant logical systems to list. This is simply a logical name to be determined by you. Normally there is a default logical system name for each client, so this may already be defined, meaning you only have to create a logical system name for your subsystem.

To determine what the default name for your client is use transaction SCC4. Double click on your client number to see the logical name associated with it.

2. Define message types

Transaction: BD64

Enter the logical system which you created (or if it was already created, the one you found using transaction SCC4) in 1 above for your Client.

Enter the customer model. (If you don’t know what this is then choose SUBSYSTEMS)

Choose Execute

Select the Logical System added for the Subsystem(SHIPCO)

Create message type and transfer the following message types:

WMBBIN, WMCATO, WMINFO, WMINVE, WMMBXY, WMRREF, WMSUMO, WMTOCO, WMTORD, WMTREQ.

3. Define RFC destination

3.1 destination definition

Transaction: SM59

Place cursor on TCP/IP connection and click Create

3.1.1 give the destination a name. (SHIPCO)

connection type: T for TCP/IP

3.1.2 Hit enter button to bring you to the technical settings screen.

3.1.3 Choose "sh_srv1.shp_reg" as the Program ID. This is the ID used by Loglink to register itself with SAP

menu path: (from within destination definition transaction) Destination -> tRFC options

here you can specify if a tRFC call should be repeated if there is a connection error, how many times the call should be retried, and the interval between calls.

4. Define port

Transaction: we21

Place cursor on transactional RFC and choose create.

Choose new entries. The SAP system will create the port number, you must just add port description and logical destination (this logical destination is the name of the RFC destination you created in number 3 above)

5.1 partner definition

Partner number should be the logical system name defined in 1 above for the receiving partner (subsystem). Partner type is LS for logical system. Click on create (or change to add a partner profile for an already existing partner)

partner status: A

note: the port is the one defined above. You can choose to have the ALE service transfer the IDOCS immediately to the subsystem, or collect the IDOCS until a specific number or packet size has been reached. In the second case the entire packet of IDOCS will be transferred in one tRFC call. The receiver of notifications can be an R/3 user or group. The remaining outbound options are not relevant.

note: You can choose to have the IDOCS sent to the application by the ALE service immediately, or you can choose to collect the IDOCS and manually trigger processing. The receiver of notifications can be an R/3 user or group. The remaining inbound options are not relevant.

define ALE link

menu path: Tools -> customizing / materials management -> warehouse management -> interfaces -> subsystems -> define ALE link

INTERFACE CONTROL :

WHSE SrcTy DestTyp Mvmt SeqNo

CFG *** STG 601 0

Here add all the Source Storage Types from which material will be PICKED

Function Modules for IDOC processing:

WMCATO L_IDOC_CREATE_WMCAID01

WMINVE L_IDOC_CREATE_WMINVID01

WMRREF L_IDOC_CREATE_WMRRID01

WMTORD L_IDOC_CREATE_WMTOID01

WMTOCO L_IDOC_INPUT_WMTOCO

many of the activities here are repeats of the configuration done above.

Of specific interest are:

1.1activate interface per warehouse number: Enter relevant warehouse and communication method (Communication Method is 1)

1.2 interface control: enter warehouse number, movement parameters, and relevant subsystem.

1.3 function modules for IDOC creation: Enter the relevant function module to be triggered for IDOC creation for the WM related outbound IDOCS defined in step 5 above.