Delete PSA for InfoObject version 7.0?

[Former Member]

Hi,

I've created an InfoObject ZUMSKD that doesn't have any attributes, it has only text.In order to load the text in the InfoObject I created a Datasource. When prompted for the type I chose version 7.0. We're on Netweaver 2004s, so I figured I need a 7.0 type datasource, even though I've only used 3.x so far.

Every time I tun the Infopackage it generates a request in the PSA. When I run my DTP it loads data from the PSA into the data target. However, from what I understand, it is trying to load all requests and as a result I get an error for duplicate data. Do I need to delete ALL requests from the PSA of the text Datasource before I load any data?

I have a delete PSA process variant in my Process chain, but I've set it in the beginning of the chain and I include all InfoObjects. However I've set that to data older than 60 days. Our upload will be monthly. I thought that keeping two months of data in the PSA is a good idea?

thanks

Michalis

[Former Member · Accepted solution]

Yes, you need to delete the data from PSA. Go to infosource tab (or infoarea tab) --> find you text infoobject --> go down and select datasource xxx_text --> right clk and select manage --> select all request and delete.

Regards

Pankaj

[Former Member · Accepted solution]

Hi Pankaj,

I no how to delete the PSA. I've also added a delete step in my Process Chain. My question is, do I need to have 0 reuqests in the PSA, before I run the InfoPackage? Because it doesn't seem to affect InfoObjects that have 3.x datasources for text and attributes. It doesn't seem like I need to delete the PSA for 3.x InfoObjects. Can someone explain why this is happening?

thanks

[Former Member · Accepted solution]

Hi,

Can some one confirm if this is correct?

Full upload Infopackages for 3.x version master data datasources will load only the latest reuqest into the datatarget. The data in the infoobject is automatically overwritten.

Full upload Infopackages for 7.0 version master data datasources will attempt to load all reuqests into the datatarget. That causes errors in the data target because of duplicate entries.

Is that correct?

Thanks

[Former Member · Accepted solution]

You are almost correct.

It has nothing to do with master data, and everything to do with how a DTP is different from an Infopackage.

For DTP, you have an option to select 'full' or 'delta'. The 'delta' option posts only those requests from PSA which are not already posted to that target.

[Former Member · Accepted solution]

Hi Ajay, thanks for that.

Ok I understand what you're saying but I need to understand this better. If I select "delta", it will only bring those records that are new in the R/3 system (source system). If however I select the (full) option for my DTP, it will load all the requests that are available in the PSA. So if I have 10 requests with 100 records each, when I run the DTP it will generate 1000 records in the data target. Actually it will probably fail because there are duplicate records, since each data set in the PSA is almost identical (text).

The "full" infopackage however, will only take the latest reuqest and it will overwrite the existing data in the infoobject. That will leave 100 records in the Infoobject, even though there are 10 requests in the PSA with 100 records each.

Is that correct?

Thanks

[Former Member · Accepted solution]

Michail,

DTP doesn't connect directly to source system, it is going to bring data from PSA only. So, you will not have 'either infopackage or DTP', rather 'an infopackage and a DTP'.

The infopackage would bring the delta from the source system, whereas DTP will bring 'full' or 'delta' (depending on what you choose) from the PSA. If you choose 'full', it will bring all the requests from the PSA (nothing to do with source system), if you choose delta it will bring the requests from PSA that are yet unloaded.

Your typical scenario in 7.0 would be

<b>Delta load</b>

Delta infopackage to PSA

Delta DTP to target

<b>Full load</b>

Full infopackage to PSA

(still) Delta DTP to target (as you don't want earlier PSA full request to be repeated)

With DTPs there would normally not be a case where you do a 'full' load - so the example you site will indeed fail- and will be an incorrect usage of DTP. The 'full' infopackage reads from source system (as opposed to DTP which reads from PSA) so it is not right to compare these two scenarios.

A little unlearning is required for DTPs, as

a DTP in 7 <> an infopackage in 3.x

[Former Member · Accepted solution]

Thanks a lot Ajay,

I know that the infopackage takes data from the datasource and you need a DTP to load that data unto your data target. I was struggling witht the whole delta/full issue.

We've used a full upload for our DTP, and to resolve the problem of duplicate entries we've added two steps in our Process chain where we delete the data in the data target and we also delte the requests from the PSA. It's like starting from scratch everytime. I just thought that was an awkward way of doing it, even though it works fine.

The Datasource we use does not have a Delta functionality. I can't then use your first option for <b>Delta load</b>. If I use the second option you suggest <b>Full load</b>, then the following will happen:

A full load for the infopackage brings 100 records in the PSA from R/3. There are already another 10-15 requests in the PSA but I'm not worried about that because I will use a Delta DTP to load data into the data target. The DTP will take the latest request (that hasn't been loaded yet) and it will attempt to load the data into the Infoobject. As we are talking about text, wouldn't the load fail? If the Infoobject already has the following entries:

01: Illness

02: Absence

03: Injury

04......100

and the new request has exactly the same values, since it is a full upload from R/3

01: Illness

02: Absence

03: Injury

04......100

wouldn't the DTP fail?

[Former Member · Accepted solution]

Michail,

Master data load works in overwrite, and it shouldn't fail.

Imagine how it worked in 3.x. You had to bring it in full load (as it is not delta capable) which would have brought all records everytime and it didn't fail.

Master data (and ODS in default setting mode) use overwrite option, so the scenario you mention is taken care of by BW/BI.

[Former Member · Accepted solution]

I've abused your help Ajay. Thanks a lot for exaplining it to me

cheers

Michalis

[S0004647611]

Hi,

When the DTP is running as delta it will only pick up the new requests from psa, if you're running full load it will pick up all available ones, and in this case you will have to clean accordingly.

Regards, Patrick Rieken.

Message was edited by:

Patrick Rieken - BI-Formance B.V.