DTP options

hi All,
I have seen many threads regarding DTP and would like to know which option is better to have in the DTP to manage error handling. We have four options in the DTP:
1) Deactivated(Switched off).
2) No update, No reporting
3) Update valid records, no reporting(request red)
4) Update valid records, reporting possible.
The reason i have started this thread is to find out the best practice to use the DTP for BI loads. Also, based on your experiences, which options should i go for DTP and for fixing the error loads,editing the data,etc.
Please advise.
Thanks in advance....

Hi Dorson,
When the error handling is set to Update valid records, no reporting(request red), DTP allows you to update valid data, the entire request turns red in case of errors. The advantage is that any errors occured during extraction is very visible (due to the red request). Disadvantage is, the data from the red request cannot be reported on.
With Update valid records, reporting possible (request green), the request is green irrespective of error records (upto a maximum limit of error records, to be set by user). Advantage, if very few records have errors, the correct updated records can be reported upon.
The below link contains some basic info on the topic:
http://help.sap.com/saphelp_nw04s/helpdata/EN/45/dc799c25c15592e10000000a1553f7/frameset.htm
Regards,
Rakesh

Similar Messages

Problems with DTP.

I am trying to use DTP option to load some masterdata text. The datasource I am working with is not delta enabled so I decided to do FULL extraction to PSA and then do DTP from PSA to my data target, however, after creating Transformation and DTP when I try to execute DTP it only brings less than 100 records into the target. I then ran the old infopackage which brought in 28,000 records. The settings I have checked for DTP are Handle Duplicate Record Keys, and DELTA as update mode. Is there a reason why an infopackage is able to load all 28,000 records but DTP is only loading 65 records?
Thanks.

This is because the infopackage is loading data upto PSA. After PSA data will be loaded to data target. So there is scope for further updates from PSA to data target.
Secondly, the difference between this data recors can be because you have a full upload upto PSA. So in PSA you ahve duplicate records. But from PSA you have DTP, and you selected handle duplicate recors, so it is excluding the duplicate records.
Please check the PSA data and compare this with the target data. It will be clear .
Hope this helps.
Edited by: Chandamita on Jun 23, 2009 8:45 PM

How to resolve error stack DTP ?

I stucked at error stack DTP and there are 20 records in error stack DTP, and i want to push the data into further data targets. how to resolve this issue. pls help me with the steps.

Hi,
first in DTP in excute tab
select the option as update the corrective records and availabe for reporting
not do not load and not avaialble for reporting.
then which ever the correct records are there they will update at first load with normal DTP
which ever the error records are there those records will be moved to error stock( it is part pSA only)--
then click error stock tab( on top menu bar you can find) and do the changse and create the Error DTP
once recors gone to error stock you can find the c reating error DTP option in existed DTP
create the ERROR DTP and load teh data.
Thansk & regards,
sathish

Problem in Activating "Creating Error DTP" Button

Hi All,
I have created a DTP between an InfoCube and an Open Hub destination.
But in the UPDATE tab of the DTP, the "Creating Error DTP" option is not active(its blurred even in edit mode). How should i make the button active??

Hello Roy,
Pls refer this weblog
/people/kamaljeet.kharbanda/blog/2006/12/07/error-dtp--bi2004s
From Std SAP Help
http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/fbd598481e1a61e10000000a422035/content.htm
Thanks
Chandran

DTP Query

Hello, I have a query regarding DTP option in 7.3 system "
Only retrieve last request
I have this checked and it used to work fine but all of sudden it stopped working. i had to re-init my datasource and re init brought back 20,000 records. ok. then i kicked off this dtp whih loaded 20,000 records in my dso which is fine. i put my delta package in process chain and it has been briging 0 record into psa ok. so then when this dtp get kicked off it keeps loading 20,000 records again and again. does any body know what i may have done to disturb this? it used to work fine and onyl extract teh last request in to my dso but no more.
please help.
thanks.

Hi,
Your dtp is delta one?
if yes then after init of your data source/info pack, you need to reinit your dtp also.
other wise it won't work.
Reinit your dtp and check it .
Thanks

Error in DTP load from PSA to IC - Error - Key figure 0 not allowed for

HI ALL,
ERROR - Key figure <> 0 not allowed for unit ' '; see long text
Diagnosis
    The unit/currency ' Source unit MEIN ' with the value 'space' is
    assigned to the key figure ' Source Key Fig. DIFF ' with the value '
    4240.000- '.
System Response
    A key figure that is not equal to 0 and for which no unit/currency is
    set has an inconsistent data state. The data record is not processed.
Procedure
    Correct the source data.
Procedure for System Administration
Please guide
BR
Prasad

Hi ,
First af all identify all such records by creating an error DTP so that the same can be collected in Error stack .
1. Go to the Update tab of the normal DTP and there you can find the create Error DTP option .Click on that .
2. This will take you to the Error DTP screen .Use the option 'Valid record updated reporting possible (request green).You can increase the number of errorneous records to be avoided there only .
3. Please make sure you have activated the option of ' Valid records update reporting possible request green ' both in the Normal and Error DTP .Also the number of errorneous records to be avoided to be mentioned in both the DTP's.
4. Activate the DTP's (Both Normal and Error) .
After this can you please run the Normal DTP again .You can check the Error stack to see the errorneous records .When you double click on any record in the error stack it will thrown an error message from where you can find the exact error with those records .You can rectify these records in the errror stack and then run the error DTP to update the same to the data target.
Ideally these records should be rectified in the Source system .
Thanks
Kamal

Error while updating to target i.e., InfoCube

Hi All,
I am getting error as "
Char value CPV does not exist in the master data table of char ' 0SALES_UNIT' .Therefore this value could not be transformed into internal SID"
Do let me know the soln for above error ,
Regards,
Anjali Singh

Hi ,
1. Go to the Update tab of the normal DTP and there you can find the create Error DTP option .Click on that .
2. This will take you to the Error DTP screen .Use the option 'Valid record updated reporting possible (request green).You can increase the number of errorneous records to be avoided there only .
3. Please make sure you have activated the option of ' Valid records update reporting possible request green ' both in the Normal and Error DTP .Also the number of errorneous records to be avoided to be mentioned in both the DTP's.
4. Activate the DTP's (Both Normal and Error) .
After this can you please run the Normal DTP again .You can check the Error stack to see the errorneous records .When you double click on any record in the error stack it will thrown an error message from where you can find the exact error with those records .You can rectify these records in the error stack and then run the error DTP to update the same to the data target.
If still you are not able to identify the error details properly then run the DTP in simulation mode for the errorneous records to get some more details .
Please try this and update accordingly later.
Regards
Kamal mehta

Use of Error Stacks when loading to a DSO

Hi all,
Hope you can help with the below.
I am loading from a flat file datasource to a DSO.
I do not want to use the DTP option 'No futher processing without master data' to identify master data errors as this causes the load to fail should an error be encountered.
I want to use the error stack and need the errors in both the transactional data AND master data to be moved to the error stack so the load to the DSO can continue, and errors be corrected later.
When I load the file which contains transactional and master data the only error that is sent to the error stack is for the transactional data - a 'data field' set to overwrite in the mapping.
However all Key Fields are master data and the errors are not being reported as well, they are flowing through to the DSO and only being reported when we try to activate the DSO.
So how can I get master data (Key Field) errors to also be moved to the error stack ?
Many thanks.

I think its not possible.
Check this doc http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10c6c05c-89c4-2c10-89bd-fc5ce1d124e2?quicklink=index&overridelayout=true
It defines a way to handle these records.

Error handling on infopackage.

Hi experts,
I want to configure a ODS load to load the correct data and report the errors. I have set set the error handling to update valid records, reporting possible (request green) and create a error dtp.
Now i have one doubt, How do i have to set the set the error handling on the error dtp? And on the infopachage?
Thanks!!
Artur

Hi Artur......
U can do error handling using both DTP and infopackage.......but DTP is only for BI 7.0......
DTP :
In the Update Tab of the DTP............u will Find the Error Handling Field..........there u will get three options..:
a)No update, no reporting (default) >> If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. The incorrect record is highlighted so that the error can be assigned to the data record.
The incorrect records are not written to the error stack since the request is terminated and has to be updated again in its entirety.
b)Update valid records, no reporting (request red) >> This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that are not updated and manually releases the request (by a QM action, that is, setting the overall status on the Status tab page in the monitor).
The incorrect records are written to a separate error stack in which the records are edited and can be updated manually using an error DTP.
c)Update valid records, reporting possible >> Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
The incorrect records are written to a separate error stack in which the records are edited and can be updated manually using an error DTP.
For ur requirement.............u hav to choose either option b or c.........
Now once loading is done........Click on the PSA icon............edit the value..........
Then in the Update Tab ..........U will Find the Create Error DTP option.............click on it..........create the Error DTP and load the edited records.........
Infopackage :
Check this........
http://help.sap.com/saphelp_bw30b/helpdata/en/05/bb223905b61b0ae10000000a11402f/frameset.htm
Regards,
Debjani........

Infopackage Setting

Hi Friends !
We have two failures in our data loads while ODS activation. Invalid characters & no SID values. I know various ways like you can edit PSA, create routine to remove the invalid characters, create a master data etc
But in our project we have to use only the infopackage to resolve the issue. I tried all the options like
1) Do not update data if no master data exists for a characteritsics
2) No update no reporting
3) Valid records update, no reporting (request RED)
4) Valid records update, no reporting (request GREEN)
but still activation is failing. Can you please help how to resolve this issue?
With Regards
Rekha

