Structural Authorization Indexing Programs

Hi Experts,
I've performed hiring updates via PA40 and manage to save it using test ID (example:TEST1) - I have no issue to view it straight away using the same test ID. However, other ID (example:TEST2) not able to view it. Other ID can only be able to view it after I executed indexing programs. Is this normal?
I'm searching for solutions in forums and post this message at the same time to experdite. Appreciate your advice for me to enable other users to view the employee details created once it is saved.
Best regards and million thanks in advance.

Hi,
I write maybe some general and obvious stuff which is not related to your specific problem but I do it only to leave this post as a reference if someone ends up here using search...
RHBAUS0x-programs index structural authorisations to reduce performance issues which may arise if structural profile is large. This can happen for example in case of higher-level managers or if there is complex requirements to restrict qualifications catalogue or business event menu.
Short description of the programs
RHBAUS02 is used to fill up table T77UU. You can setup threshold value i.e how many object user must have in the structural profile to be considered to require indexing. This program will enter and remove users from table T77UU based on their current position.
RHBAUS01 cleans up INDX table if user was removed from T77UU manually or as a result of running RHBAUS02. You should run this periodically if you use indexing.
RHBAUS00 is the actual indexing program. You can run it for specific users or all (leave user names blank) but the user ids must be in table T77UU.
Standard behaviour of indexing
This is the behaviour regardless of authorisation main switch settings (OOAC).
USER1 has large structural profile and the user id is therefore listed in table T77UU to be indexed to make users access faster. If index is refreshed (RHBAUS00 run) daily 1 am and new vacant position is created same day 7 am by another user; USER1 will see the new position next day after RHBAUS00 has been run or if it is run before that manually. I have seen various ways of trying to get over this issue.
One client tried to run RHBAUS00 every fifteen minutes and ended up crashing their system since first run didn't always finish when new was about to start. Another client created custom tcode for users to refresh their own index. It worked but users had trouble understanding the use and kept forgetting to refresh their index.
Things to consider before indexing and my comments
1. What is good threshold limit?
This can vary between system performance and how much HR is used and what type of reports are being run.
My experiences: I have often increased the value from default 1000 if that can drop lot of users from the indexing. If users complain performance of specific report check the program code and use. I have seen lot of badly coded Z-programs which can cause long run time. Another trick is to use P_ABAP authorisation if the program can be excluded from authorisation checks (office phone directory in ESS) or if user accessing the program has anyway full access to all employees (some payroll transactions for example run by payroll).
2. Can we reduce the size of strtuctural profiles?
- If it is possible to restrict something doesn't mean you should restrict it. I have seen structural profiles where each user was evaluated and they had access to see only qualifications which they currently had. Might sound secure but it is not practical and also stops users to see which qualifications they might want to achieve.
- I try to keep focus on O-S-P -objects unless there is specific request to restrict qualifications and business events. There are other methods of stopping users booking courses held at Hawaii office.
- Check the evaluation path. Sometimes evaluation path returns all object during the path even you are interested only to restrict the last one.
3. Can we use exclusion?
Sometimes HR and CEO has access to everything except something. Instead of listing everything else than the board of directors it is easier to list board of directors and use tick exclusion in OOSB (or in infotype 1017).

Similar Messages

Regeneration of INDX for Structural Authorization

Hello all,
We are having problems with the index of structural authorization.... employees can´t see objects created until we run the program RHBAUS00.
I'm reading at the documentation of program RHBAUS00, and it says that "The index for the structural authorization profile of the user is generally regenerated during the night in a batch job"..... but it is not working !
Does any body know how SAP execute an automated regeneration of index for structural authorization?
I want to know which job do that or how the system do that? or if I need to define a job by my self?
Thanks in adcanve.
Enrique Vera

Hi Enrique,
I think you have misanderstood the documentation.What it says is that usually customers run this program RHBAUS00 as batch every night. But apart from the report there is no other program/functionality that will reset the INDEX
You have to set up this report to run as BDC everynight if you require it.
Hope this help
Sarah

Structural authorization - creation of employee number in webdynpro or abap

Hello Experts,
We are facing some problems with the combination of structural authorizations and the creation of a new employee.
When we use PA40 to create a new employee this does not give any problem.
In the webdynpro we first execute a call transaction PA40 to apply infotype 0000 and 0001. This works well.
Except that the call transaction does not set the connection between PA and OM. (so we did program this ourselves)
In PO13 and the table HRP1001 the same relations are made as when we use PA40 in the sap gui.
After this we do call transactions PA30 for the next infotypes.
When we check the SU53 it gives a message: problems with structural authorizations object P (with the employeenumber) starting at 01.01.1800, enddate is empty.
The employee is manager and connected with his userid in infotype 0105.
We use in the structural profile the function module RH_GET_MANAGER_ASSIGNMENT
We checked with transaction HRHAUTH.
User has been adjusted to the tables T77UA etc.
We do not use workflow in this webdynpro
We used the trace function when this was executed, but it did not give more information about missing structural authorizations.
This issue was before on SDN (Structural authorization - creation of employee number) but unfortunally there was no solution there for the issue!
Hope one of you can help me to find the solution!
With kind regards,
Rita Mensink

Hi.
After 2½ days of frustration I finally nailed this.
Function group RHAC, that handles the authority checks, initially buffers a table called VIEW containing all objects available for the user. As stated earlier in this conversation, SAP handles creation of relations in HRP1001 (links PA and OM). At this point the new employee number is appended to buffered table VIEW in function group RHAC.
When execution the PA40 activity through CALL TRANSACTION, the creation of the relations are not handled - and the same goes for updating the buffered table VIEW. The table can be updated using the function module RH_VIEW_ENTRY_INSERT from the same fundtion group:
This example might be useful
data: ls_view_entry type hrview,
        ls_related_object type hrobject.
ls_view_entry-plvar = '01'.
ls_view_entry-otype = 'P'.
ls_view_entry-objid = lv_pernr.
ls_view_entry-begda = '18000101'.
ls_view_entry-endda = '99991231'.
ls_view_entry-maint = 'X'.
ls_related_object-plvar = '01'.
ls_related_object-otype = 'S'.
ls_related_object-objid = lv_ny_objid.
call function 'RH_VIEW_ENTRY_INSERT'
    exporting
      view_entry     = ls_view_entry
      related_object = ls_related_object.
Best regards
Poul Steen Hansen
Senior Technical Consultant
EDB Consulting Group A/S, Denmark

How To Create ABAP Code For HR Context Sensitive Structural Authorization

Hello,
We have created a HR Custom Program which IS NOT built off the PCH or PNP Logical Database. As a result, we need to manually create ABAP code for HR Context Sensitive Structural Authorization Check in our custom HR program. Via HR Context Sensitive Structural Authorizations, we are restricting access to personnel numbers and the underlying HRP* tables.
Any assistance would be greatly appreciated with the identification of the SAP standard function modules (Ex. RH_STRU_AUTHORITY_CHECK, HR_CHECK_AUTHORITY_INFTY, HR_CHECK_AUTHORITY_INFTY , etc) used in HR Context Sensitive Structural Authorization Check, how they are used to control HR Structural authorization (P_ORGINCON), and some sample code.
Thank you in advance for all your assistance,
Ken Bowers

