SAP ALE_CONDITION_CONTRACT_CLONE Function Module for BAPI -> IDoc: ALE_CONDITION_CONTRACT_CLONE









ALE_CONDITION_CONTRACT_CLONE is a standard ale condition contract clone SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI -> IDoc: ALE_CONDITION_CONTRACT_CLONE 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 ale condition contract clone FM, simply by entering the name ALE_CONDITION_CONTRACT_CLONE into the relevant SAP transaction such as SE37 or SE38.

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



Function ALE_CONDITION_CONTRACT_CLONE 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 'ALE_CONDITION_CONTRACT_CLONE'"BAPI -> IDoc: ALE_CONDITION_CONTRACT_CLONE
  EXPORTING
   CONDITIONCONTRACTNUMBER =  "Condition Contract Number
*  TESTRUN =  "Switch to Simulation Session for Write BAPIs
*  CLONEASSUCCESSOR =  "
*  OBJ_TYPE = 'BUS2235' "
*  SERIAL_ID = '0' "

TABLES
   RECEIVERS =  "
*  COMMUNICATION_DOCUMENTS =  "
*  APPLICATION_OBJECTS =  "

EXCEPTIONS
   ERROR_CREATING_IDOCS = 1
.



IMPORTING Parameters details for ALE_CONDITION_CONTRACT_CLONE

CONDITIONCONTRACTNUMBER - Condition Contract Number

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

TESTRUN - Switch to Simulation Session for Write BAPIs

Data type: WCB_FOR_BAPI-TESTRUN
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLONEASSUCCESSOR -

Data type: WCB_FOR_BAPI-CLONE_AS_SUCCESSOR
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJ_TYPE -

Data type: SERIAL-OBJ_TYPE
Default: 'BUS2235'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SERIAL_ID -

Data type: SERIAL-CHNUM
Default: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ALE_CONDITION_CONTRACT_CLONE

RECEIVERS -

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

COMMUNICATION_DOCUMENTS -

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

APPLICATION_OBJECTS -

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

EXCEPTIONS details

ERROR_CREATING_IDOCS -

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

Copy and paste ABAP code example for ALE_CONDITION_CONTRACT_CLONE 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_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS, "   
lv_error_creating_idocs  TYPE BDI_LOGSYS, "   
lv_conditioncontractnumber  TYPE BAPICCKEY-CONDITION_CONTRACT_NUMBER, "   
lv_testrun  TYPE WCB_FOR_BAPI-TESTRUN, "   
lt_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_cloneassuccessor  TYPE WCB_FOR_BAPI-CLONE_AS_SUCCESSOR, "   
lt_application_objects  TYPE STANDARD TABLE OF SWOTOBJID, "   
lv_obj_type  TYPE SERIAL-OBJ_TYPE, "   'BUS2235'
lv_serial_id  TYPE SERIAL-CHNUM. "   '0'

  CALL FUNCTION 'ALE_CONDITION_CONTRACT_CLONE'  "BAPI -> IDoc: ALE_CONDITION_CONTRACT_CLONE
    EXPORTING
         CONDITIONCONTRACTNUMBER = lv_conditioncontractnumber
         TESTRUN = lv_testrun
         CLONEASSUCCESSOR = lv_cloneassuccessor
         OBJ_TYPE = lv_obj_type
         SERIAL_ID = lv_serial_id
    TABLES
         RECEIVERS = lt_receivers
         COMMUNICATION_DOCUMENTS = lt_communication_documents
         APPLICATION_OBJECTS = lt_application_objects
    EXCEPTIONS
        ERROR_CREATING_IDOCS = 1
. " ALE_CONDITION_CONTRACT_CLONE




ABAP code using 7.40 inline data declarations to call FM ALE_CONDITION_CONTRACT_CLONE

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 CONDITION_CONTRACT_NUMBER FROM BAPICCKEY INTO @DATA(ld_conditioncontractnumber).
 
"SELECT single TESTRUN FROM WCB_FOR_BAPI INTO @DATA(ld_testrun).
 
 
"SELECT single CLONE_AS_SUCCESSOR FROM WCB_FOR_BAPI INTO @DATA(ld_cloneassuccessor).
 
 
"SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type).
DATA(ld_obj_type) = 'BUS2235'.
 
"SELECT single CHNUM FROM SERIAL INTO @DATA(ld_serial_id).
DATA(ld_serial_id) = '0'.
 


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!