Urgent Error in Displaying Hierarchy in Bex- like not assigned Material

Hi Gurus,
plz solve my problem like displaying Hierarchy in Bex ,
I loaded hierarchy from R/3 system into Bw 0Mterial.
In Bex 0material Properties I Selected heirachy on Material , this heirarchy having 8 levels,
but in the out put it showing only one level displayng
like Not Assigned Material.
i did all the bex setting well, but i dnot know why i am getting this ...
plz any one help..
Thanks in advance
Anil

hi,
Is your heirarchy uploaded properly for 0Material ?? If yes juct check out if your transcational data is in sync with the hierarchy master ? If it is not then it wuill display as Not Assigned..
Regards,

Similar Messages

Urgent Help plzzzzzzzzz Hierarchy in Bex displaying like Not Assigned Mater

Hi Experts,
plz solve my problem like displaying Hierarchy in Bex ,
I loaded hierarchy from R/3 system into Bw 0Mterial.
In Bex 0material Properties I Selected heirachy on Material , this heirarchy having 8 levels,
but in the out put it showing only one level displayng
like Not Assigned Material.
i did all the bex setting well, but i dnot know why i am getting this ...
plz any one help..
Thanks in advance
Anil

Hi Anil,
Your query is built on an infoprovider, right? The way the hierarchy is displayed depends on TRANSACTION DATA IN INFOPROVIDER. To display the hierarchy normally you need to have in the provider not blank values of the characteristics you used in the query and not blank material code. Unassigned node means that this requirement doesn't met.
If would be much more useful if you describe what you have in the query and what - in the provider.
Best regards,
Eugene

Cause is mentioned as : "The cause for this error is due to person name is not assigned to the FND_USER."

Cause is mentioned as : "The cause for this error is due to person name is not assigned to the FND_USER."
Do we need to attach the person name of employee whose reverse Global deployment we are doing or the person name of the person who is doing this transaction.
Thanks & Regards,
Kirti Mohan Sharma

You just need to attach the person to the FND User. System Administrator responsibility - Security - User screen.
After you have linked the person, you can check the table
Select * from FND_USER
Where user_name = '<user_name>';
Cheers,
Vignesh

Display attribute incorrectly reported as "not assigned" in BEX Analyser

Hi SCN
I have a simple BEX query on a master data infoobject which displays the object key and several display attributes. One of the attributes is often reported incorrectly as "not assigned" although the behaviour is erratic and can sometimes be correct from day to day. I have checked the master data table and there should be a value ... when I run the report in RSRT, the attribute is correctly reported !
I have checked the infoobject in RSRV for errors (all lights are green), deleted the cache and set the report to not use caching in RSRT but the attribute is still frequently "not assigned"
all very weird ... any thoughts ?
regards
Ian

Hi Ram
no error as such, the report displays the attribute as "not assigned" ... this image shows the query and the RSRT output
regards
Ian

Error Message while ship to party is not assigned to sold to party in VA01

Hi All,
In VA01, i need to throw an error message while giving a ship to party, which is not assigned to sold to party.
I tried in EXIT_SAPLV09A_001
              EXIT_SAPLV09A_002
              EXIT_SAPLV09A_003
              EXIT_SAPLV09A_004
above user exits, but i couldnt find the solution.
if possible provide with the code.
i appericiate the early response.
Regards,
Kumar.

User exit MV45AFZB, form-routine USEREXIT_CHECK_VBAK.

Urgent: Error while displaying data in OBIEE answers

Hi,
I'm facing an issue in OBIEE answers when trying to display values from my fact table. It is displaying something like invalid column identifier in oci call stmt execute...
I have three dimensions and that particular column is in three dimensional tables and i changed the names and placed in fact table.
when i'm trying to view data in physical layer it is displaying data.
why i'm facing this error.. How can I resolve this??
Its very urgent requirement and any help will be appreciable..
Regards,
Sindhu

Hi,
I changed the column names in BMM only. Not in physical layer. In physical layer i'm able to view data.
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 17001] Oracle Error code: 904, message: ORA-00904: "T95877"."OBSERVATION_DATETIME": invalid identifier at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed. (HY000)
SQL Issued: SELECT "FACT - RISK SLOT Overtime"."In Gas Price Value ID" saw_0 FROM "AO Risk" ORDER BY saw_0
I'm getting this error...
Regards,
Sindhu

