Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ALE (Application Component) ALE Integration Technology⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
| Data Element | EDI_EVENT_ |
| Short Description | Process type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WF_PRC_TP | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | TWFPT |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Proc. type |
| Medium | 15 | Process type |
| Long | 15 | Process type |
| Heading | 11 | Proc. type |
Documentation
Definition
This field contains the process type which determines how the document data is processed, that is which rules control the processing.
Supplementary Documentation - EDI_EVENTN0008
Use
The process type controls the outbound processing, that is the stages an SAP document passes through before it is translated into an Intermediate Document.
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_EVENTN0010
Use
The process determines into which SAP document (e.g. invoice or purchase order) the Intermediate Document is translated and to which application (e.g. purchasing or sales) the data is transferred.
You can enter an ID for the process in the following ways:
- Process type of the workflow from Release 2.1 / 2.2
You have defined the process type with transaction WF02.
- Work item / task of Workflow 3.0
Tasks are defined in the Workflow Workbench 3.0.
- Worflow task of Workflow 3.0
Workflow tasks are defined in the Workflow Workbench 3.0.
- Function module
If you want to call a function module directly (version is 6), this field remains blank. You can then use the process code 'ALED'. The function module which is to be called must be entered in table TBD50 and must comply with the interface specified by ALE (Application Link Enabling).
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_EVENTN0012
Use
The process type controls processing if an error occurs.
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_EVENTT1
Use
Errors can occur in the EDI interface during the following processes:
- inbound processing (receiving Intermediate Documents and converting them to SAP documents)
- outbound processing (converting SAP documents to Intermediate Documents and sending them)
- receiving status records
For each of these situations there is an error process with defined rules which control the processing when an error occurs. If you want to define other processes for error situations, you can define you own error processes.
Procedure
Enter the name of your own error process.
Examples
Dependencies
You need to enter the error process in table TWFPT.
You need to define rules in Workflow Management which determine the procedure when an error occurs.
Supplementary Documentation - EDI_EVENT_0001
Use
For outbound IDoc types, these are business processes in purchasing (MM) and sales (SD).
Procedure
Examples
- Purchase orders in MM
- Order confirmations in SD
Dependencies
Supplementary Documentation - EDI_EVENT_0002
Use
For inbound IDoc types, these are business processes in purchasing (MM) and sales (SD).
Procedure
Examples
- Order confirmation in purchasing
- Purchase orders in sales
Thus the process type controls whether the purchase order has to be checked by the person in charge before it can be further processed or whether the purchase order data is processed further automatically so that it is available in the respective SAP application.
Dependencies
Supplementary Documentation - EDI_EVENT_0012
Use
In the EDI interface, errors can occur during the following processes:
- inbound processing (receiving Intermediate Documents and converting them to SAP documents)
- outbound processing (converting SAP documents to Intermediate Documents and sending them)
- receiving status records
For each of these situations there is an error process, for which rules have been specified and which control the process when errors occur. If you want to specify other processes for these errors, you can define your own error processes.
Procedure
Enter the name of your own error process.
Examples
Dependencies
The error process must already have been entered in table TWFPT.
You should already have specified rules in Workflow Management regarding the procedure to be used when the respective error occurs.
History
| Last changed by/on | SAP | 19970221 |
| SAP Release Created in |
