SAP Function Modules

comments icon Comments

ALE_CONFIRMATION_INPUT SAP Function module







ALE_CONFIRMATION_INPUT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ALE_CONFIRMATION_INPUT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: HRIL
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ALE_CONFIRMATION_INPUT - ALE CONFIRMATION INPUT 





CALL FUNCTION 'ALE_CONFIRMATION_INPUT' "
* EXPORTING
*   serial_id = '0'             " serial-chnum
  TABLES
    confirmations =             " bapi_pll80
    receivers =                 " bdi_logsys
*   communication_documents =   " swotobjid
*   application_objects =       " swotobjid
  EXCEPTIONS
    ERROR_CREATING_IDOCS = 1    "
    .  "  ALE_CONFIRMATION_INPUT

ABAP code example for Function Module ALE_CONFIRMATION_INPUT





The ABAP code below is a full code listing to execute function module ALE_CONFIRMATION_INPUT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_confirmations    TYPE STANDARD TABLE OF BAPI_PLL80,"TABLES PARAM
wa_confirmations  LIKE LINE OF it_confirmations
,
it_receivers    TYPE STANDARD TABLE OF BDI_LOGSYS,"TABLES PARAM
wa_receivers  LIKE LINE OF it_receivers
,
it_communication_documents    TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_communication_documents  LIKE LINE OF it_communication_documents
,
it_application_objects    TYPE STANDARD TABLE OF SWOTOBJID,"TABLES PARAM
wa_application_objects  LIKE LINE OF it_application_objects
.





DATA(ld_serial_id) = Check type of data required
 

"populate fields of struture and append to itab
append wa_confirmations to it_confirmations.
 

"populate fields of struture and append to itab
append wa_receivers to it_receivers.
 

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents.
 

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects.
.

CALL FUNCTION 'ALE_CONFIRMATION_INPUT'
* EXPORTING
*   serial_id =                  ld_serial_id
  TABLES
    confirmations =              it_confirmations
    receivers =                  it_receivers
*   communication_documents =    it_communication_documents
*   application_objects =        it_application_objects
  EXCEPTIONS
    ERROR_CREATING_IDOCS =       1
    .  "  ALE_CONFIRMATION_INPUT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_serial_id  TYPE SERIAL-CHNUM ,
it_confirmations  TYPE STANDARD TABLE OF BAPI_PLL80 ,
wa_confirmations  LIKE LINE OF it_confirmations,
it_receivers  TYPE STANDARD TABLE OF BDI_LOGSYS ,
wa_receivers  LIKE LINE OF it_receivers,
it_communication_documents  TYPE STANDARD TABLE OF SWOTOBJID ,
wa_communication_documents  LIKE LINE OF it_communication_documents,
it_application_objects  TYPE STANDARD TABLE OF SWOTOBJID ,
wa_application_objects  LIKE LINE OF it_application_objects.





ld_serial_id = Check type of data required 

"populate fields of struture and append to itab
append wa_confirmations to it_confirmations. 

"populate fields of struture and append to itab
append wa_receivers to it_receivers. 

"populate fields of struture and append to itab
append wa_communication_documents to it_communication_documents. 

"populate fields of struture and append to itab
append wa_application_objects to it_application_objects.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ALE_CONFIRMATION_INPUT or its description.


   
 

ALE_CONFIRMATION_INPUT - 
ALE_CONDITION_CONTRACT_READ - BAPI -> IDoc: ALE_CONDITION_CONTRACT_READ
ALE_CONDITION_CONTRACT_CREATE - BAPI -> IDoc: ALE_CONDITION_CONTRACT_CREATE
ALE_CONDITION_CONTRACT_CLONE - BAPI -> IDoc: ALE_CONDITION_CONTRACT_CLONE
ALE_CONDITION_CONTRACT_CHANGE - BAPI -> IDoc: ALE_CONDITION_CONTRACT_CHANGE
ALE_COMPONET_GET -