Config Guide FSC M Prototyp

Confidential - Internal use only
Configuration Guide for FSCM System at

Client
This Configuration Guide has been created for a specific Client Company.
The configuration described below there fore has been driven by specific
clients scope, needs and requirements.
Key Contacts for the deliverable are:

Andrew Neinhardt
Michael Feiner
Version: Created on Page
Page 1 of 99
4/9/2021
Release:
Last saved by
Atilla Sis

Page 2 of 99
4/9/2021
Release:
Last saved by
Customizing Documentation for Prototype SAP FSCM
Index
A. Configuration of Business Partner Synchronization.........................................................3

Define Business Partner Role.............................................................................................................3
Assign BP Roles to BP Role Category..............................................................................................5
Define Number Ranges........................................................................................................................6
Define Groupings and Assign Number Ranges................................................................................7
Address Determination - Define Transactions..................................................................................8
Address Determination - Define Address Types..............................................................................9
Address Determination - Assign Transaction to Address Type....................................................10
Set Geocoding - Process Geographical Data for Countries..........................................................11
Process Geographical Data for Countries and Regions................................................................12
Maintain Tax Number Categories.....................................................................................................13
Maintain Industry Systems and Industries.......................................................................................14
Define Number Ranges for Business Partner Relationship..........................................................16
Synchronization Objects....................................................................................................................18
Activate PPO Requests for Platform Objects in the Dialog...........................................................19
Address Determination - Define Transactions................................................................................20
Set BP Role Category for Direction BP to Customer.....................................................................21
Define BP Role for Direction Customer to BP.................................................................................22
Define Number Assignment for Direction BP to Customer...........................................................23
Address Determination - Define Transactions................................................................................24
Activate Assignment of Contact Persons.........................................................................................25
Assign Industries.................................................................................................................................26
Synchronization of Mass Data..........................................................................................................29
A. Collection Management......................................................................................................31
Define Company Code.......................................................................................................................31
Activate Collections Management....................................................................................................32
Activate Distribution for Company Code..........................................................................................34
Activate FI-AR Mapping.....................................................................................................................35
Define Collection Segments..............................................................................................................35
Define Collection Profile.....................................................................................................................39
Define Collection Rules......................................................................................................................41
Define Collection Strategy.................................................................................................................46
Define Derivation Priority...................................................................................................................50
Define Collection Groups...................................................................................................................51
Assign Collection Groups to Collection Segment...........................................................................54
Define Customer Contact Reason Codes.......................................................................................55
Define Resubmission Reason Codes..............................................................................................58
Create Promise to Pay.......................................................................................................................60
B. Dispute Management.......................................................................................................... 68
Activate Dispute Management..........................................................................................................68
Page 3 of 99
4/9/2021
Release:
Last saved by
Activate Assignment of Open Credits and Payments....................................................................69

Define Attribute Profile.......................................................................................................................70
Create Values for Attribute 'Priority'..................................................................................................74
Create Values for Attribute "Escalation Reason"............................................................................75
Define Status Profile...........................................................................................................................77
Define Number Range........................................................................................................................79
Define Case Types.............................................................................................................................81
Create Values for Attribute "Category"............................................................................................84
Create Values for Attribute Reason..................................................................................................85
Create Profile for Case Search.........................................................................................................88
Define Root Reason Code.................................................................................................................90

Page 4 of 99
4/9/2021
Release:
Last saved by
1. Configuration Information
A. Configuration of Business Partner Synchronization
Define Business Partner Role

Application: SAP ERP
Transaction Name: Define Business Partner Roles
Transaction Code: SPRO
Menu Path: Cross-Application Components > SAP Business Partner >
Business Partner > Basic Settings > Business Partner Roles >
Define BP Roles
Define BP Roles:
Comments/Notes:
The following business partner roles are delivered by SAP and are important for master data
synchronization:
 000000 - General Business Partner
Page 5 of 99
4/9/2021
Release:
Last saved by
 FLCU00 CVI: FI Customer - Customer/Vendor Integration: FI Customer
 UDM000 BP Collections Management Business Partner Collections Management
In the next step BP Roles will be assigned to a role category.

Page 6 of 99
4/9/2021
Release:
Last saved by
Assign BP Roles to BP Role Category

Transaction Name: Assign BP Roles to BP Role Category
Business Partner > Basic Settings > Business Partner Roles >
Assign BP Roles to BP Role Category
Assign BP Roles to BP Role Category:
Comments/Notes:
First make the following settings for the business partner role: Assign BP-Role “UDM000” to BP-
Role category “UDM000” and BP-Role “FLCU00” to BP-Role category “FLCU00”.

Page 7 of 99
4/9/2021
Release:
Last saved by
Define Number Ranges

Transaction Name: Define Number Ranges
Business Partner > Basic Settings > Number Ranges and
Groupings > Define Number Ranges
Define Number Ranges:
Comments/Notes:
For this prototype we defined two kinds of number ranges for business partners. One with
internal number and one with external number.

Page 8 of 99
4/9/2021
Release:
Last saved by
Define Groupings and Assign Number Ranges

Transaction Name: Define Groupings and Assign Number Ranges
Business Partner > Basic Settings > Number Ranges and
Groupings > Define Groupings and Assign Number Ranges
Define Groupings and Assign Number Ranges:
Comments/Notes:
In this IMG-activity you define groupings for business partners and assign to the groupings the
defined range numbers in the previous step. The standard groupings “0001” and “0002”. are
delivered by SAP.

Page 9 of 99
4/9/2021
Release:
Last saved by
Address Determination - Define Transactions

Transaction Name: Address Determination - Define Transactions
Business Partner > Basic Settings > Address Determination >
Define Transactions
Address Determination - Define Transactions:
Comments/Notes:
Through address determination the system is able to be able to determine the correct address
for a particular business transaction. The business transaction “XXDFLT” is standard value of
SAP.

Page 10 of 99
4/9/2021
Release:
Last saved by
Address Determination - Define Address Types

Transaction Name: Address Determination - Define Address Types
Define Address Types
Address Determination - Define Address Types:
Comments/Notes:
In this IMG-activity, you define address types for certain business transactions. The address
type “XXDEFAULT” is supplied by SAP.

Page 11 of 99
4/9/2021
Release:
Last saved by

Page 12 of 99
4/9/2021
Release:
Last saved by
Address Determination - Assign Transaction to Address Type

