5de5e2851c
- Static bundle checks (name length, seed type, reserved words, contract test classes, testclasses_file), local abaplint parser check before SAP, max_tokens, robust JSON parse - Runner: G2 for CDS views with parameters, contract_check detail in report - G0020 and G0013 fixed by review and revalidated (oracle 100, null 0) - Pilot results in docs/faz1-tasarim.md 11e; handover notes merged into CLAUDE.md and docs Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
1. Goal
Show all shipments in one list. The shipments come from two tables: road shipments and rail shipments. The list must also show the transport mode as text. A report and an OData service will read the list, so the union must be in the database, in a CDS view.
2. Open questions
None.
3. Context
- Table {{P}}ROAD (road shipments), package $TMP. Key: SHIP_ID (CHAR 10). Fields: CUST (CHAR 10, customer), KG (DEC 15,3, weight), COST (DEC 15,2).
- Table {{P}}RAIL (rail shipments), package $TMP. Key: SHIP_ID (CHAR 10). Fields: CUSTOMER (CHAR 10, customer), WEIGHT (DEC 15,3, weight), FEE (DEC 15,2).
- The two tables use different column names for the same content.
- Both tables have data. A seed class fills them.
4. Contract
- Create the CDS view entity {{P}}I_SHIPMENT in package $TMP.
- The elements have these names: SHIP_ID, CUSTOMER, SHIP_MODE, WEIGHT, COST.
- No authorization check (#NOT_REQUIRED).
5. Business rules
- The view is the union of {{P}}ROAD and {{P}}RAIL. Each row of {{P}}ROAD gives one row of the view, and each row of {{P}}RAIL gives one row of the view.
- SHIP_MODE is the literal 'ROAD' for a row that comes from {{P}}ROAD. SHIP_MODE is the literal 'RAIL' for a row that comes from {{P}}RAIL.
- CUSTOMER is CUST for a road shipment and CUSTOMER for a rail shipment.
- WEIGHT is KG for a road shipment and WEIGHT for a rail shipment.
- COST is COST for a road shipment and FEE for a rail shipment.
- A shipment with a weight that is not positive (0 or less) is not in the view.
6. Constraints
- Release target: 7.58.
- Coding standards: Clean ABAP.
- Out of scope: do not change {{P}}ROAD and {{P}}RAIL.
7. Acceptance
- The view is active and has no syntax error.
- The hidden tests pass.
- Write ABAP Unit tests with CL_CDS_TEST_ENVIRONMENT in a global test class.