SAP IDOC_OUTPUT_BLAORD Function Module for NOTRANSL: Ausgabe Kontrakte für ALE in Zwischenstruktur ab Release 3.0A









IDOC_OUTPUT_BLAORD is a standard idoc output blaord 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: Ausgabe Kontrakte für ALE in Zwischenstruktur ab Release 3.0A 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 idoc output blaord FM, simply by entering the name IDOC_OUTPUT_BLAORD into the relevant SAP transaction such as SE37 or SE38.

Function Group: EINM
Program Name: SAPLEINM
Main Program: SAPLEINM
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function IDOC_OUTPUT_BLAORD 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 'IDOC_OUTPUT_BLAORD'"NOTRANSL: Ausgabe Kontrakte für ALE in Zwischenstruktur ab Release 3.0A
EXPORTING
OBJECT = "Message Status
CONTROL_RECORD_IN = "Control record (IDoc)

IMPORTING
OBJECT_TYPE = "Workflow: Object type of the link
CONTROL_RECORD_OUT = "Control record (IDoc)

TABLES
INT_EDIDD = "Data record (IDoc)

EXCEPTIONS
ERROR_MESSAGE_RECEIVED = 1 DATA_NOT_RELEVANT_FOR_SENDING = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEINM_001 Customer Enhancements for Control Record: Purchasing Document (Outbound)
EXIT_SAPLEINM_002 Customer Enhancements to Data Segments: Purchasing Document (Outbound)
EXIT_SAPLEINM_003 Customer Enhancements of Data Segment for Release Documentation (Outbound)
EXIT_SAPLEINM_004 Customer Enhancements for Release Documentation (Inbound)
EXIT_SAPLEINM_005 Customer Enhancements for Order Acknowledgment (Inbound)
EXIT_SAPLEINM_006 Customer Enhancements for Shipping Notification (Inbound)
EXIT_SAPLEINM_007 Customer Enhancements for Inbound Order Acknowledgment: Read IDOC Segments
EXIT_SAPLEINM_008 Customer Enhancements for Inbound Order Acknowledgment: Concluding Actions
EXIT_SAPLEINM_009 MM EDI ORDRSP: Custotmer Enhancement: Tolerances (Quantities/Dates/Prices)
EXIT_SAPLEINM_010 Cust. Enhancement for Inbound Shipping Notif.: Adopt Item Data from IDoc
EXIT_SAPLEINM_011 Concluding Customer Enhancement: EDI Outbound Purchase Order
EXIT_SAPLEINM_012 MM EDI ORDERS/ORDCHG: Customer Enhancement Transfer Configuration
EXIT_SAPLEINM_013 MM EDI ORDERS/ORDCHG: Customer Enhancement Configuration Structures
EXIT_SAPLEINM_014 MM EDI ORDRSP: Customer Enhancement: Price Tolerances
EXIT_SAPLEINM_015 MM EDI ORDRSP: Customer Enhancement: Vendor Material Change
EXIT_SAPLEINM_016 ALE Contract Distribution: Outbound: Enhancement of IDoc Segments
EXIT_SAPLEINM_017 Concluding Customer Enhancement for ALE Contract Distribution: Outbound
EXIT_SAPLEINM_018 Inbound Order Acknowledgment: Modify Segment E1EDK01
EXIT_SAPLEINM_019 Final User Exit: FRC
EXIT_SAPLEINM_020 Final User Exit: JIT

IMPORTING Parameters details for IDOC_OUTPUT_BLAORD

OBJECT - Message Status

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

CONTROL_RECORD_IN - Control record (IDoc)

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

EXPORTING Parameters details for IDOC_OUTPUT_BLAORD

OBJECT_TYPE - Workflow: Object type of the link

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

CONTROL_RECORD_OUT - Control record (IDoc)

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

TABLES Parameters details for IDOC_OUTPUT_BLAORD

INT_EDIDD - Data record (IDoc)

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

EXCEPTIONS details

ERROR_MESSAGE_RECEIVED -

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

DATA_NOT_RELEVANT_FOR_SENDING -

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

Copy and paste ABAP code example for IDOC_OUTPUT_BLAORD 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_object  TYPE NAST, "   
lt_int_edidd  TYPE STANDARD TABLE OF EDIDD, "   
lv_object_type  TYPE WFAS1-ASGTP, "   
lv_error_message_received  TYPE WFAS1, "   
lv_control_record_in  TYPE EDIDC, "   
lv_control_record_out  TYPE EDIDC, "   
lv_data_not_relevant_for_sending  TYPE EDIDC. "   

  CALL FUNCTION 'IDOC_OUTPUT_BLAORD'  "NOTRANSL: Ausgabe Kontrakte für ALE in Zwischenstruktur ab Release 3.0A
    EXPORTING
         OBJECT = lv_object
         CONTROL_RECORD_IN = lv_control_record_in
    IMPORTING
         OBJECT_TYPE = lv_object_type
         CONTROL_RECORD_OUT = lv_control_record_out
    TABLES
         INT_EDIDD = lt_int_edidd
    EXCEPTIONS
        ERROR_MESSAGE_RECEIVED = 1
        DATA_NOT_RELEVANT_FOR_SENDING = 2
. " IDOC_OUTPUT_BLAORD




ABAP code using 7.40 inline data declarations to call FM IDOC_OUTPUT_BLAORD

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 ASGTP FROM WFAS1 INTO @DATA(ld_object_type).
 
 
 
 
 


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!