Fi sd integration with copa

SAP – FISD CUSTOMIZING GUIDE FI-SD INTEGRATION
1 | P a g e
SANDESH KAKDE
EMAIL:sandeshkakde@live.com
SAP CUSTOMIZING – TABLE OF CONTENTS
SR. SUB. OBJECT TCODE EXAMPLE
1 DEFINE REGION 27 MH & 28 HYD
2 DEFINE SALES ORGANISATION OVX5 SRKS
3 DEFINE DISTRIBUTION CHANNEL OVXI SD
4 DEFINE SHIPPING POINT OVXD SKSP
5 ASSIGN SALES ORGANISATION TO CO. CODE OVX3 SRKS TO SRK
6 ASSIGN DISTRIBUTION CHANNEL TO SALES OG. OVXK SD TO SRKS
7 ASSIGN DIVISION TO SALES ORG. OVXA SP, SL, SC TO SRKS
8 SETUP SALES AREA OVXG SRKS-SD TO SL,SP,SC
9 ASSIGN SALES ORG. – DIST. CH- PLANT OVX6 SRKS-SD-SRKP
10 DEFINE RULES BY SALES AREA OVF2 “001” TO SRKS
11 ASSIGN SHIPPING POINT TO PLANT OVXC SKSP TO SRKP
12 DEFINE COMMON DISTRIBUTION CHANNEL VOR1 SD
13 DEFINE COMMON DIVISIONS VOR2 SC, SL, SP
14 DEFINE & ASSIGN PRICING PROCEDURE
A MAINTAIN PRICING PROCEDURE SKTV & MWST
B DEFINE PRICING PROCEDURE DETE. RVAA01 WITH PR00
C DEFINE TAX DETERMINATION RULE TAX Cat. MWST
15 SETUP PARTNER DETER. (CUSTOMER MASTER)
A DEFINE PARTNER FUNCTIONS SP, SH, PY, BP
B ACCOUNT GR. – FUNCTIONS ASSIGNMENT SP, SH, PY, BP TO SRKS
C CREATION OF PARTNER DET. PROCEDURE SRK
D ASSIGN PARTNER DET. PROCEDURE TO
PARTNER FUNCTIONS
SP, SH, PY, BP TO SRK
E PARTNER DET. PROCEDURE ASSIGNMENT SRKS TO SRK
16 ASSIGN SHIPPING POINT OVL2 SKSP TO SRKP
CREATE GL ACCOUNT FS00 “300005”
17 INTEGRATION BETWEEN FI & SD VKOA CTYPE “KOFI”-300005
TEST:
1 CREATE CUSTOEMR XD01 13000
2 CREATE MATERIAL (FINISHED PRODUCT) MM01 FEVERLET
3 CREATE CONDITION TYPE VK11 PR00 & MWST
CO-PA CONTROLLING & PROFITABILITY
ANALYSIS (INTRODUCTION)

2 | P a g e
1 MAINTAIN OPERATING CONCERN KEA0 SRK1
2 DEFINE PROFITABILITY SEGMENT CHAR. KEQ3 PRODUCT &
CUSTOMER
3 ASSIGN CONTROLLING AREA TO OPERATING
CONCERN
KEKK SRK TO SRK1
4 DEFINE NUMBER RANGE FOR ACTUAL POST KEN1 1 TO 99999999
5 ASSIGN VALUE FIELDS (SD – COPA FIELDS) KE4I PR00 TO VV0100 &
VPRS TO VV0110
6 SET OPERATING CONCERN PR00 TO VV0100 &
VPRS TO VV0110
7 MAINTAIN PA TRANSFER STRUCTURE FOR
DIRECT POSTING
KEI2 10 & 20 WITH SOURCE
& VALUE FIELD
8 ACTIVATE PROFITABILITY ANALYSIS KEKE “4”
TEST
1 CREATE SALES ORDER VA01 433
2 PRODUCTION RECEIPT WITH MTYPE 521 MB1C 100055
3 CREATE OUTBOUND DELIVERY VL01N 80000282
4 SALES BILLING VF01 900000
5 DISPLAY CO-PA DOCUMENT

