> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-for-im-wm-strm/applications/serial-numbers/configuration.md).

# Configuration

{% hint style="info" %}
**Note**

This configuration guide refers to PreBilt transactions beginning '*PB2\_*' and details the standard process without additional features or enhancements. You should [copy these transactions](/prebilt-for-im-wm-strm/configuration-guide/transaction-codes.md#create-a-transaction) with a different prefix to maintain a backup and protect the originals.

The guide displays the standard PreBilt screens and gives details of the structures in which the on screen fields can be found. Fields within these structures can be used to customise and enhance the screen. For instructions on how to use structures to find fields, please see [Available data structures](/prebilt-for-im-wm-strm/app-master-data/screen-framework/features/available-data-structures.md). For instructions on how to maintain the configuration elements in AMD, please see [General configuration elements](/prebilt-for-im-wm-strm/app-master-data/general-configuration-elements.md).
{% endhint %}

This configuration guide refers to transaction *PB2\_SERIAL\_NUMBERS*.

## Selection options

<table><thead><tr><th width="316.444580078125">Configuration element</th><th>Available structures</th></tr></thead><tbody><tr><td>SELECT_OPTS</td><td><p>Generic fields:</p><p>VBELN_VL or DELIVERY or INBOUND or OUTBOUND or LIKP-VBELN - delivery number</p><p>VBELN_VA or ORDER or SO - sales order number</p><p>MAT_DOC or MBLNR - material document number</p><p>DOC_YEAR or MJAHR - material document year</p><p>INSP_LOT or INSPECTION_LOT or PRUEFLOS - inspection lot number</p><p>AUFNR or PP_ORDER - production / process order</p><p>EXIDV or HU or HANDLING_UNIT - handling unit number</p><p>IBLNR or PI_DOC_NO - PI document number</p><p>EBELN or PO_NUMBER - purchase order number</p><p>BANFN or PR_NUMBER - purchase requisition number</p><p>ITEM or POSNR or TAPOS or DELIVERY_ITEM or LIPS-POSNR or EBELP - item number</p><p>MATERIAL or MATNR or LIPS-MATNR - material number</p><p>PLANT or WERKS or LIPS-WERKS - plant</p><p>SLOC or LGORT or LIPS-LGORT - storage location</p><p>SOBKZ - special stock type</p><p>SONUM - special stock number</p><p>EQUI - equipment number</p><p>BATCH or CHARG - batch</p></td></tr><tr><td>SELECT_OPTS_ACTIONS</td><td><p>BACK - back to previous screen.</p><p>CLEAR_INPUT -clear all input fields.</p><p>VAR_CHOOSE – select saved variants.</p><p>VAR_SAVE – save the selection entries as a variant.</p><p>SELECT – proceed to next screen.</p></td></tr></tbody></table>

## Serial numbers list

<table><thead><tr><th width="315.333251953125">Configuration element</th><th>Available structures</th></tr></thead><tbody><tr><td>LIST_SERIAL_NUMBERS</td><td>Primary: /TCTM/IQ09_S (IQ09)<br>Secondary: RSEROB (KEY/KEY_ACT/KEY_SRC), IKPF (IKPF), ISEG (ISEG), LIKP (LIKP), LIPS (LIPS); AFPO (AFPO)</td></tr><tr><td>LIST_SERIAL_NUMBERS_ACTIONS</td><td><p>BACK - back to previous screen.</p><p>CLEAR_LIST -clear all serial number from list.</p><p>CONTINUE – add entered serial number.</p><p>COMPLETE – process the serial number list.</p><p>SELECT – proceed to next screen.</p></td></tr><tr><td>LIST_SERIAL_NUMBERS_HEADER</td><td>Primary: /TCTM/IQ09_S (IQ09)<br>Secondary: RSEROB (KEY/KEY_ACT/KEY_SRC), IKPF (IKPF), ISEG (ISEG), LIKP (LIKP), LIPS (LIPS); AFPO (AFPO), EKKO (EKKO), EKPO (EKPO), /TCTM/MAKT (MAKT), /TCTM/MARA (MARA), /TCTM/MARC (MARC), /TCTM/MARD (MARD), /TCTM/MLGN (MLGN)</td></tr><tr><td>LIST_SERIAL_NUMBERS_HEADER_EX</td><td>n/a</td></tr><tr><td>LIST_SERIAL_NUMBERS_SORT</td><td>Primary: None</td></tr></tbody></table>

## Serial number input

<table><thead><tr><th width="314.22216796875">Configuration element</th><th>Available structures</th></tr></thead><tbody><tr><td>INPUT_SERIAL_NUMBER</td><td>Primary: /TCTM/IQ09_S (IQ09)<br>Secondary: /TCTM/EFHM_S (EFHM), /TCTM/EQBS_S (EQBS),  /TCTM/EQKT_S (EQKT), /TCTM/EQUI_S (EQUI), /TCTM/EQUZ_S (EQUZ), /TCTM/FLEET_S (FLEET), /TCTM/ILOA_S (ILOA)</td></tr><tr><td>INPUT_SERIAL_NUMBER_ACTIONS</td><td>BACK - back to previous screen.</td></tr></tbody></table>

## General configuration elements

<table><thead><tr><th width="273.111083984375">Configuration element</th><th>Available structures</th></tr></thead><tbody><tr><td>FE_APP</td><td>Frontend class to use in running the transaction.<br><br>Reference to the platform specific frontend application that should be used to run the transaction. Included in the App Master Data file supplied for setting up the initial transactions.</td></tr><tr><td>ALLOW_CAPTURE</td><td>Toggle to allow the capture of serial numbers.</td></tr><tr><td>ALLOW_DISPLAY</td><td>Toggle to allow the display of serial numbers.</td></tr><tr><td>APP_TEXTS</td><td>Defines standard app text to be used in screen headers, buttons etc.</td></tr><tr><td>TRANS_INFO</td><td>Information about the transaction.</td></tr></tbody></table>

## SERIAL\_OVERRIDE

The `SERIAL_OVERRIDE` configuration allows PreBilt to override the Serial Number Usage settings defined in the SAP Serial Number Profile for a specific Profile and Procedure combination.

The following values are supported:

<table><thead><tr><th width="118.79998779296875">Value</th><th>Description</th></tr></thead><tbody><tr><td>01</td><td>Serial numbers not required</td></tr><tr><td>02</td><td>Serial numbers optional</td></tr><tr><td>03</td><td>Serial numbers mandatory</td></tr><tr><td>04</td><td>Serial numbers mandatory and must already exist in SAP</td></tr></tbody></table>

When a matching Profile and Procedure combination is found, PreBilt uses the configured override value to determine how serial numbers are handled within the application.

{% hint style="info" %}
**Important:** Serial Override should only be used to make serial number validation more restrictive than the underlying SAP configuration. SAP will continue to enforce its own serialisation requirements during posting. Configuring PreBilt with less restrictive rules than SAP may allow a user to complete a process successfully in PreBilt, but the final SAP posting may fail due to missing serial number information.
{% endhint %}

Typical use cases include making an optional serialisation process mandatory within PreBilt, or requiring entered serial numbers to already exist in SAP before a transaction can be completed.