Child pages
  • Checklist for issues during execution of Broadcaster-Setting
Skip to end of metadata
Go to start of metadata

This page describes solutions to all issues known to SAP during the execution of BEx Broadcaster Settings.

For any broadcasting issues which occur during creation please review wikipage: Checklist for issues during creation and editing of Broadcaster-Setting

General Information

G1 - Broadcast Setting execution

There are two ways to execute broadcast settings:

A - Background Execution:

  • process chain 

  • background job execution 

B - Online Execution User:

  • BEx Broadcaster >broadcast setting > 'Execute' button   

  • Tx RSRD_START > broadcast setting entered > activate flag 'Online Execution' > 'Execute' button

  • broadcast_setting_authorization_user

G2 - Definition of users involved in broadcasting scenarios

In Broadcasting different users are involved: 

G2.1 - broadcast_setting_creator:

  • Where to find:
    • in BEx Broadcaster: Open the object which wants to be broadcast. Find column OWNER in the 1st table 'Settings <object>' (where you can find all existing broadcast settings).
    • in table RSRD_SETTING: column OWNER 
  • Needs authorization to 'send emails' and/or 'send to portal'
  • The setting OWNER is always the email sender, also in the case of using a different authorization user or flag 'user specific'. Please review KBA  2011832 .

G2.2 - broadcast_setting_authorization_user:

  • Where to find: 
    • in broadcast setting user-interface: field 'Authorization User'
    • in table RSRD_SETT_NODE_A, column ID = DI_AUTH_USER  
  • User is available/working/valid in the ABAP and JAVA stack.
  • User needs authorization to execute the broadcasting object (query/webtemplate/workbook/view).
  • RSRD_START + flag online / Broadcaster Execute-button > current logged on user is used (not the broadcasting authorization user)

G2.3 - broadcast_setting_user_specific_users: 

  • Flag 'User-specific' is switched on: Table RSRD_SETT_NODE_A, column ID = DI_USER_SPECIFIC, value = X
  • Where to find:
    • in broadcast setting fields:
      • 'User' > users
      • 'User in Role' > roles  
    • in table RSRD_SETT_NODE_A
      • column ID = DI_BW_USER > users   
      • column ID = DI_BW_ROLE > roles

G.2.4 -  background_user for background execution:

  • Where to find:
    • In Tx RSRD_LOG: see 1st row of log:
      03.06.2014  10:14:09  <background_user> - 00000000000000471708

Please find following screenshots from 'BEx Broadcaster TAB Recipient(s)' , table RSRD_SETTING and table RSRD_SETT_NODE_A for better identification of involved users:

G2.5 - JOB Creation and users

  • Once the broadcast setting is scheduled in background a process with the OWNER of the broadcast setting is created (with name SE+name of the broadcast setting).
  • Then it is time to run, it will create another process with name BIBCAST* that will run with the Authorization User (see note 1877255).
  • The email is sent always with the OWNER of the broadcast setting.

G3 - Using Bookmarks

  • When you create a broadcast setting using a bookmark there are certain limitations.
  • The bookmark is a static view of the query at a moment of the time.
  • Any change in the underlying object could make the bookmark unusable.

In case the underlying object was changed the recommendation is to recreate the broadcast setting so that a new/valid bookmark is used.

  • How to identify that broadcast setting was created for a bookmark?
    • In table RSRD_SETT_NODE_A enter the technical name of the broadcast setting into field< SETTING_ID> to select all setting details.
    • If you find a row with <ID> = PR_BOOKMARK_ID then the broadcast setting processes the bookmark which you find in <value> field.
    • In table RSRD_SETTING you can find the timestamp of creation (field <CREATED>).

G4 - Broadcasting via Process Chains

  • Use report RSRD_BROADCAST_BATCH instead of RSRD_BROADCAST_STARTER (See note 1729678).
  • Please use Tx SE38 to maintain a variant for RSRD_BROADCAST_BATCH. You can add multiple broadcast settings in one variant using report RSRD_BROADCAST_BATCH. RSRD_BROADCAST_BATCH has a inbuilt mechanism for controlled execution of broadcaster setting in parallel. The number of parallelisms is defined in Tx RSBATCH.
  • You can execute report RSRD_BROADCAST_BATCH directly in se38 or use it in Process chain or as Background Job.
  • Do not execute more than one RSRD_BROADCAST_BATCH in BW at a time.
  • Use maximum ONE RSRD_BROADCAST_BATCH in ONE process chain.
  • Process type Event Data Change can be used in Process chain. See Online-Documentation: Including Event Data Changes in Process Chains
  • Until such process chain is completed, avoid execution of any broadcaster setting via other methods (eg timepoint, Trigger Event Data Change, defined background jobs at predefined times etc.).


