Page Comparison

If a relationship definition including dependent records is deleted in the "Structure relation control" maintenance, formulas of the dependent records may not be deleted.

This has been corrected.

Starting position:

• A node in the target structure is marked with Stop
• The node is expanded to display existing sub-items
• The node with the stop marker is moved

In this case, a message "Node 000000000:000000000:T has already been registered" or a cancellation with dump may occur.

This has been corrected.

If several relationship definitions are valid for a structure relationship according to the formulas and priority, any one from the list is used.

This has been corrected and in such a case the user must select the definition to be used in the dialogue.

Depending on when the control group for an item is determined, the additional fields in the formulas are not taken into account.

This has been corrected.

In the SMC BAdI method SELECT_REL_DEFINITION, the necessary information on the priority of the definition is missing in the transfer structure.

This has been corrected.

Additional fields with item data can be output in a relationship definition. If, according to the settings, the structures below "Stop" are not read directly, but only when expanding, the additional fields defined for these components are output empty.

This has been corrected.

Affects the "Ignore" option, which is set in a control group used in the reference structure.

In this case, the reference structure is not resolved further at this point, which makes it impossible to compare underlying items that are installed elsewhere in the target. This has been corrected.

This addition has also been removed, as components installed elsewhere in the target would not be recognised in this case either:

Third part of the adjustment to SMC-85:

• In addition, the reference is now no longer resolved independently of the '"Set stop" option' after initial saving if the corresponding assembly in the target has a stop marker.

Elements in the reference are generally always resolved unless a stop option is set, which is also applied to the reference.

In the BAdI method /PCH/IF_SMC_STR_BADI_CMN~FILTER_RELATION_DEFINITIONS the information for the recorded reference and target objects is missing.

This has been corrected and the following parameters have been added to the interface:

• IV_REF_OBJECT_TYPE
• IT_REF_KEY_VALUES
• IV_TAR_OBJECT_TYPE
• IT_TAR_KEY_VALUES

If the reference of one of the fields:

• REL_PROD
• REL_ENGIN
• REL_COST
• REL_SALES
• REL_HLCONF
• REL_PMAINT
• SPARE_PART

is displayed and if the corresponding field for the BOM usage of the target is defined as a required field in the SAP settings, it is marked as set from the reference.

This has been corrected.

If an additional field is used to access the control groups and an incorrect data element or no data element at all is specified in its definition, the process is cancelled with a dump.

This has been corrected.

If a component is marked with Stop in the target and this component is used in another structural relationship as header material, the data of the first level is displayed directly from this structural relationship. However, all components are incorrectly shown as assemblies.

This has been corrected.

If the target structure in a relationship does not yet exist in SAP, no description is output for the material in the header data.

This has been corrected.

Starting position:

• A component in the target has a stop marker
• This component is removed from the target
• This component is also contained in the reference

In this case, the stop marker remains incorrectly displayed in the display of the component in the reference.

This has been corrected.

If a component is removed in the target, it is normally displayed in the worklist and the status in the reference is displayed as "Not used in the target structure".

However, if the "New item ..." setting for the item in the reference is of a type to be ignored, the component should not be displayed in the worklist. However, this is sometimes handled incorrectly and "Not used in target structure" is still displayed.

This has been corrected.

When a target BOM is written or modified, the first time the corresponding structure relationship is read, SMC needs to update some information from the reference. But if no relevant reference data is found, the opening is very slow.

This has been fixed.

When additional fields are displayed, depending on the settings, these fields are displayed in the location details screen even if they are not enabled for the target structure.

This has been corrected.