| To use posting typesPosting Types (introduction) Posting types are used
to recognize transactions. Posting types indicate where the transaction
originates from, and combine certain related posting types in project history.
In the process of posting, most posting types are a temporary display in
project history of what happens to, for example, an order. If the order is
manually entered, the posting type is Project Control. If the order is actually
entered in Finance, the posting type becomes Soft Commitment in project
history. If the goods are received on the project for direct delivery, the Soft
Commitment becomes a Hard Commitment in project history. The posting type of the transaction determines: - The posting type that
is used in history.
- The posting type of
the surcharge, if applicable.
- The financial
transactions that are made in Financials in the general ledger.
Project uses many different
posting types, and therefore the following explanation describes the various
possibilities for costs, commitments, and revenues. For example, to find out
what happens with sundry costs in ERP, the posting types clarify from where the
costs originate. For every posting type, the history posting type is provided.
The history posting types are self-explanatory, or have the same
characteristics as the actual posting types. Commitment posting types Material/Equipment/Subcontracting: - Project Control. The
commitment is entered in the cost object commitment session. History posting
type: Soft Commitment.
- Order. ERP generates
the commitment from a created purchase order. History posting type: Soft
Commitment.
- Delivery to Project.
ERP generates the commitment on delivery of a purchase order to the project.
History posting type: Hard Commitment (project).
- Project Control
(Rev.Ent). The commitment is already posted through the Process Transactions (tpppc4802m000) session, but a reverse entry must still
be made. History posting type: Soft Commitment.
- Delivery to Proj.
Wareh. ERP generates the commitment on delivery of a purchase order to the
project warehouse. History posting type: Hard Commitment Wh.
- Reverse Delivery
(Proj). A reverse entry is made for the commitment generated from a purchase
order delivery when a purchase invoice is processed in Financials. History posting
type: Hard Commitment (project). Sundry Cost:
- Project Control. The
sundry cost commitment is entered in the Commitments (Sundry Cost) (tpppc2190s000) session. History posting type: Soft Commitment.
- Proj. Control
(Rev.Entry). The sundry cost commitment is already posted through the Process Transactions (tpppc4802m000) session, but a reverse entry must still
be made. History posting type: Soft Commitment.
- Charge Soft
Commitment/ Charge Soft Comm. Reverse/ Charge Delivery to Proj./ Charge
Delivery to Proj. Wh./ Charge Reverse Delivery: These charges are surcharges on
commitments posted with the Process Transactions (tpppc4802m000) session. At project completion, these
surcharges are settled and removed from the Sundry Cost Commitment table.
History posting type: Charge Soft Commitment/ Charge Soft Comm. Reverse becomes
Surcharge Soft Commitment. History posting type: Charge Delivery to Proj./
Charge Delivery to Proj. Wh./ Charge Reverse Delivery becomes Surcharge Hard
Commitment.
Cost posting types Material Cost: - Project Control. The
material costs are entered in the Material Costs (tpppc2111s000) session. History posting type: Project Control.
- Inventory. The
material costs are generated when the Transfer Planned PRP Warehouse Orders (tppss6235m000) session is run. History posting
type: Inventory.
- Purchase Invoice
(Fin.). The material costs are posted to Project by subdividing a
cost invoice in Financials.
History posting type: Purchase Inv. Fin.
- Invoice (Purchase
Order). ERP generates the material costs during the processing of a purchase
invoice in Financials based
on a purchase order. History posting type: Invoice (Purchase Order).
- Price Variance.
Differences between the order price and the purchase invoice amount are posted
as project cost transactions. History posting type: Invoice (Purchase Order).
- expense tax. Direct
deliveries to a project are posted as project cost transactions. History
posting type: Expense Tax.
- Price Variance. If the
purchase invoice is booked, and the project warehouse issue to the project is
performed, the price variance of the purchase invoice causes a correction order
in Warehousing for the already issued items. History posting type: Value
Corrections.
Labor Cost: - Project Control. The
labor cost transactions are entered in the Labor Costs (tpppc2131s000) session. History posting type: Project Control.
- Hours Registration.
The labor cost transaction is recorded in Project from People. History posting
type: Hours Registration.
- Subcontracting Hours.
Subcontracting transactions are entered in the Subcontracting Hours (tpppc2132s000) session and have no posting type. In history,
the Subcontracting Hours posting type is displayed.
Subcontracting Costs/ Equipment Cost: - Project Control. The
subcontracting costs are entered in the Subcontracting Costs (tpppc2171s000) session. History posting type: Project Control.
- Purchase Invoice
(Fin.). The subcontracting costs are posted to Project by subdividing a
cost invoice in Financials.
History posting type: Purchase Invoice (Fin).
- Invoice (Purchase
Order). ERP generates the subcontracting costs by processing a purchase invoice
in Financials, which is
based on a purchase order. History posting type: Invoice (Purchase Order).
- Invoice Difference.
Differences between the order price and the purchase invoice amount are posted
as project cost transactions. History posting type: Invoice (Purchase Order).
- expense tax History posting
type: Expense Tax.
Sundry Cost: - Project Control. The
sundry costs are entered in the Sundry Costs (tpppc2191s000) session.
History posting type: Project Control.
- Purchase Invoice
(Fin.). The sundry costs are allocated to projects in Project by a breaking down a
cost invoice in Financials.
History posting type: Purchase Invoice (Fin).
- Expenses (BP). The
sundry costs are generated with the Hours and Expenses by Employee Overview (bptmm1100m000) session. History
posting type: Expenses (BP).
- Surcharge Post to
Finance/ Surcharge Don't Post to Finance Surcharges are entered in the Process Transactions (tpppc4802m000) session, the costs are surcharges over
costs posted with the post-transactions-process. At the end of this process,
the surcharges are removed from the Sundry Costs table. History posting type:
Surcharge on Costs
Overhead Cost: - Project Control. The
overhead costs are calculated in the Calculate Overhead (tppdm2200m000) session. History posting type: Cost history.
- Purchase Invoice
(Fin.). Overhead transactions are generated and applied to the related Project. History posting
type: Cost history.
- Expenses (BP). The
overhead costs are generated with the Calculate and Apply Overhead (tpppc6120m000) session. History posting type: Cost
history.
- Surcharge Post to
Finance/ Surcharge Don't Post to Finance Surcharges are transferred to Finance.
The costs are overheads over costs posted with the
post-transactions-process.
Revenue posting types - Project Control. The
revenue is manually entered in the Revenues (tpppc3101s000) session. History posting type: Project Control.
- Sales Invoice
(Proj.). The revenue is based on a project invoice. History posting type:
Invoicing.
- Sales Invoice
(Fin.). The revenues are posted to Project by subdividing a sales invoice in Financials. History posting
type: Sales Invoice (Fin.).
- Sales Invoice
Holdback. The revenue is accounted for, but is not yet invoiced. History
posting type: Invoicing Holdback.
- Sales Inv. Holdback
(Rev). The holdback is released and invoiced reversely. History posting type:
Invoicing Holdback.
- Sales Invoice
Advance. The revenue originates from an advanced payment. History posting type:
Invoicing.
- Sales Inv. Advance
(Rev). The invoice that originated from an advanced payment is reversed.
History posting type: Invoicing.
| |