SAP UPDATE_T8JSC Function Module for Update function for T8JSC
UPDATE_T8JSC is a standard update t8jsc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update function for T8JSC 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 update t8jsc FM, simply by entering the name UPDATE_T8JSC into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJV1
Program Name: SAPLGJV1
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function UPDATE_T8JSC 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 'UPDATE_T8JSC'"Update function for T8JSC.
EXPORTING
VENTURE_KEY = "
TABLES
IT8JSC = "Substitute cost objects
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for UPDATE_T8JSC
VENTURE_KEY -
Data type: T8JVOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for UPDATE_T8JSC
IT8JSC - Substitute cost objects
Data type: T8JSCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - any returncode <> 0
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UPDATE_T8JSC 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: | ||||
| lt_it8jsc | TYPE STANDARD TABLE OF T8JSC, " | |||
| lv_not_found | TYPE T8JSC, " | |||
| lv_venture_key | TYPE T8JV. " |
|   CALL FUNCTION 'UPDATE_T8JSC' "Update function for T8JSC |
| EXPORTING | ||
| VENTURE_KEY | = lv_venture_key | |
| TABLES | ||
| IT8JSC | = lt_it8jsc | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " UPDATE_T8JSC | ||
ABAP code using 7.40 inline data declarations to call FM UPDATE_T8JSC
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