コンテンツへスキップ
Odoo メニュー
  • サインイン
  • 無料で15日試す
  • アプリ
    財務
    • 会計
    • 請求
    • 経費
    • スプレッドシート(BI)
    • ドキュメント管理
    • 署名
    販売
    • CRM
    • 販売
    • POS店舗
    • POSレストラン
    • サブスクリプション
    • レンタル
    ウェブサイト
    • ウェブサイトビルダー
    • eコマース
    • ブログ
    • フォーラム
    • ライブチャット
    • eラーニング
    サプライチェーン
    • 在庫
    • 製造
    • 製品ライフサイクル管理 (PLM)
    • 購買
    • 整備
    • 品質
    人事業務
    • 従業員管理
    • 採用
    • 休暇管理
    • 人事評価
    • リファラル
    • フリート
    マーケティング
    • ソーシャルマーケティング
    • メールマーケティング
    • SMSマーケティング
    • イベント
    • マーケティングオートメーション
    • アンケート調査
    サービス
    • プロジェクト管理
    • タイムシート
    • フィールドサービス
    • ヘルプデスク
    • 計画
    • アポイントメント
    生産性向上ツール
    • ディスカッション
    • 承認
    • IoT
    • VoIP
    • ナレッジ
    • WhatsApp
    サードパーティアプリ Odooスタジオ Odooクラウドプラットホーム
  • インダストリー(業種別ソリューション)
    小売
    • 書店
    • アパレルショップ
    • 家具専門店
    • 食料品店
    • 金物店
    • 玩具店
    飲食・ホスピタリティ業界
    • バー・パブ
    • レストラン
    • ファストフード
    • ゲストハウス
    • 飲料販売代理店
    • ホテル
    不動産
    • 不動産会社
    • 建築事務所
    • 建設
    • 不動産管理
    • 造園
    • 住宅所有者組合
    コンサルティング
    • 会計事務所
    • Odooパートナー
    • マーケティングエージェンシー
    • 法律事務所
    • 人材派遣
    • 監査・認証
    製造
    • テキスタイル
    • 金属
    • 家具
    • 飲食
    • 醸造所
    • コーポレートギフト
    ヘルス & フィットネス
    • スポーツクラブ
    • 眼鏡店
    • フィットネスセンター
    • ウェルネス専門家
    • 薬局
    • ヘアサロン
    業種
    • 便利屋
    • IT ハードウェア・サポート
    • 太陽エネルギーシステム
    • 靴メーカー
    • クリーニングサービス
    • 空調設備サービス
    その他
    • 非営利団体
    • 環境機関
    • ビルボードレンタル
    • 写真
    • 自転車リース
    • ソフトウェアリセラー
    すべての業種を見る
  • コミュニティ
    学ぶ
    • チュートリアル
    • ドキュメンテーション
    • 認定
    • トレーニング
    • ブログ
    • ポッドキャスト
    教育サポート
    • 教育プログラム
    • Scale Up! ビジネスゲーム
    • Odooオフィス訪問
    ソフトを入手
    • ダウンロード
    • エディションを比較
    • リリース
    コラボレーション
    • Github
    • フォーラム
    • イベント
    • 翻訳
    • パートナーになる
    • パートナー様向けサービス
    • 会計事務所を登録
    サービス利用
    • パートナー一覧
    • 会計事務所一覧
    • 今すぐ相談する
    • 導入支援サービス
    • お客様一覧
    • サポート
    • アップグレード
    Github Youtube Twitter Linkedin Instagram Facebook Spotify
    +1 (650) 691-3277
    製品デモを利用する
  • 料金
  • ヘルプ

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

  • CRM
  • e-Commerce
  • 会計
  • 在庫
  • PoS
  • プロジェクト
  • MRP
All apps
コミュニティで交流するには登録する必要があります。
全てのポスト 人々 バッジ
タグ (全て表示)
odoo accounting v14 pos v15
このフォーラムについて
コミュニティで交流するには登録する必要があります。
全てのポスト 人々 バッジ
タグ (全て表示)
odoo accounting v14 pos v15
このフォーラムについて
ヘルプ

Reordering rule to specific location not working V16.0

購読

この投稿に活動があった際に通知を受け取ります

この質問にフラグが付けられました
reordering-rules
2 返信
3928 ビュー
アバター
J Dekker

Good day, i am trying to figure out how to get the reordering to work as expected.


I have made an article with an reordering rule set to a specific location (lets call it Location A, with the below reordering rule setting)

location = WH/Stock/Location A

Preffered Rout = Buy

Trigger = Auto

Min Quantity =  10

Max quantity = 0 

Multiple Quantity = 40


