FI-PP integration takes place mainly at these stages-

1) When you create and release the production order, the planned costs will be calliculated from BOM
and Routing/Master Recipe master data.-Co document will be generated for Planned postings

2) When you issue goods(Raw materials) to production (against Production order) the FI and CO entries
will get generated -CO27
FI Entry- Consumption A/C Dr
To Inventory A/C Cr
CO primary cost postings will be triggered against the cost center.

3) When operations in routings are confirmed , the cost centers in the work centers will be charged with
the activity costs
Here secondary cost postings will be triggered in the production cost centers.

4) After final confirmation of the operations, the GRN will takes place against the production order, here
also CO and FI documents will be generated -CO11
FI-Entry-
Finished Goods A/C Dr
To cost of goods produced A/C

5) If the production order is not confirmed fully, we have to run WIP at the month end-KKAO
FI entry- WIP A/C Dr
To Change in WIP A/ c Cr
The above entry will be reversed at the time of settlement of production order.

6) When the PO is technically completed, then settlement of PO takes place-K088
FI entry-
Price Difference(Goods) A/C
To cost of goods produced A/C


Integration FI, MM & SD
1. In SAP you will always get integration with other modules.
SD will interact with FI,
MM will interact with SD :-

1a. Looking at MM and SD interaction first, take the scenario of a
third party order process.
This process uses a PO (which is sent to your vendor)

Also invoice verification is used further along the process to check
that the invoice you send to your customer is the same material
and quantity as that which the vendor sends to you
(but obviously shipped directly to your customer).

1b. Billing is an SD function.
But SAP needs to know, when processing a customers payment,
to which GL account the payment has to be processed.

For instance payment of a UK based material would be placed in
a different GL account to that of a non-UK based material.

Furthermore, a UK based customer may have a different GL
account to that of an Export customer.
This is configured in Account Determination.

2. ABAPers are there to essential do some bespoke development.
Your integration, or interaction, with them would be when specifying
the tables, fields, input fields, a simple process explanation, data
mapping (if doing an interface from one system to another) etc.

The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are
copied from Material master of MM.

2. MRP and availibility check related data is also taken from MM
although you control this data in SD also.

3. While you create inbound/outbound delivery with reference to a
sales order,the shipping point determination takes place with the
help of the loading group, plant data, shipping conditions etc.
This also refers to Material Master.

4. The material which you are entering in a sales order must be
extended to the sales area of your sales order/customer
otherwise you cannot transact with this material.
There are many such links between SD and MM.


The link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order,
goods movement takes place in the bacgground.
eg. In case of standard sales order, you create an outbound
goods delivery to the customer.

Here movement 601 takes place.
This movement is configured in MM. Also, this movement hits
some G/L account in FI.
Every such movement of good s hits some G/L account.

2. The accounts posting in FI is done with reference to the billing
documents (invoice, debit note, credit note etc) created in SD.
Thus this is a link between SD and FI

3. Tax determination: In case of a tax determination also, there is a
direct link between SD and MM



SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.

Sales Order Integration Points Module
Availability Check MM
Credit Check FI
Costing CO/ MM
Tax Determination FI
Transfer of Requirements PP/ MM

Delivery & Goods Issue Integration Points Module
Availability Check MM
Credit Check FI
Reduces stock MM
Reduces Inventory $ FI/ CO
Requirement Eliminated PP/ MM

Billing Integration Points Module
Debit A/R FI/ CO
Credit Revenue FI/ CO
Updates G/ L - FI/ CO
(Tax, discounts, surcharges, etc.)
Milestone Billing PS

Return Delivery & Credit Memo Integration Points Module
Increases Inventory MM
Updates G/ L - FI
Credit Memo FI
Adjustment to A/R FI
Reduces Revenue FI




Transparent table: One to one relation
One table in data dictionary equal to one table in data base.
i. e When u create one transparent tabel in ABAP dictionary one table will be created in Database(Typically Oracle, U
can have others also) with same name(Both tabel and fields).
Basically used to hold application data.
EG: EKKO,VBAK etc.

Pooles tabel: Many to one relationship
Many tables in ABAP dictionary equal to one table pool in database. Basically used to hold system data and
customization data. One table pool contains large number of pooled tables having data of around 100 records each.

Cluster tables: Many to one relationship
Many tables in ABAP dictionary equal to one table cluster in database. Basically used to hold application data. One
table cluster contains few number of cluster tables having data of around large quantities.(In lakhs)
eg:CDPOS, BSEG etc.

Incase of pooled and cluster tables ABAP data dictionary table name and Data base table and field names differs
unlike same in case transparent table.

There are some limitations on cluster tables like we can't use joins on these tables, Select on cluster table is always
very slow.

When ever we write query on any cluster table in the table cluster data will be fetced for all the table as data for all the
tables in the cluster stores as a single record.

In reality we hardly create pooled and cluster tables.

Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data
and fields.


Pooled Table : Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables
are used to store control data. Several pooled tables can be cominied in a table pool. The data of these pooled tables are
then sorted in a common table in the database.


Cluster Table : Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster
tables can be used to strore control data. They can also be used to store temporary data or texts, such as documentation.


difference between Standard tables, Pooled tables and Clusterd Tables
A transparent table is a table that stores data directly. You can read these tables directly on the database from outside
SAP with for instance an SQL statement.


Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will
create in data base and if is basically used to store transaction data.


A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one
field.


One of the possible reasons is for instance that their content can be variable in length and build up. Database
manipulations in Abap are limited as well.


But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which
is know as table pool.


All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster
table it is must. And pool and cluster table is basically use to store application data.


Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but
few (1 to 10) cluster table.


For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table.
You can use native SQL statement for pool and cluster table.


A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.


A view is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way
the data needs to be represented. You actually call directly upon the underlying tables.


Transparent :
Contain a single table. Used to store master data
It has a one-to-one relationship with a table in the database
For each transparent table there is one associated table in the database
The database table has the same name, same number of fields and the fields have the same names
There is only a single table
Single table can have one or more primary key
Secondary indexes can be created
They can be accessed using open and native SQL
USE: They are used to hold master data e.g. Table vendors or table of customers. Example of transaction data is
orders placed by customers

Pooled:
They are used to hold a large number of very small tables(stores customizing data or system data)
It has a many-to-one relationship with a table in the database
It is stored with other pooled tables in a single table called table pool in the database
The database table has different name, different number of fields and fields have different names
Table pools contain more tables than table clusters
Primary key of each table does not begin with same fields or fields
Secondary indexes cannot be created
They can be accessed using open SQL only
USE: They reduce the amount of database resources needed when many small tables have to be opened at the
same time

Cluster:

They are used to hold data from a few number of large tables.(stores system data)
It has a many-to-one relationship with table in the database
Many cluster tables are stored in a single table in the database called a table cluster
The database table has different name, different number of fields and fields have different names
Contains less tables than table pools
Primary key of each table begins with same fields or fields
Secondary indexes cannot be created
They can be accessed using open SQL only
USE: They would be used when the tables have primary key in common and data in these tables are all accesses
simultaneously