IDXQUEUE

Hi experts,
I have a file to idoc scenario.
I want the idoc to be processed in the order of creation in SAP ECC.
I checked this blog :
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter
my web as is 6.40
but it does not seem to do anything, I created entries in the table IDXQUEUE in XI, but the I dont see the results at all, there is no changes, do you happen to know why ? The idoc still get in the standard queues XBT1_etc.. I also checked the 'queue processing' box also
Kind regards,
Jamal

HI Jamal,
Re: IDXQUEUE
While creating Partner profiles there are multiple types (ie WE20) In ECC
example one which i mentioned: KU (mean customer)
others: like LS- Logical system, US - user .....u choose according ur strategy..create partner profile and maintain
orders05 (example which i mentioned ) - (Idoc type for sales order or purchase order...)..what ever ur Idoc type...
u need to maintain as inbound parameters in that partner profile in ECC.
I hope u understood what i mentioned
Thanks
Prabaharan
Edited by: Prabaharan Rangasamy on Mar 10, 2009 3:24 PM
Edited by: Prabaharan Rangasamy on Mar 10, 2009 3:24 PM
Edited by: Prabaharan Rangasamy on Mar 10, 2009 3:27 PM
Edited by: Prabaharan Rangasamy on Mar 10, 2009 3:32 PM

Similar Messages

IDXQUEUE entry

I needed to serialize idocs while they were sent from r3 to xi. It worked fine with me when i reffered to the blog.
Setting up inbound qRFC queues for serializing IDocs using the IDoc Adapter and it worked fine.However i need to send the idoc with same message type with different values in mescod and mesfct to be routed to different queues. eg if message type = ZIDOC, mescod=aa and mesfct=bb then it must hit the queue zidocab, if mescod=ZIDOC , mescod=cc,mesfct=dd, it must hit the queue zidoccd. How should i make the table entry in idxqueue.
Please help.

Hi Saswata
check this blog How to serialize IDoc XML messages fed into XI there you can use a function module for specifing the correct queue to use.
Kind regards
Jochen

How to use table IDXQUEUE ?

Hello,
i have populated that table with an mestyp (Z1OILH01) and the correct port to ensure that all IDOCS are processed within one queue to ensure the correct order. The name of my new Queue is QUEUE1_TEST.
But nothing happend. I can still see that in SXMB_MONI the queue-id used is something like XBOT*. What can I do ?
Thanks and regards,
Christian

hi stefan,
this is a "pure" IDOC-scenario...
the third party is sending IDOCs - so there is no sender communication channel defined (not possible).
The receiver system is SAP4.72 and I set the OoS of the receiver communication channel to EOIO (Queue processing checked) via IDOC-adapter.
Is table IDXQUEUE working im my scenario for incoming idocs anyway?
That piece of documentation comes from:
<a href="http://help.sap.com/saphelp_erp2004/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm">http://help.sap.com/saphelp_erp2004/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm</a>
and
<a href="http://help.sap.com/saphelp_erp2004/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm">http://help.sap.com/saphelp_erp2004/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm</a>
I thought, through table IDXQUEUE I could "simulate" an EOIO for incoming IDOC... and with the receiver communication channel via idoc-adpater the outgoing IDOCS an EOIO again...
Thanks for any help!
Regards,
Christian

IDoc Sender - XI - Proxy Receiver with EOIO?

Hi all,
1) I'm sending custom Message Type/IDoc to XI using function module MASTER_IDOC_DISTRIBUTE from 4.7 ERP/6.2 Basis system.
2) In XI's integration engine I will be mapping the IDoc record layout to my proxy record layout. XI is Netweaver 04/6.4 Basis
3) The last step is to use the Proxy adapter to send the data to my receiver which is a BW Netweaver 04S/7.0 Basis system.
I know how to guarantee EOIO during step 3 and within my receiving system. Can I guarantee steps (1) and (2) above use QoS EOIO? If so any thoughts/discussion on how to do that would be appreciated.
Thanks!

Hi Shaun,
unfortunately in this case there is no chance..
You could pack idocs and send them all togheter, this is a queue-like processing but is not a robust and stable approach.
All you can do is to enqueue starting from XI configuring the right entries in table IDXQUEUE.
Regards,
Sergio

Sequential Message Processing in IDOC - HTTPS scenario

Hi Experts,
I have an IDoc - PI - HTTPS scenario. One of the requirement is to maintain the data sequence while processing.
This means that the sequence in which the IDocs are received by PI, should be the same sequence in which it should be posted to the URL from PI interface.
Incase, there is a connectivity issue with the URL at any point of time, then the data should be queued sequentially in PI and once the issue is resolved, the data should again process in sequence.
Please let me know which is the best approach to achieve this?
Assume the mapping is very simple
Regards,
Prajeet

