Request deletion from Manage-Master data infoobjects

Hi All,
I have a master data infoobject, for which i have created a process chain for deleting the data. I am deleting the P and S table in a program.
When i run this chain data is getting deleted from the tables, but i see the request (green/red/yellow) in the manage section of the infoobject. I want to delete those entries as well from the manage section.
Any inputs ?
Regards,
Sandeep

Hi,
to delete those entries you will have to delete the entries from standard SAP tables...all the tables begining with RSREQ stores the information about the requests...but you may not have authorization for that...
did you tried RSDMD_DEL_BACKGROUND or RSDMD_DEL_MASTER_DATA_TEXTS function modules....you can use in the program and use at as a ABAP variant in the process chain.
Thanks
Ajeet

Similar Messages

Duplicate records in master data infoobject...how to delete it...pls help

hi all,
how to delete duplicate records in master data infoobject which has no requests because it is a direct update?

Hi,
Right click on the info object and
select Maintain
in that you will get the Master data table
from that select the Record and delete it.
hope this solves your query.
reward points if useful
regards,
ANJI

Data load stuck from DSO to Master data Infoobject

Hello Experts,
We have this issue where data load is stuck between a DSO and master data infoobject
Data uploads from DSO( std) to master data infoobject.
This Infoobject has display and nav attributes in it which are mapped from DSO to Infoobject.
Now we have added a new infoobject as attribute to the master data infoobject and made it as NAV attri.
Now when we are doing full load via DTP the load is stuck and is not processing.
Earlier it took only 5 mns of time to complete the full load.
Please advise what could be the reason and cause behind this.
Regards,
santhosh.

Hello guys,
Thanks for the quick response.
But its nothing proceeding further.
The request is still running.
earlier this same data is loaded in 5 mns.
Please find the screen shot.
master data for the infoobjects are loaded as well.
I can see in SM50 the process at P table of the infoobject the process is.
Please advise.
Please find the detials
Updating attributes for InfoObject YCVGUID
Start of Master Data Update
Check Duplicate Key Values
Check Data Values
Process time dependent attributes- green.
No Message: Process Time-Dependent Attributes- yellow
No Message: Generates Navigation Data- yellow
No Message: Update Master Data Attributes - yellow
No Message: End of Master Data Update - yellow
and nothing is going further in Sm37
Thanks,
Santhosh.

Master Data is in Revised Version while transporting a request to add an attribute in existing master data infoobject

Hi Experts,
I am facing short dump when trying to send a request to add an attribute in Master Data Infoobject from DEV to QA.
Although the attribute is getting added to main Master data Info object but main master Info object is in Revised Version.
I have been searching the solution in SCN from couple of days and tried every single solution but none of them works for us.
When I check in se09 I am getting the following message
Program terminated (job: RDDEXECL, no.: 09445401)
   Execution of programs after import (XPRA)
End date and time : 20150420094559
Ended with return code: ===> 12 <===
When checking in ST22 IN QA I am getting the following message
The exception 'CX_RS_PROGRAM_ERROR' was raised, but it was not caught anywhere
along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_RSDD_DS====================CP' has to be
terminated.
When I checked in ST22 in QA I am getting following dump
   31         RAISE EXCEPTION TYPE cx_rs_program_error
   32           EXPORTING
   33             text = 'Invalid DSO subtype'.                   "#EC NOTEXT
   34     ENDCASE.
   35
   36 *   get table name from DDIC
   37     CALL METHOD cl_rsd_odso=>get_tablnm
   38       EXPORTING
   39         i_odsobject = n_infoprov
   40         i_tabt      = l_tab
   41       IMPORTING
   42         e_tablnm    = l_tablnm
   43       EXCEPTIONS
   44         OTHERS      = 1.
   45
   46     IF sy-subrc <> 0.
   47       RAISE EXCEPTION TYPE cx_rs_program_error
   48         EXPORTING
   49           text = 'Error in CL_RSD_ODSO=>get_Tablnm'. "#EC NOTEXT
   50     ENDIF.
   51
   52     CALL FUNCTION 'DDIF_NAMETAB_GET'
   53       EXPORTING
   54         tabname   = l_tablnm
   55       TABLES
   56         dfies_tab = l_t_comp
   57       EXCEPTIONS
   58         not_found = 1
   59         OTHERS    = 2.
   60     IF sy-subrc <> 0.
