Stock > Inquiries > Movements > Transactions by date 

Use this function to view the history of movements performed over a given period. This inquiry is single site or multi-site.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

Presentation

Enter your main selection criteria for the inquiry.

Site: only inquire the movements of this particular site. If no site is entered, the inquiry returns the movements of all sites. By default, this field is loaded with the Stock site linked to the user.

Start date / End date: only inquire the movements performed during this particular period. The movements of the day are suggested by default.

Selection date: specify if the movements should be sorted by creation date or by posting date.

Close

 

Fields

The following fields are present on this tab :

Selection

Enter or select the storage site where the selected product is active.

The Selection icon (magnifying glass) only suggests products that are referenced in the products-sites table.

  • Start date (field STRDAT)

Start date used to select the records to be processed.


  • End date (field ENDDAT)

End date used in the selection of the records to be processed.

  • Selection date (field SRTCOD)

Select the classification criteria for the display of the returned lines.

Block number 2

Close

 

Tab Transactions by Date

Presentation

The columns in this table depend on the setup of the chosen screen code.

The table returns by default one line by stock movement for the selected criteria, with the following main information:

*    The movement site

*    The movement lot, sublot, serial number, version numbers (minor and major), quantity and status

*    The lot expiry date, if needed

*    The base transaction of the movement

*    The supporting document number

*    The source document number.  

Close

 

Fields

The following fields are present on this tab :

Grid

 

 

 

  • Description 1 (field ITMDES1)

 

  • Allocation (field IPTDAT)

 

  • Lot (field LOT)

 

  • Sublot (field SLO)

 

  • Major version (field ECCVALMAJ)

 

  • Minor version (field ECCVALMIN)

 

  • Starting serial number (field SERNUM)

 

  • Ending serial number (field SERFIN)

 

  • Quantity (field QTYPCU)

 

 

  • STK quantity (field QTYSTU)

 

 

  • Status (field STA)

 

  • Location (field LOC)

 

 

  • Identifier 1 (field PALNUM)

 

  • Identifier 2 (field CTRNUM)

 

  • Analysis req. (field QLYCTLDEM)

 

  • Movement type (field TRSTYP)

This field indicated the stock movement type performed for the product.
When the movement relates to an action performed on a container, this movement is set to ‘License plate number change’.
To display the type of action (‘License plate number assignment’ or ‘License plate number operations’), click the Actions icon against the line.

  • Movement description (field MVTDES)

 

 

 

  • Entry type (field VCRTYPTXT)

 

  • Entry (field VCRNUM)

 

  • Line no. (field VCRLIN)

 

  • Source document type (field VCRTYPORIT)

 

  • Original document (field VCRNUMORI)

 

  • Source document line (field VCRLINORI)

 

  • Supplier lot (field BPSLOT)

 

  • Expiration (field SHLDAT)

 

  • UBD (field DLUDAT)

The use-by date (UBD) is the target date for issuing a product.
It cannot be modified. 
UBD = Reference expiry date + UBD lead time.

  • Recontrol (field NEWLTIDAT)

La date de recontrôle est associée à un lot en stock. Elle indique une date d'analyse de la marchandise, une fois le délai de péremption atteint.

SEEINFO Warning The new control date cannot go beyond the limit date of lot use.

  • Potency (field POT)

 

  • Active quantity (field ACTQTY)

 

 

  • Original coef. (field PCUSTUORI)

 

 

  • Order amount (field AMTORD)

 

  • Movement value (field AMTVAL)

 

  • Valued price (field PRIVAL)

 

  • Order variance (field VARORD)

 

  • Cost source (field PRINAT)

 

  • Movement variance (field VARVAL)

 

  • Variance not absorbed (field AMTDEV)

 

The setup determines if the analytical dimensions can be modified. They are initialized based on the setup of the default dimension.

In creation mode, if no order line has been entered and the project code is modified, the analytical dimensions are reset based on the setup of default dimensions.

In creation mode, as in modification mode, if an order line is entered and the project code is modified, the analytical dimensions are not reset.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  • Order price (field PRIORD)

 

 

  • Accounting date (field ACCDAT)

 

 

  • Accounting document (field NUMVCR)

 

  • Owner (field OWNER)

 

  • Intercompany (field BETCPY)

 

  • Creation user (field CREUSR)

 

  • Date created (field CREDAT)

 

  • Time (field CRETIM)

 

Close

 

Action icon

Stock Management Data

Click this action to display a summary screen of the main management rules applied to the inquired product.

Stock by Unit

Click this action to view the stock distribution by packing unit, for all statuses, or status by status.

Stock by Status

Click this action to view the stock distribution status by status.

Accounting Document

Click this action to view the accounting document generated for the selected movement, if subject to an accounting interface.

Stock by Lot
Traceability
Floor
Source Document

Click this action to access the source document, from which the movement originated.

Product

 

Close

 

Specific actions

Click this action to access the additional selection criteria with respect to the criteria entered on the inquiry header.

Filter by document type: you can filter movements according to the specific document type they originated from. By default, the inquiry shows all movement types.

BP: you can refine the selection by filtering movements for a given BP.

Formula: if the standard selection criteria are insufficient, you can set up an additional formula, which must be of the Stock selection type.

Movement update, suspended movement: The inquiry displays by default the actually updated movements. You can choose to display the movements pending update, for example those created from the issue of a shortage material. The display of these two types of movement cannot be carried out simultaneously.

In addition, a specific inquiry is available for suspended movements.

‘Stock’ movements / ‘Internal’ movements:

  • ‘Internal’ movements are movements generated within a storage site. These are changes of status, location or unit, but also changes by license plate numbers, which are also considered as internal changes.
  • 'Stock' movements generate an actual stock transfer. These movements represent stock receipts and issues. A stock adjustment following a stock count also represents a stock receipt/issue.

By default, the inquiry only displays the 'stock' movements. If you modify this setup, you can view the 'internal' movements only, or view the 'stock' movements as well.

Serial number aggregation: when the serial numbers are managed on the products, by default the inquiry retrieves as many lines as the serial numbers concerned by movements, for a given movement. When this option is selected, the serial numbers are aggregated to facilitate the inquiry by reducing the number of displayed lines, so that only one line per movement is presented.

Screen code: as a rule, inquiries can be set up. You can call customized inquiry screens using the screen code. You can use this customization, for instance, to choose what information should be displayed on the screen and in what order it should be positioned in the table.
Please refer to the documentation on Inquiry screens for more information.

You can save the selection criteria under a Memo code in order to recall them later on.
The STD memo code is a special code, which systematically applies when entering the inquiry.

Menu Bar

Graphic/Number of transactions

This graph displays the history of the number of receipts and issues by period.

Only movements selected in the inquiry are taken into account.

The frequency, the date ranges and the number of periods can be modified.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation