4. Data Det & Collective Processing

Question 0

2. Module contents (4 items):

Answer 0

1. Function of sales doc type
2. Plant, ship point, route det
3. Shipment scheduling
4. Collective processing

Question 1

1. Module objectives (5 items):

Answer 1

1. Sales doc types
2. Auto det of deliv plant, shipping point, route
3. Auto det of deliv dates and show scheduling
4. Combine and collectively process orders due for deliv
5. Combine and collectively process orders due for billing

Question 2

3. Sales doc types (5 items):

Answer 2

1. Sales doc types control sales docs, deliv types control shipping docs and billing types control the billing docs
2. Sales doc type std order for invoiced sales on fixed deliv dates
3. Sales doc types rush order and cash sales for sales from a plant (with or w/o invoice)
4. Sales doc type free deliveries for sales on fixed deliv dates w/o invoice
5. Sales doc type returns for return goods (credit memo / replacement deliv)

Question 3

4. Functions of sales docs (5 items):

Answer 3

1. Auto functions activated through sales doc types
2. Shipment sched and availability check for auto det of deliv dates
3. Pricing
4. Output
5. Credit check

Question 4

5. Deliv plant auto det (5 items):

Answer 4

1. System auto tries to det deliv plant from master data
2. First it checks customer-material info rec
3. Second it checks ship to party in customer master rec
4. Third it checks mat master rec
5. If nothing is found, ship point/tax auto det fails, avail check fails, outbound deliv cannot be made

Question 5

6. Shipping point auto det (5 items):

Answer 5

1. In ship point you det the times required for preparing and packing goods
2. Ship point is det for each sales item
3. Based on ship cond from sold to pty, view shipping
4. Based on load grp from mat md, view sales: gen/plant data
5. Based on deliv plant

Question 6

7. Route auto det (6 items):

Answer 6

1. Route is path between deliv plant and ship to party for each sales item and is used to define transit time and lead time
2. Has a start point and end point and may contain more than one leg
3. Based on departure zone in customizing
4. Based on shipping cond from sold to pty, view shipping
5. Transp grp in material master data, view sales: gen/plant data
6. Transp zone in ship to pty, view gen data

Question 7

8. Dates in ship scheduling (6 items):

Answer 7

1. Order date: order is placed
2. Mat avail date: when goods must be avail for picking and packing
3. Load date: picking and packing completed
4. Goods issue date: goods leave deliv plant
5. Req deliv date: good receipt date req by customer
6. Conf deliv date: goods receipt date conf

Question 8

9. Times considered in ship sched (4 items):

Answer 8

1. Pick/pack time: from mat avail date to load date
2. Transp lead time: from transp planning date to load date
3. Loading time: from load date to goods issue date
4. Transit time: from goods issue date to deliv date (req on backward sched or conf on fwd sched)

Question 9

10. Backward sched (3 items):

Answer 9

1. Req deliv date used to calc mat avail dt (pick/pack = load dt - mat avail dt) and transp plan dt (transp lead time = load dt - transp plan dt)
2. Selection date for outbound deliv is the earliest between mat avail and transp plan dt
3. If one of two dates take place before order date conf of deliv date cannot take place and system attempts fwd sched

Question 10

11. Effect of sched on sched lines (2 items):

Answer 10

1. If backward sched successful, one sched line is created for sales doc item, displaying conf deliv date as req deliv date
2. If backward sched fails, system does fwd sched and creates two sched lines: one with req deliv dt and zero conf qty and one with conf deliv dt and conf qty

Question 11

12. Collective processing in shipping (2 items):

Answer 11

1. Use deliv due list to select multiple deliveries to be created simultaneously, online or via background job
2. Deliv due list is based on selection criteria such as selection date (mat avail dt or transp plan dt) and shipping point

Question 12

13. Deliv options for customers (3 items):

Answer 12

1. Complete deliv x partial deliv
2. Combine orders in deliv using deliv due list
3. Items from diff orders can only be combined in diff deliveries is parameters are shared: shipping point, selection date, ship to, route, incoterms

Question 13

14. Collective processing for picking (3 items):

Answer 13

1. Picking is carried out through transfer orders using deliv quantities for movto with warehouse, allowing print out of picking list
2. Transfer orders can be confirmed auto or not and be processed collectively online or via batch job
3. Collective processing is based on selection criteria such as selection date and ship point

Question 14

15. Collective processing for PGI (2 items):

Answer 14

1. Select from work list based on criteria such as selection date and ship point
2. Process online or via background job

Question 15

16. Collective proc in billing (2 items):

Answer 15

1. Use bill due list to comb items and create as few bill docs as possible, online or via background job
2. Based on bill dt, payer, pay terms

Question 16

17. Billing options (3 items):

Answer 16

1. Invoice split: multiple bill docs for each deliv of sales order
2. Separate bill docs: one bill doc for each deliv of sales order
3. Collective processing: one bill doc for multiple deliv from diff sales orders

Question 17

18. Using worklists (4 items):

Answer 17

1. Deliveries
2. Transfer orders
3. Goods issue
4. Billing docs