You are on page 1of 64

Table of Contents

Configuration of FSCM Dispute Management.............................................................2


Case Record Model.....................................................................................................2
Attribute Profile..........................................................................................................6
Case Search..............................................................................................................1
Function Profile.........................................................................................................1!
"e#t Profile...............................................................................................................2$
Status Management.................................................................................................26
Maintain %umber Ranges.........................................................................................$&
Case "'pe.................................................................................................................$2
Create Attribute (alues............................................................................................$
)or*flo+...................................................................................................................$!
Process ,ntegration...................................................................................................2
Process ,ntegration +ith Accounts Recei-able Accounting.......................................!
Correspondence......................................................................................................../
Configuration of FSCM Dispute Management
"he follo+ing section outlines basic configuration steps re0uired to set up FSCM
Dispute Management in a one1s'stem scenario. "his information is based on 2CC
6.& +ith 2nhancement Pac* 2 functionalit'3 ho+e-er4 not all acti-ities in the ,M5
ha-e been included.
Case Record Model
"he case record model defines +hich t'pe of ob6ects can be lin*ed to a dispute
case. 7in*ed ob6ects pro-ide one1clic* access to related customer master data and
financial documents4 for e#ample. ,f 'ou need to create a ne+ case record model4 it
is recommended that 'ou cop' the SAP1standard model and modif' as needed.
1.1 Create Case Records Model
Customi8ing the case record model is client1independent. "o begin configuration
acti-ities4 please refer to the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : 2lement "'pes and Case Record
Model : Create and Process Case Record
Model
Transaction Code SCAS2
1.1.1 Building a Case Record Model using the S!"Standard RMS ID
#DM$DIS!#T%
1. Select Role1;ased (ie+ and drill do+n on SAP Dispute Management : Record
and Case Record Models
2. Right1clic* on Modeler for Case Records in Dispute Management and select
Find
$. Clic* on the search button
. Double clic* on the desired SAP1standard dispute management entr'
.. 7ocate the case record model in 'our histor'. Right1clic* and select <ther
Functions : Cop' Model. Please refer to the belo+ illustration for
clarification.
6. "he modeler +ill indicate that a cop' has been made. Clic* on the sa-e
button in the records modeler.
/. Clic* on the model attributes button and modif' the short description and
uni0ue ,D as desired. Clic* on the continue button to e#it the attributes
popup menu.
!. Clic* on the Model button and select Change Status. Select Status Released
and clic* on the continue button to sa-e the status.
Please note4 changing the status to final is not recommended. ;' changing the
status to final4 'ou +ill not be able to ma*e changes to the case records model.
=pdating the status to Status <bsolete +ill pre-ent ne+ cases from being
created +ith this case record model.
>. "o transport the case record model4 locate the case record model in 'our
histor'. Right clic* and select <ther Functions : "ransport 2ntr'.
,n order to deri-e the case records model ,D4 so that it can be associated to the
appropriate case t'pe4 find the case model record in the histor' section. Right1clic*
on the ne+l' created case model record and select information. "he case model
record ,D +ill be displa'ed ne#t to the document ,D field.
ttribute !rofile
"he dispute case attribute profile controls the displa' and the beha-ior of all
attributes displa'ed in the dispute case.
All fields contained in the dispute case =DMCAS2A""R&& and SCM5?"?CAS2?A""R
tables can be added to the dispute case displa'. Some of the standard dispute case
attributes ha-e been pro-ided belo+ for 'our reference. ,f 'ou need additional
fields for displa' on the dispute case4 the' must be added to the =DMCAS2A""R&&
table before the' can be configured in the attribute profile.
Table
SCMG$T$CS%$TTR
Table
#DMCS%TTR&&
'abel ttribute (ame 'abel ttribute (ame
Case "'pe CAS2?"@P2 ;loc* ,ndicator F,%?S2MAPA<R2
Case ,D 2B"?C2@ Created ;'DRFCE F,%?RFC?CR2A"<R
2#ternal refer. 2B"?R2F Coordinator F,%?C<<RD,%A"<R
Created ;' CR2A"2D?;@ Root Cause Code F,%?R<<"?CC<D2
Created <n CR2A"2?",M2 Process. Deadline F,%?D=2?DA"2
Changed ;' CAA%52D?;@ <rig. Disp. Amt F,%?<R,5,%A7?AM"
Changed <n CAA%52?",M2 Disputed Amount F,%?D,SP="2D?AM"
Closed b' C7<S2D?;@ Paid F,%?PA,D?AM"
Closed At C7<S,%5?",M2 Credited F,%?CR2D,"2D?AM"
Planned Close Date P7A%?2%D?DA"2 Cleared Manuall' F,%?)R"?<FF?AM"
Processor PR<C2SS<R Autom. )ritten <ff F,%?%<"?S<7(?AM"
Person Respons. R2SP<%S,;72 Currenc' F,%?D,SP="2?C=RR
Aeading CAS2?","72
Customer1Disputed
Amount F,%?C=S"D,SP?AM"
2scalation Reason 2SCA7?R2AS<%
Currenc' of
Customer1Disputed
Amount F,%?C=S"D,SP?C=R
Categor' CA"25<R@ Contact Person F,%?C<%"AC"?%AM2
Priorit' PR,<R,"@ e1mail F,%?C<%"AC"?MA,7
Auth. 7e-el S2C=R2?72(27 "elephone %o. F,%?C<%"AC"?"27
Status Profile PR<F,72?,D Fa# %umber F,%?C<%"AC"?FAB
Status S"A"?<RD2R%< Ctr' of Fa# %o. F,%?C<%"AC"?FABC
S'stem Status S"A"?PARA Contact Person Ce' F,%?C<%"AC"?C2@
<b6ect 5=,D S"A"?<;F%R Customer F,%?C=%%R
S'stem Status S"A"?7,%2 Compan' Code F,%?;=CRS
1.) Create ttribute !rofile
,f 'ou need to modif' the standard la'out4 create a cop' of the SAP1deli-ered profile
F,%?D,SP="2 or F,%?D,S2 for customer1disputed ob6ects and use it as a template to
modif' as needed. "o begin4 please refer to the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide
:Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing :Attribute Profile : Create
Attribute Profile
Transaction Code SPR<
1. Aighlight the F,%?D,SP SAP1deli-ered attribute profile for dispute
management.
2. Right1clic* and select Cop' As.
$. Rename the attribute profile and profile description.
. Select cop' all to cop' all dependent entries
.. Aighlight the ne+l' created attribute profile
6. Double clic* on Assign Attributes to begin modifications
,nsert and remo-e case attributes as needed. For each attribute 'ou can also
perform the follo+ing acti-ities9
Group G "his field splits the attribute displa' into different areas. SAP
recommended -alue is H1I for all attributes.
Ro* G %umber of the ro+ +hich the attribute is displa'ed +ithin each
attribute group.
Column G %umber of the column +hich the attribute is displa'ed +ithin each
attribute group. @ou can onl' input up to t+o columns.
Re+uired G Set this indicator if the attribute is mandator'.
In,isible G Set this indicator if the attribute is not -isible.
Dropdo*n G Set this indicator if the attribute has a list of possible -alues for
displa'. Sample attributes +ith -alue lists include priorit'4 status4 escalation
reason4 categor'4 reason code and root cause code.
Chec-bo. G Set this indicator if the attribute -alue should be displa'ed as a
chec* bo#.
(ot Modifiable G Set this indicator if the attribute is displa' onl'.
Modifiable (e* G Set this indicator if the attribute can onl' be modified
upon creation of the dispute case.
'og G Set this indicator if changes to this attribute should be recorded in the
dispute case log.
1./ ttribute 0alues
"he follo+ing acti-ities describe ho+ to define -alues for prioriti8ation of a dispute
case along +ith escalation reasons that are used for automatic +rite1off of the
dispute case.
1./.1 !riorit1
"o modif' dispute case priorit' -alues4 please follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management
:Dispute Management : Dispute Case
Processing : Attribute Profile : Attribute
(alues : Create (alues for Attribute JPriorit'K
Transaction Code SPR<
1. ,nsert a uni0ue priorit' ,D and priorit' description.
2. Clic* on sa-e
1./.) ttribute !rofile
After the escalation reasons ha-e been configured4 'ou need to identif' +hich
escalation reasons are -isible in the appropriate attribute profile. "o begin4 please
follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Attribute Profile : Attribute
(alues : Assign 2scalation Reasons to an
Attribute Profile
Transaction Code SPR<
1. Select the attribute profile clic* on continue
2. Clic* on the %e+ 2ntries button
$. ,nsert each escalation reason that should be a-ailable for selection
. Clic* on Sa-e
Case Search
"he case search profile defines D1E +hich dispute case attributes are used to search
for a dispute case as +ell as D2E +hich dispute case attributes can be updated using
the mass change function +hen selecting the change field content button from the
case search screen. ,f 'ou +ould li*e to modif' the SAP1deli-ered case search
profile F,%?7<C4 please create a cop' and use it as a template for 'our
modifications. After the ne+ case search profile is created4 please remember to
create a ne+ element t'pe based on the SAP1deli-ered =DM?SPS?CAS2?7<CA"<R
element t'pe. <nce created4 replace the locator profile ,D parameter -alue +ith the
ne+l' configured case search profile ,D.
1.2 Create !rofile for Case Search
,f 'ou are using the SAP1deli-ered RMS ,D =DM?D,SP="24 please use the S!"
deli,ered profile to a,oid creation of a ne* element t1pe for
#DM$S!S$CS%$'3CT3R. ,f the F,%?7<C case search profile does not e#ist4
create a ne+ search pro-ide and ensure the case search profile name is F,%?7<C.
;egin configuration b' follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Case Search : Create Profile for
Case Search
Transaction Code SPR<
1. Aighlight the F,%?7<C case search profile
2. Right1Clic* and select Cop' As
$. Rename the Profile ,D and Profile description
. Ait 2nter and select the cop' all button to cop' all dependent entries
.. Add4 remo-e and modif' selection fields
6. Add or remo-e modifiable fields as needed
/. Clic* on Sa-e
,nsert and remo-e case attributes as needed. For each attribute 'ou can define the
follo+ing items9
Ro* G %umber of the ro+ for attribute displa' in the case search selection
screen.
Column G %umber of the column for attribute displa' in the case search
selection screen.
Case ttributes G Case attribute from the dispute case =DMCAS2A""R&&
and SCM5?"?CAS2?A""R tables.
dditional Selection 3ptions G Set this indicator if multiple selections
against this attribute are allo+ed.
Function !rofile
Modif' the function profile to control +hich actions are allotted in the dispute case.
Functions are acti-ated b' clic*ing on the corresponding button to e#ecute the
desired acti-it'4 such as getting customer contact information4 generating
correspondence or sa-ing a dispute case for e#ample.
SAP1deli-ered functions for dispute management ha-e been summari8ed belo+9
Function (ame FunctionT1pe Function Description
F,%?ADD?C=S"D,SP?<;F Function
Add Customer1Disputed
<b6ect
F,%?ADD?%2)?D,SP?7,%2?,"2M Function Add Disputed <b6ect
F,%?ASS,5%?C=S"<M2R Function Assign to Customer
F,%?CA7C?CD,S?AM<=%" Function
Calculated Customer1
Disputed Amount
F,%?C<%"AC" Function Contact Person
F,%?C<%"AC"?CAA%52?7<CA7 Function Change Contact Person
F,%?C<%"AC"?52" Function 5et Contact Person
F,%?C<%"AC"?7,S" Function 7ist Contacts
F,%?C<RR?CR2A"2 Function Create Correspondence
F,%?2BC?"R,552R Function 2#ecute Actions
F,%?<;F2C"S Function F, <b6ects
F,%?R2M<(2?7,%2?,"2M Function Remo-e <b6ects
F,%?SA<)?"R,552R Function Displa' Actions
F,%?"R,552R Function Actions
PR,%" Function Print
R2FR2SA Function Refresh
R2S, Function Reduce Attributes
SA(2 Function Sa-e
S"A"=S?ACC2P" Function Confirm
S"A"=S?R2<P2% Function Resume
S"A"=S?(<,D Function (oid
"<5572?D,SP7A@?CAA%52 Function Displa' L11:Change
S=;C<MP<%2%"?7<5 Case Component Case 7og
S=;C<MP<%2%"?%<"2S Case Component %otes
S=;C<MP<%2%"?R2C<RD Case Component 7in*ed <b6ects
1.4 Create Function !rofile
,f 'ou need to modif' the SAP1deli-ered function profile4 create a cop' of the
F,%?D,SP or F,%?D,S2 function profile and use it as a template for 'our
modifications. "o begin follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Function Profile : Create
Function Profile
Transaction SPR<
1. Aighlight the desired SAP1standard function profile
2. Right1clic* and select Cop' As
$. =pdate the function profile ,D and description
. Ait 2nter
.. Clic* on the cop' all button to cop' all dependent entries
6. Aighlight the ne+l' created function profile and clic* on allo+ed functions
and allo+ed case components to modif' as needed
/. Clic* on Sa-e
Cop' the F,%?D,S2 function profile
For each function and case component 'ou can define the follo+ing items9
Function 1 ,dentif' function or case component in the function profile
Se+uence of Function Buttons G <rder in +hich the functions are
displa'ed in the dispute case
Separator fter !ushbutton G Select this indicator if a separating line
should be placed after the button
ssigned Menu G Contains dropdo+n menu to +hich the function is
assigned
Icon (ame G %ame of the icon associated to the function
(o Create G Select this indicator if the button is disabled upon creation of
the dispute case
(ot for Modif1 G Select this indicator if the function is not a-ailable for
modification
(o Displa1 G Select this indicator if the function is not a-ailable for displa'
Button *ith Menu G Select this indicator if the function has a push button
+ith a menu
Te.t !rofile
Creation of a te#t profile defines +hich t'pes of notes are contained in the dispute
case. %otes are used to capture the research and resolution of a disputed item
throughout the dispute case life c'cle. "he' can also be displa'ed on claim
correspondence to the customer re0uesting additional information or re0uesting
repa'ment for in-alid deductions.
1.5 Create Te.t !rofile
,f the SAP1deli-ered notes do not suffice4 please create a cop' of the F,%?D,SP or
te#t profile ,D and use it as a template to modif' the e#isting -alues. "o begin
configuring a ne+ te#t profile4 follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : "e#t Profile : Create "e#t
Profile
Transaction Code SPR<
1. Aighlight the F,%?D,SP te#t profile ,D
2. Right1clic* and select Cop' As
$. =pdate the te#t profile ,D and description
. Ait 2nter
.. Clic* on the cop' all button to cop' all dependent entries
6. Aighlight the ne+l' created te#t profile and clic* te#t ,DKs to modif' as
needed
/. Clic* on Sa-e
For each note t'pe 'ou can define the follo+ing items9
ID 1 =ni0ue identification for each note t'pe
Meaning G Description for each note t'pe
Se+uence G <rder in +hich the note t'pes are displa'ed in the dispute case
note drop do+n
In,isible %.ternall1 G Select this indicator if the note should not be
displa'ed on correspondence. "his te#t +ill be in-isible to the customer.
Status Management
"he status of a dispute case indicates +here the stage in of deduction resolution the
dispute case processing is. Status -alues and e-ents are used to control +hen
status -alues can be set and enable automatic status updates.
=pon creation of a dispute case the status +ill automaticall' be set to ne+. After
updates are made to the dispute case4 the status +ill be updated to reflect an in
process status. <nce a resolution has been determined b' the dispute case
processor4 he or she can manuall' update the processing status to Chargebac* or
Appro-ed to indicate the claim -alidit' or to ;ac*up Re0uested to indicate the claim
processing status4 for e#ample. <nce the claim has been paid b' the customer4
cleared +ith a credit4 andMor +ritten off the dispute case status +ill automaticall'
update to Closed. Closed dispute cases can also be updated to a confirmed status
for permanent closure.
1.6 Create Status !rofile
"o create a status profile4 please create a cop' of the F,%?D,SP status profile and
use it as a template for building the ne+ status profile. "o begin4 follo+ the belo+
,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Status Management : Create
Status Profile
Transaction Code SPR<
1. Aighlight the F,%?D,SP status profile
2. Right1clic* and select Cop' As
$. =pdate the status profile ,D and description
. Ait 2nter
.. Clic* on the cop' all button to cop' all dependent entries
6. Aighlight the ne+l' created status profile and clic* on status -alues to modif'
as needed
/. Clic* on Sa-e
For each status4 'ou need to configure the follo+ing items9
Status G =ni0ue ,D for the status
Status Description G Description for the status -alue
S1stem Status G Select a s'stem status that should be associated to each
status. S'stem status -alues are as follo+s9
S1stem Status Description G <nce a s'stem status has been input4 the
corresponding status description +ill automaticall' populate +hen hitting
return
'o* Status N 7igh Status G Se0uence numbers +hich control changes in
status. A status can be set if the current status is greater than or e0ual to
the lo+est se0uence number and smaller than or e0ual to the highest
se0uence number.
uto G Set this indicator if the status is set automaticall'
%,en for Case G Select +or*flo+ e-ent to be generated upon the dispute
case status change.
Maintain (umber Ranges
=pon creation of a dispute case4 a s'stematicall' generated number is assigned to
the dispute case ,D. "he number range for generation of the case ,D is uni0ue to
each case t'pe. "o create a number rage4 please follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Define %umber Range ,nter-al
for Case
Transaction Code SCAS2?%=M;2RRA%52
1. Clic* on the Change ,nter-als button
2. Clic* on the ,nsert ,nter-al button
$. ,nsert a uni0ue number rage and select the e#ternal indicator for e#ternal
number issuance.
. Clic* on Sa-e.

Case
"'pe
Case T1pe
A dispute case t'pe is a central ob6ect that groups customi8ing settings together to
define the -arious components4 profiles and attributes of a dispute case. A case
t'pe can be assigned to one or man' compan' codes. "herefore4 the loo* and feel
of dispute cases +ill remain consistent across a particular compan' code.
Case "'pe Components

Case
"'pe
1.8 Define Case T1pe
"o create a ne+ case t'pe4 please create a cop' of the F?DM SAP1deli-ered dispute
management case t'pe and use it as a template. "o begin4 follo+ the belo+ ,M5
menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Case "'pes : Define Case
"'pes
Transaction Code SPR<
1. Aighlight the F?DM dispute management case t'pe
2. Right1clic* and select Cop' As
$. =pdate the case t'pe and case t'pe -alues based on the customi8ing
acti-ities completed abo-e
. Clic* on Sa-e
Case
Record
Elemen
t Type
Case
Notes
Element
Type
Case
Attribut
es
Status
Text
Profile
Numbe
r
Range
RMS ID
Case
Record
s Model
unctio
ns !
Case
Compo
nents
Dispute
Case
Elemen
t Type

Case
"'pe
Create ttribute 0alues
<nce 'our case t'pe has been created4 'ou can begin the creation of -alues for the
categor'4 reason code and root cause code dispute case attributes. All three of
these attributes enable -isibilit'4 reporting and root cause anal'sis for 'our
deduction population.
Categor1 is a classification of the dispute case +hich can be used to subdi-ide
case t'pes. Sample categories are as follo+s9
Pet Products
Personal A'giene Products
%on1Product Related
Post Audit
Cause is the reason for the customerKs dispute and can be s'nchroni8ed +ith the
reason code in F,1Accounts Recei-able. Reason codes can also used to dri-e the
prioriti8ation and deri-ation of a 5M7 account for automatic +rite1off. Please see
belo+ for sample reason codes9
Shortage
Pricing
Returns
Root cause code captures the issue supporting claim resolution4 or +h' the claim
is appro-ed4 +ritten off or billed bac* for e#ample. Sample root cause codes are as
follo+s9
P<D ,ndicates Complete Deli-er'
P<D ,ndicates Partial Deli-er'
Carrier 2rror
Discount %ot Applied to ,n-oice
Sales Department 2rror
1.9 Create 0alues for ttribute Categor1
"o begin creating categor' -alues4 please follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Case "'pes : Create (alues for
Attribute HCategor'I
Transaction Code SPR<
1. Clic* on the %e+ 2ntries button
2. 2nter the case t'pe
$. 2nter a uni0ue categor' code per case t'pe
. 2nter the categor' description
.. Clic* on Sa-e
1.1& Create 0alues for ttribute Reason
Start adding dispute case reason codes b' follo+ing the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Case "'pes : Create (alues for
Attribute HReasonI
Transaction Code SPR<
1. Clic* on the %e+ 2ntries button
2. 2nter the case t'pe
$. 2nter a uni0ue reason code per case t'pe
. 2nter the reason code description
.. Clic* on Sa-e
1.11 Create 0alues for ttribute Root Cause Code
"o begin adding root cause codes4 follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Case "'pes : Create (alues for
Attribute HRoot Cause CodeI
Transaction Code SPR<
1. 2nter case t'pe in the +or* area
2. Clic* on Continue to proceed
$. Clic* on the %e+ 2ntries button
. 2nter a uni0ue root cause code
.. 2nter the root cause code description
6. Clic* on Sa-e
:or-flo*
=sing +or*flo+ +ill enable cross1departmental collaboration b' sending automatic
notifications to a dispute case processor. SAP Dispute Management is e0uipped
+ith t+o standard +or*flo+ templates. )or*flo+ template )S &1/&&& controls
the notification and sending of dispute case +or* items. <nce a +or* item has been
generated4 it can be access in one of t+o +a's9
From SAP ;usiness )or*place4 or -ia transaction S;)P.
From 'our +or*flo+ inbo# in the dispute case organi8er using transaction
=DM?D,SP="2. Please refer to the belo+ diagram for clarification.
Clic* on 'our ,nbo# to displa' +or*flo+ notifications
assigned to 'ou as the dispute case processor. Drill
do+n on ,nbo# : )or*flo+ and double1clic* to open
the dispute case +or* item.
"o enable e1mail notifications4 'ou +ill also ha-e to acti-ate +or*flo+ template )S
&1/&&&.1. 21mail notifications +ill automaticall' be sent to the dispute case
processor using the email address maintained in their SAP user profile.
;efore +or*flo+ notifications can be sent4 please ensure the follo+ing tas*s ha-e
been completed b' 'our s'stem administrator.
Maintain standard settings for SAP ;usiness )or*flo+
SAPconnect has been configured for generation of e1mails
1.1) !erform tas-"specific Customi;ing
"o acti-ate SAP1standard +or*flo+ for dispute management4 'ou need to acti-ate
the e-ent lin*age for each +or*flo+ template in the F,%1FSCM1DM1DM application
component. "o begin4 follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : )or*flo+ : Perform tas*1
specific Customi8ing
Transaction Code SPR<
1. Drill do+n on application component SAP : F,% : F,%1FSCM : F,%1FSCM1DM
2. %e#t to the ;asic Functions application component for F,%1FSCM1DM1DM4
please clic* on Acti-ate e-ent lin*age
$. Select the detail -ie+ button ne#t to the )S &1/&&& +or*flo+ template for
notification and sending of dispute case +or* items.
. Clic* on the 2-ent 7in*age Acti-ated chec* bo#
.. Ait sa-e to transport the entr'
6. Clic* on continue
/. ,f 'ou +ould also li*e to generate email notifications4 repeat the e-ent lin*age
acti-ation steps for +or*flo+ template )S &1/&&&.1.
1.1/ Define Regular !rocessor for Dispute Cases
A regular dispute case processor is someone +ho logs into SAP dispute
management on a regular basis for processing and resolution of dispute cases
assigned to him or her as the processor. Since logging into SAP dispute
management is part of their dail' acti-ities4 'ou ma' not +ant to clutter their email
or +or*flo+ inbo# +ith +or* item notifications.
Ao+e-er4 for occasional processors +ho are not accustomed to logging into SAP
dispute management on a regular basis4 generation of a +or*flo+ notification +ill
inform them that a dispute case has been assigned to them for processing.
"o enable +or*flo+ notifications for occasional processors onl'4 'ou need to
maintain the SAP user ,D for all regular processors in this customi8ing acti-it'.
Since end user ,DKs for regular processors ma' not be maintained in the golden
client for configuration4 this +ill be a manual cuto-er tas* for maintenance in each
client.
"o begin defining regular dispute case processors4 please follo+ the belo+ ,M5
menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : )or*flo+ : Define Regular
Processor for Dispute Case
Transaction Code SPR<
1. ,nput the appropriate case t'pe
2. ,nput the user ,D for each regular dispute case processor
$. Clic* on sa-e
!rocess Integration
,n this section +e +ill carr' out customi8ing acti-ities that +ill automate changes to
the status attribute +ithin the dispute case and determine the appropriate te#t ,D
for notes entered upon creation of a dispute case.
1.12 Define utomatic Status Changes
"hroughout the dispute case life1c'cle4 certain statusKs can be set to update
automaticall' based on clearing acti-ities in F,1Accounts Recei-able. "his
customi8ing acti-it' +ill allo+ 'ou to maintain the -alue of the status after the
follo+ing acti-ities occur9
utomatic Reopen G <nce a dispute case has been closed4 it can be re1
opened if the accounting document lin*ed to the closed dispute case has
been reset and re-ersed using transaction F;RA.
utomatic :rite"3ff G ,f the accounting documents lin*ed to the dispute
case ha-e been automaticall' +ritten1off using transaction =DM?)R,"2<FF4
the status can be automaticall' updated to closed.
utomatic Close G )hen the lin*ed accounting documents4 associated to
the dispute case4 ha-e been cleared against a credit or incoming pa'ment4
the status can be automaticall' updated to closed.
"o begin defining the status4 +hich +ill be populated automaticall' based on
clearing acti-ities in F,1Accounts Recei-able 4 please follo+ the belo+ ,M5 menu
path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Process ,ntegration : Define
Automatic Status Change
Transaction Code SPR<
1. ,nsert case t'pe
2. ,nsert the ,n Process status for Automatic Reopen
$. ,nsert the Closed status for Automaticall' )ritten <ff
. ,nsert the Closed status for Automatic Close
.. Clic* on Sa-e
,f 'ou lea-e an' of these -alues blan*4 the status +ill not update automaticall' after
the -arious clearing acti-ities ha-e been performed in F,1Accounts Recei-able.
1.14 Define Te.t ID for (otes
"e#t ,DKs define -arious note t'pes +hich can be recorded throughout the deduction
creation and resolution c'cle. "his customi8ing acti-it' +ill allo+ 'ou to define
+hich note t'pe4 from 'our te#t profile4 that should be assigned to an' comments
input at the time of dispute case creation.
"o select the appropriate note t'pe for dispute case creation4 please follo+ the
belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Process ,ntegration : Define
"e#t ,D for %otes
Transaction Code SPR<
1. ,nput case t'pe
2. ,nput the Accounting origin
$. Select the desired note t'pe. ,n the e#ample pro-ided belo+4 the &&&1
Description note t'pe +ill be used to capture notes upon dispute case
creation.
1.15 Define Triggering ttributes for Document Changes
,n this customi8ing acti-it'4 'ou can define +hich attributes from dispute
management can trigger a change to the lin*ed accounting documentDsE. For
e#ample4 a change in the dispute case reason code can update the corresponding
AR line item reason code. <r4 a change in the dispute case status and reason code
can update the dunning bloc* on the corresponding AR line itemDsE. Please note
that this s'nchroni8ation onl' occurs from the dispute case to the AR line item and
not from the AR line item to the dispute case.
"o define +hich dispute case attributes can trigger a document change4 please
follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Process ,ntegration :
Automatic Document Changes from Dispute
Cases : Define "riggering Attributes for
Document Changes
Transaction Code SPR<
1. ,dentif' the case t'pe and corresponding dispute case attributes +hich +ill
trigger changes to AR documents
2. Clic* on sa-e to generate the transport re0uest
"o complete customi8ing of this feature4 please ensure 'ou complete the steps for
Automatic Document Changes from Dispute Cases co-ered in the Process
,ntegration +ith Accounts Recei-able Accounting section.
ADD %2) S2C",<%
!rocess Integration *ith ccounts Recei,able ccounting
,n order to create dispute cases for open F,1Accounts Recei-able line items4 'ou
need to acti-ate the process integration +ith accounts recei-able and assign the
case t'pe along +ith default -alues to each compan' code participating in dispute
management. ,n this section 'ou +ill also ma*e other settings that are integrated
+ith accounts recei-able li*e4 for e#ample4 D1E defining +hich 5M7 account to +rite
off dispute cases to or D2E map out +hich attributes in AR +ill be updated based on
changes to certain dispute case attributes.
1.16 cti,ate !rocess Integration for S! Dispute Management
Acti-ating the integration of F,1Accounts Recei-able +ith SAP Dispute Management
is client1independent. "his tas* can be performed b' follo+ing the belo+ ,M5 menu
path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management
:Process ,ntegration +ith Accounts
Recei-able Accounting : Acti-ate Process
,ntegration for SAP Dispute Management
Transaction Code SPR<
$. Please clic* on the acti-e chec* bo# to acti-ate
. Clic* on sa-e to generate the +or*bench re0uest
1.18 Define Default 0alues for Creation of Dispute Cases
<nce the integration bet+een F,1Accounts Recei-able and SAP Dispute Management
has been acti-ated4 'ou can begin the assignment of the case t'pe to each
compan' code participating in dispute management along +ith assignment of
default -alues upon dispute case creation. "o begin4 please follo+ the belo+ ,M5
menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management
:Process ,ntegration +ith Accounts
Recei-able Accounting : Define Default
(alues for Creation Dispute Case Processing
Transaction Code FDMC=S"&1
1. "o assign a compan' code to a dispute case t1pe4 scroll do+n to the desired
compan' code and select the appropriate case t'pe.
2. <nce the case t'pe has been assigned4 double1clic* on the compan' code to
assign default -alues.
$. Select the default -alue for the categor1. Please note that this -alue +ill be
o-erridden if D1E a ;Adi has been acti-ated for automatic deri-ation and
population of the categor' upon dispute case creation or D2E the -alue is
manuall' o-erridden in the create dispute case dialog bo#.
. Select the default reason code. "his -alue +ill be o-erridden if D1E the F,1AR
reason code to Dispute Management reason code mapping has been
maintained4 D2E if a ;Adi has been acti-ated for automatic deri-ation and
population upon dispute case creation or D$E if the -alue is manuall'
o-erridden in the create dispute case dialog bo#.
.. Select the default priorit1. "he priorit' +ill also be o-erridden if D1E the
reason code to priorit' mapping has been maintained4 D2E if a ;Adi has been
acti-ated for automatic deri-ation and population upon dispute case creation
or D$E if the -alue is manuall' o-erridden in the create dispute case dialog
bo#.
6. @ou can also determine ho+ the e.ternal reference field in the dispute case
is populated upon dispute case creation. ,f the field selected in the first
priorit' is maintained4 for the associated F,1Accounts Recei-able document4
this -alue +ill be maintained in the e#ternal reference field +hen the dispute
case is created. ,f the field identified in the first priorit' is null4 then the
s'stem +ill chec* for the -alue of the field identified in the second priorit'.
"his process +ill repeat until a -alue has been identified for the highest
priorit' field. As +ith the categor'4 reason code and priorit'4 this -alue can
al+a's be o-erridden.
/. Double1clic* on the reason code folder to begin the reason code and priorit'
mapping.
!. ,nput the F,1Accounts Recei-able reason code and corresponding dispute
management reason code. @ou can also identif' a default priorit' b' reason
code upon dispute case creation.
>. Repeat this process for each compan' code participating in SAP dispute
management.
1&.Clic* on the sa-e button to complete 'our changes
1.19 Customer"Disputed 3b<ects in Dispute Cases
Creation of a customer1disputed dispute case enables the creation of a pre1
deducted dispute case4 or a dispute case +ithout reference to an open AR line item.
Accounting documents can subse0uentl' be lin*ed to Customer1Disputed dispute
cases in the follo+ing manner9
Manuall' from +ithin the dispute case
Automaticall' using program RFDM&1& for
o Automatic assignment +here uni0ue or
o Creation of an assignment proposal
Subse0uent use of program RFDM&&& to process the assignment proposal
created after e#ecution of program RFD&1&
Customer1disputed ob6ects also enable the follo+ing t'pes of documents to be
lin*ed to a dispute case
Closed ,n-oices and Deductions
<pen and Closed Credit line items
1.19.1 !rocess Settings for Customer"Disputed 3b<ects in Dispute
Cases
,n addition to the belo+ customi8ing settings4 please ensure that the follo+ing
settings ha-e been maintained to enable Customer1Disputed <b6ects functionalit'9
"he case record model also include the Customer1Disputed <b6ects structure
node along +ith the follo+ing model nodes
o ,n-oice
o CreditM<-erpa'ment
o ;illing Document
"he follo+ing functions ha-e been included in the function profile
o F,%?ADD?C=S"D,SP?<;F G Add Customer1Disputed <b6ect
o F,%?ADD?%2)?D,SP?7,%2?,"2M G Add Disputed <b6ect
o F,%?ASS,5%?C=S"<M2R G Assign to Customer
o F,%?CA7C?CD,S?AM<=%" G Calculated Customer1Disputed Amount
o F,%?R2M<(2?7,%2?,"2M G Remo-e <b6ects
"he dispute case attribute profile also includes the follo+ing attributes
o F,%?C=S"D,SP?AM" G Customer1Disputed Amount
o F,%?C=S"D,SP?C=R 1 Currenc' of Customer1Disputed Amount
"o process settings for Customer1Disputed ob6ects +ithin a dispute case4 please
follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Process ,ntegration +ith Accounts Recei-able
Accounting : Customer1Disputed <b6ects in
Dispute Cases : Process Settings for
Customer1Disputed <b6ects in Dispute Cases
Transaction Code FDM?C=S"2&
1. ,dentif' the compan' code and case t'pe
2. Chec* the JAutomaticall' Add ,n-oice to ,tem 7ist and in Document Displa'
"ransactionK chec*bo# if 'ou +ish to add the selected AR line item to the
dispute case as a customer1disputed ob6ect.
$. Chec* the JAutomaticall' Add ,n-oice to Clearing "ransactionsK chec*bo# if4
+hen 'ou are creating dispute cases from clearing transactions4 'ou +ish to
add the corresponding AR line item to the dispute case as a customer1
disputed ob6ect.
. Chec* the JAutomaticall' Add ,n-oice to Dispute Case ProcessingK chec*bo#
to enable the addition of accounting documents4 as customer1disputed
ob6ects4 from +ithin the dispute case
.. Clic* on the sa-e button to generate the transport re0uest
1.)& utomatic Document Changes from Dispute Cases
,n order to s'nchroni8e changes in dispute case attributes4 +ith the corresponding
lin*ed accounting documentDsE4 'ou need to define the target field in AR along +ith
the source fields in dispute management. <nce defined4 'ou need to complete the
dispute case attribute -alue to AR field -alue mapping along +ith the number of
da's until the AR document changes ta*e effect.
1.)&.1 Define Document Changes
"o complete customi8ing settings for automatic AR document chances4 triggered b'
a change in dispute case attributes4 please follo+ the belo+ ,M5 menu path9
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Process ,ntegration +ith Accounts Recei-able
Accounting : Automatic Document Changes
from Dispute Cases : Define Document
Changes
Transaction Code SPR<
1. ,nput the compan' code and corresponding case t'pe and hit enter to
-alidate entries
2. Aighlight the corresponding record and clic* on Selection of Fields
$. ,nput the accounts recei-able target field and corresponding source fields
from the dispute case. ,n the belo+ e#ample each time the reason code is
modified +ithin the dispute case4 the reason code on the corresponding
lin*ed accounting documentDsE +ill also be updated. See belo+ for a list of
fields that can be updated automaticall' based on changes to -arious
attributes +ithin the dispute case9
a. MA%SP G Dunning ;loc*
b. RS"5R G Reason Code for Pa'ments
c. O7SPR G Pa'ment ;loc* Ce'
d. O,%CO G 2#empted from ,nterest Calculation
e. O7SCA G Pa'ment Method
f. FD72( G Planning 7e-el
. Aighlight the corresponding record and clic* on Determination of Field (alues
.. ,dentif' the dispute case attribute to AR document field mapping and number
of da's until the corresponding AR document should be updated. ,f 'ou lea-e
the number of da's field blan*4 AR document changes +ill be immediate.
6. Clic* on sa-e to generate the transport re0uest
Correspondence
AddP.
1.)1 Define and Configure ctions
AddP
IMG Menu SAP Customi8ing ,mplementation 5uide :
Financial Suppl' Chain Management :
Dispute Management : Dispute Case
Processing : Correspondence : Define and
Configure Actions
Transaction Code SPR<
Aighlight the F,%?DM action profile
Clic* on Define Action Profile and Actions
5o to the Action Definition folder and clic* on the Displa' L 11 : Change mode
button
Clic* on the %e+ 2ntries button
Maintain the follo+ing entries for each smartform9
Action Definition
Description
Processing "ime9 ,mmediate processing
2nsure the 2#ecutable in Dialog chec*bo# is selected
2nsure the Displa' in "oolbo# chec*bo# is selected
2nsure the Partner1Dependent chec*bo# is selected
Partner Function9 PP
Determination "echnolog'9 Determination =sing Conditions that can be
"ransported
Rule "'pe9 )or*flo+ Conditions
Action Merging9 %o Action Summari8ation
,ndi-idual Dispute Case smartforms are as follo+s9
MRADMC7A,M?C<S"C<
MRADMC7A,M?D2%,A7
MRADMC7A,M?SP<R"S?A="A
MRADMC7A,M?)A7MAR"
MRADMC7A,M?"AR52"
Clic* on the Processing "'pes folder and clic* on the %e+ 2ntries button
Select 2#ternal Communication for Permitted Processing "'pes of Action
Aighlight the 2#ternal Communication entr' and clic* on the Set Processing ;utton
2nter the follo+ing information
Document "ab
Smartform %ame
Form "'pe9 SmartForm
Format9 F,%?DM?;CS
Personali8ation "'pe9 Recipient1Specific (ariable Replacement
Fa# Co-er Sheet "ab
SAP Script Standard Co-er Sheet
Archi-ing "ab
Send <nl'
Repeat these steps for each smartform listed abo-e.
Clic* on sa-e to generate the transport M +or*bench re0uests
Clic* on the green bac* arro+ button to return to the Displa' (ie+ HPFF9
Applications in Customi8ingI9 <-er-ie+ screen
Aighlight F,%?DM
Clic* on the Condition Configuration D"ransportable ConditionsE ;utton
=nder the Action Profile folder4 double clic* on SAP Dispute Management9
Correspondence DF,1ARE
Clic* on the Displa' L1: Change icon to go into change mode
Clic* on the create button and select a SmartForm
=nchec* default settings
5o to the Processing Details tab
Change the Communication Method to Print
Clic* on the Printer tab
,nput Printer
Sa-e
Repeat this process for the ,nternet Mail and Fa# Communication Methods.
Repeat this process for all smartforms.

You might also like