Details about Data Target

Hi...........
Infoproviders
http://help.sap.com/saphelp_nw04/helpdata/EN/02/bafc3f9ec4e669e10000000a155106/content.htm
Infoobjects
http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a63f9e07211d2acb80000e829fbfe/frameset.htm
Infoproviders
Different types of Infoproviders are : Infocube,DSO,Virtual providers,Infoset,Multiprovider...in this link you will find all the details..
http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a63f9e07211d2acb80000e829fbfe/frameset.htm
Master Data
http://help.sap.com/saphelp_nw70/helpdata/EN/04/cce63736544d4de10000009b38f8cf/frameset.htm
Hope this helps you............
Regards,
Debjani.............

Similar Messages

ABAP report to read request details in data-target and delete

Hi,
Is there any abap report which I can run in background to read all request details (Request ID, Date) in a data target?
And any ABAP report which can delete a particular request?
Regards
Vikrant

Hi Vikrant,
You can check Table RSREQDONE and RSREQICODS for all details about requests.
About deletion you can try with standard function in InfoPackage when uploading.
Ciao.
Riccardo.

Tcode to find about data targets

Hi all,
Do we have any tcode which lists the cubes, ods and info objects and tell us how frequently each of them gets loaded and what is the space occupied by each of the objects.

Hi........
For List of Cubes >> RSDCUBE
For List of ODS >> RSDODSO
Use Tcode DB02->detail analysis >>type the infocube name or ods name..........To analyze the space occupied.......
Use program : SAP_INFOCUBE_DESIGNS............to count size in records for infocube you can use
Hope this helps........
Regards,
Debjani.......

Need details about Statistics - Internals

Hi,
I am aware of Statistics and how it helps CBO. I would like to know more about internals of Statistics, I know Oracle
maintains certain details in the below views, also in Columns and Partitions Metadata views.
DBA_TABLES
DBA_TAB_STATISTICS
DBA_INDEXES
DBA_IND_STATISTICS
I know it maintains NUM_ROWS and LAST_ANALYZED details in DBA_TABLES and DBA_INDEXES.
Please provide details about the data being maintained in other views.
I'm aware of Histograms, it maintains actual details about Data Distribution. I would like to know how the Normal Statistics differs from Histograms,
it uses the same parameter method_opt with different values.

845956 wrote:
I know it maintains NUM_ROWS and LAST_ANALYZED details in DBA_TABLES and DBA_INDEXES.
It actually maintains much more than just the NUM_ROWS and others you specified.
DBA_TABLES
DBA_TAB_STATISTICS
DBA_INDEXES
DBA_IND_STATISTICS
Regards,
P.

Two tables that provide detail information about data source?

what are the tables that provide information about the datasource?
How to prevent duplicate records in at the data target level?

ROOSOURCE for the details of the datasource...
How to avoid duplicate? --> Dont load same data twice..If delta is supported by the datasource then do a psuedo delta, or delete pervious request with same selections when you do a full load...
Plz elaborate on your question..

Need detail information about Data Cleanse Transform.

Hi Every One,
I Need detail information about Data Cleanse Transform.
1. what is Local Cleansing Packages?
2. what are Directories and Dictioneries.
3. Data Cleanse Transform INPUT , OPTIONS, OUTPUT tabs and usage.
4. Details on Transform Input Field name in Data Cleanse INPUT tab.
5. What is PARENT_COMPONENT,FILED_NAME,FIELD_CLASS,CONTENT_TYPE in Data Cleanse OUT POT TAB.
I tried using "EnglishNorthAmericaDataCleanse" transform with NAME_OR_FIRM_LINE1. When I ran the job I got below warning message and my job was success full nut status it shown as failed.
Warning message:
"Trasform Data Cleanse is unable to retrieve cleansing packages from Cleansing Package Builder. Only local cleansing packages are available. Info: Unable to log on: Could not connect to server d184932040.sng1.attens.net:6400. Please check that the server name is correct, and that the server is running. "
Please make me understand, why did I get above message.
Thanks in Advance ...