Hello Ken
You can use the interface methods IF_EX_HRPAD00AUTH_CHECK to get the same structural authorization as you can see in PA20/PA30. You need to use the methods set_org_assignment and check_authorization for this purpose. For more information you can refer to include FP50PE21 from line 237 onwards till 270.
Regards
Ranganath

Issue in Dynamic Structure and Component Program

Hi,
I have a requirement of creating an inbound idoc program and populating dynamic structures. The program for the dynamic structure creation is as follows: ( I have been referencing Heilmans Blog ): The part for the inbound idoc creation works fine. The data will come in a flat file with Table name and 15 characterstcis. The table name is known at runtime. I need to create the dynamic table, find out the components and then populate the custom table with the dynamically created structures.
Custom table: 4 components
Internal table from file: 15 components with value.
There could be more than one table in the flat file and not all components or char in the flat file is mapped to the table. I would need some expertise in coding the OO part of the program.
Any inputs will be apprciated:
<removed 6845 lines of code (forum software cut off at this point, there was more!) - did you actually expect anyone to read that? Also, please use code tags (the "<>" icon on the toolbar)>
Edited by: Mike Pokraka on Aug 3, 2008 6:15 PM

Hi,
The program works fine fo creating inbound idocs. It is the dynamic structure population that seems to be the problem mentioned earlier: Here is the code:
*& Report /FACTGLB/GTDMI_VARTAB_IDOCS02 *
PROGRAM DESCRIPTION: Variant Table and Content Upload Interface.
 DEVELOPER: Aveek Ghose
 CREATION DATE: 2008-04-18
 RDD NUMBER: DCDD027
TRANSPORT NUMBER(S): RD2K902769
*-- REVISION HISTORY -
 DEVELOPER:
 DATE APPLIED: YYYY-MM-DD
 SCR NUMBER: <Scope Change Request ID>
 RDD NUMBER: <Toolset Object ID>
TRANSPORT NUMBER(S):
 DESCRIPTION:
REPORT ZGTDMI_VARTAB_IDOCS_DYNAMIC
 NO STANDARD PAGE HEADING
 LINE-SIZE 150
 LINE-COUNT 55
 MESSAGE-ID zfactglb.
**Include for Global Data Declaration
*INCLUDE /FACTGLB/GTDMI_VARTAB_TOP02.
**Include for Selection Screen
*INCLUDE /FACTGLB/GTDMI_VARTAB_SEL02.
**Include for Sub Routines
*INCLUDE /FACTGLB/GTDMI_VARTAB_FORMS02.
*& Include /FACTGLB/GTDMI_VARTAB_TOP02 *
*& Include /FACTGLB/GTDMI_VARTAB_TOP02 *
*& Include /FACTGLB/GTDMI_VARTAB_TOP
*& Include /FACTGLB/GTDMI_VARTAB_TOP
PROGRAM DESCRIPTION: Variant Table and Content Upload Interface.
 DEVELOPER: Aveek Ghose
 CREATION DATE: 2008-04-18
 RDD NUMBER: DCDD027
TRANSPORT NUMBER(S): RD2K902769
*-- REVISION HISTORY -
 DEVELOPER:
 DATE APPLIED: YYYY-MM-DD
 SCR NUMBER: <Scope Change Request ID>
 RDD NUMBER: <Toolset Object ID>
TRANSPORT NUMBER(S):
 DESCRIPTION:
TYPE POOLS
*Type declaration for ALV display
TYPE-POOLS : slis.
Include .
type-pools: col, "#EC *
 icon, "#EC *
 sym, "#EC *
 abap. "#EC *
Target structure definitions
tables:
E1CUVTM, "#EC *
E1DATEM, "#EC *
E1CUV1M, "#EC *
edp21, "#EC *
edi_dc40, "#EC *
edi_dd40, "#EC *
edi_ds40. "#EC *
GLOBAL TYPES
TYPES : BEGIN OF ty_vartab.
 include structure E1CUVTM.
TYPES: END OF ty_vartab.
TYPES : BEGIN OF ty_vartabdate.
 INCLUDE STRUCTURE E1DATEM.
TYPES : END OF ty_vartabdate.
*Structure for data retreived
TYPES : BEGIN OF ty_vardetails.
 INCLUDE STRUCTURE E1CUV1M.
TYPES : END OF ty_vardetails.
*Structure for data retreived from table tabinput.
TYPES : BEGIN OF ty_tabinput,
 lines type string,
 END OF ty_tabinput.
*Structure for data retreived from Table dsn_input.
TYPES : BEGIN OF ty_dsninput, "#EC *
 LINE(101) type c,
 END OF ty_dsninput.
*Structure for data retreived from Table dsn_input.
TYPES : BEGIN OF ty_newinput, "#EC *
 LINE(101) type c,
 flag(1) type c,
 END OF ty_newinput.
*Structure for keeping the values of all the custom tables
TYPES : BEGIN OF ty_custom_tabs,
 matnr TYPE matnr, "Material Number
 werks TYPE werks_d, "Plant
 lgort TYPE lgort_d, "Storage Location
 qunty TYPE P DECIMALS 2, "Standard Order Quantity
 det_loc TYPE CHAR6, "Detail Location
 class TYPE CHAR2, "Class
 rate TYPE P DECIMALS 2, "Rate
 END OF ty_custom_tabs.
*Type declared for the internal table and work area which will store
*fields for error log
TYPES : BEGIN OF ty_error_log,
 matnr TYPE matnr, "Material Number
 mtart TYPE mtart, "Material Type
 sel_data TYPE char10, "No of selectyed data
 END OF ty_error_log.
*Structure for keeping the output data
TYPES : BEGIN OF ty_final,
 VTNAM(018) type C,
 CHAR1(030) type C,
 CHAR2(030) type C,
 CHAR3(030) type C,
 CHAR4(030) type C,
 CHAR5(030) type C,
 CHAR6(030) type C,
 CHAR7(030) type C,
 CHAR8(030) type C,
 CHAR9(030) type C,
 CHAR10(030) type C,
 CHAR11(030) type C,
 CHAR12(030) type C,
 CHAR13(030) type C,
 CHAR14(030) type C,
 CHAR15(030) type C,
 FLAG(001) type C,
 END OF ty_final.
TYPES: begin of TY_CONTENTHD,
 VTNAM(018) type C,
 FLAG(001) type C,
end of TY_CONTENTHD.
TYPES: begin of TY_CONTENT,
 VTNAM(018) type C,
 CHAR1(030) type C,
 CHAR2(030) type C,
 CHAR3(030) type C,
 CHAR4(030) type C,
 CHAR5(030) type C,
 CHAR6(030) type C,
 CHAR7(030) type C,
 CHAR8(030) type C,
 CHAR9(030) type C,
 CHAR10(030) type C,
 CHAR11(030) type C,
 CHAR12(030) type C,
 CHAR13(030) type C,
 CHAR14(030) type C,
 CHAR15(030) type C,
 FLAG(001) type C.
