Multiple G/L Class Codes for an Item

[Michelle D.]

We have the following requirement:

Item 123456 in branch/plant A needs to have G/L Class Code XXXX (for actual
costs) AND G/L Class Code IN30 (for standard costs).

This requirement is the result of items that are in development and then
need to be transitioned to production. So, for a period of time (sometimes
years), the same item will be costed two different ways (actual cost and
standard cost) depending on the work order.

Right now, the only solution we see is to create another branch/plant.
However, we already have 3 different branch/plants and do not want to setup
and maintain yet another one.

Does anyone have any other ideas?

Thank you,
Michelle Dulay
ERP Coordinator
BFGoodrich Aerospace
Chandler Evans Control Systems
email: [email protected]

OneWorld B7322 with the MFG Mini-Cum, coexistent with World A7.3
AS400 V4R3 Enterprise Server
Windows NT SQL V6.5 Deployment Server
SynQuest V5.07.02
Oracle
NT Logic - between AS400 (OneWorld) and HP9000 (SynQuest)



OneWorld B7322, MFG Mini-Cum, coexistent World A7.3
AS400 V4R3 ES
WinNT SQL6.5 DS

 

[Geeze]

The G/L class code pulls from the Location level, not the branch level, so
all you have to do is set up two distinct locations and have separate G/L
classes for each one.

----- Original Message -----
From: "mdulay" <[email protected]>
To: <[email protected]>
Sent: Thursday, January 11, 2001 7:53 AM
Subject: Multiple G/L Class Codes for an Item ~~0:3738


> We have the following requirement:
>
> Item 123456 in branch/plant A needs to have G/L Class Code XXXX (for
actual
> costs) AND G/L Class Code IN30 (for standard costs).
>
> This requirement is the result of items that are in development and then
> need to be transitioned to production. So, for a period of time
(sometimes
> years), the same item will be costed two different ways (actual cost and
> standard cost) depending on the work order.
>
> Right now, the only solution we see is to create another branch/plant.
> However, we already have 3 different branch/plants and do not want to
setup
> and maintain yet another one.
>
> Does anyone have any other ideas?
>
> Thank you,
> Michelle Dulay
> ERP Coordinator
> BFGoodrich Aerospace
> Chandler Evans Control Systems
> email: [email protected]
>
> OneWorld B7322 with the MFG Mini-Cum, coexistent with World A7.3
> AS400 V4R3 Enterprise Server
> Windows NT SQL V6.5 Deployment Server
> SynQuest V5.07.02
> Oracle
> NT Logic - between AS400 (OneWorld) and HP9000 (SynQuest)
>
>
>
> OneWorld B7322, MFG Mini-Cum, coexistent World A7.3
> AS400 V4R3 ES
> WinNT SQL6.5 DS
> --------------------------
> To view this thread, visit the JDEList forum at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OWDEV&Numb
er=3738
> *************************************************************
> This is the JDEList One World / XE Developers Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> *************************************************************


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

 

[pcaenaro]

The GL Class (the one retrieved by Sales Order Processing for example)is
stored in the Item Location. You could create a new location in your
existing Branches and setup the GL at this level

Hope this helps

Philippe
----- Original Message -----
From: "mdulay" <[email protected]>
To: <[email protected]>
Sent: Thursday, January 11, 2001 2:53 PM
Subject: Multiple G/L Class Codes for an Item ~~0:3738


> We have the following requirement:
>
> Item 123456 in branch/plant A needs to have G/L Class Code XXXX (for
actual
> costs) AND G/L Class Code IN30 (for standard costs).
>
> This requirement is the result of items that are in development and then
> need to be transitioned to production. So, for a period of time
(sometimes
> years), the same item will be costed two different ways (actual cost and
> standard cost) depending on the work order.
>
> Right now, the only solution we see is to create another branch/plant.
> However, we already have 3 different branch/plants and do not want to
setup
> and maintain yet another one.
>
> Does anyone have any other ideas?
>
> Thank you,
> Michelle Dulay
> ERP Coordinator
> BFGoodrich Aerospace
> Chandler Evans Control Systems
> email: [email protected]
>
> OneWorld B7322 with the MFG Mini-Cum, coexistent with World A7.3
> AS400 V4R3 Enterprise Server
> Windows NT SQL V6.5 Deployment Server
> SynQuest V5.07.02
> Oracle
> NT Logic - between AS400 (OneWorld) and HP9000 (SynQuest)
>
>
>
> OneWorld B7322, MFG Mini-Cum, coexistent World A7.3
> AS400 V4R3 ES
> WinNT SQL6.5 DS
> --------------------------
> To view this thread, visit the JDEList forum at:
>
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OWDEV&Numb
er=3738
> *************************************************************
> This is the JDEList One World / XE Developers Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> *************************************************************



One World B733 Oracle 8.1 RS6000