Error while Displaying Heirarchy in Bex Report

Hi All,
plz Solve my problem,
In the report Heirarchy displaying like notAssignedmaterial with one level, but my Heirarchy contain 8 levels.
Plz Guide me
Thanks in Advance
Anil

Hi Anil,
Please run the Heirarchy attribute change run. It may give u the desired solution.
Administrator workbench-menubar Tools- apply hierarchy attribute change run.
after doing this run the query and check if the values are coming.
Hope it would help u
Mohan

Urgent Page Navigation display the file naming like 03_02.JPG

Hi All,
I have received the pdf file from my client, he make the some tricks in the pdf file name showing in the page navigation bar, how they done this display, please find the below snapshots for your referecne.
1. see the pag navigation tab shownin the 03_00C0.jpg beside the (1/54) this is the 1st page.
2. this page also shown the file name in the page navigation tab this page is 2nd 03_01.jpg actual page is (2/54)
Please help me how to do this and get the same display of the page navigation tab showing the file name like photos.1jpg or 05-115.tiff.
i have more than 200 jpg file how to make like this. Please help this is very urgent. I can't ask this to my client.
System Configuration:
I am using Acrobat Pro 9 in Mac OS 10.5.6.
thx
csm_phil

It may not be easy but you will have to use the Page Numbering dialog by right clicking on the page in the Pages thumbnails and enter the file name as the page number like this

Error in Displaying date in BEx

Hi,
I've created a Key figure based on calday. It has exception aggregation as 'Last Value' based on calday.
When I'm using it in a query It turns the date to 'mm/dd/yyyy' where ever possible.
e.g if a date is '03/09/2007' it shows it as '09/03/2007' but if it is '13/09/2007' it is showing it fine. I also put calday next to this KF and calday is working fine. it is showing date correctly (dd/mm/yyyy). All the data is loaded correctly and cube is having the KF correctly. When I run the same query in web KF is working fine. Its only in BEx it is having a problem. Can anyone, please tell me how to resolve this issue. If it is a bug of BEx then where can I find the patch.
My current BEx version is 3555.3.016
Regards
Tarun

I have the same problem !
I have Bex Analyzer 7.0 Package 3 and the days and months are switched if possible (01/10/2007 becomes 10/01/2007 but 30/10/2007 stays the same). I also noticed that the problem doesn't occur with Bex analyzer 7.0 package 2 and in my portal, the dates are also correct. If i do calculations with the dates (to get the difference), the results are correct.
For example:
in the portal it shows: date1 = 01/10/2007 and date2 = 02/10/2007 => the calculated difference is 1
in the analyzer it shows: date1 = 10/01/2007 and date2 = 10/02/2007 => the calculated difference is 1.
I checked my configurations and the only difference on the 2 computers is a different package (2 vs 3).
Anyone has an idea??
Kind regards

Urgent: Error-Record 39,779, segment 0001 is not in the cross-record table

Hi Gurus,
This is an urgent production issue: I got the following error-
I am updating data records from a DSO to Infocube in delta mode,
1.Record 39,779, segment 0001 is not in the cross-record table
2.Error in substep: End Routine
I dont know problem is in the End Routine or somewhere else,
The End routine is this:
PROGRAM trans_routine.
      CLASS routine DEFINITION
CLASS lcl_transform DEFINITION.
PUBLIC SECTION.
Attributs
    DATA:
      p_check_master_data_exist
            TYPE RSODSOCHECKONLY READ-ONLY,
*-    Instance for getting request runtime attributs;
    Available information: Refer to methods of
    interface 'if_rsbk_request_admintab_view'
      p_r_request
            TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
PRIVATE SECTION.
    TYPE-POOLS: rsd, rstr.
