SAP CACS_MIGRATION_WAR_JO_INSERT Function Module for NOTRANSL: Prov.: Garantiejournal eintragen

Search SAP Function Modules

CACS_MIGRATION_WAR_JO_INSERT is a standard cacs migration war jo insert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prov.: Garantiejournal eintragen 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 cacs migration war jo insert FM, simply by entering the name CACS_MIGRATION_WAR_JO_INSERT into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS_MIGRATION_WAR_JO_INSERT 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 'CACS_MIGRATION_WAR_JO_INSERT'"NOTRANSL: Prov.: Garantiejournal eintragen
  EXPORTING
   I_APPL =  "Commission Application Identification
*  I_CHECK = 'X' "Generic Type
   I_REMUNERATION =  "Remuneration Type
   I_CTRTBU_ID =  "Commission Contract Number
   I_AGR_TYP =  "Agreement Category
*  I_DATE = SY-DATUM "Date and Time, Current (Application Server) Date
   I_BEGIN =  "Date and Time, Current (Application Server) Date
   I_END =  "Date and Time, Current (Application Server) Date
   I_RULE_ID =  "Commission Contract Number
   I_PERIODRULE =  "Period Rule
   I_PERIODNO =  "Period No.

EXCEPTIONS
   PERIOD_EXIST_IN_JOURNAL = 1    INSERT_ERROR = 2 

.

IMPORTING Parameters details for CACS_MIGRATION_WAR_JO_INSERT

I_APPL - Commission Application Identification

Data type: CACSAPPL
Optional: No
Call by Reference: Yes

I_CHECK - Generic Type

Data type: C
Default: 'X'
Optional: No
Call by Reference: Yes

I_REMUNERATION - Remuneration Type

Data type: CACSREM
Optional: No
Call by Reference: Yes

I_CTRTBU_ID - Commission Contract Number

Data type: CACS_CTRTBU_ID
Optional: No
Call by Reference: Yes

I_AGR_TYP - Agreement Category

Data type: CACS_AGR_TYP
Optional: No
Call by Reference: Yes

I_DATE - Date and Time, Current (Application Server) Date

Data type: SY-DATUM
Default: SY-DATUM
Optional: No
Call by Reference: Yes

I_BEGIN - Date and Time, Current (Application Server) Date

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

I_END - Date and Time, Current (Application Server) Date

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

I_RULE_ID - Commission Contract Number

Data type: CACS_WARRU_ID
Optional: No
Call by Reference: Yes

I_PERIODRULE - Period Rule

Data type: CACSPRDRULE
Optional: No
Call by Reference: Yes

I_PERIODNO - Period No.

Data type: CACSPERIOD
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PERIOD_EXIST_IN_JOURNAL - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INSERT_ERROR - Insert not possible

Data type:
Optional: No
Call by Reference: Yes

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

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