SAP BAPI_PA_DNSTS_CHANGE Function Module for DNSTS Change
BAPI_PA_DNSTS_CHANGE is a standard bapi pa dnsts change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for DNSTS Change 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 bapi pa dnsts change FM, simply by entering the name BAPI_PA_DNSTS_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIU_PA_PPN_DNSTS
Program Name: SAPLOIU_PA_PPN_DNSTS
Main Program: SAPLOIU_PA_PPN_DNSTS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PA_DNSTS_CHANGE 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 'BAPI_PA_DNSTS_CHANGE'"DNSTS Change.
EXPORTING
DN_NO = "Well ID Number
PRD_DT = "Well Completion Number
FREQ_CD = "Effective From Date
MAJPD_CD = "Effective From Time
SUB_SYSTEM_CD = "Subsystem Code
ALLOC_RESULT_CD = "Allocation Result Code
STS_CD = "DN status Code
CLOSE_IND = "Close Indicator
IMPORTING
DNSTS_DETAIL = "Delivery Network Status BAPI Structure - Subsystem Detail
TABLES
RETURN = "Return parameter
IMPORTING Parameters details for BAPI_PA_DNSTS_CHANGE
DN_NO - Well ID Number
Data type: BAPI_OIU_DNSTH-DN_NOOptional: No
Call by Reference: No ( called with pass by value option)
PRD_DT - Well Completion Number
Data type: BAPI_OIU_DNSTH-PRD_DTOptional: No
Call by Reference: No ( called with pass by value option)
FREQ_CD - Effective From Date
Data type: BAPI_OIU_DNSTH-FREQ_CDOptional: No
Call by Reference: No ( called with pass by value option)
MAJPD_CD - Effective From Time
Data type: BAPI_OIU_DNSTH-MAJPD_CDOptional: No
Call by Reference: No ( called with pass by value option)
SUB_SYSTEM_CD - Subsystem Code
Data type: BAPI_OIU_DNSTD-SUB_SYSTEM_CDOptional: No
Call by Reference: No ( called with pass by value option)
ALLOC_RESULT_CD - Allocation Result Code
Data type: BAPI_OIU_DNSTD-ALLOC_RESULT_CDOptional: No
Call by Reference: No ( called with pass by value option)
STS_CD - DN status Code
Data type: BAPI_OIU_DNSTD-STS_CDOptional: No
Call by Reference: No ( called with pass by value option)
CLOSE_IND - Close Indicator
Data type: BAPI_OIU_DNSTD-CLOSE_INDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_PA_DNSTS_CHANGE
DNSTS_DETAIL - Delivery Network Status BAPI Structure - Subsystem Detail
Data type: BAPI_OIU_DNSTDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PA_DNSTS_CHANGE
RETURN - Return parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_PA_DNSTS_CHANGE 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_dn_no | TYPE BAPI_OIU_DNSTH-DN_NO, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_dnsts_detail | TYPE BAPI_OIU_DNSTD, " | |||
| lv_prd_dt | TYPE BAPI_OIU_DNSTH-PRD_DT, " | |||
| lv_freq_cd | TYPE BAPI_OIU_DNSTH-FREQ_CD, " | |||
| lv_majpd_cd | TYPE BAPI_OIU_DNSTH-MAJPD_CD, " | |||
| lv_sub_system_cd | TYPE BAPI_OIU_DNSTD-SUB_SYSTEM_CD, " | |||
| lv_alloc_result_cd | TYPE BAPI_OIU_DNSTD-ALLOC_RESULT_CD, " | |||
| lv_sts_cd | TYPE BAPI_OIU_DNSTD-STS_CD, " | |||
| lv_close_ind | TYPE BAPI_OIU_DNSTD-CLOSE_IND. " |
|   CALL FUNCTION 'BAPI_PA_DNSTS_CHANGE' "DNSTS Change |
| EXPORTING | ||
| DN_NO | = lv_dn_no | |
| PRD_DT | = lv_prd_dt | |
| FREQ_CD | = lv_freq_cd | |
| MAJPD_CD | = lv_majpd_cd | |
| SUB_SYSTEM_CD | = lv_sub_system_cd | |
| ALLOC_RESULT_CD | = lv_alloc_result_cd | |
| STS_CD | = lv_sts_cd | |
| CLOSE_IND | = lv_close_ind | |
| IMPORTING | ||
| DNSTS_DETAIL | = lv_dnsts_detail | |
| TABLES | ||
| RETURN | = lt_return | |
| . " BAPI_PA_DNSTS_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PA_DNSTS_CHANGE
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 DN_NO FROM BAPI_OIU_DNSTH INTO @DATA(ld_dn_no). | ||||
| "SELECT single PRD_DT FROM BAPI_OIU_DNSTH INTO @DATA(ld_prd_dt). | ||||
| "SELECT single FREQ_CD FROM BAPI_OIU_DNSTH INTO @DATA(ld_freq_cd). | ||||
| "SELECT single MAJPD_CD FROM BAPI_OIU_DNSTH INTO @DATA(ld_majpd_cd). | ||||
| "SELECT single SUB_SYSTEM_CD FROM BAPI_OIU_DNSTD INTO @DATA(ld_sub_system_cd). | ||||
| "SELECT single ALLOC_RESULT_CD FROM BAPI_OIU_DNSTD INTO @DATA(ld_alloc_result_cd). | ||||
| "SELECT single STS_CD FROM BAPI_OIU_DNSTD INTO @DATA(ld_sts_cd). | ||||
| "SELECT single CLOSE_IND FROM BAPI_OIU_DNSTD INTO @DATA(ld_close_ind). | ||||
Search for further information about these or an SAP related objects