IDoc trigger
The IDoc trigger will be used if the OPC Router should receive an IDoc from the SAP system. SAP system will trigger the transfer through this object. SAP configuration is described as overview. Please consult you SAP manual.
Properties are:
| SAP access data | Set of SAP access data. |
|---|---|
| SAP access data | SAP connection via which the relevant function is accessed. |
| IDoc type | Type of IDoc the Trigger listens. Must be the same as in corresponding transfer object. |
| IDoc Enhancement | Class extension of the IDocs. |
| Program ID | Program ID used by SAP system to call destination, identical with program ID of transaction SM59. |
| Gateway Service | Gateway Service of SAP system |
| Output | Set this field if you want to receive an output as JSON. |
Important: Program ID and function have to be written in CAPITALS. The combination of host, gateway and program ID has to be unique. From version 3.1.1.5 you can use the program ID several times provided gateway-service and/or hosts differ.
Important: If an IDoc is updated/changed in SAP, the trigger must also be adapted to the new IDoc.
Example
IDoc Trigger Settings:
| SAP access data | <SAP access data> |
| IDoc Type | PROCESSORDER |
| Program ID | INRAYTRIGGER |
| Gateway Service | Gateway Service of SAP system, e. g. 3302 |
Logical System within SAP transaction BD54:
| LogSystem | OPCRIDOC01 |
| Description | OPC Router with IDoc listener |
Corresponding SAP Settings, SM59:
| Destination | OPCROUTER |
| Connection Type | T TCP/IP |
| Activation Type | Registered Server Program |
| Program ID | INRAYTRIGGER |
| Gateway host | (no entry!) |
| Gateway service | (no entry!) |
Communication Port in transaction WE21:
| (Type) | Transactional RFC |
| Port | e.g. IDOCPORT |
| Version | (select appropriated IDoc version) |
| RFC destination | OPCROUTER |
Partner profile in transaction WE20
| (Partner type) | LS (Logical System) |
| Partner no. | OPCRIDOC01 |
Outbound parameters in WE20:
| Receiver Port | IDOCPORT |
| Outpout mode | Transfer IDoc immed. |
| IDoc Type/Basic type | PROCESSORDER |
| Cancel processing after syntax error | (activated) |
For testing, via WE19 an IDoc can be send manually providing partner no. and Port. Errors might be found in WE07. Function to call is IDOC_INBOUND_ASYNCHRONOS (as of 4.0), resp. INBOUND_IDOC_PROCESS (before 3.x).