S1 - Broadcasting errors in Tx RSRD_LOG

S1.1 - Error: "Java system error: call of FM RSRD_X_PRODUCE_PROXY to ProgId ... on host ... with SSO not authorized"

The error message indicates that the user maintained in broadcaster setting user is not valid on the Java server which is processing this request. In you server landscape multiple Java server are listening to the same "RFC program ID" that you have maintained in SM59, then all these listeners must be configured correctly.


1 - Follow check Checklist for issues during execution of Broadcaster-Setting#C1 to check the JAVA configuration.
2 - Follow check Checklist for issues during execution of Broadcaster-Setting#C2 to check RFC destination.
3 - Identify the user type with the information mentioned in paragraph Checklist for issues during execution of Broadcaster-Setting#G2 on this page.
4 - Check the user with help of check Checklist for issues during execution of Broadcaster-Setting#C3 and following information:

  • The broadcast setting is 'User Specific':
    • User-Specific settings use the recipient user to precalculate the data generated in the Broadcaster setting.
    • The BEx Broadcaster is a double-stack application (JAVA and ABAP). It uses SSO for security integration between both stacks.
    • As a consequence, this user should be able to log-in in both stacks via SSO.
    • Make sure that all the users you want to the broadcaster as User-Specific have a valid user in ABAP and JAVA stacks. In case that is not possible, uncheck the option User-Specific.
    • You can find this information in note 2002823.
  • The broadcast setting is NOT 'User Specific':
    • Make sure that the broadcast setting 'Authorization User' is valid.

If the issue remains after applying these solution:

  • Please answer questions at the end of this page: Your Analysis
  • Tell us the user ID which you have checked.

S1.2 - Error: background execution / user errors

  • You find following error details in Tx RSRD_LOG:

    • 03.06.2014 10:14:09 <background_user> - 00000000000000471708

    • <setting>: <broadcast_setting_authorization_user> is not a valid user name in the BW system

    • Setting <setting>: User <broadcast_setting_authorization_user> cannot be used for background processing

  • Message ID's:

    • RSRD 203: ... is not a valid user name in the BI system

    • RSRD 191: Setting ... : User ... cannot be used for background processing 

  • Solution: Identify the background_user (see point G2 above). The background_user needs ...

    • ... S_BTCH_JOB and S_RS_BCS authorization rights as explained in note 2029986. Details about these authorization objects can be found on wikipage Authorization in BEx Broadcasting.

    • ... S_USER_GRP authorization ID 'ACTVT' FIELD '03' display (due to security correction 1777053).

S1.3 - Error when opening an RFC connection 

  • Solution: Follow check C1 to check the JAVA configuration.

S1.4a - "Unknown Error" while broadcasting in PDF file format:

S1.4b - "Unknown Error" while broadcasting in CSV, PDF, XML file format:


S1.5 - "Unknown Error" and JAVA trace shows 'User is locked':

  • In Tx RSRD_LOG you can find the error message: "Unknown Error". You have recorded a JAVA trace. In the trace file, search/find the error message like "RfcGetException rc (7) message: User is locked."
  • Solution: Check the RFC connection in the system and make sure that the user defined to connect to the backend is unlocked. 

S1.6 - No authorization to scheduling

  • You find following error in Tx RSRD_LOG: No authorization to scheduling <setting> for users <broadcast_setting_authorization_user>.
  • Solution: Check the user type from < broadcast_setting_authorization_user >.  It's mandatory to use a dialog user. See note 1877255. A system user can not be used.

S1.7 -  Template service could not be loaded

  • You find following error in Tx RSRD_LOG: Template service could not be loaded!
  • Solution: Please set parameter ms/redirect_version=1 as per note 972514 and restart your ABAP Web Application Server.