Hi Anshul,
We opted to go for IDOC Serialisation. With this, we achieved the sequential data processing through the PI interface.
I did check a blog in SDN which had step by step instruction to achieve this, but cannot find it now
Anyways, will give you a idea on wat needs to be done at PI and SAP R/3 end.
At PI end:
Using SE16 as the transaction, We need to create a entry in the table: IDXQUEUE
 a.PORT - (SAP R/3 system port)
 b.CLIENT - (SAP R/3 system client)
 c.MESTYP - (IDoc MSGTYP)
 d.QUEUEID - (Random Queuename, for eg: EOIO_PI_Interface)
At SAP R/3 end:
1. Create a function module. The QUEUEID created in SAP PI should be mentioned in this function module. <this basically indicates which PI queue will handle this message>
2. Using transaction we85, create a queue processing rule (which would call the function module)
3. In the partner profile, for the particular Idoc type, queue processing option must be enabled. And the queue processing rule (as defined in step 2 above) should be specified here.
Hope this information helps.
When I find the link to the blog, will post it here.
Thnx,
Prajeet

IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

Hello SDN Gurus,
The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
The IDOCS produced in Appl system may be in the following order
PAYEXT
PAYEXT
EUPEXR
PAYEXT
PAYEXT
PAYEXT
EUPEXR
I need them to be processed in the same order into flat file.
The scenario is working good except for the serialization. So I did the following
Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types. I used the following link to create the above two steps.
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
The SAP system in based on WAS 6.4.
I can see the queue name & EOIO in the inbound message header.
I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
Does anybody had this problem earlier? Please advice.
Thanks
Srini Vaidyam

I found an OSS note to resolve my issue. The note number is 1057573.
Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
This forum Rocks.
Thanks.
Srini Vaidyam

EOIO for IDOCs to XI

Hi,
My scenario is IDOC ---> xi ---> File.
Need to implement EOIO(serialization) for IDOCs coming from ECC.
Checked "Queue Processing" and assigned rule "FIRST_16_OF_MESTYP".
When I send the IDOC using WE19, I get message "IDocs are stored in the queue".
But, IDOCs are not coming to XI. Please help.
Versions: ECC 6.0 & PI 7.0 SPS 13.
Also, do I need to maintain an entry in IDXQUEUE table?

Hi
use similar thread
How to implement IDOC Serialization(EOIO) using IDOC Adapter
Re: Posting idocs in sequence in SAP from file (without BPM)

How to implement IDOC Serialization(EOIO) using IDOC Adapter

I am sending IDOC from 4.6c to XI to ECC6.0 using IDOC Adapter. I want to ensure that IDOCs are processed serially(EOIO) on the receiver side. I tried setting up the SE16-->IDXQUEUE on XI for the Receiver system and enabled the Queue processing flag on the Receiver communication channel, but the IDOCs are not serialized.
I see that XI is using XBTO_007(EO) Queue. It should be using the queue that I specified in SE16.Please let me know what else needs to be done to implement EOIO for the IDOC adapter.
Please note Sender is 4.6c System while the receiver is ECC 6.0 on WAS>=6.2
Thanks in advance.
Rajeev Gupta

Rajeev,
From http://help.sap.com/saphelp_nw70/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
The receiver or sender system must be based on SAP Web Application Server 6.40 or higher.
The blog listed above is when you need to sends Idoc from R3 to XI in EOIO. It does not work with SAP R3 4.6C for the reason above.
For sending Idoc's from XI to R3 ( to ECC in your case ) in EOIO, you need to seelct Queue Processing in the Receiver Idoc adapter and the rest I think is handled implicitly by XI.
Regards
Bhavesh
PS: Have not tried this practically though!
Message was edited by:
Bhavesh Kantilal

Send IDOC Messages In Order to XI

Hi,
I am using Job Scheduling for sending the list of Vendors(CREMAS IDOCs) to SAP XI from SAP R/3.
I am generating a unique ID for each vendor received. Just because all the messages reach XI at the same time, I am getting the same ID for many Vendors.
I am using Mapping Look up to get the maximum ID. I am then adding one to the maximum number and generating the new ID.
Is there any way to solve this problem?
I would like to know if I can process the messages one after the other to solve this issue.
Regards,
Venkatesh

hi,
2 ways:
1. send IDOCs in queue (possible only is your ERP is on WAS 6.40 or more)
2. use table IDXQUEUE to queue them inside XI
both approaches described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