3 | P a g e
INTRODUCTION:
The Accounts Receivable (FI-A/R) component can help manage your customers and receivables, from
both the FI and SD perspectives. As in the case of FI-A/P, all the postings and transactions you make in FI-
A/R are also updated in FI-G/L in real-time; as a result, the general ledger is always up to date with the
A/R subledger. It comes with standard functions for managing business transactions, such as incoming
payments (from a variety of payment media, including payment cards), open-item clearing, and interest
calculation. Its dunning program helps to remind (dun) your customers of their payment dues. The
automatic payment program discussed in MM can also be used to directly debit down payments.
Interfaced with the SD module, it helps you to effectively administer and manage the credit and
associated risks. The customer information system comes with the necessary evaluations and reports for
monitoring and analysing the receivables. However, you need to customize the A/R subledger correctly to
reap the full potential of the module. Our focus of discussion in this chapter, among others, includes
Customizing the following:
_ Customer account master data
_ Business transactions
_ Credit management
_ Interest calculation
_ Dunning
Customer Account Master Data
A customer is a business partner for whom you create a master record in the SAP
system (although there is a separate type of business partner by the name of “customer”
in SAP, in this book we will consider a customer as one who owes a
receivable to you and may be any of the business partner types, including sold-to
party, consumer, and customer). Used in both FI and SD applications, a master
record identifies a customer and controls how you manage the business transactions
in the system.
Structure
The arrangement of data in a customer master record is similar to that of a vendor
master record, with three distinct segments: general data, company code data,
and sales area data.
The general data is applicable to all the company codes and sales organizations to
which a customer belongs. Specific to a company code, the company codedata
includes reconciliation account, interest indicator, terms of payment, payment
methods, house bank, tolerance group, and dunning procedure. The sales area
data consists of sales, shipping, billing, and partner function details.
for example, you will see information like sales district, sales office,
sales group, ABC classification, and more in the Sales tab.

4 | P a g e
However, you should note that certain preparations need to be in place before
you can create the master records. We will go over each of these requirements in
the following subsections.
Prepare for Creating Customer Masters
As in the case of G/L or vendor masters, you need at least one account group
defined in the system before you can start creating the master records for your
customers. The other preparations include defining the required number of number
ranges and the field status for the account groups.
©
SD CONSULTANT JOB:
Step 1: DEFINE REGION: (STATE)
Here we define the region where our business is operating their activities. In
current scenario Company code SRK is operated its business in two different
regions i.e. Maharashtra & Andhra Pradesh.

5 | P a g e
Step 2: DEFINE, COPY, DELETE, CHECK SALES ORGANIZATION:
A sales organization is responsible for the sale and distribution of goods and
services. It represents the selling unit as a legal entity. It is responsible for
product guarantees and other rights to recourse, for example. Regional
subdividing of the market can also be carried out with the help of sales
organizations.
OVX5:
In SD side we define the sales organisation. Like we define company code in FI
and purchase organisation in MM. In current scenario, we have maintained
“SRKS” as sales organisation.

6 | P a g e
Step 3: DEFINE DISTRIBUTION CHANNEL:
SAP Sales and Distribution (SAP SD) is a core functional module in SAP ERP
Central Component (ECC) that allows organizations to store and manage
customer- and product-related data. Organizations use this data to
manage all the sales ordering, shipping, billing, and invoicing of their goods
and services.
OVXI:
Here we have defined “SD” as distribution channel.
Step 4: DEFINE SHIPPING POINT:
Shipping points are independent organizational entities within which
processing and monitoring of the deliveries as well as goods issue is carried
out. A delivery is processed by one shipping point only.
OVXD:

7 | P a g e
Here we define shipping point as “SKSP”.
Till here we have defined Sales org., Distribution channel and Shipping
Point. Further we must assign them with each other and create a link
between them.
Step 5: ASSIGN SALES ORGANIZATION TO COMPANY CODE:
OVX3:
In above screen we have assigned created sales organisation “SRKS” with
our Company Code “SRK”.
Step 6: ASSIGN DISTRIBUTION CHANNEL TO SALES ORG.
OVXK:

8 | P a g e
Step 7: ASSIGN DIVISION TO SALES ORG.
PREREQUISITE:
DEFINE DIVISION:
The system uses divisions to determine the sales areas and the business
areas for a material, product and service. use of Division. A product and
service are assigned to just one division. The use of divisions lets you to
organize your sales structure around groups of similar products or product
lines.
OVXA:
Once we have created division, must assign them with sales organisation. In
current scenario Company code SRK has three divisions. SP, SL & SC.

