FW: SC Update Part WareHouse Primary Bin

Yahoo Archive
1
Well that's what you're going to get. You could write a small
program in C#/VB.Net to parse the files and create a summary. Or use
Tasks - that's what they're there for, although nothing in SC is going
to directly just give you a single file with a list of just the items
you're interested in.



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charlie Wilson
Sent: Thursday, January 29, 2009 4:46 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] FW: SC Update Part WareHouse Primary Bin



Well I'm feeding it a list of part numbers that is about 2000 parts long
for
all I know all 2000 part numbers is not in our system. I do not want
2000
separate files each containing a part number instead I want 1 file that
contains all 2000 bad part numbers.

XML is correct if you tell it to put the XLS ending on the end of the
file
excel will open the file even if it really is xml format.

~Charlie



.


<http://geo.yahoo.com/serv?s=97359714/grpId=20369/grpspId=1705007181/msg
Id=73650/stime=1233265581/nc1=3848586/nc2=3848640/nc3=5579911>




[Non-text portions of this message have been removed]
2
I'm attempting to use SC to set a series of parts in a specific Plant to all
use the same warehouse and have the same primary bin.



I'm trying to get my Conversion set correctly.



I have a Excel file that contains the Part number that needs to be changed.



I need to account for parts that are assigned to this plant that may not
have a ware house assigned to them.



I then have Process Variables set that contain the CompanyCode, Plant Code,
Warehouse Code, and Bin code.



I'm using the partservice.updaterequest as the method I'm trying to convert
to but I can't seem to figure out where all I need to link in the incoming
into the outgoing to get the conversion to work correctly.



Any pointer?





~Charlie



[Non-text portions of this message have been removed]
3
You'll need to set CompanyID at the top.



Generally I find for Part I have to always set
PartDataset/Part/Company, PartNum and PartDescription regardless of what
else I'm doing, so I generally take the PartID as input, do a
Part.GetByID, and use PartID and PartDescription from the returned Part.



In PartDataset/PartPlant, set Company, PartNum, Plant, and PrimWhse.



In PartDataset/PartWhse you'll need to set Company again, along with
PartNum, WarehouseCode, Plant, and PrimBinNum.



I think that would work.



YMMV.



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charlie Wilson
Sent: Thursday, January 29, 2009 1:14 PM
To: vantage@yahoogroups.com
Subject: [Vantage] FW: SC Update Part WareHouse Primary Bin





I'm attempting to use SC to set a series of parts in a specific Plant to
all
use the same warehouse and have the same primary bin.

I'm trying to get my Conversion set correctly.

I have a Excel file that contains the Part number that needs to be
changed.

I need to account for parts that are assigned to this plant that may not
have a ware house assigned to them.

I then have Process Variables set that contain the CompanyCode, Plant
Code,
Warehouse Code, and Bin code.

I'm using the partservice.updaterequest as the method I'm trying to
convert
to but I can't seem to figure out where all I need to link in the
incoming
into the outgoing to get the conversion to work correctly.

Any pointer?

~Charlie

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





[Non-text portions of this message have been removed]
4
Thank you very much!



I have a piece that kicks out bad part numbers. When ever it finds a bad one
it kicks out a xls file. Is there a way to make it append to an existing
file instead of overwriting each time?


~Charlie
________________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Brian W. Spolarich
Sent: Thursday, January 29, 2009 1:32 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] FW: SC Update Part WareHouse Primary Bin

You'll need to set CompanyID at the top.

Generally I find for Part I have to always set
PartDataset/Part/Company, PartNum and PartDescription regardless of what
else I'm doing, so I generally take the PartID as input, do a
Part.GetByID, and use PartID and PartDescription from the returned Part.

In PartDataset/PartPlant, set Company, PartNum, Plant, and PrimWhse.

In PartDataset/PartWhse you'll need to set Company again, along with
PartNum, WarehouseCode, Plant, and PrimBinNum.

I think that would work.

YMMV.

-bws

--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charlie Wilson
Sent: Thursday, January 29, 2009 1:14 PM
To: vantage@yahoogroups.com
Subject: [Vantage] FW: SC Update Part WareHouse Primary Bin

I'm attempting to use SC to set a series of parts in a specific Plant to
all
use the same warehouse and have the same primary bin.

I'm trying to get my Conversion set correctly.

I have a Excel file that contains the Part number that needs to be
changed.

I need to account for parts that are assigned to this plant that may not
have a ware house assigned to them.

I then have Process Variables set that contain the CompanyCode, Plant
Code,
Warehouse Code, and Bin code.

I'm using the partservice.updaterequest as the method I'm trying to
convert
to but I can't seem to figure out where all I need to link in the
incoming
into the outgoing to get the conversion to work correctly.

Any pointer?

~Charlie

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

[Non-text portions of this message have been removed]
5
I'm not quite sure what you mean here.

I *think* you mean to say that your workflow posts to an output
channel with an XML file (not xls) every time it finds a bad part
number, and the problem you have is that it overwrites the same file
since you've configured your output channel with a static filename.

