cancel
Showing results for 
Search instead for 
Did you mean: 

Missing key components during redefinition processs

friendlycoder
Participant
0 Kudos

Hi all,
I am trying to redefine the standard Odata service FDP_BD_STANDARD_CH_OP. During the process of redefinition I have noticed that the key fields are missing in the selection screen.

Here is one of the examples:

friendlycoder_0-1708329854639.png

 

friendlycoder_1-1708329854650.png

Why are the key fields not available during the redefinition process?

Best regards

Accepted Solutions (1)

Accepted Solutions (1)

JamesZ
Advisor
Advisor
0 Kudos
Is the second screenshots for key selection? Can we select from there - the second screenshot?
friendlycoder
Participant
0 Kudos

The second screen displays the original fields from default service. As you can see in image, there is a key field named BillingDocument that doesn't appear in the redefinition process.

JamesZ
Advisor
Advisor
0 Kudos
It not be a big issue, can we select key column in segw from the new segw project?

Answers (2)

Answers (2)

ZsoltBalai
Discoverer
0 Kudos

I have the same problem in SEGW, redefinition process missed key fields in Entities.

Service Project FDP_V3_BD_STANDARD_LO_GLO_GEN

Service FDP_V3_BD_STANDARD_LO_GLO_GEN_SRV

Original Entity DownPaymentNode

ZsoltBalai_0-1710496387636.png

Copied Entity DownPaymentNode missing key field BillingDocument

ZsoltBalai_1-1710496421137.png

With other services it worked before, I have problem with this service today 15.3.2014.

You can manually add the key fields (around 2-3 minutes pro field).

It seems a standard fk up (sry for word use, I am a bit upset now), a patch may be coming.

 

ZsoltBalai
Discoverer
0 Kudos
Simplest way to correct manually is to right click on entity and choose import and later mark it as a key field
jeroen_cosijnse
Newcomer
0 Kudos

Hi - have the same problem by redefinition of FDB_V3_BD_STANDARD.

Dd you find a soluion for this .?

 

Regards

Jeroen