Transaction Name: Address Determination - Assign Transaction to Address Type
Assign Transaction to Address Type
Address Determination - Assign Transaction to Address Type:
Comments/Notes:
In this IMG-activity you assign predefined transactions to address types that you have created,
for the purpose of address determination. In the case of business partners with multiple
addresses, the system must be able to determine the correct address for different transactions
(such as send order, receive goods).

Page 13 of 99
4/9/2021
Release:
Last saved by
Set Geocoding - Process Geographical Data for Countries

Transaction Name: Set Geocoding - Process Geographical Data for Countries
Menu Path: SAP NetWeaver > General Settings > Set Geocoding > Process
Geographical Data for Countries
Set Geocoding - Process Geographical Data for Countries:
Comments/Notes:
After the Address determination settings at Client System we received during the masta data
synchronization an error message regarding geocoding settings “Geokodierer SAP0: Die
Angabe des Landes ist unvollständig (Custom.)”. This was the reason why we maintained the
coordinates for each country and region.

Page 14 of 99
4/9/2021
Release:
Last saved by
Process Geographical Data for Countries and Regions

Transaction Name: Set Geocoding - Process Geographical Data for Countries and
Regions
Menu Path: SAP NetWeaver > General Settings > Set Geocoding > Process
Geographical Data for Countries and Regions
Process Geographical Data for Countries and Regions:
Comments/Notes:
After the Address determination settings at Client System we received during the masta data
synchronization an error message regarding geocoding settings “Geokodierer SAP0: Die
Angabe des Landes ist unvollständig (Custom.)”. This was the reason why we maintained the
coordinates for each country and region.

Page 15 of 99
4/9/2021
Release:
Last saved by
Maintain Tax Number Categories

Transaction Name: Maintain Tax Number Categories
Business Partner > Basic Settings > Tax Numbers > Maintain Tax
Number Categories
Maintain Tax Number Categories:
Comments/Notes:
In this IMG activity, you specify which sorts of tax numbers you can enter in business partner
master data, on the Identification tab. The different sorts of tax numbers are known as tax
number categories.

Page 16 of 99
4/9/2021
Release:
Last saved by
Maintain Industry Systems and Industries

Transaction Name: Maintain Industry Systems and Industries
Business Partner > Organizations > Maintain Industry Systems and
Industries
Maintain Industry Systems and Industries:
Comments/Notes:
In this activity you define industry systems and industries. You can create different industry
systems, to which you can assign several industries in each case. You can assign several
industry systems to one business partner.

Page 17 of 99
4/9/2021
Release:
Last saved by

Transaction Name: Maintain Industry Systems and Industries
Business Partner > Organizations > Maintain Industry Systems and
Industries
Maintain Industry Systems and Industries:
Comments/Notes:
In this activity you define industry systems and industries. You can create different industry
systems, to which you can assign several industries in each case. You can assign several
industry systems to one business partner.

Page 18 of 99
4/9/2021
Release:
Last saved by
Define Number Ranges for Business Partner Relationship

Transaction Name: Define Number Ranges for Business Partner Relationship
Business Partner Relationships > Basic Settings > Define Number
Ranges
Define Number Ranges for Business Partner Relationship:
Comments/Notes:
For internal administration of BP relationships and BP role definitions an internal number is

required from the number range interval "01".

Page 19 of 99
4/9/2021
Release:
Last saved by
Synchronization Objects
Transaction Name: Synchronization Objects
Menu Path: Cross-Application Components > Master Data Synchronization >
Synchronization Control > Synchronization Control >
Synchronization Objects
Synchronization Objects:
Comments/Notes:
In this IMG activity you can display synchronization objects provided by for the master data
synchronization and, if necessary, create your own synchronization objects. SAP recommends
using those synchronization objects that are provided as standard. Creating your own
synchronization objects in the customer namespace would require a lot of additional
programming.

Page 20 of 99
4/9/2021
Release:
Last saved by
Activate PPO Requests for Platform Objects in the Dialog

Transaction Name: Activate PPO Requests for Platform Objects in the Dialog
Synchronization Control > Synchronization Control > Activate PPO
Requests for Platform Objects in the Dialog
Activate PPO Requests for Platform Objects in the Dialog:
Comments/Notes:
In this IMG activity you decide for each platform object whether a post-processing order should
be written in the event of an error.

Page 21 of 99
4/9/2021
Release:
Last saved by

Synchronization Control > Synchronization Control > Activate
Synchronization Options
Activate Synchronization Options:
Comments/Notes:
In this IMG activity you activate the SAP synchronization options.

Page 22 of 99
4/9/2021
Release:
Last saved by
Set BP Role Category for Direction BP to Customer

Transaction Name: Set BP Role Category for Direction BP to Customer
Customer/Vendor Integration > Business Partner Settings >
Settings for Customer Integration > Set BP Role Category for
Direction BP to Customer
Set BP Role Category for Direction BP to Customer:
Comments/Notes:
In this IMG activity you can choose BP role categories for customer integration in the direction
from the business partner to the customer. You determine how the system creates a
corresponding customer in Financial Accounting when you process a business partner.

Page 23 of 99
4/9/2021
Release:
Last saved by
Define BP Role for Direction Customer to BP

Transaction Name: Define BP Role for Direction Customer to BP
Settings for Customer Integration > Define BP Role for Direction
Customer to BP
Define BP Role for Direction Customer to BP:
Comments/Notes:
In this IMG activity you assign the BP roles to the account group for the customer master record
in which the business partner is to be created when processing the customer.

Page 24 of 99
4/9/2021
Release:
Last saved by
Define Number Assignment for Direction BP to Customer

Transaction Name: Define Number Assignment for Direction BP to Customer
Settings for Customer Integration > Field Assignment for Customer
Integration > Assign Keys > Define Number Assignment for
Define Number Assignment for Direction BP to Customer:
Comments/Notes:
In this IMG activity you assign the groupings of the the business partner to the account groups
for the customer master records. With this assignment you choose whether the customer master
record is to be created with an account group with internal or external number assignment or
with identical numbers.

Page 25 of 99
4/9/2021
Release:
Last saved by

