Bursting: Could not determine recipient - Bex broadcaster

Hi experts, i have this error in bex broadcaster for an workbook:
Bursting: Could not determine recipient
when use the bursting.
The error appear when use this option:
Generate Document with Variable Value -- Name of variable
Attribute for Recipient Determination - Attribute that contain email address.
Could you help me?
Thanks a lot.
Regards.
Andrea

Hi,
May useful to you:-------
/people/ramkumar.ghattamaneni/blog/2008/02/25/using-variables-while-broadcasting-queries-to-the-portal-in-bi-7
Regards,
Suman

Similar Messages

Broadcast Setting - Bursting : Could not determine recipient

Hello,
I created broadcast setting for template using option bursting.
Template is broadcasted by district (attribute of 0plant).
Here is the option for broadcasting.
Chracteristic for receipient determination : Generate Document with Variable Value
            Variable : District
Selection of the Characteristic Values : By Following Selection
It had worked sucessfully for several months, by now from time to time ,
I would say 60% of broadcastings ended with error: Bursting: Could not determine recipient
When I run broadcast setting the second time , it's always ended sucessfully, and send templates to districts.
Could you please advise how to fix this.
I can not imagine what could cause this strange behavior,
so I'll be very appreciated for any help.
Thanks in advance,
Alena Yershova

can you install http watch on you internet explorer and run it and it will show you where its holdin gup.. or i am not sure if you can broadcasting from back end system..

Broadcast email - Bursting: Could not determine recipient

Hi,
I created a broadcast setting for email-bursting and checked it/saved it/scehduled it successfully.
The broadcast setting is trying to burst a runtime statistcis query by user (infoobject 0TCTUSERNM for users is contained in the query). The characteristic for receipient determination is "0TCTUSERNM" and the attribute is "person responsible" with attribute value being set to "user name"
However upon executing this setting I get the following error :
Bursting: Could not determine recipient with a yellow light against this error message and the bursting email is never sent-out.
can someone please advise the remedy for this problem
regards
Kulmohan

Hi Simon,
No, I donot have any person allocated to the blank entry for the characteristic being used for bursting
Can you please advise What I would need to do for this?
regards,
Kulmohan

APEX SSO and Load balancing: Could not determine workspace for application

We had a single HTTP Server serving APEX in a 10.2.0.2 database configured with SSO to be used by the developers. APEX has been registered as a partner application and the login url has been CA Siteminder protected so that the SM_USER details are forwarded in the header for the application to use for authorization. Everything is fine so far.
Now we have added a HTTP Server on another host and have it all set up for APEX and its pointing to the same database. APEX_ADMIN access works as normal, but applications previously using SSO now get the following error after entering the URL.
Expecting p_company or wwv_flow_company cookie to contain security group id of application owner.
Error ERR-7620 Could not determine workspace for application ().
Using HTTP Watch I find that the application is not even trying to redirect to the login page.
What is wrong here?

APEX has been registered as a partner application as described in
http://www.oracle.com/technology/products/database/application_express/howtos/sso_partner_app.html
In the meantime I found metalink document 368746.1 which describes the cause of this problem. Please read carefully what I wrote, it all works when the the new APEX web server is turned off in the server farm on the load balancer and directed through the original web server. When running regapp.sql the hostname in the listener token was using the virtual hostname. This works fine if the request comes from the original APEX server which proofs that there is nothing wrong with the installation and set up of SSO. When directing the request to the new APEX web server the APEX_ADMIN page still works only existing work spaces using SSO don't seems to work anymore resulting in a error as described in the subject.
As for metalink document 368746.1 naming the causes of this error:
- there are no duplicate entries in WWSEC_ENABLER_CONFIG_INFO$
-LISTENER_TOKEN clearly works for requests coming from the first web server
-theoretically the web server listener port could be changed from 7777, but port 80 needs to be maintained here as production is mimiced as far down as possible.
Is there some cache table which can be cleared? How is it that the flows schema (apex engine) can not find the work space when the request comes from a new web server which can however access the APEX_ADMIN pages.
anyone?

Abort Could not determine a value for variable 0DAT from the authorizations

