- Introduction to SAP Connector
- SAP Input
- Checking the Data in the SAP Connector
- Adding Process Specific Tags to the SAP Connector for AppOne
- Adding Process Specific Due Dates to the SAP Connector for AppOne
- Adding Automation Estimates to the SAP Connector for AppOne
- Adding Attributes to the SAP Connector for AppOne
- Adding Activities to the SAP Connector for AppOne
- Adding Entities to the SAP Connector for AppOne
- Introduction to SQL Connectors
- Setting up a SQL Connector
- CData Sync Extractions
- Running a SQL Connector
- Editing Transformations
- Releasing a SQL Connector
- Scheduling Data Extraction
- Structure of Transformations
- Using SQL Connectors for Released Apps
- Generating a Cache With Scripts
- Setting up a Local Test Environment
- Separate Development and Production Environments
Adding Entities to the SAP Connector for AppOne
The information in this guide applies to the SAP Purchase-to-Pay Connector for AppOne and SAP Order-to-Cash Connector for AppOne.
Be careful with adding entities. Adding an entity needs adaptations throughout the SAP Connector for AppOne. This may impact the structure of the out-of-box SAP Connector or AppOne.
Introduction
If your actual process contains additional entities you can add these entities to the SAP Connector. Below is a global overview of the steps you need to take to add an entity. Depending on the entity you want to add you may need to perform additional steps.
Step 1: Define Input
- Check whether an extra input table is needed or additional data can be extracted from an existing input table.
- If an extra input table is needed, add the table in the appropriate folder in the SAP Connector in the folder 1. Input.
Step 2: Add the New Entity to the 2. Entities
- Define the entity in the SAP Connector in the 2. Entities folder.
- Add the table key of the entity in the
TABKEY entity
expression. -
Optionally, add another table key when events are generated on a different level than the entity. For example, add the header of the entity in the
TABKEY header
expression.See the illustration below for an example.
- Add relevant attributes, such as
Client
and(Reference) document number
andReference document item
to create additional information about this entity that can be used.
Step 3: Add the New Entity to the 3. Event Log Creation - Entity Relations Folder
-
If the entity is part of:
- one of the processes, then add the entity in one of the existing tables in the 3. Event log creation - Entity relations folder;
- a new subprocess, then create a new table and union this table with the applicable
Entity relations
table.
-
Add the new
TABKEY
expression in the corresponding process table in the 3. Event log creation - Entity relations folder to which the entity is added. See the illustration below for an example. -
Add the new
TABKEY
expression to the Table keys of theEntity relations
table. See the illustration below. - Set the availability of the attributes added in Step 2 Add the new entity to the 2. Entities to Hidden on the tables in the folder 3. Event log creation - Entity relations.
Step 4: Add a New Group of Events in Event Log Creation
- Add a
[entity]_create_events
table and, if applicable a[entity]_header_change _events
table and an[entity]_item_change_eventstable
for the new entity in a new subfolder in the 3. Event log creation - Events folder. - Add the mandatory attributes
Activity
andEvent end
in each event table. Optionally, add event attributes in each event table. -
Create the
[entity]_events
table in the subfolder created in step 1. to join all the separate events to create a complete event log. -
Add the complete sub event log created above to the
join
expression of theEvents_preprocessing
table in the folder 5. Preprocessing. See the illustration below.