İçereği Atla
Odoo Menü
  • Portal
  • Ücretsiz deneyin
  • Uygulamalar
    Finans
    • Muhasebe
    • Faturalama
    • Masraf Yönetimi
    • Elektronik Çizelge (BI)
    • Belgeler
    • İmza
    Satış
    • Müşteri İlişkileri Yönetimi (CRM)
    • Satış
    • Satış Noktası Mağaza
    • Satış Noktası Restoran
    • Abonelikler
    • Kiralama
    Web Sitesi
    • Web Sitesi Oluşturucu
    • eTicaret
    • Blog
    • Forum
    • Canlı Sohbet
    • eÖğrenme
    Tedarik Zinciri
    • Envanter
    • Üretim
    • Ürün Yaşam Döngüsü Yönetimi
    • Satın Alma
    • Bakım
    • Kalite
    İnsan Kaynakları
    • Çalışanlar
    • İşe Alım
    • İzin
    • Değerlendirme
    • Referans
    • Filo Yönetimi
    Pazarlama
    • Sosyal Medyada Pazarlama
    • E-posta ile Pazarlama
    • SMS ile Pazarlama
    • Etkinlikler
    • Pazarlama Otomasyonu
    • Anket
    Hizmetler
    • Proje Yönetimi
    • Çalışma Çizelgeleri
    • Saha Hizmeti
    • Yardım Masası
    • Planlama
    • Randevular
    Verimlilik
    • Sohbet
    • Onay
    • Nesnelerin İnterneti
    • VoIP
    • Bilgi Bankası
    • WhatsApp
    Üçüncü taraf uygulamalar Odoo Stüdyo Odoo Bulut Platformu
  • Sektörler
    Perakende satış
    • Kitapçı
    • Giyim Mağazası
    • Mobilya Mağazası
    • Gıda Marketi
    • Hırdavat Dükkanı
    • Oyuncak Dükkanı
    Gıda ve Konaklama
    • Bar ve Pub
    • Restoran
    • Fast Food Restoranı
    • Konuk Evi
    • İçecek Distribütörü
    • Otel
    Gayrimenkul
    • Emlak Acentesi
    • Mimarlık Firması
    • İnşaat
    • Emlak Yönetimi
    • Bahçe Tasarımı
    • Mülk Sahipleri Derneği
    Uzmanlık
    • Muhasebe Firması
    • Odoo Partner
    • Pazarlama Ajansı
    • Hukuk Firması
    • Yetenek Kazanımı
    • Denetim ve Belgelendirme
    Üretim
    • Tekstil
    • Metal
    • Mobilyalar
    • Gıda
    • Bira fabrikası
    • Kurumsal Hediye
    Sağlık ve Spor
    • Spor Kulübü
    • Optik Mağazası
    • Fitness Merkezi
    • Sağlıklı Yaşam Merkezi
    • Eczane
    • Kuaför Salonu
    Ticaret
    • Tamirci
    • BT Donanım & Destek
    • Güneş Enerjisi Sistemleri
    • Ayakkabı İmalatçısı
    • Temizlik Hizmetleri
    • HVAC Hizmetleri
    Diğerleri
    • Kar Amacı Gütmeyen Kuruluş
    • Çevre Ajansı
    • Reklam Panosu Kiralama
    • Fotoğrafçılık
    • Bisiklet Kiralama
    • Yazılım Bayisi
    Tüm Sektörlere Göz Atın
  • Topluluk
    Öğrenim
    • Eğitim Araçları
    • Dokümantasyon
    • Sertifikasyonlar
    • Eğitim Etkinlikleri
    • Blog
    • Podcast
    Eğitim ve Gelişim
    • Eğitim Programı
    • Scale Up! İşletme Oyunu
    • Odoo'yu Ziyaret Edin
    Yazılım
    • İndirin
    • Sürümleri Kıyaslayın
    • Sürümler
    İş Birliği
    • Github
    • Forum
    • Etkinlikler
    • Çeviriler
    • Partner Olun
    • Partnerler için Hizmetler
    • Muhasebe Firmanızı Kaydettirin
    Hizmetler
    • Partner Bulun
    • Muhasebeci Bulun
    • Bir danışmanla görüşün
    • Kurulum Hizmetleri
    • Müşteri Referansları
    • Destek
    • Sürüm Yükseltme
    Github Youtube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    Demo randevusu alın
  • Fiyatlandırma
  • Yardım

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

  • Müşteri İlişkileri Yönetimi
  • e-Commerce
  • Muhasebe
  • Envanter
  • PoS
  • Proje Yönetimi
  • MRP
