Logging

Where the app records what happened during an import – and how to reason from that to a cause.

The levels of logging

The app logs on three levels. When something goes wrong, work down from the top.

Level	Location	Answers the question
1	Import session	Did the import as a whole complete?
2	Staging record	Which individual record has a problem, and why?
3	Action result messages	What did writing prices or building BOMs actually do?

Level 1: The import session

Every import session records the course of an import.

Field	Tells you
Status	Pending, Processing, Completed, Completed with Errors, Error, Cancelled.
File Name	Which file was processed.
DATANORM Version	The version detected from the header record.
Vendor No.	The assigned vendor.
Records Processed	Number of records read.
Records with Errors	Number of lines that could not be read.
Start Time, End Time	Duration of the import.
Error Message	Cause, if the session was aborted.

Completed with Errors means the file was processed but individual lines could not be read. The import is not worthless – check in staging what is missing.

Level 2: The staging record

Every record carries its own status and its own message.

Field	Tells you
Processing Status	Where the record sits in the flow.
Is Duplicate, Duplicate Reason	Whether and why a match was detected.
Matched Item No.	The existing item the match points to.
Error Message	Why synchronisation failed.
Merged Source Records	How many file lines the record was built from.

Filter staging on Processing Status = Error to see all the problem cases of a session at once.

Level 3: Result messages

The actions on the import session report what they did once they finish.

Action	Message contains
Write Purchase Price List	Number of purchase lines, sales lines, scale price lines and skipped articles.
Build Part Lists	Number of sets built, components created, sets skipped and errors.
Assign Vendor	Number of staging records adjusted.

Note these figures during a sign-off. They are the quickest evidence that an import ran through completely.

Archived files

With Archive Imported Files enabled, the app keeps the original file content on the import session. That makes it possible to reconstruct later what the supplier actually delivered, regardless of whether the file is still available from them.

Leave archiving on. It is often the decisive evidence when clarifying something with a supplier. Very large catalogues use storage accordingly – delete old sessions selectively if needed.

SFTP logging

The SFTP setup carries two fields for diagnostics:

Field	Tells you
Last Polling Time	When the inbound folder was last checked. An old timestamp suggests the job queue is not running.
Last Polling Status	Result or error message of the last poll.

In addition, DATANORM SFTP Files shows what is in the inbound folder.

How to approach a problem

1

Look at the session

Read the status and error message of the import session. If there is an abort reason, the cause is usually the file itself.

2

Filter staging

Filter on status Error and read the messages. If the same message repeats, the cause is in the setup, not in the data.

3

Fix the cause

Add the missing unit mapping, posting group or number series, see Common Problems.

4

Synchronise again

Only synchronise the affected records again. Re-importing the file is almost never necessary.

For a support request

Have these details ready:

• Number and status of the import session
• File name and detected DATANORM version
• Exact wording of the error message
• Number of records processed and failed
• The DATANORM file in question, if you are allowed to share it

Contacts under Support Contacts.