SAP POSED_FILL_DETAIL_WPUUMS Function Module for NOTRANSL: Statusanalyse für WPUUMS Detailebene









POSED_FILL_DETAIL_WPUUMS is a standard posed fill detail wpuums 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: Statusanalyse für WPUUMS Detailebene 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 posed fill detail wpuums FM, simply by entering the name POSED_FILL_DETAIL_WPUUMS into the relevant SAP transaction such as SE37 or SE38.

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



Function POSED_FILL_DETAIL_WPUUMS 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 'POSED_FILL_DETAIL_WPUUMS'"NOTRANSL: Statusanalyse für WPUUMS Detailebene
EXPORTING
I_WPUUMS_LINE_INDEX = "
I_EDIDC = "Control Record (IDoc)
I_EDIDD = "Data Record (IDoc)
I_E1WPU01_INDEX = "

IMPORTING
O_LOCKED = "
O_SEGNUM = "Number of SAP Segment
O_SEGNUM_END = "Number of SAP Segment

CHANGING
O_OVERVIEW_ENTRY = "Overview List for Sales Audit Editor

TABLES
* O_E1WPU02 = "POS interface, inbound sales, items
* O_LINE_ITEM_VALUE = "POS interface, inbound sales discounts
* O_WPLST = "POS Interface: Processing Log
* O_2STATUS = "Boolean Variable
.



IMPORTING Parameters details for POSED_FILL_DETAIL_WPUUMS

I_WPUUMS_LINE_INDEX -

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

I_EDIDC - Control Record (IDoc)

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

I_EDIDD - Data Record (IDoc)

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

I_E1WPU01_INDEX -

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

EXPORTING Parameters details for POSED_FILL_DETAIL_WPUUMS

O_LOCKED -

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

O_SEGNUM - Number of SAP Segment

Data type: EDIDD-SEGNUM
Optional: No
Call by Reference: Yes

O_SEGNUM_END - Number of SAP Segment

Data type: EDIDD-SEGNUM
Optional: No
Call by Reference: Yes

CHANGING Parameters details for POSED_FILL_DETAIL_WPUUMS

O_OVERVIEW_ENTRY - Overview List for Sales Audit Editor

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

TABLES Parameters details for POSED_FILL_DETAIL_WPUUMS

O_E1WPU02 - POS interface, inbound sales, items

Data type: E1WPU02
Optional: Yes
Call by Reference: Yes

O_LINE_ITEM_VALUE - POS interface, inbound sales discounts

Data type: E1WPU03
Optional: Yes
Call by Reference: Yes

O_WPLST - POS Interface: Processing Log

Data type: WPLST
Optional: Yes
Call by Reference: Yes

O_2STATUS - Boolean Variable

Data type: BOOLE
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for POSED_FILL_DETAIL_WPUUMS 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_o_locked  TYPE C, "   
lt_o_e1wpu02  TYPE STANDARD TABLE OF E1WPU02, "   
lv_o_overview_entry  TYPE POSEDOLIST, "   
lv_i_wpuums_line_index  TYPE I, "   
lv_i_edidc  TYPE EDIDC, "   
lv_o_segnum  TYPE EDIDD-SEGNUM, "   
lt_o_line_item_value  TYPE STANDARD TABLE OF E1WPU03, "   
lv_i_edidd  TYPE EDIDD, "   
lt_o_wplst  TYPE STANDARD TABLE OF WPLST, "   
lv_o_segnum_end  TYPE EDIDD-SEGNUM, "   
lt_o_2status  TYPE STANDARD TABLE OF BOOLE, "   
lv_i_e1wpu01_index  TYPE I. "   

  CALL FUNCTION 'POSED_FILL_DETAIL_WPUUMS'  "NOTRANSL: Statusanalyse für WPUUMS Detailebene
    EXPORTING
         I_WPUUMS_LINE_INDEX = lv_i_wpuums_line_index
         I_EDIDC = lv_i_edidc
         I_EDIDD = lv_i_edidd
         I_E1WPU01_INDEX = lv_i_e1wpu01_index
    IMPORTING
         O_LOCKED = lv_o_locked
         O_SEGNUM = lv_o_segnum
         O_SEGNUM_END = lv_o_segnum_end
    CHANGING
         O_OVERVIEW_ENTRY = lv_o_overview_entry
    TABLES
         O_E1WPU02 = lt_o_e1wpu02
         O_LINE_ITEM_VALUE = lt_o_line_item_value
         O_WPLST = lt_o_wplst
         O_2STATUS = lt_o_2status
. " POSED_FILL_DETAIL_WPUUMS




ABAP code using 7.40 inline data declarations to call FM POSED_FILL_DETAIL_WPUUMS

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 SEGNUM FROM EDIDD INTO @DATA(ld_o_segnum).
 
 
 
 
"SELECT single SEGNUM FROM EDIDD INTO @DATA(ld_o_segnum_end).
 
 
 


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!