SAP BORSHP_UPDATE_VTTP_NOEX Function Module for NOTRANSL: Ändern Tabelle BORGR_VTTP_NOEX

Search SAP Function Modules

BORSHP_UPDATE_VTTP_NOEX is a standard borshp update vttp noex 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: Ändern Tabelle BORGR_VTTP_NOEX 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 borshp update vttp noex FM, simply by entering the name BORSHP_UPDATE_VTTP_NOEX into the relevant SAP transaction such as SE37 or SE38.

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

Function BORSHP_UPDATE_VTTP_NOEX 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 'BORSHP_UPDATE_VTTP_NOEX'"NOTRANSL: Ändern Tabelle BORGR_VTTP_NOEX
  EXPORTING
   IT_BORGR_VTTP_NOEX_UPD =  "Table Type for BORGR_VTTP_NOEX_UPD
*  I_USE_UPDATE_TASK =  "Checkbox
*  I_NO_BUFFER_UPDATE =  "Checkbox
*  I_NO_DATABASE_UPDATE =  "Checkbox

 IMPORTING
   ET_BORGR_VTTP_NOEX_INS =  "Table Type for BORGR_VTTP_NOEX
   ET_BORGR_VTTP_NOEX_DEL =  "Table Type for BORGR_VTTP_NOEX
   ET_BORGR_VTTP_NOEX_CHA =  "Table Type for BORGR_VTTP_NOEX

EXCEPTIONS
   INVALID_OPERATION = 1 

.

IMPORTING Parameters details for BORSHP_UPDATE_VTTP_NOEX

IT_BORGR_VTTP_NOEX_UPD - Table Type for BORGR_VTTP_NOEX_UPD

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

I_USE_UPDATE_TASK - Checkbox

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

I_NO_BUFFER_UPDATE - Checkbox

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

I_NO_DATABASE_UPDATE - Checkbox

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

EXPORTING Parameters details for BORSHP_UPDATE_VTTP_NOEX

ET_BORGR_VTTP_NOEX_INS - Table Type for BORGR_VTTP_NOEX

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

ET_BORGR_VTTP_NOEX_DEL - Table Type for BORGR_VTTP_NOEX

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

ET_BORGR_VTTP_NOEX_CHA - Table Type for BORGR_VTTP_NOEX

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

EXCEPTIONS details

INVALID_OPERATION - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

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

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