SAP K_KKB_PARTNER_SPLIT Function Module for

Search SAP Function Modules

K_KKB_PARTNER_SPLIT is a standard k kkb partner split 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 k kkb partner split FM, simply by entering the name K_KKB_PARTNER_SPLIT into the relevant SAP transaction such as SE37 or SE38.

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

Function K_KKB_PARTNER_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 'K_KKB_PARTNER_SPLIT'"
  EXPORTING
   I_WERKS =  "
*  I_DIPA =  "
*  I_PRCTR =  "
*  I_KALNR_BA =  "
*  I_KALNR =  "
*  I_ERZKA = '*' "Cost Estimate Created with Product Costing
   I_MATNR =  "
   I_KLVAR =  "
   I_TVERS =  "
   I_KADKY =  "
*  I_SICHT = '01' "
*  I_LOSGR =  "
   I_KOKRS =  "
*  I_OWAER =  "

 IMPORTING
   E_PRCTR =  "

EXCEPTIONS
   NO_CALCULATION = 1    NO_AUTHORITY = 2    NO_PARTNER_SPLIT = 3 

.

IMPORTING Parameters details for K_KKB_PARTNER_SPLIT

I_WERKS -

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

I_DIPA -

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

I_PRCTR -

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

I_KALNR_BA -

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

I_KALNR -

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

I_ERZKA - Cost Estimate Created with Product Costing

Data type: KEKO-ERZKA
Default: '*'
Optional: Yes
Call by Reference: Yes

I_MATNR -

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

I_KLVAR -

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

I_TVERS -

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

I_KADKY -

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

I_SICHT -

Data type: KKBE-SICHT
Default: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LOSGR -

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

I_KOKRS -

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

I_OWAER -

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

EXPORTING Parameters details for K_KKB_PARTNER_SPLIT

E_PRCTR -

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

EXCEPTIONS details

NO_CALCULATION -

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

NO_AUTHORITY -

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

NO_PARTNER_SPLIT -

Data type:
Optional: No
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM K_KKB_PARTNER_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