SAP PERMITS_FOR_OBJECT Function Module for NOTRANSL: Genehmigungen vom Puffer lesen
PERMITS_FOR_OBJECT is a standard permits for object 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: Genehmigungen vom Puffer 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 permits for object FM, simply by entering the name PERMITS_FOR_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: IMSP
Program Name: SAPLIMSP
Main Program: SAPLIMSP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PERMITS_FOR_OBJECT 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 'PERMITS_FOR_OBJECT'"NOTRANSL: Genehmigungen vom Puffer lesen.
EXPORTING
* IV_OBJNR = "Object Number
* IV_EQUNR = "Equipment Number
* IV_TPLNR = "Functional Location
* IV_AUFNR = "Order Number
* IV_PLNTY = "TL Type
* IV_PLNNR = "Key for Task List Group
* IV_PLNAL = "TL Group Counter
* IV_DATE = SY-DATUM "Current Date of Application Server
IMPORTING
ET_PERMIT = "Approvals
ET_PERMIT_ISSUE = "Issued Permits
ET_RETURN = "Table with BAPI Return Information
IMPORTING Parameters details for PERMITS_FOR_OBJECT
IV_OBJNR - Object Number
Data type: J_OBJNROptional: Yes
Call by Reference: Yes
IV_EQUNR - Equipment Number
Data type: EQUNROptional: Yes
Call by Reference: Yes
IV_TPLNR - Functional Location
Data type: TPLNROptional: Yes
Call by Reference: Yes
IV_AUFNR - Order Number
Data type: AUFNROptional: Yes
Call by Reference: Yes
IV_PLNTY - TL Type
Data type: PLNTYOptional: Yes
Call by Reference: Yes
IV_PLNNR - Key for Task List Group
Data type: PLNNROptional: Yes
Call by Reference: Yes
IV_PLNAL - TL Group Counter
Data type: PLNALOptional: Yes
Call by Reference: Yes
IV_DATE - Current Date of Application Server
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PERMITS_FOR_OBJECT
ET_PERMIT - Approvals
Data type: EAM_T_PERMIT_READOptional: No
Call by Reference: Yes
ET_PERMIT_ISSUE - Issued Permits
Data type: EAM_T_PERMIT_ISSUE_READOptional: No
Call by Reference: Yes
ET_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PERMITS_FOR_OBJECT 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_objnr | TYPE J_OBJNR, " | |||
| lv_et_permit | TYPE EAM_T_PERMIT_READ, " | |||
| lv_iv_equnr | TYPE EQUNR, " | |||
| lv_et_permit_issue | TYPE EAM_T_PERMIT_ISSUE_READ, " | |||
| lv_iv_tplnr | TYPE TPLNR, " | |||
| lv_et_return | TYPE BAPIRETTAB, " | |||
| lv_iv_aufnr | TYPE AUFNR, " | |||
| lv_iv_plnty | TYPE PLNTY, " | |||
| lv_iv_plnnr | TYPE PLNNR, " | |||
| lv_iv_plnal | TYPE PLNAL, " | |||
| lv_iv_date | TYPE SY-DATUM. " SY-DATUM |
|   CALL FUNCTION 'PERMITS_FOR_OBJECT' "NOTRANSL: Genehmigungen vom Puffer lesen |
| EXPORTING | ||
| IV_OBJNR | = lv_iv_objnr | |
| IV_EQUNR | = lv_iv_equnr | |
| IV_TPLNR | = lv_iv_tplnr | |
| IV_AUFNR | = lv_iv_aufnr | |
| IV_PLNTY | = lv_iv_plnty | |
| IV_PLNNR | = lv_iv_plnnr | |
| IV_PLNAL | = lv_iv_plnal | |
| IV_DATE | = lv_iv_date | |
| IMPORTING | ||
| ET_PERMIT | = lv_et_permit | |
| ET_PERMIT_ISSUE | = lv_et_permit_issue | |
| ET_RETURN | = lv_et_return | |
| . " PERMITS_FOR_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM PERMITS_FOR_OBJECT
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 DATUM FROM SY INTO @DATA(ld_iv_date). | ||||
| DATA(ld_iv_date) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects