SAP PFO_OBJECT_TERMINATE Function Module for NOTRANSL: Fachliches Beenden von Objekten der BZO i.S.d. Versionsführung d
PFO_OBJECT_TERMINATE is a standard pfo object terminate 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: Fachliches Beenden von Objekten der BZO i.S.d. Versionsführung d 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 pfo object terminate FM, simply by entering the name PFO_OBJECT_TERMINATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PFO_BASIS
Program Name: SAPLPFO_BASIS
Main Program: SAPLPFO_BASIS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PFO_OBJECT_TERMINATE 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 'PFO_OBJECT_TERMINATE'"NOTRANSL: Fachliches Beenden von Objekten der BZO i.S.d. Versionsführung d.
EXPORTING
ID_TERMDATE = "Date on Which an Object is Due to End
* ID_LOGNAME = "Application Log: External ID
* ID_UPDATE_TASK = "General Flag
* ID_MASS_PROC = "General Flag
CHANGING
CR_STRUCTURE = "Generic Type
* CD_LOG = "Application Log: Log Handle
* CRT_CHANGED = "Generic Type
* CRT_COMPLETE = "Generic Type
* CO_BAL = "CACS: Application Log
* CD_NOW = "Time Stamp (YYYY.MM.DD hh:mm:ss)
* CO_BUFFER = "Memory for Mass Processing
EXCEPTIONS
ALREADY_EXISTS = 1 PROCESSING_ERROR = 2 DB_ERROR = 3 DOESNT_EXIST = 4 ID_INCONSISTENT = 5 ASSIGN_ERROR = 6 LOG_ERROR = 7
IMPORTING Parameters details for PFO_OBJECT_TERMINATE
ID_TERMDATE - Date on Which an Object is Due to End
Data type: PFO_TERMDATEOptional: No
Call by Reference: Yes
ID_LOGNAME - Application Log: External ID
Data type: BALNREXTOptional: Yes
Call by Reference: Yes
ID_UPDATE_TASK - General Flag
Data type: FLAGOptional: Yes
Call by Reference: Yes
ID_MASS_PROC - General Flag
Data type: FLAGOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for PFO_OBJECT_TERMINATE
CR_STRUCTURE - Generic Type
Data type: DATAOptional: No
Call by Reference: Yes
CD_LOG - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
CRT_CHANGED - Generic Type
Data type: DATAOptional: Yes
Call by Reference: Yes
CRT_COMPLETE - Generic Type
Data type: DATAOptional: Yes
Call by Reference: Yes
CO_BAL - CACS: Application Log
Data type: CL_CACS_BALOptional: Yes
Call by Reference: Yes
CD_NOW - Time Stamp (YYYY.MM.DD hh:mm:ss)
Data type: CACSTIMESTAMPOptional: Yes
Call by Reference: Yes
CO_BUFFER - Memory for Mass Processing
Data type: CL_PFO_BUFFEROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ALREADY_EXISTS - Data record already exists
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROCESSING_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DB_ERROR - Error Writing to DB
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DOESNT_EXIST - Data record does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ID_INCONSISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ASSIGN_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
LOG_ERROR - Error in log
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PFO_OBJECT_TERMINATE 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_id_termdate | TYPE PFO_TERMDATE, " | |||
| lv_cr_structure | TYPE DATA, " | |||
| lv_already_exists | TYPE DATA, " | |||
| lv_cd_log | TYPE BALLOGHNDL, " | |||
| lv_id_logname | TYPE BALNREXT, " | |||
| lv_processing_error | TYPE BALNREXT, " | |||
| lv_db_error | TYPE BALNREXT, " | |||
| lv_crt_changed | TYPE DATA, " | |||
| lv_id_update_task | TYPE FLAG, " | |||
| lv_crt_complete | TYPE DATA, " | |||
| lv_doesnt_exist | TYPE DATA, " | |||
| lv_id_mass_proc | TYPE FLAG, " | |||
| lv_co_bal | TYPE CL_CACS_BAL, " | |||
| lv_id_inconsistent | TYPE CL_CACS_BAL, " | |||
| lv_cd_now | TYPE CACSTIMESTAMP, " | |||
| lv_assign_error | TYPE CACSTIMESTAMP, " | |||
| lv_co_buffer | TYPE CL_PFO_BUFFER, " | |||
| lv_log_error | TYPE CL_PFO_BUFFER. " |
|   CALL FUNCTION 'PFO_OBJECT_TERMINATE' "NOTRANSL: Fachliches Beenden von Objekten der BZO i.S.d. Versionsführung d |
| EXPORTING | ||
| ID_TERMDATE | = lv_id_termdate | |
| ID_LOGNAME | = lv_id_logname | |
| ID_UPDATE_TASK | = lv_id_update_task | |
| ID_MASS_PROC | = lv_id_mass_proc | |
| CHANGING | ||
| CR_STRUCTURE | = lv_cr_structure | |
| CD_LOG | = lv_cd_log | |
| CRT_CHANGED | = lv_crt_changed | |
| CRT_COMPLETE | = lv_crt_complete | |
| CO_BAL | = lv_co_bal | |
| CD_NOW | = lv_cd_now | |
| CO_BUFFER | = lv_co_buffer | |
| EXCEPTIONS | ||
| ALREADY_EXISTS = 1 | ||
| PROCESSING_ERROR = 2 | ||
| DB_ERROR = 3 | ||
| DOESNT_EXIST = 4 | ||
| ID_INCONSISTENT = 5 | ||
| ASSIGN_ERROR = 6 | ||
| LOG_ERROR = 7 | ||
| . " PFO_OBJECT_TERMINATE | ||
ABAP code using 7.40 inline data declarations to call FM PFO_OBJECT_TERMINATE
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