Hi All,
I encountered an error '/ Abort Could not determine a value for variable 0DAT from the authorizations\' when executing my query on a multiprovider in BW 3.5.
Can anyone help me in finding a solutionn to this issue.
Thanks,
Kartik.

Hi Kartik,
I am sorry as that note is for NW2004s. Please check if 0DAT variable installed from a business content? if not then I think thats the cause of the problem.
Hope this helps,
Bye...

Could not determine value for variable 0P_FVAEX (or 0P_CTPCA)

I get the below error while accessing a query on the planning Info Cube. I used the SAP Exit variable Most Current Data (Transactional InfoCube) (0S_RQTRA) in the query for the Characteristic - Request ID (0REQUID) to extract the data from the yellow request too.
I do not use the below variables as in the below eror in my query at all. Please assist.
Diagnosis
This error diagnosis is specific only to the variables 0P_FVAEX or 0P_CTPCA !
Termination message BRAIN 632 appears:
Could not determine value for variable 0P_FVAEX (or 0P_CTPCA).
System Response
1. Operation method of SAP-Exit-Variables 0P_FVAEX or 0P_CTPCA
With queries from the CO application, both SAP-Exit-Variables look for an entry for 'controlling area'. With this controlling area from the selection screen, the SAP-Exit-Variables program reads the attributes for InfoObject 0CO_AREA (controlling area).
With queries from the FI application, the SAP Exit Variable 0P_FVAEX looks for an entry for 'company code'. With this company code from the selection screen, the SAP Exit Variables program reads the attributes for InfoObject 0COMP_CODE (Company Code).
0P_FVAEX determines the fiscal year variant (attribute 0FISCVARNT) from the attributes for 0CO_AREA (CO queries) or 0COMP_CODE (FI queries). 0P_CTPCA determines the currency type of the profit center local currency (attribute 0CURTP_PCA) from the attributes for 0CO_AREA.

Hello,
you need to take a closer look at your query. Somewhere you used one of the 0P_* exit variables, which work only for controlling related InfoCubes. Use your own variables.
Regards,
Marc
SAP NetWeaver RIG

Could not determine BW release of logical system 'BWPCLNT100

after a BI systemcopy (production to development) we get the following
error when we run load jobs of type "delta load". full loads work fine
"Could not determine BW release of logical system 'BWPCLNT100'"
even if i start the deltaload from the R/3 system with transaction RSA3
with update mode "C" i get the same error . when i use update mode "F"
it works fine , but that's not the thing we want.
BWPCLNT100 is the logical system of the productive system .
we have changed all the logical system setting to BWDCLNT100 using
transaction BDLS and we have also changed all entries in RSBASIDOC,
RSISOSMAP, RSOSFIELDMAP,.... .
we have done several systemcopies in the past , they all worked fine
and without this error. this is the first copy in BI 7.00 .
are there any loadmodules which have to be regenerated with the new logical system name?
thank you for your help and kind regards hannes toefferl

Hi,
As you said you are getting error after system copy when you are doing the delta load and full load is working fine for you.
This mainly happens due to init disturbance in the source system.
I would suggest you to delete the init and rerun the Init from BW once again.
This should solve your problem.
Thanks
Mayank

Error in ALE service 29 Could not determine recipients for message type MAT

Hi Experts,
While transferring the material using ALE am getting error 29 ie 'Error in ALE service' and message is 'Could not determine recipients for message type MATFET'.
Also i ve recieved the materials with the proper status al the end am getting the above error.
Kindly help me out.
Thanks in advance.

Hi ,
Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly in WE20 in sender system.
Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
Regards
Vikas Chaudhary

The system could not determin a business area for item 00010

i m getting bellow message while entering stock (MB1C)....
No business area can be deermined for item 000010
Diagnosis : The System could not determine a business area for imte 000010. The item has plant (G001) 7 is assigned to company N001 for which a business area is required. This is caused by incomplete setting in customizing.
Procedure : Before creating the item make sure that you have completely maintened business area assignment in customizing

hi Kartik
Please check whether your company is opted for " business area financial statments" in financial account- global setting of company code. If yes and you want to continue please maintain business area for the plant and material dvision combination under the transaction cde OVF0.
Hope this will solve your problem.

