SAP EDI_AGREE_PARTNER_UPDATE Function Module for Change partner in EDPP1

Search SAP Function Modules

EDI_AGREE_PARTNER_UPDATE is a standard edi agree partner update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change partner in EDPP1 processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for edi agree partner update FM, simply by entering the name EDI_AGREE_PARTNER_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: EDI6
Program Name: SAPLEDI6
Main Program: SAPLEDI6
Appliation area: S
Release date: 11-Dec-1995
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EDI_AGREE_PARTNER_UPDATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'EDI_AGREE_PARTNER_UPDATE'"Change partner in EDPP1
  EXPORTING
   REC_EDPP1 =  "Entry to Be Changed for EDPP1
*  NO_PTYPE_CHECK = ' ' "'X': No Partner Type Check

EXCEPTIONS
   DB_ERROR = 1    ENTRY_NOT_EXIST = 2    PARAMETER_ERROR = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEDI6_001 CA-EDI, Partner IDoc: Exit after Segment E1EDPP1
EXIT_SAPLEDI6_002 CA-EDI, Partner IDoc: Exit After Segment E1ADRM0
EXIT_SAPLEDI6_003 CA-EDI, Partner IDoc: Final Exit Before Sending
EXIT_SAPLEDI6_004 CA-EDI, Partner IDoc: Exit after Segment E1ADRP0
EXIT_SAPLEDI6_005 CA-EDI, Partner IDoc: Exit after Segment E1ADRE0
EXIT_SAPLEDI6_007 CA-EDI, Partner IDoc: Exit after Segment E1EDP13
EXIT_SAPLEDI6_008 CA-EDI, Partner IDoc: Exit after Segment E1EDP21

IMPORTING Parameters details for EDI_AGREE_PARTNER_UPDATE

REC_EDPP1 - Entry to Be Changed for EDPP1

Data type: EDPP1
Optional: No
Call by Reference: No ( called with pass by value option)

NO_PTYPE_CHECK - 'X': No Partner Type Check

Data type: EDI_HELP-ERROR_FLAG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

DB_ERROR - Database Error During Modification

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ENTRY_NOT_EXIST - Entry Does not Exist in Table

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARAMETER_ERROR - Parameters Are Set Incorrectly

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EDI_AGREE_PARTNER_UPDATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM EDI_AGREE_PARTNER_UPDATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects