regarding Process code

[Former Member]

Hi,

Is there any difference in the process code saving and message type saving?

as customized and workbench?

Thanks

Manju

[Former Member]

Hi Avinash,

Process code will be linked to the Message type and the IDOC type.

<b>Process codes</b>.

Process codes are used in ALE and EDI to identify the function module or API to be invoked for subsequent processing. An inbound interface uses a process code to determine the application module that will process the inbound IDOC to an SAP application object such as a sales (Customer) order (process code — ORDE), Material Master record (MATM), or a shipment (SHIP). An outbound interface uses process codes only in the case of applications that use message control (which I’ll get to shortly). In this case, the process code identifies the application module that populates the IDOC with application data. Each process code is associated with a message type. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.

Use transaction WE41 to display outbound process codes and WE42 to display inbound codes, or from WEDI select Control -> Outbound Process Codes/Inbound Process Codes, or from ALE customizing SALE select Extensions -> Outbound -> Maintain Process Code, or Extensions -> Inbound -> Maintain Process Code.

Regards

KER

[Former Member]

hi eswar,

i mean, why we will store Process code under Customizing request and other in workbench request

thanks

Avi

[Former Member]

Hi,

Message type can be saved in Workbench request, where as Process code can saved under customizing request.

Thanks

Beedam