Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Order Fulfillment 1 > 24. Deliv Process > Flashcards

24. Deliv Process Flashcards

0
Q
  1. Picking (3): ctrl1, use1, chk1
A
  1. Relevant for pick set in deliv item cat
  2. Pick via Lean WM transfer order recommended for fixed sbin
  3. Del qty x pick qty must be the same for PGI
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
1
Q
  1. Contents (4):
A
  1. Picking
  2. Packing
  3. Goods issue
  4. Spec func
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  1. Pick using WM (3): def1, qty1, cnf1
A
  1. Uses transf order for goods movto inside warehouse complex from source to dest sbin
  2. Del qty auto copied as pick qty
  3. Confirm TO auto when saved or via separate step
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q
  1. Transf order (2): dat2, qty1
A
  1. Contains mat#, qty, source/dest sbin

2. Qty auto copied from outbound del to TO

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q
  1. WM x Lean WM (5): use5
A
  1. Storage sections
  2. Reserve sbin
  3. Strat for put away and picking
  4. Replenishment
  5. Inv at sbin level
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q
  1. Warehouse struc in Lean WM (4): min3, add3, ass2, acv1
A
  1. Min one warehouse number, one source storage type for picking, one destination storage type to receive goods
  2. Picking areas are org units defined for each warehouse#/stor type. There are also doors and stag areas
  3. Warehouse # assigned to each plant/stor type comb
  4. Activate Lean WM in customizing at w/h no level
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
  1. Create/print transf orders (5): cre4, prn3
A
  1. As follow-on func from within deliv
  2. Explicitly with ref to deliv (individually or via del monitor)
  3. Auto/direct for automated proc
  4. Collective proc to grp del and use pick list
  5. Print can be single, comb or pick list
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q
  1. Auto/direct TO procedure (5): use1, out2, sti2
A
  1. Recommended if no pick list
  2. WMTA out type at del hdr to trigger TO auto
  3. WMTA access seq delty/shipp
  4. WMTA send time “later” (1-3) is auto via bkg job or t-cod
  5. WMTA send time “immediately” (4) is direct and trig when del saved
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q
  1. TO collective processing via Deliv Monitor (3): use1, pro3, grp1, prn2
A
  1. Use it to create picking lists
  2. Select deliv in monitor, create a grp for them and then create TOs w/ ref to grp (one TO x deliv)
  3. Picking list is printed auto or man based on print control settings
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q
  1. Picking qty diff using WM (2): alt2
A
  1. Use partial deliv to match pick qty followed by another deliv
  2. Use subsequent picking to complement pick qty
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q
  1. Confirm status in transf orders (4): doc2, fun2, add1, ctrl1
A
  1. TO copies del qty as pick qty and set pick status to C (fully picked)
  2. Pick conf req before PGI and sets WM act status to C
  3. Set diff ind to rec cause of diff
  4. Set in custom x stype (stock removal in source, stock placement in dest storage type)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q
  1. Packing materials (3): mty1, mda2, exa5
A
  1. Defined in mat master rec, normally w/ type VERP
  2. Mmd as pack weight and vol permitted for each ship mat
  3. Examples: carton, pallet, crate, container, truck
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q
  1. Handling unit (3): pty1, txt2
A
  1. Packing type assigned unique sequential number from predefined range
  2. Header contains pack mat info
  3. Overview screen displays quantities of deliv items or other handling units
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q
  1. Packing functions (5): def1, add1, ctr3, sta1, prn2
A
  1. Packing is the process of assigning deliv items to packing mat to produce handling units
  2. Handling units can suffer further packing which is called multilevel packing
  3. Set in customizing whether deliv item cat is relevant for pack: allowed (default), not allowed or mandatory
  4. Packing status gets updated for each outbound deliv item
  5. Two standard output types are setup for printing: packing list at deliv level and shipping label at handling unit level
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q
  1. Packing in SD (6): doc3, cop1, ctr1, fun3
A
  1. Avail in orders as pack prop, out/inb deliv and shipment doc
  2. Order’s pack prop can be copied to deliv via del hdr copy ctrl
  3. Can activate auto pack for each deliv type
  4. Change pack in deliv if PGI not done yet
  5. Copy pack from del to ship to pack all deliv together
  6. Impose pack cond checks such as prev pack if del blk
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q
  1. Packaging mat types and packaging mat grouping (2):
A
  1. Package mat types group similar packaging mat such as out det proc
  2. Mat grouping group mat w/ similar pack requirements like mat with same package req
16
Q
  1. Proposed packaging mat (3): ctr1, mda1, alt1
A
  1. Maint tab “allowed pack mat for each mat grp” in customizing
  2. Maint mat pack grp in mmd
  3. Otherwise mat can be packed in any pack mat dep on w8/vol check
17
Q
  1. Packing instructions (8): exa6, ctr1, use2
A
  1. Packaging mat
  2. Mat to be packed
  3. Text items
  4. Subordinate pack instructions
  5. Rounding, min qty rules
  6. Check profile
  7. Pack instr det uses cond tech
  8. Used as pack prop for online proc or pack rul for auto pack
18
Q
  1. Packing station (3): def1, use1, exa1