Hi Rekha
ODS activation gives error when SIDs are generated. So InfoPackage ( even DTP) options will not be able to segregate "invalid" records.
If your ODS has "BEx Reporting" checked then during activation ( Act queue -
>Active table) SIDs get generated and for invalid character activation fails.
If your InfoObjects are "attribute only" then ODS activation will not fail for those InfoObjects even if "invalid" characters are there.
But it depends on your project requirement.
So its better to write routine to remove those Invalid Character. I do not see any other good option.
Regards
Anindya

How i can see ECC Fi Data in BI

hi,
how i can see ECC data in BIW.
I had posted some FI documents in ECC and want to see in BIW.
Thanks
Cra

Step1: Create a generic Data Source ( disregard this since you have SAP Data Source).. Follow from step 2
Step 2: Replicate your new DataSource in BI to get the DataSource metadata copied from the SAP ECC source system to BI.
Note: in BI7.0 there are two types of DS available: new DS (RSDS) and 3.x DS (ISFS). Choose RSDS DataSource.
Step 3: Activate your DataSource in BI in order to use the DataSource later on for requesting data from the ECC system.
Step4: Create a DSO in BI
Step5: Create a Transformation between your DataSource and your DSO. Context menu of DSO you will find Create Transformation.
Note: System will offer a proposal rule automatically that you can change later according to your business requirements.
Create a Transformation between DSO and your Info Cube
Step6: Create a Transformation between DSO and your Info Cube
Step7: Crate an Info Package for your DataSource. This Info Package is used to request data from the SAP ECC system. Rt. Click on your Data Source
Step8: Create a Data Transfer Process between your DataSource and your DSO.
This DTP is used to transfer data from PSA to DSO
Rt. Click DSO to get Crate DTP option
Step9: Create a Data Transfer Process between your DSO and Info Cube.
Note: Step 6 is only when u want to load from DSO to InfoCube.
Hope this help
AKA
Edited by: Arjun Ale on Jun 6, 2008 11:33 PM

WHEN IS ADOBE BRINGING OUT THE NEW PAGEMAKER FOR MAC?

Adobe has photoshop elements for those who don't want photoshop. What about pagemaker for those that don't want to drink the In Design cool aid?
Am I really the only one complaining about the untimely death of pagemaker? I am a dual user- I have PC's and Mac's in my house.
I have gone through the transition of Wordstar to Ami Pro to Microsoft word.
I have gone through the transition of Visi Calc (on an apple II) to Lotus 1-2-3 to Excell.
I will be damned if I'm going to switch from Pagemaker to In Design. I've been using pagemaker since 1990. MY GOD THAT'S 20 YEARS!!!! Longer than some of you have been alive. I have a right to claim upgrade fatigue god damn it!!!!!!!!!
I can run pagemaker on a pc. And that's where I go everytime I want to use it. But my main computer is this mac I'm typing on right now.
I WANT TO RUN PAGEMAKER ON A MAC!!!!!! I WANT TO RUN PAGEMAKER ON A MAC!!!!!! I WANT TO RUN PAGEMAKER ON A MAC!!!!!!
Is that too much to ask?
AM I A MONSTER FOR WANTING SOMETHING SO SIMPLE?
It's a great program, it's a fantastic program. Adobe, why do you want to kill it. What did it ever do to you but bring you money. Is that such a crime?

