Metadata Analysis
The purpose of this step is to define the data access that you require in your external systems - and exposing this information in a business friendly way.
Here is an overview of what needs to be collated:
Background information
The data that you need to expose from SAP is likely stored in the SAP standard tables, and you can use you favourite search tool to get the information you need. SAP themselves provide a great resource which can provide you with the business friendly names that make working with Cruise such a pleasure.
Key resources:
Capturing in Excel
While it is possible to configure objects manually in Cruise, the simplest way to build new objects is by creating am Excel sheet as shown in the diagram above. The following are explanations of the columns you need to populate:
- Cruise Key - The data object name
- CDS View - The name of the view you want to expose
- Viewfield - Business friendly name of field
- Tabname - The SAP table or view which stores this content
- Fieldname - The SAP field name that contains the relevant field information
- Bapistructure - The mapping of the inbound bapi (advanced use)
- Bapifield - The mapping to the inbound bapi field (advanced use)
- Keyflag - Is this a key field
- Sort - Should sorting be allowed
- Editable - Indicates whether the field can be edited in downstream system
- Filter - Can you search the object using this field