SAP ISM_DELIVERABLE_PVA_MERGE Function Module for Merge Delivery Viability Sets (Internal)









ISM_DELIVERABLE_PVA_MERGE is a standard ism deliverable pva merge SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Merge Delivery Viability Sets (Internal) 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 ism deliverable pva merge FM, simply by entering the name ISM_DELIVERABLE_PVA_MERGE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_DELIVERABLE_PVA_MERGE 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 'ISM_DELIVERABLE_PVA_MERGE'"Merge Delivery Viability Sets (Internal)
  EXPORTING
   NODE_MIX_OFFERTAB =  "
   WEEKDAYS =  "IS-M/SD: Field String for Weekdays
*  CONTEXT =  "
*  XLIEFBEZIRK =  "

 IMPORTING
   MERGED_NODETAB =  "

EXCEPTIONS
   ERROR = 1    NO_DELIVERABILITY = 2    OVERLAPPING_DELIVERABILITY = 3    INCONSISTENT_DELIVERABILITY = 4
.




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_SAPLJK00_001 Restriction of Delivery Viability Sets
EXIT_SAPLJK00_002 Determination of Optimum Delivery Viability Set
EXIT_SAPLJK00_003 Delivery Viability Optimization Allowed?
EXIT_SAPLJK00_004 Determine Preferred Delivery Viability Set (from Several on Same Level)

IMPORTING Parameters details for ISM_DELIVERABLE_PVA_MERGE

NODE_MIX_OFFERTAB -

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

WEEKDAYS - IS-M/SD: Field String for Weekdays

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

CONTEXT -

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

XLIEFBEZIRK -

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

EXPORTING Parameters details for ISM_DELIVERABLE_PVA_MERGE

MERGED_NODETAB -

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

EXCEPTIONS details

ERROR -

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

NO_DELIVERABILITY - No data available

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

OVERLAPPING_DELIVERABILITY -

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

INCONSISTENT_DELIVERABILITY -

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

Copy and paste ABAP code example for ISM_DELIVERABLE_PVA_MERGE 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_error  TYPE STRING, "   
lv_merged_nodetab  TYPE JKD_MERGED_NODETAB, "   
lv_node_mix_offertab  TYPE JKD_NODE_MIX_OFFERTAB, "   
lv_weekdays  TYPE RJYWEEKDAYS, "   
lv_no_deliverability  TYPE RJYWEEKDAYS, "   
lv_context  TYPE JKD_CONTEXT, "   
lv_overlapping_deliverability  TYPE JKD_CONTEXT, "   
lv_xliefbezirk  TYPE XFELD, "   
lv_inconsistent_deliverability  TYPE XFELD. "   

  CALL FUNCTION 'ISM_DELIVERABLE_PVA_MERGE'  "Merge Delivery Viability Sets (Internal)
    EXPORTING
         NODE_MIX_OFFERTAB = lv_node_mix_offertab
         WEEKDAYS = lv_weekdays
         CONTEXT = lv_context
         XLIEFBEZIRK = lv_xliefbezirk
    IMPORTING
         MERGED_NODETAB = lv_merged_nodetab
    EXCEPTIONS
        ERROR = 1
        NO_DELIVERABILITY = 2
        OVERLAPPING_DELIVERABILITY = 3
        INCONSISTENT_DELIVERABILITY = 4
. " ISM_DELIVERABLE_PVA_MERGE




ABAP code using 7.40 inline data declarations to call FM ISM_DELIVERABLE_PVA_MERGE

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



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!