Kontakt

Ansicht
Dokumentation

CFG_API_GET_CONFLICTING_FACTS - Returns the conflicts including typed facts

CFG_API_GET_CONFLICTING_FACTS - Returns the conflicts including typed facts

ABAP Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

*"----------------------------------------------------------------------

*"*"Local Interface:

*"  IMPORTING

*"     VALUE(CONFIG_ID) TYPE  COMT_CFGM_CONFIG_ID

*"     VALUE(INST_ID) TYPE  COMT_CFGD_INSTID OPTIONAL

*"     VALUE(CONFLICT_TYPE) TYPE  COMT_CFGM_CONFLICT_TYPE OPTIONAL

*"  EXPORTING

*"     VALUE(CONFLICTS) TYPE  COMT_CFGM_TYPED_CONFLICT_I

*"----------------------------------------------------------------------

The configuration is identified with the config ID.

The conflicts occur most times within an instance; in this case the instance ID can be used as filter.

Additionally you can filter using the conflict type. If the calling application offers conflict resolution for value conflicts only, then this filter can be applied.

Possible CONFLICT_TYPE values are:

  • -1: direct conflict inferred by constraint
  • 1: a conflict between two characteristic values assigned to the same characteristic
  • 2: conflict between value assignment and static domain of the characteristic
  • 3: a conflict between the domain restriction and the value assignment
  • 4: conflict between the nil-facet and a value assignment
  • 5: conflict, because the characteristic is marked as being nil and required
  • 9: conflict between an excluded value and a value assignment

The returned conflicts have the following structure:

  • CONFLICT_ID the id of an conflict
  • CONFLICT_TYPE the type as explained above
  • INST_ID the involved instance
  • EXPLANATIONS direct explanations derived from dependencies
  • FACTS
  • Facts are structured as:
  • FACT_ID all facts that are returned in conflicts get a temporary ID. The ID is only valid until the next configuration change
  • INST_ID instance ID
  • OBSERVABLE_TYPE as one of
  • 1: characteristic observable

  • 2: decomposition observable,

  • 3: type observable

  • OBSERVABLE
  • For characteristic this will denote the characteristic name

  • For decomposition this will grant the position number and the object name

  • For types the constant $TYPE is returned

  • FACET with the following supported facets for characteristic observable
  • 0: value facet

  • 1: domain facet

  • 4: required facet

  • 5: invisible facet

  • 6: nil facet

  • 10: noinput facet

  • 11: excluded value facet

  • 12: allowed value facet

  • SIMPLE_BINDING most times a simple binding can be used, only for the domain facet the domain binding is used
  • DOMAIN_BINDING
  • AUTHOR the author of the fact as
  • S for System inferred

  • D for Default and

  • U for User set value

  • EXPLANATIONS An explanation can be maintained for constraints. As multiple constraints can be involved in a conflict, multiple explanations can occur here. They are distinguished by the constraint name.

Notes

Further information





Parameters

CONFIG_ID
CONFLICTS
CONFLICT_TYPE
INST_ID

Exceptions

COMMAND_EXCEPTION
EXCEPTION_CONFIG_NULL
PARAMETER_EXCEPTION

Function Group

COM_CFG_API_UI_COMMAND

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5707 Date: 20240523 Time: 104114     sap01-206 ( 42 ms )