SAP PACKET_PROCESS_FOR_SITES Function Module for Process Packets (Store-Dependent)









PACKET_PROCESS_FOR_SITES is a standard packet process for sites SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Process Packets (Store-Dependent) 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 packet process for sites FM, simply by entering the name PACKET_PROCESS_FOR_SITES into the relevant SAP transaction such as SE37 or SE38.

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



Function PACKET_PROCESS_FOR_SITES 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 'PACKET_PROCESS_FOR_SITES'"Process Packets (Store-Dependent)
  EXPORTING
   VALID_RANGE =  "Validity Period For Assortment List
   PACKET_INFO =  "BBTYP, DLMOD und C_LIGHT
   T_ART_FOR_SITES =  "Table Type for Store-Specific Article Changes
   T_ALL_SITES =  "Tabelle aller Filialen
   T_SITES_IN_PACKET =  "Tabelle der konkreten Filialen
   T_DLDNR =  "Tabelle mit Downloadnummern

 IMPORTING
   T_EXPORT =  "Table Type for Managing Task Return Information
   T_GROUPS =  "Tabelle für SL-Gruppen
.



IMPORTING Parameters details for PACKET_PROCESS_FOR_SITES

VALID_RANGE - Validity Period For Assortment List

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

PACKET_INFO - BBTYP, DLMOD und C_LIGHT

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

T_ART_FOR_SITES - Table Type for Store-Specific Article Changes

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

T_ALL_SITES - Tabelle aller Filialen

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

T_SITES_IN_PACKET - Tabelle der konkreten Filialen

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

T_DLDNR - Tabelle mit Downloadnummern

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

EXPORTING Parameters details for PACKET_PROCESS_FOR_SITES

T_EXPORT - Table Type for Managing Task Return Information

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

T_GROUPS - Tabelle für SL-Gruppen

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

Copy and paste ABAP code example for PACKET_PROCESS_FOR_SITES 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_t_export  TYPE TASK_EXPORT_TABLE_TYPE, "   
lv_valid_range  TYPE VALID_DATES_TYPE, "   
lv_t_groups  TYPE TABLE_GROUP_INFO_TYPE, "   
lv_packet_info  TYPE PACKET_INFO, "   
lv_t_art_for_sites  TYPE TABLE_ART_FOR_SITES, "   
lv_t_all_sites  TYPE WDL_FIL_TABLE, "   
lv_t_sites_in_packet  TYPE TABLE_SITE_ART_COUNT, "   
lv_t_dldnr  TYPE SITE_BBTYP_DLDNUM_TABLE. "   

  CALL FUNCTION 'PACKET_PROCESS_FOR_SITES'  "Process Packets (Store-Dependent)
    EXPORTING
         VALID_RANGE = lv_valid_range
         PACKET_INFO = lv_packet_info
         T_ART_FOR_SITES = lv_t_art_for_sites
         T_ALL_SITES = lv_t_all_sites
         T_SITES_IN_PACKET = lv_t_sites_in_packet
         T_DLDNR = lv_t_dldnr
    IMPORTING
         T_EXPORT = lv_t_export
         T_GROUPS = lv_t_groups
. " PACKET_PROCESS_FOR_SITES




ABAP code using 7.40 inline data declarations to call FM PACKET_PROCESS_FOR_SITES

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!