TYPES: end of TY_CONTENT.
TYPES: BEGIN OF TY_E1CUVTM,
 MSGFN TYPE MSGFN,
 VAR_TAB TYPE APITABL,
 STATUS TYPE RCUTBST,
 VTGROUP TYPE RCUTBGR,
 AUTHSTRUC TYPE RCUTBBE,
 AUTHENTRY TYPE RCUFNBI,
 FLDELETE TYPE FLLKENZ,
 DBTABNAME TYPE TABNAME16,
 DBCONACTIVE TYPE DBCON_ACTI,
 PRESDEC TYPE VTDCT,
 END OF TY_E1CUVTM.
TYPES: BEGIN OF TY_E1CUV1M,
 MSGFN TYPE MSGFN,
 VTLINENO TYPE VTLINENO,
 VTCHARACT TYPE ATNAM,
 ATWRT TYPE ATWRT,
 ATFLV TYPE ATFLV,
 ATAWE TYPE MSEHI,
 ATFLB TYPE ATFLB,
 ATAW1 TYPE MSEHI,
 ATCOD TYPE ATCOD,
 ATTLV TYPE ATTLV,
 ATTLB TYPE ATTLB,
 ATPRZ TYPE ATPRZ,
 ATINC TYPE ATINC,
 VTLINENO5 TYPE VTLINENO5,
 END OF TY_E1CUV1M.
TYPES: BEGIN OF TY_E1DATEM,
 MSGFN TYPE MSGFN,
 KEY_DATE TYPE SYDATUM,
 AENNR TYPE AENNR,
 EFFECTIVITY TYPE CC_MTEFF,
 END OF TY_E1DATEM.
TYPES: BEGIN OF ty_vtnam,
 vtint TYPE vtint, " Internal number of variant table
 vtnam TYPE vtnam, " Name of variant table
 error TYPE char1, " Indicates error in data format
 reas TYPE char50, " Reason for failure
 END OF ty_vtnam.
Get data type for characteristic
TYPES: BEGIN OF ty_cabn,
 atinn TYPE atinn, "Internal characteristic
 atnam TYPE atnam, "Characteristic Name
 atfor TYPE atfor, "Data type of characteristic
 atson TYPE atson, "Indicator: Additional Values
 atprt TYPE atprt, "Check table
 atprr TYPE atprr, "Name of Check Report Program
 atprf TYPE atprf, "Function Module for Checking Values
 anzdz TYPE anzdz, "Number of Decimal Places
 check TYPE char1, "Indicates check required or not
 END OF ty_cabn.
Get field names of variant table
TYPES: BEGIN OF ty_cuvtab_fld,
 vtint TYPE vtint, " Internal number of variant table
 atinn TYPE atinn, " Internal characteristic
 vtpos TYPE vtpos, " Item number of characteristic in variant
 exist TYPE char1, " X Indictaes characteristic is part of fil
 END OF ty_cuvtab_fld.
Store all data in internal table
TYPES: BEGIN OF ty_file,
 vtnam TYPE vtnam,
 char1 TYPE atwrt,
 char2 TYPE atwrt,
 char3 TYPE atwrt,
 char4 TYPE atwrt,
 char5 TYPE atwrt,
 char6 TYPE atwrt,
 char7 TYPE atwrt,
 char8 TYPE atwrt,
 char9 TYPE atwrt,
 char10 TYPE atwrt,
 char11 TYPE atwrt,
 char12 TYPE atwrt,
 char13 TYPE atwrt,
 char14 TYPE atwrt,
 char15 TYPE atwrt,
 flag TYPE char1,
 error TYPE char50,
 END OF ty_file.
To check for duplicates
TYPES: BEGIN OF ty_dupl,
 vtnam TYPE vtnam,
 char1 TYPE atwrt,
 char2 TYPE atwrt,
 char3 TYPE atwrt,
 char4 TYPE atwrt,
 char5 TYPE atwrt,
 char6 TYPE atwrt,
 char7 TYPE atwrt,
 char8 TYPE atwrt,
 char9 TYPE atwrt,
 char10 TYPE atwrt,
 char11 TYPE atwrt,
 char12 TYPE atwrt,
 char13 TYPE atwrt,
 char14 TYPE atwrt,
 char15 TYPE atwrt,
 slnid TYPE slnid,
 END OF ty_dupl.
Get previously loaded characteristic values for internal table (CHAR)
TYPES: BEGIN OF ty_cuvtab_valc,
 vtint TYPE vtint, " Internal number of variant table
 slnid TYPE slnid, " Key for value combination in variant tab
 atinn TYPE atinn, " Internal characteristic
 valc TYPE atwrt, " Characteristic Value
 END OF ty_cuvtab_valc.
Get previously loaded characteristic values for internal table (NUM)
TYPES: BEGIN OF ty_cuvtab_valn,
 vtint TYPE vtint, " Internal number of variant table
 slnid TYPE slnid, " Key for value combination in variant tab
 atinn TYPE atinn, " Internal characteristic
 val_from TYPE atflv, " Internal floating point from
 END OF ty_cuvtab_valn.
Store column positions of characteristics
TYPES: BEGIN OF ty_col_pos,
 vtint TYPE vtint, " Internal number of variant table
 vtnam TYPE vtnam, " Variant table name
 atinn TYPE atinn, "Internal characteristic
 atnam TYPE atnam, "Characteristic Name
 field TYPE fieldname, "Field name
 req TYPE char1, " Required or not
 vtpos TYPE vtpos, " Item number of characteristics
 END OF ty_col_pos.
Store valid values for characteristics
TYPES: BEGIN OF ty_cawn,
 atinn TYPE atinn, " Internal characteristic
 atzhl TYPE atzhl, " Int counter
 atwrt TYPE atwrt, " Characteristic Value
 atflv TYPE atflv, " Internal floating point from
 lkenz TYPE lkenz, " Deletion indicator
 END OF ty_cawn.
Store error messages for individual lines
TYPES: BEGIN OF ty_error,
 vtnam TYPE vtnam, " Variant table name
 fname TYPE fieldname, " Fieldname
 atnam TYPE atnam, " Characteristic name
 atwrt TYPE atwrt, " Characteristic value
 row TYPE char5, " Row id
 END OF ty_error.
Begin TPR# 4618
To store unique number for variant
TYPES: BEGIN OF ty_vnt_ma,
 vtnam TYPE vtnam,
 unique_no TYPE ZGTDM_UNQN,
 no_chr TYPE ZGTDM_NO_CHR,
 END OF ty_vnt_ma.
To find out concatenated number for
TYPES: BEGIN OF ty_split,
 f1 TYPE char6,
 END OF ty_split.
TYPES: BEGIN OF ty_charval,
 char TYPE char30,
 END OF ty_charval.
TYPES: BEGIN OF TY_DATA,
 name TYPE string,
 value(15) type c,
 END OF TY_DATA.
