SAP EXIT_SAPLJYNA_010 Function Module for Enhance Communication and Partner Data (Appl.J1)
EXIT_SAPLJYNA_010 is a standard exit sapljyna 010 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Enhance Communication and Partner Data (Appl.J1) 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 sapljyna 010 FM, simply by entering the name EXIT_SAPLJYNA_010 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XJYN
Program Name: SAPLXJYN
Main Program: SAPLXJYN
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLJYNA_010 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_SAPLJYNA_010'"Enhance Communication and Partner Data (Appl.J1).
EXPORTING
COM_JFRK = "
COM_TRTYP = "
COM_SPART = "
CHANGING
COM_KBJ1 = "
TABLES
* COM_PART = "
COM_JFPA = "
COM_JFRP = "
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.COMMUNICATION_AREA_KOMKBJ0
COMMUNICATION_AREA_KOMKBJ1
COMMUNICATION_AREA_KOMKBJ2
COMMUNICATION_AREA_KOMKBJ3
COMMUNICATION_AREA_KOMKBJ4
COMMUNICATION_AREA_KOMKBJ5
COMMUNICATION_AREA_KOMKBJ6
COMMUNICATION_AREA_KOMKBJ7
COMMUNICATION_AREA_KOMKBJ8
COMMUNICATION_AREA_KOMKBJ9
COMMUNICATION_AREA_KOMPBJ0
ISP_MESSAGES_SORT_FIELDS_J0
ISP_MESSAGES_SORT_FIELDS_J1
ISP_MESSAGES_SORT_FIELDS_J2
ISP_MESSAGES_SORT_FIELDS_J3
ISP_MESSAGES_SORT_FIELDS_J4
ISP_MESSAGES_SORT_FIELDS_J5
ISP_MESSAGES_SORT_FIELDS_J6
ISP_MESSAGES_SORT_FIELDS_J7
ISP_MESSAGES_SORT_FIELDS_J8
ISP_MESSAGES_SORT_FIELDS_J9
KOMKBJ0_FILL
KOMKBJ1_FILL
KOMKBJ2_FILL
KOMKBJ3_FILL
KOMKBJ4_FILL
KOMKBJ5_FILL
KOMKBJ6_FILL
KOMKBJ7_FILL
KOMKBJ8_FILL
KOMKBJ9_FILL
KOMPBJ0_FILL
IMPORTING Parameters details for EXIT_SAPLJYNA_010
COM_JFRK -
Data type: JFRKOptional: No
Call by Reference: No ( called with pass by value option)
COM_TRTYP -
Data type: TJ180-TRTYPOptional: No
Call by Reference: No ( called with pass by value option)
COM_SPART -
Data type: JFRK-SPARTOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPLJYNA_010
COM_KBJ1 -
Data type: KOMKBJ1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLJYNA_010
COM_PART -
Data type: MSGPAOptional: Yes
Call by Reference: No ( called with pass by value option)
COM_JFPA -
Data type: JFPAVBOptional: No
Call by Reference: No ( called with pass by value option)
COM_JFRP -
Data type: JFRPVBOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLJYNA_010 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_com_jfrk | TYPE JFRK, " | |||
lv_com_kbj1 | TYPE KOMKBJ1, " | |||
lt_com_part | TYPE STANDARD TABLE OF MSGPA, " | |||
lt_com_jfpa | TYPE STANDARD TABLE OF JFPAVB, " | |||
lv_com_trtyp | TYPE TJ180-TRTYP, " | |||
lt_com_jfrp | TYPE STANDARD TABLE OF JFRPVB, " | |||
lv_com_spart | TYPE JFRK-SPART. " |
  CALL FUNCTION 'EXIT_SAPLJYNA_010' "Enhance Communication and Partner Data (Appl.J1) |
EXPORTING | ||
COM_JFRK | = lv_com_jfrk | |
COM_TRTYP | = lv_com_trtyp | |
COM_SPART | = lv_com_spart | |
CHANGING | ||
COM_KBJ1 | = lv_com_kbj1 | |
TABLES | ||
COM_PART | = lt_com_part | |
COM_JFPA | = lt_com_jfpa | |
COM_JFRP | = lt_com_jfrp | |
. " EXIT_SAPLJYNA_010 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLJYNA_010
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 TRTYP FROM TJ180 INTO @DATA(ld_com_trtyp). | ||||
"SELECT single SPART FROM JFRK INTO @DATA(ld_com_spart). | ||||
Search for further information about these or an SAP related objects