Hi ,
I am seeking answer on how to consilidate deliveries for shipment against Stock transport orders.
We have the scenario as below
- Maintain Material Replinishment parameters
- RUN MRP every day
- PR's will get created based on replinishment Qty
- PR's are converted to STO on weekly basis ( storage location is the key selection to run Conversion program ) .
- Delivery due list is run every day
In this case , Multiple PR's will get created every day.
Each PR will have different delivery dates for different materials.
( One PR per Material , PR's will be consilated on materials through MRP setting)
On day of weekend , system will convert PR's to STO .
For each storage location system will create one STO.
Delivery dates are copied from PR by system as a standard.
When delivery is created , system is splittling delivery based on delivery dates including the other splitting parameters like shipping point etc...
How to consolidate the delviery by ignoring the delviery date in split rule retaining rest of the parameters.
Or
is there a way to have delviery date in STO as the System run date while converting PR' to STO .
We are on ver 4.6B
Thanks,
Sudhi
Request clarification before answering.
See if you can change the date from PR date to "current date"(ie the date on which you run the program) in the highlighted program.
Every day PR's will get created for all materials. Next we run <b>PR to PO conversion program</b> once a week for each engineer . In Convertion progam we have used Storage location as input parameter. This will group all PR's into one STO for each storage location.
Thanks,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Delivery split is by default for the following reason in STO.
1. Different Delivery Date
2. Different Receiving Plant.
These to pre-conditions are to be satisfied + supplying plant are to be same in order to merge different STOs into one delivery. Delivery date and Receiveing plants in STO can be changed using ME22N t-code.
Thanks,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashish ,
We are not creating STO manually . We use std. sap program ME59 to convert.
In this event system copies delivery date from PR to STO.
As i stated earlier, we are having same supply plant , same shipping point, same receving plant , single storage location . Only delivery date is different as PR's are created on different date by MRP.
Let me share the background of this Scenario.
We have lot of Customer Service Engineers who require materials to repair at customer site. Each engineer requires some safety stock . All engineers are created as Storage location in SAP under one plant . Based on their consumption , replinishment parameters is set in system.
Since there are many engineer we cannot give stock to all on same day.
So we need to plan to give one engineer a stock every day. So we want to run MRP for each Storage lcoation a day.
Currently MRP run cannot be run at Storage location . Only Plant level is supported. So we have no option other than to MRP for a plant.
Every day PR's will get created for all materials. Next we run PR to PO conversion program once a week for each engineer . In Convertion progam we have used Storage location as input parameter. This will group all PR's into one STO for each storage location.
But delivery due list will break up all the Items in STO based on Delivery date for each material in STO. We would like to consolidate delivery for each STO ignoring date parameter.
Then main objective is to Reduce shipping cost.
Multiple delivery , multiple shipment , same destination , has increased out Shipping cost.
There are 3 stages where consolidation can happen.
1. Run MRP at Storage Location ( NO Option )
2. Create STO with single delviery date ( ME59 is used currently)
3. Create one delivery for each STO ( can we take off split rule )
Thanks & Regards,
sudhi
| User | Count |
|---|---|
| 14 | |
| 11 | |
| 10 | |
| 6 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.