BI - Error passing data to port

[Former Member]

Hi,

We have issues executing an info-package in BIQ200 (BIQ SYSTEM).

It uses RFC to get the data from ECQ220 (ECQ DEV SYSTEM).

The data is then written to a PSA file in BIQ200.

The process should end with a green status indicator. However it is not

ending and just times out.

Please note that this functionality worked before doing the Remote

client copy from productions system ECPCLNT320 to our ECQCLNT220. All

RFC destination are properly defined. Please note that this

functionality was working correctly before the remote client copy.

Attached are some screen shot. I am not sure if the setting in WE21 for

the transactional rfc "A000000015" should be changed from "SMXCLNT200"

to "BIQCLNT200". I noticed that the transcational rfc for "A000000016"

is BIDCLNT100 and "A000000017" is "BIPCLNT300" as per the attached

screen shot.

[Former Member]

I am not sure if i understand your post clearly,

Did you run BDLS in your source system(one for converting the logsys from ECPCLNT320 to ECQCLNT220, and another one for your BW system BIP??? to BIQ200)

you have to check for your partner profile(we20) to see which port(we21) is being used and then change it accordingly.

When you are done with the above, in RSA1 you may need to restore the source system(ECQ) and replicate/activate.

[Former Member]

This was a remote client copy not system copy. I check the BDLS in both system IE: ECQ and BIQ and the logical system are there for both system for ECQCLNT220 and BIQCLNT200. I checked the partner profile in both system and they are fine. I don't see anything in SM58 for BIQ system for IDOCS. Below are parnter profile info.

In ECQ220 SYSTEM FOR BIQCLNT200

Partner profile BIQCLNT200/LS

Header entry (table EDPP1)

Correct partner status

Recipient of notifications exists

Entries for outbound processing (table EDP13)

Entry BIQCLNT200/LS/ /RSINFO /

No Message Control entry for this entry

Port exists

Basic type exists

Link exists between logical message and IDoc type

Recipient of notifications exists

Entry BIQCLNT200/LS/ /RSSEND /

No Message Control entry for this entry

Port exists

Basic type exists

Link exists between logical message and IDoc type

Recipient of notifications exists

Entries for inbound processing (table EDP21)

Entry BIQCLNT200/LS/ /RSRQST /

Process code (inbound) exists

Recipient of notifications exists

IN BIQCLNT200 FOR ECQCLNT220

IDOCCHK184632

Partner profile ECQCLNT220/LS

Header entry (table EDPP1)

Correct partner status

Recipient of notifications exists

Entries for outbound processing (table EDP13)

Entry ECQCLNT220/LS/ /RSRQST /

No Message Control entry for this entry

Port exists

Basic type exists

Link exists between logical message and IDoc type

Recipient of notifications exists

Entries for inbound processing (table EDP21)

Entry ECQCLNT220/LS/ /RSINFO /

Process code (inbound) exists

Recipient of notifications exists

Entry ECQCLNT220/LS/ /RSSEND /

Process code (inbound) exists

Recipient of notifications exists

[Former Member]

Thareq,

I assumed wrong as system copy.

If every other settings are correct, you should check the load monitor RSMO.

From there, you can see where its stuck(you can check Backgroud, abap Dump,tRFC's,systemlog, connection, etc.).

This is the good point for you to start with to troubleshoot.

[Former Member]

I checked sm21, st22 and background jobs in BIQ 200 and everything seems looks fine except for 1 job as noted below. This job could be for something ealse I checked RSM0 --> Monitor Node --> 0ACCOUNT (5/26/2010) ECQCLNT220 (Red Alert: 18082 from 0 Records) . It seems like the data is pulled from ECQCLNT220 but the records just hangs to update in BIQCLNT200. Below is the log for RSMO.

RSMO LOG

-

---

Errors while sending packages from OLTP to BI

Diagnosis

No IDocs could be sent to BI using RFC.

System Response

There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.

Further analysis:

Check the TRFC log.

You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".

Error handling:

If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.

-

---

Job log overview for job: BI_PROCESS_CHAIN / 0400012A

Date Time Message text Message class Message no. Message type

05/26/2010 04:00:13 Job started 00 516 S

05/26/2010 04:00:13 Step 001 started (program RSPROCESS, variant &0000000032064, user ID RFC_USER) 00 550 S

05/26/2010 04:00:13 Start process CHAIN ZNGK_MASTR_TEXT in run D853A0PTCQ592DBNG11QE7V16 of chain ZNGK_MAST_DATA_LOAD RSPC 156 S

05/26/2010 04:00:14 Chain Is OK RSPC 028 S

05/26/2010 04:00:16 Chain ZNGK_MASTR_TEXT was removed from scheduling RSPC 026 S

05/26/2010 04:00:16 Chain changed! Scheduling in display mode not possible RSPC 113 I

05/26/2010 04:00:16 Process did not report an instance -> no log RSPC 057 E

05/26/2010 04:00:16 Job cancelled after system exception ERROR_MESSAGE 00 564 A

[Former Member]

You should check SM58 in your ECC side to check the issue.

[Former Member]

Thank you. This issue has been resolved.