SAP CHVW_EXPLODE_ALL Function Module for NOTRANSL: mehrstufige Auflösung des Chargenverwendungsnachweis

Search SAP Function Modules

CHVW_EXPLODE_ALL is a standard chvw explode all 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: mehrstufige Auflösung des Chargenverwendungsnachweis 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 chvw explode all FM, simply by entering the name CHVW_EXPLODE_ALL into the relevant SAP transaction such as SE37 or SE38.

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

Function CHVW_EXPLODE_ALL 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 'CHVW_EXPLODE_ALL'"NOTRANSL: mehrstufige Auflösung des Chargenverwendungsnachweis
  EXPORTING
   I_MATNR =  "
   I_WERKS =  "Plant
   I_CHARG =  "Batch Number
   I_DFCHVW =  "
*  I_CUST_SORT = ' ' "Checkbox
*  I_VGEBELN =  "Purchasing Document Number
*  I_VGEBELP =  "Item Number of Purchasing Document
*  CTYPE =  "Node Type

TABLES
   T_SHADOW =  "Transfer Structure for Batch Where-Used List Display
*  T_PLANTS =  "Range Table of Permissible Plants

EXCEPTIONS
   INVALID_INPUT_DATA = 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_SAPLCHVW_001 BWUL: Fill fields in append CHVWSHADOW_Z

IMPORTING Parameters details for CHVW_EXPLODE_ALL

I_MATNR -

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

I_WERKS - Plant

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

I_CHARG - Batch Number

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

I_DFCHVW -

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

I_CUST_SORT - Checkbox

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

I_VGEBELN - Purchasing Document Number

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

I_VGEBELP - Item Number of Purchasing Document

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

CTYPE - Node Type

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

TABLES Parameters details for CHVW_EXPLODE_ALL

T_SHADOW - Transfer Structure for Batch Where-Used List Display

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

T_PLANTS - Range Table of Permissible Plants

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

EXCEPTIONS details

INVALID_INPUT_DATA -

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

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

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