When an OBT Synchronization run is executed, you notice that the run logs have a big number of postponed itineraries.
Reproducing the Issue
- Go to the Application and User Management Workcenter.
- Go to the Background jobs View.
- Click on Show and select All Jobs run in last Week.
- Select a job with Run Type as OBT Synchronization Run.
- Click on View Application Log.
You see messages like Itineraries: XX replicated, XX processed, XXX postponed, XX cleaned up.
You see a bigger number of postponed Itineraries.
With each replication process only one itinerary per user gets processed (but all itineraries for all users that are in the queue are replicated). Usually only the first one gets processed. However, if that is in status pending approval that would block all following itineraries for that user until it is approved or declined (because only then it is deleted from the queue). This is usually not a problem for real life data, but since you use one test user it shows up as an issue.
If you are testing approval workflow for itineraries, try to process the approval as fast as possible. Also you can book itineraries for different users.
KBA , SRD-CC , Cross Components , How To