Rule specific types
    TYPES:
      BEGIN OF tys_TG_1,
     InfoObject: ZVEHICLE Unique Vehicle ID.
        /BIC/ZVEHICLE           TYPE /BIC/OIZVEHICLE,
     InfoObject: ZLOCID Mine Site.
        /BIC/ZLOCID           TYPE /BIC/OIZLOCID,
     InfoObject: ZLOCSL Location Storage Location.
        /BIC/ZLOCSL           TYPE /BIC/OIZLOCSL,
     InfoObject: 0VENDOR Vendor.
        VENDOR           TYPE /BI0/OIVENDOR,
     InfoObject: ZNOMTK Nomination Number.
        /BIC/ZNOMTK           TYPE /BIC/OIZNOMTK,
     InfoObject: ZNOMIT Nomination Item.
        /BIC/ZNOMIT           TYPE /BIC/OIZNOMIT,
     InfoObject: ZNOMNR Nomination number.
        /BIC/ZNOMNR           TYPE /BIC/OIZNOMNR,
     InfoObject: ZVSTTIME Vehicle Starting Time Stamp.
        /BIC/ZVSTTIME           TYPE /BIC/OIZVSTTIME,
     InfoObject: ZVEDTIME Vehicle Ending Time Stamp.
        /BIC/ZVEDTIME           TYPE /BIC/OIZVEDTIME,
     InfoObject: ZNETWT Net Weight.
        /BIC/ZNETWT           TYPE /BIC/OIZNETWT,
     InfoObject: TU_GRS_WG Gross Wgt.
        /BIC/TU_GRS_WG           TYPE /BIC/OITU_GRS_WG,
     InfoObject: ZTU_TRE_W Tare Wgt.
        /BIC/ZTU_TRE_W           TYPE /BIC/OIZTU_TRE_W,
     InfoObject: ZCUSTWT Customer Weight.
        /BIC/ZCUSTWT           TYPE /BIC/OIZCUSTWT,
     InfoObject: ZCAR_NO Car Number.
        /BIC/ZCAR_NO           TYPE /BIC/OIZCAR_NO,
     InfoObject: ZINBND_ID Train Consist Inbound ID.
        /BIC/ZINBND_ID           TYPE /BIC/OIZINBND_ID,
     InfoObject: ZOTBND_ID Train Consist Return Load.
        /BIC/ZOTBND_ID           TYPE /BIC/OIZOTBND_ID,
     InfoObject: 0SOLD_TO Sold-to Party.
        SOLD_TO           TYPE /BI0/OISOLD_TO,
     InfoObject: 0CUSTOMER Customer Number.
        CUSTOMER           TYPE /BI0/OICUSTOMER,
     InfoObject: 0SHIP_TO Ship-To Party.
        SHIP_TO           TYPE /BI0/OISHIP_TO,
     InfoObject: ZVEHI_NO Vehicle Number.
        /BIC/ZVEHI_NO           TYPE /BIC/OIZVEHI_NO,
     InfoObject: ZCARSTDAT Car Start Date.
        /BIC/ZCARSTDAT           TYPE /BIC/OIZCARSTDAT,
     InfoObject: ZCAREDDAT Car End Date.
        /BIC/ZCAREDDAT           TYPE /BIC/OIZCAREDDAT,
     InfoObject: ZCARSTTIM Car Start Time.
        /BIC/ZCARSTTIM           TYPE /BIC/OIZCARSTTIM,
     InfoObject: ZCAREDTIM Car End Time.
        /BIC/ZCAREDTIM           TYPE /BIC/OIZCAREDTIM,
     InfoObject: 0COMPANY Company.
        COMPANY           TYPE /BI0/OICOMPANY,
     InfoObject: ZCONTRACT Contract.
        /BIC/ZCONTRACT           TYPE /BIC/OIZCONTRACT,
     InfoObject: 0PLANT Plant.
        PLANT           TYPE /BI0/OIPLANT,
     InfoObject: ZLOADTIME Total Vehicle Loading time.
        /BIC/ZLOADTIME           TYPE /BIC/OIZLOADTIME,
     InfoObject: ZSHIPDATE Shipping Date.
        /BIC/ZSHIPDATE           TYPE /BIC/OIZSHIPDATE,
     InfoObject: ZSHIPTIME Shipping Time.
        /BIC/ZSHIPTIME           TYPE /BIC/OIZSHIPTIME,
     InfoObject: ZMNEDDT Manifest End Date.
        /BIC/ZMNEDDT           TYPE /BIC/OIZMNEDDT,
     InfoObject: ZMNEDTM Manifest End Time.
        /BIC/ZMNEDTM           TYPE /BIC/OIZMNEDTM,
     InfoObject: ZLDEDDT Loaded End Date.
        /BIC/ZLDEDDT           TYPE /BIC/OIZLDEDDT,
     InfoObject: ZLDEDTM Loaded End Time.
        /BIC/ZLDEDTM           TYPE /BIC/OIZLDEDTM,
     InfoObject: ZMANVAR Manifest Variance.
        /BIC/ZMANVAR           TYPE /BIC/OIZMANVAR,
     InfoObject: ZTU_TYPE Trpr Unit Type.
        /BIC/ZTU_TYPE           TYPE /BIC/OIZTU_TYPE,
     InfoObject: ZACTULQTY Actual posted quantity.
        /BIC/ZACTULQTY           TYPE /BIC/OIZACTULQTY,
     InfoObject: ZVEDDT Vehicle End Date.
        /BIC/ZVEDDT           TYPE /BIC/OIZVEDDT,
     InfoObject: ZVEDTM Vehicle End Time.
        /BIC/ZVEDTM           TYPE /BIC/OIZVEDTM,
     InfoObject: ZVSTDT Vehicle Start Date.
        /BIC/ZVSTDT           TYPE /BIC/OIZVSTDT,
     InfoObject: ZVSTTM Vehicle Start Time.
        /BIC/ZVSTTM           TYPE /BIC/OIZVSTTM,
     InfoObject: ZTRPT_TYP Vehicle type.
        /BIC/ZTRPT_TYP           TYPE /BIC/OIZTRPT_TYP,
     InfoObject: 0CALMONTH Calendar Year/Month.
        CALMONTH           TYPE /BI0/OICALMONTH,
     InfoObject: 0CALYEAR Calendar Year.
        CALYEAR           TYPE /BI0/OICALYEAR,
     InfoObject: ZLOEDDT Quality Sent End Date.
        /BIC/ZLOEDDT           TYPE /BIC/OIZLOEDDT,
     InfoObject: ZLOEDTM Quality sent End Time.
        /BIC/ZLOEDTM           TYPE /BIC/OIZLOEDTM,
     InfoObject: ZATMDDT At Mine End Date.
        /BIC/ZATMDDT           TYPE /BIC/OIZATMDDT,
     InfoObject: ZATMDTM At Mine End Time.
        /BIC/ZATMDTM           TYPE /BIC/OIZATMDTM,
     InfoObject: ZDELAY Delay Duration.
        /BIC/ZDELAY           TYPE /BIC/OIZDELAY,
     InfoObject: ZSITYP Schedule type.
        /BIC/ZSITYP           TYPE /BIC/OIZSITYP,
     InfoObject: ZDOCIND Reference document indicator.
        /BIC/ZDOCIND           TYPE /BIC/OIZDOCIND,
     InfoObject: 0BASE_UOM Base Unit of Measure.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
     InfoObject: 0UNIT Unit of Measure.
        UNIT           TYPE /BI0/OIUNIT,
     InfoObject: ZACT_UOM Actual UOM.
        /BIC/ZACT_UOM           TYPE /BIC/OIZACT_UOM,
     Field: RECORD.
        RECORD           TYPE RSARECORD,
      END   OF tys_TG_1.
    TYPES:
      tyt_TG_1        TYPE STANDARD TABLE OF tys_TG_1
                        WITH NON-UNIQUE DEFAULT KEY.
