When you create your Landed Cost processing, you can link those costs directly to a job. To accomplish this, the Landed Cost must be based upon a GRPO that is associated with a job. The job lines associated with the GRPO must not have been processed. The job lines can only be updated if they are still a part of WIP (work-in-progress). The status of these lines must be set to Entered, or Ready to Process. In this case, the lines will automatically be updated with the amended cost. However, if the lines have already been processed and are no longer part of WIP, then the additional Landed Costs will be written off to COGS.
When you apply your cost to the Landed Cost document, those costs will flow through to the job line. The job lines will in turn be updated with those additional costs, and a journal entry will be processed in the background to update the WIP GL account.
Landed Costs can also be processed for non-inventory items, in which case Eralis Job will generate a journal entry updating the job cost accordingly. The SAP Business One journal entry will debit the expense account and credit the Landed Cost clearing account. Then a journal entry will be processed to take the cost out of the expense account and put it into the WIP balance sheet account.
It is important to note that there is an additional non-standard SAP Business One journal entry that must be processed if you are doing Landed Cost processing for non-inventory items.