Attribute QUEUE_NAME is Initial

Hi All,
My Scenario is Webservices-XI-BW...
While sending data from webservices the response i get is QUEUE_NAME is initial... this i am getting since i am using QOS--EOIO,
I have gone through weblog /people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
but i could not solve my problem....
So can any one let me know how to make this solve...
Regards,
Sridhar Reddy

Sridhar,
Please go through the Note: 856597
and the blog /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
-Naveen.

Similar Messages

Attribute QUEUE_NAME is initial Error

Hallo,
when I´m calling an BAPI over RFC and with QoS=EOIO then the following error occure:
Result:
<SAP:Error>
<SAP:Category>XIServer</SAP:Category>
<SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code>
<SAP:P1>QUEUE_NAME</SAP:P1>
<SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack>
</SAP:Error>
I made the RFC-Destination with the correct SAP-System; must i create a queue for this destination? And when yes how i can do this? I need an outbound-queue - yes?
Thanks in advance,
Frank

Did you register your queues ? Go to SXMB_ADM -> Manage Queues and register your queues. If this does not work, delete the queues and register them again using the same transaction SXMB_ADM -> Manage Queues
regards
SKM

QUEUE_NAME is initial Frank Schmitt cau u give the solution?

Hi Frank,
My Scenario is Webservices-XI-BW...
While sending data from webservices the response i get is QUEUE_NAME is initial... this i am getting since i am using QOS--EOIO,
Can u tell me how u have solved this solution which u posted in sdn long back...
Result:
<SAP:Error>
<SAP:Category>XIServer</SAP:Category>
<SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code>
<SAP:P1>QUEUE_NAME</SAP:P1>
<SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack>
</SAP:Error>
I am also getting same error ...
please can u let me know how u have solved this
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

Hi Michael,
Thanks for u r reply,
I am not using Soap Adapter, I am using XI adapter, and followed the Doc how to send XML data to BW using the doc
http://service.sap.com/~sapidb/011000358700011142902001E/HOWTOSENDXMLDATATOBW.DOC
My scenarion is XI-BW integration.
Here I am trying to send XML data as mentioned in the doc.. i can see the messeges if i give the QOS as EO but if i give EOIO then the said response i am getting...
Request u to give solution or suggestion...
Regards,
sridhar

How and When Does the attribute VI_ATTR_VXI_TRIG_STATUS get initialized

How and When Does the attribute VI_ATTR_VXI_TRIG_STATUS get initialized. Do the actual trigger lines get measured or does the attribute get initialized to a default value when the vxi resource manager is executed?

