SAP PFO_OBJECT_BACKSWITCH Function Module for NOTRANSL: Lege eine (neue) Zuordnung an und lösche alle alten
PFO_OBJECT_BACKSWITCH is a standard pfo object backswitch 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: Lege eine (neue) Zuordnung an und lösche alle alten 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 backswitch FM, simply by entering the name PFO_OBJECT_BACKSWITCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: PFO_COMPLEX
Program Name: SAPLPFO_COMPLEX
Main Program: SAPLPFO_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PFO_OBJECT_BACKSWITCH 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_BACKSWITCH'"NOTRANSL: Lege eine (neue) Zuordnung an und lösche alle alten.
EXPORTING
* ID_TERMDATE = "Date on Which an Object is Due to End
* ID_LOGNAME = "Application Log: External Identification
IR_OLD_ASSIGNED = "
* ID_UPDATE_TASK = "Indicator: Update
* ID_MASS_PROC = "Indicator: Mass Processing
CHANGING
CR_STRUCTURE = "Data Record (Bus.Object Assignment or Segment Assignment)
* CD_LOG = "Application Log: Log Handle
* CRT_CHANGED = "Data Records Changed
* CRT_COMPLETE = "All Data Records of Object
* CO_BAL = "CUX: Application LOG
* CD_NOW = "Now
* CO_BUFFER = "Memory for Mass Processing
* CT_ENQ_VAL = "Enqueue Values
EXCEPTIONS
ALREADY_EXISTS = 1 PROCESSING_ERROR = 2 DB_ERROR = 3 DOESNT_EXIST = 4 ID_INCONSISTENT = 5 ASSIGN_ERROR = 6 LOG_ERROR = 7 WRONG_KIND = 8
IMPORTING Parameters details for PFO_OBJECT_BACKSWITCH
ID_TERMDATE - Date on Which an Object is Due to End
Data type: PFO_TERMDATEOptional: Yes
Call by Reference: Yes
ID_LOGNAME - Application Log: External Identification
Data type: BALNREXTOptional: Yes
Call by Reference: Yes
IR_OLD_ASSIGNED -
Data type: DATAOptional: No
Call by Reference: Yes
ID_UPDATE_TASK - Indicator: Update
Data type: FLAGOptional: Yes
Call by Reference: Yes
ID_MASS_PROC - Indicator: Mass Processing
Data type: FLAGOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for PFO_OBJECT_BACKSWITCH
CR_STRUCTURE - Data Record (Bus.Object Assignment or Segment Assignment)
Data type: DATAOptional: No
Call by Reference: Yes
CD_LOG - Application Log: Log Handle
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
CRT_CHANGED - Data Records Changed
Data type: DATAOptional: Yes
Call by Reference: Yes
CRT_COMPLETE - All Data Records of Object
Data type: DATAOptional: Yes
Call by Reference: Yes
CO_BAL - CUX: Application LOG
Data type: CL_CACS_BALOptional: Yes
Call by Reference: Yes
CD_NOW - Now
Data type: PFO_TERMDATEOptional: Yes
Call by Reference: Yes
CO_BUFFER - Memory for Mass Processing
Data type: CL_PFO_BUFFEROptional: Yes
Call by Reference: Yes
CT_ENQ_VAL - Enqueue Values
Data type: PFO_TI_ENQ_VALOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ALREADY_EXISTS -
Data type:Optional: No
Call by Reference: Yes
PROCESSING_ERROR -
Data type:Optional: No
Call by Reference: Yes
DB_ERROR -
Data type:Optional: No
Call by Reference: Yes
DOESNT_EXIST -
Data type:Optional: No
Call by Reference: Yes
ID_INCONSISTENT -
Data type:Optional: No
Call by Reference: Yes
ASSIGN_ERROR -
Data type:Optional: No
Call by Reference: Yes
LOG_ERROR -
Data type:Optional: No
Call by Reference: Yes
WRONG_KIND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PFO_OBJECT_BACKSWITCH 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_ir_old_assigned | TYPE DATA, " | |||
| lv_crt_complete | TYPE DATA, " | |||
| lv_doesnt_exist | TYPE DATA, " | |||
| lv_id_update_task | TYPE FLAG, " | |||
| lv_co_bal | TYPE CL_CACS_BAL, " | |||
| lv_id_mass_proc | TYPE FLAG, " | |||
| lv_id_inconsistent | TYPE FLAG, " | |||
| lv_cd_now | TYPE PFO_TERMDATE, " | |||
| lv_assign_error | TYPE PFO_TERMDATE, " | |||
| lv_co_buffer | TYPE CL_PFO_BUFFER, " | |||
| lv_log_error | TYPE CL_PFO_BUFFER, " | |||
| lv_ct_enq_val | TYPE PFO_TI_ENQ_VAL, " | |||
| lv_wrong_kind | TYPE PFO_TI_ENQ_VAL. " |
|   CALL FUNCTION 'PFO_OBJECT_BACKSWITCH' "NOTRANSL: Lege eine (neue) Zuordnung an und lösche alle alten |
| EXPORTING | ||
| ID_TERMDATE | = lv_id_termdate | |
| ID_LOGNAME | = lv_id_logname | |
| IR_OLD_ASSIGNED | = lv_ir_old_assigned | |
| 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 | |
| CT_ENQ_VAL | = lv_ct_enq_val | |
| EXCEPTIONS | ||
| ALREADY_EXISTS = 1 | ||
| PROCESSING_ERROR = 2 | ||
| DB_ERROR = 3 | ||
| DOESNT_EXIST = 4 | ||
| ID_INCONSISTENT = 5 | ||
| ASSIGN_ERROR = 6 | ||
| LOG_ERROR = 7 | ||
| WRONG_KIND = 8 | ||
| . " PFO_OBJECT_BACKSWITCH | ||
ABAP code using 7.40 inline data declarations to call FM PFO_OBJECT_BACKSWITCH
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