Error in CK11n - The system could not determine a cost component split for

Hi All,
When i run CK11n i have following error:
The system could not determine a cost component split for the internal activity with activity type 502000 of cost center 10100.
Procedure
Check the master data for activity type 502000 of cost center 10100. It is possible that no activity price calculation has been carried out for the cost center.
could any one give me solution
Thanking you.

Well, did you run activity price calculation for the relevant cost center(s)?
The CCS you're using for product costing (either your COGM split, or the auxillary) has been marked as a "primary" cost component split. It wants to break secondary costs down into their cost components, and assign those components to components in its own structure.
Wihout a planned CCS for the activity, this isn't possible. (This is normally calculated by KSPI during planning.)
Either calculate an activity CCS is KSPI, assuming that all the prerequisites are in place for that, or uncheck the "primary cost component split" indicator in your costing variant configuration.

Error: ATTRIBUTE_IDOC_RUNTIME FM NLS_GET_LANGU_CP_TAB: Could not determine

Hi All
Production issue
Scenario is: File to IDOC
From 2 days our R3 production server was down. Before R3 went down i didn't stop my Sender File Communication Channels and XI was continuously accepting files to process it and then trying to post it into R3. Now I can see around 500 messages are failed into SXMB_MONI with error "ATTRIBUTE_IDOC_RUNTIME
FM NLS_GET_LANGU_CP_TAB: Could not determine code page with REP_00_301 Operation successfully executed FM NLS_GET_LANGU_CP_TAB".
Now R3 is working fine and IDOCs are successfully getting posted.
Before telling my issue i want to share one information that in Message Mapping i have implemented a concept of duplicate file handling due to this duplicate file cannot be processed again.
Now my issue is: I am trying to restart the failed messages. So, whenever i am trying to do so my request mesasge maaping is called again and it is showing a error of "Duplicate file". So how can i reprocess my failed messages????
Regards
Dheeraj Kumar
Edited by: Dheeraj Kumar on Jul 14, 2010 3:55 PM

Hi Prasanna
I am maintaining the file names in the table and that table is maintained in XI. Through UDF i am sending a query to check whether that file name exist or not if exist then it is duplicate file otherwise it will process normally.
In production environment I cant delete the entry of file name as it is disabled.
Regards
Dheeraj Kumar

Installing Oracle RAC problem: Could not determine /tmp mount point

Folks,
Hello. I am installing Oracle 11gR2 RAC using 2 Virtual Machines (rac1 and rac2 whose OS are Oracle Linux 5.6) in VMPlayer and according to the tutorial
http://appsdbaworkshop.blogspot.com/2011/10/11gr2-rac-on-linux-56-using-vmware.html
I am installing Grid infrastructure. I am on step 7 of 10 (verify Grid installation enviroment) and get this error:
"Free Space: Rac2: /tmp"
Cause: Could not determine mount point for location specified.
Action: Ensure location specified is available.
Expected value: n/a
Actual value: n/a
I have checked the free space using the command:
[root@Rac2 /]# df -k /tmp
Output:
Filesystem 1k-blocks used Available Use% Mounted on
/dev/sda1 30470144 7826952 21070432 28% /
As you see above, the free space is enough, but could not determine mount point for /tmp.
Do any folks understand how to determine the mount point for directory /tmp ?
Thanks.

Folks,
Hello. I have found the file ./bash_profile under /home/ora11g/ and the file is invisible. However, I edit the file using the command:
[ora11g@Rac2 ~]$ vi /home/ora11g/.bash_profile
I add the 2 lines into the file as below:
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR
I save the file .bash_profile and reboot Oracle Linux 5.6 and check again on step 7 of 10 in the Installer, but the problem is still not solved.
Can any folk help to solve the strange problem "could not determine mount point for /tmp" ?
Thanks.

DB Tab RFCDES: Could not determine code page

Hello,
I have a simple scenario File->XI->IDOC(orders05)
The R/3 who receive the IDOC is an 46c system. When sending a file to the XI I receive the following error message in sxmb_moni on the last step "Call Adapter"
DB Tab RFCDES: Could not determine code page with <myr3>
Does anyone have an idea whats wrong ?
Regards Bernd

