[slimjim30215]

I'm trying to initiate configuration of G/L codes and would like to get a better understanding of the hierarchy between general ledger keys, key components and key component types.

The client has yet to give me clear requirements as to whether these codes will be allocated based on orders or shipments but I'm going to assume they will be based on orders, and possibly order lines.

Any background on solutioning this hierarchy would be appreciated.

[james_foran]

OK...

From a configuration point of view...

1) First you must create your Key Components.

2) Create you General Ledger Key, which will be made up of one or more key components

3) Create your General Ledger Code. Link it to the appropriate General Ledger Key, then enter the parameters. You can leave a parameter blank, and the GL Code will still be applied.

Note, GL Code must be in same domain as Object you are assigning to.

This should get you started.

Let me know if you have any further questions.

Regards,

James Foran
Toll

[slimjim30215]

Originally Posted by james_foran

OK...

From a configuration point of view...

1) First you must create your Key Components.

2) Create you General Ledger Key, which will be made up of one or more key components

3) Create your General Ledger Code. Link it to the appropriate General Ledger Key, then enter the parameters. You can leave a parameter blank, and the GL Code will still be applied.

Note, GL Code must be in same domain as Object you are assigning to.

This should get you started.

Let me know if you have any further questions.

Regards,

James Foran
Toll

Hi James,

I'm trying to set up my General Ledger Key Components. I believe that I have to set up key components for Involved Party Qualifier, with a qualifier of "Sell-To" since the G/L code to be applied will depend on whether it was sold to a Canadian entity, a U.S. entity, or other (all other international destinations). Since I'm going to have different G/L codes depending on the mode I imagine that I'll need a separate key component for transport mode, right?

[james_foran]

Yes, that's right.

[slimjim30215]

I'm struggling to figure out whether an Order or Shipment G/L Key will meet my needs at my current client.

Here are some points to consider:

1 - Need three key components, will need to key off of shipment mode, customer "market" (which is either USA, CAN or INTL, and represents which market sold the order...and this can be a different market than where the order is ultimately delivered), and accessorial code
2 - Shipment mode is tied to the shipment, although a G/L key component can be either order or shipment based
3 - Accessorial is tied to the shipment, and it appears a G/L key component can only be shipment based.
4 - "Market" is order based, and I believe this can be addressed by the ORDEROWNER involved party.

So my challenge seems to be (in my opinion) how do I create a single G/L key that takes into account these three characteristics? It seems that the characteristics that need to be addressed are either order or shipment based, but since I can only have one key, and I need to decide if the key is either order or shipment based, I can't seem to get all three key components to fit into only an order key, or only a shipment key.

Am I missing something here? Any solution tips would be GREATLY appreciated.

[AlejandroBarba]

Hi Slimjim

If I understand correctly you need 3 components: Market, Mode and Accessorial. I agree with you about using Involved Party for the Market. You can use Shipment Mode for Mode. So it is basically, the Accessorial part that would force you to use a Shipment component. In OTM 5.5, the component for that is Accessorial Code.

Hope this helps,

Alejandro B.