Hello,
Cleansing package is a reference file that contains content and rules around person, firm, title, phone data and so on. Cleansing package used to be referred to as dictionaries. Directories are usually referred to address reference data or address directories. The input, output and option tabs are similar to other Data Quality transforms. For detail information on what each of the input fields and output fields are and how the options work can be found in the Data Services’ Designer Guide (http://help.sap.com/bods).
The warning message you are getting is stating that Data Services is not able to connect to the server to check to see if you have made modifications to the PERSON_FIRM cleansing package. You are not required to make any changes to the PERSON_FIRM cleansing package, but can change rules or content based on your organizational rules. If you want to make changes you will need to install SAP Information Steward. If you would like to install SAP Information Steward you can find documentation for installation on the Help Portal, http://help.sap.com/bods, along with some great Videos.
You can also find some great Data Services Product Tutorials on the SAP Community Network, at http://scn.sap.com/docs/DOC-54115.
Thank you,
Lynne Lintelman

Details about loaded data

Hi,
Data is loaded to ODS from Flat file.
Is there any way to find the details about the loaded data.
Like, can we find the date for loaded data or request number from which that data was loaded.
Please help.

can we find the date for loaded data or request number from which that data was loaded
Ans : Date of loaded data or request number can be seen in the ODS manage screen.
If you want to see data you can choose contents in the above tab in manage screen or use LISTCUBE.
Hope this helps

Delta and full uploads in the same data target?????

I have found that delta load and full update from different infopackages are getting loaded into the same data target that is ODS object. when do we go for such situation, can any one explain me in detail or give me some documents to know more about it.

Hi,
You have not clearly mentioned that those infopackages are ctrated on the same Datasource or not.
This way of uploading is very common when we need to upload some data from R/3 and some other data from Flat file into the Info cube. And GenerallyFlat file data would not be given in Before image and after image way, thats why we need to do full uplaod. The deleetion of already uploaded flat file data fromt he cube (before new upload from flat file ) depends up on whether the data to be uploaded from flat file system is always new data or not. And generally R/3 Extractor is capable of giving deltas, thats why only delta loads to the cube.
With rgds,
Anil Kumar Sharma .P

Details about how to do delta load

Hi,
Can someone please give me the details about how to do delta from scratch. Like, i have the custom datasource created in the RSO2, created infosource in BW, loaded that into an ODS using full load. Now how do I do the delta for the same ods instead of full load. It will be a great help to me if you can give me the steps how to do and your help is always appreciated.
Thanks in advance,
Sue

Hi
Delta Process
Definition
The delta process is a feature of the extractor and specifies how data is to be transferred. As a DataSource attribute, it specifies how the DataSource data is passed on to the data target. From this you can derive, for example, for which data a DataSource is suited, and how the update and serialization are to be carried out.
Use
The type of delta process affects the update into a data target. When you update data in an ODS object, you need to serialize it so that you can also overwrite it. According to the delta process, the system decides whether it is necessary to serialize by request or by data packet.
Structure
There are various delta processes for SAP source systems:
1. Forming deltas with after, before and reverse images that are updated directly in the delta queue; an after image shows the status after the change, a before image the status before the change with a negative sign and the reverse image also shows the negative sign next to the record while indicating it for deletion. This serializes the delta packets. The delta process controls whether adding or overwriting is permitted. In this case, adding and overwriting are permitted. This process supports an update in an ODS object as well as in an InfoCube. (technical name of the delta process in the system): ABR)
2. The extractor delivers additive deltas that are serialized by request. This serialization is necessary since the extractor within a request delivers each key once, and otherwise changes in the non-key fields are not copied over correctly. It only supports the addition of fields. It supports an update in an ODS object as well as in an InfoCube. This delta process is used by LIS DataSources. (technical name of the delta process in the system): ADD)
3. Forming deltas with after image, which are updated directly in the delta queue. This serializes data by packet since the same key can be copied more than once within a request. It does not support the direct update of data in an InfoCube. An ODS object must always be in operation when you update data in an InfoCube. For numeric key figures, for example, this process only supports overwriting and not adding, otherwise incorrect results would come about. It is used in FI-AP/AR for transferring line items, while the variation of the process, where the extractor can also send records with the deletion flag, is used in this capacity in BBP. (technical name of the delta process in the system): AIM/AIMD)
Pls do check the link
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a64d3e07211d2acb80000e829fbfe/content.htm
Re: Need Help in After Image and Before Image
Re: Generic Datasource with Additive Delta
Re: Diff between before image and after image
if it helps pls ado asiign points

Give me details about rule details functions conversion, currency etc in bi

give me details about rule details functions conversion, currency etc in bi when creating transformation