Hi Bernd,
did you have a look at SAP notes for idoc adapter code page problems? : 747322, 804570
Regards,
michal

Httpd: Could not determine the server's fully qualified domain name, using

Hello, I am checking why the response time of the display of the pages of the sites are slow, then I checked the error_log file in /var/log/httpd and I got this texts: (I am hosting 3 sites in the server)
[Mon May 14 21:21:37 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
Processing config directory: /etc/httpd/sites/*.conf
Processing config file: /etc/httpd/sites/000010.129.0.37_80avepublishing.com.conf
Processing config file: /etc/httpd/sites/000110.129.0.37_80escuelamovil.com.conf
Processing config file: /etc/httpd/sites/000210.129.0.37_80sabiduria.com.mx.conf
Processing config file: /etc/httpd/sites/0003any_80default.conf
Processing config file: /etc/httpd/sites/virtualhostglobal.conf
[Mon May 14 21:21:37 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Mon May 14 21:21:38 2007] [notice] Apache/1.3.33 (Darwin) mod_jk/1.2.6 DAV/1.0.3 mod_ssl/2.8.24 OpenSSL/0.9.7l PHP/4.4.4 configured -- resuming normal operations
[Mon May 14 21:21:38 2007] [notice] Accept mutex: flock (Default: flock)
[Mon May 14 22:12:18 2007] [error] [client 10.129.0.37] File does not exist: /Library/WebServer/Documentsescuelamovil/robots.txt
[Mon May 14 22:12:18 2007] [error] [client 10.129.0.37] File does not exist: /Library/WebServer/Documentsescuelamovil/error.html
with the alert:
[Mon May 14 21:21:37 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
the virtual host file (virtualhostglobal.conf) is:
# This file is auto-generated by the Server Admin Web
# backend plugin whenever settings are saved.
# The Listen and NameVirtualHost directives are generated
# based on the VirtualHost directive inside
# each site configuration file found in this directory.
# Please add appropriate Listen and NameVirtualHost directives
# if a site is manually edited
# i.e. the site is moved from sites to sites_disabled (or vice versa)
# or the site's Virtual Host ip address and/or port is modified
# Last updated at 2007-05-07 14:22:34 -0500
Listen 10.129.0.37:16080
NameVirtualHost 10.129.0.37:16080
Listen *:16080
NameVirtualHost *:16080
how can I correct this alert?
thanks
Dual 2 GHz PowerPC G5 Mac OS X (10.4.9) 4GB DDR SDRAM, MAC OS X Server
Dual 2 GHz PowerPC G5 Mac OS X (10.4.9) 4GB DDR SDRAM, MAC OS X Server

>how can I correct this alert?
Fix your DNS.
This non-fatal error is Apache's way of telling you that it can't work out the hostname of the machine it's running on.
It uses reverse DNS to determine this information. If you don't have a reverse DNS entry for your server's IP address, this is what you get.
Fix your DNS and the alert will go away, or just ignore it.

"Could not determine code page" inbound side error

Guys,
We are receiving a flat text file and sending an IDoc, but now I'm getting this error.
Any idea what's wrong?
And what is that "I::000" in the message?
Any help is much appreciated.
Thanks a lot,
Viktor
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page
with TABWDV100 I::000 FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not
determine code page with TABWDV100 I::000
FM LS_GET_LANGU_CP_TAB</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
PS:By the way, super sorry if this is a duplicate, my first post didn't show up,
not sure what I messed up...

Hi All,
I have a similar problem, But with a small variation in the Log.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER"><b>ATTRIBUTE_IDOC_RUNTIME</b></SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with PSRCLNT310 I::000 FM NLS_GET_LANGU_CP_TAB</SAP:P1>
<SAP:P2 />
<SAP:P3 />
It says the "ATTRIBUTE_IDOC_RUNTIME", And I have checked all possible related threads and made my settings in synch. Did anyone had a similar problem?

Bursting: Could not determine recipient - Bex broadcaster

Similar Messages

Maybe you are looking for