SAP POS_CASHIER_STAT_HEAD Function Module for NOTRANSL: Kassiererstatistik: Kopfsegment in Anwendungsbeleg übernehmen









POS_CASHIER_STAT_HEAD is a standard pos cashier stat head 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: Kassiererstatistik: Kopfsegment in Anwendungsbeleg übernehmen 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 pos cashier stat head FM, simply by entering the name POS_CASHIER_STAT_HEAD into the relevant SAP transaction such as SE37 or SE38.

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



Function POS_CASHIER_STAT_HEAD 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 'POS_CASHIER_STAT_HEAD'"NOTRANSL: Kassiererstatistik: Kopfsegment in Anwendungsbeleg übernehmen
EXPORTING
I_SEGMENT = "
I_PARSER_INFO = "Information Provided by the Parser

IMPORTING
O_APPLICATION_VARIABLES = "Variables That the Parser Receives from the Application

EXCEPTIONS
ERROR_IN_APPLICATION = 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_SAPLWPUE_001 GR Check (Correct Quantities)
EXIT_SAPLWPUE_002 GR Control (Different Quantities)
EXIT_SAPLWPUE_050 POS Inbound Processing Messages
EXIT_SAPLWPUE_100 Do Not Use! User Exit for Sales Audit: Header for IDoc WPUBON01
EXIT_SAPLWPUE_101 Do Not Use! User Exit for Sales Audit: Line Item in IDoc WPUBON0
EXIT_SAPLWPUE_102 IDoc WPUBON01 Before Document is Posted
EXIT_SAPLWPUE_103 Do Not Use: Sales Audit: Exit for User Segment E1WXX01
EXIT_SAPLWPUE_104 IDoc WPUBON01 Before Inbound Processing
EXIT_SAPLWPUE_105 Check Whether IDoc Transaction WPUBON01 Is Compressable
EXIT_SAPLWPUE_106 IDoc WPUBON01 Process User Segment
EXIT_SAPLWPUE_109 IDoc WPUBON01 After Inbound Processing
EXIT_SAPLWPUE_110 IDoc WPUUMS01 Before Posting
EXIT_SAPLWPUE_111 Do Not Use! User Exit for User Segment in IDoc WPUUMS
EXIT_SAPLWPUE_112 IDoc WPUUMS01 Before Inbound Processing
EXIT_SAPLWPUE_113 Process IDoc WPUUMS01 User Segment
EXIT_SAPLWPUE_119 IDoc WPUUMS01 After Inbound Processing
EXIT_SAPLWPUE_120 IDoc WPUKSR01 Before Document Is Posted
EXIT_SAPLWPUE_121 Do Not Use! User Exit for User Segment in IDoc WPUKSR
EXIT_SAPLWPUE_122 IDoc WPUKSR01 Process User Segment
EXIT_SAPLWPUE_123 IDoc WPUKSR01 Before Inbound Processing
EXIT_SAPLWPUE_129 IDoc WPUKSR01 After Inbound Processing
EXIT_SAPLWPUE_130 IDoc WPUFIB01 Before Document Is Posted
EXIT_SAPLWPUE_131 IDoc WPUFIB01 Process User Segment
EXIT_SAPLWPUE_132 IDoc WPUFIB01 Before Inbound Processing
EXIT_SAPLWPUE_139 IDoc WPUFIB01 After Inbound Processing
EXIT_SAPLWPUE_140 IDoc WPUWB01 Before Document Is Posted
EXIT_SAPLWPUE_141 IDoc WPUWBW01 Process User Segment
EXIT_SAPLWPUE_142 IDoc WPUWBW01 Before Inbound Processing
EXIT_SAPLWPUE_149 IDoc WPUWBW01 After Inbound Processing
EXIT_SAPLWPUE_152 IDoc WPUTAB01 Before Inbound Processing
EXIT_SAPLWPUE_159 IDoc WPUTAB01 After Inbound Processing

IMPORTING Parameters details for POS_CASHIER_STAT_HEAD

I_SEGMENT -

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

I_PARSER_INFO - Information Provided by the Parser

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

EXPORTING Parameters details for POS_CASHIER_STAT_HEAD

O_APPLICATION_VARIABLES - Variables That the Parser Receives from the Application

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

EXCEPTIONS details

ERROR_IN_APPLICATION -

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

Copy and paste ABAP code example for POS_CASHIER_STAT_HEAD 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_i_segment  TYPE EDIDD, "   
lv_error_in_application  TYPE EDIDD, "   
lv_o_application_variables  TYPE PARSER_APPLICATION_VARIABLES, "   
lv_i_parser_info  TYPE PARSER_INFO_ENTRY. "   

  CALL FUNCTION 'POS_CASHIER_STAT_HEAD'  "NOTRANSL: Kassiererstatistik: Kopfsegment in Anwendungsbeleg übernehmen
    EXPORTING
         I_SEGMENT = lv_i_segment
         I_PARSER_INFO = lv_i_parser_info
    IMPORTING
         O_APPLICATION_VARIABLES = lv_o_application_variables
    EXCEPTIONS
        ERROR_IN_APPLICATION = 1
. " POS_CASHIER_STAT_HEAD




ABAP code using 7.40 inline data declarations to call FM POS_CASHIER_STAT_HEAD

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!