The ALE/EDI layer is responsible for creating the IDoc in the SAP database. By now, a tangible IDoc that can be viewed using the various monitoring tools has been created in the system. TheIDoc 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 othervalidations. If there are no errors, the IDoc gets a status of 30 (IDoc Ready for Dispatch to ALEService).pass the IDoc to the operating system layerOutput Modefields in the partner profile are read to determine the timing of this step, and the port definition isread to determine the directory location in which the file will be created.RSEOUT00 03 (Data Passed to Port OKbetween the IDoc type, message type, and functionmodule for the inbound process is maintained in the EDIFCT table.The ALE/EDI layer creates anapplication IDoc in the database IDoc gets a status code of 50 (IDocadded). If the IDoc passed the syntax check process earlier, it gets a status code of 64 (IDocready 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 51 (Applicationdocument not posted).OYSN Number rangeswe46 inbound setting partner profilefunction RFC_REMOTE_EXECRFC destination (SERVER_EXEC Port FunctionTransactional RFC Used for ALE communicationFile Used by EDICPI-C Used to communicate with an R/2 systemInternet Used to connect with Internet applicationsABAP-PI Used for custom IDoc processing via ABAP programminginterfaceEDI_DATA_INCOMINGEDI_STATUS_INCOMINGstartrfc -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 <port 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 determinethis by looking at the status bar on your SAP screen. You can also execute transaction SM51to determine the instance ID. The instance ID comprises the two characters following theunderscore.?? userid. The ID used to log on to the SAP system. This user should be a background useror 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 applicationservers. The last two digits in the application server name provide the value for the systemnumber.?? gateway host. The name of the host on which the gateway service programs areexecuting. The gateway host is used for all RFC communications that use CPICcommunications behind the scenes. In a simple installation, this entry is the name of theapplication server host, but you can install the gateway services separately. Check with yourBasis staff for the gateway server.?? gateway services. Gateway services as defined in the services file at the OS level. Fromwithin SAP, you execute program RSPARAM and, on the output screen, look for an entry

The General Parameters view. Values are stored in table EDPP1.?? The Outbound Parameters view. Values are stored in table EDP13, except for theMessage control parameters, which are stored in table EDP12.?? The Inbound Parameters view. Values are stored in table EDP21

RSECHK07 partner profile