Document not found in lookup DSO...need to fix the issue permanently

[former_member558460]

Hi All,

DTP load get fails due to the reason no document found in Lookup DSO. For time been we are manually triggering the Lookup DSO infopackage and repeating the DTP step and load is getting successful. But I need to fix this issue permanently.

For that I have checked the load timings of Lookup DSO and Target DSO both are in one meta chain but different local chain.

Once the lookup DSO gets complete immediately after 5 mins target DSO load is getting triggered but still is not able to find the document number in Lookup DSO.

If I delay the target DSO start time by 15 mins will it going to help me? or can we set timings in Lookup logic to start 10 or 15 mins later? Please suggest different alternative approaches to solve this issue.

Thanks In Advance,

Asim.

[former_member558460]

Hi All,

Thanks for the reply.

I have checked the activation step, after activation of lookup DSO  only load is happening in target DSO but still its not picking the document number and load is getting failed.

Regards,

Asim

[KodandaPani_KV]

Hi,

are you working on the DEV system if yes please check 1 or 5 records.

check the ABAP logic for the routines.

please share the routines have you wrote and is it end rotines?

Thanks,

Phani.

[former_member558460]

Hi Phani,

Its production system and we have end routines.

Regards,

Asim.

[former_member185132]

When the DTP fails, please analyze whether the required document is available in the lookup DSO. If it is not available, you'll need to research why the document didn't get loaded into the lookup DSO.

If the document is available in the lookup DSO, then the problem maybe in your routine(s), so please share the code.

[former_member558460]

Hi Suhas,

When DTP is failing at that time required document is not available in the lookup DSO , we are manually triggering the info package of lookup DSO then its coming. so I think its not a problem with code.

Regards,

Asim

[former_member185132]

Can you run the Infopackage and DTP for the lookup DSO before loading the other DSO?

[Former Member]

Use conditions in process chain and that is only if process chain one is success then call second process chain where target DSO is loaded also after successful activation of lookup DSO...

- Try to manually see if data is available or NOT in look up DSO?

- Try to manually load few documents as FULL and see if data is being picked up from look up DSO?

- There might be CONVERSION problem here, for example value like 123 might not be there in lookup DSO but it is in format of 0000000123?

Thanks & Regards,

Mahen

[former_member558460]

Hi All,

Thanks for the reply. I have to change the sequence of process chain and test. I will update if the issue is solve.

Regards,

Asim.

[former_member558460]

Hi All,

Even after the changing the process chain sequence issue is not resolved as we are getting only 5 mins difference after changing the sequence. On further investigating I found that when the load is running in BW at the same time posting happenings at ECC, and target DSO is able to pick up that new posting records whereas lookup DSO not able to pickup the records. Thats why we are getting error "no document number found in lookup DSO"

Few Important Points to be considered.

1. Target DSO datasource is based on Generic Datasource using Functional Module which is directly fetching data from base tables. May be because of that it able to pick up the new posting happening at ECC side? and also target DSO load is after lookup DSO.

2. Lookup DSO datasource is 0FI_AP_04.

Please suggest how we can fix this issue.

Regards,

Asim.

[Former Member]

i suppose your mechanism must be delta?

as long as you are depending on V3 updates in ECC and deltas in BW you will always risk the out-of-sync you describe as long as you are loading while ECC is 'open'.

maybe using this sequence can solve your problem
- reading delta from target DSO into PSA

- reading delta from lookup DSO into PSA and in DSO

- activating lookup DSO

- loading target DSO data including lookup

don't know if this is your actual sequence?

another cause might be the safety interval? is it possible that safety interval for the generic dataosource differs from the 0fi_ap_4 datasource?

[former_member558460]

Hi All,

Further udpate to the above issue, now I need to find out why standard extractor 0FI_AP_04 and 0FI_AR_04 are not able to fetch the document number from ECC.  Once posting happened in ECC side after 20 minutes BW load is getting triggered but still standard extractor not able to fetch the document number some time. But custom extractor which is built using FM able to pull that document number.

Please help me to understand the following points:

1. Once end user posted any entry for document number in how much time it will reflect in base table of 0FI_AP_04/0FI_AR_04 (database tables: BSID, BSAD BFOK_A for AR and BSIK , BSAK, BFOD_A for AP)

2. Please explain me how  this timestamp table BWOM2_TIMEST worked for AR/AP flow.

3. once posting happened in ECC side for document numbers , after 20 mins BW load is getting triggered but still 0FI_AP_4 and 0FI_AR_4 not able to fetch the document number at first instance and load is getting failed. After 15 to 20 minutes when we trigger the infopackage at that time its fetching the document. number, pls explain delta mechanism how its work at ECC side.

Regards,

Asim

[KodandaPani_KV]

Hi,

create the two different process chains for the look up dso and target dso.

first complete the lookup DSO total loading with DSO activaiton then after trigget the target DSO.

first local chain for the look up DSO and second local chain start after completing the look up DSO.

• 1st chain  lookup DSO
• 2nd chain target DSO

add the both chains into metachain.

Thanks,

Phani.

[Former Member]

Hi Khan,

Even though the data load to Lookup DSO gets complete may be the activation step takes time to get complete. If mean while Target DSO load started it will fail since the activation of Lookup DSO is still in progress.

Here you can do one thing to avoid the issue as both are in different Local chains - Check out the impact of loads and change the design of the meta chain such a way that, First Lookup DSO load and activation Local chain completes then link Target DSO local chain. This is the way you can avoid the issue.

Regards,

Srinivas Vetcha