Connecting Middleware to ERP
Accounting
Use
To connect the Intellectual Property Management to an ERP Accounting system, perform the steps described below.
The connection refers to the integration of SAP FI (Accounting) and SAP CO (Transfer CRM contract to the Accrual Engine, update orders received in SAP CO-PA, post billing documents from the Billing Engine to Accounting).
Prerequisites
You have defined an ERP site for your ERP System in the Middleware Administration Console in the SAP CRM System.
Refer to note 728949 here.
Procedure
Navigation
Menu Path (SAP CRM System) |
Transaction Code |
Architecture and Technology ® Middleware ® Administration ® Administration Console |
SMOEAC |
...
1. Enter the value Site for the Object Type field in the drop-down box and the value R/3 as the object name. Click on the symbol with the Display Objects quick info.
The system displays all of the SAP sites.
2. Select the SAP ERP System to be used for SAP FI by double clicking on it.
A definition of the system selected is displayed in the right hand section of the screen.
3. Select the symbol with the Change quick info in the menu bar and switch to the Subscriptions tab page in the screen area on the right.
The system displays all subscriptions that have been assigned to this site. You can change the subscriptions if necessary.
4. Assign the Billing Documents – Incoming Royalties (MESG)subscription by selecting the corresponding line and clicking on the symbol with the Assign quick info. Select the corresponding subscription in the dialog box that now appears and click on the symbol with the Copy quick info. If the subscription is not available, you must create it first (see below).
The Billing Documents – Incoming Royalties (MESG) subscription is then assigned to the site.
5. Repeat step 4 for the subscriptions Billing Documents – Outgoing Royalties (MESG) and All Business Transactions (MESG).
This assigns these subscriptions to the site selected.
6. If you want to use revenue recognition as a result of the OR data values, such as the paid value, repeat step 4 for the Billing Data Collector – Outgoing Royalties (MESG) subscription. This then also assigns the subscription to the site selected.
If the subscription is not already available, you must create it. To do so, select the value Subscription for the Object Type field. Click on the symbol with the Create Object quick info. The subscriptions wizard performs the additional steps.
Note that the name of the subscription must match the name of the publication. You can assign your ERP site to the subscription directly.
The subscription is created and assigned to the ERP site.
Menu Path (SAP CRM System) |
Transaction Code |
Architecture and Technology ® Middleware ® Administration ® Define Middleware Parameters |
R3AC6 |
The system performs the conversion to the XMS format for the ERP transfer as standard. This can however cause problems in ERP. To correct this error, refer to note 631238 (SAP adapter returns error during XMS conversion).
Alternatively, you can define conversion to XML format.
In this case, make the following entry for the transaction Define Middleware Parameters:
Parameter Name |
Parameter Value |
Comments |
DATA_FORMAT |
XML |
Do not make entries for the remaining fields. |
You should also check that the adapter objects exist and have been assigned to the correct mapping module in the transaction shown below.
Menu Path (SAP CRM System) |
Transaction Code |
Architecture and Technology ® Middleware ® Data Exchange ® Object Management ® Business Objects |
R3AC1 |
You can display details on the object by double-clicking on the adapter object.
Name |
Mapping Modules: ERP to CRM |
Mapping Modules: CRM to ERP |
Comments |
BEAACCRDOCIPMO |
|
CRM_IPM_BEA_IPMO_UPL_ACCR_SRV
|
Accruals for license acquisition |
BEABILLDOCIPMI |
|
BEM_UPLOAD_FI_SRV |
Transfer IR billing document to FI |
BEABILLDOCIPMO |
|
BEM_UPLOAD_FI_SRV |
Transfer OR billing document to FI |
BEABILLSTAIPMI |
BEM_DOWNLOAD_FI_SRV |
|
Status document for FI confirmation to IR billing document |
BEABILLSTAIPMO |
BEM_DOWNLOAD_FI_SRV |
|
Status document for FI confirmation to OR billing document |
IPMACEBDC |
CRM_IPM_BEA_BDC_DOWNLOAD_MAP |
CRM_IPM_BEA_BDC_UPLOAD_SRV |
Data values for the Accrual Engine |
IPMBEAACECONF |
CRM_IPMBEAACECNF_2_BDOC_MAP |
|
Confirmation of revenue recognized values from the Accrual Engine to the OR data collector |
IPMBEAFIPAYMENT |
CRM_IPMBEAFIPAYM_2_BDOC_MAP |
|
Confirmation of payment received from FI to the OR data collector |
IPMBEAPRDSLS |
CRM_IPMBEAPRDSLS_2_BDOC_MAP |
|
Confirmation of product sale to the OR data collector |
Ensure that the following entry is available for flexible mapping in Table View Maintenance (transaction SM30) for table SMOFSUBINT:
OBJCLASS |
CALL_ORDER |
SERVICE |
MOD_NAME |
Comments |
BEABILLDOCIPMO |
10 |
UPL |
CRM_IPM_BEA_IPMO_DET_UPL_ADP |
Do not make an entry in the remaining fields. |
Make these entries at the detailed level of the Monitoring Cockpit:
Menu Path (SAP CRM System) |
Transaction Code |
Architecture and Technology ® Middleware ® Monitoring ® Central Monitoring ® Middleware Portal |
SMWP |
We advise you to define the display mode for the middleware trace at detail level 1. To do so, choose Monitoring Tools/Statistics -> Trace Status (double click). Choose the entry DetailInfo 1 for the trace level in every environment.
Check whether the following table entries exist in tables CRMSUBTAB and CRMRFCPAR in the SAP ERP system:
Menu Bar (SAP ERP System) |
Transaction Code |
System ® Services ® Table Maintenance ® Extended Table Maintenance |
SM30 |
Table CRMSUBTAB:
User |
Object Name |
Up / Down |
Object Class |
Function Module |
Comment |
CRM |
BEAACCRDOCIPMO |
U |
BEABILLDOCIPMO |
CRM_IPM_ACCR_DOC_INBOUND |
The remaining fields are blank. |
CRM |
BEABILLDOCIPMI |
U |
BEABILLDOCIPMI |
BILL_DOC_INBOUND |
The remaining fields are blank. |
CRM |
BEABILLDOCIPMO |
U |
BEABILLDOCIPMO |
BILL_DOC_INBOUND |
The remaining fields are blank. |
CRM |
IPMACEBDC |
U |
IPMBEABDC_CL |
CRM_IPM_ACE_BDC_INBOUND |
The remaining fields are blank. |
Table CRMRFCPAR:
User: CRM
Object Name: *
RFC destination: RFC destination of your CRM System
Load Type: * (All Load Types)
BAPINAME: BAPI_CRM_SAVE
InQueueFlag: X
Send XML: X (Send XML) or M (Mixed mode, optimized)
The remaining fields are blank.