[jira] [Updated] (OFBIZ-9800) French translation of OFBiz website

2018-04-10 Thread Olivier Heintz (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Heintz updated OFBIZ-9800:
--
Attachment: website-fr.tar.gz

> French translation of OFBiz website
> ---
>
> Key: OFBIZ-9800
> URL: https://issues.apache.org/jira/browse/OFBIZ-9800
> Project: OFBiz
>  Issue Type: Improvement
>  Components: site
>Reporter: Olivier Heintz
>Priority: Minor
> Attachments: website-fr.tar, website-fr.tar, website-fr.tar.gz, 
> website-fr.tar.gz, website-fr.tar.gz, website-fr.tar.gz
>
>
> To evaluate the workload of translate all the ofbiz website page in french, 
> and so to maintain the translation when there are some modifications, I have 
> start to translate them.
> There are between 10 and 15 page to translate, and translate one is between 1 
> and 2 hours.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-9800) French translation of OFBiz website

2018-04-10 Thread Olivier Heintz (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431887#comment-16431887
 ] 

Olivier Heintz commented on OFBIZ-9800:
---

[^website-fr.tar.gz]

update with svn 1828789

> French translation of OFBiz website
> ---
>
> Key: OFBIZ-9800
> URL: https://issues.apache.org/jira/browse/OFBIZ-9800
> Project: OFBiz
>  Issue Type: Improvement
>  Components: site
>Reporter: Olivier Heintz
>Priority: Minor
> Attachments: website-fr.tar, website-fr.tar, website-fr.tar.gz, 
> website-fr.tar.gz, website-fr.tar.gz, website-fr.tar.gz
>
>
> To evaluate the workload of translate all the ofbiz website page in french, 
> and so to maintain the translation when there are some modifications, I have 
> start to translate them.
> There are between 10 and 15 page to translate, and translate one is between 1 
> and 2 hours.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Reopened] (OFBIZ-9501) Move all data in applications to the datamodel component

