Master Data InfoObject why it invalid ?

[Former Member]

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

[Former Member · Accepted solution]

Hi........

What is the error message?..............If someone delete any value in R/3..........while extracting it will not come in BI side........thats all...........I think the problem is in invalid format or data type.............May the format of the data is not acceptable in BI........or the data type is not matching..........

Is ur load is through PSA?.............and are u in Bw 3.5 or BI 7.0?..........

If u r in BW 3.5............then in the Details tab of the IP monitor......check error is in which data packet.......and the number of records in that packet......then click on the PSA icon in the top.......Select the data packet number......number of records field give the number of records in the data packet.........press enter..............select the satus field.......click on filter >> select errorneous records........edit it...........just tally the field with the correct ones...and edit...........But before editing u hav to delete the request in the target without making the QM status red.................after editing in PSA......reconstruct the request.......

If u are in BI 7.0..........alll erroneous records will be dtored in the error stack.........edit it there......create an error DTP........and load it to the target...........in this case don't delete the request....then error stack also get delted......

Regards,

Debjani....

[Former Member · Accepted solution]

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

[Former Member · Accepted solution]

anyone .. please..

[Former Member · Accepted solution]

Hi,

it could be testing data which were load when they exectracted 1st time they deleted in r/3 but forget to delete in bw my understanding it is the sample data.

Thanks,

Pria,

[Former Member · Accepted solution]

I got the answer from my friend .. that what I looking for .. thanks everybody ..

For those job codes which have all blank fields, its not originally from ECC because it donu2019t have master data attribute or text from R/3. It should be from transaction data which do have JOB as it reference, it will create new SID for this 0JOB table.

It could be from flat file or other resources beside ECC. If you take a look at any DSOu2019s which have 0JOB, it received JOB from file flat, which not available under ECC

ECC- R/3

Rgds

[Former Member]

Hi,

I dont think the master data in 0JOB would be deleted with job deletion in R/3, unless you have coded to check the deletion and wipe out records from master data table in the transformation.

I think, the invalid master data in master data table is due to inconsistent format of the loaded data and the definition of the infoobject. ie chack if er case is allowed in the definition, check the datatype of the object and its characteristics and check if the loaded data is have the same datatype.

Regards,

Sunmit.

[Former Member]

data type everything was fine, because currently they are no problem if they are new 0JOB exits in r/3 it will extracted to this infoobject masterdata without any problem ..

What the best / step procedure that I need to take to delete all invalid masterdata under infoobject?