Skip to Content
avatar image
Former Member

Transport Module

Dear Gurus,

Currently i m working on transport Module.

Please tell me in pricing procedure determination- what is meant by service agent procedure group .. whether i need to maintain that service agent procedure in some master data ??

Also in transport module how to get Pricing procedure automatically determined ??

Please let me know alo any report related to excise invoice & shipment document number available in the Std SAP

Please extend ur help on this.

Thanks

Rgds,

Saurabh

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 15, 2007 at 07:53 AM

    Hi,

    Shipmet pricing is determined based on following conditions,

    -Transportation planning point

    -Service agents

    -Shipment cost item

    -Shipping type

    To determine the pricing procedure automatically, you must make the following settings in Customizing:

    Item category determination procedure group

    You must define an item category determination group and assign the corresponding items to this group.

    Service agent determination procedure group

    You must define a service agent determination group and assign the corresponding service agents to this group.

    Shipping type determination procedure group

    You must define a shipping type determination group and assign the corresponding shipping types to this group.

    Assignment by transportation planning point

    You must then assign a valid combination of item category determination group, service agent determination group and shipping type determination group to a pricing procedure for every transportation planning point.

    ---You can get all shipmet documents from VTTK table

    Regards,

    Chandra

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 15, 2007 at 07:55 AM

    dear saurabh

    Purpose

    Transportation is an essential element in the logistics chain. It affects both incoming and outgoing goods. Effective transportation planning and processing ensure that shipments are dispatched without delay and arrive on schedule. Transportation costs play an essential role in the calculation of the price of a product. It is important to keep these transportation costs to a minimum so that the price of a product remains competitive. Efficient transportation planning and processing helps to keep these costs down.

    Integration

    As illustrated in the following graphic, you can use the SAP transportation functions to plan and process:

    • Incoming shipments in Materials Management based on purchase orders and shipping notifications

    • Outbound shipments in Sales and Distribution based on sales orders and deliveries

    The graphic below illustrates this process:

    Transportation planning and processing is based on the shipment document. This document facilitates the flow of information from the shipper to the customer and to any service agents who are involved in the business transaction.

    Features

    The transportation component includes basic transportation processing functions:

    • Transportation planning and shipment completion

    • Shipment costs calculation

    • Shipment costs settlement

    • Shipment costs calculation for individual customers

    • Billing of customer freight

    • Service agent selection

    • Management of means of transport and utilities

    • Follow-up and supervision of shipments

    • Management of shipment costs

    These transportation functions can handle planning and processing for both inbound and outbound shipments. You can control and monitor the entire transportation process from the planning stage to goods issue at your shipping point (for outbound shipments) or vendor location (for inbound shipments), through to goods receipt at the customer location or your plant.

    Other available functions include: shipment costs calculation and settlement with the service agent, transfer to accounting, credit memo creation and invoice verification.

    This documentation describes procedures in outbound shipment processing. Unless specifically stated otherwise, the information here also applies to inbound shipment processing. Differences between the two will be pointed out where necessary.

    For information on creating and processing inbound deliveries, see the Confirmations section of the R/3 Library documentation for Purchasing (MM-PUR).

    Transportation Planning Point

    Definition

    You can now carry out transportation planning and shipment completion using a new organizational unit, the transportation planning point. Basically, the transportation planning point consists of a group of employees responsible for organizing transportation activities. Each shipment is assigned to a specific transportation planning point for transportation planning and shipment completion. You must define the various transportation planning points used in your organization in Customizing for Corporate Structure before they can be used to perform transportation functions. You can define this organizational unit according to your company’s needs, for example, according to geographical location or mode of transport.

    The transportation planning point is assigned to a company code, but is otherwise independent of other organizational units.

    Procedures Valid for Entire Company Codes

    Use

    It is not necessary to assign the transportation planning point to a company code for transportation planning purposes. However, company code assignment is necessary for shipment costing and settlement. Internal offsetting of costs between company codes (one company code takes care of transportation processing for all the firm’s company codes, for example) is presently not available. These must be manually entered in the financial accounting ledgers.

    Prerequisites

    In order for this cross-company-code manual processing to be possible in financial accounting, cost distribution for shipment costs must occur on the shipment cost item level rather than delivery level or delivery item level, since in the latter two cases, the delivery’s company code would be adapted to the transportation planning point’s company code.

    A company’s plant in Japan delivers goods to a plant in Houston. The plant in Japan takes care of the shipment costs until the goods reach the airport in Japan, and the Houston plant pays the rest of the shipment costs (Japan airport  Houston airport  Houston plant).

    The transportation chain with cross-company-code billing looks like this:

    There are a total of three shipments:

    • The first shipment is created by the transportation planning point in Japan and ends at the airport in Japan. Cost distribution occurs on the shipment cost item level.

    • The second and third shipments are created by the transportation planning point in Houston. In both cases, cost distribution occurs on the shipment cost item level.

    Shipment Types

    Definition

    The shipment type contains all the important control features for a shipment, such as the number range, whether the shipment is inbound or outbound, how leg determination is performed, and which leg indicator has been set for a shipment of this type. You can also enter a selection variant for the shipment type. The values defined in the variant appear on the selection screen when you create a shipment document of this type.

    The system supports the following shipment types:

    • Individual shipment

    • Collective shipment

    • Transportation chain

    Individual shipment

    An individual shipment includes

    • One or more deliveries

    • One point of departure

    • One destination

    • One mode of transport

    Collective shipment

    A collective (or milk-run) shipment includes

    • One or more deliveries

    • Several points of departure

    • Several destinations

    • One mode of transport

    Transportation chain

    A transportation chain is useful if you are dealing with deliveries that will be transported using multiple modes of transportation (and are thus processed by different departments at the transportation planning point).

    Transportation Chain

    The department responsible for transportation by land organizes truck shipments and another department organizes ships and their cargo for goods shipment by sea. Each mode of transport (truck and ship) requires individual shipping papers. Each mode of transportation requires separate transportation papers, meaning that you need to create a shipment document for the overland leg and another for the overseas leg of the journey.

    If shipments use more than one mode of transportation, it is a good idea to create a transportation chain. Because you will have a separate shipment document for each mode of transportation, you can maintain separate output, texts, statuses, and so on.

    Example for using a transportation chain

    At shipping points 0001 and 0002 in Germany, a large number of deliveries are to be sent to customers in the United States by the beginning of December. You and your customers agreed that part of the shipment be sent carriage paid and the other part carriage, insurance, freight paid to (CIF) New York only (meaning that the end customer must pay carriage, insurance and freight from New York to the final destination).

    The goods are to be transported by land within Germany, by sea from Hamburg to New York, and by land again in the United States. It is, of course, possible to document the entire process in a shipment document. However, problems can arise if certain parts of the shipment functions are used:

    • For instance, data on the shipment status always refers to the entire shipment document (for example, the status "Loading finished"). However, in this example loading takes place several times.

    • For the same reason, an assignment of dates and texts to a handling unit is difficult because these can change within the shipment document. The very definition of a handling unit is in itself problematic.

    • Output to be created in combination with the shipment document contains all data for the entire shipment document. When the truck driver leaves the shipping point, his printout also contains data that refers to the ship. This is unnecessary and a nuisance. Processing several required preliminary legs at different times also requires that output be printed at different times.

    In cases like this, it makes more sense to use a transportation chain in which deliveries are passed on in a series of different shipments. In the above example, you would create several shipment documents in the system: ten preliminary leg shipments by truck, one main leg by ship, and if necessary, eight subsequent legs by truck again. That way, you avoid the problem of assigning deadlines, output, or texts to the packaging material.

    With that in mind, you might put together your transportation chain like this:

    1. Create a main leg

    At transportation planning point 0001, you create a main leg shipment for all deliveries to be sent by ship from Hamburg to New York City at the beginning of December. There should be a special shipment type set for this set in Customizing. This could include the following settings:

    Set the leg indicator field for the shipment header to Main leg. The system will recognize that this shipment must be linked to other shipments.

    The leg determination type for this shipment type should be ‘‘this means that no automatic leg determination will be carried out. This is reasonable since the Hamburg-to-New York leg does not include any points of departure or destinations from the delivery (however, this data will be taken into account during leg determination).

    Route determination resulting in the Hamburg-to-New York route may have already been carried out in the delivery. If you want to copy this route automatically into the main leg shipment, you can specify in Customizing that routes must be copied into the shipment document. Copying starts as soon as you set the Planned status in the shipment document.(Note that the route in the deliveries must be unique.) At the same time, the service agent can also be copied automatically from the delivery provided you have made the appropriate settings in Customizing and that the same service agent has been assigned to the deliveries.

    When the deliveries were created, they were given transportation planning status A, meaning they were ready for transportation planning. Now, after creating the main leg shipment, these deliveries have transportation planning status B, meaning that they have been partially planned (since a main leg shipment needs preliminary and possibly subsequent legs).

    2. Create preliminary legs

    The preliminary leg shipments that are used to send the goods from shipping points 0001 and 0002 to the ship in Hamburg can be organized much faster than the ship itself, which is why they are planned at this time. You must now combine all deliveries in the main leg shipment into one or more preliminary leg shipments. You can do this in the Create Shipment transaction.

    To do this, you must select all deliveries in the main leg shipment. The transportation planning status of the delivery may be helpful in determining which deliveries are in the main leg shipment since their status is now set to B instead of A. Of course, this is not sufficient as a single selection criterion. He can enter further selection criteria that are used during delivery selection for the main leg. This may be impractical since you may not now what the selection criteria were or too many deliveries may be selected.

    Therefore, it is better to specify the shipment number of the corresponding main leg shipment in the Reference to line when selecting deliveries. If you do not know the number, press F4 and a selection screen will appear. In this case, a further selection screen for shipment number selection appears. On this screen, you can specify the person who created the shipment document, the point of departure, and the date in order to determine the number of the main leg shipment.

    You create shipments using the worklist you defined. If each delivery corresponds to exactly one truckload, the planner can call up the function Edit Automatic planning One dlv. one shipment, which creates a separate shipment for each delivery.

    You should use the following settings:

    o Set the leg indicator to preliminary leg.

    o Set the leg determination type to 1 (leg determination according to pick-up sequence and itinerary).

    o Do not copy the route from the delivery. It may be a good idea to copy the service agent.

    When the Planned status is set, leg determination begins, but the route is not copied from the deliveries. It will determine the pick-up sequence. In addition, the system suggests Hamburg as destination since the deliveries are part of a main leg shipment that runs from Hamburg to New York.

    When the shipment is saved, the system updates the delivery status. The status for the carriage paid deliveries remains B (partially planned), since the second part of the Incoterm was left blank and the system assumes that a subsequent leg is required. The status of the deliveries with CIF New York is set to C (completely planned) since the second part of the Incoterm has been specified and the system assumes that a subsequent leg is not necessary.

    3. Create subsequent legs

    You create subsequent legs the same way you create preliminary legs. Use these settings:

    o Set the leg indicator to subsequent leg.

    o Use category 1 for leg determination.

    o Do not copy the route from the deliveries.

    In order to create these shipments, search for deliveries with a transportation planning status of B. The system then finds only those deliveries for which a subsequent leg is to be created. If the Planned status is set, it also carries out leg determination. The system automatically suggests ‘New York’ as a point of departure, since the main leg shipment ends in New York. The sequence in which the goods are delivered (itinerary) is determined by the sequence in which the deliveries are displayed on the screen. If the subsequent leg shipments are saved, the transportation planning status of the corresponding deliveries is set to C (completely planned) since these deliveries now have preliminary, main, and subsequent legs.

    Following these steps ensures that every delivery is included in the transportation chain. In the example, there are ten preliminary leg shipments to Hamburg followed by a main leg shipment and eight possible subsequent leg shipments in the United States. In this way, a group of deliveries forms a network of shipments.

    4. Monitor the transportation chain

    In order to monitor the shipments, choose Environment Transportation info Shipment list or Environment Transportation info Transportat.network depending on whether you are processing orders, deliveries, or shipments. Worklists for transportation planning and processing may also provide an overview. To generate a worklist, enter one of the shipment numbers that make up the transportation network in the Reference to line. The system will then select all shipment documents in the network

    Shipment document

    Definition

    The shipping document is the central element of transportation planning and shipment completion. It contains all the information necessary for carrying out transportation.

    Use

    You create shipment documents using a worklist. Different types of shipment documents have been defined to enable you to reflect in the system the various forms of transportation used in your organization.

    For example, you use the individual shipment document to plan and process the transportation of goods from one location to another. You use the collective shipment to move goods from one or more points of departure to one or more destinations. Separate document types deal with inbound and outbound shipments.

    You can use shipment documents to:

    • Combine deliveries into one inbound or outbound shipment

    • Specify shipment stages

    o Legs

    o border crossing points

    o load transfer points

    • Assign goods to handling units

    • Assign service agents

    • Specify planned transportation deadlines

    • Record actual transportation deadlines

    • Specify output required for transportation (such as shipping papers or EDI messages)

    • Define transport-relevant texts

    Information in the Shipment Document

    Use

    You can record the following information in the shipment document:

    • Means of transport

    • Service agents

    • Deadlines

    • Status

    • Tendering status

    • Route

    • Texts

    • Output

    • Dangerous goods

    Features

    Means of transport

    The means of transport necessary for a shipment is reflected in the system as a handling unit. These handling units contain information about tare weight and -volume of the means of transport as well as the weight of the packed handling unit. Information about the country providing the means of transport, details about the driver and travel time are also included in these handling units. Handling units that have already been created for delivery items are copied into the shipment document where they can be packed further, if necessary. Delivery items that have only been partially packed or not packed at all can be packed in the shipment documents.

    See also:

    Packing in the Shipment Document

    Service agents

    You can store information about the service agents (such as forwarding agents or customs agents) who are involved in the transportation process. You can record this information at the header or stage level of the shipment document.

    See also:

    Assigning Service Agents in the Shipment Document

    Deadlines

    The time required for organizing and performing the various transportation activities is stored as planned and actual deadlines in the shipment document. This information can be used for monitoring and analysis purposes.

    See also:

    Maintaining Planned and Actual Deadlines in the Shipment Document

    Transfer of Delivery Dates to Shipment

    Status

    Once you have completed the planning activities for a shipment document, you can set the planned status. As soon as you set this status, you can no longer carry out planning activities for this shipment document (remove deliveries from the document or move deliveries within the document, for example). Leg determination is carried out automatically. You can define which activities take place when you set the status in the Activity Profiles section.

    A traffic light icon indicates the overall status of the shipment document. The icon can be interpreted as follows:

    No traffic light:

    No planning activities have been performed

    Red light:

    Transportation planning is complete

    Yellow light:

    Loading at the plant has either started or is complete

    Green light:

    Shipment has been processed and is en route or has arrived

    See also:

    Maintaining Status in the Shipment Document

    Tendering status

    The tendering status describes the current status of a shipment with respect to negotiations with a forwarding agent through the Internet.

    See also:

    Requesting Tenders for Service Agents Through the Internet

    Route

    If the route and the forwarding agent are the same in all deliveries, they are copied from the deliveries into the shipment document when you set the status to Planned.

    Country-specific restrictions with respect to total weight of the shipment on a particular route require recording the restriction already at the route level. This upper level can be specified at route level and is then taken into consideration during shipment processing. If the allowed total weight is exceeded during delivery assignment to the shipment, the system issues a warning message. The shipment can then be changed accordingly. The fields are displayed on the planning screen.

    During order processing and delivery processing, this check is not taken into consideration.

    Further transportation-relevant information is copied into the shipment document if you define the Copying Routines in the Implementation Guide.

    Texts

    Additional information that could help the transportation process to run smoothly can be entered as text at header level in the shipment document. This information can be accessed by all business partners involved in the process. Shipment text types are defined in Customizing and assigned to text determination procedures. Text determination procedures are defined in the shipment document type.

    See also:

    Maintaining Texts in the Shipment Document

    Output

    Output processing is performed just as it is in other areas of the Sales and Distribution module: using the condition technique. The types of output that have been set in Customizing for transportation and for which you have created condition records appear in the shipment document and apply to the entire document. The output type ALTR has been defined for transportation in the standard SAP System. You can change this output type to suit your needs.

    See also:

    Output Determination in the Shipment Document

    Dangerous goods

    To conform to the legal requirements with respect to the transportation of dangerous goods, it is important that you check in the shipment document whether transportation of such goods is actually allowed.

    Here different dangerous goods checks can run either automatically or through manual request. For example, you can check whether the transportation of certain materials is allowed in certain modes of transport. In this way, you can prevent deliveries or shipments from leaving the company when they are not suited for transport, according to dangerous goods regulations. Also, you can create dangerous goods documents using the respective dangerous goods data.

    See also:

    Dangerous Goods Check in the Shipment

    Copying Information Relevant for Transportation

    Use

    When you create shipments, you can use information relevant for transportation as selection criteria. For example, you can group together outbound deliveries with means-of-transport type "Truck" and means of transport "Small truck" into one shipment. In sales orders and/or deliveries, you can specify that the following information is relevant for transportation:

    Means of transport

    Shipping type

    Type of means of transport

    Special processing

    Integration

    In order to copy proposals for dates and times from the delivery, you must create a connection between the shipment dates and delivery dates. Copy routines serve this purpose.

    Prerequisites

    The system uses the copy routine to copy data from sales orders into deliveries and then into shipments. In order for the system to do this, you must first carry out the following activities in the Implementation Guide (IMG):

    Specify copy control for deliveries

    Define shipment types

    Features

    Information relevant for transportation is copied from the order into the header of the outbound delivery, and thus supplies split criteria for outbound deliveries. For example, two order items with different shipping types, means of transport or means-of-transport types cannot be combined into the same outbound delivery.

    However, information can be copied from the outbound deliveries into the shipment, provided it is unique data. You create a handling unit in the shipment for the means of transport (likewise only if this is unique). The copying takes place when you set the status "Planned". Here you must store an appropriate copy routine in Customizing for the shipment type.

    The system also checks the capacity of the mode of transport in the delivery. If this capacity is exceeded, you will receive a warning message.

    Since the means of transport can also be specified on the Pack screen, the means of transport entries in the sales order, delivery header and the corresponding packing information could vary. Changes made on the Pack screen have no effect on the transportation-relevant information in sales orders and deliveries.

    Shipment Outputs

    Purpose

    In addition to printing and faxing, electronic data exchange is becoming increasingly important as a method of communicating transportation data. Senders (shippers) transmit their shipping orders and transportation information to their service agents (forwarding agents, ship owners, customs agents). The service agents organize the transportation process and ensure that it is carried out smoothly. A logistics transportation chain involving multiple modes of transport and service agents often occurs during the shipment. To ensure efficiency in such a situation, it is especially important to get all necessary information to all parties involved at the earliest possible point in the process.

    Process Flow

    Sample process flow for electronic data exchange:

    Shipping Inbound Processing

    The shipper sends the forwarding agent a partially- or completely planned shipment (shipping order). The forwarding agent receives the transportation requests and assumes responsibility for planning the shipment details.

    The forwarding agent sends information about the completely planned shipments back to the shipper. The vendor receives the completely planned shipments from the forwarding agent.

    The shipper or forwarding agent informs the customer about the upcoming shipment (shipment notification). The customer receives information about the upcoming shipment.

    For more information on output control, see the Output section in the online Implementation Guide.

    You can find more information about output administration in Working with Output in Sales and Distribution.

    Output Control

    Use

    You can use output control to automate either messages or subsequent processing of partner-specific messages. The application uses interfaces that were predefined in Customizing for conditions to call up output control.

    You can use these interfaces to describe different constellations of data and the processing methods of your choice. If one of these data constellations occurs in the application, it triggers the corresponding processing method (either sy n ch ron ously or asynchronously). You can define processing methods in many different ways (as print output or as a shipping IDoc for EDI, for example).

    Prerequisites

    The Logistics Execution application always uses output control for issuing output. You can maintain settings for output control in Customizing in Message control activity.

    Features

    The condition technique is used in the SAP System for formulating data constellation conditions. If the current application data matches one of the conditions defined in Customizing, output determination was successful and an output proposal is generated. You can then change this proposal ( edit) and the output will be processed either immediately or at a specified time. The output's processing status is saved in a status record and a processing log is created.

    See also:

    Message Control Structure

    Output control only supports certain transmission media. For more information, see Transmission media.

    Activities

    In Message Control Customizing, you can define rules according to which the system accesses individual condition records.

    You can define concrete messages as condition records in the application: Message definition in the application.

    Determining Output in the Shipment Document

    Use

    The output determination function enables you to perform tasks for shipping and transportation output for delivery and transportation processing with your customers and within your company. You can create shipment output and output for handling units. Staff members in your company can send messages. For example, the system automatically finds the message that a bill of lading is to be printed.

    Integration

    The output control checks whether the application data matches the condition records (that were defined in Customizing). If this is the case, one or several messages are "found", and they can then be processed (for example, sent electronically). The condition records are searched for during output determination on the basis of a predefined hierarchy.

    The Output determination function is used in output control. You can use the output control function to exchange information with internal and external partners. Output control consists of the following functions that are described in the cross-application documentation CA – Output Control:

    Output Determination

    Output Processing

    Status Management

    Prerequisites

    For output determination, the condition elements and condition records need to be defined since the output determination runs using the condition technique.

    In Customizing, you can define the conditions in which the output types you define will be selected. For more information on output control, see the Output section of the Implementation Guide.

    Features

    The system can propose output automatically for a document. You can change this output in the document.

    Output determination occurs when:

    Accessing the output screen during shipment processing

    Saving a shipment document that is new or has been changed

    See also:

    For more information on output, refer to the following documentation:

    Application Documentation

    Basis BC – SAP Communication: Configuration

    Cross-application functions Output Control

    SAP Business Workflow

    You will find Customizing settings and examples in the above documentation.

    Example

    Bill of lading

    Output determination starts in V7STRA with output type CMR1 and the assigned access sequence.

    The access sequence defines the fields with which the key for the condition table is read. (for example, condition table B017: shipment type of the shipment is read)

    If the condition record is found, the system proposes an output with the output attributes found in the table.

    The output proposal (possibly not yet processed) is stored after the document is posted as an output status record in the NAST table.

    Outbound EDI messages

    Use

    Shipment documents are normally sent in one of the following two situations:

    The shipper sends the forwarding agent a partially- or completely-planned shipment (transfer order).

    The shipper or forwarding agent informs the customer about the upcoming shipment (shipment notification).

    Prerequisites

    You need to create an output type that you can use to send the shipment document per Electronic Data Interchange (EDI). Output type SEDI is provided for this purpose. You can also make a copy of this output type and tailor it to your needs, if necessary. The transmission medium must be set to 6 (EDI).

    The following condition components must be maintained:

    Condition component Value

    Access sequence 0001

    Output type SEDI (or copy of SEDI)

    Schema V7STRA, for example

    Application V7

    Processing routine RSNASTED program, FORM-routine EDI-PROCESSING

    General data Select Access to conditions and Multiple sending of output. Leave all other fields blank.

    Time 3 (explicit request), as an example

    Transmission medium 6

    Partner function CR (Carrier) or SH (Ship-to party)

    IDoc interface

    You must also enter the following values for outbound partner profiles and any additional outbound parameters under message control.

    Field Value

    Output type SHPMNT or SHPADV

    Partner type LI (vendor/creditor) or KU (customer)

    Partner function CR (Carrier) or SH (Ship-to party)

    Port SUBSYSTEM

    Output mode Collect IDocs, for example

    Basic type SHPMNT03

    Application V7

    Output type SEDI, or your modified copy of SEDI

    Process code SHPM

    Scenario: The shipper sends the forwarding agent a partially- or completely-planned shipment (transfer order).

    You create a shipment document that is either partially or fully planned (depending on whether the transportation planning details will be carried out by the forwarding agent or if you do it yourself).

    Depending on what point in the process the message determination is set to take place, the EDI is triggered immediately after posting (time 4) or when explicitly requested (time 3).

    Scenario: The shipper or forwarding agent informs the customer about the upcoming shipment (shipment notification).

    You have a fully-planned shipment document (that you have created and planned yourself, or that the forwarding agent has planned for you).

    Depending on what point in the process the message determination is set to take place, the EDI is triggered immediately after posting (time 4) or when explicitly requested (time 3).

    To improve performance, you should make sure that when you use IDocs for special purposes that you only generate segments that include the data you need. You can hide certain segments by using a reduction technique.

    To make the necessary settings in Customizing, choose Cross-Application Components  Distribution (ALE)  Processing IDocs  Set up segment filtering.

    Inbound EDI messages

    Use

    You can create or change shipment using EDI output.

    In this way, the following tasks are possible:

    Collective Goods Traffic

    The forwarding agent picks up deliveries from the vendor during the preliminary leg. Then the agent puts together the shipment for the main leg and passes on this information to the customer as a shipment notification. Now the customer can easily post a goods issue for the entire shipment (more precisely, for the deliveries it contains).

    Transportation planning

    A vendor supplies the forwarding agent with the outbound deliveries as transfer requirements. The forwarding agent plans the shipment and informs the vendor of the result, who can then start the appropriate activities for goods issue of the respective outbound deliveries. To create shipments at the customer site, you can use message SHPADV (shipment message or shipment notification). To create or change your own shipments, use message SHPMNT. Both messages are based on IDoc type SHPMNT03; processing is executed through process code SHPM. You can maintain these parameters within the EDI partner profile. For this purpose, select Tools ->Business Communication -> IDoc -> Partner profile.

    Output for deadline and status

    The forwarding agent confirms the planned or actual deadline via EDI, including the status for the end of the shipment with the respective time.

    The inbound deliveries to which the shipment refers must exist in the system. The reference is made through the delivery number of the vendor (collective goods traffic) or directly (transportation planning). Therefore, it is necessary to notify the customer of the deliveries where collective goods traffic is concerned. You can do this using the DESADV (shipping notification) message. It is not possible to create deliveries in the initial processing of shipments, as required for direct shipments. Also, no change is made to the delivery (with effects on material planning) if there is a change in the shipment (planned arrival date, for example).

    Prerequisites

    The deliveries that the shipment refers to must exist in the receiving system.

    Features

    Control of IDoc Receipt SHPMNT03

    You can control the processing of the receipt of IDoc SHPMNT03 using the specifications in the segment E1EDT18. For this purpose, you can use the following E1EDT18-QUALF qualifiers:

    QUALF = ORI Shipment document is created

    QUALF = CHA Shipment document is changed

    QUALF = PID Specification of an identification field for the shipment document.

    Processing and copy control

    If you use the qualifier ORI or CHA, you can control the data transfer strategy from the IDoc into the shipment document using the parameter field. Basically, there are four strategies which are indicated by the first character in the E1EDT18-PARAM field. The respective marker characters are in the second character in the E1EDT18-PARAM field:

    0 IDoc fields are always copied; empty ID fields cause document fields to be deleted (standard case; will be processed if no specification is made).

    1 IDoc fields are only copied if they are empty

    2 Similar to strategy 0, but an IDoc field is not transferred if it is filled completely with the marker character.

    3 Similar to strategy 1, but an IDoc field is not transferred if it is filled completely with the marker character.

    Example of segment E1EDT18:

    QUALF PARAM

    ORI 2! Copy all fields, except those containing a !

    CHA 3% Copy fields that are filled in and delete fields with %%%%... in the document.

    Control of identification

    You can control the identification link between the IDoc and the shipment document in segment E1EDT18 with qualifier PID, which can appear up to three times per IDoc.

    In most day-to-day cases, the PID qualifier is not present. In this case, the E1EDT20-TKNUM field is copied into VTTK-EXTI1 during creation. The system assigns the shipment number VTTK-TKNUM internally. If there is a change, the system searches for a suitable shipment document using the following criteria:

    E1EDT20-TKNUM = VTTK-EXTI1

    E1ADRE4-EXTEND_D = VTTK-TDLNR (where you must have E1ADRE4-EXTEND_Q = 300)

    If PID qualifiers are specified in E1EDT18, no data is copied from TKNUM to EXTI1.

    If the shipment number is to have external number assignment, you can specify the shipment number as a primary identification with E1EDT18-QUALF = PID and E1EDT18-PARAM = TKNUM. The shipment is created using VTTK-TKNUM = E1EDT20-TKNUM, and is searched for with the same condition if you want to change it.

    You can use the IDoc fields EXTI1, EXTI2, and TKNUM for the identification.

    Examples of segment E1EDT18:

    QUALF PARAM Function for creating Function for changing

    None None Copy E1EDT20-TKNUM to VTTK-EXTI1

    Internal number assignment Search for shipment with VTTK-EXTI1 = E1EDT20-TKNUM and VTTK-TDLNR = E1ADRE4-EXTEND_D

    PID TKNUM External number assignment VTTK-TKNUM = E1EDT20-TKNUM Search with VTTK-TKNUM = E1EDT20-TKNUM

    PID EXTI1 Internal number assignment Search with VTTK-EXTI1 = E1EDT20-EXTI1

    PID

    PID TKNUM

    EXTI2 External number assignment Search with VTTK-TKNUM = E1EDT20-TKNUM and VTTK-EXTI2 = E1EDT20-EXTI2

    PID

    PID EXTI1

    EXTI2 Internal number assignment Search with VTTK-EXTI1 = E1EDT20-EXTI1 and VTTK-EXTI2 = E1EDT20-EXTI2

    Activities

    You must also enter the following values for outbound partner profiles and any additional outbound parameters under message control.

    Field Value

    Output type SHPMNT or SHPADV

    Partner type LI (vendor/creditor)

    Basic type SHPMNT03

    Application V7

    Output type SEDI, or your modified copy of SEDI

    Process code SHPM

    Report: Output for Shipments

    Use

    You can use this report to create a list of outputs that meet your selection criteria. You can specify whether your list should include outputs related to shipments, deliveries, handling units, or invoices. You can then display or process the output of your choice from the list.

    Features

    You can enter shipment numbers, planned shipment completion dates, transportation planning points or partners as selection criteria. You can also specify that you want to see only those outputs relating to shipments or deliveries, for example. Use output type, transmission medium and processing mode to further limit the search.

    From the list of outputs that appears, you can start immediate processing, make changes to the processing parameters, or display either the output itself or its corresponding log. The log records how often the output is processed or printed.

    This report only lists outputs that have been found via output determination or defined manually in the selected documents (shipments, deliveries, or invoices, for example). Output determination is not carried out in this report.

    Freight Codes and Freight Code Sets; Freight Classes

    Definition

    Forwarding agents or railroads use freight codes (and sets of freight codes) to classify the goods they transport. Freight codes are specified in the transportation papers, and some are specific to rail or road transportation.

    These are compiled in freight code sets published by forwarding agents and the railroad authorities and are used specifically when referring to rail or road transport. Specific freight codes are defined in each freight code set.

    Freight code Description

    4001 Methyl alcohol

    4002 Glycol

    4003 Alcohol

    4004 Formaldehyde

    Freight classes are made up of one or more freight codes and are one of the criteria for shipment costing.

    Determining the Freight Code

    Process Flow

    Determining the freight code is carried out in two steps:

    Step 1

    Automatic freight code determination uses the following criteria:

    Country of origin

    Shipping type (truck, rail, etc.)

    Forwarding agent (forwarding agent freight group in the vendor master)

    If an external transportation planning system is being used, then the freight code set can also be defined by the route.

    Step 2

    Automatic freight code determination uses the following criteria:

    Freight code set

    Material (material freight group in the material master)

    This allows you to determine the freight codes of all materials in a shipment.

    Freight classes

    Definition

    A freight class is a group of freight codes used to calculate shipment costs.

    Use

    The freight class can be used as one of the criteria for figuring shipment costs. For example, you could enter condition records for freight rates that specifically refer to a combination of tariff zone and freight class. The freight code is used if the material that is being shipped should figure into the shipment costs.

    Integration

    One or more freight codes are assigned to a freight class within a freight code set.

    The following illustration is an example of how freight code set, freight code and freight class are interrelated.

    Editing Shipment Lists

    There are various functions which you can perform in both the transportation planning and shipment completion worklists to help you locate the documents you want to edit.

    Transportation List Views

    To switch from the normal to the status view of the transportation list and vice versa, choose Edit  Change view.

    Search Function

    To find documents with a particular characteristic (for example, you want to find all documents with a specific forwarding agent), proceed as follows:

    Choose Edit  Find  Find delivery.

    The screen Delivery selection view appears where you can specify characteristics of the delivery you are looking for.

    Enter one or more delivery characteristics.

    Choose Program Execute.

    The system finds all deliveries that match your selection criteria.

    Sort Function

    You can navigate within the transportation list much easier by sorting it according to criteria such as shipment type or planned loading date. To do this, proceed as follows:

    Place your cursor on the column heading according to which you want to sort your list.

    Choose Edit  Sort Ascending order to sort the list in ascending order. If you want to sort the list in descending order, choose Edit  Sort  Descending.

    The system sorts the list based on the column header on which you placed your cursor and, depending on the menu option you select, in either descending or ascending order.

    List Viewer Functions

    Some lists are managed with a special tool, the ABAP List Viewer. The List Viewer features various functions that you can use to tailor the list to your needs. This tool allows you to make settings such as which columns appear in what order, for example. For more information, see ABAP List Viewer.

    Searching for Deliveries in a Transportation List

    To locate specific deliveries within a transportation list, proceed as follows:

    Choose Edit  Find  Find delivery.

    Enter your selection criteria (for example, the number of the ship-to party).

    Choose Program Execute.

    The system issues a list of all the shipment documents in the list which contain deliveries that match your selection criteria.

    Transportation Planning

    Use

    Transportation planning involves all the activities that must be performed before the shipment leaves the shipping point. These activities include:

    Acquiring the services of a forwarding agent

    Organizing the means of transport

    Specifying the route for the shipment

    Defining the stages for covering this route in the most efficient way.

    There are different types of shipment document types to deal with the various forms of transportation (for example, individual shipments or collective shipments). The shipment documents are used as a basis for carrying out transportation planning. This includes, among other things, the execution of the above activities.

    Prerequisites

    Before you can carry out transportation planning, the following requirements must be met:

    For outbound shipments

    Specify in Customizing for Transportation that a delivery type for the shipping notification is relevant for transportation planning and shipment completion.

    Specify a route in the deliveries.

    Specify in Customizing for Transportation that the routes in the deliveries are relevant for transportation planning and shipment completion.

    Make sure the ShpmtBlReason (shipment blocking reason) field is blank. You can find this field in the delivery header on the transportation screen.

    Once these requirements have been met, the system automatically sets the transportation planning status to A (Not yet planned) in the Trns.plan.status field in the delivery header.

    For inbound shipments

    Specify in Customizing for Transportation that a delivery type for the inbound delivery is relevant for transportation planning and shipment completion.

    Assign all items to the same plant in the inbound delivery. The system carries out a corresponding check.

    Features

    There are different types of worklists and lists you can use to perform various tasks in transportation planning:

    Shipment list

    You use the shipment list to establish which inbound or outbound deliveries are due for shipment. After you have created the list, you can

    – Create the necessary shipment documents for particular inbound or outbound deliveries

    – Specify the order in which the inbound or outbound deliveries (or shipment items) are to be delivered

    Transportation planning list

    When you are creating the shipment due list, you do not usually have all the information you need to complete transportation planning. For instance, you probably do not know which forwarding agent will take care of goods shipment at this stage. You could also decide not to finish the entire planning for a shipment in the shipment list because the capacity for this shipment is not yet used to the full. Once you have the information you require or once there are enough deliveries to fill the shipment, you can use the transportation-planning list to locate these documents and complete transportation planning.

    This list contains shipment documents for which planning activities still have to be completed and which match selection criteria that you define. You can use the list as a basis for performing transportation planning activities, such as organizing a means of transport, scheduling loading activities and acquiring the services of forwarding agents.

    Besides this "normal" transportation planning list, there are additional lists that you can use to find shipments according to certain categories. For instance, in the Utilization list, you could enter the shipment’s degree of utilization as a percent, according to weight and volume, as one of the selection criteria.

    Activities

    You must first determine which inbound or outbound deliveries are due for transport. A worklist for this purpose is created using selection criteria. Deliveries or outbound deliveries are then assigned automatically or manually to shipment documents. Relevant data, such as shipping points and destinations, is then used to determine the route and to break it into stages.

    The route in the delivery can be used as one of the criteria for selecting deliveries due for shipment. It is not, however, copied into the shipment document. More information is available in the following sections.

    You can make the appropriate settings in Customizing so that routes and service agents are copied from the deliveries into the shipment documents.

    Using the Route as Selection Criterion

    The route in the delivery can represent:

    One or more legs

    A link between the point of departure and the destination

    The destination region

    The route in the shipment document differs from the route in the delivery. The following examples should illustrate the difference between a route in the delivery and a route in the shipment document.

    Example of a route as a link between departure and destination locations

    The following graphic shows the route as a link between the point of departure and the destination.

    In the delivery document, the route NA indicates that both deliveries are to be transported across the North Atlantic.

    During transportation planning, you select all deliveries with the route NA and then look for a ship that can transport the deliveries at the required time. You find a ship that sails from Antwerp to New York and enter the route NA1 in the shipment document header.

    Example of a route as a target area:

    Routes can also be destination regions. The following graphic shows routes R5, R6, R7, and so on as destination regions.

    During transportation planning, you select all deliveries with route R5. You notice that there is still room in the truck. To make use of this capacity, the deliveries with route R6 are selected as well.

    Creating Shipments

    Purpose

    When you create shipments, you can choose deliveries according to certain selection criteria and then assign them to the new shipment.

    On the overview screen you can, for example, assign deliveries to the shipment manually or automatically, or also remove deliveries from the shipments. On the selection screen that is within the overview screen you can also enter selection criteria for the relevant deliveries or inbound deliveries.

    Process Flow

    1. Activities on the Selection Screen

    On the selection screen, you can enter selection criteria for the documents (inbound or outbound deliveries) that you want to assign to a shipment. You define the selection criteria that are displayed on the selection screen beforehand. You can use selection variants to specify these criteria. On the selection screen, you specify whether you want the documents due for shipment to be assigned automatically to a shipment document or whether you want to assign them manually once the shipment has been created. There are separate selection screens for inbound and outbound shipments. The selection screen for creating an inbound shipment contains, for example, the selection criteria Vendor and Destination point: Plant; in the case of an outbound shipment, the criteria are Ordering party and Destination point: Shipping point.

    2. Activities on the Selection Screen

    The overview screen is divided into two sections: One section contains one or several shipment documents, and the other section lists the deliveries that have not yet been assigned to shipment documents. If the documents have not been assigned automatically to a shipment document, you can do this manually on the overview screen. You can also create new shipment documents and move shipment items (inbound or outbound deliveries) within a shipment or from one shipment to another. In addition, you can remove shipment items from the shipment if, for example, you run out of room on a truck. If you decide that you do have the capacity to select additional deliveries or inbound deliveries for additional shipments, you can create a new shipment from the overview screen.

    Two views are possible: For example, one view displays the address of the ship-to party, and the other displays the name of the ship-to party. Different data is made available for shipments and shipment items (delivery, inbound delivery).

    The settings can be changed through trees and table controls.

    You cannot place outbound deliveries and inbound deliveries together in the same shipment document. Nor is it possible to assign Items from a delivery or an inbound delivery to different shipment documents. You must decide at the delivery stage whether order items can be shipped together in one delivery and therefore require only one shipment.

    See also:

    Creating Shipment Worklist

    Shipment Stages

    Definition

    Stages contain information about the geographical factors for a shipment. In addition to their other functions, stages can also be the basis for calculation of shipment costs. Shipment stages can include:

    Legs

    A beginning point and end point is defined. For example, you can define main, preliminary, and subsequent legs.

    Load transfer points

    The point where a shipment is unloaded from one means of transport and loaded onto another.

    Border crossing points

    The point where a shipment crosses the border.

    The various types of shipment stages are illustrated in the following figure:

    Use

    The following can be beginning points or end points:

    Transportation connection point (train station or port, for example)

    Shipping point (or loading point)

    Plant (or storage location)

    • Customer location (may include customer’s unloading point)

    • Vendor

    • Freely-definable address

    It is also possible to record other information about beginning or end points:

    • Warehouse number/dock door

    • Additional info, can be any text you choose (quay 17, for example)

    If reference to a customer, shipping point, etc. is made in Customizing in the definition of a transportation connection point, that reference is automatically copied. This reference cannot be changed in the document since it was copied from the transportation connection point.

    You can display the address of each point by choosing Address. If you are in change mode, you can make any necessary changes to the address. If you make changes to the address, the system simply creates a different address in the current shipment document.

    Load transfer points can be defined the same way as beginning or end points of a leg. This means that it is possible to create a load transfer point at a customer or vendor address. If a transportation connection point is to serve as a location entry, however, it must have the corresponding characteristic Load transfer point in Customizing.

    You can only use transportation connection points for border crossing points. These must already be set up in Customizing with the Border crossing point attribute.

    Certain rules must be followed when defining a point in a shipment stage (a customer and a shipping point may not be entered at the same time, for example). You can find these rules in the Creating Shipment Stages Manually section.

    You can create stages manually in the shipment document.

    You can, however, use various functions to simplify or automate the entries:

    • Entering a route in the shipment header. The stages defined in Customizing for the route are then transferred to the shipment document. You can control which stages are transferred, if any.

    • Using the Leg determination function. Leg determination is a mechanism that generates stages. The determination is based on simple rules. It uses delivery information that is relevant for shipment in order to generate stages. (No optimization is involved here.)

    See also:

    Automatic Leg Determination

    By combining various control parameters for the transfer of the routes with leg determination, you can automatically generate leg scenarios (either fully or partially).

    rewards if it helps

    siva

    Add comment
    10|10000 characters needed characters exceeded