SAP Note 17293 - KE21/screen SAPLKEA30300

Symptom:

Problems during batch input from trasaction KE21 or KE11 (Create profitability analysis line items or profit planning):
If the batch input session contains screen SAPLKEA30300, then after carrying out the first transaction (KE21) the next transaction has no data in the first screen.

Cause and prerequisites

Transaction KE21 sends screen SAPLKEA30300 depending on whether the parameter ERG (operating concern) is set or not. If the parameter is not present at the start of the session, the pop-up appears in the first KE21 transaction, but not in the second.

Solution
A new transaction KEBI has been implemented which must be executed as the first transaction of a batch input session for KE21 or KE11. The transaction sets the operating concern at the start of the session independent of the user. The new transaction will be delivered as a correction to 2.1J/2.2D/3.0.
In the meantime, you can install transaction KEBI into the system by carrying out the following steps:
- Call transaction SE93, enter transaction code "KEBI",
Choose the function "CREATE", select "Report transaction"
in the pop-up and the function "PROCEED", in the next
pop-up enter the transaction text "Set operating concern
(batch input)" and program "RKEERKRS", (no check object),
then choose the function "SAVE". A corresponding repair
must be created so that this can be saved; 'Confirm' this
after completing the correction so as not to prevent
transports for a later maintenance level.
- Call transaction SE38 and supplement program RKEERKRS as follows:

REPORT RKEERKRS MESSAGE-ID KE.

DATA: ERKRS LIKE TKEB-ERKRS.

CASE SY-TCODE.
WHEN 'KEBC'.
CALL FUNCTION 'RKE_CHANGE_ERKRS'
EXPORTING FCODE = 'AE'
I_ERKRS = ERKRS.
WHEN 'KEBA'.
CALL FUNCTION 'RKE_CHANGE_ERKRS'
EXPORTING FCODE = 'AZ'
I_ERKRS = ERKRS.
WHEN 'KEBI'. "<==== New
CALL FUNCTION 'RKE_CHANGE_ERKRS' "<==== New
EXPORTING FCODE = 'EE' "<==== New
I_ERKRS = ERKRS. "<==== New
ENDCASE.