• No results found

Blacklist vehicles data should be maintained and controlled through system

In document SAP SD Blue Print (Page 84-88)

7. While making gate entry following points should be covered :

a. Different gate entry number ranges for different plants should be provided.

b. Vehicle number should in alphanumeric with no special characters like “*/-\|,”

c. LR number should be maintained at gate entry for sales returns and same should be used for material receipt conformation.

d. System should not allow gate entry for blocked/ hold orders.

e. Repeated vehicles Weighment should be monitored and controlled. System should pop up message if tare weight of vehicle exceeds 300kgs than any of earlier tare weight for same vehicle.

f. There should be some provision to upload data in SAP, in case data is maintained in legacy system during power cuts &

network failure.

2. Sales Order Number, Vehicle No. and Transporter name shall be enter while making gate entry for a vehicle and same shall be use to print as a ‘Gate Pass’ using ABAP script and a copy shall be given to the Transporter.

3. Customer specific requirement for specific capacity vehicle shall be maintained in item text of sales order and same shall be displayed as a report.

4. Gate entry system will allow user to select Available Sales orders, Transporters,

Materials, Ship to party.

5. A separate table shall be prepared.

6. Blocked list vehicles data shall be maintained through a different table.

7. While making gate entry following functionality shall be followed:

a. A separate number range shall be maintained for gate entry at each plant.

b. Through data validation, special characters in vehicle number shall be avoided.

c. L.R. Number shall be maintained in Shipment in case of gate entry of sales return material.

d. System shall not allow the gate entry of blocked / hold orders, this shall be handled through ABAP functionality.

e. Since the system performance get effect to make this process for each and every vehicle, mapping shall not be possible. A report shall be prepared to monitor the vehicles.

f. Sap standard functionality doesn’t allow uploading data from legacy system- there should not be more than one live system for one process.

g. Delivery’s shall be clubbed at the stage

g. If multiple materials against multiple delivery’s are loaded in single vehicle then system should provide net wt. for each material.

h. System should also provide a facility to get Weighment of any material without gate entry and without reference to any sales document.

i. Provision for Deletion and reweighment before PGI

j. Loading point should be entered.

k. Coils should be selected.

l. If LR number is not available against the selected Transporter and shipping point then system should restrict for further Transaction

m. If any gate entry is done against any sales order / purchase order, any change in that sales order should not be allowed to marketing till preparation of invoice. (With respect to logistics point of view).

6. For any gate entry against pre paid material, check should provided so that the vehicle should not be allowed to gate in if not having contract of that particular transporter against the customer mentioned in SO. Also system should also inform the marketing for non availability of transport agreement in system.

of shipment multiple delivery’s, multiple Weighment, total Weighment can be displayed.

h. A Component shall be developed through ABAP.

i. Capture and delete options shall be provided

j. A separate field shall be provided for storing loading point in the shipment.

k. Batches shall not determine at the time of gate entry.

l. Trigger shall be developed for the same.

m. Once the material produced against sales order then automatically sales order shall be blocked for changes and deletion.

6. System will allow only those

transporters which were maintained the sales order. In case of multiple sales orders system shall determine the common transporters.

Checking of Transporter Condition records while gate entry shall not be possible.

6.1.9.3 Empty Vehicle

Weighment Tare weight of empty truck is taken at the weigh bridge and should get capture in the system and also time should get capture in the system. Hard copy of tare wt. slip is taken out and handed over to the Transporter.

1. System should popup a message if the vehicle reaches to weighbridge after 15 minutes (can be variable) from gate entry.(Not for HR coils)

2. There should be Provision for entering Weighbridge number at weighbridge.

The tare weight of the vehicle is recorded and a Weighment Note is issued to the Vehicle Driver.

This shall be handled using ABAP/4 development.

1. System shall pop up message at the time of gate out, if vehicle reached to weighbridge after allowed time. This shall be handle trough ABAP functionality.

2. Separate field for weighbridge number shall be incorporated through ABAP in shipping screen.

( C / G )

3. Two Gross and Tare weighment provision should be provided.

4. Before making delivery for any product except mill coil and wider slit coil, it must be ensure (lock) that tare weight is performed against that vehicle.

5. As one vehicle is reporting more than one time in a shift (and the net weight is only the reference weight for drafting), Provision should be there to make tare weight only once in a shift for

particular vehicle to avoid more movement of vehicles at weigh bridge.

3. Addition fields should be incorporated in the shipment files to store Gross, Tare

weighments and net weighment.

4. Tare weighment is not a mandatory for all vehicles. But if vehicle goes without tare weighment (other than mill coil and wider slit coil), so tare weight field shall be blank and no delivery shall be performed.

5. Weighbridge software is a interface to SAP which shall not allow for taking second Weighment without first Weighment.

