Currently the integration framework is capable of updating external records in two ways in either ‘Create’ mode or ‘Update’ mode, these ‘modes’ are known within the integration framework as process codes and to try and ensure forwards compatibility these have been made configurable but would obviously require code changes if any other process codes were to become available. These process codes are held in table ‘/BTI/TE_INT_PC’. These two process codes would need to be shipped for standard functionality.
SM30
| /BTI/TE_INT_PC – Process Codes | |
|---|---|
| Field | Description |
| PROCESS_CODE | The process codes used by the integration framework to perform some kind of action. The framework gets shipped with two standard process codes CREATE and UPDATE. |
| CODE_DESCRIPTION | Description of above code. |
| ACTION_CLASS | The class specified is only used by the polling process, and must implement /BTI/TE_IF_INTEGRATION_ACTION |
This existed already, but has a new field INBOUNDACTIONCLASS.
The class specified is only used by the polling process, and must implement /BTI/TE_IF_INTEGRATION_ACTION
| Record | Action Class |
|---|---|
| CREATE – Create integration record | /BTI/TE_CL_INTEGR_CREATE |
| TESTERS – Testing complete | /BTI/TE_CL_INTEGR_TESTERS |
| UPDATE – Update integration record | /BTI/TE_CL_INTEGR_UPDATE |
| TRANSITION > State transition | N/A |
Post your comment on this topic.