[SVIM] Add new object type SVIM

[shashank-yadav87]

Hi, attaching the ABAP screens from which the attributes and events are derived for this AFF. Example view 'V_T005_BAS' is considered here.

[cla-assistant]

All committers have signed the CLA.

[larshp]

rename the examples folder from "example" to "examples"

[shashank-yadav87]

rename the examples folder from "example" to "examples"

Done

[shashank-yadav87]

FYI: The example for SVIM was created manually by referring to the existing examples.

[GuilhermeSaraiva96]

Thank you for pushing your AFF and for posting the SAP GUI screenshots. I have a couple questions, as I have no idea what this transaction does:

-do overview screen and single screen correspond to object types? I see they are clickable in SAP GUI.
-the Compare Flag Field in SAP GUI, I could not find it in the Aff, is it not relevant or did I miss it?
-The recording routine in SAP is translated into the transport_recording in the AFF?

[GuilhermeSaraiva96]

@shashank-yadav87 mentioning you here for visibility. please check my previous comment

[shashank-yadav87]

Hi @GuilhermeSaraiva96, the screen pertains to the maintenance dialog of a database table or a view. This maintenance dialog is used to maintain customizing data. Refer the following SAP Help link for the details.
BC - Generate Table Maintenance Dialog

-do overview screen and single screen correspond to object types? I see they are clickable in SAP GUI.
Answer: No. These are parameters of the maintenance dialog which define how the screen layout will be. Will it have just one screen(overview) or two screens(overview and detail).
-the Compare Flag Field in SAP GUI, I could not find it in the Aff, is it not relevant or did I miss it?
Answer: Compare flag is not relevant for this object type(SVIM)
-The recording routine in SAP is translated into the transport_recording in the AFF?
Answer: Yes. This specifies whether and how the table/view contents maintained with the dialog are put in a transport.

Refer the following SAP Help link for the details.
Define maintenance dialog

[GuilhermeSaraiva96]

DS_STORE file needs to be removed from the root folder

[Markus1812]

DS_STORE file needs to be removed from the root folder

done

[Markus1812]

Hi, thanks for contributing! In general, the AFF looks good to me. I have one suggestion regarding consistency to other AFFs. Would be nice if you could change that. Otherwise, I don't think we have to do much here.

[Markus1812]

Thanks, the AFF looks good to me. Pinging another reviewer to double-check.

[GuilhermeSaraiva96]

Looks good to me as well

[shashank-yadav87]

Thanks for approving. Would you be proceeding with the merge @Markus1812 ?

[schneidermic0]

LGTM. I've just found a missing default value for the event types. This is not mandatory, but might help in the future to set a default value if new enum values are added.

[shashank-yadav87]

Hi @GuilhermeSaraiva96 @Markus1812 @schneidermic0 , please let me know in case there are any further issues to be addressed. If not, can you please proceed with the approval and merge?

Thanks,
Shashank

[Markus1812]

Thanks for the update. This AFF is only for defining a transport format, no server-driven editor at the moment, right?

[shashank-yadav87]

Thanks for the update. This AFF is only for defining a transport format, no server-driven editor at the moment, right?

Yes. No server driven editor at the moment. Currently, no ABAP File Format (AFF) is defined for SVIM. This has two consequences:

1. gCTS / source-code-based transport: SVIM objects cannot be serialized to a structured JSON representation for version control and transport via gCTS.
2. AI and Knowledge Graph: The ABAP Metadata Extraction Tool exports repository objects (as AFF, EDMX, or CSN) to hydrate the SAP Knowledge Graph. SVIM is not listed in the current export-relevant object types matrix, meaning Joule and agents cannot discover or reason about view maintenance screen metadata. This directly blocks the goal of expanding AI scenario coverage per the All-in on AI — Metadata Acquisition Decision.