Thanks for the response.
I just might try out page plus- when I absolutely have to. I might not upgrade to Win 7 if it won't support pagemaker.
I love pagemaker! It is completely part of me.
PS:I'm going to have to change that message that automatically appears at the bottom of all my emails.
This email is from me. You know it's true because it says so right here, at the bottom of this email.
Date: Wed, 10 Mar 2010 04:09:36 -0700
From: [email protected]
To: [email protected]
Subject: WHEN IS ADOBE BRINGING OUT THE NEW PAGEMAKER FOR MAC?
Bacause I said so, you may find Bob and Big John's responses to you post a somewhat harsh. I'd call them suscinct and to the point. Nevertheless, they are quite correct. PM is dead. PM will NOT be fixed, upgraded or updated to run on Win Vista, Win 7 or the latest version of Mac OS X. So from that point of view, you HAVE to get over it! Unless of course you continue to run Win 2000 or XP.
Of course, there is always more than one way to skin a cat. One option is to use Win 7's XP mode. I do not have time to go into haow XP Mode works. Suffice to say that you need Win 7 Pro or Ultimate and an Intel or AMD cpu that supports virtualisation. How good is it? Well, I use an acient DOS program. on Win XP mode and it runs perfectly well. In this case I have no choice other than to use a true copy Win XP (which has nver been installed on this PC). XP mode is a perfectly viable alternative to this.
That said, I would NOT run a complex app such as PM on Win XP mode. Not that it would not work, but more from the point of view that XP Mode should be seen as a temporary fix or where an old program has to be used which will NOT gain any upgrades or updates and where NO OTHER alternative program exists, such as my old DOS program.
With PM, there is an upgrade called InDesign. Yes, you may not like this situation, and neither did I a few years ago. However, the writing was on the wall for PM as soon as InDesign was announced in 1999 and launched in 2000. PM was then 'downshifted' into becoming a business publishing platform to compete more with the likes of MS Publisher, hence the more business orientated marketing. As time went on it became clear that the future of Adobe's publishing focus was InDesign, even though I was assured at an Adobe seminar years ago that PM would continue with more InDesign features!
Remember, InDesign was not only a response to the technical challenges og making PM comlient with thae latest Win and Mac OS's, it was also a response to QuarkXpress which had left PM far behind by 1992.
Adobe is not the only answer of course. No one is forcing you to use InDesign. If I were you, I'd strongly consider PagePlus. It runs on Win Vista and 7 and no doubt packs a lot more up to date featutes than PM 7 does right now. It is also updated, upgraded AND supported! Or if you're happy to use what is essentially a drawing program with some DTP options, give CorelDraw a look.
Ian
>

DELTA option is not working in DTP

Hi All,
I am trying to load data in Infocube using flat file.
It's working fine with full extraction but I' ve added few records in flat file & changed extraction mode to Delta with 'Get data by request' checkbox option checked.
In this case, System taking all records(Old & newly added) in new request. It should take only new records as per my knowledge.
Kindly help me out.
Thanks,
Shamkant

your case should be fulfilled by the normal DTP as mentioned in the blog.
-Sumit

Option for error handling for DTP, ' no updata, no reporting" and "deactiva

Hello Gurus,
     option for error handling for DTP, ' no updata, no reporting" and "deactivated" , please give some explanation and instance for them?
Many Thanks,

On the Update tab page, specify how you want the system to respond to data records with errors:
                            a.      No update, no reporting (default)
If errors occur, the system terminates the update of the entire data package. The request is not released for reporting. However, the system continues to check the records.
                            b.      Update valid records, no reporting (request red)
This option allows you to update valid data. This data is only released for reporting after the administrator checks the incorrect records that have not been updated and manually releases the request by setting the overall status on the Status tab page in the monitor (QM action).
                            c.      Update valid records, reporting possible
Valid records can be reported immediately. Automatic follow-up actions, such as adjusting the aggregates, are also carried out.
http://help.sap.com/saphelp_smehp1/helpdata/en/42/fbd598481e1a61e10000000a422035/content.htm
Hope it helps.
rgds, Ghuru

Which is better or 'standard' option for a Delta DTP request

Hi folks,
I am creating a delta DTP for loading HR Payroll data. While creating the DTP I see two options
a) Only Get Delta once
b) Get all new data request by request
which is a better option if I have a lot of records to upload for every delta upload.
Points waiting to be given to you...
Thanks
Sunil

U should go with Get all new data request by request
i. With Only Get Delta Once, define if the source requests should be transferred only once.
Setting this flag ensures that the content of the InfoProvider is an exact representation of the source data.
A scenario of this type may be required if you always want an InfoProvider to contain the most recent data for a query, but technical reasons prevent the DataSource on which it is based from delivering a delta (new, changed or deleted data records). For this type of DataSource, the current data set for the required selection can only be transferred using a full update.
In this case, a DataStore object cannot normally be used to determine the missing delta information (overwrite and create delta). If this is not logically possible because, for example, data is deleted in the source without delivering reverse records, you can set this flag and perform a snapshot scenario. Only the most recent request for this DataSource is retained in the InfoProvider. Earlier requests for the DataSource are deleted from the (target) InfoProvider before a new one is requested (this is done by a process in a process chain, for example). They are not transferred again by the DTP delta process. When the system determines the delta when a new DTP request is generated, these earlier (source) requests are considered to have been retrieved
ii. Define if you want to Get All New Data in Source Request by Request.
Since a DTP bundles all transfer-relevant requests from the source, it sometimes generates large requests. If you do not want to use a single DTP request to transfer the dataset from the source because the dataset is too large, you can set the Get All New Data in Source Request by Request flag. This specifies that you want the DTP to read only one request from the source at a time. Once processing is completed, the DTP request checks for further new requests in the source. If it finds any, it automatically creates an additional DTP request.
u201COnly get Delta Onceu201D
/people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147only-get-delta-once148
u201CGet Data by Requestu201D
/people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147get-data-by-request148

DTP options

Similar Messages

Maybe you are looking for