inbound queue in APO side

[Former Member]

hi,

All R/3 changes are not transfered to APO. It got stuck in SMQ2 in APO side. every time i am manually activating those queues in ready status.

1) Is there any simple way to activate all the queues having status "ready" in single execution.

2) what will be the reason for inbound queue and how to avoid? i able to see only "ready" and "waiting" status queues there is no error

[Former Member · Accepted solution]

Hi Thennarasu,

Under LC10 transaction, you need to enter the name of database connection.

Then click on livecache monitoirng.

This will takes you to livecache monitoring screen. You can open the

Alert monitor for livecache database instance.

In the livecache monitoring screen, the properties of livecache database

instance will get displayed.

You can also monitoring tools and functions under the following areas.

1) Current Status

2) Problem Analysis

3) Statistics

4) Administration

5) Tools

You can also view error codes, user, information on system tables etc.,

Regards

R. Senthil Mareeswaran.

[Former Member]

Hi Thennarasu,

If you are having often struck or waiting queues, the probable reasons could

be

1) Check performance of livecache

2) Check master data

3) Check configuration

4) Carry out CCR very often to avoid inconsistency of data

5) Master data errors can be controlled via suitable action taken for sysfails

and application error logs.

This will have more control on struck queues

Regards

R. Senthil Mareeswaran.

[Former Member]

hi senthil,

Can you explain how to analyse performance of livecache in LC10?

[Former Member]

Hi,

Please check the status of the QIN and QOUT scheduler in transaction SMQR/SMQS and see if the destination is registered or not. I am pasting the content of the SAP Help for you quick reference.

**************************************************************************************************************************************************************

Set Up QOUT Scheduler

Use

Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).

You complete the following steps in the relevant client in the production system.

You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.

The following options exist for a registered destination:

Type

R: The destination is registered, that is, it is started using the QOUT scheduler.

U: The destination is not registered, that is, it is not processed.

N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.

Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.

Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.

The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.

Requirements

The qRFC configuration must be configured. For more information, see

**************************************************************************************************************************************************************

Set Up QOUT Scheduler

Use

Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).

You complete the following steps in the relevant client in the production system.

You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.

The following options exist for a registered destination:

Type

R: The destination is registered, that is, it is started using the QOUT scheduler.

U: The destination is not registered, that is, it is not processed.

N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.

Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.

Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.

The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.

Requirements

The qRFC configuration must be configured. For more information, see

**************************************************************************************************************************************************************

Regards,

Senthilrajan

Edited by: Senthil_APO on Oct 12, 2009 10:54 AM

Edited by: Senthil_APO on Oct 12, 2009 10:55 AM

[Former Member]

hi senthil,

thanks for your quick reply. in both a cases (SMQR/SMQS) scheduler status is "INACTIVE". so i need to activate?

[Former Member]

Hi,

Please see the value for the field 'Type'. If the value is U, that means the queue is not registered. Kindly click on the 'Registration' Button there and restart the queues.

Regards,

Senthilrajan