SAP ISP_AGENT_CONTRACT_ITEM_DELETE Function Module for IS-M/AM: Delete an Element from a Sales Agent Contract

Search SAP Function Modules

ISP_AGENT_CONTRACT_ITEM_DELETE is a standard isp agent contract item delete 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: Delete an Element from a Sales Agent Contract 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 isp agent contract item delete FM, simply by entering the name ISP_AGENT_CONTRACT_ITEM_DELETE into the relevant SAP transaction such as SE37 or SE38.

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

Function ISP_AGENT_CONTRACT_ITEM_DELETE 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 'ISP_AGENT_CONTRACT_ITEM_DELETE'"IS-M/AM: Delete an Element from a Sales Agent Contract
  EXPORTING
*  PV_FLG_ENQUEUE = CON_ANGEKREUZT "
*  PV_AGENTUR =  "
*  PV_GPNR =  "
   PV_VERM_GPNR =  "Media Sales Agent
*  PV_GUELTIGAB =  "
*  PV_GUELTIGBIS =  "
   PV_VKORG =  "
   PV_VTWEG =  "
   PV_SPART =  "
   PV_TRTYP =  "
*  PV_VTNR =  "

EXCEPTIONS
   COND_TYPE_NOT_FOUND = 1    SEVERAL_CONTRACTS_IN_PURCH_ORG = 10    TOO_MANY_INPUT_PARAMS = 11    WRONG_DATE = 12    CONTRACT_LOCK_FAILURE = 2    ITEM_ALREADY_EXISTS = 3    NO_AUTHORITY = 4    NO_COND_FOUND = 5    NO_CONTRACT_IN_PURCH_ORG = 6    NO_GPNR = 7    NO_INPUT_PARAMS = 8    NO_PURCHASING_ORG_FOUND = 9 

.

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_SAPLJJGA_001 IS-M/AM: Sort Contract Requirements (1.Variant)
EXIT_SAPLJJGA_002 IS-M/AM: Sort Contract Requirements (2. Variant)
EXIT_SAPLJJGA_003 IS-M/AM: Sort Contract Elements (1. Variant)
EXIT_SAPLJJGA_004 IS-M/AM: Sort Contract Elements (2. Variant)
EXIT_SAPLJJGA_005 IS-M: Define Default Contract Header when Creating a Sales Agent Contract
EXIT_SAPLJJGA_006 IS-M/AM: Plausibility Check for Sales Agent Contract Header
EXIT_SAPLJJGA_007 IS-M/AM: Plausibility Checks for Sales Agent Contract Requirements
EXIT_SAPLJJGA_008 IS-M/AM: Plausibility Check for Sales Agent Contract/Sales Areas
EXIT_SAPLJJGA_009 IS-M/AM: Plausibility Checks for Sales Agent Contract Requirement Elements
EXIT_SAPLJJGA_010 IS-M/AM: Sales Agent Contract Consistency Check
EXIT_SAPLJJGA_011 IS-M/AM: Customer Potential: Determine Contract-Relevant BP Role
EXIT_SAPLJJGA_012 IS-M: Customer Potential: Identify Free Attributes with Customer Relevance

IMPORTING Parameters details for ISP_AGENT_CONTRACT_ITEM_DELETE

PV_FLG_ENQUEUE -

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

PV_AGENTUR -

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

PV_GPNR -

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

PV_VERM_GPNR - Media Sales Agent

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

PV_GUELTIGAB -

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

PV_GUELTIGBIS -

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

PV_VKORG -

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

PV_VTWEG -

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

PV_SPART -

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

PV_TRTYP -

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

PV_VTNR -

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

EXCEPTIONS details

COND_TYPE_NOT_FOUND -

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

SEVERAL_CONTRACTS_IN_PURCH_ORG -

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

TOO_MANY_INPUT_PARAMS -

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

WRONG_DATE - Start date later than end date

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

CONTRACT_LOCK_FAILURE -

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

ITEM_ALREADY_EXISTS -

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

NO_AUTHORITY - User does not have authorization

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

NO_COND_FOUND -

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

NO_CONTRACT_IN_PURCH_ORG -

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

NO_GPNR -

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

NO_INPUT_PARAMS -

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

NO_PURCHASING_ORG_FOUND -

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

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

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