Tr Transmission of Location Master Data

The following sections describe the functions for transmission of location data.

The initial transmission of location master data should take place when the interface is active. All necessary master data should be copied into the database of the transportation planning system. During this process, the SAP system always represents the reference.

You can start master data transmission via transaction VT60 or menu path Logistics ® Sales/distribution ® Transportation ® External systems ® Transportation planning ® Transmit master data.

The first program (RV56LMTP) serves to define the planning system (transportation planning point) and the location master data that is to be transmitted. This program then starts the actual transmission program (RV56LMSL), the selection screen of which allows you to specify exactly which location master data you want to transmit .

In the selection screen of the first program (RV56LMTP), only transportation planning points that are linked to an external planning system are accepted. You can also use checkboxes to select which location master data types will appear on the selection screen of the second program (RV56LMSL).

The master data of customers, vendors and also of forwarding agents is connected to the ALE change indicator. The function is available after activating the change indicator for message type TPSLOC in Customizing. If a data field relevant to the interface is changed in a master record that has already had details transmitted or if a new master record is added, then a change indicator is created automatically.

The change indicators must then be evaluated. This involves transmitting the changed master data documents. The evaluation of the change indicators is carried out with transaction BD21 or via Logistics ® Sales/distribution ® Transportation ® External systems ® Transportation planning ® Change master data. Then enter message type TPSLOC.

Regular, automatic evaluations of the change indicators can be carried out as a job via program RBDMIDOC.

The master data records for plants, shipping points and transportation connection points cannot be connected to the ALE change indicator for technical reasons. If these master data records are changed or if new ones are added, then you need to carry out a manual transmission using the function described in the Initial Transfer section.

If the changed or new master data can be limited (by entry date, for example) then an automatic transmission can be carried out as a job with program RV56LMSL. The selection criteria can then be entered as selection variants.

Using explicit transmission , you can transmit a large number of deliveries chosen from the selection requirements and which are also available in manual shipment processing (transaction VT01) to a transportation planning system. Specifying the transportation planning point (planning system) and the processing type (outbound or inbound shipment) is obligatory.

You can start the planning request transmission via transaction VT61 or menu path Logistics ® Sales and distribution ® Transportation ® External systems ® Transport. planning ® Send deliveries.

Deliveries can be transmitted regularly and automatically to one or more planning systems according to certain selection criteria. This is appropriate, for example, if all shipments are to be planned overnight.

To do this, program RV56LFTP should be included as a job. Parameters must include transportation planning point, completion type, the deleted indicator for displaying the selection screen as well as a selection variant for program RV56LFSL.

Fully automatic transmission of planning requests for generating deliveries is a special case. It should only be applied if a company wishes to plan all its deliveries with an external planning system in transportation but where only one planning system (in other words, one transportation planning point) is available. In this case the function can be activated via a special configuration of message control (more information in Procedure for Transmitting Planning Requests - Automatic Transmission ). Depending on the message control configuration, the message transmission will either take place immediately after posting the delivery or in later collective processing.

Remov Removing Planning Requests

If deliveries should be taken out of the planning system because planning should be either carried out manually, using another system or not at all, the following options can be used.

Explicit Removal from Planning

Explicit removal from planning means taking a delivery out of a planning system without deleting the delivery in R/3. You can remove ( deallocate ) deliveries via transaction VT68 or by using menu path Logistics ® Sales and distribution ® Transportation ® External systems ® Transport. planning ® Plan deliveries.

Once you have entered the delivery document number for the delivery to be removed , a list of all the planning systems that the delivery has been transmitted to will appear. You can select the system and start the process using Execute.

Automatic Removal from Planning by Deleting a Delivery

If a delivery is deleted in R/3, it is then automatically removed from planning in all the planning systems that it has already been transmitted to. This procedure needs no previous configuration.

 

Receipt of Planned Shipments

The receipt of planned shipments in R/3 takes place automatically via the ALE layer mechanisms. Some functions are available within inbound processing and further document processing which affect the transportation planning interface. You must also take into account other attributes that can be influenced by Customizing settings.

Deleting Shipments or Handling Units within a Shipment

Deleting handling units that have been created in a shipment or deleting a whole shipment is not possible in the transportation planning system if a handling unit is not empty, that is, if something has been packed into the handling unit.

If materials have been packed manually into a handling unit in an externally-planned shipment document, they must first be manually unpacked before the planning system can delete the handling unit or the shipment.

 

Automatically Setting ‘Planned’ Status

‘ Planned’ status is automatically set when the system receives an externally-planned shipment document. This happens regardless of whether a planned date has been transmitted to the incoming document or not.

If the planning date is transmitted from an external planning system, this is copied over to the planning date in the shipment document. If a planning date is not transmitted, the planning date in the R/3 document is set to the date of receipt of the external document.

 

Locking Document Status for External Planning Systems

Document status can be set to two values for external planning systems:

• Document modifiable in planning system

• Document not modifiable in planning system

You can set the status of document modifiability in the R/3 shipment document depending on the shipment’s overall status. In R/3 Customizing you can set as of which shipment status (e.g. Start load.) changing the shipment in the planning system is no longer appropriate or permitted.

If the given status is reached or overstepped because R/3 transportation activities were set manually, a fix message will be sent automatically to the transportation planning system to freeze the corresponding shipment document, whereby the shipment document must be set to Do not change in the planning system.

If the given status is overstepped in R/3 transportation activities by resetting the shipment’s overall status, a message is sent to the planning system, which makes it possible to re-release the processing of the shipment document.

Modifiability of Externally-Planned Shipments

Externally planned shipments can be limited in the R/3 System with respect to their ability to be changed. You can set this through Customizing for the planning system. The following settings are possible:

• No planning-relevant changes permitted

• No planning relevant changes permitted, apart from service agent data

• No restrictions on changes