Then when i make an salesorder for this article with an amount greater then the current stock. Odoo will make a new MANUAL reorder rule for the location "warehouse".

location = WH/Stock/

Preffered Rout = Buy

Trigger = Manual

Min Quantity = 0

Max quantity = 0 

Multiple Quantity =0


What i expect is that Odoo would make an RFQ for the desired location following the given rules. (else what is the point of making the rule of Odoo just makes another one)


So what am I doing wrong?

any help is appreciated

Thanks in advance!





0
アバター
破棄
アバター
Waleed Ali Mohsen
最善の回答

There is a difference between  reordering rules and MTO (Make To Order).

Make to order (MTO) is a procurement route that creates a draft purchase order (or manufacturing order) each time a sales order is confirmed, regardless of the current stock level.

Unlike products replenished using reordering rules, Odoo automatically links the sales order to the PO or MO generated by the MTO route.

Another difference between reordering rules and MTO is, with MTO, Odoo generates a draft PO or MO immediately after the SO is confirmed. With reordering rules, Odoo generates a draft PO or MO when the product’s forecasted stock falls below the set minimum quantity.

In addition, Odoo automatically adds quantities to the PO or MO as the forecast changes, so long as the PO or MO is not confirmed.

The MTO route is the best replenishment strategy for products that are customized, and/or for products that have no stock kept on-hand.


You need to activate the MTO route because it's archived by default so you can refer to the blow documentation: 

Selecting a replenishment strategy — Odoo 16.0 documentation  


0
アバター
破棄
J Dekker
著作者

Thank you for your feedback. I do not think MTO is the way to go.
I simply want our stock to be refiled based on the re-order rule. In my mind the stock should be used up via a salesorder.

Waleed Ali Mohsen

If you want to replenish your stock so you will use reordering rules and Odoo will generate draft PO when the product’s forecasted stock falls below the set minimum quantity.

J Dekker
著作者

Thank you again for your feedback. I thought that reordering rules would indeed trigger an RFQ/PO when it drops below the minimum value. However the salesorder appears to demand the items from the warehouse stock location. Not from the article specific location. I do not understand why.

Waleed Ali Mohsen

the sales order appears to demand the items from the warehouse stock location because of the source warehouse in Delivery order operation is the warehouse stock location.

J Dekker
著作者

Thank you for your awnser. I have added a picture to my question. I hope you can read it.
It shows the diagram of my Buy route on an specific item. In the far right you can see my re-order rule. When i look at this, i think that, upon a sale, Odoo does nothing with the re-order rule. It will look in the warehouse stock. I could adjust the buy route. But then i would have to make it unique per item.
So i am guessing i do not understand the principle. I simply want an item to arrive into a certain location. and upon sales be picked/sold/replenished on that same location. This should however be item unique. (our warehouse is not one big pile of stuff).

So the question remains, what am i doing wrong?

アバター
Jaideep
最善の回答

If you wish to generate a RFQ, then you would need to set the Trigger in replenishment to "Auto" with route as 'Buy'

(You can select additional columns to view using the double arrow icon on the right side of header row.)

Stock availability and validation at a location are defined in the routes being triggered, post this validation a reorder is created in replenishment.

Not sure if your question is regarding route or replenishment trigger.

 

0
アバター
破棄
J Dekker
著作者

Thank you for your feedback. I have added some data in hope to clarify my question.
My re-ordering rule already has a trigger which is set to auto. My route is Buy.
Maybe i am missing something in here, but i thought this is all you need to do. (that and assign a supplier to the specific article and make it stock holding)

Jaideep
Replenishment is created at a different location, suggesting it has to do with your delivery route.

Suspecting that the delivery route is configured to pull from WH/ Stock rather than WH/Stock/ Loc A.

J Dekker
著作者

Thanks again for your feedback. I am only using the "buy" route. Does that mean i have to make an unique route for every article? (we have almost 10000) i thought that was controlled via the reordering rules?

Jaideep
My reference was to the delivery route which is triggered by sale order. If you store the product in LocA the delivery order needs to pull from this location and in the absence of stock at this location your reorder rule is configured to trigger a RFQ.

From what you describe, the reorder rule is triggered from WH/Stock location makes for the suspension that delivery order is looking for the product availability at WH/Stock location rather than LocA.

Am not certain I understand your question on the number of products.. reorder rules are defined at product level as min max and multiples of qty vary by the product.

Delivery route can be on product or product category or sale order line or WH

Hope I have been able to address your question, else it might help if you describe the expected process.
J Dekker
著作者