Rule Type
Use
The rule type determines whether and how a characteristic or key figure, or a data field or key field is updated into the target.
Direct Assignment:
The field is filled directly from the selected source InfoObject. If the system does not propose a source InfoObject, you can assign a source InfoObject of the same type (amount, number, integer, quantity, float, time) or you can create a routine.
If you assign a source InfoObject to a target InfoObject that has the same type but a different currency, you have to translate the source currency into the target currency using a currency translation, or apply the source currency.
If you assign a source InfoObject to a target InfoObject that has the same type but a different unit of measure, you have to convert the source unit of measure into the target unit of measure using a unit of measure conversion, or apply the unit of measure from the source.
Constant:
The field is not filled by the InfoObject; it is filled directly with the value specified.
Formula:
The InfoObject is updated with a value determined using a formula.
Read Master Data:
The InfoObject is updated by reading the master data table of a characteristic that is included in the source with a key and a value and that contains the corresponding InfoObject as an attribute. The attributes and their values are read using the key and are then returned.
The Financial Management Area characteristic is included in the target but does not exist in the source as a characteristic. However, the source contains a characteristic (cost center, for example) that has the Financial Management Area characteristic as an attribute. You can read the Financial Management Area attribute from the master data table and use it to fill the Financial Management Area characteristic in the target.
It is not possible to read recursively, that is, to read additional attributes for the attribute. To do this, you have to use routines.
If you have changed master data, you have to execute the change run. By reading the master data, the active version is read. If this is not available, an error occurs.
If the attribute is time dependent, you also have to define when it should be read: at the current date (sy-date), at the beginning or end of a period (defined by a time characteristic in the InfoSource), or at a constant date that you enter directly. Sy-date is used as the default.
Routine:
The field is filled by the transformation routine you have written.
The system allows you to select whether the routine is to be valid for all attributes for this characteristic, or only for the attributes displayed.
Transformation rules generally only have one return value. If you select Return Table, the corresponding key figure routine no longer has a return value; it has a return table. You can then generate any number of values from a data record.
For DataStore objects and InfoObjects: you cannot use the return code in the routine for data fields that are updated by being overwritten. If you do not want to update specific records, you can delete these from the start routine.
If, for the same characteristic, you generate different rules for different key figures or data fields, a separate data record can be created for each key figure from a data record of the source.
With InfoCubes: You can also select Routine with Unit. The return parameter 'UNIT' is then also added to the routine. You can store the required unit of the key figure, such as 'ST', in this parameter. You can use this option, for example, to convert the unit KG in the source, into tons in the target.
If you fill the target key figure from a transformation routine, currency translation has to be performed using the transformation routine. This means that automatic calculation is not possible.
Time Update:
When performing a time update, automatic time conversion and time distribution are available.
Direct Update: the system automatically performs a time conversion.
Time Conversion:
You can update source time characteristics to target time characteristics using automatic time conversion. This function is not available for DataStore objects, since time characteristics are treated as normal data fields. The system only displays the time characteristics for which an automatic time conversion routine exists.
Time Distribution:
You can update time characteristics with time distribution. All the key figures that can be added are split into correspondingly smaller units of time. If the source contains a time characteristic (such as 0CALMONTH) that is not as precise as a time characteristic of the target (such as 0CALWEEK), you can combine these characteristics with one another in the rule. The system then performs time distribution in the transformation.
The time distribution is always applied to all key figures.
Initial:
The field is not filled. It remains empty.
No Transformation:
The key figures are not written to the InfoProvider.
Unit of Measure Conversion and Currency Translation
You can convert data records into the unit of measure or currency in the target transformation.
Assigning InfoObjects for Converting Amounts or Currencies
Use
An InfoObject has to be assigned to a source field of a DataSource if currencies or units of measure need to be converted. The translation types require InfoObjects as input fields to carry out a conversion. You therefore have to assign the appropriate InfoObject to the source field.
If the target has a fixed unit, you only have to assign an InfoObject if you want to carry out a conversion. Otherwise, you can select the No Conversion option.
Procedure
1.      You are in the rule details. Select the rule type Direct Assignment.
2.      Select an appropriate key figure in the InfoObject Assignment field in the Source Fields of Rule area.
3.      Choose the required conversion in the Currency field.
4.      Choose Transfer Values.
Example
In your transformation, you want to assign the AMOUNT field of the DataSource to the FIX_EUR InfoObject in your target, carrying out a currency conversion. To do so, you assign the FIX_EUR InfoObject to the AMOUNT field in the rule details so that the currency can be read from the InfoObject.
Hope this helps u...
Regards,
KK.