$$ begin of global - insert your declaration only below this line -
... "insert your code here
$$ end of global - insert your declaration only before this line   -
    METHODS
      end_routine
        IMPORTING
          request                  type rsrequest
          datapackid               type rsdatapid
        EXPORTING
          monitor                  type rstr_ty_t_monitors
        CHANGING
          RESULT_PACKAGE              type tyt_TG_1
        RAISING
          cx_rsrout_abort.
    METHODS
      inverse_end_routine
        IMPORTING
          i_th_fields_outbound         TYPE rstran_t_field_inv
          i_r_selset_outbound          TYPE REF TO cl_rsmds_set
          i_is_main_selection          TYPE rs_bool
          i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
          i_r_universe_inbound         TYPE REF TO cl_rsmds_universe
        CHANGING
          c_th_fields_inbound          TYPE rstran_t_field_inv
          c_r_selset_inbound           TYPE REF TO cl_rsmds_set
          c_exact                      TYPE rs_bool.
ENDCLASS.                    "routine DEFINITION
$$ begin of 2nd part global - insert your code only below this line *
... "insert your code here
$$ end of 2nd part global - insert your code only before this line   *
      CLASS routine IMPLEMENTATION
CLASS lcl_transform IMPLEMENTATION.
      Method end_routine
      Calculation of result package via end routine
      Note: Update of target fields depends on rule assignment in
      transformation editor. Only fields that have a rule assigned,
      are updated to the data target.
