SAP ISPAM_INV_NAST_OBJKY_BUILD Function Module for IS-M/AM: Create Object Key for Messages Using Message Control for Bill.Doc

Search SAP Function Modules

ISPAM_INV_NAST_OBJKY_BUILD is a standard ispam inv nast objky build 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/AM: Create Object Key for Messages Using Message Control for Bill.Doc 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 ispam inv nast objky build FM, simply by entering the name ISPAM_INV_NAST_OBJKY_BUILD into the relevant SAP transaction such as SE37 or SE38.

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

Function ISPAM_INV_NAST_OBJKY_BUILD 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 'ISPAM_INV_NAST_OBJKY_BUILD'"IS-M/AM: Create Object Key for Messages Using Message Control for Bill.Doc
  EXPORTING
   IN_JHTFK =  "
   IN_BELEG =  "

 IMPORTING
   OUT_OBJKY =  "

.

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_SAPLJHF1_001 IS-M/AM: Sort Billing Interfaces -Itab XKOMFKGN - Order-Related
EXIT_SAPLJHF1_003 IS-M/AM: Pricing for Billing: Header Price Fields. Fill Debit-Side & RevD
EXIT_SAPLJHF1_004 IS-M/AM: Pricing for Billing: Item Price Fields. Fill Debit-Side & RevD
EXIT_SAPLJHF1_005 IS-M/AM: Number Assignment for Billing
EXIT_SAPLJHF1_006 IS-M: Account Determination for Billing: Fill Header Communication Struct.
EXIT_SAPLJHF1_007 IS-M/AM: IS-M: Account Determination for Billing: Fill Item Comm.Struct.
EXIT_SAPLJHF1_008 IS-M/AM: Billing Split Using Billing Header Field ZUKRI
EXIT_SAPLJHF1_010 IS-M/AM: Generate Billing Document: Check and Enhance Header and Item
EXIT_SAPLJHF1_011 IS-M/AM: Billing: Prior to Update
EXIT_SAPLJHF1_012 IS-M/AM: Billing: Prior to Accessing Pricing
EXIT_SAPLJHF1_013 IS-M/AM: Change Billing Document - Fill Dynamic Section of XJHTFP
EXIT_SAPLJHF1_014 IS-M/AM: Generate Billing Document: Enhance Header /Item After Pricing
EXIT_SAPLJHF1_015 IS-M: CO-PA Object Determination, Fill Communication Structure
EXIT_SAPLJHF1_016 IS-M/AM: Billing Document with Revenue Object Data Prior to Update
EXIT_SAPLJHF1_101 IS-M/AM: Fill Billing Interface - Sales Agent Payment
EXIT_SAPLJHF1_102 IS-M/AM: Sort Billing Interface Itab XKOMFKGN - Sales Agent Settlement
EXIT_SAPLJHF1_103 IS-M/AM: Pricing in Billing: Fill Header Price Fields - Credit-Side
EXIT_SAPLJHF1_104 IS-M/AM: Pricing in Billing: Fill Item Price Fields - Credit-Side
EXIT_SAPLJHF1_105 IS-M/AM: Fill Billing Interface - Sales Agent Payment Deduction
EXIT_SAPLJHF1_201 IS-M/AM: Enhance Revenue Distribution Interface for Billing Documents
EXIT_SAPLJHF1_202 IS-M/AM: Revenue Objects for a Billing Dataset

IMPORTING Parameters details for ISPAM_INV_NAST_OBJKY_BUILD

IN_JHTFK -

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

IN_BELEG -

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

EXPORTING Parameters details for ISPAM_INV_NAST_OBJKY_BUILD

OUT_OBJKY -

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

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

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