SAP OBJECT_ASSIGN_S Function Module for NOTRANSL: Laden/Sichern von Objektdaten in globaler Memory
OBJECT_ASSIGN_S is a standard object assign s 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: Laden/Sichern von Objektdaten in globaler Memory 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 object assign s FM, simply by entering the name OBJECT_ASSIGN_S into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVAZ
Program Name: SAPLFVAZ
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function OBJECT_ASSIGN_S 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 'OBJECT_ASSIGN_S'"NOTRANSL: Laden/Sichern von Objektdaten in globaler Memory.
EXPORTING
* FLG_SAVE_IN_UPDT = ' ' "
FUNCTION = "
OBJNR = "Object number (virtual object)
* SANO1_NEW = ' ' "Address-object relationship
* SANS1_NEW = ' ' "Address table
IMPORTING
FLG_FIRST_LOAD = "
SANO1_OLD = "Address-object relationship
SANS1_OLD = "Address table
TABLES
* VZPARUS_TAB = "User data central partner and address management
EXCEPTIONS
ERROR = 1 OBJECT_NOT_FOUND = 2
IMPORTING Parameters details for OBJECT_ASSIGN_S
FLG_SAVE_IN_UPDT -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
FUNCTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJNR - Object number (virtual object)
Data type: SANO1-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
SANO1_NEW - Address-object relationship
Data type: SANO1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SANS1_NEW - Address table
Data type: SANS1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OBJECT_ASSIGN_S
FLG_FIRST_LOAD -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SANO1_OLD - Address-object relationship
Data type: SANO1Optional: No
Call by Reference: No ( called with pass by value option)
SANS1_OLD - Address table
Data type: SANS1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OBJECT_ASSIGN_S
VZPARUS_TAB - User data central partner and address management
Data type: VZPARUSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR -
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)
Copy and paste ABAP code example for OBJECT_ASSIGN_S 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_error | TYPE STRING, " | |||
lt_vzparus_tab | TYPE STANDARD TABLE OF VZPARUS, " | |||
lv_flg_first_load | TYPE VZPARUS, " | |||
lv_flg_save_in_updt | TYPE VZPARUS, " SPACE | |||
lv_function | TYPE VZPARUS, " | |||
lv_sano1_old | TYPE SANO1, " | |||
lv_object_not_found | TYPE SANO1, " | |||
lv_objnr | TYPE SANO1-OBJNR, " | |||
lv_sans1_old | TYPE SANS1, " | |||
lv_sano1_new | TYPE SANO1, " SPACE | |||
lv_sans1_new | TYPE SANS1. " SPACE |
  CALL FUNCTION 'OBJECT_ASSIGN_S' "NOTRANSL: Laden/Sichern von Objektdaten in globaler Memory |
EXPORTING | ||
FLG_SAVE_IN_UPDT | = lv_flg_save_in_updt | |
FUNCTION | = lv_function | |
OBJNR | = lv_objnr | |
SANO1_NEW | = lv_sano1_new | |
SANS1_NEW | = lv_sans1_new | |
IMPORTING | ||
FLG_FIRST_LOAD | = lv_flg_first_load | |
SANO1_OLD | = lv_sano1_old | |
SANS1_OLD | = lv_sans1_old | |
TABLES | ||
VZPARUS_TAB | = lt_vzparus_tab | |
EXCEPTIONS | ||
ERROR = 1 | ||
OBJECT_NOT_FOUND = 2 | ||
. " OBJECT_ASSIGN_S |
ABAP code using 7.40 inline data declarations to call FM OBJECT_ASSIGN_S
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.DATA(ld_flg_save_in_updt) | = ' '. | |||
"SELECT single OBJNR FROM SANO1 INTO @DATA(ld_objnr). | ||||
DATA(ld_sano1_new) | = ' '. | |||
DATA(ld_sans1_new) | = ' '. | |||
Search for further information about these or an SAP related objects