SAP ALE_RCVPRODCF_REQUEST_CONF Function Module for NOTRANSL: BAPI -> IDoc: ALE_RCVPRODCF_REQUEST_CONF
ALE_RCVPRODCF_REQUEST_CONF is a standard ale rcvprodcf request conf 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_RCVPRODCF_REQUEST_CONF 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 rcvprodcf request conf FM, simply by entering the name ALE_RCVPRODCF_REQUEST_CONF into the relevant SAP transaction such as SE37 or SE38.
Function Group: IFCIBD02
Program Name: SAPLIFCIBD02
Main Program: SAPLIFCIBD02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ALE_RCVPRODCF_REQUEST_CONF 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_RCVPRODCF_REQUEST_CONF'"NOTRANSL: BAPI -> IDoc: ALE_RCVPRODCF_REQUEST_CONF.
EXPORTING
* REQTIMETICKET = ' ' "Request Confirmation Time Ticket
* REQTIMEEVENT = ' ' "Indicator: request time events
* LOGICALSYSTEM = "Logical system
* OBJ_TYPE = 'RCVPRORDCF' "Object Type
* SERIAL_ID = '0' "ALE channel number
TABLES
RECEIVERS = "Transfer structure for logical systems
* COMMUNICATION_DOCUMENTS = "Structure for Object ID
* APPLICATION_OBJECTS = "Structure for Object ID
EXCEPTIONS
ERROR_CREATING_IDOCS = 1
IMPORTING Parameters details for ALE_RCVPRODCF_REQUEST_CONF
REQTIMETICKET - Request Confirmation Time Ticket
Data type: BAPI_PP_PDC_PARAM-REQTTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
REQTIMEEVENT - Indicator: request time events
Data type: BAPI_PP_PDC_PARAM-REQTEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LOGICALSYSTEM - Logical system
Data type: BAPI_PP_PDC_PARAM-SOURCE_SYSOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJ_TYPE - Object Type
Data type: SERIAL-OBJ_TYPEDefault: 'RCVPRORDCF'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SERIAL_ID - ALE channel number
Data type: SERIAL-CHNUMDefault: '0'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ALE_RCVPRODCF_REQUEST_CONF
RECEIVERS - Transfer structure for logical systems
Data type: BDI_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
COMMUNICATION_DOCUMENTS - Structure for Object ID
Data type: SWOTOBJIDOptional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION_OBJECTS - Structure for Object ID
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_RCVPRODCF_REQUEST_CONF 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_reqtimeticket | TYPE BAPI_PP_PDC_PARAM-REQTT, " SPACE | |||
| lv_error_creating_idocs | TYPE BAPI_PP_PDC_PARAM, " | |||
| lv_reqtimeevent | TYPE BAPI_PP_PDC_PARAM-REQTE, " SPACE | |||
| lt_communication_documents | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_logicalsystem | TYPE BAPI_PP_PDC_PARAM-SOURCE_SYS, " | |||
| lt_application_objects | TYPE STANDARD TABLE OF SWOTOBJID, " | |||
| lv_obj_type | TYPE SERIAL-OBJ_TYPE, " 'RCVPRORDCF' | |||
| lv_serial_id | TYPE SERIAL-CHNUM. " '0' |
| CALL FUNCTION 'ALE_RCVPRODCF_REQUEST_CONF' "NOTRANSL: BAPI -> IDoc: ALE_RCVPRODCF_REQUEST_CONF |
| EXPORTING | ||
| REQTIMETICKET | = lv_reqtimeticket | |
| REQTIMEEVENT | = lv_reqtimeevent | |
| LOGICALSYSTEM | = lv_logicalsystem | |
| 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_RCVPRODCF_REQUEST_CONF | ||
ABAP code using 7.40 inline data declarations to call FM ALE_RCVPRODCF_REQUEST_CONF
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 REQTT FROM BAPI_PP_PDC_PARAM INTO @DATA(ld_reqtimeticket). | ||||
| DATA(ld_reqtimeticket) | = ' '. | |||
| "SELECT single REQTE FROM BAPI_PP_PDC_PARAM INTO @DATA(ld_reqtimeevent). | ||||
| DATA(ld_reqtimeevent) | = ' '. | |||
| "SELECT single SOURCE_SYS FROM BAPI_PP_PDC_PARAM INTO @DATA(ld_logicalsystem). | ||||
| "SELECT single OBJ_TYPE FROM SERIAL INTO @DATA(ld_obj_type). | ||||
| DATA(ld_obj_type) | = 'RCVPRORDCF'. | |||
| "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