SAP SD_SCD_CHECK_CHANGES Function Module for NOTRANSL: Überprüfung eines Frachtkostendokumentes auf Änderungen

Search SAP Function Modules

SD_SCD_CHECK_CHANGES is a standard sd scd check changes 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: Überprüfung eines Frachtkostendokumentes auf Änderungen 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 sd scd check changes FM, simply by entering the name SD_SCD_CHECK_CHANGES into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_SCD_CHECK_CHANGES 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 'SD_SCD_CHECK_CHANGES'"NOTRANSL: Überprüfung eines Frachtkostendokumentes auf Änderungen
  EXPORTING
*  I_BLDGR = ' ' "Screen group
*  I_TRTYP = ' ' "Transaction type
   I_SCD =  "

CHANGING
   C_CHANGE =  "Update indicator

EXCEPTIONS
   NO_CHANGE = 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_SAPLV54U_001 Review of Shipment Costs for Changes
EXIT_SAPLV54U_002 Review of Shipment Costs for Completeness
EXIT_SAPLV54U_003 Specification of shipment cost number
EXIT_SAPLV54U_004 Shipment Cost Processing: Prepare New Objects for Saving
EXIT_SAPLV54U_005 Shipment Cost Processing: Save New Objects
EXIT_SAPLV54U_006 Shipment Purchase Order - Sales Data (Header)
EXIT_SAPLV54U_007 Shipment Purchase Order - Sales Data (Item)

IMPORTING Parameters details for SD_SCD_CHECK_CHANGES

I_BLDGR - Screen group

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

I_TRTYP - Transaction type

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

I_SCD -

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

CHANGING Parameters details for SD_SCD_CHECK_CHANGES

C_CHANGE - Update indicator

Data type: VFKKD-UPDKZ
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_CHANGE -

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

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

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