[leo_glog]

Hi Anita,

what exactly is the requirement?

do u want to setup Gl againSt order or shipment?

I guess its on shipment level buy site?

Basic requirement is the code must be unique. So in your case you need a buy side SHIPMENT GL LOOKUP KEY
with different key components. Lets work it out:

Simplest would be a code based on cost type A (ccessorial) or B (ase)

the system would allocate for A: zzzz
and for base cost : xxxxx, yyyyyy

So it's not unique. We need add another key component to dsitinguish between out and inbound

Can we use transport mode? i dont think so. It would suprise me if you design the solution with an out and inbound specific modes like TL OUT, TL IN.

Lets think about shipment_location as key component.
If you set it up you will be ask for D (estination) or S(ource) . We nned both

So now we defined 3 key components

cost type
source_location
dest_location

Assign them to the SHIPMENT GL LOOKUP KEY.

now we can create the gl codes

1) xxxxx (scenario we receiving goods from nyc or washington to philly)
cost type B, source loc is blanc, dest location is PHL

2) yyyyy
cost type B, source loc PHL, dest location is blanc

3)
cost type A, source loc blanc, dest blanc

..................
If you have a more complex network with a bunch of inbound location and even more outbound location or you shipping good from to US i would use
the key component involved_party instead of shipment location.

you setting up an agent which inserts an involved party qualifier maybe GLANNEX
with value of INBOUND and OUTBOUND, (if source country us....etc)

now your SHIPMENT GL LOOKUP KEY contains 2 key components
1) cost type
2) involved party..

create gl code..

xxxx
cost type B,
involved party value: INBOUND

yyyyy
cost type B,
involved party value: OTBOUND

zzzzz
cost type A,
involved party value blanc

Let me know if it works..

design is based on 5.0

Jens