Fixed assets > Inquiries > Document traceability 

Use this function to view the log of a journal linked to fixed assets (expense or asset) by giving:

  • the upstream flow leading to the original journals (purchase requests, purchase orders, supplier BP invoices, etc.),
  • the downstream flow of journals up to the asset.

The representation of traceability also displays the status of each journal. You can access the management screen of the document via the Actions icon.

SEEINFO This function can also be accessed directly from each of the management functions of fixed assets and journals.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

Presentation

The inquiry header is used only to select the expense or asset to be traced.

Once the journal has been selected, its status(es), the supplier code and name, the company currency and the folder currency are displayed for information purposes.

Close

 

Fields

The following fields are present on this tab :

  • Sign (field TRKSEL)

Choose the direction of the search:
- Upstream
- Downstream

This field displays the company currency and cannot be modified.

This field displays the folder currency and cannot be modified.

  • Document type (field VCRTYPSEL)

Enter a document type if you wish to filter the inquiry and restrict it to this type of document.

  • Document number (field VCRNUMSEL)

Enter the document number reference to inquire, depending on the chosen document type.

 
  • Line number (field VCRLINSEL)

Line number of the document to inquire.
Example: line 1 = 1000

Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets).
This field displays the BP code and cannot be modified.
For purchase requests, this field is empty since the BP code is displayed on the line.

  • Part status (field VCRSTA)

Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets).
This field displayed the journal status, its title depends on the journal type inquired.

For instance:

  • For a purchase request: Closed
  • For a purchase order: Invoiced
  • For a sales order: Order status
  • Part status (field VCRSTA_L)

Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets).
3 fields of this type are available. They display the status of the upstream/downstream journals related to the journal displayed. Their display and their title depend on the type of journal displayed.

Examples :

  • For a purchase order:
    - Invoiced: Yes / No
    - Closed: Yes / No
  • For a purchase invoice:
    - Invoice status: Pending / Validated
  • For a sales order:
    - Delivery status
    - Invoice status
    - Signature
  • For an expense:
    - Fixed: Yes / No

Close

 

Tab Traceability

Presentation

The traceability of the various documents is shown in the form of a tree structure and a grid, with the status of each journal indicated.

Example of flow tree structure representation:

Example of the Upstream representation of an Asset flow:

Asset 

 

 

 

 

 

Fixed asset in service

 

Expense

 

 

 

 

Invoice
Capitalized: Yes

 

 

Purchase invoice

 

 

 

Invoice status: Validated

 

 

 

Purchase receipt

 

 

Invoiced: Totally
Posted: No
Closed: Yes

 

 

 

 

Purchase order 

 

Invoiced: Totally
Signature: No management
Closed: Yes
Receipt: Totally

 

 

 

 

 

Purchase request

Closed: Yes
Ordered: Yes
Signature: No management 

Close

 

Fields

The following fields are present on this tab :

XSL

Grid

  • Level (field LEV)

Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets).
This displays the level in the document hierarchy. Value 1 corresponds to the selected document, value 2 to the document directly linked to the selected document, 15 being the maximum value of a multi-level log.

Example of a sales invoice with an upstream traceability:
Level 1 = invoice level.
Level 2 = delivery level.
Level 3 = order level.
Level 4 = quote level.

The same level can be used as often as there are levels for this invoice. For instance, there will be a delivery level as often as there are deliveries for this invoice.

  • Document type (field VCRTYP)

Document type.

  • Document number (field VCRNUM)

The type, number and line number of the document are used to identify its origin.

  • Document date (field IPTDAT)

Posting date of the document.

Origin site of the document.

This field indicates the code identifying the BP. 

  • Company name (field BPRNAM)

This is the corporate or company name of the chosen supplier. This information is not accessible.

This field is filled only if the line is posted and an accounting document has been generated.

  • Document status (field VCRSTAT1)

Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets).
This field indicates the journal status. Three other fields of this type are available. They display the status of the upstream/downstream journals related to the journal displayed. Their display and their title depend on the type of journal displayed.
For example, for a sales order, its status is displayed as well as the delivery and invoice status.

Close

 

Action icon

Document

Use this button to access the line document.

Upstream traceability

Use this button to inquire the upstream traceability of the document on the line.

Downstream traceability

Use this button to inquire the downstream traceability of the document on the line.

Entry

 

Close

 

Specific Buttons

Use this button to access the additional information of the displayed document, especially the amounts in the journal currency, company currency and folder currency.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation