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
Request clarification before answering.
Hi Marco,
Rather than enhancing the extract structure, better to go with staging layer solution.
Load header data and item data to Write optimized DSO's. While moving data from item dso to further target level, you may call required information from Header DSO level based on that doc.
Try this at Dev system and check it. do the all test cases and move further if its worked as you needs.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.