Completing Signatures (Mapping)

Use

Mapping is one of the manual tasks you perform when you create API-based service implementations (with service definitions to be stored in ES Repository). The Service Implementation Architect (see Roles within SIW) determines how many manual steps the mapping for a service implementation comprises, whether they are mandatory or optional when he or she creates the configuration (class). The Service Implementation Architect also fixes the number of code slots that you must or can fill with service-specific coding. Depending on the related configuration, mapping can be a large or a small part of the service implementation.

Mapping refers to the following:

Defining a name for each field (simple type)

Enter an ES Repository Field Name for each field in the mapping structure of your project, if it differs from the corresponding field name of the underlying API.
Assigning a global data type (GDT) or a core data type (CDT) for each field (simple type)

Assign a global data type or a core data type to each field in the mapping structure of your project. To find the global data types in the ES Repository, you use the GDT Finder. The presence of a central repository enables reuse of its elements. With the GDT Finder, you can scan ES Repository to see if you can reuse any global data types. For more information, see Finding Global Data Types (GDT Finder).
Defining a name for each field, for each structure, and table (intermediate data types)

Enter an ES Repository Field Name and an IDT Name for each structure and table.

Note

Simple types correspond to data elements in the ABAP Data Dictionary. You need to map every simple type to a global data type or core data type. Intermediate data types correspond to tables or structures in the Data Dictionary. You can change the names that SIW proposes as the configuration default. It is not necessary to explicitly name an intermediate data type (IDT) for the line structure contained in the table. In the ES Repository, a single IDT represents both entities; the system distinguishes a table from a structure just by a different cardinality.

Prerequisites

You have created a project (see Creating Projects (API-based). Before you start the mapping, it is important that you understand the structure of the project tree (see The Project Tree).

Procedure

To map your fields (simple types), structures, and tables (intermediate data types), you have the following options:

Execute the Mapping Check and correct the erroneous entries. For more information, see Executing Mapping Check.

Note

Some warnings resulting from Mapping Check refer to violations of the SAP naming conventions for ES Repository entries. You can correct them, but do not need to do so.
Or, proceed as follows:

Start Service Implementation Workbench (transaction code SIW). Select your project in the project tree and open it (see Opening Projects or Finding Projects). The Mapping subnode is displayed. To expand its entire substructure that is determined by the underlying API, choose the pushbutton.

Note

The system displays elements of the project tree that you need to map in red to emphasize that their mapping is not yet complete. It removes the red color when you have finished the mapping.
Navigate to the first simple type (field name) entry marked in red. To open the related detail screen that includes all mapping properties of the field, double-click on it. The system then selects the ES Repository Category automatically. The category Basic Global Data Type correspond to fields. The category Intermediate Data Type corresponds to tables and structures.

Note

Since the underlying API determines the structure of your enterprise service, you cannot delete or add fields, you can deactivate their use for the service, if the configuration allows this. If this is not allowed, the corresponding checkboxes on the detail-screens are displayed as deactivated and not changeable.
Check whether the Used in Service checkbox in the ES Repository-Related-Properties group box is changeable. If so, decide whether you want to use the specified field for your enterprise service. If necessary, change to edit mode and activate or deactivate the checkbox accordingly. Choose Save. As a result, the system activates or deactivates the field for the service implementation and changes its color in the project tree. The other fields remain activated (black).
Check whether the Optional checkbox in the same group box is changeable. If so, decide whether you want to use the field optionally in the enterprise service. If necessary, change to edit mode and activate or deactivate the checkbox accordingly. Choose Save.
Select the suitable core data type (CDT).
Choose the suitable global data type (GDT). To do so, change to edit mode and enter a GDT Type Name for the field. Choose Save. If you want to search for a global data type, you can also use the Global Data Type (GDT) Finder (see Finding Global Data Types (GDT Finder)). In the edit mode and only for simple types (fields), the system displays the GDT Finder group box at the bottom of the detail screen.

Note

You can also enter an ES Repository Name and an ABAP Field Name in the corresponding fields. The system uses theses names for the proxy generation.
Repeat the described steps for all fields, structures, and tables marked in red. For structures and tables the GDT-Finder is not relevant. You can change the IDT Name, IDT Namespace, Field Name in the ES Repository ( ES Rep. Name), and ABAP Field Name for the proxy.

Result

The system removes the red markup for all mapped elements. When you have finished the mapping, the system automatically checks it and displays a detailed error log. For more information about how to manually start the Mapping Check when you correct the mistakes, see Executing Mapping Check. Thereafter, you can start to generate the service interface and the proxies. For more information about the whole process, see Service Creation and Implementation (API-based with Repository).