DATA: I_DATATAB TYPE STANDARD TABLE OF TY_DATA.
TYPES:
TUMLS_MESSTYPE type /SAPDMC/LS_MESSTYPE,
TUMLS_MESSTYPETXT type EDI_TEXT60,
TUMLS_MESSCODE type EDIPMESCOD.
TYPES:
TUMLS_TABNAME TYPE TABNAME, "#EC *
TUMLS_SEGMENT TYPE TABNAME. "#EC *
TYPES:
TUMLS_PATHFILE TYPE /SAPDMC/LS_FILENAME,
TUMLS_FILENAME TYPE /SAPDMC/LS_FILENAME,
TUMLS_FILETEXT TYPE /SAPDMC/LS_FILETEXT.
TYPES:
BEGIN OF type_errorline,
 msgty type SYMSGTY,
 id type SYMSGID,
 msgno type symsgno,
 par1 type symsgv,
 par2 type symsgv,
 par3 type symsgv,
 par4 type symsgv,
END OF type_errorline.
TYPES:
type_errortab TYPE SORTED TABLE
 OF type_errorline
 WITH NON-UNIQUE KEY id msgno par1 par2 par3 par4.
DATA:
 LV_INDEX TYPE SY-INDEX,
 LV_INDEX2 TYPE SYINDEX,
 LV_TABLE1 TYPE REF TO DATA,
 LV_TABLE2 TYPE REF TO DATA,
 LV_TABLE3 TYPE REF TO DATA,
 LV_TABLE4 TYPE REF TO DATA,
 LV_LINE1 TYPE REF TO DATA,
 LV_LINE2 TYPE REF TO DATA,
 LV_LINE3 TYPE REF TO DATA,
 LV_LINE4 TYPE REF TO DATA,
 LV_OFFSET1 TYPE SYTABIX,
 ST_IS_LAYOUT_ALV TYPE SLIS_LAYOUT_ALV,
 L_IT_FCATLOG_ALV TYPE SLIS_T_FIELDCAT_ALV,
 L_IT_FLDCAT TYPE LVC_T_FCAT.
GLOBAL INTERNAL TABLES
DATA : i_newinput TYPE STANDARD TABLE OF ty_newinput INITIAL SIZE 0."#EC *
DATA : i_contentheader1 TYPE STANDARD TABLE OF ty_contenthd INITIAL SIZE 0."#EC *
DATA : i_contenttab1 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_contenttab2 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_contenttab3 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_contenttab4 TYPE STANDARD TABLE OF ty_content INITIAL SIZE 0."#EC *
DATA : i_E1CUV1M TYPE STANDARD TABLE OF E1CUV1M INITIAL SIZE 0."#EC *
DATA : i_errortab TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
GLOBAL WORK AREAS
**Internal Table for the structure TY_T001L
DATA : wa_vartab TYPE ty_vartab. "#EC *
DATA : wa_vartabdate TYPE ty_vartabdate. "#EC *
DATA : wa_vardetails TYPE ty_vardetails. "#EC *
DATA : wa_tabinput TYPE ty_tabinput. "#EC *
DATA : wa_dsninput TYPE ty_dsninput. "#EC *
DATA : wa_newinput TYPE ty_newinput. "#EC *
DATA : wa_gnewinput TYPE ty_newinput. "#EC *
DATA : wa_ginput_data TYPE ty_newinput. "#EC *
DATA : wa_final TYPE ty_final. "#EC *
DATA : wa_content TYPE ty_content. "#EC *
DATA : wa_contenthd TYPE ty_contenthd. "#EC *
DATA : wa_contentheader type ty_contenthd. "#EC *
DATA : wa_contenttab TYPE ty_content. "#EC *
DATA : wa_content1 TYPE ty_content. "#EC *
DATA : wa_contenthd1 TYPE ty_contenthd. "#EC *
DATA : wa_contentheader1 type ty_contenthd. "#EC *
DATA : wa_contenttab1 TYPE ty_content. "#EC *
DATA : wa_contenttab2 TYPE ty_content. "#EC *'
DATA : wa_contenttab3 TYPE ty_content. "#EC *
DATA : wa_contenttab4 TYPE ty_content. "#EC *
DATA : wa_E1CUVTM TYPE E1CUVTM. "#EC *
DATA : wa_E1CUV1M TYPE E1CUV1M. "#EC *
DATA : wa_E1DATEM TYPE E1DATEM. "#EC *
DATA : wa_error_tab TYPE solisti1. "#EC *
INTERNAL TABLES AND WORK AREAS FOR BDC
*Internal Table to store the data to display the error message
DATA : i_errormsg TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
*Internal Table to store the data to display the error message
DATA : i_error TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
DATA : itab_error TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0."#EC *
**Work area to store the data to display the error message
DATA : wa_errormsg TYPE solisti1. "#EC *
**Internal table which will store data for the error log
DATA:i_error_log TYPE STANDARD TABLE OF ty_error_log INITIAL SIZE 0."#EC *
GLOBAL VARIABLES
DATA: G_FILE TYPE string. "#EC *
DATA : g_ctr_input_recs(5) type c. "#EC *
DATA: g_ctr_output_recs(5) type p. "#EC *
data : g_msg(100) type c. "#EC *
data: g_struct_file TYPE string. "#EC *
data: g_login type FILEINTERN. "#EC *
data: g_phyin type string. "#EC *
DATA: g_lprnt type RSPOPSHORT. "#EC *
DATA: g_FNAME1 TYPE STRING. "#EC *
DATA : g_repid TYPE repid, "#EC *
 g_exit(1) TYPE C, "#EC *
 gx_variant type disvariant. "#EC *
DATA : g_lines TYPE i . "#EC *
data : g_save(1) type c. "#EC *
DATA : g_splid TYPE rspoid . "#EC *
data: p_login type FILEINTERN. "#EC *
data: p_phyin type string. "#EC *
DATA:
go_table TYPE REF TO cl_salv_table,
go_sdescr TYPE REF TO cl_abap_structdescr,
go_tdescr TYPE REF TO cl_abap_tabledescr,
gdo_data TYPE REF TO data,
gdo_handle TYPE REF TO data,
gs_comp TYPE abap_componentdescr,
gt_components TYPE abap_component_tab.
FIELD-SYMBOLS:
 TYPE table.
GLOBAL CONSTANTS
CONSTANTS c_msgar TYPE rslgarea VALUE 'F8'. "#EC *
CONSTANTS c_msgid TYPE rslgsubid VALUE 'E'. "#EC *
CONSTANTS c_urgnc TYPE char04 VALUE 'HIGH'. "#EC *
CONSTANTS C_X(1) TYPE C VALUE 'X'. "#EC *
CONSTANTS C_Y(1) TYPE C VALUE 'Y'. "#EC *
CONSTANTS C_Z(1) TYPE C VALUE 'Z'. "#EC *
CONSTANTS C_E(1) TYPE C VALUE 'E'. "#EC *
CONSTANTS C_SAP(3) TYPE C VALUE 'SAP'. "#EC *
CONSTANTS C_MOD(3) TYPE C VALUE 'MOD'. "#EC *
CONSTANTS C_MD1(3) TYPE C VALUE 'MD1'. "#EC *
CONSTANTS C_MD2(3) TYPE C VALUE 'MD2'. "#EC *
CONSTANTS C_MD3(3) TYPE C VALUE 'MD3'. "#EC *
constants: c_000001(6) type c value '000001', "#EC *
 c_e1cuv1m(7) type c value 'E1CUV1M', "#EC *
 c_02(2) type c value '02', "#EC *
 c_009(3) type c value '009', "#EC *
 c_0001(4) type c value '0001'. "#EC *