Thank you for your awnser. I have added a picture to my question. I hope you can read it.
It shows the diagram of my Buy route on an specific item. In the far right you can see my re-order rule. When i look at this, i think that, upon a sale, Odoo does nothing with the re-order rule. It will look in the warehouse stock. I could adjust the buy route. But then i would have to make it unique per item.
So i am guessing i do not understand the principle. I simply want an item to arrive into a certain location. and upon sales be picked/sold/replenished on that same location. This should however be item unique. (our warehouse is not one big pile of stuff).

So the question remains, what am i doing wrong?

OdooBot
>>> I simply want an item to arrive into a certain location. and upon sales be picked/sold/replenished on that same location. This should however be item unique. (our warehouse is not one big pile of stuff).<<<

1. To have an item be received in a specific location what configurations are set? Default receive location is WH/Stock - one of the ways is to use 'Put away rules' or to manually set the location on the receipt operation.

2. To have a product picked from a location - the delivery route has to be set to pull from that location. As default rules it is set as WH/Stock. If you need this to pick from a specific location this has to be set on the rule. Or manually set on the Delivery operation.

3. Replenish rules are triggered based on product reservation and availability at the specified location. You have set this on WH/Stock/ Loc A in your example. Since the product is being picked from WH/Stock as per your example this rule didn't trigger as there was no change to stock at this location. If you change the source location manually on the delivery order to LocA and check availability or validate the delivery, replenishment rule would trigger.

Yes, specific to this example you are right that the replenishment did not trigger at LocA, but the replenishment triggered at WH/Stock >> When i look at this, i think that, upon a sale, Odoo does nothing with the re-order rule.<< 

You are not doing anything wrong, just that with addition of multiple locations, the configuration needs to be aligned with the process. The suggested configuration would need to be based # of locations (seems you have 1 for each item as you mention 'item unique'), # products and the process to receive, reserve and pick.

If there weren't multi locations involved, the configuration would have worked out of the box

A couple of suggestions to try out as you go about defining the configuration that best suits your business.

1. To not have the sale order trigger a route, but have replenishment rules trigger them .. validate that the supply method on the delivery rule is set to "Take from Stock". I believe this set as the RFQ wasn't generated but a replenishment at WH/Stock



2. Reservation - Set this to manual on the delivery operation, this might prevent the replenishment to be triggered at WH/Stock, allowing for the replenishment rules to trigger after the stock is removed from WH/Stock/LocA.



Hope this helps.

J Dekker
著作者

Thank you for your feedback. I have come up with this.
(see my question, because i can not paste a picture in the comment)

OdooBot
I believe the process is location centric (sales, delivery, buy, receipt) and not article centric.





Notwithstanding the 2nd screenshot has receipt operation vendor to location which is desired. However, there are 2 delivery rules configured for the product Loc to customer and WH/Stock to customer. You need to ensure the Loc to customer route is triggered by sale and not WH/Stock to customer route 


ディスカッションを楽しんでいますか?読むだけでなく、参加しましょう!

今すぐアカウントを作成して、限定機能を利用したり、素晴らしいコミュニティと交流しましょう!

登録
関連投稿 返信 ビュー 活動
Reorder Rules creating RFQ for purchase when demand is already satisfied
inventory reordering-rules
アバター
0
7月 24
1833
How to update reordering rules in bulk? 解決済
ReorderingRule reordering-rules
アバター
アバター
2
1月 24
2745
Reordering Rules SNOOZE not Working.
ReorderingRule reordering-rules
アバター
アバター
1
1月 23
2928
How to stop automatic purchase orders splitting for same vendor in Odoo14? reordering rules problem 解決済
v14 reordering-rules
アバター
アバター
アバター
2
7月 22
4018
Reordering rule 0-0-1 not working 解決済
odoo reordering-rules v17
アバター
アバター
アバター
2
6月 25
2194
コミュニティ
  • チュートリアル
  • ドキュメンテーション
  • フォーラム
オープンソース
  • ダウンロード
  • Github
  • Runbot
  • 翻訳
サービス
  • Odoo.shホスティング
  • サポート
  • アップグレード
  • カスタム開発
  • 教育プログラム
  • 会計事務所一覧
  • パートナー一覧
  • パートナーになる
企業情報
  • 会社概要
  • ブランドアセット
  • お問い合わせ
  • 採用情報
  • イベント
  • ポッドキャスト
  • ブログ
  • お客様一覧
  • リーガル情報 • プライバシーポリシー
  • セキュリティ
الْعَرَبيّة 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(オドゥー)は、CRM、eコマース、会計、在庫管理、POS、プロジェクト管理など、企業のさまざまな業務を一つのシステムで管理できる、ベルギー発のオープンソースのERPソフトウェアです。

高機能で使いやすく、完全に統合されたERPとして、ユニークな価値を提供しています。

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