Details about Process chain

Details about Process chain

Hi Vijay,
            Well the major components of Process chain is mentioned as under:-
A process Chain is a sequence of processes in BI system that executes in the Background.
Commonly Used Process Types
1. Start
2. Execute InfoPackage
3. DTP
4. Attribute Change Run
5. Save Hierarchy
6. Delete Index
7. Generate Index
8. Activate DSO data
9. Update DSO data
10. Complete Deletion of Data Target Content
11. Delete Entire Content of Linked Transactional DSO/ODS
12. Initial Fill of New Aggregates
13. Roll up of Filled Aggregates/BIA indexes
14. Compression of InfoCubes
15. Read PSA and Update Data Target
16. AND
17. OR
18. XOR
If you want to include a load process in the process chain, you need to have already created an InfoPackage.
You cannot load flat file data from a client workstation in the background. For this reason, you have stored your data on an application server.
Creating Process Chains
You have the option of creating a process chain in the process chain maintenance screen directly or by using a maintenance dialog for a process:
Creating a Process Chain Directly in the Process Chain Maintenance Screen
You are in the BW Administrator Workbench.
       1.      Click on the Process Chain Maintenance icon in the AWB toolbar.
The Process Chain Selection dialog window appears.
       2.      Choose Create.
       3.      Enter the technical name and a description of the chain, and confirm your entry.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
       5.      Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
       1.      Choose the Process Chain Maintenance pushbutton and create a process variant.
       2.      Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
       3.      Confirm your entries.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
       5.      Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
       6.      When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process
Function Information
Maintain Variants
With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants
You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs
Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs
After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message
You can also send messages to an application process of the chain, depending on the success or failure of the process.
1.       From the context menu of a process, create an additional process variant of the Send Message type.
2.       If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3.       You arrive at a window, in which you can select an existing process variant or create a new one.
4.       If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5.       Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process
You use this function to remove a process from a process chain.
Manage Data Target
You use this function in connection with the following types of process variants
·         constructing indexes
·         deleting indexes
·         constructing database statistics
·         rolling up filled aggregates
·         compressing InfoCubes
·         activating ODS object data
to call up the administration for each of the data targets.
       7.      Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
       8.      If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
       9.      Under Attributes ®Display Components assign a display component to the process chain.
   10.      Maintain additional process chain attributes if necessary.
   11.      Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
   12.      Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.

Data target issues

hai sap gurusssssss
how to fix if the data is not availble inthe data target.
and how to fix if a report contains false data. plz z explain step by step scenario..

Hi Banda Naren,
Could you please provide us your detail scenario as I'm not sure about your question & hence not able to suggest anything.
Thanks.
Best regards,
HC.

Error while loading the data from PSA to Data Target

Hi to all,
     I'm spacing some error while loading the data to data target.
