SAP EXIT_SAPMJ45A_006 Function Module for IS-M/SD: Influence Desired Transmission Date for Output

Search SAP Function Modules

EXIT_SAPMJ45A_006 is a standard exit sapmj45a 006 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Influence Desired Transmission Date for Output 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 exit sapmj45a 006 FM, simply by entering the name EXIT_SAPMJ45A_006 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XJK1
Program Name: SAPLXJK1
Main Program: SAPLXJK1
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPMJ45A_006 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 'EXIT_SAPMJ45A_006'"IS-M/SD: Influence Desired Transmission Date for Output
  EXPORTING
   INAST =  "Message Interface
   IRJKWE =  "Ship-To Party Data
   IRJKVM =  "Sales Agent Data
   IJKAK =  "Order Header
   IJKAP =  "Order Item
   IJKKD =  "Business Data on Order Item
   IJKPROM =  "Promotion Data
   IJKKUEND =  "Termination Data
   IJKEP =  "Schedule Line Data
   IRJKRG =  "Payer Data
   IRJKRE =  "Bill-To Party Data

CHANGING
   VERSANDDATUM =  "Desired Date of Output Transmission
   VERSANDZEIT_AB =  "
   VERSANDZEIT_BIS =  "

.

IMPORTING Parameters details for EXIT_SAPMJ45A_006

INAST - Message Interface

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

IRJKWE - Ship-To Party Data

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

IRJKVM - Sales Agent Data

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

IJKAK - Order Header

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

IJKAP - Order Item

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

IJKKD - Business Data on Order Item

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

IJKPROM - Promotion Data

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

IJKKUEND - Termination Data

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

IJKEP - Schedule Line Data

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

IRJKRG - Payer Data

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

IRJKRE - Bill-To Party Data

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

CHANGING Parameters details for EXIT_SAPMJ45A_006

VERSANDDATUM - Desired Date of Output Transmission

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

VERSANDZEIT_AB -

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

VERSANDZEIT_BIS -

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

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

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