Does anyone know how to determine what can be automatically generated in the "reference" field. This is applicable to payables, receivables and general ledger items.

Phil

The object or intentions of external references in tables is to do at least two things.

a) To prove that the field value that you provided exists in the referred to table, ensuring that the field is known (validation). For example, a reference to warehouse table (cwar).

The reference has to be to a unique key in the external table. But your reference may be part of a combined key, where the individual items may be duplicates, but the combination is unique, and the referred to table may accept the combined field for synchronization.

b) The second reason for a reference field is that information that is not pertenant to the initial intent can be stored im this referred to table . For Cwar, it's contains it's description and some other properties.

I do hope that I have reponded to your question appropriately. If I answered the wrong question (perhaps I didn't understand your question), send me an email.

Regards

Leslie

If you are referring to the field on the Finalised Transactions table in Finance (tfgld106.refr) it appears on this table in a variety of ways.

Sessions Mainatain Sales Invoices tfacr1110s000 and Maintain Bank Transactions tfcmg2100s000 have a reference field in the session so the user can input it manually. It is then stored in tables tfcmg204.refr and tfacr200.refr respectively before being transferred to tfgld106.

In other areas of our system it is blank for Supply Chain Sales Invoices generated by Print Sales Invoices tdsls4404m000 and for our Purchase Invoices entered by tfacp1110s000 the refr field is set to the name of the supplier but I can't quite work out why.

We are running 4c3.

Regards
Neal Matthews
Intier Automotive

Well,

The reference field you were referring to is the one in finance, and from a business situation, it is a business reference code that you may put in.

The one I was referring to was that as defined in the definition of Baan tables.

I was right, wasn't I, I answered the right question about the wrong "referrence"!

Yes, you are right - but thanks for trying.

In Baan 5c, the ACP200 field for P.O. Number is not populated (from Baan support - yes this is really true), so I was wondering if we could automatically populate this value in the reference field.
I was hoping there was some way to configure this.
In the G/L you get quite a good reference generated for integration transactions - I don't know if this is changeable either.

Phil,

I think the problem Baan faced with populating PO # in ACP200 is that a supplier invoice can legitimately be matched, approved, paid against more than one Purchase Order.

Scott Johnson

another reason why it probably shouldn't have the PO number automatically populate is that this table also contains records for cost invoices, credits etc. that are not related to PO's, so this is more of a user defined field, which is probably better so that you can enter a reference as needed. For example, if it is a credit invoice, perhaps you want to enter in a reference such as "credit for returned goods" or something.

That's not quite it.
I agree that the reference field should be free-form, but that doesn't mean you shouldn't be able to default an entry. I was wondering how to default something (looks like I can't).
In terms of things like P.O. number and Project, the frustrating thing is that Baan provides the fields in the tables (ACR200, ACP200) and also allows you to choose them for statements - but they don't work.
I also understand the reasons that might give you more than one P.O. per invoice etc - the logic should be to populate the field if there is only one, otherwise it is "various".