A
  1. Deliv and handling units can be packed using pack station
  2. Each pack station can be controlled individually using the terminal ID
  3. Connect keyboard scanner and scales to pack station computer for rapid/precise data entry and also print ship labels to label handling units immediately
19
Q
  1. Packing subsequent processing (3): use1, del2, bil2, add2
A
  1. To manage stock for pack mat sys can gen a deliv item for each pack mat
  2. To auto gen deliv item for pack mat you set in customizing the deliv item cat with PACK usage and the deliv plant must be det using plant det rule in pack mat type or entered manually
  3. You can bill customer for pack mat using item cat grp VERP in mat master (which det item cat DLN) or use returnable pack mat by using item cat grp LEIH (item cat TAL) in which case pack is not copied to bill doc
  4. Subs proc of LEIH using pack pickup order LA then ret del or pack issue order LN then bill
20
Q
  1. Goods issue (3): alt4, add1, def1
A
  1. Via single outbound deliv, collective proc, outbound deliv monitor or when transf order is confirmed
  2. PGI date can be set man when posting individual deliv
  3. Completes shipping process
21
Q
  1. Effect of PGI (6): pst1, red2, upd2
A
  1. Reduces inv stock
  2. Posts value change to stock accts in inv accting
  3. Reduces deliv req
  4. Enter status info in outbound deliv
  5. Is stored in doc flow
  6. Creates a worklist for billing
22
Q
  1. Cancel goods issue (5): pst1, upd2, req2
A
  1. Inv posting carried out with reversed quantities and values
  2. Cancelation doc created is entered in doc flow for outbound deliv
  3. Goods movto status of outbound deliv reset to not yet started
  4. If outbound deliv has been billed or part billed canceling PGI is a 2 step process bc you must first cancel the bill doc
  5. For each movto type in inv mgmt you must define a reversal movto type in customizing
23
Q
  1. Selecting outbound deliv for cancelation (3): par6, pro1, add1
A
  1. Via selection screen entering criteria like: deliv#, ship point, route, goods issue dt, outbound deliv grp and shipment#
  2. Double-click on a list entry to access deliv doc
  3. Sys gen log of cancels or errors
24
Q
  1. QM in shipping (5): def1, mda1, pro2, chk1, prn1
A
  1. Qual inspec for goods issue, like pack inspec
  2. Matl qual insp rel set in mmd/qm
  3. When outbound deliv is created sys creates an inspection lot to indicate items that require inspection
  4. Accept or reject inspection lot via usage decision
  5. PGI can be or not be dependent on inspection results
  6. Print COQ from out ctrl at del item lvl
25
Q
  1. Spec func - batches (4): mda2, pro2, chk1, add4
A
  1. Indicate whether mat is handled in batches in mat master rec views storage1 and purchasing
  2. If batch copied from order it cannot change in deliv otherwise can enter one in the picking screen of outbound deliv
  3. PGI can happen only after batches are specified
  4. Use batch split func (man, auto batch det, via WM) if item deliv quantities are copied from diff batches
26
Q
  1. Spec func - serial numbers (3): mda1, alt2, chk1
A
  1. To use serial# enter serial number profiles in mat master rec
  2. Usually specified in deliv item or order but could also be assigned auto by system
  3. PGI can happen only after serial # assignment
27
Q
  1. Spec func - Pricing in outbound deliv (3): def1, use3, ctr1
A
  1. Outbound deliv may contain ship cond
  2. Can print cond on a deliv note, transfer to bill doc, but cannot copy from preceding docs
  3. Setup in customizing via pricing procedure assignment to del type
28
Q
  1. Spec func - split existing deliv (3): pro1, def1, ctr1
A
  1. Call up a list and select the deliv items, partial qty deliv items or handling units to extract from existing deliv
  2. Deliv is split into one or more deliv called results and remainder
  3. Specify a split profile, which contain control parameters set in customizing and assigned to deliv types
29
Q
  1. Spec func - Deliv interface comm (4): def3, use1, ctr1
A
  1. Normally EDI messages are used for external comm and ALE for internal
  2. Deliv interface groups all EDI and ALE messages related to same delivery in the same IDoc
  3. IDocs are data structures containing deliv doc fields and other ship relevant ones like route and batch info
  4. Output control for deliv header triggers filling of IDocs
30
Q
  1. Spec func - log of incomplete items (3): use1, chk2, ctr2
A
  1. Call it up to gen list of incomplete data in outbound deliv
  2. Sys checks completeness at header and item levels
  3. Set in customizing which fields cause deliv to be incomplete depending on deliv type and deliv item cat
31
Q
  1. Spec func - proof of deliv (4): def1, pro2, bil2, ctr2, mda1
A
  1. Designed to allow invoicing only after customer confirms goods receipt by transfer POD via IDoc
  2. Verification/confirmation are auto using IDoc unless there are discrepancies in which case you finish process man
  3. Bill doc created based on verified qty and bill due list processing is blocked until POD is confirmed
  4. Set which deliv item cat are POD relevant, reasons for deviation and in customer master the POD relevance

Order Fulfillment 1 (23 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions