<commit_before># -*- coding: utf8 -*-
#
# Copyright (C) 2014 NDP Systèmes (<http://www.ndp-systemes.fr>).
#
#    This program is free software: you can redistribute it and/or modify
#    it under the terms of the GNU Affero General Public License as
#    published by the Free Software Foundation, either version 3 of the
#    License, or (at your option) any later version.
#
#    This program is distributed in the hope that it will be useful,
#
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU Affero General Public License for more details.
#
#    You should have received a copy of the GNU Affero General Public License
#    along with this program.  If not, see <http://www.gnu.org/licenses/>.
#

{
    'name': 'Purchase Planning Improved',
    'version': '0.1',
    'author': 'NDP Systèmes',
    'maintainer': 'NDP Systèmes',
    'category': 'Purchase',
    'depends': ['purchase', 'purchase_working_days', 'stock_planning_improved'],
    'description': """
Purchase Planning Improved
==========================
This modules implement the improved planning to the purchase module.

Improved planning concept
-------------------------
The improved planning is a standardization of planning management in Odoo based on the following concepts:

- A planning is made of several tasks linked together. Each task can happen only when all the previous tasks are done.
- Each task has two dates:

    - A due date which is the date before which the task is to be done at the latest. The due date is changed only when
      a major rescheduling occurs. It is calculated backwards, task by task, from the due date of rightmost task of the
      planning (which is usually the date at which we promised to deliver the product to the customer).
    - A planned date which is the date at which we imagine the task is going to be executed given the information we
      have now. The planned date should be changed each time we have a new information and should never be in the past
      (since we are today and the task is not done, we have the information that the task will be executed sometime from
      now, but not before). It is calculated forwards, task by task, from the task(s) currently in execution.
- When a task is done, the actual execution date and the planned date are the same, but the due date is unchanged.
- The only relevant way to measure whether the project is late or early is for each task to compare the due date and
  the planned date.
- Comparing the planned date with today's date gives a indication on the accuracy of the planning, not on whether we
  are late or early.

Improved planning applied to purchase
-------------------------------------
In the purchase module, the application of the improved planning concepts is the following:

- Tasks are purchase order lines and stock moves associated to goods receipts.
- Tasks links are links between purchase order lines dans stock moves made by the procurement rules (buy)
- Purchase order lines are given a new field date called "date_required" which is the due date of the purchase order
  line.
- The "date_planned" field is the planned date of the receipt which is the date confirmed by the supplier.
- If a procurement is rescheduled, the "date_required" fields of its purchase order lines are also modified to reflect
  the new date.

Notes
-----
- This module depends on the stock_planning_improved module and interfaces with the other planning improved modules
  such as mrp.
- This module also depends on purchase_working_days module since no decent planning can be done without taking into
  account the working days.


""",
    'website': 'http://www.ndp-systemes.fr',
    'data': [
        'purchase_planning_improved_view.xml',
    ],
    'demo': [
        'purchase_planning_improved_demo.xml',
    ],
    'test': [],
    'installable': True,
    'auto_install': False,
    'license': 'AGPL-3',
    'application': False,
}
<commit_msg>Correction erreur dans desccription module purchase_planning_improved<commit_after># -*- coding: utf8 -*-
#
# Copyright (C) 2014 NDP Systèmes (<http://www.ndp-systemes.fr>).
#
#    This program is free software: you can redistribute it and/or modify
#    it under the terms of the GNU Affero General Public License as
#    published by the Free Software Foundation, either version 3 of the
#    License, or (at your option) any later version.
#
#    This program is distributed in the hope that it will be useful,
#
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU Affero General Public License for more details.
#
#    You should have received a copy of the GNU Affero General Public License
#    along with this program.  If not, see <http://www.gnu.org/licenses/>.
#

{
    'name': 'Purchase Planning Improved',
    'version': '0.1',
    'author': 'NDP Systèmes',
    'maintainer': 'NDP Systèmes',
    'category': 'Purchase',
    'depends': ['purchase', 'purchase_working_days', 'stock_planning_improved'],
    'description': """
Purchase Planning Improved
==========================
This modules implement the improved planning to the purchase module.

Improved planning concept
-------------------------
The improved planning is a standardization of planning management in Odoo based on the following concepts:

- A planning is made of several tasks linked together. Each task can happen only when all the previous tasks are done.
- Each task has two dates:

    - A due date which is the date before which the task is to be done at the latest. The due date is changed only when
      a major rescheduling occurs. It is calculated backwards, task by task, from the due date of rightmost task of the
      planning (which is usually the date at which we promised to deliver the product to the customer).
    - A planned date which is the date at which we imagine the task is going to be executed given the information we
      have now. The planned date should be changed each time we have a new information and should never be in the past
      (since we are today and the task is not done, we have the information that the task will be executed sometime from
      now, but not before). It is calculated forwards, task by task, from the task(s) currently in execution.
- When a task is done, the actual execution date and the planned date are the same, but the due date is unchanged.
- The only relevant way to measure whether the project is late or early is for each task to compare the due date and
  the planned date.
- Comparing the planned date with today's date gives a indication on the accuracy of the planning, not on whether we
  are late or early.

Improved planning applied to purchase
-------------------------------------
In the purchase module, the application of the improved planning concepts is the following:

- Tasks are purchase order lines and stock moves associated to goods receipts.
- Tasks links are links between purchase order lines and stock moves made by the procurement rules (buy)
- Purchase order lines are given a new field date called "date_required" which is the due date of the purchase order
  line.
- The "date_planned" field is the planned date of the receipt which is the date confirmed by the supplier.
- If a procurement is rescheduled, the "date_required" fields of its purchase order lines are also modified to reflect
  the new date.

Notes
-----
- This module depends on the stock_planning_improved module and interfaces with the other planning improved modules
  such as mrp.
- This module also depends on purchase_working_days module since no decent planning can be done without taking into
  account the working days.


""",
    'website': 'http://www.ndp-systemes.fr',
    'data': [
        'purchase_planning_improved_view.xml',
    ],
    'demo': [
        'purchase_planning_improved_demo.xml',
    ],
    'test': [],
    'installable': True,
    'auto_install': False,
    'license': 'AGPL-3',
    'application': False,
}

{'fraction_non_alphanumeric': 0.08196518948277991, 'fraction_numerical': 0.00222194790766572, 'mean_word_length': 3.393709327548807, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 6, 'xml': 4}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4657268', 'n_tokens_mistral': 2074, 'n_tokens_neox': 2017, 'n_words': 1141}