SAP PCAMPAIGN_DB_UPDATE Function Module for NOTRANSL: Produktionskampagne auf DB sichern









PCAMPAIGN_DB_UPDATE is a standard pcampaign db update 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: Produktionskampagne auf DB sichern 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 pcampaign db update FM, simply by entering the name PCAMPAIGN_DB_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function PCAMPAIGN_DB_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 'PCAMPAIGN_DB_UPDATE'"NOTRANSL: Produktionskampagne auf DB sichern
  EXPORTING
*  NO_COMMIT =  "New Input Values
*  CALL_BAPI =  "New Input Values

 IMPORTING
   PCM_SAVED =  "New Input Values

TABLES
   PCM_PCMHB_TAB_T =  "Buffer table for production campaign owner
*  PCM_PCMO1B_TAB_T =  "Buffer table for production campaign pegged reqmt - material
*  PCM_PCMO2B_TAB_T =  "Buffer table for production campaign pegged reqmt - reqmts
*  PCM_PCMO3B_TAB_T =  "Buffer table for production campaign pegged reqmt - recipe
*  PCM_PCMO4B_TAB_T =  "Buffer table for prod. camp. pegged reqmt - resource network
   PCM_PCMPB_TAB_T =  "Buffer table for production campaign item
.



IMPORTING Parameters details for PCAMPAIGN_DB_UPDATE

NO_COMMIT - New Input Values

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

CALL_BAPI - New Input Values

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

EXPORTING Parameters details for PCAMPAIGN_DB_UPDATE

PCM_SAVED - New Input Values

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

TABLES Parameters details for PCAMPAIGN_DB_UPDATE

PCM_PCMHB_TAB_T - Buffer table for production campaign owner

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

PCM_PCMO1B_TAB_T - Buffer table for production campaign pegged reqmt - material

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

PCM_PCMO2B_TAB_T - Buffer table for production campaign pegged reqmt - reqmts

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

PCM_PCMO3B_TAB_T - Buffer table for production campaign pegged reqmt - recipe

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

PCM_PCMO4B_TAB_T - Buffer table for prod. camp. pegged reqmt - resource network

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

PCM_PCMPB_TAB_T - Buffer table for production campaign item

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

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

DATA:
lv_no_commit  TYPE XFLAG, "   
lv_pcm_saved  TYPE XFLAG, "   
lt_pcm_pcmhb_tab_t  TYPE STANDARD TABLE OF PCMHB, "   
lv_call_bapi  TYPE XFLAG, "   
lt_pcm_pcmo1b_tab_t  TYPE STANDARD TABLE OF PCMO1B, "   
lt_pcm_pcmo2b_tab_t  TYPE STANDARD TABLE OF PCMO2B, "   
lt_pcm_pcmo3b_tab_t  TYPE STANDARD TABLE OF PCMO3B, "   
lt_pcm_pcmo4b_tab_t  TYPE STANDARD TABLE OF PCMO4B, "   
lt_pcm_pcmpb_tab_t  TYPE STANDARD TABLE OF PCMPB. "   

  CALL FUNCTION 'PCAMPAIGN_DB_UPDATE'  "NOTRANSL: Produktionskampagne auf DB sichern
    EXPORTING
         NO_COMMIT = lv_no_commit
         CALL_BAPI = lv_call_bapi
    IMPORTING
         PCM_SAVED = lv_pcm_saved
    TABLES
         PCM_PCMHB_TAB_T = lt_pcm_pcmhb_tab_t
         PCM_PCMO1B_TAB_T = lt_pcm_pcmo1b_tab_t
         PCM_PCMO2B_TAB_T = lt_pcm_pcmo2b_tab_t
         PCM_PCMO3B_TAB_T = lt_pcm_pcmo3b_tab_t
         PCM_PCMO4B_TAB_T = lt_pcm_pcmo4b_tab_t
         PCM_PCMPB_TAB_T = lt_pcm_pcmpb_tab_t
. " PCAMPAIGN_DB_UPDATE




ABAP code using 7.40 inline data declarations to call FM PCAMPAIGN_DB_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!