OFBiz › OFBiz - Dev

[jira] Created: (OFBIZ-342) Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Nicolas Malin (Jira)

[jira] Created: (OFBIZ-342) Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.

Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.
--------------------------------------------------------------------------------------------

Key: OFBIZ-342
URL: http://issues.apache.org/jira/browse/OFBIZ-342
Project: OFBiz (The Open for Business Project)
Issue Type: Improvement
Components: accounting
Reporter: Anil K Patel
Priority: Minor

Right now Maintenance on a FixedAsset can be created in Maintenance tab on EditFixedAsset Screen.

When a Maintenance is performed on a FixedAsset, Most of time we need to Replace a Part or Add some enhancement. E.g Change Air filter on a Car, Re-Fuel a Pick-Up, Add CD player in a CAR etc. There is no Place in Maintenance for recording NEED for a Part, Issuence of a Part etc.

If this is done, Inventory managment section may also need some changes. Parts needed for Maintenance may be available in Stock in PARTS WAREHOUSE. When a Part is Issued for doing a Maintenance, as a chained effect Inventory of Part will change. Some parts are not STOCKED. As and when there is need, Its is Ordered.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-342) Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.

[ http://issues.apache.org/jira/browse/OFBIZ-342?page=comments#action_12438953 ]

Anil K Patel commented on OFBIZ-342:
------------------------------------

For supporting the above requirement, There is need for a new Table and then associate it with ItemIssuence table.

Table Name:
FIXED_ASSET_MAINT_SUPPLY_ITEM
Primary Key:
FixedAssetId, maintHistSeqId (Primary Key of FIXED_ASSET_MAINT table )
supplyItemSeqId because there can be need for more then one Part on a Maintenance.
Other Fields:
IsStackItem: Is this Supply Item a Stock Item in Supplies Warehouse or need to be special Order. Sometimes it can be a Service by a outside Provider (Vender)
purchaseOrderId, orderItemSeqId, If there was a Purchase order issued for a Special order item.
invoiceId, In case special order Item was purchased without going through purchase order process.
UnitPrice, Quantity, CancelQuantity, ItemDescription, statusId

Add The PK fields of the above table to ItemIssuence table. The fields will be
fixedAssetId, maintHistSeqId, supplyItemSeqId

With above data model changes and corresponding services the above requirements can be implemented.

> Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.
> --------------------------------------------------------------------------------------------
>
> Key: OFBIZ-342
> URL: http://issues.apache.org/jira/browse/OFBIZ-342
> Project: OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Components: accounting
> Reporter: Anil K Patel
> Priority: Minor
>
> Right now Maintenance on a FixedAsset can be created in Maintenance tab on EditFixedAsset Screen.
> When a Maintenance is performed on a FixedAsset, Most of time we need to Replace a Part or Add some enhancement. E.g Change Air filter on a Car, Re-Fuel a Pick-Up, Add CD player in a CAR etc. There is no Place in Maintenance for recording NEED for a Part, Issuence of a Part etc.
> If this is done, Inventory managment section may also need some changes. Parts needed for Maintenance may be available in Stock in PARTS WAREHOUSE. When a Part is Issued for doing a Maintenance, as a chained effect Inventory of Part will change. Some parts are not STOCKED. As and when there is need, Its is Ordered.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-342) Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.

In reply to this post by Nicolas Malin (Jira)

[ http://issues.apache.org/jira/browse/OFBIZ-342?page=comments#action_12439321 ]

Si Chen commented on OFBIZ-342:
-------------------------------

You should be using the Requirement entity instead of creating this new entity, as it already supports an entire automated purchasing scheme. Is the relationship between a maintenance task and the parts used always the same, in which case it should be defined in the database, or is it something where the maintenance technician enters what parts are needed, in which case you can have a screen for creating Requirements for a maintenance task?

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-342) Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.

In reply to this post by Nicolas Malin (Jira)

[ http://issues.apache.org/jira/browse/OFBIZ-342?page=comments#action_12448308 ]

Anil K Patel commented on OFBIZ-342:
------------------------------------

Now ItemIssuence entity has necessary field to link to fixedAssetMaint entity. In certain cases a Part may not be in Stock or a Part can be Special Order Item or it may be a Service like repair a part, we may use requirement entity. Do you think its valid to link Requirement Entity to FixedAssetMaint entity so we can track, what caused a requirement.

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-342) Issue Parts (Supplies) for Fixing Broken part of FixedAsset when a Maintenance is performed.

In reply to this post by Nicolas Malin (Jira)

[ http://issues.apache.org/jira/browse/OFBIZ-342?page=comments#action_12448353 ]

David E. Jones commented on OFBIZ-342:
--------------------------------------

Yes, I think linking these up would be a good way to go (ie so that we know when a Requirement comes from a FixedAssetMaint, and from which one). Taking a quick look at the entity, it should be fine to put directly on the Requirement entity (which already has a fixedAssetId).