S1.8 - Parallel processing not possible  

  • You find the error message "Parallel processing not possible" in the broadcasting log file.
  • Solution : Make sure that note 1431856 is implemented and set the parameters as explained. System checks every <BC_WAIT_SECONDS_PER_CYCLE> seconds for a free BACKGROUNG_PROCESS. The system tries that <BC_MAX_WAIT_CYCLES> times.
  • Start with a look into Broadcasting LOG (Tx RSRD_LOG) to find the "shortest execution time" for any package. Similarly, find the "longest execution time" for any package
  • Now calculate the RSADMIN parameter like following:
    • BC_MAX_WAIT_CYCLES = "longest execution time"  / "shortest execution time"  cycles
    • BC_WAIT_SECONDS_PER_CYCLE = "shortest execution time"  seconds
  • For Example, you calculated BC_MAX_WAIT_CYCLES = 100 and BC_WAIT_SECONDS_PER_CYCLE = 300 then start testing using this parameter. Increase the BC_MAX_WAIT_CYCLES value until the "Parallel processing not possible" error no longer occurs. 
  • The parallel processing in broadcasting is configured in table RSBATCHPARALLEL.
    • With a look into this table with selection PROCESS_TYPE = BROADCAST you can see all broadcasting relevant entries.
    • Our example shows ...
      • ... as 1st entry the global setting for the broadcasting area (PC_VARIANT is empty), 3 parallel processes ar maintained.
      • And there are 3 broadcasting entries with process chain variants (PC_VARIANT = <variant name>) with specific settings which override the global setting.
    • See also the Online Documentation: Setting Parallel Processing of BW Processes

S1.9 - Java system error: Exception in method processFunction

Solution: Follow check Checklist for issues during execution of Broadcaster-Setting#C1 to check the JAVA configuration. Check the Java Default Trace for errors. As there may be huge java default trace in the system use the time that the error occurred to isolate the correct trace. The trace reader provided with the Portal tools can be used to decode the date and time.

S1.10 - EXPORT XFA exception when calling the PDF object after ... msec

  • Message no. RSBOLAP014
  • Solution: Activate the "SAP BI Export Library" as explained in note 1112132

 S1.11 - Parameter object with the name ...  and the index ... still does not exist in the parameter list

  •  Solution: Identify the RFC Destination of your Default Portal and set the RFC to Unicode communication as explained in KBA 2036517.

S1.12 - Error of type OSERR_BCS occurred sending document

  • This error indicates that the user who has created the broadcast setting does not exist in the system. To identify, this user, also called OWNER review point G2 / A - broadcast_setting_creator.
  • Solution:   According to SAP note 1463160 you need to recreate the broadcast setting with a user that exists in the system.

S1.13 - CL_RSRD_PRODUCER_PRECALC type PROD did not deliver a document 

  • This error indicates that the recipient-user is not a valid user or for 
  •  Solution: Find the affected user ID in log (Tx RSRD_LOG). Review point Checklist for issues during execution of Broadcaster-Setting#C3 to understand what valid user means and check/correct the affected user. Additional check JAVA service XMLFormService for any warnings.
  • The issue could also happen for some specific output format, as MHTML. Under XML(Excel), the broadcast setting works. This is caused by a Portal Theme issue. The solution is always to use the latest patch of BI Java components.  See check C1.1 

S1.14 - An Unknown Error Occurred During Portal Communication + Error while instantiating the Web template

  • in process

S1.15 - Error: Provider Selection Object: Initialization Issue 

  • Identify the object which is broadcasted (Query, QueryView or Web Template). Execute the object in JAVA WEB with the same selection and user maintained in the Broadcaster setting. In case of queries and query views you can test with transaction RSRT using Java Web mode.
  • For doing broadcasting make sure that direct execution of broadcasted object works without any errors.
  • Few corrections are available for this error, when the system is correctly configured.
    • For BW 730, implement the SAP Note 1745596 - Provider Selection Object: Initialization Issue
    • For BW 730 and 731, implement the SAP Note 1717943 - Variable screen: Empty hierarchy variable causes exception
  • Make sure the BI Diagnostics returns no red alert.
  • The BI Java patches must be on latest patchlevel

S1.16 - Error: Parameter Object with the name “EMBEDDING_TEMPLATE” and the index “0” still does not exist in the parameter list

  • Solution:   According to note 2036517 you need to change the RFC to Unicode communication.

