Handling deadlines (or Dates) in Delivery and Transportation

Thanks to Andrey Karepanov

Deadlines in delivery and transportation tab - is the place to keep different dates in one place.

The general task looks like this (all actions performed in Delivery):

1.To fulfill Pick-Up Date which represent the date, when Dealer wants to start transportation, to Delivery in field Planned Goods Issue Date (number 1 on the scheme) – this step will be done manually

2.To put (automatically) Planned Goods Issue Date (1) to new field (Delivery Header, Tab Dates) Shipment Begin Plan and Actual Goods Issue Date (2) to Shipment Begin Actual, see a picture below.

Some small things before we start.

In Delivery (Tab Dates) one Event can represent four different moments of time:

- Begin Plan & Begin Actual

- End Plan & End Actual

In the general scheme we defined how delivery dates should correspond with Deadlines. Correspondence of deadlines with Logical time, like Begin & End, Plan & Actual are depicted below:

In customizing, we need to do next operations:

SPRO: Logistics Execution -- Shipping -- Basic Shipping Functions – Scheduling -- Additional Deadlines -- Maintain Deadlines and Events

Specify an alternative name for the logical time (selected times already have existed in my test system):

Go to every time’s details (Magnifier button) and mark checkboxes Read Inline & Write inline, that means deadlines should be read from the application tables:

Then go to Time Mapping IL menu, and setup those dates:

For every line, define Date&Time field (from Delivery, LIKP table in this example):

Define Time Segment Procedure:

SPRO: Logistics Execution -- Shipping -- Basic Shipping Functions – Scheduling -- Additional Deadlines -- Create Event Groups

Where you have to select a table in order to define the dates for deadlines (LIKP in this example, in all 4 tables):

Define all events for template in certain order (Sort Sequence):

If checkbox Optional trans. is selected, events appear in delivery only if they are not empty or manually selected and you can delete them.

Also you have to assign Event Groups to Delivery Type:

SPRO: Logistics Execution -- Shipping -- Basic Shipping Functions – Scheduling -- Additional Deadlines -- Assign Event Groups to Delivery Type

Result: dates from delivery (Processing Tab)

Reflect automaticaly in dealines (Dates Tab):

Date 4, is POD date, (proof of delivery) appears if you activate POD functionality.
 

In the next step we will see how to copy deadlines from delivery to shipment.

How to setup loopback connection for IDOC and copy characteristics from 300 to 023 class type.

If you have one system and want to test IDOC it is reasonable to setup loopback connection.

In my case I want to achive two things:

1. Create characteristics and classes for batch the same, like I already have in configuration (300 class type).

2. Easiest way for step 1 - is to transfer characteristics (CHRMAS) and classes (CLSMAS) at the same system with change of class type at the end.

Sounds easy... Let's go!

In some cases you may need personalized connection (for example - IDOC ORDERS) with Vendor Partner Number. In this particular case it is enough just Logical system connection.

Make sure, you have LOCAL logical system (SALE -- Basic Settings -- Logical Systems -- Define Logical System)

Create two virtual logical systems

Internal LS for IDOCs-receiver
Internal LS for IDOCs-sender

Create new distribution model in BD64 

Add message type (CHRMAS, CLSMAS)

Create Outbound Partner profile parameters for receiver in WE20(/ER5CLNT999/LS//CHRMAS+CLSMAS)

• Message type CHRMAS -- Basic type CHRMAS04
• Message type CLSMAS -- Basic type CLSMAS04

Create Inbound Partner profile parameters for your real system (/DIS_00_710/LS//CHRMAS+CLSMAS)

Message type CHRMAS -- Process code CHRM

Message type CLSMAS -- Process code CLSM

 

After that, you can transfer characteristics and classes to the same system/client:

1. BD91 - Send Characteristic - first
2. BD92 - Send Class  - second

you also have to change class type from 300 to 023 manually and re-transfer IDOCs thru WE19

At the end you need assign materials to class in mass by CL24N - Assign Objects/Classes to Class