SAP ABAP IMG Activity /DSD/HH_TRADAT (Specify Volume of Transmitted Shipping Data)
Hierarchy
☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ LE-DSD-DC-DU (Application Component) Download/Upload
     ⤷ /DSD/HH (Package) Handheld
IMG Activity
ID /DSD/HH_TRADAT Specify Volume of Transmitted Shipping Data  
Transaction Code /DSD/91000223   IMG Activity: /DSD/HH_TRADAT 
Created on 20020424    
Customizing Attributes /DSD/HH_ALG   Route Accounting - General Attibutes for IMG 
Customizing Activity /DSD/HH_TRADAT   Specify Volume of Transmitted Shipping Data 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name /DSD/HH_TRADAT    

Use

In this menu item, you can control which data (message types, IDocs) is passed on to the Handheld Middleware Server (HHMWS). To do so, you have to enter all the data (message types, IDocs) that you want to be processed further in this Customizing table. The download program, /DSD/HH_IDOC_OUTPUT_CONTROL, reads this Customizing table and calls the respective function module (field "FUNCMOD") for all entries (message types) that are maintained for the shipment type and transportation planning point.

The following function modules for DSD route accounting are available:

  • /DSD/HH_DL_FM_CREDIT_DATA         DSD:Download credit data (KNKK + credit limit)
    • Message type: /DSD/HH_CREDITDATA            Credit data
  • /DSD/HH_DL_FM_DELIVERY             DSD:Download delivery data
    • Message type: DESADV                        Delivery
  • /DSD/HH_DL_FM_INVOICE             DSD:Download billing document data
    • Message type: INVOIC                        Invoices
  • /DSD/HH_DL_FM_LOAD_DELIVERY         DSD:Download load delivery
    • Message type: /DSD/HH_LOAD_DELIVERY            Load delivery
  • /DSD/HH_DL_FM_ROUTE_ITINERARY     DSD:Download visit list
    • Message type: /DSD/HH_ROUTE_ITINERARY        Visit list
  • /DSD/HH_DL_FM_SALES_ORDER         DSD:Download order data
    • Message type: ORDRSP                        Order
  • /DSD/HH_DL_FM_SHIPMENT             DSD:Download shipment data
    • Message type: SHPMNT                        Shipment

Note:

  • Some data (message types, IDocs) is mandatory.
    • The control IDoc - /DSD/HH_CONTROL - is always sent. Therefore, you do not have to enter it in the table.
  • Only the optional data (message types, IDocs) is entered in this Customizing table.
  • The table is open for customer enhancements: you can maintain entries for new fnction modules (you have to program the flow logic for further processing yourself).
  • The download program, /DSD/HH_IDOC_OUTPUT_CONTROL, creates the appropriate IDocs for all the optional message types entered in table /DSD/HH_TRADAT. If no entries exist (for transportation planning point and shipment type), no optional data is transferred.
  • The control takes place at message type level (IDoc).

Requirements