S1.17 - Error: RSRD_X_PRODUCE_PROXY not found

  • This error indicates that portal and ABAP communication is not working properly.
  • Solution: Follow check C1 to check the JAVA configuration.

S1.18 - Java communication error: Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT', communication rc: CM_RESOURCE_FAILURE

  • This error indicates that portal and ABAP communication is not working properly.
  • Solution: If after checking C1 and Checklist for issues during execution of Broadcaster-Setting#C2 the issue still persists, ensure that in the RFC destination configuration on the portal side, the 'Server Count' parameter is greater than 2 especially if you have multiple server nodes. Restarting the RFC destinations also helps when making configuration changes or when IP addresses of the servers changes.

S2 - The document/file sent from Broadcaster is wrong

S2.1 - MHTML report is not readable

The from BEx Broadcaster sent MHTML report is not readable. The MHT file contains CSS data:

S2.1.1 - Make sure that you are using BEx Broadcaster 7x
  • Please note that old BEx Broadcaster 3x is not supported for SAP Netweaver 2004s and above. Regarding this please review following notes:
    • 2044155 - BEx Broadcaster 3.x is not supported
    • 2020590 - SAP BEx Information Broadcaster 3.x and Reporting Agent not supported in BW 7.4
  • How to identify the BEx Broadcaster version of affected broadcast setting?
    • Start Tx SE16, table rsrd_setting, enter the technical name of the broadcast setting into field SETTING_ID. 
    • Read out the field 'OBJECT TYPE' of the broadcast setting:
    • Old BEx Broadcaster 3x:  QU Query / HT  WebTemplate (3.x style)       
    • New BEx Broadcaster 7x: BQ  Query / BV  Query view / BT  WebTemplate (BI Java) / RP  Enterprise Report / WB  Workbook
  •   If it is a 3x broadcast setting you to need to create a new 7x broadcast setting with new BEx Broadcaster 7x.
  •   Broadcast settings 3.x cannot be migrated. Link 
  • Please review wikipage: Prerequisites for using BEx Broadcaster  
  •   Go on with reading only in case it is a 7x broadcast setting.
S2.1.2 - Check the sent report in Tx SOST
  • Start Tx SOST and find the from broadcaster sent email.
  • Open the attached MHT file and confirm that the unreadable format is here also shown. 
  • If the report is fine you can sort out any problem with BEx Broadcaster.
S2.1.3 - Check the result with another Email client as MS Outlook
  • If the report is fine in another Email client then issue seems related to Outlook rendering.
  • You can sort out any problem with BEx Broadcaster.
S2.1.4 - Use ZIP file option
  • Set flag "as a ZIP file" in the broadcast setting as explained in note 772246 to overcome this problem.
  • Starting with BW701 apply JAVA correction 1897716 and activate RSADMIN parameter RSWR_BC_MHT_OUTLOOK_FIX.
S2.1.6 - Check broadcast setting authorization user
  • Check the authorization of < broadcast_setting_authorization_user >. See point G2.
  • Execute the direct execution of the broadcasting object in JAVA web with < broadcast_setting_authorization_user >. 

  • Make sure that < broadcast_setting_authorization_user > has S_RS_COMP1 / RSZCOMPID=* authorization.   

S2.2 - Broadcasted PDF document does not contain all expected tabs

  • You broadcast a WebTemplate which contains several tabs (tabstrip items). The broadcasted PDF document contains only the 1st tab, expected are all Tabs of the WebTemplate.

  • Solution: Apply solution mentioned in note 1821722 and use RSADMIN parameter EXPORT_ALL_TABS_PDF_BROAD. JAVA correction from 2128654  needs to be applied. In case of issue remains please check JAVA configuration using SAP NetWeaver BI Diagnostics & Support Desk Tool.

S2.3 - In broadcasted PDF/Excel document the content is shown multiple times

  • This issue is export related, you can also reproduce it with using .... 'Export to  PDF' functionality. See check Checklist for issues during execution of Broadcaster-Setting#C4 or ... 'Export to  XLS' functionality. The issue can occur in the case of parameter EXPORT_ALL_TABS_PDF_BROAD (see Point S2.2) is active.  For this issue, the SAP note 2150610 was created. The Java correction will be delivered with note 1918269 .