Integration > Assign Keys > Define Number Assignment for
Address Determination - Define Transactions:
Comments/Notes:
In this IMG activity you assign the groupings of the the business partner to the account groups
for the customer master records. With this assignment you choose whether the customer master
record is to be created with an account group with internal or external number assignment or
with identical numbers.

Page 26 of 99
4/9/2021
Release:
Last saved by
Activate Assignment of Contact Persons

Transaction Name: Activate Assignment of Contact Persons
Integration > Assign Attributes > Contact Person > Activate
Assignment of Contact Persons
Activate Assignment of Contact Persons
Comments/Notes:
In this IMG activity you can activate the assignment of contact persons in order to synchronize
the attributes for the contact person.

Page 27 of 99
4/9/2021
Release:
Last saved by
Assign Industries
Transaction Name: Assign Industries
Integration > Assign Attributes > Assign Industries
Assign Industries:
Comments/Notes:
In this IMG activity you assign industries between the business partner and the customer master
record

Page 28 of 99
4/9/2021
Release:
Last saved by

Define Outgoing Industry Mapping:
Comments/Notes:
record

Page 29 of 99
4/9/2021
Release:
Last saved by

Page 30 of 99
4/9/2021
Release:
Last saved by

Define Incoming Industry Mapping:
Comments/Notes:
record

Page 31 of 99
4/9/2021
Release:
Last saved by
Synchronization of Mass Data