<-> result package
METHOD end_routine.
*=== Segments ===
    FIELD-SYMBOLS:
      <RESULT_FIELDS>    TYPE tys_TG_1.
    DATA:
      MONITOR_REC     TYPE rstmonitor.
*$*$ begin of routine - insert your code only below this line        *-*
Fill the following fields by reading Nomination and Vehicls DSO
SOLD_TO, Customer
data: L_TIMESTAMP1 TYPE timestamp,
      L_TIMESTAMP2 TYPE timestamp,
      L_TIMESTAMP3 type CCUPEAKA-TIMESTAMP,
      L_TIMESTAMP4 type CCUPEAKA-TIMESTAMP,
      L_TIMESTAMP5 type CCUPEAKA-TIMESTAMP,
      L_TIMESTAMP6 type CCUPEAKA-TIMESTAMP,
      L_TIMESTAMP7 TYPE timestamp,
      L_TIMESTAMP8 TYPE timestamp,
      L_TIMESTAMP9 type timestamp,
      L_TIMESTAMP10 type TIMESTAMP,
      L_CHAR1(14),
      L_CHAR2(14),
      l_duration type I,
      L_TS TYPE TZONREF-TZONE,
      l_flag,
      l_nomit TYPE /BIC/OIZNOMIT,
      l_error_flag.
l_TS = 'CST'.
Data: EXTRA_PACKAGE type tyt_TG_1.
data: extra_fields type tys_TG_1.
LOOP at RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
clear l_error_flag.
Get sold_to and customer from nomination table.
   Select single SOLD_TO /BIC/ZLOCSL /BIC/ZCONTRACT COMPANY
                 /BIC/ZMNEDDT /BIC/ZMNEDTM /BIC/ZLDEDDT
                 /BIC/ZLDEDTM SHIP_TO /BIC/ZACTULQTY
                 /BIC/ZLOEDDT /BIC/ZLOEDTM /BIC/ZDELAY
                 /BIC/ZATMDDT /BIC/ZATMDTM
                 /BIC/ZSITYP /BIC/ZDOCIND
           into (<RESULT_FIELDS>-SOLD_TO,
                 <RESULT_FIELDS>-/BIC/ZLOCSL,
                 <RESULT_FIELDS>-/BIC/ZCONTRACT,
                 <RESULT_FIELDS>-company,
                 <RESULT_FIELDS>-/BIC/ZMNEDDT,
                 <RESULT_FIELDS>-/BIC/ZMNEDTM,
                 <RESULT_FIELDS>-/BIC/ZLDEDDT,
                 <RESULT_FIELDS>-/BIC/ZLDEDTM,
                 <RESULT_FIELDS>-SHIP_TO,
                 <RESULT_FIELDS>-/BIC/ZACTULQTY,
                 <RESULT_FIELDS>-/BIC/ZLOEDDT,
                 <RESULT_FIELDS>-/BIC/ZLOEDTM,
                 <RESULT_FIELDS>-/BIC/ZDELAY,
                 <RESULT_FIELDS>-/BIC/ZATMDDT,
                 <RESULT_FIELDS>-/BIC/ZATMDTM,
                 <RESULT_FIELDS>-/BIC/ZSITYP,
                 <RESULT_FIELDS>-/BIC/ZDOCIND)
           from   /BIC/AZTSW_0000
           where /BIC/ZNOMTK = <RESULT_FIELDS>-/BIC/ZNOMTK
            AND /BIC/ZNOMIT = <RESULT_FIELDS>-/BIC/ZNOMIT.
