CO-PA Derivation User Exit: What I_DERIVATION_DATE Contains for Actual and Plan Data

In ECC 6.0 CO-PA characteristic derivation (KEDR), the user exit EXIT_SAPLKEDRCOPA_001 (include ZXKKEU11) receives a parameter called I_DERIVATION_DATE. This post records, with the ABAP debugger, which date arrives in that parameter for actual postings and which date arrives for plan data.

Note: screen names, menu paths and settings can differ by SAP release and system configuration. The screenshots are from a Korean-language GUI.

1. What to check

The line inside the user exit that builds a year+period key (P_YMM) from the derivation date:

CONCATENATE I_DERIVATION_DATE(4) '0' I_DERIVATION_DATE+4(2) INTO P_YMM.
Item Detail
P_YMM format YYYY0MM (for example 2026009). Used as the lookup key against the period range (FJAHRPER to TJAHRPER) of a profit-center mapping table
Question Which date does I_DERIVATION_DATE carry for an actual document, and which for plan data?

2. Actual postings

KEDR → Derivation → Test. Enter a company code and a derivation date, set a breakpoint on the line above, and run.

Derivation date entered I_DERIVATION_DATE P_YMM
2014.02.01 20140201 2014002

For actual postings the posting date is passed as the derivation date.

3. What got in the way on the KEDR test screen

Item Detail
Controlling area There is no input field. When you enter a company code, a standard derivation step fills it
Plan/actual indicator There is no input field. In the test it arrives blank
Cost center The check-table validation (CSKS) runs before the controlling area is derived, so entering a cost center gives a "value does not exist" error. Workaround: set P_COPA_ITEM-AKSTL directly in the debugger

4. Plan data

Item Detail
Line item tables Plan line items are in CE2xxxx, actual line items in CE1xxxx
Upload program Found with RPR_ABAP_SOURCE_SCAN by searching for BAPI_COPAPLANNING_POSTDATA. The source is KP06 cost center planning (COSP)
Test procedure Enter a plan value in KP06 → run the upload program in test mode → the breakpoint on line 41 stops

5. Values at line 41 on the plan path

Variable Value
I_DERIVATION_DATE 20140101 (the plan year was 2019)
P_COPA_ITEM-PLIKZ blank
P_COPA_ITEM-PERDE 000
Debugger variables: I_DERIVATION_DATE 20140101, PLIKZ blank, PERDE 000
Debugger, plan path: I_DERIVATION_DATE = 20140101 while the plan year is 2019. PLIKZ is blank, PERDE is 000.

The plan derivation date has nothing to do with the plan period. At the time the exit runs, PLIKZ is not filled yet.

6. Where the plan derivation date comes from

OKEQ → select the version → Settings for operating concern → operating concern details → Derivation date (characteristic derivation date).

OKEQ version settings: currency type B0, exchange rate type M, derivation date 2014.01.01
OKEQ, version settings for the operating concern: the derivation date was 2014.01.01.

This value was 2014.01.01. After changing it to 2019.01.01 and running the upload again, line 41 shows I_DERIVATION_DATE = 20190101.

7. Summary

Item Detail
Derivation date, actual Posting date
Derivation date, plan The derivation date in the OKEQ version settings for the operating concern. It has to be updated for each business plan year
PLIKZ Blank when the exit runs, so it cannot be used to tell plan from actual inside the exit
Line item tables Plan CE2xxxx, actual CE1xxxx

Korean version of this post: blog.naver.com/jeonnow/224413973882

Comments

Post a Comment

Popular posts from this blog

SAP S/4HANA Table Reference — Tables I Actually Query, by Topic

SAP tables I actually queried while building custom reports and running end-to-end tests on an S/4HANA sandbox, grouped by topic. Updated continuously as development goes on. Each table: Table / Description / Key fields / T-codes / Used in our custom reports. Last updated: 2026-08-13 1. CO — Allocation Cycles (Assessment / Distribution) Table Description Key fields T-codes Used in our reports T811C Allocation cycle header ※ Distribution = ALART 'V', assessment = ALART 'U'. Classic CO-OM uses TAB='CCSS' TAB / CYCLE / SDATE KSU3, KSV3 ZCO0040 (allocation cycle report), ZCO0041 (distribution cycle detail) T811S Cycle segments ※ SRULE (sender rule) / RRULE (receiver rule) / SPERCENT / RCDATA (variable portion type) / NEGTEST (negative tracing factors — stored value differs from the screen code) TAB / CYCLE / SDATE / SEQNR KSU3, KSV3 ZCO0040, ZCO0041 T811K Selection criteria per segment ※ SETKIND: 0=cycle, 1=sender control, 2=sender, 3=rece...
Read more

Production Order Variance Calculation KKS1 — Fixing KV031 and KV011, and What Lands in COSB

In the last post on cost center variance calculation (KSS1) I noted that the similarly-named KKS1 is a different animal. This is that post: production order variance calculation. I hit two errors on the way in, so we start with their causes and fixes, then verify — by comparing the database before and after — exactly what gets stored where. Environment: controlling area JNC2, plant JNC2, period 2026/008, KRW, three production orders. ※ Screens, menus, and settings may differ depending on your SAP release and system configuration. Two errors before it would even run KV031 ("no target cost version") — version 0 itself existed. What was empty was the variance variant for orders (AWVAO) in OKV6: only the cost-center one (AWVAS) was maintained, which is why KSS1 worked fine while KKS1 refused. Same OKV6 screen, different column. KV011 is an order status problem. Order 1004916 got its goods receipt and final delivery on August 2 — run KKS1 for period 007 and, as of that pe...
Read more

Modern ABAP Syntax Notes — Patterns and Pitfalls from Real Development

ABAP syntax actually used while developing our custom Z reports, organized by topic. Examples come from working sources, together with the pitfalls we actually hit. Structure: syntax item → explanation → example code. Last updated: 2026-08-13 1. Data Declarations and Types ▷ Inline declarations DATA(...) / @DATA(...) — Declare and assign in one statement. SELECT result tables land directly in @DATA(lt_...) — the structure is derived from the SELECT list SELECT matnr, maktx FROM makt INTO TABLE @DATA(lt_makt) WHERE spras = @sy-langu. DATA(lv_qty) = ls_stpo-menge * iv_losgr / lv_bmeng. LOOP AT lt_mat INTO DATA(ls_mat). " loop variable inline too ENDLOOP. ▷ FIELD-SYMBOLS / ASSIGNING — Modify internal table rows in place without copying. ASSIGN COMPONENT lets you pick the column name at runtime (used for dynamic logic such as auto-hiding empty columns) LOOP AT gt_list ASSIGNING FIELD-SYMBOL(<ls_list>) WHERE typps = 'M'. <ls_list...
Read more