The CRM Journal traceability function can also be accessed directly from each of the management functions of CRM journals.
Refer to documentation Implementation
Presentation
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.
Close
Fields
The following fields are present on this tab :
| Choose the direction of the search: |
| This field displays the company currency and cannot be modified. |
| This field displays the folder currency and cannot be modified. |
| Enter a document type if you wish to filter the inquiry and restrict it to this type of document. |
| Enter the document number reference to inquire, depending on the chosen document type. |
| Line number of the document to inquire. |
| Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). |
| Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). For instance:
|
| Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). Examples :
|
Close
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 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 |
Close
Fields
The following fields are present on this tab :
XSL
| Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). Example of a sales invoice with an upstream traceability: 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. |
| The type, number and line number of the document are used to identify its origin. |
| Posting date of the document. |
| Origin site of the document. |
| This field indicates the code identifying the BP. |
| 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. |
| Help common to the different Journal traceability inquiries (purchasing, sales, CRM, A/P-A/R accounting and fixed assets). |
Close
Action icon
Use this button to access the line 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.
Use this button to inquire the upstream traceability of the document on the line.
Use this button to inquire the downstream traceability of the document on the line.
Close