Error : Record 1 :Value 'Kuldeep Puri Milan Joshi ' (hex. '004B0075006C0064006500650070002000500075007200690
Details:
Requests (messages): Everything OK
Extraction (messages): Everything OK
Transfer (IDocs and TRFC): Errors occurred
      Request IDoc : Application document posted
      Info IDoc 2 : Application document posted
      Info IDoc 1 : Application document posted
      Info IDoc 4 : Application document posted
      Info IDoc 3 : Application document posted
      Data Package 1 : arrived in BW ; Processing : Data records for package 1 selected in PSA - 1 er
Processing (data packet): Errors occurred
      Update PSA ( 2462 Records posted ) : No errors
      Transfer Rules ( 2462 -> 2462 Records ) : No errors
      Update rules ( 2462 -> 2462 Records ) : No errors
      Update ( 0 new / 0 changed ) : Errors occurred
      Processing end : Errors occurred
I'm totally new to this issue. please help to solve this error.
Regards,
Saran

Hi,
I think you are facing an invalid character issue.
This issue can be resolved by correcting the error records in PSA and updating it into the target. For that the first step should be to identify if all the records are there in PSA. You can find out this from checking the Details tab in RSMO, Job log , PSA > sorting records based on status,etc. Once its confirmed force the request to red and delete the particular request from the target cube. Then go to PSA and edit the incorrect records (correcting or blanking out the invalid entries for particular field InfoObject for the incorrect record) and save it. Once all the incorrect records are edited go to RSA1>PSA find the particular request and update to target manually (right click on PSA request > Start update immediately).
I will add the step by step procedure to edit PSA data and update into target (request based).
In your case the error message says Error : Record 1 :Value 'Kuldeep Puri Milan Joshi '. You just need to conver this to Capital letter in PSA and reload.
Edit the field to KULDEEP PURI MILAN JOSHI in PSA and push it to target.
Identifying incorrect records.
System wont show all the incorrect records at the first time itself. You need to search the PSA table manually to find all the incorrect records.
1. First see RSMO > Details > Expand upate rules / processing tabs and you will find some of the error records.
2. Then you can go to PSA and filter using the status of records. Filter all the red requests. This may also wont show the entire incorrect records.
3. Then you can go to PSA and filter using the incorrect records based on the particular field.
4. If this also doesnt work out go to PSA and sort (not filter) the records based on the particular field with incorrect values and it will show all the records. Note down the record numbers and then edit them one by one.
If you want to confirm find the PSA table and search manually."
Also Run the report RS_ERRORLOG_EXAMPLE,By this report you can display all incorrected records of the data & you can also find whether the error occured in PSA or in TRANSFER RULES.
Steps to resolve this
1. Force the request to red in RSMO > Status tab.
2. Delete the request from target.
3. Come to RSMO > top right you can see PSA maintenace button > click and go to PSA .
4.Edit the record
5. Save PSA data.
6. Got to RSA15 > Search by request name > Right click > update the request from PSA to target.
Refer how to Modify PSA Data
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40890eda-1b99-2a10-2d8b-a18b9108fc38
This should solve your problem for now.
As a long term you can apply some user exit in source system side or change your update rules to ensure that this field is getting blanked out before getting loaded in cube or add that particular char to permitted character list in BW.
RSKC --> type ALL_CAPITAL --> F8 (Execute)
OR
Go to SE38 and execute the program RSKC_ALLOWED_CHAR_MAINTAIN and give ALL_CAPITAL or the char you want to add.
Check the table RSALLOWEDCHAR. It should contain ALL_CAPITAL or the char you have entered.
Refer
/people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2
/people/sap.user72/blog/2006/07/08/invalid-characters-in-sap-bw-3x-myths-and-reality-part-1
/people/aaron.wang3/blog/2007/09/03/steps-of-including-one-special-characters-into-permitted-ones-in-bi
http://help.sap.com/saphelp_nw04/helpdata/en/64/e90da7a60f11d2a97100a0c9449261/frameset.htm
For adding Other characters
OSS note #173241 Allowed characters in the BW System
Thanks,
JituK
Edited by: Jitu Krishna on Mar 22, 2008 1:52 PM

Unable to delete data target contents of Write-Optimized DSO in Process Chain

Hi Experts,
We are using SAP Net Weaver BW 7.01 version and we need to delete the entire data target contents of Write-Optimized DSO in the process chain before the next data load.
I included this step in process chain but still it is failing with errore message"Message not found (in main memory), Drop Cube Failed In Data Target"
This process type is working during BW 7.0 version but not in BW 7.01 version.
However i found that we can use the program RSSM_DELETE_WO_DSO_REQUESTS to delete old requests in the Write-Optimized DSO for BW 7.01 SP07 as per SAP Note 1437407 but still it's not working even after implementing this program as the Prerequisite to delete the request is the data mart status should be updated where it is not happening for the program.
We had an process type option to 'delete the requests from Write-Optimized DSO' directly in BW 7.3 but still not available in 7.01 version.
Could you please suggest me on how to resolve this issue in BW 7.01?
Many thanks for your help in advance.
Regards,
Madhu

Create ABAP program as attached code.
Then you can use that ABAP program in process chains through ABAP variant
ABAP varaint should have following properties
Select call mode as Synchronous; call from Local; and Program
Give your ABAP program name in "program name" and create one program variant for each write optimized DSO.
Please refer how to use ABAP program in process chains for further details.
Hope this helps

Data is not updating in data target from PSA

Hi,
i have loaded data from flat file to an Info Object(with direct update)....the data is loaded correctly into PSA...when i manually read data from PSA to data target its not updting in data target.......can anyone help with this....thanks in advance..

hi bwusr,
direct update, so it's master data,
is it attribute or text ? perhaps there's invalid character or lower case,
check in monitor tab detail.
and when you said not updated to data target,
you check by right click 'maintain master data' ?
or you mean it's not updated to reporting ?
execute change run ? rsa1->tools->apply attribute/hierarchy change.
hope this helps.

Details about Data Target

Similar Messages

Maybe you are looking for