Identifying Business Components
When you have decided on the purpose of the integration (to create a customer or supplier opening balance, to complete banking entries for posted transactions, or to complete AR or AP payment cycles), you then identify the business components you want to be use to process the imported data.
For example, you may want to process payroll transactions for wages already paid as banking entries. You need to import both the transaction data and the employee data, and may want to import the employee data to be used as Financials system Employees. The components you will need are Banking Entry and Employee, and the data you import must comply with the schema files for these components.
To identify the name of the business component you need:
1 Right-click on the menu item.
2 Choose Properties.
3 Check the URI field.
For Financials objects, the name is typically in the format
urn:cbf:<businessComponent>.<Activity>.
(for example, BBusinessRelation.Modify)
You can now view the HTML documentation for this component. See
Tables and Mandatory Fields.
You normally use the Business Relations component when importing customer or supplier address and contact information. Business relations contain location and contact information for all addresses defined in the system. They also contain tax details that are directly referenced or used as defaults for customers and suppliers. Therefore, when converting your data to a dataset that can be processed as a Financials component, you should be aware of the component structure.
Identifying Components for Customer and Supplier Invoices
Posted customer and supplier invoices differ from other components in that the invoice can consist of two parts:
• The invoice posting
• The related journal entry postings
A standard Financials supplier or customer invoice posted to the official layer automatically contains all the required posting data. If you are integrating invoices that match the standard posted Financials invoice in every respect, you can therefore generate an XML dump from a Financials invoice to use as a template for integration. The components you need in this case are BDInvoice and BCInvoice.
If, however, you are integrating invoices that use different posting rules (for example, different expense or tax accounts, or different allocation), you should be aware that your integrated file must contain both the customer invoice data and the related journal entry data. In this case, the components you need for a posted customer invoice are BDInvoice and BCJournalEntry, and for a posted supplier invoice, BDInvoice and two BJournalEntry components (containing SI Posting data and Matching Posting data respectively).
When you have modified the field values with your data, you then combine the files into one. Schema files are available for a posted customer invoice (BDInvoiceJournalEntry) and posted supplier invoice (BCInvoiceJournalEntry), and you must rename the tags in your combined files to conform with these schemas.