The ALE/EDI layer is responsible for creating the IDoc in the SAP database.

By n
ow, a tangible
IDoc that can be viewed using the various monitoring tools has been created in t
he system. The
IDoc gets a status record with a status code of 01 (IDoc Created).
The IDoc, before being saved in the database, goes through a syntax check and ot
her
validations. If there are no errors, the IDoc gets a status of 30 (IDoc Ready fo
r Dispatch to ALE
Service).
pass the IDoc to the operating system layerOutput Mode
fields in the partner profile are read to determine the timing of this step, and
the port definition is
read to determine the directory location in which the file will be created.RSEOU
T00 03 (Data Passed to Port OK
between the IDoc type, message type, and function
module for the inbound process is maintained in the EDIFCT table.
The ALE/EDI layer creates an
application IDoc in the database IDoc gets a status code of 50 (IDoc
added). If the IDoc passed the syntax check process earlier, it gets a status co
de of 64 (IDoc
ready to be passed to application)
transaction BD51 table TBD51 1 call transaction 0 function module 53
(Application document posted). If errors occur, the IDoc gets a status code of 5
1 (Application
document not posted).
OYSN Number ranges
we46 inbound setting partner profile
function RFC_REMOTE_EXEC
RFC destination (SERVER_EXEC
Port
Function
Transactional RFC Used for ALE communication
File Used by EDI
CPI-C Used to communicate with an R/2 system
Internet Used to connect with Internet applications
ABAP-PI Used for custom IDoc processing via ABAP programming
interface
EDI_DATA_INCOMING
EDI_STATUS_INCOMING
startrfc -3 d <system id> -u <userid> -p <password> -c <client> -l <language> -h
<App. Server>
-s <system number> -g <gateway host> -x <gateway services> -t E <file name> -E <p
ort name>
-F <function module name>
?? -3. Indicates the script is to log on to the R/3 system.
?? system id. The three-character identifier assigned to your SAP instance. You
determine
this by looking at the status bar on your SAP screen. You can also execute trans
action SM51
to determine the instance ID. The instance ID comprises the two characters follo
wing the
underscore.
?? userid. The ID used to log on to the SAP system. This user should be a backgr
ound user
or a CPIC user. This ID has SAPALL permission.
?? password. The password for the logon ID used to log on to the system.
?? client. The SAP client.
?? language. The language of the logon ID.
?? App. Server. The server to which the user will log on in order to connect to
the SAP

system.
?? system number. The two-digit system number. Use SM51 to display the applicati
on
servers. The last two digits in the application server name provide the value fo
r the system
number.
?? gateway host. The name of the host on which the gateway service programs are
executing. The gateway host is used for all RFC communications that use CPIC
communications behind the scenes. In a simple installation, this entry is the na
me of the
application server host, but you can install the gateway services separately. Ch
eck with your
Basis staff for the gateway server.
?? gateway services. Gateway services as defined in the services file at the OS
level. From
within SAP, you execute program RSPARAM and, on the output screen, look for an e
ntry
The General Parameters view. Values are stored in table EDPP1.
?? The Outbound Parameters view. Values are stored in table EDP13, except for th
e
Message control parameters, which are stored in table EDP12.
?? The Inbound Parameters view. Values are stored in table EDP21
RSECHK07 partner profile