Коллеги, добрый день!

Вводим цены на 2014год, сотрудников закупа много,
соответственно, есть большая необходимость работать в MEK1- MEK2 нескольким пользователям.

При попытке зайти "второму" пользователю открывается сообщение "Условия по указанным параметрам выбора блокирует <логин>".

Наверняка, сталкивались с такой проблемой, как решили? Будем рады любому совету- помощи.
Заранее спасибо.

IDOC-и не помогут в этом деле? Чтобы все разом (раз в день) запулить через LSMW хотя бы?

посмотрите ноту 45104

A user changes condition records and at the same time, a different user may have no option to edit condition records for the same condition type.

Other terms

Condition, condition record, locking, enqueue, lock logic, granularity

SM12

Reason and Prerequisites

The problem is caused by the standard maintenance transaction (for example VK12, VK14)

•
When you create:

o If you enter a condition record, a lock entry is created for exactly this condition record.

•
When you change or create with reference:

o The way in which the system locks depends on the selection screen.A generic lock entry is created for the header of the selection screen or the fast entry.As a result, only one user can maintain records with this generic lock entry that is, with these header fields.(The header fields of the selection screen correspond to the required entry fields.)



Solution

Within the standard SAP system, there is no solution concerning locking as far as it affects the standard maintenance transactions for changing and creating with reference (for example, VK12, VK14).

However, you have the option to maintain the header fields of a condition table using Transaction V/04 (or more general VK04) under 'Technical view'. If a key field of the table which was an item field before becomes a header field, the lock argument becomes more specific.

As of Release 4.0B, you also have the option to branch to the single record maintenance of a condition record via a suitable condition list. Then only the one affected record is locked.If you branch from the pricing report to the creation, to be precise, creation with reference, the generic lock applies as specified above.
In addition, you have the option to maintain conditions of pricing via a condition index table.When you change records (or create with reference as of Release 4.0B), only the affected individual records are locked.
As of Release 4.6, you always enter the new maintenance of condition records (Transaction VK32, VK34) via a pricing report and therefore, single record locks are set.
Remark: If single record locks are set, performance problems or an overflow of the lock table may occur during mass maintenance

Коллеги, спасибо за помощь, но нотка для релизов
As of Release 4.0B, As of Release 4.6, не подходит нам- работаем на SAP ECC 6.0 EHP4, базисники не ставят.

Вариант с LSMW не очень удобен.

Нашли ещё темку
viewtopic.php?f=1&t=20651&p=137899&hilit=%D0%B1%D0%BB%D0%BE%D0%BA%D0%B8%D1%80%D0%BE%D0%B2%D0%BA%D0%B0+%D0%B2+mek1#p137899

Решения пока нет...

А страна у вас там только одна?

Да, страна одна.
Проблема так и не решена

согласно ноте 886773 - FAQ: General condition technique

6. Question: When I maintain condition records, the system issues message VK 083: "Conditions for the selection entered are blocked &"How can I avoid this?
Answer:
See Note 45104, which explains the lock logic for condition records.
In particular, this note describes how you can structure the lock argument more accurately (convert line fields into header fields) or use other transactions; for example, by using a condition index table or a pricing report (new condition maintenance VK31, VK32).

попробуйте использовать VK31/VK32

в ноте 45104 вроде пишеться как настройть таблицу условии чтоб не блокировало кажется там можно еще расширить структуру таблицы Z* полем

Within the standard SAP system, there is no solution concerning locking as far as it affects the standard maintenance transactions for changing and creating with reference (for example, VK12, VK14).
However, you have the option to maintain the header fields of a condition table using Transaction V/04 (or more general VK04) under 'Technical view'. If a key field of the table which was an item field before becomes a header field, the lock argument becomes more specific.

Всем Привет!

У вас как нить получилось решить вопрос работы с MEK1 - нескольким пользователям?
У нас сейчас такая же задача.