Rapid Response Business Logic
Ver 1.0 Dated : 20th June’ 06
- RRO Features :
- Three different Order types ZRRN, ZRRE & ZRRS for Normal , Express or Super Express mode of serving the Order are created in the SAP system.
- The due dates have a default value of 7 days, 14 days & 21 days for N, E & SE type respectively. It can be modified by the user at the time of order entry.
- Also there would be display of price multiplier of 1, 1.2 & 1.5 respectively for N, E & SE type respectively which can be modified. There will be a condition type for Rapid Response Orders. This condition type will appear in the pricing proc with correct premium value as per the order types. The pricing conditions will be non-modifiable in ZDO.
Sl. No. / Feature at SO item Level / Type of Order / Default Value with Modifiable field
1 / Delivery Period / Normal / 21 Days
Express / 14 Days
Super- Express / 7 Days
2 / TOC Premium / Normal / 0
Express / 20 %
Super- Express / 50 %
3 / Per day Penalty / Normal / 1 %
Express / 4 %
Super- Express / 6 %
- Rapid Response Order ( RRO ) will be served well before the max “Requirement due date” hence “ First date” should be entered while booking an order. The “First date” is the date on which the processing for dispatches should start from the billing plant location. This includes the administrative time for issuing ZDO, arranging for vehicles etc.
- If RRO is logged exactly as per Req. due date i.e. Normal RRO in 21 days in advance , Exp. In 14 days in advance & S. Exp. 7 days in advance then the “First date” for SE should be the date of logging RRO, for Exp. RRO it should be (7days – order processing time) from current date and for Normal RRO it should be around (14 days– order processing time) from current date. This will prevent killing our own “Offers”.
- The Availability date shown through ATP check is of no consequence in the case of RRO since if the stock becomes available at the servicing location then the
“First date” becomes equal to the available date of ATP. In the case when the stock is not available in the servicing location the available date of ATP becomes ahead of the 1st date which has got no significance in the case of TOC.
- The ZPRO price printed on the invoice is determined based on a Price multiplying factor over the std price. It is not dependent on the “Per day Penalty” factor. Penalty factor would be required in compliance reports & in decision making process for raising of credit note to the customer if penalty gets decided for payment.
- Order Logging discipline :
- Each RRO logged will have one line item in the Sales Order. This will ensure unique delivery date & first date of dispatch.
- A RRO can be logged max of 60 days in advance of Requested Delivery date.
- Any order logged which has creation date earlier than 60 days from current date is not a valid order and should not be used for monitoring. It would be closed by the respective CAMs.
- Once an order gets logged, the material movement execution starts immediately and hence once logged the order cannot be cancelled.
- No change in the order data will be permitted once the order has been picked up for backward processing. Order data includes Requested Delivery date, First Date, Quantity, TOC premium, Penalty factor.
- Subsequent documents (STRs) which will be auto generated & should not be modified. Once executed it should be closed.
- Buffer Design :
- RRT drives the Buffering location and Local Billing Requirement drives the selection of servicing plant.
- RRO that is required to be serviced from buffer of the servicing plant will have “REPL” storage location mentioned in the order-Item.
- RRO that is required to be serviced from buffer maintained at another supplying plant which is different from the billing location ( say a order being logged at RWH & material is to be supplied from PWH ) should have “RRSL” storage location mentioned at the order-item level.
- Material Movement against STR for two legged dispatches :
- A new storage location RRSL( Rapid Response Storage Location ) will be defined. This storage location will be defined for all the Stockyards where RR offer is rolled out. RROs for which buffer is maintained at PWH should have this storage location mentioned in the order-item.
- RROs having storage location “RRSL” will be converted into STR in full quantity.
- STRs for supply of material to RWH against RRO will be generated if the date based on (Requested delivery date –21 days ) is greater than or equal to current date.
- The corresponding STR will be serviced from PWH “REPL” storage location. The STR will be converted to STO through auto STO making process. Both the STR & STO should have receiving stockyard storage location “RRSL”. When this STO is used to create delivery the defaulted storage location should be “REPL” for picking to happen from source location. (This needs to be achieved through an User Exit.)
- The GR should only happen at “RRSL” location . This would be suggested by the system.
- The RRO having “RRSL” storage location & the corresponding STR will be linked through “Tracking No” which will be defaulted as “DESP_PLAN” and the “Requisitioner” which will bear the RR Order No.
- RRT Components :
- The tracking of Normal RRO has following components
- Normal RRO booking time to STR making
- STR making to dispatch to stockyard
- Transit time between PWH & StockYard
- Unloading & Loading time at stockyard
- Transit time between Stock Yard to Customer
- Component no. 3 & 5 will be defined at the time of roll-out of RR offer. It would be defined as follows :
Sold to party / Ship to party / Stock yard / Transit time between PWH & Stockyard / Transit time between Stock Yard to Customer
- Other components will be a standard fixed value for any dispatch.
- Reporting Requirement :
- A report is required which should have Req. delivery date, 1st date Report, Penalty factor, Price premium etc for all Rapid Response Orders. Existing ZSS report, YVMRS report may be modified to include these fields.
- A Report is required to track Normal RRO. It should have following informations
Normal RRO No/RRO creation dt / Material / Qty / STR No / Crt dt / STO Nos./ Qty. / Crt dt / Del. Nos.against STO and Del. Qty. / Invoice Dt against Delivery
GR dt / ZDO no / ZDO Qty. / ZDO Crt. dt / Del. Nos. against ZDO / Del Qty against ZDO / Invoice Dt against ZDO
- Time buffer report to monitor the individual Order progress at Order / Item level is required based on standard lead times for various components defined at the time of roll out of the offer.
- Excise Requirement :
- All Excise related requirements would be co-ordinated by concerned CAM, Hub-Manager & LP Planning outside the IT system for it’s full compliance.
1 of 3