SAP CRM_ISU_BASKET_CHDOC_UP Function Module for EEW Template: chdoc update









CRM_ISU_BASKET_CHDOC_UP is a standard crm isu basket chdoc up SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EEW Template: chdoc update 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 crm isu basket chdoc up FM, simply by entering the name CRM_ISU_BASKET_CHDOC_UP into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_ISU_BASKET_CHDOC_UP 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 'CRM_ISU_BASKET_CHDOC_UP'"EEW Template: chdoc update
  EXPORTING
   OBJECTID =  "Object value
*  UPD_ICDTXT = ' ' "Change type (U, I, E, D)
*  UPD_FLAG = ' ' "Change type (U, I, E, D)
   TCODE =  "Transaction in which a change was made
   UTIME =  "Time changed
   UDATE =  "Creation date of the change document
   USERNAME =  "User name of the person responsible in change document
*  PLANNED_CHANGE_NUMBER = ' ' "Planned change number
*  OBJECT_CHANGE_INDICATOR = 'U' "Application object change type (U, I, E, D)
*  PLANNED_OR_REAL_CHANGES = ' ' "Application object change type (U, I, E, D)
*  NO_CHANGE_POINTERS = ' ' "Application object change type (U, I, E, D)

TABLES
   ICDTXT =  "Change documents: Text changes
   XTABLE =  "Change Document Structure; Generated by RSSCD000
   YTABLE =  "Change Document Structure; Generated by RSSCD000
.



IMPORTING Parameters details for CRM_ISU_BASKET_CHDOC_UP

OBJECTID - Object value

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

UPD_ICDTXT - Change type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

UPD_FLAG - Change type (U, I, E, D)

Data type: CDPOS-CHNGIND
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

TCODE - Transaction in which a change was made

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

UTIME - Time changed

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

UDATE - Creation date of the change document

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

USERNAME - User name of the person responsible in change document

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

PLANNED_CHANGE_NUMBER - Planned change number

Data type: CDHDR-PLANCHNGNR
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_CHANGE_INDICATOR - Application object change type (U, I, E, D)

Data type: CDHDR-CHANGE_IND
Default: 'U'
Optional: No
Call by Reference: No ( called with pass by value option)

PLANNED_OR_REAL_CHANGES - Application object change type (U, I, E, D)

Data type: CDHDR-CHANGE_IND
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

NO_CHANGE_POINTERS - Application object change type (U, I, E, D)

Data type: CDHDR-CHANGE_IND
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CRM_ISU_BASKET_CHDOC_UP

ICDTXT - Change documents: Text changes

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

XTABLE - Change Document Structure; Generated by RSSCD000

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

YTABLE - Change Document Structure; Generated by RSSCD000

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

Copy and paste ABAP code example for CRM_ISU_BASKET_CHDOC_UP 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_icdtxt  TYPE STANDARD TABLE OF CDTXT, "   
lv_objectid  TYPE CDHDR-OBJECTID, "   
lv_upd_icdtxt  TYPE CDPOS-CHNGIND, "   SPACE
lv_upd_flag  TYPE CDPOS-CHNGIND, "   SPACE
lv_tcode  TYPE CDHDR-TCODE, "   
lt_xtable  TYPE STANDARD TABLE OF VCRMA_ISU_BASKET, "   
lv_utime  TYPE CDHDR-UTIME, "   
lt_ytable  TYPE STANDARD TABLE OF VCRMA_ISU_BASKET, "   
lv_udate  TYPE CDHDR-UDATE, "   
lv_username  TYPE CDHDR-USERNAME, "   
lv_planned_change_number  TYPE CDHDR-PLANCHNGNR, "   SPACE
lv_object_change_indicator  TYPE CDHDR-CHANGE_IND, "   'U'
lv_planned_or_real_changes  TYPE CDHDR-CHANGE_IND, "   SPACE
lv_no_change_pointers  TYPE CDHDR-CHANGE_IND. "   SPACE

  CALL FUNCTION 'CRM_ISU_BASKET_CHDOC_UP'  "EEW Template: chdoc update
    EXPORTING
         OBJECTID = lv_objectid
         UPD_ICDTXT = lv_upd_icdtxt
         UPD_FLAG = lv_upd_flag
         TCODE = lv_tcode
         UTIME = lv_utime
         UDATE = lv_udate
         USERNAME = lv_username
         PLANNED_CHANGE_NUMBER = lv_planned_change_number
         OBJECT_CHANGE_INDICATOR = lv_object_change_indicator
         PLANNED_OR_REAL_CHANGES = lv_planned_or_real_changes
         NO_CHANGE_POINTERS = lv_no_change_pointers
    TABLES
         ICDTXT = lt_icdtxt
         XTABLE = lt_xtable
         YTABLE = lt_ytable
. " CRM_ISU_BASKET_CHDOC_UP




ABAP code using 7.40 inline data declarations to call FM CRM_ISU_BASKET_CHDOC_UP

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 OBJECTID FROM CDHDR INTO @DATA(ld_objectid).
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_icdtxt).
DATA(ld_upd_icdtxt) = ' '.
 
"SELECT single CHNGIND FROM CDPOS INTO @DATA(ld_upd_flag).
DATA(ld_upd_flag) = ' '.
 
"SELECT single TCODE FROM CDHDR INTO @DATA(ld_tcode).
 
 
"SELECT single UTIME FROM CDHDR INTO @DATA(ld_utime).
 
 
"SELECT single UDATE FROM CDHDR INTO @DATA(ld_udate).
 
"SELECT single USERNAME FROM CDHDR INTO @DATA(ld_username).
 
"SELECT single PLANCHNGNR FROM CDHDR INTO @DATA(ld_planned_change_number).
DATA(ld_planned_change_number) = ' '.
 
"SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_object_change_indicator).
DATA(ld_object_change_indicator) = 'U'.
 
"SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_planned_or_real_changes).
DATA(ld_planned_or_real_changes) = ' '.
 
"SELECT single CHANGE_IND FROM CDHDR INTO @DATA(ld_no_change_pointers).
DATA(ld_no_change_pointers) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!