SAP ISH_COST_ALLOCATION_PREPARE Function Module for









ISH_COST_ALLOCATION_PREPARE is a standard ish cost allocation prepare SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ish cost allocation prepare FM, simply by entering the name ISH_COST_ALLOCATION_PREPARE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISH_COST_ALLOCATION_PREPARE 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 'ISH_COST_ALLOCATION_PREPARE'"
EXPORTING
I_RNHK1 = "Header information

IMPORTING
BREAK_ALLOCATION = "Switch: Terminate Processing?

TABLES
KONTIERUNGEN = "Generated account asgmt table
T_NLEI = "Table of selected services
.




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_SAPLNHCO_001 IS-H: Function exit for changing an account assignment line

IMPORTING Parameters details for ISH_COST_ALLOCATION_PREPARE

I_RNHK1 - Header information

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

EXPORTING Parameters details for ISH_COST_ALLOCATION_PREPARE

BREAK_ALLOCATION - Switch: Terminate Processing?

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

TABLES Parameters details for ISH_COST_ALLOCATION_PREPARE

KONTIERUNGEN - Generated account asgmt table

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

T_NLEI - Table of selected services

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

Copy and paste ABAP code example for ISH_COST_ALLOCATION_PREPARE 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_i_rnhk1  TYPE RNHK1, "   
lt_kontierungen  TYPE STANDARD TABLE OF RNHC01, "   
lv_break_allocation  TYPE RNHC01, "   
lt_t_nlei  TYPE STANDARD TABLE OF NLEI. "   

  CALL FUNCTION 'ISH_COST_ALLOCATION_PREPARE'  "
    EXPORTING
         I_RNHK1 = lv_i_rnhk1
    IMPORTING
         BREAK_ALLOCATION = lv_break_allocation
    TABLES
         KONTIERUNGEN = lt_kontierungen
         T_NLEI = lt_t_nlei
. " ISH_COST_ALLOCATION_PREPARE




ABAP code using 7.40 inline data declarations to call FM ISH_COST_ALLOCATION_PREPARE

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!