Rap generator for unmanaged scenario

[shavneet1]

Hello andre.fischer ,

I am Generating all the backend artifacts using the updated RAP generator. Source code for the table is at the bottom.

It generates the repository object perfectly. But on moving from list to object page , when i click on Edit button , i get the following error. I am using a unmanaged scenario.

It works perfectly with managed scenario , but my requirement is managed (as i am not able to update standard table on SAVE in managed , because the current table data is required).

Managed Scenario no such error message.

Source Code :

@EndUserText.label : 'RFQ Header'

@AbapCatalog.enhancement.category : #NOT_EXTENSIBLE

@AbapCatalog.tableCategory : #TRANSPARENT

@AbapCatalog.deliveryClass : #A

@AbapCatalog.dataMaintenance : #ALLOWED

define table zscp_ekko_test {

@AbapCatalog.foreignKey.screenCheck : true

key client : mandt not null

with foreign key t000

where mandt = zscp_ekko_test.client;

key ebeln : ebeln not null;

bstyp : ebstyp;

bsart : esart;

loekz : eloek;

statu : estak;

aedat : mmpur_erdat;

ernam : mmpur_ernam;

lifnr : elifn;

zterm : dzterm;

ekorg : ekorg;

ekgrp : bkgrp;

waers : waers;

bedat : ebdat;

bwbdt : bwbdt;

angdt : angab;

bnddt : ebndt;

angnr : angnr;

ihran : ihran;

ihrez : ihrez;

inco1 : inco1;

inco2 : inco2;

submi : submi;

procstat : meprocstate;

revno : revno;

hinweis_besch : zpur_hinw_b;

gegenstand : zpur_gegenstand;

req_deliv_date : zpur_rfq_req_deliv_date;

alt_deliv_per : zpur_rfq_alt_deliv_per;

zzstatus_bew : zpur_status_bew;

zzbewerb_ist : zpur_bewerb_ist;

lastchangedatetime : changedatetime;

}

@EndUserText.label : 'RFQ Items'

@AbapCatalog.enhancement.category : #NOT_EXTENSIBLE

@AbapCatalog.tableCategory : #TRANSPARENT

@AbapCatalog.deliveryClass : #A

@AbapCatalog.dataMaintenance : #ALLOWED

define table zscp_ekpo_test {

@AbapCatalog.foreignKey.screenCheck : true

key client : mandt not null

with foreign key t000

where mandt = zscp_ekpo_test.client;

@AbapCatalog.foreignKey.screenCheck : true

key ebeln : ebeln not null

with foreign key zscp_ekko_test

where client = zscp_ekpo_test.client

and ebeln = zscp_ekpo_test.ebeln;

key ebelp : ebelp not null;

loekz : eloek;

statu : astat;

aedat : paedt;

txz01 : txz01;

matnr : matnr;

ematn : ematnr;

bukrs : bukrs;

werks : ewerk;

matkl : matkl;

@Semantics.quantity.unitOfMeasure : 'zscp_ekpo_test.meins'

ktmng : ktmng;

@Semantics.quantity.unitOfMeasure : 'zscp_ekpo_test.meins'

menge : bstmg;

meins : bstme;

bprme : bbprm;

@Semantics.amount.currencyCode : 'zscp_ekpo_test.waers'

netpr : bprei;

peinh : epein;

waers : waers;

agdat : angab;

elivery_time_we : zpur_delivery_weeks;

bereitst_ort : zpur_bereitst_ort;

manufacturer : zpur_manufacturer;

country_origin : zpur_country_of_origin;

lastchangedatetime : changedatetime;

}

WOuld you please check , why the behavior is different in unmanaged scenario.

Also i would like to know , how do i do unmanaged save or additional save (if i have to use managed scenario)

Because it is giving me following Erros , when i am calling my API's in additional save method.

A BEHAVIOR implementation is active for "ZR_HEADER02TP". While this is the case,
the following ABAP statements are illegal:

- COMMIT
- ROLLBACK
- SUBMIT
- CALL TRANSACTION
- LEAVE
all DYNPRO-related statements, such as MESSAGE, CALL DIALOG, and CALL
SCREEN

The following statement is only allowed in the "Save” phase: - CALL
FUNCTION IN UPDATE TASK - CALL FUNCTION IN BACKGROUND TASK - CALL
FUNCTION IN BACKGROUND UNIT

Thanks and Best Regards ,

Shavneet Singh