Product Dispatch Processing

8/14/2019 Product Dispatch Processing

http://slidepdf.com/reader/full/product-dispatch-processing 1/18

!"" # $ !%&'(%)*+ , ++- * ++

$

for

SAP SD – Sales and Distribution

Process Name: Product Dispatch Processing

Process No: TRF/O2C/8.0

Control Copy No: TRF/O2C/8.0/

(. ($

/ 01 2 01 01

!

"# #



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ ' , 4)

Introduction

Enterprise Order to Cash process in TRF has the following business processes.

$* * ! ! *

+-. $% /001

2 $% /001

3 4% /00

%4 /00

5 %4 6'7 /0081

9 1 % $% /00

: $% 4% 4% /00;

; (% $% 0/0

$% 0/0

# #4 '# /003

For each of the above processes, a separate End User Training Manuals is available

This document covers sl. No. 7 of the above list, that is Product DispatchProcessing.

This End User Training manual on Product Dispatch Processing consists of the

following sequence of sub-processes as listed in the Table of contents (next page)



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 5 , 4)

< . & /00;

=>)& ? ,% 9

Define and Assign Text Determination Procedures-this is done in spro



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ - , 4)

@, , @. &

< . 44 44 % % 4%! 4%! 4

@ < . 4% 4484 ,# % , 44 %

# %%# 44 4% %# A < .

% 44 % % 4%! . %

44 4% % .

) , < / &

/ ? .4 ,

• $% . 6'7+

• @. ,# 4% 6'7+6'7$B+

/ @. % <? < 4%

• $8- , @.

• @. %

• $%!

• >

• 4

• 1## . # , 4%

• 4

@. 4% <% &

' . 4% # 4 %#4% !

%% < ,#

+# . &

• 4 4.

• @.

• 04%

• ' -.• $%

4 % ? < % %# , 4 # ? %#

@. &

.# ? 4% , < ? < < % ? %# %



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 6 , 4)

$%!&

$%! ? < 4 % #

( 7 0 $1 7 $

. $0$ 7 .

$- & %,# C .# . <%!

# ,# 4% 4# , % . %#

/? < , . %

• 44 4

• @. %

•

• #

•

87 . 2 $1 . $1 $ . . /9++ .

2$$ . . :88# ; (( ( 2.. 2$$ $1

% 44

=>



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ < , 4)

B % % % %. ? 44 % ? .

! "

/? < , . %

o 44 4

o @. %

o

o #

o

2. 4 4 . %# 4 . <. #,. -. <. % ? . %#

? <. 4% %

( % , C4 %# 44 4%! ? 4%! ,# % <

4 . %# < % % ,? 4# -

<- 4% %%. % .



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 3 , 4)

% 4. ! , 44 4 4 ,# %

%%! <

% ? < 4. ? ? %%! D7 D < % <

4.

A

,



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ ) , 4)

% 4. ,# ? %%! 4 #4. 4<

4

% 4. %%! 4 < ? % ? ! . 4 4 4

%!

$

$



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ = , 4)

87 2 $ $> $ 7 $ . 0 ?

Define and Assign Text Determination Procedures-this is done in spro

The text types of a text object are grouped together in text determination procedures. You assign a textdetermination procedure using certain keys, for example, account group customer or sales document type.

The SAP System offers the text types of the corresponding text determination procedure for maintenance, forexample, when you are editing a customer master record of the assigned account group customer or a salesdocument of the assigned sales document type.

In this menu option you set the following defaults:

• You define the text determination procedures.

• You assign the text determination procedures for automatic text determination.

To define a text determination procedure you have to set the following defaults for every text type:

• Dupli (duplicating when copying a text)

If you select "yes", the text is duplicated from the reference. It can be changed, but needs more storage

space. If you select "no", the text is copied from the reference, but cannot be changed.

• FGrp (error group)

Using the error group, you can mark texts as relevant for the incompletion log of the sales documents. If a

