Inter-company procurement Article series-inter-company procurement plan agreement

Plan agreement for inter-company procurement

Inter-company procurement can be in the form of procurement orders, but in some cases it is more appropriate to adopt a plan agreement.

For example, a large amount of spare parts may be dumped between different production plants every day. Therefore, when purchasing orders are used, the workload will be relatively large.

This document briefly describes the process.

TransactionsCode: Me31 creates a scheduler protocol. to simplify the operation, we use the scheduler protocol type LP. Save the plan protocol and generate the scheduler Protocol Number 9500000002.

Click shipping in the menu to view the shipping information.

Me38 maintains the delivery plan, which can be input manually (in this example), but is generally generated based on the MRP running result in actual business.

We enter three delivery dates: 10, 20, and 30. It can be seen that, If you create a purchase order, you need to create three purchase orders, a lot of work.

Transaction code: vl10d, create a bill of lading and ship the bill

Select the date from January 1, April 18-4 to the 19th day. In combination, you can see that the number of items in the purchase order line depends on the date on which the delivery order is created.

If the date is from January 1, April 18-4 to January 18, the number is 10.

If the date is from January 1, April 18-4 to April 20, the number is 60.

The number is 30, which corresponds to the first two rows in the Plan protocol.

Migo: goods received by Purchase Order (detailed steps omitted)

Vf01, create invoice (detailed steps omitted)

Miro, invoice verification (detailed steps omitted)

Note: When creating an invoice for vf01, you cannot copy the price from the plan agreement. The specific reason is described later.