Select Invalid Nominations
if sy-subrc <> 0.
    l_error_flag = 'X'.
endif.
   <RESULT_FIELDS>-customer = <RESULT_FIELDS>-SOLD_TO.
Prepare time stamp for Time Differences
Vehicle Starting Time Stamp
clear : L_TIMESTAMP9,L_TIMESTAMP10.
CONVERT DATE <RESULT_FIELDS>-/BIC/ZCARSTDAT TIME
               <RESULT_FIELDS>-/BIC/ZCARSTTIM
           INTO TIME STAMP L_TIMESTAMP9 TIME ZONE l_TS.
Vehicle Ending Time Stamp
CONVERT DATE <RESULT_FIELDS>-/BIC/ZCAREDDAT TIME
               <RESULT_FIELDS>-/BIC/ZCAREDTIM
           INTO TIME STAMP L_TIMESTAMP10 TIME ZONE l_TS.
Clear : L_TIMESTAMP3, L_TIMESTAMP4,
         <RESULT_FIELDS>-/BIC/ZVEDTIME,
         <RESULT_FIELDS>-/BIC/ZVSTTIME.
<RESULT_FIELDS>-/BIC/ZVEDTIME = L_TIMESTAMP10.
<RESULT_FIELDS>-/BIC/ZVSTTIME = L_TIMESTAMP9.
L_TIMESTAMP3 = L_TIMESTAMP10.
L_TIMESTAMP4 = L_TIMESTAMP9.
Caliculate the load time
IF L_TIMESTAMP3 is initial.
   clear <RESULT_FIELDS>-/BIC/ZLOADTIME.
elseif L_TIMESTAMP4 is initial.
   clear <RESULT_FIELDS>-/BIC/ZLOADTIME.
else.
   CALL FUNCTION 'CCU_TIMESTAMP_DIFFERENCE'
     EXPORTING
       timestamp1       = L_TIMESTAMP3
       timestamp2       = L_TIMESTAMP4
     IMPORTING
       DIFFERENCE        = <RESULT_FIELDS>-/BIC/ZLOADTIME
ENDIF.
Caliculate the Manifest Variance
   clear : L_TIMESTAMP5,L_TIMESTAMP6,L_TIMESTAMP7,L_TIMESTAMP8.
   CONVERT DATE <RESULT_FIELDS>-/BIC/ZMNEDDT TIME
                <RESULT_FIELDS>-/BIC/ZMNEDTM
           INTO TIME STAMP L_TIMESTAMP7 TIME ZONE l_TS.
   CONVERT DATE <RESULT_FIELDS>-/BIC/ZLDEDDT TIME
                <RESULT_FIELDS>-/BIC/ZLDEDTM
           INTO TIME STAMP L_TIMESTAMP8 TIME ZONE l_TS.
L_TIMESTAMP5 = L_TIMESTAMP7.
L_TIMESTAMP6 = L_TIMESTAMP8.
Caliculate the Maniefest Variance
IF L_TIMESTAMP5 is initial.
   clear <RESULT_FIELDS>-/BIC/ZMANVAR.
elseif L_TIMESTAMP6 is initial.
   clear <RESULT_FIELDS>-/BIC/ZMANVAR.
else.
   CALL FUNCTION 'CCU_TIMESTAMP_DIFFERENCE'
     EXPORTING
       timestamp1       = L_TIMESTAMP5
       timestamp2       = L_TIMESTAMP6
     IMPORTING
       DIFFERENCE        = <RESULT_FIELDS>-/BIC/ZMANVAR
   IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
   ENDIF.
