SAP ATP3_COMMIT4ASTACK Function Module for ATP Server: Make commitment results for an ATP stack with mult-level check









ATP3_COMMIT4ASTACK is a standard atp3 commit4astack SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for ATP Server: Make commitment results for an ATP stack with mult-level check 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 atp3 commit4astack FM, simply by entering the name ATP3_COMMIT4ASTACK into the relevant SAP transaction such as SE37 or SE38.

Function Group: ATP3
Program Name: SAPLATP3
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ATP3_COMMIT4ASTACK 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 'ATP3_COMMIT4ASTACK'"ATP Server: Make commitment results for an ATP stack with mult-level check
  EXPORTING
*  P_MULTI = ' ' "multi-level check flag
*  P_REPLT =  "Replenish lead time
*  P_LASTX =  "last table index of p_ATPXQ
*  P_LASTW =  "
*  P_LVLNO = 1 "

CHANGING
*  P_ATP_1 =  "1st bucket ATP qty

TABLES
   P_REQ_Q =  "queued requirements
*  P_ATP_Q =  "queued ATPs
*  P_ATPXQ =  "extended ATP Stack
*  P_SEG_T =  "single MRP segment results
   P_MLT_T =  "multi-level results
.



IMPORTING Parameters details for ATP3_COMMIT4ASTACK

P_MULTI - multi-level check flag

Data type: T441V-EISBP
Default: SPACE
Optional: Yes
Call by Reference: Yes

P_REPLT - Replenish lead time

Data type: ATPMAT-ENDWZ
Optional: Yes
Call by Reference: Yes

P_LASTX - last table index of p_ATPXQ

Data type: SY-TABIX
Optional: Yes
Call by Reference: Yes

P_LASTW -

Data type: ATPXS
Optional: Yes
Call by Reference: Yes

P_LVLNO -

Data type: SY-TABIX
Default: 1
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ATP3_COMMIT4ASTACK

P_ATP_1 - 1st bucket ATP qty

Data type: ATPGC-ATPM1
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for ATP3_COMMIT4ASTACK

P_REQ_Q - queued requirements

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

P_ATP_Q - queued ATPs

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

P_ATPXQ - extended ATP Stack

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

P_SEG_T - single MRP segment results

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

P_MLT_T - multi-level results

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

Copy and paste ABAP code example for ATP3_COMMIT4ASTACK 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_p_atp_1  TYPE ATPGC-ATPM1, "   
lv_p_multi  TYPE T441V-EISBP, "   SPACE
lt_p_req_q  TYPE STANDARD TABLE OF MDVS, "   
lt_p_atp_q  TYPE STANDARD TABLE OF ATP_S, "   
lv_p_replt  TYPE ATPMAT-ENDWZ, "   
lt_p_atpxq  TYPE STANDARD TABLE OF ATPXS, "   
lv_p_lastx  TYPE SY-TABIX, "   
lv_p_lastw  TYPE ATPXS, "   
lt_p_seg_t  TYPE STANDARD TABLE OF MDVE, "   
lv_p_lvlno  TYPE SY-TABIX, "   1
lt_p_mlt_t  TYPE STANDARD TABLE OF MDVE. "   

  CALL FUNCTION 'ATP3_COMMIT4ASTACK'  "ATP Server: Make commitment results for an ATP stack with mult-level check
    EXPORTING
         P_MULTI = lv_p_multi
         P_REPLT = lv_p_replt
         P_LASTX = lv_p_lastx
         P_LASTW = lv_p_lastw
         P_LVLNO = lv_p_lvlno
    CHANGING
         P_ATP_1 = lv_p_atp_1
    TABLES
         P_REQ_Q = lt_p_req_q
         P_ATP_Q = lt_p_atp_q
         P_ATPXQ = lt_p_atpxq
         P_SEG_T = lt_p_seg_t
         P_MLT_T = lt_p_mlt_t
. " ATP3_COMMIT4ASTACK




ABAP code using 7.40 inline data declarations to call FM ATP3_COMMIT4ASTACK

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.

"SELECT single ATPM1 FROM ATPGC INTO @DATA(ld_p_atp_1).
 
"SELECT single EISBP FROM T441V INTO @DATA(ld_p_multi).
DATA(ld_p_multi) = ' '.
 
 
 
"SELECT single ENDWZ FROM ATPMAT INTO @DATA(ld_p_replt).
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_p_lastx).
 
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_p_lvlno).
DATA(ld_p_lvlno) = 1.
 
 


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!