SAP ALE_PCSTAT_CREATE Function Module for BAPI -> IDoc: ALE_PCSTAT_CREATE









ALE_PCSTAT_CREATE is a standard ale pcstat create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_PCSTAT_CREATE 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 ale pcstat create FM, simply by entering the name ALE_PCSTAT_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_PCSTAT_CREATE 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 'ALE_PCSTAT_CREATE'"BAPI -> IDoc: ALE_PCSTAT_CREATE
  EXPORTING
   GENERALDATA =  "
*  TOTAL =  "Total Invoice Data
*  SERIAL_ID = '0' "

TABLES
   POSITIONDATAVALUE =  "
*  POSITIONDATATAX =  "
*  POSITIONDATALOG =  "
*  POSITIONDATAADDR =  "
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "
*  APPLICATION_OBJECTS =  "

EXCEPTIONS
   ERROR_CREATING_IDOCS = 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_SAPLBBP_PC_001 Userexit for P-Card datafeed

IMPORTING Parameters details for ALE_PCSTAT_CREATE

GENERALDATA -

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

TOTAL - Total Invoice Data

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

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_PCSTAT_CREATE

POSITIONDATAVALUE -

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

POSITIONDATATAX -

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

POSITIONDATALOG -

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

POSITIONDATAADDR -

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

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

Copy and paste ABAP code example for ALE_PCSTAT_CREATE 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_generaldata  TYPE BAPIPCGEN, "   
lt_positiondatavalue  TYPE STANDARD TABLE OF BAPIPCPOS, "   
lv_error_creating_idocs  TYPE BAPIPCPOS, "   
lv_total  TYPE BAPIPCTOT, "   
lt_positiondatatax  TYPE STANDARD TABLE OF BAPIPCTAX, "   
lv_serial_id  TYPE SERIAL-CHNUM, "   '0'
lt_positiondatalog  TYPE STANDARD TABLE OF BAPIPCLOG, "   
lt_positiondataaddr  TYPE STANDARD TABLE OF BAPIPCADD, "   
lt_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID. "   

  CALL FUNCTION 'ALE_PCSTAT_CREATE'  "BAPI -> IDoc: ALE_PCSTAT_CREATE
    EXPORTING
         GENERALDATA = lv_generaldata
         TOTAL = lv_total
         SERIAL_ID = lv_serial_id
    TABLES
         POSITIONDATAVALUE = lt_positiondatavalue
         POSITIONDATATAX = lt_positiondatatax
         POSITIONDATALOG = lt_positiondatalog
         POSITIONDATAADDR = lt_positiondataaddr
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_PCSTAT_CREATE




ABAP code using 7.40 inline data declarations to call FM ALE_PCSTAT_CREATE

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.

 
 
 
 
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 
 
 
 
 
 


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!