SAP CS_SO_PJ_FIND_FREE Function Module for NOTRANSL: Analyse der Projekt BOMs
CS_SO_PJ_FIND_FREE is a standard cs so pj find free 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: Analyse der Projekt BOMs 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 cs so pj find free FM, simply by entering the name CS_SO_PJ_FIND_FREE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CSSO
Program Name: SAPLCSSO
Main Program: SAPLCSSO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CS_SO_PJ_FIND_FREE 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 'CS_SO_PJ_FIND_FREE'"NOTRANSL: Analyse der Projekt BOMs.
EXPORTING
I_PSPNR = "Work Breakdown Structure Element (WBS Element)
I_CAPID = "Application
* I_AENNR = "Change Number
* I_DATUV = "Valid-From Date
TABLES
* ET_MAT = "Document table for MAST records
* ET_PJS = "Buffer table for PRST records
* ET_PJR = "Buffer table for PRST records
* ET_DBL = "Buffer table for PRST records
* ET_HDR = "Buffer table for PRST records
* ET_POS = "Buffer table for PRST records
EXCEPTIONS
NO_RECORD_FOUND = 1 PROBLEMS_READ_BOM = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCSSO_001 Order/WBS BOM, HTML control
EXIT_SAPLCSSO_002 Order-,Project-,Material BOM. Explos.-/Creation-/Default Date for Browser
EXIT_SAPLCSSO_003 Customer-specific processing result of an explosion in the browser
IMPORTING Parameters details for CS_SO_PJ_FIND_FREE
I_PSPNR - Work Breakdown Structure Element (WBS Element)
Data type: PRST-PSPNROptional: No
Call by Reference: No ( called with pass by value option)
I_CAPID - Application
Data type: RC29L-CAPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_AENNR - Change Number
Data type: RC29L-AENNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATUV - Valid-From Date
Data type: RC29L-DATUVOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CS_SO_PJ_FIND_FREE
ET_MAT - Document table for MAST records
Data type: MASTBOptional: Yes
Call by Reference: Yes
ET_PJS - Buffer table for PRST records
Data type: PRSTBOptional: Yes
Call by Reference: Yes
ET_PJR - Buffer table for PRST records
Data type: PRSTBOptional: Yes
Call by Reference: Yes
ET_DBL - Buffer table for PRST records
Data type: PRSTBOptional: Yes
Call by Reference: Yes
ET_HDR - Buffer table for PRST records
Data type: PRSTBOptional: Yes
Call by Reference: Yes
ET_POS - Buffer table for PRST records
Data type: PRSTBOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_RECORD_FOUND -
Data type:Optional: No
Call by Reference: Yes
PROBLEMS_READ_BOM -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CS_SO_PJ_FIND_FREE 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: | ||||
| lt_et_mat | TYPE STANDARD TABLE OF MASTB, " | |||
| lv_i_pspnr | TYPE PRST-PSPNR, " | |||
| lv_no_record_found | TYPE PRST, " | |||
| lt_et_pjs | TYPE STANDARD TABLE OF PRSTB, " | |||
| lv_i_capid | TYPE RC29L-CAPID, " | |||
| lv_problems_read_bom | TYPE RC29L, " | |||
| lt_et_pjr | TYPE STANDARD TABLE OF PRSTB, " | |||
| lv_i_aennr | TYPE RC29L-AENNR, " | |||
| lt_et_dbl | TYPE STANDARD TABLE OF PRSTB, " | |||
| lv_i_datuv | TYPE RC29L-DATUV, " | |||
| lt_et_hdr | TYPE STANDARD TABLE OF PRSTB, " | |||
| lt_et_pos | TYPE STANDARD TABLE OF PRSTB. " |
|   CALL FUNCTION 'CS_SO_PJ_FIND_FREE' "NOTRANSL: Analyse der Projekt BOMs |
| EXPORTING | ||
| I_PSPNR | = lv_i_pspnr | |
| I_CAPID | = lv_i_capid | |
| I_AENNR | = lv_i_aennr | |
| I_DATUV | = lv_i_datuv | |
| TABLES | ||
| ET_MAT | = lt_et_mat | |
| ET_PJS | = lt_et_pjs | |
| ET_PJR | = lt_et_pjr | |
| ET_DBL | = lt_et_dbl | |
| ET_HDR | = lt_et_hdr | |
| ET_POS | = lt_et_pos | |
| EXCEPTIONS | ||
| NO_RECORD_FOUND = 1 | ||
| PROBLEMS_READ_BOM = 2 | ||
| . " CS_SO_PJ_FIND_FREE | ||
ABAP code using 7.40 inline data declarations to call FM CS_SO_PJ_FIND_FREE
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 PSPNR FROM PRST INTO @DATA(ld_i_pspnr). | ||||
| "SELECT single CAPID FROM RC29L INTO @DATA(ld_i_capid). | ||||
| "SELECT single AENNR FROM RC29L INTO @DATA(ld_i_aennr). | ||||
| "SELECT single DATUV FROM RC29L INTO @DATA(ld_i_datuv). | ||||
Search for further information about these or an SAP related objects