middle ware

7/18/2019 Middle Ware

http://slidepdf.com/reader/full/middle-ware-56d688e3e3821 1/16

Adaptor Objects:

Business adaptor object : R3AC1

Customizing adaptor object : R3AC3

Condition adaptor object : R3AC5

Queues:

Outbound queue monitor : SMQ1

Inbound queue monitor : SMQ2

Monitor Bdoc Messages BDOC’s: SMW01, SMW02

Trigger initial load : R3AS

Initial load monitor : R3AM1

Request load creation : R3AR2

Request load Monitor : R3AR3Request load : R3AR4

BDOC structure : SBDM

Queues register and de register : SMQR & SMQS

Initial setup B/n R/3 and CRM:

CRM :Settings in CRM:

Goto T code SE12

Check table “CRMCONSUM” display click on table contents (toolbar ….Box) (cltl + shift+f10)

Next screen Execute (f8)



We have to check the record that is in “Application Active” column “CRM” should have the value as “X”

(Active)

R/3:

1. SE12

Data base table “CRMCONSUM” display click on table contents execute same CRM

should be “X”

2. 2nd table “ CRMRFCPAR” (RFC –Remote function call we have QRFC, TRFC)

Table contents consumer =CRM

Execute (there should be one entry of CRM) RFC destination is “CRm systems RFC)

3. Check RFC destinations : SM59

ABAP connections double click on : (in IDES ex : DTZ 800) to create new connection type

&destination (it should be CRM system ) system no (AA) logon & security tab client no :100 USER ID (XYZ, user who uses this ) password (….) click on “ remote logon’ if every thing

works fine the CRM login will get open

CRM

Same SM 59 step to be done in CRM also(DII 800)



Maintain Sites:

T code: SMOEAC

Create

Name: R/3

Description: R/3

Type: R/3

Site attributes in RFC destination “DII-800(ex) enter automatically it will retrieve the details of the

logical system enter and save

(to check logical system name in R/3 Tcode : SALE)

Click on “create” down in subscriptions tab “publications ‘’ enter select all new window select all

copy save

Expand R/3 in left will see all subscriptions

Sites: system which are involved in data exchanging of data is called SitesPublications:



Some Notes:



Error Analysis:

Here some basic Bdoc monitoring knowledge is explained

Start SMW01 with following settings. In the Block "Bdoc State" I chose "Errors" as this is what I want

to monitor.

http://sapuniversity.eu/wp-content/uploads/2012/10/image0014.png



Press Execute.

You can see now if there are any BDOCS which contain mistakes.

The different relevant BDOC types that were relevant for monitoring at a particular customer were the

following:

- BUPA_MAIN: contains the master data of a business partner (and is triggered on creation and

change of a business partner)

- BUPA_REL: used when you create a relationship between two business partners

- PRODUCT_MAT: is used for data exchange of products/materials

- CRM_EQ_DMBDOC: used for data exchange of Equipments

- BUS_TRANS_MSG: for data exchange of transactional data

Once you get a list of Bdocs that went in error, you can check the error itself by selecting a line and

pressing the button





Now press the „blue button‟ errors.

You will see the actual error messages.

In this case we do know the Business partner number in the CRM system: 502664

Via the transaction BP we can lookup this „contact person‟.

In this case you will notice that the business partner has several mandatory fields that are not or at

least not correct maintained in CRM.















In this particular CRM system, the mandatory fields in CRM are:

- Country

- Correspondence language

After filling out these fields, at least the errors in SAP CRM for this contact person are solved.

Now, the BDOC will be triggered to create or update this contact person in R/3 too.

However, the Bdoc will go in error again due to the fact that we did not fill out a first and last name,

which are on their turn mandatory in the R/3 system.

NUMBER RANGES:

The number ranges for contact persons are different in the CRM system and the R/3 system.

For Customers the Business Partner number is the same in both CRM and R/3.




Lookup business partners (Customer/contact person/employee) in CRM: use BP

Lookup a customer in R/3: XD03

Lookup a contact person: VAP3

In order to know who created for example a business partner in SAP CRM, you can look up this

information in table BUT000 via transaction code SE16.

Fill out the relevant Business partner number, and press execute.







Select the line and press on the binoculars.

Scroll down and look at the field „Created By‟.

This contains the username of the person who created this business partner.

e.g. UK0290

Via transaction code SU01 or SU01D you can see who the user is. SU01D (display user master

record) in a SAP Production system. You can now contact this user about the problem.

After the correction is made by the user, you should verify the Bdocs again.

It might be necessary to reprocess the BDOC.




Product:

BDOC Errors:

Via SMW01 monitoring you will see for the BDOC type PRODUCT_MAT several errors.

Plant xxx is not assigned to any location

Value xx is not permitted for attribute product group

Details of the error:

If you look at the product via transaction COMMPR01







The available entries for input for the field “Product Group” in the CRM system currently are:




The Customizing table in CRM for Price (product) groups is the following:

CRMC_PRC_PRGRP

The customizing path is the following:

SAP IMG → Customer relationship Management → Basic Functions → Pricing → Pricing in the business

transaction → Groupings → Define Price groups (for products)

If you look at the material in the R/3 system on the tab page “Sales: sales org 2” you will see that the

material pricing group 51 is maintained.




Customizing path in R/3:

SAP IMG → Sales and Distribution → Basic Functions → Maintain Price-relevant Master data fields

→ Define Material Groups







The customizing table view is the following: V_T178

R/3 Table = T178

In order to know the customizing object we have to download, check the following in the CRM system:

Table: SMOFTABLES

→ Fill out table name = *T178*

Now that you know the Adapter object we have to download, launch the transaction R3AS.












You can monitor the download via transaction R3AM1.

The download was successfully.

Now you can check the CRM Customizing settings again.

The missing entries are now available.

You can now try to reprocess the faulty Bdocs for PRODUCT_MAT.





middle ware

Documents