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.
Changing and Creating Data Records
Data can be changed and created using the tables. It is also possible tochange a header object and also create a new subobject for the sameheader object at the same time.
To change the data records, the caller must do the following:

• Specify the key values for the data records to be changed.


• Specify the new contents of their application-related fields.


• Transfer the direct and indirect parent records to all data records.


• Set the attribute LINEMOD to 'U' for the records to be changed. (There
are constants to do this in the Include file CBUI04.)
This distinguishes which records have new content and which do not.
To create data records, the caller must do the following:

• Set the attribute LINEMOD to the value 'I' for the data records to be
created.

• Fill the RECN column with valid numbers for all new data records using
the function module C149_RECN_GET_NEXT.
The caller is responsible for correctly generated RECN numbers beingspecified. (In check only mode, temporary RECN numbers can alsobe used if the uniqueness of the RECN attribute remains untouched.)
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. With this parameter, it ispossible when creating and changing data, to switch the key date andchange number without having to save. When the key date or change numberis switched, the internal buffer of the Environment, Health andSafety (EH&S) component does not abandon its data. You should,however, note the rules under Interval-
Based Reading and Writing of Data Records.

• Parameters for language handling:

I_LSADM

• Other parameters:

I_FLG_CHECK_ONLY (Run modification as test. Data is not written to thebuffer.)
I_FLG_OWNID_SRSID_KEEP (When modifying, the attributes data provider anddata source remain unchanged)
I_FLG_STATUS_CHECK (Status check on)

• 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 modified. All its direct andindirect subobjects are also marked as containing errors and are alsonot modified.

Logic
For the Modify 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 determines
specifications for the transferred data records that already exist. Herethe data is read across the whole time axis to check for duplicates.
If you are working without change numbers, the API function module readsonly the data records transferred by the caller and the direct andindirect parent records of the data records to be changed or created.
If you are working with change numbers, the API function modulecontinues the data record split (see Rulefor Engineering Change Management in Specification Management). To dothis the API function module reads all necessary parent records andchild records of the data records to be edited and marks these as tobe changed, so that a data record split is also created for them.

• The MODIFY subroutine in the specification header for changing and
creating is called and performs the actual tasks.

Notes
INCLUDE EHS_FU_PHRASE_AUTH_NOT_CHECK OBJECT DOKU ID TX