SAP SD_PARTNER_ATTRIBUTES_SET Function Module for NOTRANSL: Setzt (überschreibt!) die Attribute eine Partners (z.B. Abladess









SD_PARTNER_ATTRIBUTES_SET is a standard sd partner attributes set 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: Setzt (überschreibt!) die Attribute eine Partners (z.B. Abladess 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 attributes set FM, simply by entering the name SD_PARTNER_ATTRIBUTES_SET 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_ATTRIBUTES_SET 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_ATTRIBUTES_SET'"NOTRANSL: Setzt (überschreibt!) die Attribute eine Partners (z.B. Abladess
  EXPORTING
   FIC_OBJECTTYPE =  "Object Type
   FIC_OBJECTKEY =  "Object Key
   FIF_PARVW =  "Partner Role
   FIF_POSNR =  "Item Number
   FIF_PARNR =  "Partner Number
   FIS_ATTRIBUTES =  "Attributes

EXCEPTIONS
   PARAMETER_INCOMPLETE = 1    OBJECT_NOT_FOUND = 2    PARTNER_NOT_FOUND = 3    CHANGE_NOT_POSSIBLE = 4
.




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_ATTRIBUTES_SET

FIC_OBJECTTYPE - Object Type

Data type: SWO_OBJTYP
Optional: No
Call by Reference: Yes

FIC_OBJECTKEY - Object Key

Data type: SWO_TYPEID
Optional: No
Call by Reference: Yes

FIF_PARVW - Partner Role

Data type: PARVW_4
Optional: No
Call by Reference: Yes

FIF_POSNR - Item Number

Data type: POSNR
Optional: No
Call by Reference: Yes

FIF_PARNR - Partner Number

Data type: SD_PARTNER_PARNR
Optional: No
Call by Reference: Yes

FIS_ATTRIBUTES - Attributes

Data type: SDPARTNER_ATTRIBUTES
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PARAMETER_INCOMPLETE -

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

OBJECT_NOT_FOUND -

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

PARTNER_NOT_FOUND -

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

CHANGE_NOT_POSSIBLE -

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

Copy and paste ABAP code example for SD_PARTNER_ATTRIBUTES_SET 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:
lv_fic_objecttype  TYPE SWO_OBJTYP, "   
lv_parameter_incomplete  TYPE SWO_OBJTYP, "   
lv_fic_objectkey  TYPE SWO_TYPEID, "   
lv_object_not_found  TYPE SWO_TYPEID, "   
lv_fif_parvw  TYPE PARVW_4, "   
lv_partner_not_found  TYPE PARVW_4, "   
lv_fif_posnr  TYPE POSNR, "   
lv_change_not_possible  TYPE POSNR, "   
lv_fif_parnr  TYPE SD_PARTNER_PARNR, "   
lv_fis_attributes  TYPE SDPARTNER_ATTRIBUTES. "   

  CALL FUNCTION 'SD_PARTNER_ATTRIBUTES_SET'  "NOTRANSL: Setzt (überschreibt!) die Attribute eine Partners (z.B. Abladess
    EXPORTING
         FIC_OBJECTTYPE = lv_fic_objecttype
         FIC_OBJECTKEY = lv_fic_objectkey
         FIF_PARVW = lv_fif_parvw
         FIF_POSNR = lv_fif_posnr
         FIF_PARNR = lv_fif_parnr
         FIS_ATTRIBUTES = lv_fis_attributes
    EXCEPTIONS
        PARAMETER_INCOMPLETE = 1
        OBJECT_NOT_FOUND = 2
        PARTNER_NOT_FOUND = 3
        CHANGE_NOT_POSSIBLE = 4
. " SD_PARTNER_ATTRIBUTES_SET




ABAP code using 7.40 inline data declarations to call FM SD_PARTNER_ATTRIBUTES_SET

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!