SAP ISPAM_PROTOCOL_INIT_AVMPOS Function Module for IS-M/AM: Create a New Tree Structure for a Log

Search SAP Function Modules

ISPAM_PROTOCOL_INIT_AVMPOS is a standard ispam protocol init avmpos 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 a New Tree Structure for a Log 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 protocol init avmpos FM, simply by entering the name ISPAM_PROTOCOL_INIT_AVMPOS into the relevant SAP transaction such as SE37 or SE38.

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

Function ISPAM_PROTOCOL_INIT_AVMPOS 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_PROTOCOL_INIT_AVMPOS'"IS-M/AM: Create a New Tree Structure for a Log
  EXPORTING
*  AVM_NR =  "
*  POS_NR =  "
*  PV_FLG_POP =  "

.

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_SAPLJHAC_001 IS-M: Modify Outcome of Exclusion Requirements Check
EXIT_SAPLJHAC_002 IS-M: Modify Outcome of Rate Requirements Check
EXIT_SAPLJHAC_003 IS-M/AM: Modify Outcome of Contract Determination
EXIT_SAPLJHAC_004 IS-M: Check Additional Attributes in the Requirement Element
EXIT_SAPLJHAC_005 IS-M/AM: Modify Outcome of Conversion for Contract Update
EXIT_SAPLJHAC_006 IS-M/AM: Fill Contract Interface for Subsequent Contract Determination
EXIT_SAPLJHAC_007 IS-M: Control Exclusivity During Contract Determination
EXIT_SAPLJHAC_008 IS-M: Calculation of Additional Criteria for Conflict Control
EXIT_SAPLJHAC_009 IS-M: Check Partner Roles During Contract Determination
EXIT_SAPLJHAC_010 IS-M: Determine Update Quantity Without Ad Spec Data
EXIT_SAPLJHAC_011 IS-M: Prevent System Contract Creation
EXIT_SAPLJHAC_012 Terminate Contract Determination and Set Incompleteness Characteristic

IMPORTING Parameters details for ISPAM_PROTOCOL_INIT_AVMPOS

AVM_NR -

Data type: JHAP-AVM_NR
Optional: Yes
Call by Reference: Yes

POS_NR -

Data type: JHAP-POS_NR
Optional: Yes
Call by Reference: Yes

PV_FLG_POP -

Data type: JPAM_XFELD_VAR
Optional: Yes
Call by Reference: Yes

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

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