All apps
You need to be registered to interact with the community.
All Posts People Badges
Etiketler (View all)
odoo accounting v14 pos v15
About this forum
You need to be registered to interact with the community.
All Posts People Badges
Etiketler (View all)
odoo accounting v14 pos v15
About this forum
Yardım

I do not understand why every time stock picking documents ..

Abone Ol

Get notified when there's activity on this post

Bu soru işaretlendi
warehousesmovepicking
4 Cevaplar
4919 Görünümler
Avatar
Jason Wu

Dears:


Under the guidance of this question of how someone can deal with it?

Why when I update or add a stock picking documents, the database will be updated at the same time all the stock move and work flow? When there are 400,000 strokes stock move, we had to wait for finished updating the data stored will be successful. This is not a very inefficient something?


DB log:

2016-07-04 00:18:55,791 805 DEBUG PROD openerp.sql_db: query: SELECT "stock_move"."picking_type_id","stock_move"."id" FROM "stock_move"

WHERE "stock_move".id IN (187910, 187912, 187914, 187918, 187920, 192088, 187922, 187924, 187926, 187928, 187930, 187932, 187934, 187936, 187938, 187940, 187942, 187944, 187946, 187948, 187950, 187952, 187954, 187960, 187962, 187964, 187966, 187968, 187970, 187972, 187974, 187976, 187982, 192084, 187992, 192090, 188057, 56986, 188059, 56988, 188061, 56990, 188063, 56992, 188065, 56994, 188067, 56996, 188069, 56998, 188071, 57000, 188073, 57002, 188075, 57004, 188077, 57006, 188079, 57008, 57010, 57012, 57014, 57016, 57018, 57020, 188093, 57022, 188095, 57024, 188097, 57026, 188099, 57028, 188101, 57030, 188103, 57032, 188105, 57034, 188107, 57036, 188109, 57038, 188111, 57040, 188113, 57042, 188115, 57044, 188117, 57046, 188120, 57050, 57052, 57054, 57056, 188129, 57058, 57060, 57062, 188135, 57064, 188137, 57066, 188139, 57068, 188141, 57070, 188143, 57072, 188145, 57074, 188147, 57076, 188149, 57078, 188151, 57080, 188153, 57082, 188155, 57084, 188157, 57086, 188159, 57088, 188161, 57090, 188163, 57092, 188165, 57094, 188167, 57096, 188169, 57098, 188171, 57100, 188173, 57102, 188175, 57104, 188177, 57106, 188179, 57108, 188181, 57110, 188183, 57112, 188185, 57114, 188187, 57116, 188189, 57118, 188191, 57120, 188193, 57122, 188195, 57124, 188197, 57126, 188199, 57128, 188201, 57130, 188203, 57132, 188205, 57134, 188207, 57136, 188209, 57138, 187743, 187759, 187844, 187846, 187848, 187850, 187852, 187854, 187856, 187858, 187860, 187862, 187864, 187866, 187868, 187870, 187872, 187874, 187878, 187880, 187882, 187884, 187898) ORDER BY "stock_move"."date_expected" DESC,"stock_move"."id"

2016-07-04 00:18:55,876 805 DEBUG PROD openerp.sql_db: query: SELECT "stock_move"."picking_type_id","stock_move"."id" FROM "stock_move"