ENDIF.
Delete datapackets with blank nominations
Delete datapackets with blank shipdate and Invalid Time Stamps
*IF <RESULT_FIELDS>-/BIC/ZNOMTK IS INITIAL OR
<RESULT_FIELDS>-/BIC/ZSHIPDATE IS INITIAL.
l_error_flag = 'X'.
*ENDIF.
<RESULT_FIELDS>-/BIC/ZVEHI_NO = 1.
<RESULT_FIELDS>-CALMONTH = <RESULT_FIELDS>-/BIC/ZSHIPDATE(6).
<RESULT_FIELDS>-CALYEAR = <RESULT_FIELDS>-/BIC/ZSHIPDATE(4).
if l_error_flag = 'X'.
Looks like Monitor Entries are not working in SP11.
Hence the following is commented temporarily.
CLEAR MONITOR_REC.
MONITOR_REC-MSGID = '0M'.
MONITOR_REC-MSGTY = 'S'.
MONITOR_REC-MSGNO = '501'.
MONITOR_REC-MSGV1 = <RESULT_FIELDS>-/BIC/ZNOMTK.
MONITOR_REC-recno = sy-tabix.
APPEND MONITOR_REC to MONITOR.
RAISE exception type CX_RSROUT_ABORT.
DELETE RESULT_PACKAGE index sy-tabix.
CLEAR L_ERROR_FLAG.
else.
   MODIFY RESULT_PACKAGE FROM <RESULT_FIELDS>.
endif.
clear l_nomit.
l_nomit = <RESULT_FIELDS>-/BIC/ZNOMIT.
extra_fields = <RESULT_FIELDS>.
Actual Qty and Contract details
   Select /BIC/ZLOCSL /BIC/ZNOMIT /BIC/ZCONTRACT /BIC/ZACTULQTY
          /BIC/ZSITYP /BIC/ZDOCIND
          SOLD_TO SHIP_TO COMPANY
           into (extra_fields-/BIC/ZLOCSL,
                 extra_fields-/BIC/ZNOMIT,
                 extra_fields-/BIC/ZCONTRACT,
                 extra_fields-/BIC/ZACTULQTY,
                 extra_fields-/BIC/ZSITYP,
                 extra_fields-/BIC/ZDOCIND,
                 extra_fields-SOLD_TO,
                 extra_fields-SHIP_TO,
                 extra_fields-company)
           from /BIC/AZTSW_0000
           where /BIC/ZNOMTK = <RESULT_FIELDS>-/BIC/ZNOMTK AND
                 /BIC/ZNOMIT <> l_NOMIT.
       INSERT extra_fields into table EXTRA_PACKAGE.
   endselect.
ENDLOOP.
Append lines of extra_package to RESULT_PACKAGE.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*-   to make monitor entries
... "to cancel the update process
   raise exception type CX_RSROUT_ABORT.
$$ end of routine - insert your code only before this line         -
ENDMETHOD.                    "end_routine
      Method inverse_end_routine
      This subroutine needs to be implemented only for direct access
      (for better performance) and for the Report/Report Interface
      (drill through).
      The inverse routine should transform a projection and
      a selection for the target to a projection and a selection
      for the source, respectively.
      If the implementation remains empty all fields are filled and
      all values are selected.
METHOD inverse_end_routine.
$$ begin of inverse routine - insert your code only below this line-
... "insert your code here
$$ end of inverse routine - insert your code only before this line -
ENDMETHOD.                    "inverse_end_routine
ENDCLASS.                    "routine IMPLEMENTATION

Hi,
Most probably you are appending some records in the data package or deleting from the data package through end routine or expert routine or start routine.
I just solved it.....you will have to import the note 1180163.
Then modify the code which you are using....and include the function module as mentioned in the note 1223532.
You need to add the function module just before you append the records.This will work perfectly.
Thanks
Ajeet

BEx Report- Not assigned is displaying in report

Hi All,
I'm running a report on remote cube.
I maintained all master data values for one char which has navigational attributes.
When i run the report it showing for not assiagned to one value for rest it showing the values.
I did the change run also.
Any guesses.
Thanks.

baazi,
U need check whether data exists for the combination of characteristics say if u have 3 chars
Char1    char2    char3(NAV)
ABC       M01      A123
ABC       M02        #
means there is no record for the combination ABC and M02 .
Like this u have to do the analysis.
Hope it helps
bhaskar

Error While loading Hierarchy from R3 to BW

Hi Experts,
plz solve my problem,
I am rtying to load Hierarchy data from IS-R R/3 to Bw
In the monitoring(left hand side) QM status is green saying that the load is successfull
Right hand side QMStatus also Green,
But in the Details Tab(right hand side)
the overall Status is Yellow and it's giving warning messa like Missing messages and Warnings Under this
*Requests (messages): Everything OK
   Data request arranged
   Confirmed with: OK
