Header-data for item-level

[marco_simon2]

Hi experts,

quite often we've got the requirement, that an item-level report shall contain
the header-information as well. For example the order-date (which is maintained
on the header level) shall be available in item-level-reports as well.

Unfortunately the extractor does not support that scenario.

How do you handle such cases?

One option might be to extend the item-level export-structure and
filling the new field using the extraction-customer-exit.

But this has a hatch: If only the header-field is changed, no item-delta

will be triggered. Hence the item-records refering to this header won't
pass the exit (immedialtely) and won't be updated.

Another option might be a data-staging based solution:

After having loaded the header- and item-deltas, one could forward
the header-records to the item-infoprovider;  using a start-routine in
order to clone the header records for each item-level-record.

Futheron this could be used to update only those positions, where
the header changed recently.

Is this the best-practice? Or is there another option I didn't mind?

Best regards,

Marco

[yasemin_kilinc · Accepted solution]

Hi Marco,

I am not sure if it would cause any performance problem but an easier method would be getting the header data as the master data of the item level data. Then you could directly use the attributes in your query. Just an idea...

Regards

Yasemin...

[marco_simon2 · Accepted solution]

Yes, that would be a nice option as well.

That would mean to create master-data-records based on transactional records.

That might have the disadvantace that nav-attributes of the header-characteristics might not be available anymore, because the characteristics themselfe are already the attributes of the header-key (~doc-number). But it would be a nice an very general way to embed the all header-chars into the position.

I crossed that option several times lately, but I'm not yet sure if this is really the best-practice way to solve the simple and imho very general issue described above.

[yasemin_kilinc · Accepted solution]

Hi Marco,

I think the same as well. It may not be the best practice. But still if you require the nav. attributes of the header characteristics, you can still achieve that writing a field routine and reading the value from master data table of the header characteristic while loading.

Regards

Yasemin...

[former_member182470 · Accepted solution]

Hi Yasmein,

How can you bring Transaction data as Master data?

[marco_simon2 · Accepted solution]

Hi Suman,

our way to do that:

We load the transactional data (as usual) to an DSO (which is used for further data-staging to cubes, etc.) and use this DSO as a datasource (not literaly the BW-term) for loading them (partially) to the masterdata-tables of the primary-key InfoObject.

In the case of sales-orders we forward the "customer's order number" and the "order date" to the attributes of the InfoObject 0DOC_NUMBER. This forwarding is done regularly in a process-chain which is situated after the 'real' masterdata-chains and the general transactional-data-chains.

Does that give you a clue?

[former_member182470 · Accepted solution]

I got your most liked workaround. Please carry on with your development..