Reflect Inventory availability w/o concrete figures

[c.schinzer]

All,


I'd like to find a way to build the following requirements into the standard
product / facility mechanisms of OFBiz:

* Inventory is not kept in the store, actually the stite is a reseller
platform (orders collected and forwarded to reseller who does all handling
includung shipping)
* Availability of Inventory is communicated nightly by the Product Supplier;
this is not figures of QoH but rather an info of type: {we have it; we won't
have it any more; will be available as of date}

I am currently slightly confused about the Product and Inventory data model
and how I should set flags on Product:
* Is it enough to Create an InventoryItem per product and set the 'statusId'
to a proper value? A nightly job would then check the status and change it?
How can I -- in this aproach -- reflect projected "available-again" dates?
* Is it required to go the InventoryItemDetail path and create a detail for
each availability-period of a product?
* How do I handle QoH? Can I just set to value 1 and switch off the
"requires QoH" flag on the Product? What would I then select as Inventory
Method?

Thanks for any hint !
Regards


Carsten

[BJ Freeman]

your describing Dropship with a customization for inventory levels.
Normally in Dropship the code does not look for inventory.
the way I handle it is a component for the dropshipper or fulfillment
company. I define an entity that fits their data. once this is imported,
I use the custom code to read their data and set the dates based on
their inventory. if discontinued then use the through date to disable
product. if out of stock change the from date to when the product will
be in-stock.

the custom code creates a product in  catalog for the supplier of new
products that a employee can then copy in their store catalog. Custom
code copies the product then adds a supplier product in inventory linked
to the catalog product they copied.
The custom code looks for products that are linked to the supplier
product by partyID to change the dates.

this should get you going in the right direction.



Carsten Schinzer sent the following on 7/8/2011 12:34 AM:

> All,
>
>
> I'd like to find a way to build the following requirements into the standard
> product / facility mechanisms of OFBiz:
>
> * Inventory is not kept in the store, actually the stite is a reseller
> platform (orders collected and forwarded to reseller who does all handling
> includung shipping)
> * Availability of Inventory is communicated nightly by the Product Supplier;
> this is not figures of QoH but rather an info of type: {we have it; we won't
> have it any more; will be available as of date}
>
> I am currently slightly confused about the Product and Inventory data model
> and how I should set flags on Product:
> * Is it enough to Create an InventoryItem per product and set the 'statusId'
> to a proper value? A nightly job would then check the status and change it?
> How can I -- in this aproach -- reflect projected "available-again" dates?
> * Is it required to go the InventoryItemDetail path and create a detail for
> each availability-period of a product?
> * How do I handle QoH? Can I just set to value 1 and switch off the
> "requires QoH" flag on the Product? What would I then select as Inventory
> Method?
>
> Thanks for any hint !
> Regards
>
>
> Carsten
>

[c.schinzer]

Hi BJ and thanks for your comment.
I realize, I had a typo in my requirements as it is rather the product supplier who handles fulfillment after we drop orders to their end. Not the reseller.

However I do not feel this will change your comments. Will need to get that on a sheet of paper though and digest.

Thanks again. Regards


Carsten
Gesendet mit BlackBerry® Webmail von Telekom Deutschland  

-----Original Message-----
From: BJ Freeman <[hidden email]>
Date: Fri, 08 Jul 2011 07:50:13
To: <[hidden email]>
Reply-To: [hidden email]
Subject: Re: Reflect Inventory availability w/o concrete figures

your describing Dropship with a customization for inventory levels.
Normally in Dropship the code does not look for inventory.
the way I handle it is a component for the dropshipper or fulfillment
company. I define an entity that fits their data. once this is imported,
I use the custom code to read their data and set the dates based on
their inventory. if discontinued then use the through date to disable
product. if out of stock change the from date to when the product will
be in-stock.

the custom code creates a product in  catalog for the supplier of new
products that a employee can then copy in their store catalog. Custom
code copies the product then adds a supplier product in inventory linked
to the catalog product they copied.
The custom code looks for products that are linked to the supplier
product by partyID to change the dates.

this should get you going in the right direction.



Carsten Schinzer sent the following on 7/8/2011 12:34 AM:

> All,
>
>
> I'd like to find a way to build the following requirements into the standard
> product / facility mechanisms of OFBiz:
>
> * Inventory is not kept in the store, actually the stite is a reseller
> platform (orders collected and forwarded to reseller who does all handling
> includung shipping)
> * Availability of Inventory is communicated nightly by the Product Supplier;
> this is not figures of QoH but rather an info of type: {we have it; we won't
> have it any more; will be available as of date}
>
> I am currently slightly confused about the Product and Inventory data model
> and how I should set flags on Product:
> * Is it enough to Create an InventoryItem per product and set the 'statusId'
> to a proper value? A nightly job would then check the status and change it?
> How can I -- in this aproach -- reflect projected "available-again" dates?
> * Is it required to go the InventoryItemDetail path and create a detail for
> each availability-period of a product?
> * How do I handle QoH? Can I just set to value 1 and switch off the
> "requires QoH" flag on the Product? What would I then select as Inventory
> Method?
>
> Thanks for any hint !
> Regards
>
>
> Carsten
>