Hey whl6868,
According to page 157 (or 3-135) of the manual (http://www.ni.com/pdf/manuals/370132c.pdf), there is no default value for VI_ATTR_VXI_TRIG_STATUS. If Resman is returning valid values for it, then it must be actually reading the lines. Else, I would only expect it to return valid values when you actually call the function yourself.
Regards,
David R
Applications Engineer
National Instruments

Attribute Manifest is Initial Error

Hi all.
I have a scenario, HTTP To Proxy.
All these days the scenario was working fine in Prod.
Now there was a strange error like below.
Attribute Manifest cid:att-afca9240544511e092426ad000004002(@)sap.com is initial
Error category: Internal (in Moni)
Any s

Implemented the SAP Note: 1501345
Problem resolved.

QUEUE_NAME for outbound

Hallo,
when i have a rfc-destination i need to assign a queue for destination?
Because this error occured by invoking a bapi over plain http-adapter (QoS=EOIO):
Result:
<SAP:Error>
<SAP:Category>XIServer</SAP:Category>
<SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code>
<SAP:P1>QUEUE_NAME</SAP:P1>
<SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack>
</SAP:Error>
Thanks in advance,
Frank

HI,
You need to register the quesues:
IN SXMB_ADM -> Manage Queues and register your queues.
Priyanka

Lenght of ds string

Folks,
We are trying to store xml documents in LDAP. What is the sizelimit? We can load a 2mb file but nothing larger.
thanks,
keith

Hi Frank,
Can u tell me how u have solved this solution which u posted in sdn long back...
Hallo,
when i have a rfc-destination i need to assign a queue for destination?
Because this error occured by invoking a bapi over plain http-adapter (QoS=EOIO):
Result:
<SAP:Error>
<SAP:Category>XIServer</SAP:Category>
<SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code>
<SAP:P1>QUEUE_NAME</SAP:P1>
<SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack>
</SAP:Error>

I am also getting same error ...
please can u let me know how u have solved this
Regards,
Sridhar

QueueId for HTTP Sender Adapter.

Hi All:
I modified the HTTP client and sending QoS = EOIO and queueid=test_queue. But I am getting an Error :
Result:
<SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code><SAP:P1>QUEUE_NAME</SAP:P1><SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack></SAP:Error>
Can any one tell me what is the cause of this Error
Thanks
Farooq.

Double check the URL:
... &QOS=EOIO&queueid=test_queue ...
Stefan

HTTP Queue

Hi All,
I have Http to JDBC scenario in which I need to send the messages EOIO.
For this I need a queue.In Http client I set the QoS : EOIO .But I need to give a 'queueid' to make use it.
Plz any one knows how to create,Register and Acitvate the Queues.
Thanks
Praveen Kumar

I updated the HTTP client on the sender side, added the parameter queueid to the URL string and assign it with some name.
Queue has created with the respective name assigned to the queueid.The corresponding XML schema will be passed through the same queue.
But am getting the following error while sending through HTTP client:
Result:
<SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>INTERNAL.ATTRIBUTE_INITIAL</SAP:Code><SAP:P1>QUEUE_NAME</SAP:P1><SAP:Stack>Attribute QUEUE_NAME is initial</SAP:Stack></SAP:Error>
Any clue on this error?
Thanks
Praveen Kumar

Problem with setting custom attribute and it being searchable

I'm having an issue with setting a custom attribute and having it be searchable using Portal 10.1.4. The situation that we have is that we initially added a bunch of files to Oracle Portal using webdrive. Later on, we decided that we needed another custom attribute called "Pinned Item" that will be used for searching (boolean value) and gave it a default value of false. The attribute was then added to the "File" item type in the "Shared Objects" group.
It appears that since this attribute wasn't initially available on the file object, we couldn't search on it so we decided to set it programatically. First, I tried using wwsbr.set_attribute but it errored out seemingly because the value wasn't set in the first place. If I set a value first by using the web front end, I could then use the set_attribute procedure.
So, I moved on to using wwsbr_api.modify_item and it appears to set it (although everything is being set to false until I changed it to "text" instead of "boolean" which is OK because that's what I wanted anyway... see metalink bug 390618.1). I'm using the method outlined in metalink doc 413079.1. When I do set it to a "1", and edit the item the check box is checked indicating that it is set correctly. And if I just click "OK" to save the attributes after I open it everything works like it should.
However, the advanced search (and custom search portlet) and the search APIs are not picking it up. I'm not sure if I'm hitting Metalink bug ID 5592472 or not as that's using the "set_attribute" procedure instead of the modify_item procedure. And their "workaround" of setting the attribute in the UI isn't really feasible for a couple thousand files.
So far I've tried the following things to get it working:
1. I am calling wwpro_api_invalidation.execute_cache_invalidation
2. I have executed wwv_context.sync
3. I cleared the page group cache
4. I invalidated all of the web cache
Does anyone else have any other suggestions?

I'm having an issue with setting a custom attribute and having it be searchable using Portal 10.1.4. The situation that we have is that we initially added a bunch of files to Oracle Portal using webdrive. Later on, we decided that we needed another custom attribute called "Pinned Item" that will be used for searching (boolean value) and gave it a default value of false. The attribute was then added to the "File" item type in the "Shared Objects" group.
It appears that since this attribute wasn't initially available on the file object, we couldn't search on it so we decided to set it programatically. First, I tried using wwsbr.set_attribute but it errored out seemingly because the value wasn't set in the first place. If I set a value first by using the web front end, I could then use the set_attribute procedure.
So, I moved on to using wwsbr_api.modify_item and it appears to set it (although everything is being set to false until I changed it to "text" instead of "boolean" which is OK because that's what I wanted anyway... see metalink bug 390618.1). I'm using the method outlined in metalink doc 413079.1. When I do set it to a "1", and edit the item the check box is checked indicating that it is set correctly. And if I just click "OK" to save the attributes after I open it everything works like it should.
However, the advanced search (and custom search portlet) and the search APIs are not picking it up. I'm not sure if I'm hitting Metalink bug ID 5592472 or not as that's using the "set_attribute" procedure instead of the modify_item procedure. And their "workaround" of setting the attribute in the UI isn't really feasible for a couple thousand files.
So far I've tried the following things to get it working:
1. I am calling wwpro_api_invalidation.execute_cache_invalidation
2. I have executed wwv_context.sync
3. I cleared the page group cache
4. I invalidated all of the web cache
Does anyone else have any other suggestions?

Custom Field no longer works as an attribute since upgrade from 5.2 to 5.3

We have just upgrade from CUP 5.2 to CUP 5.3 SP8.1 and it seems that the custom field that could be used in 5.2 as an attribute in the logic used to control initiators no longer works as an attribute in 5.3. The initiators that are now configured with the custom field still work but when we try to change or create a new one it errors saying that the custom field is not an attribute and stops me from including it to use as a flag. I looked in the attribute tabs list and the custom field is not listed but it still show in the drop down list in the change initiator screen select attributes selection.
Has anyone else seen this and if so do you know how to allow us to use a custom field as an attribute in the initiator select attributes screen.

Hello Clark,
try to change the "applicable to" option in custom field configuration to initiator.
Best regards,
Bianca

Queue Name is Initial while calling XI through webservice

Hi All,
While i am sending data to XIServer through webservice with Quality of service as EOIO i am getting the response
XIServerINTERNAL.ATTRIBUTE_INITIALQUEUE_NAMEAttribute QUEUE_NAME is initial
Due to this i cannot see any messages in SXMB_mONI..
Can anybody give solution or suggestions...
And also CCMS status is in red in component monitoring of Adapter engine for XISERVER...
Thanks and regards,
Sridhar

Hi Michael,
Thanks for u r reply,
I am not using Soap Adapter, I am using XI adapter, and followed the Doc how to send XML data to BW using the doc
http://service.sap.com/~sapidb/011000358700011142902001E/HOWTOSENDXMLDATATOBW.DOC
My scenarion is XI-BW integration.
Here I am trying to send XML data as mentioned in the doc.. i can see the messeges if i give the QOS as EO but if i give EOIO then the said response i am getting...
Request u to give solution or suggestion...
Regards,
sridhar

Difference Between Attribute Tab and Role Attribute Option

Hi Experts,
What is the relation between option custom fields and sub-option attribute under option roles in CUP> config.
I am asking this because, i have created a workflow based on functional area and now i am getting two functional area options in CAD(select attribute) and in initiator.I know, from where they are coming from....
1.Custom field>functional area.
2.Roles>Attributes>functional area.
Under both options different values are maintained for functional areas,for e.g.AP and AR in first and Bank and Asset in the other one.
The strange thing to me is that i am able to view only values maintained in Custom field>functional area while creating a test request no value is coming from Roles>Attributes>functional area.
However, while selecting role(option selct role), initially creating request, i can see the values maintained under functional area(coming from Roles>Attributes>functional area)
Regards,
Mukesh

Mukesh,
In simple words, there is no relationship between custom fields and role attributes.
Function area under role attribute is referred as "Functional Area of Role" in CUP. The other functional area refers to the "functional area of the user". In a company, both these functional areas can be similar or different as an user from "AP" can have roles from "AP" as well as "FI".
When you are creating CAD, do not select functional area of role and you would not see the attribute values from role FA.
I hope this helps you.
Regards,
Alpesh

IdM v7 and User Extended Attributes

I did a demo install of IdM version 7.1 and when I looked under debug and then list 'Configuration' objects,
I did not see 'User Extended Attributes' ?
I thought this comes as part of IdM in a very basic simple format ?
I've worked with IdM a fair amount, and don't every remember creating this file.
Can someone confirm this ( one way or the other ) ?
TIA

The "IDM Schema Configuration" object is an IDM 8+ object only. The extended attributes have been completely changed between IDM 7 and IDM 8.
In IDM 7.1 the extended attributes are stored in the Configuration object called "User Extended Attributes". The initial import and set up of your repository should have created it. By default there's a few extended attributes (like idmManager, etc) that are set up. On a fresh install you won't find the file in the sample directory. It's only in the repository. You should be able to see it from the debug page or by extracting the XML object from the repository directly using the lh command line tool. If not then something might have screwed up in the installation.
However, the fact that you've got attributes called "IDMAttributeConfiguration" and "IDMObjectClassConfigurations" leads me to believe you've actually got an IDM 8 install, not an IDM 7 install. In which case, as Paul pointed out, your attributes are stored in the "IDM Schema Configuration" object. (Again, not found in the sample dir, only in the repository and is created on initial import.)

Problem with "pdfSource" attribute in Adobeform scenario

Hello,
Scenario:
I am calling an interactive form from my webdynpro application , wherein the user enters many details and finally presses on Submit.
In the OnSubmit method , I validate the data and send email with my form as attachment.
To make this attachment , I use the "pdfSource" attribute to get the latest form data . But this attribute has the initial form data sent and no updated one.
I checked the SAP note 1120324 & corrections 967024 , 967025 .. which is same as the problem I am facing.
But these are already in place.
Kindly help in this.
Thanks in advance,
Omkar Mirvankar

Hi Omkar,
Here you go..
*@# PDF Creation data.
data :lv_xml type xstring,
                lv_adobe type ref to cl_wd_adobe_services,
                lv_pdf type xstring.
*@#End PDF.
*Create PDF on Submit.
                create object lv_adobe
                  exporting
                    i_form_name = 'your form name'.
                lv_xml = lv_adobe->get_wd_context_as_xml( data_source = lo_nd_nodename ).
                lv_pdf = lv_adobe->create_pdf( enabled = 'X' data_source = lo_nd_nodename data_xml = lv_xml ).
*@#End PDF creation.
you can use lv_pdf for your rest of the process...
Regards,
Ravi.D

Attribute QUEUE_NAME is Initial

Similar Messages

Maybe you are looking for