SAP ALE_FMCABILLDOC_REVERSE Function Module for BAPI -> IDoc: ALE_FMCABILLDOC_REVERSE
ALE_FMCABILLDOC_REVERSE is a standard ale fmcabilldoc reverse 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_FMCABILLDOC_REVERSE 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 fmcabilldoc reverse FM, simply by entering the name ALE_FMCABILLDOC_REVERSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCA_BILL_BOR
Program Name: SAPLFMCA_BILL_BOR
Main Program: SAPLFMCA_BILL_BOR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ALE_FMCABILLDOC_REVERSE 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_FMCABILLDOC_REVERSE'"BAPI -> IDoc: ALE_FMCABILLDOC_REVERSE.
EXPORTING
REVERSEDDOC = "
REVERSALDOC = "
* READARCHIVE = "
* TESTRUN = ' ' "Kennzeichen
* OBJ_TYPE = 'PS_BILLDOC' "
* SERIAL_ID = '0' "
TABLES
* EXTENSIONIN = "Bezugsstruktur für BAPI-Parameter ExtensionIn / ExtensionOut
RECEIVERS = "
* COMMUNICATION_DOCUMENTS = "
* APPLICATION_OBJECTS = "
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_FMCABILLDOC_REVERSE
REVERSEDDOC -
Data type: BAPI_FMCA_EXT_REVERSED_DOCOptional: No
Call by Reference: No ( called with pass by value option)
REVERSALDOC -
Data type: BAPI_FMCA_EXT_REVERSAL_DOCOptional: No
Call by Reference: No ( called with pass by value option)
READARCHIVE -
Data type: BAPI_FMCA_READ_ARCHIVEOptional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Kennzeichen
Data type: BAPI_FMCAINV_FIELDS-TESTRUNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE -
Data type: SERIAL-OBJ_TYPEDefault: 'PS_BILLDOC'
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_FMCABILLDOC_REVERSE
EXTENSIONIN - Bezugsstruktur für BAPI-Parameter ExtensionIn / ExtensionOut
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)
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_FMCABILLDOC_REVERSE 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_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_reverseddoc | TYPE BAPI_FMCA_EXT_REVERSED_DOC, " | |||
| lv_error_creating_idocs | TYPE BAPI_FMCA_EXT_REVERSED_DOC, " | |||
| lt_receivers | TYPE STANDARD TABLE OF BDI_LOGSYS, " | |||
| lv_reversaldoc | TYPE BAPI_FMCA_EXT_REVERSAL_DOC, " | |||
| lv_readarchive | TYPE BAPI_FMCA_READ_ARCHIVE, " | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_testrun | TYPE BAPI_FMCAINV_FIELDS-TESTRUN, " SPACE | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'PS_BILLDOC' | |||
| lv_serial_id | TYPE SERIAL-CHNUM. " '0' |
|   CALL FUNCTION 'ALE_FMCABILLDOC_REVERSE' "BAPI -> IDoc: ALE_FMCABILLDOC_REVERSE |
| EXPORTING | ||
| REVERSEDDOC | = lv_reverseddoc | |
| REVERSALDOC | = lv_reversaldoc | |
| READARCHIVE | = lv_readarchive | |
| TESTRUN | = lv_testrun | |
| OBJ_TYPE | = lv_obj_type | |
| SERIAL_ID | = lv_serial_id | |
| TABLES | ||
| EXTENSIONIN | = lt_extensionin | |
| RECEIVERS | = lt_receivers | |
| COMMUNICATION_DOCUMENTS | = lt_communication_documents | |
| APPLICATION_OBJECTS | = lt_application_objects | |
| EXCEPTIONS | ||
| ERROR_CREATING_IDOCS = 1 | ||
| . " ALE_FMCABILLDOC_REVERSE | ||
ABAP code using 7.40 inline data declarations to call FM ALE_FMCABILLDOC_REVERSE
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 TESTRUN FROM BAPI_FMCAINV_FIELDS INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'PS_BILLDOC'. | |||
| "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