Financial Team

1. Financial Team FI/CO, PS, RE & SD

2. FI (Financial Accounting) • GL (General Ledger) • AR (Accounts Receivable) • AP (Accounts Payable) • FA (Fixed Assets) • Travel • Cashiers • Validation Rules • Substitution Rules • Workflow

3. CO (Controlling) • Cost Elements • Cost Centers • Internal Orders • Settlements • Costing Sheets

4. PS (Project Systems) • Projects • WBS Elements

5. RE (Real Estate) • Properties • Buildings

6. SD (Sales & Distributions) • Sales Orders (Cost Reimbursable) • Billing Requests • Sales Contracts (Consortia & Directed Research) • Standard Periodic Billing • Deferred Revenue Billing (Media Lab) • Billing

7. Enterprise Structure Data Model MIT FM Area MIT Controlling area HEUS Chart of Accounts Tech Review Main campus Real Estate Foundation CUR Company Code REFI Company Code TECR Company Code One controlling area to many company codes. One company code to many sales organizations. One company code to many plants. Many company codes to many purchasing orgs. PPLT Plant Internal Provider Plants GPO GPO 1000 Sales Org 10 Sales Org 5000 Sales Org Purchasing orgs can be assigned to multiple company codes for corporate-wide purchasing. We currently do not have any corporate-wide purchasing orgs. GPLT Plant GPLT Plant RPLT Plant corporate wide purchasing GPO GPO TPO

8. FI/CO SD MIT Controlling area HEUS Chart of Accounts Main campus CUR Company Code The FI/CO SD (Sponsored Research Billings) Modeled through Data Normally, SD is found under Logistics because of its close ties to materials. At MIT, we sell research, which is not delivered per se, nor is it a real material. Therefore, it is much more closely aligned with FI/CO (receivables and revenue) than it is Logistics. 1000 Sales Org

9. FI Invoice doc # company code Header BELNR fiscal year BUKRS BKPF GJAHR Header BUZEI BSEG • BKPF • BUKRS • BELNR • GJAHR line item # Line items Line items 1:CN • BSEG • BUKRS • BELNR • GJAHR • BUZEI One header (1) can have any number of line items (CN)

10. Environment -> Accounting Documents Select “Cost accounting doc.”

11. CO Document controlling area KOKRS Header COBK COEP Notice that there is only one line item - CO reports on revenue and expenses only. It does not report on the receivable (the customer line item in the FI invoice). BELNR Line items Header doc # • COBK • KOKRS • BELNR BUZEI Line items 1:CN line item # • COEP • KOKRS • BELNR • BUZEI One header (1) can have any number of line items (CN)

12. SD Bill doc # Header VBELN VBRK Environment -> Source Document line item # POSNR VBRP Sales Org (VKORG) is not part of the primary key. But it is the ES attribute that separates one company code’s bill from another’s. Header Line items • VBRK • VBELN Line items 1:CN • VBRP • VBELN • POSNR One header (1) can have any number of line items (CN)

13. Environment -> Display document flow Select “Contract” - Display document

14. SD Contract (Sales Document) Header doc # VBELN VBAK POSNR ? Line items VBAP line item # In VBAK, transaction group, TRVOG, separates sales contracts from sales orders. Sales document type, AUART, separates sales orders from billing requests. Sales Org (VKORG) is not part of the primary key. But it is the ES attribute that separates one company code’s sales docs from another’s. Header • VBAK • VBELN Line items 1:CN • VBAP • VBELN • POSNR One header (1) can have any number of line items (CN)

15. SD Contract Billing Plans Header FPLA Billing plan number, FPLNR, and item, FPLTR, are never displayed. A sample data view from SE16 is on the web: ! fuller.mit.edu/tech/sample_fpla.htm FPLT Header One billing plan header for each line item on a contract with a billing plan, which is all the main campus contracts. The billing plan number for the contract line item is stored on VBKD, sales doc Business Data. Line items • FPLA • FPLNR Line items 1:CN • FPLT • FPLNR • FPLTR One header (1) can have any number of line items (CN)