Show TOC

 Support for Relocation in Decentralized Systems

Use

During relocation, relevant movement data must be sent manually to the decentralized system in intermediate documents (IDocs).

You have to define manually which picked outbound deliveries for goods issues have been posted and that originate from relocation stock transport orders are to be sent.

Prerequisites

You have customized the Cross-System Flow of Goods scenario in both the ordering system (decentralized system) and the delivery system (central system).

For more information, see SAP Library under Start of the navigation path SAP R/3 Enterprise Application Components Next navigation step Logistics Next navigation step Logistics – General Next navigation step Special Processes in Logistics  Next navigation step Cross-System Flow of Goods Next navigation step Implementation Guide Next navigation step Settings in Customizing for Replenishment End of the navigation path .

For each plant that is used as an external supplying plant in the decentralized system in the relocation stock transport order, you have created a vendor master record with a supplying plant assignment.

The advantage of this function is that you do not have to create any plant or storage location data (master data records) for external plants.

In addition to the business-related Customizing settings for the Cross-System Flow of Goods process, you have defined an ALE model between the central and decentralized systems. For more information, see the Implementation Guide (IMG) for Start of the navigation path SAP Web Application Server Next navigation step Application Link Enabling (ALE) End of the navigation path .

If you want the IDocs to be serialized, you have created a serialization group for IDocs (transaction BD44).

To create an offline purchase order, you have to create a new number range, 55, which matches the number range interval for outbound delivery numbering in the central system and assign it to the new order type VUB.

  • New document type stock transport order for relocation

    Create VUB as a copy of UB and ensure it is taken into account during determination.

    When you define this document type, you must ensure that the Vendor indicator is set to X so that the system uses the vendor data in the stock transport order.

  • New delivery type delivery for relocation

    Create VNL as a copy of VL and ensure it is taken into account during determination.

  • New item category VLN for relocation

    Create VNL as a copy of NLN and ensure it is taken into account during determination.

  • New schedule line category VN for relocation

    Create VN as a copy of NN with movement type 6A1 and ensure it is taken into account during determination.

  • External supplying plant for relocation (with vendor master)

    You have to define a plant as the supplying plant for relocation, with a vendor master, which is copied to the relocation step definitions.

Features

The List of Deliveries for Relocation (transaction /ISDFPS/VLV1) supports the tasks involved during relocations.

Selection Screen

When you call up the List of Deliveries for Relocation , a screen appears on which you select deliveries for relocation.

You enter data to select the deliveries you want to process.

You can use the following indicators to control the program flow:

  • Procg Mode

    If you set the Interactive indicator, the system displays a list when you have made your selection, which you can use to send the outbound deliveries manually.

    If you set the In the Background indicator, the system selects and processes the outbound deliveries. You use this mode to schedule a processing job automatically.

  • Settings for IDocs

    If you set the Send IDocs Automatically indicator, the system triggers IDoc transmission in the sequence defined in Customizing for the specified serialization group. The default value is SDP_BW_VSTO.

List of Deliveries

When you call up interactive processing, the system displays a list of all the deliveries that meet your selection criteria.

The list contains the following information:

  • Delivery

    The document number of the outbound delivery for relocation

  • Distribution status

    The distribution status indicates whether the outbound delivery has already been sent to the decentralized system (that is, whether the IDoc has already been created for BAPI BAPI_PO_CREATE1).

    The traffic lights indicate the following:

    • Gray

      An IDoc has not yet been generated for creating the purchase order.

    • Yellow

      An IDoc for creating the purchase order has been generated but not yet sent.

    • Green

      An IDoc for creating the purchase order has been generated and sent successfully.

    • Red

      An IDoc for creating the purchase order has been generated and has the status Incorrect .

  • Offline logical system

    The identification of the logical system on a decentralized system

  • Offline purchase order number

    The document number of the decentralized purchase order (identical to the document number of the outbound delivery in the central system). You can navigate to the document display by double-clicking the document number.

  • Total goods movement status

    The delivery status

  • Central purchase order and item

    The preceding document of the outbound delivery. You can navigate to the display of the purchase order for relocation by double-clicking the document number.

  • Relocation information

    The receiving force element, relocation, relocation step.

In addition to the columns listed here, you can use the user layout to show other columns from the document header.

The following functions are also available (from left to right):

  • Selection of outbound deliveries: by row (one or more rows), all rows

  • Send outbound deliveries to decentralized systems

  • Refresh the display: The system rereads the information in the list, such as the distribution status, and refreshes the display.

  • Display relationships for the selected outbound delivery:

    exactly one outbound delivery and choose Display Linked Documents .

    In the bottom screen area, the system displays the IDoc relationships for the selected delivery. From this display, you can navigate forwards to the IDoc display with status management.

  • Display log for processing the sent deliveries

Logging

The system logs messages that are created during background processing. The messages from background processing are collected for each delivery and saved for a collective run with the newly defined type VL ( deliveries for relocations ).

You can use the existing Log of Collective Runs program (transaction V_SA) to perform an evaluation hierarchically by delivery number.

This log can also be displayed for the distributed deliveries for relocations from the monitor of the delivery for relocation. The most recently generated log is always displayed.

Activities

Changing the Purchase Order Number and Receiving Plant for Relocation

In the relocation scenario, the goods movement for setting up the stock in transit is also created when the goods issue is posted.

In the IDoc for posting the stock in transit in the decentralized system, the system replaces the purchase order number with the delivery number. The external number of the decentralized purchase order is identical to the document number of the outbound delivery in the central system.

In contrast to the scenario for cross-system flow of goods , in which the VGSYS field is filled, the IDoc has to be created explicitly in this case. Business Add-In (BAdI) LE_SHP_GOODSMOVEMENT is used for this purpose.

The system checks whether the delivery is relevant for the relocation.

If it is, the logical system name of the decentralized system is entered. For the determination of the logical system, a distinction is made between two cases:

  • Relocation in formation area

    In this case (identified by the Second Relocation Step indicator), the system copies the plant from the relocation step (this plant is the same as the external supplying plant for relocation)

  • Relocation in target area

    In this case, the plant remains unchanged.