Creating & Extending Transactional Apps

When you add a property to an entity type in a redefined SEGW service, you fill in Name, Label, EDM Core Type, Max Length, and the ABAP Field Name binding. If the binding and the EDM type/length disagree, which one governs — and why does that matter?

An extension touches the ABAP back end, the Gateway (ABAP front end), and the UI layer. A teammate opens SEGW to add a DDIC append field. What did they get wrong, and which tool belongs to each layer?

SAP ships the full SAPUI5 project of every transactional app. Does that mean you can insert custom content anywhere in any view — and how do you know where you actually can?

A colleague claims the nine-step Fiori extension flow survives standard-app upgrades 'because everything is in its own transport.' Why is that the wrong reason, and what is the real one?

You deployed a custom app and set up LPD_CUST, the FLP catalog/tile, and a PFCG role — but the tile still 404s. Which easily-skipped step did you likely miss?

Your extended view shows the binding key {i18n>EXT_STATE} literally instead of the word 'State'. Where must the text live, and why not in the app's existing properties file?

You need a new field in an app's data at the Business Suite layer. Why use an append structure on the OData DDIC structure rather than editing that structure directly — and what's the path?

An extension project starts by importing the original app (e.g. sd_myquotes) from the SAPUI5 ABAP Repository. Doesn't that fork the standard app and create a merge burden? Why not?

You want to drop a brand-new field into a standard view at its extension point. Of component.js's four extension configs, which one — and what does picking the wrong one cost you?

When creating a custom transactional app from a template (e.g. SAP Fiori Worklist Application), why must the OData service exist before you run the template wizard — what breaks if it doesn't?

A reviewer flags that a field shows 'State' on screen but its DDIC structure field is named REGION, and wants REGION renamed to match. Why is the rename unnecessary — and risky?

Your redefined service's $metadata shows the new property, but you're not sure data actually flows. In the Gateway Client, what is the order of checks and why isn't $metadata alone enough?

To confirm the OData service's Ship-to State/Region matches the SAP back end for a sales quotation, what is the exact VA23 navigation — and which screen actually holds the partner's region?

Inside a standard XML view, what exactly does an extension-point tag mark — and how is that different from editing an existing control there?

In the six UI-layer extension steps, what must happen between creating the extension project and identifying extension points — and what fails if you skip it?

You deploy a custom app via Web IDE → Deploy to SAPUI5 ABAP Repository. People assume it runs as a standalone app — what does it actually become on the ABAP server, and why does that matter for go-live?

In the SAP Fiori worklist template wizard, the binding is split across two pages. What does each page bind — and what is notable about the whole wizard?

In a redefined service, generation creates base DPC/MPC classes and _EXT extension classes. Which one do you put custom CRUD logic in — and what happens if you code in the wrong one?

After Replace Service swaps the delivered app's OData service for your custom one (e.g. ZLORD_MY_QUOTATION_SRV), what is the one verification you must not skip before moving on?

A required value exists in the Gateway service but doesn't appear in the Fiori app. Which layer do you extend — and what's the rule that decides among all three?

Staffing a Fiori extension that needs a new back-end field surfaced in the UI: which skill set does each layer demand, and why can't one specialist own all three?

Your custom OData service generated successfully in the back end but the client still can't reach it. What's the actual missing step — and why is regenerating the service the wrong fix?