> 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/stock-movements/functions-and-features.md). # Functions and Features {% hint style="info" %} **Note** This Functions and Features page contains differing sections of useful, additional information and topics related to each app which may be of a functional or technical nature.​ {% endhint %} ## Source / destination screen flow and verification fields Up to and including release 5.8.0 the follow logic controls whether the source and/or destination confirmation screens are displayed in the app transactions. Firstly the system checks whether two-step confirmation (LTAP-KGVNQ) is valid in the transfer order item. If it is then the source confirmation screen will be displayed unless the picking confirmation (LTAP-PVQUI) has been already made, in which case it will go straight to the destination confirmation screen. The source confirmation screen is then displayed unless there are no source verification fields required (*see below for how that is determined*) and both the "Skip source screen" option (T313A-DISPL) is selected in the profile and the source storage type is not relevant for confirmation removal (T331-QUAUS). However if "Zero Stock Check" is active for the transfer order item (LTAP-KZNKO) and the picking confirmation (LTAP-PVQUI) has not been completed then the source confirmation screen, regardless of the above, is displayed with the "Zero Stock Check" popup over the top. In order to work out the source confirmation verification fields required, the system reads the verification profile assigned (from table T313B) for the particular storage types and movement type combination (from table T313A). It then removes the material and the bin verification requirements respectively if either of those were used in the initial selection at the start of the transaction. The assumption is that if these were used in the initial selection of the data then there is no need to rescan that data on the source screen. Note however, that the same logic does not apply to the destination confirmation screen even if values are entered in the selection. Once on the source confirmation screen, the fields chosen to be displayed for verification will be controlled by i) the appropriate "\_VERIF" field being defined in the AMD with the standard 510 app field class; ii) whether the fields have been selected for verification in an appropriate verification profile determined by the standard SAP WM configuration in tables T313A and T313B; and iii) whether the fields for verification were in fact already entered in the initial selection which, if so, would mean that those fields are removed for verification. {% hint style="info" %} **Note** From release 5.9.0 onwards, the screen flow logic will be changed slightly to better adhere to SAP's configuration and RF mobile philosophy. This involves respecting the "Skip source screen" option (T313A-DISPL) regardless of whether the profile T313B-PROFI has source fields defined. {% endhint %} For release 5.9.0 onwards, the logic will be as follows: The system checks whether two-step confirmation (LTAP-KGVNQ) is valid in the transfer order item. If it is then the source confirmation screen will be displayed, regardless of any verification profile configuration, unless the picking confirmation (LTAP-PVQUI) has been already made, in which case it will go to the destination confirmation screen. If "Zero Stock Check" is active for the transfer order item (LTAP-KZNKO) and the pickling confirmation (LTAP-PVQUI) has not been completed then the source confirmation screen is displayed with the "Zero Stock Check" popup over the top, regardless of any verification profile configuration. If an appropriate verification profile is selected for the storage types and movement type combination and either the "Skip source screen" is set or there are no required verification fields determined, then the transaction will display the destination confirmation screen and "skip" the source confirmation screen. As before the system works which fields are relevant for source confirmation verification by reading the verification profile assigned (T313B) and removing the source material, source batch or source bin verification requirements respectively if any of those were used in the initial selection at the start of the transaction. The assumption is that if these were used in the initial selection of the data then there is no need to rescan that data on the source confirmation screen. Note however, that the same logic does not apply to the destination confirmation screen even if values are entered in the selection. If no suitable verification profile is found for the storage types and movement type combination then the system uses a more simplistic logic of checking whether the source storage type required confirmation removal (T331-QUAUS). If confirmation removal is required then the source confirmation screen will be displayed otherwise the destination confirmation screen. If the material is not batch managed or there is no batch in the transfer order item then the batch verification will be ignored / suppressed. ## Two-step confirmation From release 5.9.0 onwards, it will be possible to confirm with a difference on BOTH the source confirmation screen and the destination confirmation screen if two-step confirmation (LTAP-KGVNQ) is valid in the transfer order item AND the appropriate source and destination quantity verification fields are active in the AMD for each screen. The quantity that is being verified against on the destination screen is the new quantity that was confirmed from the source confirmation screen. The exception to this feature is for removal from bulk storage types where a separate transfer confirmation is not supported in SAP and so this is not supported in PreBilt. ## Create transfer order: automatic destination storage type determination from bin When creating a transfer order in PreBilt if you want the system to automatically select the correct destination storage type or propose in a popup the appropriate destination storage types, when you enter the destination storage bin then you **must** remove (*not hide*) the destination storage type field from the AMD of both the SELECT\_OPTS screen and the INPUT\_QUANT\_DEST\_DETAIL or INPUT\_SU\_BIN\_DETAIL screens as appropriate.