To transfer IDocs, you have to perform the following steps:

  • Configure the logical systems for sender (R/3) and recipient (HHMWS) (Customizing)
  • Assign the sender's logical system to a client (Customizing)
    • You have to enter /DSD/HH_CONTROL as output parameter for the logical system. You also have to enter the message type (EDI or ALE) with the appropriate transaction code (/DSD/HHDL) in the detail screen.
  • Create ports
    • TA WE21
    • Choose format (file)
    • The function modules that write the data to a directory are provided by SAP (F1 help)
  • Define transaction code for outbound processing
    • TA WE41
    • Assign function module /DSD/HH_IDOC_OUTPUT_CONTROL and message type /DSD/HH_CONTROL to this transaction code.
  • Maintain partner agreements
    • TA WE20
    • Partner type LS
    • Select a logical system and the appropriate entries (inbound/outbound parameters)
    • Enter the appropriate message types.
    • Outbound parameters
    • Field "Message Type" only allows message types that can be passed on by the download program (function module /DSD/HH_IDOC_OUTPUT_CONTROL).
    • Allowed message types:
    • /DSD/HH_CONTROL                Control messages
    • /DSD/HH_CREDITDATA                Credit data
    • /DSD/HH_ROUTE_ITINERARY            Visit list
    • /DSD/HH_LOAD_DELIVERY            Load delivery
    • /DSD/HH_TXTDRV                    Definition of driver texts
    • DESADV                        Delivery
    • INVOIC                        Invoices
    • ORDRSP                        Order
    • SHPMNT                        Shipment

  • You have to enter the recipient port and the base IDoc type for each message type.
  • Note
  • You have to maintain message control additionally for message type /DSD/HH_CONTROL. You have to enter the data for the application, message type, and transaction code.
  • Enter an outbound parameter for EDI (with partner role LS) and ALE (without a partner role) for each message type.
  • Upload Inbound Parameters
  • Maintenance of inbound parameters is only intended for the UPLOAD, and is only mentioned here for completeness' sake.
  • You can maintain the following message types in the inbound parameters:
  • /DSD/ROUTEACCOUNT_CCOCI0        RA: Create check-in/check-out data
  • /DSD/ROUTEACCOUNT_CCTRDT0        RA: Transfer general control data
  • /DSD/ROUTEACCOUNT_CCUSVI0        RA: Create customer visit data
  • /DSD/ROUTEACCOUNT_CDELFU0        RA: Create delivery fulfillment data
  • /DSD/ROUTEACCOUNT_CENCAS0        RA: Create payment data
  • /DSD/ROUTEACCOUNT_CINV0            RA: Create billing documents
  • /DSD/ROUTEACCOUNT_CIVPRT0        RA: Create confirmation for BillDoc print.
  • /DSD/ROUTEACCOUNT_CORDER0        RA: Create new orders
  • /DSD/ROUTEACCOUNT_CTDIST0        RA: Create tour distance sheet
  • /DSD/ROUTEACCOUNT_CTTIME0        RA: Create tour time sheet

  • Maintain the transaction code (BAPI) for each message type.

  • Maintain message types
    • Message type "Download"
    • Send medium 6 = "EDI"
    • Application V7 = "Shipment"
    • Message type "Download - ALE"
    • Send medium A = "ALE"
    • Application V7 = "Shipment"

The message types are assigned a processing program, /DSD/HH_NASTED, which creates appropriate IDocs for all data (deliveries, orders, ...) related to the shipment.

Standard settings

Transaction data is sent to the Handheld Middleware Server (HHMWS) shipment-based. This means all the data for a shpiment is sent to the Handheld Middleware Server in consolidated form. IDoc /DSD/HH_Control02 IDOC encompasses the full data transmission.

Note

  • When a shipment is deleted, a control IDoc is also created to inform the HHMWS.

The standard SAP output determination is used for control. Because output determination is already included in the shipment, you only have to create two new message types.

You can use all the standard SAP options for output determination and message dispatch.

The system tries to use as many IDocs as possible (including the modules for filling them) from the SAP standard (for shipments and deliveries, for example). New IDocs are created for data that is not contained in the standard IDocs.

Note:

The message type can only be found automatically when:

  • It is entered in the output determination procedure
  • A condition record exists
  • An appropriate entry exists for the partner agreement

Process flow

Output determination takes place when you save the shipment. An NAST record is generated as the result of output determination. The selection program for dispatching messages, RSNAST00, calls the control IDoc in the outbound parameters of the partner agreements in the logical system. This determines the recipient port and base IDoc type, as well as the appropriate transaction control for the message type. In turn, this transactino code is used to determine the download program, /DSD/HH_IDOC_OUTPUT_CONTROL. The download program calls table /DSD/HH_TRADAT and determines the IDocs to be created. Before the data is read, another check is performed as to whether the message type determined from table /DSD/HH_TRADAT is allowed at all in the partner agreement. If not, an error message is output and processing is cancelled. Otherwise, the download program is processed further.

The following data is transmitted to the HHMWS:

  • Itinerary (visit list)
  • Customer credit data (credit line, credit limit)
  • Deliveries
  • Orders
  • Shipments
  • Invoices (billing documents)
  • Load delivery

Activities

A BAdI (definition name: /DSD/HH_READ_TRADAT) is provided for reading the Customizing data. This enables you to implement customer enhancements (such as searching for wildcard values). The BAdI must return a table with the entries found in the Customiz

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
/DSD/HH_TRADAT_V V - View SM30  
History
Last changed by/on SAP  20040227 
SAP Release Created in 461