SAP IMA_CRT_ACCOUNT_RULE_4 Function Module for

Search SAP Function Modules

IMA_CRT_ACCOUNT_RULE_4 is a standard ima crt account rule 4 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 ima crt account rule 4 FM, simply by entering the name IMA_CRT_ACCOUNT_RULE_4 into the relevant SAP transaction such as SE37 or SE38.

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

Function IMA_CRT_ACCOUNT_RULE_4 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 'IMA_CRT_ACCOUNT_RULE_4'"
  EXPORTING
   I_INSOBJECT =  "Identification for an Insurance Object
   I_PARTNER =  "Business Partner Number
*  I_RCL_INSOBJECT =  "Identification for an Insurance Object
*  I_RCL_PARTNER =  "Business Partner Number
*  I_INSOBJECTTYP =  "Insurance Object Category
*  I_CRTVAR_PARTNER =  "Business Partner Number
*  I_CRTVAR_VKONT =  "Contract Account Number
*  I_VKTYP =  "Contract Account Category

 IMPORTING
   E_X_NEW_ACCOUNT =  "Indicator for Creating a New Contract Account
   E_X_NEW_PARTNER_ACC =  "Indicator for Creating a New Partner Account-Relationship
   E_VKONT =  "Contract Account Number
   E_VKTYP =  "Contract Account Category
   E_MSGV1 =  "Messages, Message Variable

EXCEPTIONS
   SEVERAL_ACCOUNTS = 1    PARTNERACC_NOT_UNIQUE = 2    REF_INSOBJECT_NOT_FOUND = 3    NO_UNIQUE_ACCOUNT_IN_GROUP = 4    REF_PARTNER_NOT_RIGHT = 5    NO_ACCOUNT_FOR_PARTNER = 6    MISSING_PARTNER_OR_ACCOUNT = 7    PARTNERACC_NOT_UNIQUE_IN_ATYP = 8    NO_UNIQUE_ACC_IN_GROUP_IN_ATYP = 9 

.

IMPORTING Parameters details for IMA_CRT_ACCOUNT_RULE_4

I_INSOBJECT - Identification for an Insurance Object

Data type: DIMAIOBPAR-INSOBJECT
Optional: No
Call by Reference: Yes

I_PARTNER - Business Partner Number

Data type: DIMAIOBPAR-PARTNER
Optional: No
Call by Reference: Yes

I_RCL_INSOBJECT - Identification for an Insurance Object

Data type: DIMAIOBPAR-RCL_INSOBJECT
Optional: Yes
Call by Reference: Yes

I_RCL_PARTNER - Business Partner Number

Data type: DIMAIOBPAR-RCL_PARTNER
Optional: Yes
Call by Reference: Yes

I_INSOBJECTTYP - Insurance Object Category

Data type: DIMAIOBPAR-INSOBJECTTYP
Optional: Yes
Call by Reference: Yes

I_CRTVAR_PARTNER - Business Partner Number

Data type: DIMAIOBPAR-PARTNER
Optional: Yes
Call by Reference: Yes

I_CRTVAR_VKONT - Contract Account Number

Data type: DIMAIOBPAR-PARTNERACC
Optional: Yes
Call by Reference: Yes

I_VKTYP - Contract Account Category

Data type: TIMA_CRT_ACC-VKTYP
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for IMA_CRT_ACCOUNT_RULE_4

E_X_NEW_ACCOUNT - Indicator for Creating a New Contract Account

Data type: BOOLE-BOOLE
Optional: No
Call by Reference: Yes

E_X_NEW_PARTNER_ACC - Indicator for Creating a New Partner Account-Relationship

Data type: BOOLE-BOOLE
Optional: No
Call by Reference: Yes

E_VKONT - Contract Account Number

Data type: DIMAIOBPAR-PARTNERACC
Optional: No
Call by Reference: Yes

E_VKTYP - Contract Account Category

Data type: DIMAIOBPAR-PARTNERACCTYP
Optional: No
Call by Reference: Yes

E_MSGV1 - Messages, Message Variable

Data type: SY-MSGV1
Optional: No
Call by Reference: Yes

EXCEPTIONS details

SEVERAL_ACCOUNTS - Partners have several accounts

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

PARTNERACC_NOT_UNIQUE - One Partner has more than one account

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

REF_INSOBJECT_NOT_FOUND - Referenced insurance object-partner relationship not found

Data type:
Optional: No
Call by Reference: Yes

NO_UNIQUE_ACCOUNT_IN_GROUP - Multiple Accounts in Insurance Object Group Type

Data type:
Optional: No
Call by Reference: Yes

REF_PARTNER_NOT_RIGHT - Referenced partner is not the same as partner on claims object

Data type:
Optional: No
Call by Reference: Yes

NO_ACCOUNT_FOR_PARTNER - Partner has no account

Data type:
Optional: No
Call by Reference: Yes

MISSING_PARTNER_OR_ACCOUNT - Partner or account not filled

Data type:
Optional: No
Call by Reference: Yes

PARTNERACC_NOT_UNIQUE_IN_ATYP - One Partner has more than one account with the same account type

Data type:
Optional: No
Call by Reference: Yes

NO_UNIQUE_ACC_IN_GROUP_IN_ATYP - Multiple Accounts with the Same Account Type in Insurance Object Type Group

Data type:
Optional: No
Call by Reference: Yes

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

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