IDOC TO XI WITH DEDICATED QUEUE HAS STATUS 30

Hi, i have an interface IDOC to XI to JDBC, it has implemented a dedicated Queue, it dosnt have configured the acknowledge.
it was working fine, then we implemented the dedicated queue, it works fine a cuple of thays but then the idocs start to have all status 30. (note: i have configured output mode 2)
SM59 config image:
<a href="http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG">[IMG]http://img144.imagevenue.com/loc991/th_95044_SM59_122_991lo.JPG[/IMG]</a>
or:
<a href="http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG">[img=http://img144.imagevenue.com/loc991/th_95044_SM59_122_991lo.JPG]</a>
WE20 config image:
<a href="http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG">[IMG]http://img169.imagevenue.com/loc768/th_95050_WE20_122_768lo.JPG[/IMG]</a>
or:
<a href="http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG">[img=http://img169.imagevenue.com/loc768/th_95050_WE20_122_768lo.JPG]</a>
Table IDXQUEUE in XI SE16 image:
<a href="http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG">[IMG]http://img140.imagevenue.com/loc850/th_95050_XI_SE16_IDXQUEUE_122_850lo.JPG[/IMG]</a>
or:
<a href="http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG">[img=http://img140.imagevenue.com/loc850/th_95050_XI_SE16_IDXQUEUE_122_850lo.JPG]</a>
Function module in SE80 image:
<a href="http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG">[IMG]
http://img41.imagevenue.com/loc768/th_95052_SE80_FM_122_768lo.JPG[/IMG]</a>
or:
<a href="http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG">[img=http://img41.imagevenue.com/loc768/th_95052_SE80_FM_122_768lo.JPG]</a>
First message that came out by de dedicated queue image:
<a href="http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG">[IMG]http://img179.imagevenue.com/loc193/th_95057_first_message_122_193lo.JPG[/IMG]</a>
or:
<a href="http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG">[img=http://img179.imagevenue.com/loc193/th_95057_first_message_122_193lo.JPG]</a>
Last message that came out by de dedicated queue image:
<a href="http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG">[IMG]http://img192.imagevenue.com/loc343/th_96230_last_message_ok_122_343lo.JPG[/IMG]</a>
or:
<a href="http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG">[img=http://img192.imagevenue.com/loc343/th_96230_last_message_ok_122_343lo.JPG]</a>
BD87 from the day that everything work fine to today image:
<a href="http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG">[IMG]http://img178.imagevenue.com/loc90/th_96306_bd87_122_90lo.JPG[/IMG]</a>
or:
<a href="http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG">[img=http://img178.imagevenue.com/loc90/th_96306_bd87_122_90lo.JPG]</a>
Anyone has an idea why is this? I have allready tried the report and TRX to process the idocs with status 30 and it didnt work.
Thanks.
Regards.
Mariano Billinghurst

Sorry i have posted wrong the images, here it goes again...
Hi, i have an interface IDOC to XI to JDBC, it has implemented a dedicated Queue, it dosnt have configured the acknowledge.
it was working fine, then we implemented the dedicated queue, it works fine a cuple of thays but then the idocs start to have all status 30. (note: i have configured output mode 2)
SM59 config image:
http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG
WE20 config image:
http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG
Table IDXQUEUE in XI SE16 image:
http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG
Function module in SE80 image:
http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG
First message that came out by de dedicated queue image:
http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG
Last message that came out by de dedicated queue image:
http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG
BD87 from the day that everything work fine to today image:
http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG
Anyone has an idea why is this? I have allready tried the report and TRX to process the idocs with status 30 and it didnt work.
Thanks.
Regards.
Mariano Billinghurst

Processing in Idoc

Hi
I have a Scenario.
Loop at idoc records.
Step 1: Thru User Exit Before Posting I Called a BAPI but did not Commit.
Step 2.Idoc is proccessed.
 If Idoc _status = successfull
 Will My BAPI will commit Automatically ?
Endloop.
Let me know wether my BAPI will commit automatically without BAPI_TRANSACTION_COMMIT ?
Bala.M
Moderator message: vague subject, wrong forum, please try yourself before asking others.
locked by: Thomas Zloch on Aug 6, 2010 2:15 PM

Hi Anshul,
We opted to go for IDOC Serialisation. With this, we achieved the sequential data processing through the PI interface.
I did check a blog in SDN which had step by step instruction to achieve this, but cannot find it now
Anyways, will give you a idea on wat needs to be done at PI and SAP R/3 end.
At PI end:
Using SE16 as the transaction, We need to create a entry in the table: IDXQUEUE
 a.PORT - (SAP R/3 system port)
 b.CLIENT - (SAP R/3 system client)
 c.MESTYP - (IDoc MSGTYP)
 d.QUEUEID - (Random Queuename, for eg: EOIO_PI_Interface)
At SAP R/3 end:
1. Create a function module. The QUEUEID created in SAP PI should be mentioned in this function module. <this basically indicates which PI queue will handle this message>
2. Using transaction we85, create a queue processing rule (which would call the function module)
3. In the partner profile, for the particular Idoc type, queue processing option must be enabled. And the queue processing rule (as defined in step 2 above) should be specified here.
Hope this information helps.
When I find the link to the blog, will post it here.
Thnx,
Prajeet

Determination of QOS for IDOC messages

Hi,
sending IDOC from SAP to XI, and then to an external system using a JDBC adapter, the QOS for messages is automatically set to EO: anyone knows if it's possible to change this parameter (I need EOIO)? Where can I find documentation about setting/changing QOS?
Thanks for any suggestion.
Simona

I had the same scenario as Simona and at the end it turned out to be pretty simple (if WAS >= 6.40). On the sender system (SAP ERP) in partner profiles -> in the outbound parameters for the message type, you need to check Queue Processing parameter. When you do this an aditionalfield will apear: Rule name. This determines which rule will be used as QueueID. Rules are customized in WE85 where you can assign your own function modules to custom rule names.
Once I assigned appropriate rule (for test I used FIRST_16_OF_MESTYP) xml message was automaticaly set to
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
and the message got the QueueID XBQO* (in SXMB_ADMIN).
Again, if WAS is WAS >= 6.40 you don't need to set up IDXQUEUE table.
Regards,
Elvis

IDX2 and Idoc metadata in production system

As explained my Michal & SAP note - 767091, I ran program IDX_GET_CONFIG in production, pointed rfc dest to source where the config is located. It loaded the data but the metadata in the tables are pointing to the XI development (DEV) target system port and not production (PRD)landscape....meaning
XI0 sending data to SAPDEV port
XC0 sending data to SAPTST port
XP0 sending Idoc data to SAPPRD port
Now all my entries in xp0 is pointing to SAPDEV port
How do I fix this. I don't want to create a SAPPRD port in XI0 and load metadata from SAPPRD into Xi0...its would not be SOX complaint.
IDoc Adapter: Configuration Data Transfer
 17 Entries for table IDXSLOAD
 0 Entries for table IDXIDOCINB
 1 Entries for table IDXNOALE
 0 Entries for table IDXQUEUE
 9 Entries for table IDXPORSM59
 492 Entries for table IDXIDOCSYN
Please Help!
 4470 Entries for table IDXEDSAPPL
 636 Entries for table IDXEDISDEF

hi,
just like I said you need to do it manually
I gave you note 767091 just to consider
(the note is for system copy not for DEV-PRD)
also Naveen told you the same
you only need to be careful and read what we write
now just delete IDX1 entries in PRD and create new
manually - just like we said
Regards,
michal

Specify a XI queue for processing ?

Hi,
I would like to specify clearly a queue for a specific outbound Message Interface. For instance :
Queue_1   for all MessageInterface_4
Queue_2   for all MessageInterface_5
Queue_3   for all MessageInterface_6
By this way, I will be sure that all messages of "MessageInterface_4" sent every 10min will be processed by the same Queue "Queue_1".
Thus if a queue is in status "Stopped", that's means that only one interface will be affected.
Note: I use mainly adapter JDBC, IDoc, Abap proxy in Asynchronous mode EOIO.
Note: Another way is perhaps serialization, but I'm not sure that's possible with XML message inside XI.
Thanks
Mickael
P.S: I know well document "How to Priorize XI messages on IS - NW2004S.pdf"

Hi,
As its mentioned in above one of the post
You could arrange the queue for IDOC with
1. Create a function module, which will be used to indicate QueueID for the IDoc type.
2. Import parameters: CONTROL of type EDIDC & Export parameter: NAME of type CHAR16
3. Tables: DATA of type EDID4 In the body of source code, simply specify the QueueID with one line of code.
Note that it must match with the QueueID specified in IDXQUEUE table in your XI system.
For JDBC to be serialized
"Database Transaction Level" Setting as serializable:
Most restrictive isolation level. When it's used, the phantom values cannot occur. It prevents other users from updating or inserting rows into the data set until the transaction will be completed.Phantom behavior occurs when a transaction attempts to select a row that does not exist and a second transaction inserts the row before the first transaction finishes. If the row is inserted, the row appears as a phantom to the first transaction, inconsistently appearing and disappearing.
You need to go through below link also
/people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter
Thanks
Swarup

Sequencing 2 different idocs

Hi,
PI will receive 2 IDOCS at an instant from MDM. 1) MATMAS
                                                                            2) classification IDOC
PI might receive these idocs in any order. But will have to send the MATMAS IDOC first and then the classification IDOC to the ECC system.
any suggestions please... If i can do it through BPM.. kindly give me some links for it.
Rgds,
Mickz

If you are facing a challenge in the MDM system, you can make the necessary changes in PI to achieve this.
Please do the following, as mentioned earlier.
Write the following code in the PI system.
1. Go to SE38 and create a program ZXX_UPDATE_IDXQUEUE.
REPORT z_xi_idd0XXX_quereg NO STANDARD PAGE HEADING.
******* Data Declaration ***************************
CONSTANTS: c_queuid   TYPE sxmsqid VALUE 'ZQUE_DIRDEB'.
DATA: v_sysid        TYPE    syst-sysid,
       v_sysport      TYPE    idx_port,
       v_client       TYPE    edi4mandt,
       v_msgtyp       TYPE    edi4mestyp,
       wa_idxqueue    TYPE    idxqueue,
       v_count        TYPE    int4,
       i_idxqueue     TYPE   STANDARD TABLE OF idxqueue
       INITIAL SIZE 0.
********* End of Data Declaration *******************
********Seleccion Screen Information *****************************
******* End of Selection screen       *****************************
INITIALIZATION.
v_sysid = sy-sysid.
START-OF-SELECTION.
SELECT COUNT(*)
FROM idxqueue
INTO v_count
WHERE mestyp EQ 'PAYEXT' .
IF v_count = 0.
* Dev system
    IF v_sysid EQ 'DXX'.
      wa_idxqueue-port = 'SAPXXX'.
      wa_idxqueue-client = '230'.
      wa_idxqueue-mestyp = 'PAYEXT'.
      wa_idxqueue-queueid = c_queuid.
      APPEND wa_idxqueue TO i_idxqueue.
      CLEAR wa_idxqueue.
* QA system
    ELSEIF v_sysid EQ 'QXX'.
      wa_idxqueue-port = 'SAPXXX'.
      wa_idxqueue-client = '400'.
      wa_idxqueue-mestyp = 'DIRDEB'.
      wa_idxqueue-queueid = c_queuid.
      APPEND wa_idxqueue TO i_idxqueue.
      CLEAR wa_idxqueue.
      wa_idxqueue-port = 'SAPXXX'.
      wa_idxqueue-client = '400'.
      wa_idxqueue-mestyp = 'ZSTIDOCM'.
      wa_idxqueue-queueid = c_queuid.
      APPEND wa_idxqueue TO i_idxqueue.
      CLEAR wa_idxqueue.
* Production
    ELSEIF v_sysid EQ 'PXX'.
      wa_idxqueue-port = 'SAPXXX'.
      wa_idxqueue-client = '230'.
      wa_idxqueue-mestyp = 'DIRDEB'.
      wa_idxqueue-queueid = c_queuid.
      APPEND wa_idxqueue TO i_idxqueue.
      CLEAR wa_idxqueue.
      wa_idxqueue-port = 'SAPXXX'.
      wa_idxqueue-client = '230'.
      wa_idxqueue-mestyp = 'ZSTIDOCM'.
      wa_idxqueue-queueid = c_queuid.
      APPEND wa_idxqueue TO i_idxqueue.
      CLEAR wa_idxqueue.
    ENDIF.
ELSE.
ENDIF.
IF i_idxqueue[] IS INITIAL.
    LOOP AT i_idxqueue INTO wa_idxqueue.
      INSERT idxqueue FROM wa_idxqueue.
      CLEAR wa_idxqueue.
    ENDLOOP.
ENDIF.
END-OF-SELECTION.
DESCRIBE TABLE i_idxqueue LINES v_count.
IF sy-subrc EQ 0.
    WRITE: /10 'Total Entries in Table IDXQUEUE is '(001),
            55 v_count.
ELSE.
    WRITE: /10 v_count LEFT-JUSTIFIED,
            20 'Total Entries could not update Table IDXQUEUE. '(003).
ENDIF.
2. At the end run the program to update the IDXQUEUE table and transport the program to the different landscape. This program should be part of your cutover activity.
Regards,
Indranil

IDXQUEUE

Similar Messages

Maybe you are looking for