14. Incompleteness

Question 0

2. Incompletion log (3):

Answer 0

1. List of all data essential in a sales doc that has not yet been entered
2. Define essential data fields in customizing for incompletion procedure
3. Go from incompletion log to various views where you can edit the incomplete data

Question 1

1. Contents (2):

Answer 1

1. Incompletion log

2. Config of incompletion procedure

Question 2

3. List of incomplete orders (2):

Answer 2

1. List incomplete docs or blocked docs due to incompleteness
2. Incomplete orders can be called up from the list and completed

Question 3

4. Incomplete sales docs (2):

Answer 3

1. Set in customizing the incompletion message field for sales doc types to determine if incomplete sales docs can be saved
2. Control the effect of incomplete data: if pay terms are missing order can be deliv but not billed; purch order # is missing but you can continue to process doc

Question 4

5. Control for incompletion log (3):

Answer 4

1. Incompletion procedures define fields checked for completion at header, item and sched line levels
2. Assign procedures to sales doc type for header check, item cat for item check and sched line cat for sched line check
3. Flag partner functions, texts and cond types as mandatory as needed so they appear in incompletion log

Question 5

6. Status of incomplete sales docs (3):

Answer 5

1. A status grp is assigned to each field in the incompletion procedure, defining which steps should fail if data is missing
2. A status grp can be: incomplete for deliv, billing or pricing (no order conf or bill possible)
3. A status grp can contain any number of these consequences and allows to control effects of incomplete data separately for each field