SAP ABAP Data Element RV56GN_HLP (Functioning of collective processing for shipments)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-BF (Application Component) Basic Functions
     ⤷ VTR (Package) SD R/3 transport processing
Basic Data
Data Element RV56GN_HLP
Short Description Functioning of collective processing for shipments  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CHAR01    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 6 Method 
Medium 14 Method 
Long 14 Method 
Heading 0   
Documentation

Functioning of the collective processing for shipments (VT04).

On the selection screen of this report (RV56TRGN), you define how the collective processing, which works through the work list for shipments. is to be executed.

You can store the input on this screen as a variant in order to, for example, start this report in the background. The selection variants for this report are identified also as a planning profile and are used in the planning proposal (usable in the creation of shipments) or in freight information in the order.

The screen is divided into five main sections:

  • Default settings
  • Select deliveries
  • Create shipments
  • Save created shipments
  • Log

These are explained in more detail below.

Default settings:

In this section you specify whether you want to create incoming or outgoing shipments.
This is an important setting as it controls which selection variants can be used to select deliveries (for example, a variant created for selecting incoming deliveries cannot be used for outgoing shipments).

Select deliveries:

In this section you can select the deliveries you want to process in this collective processing run.
To do this, you can enter the name of a selection variant that you have created with transaction VT01, for example. Enter the name of the selection variant in this field or select one using F4 help. You can display and modify this variant by choosing [Maintn] to the right of the field.
You can also create a new variant. To do this, enter the name of the variant you want to create and choose [Maintn].

After you have chosen [Maintn], the system displays the selection screen where you can select the deliveries. On this screen you can enter the criteria for selecting the deliveries (for more information see Selecting deliveries).
For example, you can specify on this screen that you want to select all deliveries that use route '000001' (northern route) or '000002' (western route).

The 'Selection variant' field is a required field and you always have to enter a value here.

Create shipments:

In this section you define the rules for allocating the deliveries selected to the shipments and the data to be included in the shipment documents created.

As in the 'Selection variant' field in the 'Select deliveries' section, you can enter the name of a variant in the 'Grouping criteria' field (or select one using F4) that defines the rules for grouping deliveries for shipments.
For example, you can specify that you want to group all deliveries into one shipment that use the same shipping point and the same route, that you want to sort these deliveries based on the postal code of the ship-to party address, and that the maximum weight of the shipment may not exceed 30 tons (for more information see Grouping criteria).

The 'Grouping criteria' field is optional. If you do not enter a value here, all selected deliveries will be allocated to one shipment.

You use the next field, 'Data and options', to specify the data you want to include in the shipment documents created (transportation planning point, shipment type, service agent, route, and so on) and the functions you want to perform (execute leg determination, set 'Planned' status, and so on).
As in the other fields you have to enter the name of a variant or create a new one (for more information see Data and options).

This field is a required field and you always have to enter a value here.

Choose [Create transportat. chain] if you want to create an entire transportation chain at once in this collective processing run. For more information see below.

Save created shipments:

During shipment document creation, the collective processing run may return an error or a warning.

Certain errors generally result in a document not being created. If, for example, the shipment type you specified does not exist, the document cannot be created.

While other errors or warnings do not necessarily mean that a document is inconsistent, you may nevertheless decide not to create the document - seeing that, for example, route determination could not be performed, the service agent could not be adopted from the delivery, or the maximum weight has been exceeded.

In this section you can specify whether you want to save a shipment if these less serious errors occur:

  • Do not save shipment if warnings/errors occurred. If you choose this option, a shipment will only be created if it does not require any rework.
  • Do not save shipment if errors occurred. If you choose this option, a shipment will be created even if warnings have occurred (but not if errors have occurred). Some minor rework may be required.
  • Always save shipment. The shipment document will be saved even if warnings or errors have occurred. Rework is required.
  • Never save shipment. This option may be used to simulate a collective processing run, for example if you want to check whether any errors will occur.

Log:

In this section you can specify whether you want to generate a log and the level of detail you want the generated log to show.

For example, you can specify that you do not want to save the log. In this case the log will be displayed after the collective processing run is finished, but it will be lost if the transaction is quit (this means that you cannot display any information for collective processing runs in batch mode!).

For normal logs, only errors and warnings (for example, invalid service agent) and important messages (for example, shipment 1013 created) about the system processing status will be recorded. The detailed log contains additional information on successfully performed subfunctions (for example, leg determination has been carried out). The very detailed log also provides technical information (for example, stage created with key 1013/0004).

Create transportation chain in a collective processing run

For a collective processing run, you can also specify that you want to create a transportation chain that consists of several shipment documents.

For example, you can allocate all selected deliveries to main leg shipments, and afterwards to preliminary shipments or to subsequent shipments.
In this case the quantity of the selected deliveries will be processed multiple times in different legs.

If you choose [Create transportat. chain], the system displays several screen sections where you can specify the grouping criteria as well as the data and options for the different legs (the maximum number of which is 5).

Example:

  • Suppose you want to allocate all deliveries first to a main leg shipment that, for example, travels by train from Philadelphia to New York.
    To do this, you enter a variant in the 'Data and options' field of the '1st leg' section that indicates the transportation planning point, the shipment type as well as the service agent, and the route for shipping the goods by train.
    You do not enter the 'Grouping criteria' field since you want to group all deliveries into one shipment.
  • In the second leg you allocate all deliveries to the corresponding preliminary shipments that move the goods from the shipping points to the station in Philadelphia.
    To do this, you enter a variant in the 'Grouping criteria' field that specifies the shipping point as grouping criterion. The variant also specifies that the maximum weight for one shipment is 30 tons.
    In the 'Data and options' field you enter a variant that indicates the transportation planning point, the shipment type, and so on for the preliminary shipment by truck. You also specify that you want to carry out route determination.
  • In the third leg you generate the subsequent shipments. The procedure is the same as for the preliminary shipments.

NOTE:

  1. Each of the selected deliveries is allocated to three shipment documents. This means that each delivery is part of several successive shipments (a preliminary shipment by truck, a main leg shipment by train and a subsequent shipment by truck).
  2. It is not necessary for you to create a complete transportation chain in a collective processing run. You also have the option of creating only parts of the transportation chain in a collective processing run. One possibility is to manually create the main leg shipment by train in the system and generate the preliminary and the subsequent shipments in a collective processing run.
  3. If you use route determination for a preliminary shipment (for example, by selecting the 'Execute leg determination' function under 'Data and Options' or by setting the 'Planned' status), the route determination task will search for a destination&#x
History
Last changed by/on SAP  20130529 
SAP Release Created in