The solution to that is to set the mask on the output channel
communication properties to %GUID%.xml. That will generate a GUID for
each XML file.

Alternatively you could have your "invalid part check" task just
create a Service Connect task instead. All you would have to do is
create a task item on your workflow palette and give it a name (e.g.
"Invalid Part"). The XSD schema for the input would presumably be
GetPartByIDResponse, as your workflow would presumably look like this:

[Part Lookup Conversion] -> [Web Method - GetPartByID()] -> [Choice:
Part Exists?] -> <no> -> [Create Task]

The Choice activity on the workflow passes the XML document through
unchanged, so you'll get attached to your task the output of the Web
Method, which will tell you which PartID was bad.

You can interact with those tasks either in Service Connect admin
console (under Tasks), or via the TaskManager web interface, at
http://scshost/TaskManager/. You'll logon with a valid Service Connect
account (e.g. "admin").

-bws

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charlie Wilson
Sent: Thursday, January 29, 2009 3:45 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] FW: SC Update Part WareHouse Primary Bin

Thank you very much!

I have a piece that kicks out bad part numbers. When ever it finds a bad
one
it kicks out a xls file. Is there a way to make it append to an existing
file instead of overwriting each time?
6
Well IÂ’m feeding it a list of part numbers that is about 2000 parts long for
all I know all 2000 part numbers is not in our system. I do not want 2000
separate files each containing a part number instead I want 1 file that
contains all 2000 bad part numbers.

XML is correct if you tell it to put the XLS ending on the end of the file
excel will open the file even if it really is xml format.

~Charlie
________________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Brian W. Spolarich
Sent: Thursday, January 29, 2009 4:10 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] FW: SC Update Part WareHouse Primary Bin

I'm not quite sure what you mean here.

I *think* you mean to say that your workflow posts to an output
channel with an XML file (not xls) every time it finds a bad part
number, and the problem you have is that it overwrites the same file
since you've configured your output channel with a static filename.

The solution to that is to set the mask on the output channel
communication properties to %GUID%.xml. That will generate a GUID for
each XML file.

Alternatively you could have your "invalid part check" task just
create a Service Connect task instead. All you would have to do is
create a task item on your workflow palette and give it a name (e.g.
"Invalid Part"). The XSD schema for the input would presumably be
GetPartByIDResponse, as your workflow would presumably look like this:

[Part Lookup Conversion] -> [Web Method - GetPartByID()] -> [Choice:
Part Exists?] -> <no> -> [Create Task]

The Choice activity on the workflow passes the XML document through
unchanged, so you'll get attached to your task the output of the Web
Method, which will tell you which PartID was bad.

You can interact with those tasks either in Service Connect admin
console (under Tasks), or via the TaskManager web interface, at
http://scshost/TaskManager/. You'll logon with a valid Service Connect
account (e.g. "admin").

-bws

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charlie Wilson
Sent: Thursday, January 29, 2009 3:45 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] FW: SC Update Part WareHouse Primary Bin

Thank you very much!

I have a piece that kicks out bad part numbers. When ever it finds a bad
one
it kicks out a xls file. Is there a way to make it append to an existing
file instead of overwriting each time?
7
Well IÂ’m feeding it a list of part numbers that is about 2000 parts long for
all I know all 2000 part numbers is not in our system. I do not want 2000
separate files each containing a part number instead I want 1 file that
contains all 2000 bad part numbers.

XML is correct if you tell it to put the XLS ending on the end of the file
excel will open the file even if it really is xml format.

~Charlie


~Charlie
________________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Brian W. Spolarich
Sent: Thursday, January 29, 2009 4:10 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] FW: SC Update Part WareHouse Primary Bin

I'm not quite sure what you mean here.

I *think* you mean to say that your workflow posts to an output
channel with an XML file (not xls) every time it finds a bad part
number, and the problem you have is that it overwrites the same file
since you've configured your output channel with a static filename.

The solution to that is to set the mask on the output channel
communication properties to %GUID%.xml. That will generate a GUID for
each XML file.

Alternatively you could have your "invalid part check" task just
create a Service Connect task instead. All you would have to do is
create a task item on your workflow palette and give it a name (e.g.
"Invalid Part"). The XSD schema for the input would presumably be
GetPartByIDResponse, as your workflow would presumably look like this:

[Part Lookup Conversion] -> [Web Method - GetPartByID()] -> [Choice:
Part Exists?] -> <no> -> [Create Task]

The Choice activity on the workflow passes the XML document through
unchanged, so you'll get attached to your task the output of the Web
Method, which will tell you which PartID was bad.

You can interact with those tasks either in Service Connect admin
console (under Tasks), or via the TaskManager web interface, at
http://scshost/TaskManager/. You'll logon with a valid Service Connect
account (e.g. "admin").

-bws

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Charlie Wilson
Sent: Thursday, January 29, 2009 3:45 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] FW: SC Update Part WareHouse Primary Bin

Thank you very much!

I have a piece that kicks out bad part numbers. When ever it finds a bad
one
it kicks out a xls file. Is there a way to make it append to an existing
file instead of overwriting each time?