WHERE "stock_move".id IN (57344, 57346, 57348, 188422, 57351, 188424, 57353, 188426, 57355, 188428, 57357, 57359, 57361, 57363, 57365, 57367, 57369, 57371, 57373, 57375, 57377, 57379, 57381, 57383, 57385, 188459, 57389, 188463, 188465, 57395, 57397, 57399, 57401, 57403, 57405, 57407, 57409, 188483, 57413, 57415, 57417, 188491, 57420, 188493, 57422, 188495, 57424, 188497, 57426, 188499, 57428, 188501, 57430, 188503, 57432, 188505, 57434, 188507, 57436, 188509, 57438, 188511, 57440, 188513, 192098, 188515, 57444, 188517, 57446, 188519, 57448, 188521, 57450, 57442, 188211, 57140, 188213, 57142, 188215, 57144, 188217, 57146, 188219, 57148, 188221, 57150, 188223, 57152, 188225, 57154, 188227, 57156, 188229, 57158, 188231, 57160, 188233, 57162, 188235, 57164, 188237, 57166, 188239, 57168, 188241, 57170, 188243, 57172, 188245, 57174, 188247, 57176, 188249, 57178, 188251, 57180, 188253, 57182, 188255, 57184, 57186, 57188, 57190, 57192, 57194, 188268, 188270, 57200, 188274, 188276, 188278, 188280, 188282, 57212, 188286, 57216, 188290, 57220, 188294, 188296, 57226, 57228, 57230, 57232, 57234, 57236, 57238, 57240, 57242, 57244, 57246, 57248, 57250, 57252, 188326, 57256, 57258, 57260, 57262, 57264, 57266, 57268, 57270, 57272, 57274, 57276, 188350, 188352, 188354, 188356, 188358, 188360, 188362, 188364, 188366, 188368, 188370, 188372, 188374, 188376, 188378, 188380, 188382, 57312, 57314, 57316, 57318, 57320, 57322, 57324, 57326, 57328, 118769, 57330, 57332, 57334, 57336, 188410, 188412, 188414) ORDER BY "stock_move"."date_expected" DESC,"stock_move"."id"

2016-07-04 00:18:56,279 805 DEBUG PROD openerp.sql_db: query: SELECT "stock_move"."picking_type_id","stock_move"."id" FROM "stock_move"

WHERE "stock_move".id IN (188416, 188418, 188420, 188431, 188433, 188435, 188437, 188439, 188441, 188443, 188445, 188447, 188449, 188451, 188453, 188455, 188457, 188461, 188467, 188469, 188471, 188473, 188475, 188477, 188479, 188481, 188485, 188487, 188489, 188523, 57452, 188525, 57454, 188527, 57456, 188529, 57458, 188531, 57460, 188533, 57462, 188535, 57464, 188537, 57466, 188539, 57468, 188541, 57470, 188543, 57472, 188545, 57474, 188547, 57476, 188549, 57478, 188551, 57480, 188553, 57482, 188555, 57484, 188557, 57486, 188559, 57488, 188561, 57490, 188563, 57492, 188565, 57494, 188567, 57496, 188569, 57498, 188571, 57500, 188573, 57502, 188575, 57504, 188577, 57506, 188579, 57508, 188581, 57510, 188583, 57513, 57515, 57517, 57519, 57521, 57523, 57525, 57527, 57529, 57531, 57533, 57535, 188609, 57539, 188613, 57542, 188615, 57544, 188617, 57546, 188619, 57548, 188621, 57550, 188623, 57552, 188625, 57554, 188627, 57556, 188629, 57558, 188631, 57560, 188633, 57562, 188635, 57564, 188637, 57566, 188639, 57569, 57571, 188645, 57575, 57577, 57579, 57581, 57583, 188657, 57587, 57589, 57591, 57593, 57595, 188669, 57599, 57601, 57603, 57605, 57607, 188681, 188683, 57613, 57615, 57617, 57619, 57621, 57623, 57625, 188258, 188260, 188262, 188264, 188266, 57208, 188292, 57222, 57224, 188298, 188302, 188304, 188306, 188308, 188310, 188312, 188314, 188316, 188318, 188320, 188322, 188324, 57254, 188328, 188330, 188332, 188334, 188342, 188348, 188384, 188386, 188388, 188390, 188392, 188394, 188404, 188406, 188408, 57338, 57340) ORDER BY "stock_move"."date_expected" DESC,"stock_move"."id"

2016-07-04 00:19:41,799 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (8379)

2016-07-04 00:19:41,800 805 DEBUG PROD openerp.sql_db: query: select id from wkf_instance where res_id=8379 and res_type='stock.move' and state='active'

