Kitchen partners

A partner feed changes a source field while an older order remains open. The coordinator checks the effective mapping version and policy reference for that partner, then records which definition the order uses. Existing orders retain their linked definition. The work starts with partner code, organization and active state. Those details let the next person open the same order or partner context instead of relying on a message thread. The team then checks effective dates, policy reference and feed mapping version. The important decision is whether the partner definition used by an order is effective for its operating date.

The records here separate an operating fact from its review. An order can have a status, an observation can have an outcome, and a run can have an execution result. Each answers a different question. When the team sees an inactive partner or mapping with the wrong effective date, it keeps the partner policy reference and source mapping beside the source order so a later reviewer can reconstruct what happened.

• Identify the source. Start from partner code, organization and active state and keep the related organization, partner and order visible.
• Check the decision. Review effective dates, policy reference and feed mapping version before the order moves to the next status or a result is used.
• Keep the trail. Record the partner policy reference and source mapping with the same source identity when a question needs investigation.

Agree who maintains each partner code, active period and policy reference within an organization. Kitchen Coordinator should review source and target fields, mapping version and effective date before an order uses the definition. Keep the source snapshot coverage period available for feed investigations.

Give the Kitchen Coordinator a partner with a known code and effective date. Walk through an accepted case and an inactive partner or mapping with the wrong effective date. Check that the person responsible for the next step can find the linked source record and its current status. Keep earlier revisions, outcomes and reasons available when the team investigates a change.

A partner feed changes a source field while an older order remains open. The coordinator checks the effective mapping version and policy reference for that partner, then records which definition the order uses. Existing orders retain their linked definition. Ask Order Operator to open the order and name its linked partner definition. Kitchen Coordinator should show which mapping version covered its order date. If the feed changes a field, keep the older mapping visible while the new version is reviewed.

Rehearse the case with a returned or uncertain outcome as well. The team should keep that result visible, assign an action with a due date where needed, and close the action with a resolution that points back to the order. The order trail should still show what happened before the correction.

• Partner Coverage — Check partner coverage, effective dates and policy references before routing.
• Source Coverage Schedule — Review source-system coverage dates and freshness for partner feed work.

Follow the worked process and agree the implementation sequence before the first operating cycle.