BAPIs for Data Transfer to the FI/CO Interface 
BAPIs for Data Transfer to the FI/CO Interface
Use
The FI/CO interface (RWIN) is the central interface for transferring postings from other application components in the SAP R/3 System to Accounting. The FI/CO interface controls updates of actual data in Accounting and carries out checks from the Accounting standpoint.
Actual data relevant to Accounting from other SAP R/3 application components is first transferred to the FI/CO interface. The FI/CO interface then sends the data to the appropriate Accounting application component (such as Asset Management, Financial Accounting, Cost Center Accounting, Profit Center Accounting, Profitability Analysis, and so on).
Billing data from the Sales and Distribution (SD) application component is transferred to the FI/CO interface. The interface then creates the relevant Accounting documents (CO document, FI document, and so on).
You can use Business Application Programming Interfaces (BAPIs) to transfer postings from other application components to Accounting. A BAPI is a standard interface that facilitates the integration of the SAP R/3 System with the processes and data of other business application systems.
For more information about BAPIs, see the SAP Library under Cross-Application Components ® Business Framework Architecture (CA-BFA) ® Desktop Development (CA-BFA-INT) ® SAP Automation.
Features
The BAPIs transfer actual data to Accounting via the FI/CO interface. You can use the following methods (BAPIs) to transfer data from specific business transactions to Accounting:
AccountingGoodsMovement.Post
Goods movements are triggered by transactions in the Production (PP) and Sales and Distribution (SD) application components, or by inventory postings. In Logistics, they lead to adjustments in warehouse stock in the Inventory Management (MM-IM) application component. This also results in a posting to Accounting. Therefore, Accounting receives the relevant data from Logistics.
Consumption of raw materials results in an inventory change posted to Inventory Management. The posting is also transferred to Accounting.
The above check method checks whether the goods movement data relevant to accounting can be posted in Accounting.
The above posting method posts the goods movement data relevant to accounting in Accounting.
AccountingBilling.Post
Billing transactions in the Sales and Distribution (SD) application component result in billing data being sent to Accounting.
Goods sold on credit result in revenues, which are posted to billing and then transferred to Accounting.
The above check method checks whether the billing data relevant to accounting can be posted in Accounting.
The above posting method posts the billing data relevant to accounting in Accounting.
Posted revenues and sales deductions are updated to the Profitability Analysis (CO-PA) application component.
AccountingInvoiceReceipt.Post
The SAP R/3 Accounting components can accept data from invoice receipts posted in logistic systems.
Raw materials are sold on credit and the invoice receipt is posted in a logistic system. The FI/CO interface transfers the relevant data to the Accounting application components.
The above check method checks whether the invoice receipt data relevant to accounting can be posted in Accounting.
The above posting method posts the invoice receipt data relevant to accounting in Accounting.
AccountingPurchaseRequisition.Post
A purchase requisition created in Logistics represents a formal request to Purchasing to supply a specific quantity of material or perform a specific service at a specific date.
The expected costs from the purchase requisition have to be transferred to Accounting as purchase requisition commitments.
The purchase requisition commitments can update to the following components in Accounting:
The above check method checks whether the purchase requisition data relevant to accounting can be posted in Accounting.
The above posting method posts the purchase requisition data relevant to accounting in Accounting.
AccountingPurchaseOrder.Post
A purchase order created in Logistics represents a formal request from a purchasing organization to a vendor to supply a specific quantity of material or perform a specific service at a specific date.
When a purchase order is made for a material that is consumed immediately (that is, the material is not taken into stock), the expected costs have to be transferred to Accounting as purchase order commitments.
The purchase order commitments can update to the following components in Accounting:
The above check method checks whether the purchase order data relevant to accounting can be posted in Accounting.
The above posting method posts the purchase order data relevant to accounting in Accounting.
AccountingEmployeeExpenses.Post
G/L account postings made in Payroll and Travel Expenses update to Accounting. Examples of such G/L account postings include:
In this scenario, Accounting does not use accounts receivable or accounts payable accounting.
The above check method checks whether the G/L account postings made in Payroll and Travel Expenses can be posted in Accounting.
The above posting method posts the G/L account postings made in Payroll and Travel Expenses in Accounting.
AccountingEmployeeReceivables.Post
Accounts receivable postings made in Payroll update to Accounting. Examples of such postings include:
The above check method checks whether the accounts receivable postings made in Payroll can be posted in Accounting.
The above post method posts the accounts receivable postings made in Payroll in Accounting. The general ledger is also updated.
AccountingEmployeePayables.Post
Accounts payable postings made in Payroll and Travel Expenses update to Accounting. Examples of such postings include:
The above check method checks whether the accounts payable postings made in Payroll and Travel Expenses can be posted in Accounting.
The above posting method posts the accounts payable postings made in Payroll and Travel Expenses in Accounting. The general ledger is also updated.