constants: c_e1datem(7) type c value 'E1DATEM'. "#EC *
constants: c_e1cuvtm(7) type c value 'E1CUVTM'. "#EC *
GLOBAL INTERNAL TABLES FOR ALV DISPLAY
*Internal tables for ALV Field cat
DATA :
i_fieldcat_ov TYPE STANDARD TABLE OF slis_fieldcat_alv INITIAL SIZE 0,"#EC *
i_fieldcat_dtl TYPE STANDARD TABLE OF slis_fieldcat_alv INITIAL SIZE 0,"#EC *
i_fieldcat_ov1 TYPE lvc_t_fcat, "#EC *
i_events TYPE slis_t_event. "#EC *
GLOBAL WORK AREAS FOR ALV DISPLAY
*Work area for ALV Field layout
DATA : wa_layout TYPE slis_layout_alv. "#EC *
*Work area for Field Cat. Table
DATA : wa_fieldcat TYPE slis_fieldcat_alv. "#EC *
GLOBAL VARIABLES FOR ALV DISPLAY
DATA : g_event TYPE slis_t_event. "#EC *
DATA : g_top_of_page TYPE slis_t_listheader. "#EC *
DATA : g_ok_code TYPE char4. "#EC *
DATA : g_variant type disvariant. "#EC *
GLOBAL CONSTANTS FOR ALV DISPLAY
BAL handling
data: iv_log_handle type BALLOGHNDL. "#EC *
data: is_log_header type bal_s_log. "#EC *
data: iv_object type bal_s_log-object value 'CAPI'. "#EC *
data: iv_subobject type bal_s_log-subobject value 'CAPI_LOG'."#EC *
data: iv_tcode type bal_s_log-altcode value 'SE38'. "#EC *
*MOD-005
RANGES:
 R_MESTYP FOR EDIDC-MESTYP, "#EC *
 R_CREDAT FOR EDIDC-CREDAT, "#EC *
 R_CRETIM FOR EDIDC-CRETIM, "#EC *
 R_SNDPRT FOR EDIDC-SNDPRT, "#EC *
 R_SNDPRN FOR EDIDC-SNDPRN. "#EC *
DATA:
 L_MESSTYPE TYPE TUMLS_MESSTYPE. "#EC *
*MOD-005
data: p_sndprn TYPE EDI_SNDPRN, "#EC *
 p_sndprt TYPE EDI_SNDPRT, "#EC *
 p_sndpor TYPE EDI_SNDPOR. "#EC *
data: p_rcvprn TYPE EDI_RCVPRN, "#EC *
 p_rcvprt TYPE EDI_RCVPRT, "#EC *
 p_rcvpor TYPE EDI_RCVPOR. "#EC *
data:
init_E1CUVTM type E1CUVTM, "#EC *
prev_E1CUVTM type E1CUVTM, "#EC *
init_E1DATEM type E1DATEM, "#EC *
prev_E1DATEM type E1DATEM, "#EC *
init_E1CUV1M type E1CUV1M, "#EC *
prev_E1CUV1M type E1CUV1M. "#EC *
Source structure definitions
data:
begin of LSMW_TAB_CONTENT, "#EC *
 VTNAM(018) type C,
 CHAR1(030) type C,
 CHAR2(030) type C,
 CHAR3(030) type C,
 CHAR4(030) type C,
 CHAR5(030) type C,
 CHAR6(030) type C,
 CHAR7(030) type C,
 CHAR8(030) type C,
 CHAR9(030) type C,
 CHAR10(030) type C,
 CHAR11(030) type C,
 CHAR12(030) type C,
 CHAR13(030) type C,
 CHAR14(030) type C,
 CHAR15(030) type C,
 FLAG(001) type C,
end of LSMW_TAB_CONTENT.
Counters
data:
g_cnt_VAR_TAB type i, "#EC *
g_cnt_TAB_CONTENT type i. "#EC *
Counter ct_xxxxxxxxxx: number of transferred records
data:
ct_edi_dc40 type i, "#EC *
cs_edi_dc40 type i, "#EC *
ct_E1CUVTM type i, "#EC *
cs_E1CUVTM type i, "#EC *
ct_E1DATEM type i, "#EC *
cs_E1DATEM type i, "#EC *
ct_E1CUV1M type i, "#EC *
cs_E1CUV1M type i. "#EC *
Global data definitions and data declarations
DATA: wa_cabn TYPE ty_cabn,
 wa_cawn TYPE ty_cawn,
 wa_file TYPE ty_file,
 wa_vtnam TYPE ty_vtnam,
 wa_cuvtab_fld TYPE ty_cuvtab_fld,
 wa_cuvtab_valn TYPE ty_cuvtab_valn,
 wa_cuvtab_valc TYPE ty_cuvtab_valc,
 wa_col_pos TYPE ty_col_pos,
 wa_error TYPE ty_error,
 wa_dupl TYPE ty_dupl,
 wa_dupl_file TYPE ty_dupl.
DATA: wa_vnt_ma TYPE ty_vnt_ma,
 wa_split TYPE ty_split.
DATA: wa_charval TYPE ty_charval. "#EC *
Internal table
DATA: i_cabn TYPE STANDARD TABLE OF ty_cabn, "#EC *
 i_cabn_temp TYPE STANDARD TABLE OF ty_cabn, "#EC *
 i_cabn_atinn TYPE STANDARD TABLE OF ty_cabn, "#EC *
 i_file TYPE STANDARD TABLE OF ty_file, "#EC *
 i_file_tmp TYPE STANDARD TABLE OF ty_file, "#EC *
 i_vtnam TYPE STANDARD TABLE OF ty_vtnam, "#EC *
 i_cuvtab TYPE STANDARD TABLE OF ty_vtnam, "#EC *
 i_cuvtab_fld TYPE STANDARD TABLE OF ty_cuvtab_fld, "#EC *
 i_cuvtab_valn TYPE STANDARD TABLE OF ty_cuvtab_valn, "#EC *
 i_cuvtab_valc TYPE STANDARD TABLE OF ty_cuvtab_valc, "#EC *
 i_col_pos TYPE STANDARD TABLE OF ty_col_pos, "#EC *
 i_cawn TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cawn_n TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cawn_c TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cawn_i TYPE STANDARD TABLE OF ty_cawn, "#EC *
 i_cuv_error TYPE STANDARD TABLE OF ty_vtnam, "#EC *
 i_dupl TYPE STANDARD TABLE OF ty_dupl. "#EC *
DATA: i_vnt_ma TYPE STANDARD TABLE OF ty_vnt_ma, "#EC *
 i_split TYPE STANDARD TABLE OF ty_split. "#EC *
