Journal traceability
Use this function to view the log of an entry related to the customer relations management (CRM activity and/or customer support, depending on the activation of these modules).
This function provides:
- the upstream flow leading to the documents of origin, including the flow of sales documents (for example: invoices, service contracts, orders and quotes),
- the downstream flow for documents leading down to the total payment of invoices for service contracts or requests.
The CRM Journal traceability function can also be accessed directly from each of the management functions of CRM journals.
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 customer 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 Customer base document flow:
Customer base |
|
|
|
|
End user |
|
Shipment |
|
|
|
Return status: Partially returned |
|
|
Picking ticket |
|
|
Picking ticket status Delivered |
|
|
|
Sales order |
|
Closed |
|
|
|
|
Sales quote |
Totally ordered |
Example of a Downstream representation of a Customer base document flow:
Customer base |
|
End user |
|
|
Service request |
|
Dispatching |
|
|
Action |
Completed: Yes |
|
|
Solution |
Category A1 |
Example of an Upstream representation of a Task document flow:
Task |
|
|
|
|
|
Completed: No |
|
Sales invoice |
|
|
|
|
Invoice status: Validated |
|
Shipment |
|
|
|
Return status: Partially returned |
|
|
|
|
Picking ticket |
|
|
Picking ticket status Delivered |
|
|
|
|
Sales order |
|
Closed |
|
|
|
|
|
Sales quote |
Totally ordered |
Document |
Use this button to access the line document. |
Document |
This Project action is only available in the upstream flow inquiry of a quote when it is related to a mixed project (PRP and CRM). In this case, you can quickly access the two types of projects using this button and the Back button. |
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. |