bad contract number

[former_member391220]

Hi Folks:

I came across a strange situation at a client today (at least I haven't seen it before).  In the contract data load: the extractor works fine and the data gets to the PSA correctly; however, the concantenated contract key (0XSARAGRNUM) is showing up in the following format <contract #> _ <SID> _ _ <line item #>  (instead of the normal _ <SID> _ <contract #> _ <line item #>).

My solution is to just create a template for contracts, but I wanted to check with the group to see if anyone has seen this before; whether or not it is a know bug; etc.

Thanks,

Mark

[former_member391220]

The new template didn't make any difference; once I set it back to default template it started to work again.

I'm closing this one out.

[former_member391220]

oops, I forgot to mention that in addition to the odd concatenation order the last 2 characters in the line item are truncated so if you have 99 line items or less, only one is sent to the inbound DSO.  And then the contract key generation in the PO read is done correctly which means no POs or Invoices will link to a contract.