0record mode field not coming in infocube

[Former Member]

Hello friends,

I have an issue:--

When I am mapping fields in transformation between dso and cube then there is a field in sourse 0RECORDMODE but it is not in target so not able to map this field and while implementing DELTA load it should be mapped .

So can anyone guide me how to get orecordmode field in cube level.

Thanks & Regards,

Arpit

[RamanKorrapati · Accepted solution]

Hi Arpit,

Assuming as your on bw 7.x.

0RECORDMODE is part of DSO to capture the changes.

For info cube delta loads are loaded by request based, so you won't see any info object related recordmode at info cube level.so no need to worry about it.While loading dso to info cube for delta loads you need to load data from changelog table.

Thanks

[Former Member · Accepted solution]

Thanks raman for  your reply

But I am facing issue scenerio is like :-

I have 32 records at dso level but at cube level dtp is fetching 40 records how can it possible.

Thats why I want to see their recordmode type in INFOCUBE.

One more majore issue:-

BDOCs are not processing automatically we have to process them manually in production system (Through SMW01 tcode)

Thanks & Regards,

Arpit

[former_member182470 · Accepted solution]

Your 40 records are not due to recordmode field. It must be due to either Multiple rule groups or some routines in the transformation. Check your DTP monitor to understand where exactly 32 is becoming 40 records.

[RamanKorrapati · Accepted solution]

Hi,

Addition to suman reply:

Please check is there any routines or look ups. with out rules groups/routines and lookups we never get more records into target.

Please check at your transformations from DSO to info cube.

assuming as your loading delta loads. if yes then check form which table your loading.

DTP --> extraction tab  active or change log table.

Bdocs need to proces automatically, if not happens then your source system may be busy during load time. ask your basis team to clear logs or failed queue at source system.

Thanks

[Former Member · Accepted solution]

Hi Arpit,

Please check the number of records in change log, since delta DTP picks data from change log table.

Thanks,

Surya

[MGrob]

Hi

As the others said 0recordmode is a technical object required for delta handling to your DSO. (check one of my documents about delta handling). You'll find the object in your technical rule group. Your delta handling should happen to your DSO and then you don't need a 0recordmode for your cube the DTP will handle the delta mechanics.

hope that helps

Martin

[Former Member]

1. 0Recordmode is a technical object created by system itself when you create a Standard DSO, that too in Change log table.

2. It captures the images (New image,After Image,Before image) of the record that has been loaded in DSO. Based on these images the Change log table stores the records.

3. When you load the data from DSO to cube the data from Change log table actually goes to cube as it has the updated data. This updation of data is with the help of 0Recordmode's images.

Please revert for further clarifications.

Regards,

Kavitha.

[Former Member]

Hi Arpit,

0Recordmode is a property of DSO so this will not be present in Cube. This Object is used for managing delta in DSO. If you have any specific logic based on record mode then you can use that otherwise you can keep this field unmapped.

In DSO when you activate record what action has been taken is based record mode and in Cube it does not make any difference as records are inserted directly as a new record in Cube.

Regards,

Ganesh