Skip to Content

Hi Guys,


Latest notes in preference and risk:

When performing the preference determination (SAPSLL/PRE_CAL_401) the processing terminates with a dump DBSQL_DUPLICATE_KEY_ERROR, CX_SY_OPEN_SQL_DB in /SAPSLL/SAPLPRFPMRR_DB_UPDATE. This is due to incorrect customizing settings in GTS. Table /SAPSLL/PRETFCNO or /SAPSLL/PSVTFCNO contain entries with an identical preference standard rule and alternative rule. Please see KBA 2220956 for steps to resolve this dump.


The change stamp is always updated even if no change was made during the determination of low level codes in BOMs. This issue is fixed with note 2243379.

Requesting vendor-based long-term vendor declarations (V-LTVDs) with the indicator ‘Request Initial LTVD’ leads to short dump ‘SAPSQL_ARRAY_INSERT_DUPREC’ if aggregation-relevant long-term vendor declarations (LTVDs) exist that have been requested but not maintained. This issue is fixed with note 2162389.


Note 2238004 fixes message /SAPSLL/CORE_PRODUCT 000: ‘Relation indicator incorrect’ for an item transferred to GTS with a deletion indicator set in a purchase order.

Performance/TIME_OUT:

Note 2235170 tunes the performance of transaction /SAPSLL/SPL_MD03 to avoid TIME_OUT errors.


Regards
GTS Support

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply