Gateway Work Process SMGW

SMGW is used to monitor the gateway process. Gateway is used to communicate between SAP and NON-SAP systems. There will be only 1 gateway/ instance. If required we can also install a standalone gateway on a JAVA engine.

Gateway listens on port ’3300′+instance number (3300, 3301,3302 where 01, 02 are the instances).

Gateway provides an interface so that the external system can communicate with SAP system on the specified port.

When RFC’s are defined between the systems they use SAP gateway when (ALE, EDI, IDOC are transferring they use gateway)

If you like this post, you may as well like these too:

1. Types of Work Processes Even though the Work processes are unique at OS level SAP differentiated between the work processes based on the nature of work. The process are determined by the instance name...
2. ABAP Programs: Using an alternative work area REPORT ZSOURCE1102.* Work area for a database tableTABLES CUSTOMERS.* alternative work areaDATA MY_CUSTOMER LIKE CUSTOMERS.* Reading all entries of the database tableSELECT * FROM CUSTOMERS INTO MY_CUSTOMER. WRITE: / MY_CUSTOMER-NAME.ENDSELECT....
3. Capital Work in Progress and Assets Capital WIP is referred to as Assets under Construction in SAP and are represented by a specific Asset class. Usually depreciation is not charged on Capital WIP. All costs incurred...
4. ABAP: How to create a dynamic internal table and work area FIELD-SYMBOLS:<fs_table> TYPE STANDARD TABLE, <fs_table_wa> TYPE ANY. DATA: table_ref TYPE REF TO data, wa_ref TYPE REF TO data. DATA: l_structure TYPE dd02l-tabname value 'VBAP'.   CREATE DATA table_ref TYPE STANDARD...