SAP ALE_CUSTOMEREXPINV_RELEASE Function Module for NOTRANSL: BAPI -> IDoc: ALE_CUSTOMEREXPINV_RELEASE
ALE_CUSTOMEREXPINV_RELEASE is a standard ale customerexpinv release 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: BAPI -> IDoc: ALE_CUSTOMEREXPINV_RELEASE 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 customerexpinv release FM, simply by entering the name ALE_CUSTOMEREXPINV_RELEASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: 2144_ALE_OUT
Program Name: SAPL2144_ALE_OUT
Main Program: SAPL2144_ALE_OUT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ALE_CUSTOMEREXPINV_RELEASE 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_CUSTOMEREXPINV_RELEASE'"NOTRANSL: BAPI -> IDoc: ALE_CUSTOMEREXPINV_RELEASE.
EXPORTING
* ENQUEUEALL = 'X' "Document Lock
* TESTRUN = ' ' "Test Run
* OBJ_TYPE = 'BUS2144002' "
* SERIAL_ID = '0' "
TABLES
* DOCUMENTNUMBERRANGE = "Document Number
* DOCDATERANGE = "Document Date
* REFDOCNORANGE = "Reference
* REFDOCNOLONGRANGE = "Reference (Long)
* ALLOCNMBRRANGE = "Assignment
* PAYMTREFRANGE = "Payment Reference
* HEADDATAOUT = "Header Data (Output)
* EXTENSIONOUT = "Enhancements (Output)
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
* CUSTOMERRANGE = "Bill-To Party
* SALESORGRANGE = "Sales Organization
* DISCHANELRANGE = "Distribution Channel
* DIVISIONRANGE = "Division
* COMPCODERANGE = "Company Code
* BILLDATERANGE = "Posting Date
* INVLISTDATERANGE = "Remuneration List Date
* BILLTYPERANGE = "Billing Type
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_CUSTOMEREXPINV_RELEASE
ENQUEUEALL - Document Lock
Data type: BAPIABCON-ENQUEUEALLDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Test Run
Data type: BAPIACHEAD-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'BUS2144002'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID -
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_CUSTOMEREXPINV_RELEASE
DOCUMENTNUMBERRANGE - Document Number
Data type: BAPIACDOCRANOptional: Yes
Call by Reference: No ( called with pass by value option)
DOCDATERANGE - Document Date
Data type: BAPI_RANGESBLDATOptional: Yes
Call by Reference: No ( called with pass by value option)
REFDOCNORANGE - Reference
Data type: BAPI_RANGESXBLNROptional: Yes
Call by Reference: No ( called with pass by value option)
REFDOCNOLONGRANGE - Reference (Long)
Data type: BAPI_RANGESXBLNR_LONGOptional: Yes
Call by Reference: No ( called with pass by value option)
ALLOCNMBRRANGE - Assignment
Data type: BAPI_RANGESZUONROptional: Yes
Call by Reference: No ( called with pass by value option)
PAYMTREFRANGE - Payment Reference
Data type: BAPI_RANGESKIDNOOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADDATAOUT - Header Data (Output)
Data type: BAPICSHEADOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXTENSIONOUT - Enhancements (Output)
Data type: BAPIPAREXOptional: Yes
Call by Reference: No ( called with pass by value option)
RECEIVERS -
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS -
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
CUSTOMERRANGE - Bill-To Party
Data type: BAPI_RANGESKUNNROptional: Yes
Call by Reference: No ( called with pass by value option)
SALESORGRANGE - Sales Organization
Data type: BAPI_RANGESVKORGOptional: Yes
Call by Reference: No ( called with pass by value option)
DISCHANELRANGE - Distribution Channel
Data type: BAPI_RANGESVTWEGOptional: Yes
Call by Reference: No ( called with pass by value option)
DIVISIONRANGE - Division
Data type: BAPI_RANGESSPARTOptional: Yes
Call by Reference: No ( called with pass by value option)
COMPCODERANGE - Company Code
Data type: BAPI_RANGESBUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
BILLDATERANGE - Posting Date
Data type: BAPI_RANGESWFDATOptional: Yes
Call by Reference: No ( called with pass by value option)
INVLISTDATERANGE - Remuneration List Date
Data type: BAPI_RANGESWFDAT_RLOptional: Yes
Call by Reference: No ( called with pass by value option)
BILLTYPERANGE - Billing Type
Data type: BAPI_RANGESLFARTOptional: 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_CUSTOMEREXPINV_RELEASE 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: | ||||
| lv_enqueueall | TYPE BAPIABCON-ENQUEUEALL, " 'X' | |||
| lt_documentnumberrange | TYPE STANDARD TABLE OF BAPIACDOCRAN, " | |||
| lv_error_creating_idocs | TYPE BAPIACDOCRAN, " | |||
| lt_docdaterange | TYPE STANDARD TABLE OF BAPI_RANGESBLDAT, " | |||
| lt_refdocnorange | TYPE STANDARD TABLE OF BAPI_RANGESXBLNR, " | |||
| lt_refdocnolongrange | TYPE STANDARD TABLE OF BAPI_RANGESXBLNR_LONG, " | |||
| lt_allocnmbrrange | TYPE STANDARD TABLE OF BAPI_RANGESZUONR, " | |||
| lt_paymtrefrange | TYPE STANDARD TABLE OF BAPI_RANGESKIDNO, " | |||
| lt_headdataout | TYPE STANDARD TABLE OF BAPICSHEADO, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_testrun | TYPE BAPIACHEAD-TESTRUN, " SPACE | |||
| lt_customerrange | TYPE STANDARD TABLE OF BAPI_RANGESKUNNR, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'BUS2144002' | |||
| lt_salesorgrange | TYPE STANDARD TABLE OF BAPI_RANGESVKORG, " | |||
| lv_serial_id | TYPE SERIAL-CHNUM, " '0' | |||
| lt_dischanelrange | TYPE STANDARD TABLE OF BAPI_RANGESVTWEG, " | |||
| lt_divisionrange | TYPE STANDARD TABLE OF BAPI_RANGESSPART, " | |||
| lt_compcoderange | TYPE STANDARD TABLE OF BAPI_RANGESBUKRS, " | |||
| lt_billdaterange | TYPE STANDARD TABLE OF BAPI_RANGESWFDAT, " | |||
| lt_invlistdaterange | TYPE STANDARD TABLE OF BAPI_RANGESWFDAT_RL, " | |||
| lt_billtyperange | TYPE STANDARD TABLE OF BAPI_RANGESLFART. " |
| CALL FUNCTION 'ALE_CUSTOMEREXPINV_RELEASE' "NOTRANSL: BAPI -> IDoc: ALE_CUSTOMEREXPINV_RELEASE |
| EXPORTING | ||
| ENQUEUEALL | = lv_enqueueall | |
| TESTRUN | = lv_testrun | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| DOCUMENTNUMBERRANGE | = lt_documentnumberrange | |
| DOCDATERANGE | = lt_docdaterange | |
| REFDOCNORANGE | = lt_refdocnorange | |
| REFDOCNOLONGRANGE | = lt_refdocnolongrange | |
| ALLOCNMBRRANGE | = lt_allocnmbrrange | |
| PAYMTREFRANGE | = lt_paymtrefrange | |
| HEADDATAOUT | = lt_headdataout | |
| EXTENSIONOUT | = lt_extensionout | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| CUSTOMERRANGE | = lt_customerrange | |
| SALESORGRANGE | = lt_salesorgrange | |
| DISCHANELRANGE | = lt_dischanelrange | |
| DIVISIONRANGE | = lt_divisionrange | |
| COMPCODERANGE | = lt_compcoderange | |
| BILLDATERANGE | = lt_billdaterange | |
| INVLISTDATERANGE | = lt_invlistdaterange | |
| BILLTYPERANGE | = lt_billtyperange | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_CUSTOMEREXPINV_RELEASE | ||
ABAP code using 7.40 inline data declarations to call FM ALE_CUSTOMEREXPINV_RELEASE
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 ENQUEUEALL FROM BAPIABCON INTO @DATA(ld_enqueueall). | ||||
| DATA(ld_enqueueall) | = 'X'. | |||
| "SELECT single TESTRUN FROM BAPIACHEAD INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'BUS2144002'. | |||
| "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