S2.4 -  Images are missing

  • For output format Excel and PDF, activate RSADMIN parameter RSWR_EXPORT_INTERNAL_ITEM = X (See note 2057789).  You can use report SAP_RSADMIN_MAINTAIN to maintain the parameter.  Rebooting the JAVA Server after adding the RSADMIN is required.
  • For output format MHTML, apply solution mentioned in note 2014870.

S2.5 -  MHTML format: Incorrect Display in MS Outlook / repeated rows

Solution: Please implement note 2179663. Review the template if it is not forcing to repeat the values:

S3 - Execution error: "ITEM of type ... could not be generated"

  • You execute a broadcast setting. The error "ITEM of type ... could not be generated" occurs:

  • Solution: Please implement the corrections of SAP Note 2283483  and use theme  sap_tradeshow_plus.
    This is the only theme supported by SAP.

  • The  KBA 2076512 also provide a solution, but for old support packages. - For that case, use  sap_chrome.

S4 - Execution error: Error while generating HTML

  • in process

S5 - Parallel broadcasting not working

  • While mass broadcasting packages are generated. These packages are processed in parallel as maintained in table RSBATCHPARALLEL. For details see point S1.7. You observed that broadcasting works sequentially but you expect parallel processing.
  • Solution: Implement note 2025948. In case of the issue remains please create a variant for  RSRD_BROADCAST_BATCH to reproduce the issue and perform check Checklist for issues during execution of Broadcaster-Setting#C1

S6 - Broadcast to Portal / KM folder not working

S7 - Java system error: while trying to get the length of a null array loaded from local variable 'arr$'

  • The issue is a side effect of incorrect configuration of BI Java Portal. The Portal cannot create a communication with BW Abap. 
    Check with Portal team, the BI Diagnostics is damaged on BI Mastersystem.

    The issue is NOT BEx Broadcaster. The issues on your broadcaste r are a side effect of incorrect BI Java configuration
  • Here are some most common configuration issues are documented below:

    • While running diagnostics BI Diagnostics
    • When you click reload configuration on BI Diagnostics Reload Configuration
    • When you test the connector tests on BI Java Portal Connection_Test
    • KBA   2544695 - While trying to get the length of a null array loaded from a local variable at slot xx

S8 - Broadcast failing for specific users

S9 - Mime path "" does not exist
OR Mime path "" does not exist

  • Officially there is one theme supported by SAP, valid for BEx Broadcaster. The theme is  sap_tradeshow_plus .   More details can be found here:
    SAP Note 2283483 - BEx Web 7.3+ - Changed standard theme and theme determination in Broadcaster

  • For old version of BW, you will find the note 2057952 - Broadcaster return error ITEM of type could not be generated
  • The note activates sap_chrome has the Broadcast theme. Only proceed with this correction ONLY IN THE CASE when the correction of note 2283483 cannot be implemented.

 S10 - The parameter "CONFIRM_OVERWRITE" does not exist

  • The issue is caused by an error on BI Java Portal. The error experienced on BEx Broadcaster is just a side effect.
    The solution is documented in SAP Note 2430461  - BEx Web 7.3+: The parameter "CONFIRM_OVERWRITE" does not exist. 
    Please, read the note and implement the solution. 
  • BE SURE there is no issue related to your BI Java Portal. If the BEx Web Analyzer does not work, the issue is related to BW-BEX-ET-WJR.
    So please, for this case, open an incident to this component and describe the issues experienced. Do not forget to mentions that you are experiencing issues while running the query on BI Java Portal (BEx Web Analyzer).


C1 - SAP NetWeaver BI Diagnostics & Support Desk Tool

  • Execute the 'SAP NetWeaver BI Diagnostics & Support Desk Tool' to check the configuration of your system. 
    • 937697 Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool > find the in note mentioned 'related/referenced notes' to get help for correcting the configuration
    • A COMPLETE GREEN Diagnostic Tool is mandatory (see note 1177154 ).
  • If the result shows UNDEFINED items: The user who executes the SDT needs to be an administrator on JAVA and ABAP instance. If the user has limited authorization you will get UNDEFINED results.
  • If the result shows RED items: Involve your JAVA administrator to correctly configuration of the system using note: 
    • 2113395 Supportdesk Tool RED signal checking the troubleshooting guide

C1.1 - BI Java  patch level 0 is not supported 

  • BI Java  patch level 0 is not supported because it does not include all the subsequent corrections, see note 1899396.