2016-07-04 00:19:41,814 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (270524)

2016-07-04 00:19:41,815 805 DEBUG PROD openerp.sql_db: query: select id from wkf_instance where res_id=270524 and res_type='stock.move' and state='active'

2016-07-04 00:19:41,833 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (8381)

2016-07-04 00:19:41,834 805 DEBUG PROD openerp.sql_db: query: select id from wkf_instance where res_id=8381 and res_type='stock.move' and state='active'

2016-07-04 00:19:41,851 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (270526)

2016-07-04 00:19:41,853 805 DEBUG PROD openerp.sql_db: query: select id from wkf_instance where res_id=270526 and res_type='stock.move' and state='active'

2016-07-04 00:19:41,875 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (8383)

2016-07-04 00:19:41,879 805 DEBUG PROD openerp.sql_db: query: select id from wkf_instance where res_id=8383 and res_type='stock.move' and state='active'

2016-07-04 00:19:41,900 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (8385)

2016-07-04 00:19:41,901 805 DEBUG PROD openerp.sql_db: query: select id from wkf_instance where res_id=8385 and res_type='stock.move' and state='active'

2016-07-04 00:19:41,919 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (8387)

2016-07-04 00:19:41,920 805 DEBUG PROD openerp.sql_db: query: select id from wkf_instance where res_id=8387 and res_type='stock.move' and state='active'

2016-07-04 00:19:41,939 805 DEBUG PROD openerp.sql_db: query: UPDATE "stock_move" SET "picking_type_code"='internal',"write_uid"=1,"write_date"=(now() at time zone 'UTC') WHERE id IN (8389)

1
Avatar
Vazgeç
Rubén Cabrera

Any updates on this?

Rubén Cabrera

Is your odoo a fresh install or an upgrade from another version?

Avatar
Gonzalo Borras Beta
En İyi Yanıt

someone solved this problem? i have an installation with the same problem

1
Avatar
Vazgeç
Avatar
Ana Juaristi Olalde
En İyi Yanıt

  is this problem happening on Odoo version 8 or version 9?   

0
Avatar
Vazgeç
Rubén Cabrera

I've seen it in version 8. Didn't check in v9.

Enjoying the discussion? Don't just read, join in!

Create an account today to enjoy exclusive features and engage with our awesome community!

Üye Ol
İlgili Gönderiler Cevaplar Görünümler Aktivite
Picking Customization Option
warehouses inventory picking
Avatar
Avatar
1
May 25
2171
What is the best practice for Inter warehouse moves?
warehouses move v7
Avatar
Avatar
1
Mar 22
8774
How to request procurement from one warehouse to another?
warehouses procurement picking
Avatar
Avatar
1
Nis 18
5561
Difference between stock_move and stock_picking on Odoo(Openerp) ? Çözüldü
stock move picking
Avatar
Avatar
1
Mar 17
7246
Modify stock pickings and moves generated on sale confirmation
move picking confirm
Avatar
0
Şub 16
4140
Topluluk
  • Eğitim Araçları
  • Dokümantasyon
  • Forum
Açık Kaynak
  • İndirin
  • Github
  • Runbot
  • Çeviriler
Hizmetler
  • Odoo.sh Hosting
  • Destek
  • Sürüm Yükseltme
  • Özel Geliştirmeler
  • Eğitim
  • Muhasebeci Bulun
  • Partner Bulun
  • Partner Olun
Hakkında
  • Şirketimiz
  • Pazarlama Gereçleri
  • İletişim
  • Kariyer
  • Etkinlikler
  • Podcast
  • Blog
  • Müşteriler
  • Hukuki • Gizlilik
  • Güvenlik
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk slovenščina Español (América Latina) Español ภาษาไทย Türkçe українська Tiếng Việt

Odoo, müşteri ilişkileri yönetimi, eTicaret, muhasebe, envanter, satış noktası, proje yönetimi gibi şirketinizin tüm ihtiyaçlarını karşılayan bir açık kaynak işletme uygulamaları paketidir.

Odoo’nun eşsiz değer önermesi, aynı anda hem kullanımının çok kolay olup hem de tamamen entegre olmasıdır.

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now