Use
You can use the IDoc Interface function modules to maintain the partner data automatically. For example, you can add a large number of partners to the database without having to enter the partner data in the system.
Features
The function modules access the four partner profiles tables: EDPP1 (general partner profile), EDP12 (Message Control), EDP13 (outbound parameters) and EDP21 (inbound parameters).
The names of the function modules start with EDI_AGREE. The end of the name describes the relevant database operation.
Function modules for EDPP1 (general partner profile)
Name |
Description |
EDI_AGREE_PARTNER_INSERT |
Inserts new partners. after checking whether: · Partner number exists in the system (for example, master record)? · Partner type is permitted? · Partner status is permitted ("A", "I", or "T")? · Agent type is permitted? · Permitted agents exist? · Test and archive indicators are set? The partner type and number can be copied without being checked. |
EDI_AGREE_PARTNER_UPDATE |
Changes partners. Same checks as EDI_AGREE_PARTNER_INSERT. |
EDI_AGREE_PARTNER_DELETE |
Deletes partners |
EDI_AGREE_PARTNER_READ |
Reads partner data |
Function modules for EDP12 (Message Control)
Name |
Description |
EDI_AGREE_OUT_IDOC_INSERT |
Inserts a new entry. after checking whether:
|
EDI_AGREE_OUT_IDOC_UPDATE |
Changes a line. Same checks as EDI_AGREE_OUT_IDOC_INSERT, exception: Does not check whether the partner exists in EDPP1. |
EDI_AGREE_OUT_IDOC_DELETE |
Deletes a line. |
EDI_AGREE_OUT_IDOC_READ |
Reads a line. |
Function modules for EDP13 (outbound parameters)
Name |
Description |
EDI_AGREE_OUT_MESSTYPE_INSERT |
Inserts a new entry. after checking whether:
|
EDI_AGREE_OUT_MESSTYPE_UPDATE |
Changes a line. Same checks as EDI_AGREE_OUT_MESSTYPE_INSERT, exception: Does not check whether the partner exists in EDPP1. |
EDI_AGREE_OUT_MESSTYPE_DELETE |
Deletes a line. |
EDI_AGREE_OUT_MESSTYPE_READ |
Reads a line. |
Function modules for EDP21 (inbound parameters)
Name |
Description |
EDI_AGREE_IN_MESSTYPE_INSERT |
Inserts a new entry. after checking whether:
|
EDI_AGREE_IN_MESSTYPE_UPDATE |
Changes a line. Same checks as EDI_AGREE_IN_MESSTYPE_INSERT. |
EDI_AGREE_IN_MESSTYPE_DELETE |
Deletes a line. |
EDI_AGREE_IN_MESSTYPE_READ |
Reads a line. |
The following function modules access several tables in the partner profiles:
Other function modules
Name |
Description |
EDI_PARTNER_READ_COMPLETE |
Reads all partner profiles (EDPP1, EDP12, EDP13, EDP21) for a specific partner. |
EDI_PARTNER_DELETE_COMPLETE |
Deletes all partner profiles for a specific partner. |
EDI_PARTNER_COPY_COMPLETE |
Copies all partner profiles of a specific partner. |
EDI_PARTNER_APPL_READ_OUT |
Reads EDP13 for a specific partner. The partner status must be set to "active". |
EDI_PARTNER_READ_OUTGOING |
Reads EDP12 and EDP13 for a specific partner. The partner status must be set to "active". |
EDI_PARTNER_READ_INCOMING |
Reads EDP21 for a specific partner. The partner status must be set to "active". |
EDI_PARTNER_READ_USER_OUTGOING |
Reads permitted agents from EDP13 or EDPP1. |
EDI_PARTNER_READ_USER_INCOMING |
Reads permitted agents from EDP21 or EDPP1. |
EDI_PARTNER_TEST_OUTGOING |
Tests whether a partner is defined for outbound processing. |
EDI_PARTNER_TEST_INCOMING |
Tests whether a partner is defined for inbound processing. |