SAP MASTERIDOC_CREATE_COND_A Function Module for NOTRANSL: ALE-Konditionsübernahme Ausgangsverarbeitung

Search SAP Function Modules

MASTERIDOC_CREATE_COND_A is a standard masteridoc create cond a 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: ALE-Konditionsübernahme Ausgangsverarbeitung 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 masteridoc create cond a FM, simply by entering the name MASTERIDOC_CREATE_COND_A into the relevant SAP transaction such as SE37 or SE38.

Function Group: VKOE
Program Name: SAPLVKOE
Main Program: SAPLVKOE
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MASTERIDOC_CREATE_COND_A 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 'MASTERIDOC_CREATE_COND_A'"NOTRANSL: ALE-Konditionsübernahme Ausgangsverarbeitung
  EXPORTING
   PI_MESTYP =  "
*  PI_LOGSYS = ' ' "
*  PI_DIREKT = ' ' "
*  PI_KONH_COMPLETE = ' ' "
*  PI_PROTOCOLL = 'X' "
*  WITHOUT_CUTOFF = ' ' "Checkbox

 IMPORTING
   CREATED_COMM_IDOCS =  "Internal Tables, Current Row Index

TABLES
   PIT_CONDITIONS =  "
*  TE_IDOC_CONTROL =  "Control Record (IDoc)

EXCEPTIONS
   IDOC_COULD_NOT_BE_CREATED = 1 

.

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_SAPLVKOE_001 Condition Transmission: Derivation of Filter Object E1KOMG
EXIT_SAPLVKOE_002 Condition Transmission: Derivation of a Customer Segment to E1KOMG

IMPORTING Parameters details for MASTERIDOC_CREATE_COND_A

PI_MESTYP -

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

PI_LOGSYS -

Data type: TBDLS-LOGSYS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_DIREKT -

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

PI_KONH_COMPLETE -

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

PI_PROTOCOLL -

Data type:
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

WITHOUT_CUTOFF - Checkbox

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for MASTERIDOC_CREATE_COND_A

CREATED_COMM_IDOCS - Internal Tables, Current Row Index

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

TABLES Parameters details for MASTERIDOC_CREATE_COND_A

PIT_CONDITIONS -

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

TE_IDOC_CONTROL - Control Record (IDoc)

Data type: EDIDC
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

IDOC_COULD_NOT_BE_CREATED -

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

Copy and paste ABAP code example for MASTERIDOC_CREATE_COND_A 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.

ABAP code using 7.40 inline data declarations to call FM MASTERIDOC_CREATE_COND_A

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.

Search for further information about these or an SAP related objects