Prepared Isuue Close Responsible

Program ID Issue Log ID Prepared By Date Date (On-Site) Status

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 1 Chowdhury 10/22/2009 10/28/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 2 Chowdhury 10/26/2009 10/28/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 3 Chowdhury 10/28/2009 10/29/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 4 Chowdhury 10/28/2009 10/30/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 5 Chowdhury 10/28/2009 10/29/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 6 Chowdhury 10/28/2009 10/30/2009 Krishnan Closed
OM_EDD_12 OM_EDD_12 Ashim Mohan
9 9- ISS - 7 Chowdhury 10/28/2009 10/29/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 8 Chowdhury 10/28/2009 10/29/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 9 Chowdhury 10/30/2009 11/3/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 10 Chowdhury 10/30/2009 11/16/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 11 Chowdhury 11/2/2009 11/5/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 12 Chowdhury 11/10/2009 11/16/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 13 Chowdhury 11/10/2009 11/11/2009 Krishnan Closed
OM_EDD_12 OM_EDD_12 Ashim Mohan
9 9- ISS - 14 Chowdhury 11/11/2009 11/12/2009 Krishnan Closed

OM_EDD_12 OM_EDD_12 Ashim Mohan

9 9- ISS - 15 Chowdhury 11/13/2009 11/16/2009 Krishnan Closed
Issue Description Resolution/Comments

What is the exact scope of WM_EDD_129? As per the telecon the

scope is as follows:
1. Create of the Route Exception table.
2. Enhacement of the user exit
MV45AFZZ/USEREXIT_MOVE_FIELD_TO_VBAP to get the Route
and assign it to VBAP-ROUTE for sales order.
An upodated process flow document has been shared by Mohan
on 10/28/2009. As per the new document BAPI creation for
updation of Route Exception table is also part of the
development scope of this object. Doubts/Clarification on that
document will be maile

It has been agreed in the con-call on 22-Oct-2009 that a separate and

updated document on the detailed process logic of OM_EDD_129 will
be send by Mohan. This logic will be implemented inside the user exit. An updated user-exit logic has been send on 28/10/2009.
Doubts/Questions on the same will be communicated to Mohan.
The use-exit logic document send by Mohan on New issues will be created for those clarification points.

In the updated process flow document it has been mentioned that

"Bapi will have to be built for updation of exception table". Here is the
list of doubts:

1. What do we understand from updation of exception table? Is it only A list of six BAPI name has been provided. The details logic yet
updation of existing record to be clarified.

In the process flow document the first step in data extraction has been
mentioned as "Get the data from the table ZSDPARAM" Replt from Mohan on 10/29/2009

Issue: What data we are going to extract from table ZSDPARAM using All the default values are available in this table Get entry from
what condition? ZSDPARAM table for the default shipping condition.please refer
to table entry in De1/120 SHIPCOND. As per the data in that
Where we will use that data in the process tabkle the query will be select

Document Type Check:

We do order type check from table ZSD_ORDERTYPE while
assigning route from ACRS table. This is the only case where sales
order type information will be used? As per con-call on 29-Oct order type check will be used only for
If this is not the case, then please provide us the details logic on order route number extraction from ACRS table only.

Cut-off time check:

In the process logic flow at what point we need to make a check on

cut-off time? Only when we are selecting route from Static Route
table?
This check needs to be done for all the cases.
Transaction where Route Assignment is to be called:
The process logic needs to be executed during sales order creation The transactions are:
(USEREXIT_MOVE_FIELD_TO_VBAP). What are the other VA01, VA02, VL01N and VN02N that is both sales order and
transactions where the same route assignment needs to be under the delivery creation/update.
development scope Refer HLD section 2.3.1.2

As per con-call on 29 Oct the route type check will be used for
Does the process logic depend on Route type (O, C, P, T etc). In ACRS and SCRS case only. For ACRS we will use route with
which step (Exception,/ACRS/SCRS) the route extraction-assignment route type C. For SCRS we will use route type O, C and P only.
logic differ on Route type? The logic for O and C is same. But for P we have separate logic.

BAPI logic is not given. Once the updated spec with BAPI logic has BAPI logic has been provided. Mails has been send for some
been received the same can be check, verified and clarified. minor c;arification. Mohan will get back on those.

As per the telecon on 30Oct, Mohan will update the static route
sequence block (step 5) in the process loguic flow document. The
logic in this section will be different than what has been mentioed in
the HLD. The HLD also need to be updated. Updated logic has been provided by Mohan.

Cut-off Time Check:
1. Q: Route no-Plant no combination is not the primary key in Static
Route Param table. Is there any situation of getting mutiple records in
this query? What should we do in that case?
2. Which cut off time has been mentioned in HL
There are series of checks for a route namely
Route Close Status – The route should not be a closed route
Route Execution Complete Status – Route execution status
should not be complete.
Max Cube Reach Status – Max cube should not be reached for
the r

For the list of BAPIs in 129, are we going to access them through
methods of business object or as a remote function module? If remotte
function module is suffice then there is no need to attach the same Same business object ZMM_SROUTE will be used. All BAPI
with some business object method. should be created under function group ZMM_ROUTEPLAN

Route with status Planned and Ready can only be considered for
further validation check.
Route with all other status (Closed, Execution complete, PGId ) will be
invalid route.
As per mail from Mohan "This may leads to some practical
Now there is another requirement - for route with status Execution problem. that is why they asked to do the status updation for
Comple every Salres Order / Delivery transaction."
Truck Departure time validation for Route :

For truck departure validation we use data from the ZSD_ROUTE

table but to know whether this is CDX route we have to hit the Static
Route Param table. Why can't we have the CDX_ROUTE flag in the As per Rajan/Carey the CDX flag can only be in Static Route
ZSD_ROUTE tab Param table

Updation of Delivery Date:

In addition to route assignment in the sales order line item (VBAP-
ROUTE), we will also assign route date to delivery date depending on As per Mohan all the schedule line for a sales order line will be
the flag. But delivery date field is not there in the VBAP work area. It is updated with delivery date (VBEP-EDATU). For delivery the field
in the Schedule is LIKP-WADAT.