Kontakt

Ansicht
Dokumentation

C1F5_SPECIFICATIONS_MODIFY - EHS: Create or Change Specification Data - New

C1F5_SPECIFICATIONS_MODIFY - EHS: Create or Change Specification Data - New

Vendor Master (General Section)   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

Interface

Object Class Dependency

The interface for the Application Programming Interface (API) function module to read specification data has a flat branched table for each object class, see Object Class Dependency.

Changing and Creating Data Records

Data can be changed and created using the tables. It is also possible to change a header object and also create a new subobject for the same header 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 being specified. (In check only mode, temporary RECN numbers can also be used if the uniqueness of the RECN attribute remains untouched.)

Scenario Parameters

Using the scenario parameter I_SCENARIO, the caller specifies which object class is to be deleted in the same way as in the Read 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 relevant for 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), the parameter I_FLG_INTERVAL_ACCESS is set. With this parameter, it is possible when creating and changing data, to switch the key date and change number without having to save. When the key date or change number is switched, the internal buffer of the Environment, Health and Safety (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 the buffer.)

  • I_FLG_OWNID_SRSID_KEEP (When modifying, the attributes data provider and data 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 and indirect subobjects are also marked as containing errors and are also not modified.

Logic

For the Modify API function module, the same statements apply as for the Read API Function Module, if relevant.

The process is as follows:

  • First the Read API function module is called and determines specifications for the transferred data records that already exist. Here the data is read across the whole time axis to check for duplicates.
  • If you are working without change numbers, the API function module reads only the data records transferred by the caller and the direct and indirect parent records of the data records to be changed or created.

  • If you are working with change numbers, the API function module continues the data record split (see Rule for Engineering Change Management in Specification Management). To do this the API function module reads all necessary parent records and child records of the data records to be edited and marks these as to be 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.

Example

Notes

Further information





Parameters

E_ERROR_TAB
E_FLG_ERROR
E_FLG_INTERNAL_ERROR
E_FLG_WARNING
I_ADDINF
I_FLG_ATWRT_HAS_INT_FORMAT
I_FLG_CHECK_ONLY
I_FLG_CREATE_MODE
I_FLG_DB_SEARCH_AT_BIG_BUFFER
I_FLG_INTERVAL_ACCESS
I_FLG_KEY_DATE_SWITCH_ONLY
I_FLG_OWNID_SRSID_KEEP
I_FLG_PRCSS_INH_DRCT
I_FLG_SHORTLONGTXT_SYNCHRONIZE
I_FLG_SKIP_BRDRCHCK
I_FLG_SKIP_CMPFLTRCHCK
I_FLG_SKIP_STATUS_SAVE_EXIT
I_FLG_STATUS_CHECK
I_FLG_WRNG_AT_REF_OVERWRITE
I_FLG_WRNG_IDNT_ORD_0
I_LSADM
I_SCENARIO
X_ASSESSMENT_TAB
X_CARRIAGE_TAB
X_CHARACT_DATA_TAB
X_COMPOSITION_TAB
X_FURTHER_PARAMS
X_IDENTIFIER_TAB
X_IDENTIFIER_USAGE_TAB
X_IDENT_LONGTEXT_TAB
X_MATERIAL_TAB
X_PACKAGING_TAB
X_PACK_CODE_APPR_TAB
X_REFERENCE_TAB
X_REGULATORY_LIST_TAB
X_RELATION_TAB
X_RESTRICTION_TAB
X_RISK_CLASS_TAB
X_SOURCE_TAB
X_SPEC_HEAD_TAB
X_SPEC_PROV_PACK_TAB
X_STATUS_TAB
X_TRANSPORT_APPR_TAB
X_TRANSPORT_CLASS_TAB
X_USER_DEF_TEXT_TAB
X_USR_DEF_LONGTEXT_TAB
X_VALUATION_HEAD_TAB
X_VALUATION_INST_TAB
X_VALUATION_USAGE_TAB

Exceptions

Function Group

C1F5

General Material Data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 7598 Date: 20240523 Time: 083932     sap01-206 ( 100 ms )