The following parameters are important regarding system
performance:
Usage Distance Tables in the COM Parameters (tccom5000m000) session
If you do not base delivery dates on distances tables, to
increase performance, in the Usage Distance Tables field select No.
Check Project Code in Item Code in the Item Base Data Parameters (tcibd9199m000) session
An item code in LN can consist of a project segment and an item
segment. If no PCS or TP project is present for an item, which means the item
is neither customized (PCS) nor allocated (TP), the project segment of the item
code is empty. LN then
considers the item code as consisting of nine spaces, followed by the name in
the item segment.
However, external applications usually do not recognize an
item code consisting of a project segment and an item segment, or an item code
preceded by nine spaces. Therefore, the project segment of an item code
transferred from LN to
an external application is not recognized as such by the external application,
and becomes part of the item name.
To avoid defining item codes in LN that are conflicting
in external applications, select the Check Project Code in Item Code check box.
If this check box is selected, and you add a new item
code or project code, LN performs checks:
If you define an item in the Items (tcibd0501m000) details session, the first nine characters of the item
name should not equal an existing project code in LN.
If you define a project code in the General Projects (tcmcs0552m000) details session, the code should not equal the first
characters of an existing item code in LN.
Selecting this check box makes software performance
significantly worse. Instead, you can clear this check box and use the Print Items where a Project Code is part of the Item Code (tcibd0401m100) session to check whether a range of existing item codes or project codes will
produce conflicts for external applications.