Inbound Setup Procedure

Link SAP to Translator
Define logical system, etc. if you're connecting to your translator via ALE.
Create an RFC Destination if your translator can be directly triggered by SAP or vice-versa. This is typically a Basis function.
Create a port over which SAP and your translator will exchange documents (see the translator page for more information on ports)

Translate external partner numbers to internal partner numbers on a sold-to partner basis. The input to this table is the sold-to partner number (E1EDKA1-AG.PARTN), partner type E1EDKA1.PARVW, and external partner number E1EDKA1.PARTN. Note: If you will provide the SAP partner number on E1EDKA1.PARTN, there's no need to populate this table.
Some work will also be required on your translator's system to either:

1. Implement a schedule for your translator to pick-up and drop-off documents at the port (if remote triggering will not be used and the port is of type FILE or XML)

2. Setup a script to initiate translation when invoked by SAP via RFC (if remote triggering will be used and the port is of type FILE or XML)

3. Some configuration to configure the tool for ALE (if ALE tRFCs will be used to communicate)
For each inbound EDI message
Determine the process code and then the logical message types you'll be using. (if you can't find one, you may need to do some custom development)
Determine which IDoc type you'll feed to this function module
Within your translator, work will be needed to:

1. Define the structure of the IDoc selected

2. Define mappings to translate business partner documents to this structure. If you find gaps where SAP does not provide the needed fields or functionality, you will need to extend SAP's standard offering.
Setup Partners and Partner Messages
Create/update organizational settings for managing EDI-related workflow tasks
Define your business partners, which transactions you will receive from them, and whom SAP should handle problems when they occur.

Define the sales areas (sales org, distribution channel, division) for inbound orders for each sold-to -- the real sold-to (i.e., from EDPAR), not the WE20 customer. This table is consulted if sales area information is not provided in the IDoc's E1EDK14 segments. However, if you specify a sales document type here, it will override any sales order type you specify on the IDoc's K01 segment.