DATA: i_dupl_file TYPE STANDARD TABLE OF ty_dupl. "#EC *
DATA: i_charval TYPE STANDARD TABLE OF ty_charval. "#EC *
Constants
CONSTANTS: c_char TYPE atfor VALUE 'CHAR', "#EC *
 c_date TYPE atfor VALUE 'DATE', "#EC *
 c_time TYPE atfor VALUE 'TIME', "#EC *
 c_varcond TYPE atnam VALUE 'Z_VARCOND'. "#EC *
Field Symbols
FIELD-SYMBOLS: TYPE ANY.
Variables
DATA: g_raw(500) TYPE c, "#EC *
 g_invalid TYPE char1, "#EC *
 g_error TYPE char1, "#EC *
 g_message TYPE char50, "#EC *
 g_slnid_c TYPE slnid, "#EC *
 g_slnid_n TYPE slnid, "#EC *
 g_row TYPE char5. "#EC *
DATA: g_varcond TYPE varcond, "Variant condition "#EC NEEDED
 g_split_var TYPE i. "#EC *
Types: begin of ty_charname,
 name type atnam,
 end of ty_charname.
data: wa_charname type ty_charname, "#EC *
 i_charname type standard table of ty_charname. "#EC *
data: cnt_i type i, "#EC *
 g_tabix type char10. "#EC *
Types: begin of ty_itab_zedidc40.
 include structure edi_dc40.
TYPES: end of ty_itab_zedidc40.
Types: begin of ty_itab_zedidd40.
 include structure edi_dd40.
TYPES: end of ty_itab_zedidd40.
DATA: itab_zedidc40 type standard table of
 ty_itab_zedidc40 initial size 0. "#EC *
DATA: itab_zedidd40 type standard table of
 ty_itab_zedidd40 initial size 0. "#EC *
DATA: wa_itab_zedidc40 type ty_itab_zedidc40.
DATA: wa_itab_zedidd40 type ty_itab_zedidd40.
*MOD-009
data: itab_ze1cuvtm type e1cuvtm, "#EC *
 itab_ze1datem type e1datem, "#EC *
 itab_ze1cuv1m type e1cuv1m. "#EC *
data: wdocnum(16) type n value 0. "#EC *
data: wsegnum(6) type n value 0. "#EC *
data: witemno(10) type n value 0. "#EC *
data: witemno_new(10) type n value 0. "#EC *
data: witemno_gst(10) type n value 0. "#EC *
data: witemno_qst(10) type n value 0. "#EC *
TYPES: BEGIN OF ty_input_data1, "#EC *
 line(560) type c,
 flag(1) type c,
 END OF ty_input_data1.
DATA: i_input_data type standard table of
 ty_input_data1 initial size 0. "with header line.
DATA: i_input_data1 type standard table of
 ty_input_data1 initial size 0. "with header line.
DATA: wa_input_data type ty_input_data1. "#EC *
DATA: g_cnt_input_recs type i. "#EC *
DATA: g_flg_error type c. "#EC *
DATA: l_lines type i. "#EC *
DATA: l_tabix type i. "#EC *
DATA: wa_input_data1 type ty_input_data1. "#EC *
DATA: FILE TYPE STRING.
Fields that are made available to the user:
DATA:
g_cnt_records_read TYPE i, "#EC *
g_cnt_records_transferred TYPE i, "#EC *
g_cnt_transactions_read TYPE i, "#EC *
g_cnt_transactions_transferred TYPE i, "#EC *
g_cnt_idocs_package TYPE i. "#EC *
data: v_log_handle type balloghndl. "#EC *
DATA: gt_curr_edi_dc40 TYPE STANDARD TABLE OF edi_dc40 initial size 0."#EC *
DATA: gt_curr_edi_dd40 TYPE STANDARD TABLE OF edi_dd40 initial size 0."#EC *
DATA: wa_curr_edi_dc40 TYPE edi_dc40. "#EC *
DATA: wa_curr_edi_dd40 TYPE edi_dd40. "#EC *
internal table for error messages during conversion
DATA: g_error_tab TYPE type_errortab, "#EC *
 wa_errortab TYPE type_errorline. "#EC *
DATA: g_edidd_segnam type EDI4SEGNAM, "#EC *
 g_edidd_hlevel type EDI4HLEVEC. "#EC *
DATA: g_segnum(6) TYPE n.
DATA: g_objecttype(2) type C.
DATA: P_FNAME(128) TYPE C VALUE '/usr/sap/trans/vartabheader'. " MODIF ID MD1 OBLIGATORY.
DATA: P_FNAME1(128) TYPE C VALUE '/usr/sap/trans/vartabcontent'. " MODIF ID MD1 OBLIGATORY.
DATA: alv_fldcat TYPE slis_t_fieldcat_alv,
 it_fldcat TYPE lvc_t_fcat.
field-symbols: .
data: dy_table type ref to data,
 dy_line type ref to data,
 xfc type lvc_s_fcat,
 ifc type lvc_t_fcat.
data: l_wa_data TYPE TY_CONTENT,
 itab_data TYPE standard table of TY_CONTENT.
DECLARATION FOR SELECTION SCREEN
*selection-screen skip 1.
*For all the input field entries
SELECTION-SCREEN BEGIN OF BLOCK bl1 WITH FRAME TITLE text-001.
*Parameter for Input File Name:
PARAMETERS: p_inpt TYPE RLGRAP-FILENAME MODIF ID MOD . " Presentation server File Variant table
PARAMETERS: p_inpt1 TYPE RLGRAP-FILENAME MODIF ID MOD . " Presentation server File variant Content
SELECTION-SCREEN END OF BLOCK bl1.
IDoc creation
selection-screen begin of block idocpars
 with frame title text-006.
parameters:
 p_trfcpt as checkbox default C_X MODIF ID MD3,
 p_packge(5) type n default 1 MODIF ID MD3.
selection-screen end of block idocpars.
SELECTION-SCREEN BEGIN OF BLOCK bl3 WITH FRAME TITLE text-032.
Radio Buttons :
parameters:
rb_apsrv RADIOBUTTON GROUP RB1 DEFAULT 'X' USER-COMMAND UCOM,
rb_convt RADIOBUTTON GROUP RB1,
rb_idoc RADIOBUTTON GROUP RB1,
rb_proc RADIOBUTTON GROUP RB1.
SELECTION-SCREEN END OF BLOCK bl3.
INITIALIZATION
INITIALIZATION.
Check selection-screen entries *
*AT SELECTION-SCREEN.
PERFORM sub_get_physical_file USING p_fpath p_fname.
PERFORM sub_get_physical_file1 USING p_fpath1 p_fname1.
AT SELECTION SCREEN
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
PERFORM sub_get_file. " CHANGING p_fname. "#EC *
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname1.
PERFORM sub_get_file1. " CHANGING p_fname1. "#EC *
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_INPT.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 STATIC = C_X
 CHANGING
 FILE_NAME = P_INPT
 EXCEPTIONS
 MASK_TOO_LONG = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
 MESSAGE e241.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_INPT1.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 STATIC = C_X
 CHANGING
 FILE_NAME = P_INPT1
 EXCEPTIONS
 MASK_TOO_LONG = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
 MESSAGE e241.
