What happen when you run the WIP accounting interface FUNWIPACC?

1 minute read time.

When a work order is created then sent to production for processing and completion, the system creates several records in the WIPCOST (WIP value) table with different TXNTYP information. The WIPCOST table is the source table for all WIP posting that will update to the general ledger.

The TXNTYP fields which identify the origin of the cost are the main criteria driving the accounting posting. The common TXNTYP in the WIPCOST table are labor and machine cost, material and labor expenses, machine expenses, and production statement. After completing and closing the work order, the WIP finalization FUNWIPMFC is run to calculate the variance between the actual cost and standard cost, and upon the calculation of the actual cost, the system might generate several extra TXNTYP records such as material and labor variances, machine and overhead variances.

However, these TXNTYP records information will not update the general ledger unless we run the WIP posting FUNWIPACC function. Several fields in the WIPCOST table such as the posting flag GLPSTA, posting date GLPDAT, journal type JOUTYP, and journal number JOUNUM will not update by running the FUNWIPMFC.

Upon running the WIP accounting interface FUNWIPACC, the following fields are updated in the WIPCOST table:

GLPSTA: The posted flag is changed from 1 (No) to 2 (Yes).

GLPDAT: The posted date will update with the accounting date of the posted movement.

JOUTYP: This is the journal type for the accounting entry type of the posted movement. However, the records for the material issue will be updated in the STOJOU table.

JOUNUM: This entry number has the accounting entry number of posted movement. The material issue will be updated in the STOJOU table.

Running the FUNWIPACC will pass the work order records that have resulted from the production tracking along with any variances or adjustment records during the production cost calculation to the accounting module.