Poultry ERP Questions & Answers

Based on the current date of late September 2025, you should avoid enabling new Odoo features during the following windows in Q4 2025:

• October 1–2, 2025: Avoid enabling features during the Indian national holidays for Gandhi Jayanti and Dussehra, as this is a major holiday period.
• October 20, 2025: Avoid the Diwali festival period, especially if your business is in India or has a significant Indian customer base, as this is a major time of high online traffic.
• Late November to December: Avoid deployments during the global holiday shopping season, including Black Friday (Nov 28), Cyber Monday (Dec 1), and the extended Christmas/New Year holiday period.

To export SAP BTP logs to a Security Information and Event Management (SIEM) system with least-privilege scopes, use the Audit Log Retrieval API with a dedicated service key. This method avoids giving your SIEM platform wide-ranging access to your SAP BTP account. The logs are retrieved via a pull-based mechanism, ensuring your SIEM only receives the data it requests.

• Step 1: Create an Auditlog Management service instance 
• Step 2: Create a least-privilege service key
• Step 3: Configure your SIEM to pull logs 
• Step 4: Automate the retrieval process

Rollback plan
A robust rollback plan for SAP S/4HANA depends on the migration approach (e.g., Brownfield conversion, Greenfield implementation). This plan focuses on reversing the change with minimal data loss. 
Phase 1: Pre-rollout preparation

• Create a fallback snapshot: Before starting the system conversion, take a full backup or a fallback snapshot of the existing SAP ECC database. This is your most critical safety net, allowing you to revert the system to its original state if a critical error occurs.

Phase 2: Active monitoring and decision-making

• Monitor post-go-live performance: Use SAP Solution Manager or third-party monitoring tools to continuously track performance indicators against the established baselines.

Phase 3: Executing the rollback 

• Post-rollback analysis: After the system is restored, analyze the root cause of the performance regression to inform the next attempt. This may involve code optimization, configuration changes, or hardware enhancements. 

Communications plan
A proactive and transparent communications strategy is crucial for managing the impact of a performance-related rollback. 
Before the rollout

• Communicate performance expectations: Inform all users of the potential for temporary performance changes during the initial stabilization or hypercare phase post-go-live.

During an incident (performance regression)

• Initial alert (within 15 minutes of detection):
• Rollback decision (within 1 hour):
• Resolution update (as soon as the rollback is complete):

Post-incident

• Lessons learned session: Organize a session with key stakeholders to discuss what worked and what didn't in the rollback plan and communication strategy. Use this feedback to improve future risk mitigation efforts.