Unique warehouse ID for Multi-plant?

Thanks for the feedback! I’m glad I found this User’s Group!!!

☺





Ron Brown

Process Manager

Tank Connection

3609 N. 16th St.

Parsons, KS 67357

Office: 620-423-3010 ext. 158

Email: rbrown@...<mailto:rbrown@...>



[cid:tcaffiliates_2008536d3f]<http://www.tankconnection.com>



[cid:linkedine5430a] <http://www.linkedin.com/company/tank-connection-affiliate-group> [cid:facebookc9e212] <http://facebook.com/tankconnection> [cid:twitter492aec] <http://twitter.com/TankConnection> [cid:youtube517e74] <http://youtube.com/user/TankConnection>

________________________________

NOTICE: This email and any attachments are considered confidential and intended for the addressee only. If you have received this email in error, please notify the sender as soon as possible and delete this email. If you are not the intended addressee, any dissemination, distribution or copying of this message is strictly prohibited by law.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Miguel Santillan
Sent: Thursday, February 13, 2014 5:47 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Unique warehouse ID for Multi-plant?


Same with everything else. Unique Ops, Resources.

We use

Kit
C-Kit
D-KIT
N-KIT
S-KIT

Each letter indication the location of the plant.

Miguel A. Santillan
Compass Manufacturing Systems
510-661-6666 Office

From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of Neil Buckman
Sent: Thursday, February 13, 2014 3:44 PM
To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
Subject: RE: [Vantage] Unique warehouse ID for Multi-plant?



Warehouses are held in one table, regardless of plant, and so must have unique ID's


Neil Buckman
Information Technology

[Gibson Shopfitters]

DH Gibson Pty Ltd | 205-231 Fairfield Rd | YENNORA NSW 2161
Office 8724 4600 | Direct 8724 4618 | Fax 8724 4604 | Mobile 0413 125 994
nbuckman@...<mailto:nbuckman@...<mailto:nbuckman@...%3cmailto:nbuckman@...>> | www.gibsonshopfitters.com.au<http://www.gibsonshopfitters.com.au> <http://www.gibsonshopfitters.com.au/>




From: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com> [mailto:vantage@yahoogroups.com] On Behalf Of tank.connection@...<mailto:tank.connection@...>
Sent: Friday, 14 February 2014 10:30 AM
To: vantage@yahoogroups.com<mailto:vantage@yahoogroups.com>
Subject: [Vantage] Unique warehouse ID for Multi-plant?



We are in the early stages of implementation. We originally thought we would go single plant / multi-warehouse. However, as we are getting deeper into the software and based upon feedback from the EUG community, we are testing the multi-plant approach. As we are setting up the warehouses, resource groups, and operations for the new plants in our Test Database, we are getting messages indicating the warehouses, resource groups, etc. must have a unique identifier. Did we corrupt our test data base by first setting up as a single plant? We were presuming we could have a warehouse identified as MAIN in Plant 1 as well as a warehouse identified as MAIN in Plant 2. The messages received indicate that isn't possible. Is that correct or are we missing something? Before we start setting up MAIN1, MAIN2, etc. for warehouses, resource groups, operations, etc. I was hoping I could get some real world feedback.



Thanks in advance for any feedback!



Notice:This e-mail and any attachments are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient please advise the sender by return e-mail and delete the message and any attachments. Any use, interference with, disclosure or copying of this message or any attachments is unauthorised and prohibited. The sender does not warrant that the information is free of a virus or any other defect or error, and any views expressed herein, unless specifically indicated otherwise, are those of the individual sender.

The DH Gibson Group of Companies - http://www.gibsonshopfitters.com.au

P Please consider our shared environment before printing this communication.


[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]

We are in the early stages of implementation.  We originally thought we would go single plant / multi-warehouse.  However, as we are getting deeper into the software and based upon feedback from the EUG community, we are testing the multi-plant approach.  As we are setting up the warehouses, resource groups, and operations for the new plants in our Test Database, we are getting messages indicating the warehouses, resource groups, etc. must have a unique identifier.  Did we corrupt our test data base by first setting up as a single plant?  We were presuming we could have a warehouse identified as MAIN in Plant 1 as well as a warehouse identified as MAIN in Plant 2.  The messages received indicate that isn't possible.  Is that correct or are we missing something?  Before we start setting up MAIN1, MAIN2, etc. for warehouses, resource groups, operations,  etc. I was hoping I could get some real world feedback.


