SAP G_PCA_FROM_CO_PLAN_UPDATE Function Module for

Search SAP Function Modules

G_PCA_FROM_CO_PLAN_UPDATE is a standard g pca from co plan update 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 g pca from co plan update FM, simply by entering the name G_PCA_FROM_CO_PLAN_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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

Function G_PCA_FROM_CO_PLAN_UPDATE 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 'G_PCA_FROM_CO_PLAN_UPDATE'"
  EXPORTING
*  I_TEST_ONLY = ' ' "
*  X_BATCH = ' ' "

 IMPORTING
   E_ERROR_FOUND =  "

TABLES
   T_COBK =  "Document header
   T_COEJA =  "Planning Items
   T_COIOB =  "Objects
   T_LEDGER =  "Ledger table
   T_PERIODS =  "Periods

.

IMPORTING Parameters details for G_PCA_FROM_CO_PLAN_UPDATE

I_TEST_ONLY -

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

X_BATCH -

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

EXPORTING Parameters details for G_PCA_FROM_CO_PLAN_UPDATE

E_ERROR_FOUND -

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

TABLES Parameters details for G_PCA_FROM_CO_PLAN_UPDATE

T_COBK - Document header

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

T_COEJA - Planning Items

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

T_COIOB - Objects

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

T_LEDGER - Ledger table

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

T_PERIODS - Periods

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

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

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