Functionality

Interface
Object Class Dependency
The interface for the Application Programming Interface (API) functionmodule to read specification data has a flat branched table for eachobject class, see Object Class Dependency.
Deleting Data
The calling program specifies the data records to be deleted using thetables. The API function module does the following:

• Fills the attributes RECN, RECN[MST|Txy], and RECNROOT


• Sets the attribute LINEMOD to the value 'D' for data records to be
deleted. These data records can then be distinguished from data recordsthat are not to be deleted.
The API function module does not delete the data records physically; itsets the delete indicator DELFLG to the value 'X'. When an object isdeleted, all its direct and indirect subobjects are also deletedautomatically.
Note:
For the physical deletion, you use the report program RC1PHDEL.
Scenario Parameters
Using the scenario parameter I_SCENARIO, the caller specifies whichobject class is to be deleted in the same way as in theRead API Function Module.
Note:
The logic only evaluates the cases = 'X' and <> 'X' here. (The values'N' and 'S' are not taken into account because they are only relevantfor the Read API function module.)
Parameters

• Parameters for specifying the time period for which the data is to be
read:
I_ADDINF
I_FLG_KEY_DATE_SWITCH_ONLY
Note:
Instead of specifying an interval (see Read API function module), theparameter I_FLG_INTERVAL_ACCESS is set. If it is set, the API functionmodule works with the time interval from 01/01/0001 to 12/31/9999. Thisensures that logical keys are unique across the whole time axis.

• Other parameters:

I_FLG_CHECK_ONLY (Run delete as test. Data is not written to thebuffer.)
I_FLG_OWNID_SRSID_KEEP (When deleting, the attributes data provider anddata source remain unchanged)
I_FLG_STATUS_CHECK (Status check on)
I_FLG_DATA_PASSED_ON_W_INH_REL (When deleting inheritance relationships,the passed on identifiers and value assignment instances are alsodeleted)

• Parameters for notifying errors and warnings:

E_FLG_INTERNAL_ERROR
E_FLG_ERROR
E_FLG_WARNING
E_ERROR_TAB (of type ESPAP_EXTERROR_TAB_TYPE in type group ESPAP)
If an error occurs in an object, it is not deleted and all its directand indirect subobjects are marked as containing errors and are also notdeleted.

Logic
For the Delete API function module, the same statements apply as for theRead API Function Module, ifrelevant.
The process is as follows:


• First the Read API function module is called and reads, checks, and
locks the specifications for the objects to be deleted. The API functionmodule reads the objects and their direct and indirect parent and childobjects.
If whole specifications are deleted, the API function module determinesthe data across the whole time axis. Otherwise, the API function modulereads the data on the key date because the change states of the datarecords are synchronous among the hierarchy levels below thespecification header level (see Rule forEngineering Change Management in Specification Management).

• The Delete API function module (DELETE subroutine for the specification
header) is called that carries out the actual deletion.
If you are working with change numbers, the API function moduledistributes data record splits to the hierarchy levels (seeRule for Engineering Change Management inSpecification Management). To do this, the API function module marksthe direct parent objects of the deleted objects as to be changed andpasses them to the Modify API function module so that it can create therequired data record splits.

Notes
INCLUDE EHS_FU_PHRASE_AUTH_NOT_CHECK OBJECT DOKU ID TX