9 | P a g e
Step 8: SETUP SALES AREA:
SD is organized according to sales organization, distribution channel and
division. A combination of these three organizational units forms the sales
area. Sales organization: An organizational unit within logistics that sells
and distributes products and negotiates terms of sale.
OVXG:
Here we have created the link between Sales org., Sales distribution and
divisions.
Step 9: ASSIGN SALES ORG. – DISTRIBUTION CHANNEL – PLANT
OVX6:
Sales organisation, sales distribution is assigned to plant which we have created
in MM configuration.

10 | P a g e
Step 10: DEFINE RULES BY SALES AREA:
OVF2:
Step 11: ASSIGN SHIIPING POINT TO PLANT:
OVXC:
Step 12: DEFINE COMMON DISTRIBUTION CHANNEL:
VOR1:

11 | P a g e
Step 13: DEFINE COMMON DIVISION:
VOR2:
Step 14: DEFINE & ASSIGN PRICING PROCEDURE:
Pricing Procedure is indeed a heart of SD module, reason being if everything else
is working fine, but price is not being calculated correctly, the purpose of billing
fails.
An Overview of Determination & Configuration of Pricing Procedure is as follows:
A) Maintain Pricing Procedure:
Deselect the required check box for condition type SKTV & MWST.
B) DEFINE PRICING PROCEDURE DETERMINATION:
Maintain below new entries.

12 | P a g e
C) DEFINE TAX DETERMINATION RULE:
Material Tax Classification (You give in Material Master) Rest of
the determination takes places as per condition Technique i.e., You have
a tax determination procedure - TAXINJ / TAXINN. System will read pricing
procedure and reads MWST (TAX Condition Type) against this you have
access sequence.
Step 15: SETUP PARTNER DETERMINATION:
This a procedure by which system selects the assigned sales relevant partner
function/functions to the object in Order to Cash process.
In brief, sales partner are business parties which are involve/relevant to a sales
process/transaction. Each partner is defined/identified based on role & function
they play in those sales’ process/transaction. These can internal or external to an
organization. To setup, determine & copy these business partners in a sales
process or specific sales process or master in SAP SD, we use a search technique,
known as Partner Determination.

13 | P a g e
Then select Setup Partner determination for Customer Master
A) First, we define the Partner Functions
i.e. Sold to party, Ship to party, Payer, Bill to Party.

14 | P a g e
B) Select Partner Function and click on account groups – function assignment

15 | P a g e
Repat this step for all partner functions.

16 | P a g e
C) Creation of Partner Determination procedures
In Current scenario, we have created “SRK” as partner determination procedure.
D) Assign partner determination procedure to all partner functions in
procedure
Select partner determination procedure “SRK” and double click on partner
functions in procedure folder.

17 | P a g e
Maintain all partner functions with partner determination procedure.
E) Partner determination procedure assignment:
Double Click on Partner determination procedure assignment folder and
assign partner determination procedure “SRK” with Sales Org. “SRKS”

18 | P a g e
Step 16: Assign Shipping points:
OVL2:
Here we have finished with SD Consultant Job.
FI CONSULTANT JOB:
Step 16: Create GL Account “300005” – Local own goods a/c
FS00:
Step 17: Integration between FI and SD
Here we integrate the FI system with SD. Like we have OBYC t-code in MM.
VKOA:
Click on Table “1”

19 | P a g e
Maintain the above combination for Condition type “KOFI”

20 | P a g e
TEST:
1) Create Customer
XD01:

21 | P a g e

22 | P a g e
2) Create Material:
MM01:

23 | P a g e

24 | P a g e

25 | P a g e

26 | P a g e

27 | P a g e

28 | P a g e
3) Create a Condition type:
VK11:
SELECT USING CONDITION TYPE-CREATE

29 | P a g e

30 | P a g e
CO-PA CONTROLLING & PROFITABILITY ANALYSIS
Introduction:
Co for Controlling
PA for Profitability Analysis
This is used to view profitability for number of parameters at a time:
Eg: Customer wise /Product wise /Sales order wise/ plant wise, Sales
organization
profitability.
Account based profitability /costing-based profitability analysis / both (in India
we use
both)
PP Module
MM Module
FI Module à product costing à SD module à CO-PA
CO Module
Define an operating concert:
Operating concern can be equal to controlling area or above controlling area
Controlling area can be equal to our company code or above company code
Company code =controlling area =operating concern
Data structure
Characteristics Value fields
Customer
Product
Sales order
Plant Sales cost of goods sold net profit
Sales organization
Sales employee
Country
Profitability segment:

31 | P a g e
It consists of
A) System defaulted characteristics
Eg: customer / Product / Sales order /Plant /Sales organization
B) Client required characteristics
Eg: Sales employee / Industry
Data flow in SD module:
1. Inquiry and quotation
2. Sales order –customer /product /plant sales organization /quantity /rate
delivery
terms payment terms.
3. Delivery with reference to sales order.
A) without posting goods issue (without PGI)
B) with post goods issue (with PG1)
4. Sales billing with reference to delivery
Data flow in Co-PA:
SD condition types CO-PA value fields
PR00 Price VV 0100 – Revenues
VPRS Costs VV 0110 – Cost of goods
sold
(Product costs)
(up to COGM level) CO - +FI COGM Admin & SD
Exp.
(Both –costing based, and account
based)
We are going to MAP:
PR00 =VV0100
VPRS=VV0110
Product cost : Feverlet
Cost sheet: Feverlet
Raw materials xxx
Raw material overheads xxx

32 | P a g e
Production costs xxx ----- Production valuation will be at COGM level or
COGM+ admin exp level.
Cost of goods manufactured xxx
(COGM)
Administration xxx
Sales & Distribution xxx
-----------------
Cost of goods sold (COGS) Xxxxx
Configuration:
1) MAINTAIN OPERATING CONCERN:
The operating concern is the key organizational unit within CO-PA. It defines
the extent of the marketing and sales information that can be reported in
combination by this component. One or more controlling areas are assigned
to an operating concern when organizational structures are defined.
KEA0 :
Maintain Operating Concern name which we want to create. In current scenario
We have maintained “SRK1” as operating concern.
Enter.

33 | P a g e
Select Costing based and Accounting based profitability analysis.
Maintain Currency, and Fiscal year variant. It should same as per controlling area.
SAVE

34 | P a g e
Then go to Data structure tab.
Click on create button.
Transfer KMVTR as a characteristic.

35 | P a g e
Go to Value field tab.
Transfer VV0100 and VV0110 as Value field.
SAVE & Activate

36 | P a g e
BACK

37 | P a g e
2) DEFINE PROFITABILITY SEGMENT CHARACTERISTICS:
KEQ3:
3) ASSIGN CONTROLLING AREA TO OPERATING CONCERN
KEKK:

38 | P a g e
4) DEFINE NUMBER RANGE FOR ACTUAL POSTINGS:
KEN1:

39 | P a g e
5) ASSIGN VALUE FIELDS:
KE4i
6) SET OPERATING CONCERN:

40 | P a g e
7) MAINTAIN PA TRANSFER STRUCTURE FOR DIRECT POSTING:
KEI2:
Maintain Source and value field for Assignment “20”

41 | P a g e
Same step followed for Assignment line 10.
8) Activate profitability analysis
KEKE:
Here we activate the profitability analysis.

42 | P a g e
Test:
1) Create Sales Order
VA01:
Ctl+F8 to check document completeness
Save.

43 | P a g e
Production receipt:
Scenario 1: With movement type 521
Scenario 2: With movement type 101
Prerequisite:
Assign Variant to Transaction code (Since we have activated the Document
Splitting, we must maintain below setting)
GSP_VZ3:

44 | P a g e
MM02:
Material Feverlet should have profit center in material master

45 | P a g e
MB1C:
ENTER

46 | P a g e

47 | P a g e
Outbound Delivery:
Prerequisite:
Assign Variant to Transaction code
Assign G/L for Item category 0001

48 | P a g e
VL01N:

49 | P a g e
Sales Billing:
Billing document:
VF01:

50 | P a g e
We can see Profitability analysis document is also created.
End FI-SD Integration with CO-PA

Fi sd integration with copa

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Fi sd integration with copa

Similar to Fi sd integration with copa (20)

More from Capgemini

More from Capgemini (10)

Recently uploaded

Recently uploaded (20)

Fi sd integration with copa