Journal traceability
Use this function to view the log of a sales document linked to the A/P-A/R accounting (Statement or Payment) by giving:
- the upstream flow leading to the documents of origin,
- for statements: sales documents (sales invoice, delivery, picking ticket, order, quote, etc.),
- for payments: purchase or sales documents,
- the downstream flow of documents down to the total payment of the invoice (payment, open items, etc.).
The BP entries traceability function can also be accessed directly form each management function of entries.
Prerequisites
Refer to documentation Implementation
Screen management
Header
The inquiry header is used only to select the sales journal to be traced.
Once the journal has been selected, its status, the BP code and name, the company currency and the folder currency are displayed for information purposes.
Sign (field TRKSEL) |
Choose the direction of the search: |
Company currency (field CURSOC) |
This field displays the company currency and cannot be modified. |
Folder currency (field CURFOL) |
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. |
BP (field BPRNUM) |
Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). |
Part status (field VCRSTA) |
Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). For instance:
|
Part status (field VCRSTA_L) |
Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). Examples :
|
Tab Traceability
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.
Examples of flow tree structure representations:
Example of an Upstream representation of a Statement flow:
Statement |
|
|
|
|
Journal validated: No |
|
|
Sales invoice |
|
|
|
|
Invoice status: Validated |
|
|
Shipment |
|
|
|
Return status: Partially returned |
|
|
|
Picking ticket |
|
|
Picking ticket status Delivered |
|
|
|
|
Sales order |
Closed |
|
|
|
|
|
|
Sales quote |
Totally ordered |
Example of a Downstream tree representation of a Statement flow:
Statement |
|
|
Journal validated: No |
|
Open item |
|
Reminder: Yes |
|
|
Payment |
In the bank |
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. |