Date Property issue in SEGW

[Pavan_Golesar]

Hi,

Facing issue in handling DATE Property in SEGW.

Below snapshot will clear my doubt:

The property Entry Date is having Technical Type (Packed Decimal) and BAPI returns type Date (Dats).

I am well aware of manually changing the property Technical Type by - > Entity type - > Select Property - > ABAP Editor - > Internal Type - > Type D.

Save & generate.

Clear Cache.

But still it takes it as Packed Decimal as I had checked in zcl****_MPC class.. Structure.. it show

ENTRY_DATE type P length 8 decimals 0,

Wierd..

does anyone have encountered this kind of issue.

Regs,

Pavan G

[Pavan_Golesar · Accepted solution]

It does have this abap type:

Sp levels:

Regs:Pavan G

[AshwinDutt · Accepted solution]

Hello Pavan,

In the ABAP Type Editor once you select the Internal Type and Type as DATE, are you able to change the length ? is it editable ?

In screen shot it looks like it is editable. Try to change it to 8 manually.

Regards,

Ashwin

[Pavan_Golesar · Accepted solution]

Details of Components:

ON Gateway Development:

<Component>      <Release>      <sp level>

GW_CORE             200              0005    -   SAPK-20005INGWCORE SAP GW CORE 200

IW_BEP                 200              0005            -   SAPK-20005INIWBEP Backend Event Provider

IW_FND                 250              0005

SAP_BASIS           731            0000     - SAP Basis Component

SAP_ABA              731            0000     - Cross-Application Component

***********************************************

ON ECC DEV:

<Component>      <Release>          <sp level>

GW_CORE         190                0002 SAPK-19002INGWCORE SAP GW CORE 190

IW_FND              240                0002 SAPK-24002INIWFND SAP IW FND 240

IW_BEP              200                0006 SAPK-20006INIWBEP Backend Event Provider

***********************************************

ON ECC Quality:

<Component>      <Release>          <sp level>

IW_BEP              200               0006 SAPK-20006INIWBEP Backend Event Provider

SAP_BASIS        700               0029 SAPKB70029 SAP Basis Component

SAP_ABA          700               0029  SAPKA70029 Cross-Application Component

... Please suggest do I need to care about components levels?

[JyotiD · Accepted solution]

Hi Pavan,

Did you tried doing explicit assignment in 'ABAP Type Editor'. Maybe this helps you as your BAPI also returns DATS format.

Regards,

Tarun

[Pavan_Golesar · Accepted solution]

OKay, so you suggest to try Data element  - > DATS

Instead of Internal Type - D.

I Tried but as you see it takes 16 instead of 8.

As you see this is creating lot of issue .. My OData service generated successfully but gives error on running due to this runtime issue.

BAPI returns Dats (8)  but service level my property only accepts DATS (16)..

What should I do.?

Below is the error log:

Message was edited by: Pavan Golesar

Message was edited by: Pavan Golesar

[Pavan_Golesar · Accepted solution]

Thanks ashwin but, on Data element it takes 16 (non-editable field) and if we go for category:Internal Type I does not take 8. it takes 16 only by default.. pls guide whats is happening.?

Regards,

Pavan Golesar

[amarnath_prasad · Accepted solution]

Please select mode as explicit Assignment ,Category as Data Element & Associated Type As DATS.

After doing above step,Click on runtime object generation(red coloured button in tcode segw)

Clean Cache At Both Hub(/n/iwfnd/cache_cleanup) & Development System(/n/iwbep/cache_cleanup).

[Pavan_Golesar · Accepted solution]

Thanks for reply but as you see it does take dats but  of length 16 and not 8 as you do.

Can sumone put light on this .. why this issue of date length 16 is hapenning.?

Thanks a lot.

Pavan G

[amarnath_prasad · Accepted solution]

Did you create model using mapping rfc?If yes then check fm data type.

[Pavan_Golesar · Accepted solution]

[Pavan_Golesar · Accepted solution]

Yes, I had created based in RFC FM which has below structure....

[amarnath_prasad · Accepted solution]

Remove 8 then click enter.Now check

[amarnath_prasad · Accepted solution]

Actually  precision 8 is adding in total length that's why taking 16 length.

[AshwinDutt · Accepted solution]

Hello Pavan,

Keep Edm.DateTime but do not maintain any Precision.

Now in the ABAP Type Editor select the Internal Type and Type as DATE.

Generate objects and clear the cache.

Regards,

Ashwin

[Pavan_Golesar · Accepted solution]

No success.... WIth data element as begda. or any other with DATS.

Message was edited by: Pavan Golesar

[Pavan_Golesar · Accepted solution]

AGAIN.. nice 1

Regs,

PavanG

[Pavan_Golesar · Accepted solution]

Thanks amarnath.... It was resolved by setting it as internal and not what we were trying(i.e with data element approach)

[grabz]

If anyone else would face similar issue, then I suggest to proceed with this KBA: 2819936 - Check Project Consistency button in SEGW results in numerous warnings and/or error messages