C2 - Check RFC destination

  • Make sure that RFC destination (maintained in table RSPOR_T_PORTAL) for the default portal is unique as described in note 1573365 .
  1. Identify the RFC destination of default portal in table RSPOR_T_PORTAL.
  2. In SM59, TCP/IP Connections, find and open the default portal RFC destination.
  3. In RFC destination press button 'Connection Test' (Ctrl + F3) to test the RFC connection > no error should occur.
  4. Go Back (F3).
  5. In RFC destination navigate: Extras > System Information > Target System (Shift + F7) > write down the Network IP Address.
  6. Go Back (F3).
  7. Repeat steps 5 and 6 several times. Write down all different Network IP Addresses. (It is OK if there is only one IP Address.)
  8. Please check: 
    1. All found Network IP Addresses must belong to the server node of the same system.
    2. All the server nodes must be functional.
    3. The server nodes contains 'BI component' and use SCA patchs PL>0 

C3 - Check validity of the user

  • According to notes 1442771 and 2002823 valid user means: "User is unlocked" AND "User is active" AND "Password is not initial" AND "User has a non-expired password"
  • Hint: Check parameter login/password_expiration_time.
  • In Tx SE37 execute following function modules for the user and see if you get any error/exception, If you have identified a non valid user please correct the user. 

C4 - Check Export to PDF functionality

If you use the output format PDF and the generated PDF document is not as expected or while generation of PDF document a problem occurs then please check the PDF generation without involvement of BEx Broadcaster.


  • If the issue happens also with direct PDF generation then this issue is related Export (component BW-BEX-ET-WJR-EXP) and not to BEx Broadcaster. This information is very important as it helps to analyze/solve your issue more quickly.

How to check?

  • Execute the broadcasted object (Query, Query View or WebTemplate) directly in JAVA WEB.
  • In the context menu select the option "Print Version" to generate the PDF document.
  • If the context menu option "Print Version" is not available search for the Export function in the Navigation Bar > select sub option "Export to PDF" to generate the PDF document.
  • Check the PDF generation and the generated PDF document.

C5 - Check user parameters on SU01

  • User parameters can influence on BEx Broadcaster execution.Got to SU01 transaction -> search for the user -> go to parameters tab. Check if there is any parameter that is forcing the user to use another RFC Destination from another Portal, like “RSPOR_DEFAULT_PORTAL".
  • If so, remove or maintain the correct RFC Destination of your Default BI Java Portal (you see the RFC into table RSPOR_T_PORTAL).

Your Analysis

  • In case of the issue remains after applying the solution then please answer following questions.
  • Please, copy/paste this part into a TXT file and attach into the incident.
01. The SAP NetWeaver BI Diagnostics & Support Desk Tool is green?
    YES/NO  (If NO please correct the RED alerts first.)
02. Is a BI JAVA patch higher than 0 deployed for SCA's mentioned in note 1899396?
03. The RFC Destination check (see check C2) was successfully? All IP addresses are valid/correct (the test must be made at least 10 times)?
04. SUPPORTDESK.ZIP file (generated from SAP Note 937697) is attached on the incident?
05. Please provide your findings regarding mentioned checks.
    Your issue matchs to symptom: S... (please enter the number)
    Have you applied the solution? 
06. Please provide a broadcast setting for reproducing the issue in Tx RSRD_START.
    technical name of broadcast setting = ...
07. May SAP Product Support execute this broadcast setting, please confirm?
    YES/NO (If no please create/provide a copy of the setting and change it as needed so that SAP Product Support may execute it.)
08. Execute the setting in Tx RSRD_START and provide the LOG Details. You can find it in Tx RSRD_LOG:     
    RSRD_LOG date/time = DD.MM.YYYY / HH:MM:SS       
    RSRD_LOG ID = ... 
09. R/3 connection to your NW BW system and HTTP service connections are opened?
10. A valid user in SAP Secure Area with sufficient authorization for NW BW and an administrator user to the Portal are available on secure area?
    (minimum transactions necessary: Tx: SE38, SE16, RSRD_START, RSRD_LOG, RSRD_ADMIN, RSRT, SE16, SE37 ...)
    USER_ID = ...

Link to this page:

Bridge KBA: 2441051 - Checklist for issues during creation and editing of Broadcaster Setting

1 Comment

  1. Nice! ...but does anyone know how to delete workbooks from the portal with a program or process?