Show TOC

 Distributed Supply of Individual/Bulk Consumable Goods

Purpose

You supply individual and bulk consumable goods in a distributed environment.

Prerequisites

Initial situation:

  • The recipient is the same as the requisitioner and works in a logical system1 (for example, a decentralized system).

  • The supplier (sender, MRP controller) works in a second logical system. This logical system can be installed in a central system or in a different decentralized system.

Process

Creating the purchase requisition

  1. A requirement is generated in the decentralized system.

  2. The requisitioner creates a purchase requisition that contains the receiving plant and receiving storage location.

  3. On the basis of the supply relationship, the system determines the external supplier whose plant/storage location combination is transferred to the purchase requisition as the supplying plant and issuing storage location.

  4. The requisitioner saves the purchase requisition.

Synchronizing the purchase requisition

  1. Once the requisitioner has saved the purchase requisition, the following occurs:

    • A purchase requisition without a release strategy is synchronized immediately by the system when it is saved.

    • A purchase requisition with a release strategy is synchronized dependent on the release indicator defined in Customizing (/ISDFPS/CFRGKZ_CS).

  2. The system generates an IDoc and sends it to the supplier’s system.

  3. The supplier’s system creates a new purchase requisition.

  4. The system makes an entry in the CS Item Cat. field of the purchase order item on the Codes tab page.

    This entry indicates that the purchase requisition is one of the following types:

    • Cross-system sender purchase requisition (ITEM_CS = S)

    • Cross-system recipient purchase requisition (ITEM_CS = S)

    • Internal system purchase requisition (ITEM_CS = blank)

The reference between the two purchase requisitions is created on the basis of the entry in the CS PReq and CS Item Cat. fields on the Codes tab page.

Converting to a purchase order

The supplier converts the internal system and cross-system sender purchase requisitions in his or her system to a purchase order.

Note Note

Cross-system recipient purchase requisitions cannot be converted.

End of the note.

As a result of this procedure, the actual quantity ordered is updated in the sender purchase requisition. This quantity, ordered by the external sender, is synchronized back to the receiving system by means of an IDoc and stored in the BMSNG_CS field on the Codes tab page.

Creating the outbound delivery

The supplier uses standard tools to create an outbound delivery for the cross-system stock transport order (such as VL10B).

Posting the goods issue

When a goods issue is posted for the cross-system delivery, the following occurs:

  1. Movement type 6A1 is used in the sending system. In the sending system, the goods issue is posted with 6A1.

  2. The following messages are created:

    • Message /ISDFPS/DESADV generates an inbound delivery in the receiving system.

    • Message /ISDFPS/PO generates a recipient purchase order in the receiving system.

    • Message /ISDFPS/GOODSMVT_SAPCREATE generates the offsetting posting 6B1 for the recipient purchase order in the receiving system. The offsetting posting for 6A1 means that the stock in transit is created in the receiving system.

  3. All these IDocs are grouped together by the system and sent in a UPS packet automatically. You can track this procedure in transaction UPS.

  4. In the sending system, the 6A1 posting updates the purchase order history of the sender purchase order. In the receiving system, the 6B1 posting updates the purchase order history of the recipient purchase order.

The following applies:

  • The recipient purchase order number is identical to the outbound delivery number in the sending system.

  • By default, the recipient purchase order type EUB is used.

    If you want to create user-specific recipient purchase order types, these have to be copied from EUB.

    See also the Implementation Guide (IMG) for Start of the navigation path Materials Management Next navigation step Purchasing Next navigation step Purchase Order Next navigation step Define Document Types End of the navigation path .

    If entries are defined in the IMG activity Start of the navigation path Derive Recipient Purchase Order Document Type(underDefense Forces and Public Security Next navigation step Distributed System Landscape Next navigation step Application-Specific Settings Next navigation step Distributed Materials Management) End of the navigation path , these entries have priority and override the standard setting.

Posting the goods receipt

  1. In the receiving system, the goods receipt is posted for the inbound delivery and the purchase order history of the recipient purchase order is updated.

  2. The system generates an IDoc with the goods receipt information and sends it to the supplier’s system. This message updates the purchase order history for the sender purchase order.

This concludes the supply of individual/bulk consumable goods in a distributed environment.