SAP CACS_PS_LOSA_INIT_SPLIT Function Module for NOTRANSL: LOS: Partnerschaften, Aufteilungssätze vorbelegen
CACS_PS_LOSA_INIT_SPLIT is a standard cacs ps losa init split 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: LOS: Partnerschaften, Aufteilungssätze vorbelegen 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 ps losa init split FM, simply by entering the name CACS_PS_LOSA_INIT_SPLIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_PS_MD_LOS
Program Name: SAPLCACS_PS_MD_LOS
Main Program: SAPLCACS_PS_MD_LOS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_PS_LOSA_INIT_SPLIT 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_PS_LOSA_INIT_SPLIT'"NOTRANSL: LOS: Partnerschaften, Aufteilungssätze vorbelegen.
EXPORTING
I_BUSI_TIME = "Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
I_TECH_TIME = "Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)
I_CACSAPPL = "Commission Application Identification
I_OBJ_TYPE = "Object Type Class (OTC) for Logical Service
I_OBJ_METHOD = "Assigned Method for Object Type Class for Logical Service
I_OBJ_ID = "Calculating Object Identification
I_SPLIT_TYPE = "Partnerships: Determination Type for Distribution Ratios
IS_PS_HEADLINE = "Partnerships Transfer Structure
IMPORTING
ET_MSG = "Message List for Partnerships
CHANGING
CS_DYNTAB = "Distribution Ratios for Each Split ID for BDT Display
IMPORTING Parameters details for CACS_PS_LOSA_INIT_SPLIT
I_BUSI_TIME - Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
Data type: CACSBUSITIMEOptional: No
Call by Reference: Yes
I_TECH_TIME - Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)
Data type: CACSTECHTIMEOptional: No
Call by Reference: Yes
I_CACSAPPL - Commission Application Identification
Data type: CACSAPPLOptional: No
Call by Reference: Yes
I_OBJ_TYPE - Object Type Class (OTC) for Logical Service
Data type: CACS_LOS_OTCOptional: No
Call by Reference: Yes
I_OBJ_METHOD - Assigned Method for Object Type Class for Logical Service
Data type: CACS_LOS_METHOptional: No
Call by Reference: Yes
I_OBJ_ID - Calculating Object Identification
Data type: CACS_LOS_OBJIDOptional: No
Call by Reference: Yes
I_SPLIT_TYPE - Partnerships: Determination Type for Distribution Ratios
Data type: CACSSRCHTYPEOptional: No
Call by Reference: Yes
IS_PS_HEADLINE - Partnerships Transfer Structure
Data type: CACS_S_PS_HEADLINEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CACS_PS_LOSA_INIT_SPLIT
ET_MSG - Message List for Partnerships
Data type: CACS_TT_PS_MSGOptional: No
Call by Reference: Yes
CHANGING Parameters details for CACS_PS_LOSA_INIT_SPLIT
CS_DYNTAB - Distribution Ratios for Each Split ID for BDT Display
Data type: CACS_S_PS_SP_DOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_PS_LOSA_INIT_SPLIT 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.| DATA: | ||||
| lv_et_msg | TYPE CACS_TT_PS_MSG, " | |||
| lv_cs_dyntab | TYPE CACS_S_PS_SP_D, " | |||
| lv_i_busi_time | TYPE CACSBUSITIME, " | |||
| lv_i_tech_time | TYPE CACSTECHTIME, " | |||
| lv_i_cacsappl | TYPE CACSAPPL, " | |||
| lv_i_obj_type | TYPE CACS_LOS_OTC, " | |||
| lv_i_obj_method | TYPE CACS_LOS_METH, " | |||
| lv_i_obj_id | TYPE CACS_LOS_OBJID, " | |||
| lv_i_split_type | TYPE CACSSRCHTYPE, " | |||
| lv_is_ps_headline | TYPE CACS_S_PS_HEADLINE. " |
|   CALL FUNCTION 'CACS_PS_LOSA_INIT_SPLIT' "NOTRANSL: LOS: Partnerschaften, Aufteilungssätze vorbelegen |
| EXPORTING | ||
| I_BUSI_TIME | = lv_i_busi_time | |
| I_TECH_TIME | = lv_i_tech_time | |
| I_CACSAPPL | = lv_i_cacsappl | |
| I_OBJ_TYPE | = lv_i_obj_type | |
| I_OBJ_METHOD | = lv_i_obj_method | |
| I_OBJ_ID | = lv_i_obj_id | |
| I_SPLIT_TYPE | = lv_i_split_type | |
| IS_PS_HEADLINE | = lv_is_ps_headline | |
| IMPORTING | ||
| ET_MSG | = lv_et_msg | |
| CHANGING | ||
| CS_DYNTAB | = lv_cs_dyntab | |
| . " CACS_PS_LOSA_INIT_SPLIT | ||
ABAP code using 7.40 inline data declarations to call FM CACS_PS_LOSA_INIT_SPLIT
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