SAP MILL_VS_FIELD_CONTROL_PBO Function Module for Rev.Rec.: Field Modification Sales
MILL_VS_FIELD_CONTROL_PBO is a standard mill vs field control pbo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Rev.Rec.: Field Modification Sales 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 mill vs field control pbo FM, simply by entering the name MILL_VS_FIELD_CONTROL_PBO into the relevant SAP transaction such as SE37 or SE38.
Function Group: MILL_VS
Program Name: SAPLMILL_VS
Main Program: SAPLMILL_VS
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MILL_VS_FIELD_CONTROL_PBO 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 'MILL_VS_FIELD_CONTROL_PBO'"Rev.Rec.: Field Modification Sales.
EXPORTING
IF_SCREEN_NAME = "
IS_VBAP = "
IS_XVBUP = "
IF_AUART = "
CHANGING
CF_SCREEN_ACTIVE = "
CF_SCREEN_INVISIBLE = "
CF_SCREEN_INPUT = "
IMPORTING Parameters details for MILL_VS_FIELD_CONTROL_PBO
IF_SCREEN_NAME -
Data type: FELD-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
IS_VBAP -
Data type: VBAPOptional: No
Call by Reference: Yes
IS_XVBUP -
Data type: VBUPVBOptional: No
Call by Reference: Yes
IF_AUART -
Data type: VBAK-AUARTOptional: No
Call by Reference: Yes
CHANGING Parameters details for MILL_VS_FIELD_CONTROL_PBO
CF_SCREEN_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
CF_SCREEN_INVISIBLE -
Data type:Optional: No
Call by Reference: Yes
CF_SCREEN_INPUT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MILL_VS_FIELD_CONTROL_PBO 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_if_screen_name | TYPE FELD-NAME, " | |||
| lv_cf_screen_active | TYPE FELD, " | |||
| lv_is_vbap | TYPE VBAP, " | |||
| lv_cf_screen_invisible | TYPE VBAP, " | |||
| lv_is_xvbup | TYPE VBUPVB, " | |||
| lv_cf_screen_input | TYPE VBUPVB, " | |||
| lv_if_auart | TYPE VBAK-AUART. " |
|   CALL FUNCTION 'MILL_VS_FIELD_CONTROL_PBO' "Rev.Rec.: Field Modification Sales |
| EXPORTING | ||
| IF_SCREEN_NAME | = lv_if_screen_name | |
| IS_VBAP | = lv_is_vbap | |
| IS_XVBUP | = lv_is_xvbup | |
| IF_AUART | = lv_if_auart | |
| CHANGING | ||
| CF_SCREEN_ACTIVE | = lv_cf_screen_active | |
| CF_SCREEN_INVISIBLE | = lv_cf_screen_invisible | |
| CF_SCREEN_INPUT | = lv_cf_screen_input | |
| . " MILL_VS_FIELD_CONTROL_PBO | ||
ABAP code using 7.40 inline data declarations to call FM MILL_VS_FIELD_CONTROL_PBO
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 NAME FROM FELD INTO @DATA(ld_if_screen_name). | ||||
| "SELECT single AUART FROM VBAK INTO @DATA(ld_if_auart). | ||||
Search for further information about these or an SAP related objects