relevant text of this text type is missing in the sales document, a note is included in the incompletion log.

• Required

Here, you indicate whether the existence of a text is obligatory, or whether the SAP System should only

propose the text type.

In addition, you can indicate which texts the SAP System should display in a pop-up window in case of

copying (for example, from the customer master record into a sales document).

• Sequence (assignment of an access sequence)

For text determination in the sales & distribution documents, you assign an access sequence to the text

types in the procedure. The access sequence defines how the SAP System is to search for the texts.

For the text object "customer master record you do not specify access sequences since these texts are not

copied but manually specified by the user.

Afterwards you assign the defined text determination procedures as follows:

Text object Key

Customer master record Account group

Sales document header Sales document type



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 4+ , 4)

Sales document item Item category

Delivery header Delivery type

Delivery item Item category

Billing header Billing type

Billing item Billing type

CAS CAS sales activity type

Note

Currently you cannot set up your own error groups for the incompletion log for texts in customizing.

In the standard SAP R/3 System, error group "50" is defined for texts. The incompletion log takes it into account if thetexts are additionally characterized as required in the procedure.

Requirements

You can only include text types and access sequences in a procedure which you have defined beforehand (see thesection "Define text types" and "Define access sequences").

• The account groups, document types, and item categories must already be defined. They are then proposedto you automatically for assignment.

Actions

1. Check to what extent you can use the text determination procedures contained in the standard SAP R/3

System.

2. Change the existing text determination procedures according to your needs or create new ones.

To do this, branch to the text determination procedures for a text object and display the texts in the

procedure.

3. Assign the text determination procedures.

There are 2 ways to do this:

o by calling up the text determination procedure assignment

Here, you can carry out the assignment for the selected text determination procedure.

o by calling up text determination procedure usage

Here, the assignments are displayed for the account groups, the document types and item

categories.



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 44 , 4)

)C %%! 4 % < ? < % , . @4% 4

? $"( ! 4 , @. %# % $"( , . %# , 6 ,

/% 4# +C

• $8,# % % , C4 , 4%

• ##% % % , #% 4%

&

$%! 4 , %! < 4 4%! % C #

1$

% 4. ? @. < 5

@ %



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 4' , 4)

/9+= ($$ 7 "#8

($$ 7 7 $1 01 . , $"( < <, , < 0

% %#

" ?. 4 % < %%

/? < ,

• 44 4

• @. %#

• * ,# 4% 4# % % . %# %,#

%%! DE <

• .# # , %%, %% , , .

• .# # %# # , $"( / @+>(=+B @*'+)

+=+1> / $"( , .

(, . ?! , . , . %# ? 44 4 ,

@4% 4 % $"( , # . , ?% .

1< 4% , ## ? < 44%< , .4 . %#

• @. ,# 4%

• < . %#

% 4. % D < .E ,# % %%! C% < ,# < %

? 4. # %%, %% , <

< .



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 45 , 4)

87 2 . . & 0 $1 . . /9+'

. /9+'

% ? . % - ? 4%!

% 4. @. %# ( 5 % < 4 < <

? ? % . #! !4 % < 4 #! %



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 4- , 4)

87 2 . . 0 $1 2. . $ . . /9+'

+ . %# 5 4

% 4. % %



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 46 , 4)

87 . 2 2 . 7 $1 . . /9+5

. /9+5

% 4. . %# %%! <

% 4. ? %%! %# ,? <

@%# ,?



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 4< , 4)

% 4. ?



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 43 , 4)

87 . 2 $1 $$ . $ 2. : 7 $ . /9+5

% 4. %# , C 5

% 4. , . ? 4. % %



$%& '(() *+

!"" # $ !%&'(%)*+ , ++3 * ++

$ 4) , 4)

% 4. ? ? <

7 " !"" # $ !%&'(%)*+ , ++3 * ++

Documents

Product Dispatch Processing