>>>>> RAISE EXCEPTION TYPE cx_rs_program_error
   62         EXPORTING
   63           text = 'Error in DDIF_NAMETAB_GET'.        "#EC NOTEXT
   64     ENDIF.
I have attached the short dump
Thanks In Advance
Rashid

Hi Tom
Thanks for your reply.
I am not sure what do you mean by Manually activated in Dev or QA . If you mean Dev then i did and also maintain the infoobject related tables using transaction SE14 but still same error.
But if you mean in QA then QA is lock for manual activation but i tried though program RSDG_IOBJ_ACTIVATE but again failed. I also maintain the infoobject related tables using transaction SE14 but still same error.
Regards
Rashid

How to delete the sales org information from BP Master Data in SAP CRM 5.0

Hi Guruu2019s
How to delete the sales org information from BP Master Data in SAP CRM 5.0
Thanks...
Mahesh Pasupunuri

Hello
There is a report attached to [SAP Note 725857|https://service.sap.com/sap/support/notes/725857] that performs the deletion.
Regards
Joaquin

Updating the Master data Infoobjects attributes from the Portal

Dear All,
There is a requirement where through portal i want to retrive the master data infoobject ( based on the value seleceted for that infoobject by the user ) and its attributes in the portal , edit them and save them back so that the updated values goes back to BW master data infoobject data base tables and updates the value.
Eg . I have Natural Account master data infoobject in the BW with attributes fucntional area and expense center.Based on the user selection of any values for the Natural account lets say 01110 , then for 01110 natural account the portal should display the correspoding attributes values of fucntional area and expense center.Lets take this values as 10 , 20 respectively for fucntional area and expense center . What I want to do now is to change these attrbute values to 30 and 40 and I would like to save it back as the changed attribute values for that natural account for 01110 with new attribute values 30 & 40 respectively for fucntional area and expense center .
Is this possible through portal and BW?
Any idea on this would be appriciated.
Regards,
Ankit

Hi Ankit,
this is a quite tough but not impossible requirement. Maintaining Master data is possible with Visual Composer and some function modules (at least that's one way I know). However it could be a bit complicated maintaining attributes Master data depending on your data model. This How might help getting familiar with this topic:
Maintaining BI Master Data with SAP NetWeaver® Visual Composer
Good luck.
Brgds,
Marce

Adjusting the SID table for master data infoobject

Hai
Im trying to activate one master data infoobject. But it says the error like below
<b>The SID Table /BI0/SBBP_DELREF must be converted incompatibly with an activation of characteristic 0BBP_DELREF (changes to the key in the table). Table /BI0/SBBP_DELREF contains data. Parts of this data were lost in the conversion</b>.
or
<b>Undo the changes that led to the incompatible conversion (the changes in the key) or delete all data from table /BI0/SBBP_DELREF.</b>
So how can i adjust the SID table for this .
pls tell me
kumar

Hi,
you'll have to delete ALL the master data for this IObj. Therfore you'll have to
delete all data in ALL the IObjs using 0BBP_DELREF (ODS, CUbes and characteristics).
Then activate your IObj. You will go through some step which I explained in the
following thread
Re: Urgent...Company Code lenght has been changed
Extract:
1. Delete 0COMP_CODE master data.
- get objects list using 0COMP_CODE with loaded data: I suggest to delete
master data via AWB (right click the characteristic). If it can't be deleted because
it is used display the deletion log (via AWB or tx SLG1 / RSDMD, MD_DEL).
- delete loaded data for the list above.
This should not be too much since you are in DEV.
2. change 0COMP_CODE length
- change the length to 4;
*- Activate your IObj. You'll get a popup log, validate. Activate despite warning and
errors. You will get An error message, validate.
You should get an horizontal pane with the activation log. Read it for your personal culture but if you don't have time then don't...
- Next the system will prompt to convert the tables: answer YES. The system will ask to schedule the table conv. in the background, go4it.
- next is the SE14 screen for the P table: Hit Activate and adjust (Direct
execution, or in the back as you wish). Answer yes to the mass processing
question and yes (again) for request adjust online. Your table should be converted successfully.
- go back twice from this screen (leaving SE14 tx and return to RSD1). reread the update log if you wish.
- repeat from the *- above... it will perform the very same for all other P tables of IObj using 0COMP_CODE and the 0COMP_CODE S table.
Your IObj is reactivated again. So should your ODS/DSO objects (check activate for example). Cube didn't need to convert tables since the MDID is note posted in any table of a cube.
Please note that once your IObj is in revised version you can perform the same via the menu extras / database table / convert all (see my previous post).
Now you have to evaluate the task. Of course that is a work to fix the mistake.
Depending on when it has be changed it may be worth to restore your DEV sys with a backup (loose work performed from the backup until now).
hope this helps... otherwise, revert.
Olivier.

Data not uploading in Time dependent Master data Infoobject

Hello All,
I have a master data infoobject for HR entity and have to load data from PSA to that info object.
The HR entity infoobject already have sone data like below:
HR Entity
Version
Date from
Date To
x
A
01.07.2013
31.12.9999
x
A
19.04.2013
30.06.2013
x
A
01.09.2012
18.04.2013
x
A
01.01.2012
31.08.2012
x
A
01.01.1000
31.12.2011
Now the data in PSA is as follows:
HR Entity
Start Date
End Date
X
01.01.2012
18.12.2013
Once I loaded this data to the infoobject, i can not see this value which is the latest value of this HR entity.
Can somebody please explain how the data gets loaded in the time dependent master data infoobject and why this entry is not getting loaded in the info object.
Regards
RK

Hi,
did you activate master data after your load?
You can check also version 'M' records and see if your record is there.
The load went green?
The problem is, that your entry overlaps all exisitng time intervals, which can't be deleted or merged as there may be dependent transactional data. You have first to delete the transactional data for this entity.
Then you can delete the time-dependent data and reoload it from your PSA.
BW will build then correct time intervals.
The easiest is to change the time interval in PSA, see example below:
At the moment the time interval is not accepted. But you can add time intervalls before 31.12.2011 and after 01.07.2013, Then system will create remaiing time intervals, e.g. your new record is:
HR Entity
Start Date
End Date
X
01.08.2013
18.12.2013
Result will be:
HR Entity
Version
Date from
Date To
x
A
19.12.2013
31.12.9999
x
A
01.08.2013
18.12.2013
x
A
01.07.2013
31.07.2013
Regards, Jürgen

Request Deletion from Write-optimized DSO

Hello,
With the new Write-optimized technology, it is possible to delete manually "older" requests from the W-O DSO.
Could anyone of you think of an automated process to delete "old" requests from a W-O DSO (not the entire content , the most recent should still be available.
For instance : delete everyday the request older than 7 days.
Already checked solutions :
- Selective deletion at the administration level of the DSO -> cannot be repeatedly scheduled
- Copying the Selective Deletion generated program to make one's own program and schedule it (system cannot "remember" the generated program)
- Diverse SAP Function Module -> do not work for this scenario (like RSSM_DELETE_REQUEST, only for cubes, RSSM_PROCESS_REQUDEL_ODSO or    RSSM_DELETE_REQUEST, where you need to specify the Request number
- We do not want to include a delete job in a routine at the Transformation level.
- We do not want to complicate the Data Model by creating a new intermediate DSO allowing to flush the DSO at each load..
Any other ideas??
We are on Version 7.0, SP 13.
Many thanks!
amanda

Hi ,
We have worked on similar business requirement .We wrote a report program in SE38 and running it via a process chain .
If you want i can help you to write code for same .
It will be a two step process :
1.deleting request from RSICCONT so that it get deleted from manage tab.
2.deleting data from active table of that WDSO .
Code for Program :
data :v_time type c length 17,
          v_date like sy-datum .
( N) = 7 put no of days here before which you want to delete records
v_date = sy-datum.
subtract 7 from v_date.
concatenate v_date   sy-uzeit into v_time.
delete from rsiccont where icube = wdso_name and timestamp LT v_time .
delete from wdso_active_table_name where rstt_tsmp LT v_time.
It will do your work .
Regards ,
Jaya

Get PO from vendor master data

Hi,
Those any body knows a BAPI or FM that would get the PO that was created in the IDOC from vendor master data?
Please help...
thank you...
regards,
mae

Hi Mae,
hope this may be of some help.
REPORT zpo_bapi_purchord_tej.
DATA DECLARATIONS *
TYPE-POOLS slis.
TYPES: BEGIN OF ty_table,
v_legacy(8),
vendor TYPE bapimepoheader-vendor,
purch_org TYPE bapimepoheader-purch_org,
pur_group TYPE bapimepoheader-pur_group,
material TYPE bapimepoitem-material,
quantity(13),
delivery_date TYPE bapimeposchedule-delivery_date,
net_price(23),
plant TYPE bapimepoitem-plant,
END OF ty_table.
TYPES: BEGIN OF ty_alv,
v_legs(8),
success(10),
v_legf(8),
END OF ty_alv.
TYPES: BEGIN OF ty_alv1,
v_legf1(8),
v_msg(500),
END OF ty_alv1.
*-----Work area declarations.
DATA: x_table TYPE ty_table,
x_header TYPE bapimepoheader,
x_headerx TYPE bapimepoheaderx,
x_item TYPE bapimepoitem,
x_itemx TYPE bapimepoitemx,
x_sched TYPE bapimeposchedule,
x_schedx TYPE bapimeposchedulx,
x_commatable(255),
x_alv TYPE ty_alv,
x_alv1 TYPE ty_alv1,
x_alv2 TYPE ty_alv1.
*-----Internal table declarations.
DATA: it_table TYPE TABLE OF ty_table,
it_commatable LIKE TABLE OF x_commatable,
it_item TYPE TABLE OF bapimepoitem,
it_itemx TYPE TABLE OF bapimepoitemx,
it_sched TYPE TABLE OF bapimeposchedule,
it_schedx TYPE TABLE OF bapimeposchedulx,
it_alv TYPE TABLE OF ty_alv,
it_alv1 TYPE TABLE OF ty_alv1,
it_alv2 TYPE TABLE OF ty_alv1.
DATA: po_number TYPE bapimepoheader-po_number,
x_return TYPE bapiret2,
it_return TYPE TABLE OF bapiret2,
v_file TYPE string,
v_temp(8),
v_succsount TYPE i VALUE 0,
v_failcount TYPE i VALUE 0,
v_total TYPE i.
DATA: v_temp1(5) TYPE n VALUE 0.
DATA: x_event TYPE slis_t_event,
x_fieldcat TYPE slis_t_fieldcat_alv,
x_list_header TYPE slis_t_listheader,
x_event1 LIKE LINE OF x_event,
x_layout1 TYPE slis_layout_alv,
x_variant1 TYPE disvariant,
x_repid2 LIKE sy-repid.
DATA : it_fieldcat TYPE TABLE OF slis_t_fieldcat_alv.
SELECTION-SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK v_b1 WITH FRAME.
*-----To fetch the flat file.
PARAMETERS: p_file TYPE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK v_b1.
AT SELECTION-SCREEN *
AT SELECTION-SCREEN.
IF p_file IS INITIAL.
MESSAGE text-001 TYPE 'E'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
*-----To use F4 help to find file path.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = p_file.
v_file = p_file.
START-OF-SELECTION *
START-OF-SELECTION.
PERFORM gui_upload.
LOOP AT it_table INTO x_table.
PERFORM header_details.
v_temp = x_table-v_legacy.
LOOP AT it_table INTO x_table WHERE v_legacy = v_temp.
PERFORM lineitem.
PERFORM schedule.
ENDLOOP.
DELETE it_table WHERE v_legacy = v_temp.
PERFORM bapicall.
MOVE po_number TO x_alv-success.
APPEND x_alv TO it_alv.
CLEAR x_alv.
*-----To clear the item details in internal table after the operation for a header.
REFRESH: it_item,
it_itemx,
it_sched,
it_schedx.
CLEAR: v_temp1.
ENDLOOP.
v_total = v_succsount + v_failcount.
PERFORM display_alv.
FORM GUI_UPLOAD *
FORM gui_upload .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = v_file
filetype = 'ASC'
TABLES
data_tab = it_commatable
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17
IF sy-subrc = 0.
*-----To fetch the comma seperated flat file into an internal table.
LOOP AT it_commatable INTO x_commatable.
IF x_commatable IS NOT INITIAL.
SPLIT x_commatable AT ',' INTO
x_table-v_legacy
x_table-vendor
x_table-purch_org
x_table-pur_group
x_table-material
x_table-quantity
x_table-delivery_date
x_table-net_price
x_table-plant.
APPEND x_table TO it_table.
ENDIF.
CLEAR x_table.
ENDLOOP.
ENDIF.
ENDFORM. " gui_upload
FORM HEADER_DETAILS *
FORM header_details .
MOVE 'NB' TO x_header-doc_type.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-vendor
IMPORTING
output = x_table-vendor
MOVE x_table-vendor TO x_header-vendor.
MOVE x_table-purch_org TO x_header-purch_org.
MOVE x_table-pur_group TO x_header-pur_group.
x_headerx-doc_type = 'X'.
x_headerx-vendor = 'X'.
x_headerx-purch_org = 'X'.
x_headerx-pur_group = 'X'.
ENDFORM. " header_details
FORM LINEITEM *
FORM lineitem .
v_temp1 = v_temp1 + 10.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = v_temp1
IMPORTING
output = v_temp1.
MOVE v_temp1 TO x_item-po_item.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-material
IMPORTING
output = x_table-material.
MOVE x_table-material TO x_item-material.
MOVE x_table-quantity TO x_item-quantity.
MOVE x_table-net_price TO x_item-net_price.
MOVE x_table-plant TO x_item-plant.
x_itemx-po_item = v_temp1.
x_itemx-material = 'X'.
x_itemx-quantity = 'X'.
x_itemx-net_price = 'X'.
x_itemx-plant = 'X'.
APPEND x_item TO it_item.
APPEND x_itemx TO it_itemx.
CLEAR: x_item, x_itemx.
ENDFORM. " lineitem1
FORM SCHEDULE *
FORM schedule .
MOVE x_table-delivery_date TO x_sched-delivery_date.
MOVE v_temp1 TO x_sched-po_item.
x_schedx-delivery_date = 'X'.
x_schedx-po_item = v_temp1.
APPEND x_sched TO it_sched.
APPEND x_schedx TO it_schedx.
CLEAR: x_sched, x_schedx.
ENDFORM. " schedule
FORM BAPICALL *
FORM bapicall .
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = x_header
poheaderx = x_headerx
IMPORTING
exppurchaseorder = po_number
TABLES
return = it_return
poitem = it_item
poitemx = it_itemx
poschedule = it_sched
poschedulex = it_schedx.
IF po_number IS NOT INITIAL.
v_succsount = v_succsount + 1.
MOVE x_table-v_legacy TO x_alv-v_legs.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ELSE.
v_failcount = v_failcount + 1.
MOVE x_table-v_legacy TO x_alv-v_legf.
MOVE x_table-v_legacy TO x_alv1-v_legf1.
LOOP AT it_return INTO x_return.
IF x_alv1-v_msg IS INITIAL.
MOVE x_return-message TO x_alv1-v_msg.
ELSE.
CONCATENATE x_alv1-v_msg x_return-message INTO x_alv1-v_msg SEPARATED BY space.
ENDIF.
ENDLOOP.
APPEND x_alv1 TO it_alv1.
CLEAR x_alv1.
ENDIF.
ENDFORM. " bapicall
FORM DISPLAY_ALV *
FORM display_alv .
PERFORM x_list_header.
PERFORM build_fieldcat CHANGING x_fieldcat.
x_repid2 = sy-repid.
x_event1-name = 'TOP_OF_PAGE'.
x_event1-form = 'TOP_OF_PAGE'.
APPEND x_event1 TO x_event.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = x_fieldcat
i_callback_user_command = 'USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
i_save = 'A'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " display_master_data
FORM USER_COMMAND *
FORM user_command USING ucomm LIKE sy-ucomm selfield
TYPE slis_selfield.
READ TABLE it_alv INTO x_alv INDEX selfield-tabindex.
CLEAR : x_alv2,it_alv2[].
LOOP AT it_alv1 INTO x_alv1 WHERE v_legf1 = x_alv-v_legf.
x_alv2 = x_alv1.
APPEND x_alv2 TO it_alv2 .
ENDLOOP.
DATA : it_fieldcat TYPE slis_t_fieldcat_alv.
DATA : x3_fieldcat LIKE LINE OF it_fieldcat.
CLEAR : x3_fieldcat,it_fieldcat[].
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_LEGF1'.
x3_fieldcat-reptext_ddic = text-111.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_MSG'.
x3_fieldcat-reptext_ddic = text-112.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
x_layout1-colwidth_optimize = 'X'.
x_layout1-zebra = 'X'.
IF it_alv2[] IS NOT INITIAL.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = it_fieldcat
i_save = 'A'
i_callback_top_of_page = 'TOP'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv2
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDIF.
ENDFORM.
FORM USER_COMMAND *
FORM top.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = 'Commentry'.
ENDFORM.
FORM BUILD_FIELDCAT *
FORM build_fieldcat CHANGING et_fieldcat TYPE slis_t_fieldcat_alv.
DATA: x1_fieldcat TYPE slis_fieldcat_alv.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '1'.
x1_fieldcat-fieldname = 'V_LEGS'.
x1_fieldcat-reptext_ddic = text-108.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '2'.
x1_fieldcat-fieldname = 'SUCCESS'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-109.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '3'.
x1_fieldcat-fieldname = 'V_LEGF'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-110.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
ENDFORM. " build_fieldcat
FORM BUILD_LIST_HEADER *
FORM x_list_header.
DATA: x_list_header1 TYPE slis_listheader.
*-----List Header: type H
CLEAR x_list_header1 .
x_list_header1-typ = 'H'.
x_list_header1-info = text-105.
APPEND x_list_header1 TO x_list_header.
*-----List Key: type S
x_list_header1-typ = 'S'.
x_list_header1-key = text-106.
x_list_header1-info = v_total.
APPEND x_list_header1 TO x_list_header.
*-----List Key: Type S
CLEAR x_list_header1 .
x_list_header1-typ = 'S'.
x_list_header1-key = text-107.
x_list_header1-info = v_succsount.
APPEND x_list_header1 TO x_list_header.
ENDFORM. " build_list_header
FORM TOP_OF_PAGE *
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = x_list_header.
ENDFORM. " TOP_OF_PAGE
cheers,
Hema.

Master data infoobject can't handle duplicate records after SP10

Hi
I am trying to load master data which happened to contain duplicate records from the source system. In the DTP of the master data infoobject, I have ticked the 'Handle Duplicate Record Keys' checkbox. After executing this DTP, the duplicate master data records were trapped in the Error Stack. I am expecting overwriting of the duplicate master data to take place instead. I understand that this error was fixed in Note 954661 - Updating master data texts when error in data package which is from SP9. After applying Support Pack 10, the master data infoobject just can't handle records with duplicate keys.
Please let me know if you manage to fix this problem.
Many thanks,
Anthony

Found a fix for this problem. Just applied this OSS note Note 986196 - Error during duplicate record handling of master data texts.

Master Data InfoObject why it invalid ?

I do have master data infoobject 0JOB . The extraction are Delta. A lots of record under this infoobject masterdata contained invalid masterdata.
Why this thing happen ?? Why its become invalid
Are this cause of :-
1) under R/3 they will delete this 0JOB which no longer been used? ( Delta not capable to delete this JOB once it deleted under r/3 )
Sorry I'm still tyring to understand .. anyone could help me to explain more detail..
Point for sure..
Thanks..
Edited by: Edi Erwan Abu Talib on Nov 23, 2008 4:04 AM

Hi Debjani..
Thanks for your reply .. I do not have any problem while extraction .. PSA do not have any problem .. I'm using Bi7.0 .. here the situation..
under infoobject 0JOB , maintain master data .. I view the data under this infoobject ..
JOB LANG To Valid from Job Group EEO
50000000 - 31.12.9999 01.01.1000
50000003 - 31.12.9999 01.01.1000
50000005 - 31.12.9999 01.01.1000
50000007 - 31.12.9999 01.01.1000
50013218 EN 31.12.9999 01.01.1900 1B AC
Here I get confuse ..JOB (50000000 , 50000003, 50000005 , 50000007 etc) which do not contained LANG and other related field such Job Group / EEO etc .. do not exits at r/3 , .I do check used PO03 / or at rsa3 , data not exits, why it been view under 'Maintain masterdata ' for 0JOB infoobject.
Hope you guys could help me to elaborate more about this situation..
Edited by: Edi Erwan Abu Talib on Nov 23, 2008 9:50 AM
Edited by: Edi Erwan Abu Talib on Nov 23, 2008 4:45 PM

Overwrite data of master data infoobject

Hi all,
We have one master data infoobject ZASRYHMA. This infoobject does not have any attrbiutes but it has two compounding fields ZSITE and 0DISTR_CHAN.
Now customer has a requirement in which value of ZASRYHMA can change for a particular site and distribution channel. Generally if this value changes then system creates a new entry in tables /bic/pzasryhma and /bic/szasryhma.
What they want is to overwrite the existing entry.
Is it possible to achieve? It's a master data infoobject.
Please provide your kind help.
Regards,
Nilima Rodrigues

Hi,
You have three fields as key field in table as shown below along with values,
ZASRYHMA     ZSITE         0DISTR_CHAN
A-1                     B-1            C-1
A-2                     B-2            C-2
now if you want to change the value of say second row to
A-3                    B-2             C-2
right?
This is not possible just by overwritting in the info-object master data. Because these are key-fields system will treat A-3 as new value and create new entry, on top of this your A-2 master data values must have been used in transactional data.
Only way I can think of is to delete the transactional data where ever A-2 is used and then delete ZASRYHMA master data and then upload master data for ZASRYHMA with new values. And then transacional data.

Error while loading to master data infoobject hierarchy (0RPM_PORT_ITEM_HIERARCHY)

Hi All,
I have an issue while loading the data from psa to master data infoobject.
DTP Error:
When we had extracted the data from ECC to PSA, the values for field "IOBJNM" are not populated for 0RPM_PORT_ITEM_HIERARCHY
Thus it is throwing an error while populating this data to the target.
From where this field will fetch the values?
Why these values are not being populated from ECC?
Will there be any issue from BI side? can anyone help me on this.

Hi Raman,
yes I had extracted data in RSA3
There are no values for the field "object".
Do you have any idea why these values are missing?

Creation of Master Data InfoObject

Hi All,
I need to modify 0COMP_CODE Master data Infoobject, with adding some fields as attributes.
I need to add few fields to 0COMP_ CODE, based on tables.
And 0COMP_CODE should pull data from source tables while used at reporting.
Can you please help me on this.

Hello Sri,
You can add the required inobjects in the Attribute tab of 0COMP_ CODE masterdata object.
Also mark them as Navigational if you want them to be used in reports for drill down, navigation etc.
Now either you can enhance the masteradata datacource for 0COMP_ CODE in source system or create your own custom datasource. If you are modifying the already existing DS them you would have to write ABAP code in CMOD for those fields you are adding to 0COMP_ CODE.
Replicate it to BW. Activate the datasource. Create transformations(modify transformation in case you haev modified the already existing DS) to update these new fields to 0COMP_ CODE masterdata attribute.
Now rest of the things are same, like create DTP or IPs etc.
Now as you would have marked these new objects as Navigational in 0COMP_ CODE masteradat attributes tab, you will be able to use them in query design.
Hope it helps...
Regards,
Pratap Sone

Request deletion from Manage-Master data infoobjects

Similar Messages

Maybe you are looking for