SAP FC_PERIVS_MAP Function Module for

Search SAP Function Modules

FC_PERIVS_MAP is a standard fc perivs map SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fc perivs map FM, simply by entering the name FC_PERIVS_MAP into the relevant SAP transaction such as SE37 or SE38.

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

Function FC_PERIVS_MAP 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 'FC_PERIVS_MAP'"
  EXPORTING
   I_PERIV_DEST =  "

 IMPORTING
   E_FLG_UNIQUE_PERIV =  "
   E_ANZBP_DEST =  "
   E_ANZSP_DEST =  "

TABLES
   T_YEARPER =  "
*  E_T_PERIVDATE =  "
*  E_T_PERIVMAP =  "
*  E_T_PERIDCOMP =  "

EXCEPTIONS
   INCOMPATIBLE_PERIODS = 1 

.

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_SAPLFCIN_100 Integration: User Exit for Identifier and Texts from Cons Org Units
EXIT_SAPLFCIN_110 Integration: User Exit for 'Parents' of Cons Org Units
EXIT_SAPLFCIN_200 Integration: User Exit for Definition of the Data Stream on Rollup
EXIT_SAPLFCIN_210 Integration: Output Fields of Incorrect Data Records in Rollup
EXIT_SAPLFCIN_220 Integration: Sender Fields for Organizational Units on Rollup
EXIT_SAPLFCIN_230 Integration: Sender Fields for Subitems on Rollup
EXIT_SAPLFCIN_240 Integration: Edit from Value Fields before Update with Rollup
EXIT_SAPLFCIN_250 Integration: Get Custom Subassignments

IMPORTING Parameters details for FC_PERIVS_MAP

I_PERIV_DEST -

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

EXPORTING Parameters details for FC_PERIVS_MAP

E_FLG_UNIQUE_PERIV -

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

E_ANZBP_DEST -

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

E_ANZSP_DEST -

Data type: T009-ANZSP
Optional: No
Call by Reference: Yes

TABLES Parameters details for FC_PERIVS_MAP

T_YEARPER -

Data type: FCIN_T_YEARPER
Optional: No
Call by Reference: No ( called with pass by value option)

E_T_PERIVDATE -

Data type: FCIN_T_PERIVDATE
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_T_PERIVMAP -

Data type: FCIN_T_PERIVMAP
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_T_PERIDCOMP -

Data type: FCIN_T_PERID_COMP
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INCOMPATIBLE_PERIODS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

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

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