<?xml version="1.0" encoding="utf-8"?>
<OptionList ID="/baanerp/tp/domains/pdm.lexp" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Log Commitments (Purchase Transactions)</Title>
	</Header>
	<ListValue ID="not"><Value>Not</Value>
		<Paragraph>An exception is hard commitments in case a purchase order is delivered directly to a Project site. In that case, a hard commitment line is created. In the case of a direct delivery to a project site, the cost of WIP is posted to Finance. Hence, the commitment in Project becomes cost in Finance.</Paragraph>
		<Paragraph>This is done because of the timing of the next step: "invoice approval". The moment of the invoice approval is not controlled from Project but from Finance. Therefore, the cost of WIP is posted to Finance .</Paragraph>
		<Paragraph>So, on one hand we cannot wait until invoice approval for registering WIP costs because this in many cases will be late. On the other hand, there is still commitment, because the goods are only delivered (not consumed) to the project and may be returned to a warehouse (for example, the goods have been ordered, but are not used).</Paragraph>
	</ListValue>
	<ListValue ID="both"><Value>Order and Delivery</Value>
		<Paragraph>Commitments are logged at the point of ordering and at the point of delivery (when the goods or services are received).</Paragraph>
	</ListValue>
	<ListValue ID="pur.deliv"><Value>Delivery</Value>
		<Paragraph>Commitments are logged only at the point of delivery.</Paragraph>
	</ListValue>
</OptionList>