Thanks in advance for any feedback!

Warehouses are held in one table, regardless of plant, and so must have unique ID's


Neil Buckman
Information Technology

[Gibson Shopfitters]

DH Gibson Pty Ltd | 205-231 Fairfield Rd | YENNORA NSW 2161
Office 8724 4600 | Direct 8724 4618 | Fax 8724 4604 | Mobile 0413 125 994
nbuckman@...<mailto:nbuckman@...> | www.gibsonshopfitters.com.au <http://www.gibsonshopfitters.com.au/>




From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of tank.connection@...
Sent: Friday, 14 February 2014 10:30 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Unique warehouse ID for Multi-plant?



We are in the early stages of implementation. We originally thought we would go single plant / multi-warehouse. However, as we are getting deeper into the software and based upon feedback from the EUG community, we are testing the multi-plant approach. As we are setting up the warehouses, resource groups, and operations for the new plants in our Test Database, we are getting messages indicating the warehouses, resource groups, etc. must have a unique identifier. Did we corrupt our test data base by first setting up as a single plant? We were presuming we could have a warehouse identified as MAIN in Plant 1 as well as a warehouse identified as MAIN in Plant 2. The messages received indicate that isn't possible. Is that correct or are we missing something? Before we start setting up MAIN1, MAIN2, etc. for warehouses, resource groups, operations, etc. I was hoping I could get some real world feedback.



Thanks in advance for any feedback!



Notice:This e-mail and any attachments are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient please advise the sender by return e-mail and delete the message and any attachments. Any use, interference with, disclosure or copying of this message or any attachments is unauthorised and prohibited. The sender does not warrant that the information is free of a virus or any other defect or error, and any views expressed herein, unless specifically indicated otherwise, are those of the individual sender.

The DH Gibson Group of Companies - http://www.gibsonshopfitters.com.au

P Please consider our shared environment before printing this communication.



[Non-text portions of this message have been removed]

Same with everything else. Unique Ops, Resources.

 

We use

 

Kit

C-Kit

D-KIT

N-KIT

S-KIT

 

Each letter indication the location of the plant.

 

Miguel A. Santillan

Compass Manufacturing Systems

510-661-6666  Office

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Neil Buckman
Sent: Thursday, February 13, 2014 3:44 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Unique warehouse ID for Multi-plant?

 

 


Warehouses are held in one table, regardless of plant, and so must have unique ID's


Neil Buckman
Information Technology

[Gibson Shopfitters]

DH Gibson Pty Ltd | 205-231 Fairfield Rd | YENNORA NSW 2161
Office 8724 4600 | Direct 8724 4618 | Fax 8724 4604 | Mobile 0413 125 994
nbuckman@...<mailto:nbuckman@...> | www.gibsonshopfitters.com.au <http://www.gibsonshopfitters.com.au/>




From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of tank.connection@...
Sent: Friday, 14 February 2014 10:30 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Unique warehouse ID for Multi-plant?



We are in the early stages of implementation. We originally thought we would go single plant / multi-warehouse. However, as we are getting deeper into the software and based upon feedback from the EUG community, we are testing the multi-plant approach. As we are setting up the warehouses, resource groups, and operations for the new plants in our Test Database, we are getting messages indicating the warehouses, resource groups, etc. must have a unique identifier. Did we corrupt our test data base by first setting up as a single plant? We were presuming we could have a warehouse identified as MAIN in Plant 1 as well as a warehouse identified as MAIN in Plant 2. The messages received indicate that isn't possible. Is that correct or are we missing something? Before we start setting up MAIN1, MAIN2, etc. for warehouses, resource groups, operations, etc. I was hoping I could get some real world feedback.



Thanks in advance for any feedback!



Notice:This e-mail and any attachments are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient please advise the sender by return e-mail and delete the message and any attachments. Any use, interference with, disclosure or copying of this message or any attachments is unauthorised and prohibited. The sender does not warrant that the information is free of a virus or any other defect or error, and any views expressed herein, unless specifically indicated otherwise, are those of the individual sender.

The DH Gibson Group of Companies - http://www.gibsonshopfitters.com.au

P Please consider our shared environment before printing this communication.


[Non-text portions of this message have been removed]