*Extraction (messages): Everything OK
   Data request received
   Data selection scheduled
   6154 Records sent ( 6154 Records received )
   Data selection ended
*Transfer (IDocs and TRFC): Missing messages(QMStatus is Yellow)
*Processing (data packet): Everything OK
*Data Package 1 ( Records ) : Everything OK
    *Transfer rules ( 6154 Records ) : No errors
      *Hierarchies for master data received. Processing being started.
      *Transfer 6154 data records in communication structure
    *Update ( 0 new / 0 changed ) : No errors
    *Data saved successfully
     *Processing end : No errors
       *Data successfully transferred to the update
*Subseq. processing (messages) : No errors
   -> Start update of master data hierarchy
   <- End update of master data hierarchy
Hierarchy successfully activated
Why in the update mode showing 0 new and 0 changed
it has to show records 6154 new.
but the hierarchy(Merchandise Category) is attching to the infoobject(0material),All the hierarchies are available in the BW .
But its displaying in the BEx report like Not Assigned Material,
I am Unable to solve this proble,
Plz give me the solution
Thanks in Advance
Anil

Hi Anil,
   See if this link can help you.. I am not sure though...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=/help/sdn_nw04/saphelp_nw04/helpdata/en/1f/83813ec8d3fe3ee10000000a114084/content.htm
Thanks,
Raj

Error while loading Hierarchy using Idoc

Hi Experts,
I am loading Hierarchy data from r/3 to Bw,
After load , in the monitoring details tab
its like this
Data Package 1 ( Records ) : Everything OK
Transfer rules ( 911 Records ) : No errors
Hierarchies for master data received. Processing being started.
Transfer 911 data records in communication structure
Update ( 0 new / 0 changed ) : No errors
Data saved successfully
Processing end : No errors
Data successfully transferred to the update
Subseq. processing (messages) : No errors
-> Start update of master data hierarchy
<- End update of master data hierarchy
Hierarchy successfully activated
the hierarchy is adding to the infoobject
But in the reporing it showing like not assigned material
I think the hierarchy is not loaded correctly into the target.
because of the Idoc process , i am Unable to debugg..
plz give me any idea

Hi Vijay
Here:
NODENAME tab
EXTERNAL                         INTERNAL                                                       FORMULA
*                                             js:%external%.toString().replace(/\s+/g,"")
*                                             js:%external%.toString().replace("#","_")
*                                             js:%external%.toString().replace(",","_")
A006-#????                              *skip
Only the first line will work, you have to perform all replacements in on JS line, like:
js:%external%.toString().replace(/\s+/g,"").replace("#","_").replace(",","_")
* in EXTERNAL means ALL
Vadim

Product hierarchy is showing 'Not assigned Materials' in Bex Report

Dear Gurus,
I have loaded product hierarchy to 0material from 0PROD_HIER_LPRH_HIER successfully. In Bex report if i use product hierarchy nothing showing to me and it is showing message in one row like 'Not assigned Materials.
If i remove the Hierarchy i am able to see all materials in the report.
I have searched in sdn but i didnt get any help.Please help me in this issue.
Thanks & Regards,
chandu

Hi Ravi,
I have run the Hierarchy change run for 0material.but again it is showing same message 'not assigned materials'.
Regards,
chandu

ENT-06972: Error While Displaying BIBEAN for Dimension Dataviewer

Hi, I got the following message out of the blue when trying to view data for a dimension within OWB :-
ENT-06972: Error While Displaying BIBEAN for Dimension Dataviewer
Not only can I not see the data for the new dimension I was creating, but all my other existing dimensions generate the same error. Although I can see the data in the underlying db tables none of my Disco reports work either now !.
I have stopped and started the system to no avail.
Any ideas (while I log an SR) ?
I think the OLAP catalog is somewhat screwed.
thanks
Paul

Before you deploy the dimensions and the cube, ensure that the deployment option is set to Deploy to Catalog Only. Using this option, you can view the loaded data in the dimensions and the cube in the Data Viewer.

Urgent Error in Displaying Hierarchy in Bex- like not assigned Material

Similar Messages

Maybe you are looking for