Transaction Name: Synchronization of Mass Data
Synchronization of Mass Data:
Comments/Notes:
With this IMG activity you are able to start the user interface for master data synchronization.
Choose the source and target object for the synchronization process (for example source =
customer and target = business partner. In the processing tab select a field name (customer)
and set the customer value for lower limit and upper limit. Afterwards start the master data
synchronization.

Page 32 of 99
4/9/2021
Release:
Last saved by

Transaction Name: Synchronization of Mass Data
Synchronization of Mass Data:
Comments/Notes:
In the Monitor tab you see the process status of synchronizations. In queue monitor you
analyze the errors.

Page 33 of 99
4/9/2021
Release:
Last saved by
A. Collection Management
Define Company Code

Application-Release: SAP R 45 ERP 6.0
Transaction Name: Define Company Codes for SAP Collections MGMT
Menu Path: Financial Supply Chain Management > Collections Management >
Basic Settings for Collection Management > Basic Data > Define
Company Codes for SAP Collections Management
Configuration Change (What?) or Screen Print:

Page 34 of 99
4/9/2021
Release:
Last saved by
Change Position/Rationale (Why?):
Step 1 -> Click the “New Entries” Button
Step 2 -> Enter Company Code “7503” in the company code “CoCd” field
Step 3 -> Click the “Save” Button
Comments/Notes:
This Company Code is defined within FSCM in order to identify the FI-AR items that the
collection management process would apply to. This process does not preclude adding
additional company codes in the future
Activate Collections Management

Transaction Name: Activate SAP Collections Management

Page 35 of 99
4/9/2021
Release:
Last saved by
Integration with Accounts Receivables Accounting > Activate SAP

Collections Management
Configuration Change/Screen Print:

Configuration Steps:
1. Go to Menu Path: (IMG) Financial Supply Chain Management > Collections
Management > Integration with Accounts Receivables Accounting > Activate SAP
Collections Management.
Results: Change View page for activating Collection Management will display.
2. Select Change/Display Button
3. Enter Application name to activate under the column.
4. Under the Activate Column select the radio button to activate CM .
Results: Text will display confirming that the application to be activated is SAP Collection
Management.

Page 36 of 99
4/9/2021
Release:
Last saved by
5. Click the Save button to activate Collections Management.
Results: Collection Management is now Activated.
Comments/Notes:
SAP Collection Management has to be activated in order to ensure that the Collections
Management Module Synchs up with the FI module and in order to Ensure that the “UDM_BP”
profile for business partners can be activated and utilized.
Activate Distribution for Company Code

Transaction Name: Activate SAP Collections Management
Integration with Accounts Receivables Accounting > Activate
Distribution per company code

Page 37 of 99
4/9/2021
Release:
Last saved by
Step 1 -> Enter 7503 under the company code field
Step 2 -> Click Save once complete
Client HC will use Company Code 7503. Company code must be defined in FSCM in order for
the applicable company code (7503) FI-AR Open Receivables to be integrated. This process
would also enable FSCM collection strategy apply to the applicable AR open items
Comments/Notes:
If the Direct Pay indicator is set, in SAP Collections Management, data is only considered from
customers that are direct payers. Customers that, for example, always participate in automatic
payment transactions based on an automatic debit authorization are not considered.
Activate FI-AR Mapping

Transaction Name: Activate SAP FI-AR
Integration with Accounts Receivables Accounting > Mapping of
Master Data > Activate Standard Implementation for Mapping FI-
AR
Client HC will utilize the integration between FI-AR and Collections Management. In order to
integrate the transaction activity of all customers between FI-AR and FSCM
Comments/Notes:
Activating the standard Implementation ensures that FSCM and FI-AR are in synch. This also

Page 38 of 99
4/9/2021
Release:
Last saved by
ensures FSCM in linked to SAP R/3 rather than a Third Party Legacy Application.
Define Collection Segments

Transaction Name: Define Collections Segment
Menu Path: Financial Supply Chain Management > Collections
Management > Basic Settings for Collection Management
>Organizational Structure >Define Collection Segments

Page 39 of 99
4/9/2021
Release:
Last saved by

Page 40 of 99
4/9/2021
Release:
Last saved by
Step 1 -> Enter “Z7503_SEG” in the Collections Segment field
Step 2 -> Enter “7503 Collections Segment“ in the Name of Segment Field
Step 3 -> Click the Released Check off Box
Step 4 -> Click “Save”
Step 5 -> Select the 7503 Collections Segment
Step 6 -> Double Click the “Assign Company Code Folder “
Step 8 -> Enter Company Code “7503“ in the CoCd field
Step 9 -> Click the “SAVE” button Once Complete
Collection segments group company codes of a company from the view of SAP Collections
Page 41 of 99
4/9/2021
Release:
Last saved by
Management so that transaction data (open items, dispute cases, and promises to pay) of a
business partner from these company codes can be considered together.
Comments/Notes:
This process does not preclude Client HC from creating additional Collection Segments for
specific company codes or assigning more company codes to an existing collections segment.
You can only use collection segments in SAP Collections Management if you have released
them. Once you have released them, the company codes that you have assigned to the
segment can no longer be removed or deleted.
This restriction is necessary so that after reorganizations (for example, profile changes or
changes to collection-specific data in the business partner master record), the system can
assign customer contacts and resubmissions from old segments to the new segments.
Define Collection Profile

Transaction Name: Define Collections Profile
Basic Settings for Collection Management >Organizational
Structure >Define Collection Profile

Page 42 of 99
4/9/2021
Release:
Last saved by

Page 43 of 99
4/9/2021
Release:
Last saved by
Step 1 -> Click the New Entries Button
Step 2 -> Enter “Z7503_Prof” in the Collection Profile Field
Step 3 -> Enter “7503 Collection Profile” in the Name of Collection Profile Field
Step 4 -> Click the “ SAVE” button
Step 5 -> Select The Client HC Collection Profile
Step 6 -> Double Click the “Assign Collection Segments To Profile” Folder
Step 8 -> Click the “Assign Collection Segments To Profile” Folder
Step 9 -> Enter the collections segment “Z7503_COL” in the segment field
Step 10 -> Click the “SAVE” button
Comments/Notes:
Collection profiles are a grouping of collection segments and thus split the company codes that
participate in SAP Collections Management. You can determine how the company codes are
split in a profile and which company codes are not included in a profile.
For collecting receivables using SAP Collections Management, a collection profile is assigned to
every customer.
This process does not preclude Client HC from creating additional Collection Profiles for specific
Collections Segments
Define Collection Rules

Transaction Name: Define Collection Rules
Management > Basic Settings for Collection Management >
Collection Strategies >>Define Collection Rules
Configuration Change (What) or Screen Print:

Page 44 of 99
4/9/2021
Release:
Last saved by

Page 45 of 99
4/9/2021
Release:
Last saved by

Page 46 of 99
4/9/2021
Release:
Last saved by
Change Position/Rationale (Why):
Step 2 -> Enter Collection Rule “Z7503RULE1” in the RULE field
Step 3-> Enter Collection Rule Name “7503 Collection Rule” in the Collection Rule Name Field
Step 4 -> Click Save
Step 5 -> Highlight “Z7503Rule1” collection rule by clicking the Select button
Step 6 -> Double Click The “Assignment Of Basic Rules To Rules” Folder
Step 7 - Click the New Entries Button
Step 8 - Click the Matchcode button on the Basic Rules field to select the applicable Basic Rules
Step 9 -> Double Click Selected Basic Rule
Per Client HC Prototype Requirements – Basic Rules below were selected
PLEASE REPEAT THIS STEPS FOR ALL RULES
Rule Description (engl.) Description (dt.)

Basic Rule - BR00000002 - Total of Betrag aller Posten überfälligen seit
Z7503RULE1 All Items Overdue Since n Days n Tagen
Step 10 -> Click the Save Button Once Complete
Client HC will use the collection rules to be used later for the definition of collection strategies in
order to group the various basic collection rules that would be assigned to a Collection Strategy.
These rules would be used to identify and assign the collector specialist work list tasks and
outstanding receivables. When work lists are created, the collection rules lead to a prioritization of
the business partners. The system checks the conditions of all basic rules that make up the

Page 47 of 99
4/9/2021
Release:
Last saved by
individual collection rule.
Comments/Notes:
Rules could also be utilized as Perquisites or Conditions for other Basic rules. This is not being
utilized; in the future Client HC may add collection rule or implement additional Collection rules.
Define Collection Strategy

Transaction Name: Define Collection Strategy
Management > Basic Settings for Collection Management
>Collection Strategies > Process Strategies

Page 48 of 99
4/9/2021
Release:
Last saved by

Page 49 of 99
4/9/2021
Release:
Last saved by
Step 1 -> Click the Create Strategy Button
Step 2 -> Enter “Z7503_STGY” in the strategy field

Page 50 of 99
4/9/2021
Release:
Last saved by
Step 3 -> Enter “7503 Customer Collection Strategy” in the Strategy description field
Step 4-> Enter “EUR” in the currency field
Step 5 -> Click the create button
Step 6-> Click the Macthcode under the Rule Tab in order to select the appropriate
Collection Rule “Z7501RULE1”
PLEASE REPEAT THESE STEPS FOR CLIENT HC’ STRATEGY
Step 7 -> Enter the Valuation Points for each Collection Rule
The Collection rules valuation points determine the level of priority for each item in a Collectors
Specialists Worklist
The Total Valuation points should not exceed “100 pts” as defined in the derivation priority
configuration
Step 8 -> Click SAVE button Once Complete
Step 9 -> The Collection would have to be modified in order to adjust the basic collection rules
to Client HC’s Collection Strategy
Step 10 -> Click the “Perquisites and Conditions Button”
Step 11 -> Modify the Basic Rules To Meet the Current Collection Strategy
Step 12 -> Double click the Item Total (EUR) field and select the “>” sign
Step 13 -> Click the Execute Button
Step 14 -> Click Save Once Complete
Collection Strategies are used for a variety of reasons such as

 Prioritize business partners on the work list
 Define the currency in which the amounts are to be displayed in the work list
 Determine the time intervals with which the business partner payables are to be
sorted
 Determine the influence of the terms of payment on Collections Management
(proactive receivables processing)
All specialists in a collection group collect open receivables from business partners with the
same strategy.

Page 51 of 99
4/9/2021
Release:
Last saved by
Comments/Notes:
Define Derivation Priority

Transaction Name: Define Derivation of Priorities
Management - > Collection Strategies >Priorities -> Define
Derivation of Priorities

This Configuration task is Delivered standard by SAP but it provides users the ability to increase
or decrease the various valuation percentage points ranking. The total Percentage Points within
this configuration activity are directly related to the Total valuation points in the Collection
Page 52 of 99
4/9/2021
Release:
Last saved by
Strategy Activity
Comments/Notes:
Define Collection Groups

Transaction Name: Create Collections Groups
Management - > Organizational Structure >Define Collection
Groups

Page 53 of 99
4/9/2021
Release:
Last saved by
Step 2 -> Enter “Z7503_HA” in the Group Field
Step 3 -> Enter “7503 Group Region Hanse” in the Group Name Field
Step 4-> Enter “Z7501_STGY” in the Strategy Field
*This Step should be repeated for all Collections Groups
Step 5 -> Click the “Save” Button Once Complete
Within this configuration we would define the groups of collection specialists that are to contact
customers in SAP Collections Management.

Page 54 of 99
4/9/2021
Release:
Last saved by
You assign collection specialists to each group using their user names. Each collection
specialist can also enter a temporary substitute (for example, for vacation or sickness). When
the specialist is absent, the system assigns the worklist items to the substitute.
All specialists in a collection group collect open receivables from business partners with the
Group Group Name Processor
Z7503_HA 7503 Group Region Hanse T.b.d.
Z7503_MI 7503 Group Region Mitte T.b.d.
Z7503_NB 7503 Group Region Nordbayern Z002KXUT (Testuser)
Z7503_NR 7503 Group Region Nordrhein T.b.d.
Z7503_ON 7503 Group Region Ost-Nord T.b.d.
Z7503_OS 7503 Group Region Ost-Süd T.b.d.
Z7503_RMF 7503 Group Region Rhein-Main T.b.d.

Frankfurt
Z7503_RMM 7503 Group Region Rhein-Main T.b.d.

Mannheim
Z7503_RU 7503 Group Region Ruhr T.b.d.
Z7503_SB 7503 Group Region Südbayern T.b.d.
Z7503_SW 7503 Group Region Südwest T.b.d.
Z7503_DD 7503 Group Dummy T.b.d.
same strategy. You therefore assign a collection strategy to each group.
Comments/Notes:
This configuration activity is required in order to define which contact groups are to contact
business partners in the respective collection segments. You have to assign the respective
collection specialists to the collection groups.
The allocation of the Processor to the collection group is not in scope of the prototype phase. A
test user is assigned to one collection group for testing reasons.

Page 55 of 99
4/9/2021
Release:
Last saved by
Assign Collection Groups to Collection Segment

Transaction Name: Assign Collection Groups to Collection Segment
Menu Path: Financial Supply Chain Management > Collections Management -
> Organizational Structure >Assign Collection Groups to Collection
Segment
Step 1 -> Click the Select All Button
Step 2 -> Double Click the “Assign Collections Group to Segment” Folder
Step 3 -> Click the “ New Entries” Button
Step 4 -> Enter “ Z7503_HA” in the Group Field
 Please Repeat Process for

Page 56 of 99
4/9/2021
Release:
Last saved by
Step 9 -> Click the “Default” Radio Button For Group Z7503_DD
Group Group Name
Z7503_HA 7503 Group Region Hanse
Z7503_MI 7503 Group Region Mitte
Z7503_NB 7503 Group Region Nordbayern
Z7503_NR 7503 Group Region Nordrhein
Z7503_ON 7503 Group Region Ost-Nord
Z7503_OS 7503 Group Region Ost-Süd
Z7503_RMF 7503 Group Region Rhein-Main Frankfurt
Z7503_RMM 7503 Group Region Rhein-Main Mannheim
Z7503_RU 7503 Group Region Ruhr
Z7503_SB 7503 Group Region Südbayern
Z7503_SW 7503 Group Region Südwest
Z7503_DD 7503 Group Dummy
Step 10 -> Click Save button once complete
This configuration activity is required in order to define which contact groups are to contact
business partners in the respective collection segments.
You must define one of the groups as a default group - ref (7503 Dummy Group). The system
proposes this per related segment when you enter a profile in the business partner master
record. This ensures that in each segment, a group of collection specialists is responsible for the
customer. You have to assign the Business partner to the correct collection group.
Comments/Notes:

Page 57 of 99
4/9/2021
Release:
Last saved by
Define Result of Customer Contact

Transaction Name: Define Result of Customer Contact
Management – Basic Settings for Collection Management
>Customer Contacts -> Define Result of Customer Contact

Page 58 of 99
4/9/2021
Release:
Last saved by

Within this configuration activity we would define the various customer contact reason codes
and their status “Remove” OR “Reached” in reference to activities on the collectors Worklist.
In order to Create a New Reason Code
Step 1 - Click the New Entries Button -
Step 2 – Enter The Customer Contact Reason code “ZDM” in the result field
Step 3 – Enter The Conversion Reason Description “Customer was reached Dispute
Crated” in the Description Field
Step 4 – Click the “Reached” Check Off Box.
Step 5 – Click Save Once THE PROCESS is Complete
This process was repeated for all Client HC Customer Contact Reason Codes
Result Description Remove Reached
ZDM Customer was reached Dispute Crated x
Page 59 of 99
4/9/2021
Release:
Last saved by
ZDU In Dispute-Underdelivery x
ZFP Flight Pending X
ZIL Call from First Letter X
ZIP Customer Called – Disputes Payment Amount X
ZOC Third Party Correspondence X
ZOE External Customer Email X
ZPP Customer Promised to Pay X
ZRP Contact in Restructure Process X
ZOT Call and talked to Customer X
ZOM Internal Email
ZON Call and No Connection
ZOO Other Miscellaneous
ZOV Call and left Voicemail
Comments/Notes:
If the “Removed” button is checked off The Worklist item is taken off the collectors Worklist after
the reason code is selected.
If the Reached Check Off is selected the Customer is noted as reached but the item is taken off
the collectors Worklist
For the prototype it was defined, that in the Worklist items must not be removed from the
Worklist, after the customer is contacted.
Define Resubmission Reason Codes

Transaction Name: Define Resubmission Reason
Menu Path: Financial Supply Chain Management > Collections Management –
Basic Settings for Collection Management >Customer Contacts ->
Define Resubmission Reason

Page 60 of 99
4/9/2021
Release:
Last saved by

Within this configuration activity we would define the various customer Resubmission Reason
codes in reference to activities on the collector’s Worklist.
Step 1 - Click the New Entries Button -
Step 2 – Enter The Customer Contact Reason code “CNR” in the result field
Step 3 – Enter The Resubmission Reason Description “Customer not reached” in the
Description Field
Step 4 – Click Save Once THE PROCESS is Complete
This process was repeated for all S Customer Contact Reason Codes
Reason Resubmission Reason
CNR Customer not reached
CRC Customer asks for recall

Page 61 of 99
4/9/2021
Release:
Last saved by
Comments/Notes:
Create Promise to Pay

Transaction Name: Create Status Profile
> Basic Settings for Collections Management > Promise to Pay >
Create Status Profile
Step 1: Click New

Step 2: Stat Prof  Z7503PAY
Step 3: Description  7503 Promise to Pay
Step 4: Select row
Step 5: Status Values  Click
Step 6: Insert Status  10
Step 7: Insert Status Description  Active
Step 8: Select System Status  002
Step 9: High Status  10

Page 62 of 99
4/9/2021
Release:
Last saved by
PLEASE REPEAT THIS STEPS FOR STATUS
Status Status System System Low High Auto Event

Description Status Status Desc. Status Status for Case
10 Active 002 In Process 10
20 Receipted 008 Confirmed 10 20
30 Devaluated 009 Voided/Delet 10 30 [click]
ed/Canceled

Page 63 of 99
4/9/2021
Release:
Last saved by
Comments/Notes:

Transaction Name: Define Number Range Interval for Case
Define Number Range Interval for Case

Page 64 of 99
4/9/2021
Release:
Last saved by
Step 1: Change intervals
Step 2: Insert Interval

Step 3: Insert No  2
Step 4: Insert From number  1
Step 5: Insert To number  999999999999
Step 6: Save
Comments/Notes:

Transaction Name: Define Case Types
Page 65 of 99
4/9/2021
Release:
Last saved by
Define Case Types

Page 66 of 99
4/9/2021
Release:
Last saved by
Step 1: Click New Entries

Step 2: Insert Case Type  ZCOL
Step 3: Insert Case Type Name  Collection Management
Step 4: Insert RMS ID  UDM_COLLECTIONS
Step 5: Insert Element Type ID (Case)  UDM_SPS_P2P
Step 6: Insert Element Type ID (Notes)  UDM_SPS_P2P_NOTES
Step 7: Insert Attrib.Profile  Collection Management Promise to Pay
Step 8: Insert Funct. Profile  Collection Management Promise to Pay
Step 9: Insert Status Profile  7503 Promise to Pay
Step 10: Insert Text Profile  Collection Management Promise to Pay
Step 11: Insert Process  Collection Management Promise to Pay
Step 12: Save
Comments/Notes:

Page 67 of 99
4/9/2021
Release:
Last saved by

Transaction Name: Define Automatic Status Changes
Process integration > Define Automatic Status Changes
Step 1: click New Entries

Step 3: Insert Case Type Name  Collection Management
Step 4: Insert Auto. Confirmation  20
Step 5: Save
Comments/Notes:

Page 68 of 99
4/9/2021
Release:
Last saved by

Transaction Name: Define Text ID for Notes
Process integration > Define Text ID for Notes
Step 1: click New Entries

Step 3: Insert Case Create  0002
Step 5: Save
Comments/Notes:

Page 69 of 99
4/9/2021
Release:
Last saved by
B. Dispute Management
Activate Dispute Management

Transaction Name: Activate Dispute Management
Menu Path: Financial Supply Chain Management > Dispute Management
>Process Integration with Accounts Receivable Accounting
-> Activate Process Integration for Dispute Management

Page 70 of 99
4/9/2021
Release:
Last saved by

This configuration activity you activate the connection of SAP Dispute Management to your
Accounts Receivable R3 system
Step 1-> Click the check off button
Comments/Notes:
This Button Can only be activated once
Activate Assignment of Open Credits and Payments

Transaction Name: Activate Assignment of Open Credits and Payments
>Process Integration with Accounts Receivable Accounting
-> Assignment of Open Credits and Payments > Activate
Assignment of Open Credits and Payments

Page 71 of 99
4/9/2021
Release:
Last saved by

This configuration activity you activate the connection of Payments from your Accounts
Receivable R3 system
Step 1-> Click the check off button
Comments/Notes:
This Button Can only be activated once
Define Attribute Profile

Transaction Name: Create Dispute Management Attribute Profile
>Dispute Case Processing -> Attribute Profile-> Create Attribute
Profile
Page 72 of 99
4/9/2021
Release:
Last saved by

Page 73 of 99
4/9/2021
Release:
Last saved by

Page 74 of 99
4/9/2021
Release:
Last saved by

Within this configuration activity we would define which attributes are used. We would also
define the display and maintenance properties of each attribute.
Step 1 -> Highlight the Standard SAP “FIN_DISP” Profile
Step 2 -> Click the Copy Button
Step 3 -> Change The Attribute Profile To “Z7503DIS”
Step 4 -> Change The Description To “7503 Dispute Management”
Step 5 -> Click the Copy (Enter) Button
Step 6 -> Click the Copy All Button

Step 7 -> Highlight the Profile “Z7503DIS”
Step 8 -> Double Click the Attribute Group Folder

Page 75 of 99
4/9/2021
Release:
Last saved by
Step 10 -> Double Click the Attribute Group Folder
Step 11 -> Enter 1 In the Group Column
Step 12 -> Enter “7503 Dispute Management System” in the Title of Attribute Group Field
Step 13 -> Click the Save Button Once Complete
Step 14 -> Highlight the Z7503DIS attribute
Step 15 -> Double Click the Assign Attribute Folder
Step 16 -> Assign additional attributes
Step 17 -> Click the New Entries Button -
Step 18 -> Choose attribute “UDM_BELNR”
Step 19 -> Add Group and Position -> Group = 1, Row = 2, Column = 21
Attribute Required Invisible Dropdown Checkbox Not Modif. Log

Modificable New
UDM_BELNR t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
UDM_BUZEI t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
UDM_DZLSPR t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
UDM_GSBER t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
UDM_MANSP t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
UDM_VKBUR t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
UDM_XBLNR t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
UDM_ZUONR t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d. t.b.d.
Comments/Notes:
Within the prototype the added fields do not contain any functionality or data. The fields were
added to the table “SCMG_T_CASE_ATTR in order to visualize the relevant fields of a dispute
case.
This Process enables Users to select which Fields should be

Page 76 of 99
4/9/2021
Release:
Last saved by
- Required
- Invisible
- Dropdown
- Checkbox
- Not Modifiable
- Modifiable New
- Log – Record of All Changes Made
Create Values for Attribute 'Priority'

Transaction Name: Create Dispute Management Status Profile
>Dispute Case Processing > Attribute Profile > Attribute Values >
Create Values for Attribute 'Priority'

Page 77 of 99
4/9/2021
Release:
Last saved by
Step 2: Insert Priority  1
Step 3: Insert Text  Very high
Priority Description (engl.) Description (dt.)

1 Very high Sehr hoch
2 High Hoch
3 Low Niedrig
4 Very low Sehr niedrig
Comments/Notes:
Create Values for Attribute "Escalation Reason"

Transaction Name: Create Dispute Management Status Profile
>Dispute Case Processing > Attribute Profile > Attribute Values >
Create Values for Attribute "Escalation Reason"

Page 78 of 99
4/9/2021
Release:
Last saved by
Step 2: Insert Priority  1
Step 3: Insert Text  Customer Call
Priority Description (engl.) Description (dt.)

1 Customer call Kundenanruf
2 Timeout Zeitüberschreitung
3 Time Limit Exceeded Zeitlimit überschritten
Comments/Notes:
Define Status Profile

Page 79 of 99
4/9/2021
Release:
Last saved by
Transaction Name: Create Status Profile

>Dispute Case Processing -> Status Management-> Create Status
Profile

Page 80 of 99
4/9/2021
Release:
Last saved by

A status profile contains multiple status values that can be assigned to a case. Status is an
attribute that the user can set for each case. This Configuration activity enables users define the
various Case Statuses
Step 1 -> Highlight Z7503DIS Profile
Step 2 -> Click the “Copy Button”
Step 3 -> Enter “Z7503DIS” in the Stat.Prof Field

Step 4-> Enter “7503 Dispute Management” in the description field
Step 5-> Click the Copy(Enter) button Once Complete

Status Description (engl.) Description (dt.)
20 To be collected Einzufordern
40 Received Empfangen
50 Devaluated Entwertet

Page 81 of 99
4/9/2021
Release:
Last saved by
Step 6 -> Double Click the Status Values Folder – In order to validate the various case statuses
Step 7-> Validate the Status and their Order
Comments/Notes:
Define Number Range

Transaction Name: Define Number Range
>Dispute Case Processing -> Define Number Range Interval
for case

Page 82 of 99
4/9/2021
Release:
Last saved by

This configuration activity provides users the ability to create the number range for Dispute
Cases and Promise To Pay cases
Step 1 -> Click the Change Intervals button
Step 2 -> Click the Interval button
Step 3-> Enter the Interval No.
Step 4 -> Select the Number Range from the Drop Down Menu
Step 5 -> Click Save Once Complete

Page 83 of 99
4/9/2021
Release:
Last saved by
Comments/Notes:
7503 would be utilizing the same number range for both Dispute cases and Promise to
Pay cases. Within FSCM separate number ranges can be created for both Promise to Pay
and Disputes
Define Case Types

Transaction Name: Define Case Types
>Dispute Case Processing -> Case Types -> Define Case Types

Page 84 of 99
4/9/2021
Release:
Last saved by

Page 85 of 99
4/9/2021
Release:
Last saved by

Step 1- > Click the “New Entries” Button
Step 2-> Enter the Case Type Name -“ ZDIS”
Step 3 -> Enter the Case Type Description – “7503 Dispute Management System”
Step 4 -> Select Case row
Step 5: Enter Case Type -> ZDIS
Step 6: Enter Name -> 7503 Dispute Management System
Step 7: Enter the RMS ID -> UDM_DISPUTE
Step 8: Enter Case Rec. Model -> Select Dispute Management
Step 9: Enter the Element Type ID (Case) –> UDM_SPS_CASE
Step 10: Enter the Element Type ID (Rec) -> UDM_SPS_CASE_Record
Step 11- > Enter the Element Type ID: Notes – UDM_SPS_CASE_NOTES
Step 12-> Enter the Attribute Profile : “Z7501_DIS”
Step 13 -> Enter the Function Profile “Z7501_DIS”
Step 14 -> Enter the Status Profile “Z7501_DIS”
Step 15 -> Enter the Text Profile “Z7501_DIS”
Step 16 -> Enter the Terminology “SOA_IS”
Step 17 -> Enter the Action Profile “FIN_DM”
Step 18 -> Enter Process “F_DM”
Step 19 -> Enter The Int. No. Range “2”
(This Number can change depending on the number range selected for a case type)
Step 20 -> Click the “SAVE” button once complete
This configuration activity provides users the ability to define/configure the various case types
that would be utilized.
Comments/Notes:
This Configuration activity may change if a new Case record model is utilized.

Page 86 of 99
4/9/2021
Release:
Last saved by
These standard configuration objects are required in order to complete the configuration process
for dispute management RMS Model
Create Values for Attribute "Category"

Transaction Name: Create Values for Attribute “Category”
Menu Path: Financial Supply Chain Management > Dispute Management >Dispute
Case Processing -> Case Types -> Create Values for Attribute “Category”

Step 1 -> Click on the “New Entries” Button
Step 2 -> Enter the Case Type “ZDIS” – 7503 Dispute Management
Step 3 -> Enter the Category “1 “
Step 4 -> Enter the Category Description in the Text Field “Sales Personal”

Page 87 of 99
4/9/2021
Release:
Last saved by
Step 5 -> Click the Save button once complete
This Process was repeated for the following Reason Codes

Case Type Category Description (engl.) Description (dt.)
ZDIS 1 Sales Personal Vertrieb

ZDIS 2 Accounting Personal Buchhaltung
ZDIS 3 Other Other
Comments/Notes:
Create Values for Attribute Reason

Transaction Name: Create Values for Attribute Reason
>Dispute Case Processing -> Case Types -> Create Values for
Attribute Reason

Page 88 of 99
4/9/2021
Release:
Last saved by

Page 89 of 99
4/9/2021
Release:
Last saved by

Page 90 of 99
4/9/2021
Release:
Last saved by

This configuration activity provides users the ability to define/configure the Dispute Management
reason codes
Step 1 -> Click on the “New Entries” Button
Step 2 -> Enter the Case Type “ZDIS” – 7503 Dispute Management
Step 3 -> Enter The Cause Code “LP “
Step 4 -> Enter the Cause Description in the Text Field “ Late Payment”
Step 5 -> Click the Save button once complete
Case Type Cause Text

ZIDS LP Late payment
ZIDS BDW Bad Debt Write-Off
ZIDS OVP Overpayment

Page 91 of 99
4/9/2021
Release:
Last saved by
ZIDS RFQ Refund Request

ZIDS UDP Under Payment
ZIDS WPRD Wrong Product
ZIDS BPP Broken Promise to Pay
This Process was repeated for the Reason Codes above
This Reason codes were configured for 7503 dispute cases
Comments/Notes:
Create Profile for Case Search

Transaction Name: Create Profile for Case Search
>Dispute Case Processing -> Case Search -> Create Profile for
Case Search

Page 92 of 99
4/9/2021
Release:
Last saved by
Step 1 -> Enter the Profile -> FIN_LOC
Step 2 -> Enter the Name of Profile -> 7503 CASE Search Profile
Step 3 -> Enter the Table Name -> UDMCASEATTR00
Step 4 -> Highlight the 7503 CASE Search Profile
Step 5 -> Select -> Selection Fields
Step 6 -> Enter Row -> 1
Step 7 -> Enter Column -> 1
Step 8 -> Enter Case Attribute -> Processor
Step 9 -> Click “Sel. Opt”
Row Column Case Attribute
1 1 Processor
1 2 CREATE_TIME

Page 93 of 99
4/9/2021
Release:
Last saved by
2 1 STAT_ORDERNO
2 2 PRIORITY
3 1 EXT_KEY
3 2 EXT_REF
4 1 CASE_TITLE
4 2 CATEGORY
5 1 FIN_KUNNR
5 2 PLAN_END_DATE
6 1 FIN_DISPUTED_AMT
6 2 Dispute CURR
7 1 UDM_VKBUR
7 2 UDM_BELNR
8 1 UDM_BUZEI
8 2 UDM_GSBER
9 1 UDM_ZUONR
9 2 UDM_DZLSPR
10 1 UDM_MANSP
10 2 UDM_XBLNR
Within the prototype the added fields do not contain any functionality or data. The fields were
added to the table “SCMG_T_CASE_ATTR in order to visualize the relevant fields of a dispute
case search.
Comments/Notes:

Page 94 of 99
4/9/2021
Release:
Last saved by
Define Root Reason Code

Transaction Name: Define Attribute Root Reason Codes
>Dispute Case Processing -> Case Types -> Create Values for
Attribute "Root Cause Code"

Page 95 of 99
4/9/2021
Release:
Last saved by

Page 96 of 99
4/9/2021
Release:
Last saved by

This configuration activity provides users the ability to define/configure the Dispute Management
Root reason codes.
Step 1-> Enter “ZDIS” in the case type field
Step 2-> Click the Enter Button
Step 4-> Click the Enter Button
Step 5 -> Enter the Root Reason Code ID “01”

Page 97 of 99
4/9/2021
Release:
Last saved by
Step 6- > Enter Root Cause Code Description – “Posten maschinell ausgemahnt”
Step 7-> Click the “Save” Button when complete
This Process was repeated for the following Root Reason Codes
Root Cause Root Cause Code
01 Posten maschinell ausgemahnt
02 Kunde kürzt bei Zahlung
03 Kunde erwartet Teilgutschrift
04 Kein Skonto vereinbart
05 Skontofrist überschritten
06 Skontodifferenz
07 Rabattdifferenz
08 Kunde zahlt Serviceerhöhung nicht
09 Klärung mit Hausbank
10 Vertrag ist gekündigt
11 Liefer-/ Arbeitsnachweis fehlt
12 Rechnung ging zurück
13 Fehlerhafte Rechnung
14 Kürzung Transportspesen
15 Kunde unbekannt verzogen
16 Falsche Fälligkeit
17 Einbehaltene Sicherheit
18 Reklamation Kunde
19 Reklamation Vertrieb
20 Siehe Individualtext
21 Rücklastschrift wegen Widerspruch
22 Rücklastschrift ohne Widerspruch
23 Klageanfrage durch Mahnverfahren
24 Interne Gutschrift
Comments/Notes:

Page 98 of 99
4/9/2021
Release:
Last saved by
2. Issues
ID Description Summary
3. Reviewer/ Approvals
< Team lead comments on configuration rationale>

< BPOs and SMEs comments from CRP reviews>
Created on Page 99 of 99
Release: 1.0

Config Guide FSC M Prototyp

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Config Guide FSC M Prototyp

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Config Guide FSC M Prototyp

Uploaded by

Copyright:

Available Formats

Confidential - Internal use only

Configuration Guide for FSCM System at

Key Contacts for the deliverable are:

Version: Created on Page

Customizing Documentation for Prototype SAP FSCM

A. Configuration of Business Partner Synchronization.........................................................3

Activate Assignment of Open Credits and Payments....................................................................69

Version: Created on Page

A. Configuration of Business Partner Synchronization

Define Business Partner Role

 FLCU00 CVI: FI Customer - Customer/Vendor Integration: FI Customer

 UDM000 BP Collections Management Business Partner Collections Management

In the next step BP Roles will be assigned to a role category.

Version: Created on Page

Assign BP Roles to BP Role Category

Assign BP Roles to BP Role Category:

Version: Created on Page

Define Number Ranges

Define Number Ranges:

Version: Created on Page

Define Groupings and Assign Number Ranges

Define Groupings and Assign Number Ranges:

Version: Created on Page

Address Determination - Define Transactions

Address Determination - Define Transactions:

Version: Created on Page

Address Determination - Define Address Types

Address Determination - Define Address Types:

Version: Created on Page

Version: Created on Page

Address Determination - Assign Transaction to Address Type

Address Determination - Assign Transaction to Address Type:

Version: Created on Page

Set Geocoding - Process Geographical Data for Countries

Set Geocoding - Process Geographical Data for Countries:

Version: Created on Page

Process Geographical Data for Countries and Regions

Process Geographical Data for Countries and Regions:

Version: Created on Page

Maintain Tax Number Categories

Maintain Tax Number Categories:

Version: Created on Page

Maintain Industry Systems and Industries

Maintain Industry Systems and Industries:

Version: Created on Page

Application: SAP ERP

Maintain Industry Systems and Industries:

Version: Created on Page

Define Number Ranges for Business Partner Relationship

Define Number Ranges for Business Partner Relationship:

For internal administration of BP relationships and BP role definitions an internal number is

Version: Created on Page

Version: Created on Page

Activate PPO Requests for Platform Objects in the Dialog

Activate PPO Requests for Platform Objects in the Dialog:

Version: Created on Page

Address Determination - Define Transactions