SAP POS_TRIGGER_INFO_SEND Function Module for POS-Ausg.: Schicke Trigger-Info an Business Connector

Search SAP Function Modules

POS_TRIGGER_INFO_SEND is a standard pos trigger info send SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for POS-Ausg.: Schicke Trigger-Info an Business Connector 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 trigger info send FM, simply by entering the name POS_TRIGGER_INFO_SEND into the relevant SAP transaction such as SE37 or SE38.

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

Function POS_TRIGGER_INFO_SEND 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_TRIGGER_INFO_SEND'"POS-Ausg.: Schicke Trigger-Info an Business Connector
  EXPORTING
   PI_TRIGGER_NAME =  "Name des vom BC zu erzeugenden Trigger-Files

TABLES
   PIT_IDOC_FILES =  "Namen der vom BC zu eugenden IDOC-Files einer Filiale

.

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_SAPLWPDA_001 POS Interface: Modification of the IDoc Data Material Groups
EXIT_SAPLWPDA_002 POS Interface: Modification of IDoc Data for Material Master
EXIT_SAPLWPDA_003 POS Interface: Modification of IDoc Data for EAN/UPC References
EXIT_SAPLWPDA_004 POS Interface: Modification of IDoc Data for Set Assignments
EXIT_SAPLWPDA_005 POS Interface: Modification of IDoc Data for Follow-On Items
EXIT_SAPLWPDA_006 POS Interface: Modification of IDoc Data for Exchange Rates
EXIT_SAPLWPDA_007 POS Interface: Modification of IDoc Data for Taxes
EXIT_SAPLWPDA_008 POS Interface: Modification of IDoc Data for Personal Data
EXIT_SAPLWPDA_009 POS Interface: Additional Change Pointer Analysis for WP_PLU
EXIT_SAPLWPDA_010 POS Interface: Additional Change Pointer Analysis for WPDSET
EXIT_SAPLWPDA_011 POS Interface: Additional Change Pointer Analysis for WPDNAC
EXIT_SAPLWPDA_012 POS Interface: Additional Change Pointer Analysis for WPDWGR
EXIT_SAPLWPDA_013 POS Interface: Additional Change Pointer Analysis for WP_PER
EXIT_SAPLWPDA_015 POS Outbound: Additional Filter Option in Condition Pointer Analysis
EXIT_SAPLWPDA_016 POS Interface: Modification of IDoc Data for Promotion Discounts
EXIT_SAPLWPDA_017 POS Interface: Additional Change Pointer Analysis for WPDREB

IMPORTING Parameters details for POS_TRIGGER_INFO_SEND

PI_TRIGGER_NAME - Name des vom BC zu erzeugenden Trigger-Files

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

TABLES Parameters details for POS_TRIGGER_INFO_SEND

PIT_IDOC_FILES - Namen der vom BC zu eugenden IDOC-Files einer Filiale

Data type: WPDTEXT
Optional: No
Call by Reference: Yes

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

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