Shipment confirmation via EDI for Hilti

Version 5 – December 26th

Process Overview........................................................................................................................2
Note 1 – Number of packages.................................................................................................3
Note 2 – Volume information..................................................................................................3
Note 3 – Reference PO number and Line...............................................................................4
Note 4 – Delivery date at customer.........................................................................................4
Note 5 – Shipments with gross weight equal or less than net weight are not accepted..........5
Prerequisites for process set-up (Users)......................................................................................8
ZFRA Output maintenance.....................................................................................................8
Technical details (GDC/ BASIS team).....................................................................................10
Customer profile...................................................................................................................10
EDI/ DEV settings................................................................................................................12
Process Overview

The purpose is to send a confirmation via EDI to Hilti after the shipment is completed in SAP.

How is it done:

1. Shipment is created from one or more deliveries (VT01N).

2. Packing is done.
Note 1 – Number of packages
For shipments to Hilti US information on the number of packages is required. This can
be done in two ways:
a. Nested packing - boxes in pallets

b. Pack on pallets and complete the packages information in the Contents field of the
HU. The format should be X CARTON, where X is the number of packages.

Way to proceed to be decided by business.

Note 2 – Volume information

Volume information is required by Hilti. It will be calculated automatically in the
IDOC, same as it is done in printed output ZFS2
Requirement for business is to have always the dimensions maintained for the
handling unit:
Note 3 – Reference PO number and Line
Initial line item number of the PO is required by Hilti.
This is being added automatically in field Purchase order item.

Should an incoming EDI ORDER fail and the SO must be created manually by
Customer Service, make sure that Purchase order item number is maintain exactly as
in the PO for each line item. Failure to do so will cause the shipment advice to error
out.

Note 4 – Delivery date at customer

Delivery date to customer is required by Hilti. This is calculated by adding the
duration in days of the route to the completion date of the shipment
 Prerequisite: The shipment needs to be completed up to the status Shipment end
before 12:45 PM (CET).
Shipments processed after this hour will be send with the next day’s job.

Note 5 – Shipments with gross weight equal or less than net

weight are not accepted

3. The output ZFRA is created with status 1 – Send/ processed with daily scheduled job
4. Hilti requires one IDOC XML per shipment.
Step 1 - Batch job ZSD_NL_DD_RSNAST00_ZFRA_14:45 PM runs daily at 12:45 PM CET
and processes all the ZFRA outputs.

Step 2 - the IDOC is transformed into an XML file and saved on the P16 server
5. EUREDI script will run and will transmit the XML file to the customer at 13:05 PM CET

Prerequisites for process set-up (Users)

ZFRA Output maintenance

T-code VV71.
Use VV72 to modify and VV73 to display.

Enter condition type ZFRA :

Choose combination key : TrspPlanPt/ShipmntTyp/Ship-to.

Confirm.

Enter transportation planning point and Shipment type.

For Hilti these are:
Planning point: 9302
Shipment type: Z00D

Execute.

In the Create condition record screen enter:

The ship-to party customer
Partner Function: SH
Medium: 6 (will come automatically when pressing enter)
Time: 1 (this will create the output and have it wait for the batch job processing)
Save your entries.
Note: At the moment of Go-Live these customers will have the outputs maintained.

List of Hilti customers

to be setup for SHPADV V.1.xls

Update – Dec 26th, 2012

Hilti Moscow – deactivated
Hilti France – activated
Technical details (GDC/ BASIS team)
Customer profile
Tcode WE20
Select customer (KU)

And add the SHPADV message type in the outbound parameters with the following options:

Message control:
EDI/ DEV settings

XML Port: ZHLTXMLPRT - XML Hilti shipment File transfer has been defined for this
shipment confirmation.

Function module: Z_S_EDI_PATH_CREATE_HILTI ensures that the name of the xml file is
in the format:
HILTI_DELV_SHP_ADV_YYYYMMDD_HHMMSS_SHIPNO.XML

Folders on the SAP servers for the XML files:

/boltons/T16/interfaces/EUR/EDI/out/HILTI/ - for T16 (test environment)

/boltons/P16/interfaces/EUR/EDI/out/HILTI/ - for P16 (productive environment)

ZTZ_FIXDATA entries for Modification when XML generated on the field <SNDPRT>.The changes for
Partner Function and Partner number in XML for HILTI:
SAPLEDI7 SHPMNT1 1 SHPADVZHLTXMLPRT
SAPLEDI7 SNDPRN 1 0001000427
SAPLEDI7 SNDPRT 1 LI

ZTZ_FIXDATA for Function module Z_S_EDI_PATH_CREATE_HILTI & the changes

related encoding information & TABNAM in Control Segment and XML Version 1
SAPLZS_HILTI FNAME1 1 HILTI_DELV_SHP_ADV_

ZTZ_FIXDATA for calculating volume in HU, based on the dimension provided

SAPLXTRK OTP 1 9302

P16 batch job to process the ZFRA output:

ZSD_NL_DD_RSNAST00_ZFRA_14:45 PM
Program: RSNAST00
Variant ZSD_9302_ZFRA
Frequency: Daily at 12:45 PM

Persons to be notified if the job fails:

Vincent.vandenBerg@saint-gobain.com
Roxana.Stoica@saint-gobain.com