6.1.9.4 Delivery Order Creation &

Picking

Load carrying capacity of the vehicle should be checked before making the Delivery. Ideally, if the load carrying capacity of the vehicle is less than the weight of the material for which Delivery is being prepared, then the system should issue a Warning’

message.

During the creation of delivery order, the following activities are to be performed:

 Picking: Coil No. to be despatched against a particular order are to be chosen during delivery creation. D.O. can also be created packet/coil wise.

 Packing: This is a part of the production process and not done as part of delivery.

Issue:

In S.O maximum four transporters are allowed but practically more than four transporters can do a delivery for a single sales order. In this condition frequent changes are done for transporter code in Sales Order as per vehicle reporting which should be

1. Delivery is created with reference to the Sales Order.

2. In case of Make to Order scenario, the stock is already allocated and appears in the delivery when it is being created.

3. In case of Make to Stock, the person who is allocating the stock shall use batch search strategy to find the materials, which batch the customer specifications and chose them for Picking.

4. If the transporter in the Sales Order which defaults into the delivery and the transporter in the Gate Pass is different, then provision to change the transporter shall be made available.

5. During Delivery, all items, which are due for delivery in the Sales Order, are defaulted.

6. After the delivery is made, it shall be printed and given to the Driver of the vehicle.

7. The delivery note contains material specifications, partner details, gate entry number etc.

8. Picking is the first stage in delivery where

1-5 , 8,d - (A) 6,7,a-c,e-h - ( C )

eliminated. In this case if the material is distributed to all transporter in any proportion, then it is very difficult to make a trace of dispatches against each transporter for distributed quantity.

a ) Vehicle should reach logistics within 20 minutes (variable) after gate entry (time) for HR coil otherwise system should ask for reason.

b ) Only gate entry number/ shipment number with sales order No. should be supplied for creating delivery

c ) Truck number, transporter, net weight, container No, Container seal should appear while creating delivery.

d ) Provision should be there to create delivery against more than one sales order

e ) Modification of SO number, Truck number, Transporter should be provided till gate out.(in shipment).

f ) Different number ranges for delivery should be maintained on the base of plant

g ) Road permit data should be maintained for individual customers. If permit’s not available System should pope up the message “Road permits Required / not available” at gate entry level and Delivery level

h ) Container despatches, container number and seal number should be maintained in delivery while picking and should appear in invoice document.

i ) Loading Points and Loading point capacity should be maintained. On the base of loading point capacity vehicles inwards should be controlled.

the material is staged in right quality and quantity and made ready for delivery. This can be done during delivery creation in the picking screen by choosing the coil numbers against delivery. The storage location is the picking location.

Issue:

This issue can be addressed by using the

“Shipping’ function of Logistics Execution.

a ) One trigger shall be prepared in ABAP at the time of Gate out.

b ) Separate screen shall be prepared through ABAP. Delivery shall be created through standard Tr. VL01N. And the same delivery number shall be attached to shipment/Gate entry number.

c ) Standard screen shall be modified with shipment number, Truck number, Gate entry number

d ) Through standard transaction (VL10) e ) Shipment shall be changed any time. But

controlling is Issue.

f ) Different number ranges shall be maintained.

g ) Separate table shall be provided and the functionality shall be mapped through ABAP.

h ) Container number and container owned by shall be stored in gate entry screen and seal shall be stored in item text of delivery.

i ) Same shall be done through ABAP functionality.

6.1.9.5 Loading

Different types of material are loaded at different places hence all the loading points have to be identified in the system.

All loading points shall be maintained and used at the point of loading in delivery. The loading

points are assigned to shipping points.. ( A)

6.1.9.6 Final Before Issuing the goods for Billing, the vehicle is The Final weight of the vehicle (Gross Weight) is ABAP Development

Weighment

again weighed.

Final weighment should be captured by the system. recorded and a Weighment Note is issued to the Vehicle Driver. This shall be accomplished by

ABAP/4 development. - ( C )

6.1.9.7 Post Goods Issue

If there is a difference in the weight which is

mentioned in the delivery and the actual weight, then manual adjustments of weight have to be made in the stock.

Before billing posting of goods issue should be done, which will update the stock.

I. Time between creation of delivery and PGI for HR coils should not be more than 40 minutes if so reason should be maintained.

II. From invoice time to gate out time should be with in 20 minutes other wise system should ask for reason.

III.

If HR coil is silted and during actual weighment it has noticed that slit coil weight is different from system wt. (it is not as per the actual wt.), then the difference of weight should be updated against other secondary by-product of the same coil to match the mill coil weight with its by-product weight.( weight tally

).

IV. Delivery performance (scheduled delivery date and actual delivery date) details should be made available in the system.

V. Entering of Loading point and Loading person

In document SAP SD Blue Print (Page 84-88)