[satya_m]

Hi Ian,

I haven't worked on BN Generator anytime,but a quick look at the code, this is what i found out. Please correct me if i am wrong.

1) Why are shipment IDs not generating in exact running sequence?

There is a propery in the glog.base.properties - 'glog.server.bngenerator.oracleSequence' . While generating the xid, the BNEngine looks for this property, and if its not definied, it generates the xid using the BNSequence.

I am not exactly sure why an exact running sequence is not getting generated, but when a shipment xid is generated, the BNEngine makes an entry into the BN_SEQUENCE talbe, updating the currValue. So when a shipment is getting generated next time, it picks up the currValue from this table for this Shipment BN Rule and generates a new sequence number for the xid.

2) Is the Shipment ID BN generator shared across all shipment object types (Buy/Sell/Group/Secondary Charge)

For both 'Buy' and 'Sell' its the same Shipment ID BN generator.

Group has a seperate BN GEnerator. Not sure about Secondary Charge.

3) How can we have a different BN generator for Buy and Sell shipments?

Not sure if this is possible. Its the same set of classes used to generate the shipment,both buy and sell. Its the shipmentBean that gets invoked and this bean generates the PK irrespective of the perspective. Even if you see the BN Rule, there is only one rule defined for Shipment. No seperate rules for Buy and Sell.

Hope this info helps.

Thanks,
Satya.