Create and post an inventory journal
Only one user at a time can access a journal. If several users must access journals at the same time to create journal lines, those users must select journals that aren't currently being used to prevent information from being overwritten. In situations where multiple departments use the same journal type, it's helpful to create multiple journal names (for example, one for each department). It can also be helpful to divide journals so that people enter each posting routine in its own unique inventory journal.
For posting routines that are associated with inventory transactions, you can create one journal for periodic inventory adjustments and another for inventory counting.
Post journal lines
You can post the journal lines that you create at any time until you lock an item from extra transactions. The data that you enter in a journal remains in that journal, even if you close the journal without posting the lines.
Not all inventory journals are OData-supported; therefore, you can't use the Microsoft Excel data connector to get data published, updated, and imported back to Supply Chain Management.
Another difference between the journal data entities is the ability to use composite entities that include the header and line data. You can use the composite entities for the following journals:
Inventory adjustment
Inventory movement
The following two inventory journals only support the Initialize stock scenario as part of a data management import project:
When you don't specify a journal header number but you specify a number sequence for the journal type, the import job automatically creates journal headers for every 1000 lines. For example, importing 2020 lines results in the following three journal headers:
Header 1 - Contains 1000 lines
Header 2 - Contains 1000 lines
Header 3 - Contains 20 lines
Assume that unique line information exists for each inventory dimension, which can be a product, storage, and tracking dimension. Therefore, you can't import journal lines where only the date field differs on the lines in the same import project.