2018-04-10 Thread Rishi Solanki (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rishi Solanki reopened OFBIZ-9501:
--

Reopening the ticket to address the improvement suggested by Taher in his last 
comment.

> Move all data in applications to the datamodel component
> 
>
> Key: OFBIZ-9501
> URL: https://issues.apache.org/jira/browse/OFBIZ-9501
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL APPLICATIONS
>Affects Versions: 17.12.01
>Reporter: Taher Alkhateeb
>Assignee: Rishi Solanki
>Priority: Minor
>  Labels: application, data
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, 
> OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, OFBIZ-9501-DemoData.patch, 
> OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, 
> OFBIZ-9501_Consolidated.patch
>
>
> As per a community [discussion 
> thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E]
>  we decided to move all data (seed, seed-initial, demo) to the datamodel 
> component. and to also reduce and cleanup this data to ease debugging and 
> maintenance.
> After moving all the data, the directory and file structure would be similar 
> to the below:
> data/
> ├── demo
> │   ├── AccountingDemoData.xml
> │   ├── CommonDemoData.xml
> │   ├── ContentDemoData.xml
> │   ├── HumanresDemo.xml
> │   ├── ManufacturingDemoData.xml
> │   ├── MarketingDemoData.xml
> │   ├── OrderDemoData.xml
> │   ├── PartyDemoData.xml
> │   ├── ProductDemoData.xml
> │   ├── ShipmentDemoData.xml
> │   └── WorkEffortDemoData.xml
> ├── seed
> │   ├── AccountingSeedData.xml
> │   ├── CommonSeedData.xml
> │   ├── ContentSeedData.xml
> │   ├── HumanresSeedData.xml
> │   ├── ManufacturingSeedData.xml
> │   ├── MarketingSeedData.xml
> │   ├── OrderSeedData.xml
> │   ├── PartySeedData.xml
> │   ├── ProductSeedData.xml
> │   ├── ShipmentSeedData.xml
> │   └── WorkEffortSeedData.xml
> └── seed-initial
> ├── AccountingSeedInitialData.xml
> ├── CommonSeedInitialData.xml
> ├── ContentSeedInitialData.xml
> ├── HumanresSeedInitialData.xml
> ├── ManufacturingSeedInitialData.xml
> ├── MarketingSeedInitialData.xml
> ├── OrderSeedInitialData.xml
> ├── PartySeedInitialData.xml
> ├── ProductSeedInitialData.xml
> ├── ShipmentSeedInitialData.xml
> └── WorkEffortSeedInitialData.xml



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (OFBIZ-9501) Move all data in applications to the datamodel component

2018-04-10 Thread Rishi Solanki (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rishi Solanki resolved OFBIZ-9501.
--
Resolution: Fixed

Done at -r1828817.

> Move all data in applications to the datamodel component
> 
>
> Key: OFBIZ-9501
> URL: https://issues.apache.org/jira/browse/OFBIZ-9501
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL APPLICATIONS
>Affects Versions: 17.12.01
>Reporter: Taher Alkhateeb
>Assignee: Rishi Solanki
>Priority: Minor
>  Labels: application, data
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, 
> OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, OFBIZ-9501-DemoData.patch, 
> OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, 
> OFBIZ-9501_Consolidated.patch
>
>
> As per a community [discussion 
> thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E]
>  we decided to move all data (seed, seed-initial, demo) to the datamodel 
> component. and to also reduce and cleanup this data to ease debugging and 
> maintenance.
> After moving all the data, the directory and file structure would be similar 
> to the below:
> data/
> ├── demo
> │   ├── AccountingDemoData.xml
> │   ├── CommonDemoData.xml
> │   ├── ContentDemoData.xml
> │   ├── HumanresDemo.xml
> │   ├── ManufacturingDemoData.xml
> │   ├── MarketingDemoData.xml
> │   ├── OrderDemoData.xml
> │   ├── PartyDemoData.xml
> │   ├── ProductDemoData.xml
> │   ├── ShipmentDemoData.xml
> │   └── WorkEffortDemoData.xml
> ├── seed
> │   ├── AccountingSeedData.xml
> │   ├── CommonSeedData.xml
> │   ├── ContentSeedData.xml
> │   ├── HumanresSeedData.xml
> │   ├── ManufacturingSeedData.xml
> │   ├── MarketingSeedData.xml
> │   ├── OrderSeedData.xml
> │   ├── PartySeedData.xml
> │   ├── ProductSeedData.xml
> │   ├── ShipmentSeedData.xml
> │   └── WorkEffortSeedData.xml
> └── seed-initial
> ├── AccountingSeedInitialData.xml
> ├── CommonSeedInitialData.xml
> ├── ContentSeedInitialData.xml
> ├── HumanresSeedInitialData.xml
> ├── ManufacturingSeedInitialData.xml
> ├── MarketingSeedInitialData.xml
> ├── OrderSeedInitialData.xml
> ├── PartySeedInitialData.xml
> ├── ProductSeedInitialData.xml
> ├── ShipmentSeedInitialData.xml
> └── WorkEffortSeedInitialData.xml



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (OFBIZ-9501) Move all data in applications to the datamodel component

2018-04-10 Thread Rishi Solanki (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rishi Solanki closed OFBIZ-9501.


> Move all data in applications to the datamodel component
> 
>
> Key: OFBIZ-9501
> URL: https://issues.apache.org/jira/browse/OFBIZ-9501
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL APPLICATIONS
>Affects Versions: 17.12.01
>Reporter: Taher Alkhateeb
>Assignee: Rishi Solanki
>Priority: Minor
>  Labels: application, data
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, 
> OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, OFBIZ-9501-DemoData.patch, 
> OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, 
> OFBIZ-9501_Consolidated.patch
>
>
> As per a community [discussion 
> thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E]
>  we decided to move all data (seed, seed-initial, demo) to the datamodel 
> component. and to also reduce and cleanup this data to ease debugging and 
> maintenance.
> After moving all the data, the directory and file structure would be similar 
> to the below:
> data/
> ├── demo
> │   ├── AccountingDemoData.xml
> │   ├── CommonDemoData.xml
> │   ├── ContentDemoData.xml
> │   ├── HumanresDemo.xml
> │   ├── ManufacturingDemoData.xml
> │   ├── MarketingDemoData.xml
> │   ├── OrderDemoData.xml
> │   ├── PartyDemoData.xml
> │   ├── ProductDemoData.xml
> │   ├── ShipmentDemoData.xml
> │   └── WorkEffortDemoData.xml
> ├── seed
> │   ├── AccountingSeedData.xml
> │   ├── CommonSeedData.xml
> │   ├── ContentSeedData.xml
> │   ├── HumanresSeedData.xml
> │   ├── ManufacturingSeedData.xml
> │   ├── MarketingSeedData.xml
> │   ├── OrderSeedData.xml
> │   ├── PartySeedData.xml
> │   ├── ProductSeedData.xml
> │   ├── ShipmentSeedData.xml
> │   └── WorkEffortSeedData.xml
> └── seed-initial
> ├── AccountingSeedInitialData.xml
> ├── CommonSeedInitialData.xml
> ├── ContentSeedInitialData.xml
> ├── HumanresSeedInitialData.xml
> ├── ManufacturingSeedInitialData.xml
> ├── MarketingSeedInitialData.xml
> ├── OrderSeedInitialData.xml
> ├── PartySeedInitialData.xml
> ├── ProductSeedInitialData.xml
> ├── ShipmentSeedInitialData.xml
> └── WorkEffortSeedInitialData.xml



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (OFBIZ-9501) Move all data in applications to the datamodel component

2018-04-10 Thread Rishi Solanki (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432270#comment-16432270
 ] 

Rishi Solanki edited comment on OFBIZ-9501 at 4/10/18 1:38 PM:
---

Done at -r1828817. Thanks Taher!


was (Author: rishisolankii):
Done at -r1828817.

> Move all data in applications to the datamodel component
> 
>
> Key: OFBIZ-9501
> URL: https://issues.apache.org/jira/browse/OFBIZ-9501
> Project: OFBiz
>  Issue Type: Improvement
>  Components: ALL APPLICATIONS
>Affects Versions: 17.12.01
>Reporter: Taher Alkhateeb
>Assignee: Rishi Solanki
>Priority: Minor
>  Labels: application, data
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-9051-004.patch, OFBIZ-9501-001.patch, 
> OFBIZ-9501-002.patch, OFBIZ-9501-003.patch, OFBIZ-9501-DemoData.patch, 
> OFBIZ-9501-WorkEffortSeedData.patch, OFBIZ-9501_Consolidated-2.patch, 
> OFBIZ-9501_Consolidated.patch
>
>
> As per a community [discussion 
> thread|https://lists.apache.org/thread.html/eb6ea79195204356a362dbf208c5dbb6d321d001bf2b79819dc45a24@%3Cdev.ofbiz.apache.org%3E]
>  we decided to move all data (seed, seed-initial, demo) to the datamodel 
> component. and to also reduce and cleanup this data to ease debugging and 
> maintenance.
> After moving all the data, the directory and file structure would be similar 
> to the below:
> data/
> ├── demo
> │   ├── AccountingDemoData.xml
> │   ├── CommonDemoData.xml
> │   ├── ContentDemoData.xml
> │   ├── HumanresDemo.xml
> │   ├── ManufacturingDemoData.xml
> │   ├── MarketingDemoData.xml
> │   ├── OrderDemoData.xml
> │   ├── PartyDemoData.xml
> │   ├── ProductDemoData.xml
> │   ├── ShipmentDemoData.xml
> │   └── WorkEffortDemoData.xml
> ├── seed
> │   ├── AccountingSeedData.xml
> │   ├── CommonSeedData.xml
> │   ├── ContentSeedData.xml
> │   ├── HumanresSeedData.xml
> │   ├── ManufacturingSeedData.xml
> │   ├── MarketingSeedData.xml
> │   ├── OrderSeedData.xml
> │   ├── PartySeedData.xml
> │   ├── ProductSeedData.xml
> │   ├── ShipmentSeedData.xml
> │   └── WorkEffortSeedData.xml
> └── seed-initial
> ├── AccountingSeedInitialData.xml
> ├── CommonSeedInitialData.xml
> ├── ContentSeedInitialData.xml
> ├── HumanresSeedInitialData.xml
> ├── ManufacturingSeedInitialData.xml
> ├── MarketingSeedInitialData.xml
> ├── OrderSeedInitialData.xml
> ├── PartySeedInitialData.xml
> ├── ProductSeedInitialData.xml
> ├── ShipmentSeedInitialData.xml
> └── WorkEffortSeedInitialData.xml



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10306) Create an asciidoc style guide for the OFBiz project

2018-04-10 Thread Sharan Foga (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432571#comment-16432571
 ] 

Sharan Foga commented on OFBIZ-10306:
-

Hi [~mbrohl] - this is great work. Let's get this committed. There are some 
minor grammar changes but nothing major so it will be easier for me to fix once 
the patch is in the codebase :)

> Create an asciidoc style guide for the OFBiz project
> 
>
> Key: OFBIZ-10306
> URL: https://issues.apache.org/jira/browse/OFBIZ-10306
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
>Priority: Minor
>  Labels: asciidoc, documentation
> Attachments: OFBIZ-10306_Create_styleguide.patch
>
>
> Create a guideline/ style guide as discussed in the mailing list (see 
> [https://s.apache.org/qJoS]).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (OFBIZ-10263) Add Document Content: hr-positions.adoc

2018-04-10 Thread Sharan Foga (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-10263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432722#comment-16432722
 ] 

Sharan Foga commented on OFBIZ-10263:
-

Hi [~bjugl], yes you are right. This is a duplicate, so will close it 
highlighting that.

> Add Document Content: hr-positions.adoc
> ---
>
> Key: OFBIZ-10263
> URL: https://issues.apache.org/jira/browse/OFBIZ-10263
> Project: OFBiz
>  Issue Type: Sub-task
>Reporter: Sharan Foga
>Assignee: Benjamin Jugl
>Priority: Minor
> Attachments: hr-positions.adoc
>
>
> Using details from the OFBiz wiki workspaces and the Human Resources Guide 
> and other human resources asciidoc file,  write or organise the content for 
> the hr-positions.adoc file.
> A copy of the existing file will be attached. Please write document content 
> for hr-positions.adoc by updating the template then re-attach the updated 
> document to this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (OFBIZ-10306) Create an asciidoc style guide for the OFBiz project

2018-04-10 Thread Michael Brohl (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brohl closed OFBIZ-10306.
-
Resolution: Implemented

Hi Sharan,

I've committed the draft at r1828857. Thanks for your help!

> Create an asciidoc style guide for the OFBiz project
> 
>
> Key: OFBIZ-10306
> URL: https://issues.apache.org/jira/browse/OFBIZ-10306
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Michael Brohl
>Priority: Minor
>  Labels: asciidoc, documentation
> Attachments: OFBIZ-10306_Create_styleguide.patch
>
>
> Create a guideline/ style guide as discussed in the mailing list (see 
> [https://s.apache.org/qJoS]).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (OFBIZ-6964) Support for replenishment of a secondary warehouse from a main warehouse

2018-04-10 Thread Pawan Verma (JIRA)

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pawan Verma reassigned OFBIZ-6964:
--

Assignee: Pawan Verma  (was: Swapnil Shah)

> Support for replenishment of a secondary warehouse from a main warehouse
> 
>
> Key: OFBIZ-6964
> URL: https://issues.apache.org/jira/browse/OFBIZ-6964
> Project: OFBiz
>  Issue Type: New Feature
>  Components: manufacturing, product
>Reporter: Shrenik Bhura
>Assignee: Pawan Verma
>Priority: Major
>  Labels: features
> Fix For: 17.12.01
>
> Attachments: screenshot-1.png
>
>
> At the onset let me define a few terms clearly as I mean it in the story 
> description below :
> Requirement - A request generated for a particular product for a specific 
> quantity that needs to be purchased from a supplier for satisfying certain 
> inventory needs of a particular facility.
> Replenishment - A request generated for a particular product for a specific 
> quantity that needs to be transferred from a "backup facility" for satisfying 
> certain inventory needs of a particular facility.
> Fulfilment - The process of reserving, picking, packing and shipping the 
> ordered quantity of product(s) as per a sales order.
> Terms 'warehouse' and 'facility' have been used interchangeably.
> *The Use Case:*
> Consider a scenario wherein there is a website and a physical retail store of 
> the same Company.
> Each having its own facility i.e. 1:1 mapping.
> {{Store A (webstore) -> associated with facility 1 (webstore facility)}}
> {{Store B (retailstore) -> associated with facility 2 (retailstore facility)}}
> However, both the stores share the same catalog/products. But both have 
> independent inventory requirement and replenishment rules for the same 
> product. 
> There is a Requirement Method Enum ID (RMEI) of each product which is 
> applicable irrespective of the store and supersedes the RMEI defined, if any, 
> on a store. 
> A product's inventory thresholds (Minimum Stock, Reorder Quantity) are 
> independently managed via the facilities tab for the product. A product has 
> its ATP and QOH levels on a per facility basis. _Do note that all these 
> inventory numbers are at a facility level and has no bearing at a store 
> level._
> Where the difficulty crops up with the current implementation is the way 
> requirements are generated. A product can have only one RMEI. When an order 
> is placed from any store, then based on the combination of a product's RMEI 
> and the store mapped facility's inventory threshold, requirements are 
> generated. This is without consideration of the inventory status (surplus or 
> otherwise) at another facility of the same Company. If a store has multiple 
> facilities associated with it then the one defined in the ProductStore entity 
> -> inventoryFacilityId field would be considered for picking the inventory 
> threshold values and thus for requirement generation. 
> Most typical real-world facility arrangements: 
>   1. Usually an organisation would have a main facility/warehouse where 
> all the purchases are received and sub-facilities which are replenished from 
> the main facility after QA, internal processes, etc. OR 
>   2. For each product there would be a primary facility where the product 
> is received from the supplier (to derive benefits of demographic convenience 
> and consumption patterns) and then replenished to other facilities on a 
> demand based pull basis.
> To drive efficiencies across an organisation they need methods to consider 
> open fulfilment needs, in process purchase orders and inventory levels across 
> multiple facilities and thereafter propose inventory transfers across them to 
> facilitate better stocking and thus order fulfilment.
> Coming back to our use case, the webstore warehouse is the main facility at 
> which incoming shipments from suppliers are received for the entire Company 
> but sales order fulfilment happens only for the webstore. The retail 
> warehouse is primarily 're-stocked' via replenishment requests raised upon 
> the webstore warehouse and thus need not issue direct purchase orders to 
> suppliers. However, if the need be, requirement generated based on the 
> product's RMEI and the retail facility's inventory thresholds can also be 
> approved, converted into Purchase order and issued.
> *Proposed Solution:*
> There doesn't seem to be an out of the box solution for this in OFBiz. This 
> could work if either we think of -
> Approach A: Setting RMEI at a ProductFacility level as well which shall 
> supersede the Product level RMEI setting OR 
> Approach B: Build in support for a solution that I have encountered in 
> Opentaps (a system built atop OFBiz) i.e. implement support for