Assignment of Dependencies 

Use

You can use APIs to assign object dependencies to the following objects, as in dialog mode:

·         Characteristic

·         Characteristic value

·         BOM item

·         Configuration profile

There are 6 types of dependency:

1	CON	Constraint
2	PRE	Precondition
3	ACT	Activity
4	SEL	Selection condition
5	CNET	Constraint net
6	PROC	Procedure

 

You have the option of entering either the number or the key for the dependency type. The read modules always display the external keys.

There are 2 methods for maintaining and reading dependencies for the following function groups:

·         CSAP

CARD and CAMA

Rules for Modules in Group CSAP

This method is also used to assign dependencies in modules CAMA_CON_PROFILE_MAINTAIN (maintain configuration profile) and CAMA_TABLE_MAINTAIN_ENTRIES (maintain table entries).

There are maintenance modules for the individual objects, containing 5 dependency data tables in the interface. These tables allow you to assign local and global object dependencies to BOM items.

·         A local dependency does not have an internal name until you save it, so you enter an external name when you create a local dependency, and this name is used to refer to the various tables containing data that belongs to the dependency.

·         If you want to assign global dependencies, you enter the name of the dependency in the Internal dependency name field. You use table DEP_ORDER to assign global dependencies.

The tables contain the following data:

·         Table DEP_DATA (object dependencies basic data)

This table is for transferring the basic data of a dependency.

-         Internal dependency name

-         External dependency name

-         Dependency type

-         Status

-         Dependency group

-         Authorization profile

-         Deletion indicator

·         Table DEP_DESCR (object dependencies descriptions)

This table is for transferring the language-dependent descriptions of a dependency.

-         Internal dependency name

-         External dependency name

-         Language

-         Description

-         Deletion indicator

·         Table DEP_ORDER (assigned dependencies)

-         Internal dependency name

-         External dependency name

-         Counter for sort sequence of objects

This table shows the dependencies that are assigned to an object. To delete an assignment, enter a deletion indicator in this table or table DEP_DATA. This deletes the assignment for a global dependency, but deletes a local dependency completely. You can also enter the sort sequence for procedures in this table, in field DEP_LINENO.

·         Table DEP_SOURCE (object dependencies source code)

This table is for transferring the source code of a dependency.

-         Internal dependency name

-         External dependency name

-         Line number

-         Line for source code

·         Table DEP_DOC (object dependencies document)

-         Internal dependency name

-         External dependency name

-         Language

-         Line number

-         Text format

You can enter long texts for dependencies. In field TXT_FOR in table DEP_DOC, you can enter data in SAPscript format, for example:

-         AS Standard paragraph

-         B1 First-level list

-         N1 Numbered list

Rules for Modules in Groups CARD and CAMA

To assign local dependencies, your data must be complete, because a local dependency does not have a name that that application programmer can see, unlike global dependencies.

Each new call creates a new dependency. If you set the deletion indicator, you delete all local dependencies. You can create actions, procedures, selection conditions, and preconditions as local dependencies. You cannot create constraints as local dependencies.

You must enter the following data when you create local dependencies:

·         Language

·         Description

·         Status

·         Dependency type

·         At least one line of source code

A log shows the cause of any errors.

 

To assign a global dependency, you use the name that was assigned when the dependency was created. This name remains during the effectivity period of the dependency and is unique. The dependency is assigned by saving its name in an internal table. You can create or delete individual global dependencies.

When dependencies are read, all local dependencies are provided with all available data (such as description and source code). Each call returns a dependency. Global dependencies appear as a list of assignments in a separate table.

The structure of the tables matches the method for CSAP modules. However, there are no name fields, and the basic data of a dependency is transferred as an individual structure, not as a table.