Customer with 16 Page Job Card requirements from RPO

Question

Hi I have a customer that needs a Traveler for Lack of better description for each RPO it can be as small as 10 pages and large as 16 per item being produced. Does anyone have any Ideas on this move of the documents need just header fill in but others need details like the Components, and yes they use lot tracking of the components as well as the Finished Goods. These reports change from Time to time and not all pages are required for all FG Items. My developer said we should just modify and use a RDLC report but I would think that would be a giant undertaking to do this by Item.

Thank you

Carol

Answer 1

For your customer's requirement of generating a Traveler document for each RPO with varying page counts (10 to 16 pages), it sounds like a flexible reporting solution is needed. Using RDLC reports can indeed be a significant undertaking, especially if the reports need to change frequently based on the finished goods (FG) items and their specific requirements.

Here are some considerations:

1. Dynamic Report Generation: Instead of creating a separate RDLC report for each item, consider designing a single RDLC report that can dynamically adjust based on parameters. This way, you can control which sections (pages) to display based on the item being produced.
2. Header and Detail Sections: You can create a report with a header section that fills in general information and detail sections that include components and lot tracking information. This approach allows you to manage the visibility of different components based on the specific requirements of each FG item.
3. Parameterization: Utilize parameters to filter the data shown in the report. This will help in managing which details are necessary for different items without needing to create multiple reports.
4. Version Control: Since the reports change from time to time, consider implementing a version control system for the report templates. This will allow you to make updates without disrupting the entire reporting process.
5. Collaboration with Developers: Work closely with your developer to ensure that the RDLC report can be modified easily as requirements change. This may involve creating a modular report design that can be updated without extensive rework.

This approach can help streamline the reporting process while accommodating the varying needs of your customer without the overhead of managing multiple separate reports.

---

References:

• Prod. Order - Job Card
• Using request pages with reports