SAP PAMS_CUSTO_OBJECTS Function Module for NOTRANSL: Statusschema zur Balkengraphik (gepuffertes Lesen)
PAMS_CUSTO_OBJECTS is a standard pams custo objects 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: Statusschema zur Balkengraphik (gepuffertes Lesen) 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 pams custo objects FM, simply by entering the name PAMS_CUSTO_OBJECTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: PAMS_CUSTOMIZING
Program Name: SAPLPAMS_CUSTOMIZING
Main Program: SAPLPAMS_CUSTOMIZING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PAMS_CUSTO_OBJECTS 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 'PAMS_CUSTO_OBJECTS'"NOTRANSL: Statusschema zur Balkengraphik (gepuffertes Lesen).
EXPORTING
IV_APPLICATION = "Indicator for the Application
* I_NOTART = "Message Type
* I_AUFART = "Sales Document Type
IMPORTING
E_T_OBJECTS = "
CHANGING
* E_TAB_OBJECTS = "Objects for Processing
* DIRECTPLAN = "Flag (X or Blank)
EXCEPTIONS
NOT_ACTIV = 1
IMPORTING Parameters details for PAMS_CUSTO_OBJECTS
IV_APPLICATION - Indicator for the Application
Data type: PAMS_APPLICATIONOptional: No
Call by Reference: Yes
I_NOTART - Message Type
Data type: QMARTOptional: Yes
Call by Reference: Yes
I_AUFART - Sales Document Type
Data type: AUARTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PAMS_CUSTO_OBJECTS
E_T_OBJECTS -
Data type:Optional: No
Call by Reference: Yes
CHANGING Parameters details for PAMS_CUSTO_OBJECTS
E_TAB_OBJECTS - Objects for Processing
Data type: PAMS_TT_OBJEOptional: Yes
Call by Reference: Yes
DIRECTPLAN - Flag (X or Blank)
Data type: AS4FLAGOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_ACTIV - Inactive
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PAMS_CUSTO_OBJECTS 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_not_activ | TYPE STRING, " | |||
| lv_e_t_objects | TYPE STRING, " | |||
| lv_e_tab_objects | TYPE PAMS_TT_OBJE, " | |||
| lv_iv_application | TYPE PAMS_APPLICATION, " | |||
| lv_i_notart | TYPE QMART, " | |||
| lv_directplan | TYPE AS4FLAG, " | |||
| lv_i_aufart | TYPE AUART. " |
|   CALL FUNCTION 'PAMS_CUSTO_OBJECTS' "NOTRANSL: Statusschema zur Balkengraphik (gepuffertes Lesen) |
| EXPORTING | ||
| IV_APPLICATION | = lv_iv_application | |
| I_NOTART | = lv_i_notart | |
| I_AUFART | = lv_i_aufart | |
| IMPORTING | ||
| E_T_OBJECTS | = lv_e_t_objects | |
| CHANGING | ||
| E_TAB_OBJECTS | = lv_e_tab_objects | |
| DIRECTPLAN | = lv_directplan | |
| EXCEPTIONS | ||
| NOT_ACTIV = 1 | ||
| . " PAMS_CUSTO_OBJECTS | ||
ABAP code using 7.40 inline data declarations to call FM PAMS_CUSTO_OBJECTS
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