SAP PCHEAD_ALOG_WRITE Function Module for NOTRANSL: ALE-Eingang PCHEAD: Anwendungslog schreiben









PCHEAD_ALOG_WRITE is a standard pchead alog write 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: ALE-Eingang PCHEAD: Anwendungslog schreiben 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 pchead alog write FM, simply by entering the name PCHEAD_ALOG_WRITE into the relevant SAP transaction such as SE37 or SE38.

Function Group: WPCA
Program Name: SAPLWPCA
Main Program: SAPLWPCA
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function PCHEAD_ALOG_WRITE 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 'PCHEAD_ALOG_WRITE'"NOTRANSL: ALE-Eingang PCHEAD: Anwendungslog schreiben
  EXPORTING
*  CATALOGBASEDATA =  "Product Catalog Basic Data
*  LAYOUT =  "Product Catalog Layout

TABLES
   PX_T_RETURN =  "
*  EXTENSIONIN =  "Customer Enhancements
*  CATALOGNAME =  "Product catalog description
*  VARIANTS =  "Product Catalog Variants
*  VARIANTNAMES =  "Variant Description
*  LAYOUTNAME =  "Layout description
*  AREAS =  "Product Catalog Layout Areas
*  AREANAMES =  "Layout Area Description
*  AREATEXTS =  "Layout Area Texts
*  AREALONGTEXTS =  "Layout Area Long Texts
.




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_SAPLWPCA_001 Function Exit for Product Catalog IDoc Outbound Message Type PCHEAD
EXIT_SAPLWPCA_002 Function Exit for Product Catalog IDoc Outbound Message Type PCITEMS
EXIT_SAPLWPCA_003 Function Exit for Product Catalog IDoc Inbound Message Type PCHEAD
EXIT_SAPLWPCA_004 Function Exit for Product Catalog IDoc Inbound Message Type PCITEMS

IMPORTING Parameters details for PCHEAD_ALOG_WRITE

CATALOGBASEDATA - Product Catalog Basic Data

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

LAYOUT - Product Catalog Layout

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

TABLES Parameters details for PCHEAD_ALOG_WRITE

PX_T_RETURN -

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

EXTENSIONIN - Customer Enhancements

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

CATALOGNAME - Product catalog description

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

VARIANTS - Product Catalog Variants

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

VARIANTNAMES - Variant Description

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

LAYOUTNAME - Layout description

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

AREAS - Product Catalog Layout Areas

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

AREANAMES - Layout Area Description

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

AREATEXTS - Layout Area Texts

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

AREALONGTEXTS - Layout Area Long Texts

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

Copy and paste ABAP code example for PCHEAD_ALOG_WRITE 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:
lt_px_t_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_catalogbasedata  TYPE BAPIPCWWMI, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_layout  TYPE BAPIPCTWGV, "   
lt_catalogname  TYPE STANDARD TABLE OF BAPIPCWWMIT, "   
lt_variants  TYPE STANDARD TABLE OF BAPIPCWWMV, "   
lt_variantnames  TYPE STANDARD TABLE OF BAPIPCWWVT, "   
lt_layoutname  TYPE STANDARD TABLE OF BAPIPCTWGVT, "   
lt_areas  TYPE STANDARD TABLE OF BAPIPCTWGLV, "   
lt_areanames  TYPE STANDARD TABLE OF BAPIPCTWGLVT, "   
lt_areatexts  TYPE STANDARD TABLE OF BAPIPCWLMT, "   
lt_arealongtexts  TYPE STANDARD TABLE OF BAPIPCLTEXT. "   

  CALL FUNCTION 'PCHEAD_ALOG_WRITE'  "NOTRANSL: ALE-Eingang PCHEAD: Anwendungslog schreiben
    EXPORTING
         CATALOGBASEDATA = lv_catalogbasedata
         LAYOUT = lv_layout
    TABLES
         PX_T_RETURN = lt_px_t_return
         EXTENSIONIN = lt_extensionin
         CATALOGNAME = lt_catalogname
         VARIANTS = lt_variants
         VARIANTNAMES = lt_variantnames
         LAYOUTNAME = lt_layoutname
         AREAS = lt_areas
         AREANAMES = lt_areanames
         AREATEXTS = lt_areatexts
         AREALONGTEXTS = lt_arealongtexts
. " PCHEAD_ALOG_WRITE




ABAP code using 7.40 inline data declarations to call FM PCHEAD_ALOG_WRITE

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!