ENDIF.
At Selection Screen Output
AT SELECTION-SCREEN OUTPUT.
IF rb_apsrv = 'X'.
 LOOP AT SCREEN.
 IF SCREEN-GROUP1 = c_mod.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md2.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md3.
 SCREEN-INPUT = 0.
 ENDIF.
 MODIFY SCREEN.
 ENDLOOP.
endif.
IF rb_apsrv = 'X'.
LOOP AT SCREEN.
 IF SCREEN-GROUP1 = c_md1.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md2.
 SCREEN-INPUT = 0.
 ENDIF.
 IF SCREEN-GROUP1 = c_md3.
 SCREEN-INPUT = 0.
 ENDIF.
 MODIFY SCREEN.
ENDLOOP.
endif.
START-OF-SELECTION
START-OF-SELECTION.
*Subroutines for start of selection event
PERFORM sub_start_selection.
IF rb_apsrv = 'X'.
 PERFORM sub_upload_data_app.
 MESSAGE i256.
 LEAVE LIST-PROCESSING.
 EXIT.
ELSE.
 PERFORM sub_upload_data.
ENDIF.
PERFORM sub_upload_data.
Get characteristic details
PERFORM sub_get_cabn.
Get value for characteristics
PERFORM sub_get_cawn.
perform sub_convert_transaction.
END-OF-SELECTION.
END OF SELECTION
*MOD-012
Final message
perform sub_final_message_idoc.
Display errorneous variant tables.
perform sub_display_variant.
Display lines with incorrect data
perform sub_display_errorlines.
*Subroutines for end of selection event
PERFORM sub_end_selection.
perform sub_clear_source_tables.
*MOD-012
*& Include /FACTGLB/GTDMI_VARTAB_FORMS02 *
*& Include /FACTGLB/GTDMI_VARTAB_FORMS02 *

Error Occured when Applying Structural Authorizations in E-Recruitment

Dear Experts,
The E-Recruitment functionalities were working fine when no structural authorizations are applied. However, when structural authorizations are configured for the user on the backend SAP system (I configured structural authorizations for the user to have access to only his own department), the E-Recruitment module does not work.
When I tried to access requisitions-> maintenace, application management->applications, etc, (i.e. when the E-Recruitment module tries to retrieve data from the backend), the the following error message occurred.
Error when processing your request
What has happened?
The URL http://<hostname>:<port>/sap/bc/bsp/sap/hrrcf_start_int/application.do was not called due to an error.
Note
The following error text was processed in the system ABC : RAISE EVENT statement nested to deep. The error occurred on the application server XYZ and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: ON_CHANGE of program CL_HRRCF_INFOTYPE=============CP
Method: INSERT_RECORD of program CL_HRRCF_INFOTYPE=============CP
Method: READ_RECORDS of program CL_HRRCF_REQUISITION_INFO=====CP
Method: GET_RECORDS of program CL_HRRCF_INFOTYPE=============CP
Method: GET_RECORDS_BY_DATE of program CL_HRRCF_INFOTYPE=============CP
Method: ON_REQUISITION_UPDATE of program CL_HRRCF_REQUI_BL=============CP
Method: ON_CHANGE of program CL_HRRCF_INFOTYPE=============CP
Method: INSERT_RECORD of program CL_HRRCF_INFOTYPE=============CP
Method: READ_RECORDS of program CL_HRRCF_REQUISITION_INFO=====CP
Method: GET_RECORDS of program CL_HRRCF_INFOTYPE=============CP
Please advice if E-Recruitment supports structural authorizations. If it does, are there additional configuration required to enable structural authorization. Kindly enlighten me on how to resolve this error. Any help will be much appreciated.

Hello Louis,
I implemented e-recruiting with structural authorizations for a customer and encountered exactly the same error. Anything in the e-recruiting implementation leads to this problem. When you miss some object authorizations the implementation generates an infinite callstack which results in this short dump.
So be sure you assigned all necessary objects to recruiters and also candidates (NA, NB, NC, ND, NE, NF, BP, CP, P, Q, QK, VA, VB, VC) but this might be difficult esp. with the P object, when you use structural authorizations for other purposes, too. This usually generates problems in manager involvement (e.g. manager can't choose a recruiter to approve his requisition as he has not the structural authorization for the hr department members).
It is also a bit strange that candidates need for example change rights for the requisition (NB) although they won't actually change it but without it the relation application->requisition, candidacy->requsition cannot be created correctly.
Last but not least be always sure that you refreshed the authorization buffers after changing structural authorizations. They are usually switched on for better performance.
Best regards
Roman Weise
PS: be aware that using structural authorizations will keep you busy for some time. we needed ~2 months to set up the system in a way that e-recruiting worked as the custoimer wanted without interfering any other productive hr component (admin, org. mgmnt., managers desktop).

Control Workflow Report output using Structural Authorization

Is it possible to control output of Workflow Reports using Structural Authorizatins. E.g. Workflow Admins having access to tcode SWi2_FREQ will be able to see project wide data, but i want to restrict the workflow admins at department level from seeing workflow data for other departments. is that possible using Structural authorizations or any other mechanism?
My understanding is that Structural authorizations pretty much control PA/PD, and not other modules. I did a quick test,
1) Created a org structure
2) Created employees, users, and set up structural authorizations
Now when users are granted authorization to PA20, they are restricted to what they should be seeing, but when they are granted authorization for workflow admin reports, structural authorization don't seem to work, they are able to see data for workflow triggered for other departments as well. Is that the standard behavior or i am missing something. I don't have enough experience with Structural auth.
I will appreciate any guidance on this matter.
Thanks,
Saurabh

Arghadip, please explain how this will prevent someone from Norway from looking at the workflow log of a workflow for an employee belonging to the Danish part of the organisation.
Message was edited by Kjetil Kilhavn:
To explain a bit more in detail: how does this prevent me (Norwegian) from going into SWI1, SWIA or any other transaction, and looking at data from other parts of the organisation. I don't think it will work.
I think the only way to achieve this is to either modify SAP's standard code and include some structural authorisation checks - or take the standard transactions out from every user role and create your own wrappers or program copies which basically does the same as the modification would have to do.

BW/HR structural authorization in BI 7.0 version

Dear experts,
Can anyone please explain how to extract HR structural authorization from R/3 to BW 7.0, and how to configure the authorization in the BW, I hope everyone can give me a work flow.
Thanks.

Hi Auke, thanks for your answer.
Changes inside the user profile are working, but deletion don't. And yes, the meaning of this is that user should not have role anymore.
I saw help documents with some procedure using D_E_L_E_T_E user. I didn't understand. Do you know something about that? Is that maybe the right way?
Thanks,
Thiago

MSS genericiview and R/3 structural authorizations

