Initial load of product categories - Middleware issue

[former_member184214]

Hello all,

I need fresh idea regarding middleware problem that I am facing.

My setup of middleware is done by note 720819, sites (CRM and R/3) are defined, report for product settings is run (service set to inactive), RFC connections set, filters for DNL_CUST_PROD1 set and nothing is happening when I try to transfer material groups for the backend. RFC users have SAP_ALL.

Object is in status running and that is. I checked RFC connection and it is working, so EBP is entering R/3 and here everything stops.

I used note 429423 for analysis with no much use because there is no BDocs at all.

customizing is the same on DEV and QAS but on QAS is doing nothing while on DEV is happily executing.

Please give some clue what is happening.

TIA

Gordan

[Former Member · Accepted solution]

Hi Gordan,

if your object is in status "Running", you might found something in the queues.

Check SMQ1 & SMQ2 in SRM and in R/3 as well, and tell me if you find something.

Rgds

Christophe

[former_member184214 · Accepted solution]

Hello Christophe,

Both queues are empty even object status is "running".

Looking at Adapter status information in CRM Middleware monitor I have yellow light for node "CRM default entry for object load from R/3 Backend" - "No default entry exists". Explanation is like I do not have entry in backend table CRMRFCPAR which I have for bot Initial and Delta download.

Gordan

[Former Member · Accepted solution]

Gordan

Check the following entries in R/3.

1.See if users CRM and EBP are maintained in table CRMCONSUM.

2. Check for entries for EBP and CRM users in table CRMRFCPAR.

Also Ref SAP note 432339.

Regards

Jagdish

[former_member184214 · Accepted solution]

So,

after digging around EBP and R/3 (do you remeber Digger game) I found out two things.

1. RFC user had wrong authorizations (not SAP_ALL, SAP_NEW) what was different that on other systems. Finally agree with other that this authorizations are possible if user is not dialog.

2. Because load was started with unproper authorizations it was stuck in OUTBOUND queue of SRM. When I deleted loads in queue and with proper authorizations everything went OK.

Point: do not look only inbound queue in SRM

Gordan

[Former Member · Accepted solution]

I Gordan,

That's why I told you to

"Check SMQ1 & SMQ2 in SRM and in R/3 as well"...

Rgds

Christophe

[yann_bouillut]

Hi Gordan,

How was your QAS system created ?

Is it a copy from DEV ?

Kind regards,

Yann

[former_member184214]

Hello Yann,

no QAS is istallation.

I forget systems: EBP is 5.0, R/3 is 4.7

Gordan