SAP FITP_SYNCHRONIZE_REQUEST_PLAN Function Module for Synchronization Plantab. - Requesttab.

Search SAP Function Modules

FITP_SYNCHRONIZE_REQUEST_PLAN is a standard fitp synchronize request plan SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Synchronization Plantab. - Requesttab. 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 fitp synchronize request plan FM, simply by entering the name FITP_SYNCHRONIZE_REQUEST_PLAN into the relevant SAP transaction such as SE37 or SE38.

Function Group: FITP_SYNCHRONIZE
Program Name: SAPLFITP_SYNCHRONIZE
Main Program: SAPLFITP_SYNCHRONIZE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FITP_SYNCHRONIZE_REQUEST_PLAN 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 'FITP_SYNCHRONIZE_REQUEST_PLAN'"Synchronization Plantab. - Requesttab.
  EXPORTING
   MOREI =  "Trip Provision Variant
*  UPDATE =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  SW_PORTAL =  "Single-Character Indicator

 IMPORTING
   WA_REQ_HEAD_CHANGED =  "Checkbox
   HOMELAND =  "Country Key

CHANGING
   WA_REQ_HEAD =  "Framework Data of Travel Request
   WA_PLAN =  "General Plan Data

TABLES
   T_REQ_HEAD =  "Framework Data of Travel Request
   T_REQUEST =  "Travel Plan Requests
   T_PLAN =  "General Plan Data
   T_ITEM =  "Travel Service Request Item

EXCEPTIONS
   NO_ENTRY_IN_TABLE = 1    INFOTYPE_NOT_FOUND = 2    ERROR_SYNCHRO = 3 

.

IMPORTING Parameters details for FITP_SYNCHRONIZE_REQUEST_PLAN

MOREI - Trip Provision Variant

Data type: PTRV_HEAD-MOREI
Optional: No
Call by Reference: Yes

UPDATE - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

SW_PORTAL - Single-Character Indicator

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FITP_SYNCHRONIZE_REQUEST_PLAN

WA_REQ_HEAD_CHANGED - Checkbox

Data type: XFELD
Optional: No
Call by Reference: Yes

HOMELAND - Country Key

Data type: T005-LAND1
Optional: No
Call by Reference: Yes

CHANGING Parameters details for FITP_SYNCHRONIZE_REQUEST_PLAN

WA_REQ_HEAD - Framework Data of Travel Request

Data type: FTPT_REQ_HEAD
Optional: No
Call by Reference: Yes

WA_PLAN - General Plan Data

Data type: FTPT_PLAN
Optional: No
Call by Reference: Yes

TABLES Parameters details for FITP_SYNCHRONIZE_REQUEST_PLAN

T_REQ_HEAD - Framework Data of Travel Request

Data type: FTPT_REQ_HEAD
Optional: No
Call by Reference: Yes

T_REQUEST - Travel Plan Requests

Data type: FTPT_REQUEST
Optional: No
Call by Reference: Yes

T_PLAN - General Plan Data

Data type: FTPT_PLAN
Optional: No
Call by Reference: Yes

T_ITEM - Travel Service Request Item

Data type: FTPT_ITEM
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_ENTRY_IN_TABLE -

Data type:
Optional: No
Call by Reference: Yes

INFOTYPE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ERROR_SYNCHRO -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FITP_SYNCHRONIZE_REQUEST_PLAN 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.

ABAP code using 7.40 inline data declarations to call FM FITP_SYNCHRONIZE_REQUEST_PLAN

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