Hi,
I have created some iViews based on par-file "eeprofilegenericiviewtable" to display R/3-queries. In R/3 we use also structural authorizations for the managers with functional module RH_GET_MANAGER_ASSIGNMENT.
The structural authorization is working in R/3 for a selected manager selecting a query directly from the R/3 via SQ01, but it doesn't in the iview. When the same user is viewing the "query"-iview, the message "No data selected" appears.
When I assign the user a structural authorization without the functional module RH_GET_MANAGER_ASSIGNMENT, e.g. only with some object types, the user can retrieve data without any problem using "query"-iview.
Probably the problem is in the functional module HR_INFO_GET_USING_QUERY used for retrieving R/3 query data from the portal and used by the iview eeprofilegenericiviewtable.
Has anybody met a similar problem? We are using EP6.0 SP14 and SAP R/3 4.6C.
Beata

Hi Dwayne (and others!),
Were facing similar problems with the error message "R3_CONNECT_FAILED". However, our difficulties are a bit strange because i only occurs on one of our two server nodes. We're running SAP EP 6.4, SP9.
Previously, we've had problems with the maximum number of connections towards our backend system, SAP R/3. But setting the environment variable CPIC_MAX_CONV helped us.
However, now we get the above error, but only on one of our server nodes. Do you (or anyone else) have any suggestions as to what might be wrong?
Thanks in advance,
Rasmus

SAP BI 7.0 Transport issue with HR Structural Authorization DSO

Hi,
I am trying to transport HR Structural Authorization DSO Objects in BI 7.0 from Dev to QA system. The Data sources are 0PA_DS02 and 0PA_DS03. ( I am sure that there are lots of changes in Authrorization concept in BI 7.0),.
1. Please suggest me if I need to make any changes and tests before moving these authorization objects to QA system.
2. Also, do I need to take any pre-cautions while activating business content objects 0TCTAUTH and 0TCTAUTH_T (Datasources look like are from 3.x) as I am getting issue with the activation of the transfer structure for these objects?
Thanks a lot for your valuable inputs.
Regards
Paramesh
Edited by: paramesh kumar on May 5, 2009 12:45 AM

Hi Paramesh.
You can use the DSOs 0PA_DS02 and 0PA_DS03 in BI7.0 as well. You just need to use the new generation of analysis authorizations in transaction RSECADMIN.
You can use 0TCTAUTH and 0TCTAUTH_T in BI7.0, however we have experienced som problems with the 0TCTAUTH_T extractor, which dumped because of a poorly designed SELECT statement that was unable to cope with 10000 records. We have replaced it with a generic data source that uses table RSECTEXT directly.
Regards,
Lars

Regarding structure of abap program

hi,
can any one exaplain to me what is the structure of the abap program.
thank&regards,
ramnaresh

Hi..
This is the Structure of ABAP program.
REPORT <NAME>.
**Global Data definitions
TYPES:
DATA:
**Selection Screen Definition
SELECT-OPTIONS
PARAMETERS
**Event Blocks
INITIALIZATION .
 perform X.
START-OF-SELECTION.
 perform Y.
****Form routines definition
FORM X.
ENDFORM.
FORM Y.
ENDFORM.
<REMOVED BY MODERATOR>
Message was edited by:
 Alvaro Tejada Galindo

Structure of ABAP program

hi SDNs,
           what is the typical structure of an ABAP program?
           thanks and regards,
               aravind.

hi
plz check the structure of ABAP Program under..
http://help.sap.com/saphelp_47x200/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/frameset.htm
below the typical structure...
1.data declaration
2.selection-screen declartion
3.data validation
4.output.
Cheers
Abdul Hakim

R/3 reports related to structural authorization

Can anyone advise which standard reports/transcation codes in R/3 relate to structural authorization? are some better than others? I am interested in viewing allowable objects etc,.
Thank you,
Meghan

Hi Jim,
As you have mentioned you have worked a lot on structural authorizations,
I would request you to kindly help us on the below mentioned scenerio..
Issue : (Scenario)
C directly reports to B, and B Reports to A.
In the above scenario we have logged as B and did the compensation planning for C. A is the approver for the Cs compensation planning.
As C is HOD for HR Org unit. He will submit compensation plans of his subordinates to B for approval. That means B has to have approval authorization for Cs subordinates and he should not have approval authorization for his direct reporting employees.
In our scenario, B is able to perform the compensation planning as well as able to approve the same for his direct reporting employees. This shouldnt happen in our process.
How can achieve this, Please advice
Regards
Raghav

HR Structural Authorization DSO's

Hi,
I have developed HR module for the first time. I need to create the authorization objects for the HR reports.
I found 0PA_DS02 and 0PA_DS03 for structural authorizations in HR. I dont understand the purpose of these DSO's.
Can some one explain what is purpose of the 0PA_DS02 and 0PA_DS03 dso's and how to create authorizations in HR?
Thanks and Regards,
Pooja

HI Pooja,
Use "Rsecadmin" create a authorization object and in that click on the below tool bar infocube authorizations which gives you a option to choose the infoprovider either cube or dso .choose your dso and then navigate around according to your requirements with include option.
I think you need to load the DSO 0TCA_DS01 for Authorization Data(Values). Activate this DSO and try loading the data into this DSO as well and then try to generate the authorizations from this
Thank you

Context sensitive solution for Structural authorization

Dear all,
I would like to know whether new relationship, evaluation path and authorization profile has to be created for each role with context sensitive structural authorization ?
In T77UA table, each user has assigned a profile which tells the system how to find the structure by evaluation path (in T77PR table). Then in tranx OOAW, the evaluation path indicate how to build the structure by series of relationship, and this way we have to create new relationship for each role with context.
Am i correct ?
If an organization has many roles, then many relationship, evaluation path, profile.. has to be created !
Thanks for your help !
patrick cheung

Hi Chandra,
Thanks for your prompt reply !
This is for Context Sensitive solution, not the normal structural authorization:
Yes, if you add the authorization object P_ORGINCON in PFCG, you will notice that the field "Authorization Profile" has to be entered which tells the system WHICH ORG STRUCTURE does this authorization are refering to...
In table T77PR, instead of hardcoding the organization unit in the object ID field, we use Evaluation path to tell the system how to find the org structure for employees. Function RH_GET_MANAGER_ASSIGNMENT will return the org unit ID for the evaluation path.
In transaction OOAW, the said evaluation path specified the relationships which the system should use to draw the org structure of the employee's supervision... and there should be relationship like "Is managed by", may be as follows:
O B 002 Is line supervisor of * O
O A 011 Cost center asignmnt * K
O B 003 Incorporates * S
O B 012 Is managed by... * S
Up to now.... if you want to assign authorization to someone as follows, you could not simply maintain the same relationship "Is managed by" to Org Structure A and B because this will confuse the system as to which org structure you want the employee to maintain infotype 7 or 14/15. You should then create different relationships and maintain them to Org Structure A and B. And tell the system how to find the structure from the Evaluation path, which is stick to the Auth. profile. The Auth. profile is then maintain in the Context sensitive master data object P_ORGINCON !
(1)
Org Structure A
Maintain only infotype 7
(2)
Org Structure B
Maintain only infotype 14, 15
So... that's why i said if an employee has many role to perform duties in many different Org Structures (e.g. A, B, C...etc), you would create many relationship...
Hope this message will give idea to someone who intend to implement Context Sensitive Solution.

Structural Authorization Indexing Programs

Similar Messages

Maybe you are looking for