Entering content frameProcess documentation MM Scenario - Interplant Purchasing Locate the document in its SAP Library structure

Purpose

This scenario explains the issues involved for performing interplant purchasing between plants that are in distant time zones. Using the Time Zone function, the system can display local dates and times, but the system times remain unchanged. We have a choice of using the standard purchasing stock transport or the delivery enabled stock transport. Using deliveries enables shipping functions such as ATP checking upon delivery create, use of routing times, print documentation for the movement and delivery scheduling.

For longer distances we recommend that SD deliveries be used even though it involves more configuration and processing. Stock transport orders do not have the necessary in-transit planning needed for longer distances, and time zone differences can worsen the situation.

Process Flow

  1. A stock transport purchase order is created to bring goods from a distant plant location (whether they are in the same company or not). The delivery date can be in the past since it is the delivery date of the receiving plant, and not of the user entering the transaction. The order date is based on the time zone of the user entering the transaction.
  2. A delivery due list can be called to display what should be delivered from the supplying plant. The delivery due list is called up based on the delivery creation date proposed. The delivery creation date is determined from the receipt date of the customer minus the planned delivery time in the material master.

    3. Note

    The delivery time from goods issue in the supplying plant to goods receipt in the requesting plant cannot be defined unless you use route determination with transit time.

  3. Even though there is a goods issue date on the delivery, the goods issue for the delivery is posted with the system date when the items move out of the supplying plant in-transit to the receiving plant. This is because the date is assigned in the background and cannot be seen by the user.
  4. When the goods arrive at the receiving location, the posting date is the same as the date of the user making the transaction. The entry date is the same as the system date when the transaction occurred.

Result

The stock transport has an order date based on the local user time but a delivery date based on the requested date of the plant receiving the goods.

On the delivery due list, the delivery creation date is based on the due date at the receiving plant minus the planned delivery time.

On the delivery, the goods issue date is a week prior to the actual delivery date. The GERUSA route has in-transit, load time, and a calendar that it uses in calculating this date.

On the accounting document for the material movement of the goods from the supplying plant to the receiving plant, the posting date is the system date since it does not appear when creating the delivery.

The important thing in material documents is that the value of the goods is transferred immediately upon the issue from the supplying plant to the receiving plant.

Tips

Delivery documents post goods issue with the system date as the posting date. This cannot be changed manually.

You can use standard MM stock transfers or SD deliveries for these types of transactions, but there is currently a gap in that the transportation time from when the supplying plant issues the goods and when the receiving plant makes it available. Currently the stock is available in an in-transit status immediately.

Therefore, we recommend that for long transit times the delivery processing option is used with route determination for managing long in-transit times.

As soon as the delivery is posted in the shipping plant, the goods are valued in the receiving plant in an "in-transit" status. The value of these goods will then show up in the inventory account of the receiving plant.

See also:

MM Scenario - Global Purchasing

Leaving content frame