SAP SD_PARTNER_DATA_PUT Function Module for NOTRANSL: set local memory for function group LV09A
SD_PARTNER_DATA_PUT is a standard sd partner data put SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: set local memory for function group LV09A 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 sd partner data put FM, simply by entering the name SD_PARTNER_DATA_PUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: V09A
Program Name: SAPLV09A
Main Program: SAPLV09A
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SD_PARTNER_DATA_PUT 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 'SD_PARTNER_DATA_PUT'"NOTRANSL: set local memory for function group LV09A.
EXPORTING
FIC_OBJECTTYPE = "Object Type
FIC_OBJECTKEY = "Object Key
TABLES
* FRT_XVBPA = "Partner Table
* FRT_YVBPA = "
* FRT_XVBUV = "Incompleteness Log
* FRT_HVBUV = "
* FRT_XVBADR = "Document Addresses
* FRT_YVBADR = "
EXCEPTIONS
NO_OBJECT_SPECIFIED = 1 NO_OBJECT_CREATION_POSSIBLE = 2
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_SAPLV09A_001 Duplicate/Use as a Referene: Decision Making Manual Address
EXIT_SAPLV09A_002 EXIT in NO_KNVV for Partner Type
EXIT_SAPLV09A_003 User Exit Partner Determination (Entry Mode XYZ)
EXIT_SAPLV09A_004 U.Exit for Part. Determ.(before entering determined partner)
IMPORTING Parameters details for SD_PARTNER_DATA_PUT
FIC_OBJECTTYPE - Object Type
Data type: SWO_OBJTYPOptional: No
Call by Reference: No ( called with pass by value option)
FIC_OBJECTKEY - Object Key
Data type: SWO_TYPEIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SD_PARTNER_DATA_PUT
FRT_XVBPA - Partner Table
Data type: VBPAVOptional: Yes
Call by Reference: Yes
FRT_YVBPA -
Data type: VBPAVOptional: Yes
Call by Reference: Yes
FRT_XVBUV - Incompleteness Log
Data type: VBUVVBOptional: Yes
Call by Reference: Yes
FRT_HVBUV -
Data type: VBUVVBOptional: Yes
Call by Reference: Yes
FRT_XVBADR - Document Addresses
Data type: SADRVBOptional: Yes
Call by Reference: Yes
FRT_YVBADR -
Data type: SADRVBOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_OBJECT_SPECIFIED - No objects specified
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_OBJECT_CREATION_POSSIBLE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SD_PARTNER_DATA_PUT 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.DATA: | ||||
lt_frt_xvbpa | TYPE STANDARD TABLE OF VBPAV, " | |||
lv_fic_objecttype | TYPE SWO_OBJTYP, " | |||
lv_no_object_specified | TYPE SWO_OBJTYP, " | |||
lt_frt_yvbpa | TYPE STANDARD TABLE OF VBPAV, " | |||
lv_fic_objectkey | TYPE SWO_TYPEID, " | |||
lv_no_object_creation_possible | TYPE SWO_TYPEID, " | |||
lt_frt_xvbuv | TYPE STANDARD TABLE OF VBUVVB, " | |||
lt_frt_hvbuv | TYPE STANDARD TABLE OF VBUVVB, " | |||
lt_frt_xvbadr | TYPE STANDARD TABLE OF SADRVB, " | |||
lt_frt_yvbadr | TYPE STANDARD TABLE OF SADRVB. " |
  CALL FUNCTION 'SD_PARTNER_DATA_PUT' "NOTRANSL: set local memory for function group LV09A |
EXPORTING | ||
FIC_OBJECTTYPE | = lv_fic_objecttype | |
FIC_OBJECTKEY | = lv_fic_objectkey | |
TABLES | ||
FRT_XVBPA | = lt_frt_xvbpa | |
FRT_YVBPA | = lt_frt_yvbpa | |
FRT_XVBUV | = lt_frt_xvbuv | |
FRT_HVBUV | = lt_frt_hvbuv | |
FRT_XVBADR | = lt_frt_xvbadr | |
FRT_YVBADR | = lt_frt_yvbadr | |
EXCEPTIONS | ||
NO_OBJECT_SPECIFIED = 1 | ||
NO_OBJECT_CREATION_POSSIBLE = 2 | ||
. " SD_PARTNER_DATA_PUT |
ABAP code using 7.40 inline data declarations to call FM SD_PARTNER_DATA_PUT
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