SAP PAR_DB_STATECHANGE_DB Function Module for Change state of ProductAvilabilityRequirement on DB
PAR_DB_STATECHANGE_DB is a standard par db statechange db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change state of ProductAvilabilityRequirement on DB 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 par db statechange db FM, simply by entering the name PAR_DB_STATECHANGE_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: PAR_DB
Program Name: SAPLPAR_DB
Main Program: SAPLPAR_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function PAR_DB_STATECHANGE_DB 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 'PAR_DB_STATECHANGE_DB'"Change state of ProductAvilabilityRequirement on DB.
EXPORTING
IV_TRGUID = "ATP: Unique ID for relevant transaction in APO server
IV_STATE = "Technical state of PAR object
* IV_CHANGER = "User Name
IMPORTING Parameters details for PAR_DB_STATECHANGE_DB
IV_TRGUID - ATP: Unique ID for relevant transaction in APO server
Data type: APOTRGUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_STATE - Technical state of PAR object
Data type: PAR_STATEOptional: No
Call by Reference: No ( called with pass by value option)
IV_CHANGER - User Name
Data type: SYUNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PAR_DB_STATECHANGE_DB 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_iv_trguid | TYPE APOTRGUID, " | |||
| lv_iv_state | TYPE PAR_STATE, " | |||
| lv_iv_changer | TYPE SYUNAME. " |
|   CALL FUNCTION 'PAR_DB_STATECHANGE_DB' "Change state of ProductAvilabilityRequirement on DB |
| EXPORTING | ||
| IV_TRGUID | = lv_iv_trguid | |
| IV_STATE | = lv_iv_state | |
| IV_CHANGER | = lv_iv_changer | |
| . " PAR_DB_STATECHANGE_DB | ||
ABAP code using 7.40 inline data declarations to call FM PAR_DB_STATECHANGE_DB
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