(Glue-2305) Changed scenarios of SNP Glue™ objects
SNP Glue™ Transport Management enables you also to change SNP Glue™ objects on the target system.
Supported changes for specific objects
SNP Glue™ Table
SNP Glue™ object | Scenario | Status | Notes | |
---|---|---|---|---|
Table | Append fields to SNP Glue™ table | Columns are appended (added to the end of the table). If applied, SNP Glue™ also adjusts the extractor automatically without any need to transport it. If a field was added only to an external storage table, the source field is empty. If a field was added to the SAP source table, it's mapped to a new field in the SNP Glue™ table. | ||
Recreate a table structure | If you deactivate a table or add fields to the middle of the table structure and then activate and transport it to another system, you will receive an error. This error occurs, as adding fields to the middle of the structure isn't valid ALTER TABLE operation. To recreate a table structure, delete the original table from the target system using a deletion transport and then import the modified table using a standard transport mechanism. | |||
Remove fields | Removing a field from the SNP Glue™ table requires deactivation of the table. This means that you must follow the same procedure as described above. | |||
Modify File storage options | Modification of File storage options is possible except for changing the Container name parameter. To modify it, delete the original table from the target system using a deletion transport and then import the table with the modified container name using a standard transport mechanism. | |||
Change description | Change of table description is allowed. To change the description go to edit mode, change the description to the desired one, and activate the table. |
SNP Glue™ Table created from external table
SNP Glue™ object | Scenario | Status | Notes | |
---|---|---|---|---|
Table | Append fields to SNP Glue™ table | Appending fields to a table created from external is not supported. | ||
Recreate a table structure | Altering a table created from external is not supported. | |||
Remove fields | Removing fields from a table created from external is not supported. | |||
Change description | Changing the table description is not supported. |
Extractor 1.0 objects
SNP Glue™ object | Scenario | Status | Notes | |
---|---|---|---|---|
Extractor | Add routines | |||
Add selection fields | ||||
Add source fields | ||||
Change Skip initial Full load | The value of Skip initial Full load flag will stay unchanged on the target system | |||
Variant | Change package size | |||
Change the select option values |
Extractor 2.0 objects
SNP Glue™ object | Scenario | Status | Notes |
---|---|---|---|
Fetcher | Change selection fields | Selection fields are changed accordingly. | |
RDE flag | Check/uncheck the "Read deleted entries" flag in Fetcher is changed accordingly. | ||
Change source object | Change source object to fetch data from e.g. SAP Table. This change will affect objects using the fetcher. | ||
Change delta type | Delta type is changed. | ||
Change load type | Load type is changed. | ||
Consumer | Change enable merge | Enable merge is checked. | |
Process | Change start/end routine | Start/end routine is changed. | |
Add routines | |||
Queue | Change description | The description is changed. | |
Change structure | The structure is changed. | ||
Change list of subscribers | The list of Active queue subscribers will stay unchanged on the target system. |
Depending on the changes you performed on the source object, you should either use a standard transport or a deletion transport to transport the updated object to the target system.
If you perform changes on the SNP Glue™ object with a green status in the table below, you should use the standard transport for updating the object on the target system.
In this case, proceed as described in the section (Glue-2305) Transport Management.
In this case, you alter the SNP Glue™ object in a way that is marked red in the above section Supported changes and transport it with standard transport, the transport of this SNP Glue™ object will fail.
If you perform changes on the object with a red status in the above section Supported changes, you have two options on how to transport the changed object to another system.
We recommend using the first option, as you may transport changes from a source system to a target system without deleting the SNP Glue™ object on the source system. During this option, delete the SNP Glue™ object on the target system first and then import the changed SNP Glue™ object from the source to the target system.
The first option consists of these steps:
Change the SNP Glue™ object on the source system.
- Create both deletion and standard transport for the changed object (this step will save the user's need to use two separate transports) in both cases use the same Request Number when collecting changed object
- Release this transport through standard SAP procedure
- Import this transport through standard SAP procedure
- Import this transport through SNP Glue™ TMS (/DVD/GLTR)
SNP Glue™ TMS will delete the changed object and create it with made changes with one transport.
The second option consists of these steps:
Delete the SNP Glue™ object on the source system.
Create and import a deletion transport for this object.
Create a newly changed SNP Glue™ object on the source system.
Transport newly changed SNP Glue™ object through a standard transport.