Transaction references

Each type of transaction, for example, a sales order or a movement order, needs a unique reference number, which must be set up before the transaction can be processed.

You can define the layout and content of transaction references depending on your requirements. For example, you may need part of the reference number to include the Operator ID, date or a specific number.

Once you have created a transaction reference, you can include it in the document format where it is to be used, so that the document uses the correct formats. For example, the document format for a sales order may include the transaction reference for the sales order. Default references are held in Purchase Business Setup (PBS_, Sales Business Setup (SBS) and Inventory Business Setup (IBS). The defaults are used if there are none defined on the document format.

Transaction references can contain up to four parts which are each defined separately. It is not mandatory that all four parts are used.

You can use analysis to change the contents of any or all parts, depending on the characteristics of a transaction. For example, a different prefix for each warehouse. If you use a code which exists on an order line, the code on the first line processed is used.

You can use transaction references in conjunction with number streams, which are used to define the next available number in a transaction reference sequence.

Note: You should not use the same number stream for two different transaction reference records, as this causes downstream problems, and as a result you must use a prefix to differentiate the transaction references.