{
  "test_id": "ORCL.SCM.INV.PI.ADJUST",
  "scenario_name": "Process Physical Inventory Adjustments",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Inventory Management",
  "module": "Inventory Management",
  "process": "Physical Inventory",
  "business_flow": "Plan-to-Produce",
  "scenario_type": "Positive / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/scm/inventory-management/physical-inventory/process-physical-inventory-adjustments/",
  "objective": {
    "intro": "Validate approval and posting of the inventory adjustments generated by a completed physical inventory count, and confirm that the physical inventory can only be closed once every adjustment has been actioned and every tag is accounted for, without assuming any specific hard-coded tolerance value.",
    "confirms": [
      "adjustments generated by the completed physical inventory count route to the appropriate approver based on ${APPROVAL_TOLERANCE} and variance magnitude, not a hard-coded threshold",
      "an approver can approve an adjustment individually within their configured authority",
      "an approver can approve adjustments in bulk across the physical inventory",
      "an approver can override the default account on an adjustment where permitted",
      "multi-level approval routing is enforced where configured",
      "an approved adjustment posts correctly to on-hand quantity and accounting",
      "the physical inventory cannot be closed while unresolved variances or unaccounted tags remain",
      "approval history and audit trail are captured and retained against each adjustment",
      "users without the appropriate role or authority cannot approve adjustments or close the physical inventory"
    ],
    "scope_note": "This scenario assumes counts have already been entered through the Enter Physical Inventory Counts scenario and that a variance report has been generated. It does not cover physical inventory definition, tag generation or count entry — those are addressed by earlier scenarios in the Physical Inventory lifecycle. This is the fourth and final page of the Physical Inventory sub-cluster."
  },
  "preconditions": [
    "Oracle Fusion Inventory Management access is configured and available for the test user.",
    "All tags in scope for the physical inventory have been counted or explicitly marked void.",
    "A variance report has been generated for the completed physical inventory, listing the resulting adjustments.",
    "Approval rules and approver assignments are configured for the applicable organization or item class.",
    "The test user (or approver context) has the appropriate role and access to action physical inventory adjustment approvals and closure."
  ],
  "test_data": [
    {
      "field": "Physical Inventory Name",
      "example": "${PHYSICAL_INVENTORY_NAME}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Variance Quantity",
      "example": "${VARIANCE_QUANTITY}"
    },
    {
      "field": "Approval Tolerance",
      "example": "${APPROVAL_TOLERANCE} — customer-configured value, not a fixed dollar or quantity threshold"
    },
    {
      "field": "Approver",
      "example": "${APPROVER} — valid approver assigned to the applicable rule and level"
    },
    {
      "field": "Account",
      "example": "${ACCOUNT}"
    },
    {
      "field": "Adjustment Type",
      "example": "Increase / Decrease — scenario-defined"
    },
    {
      "field": "Approval Action",
      "example": "Approve / Reject, where applicable"
    },
    {
      "field": "Tag Status",
      "example": "All Tags Counted or Void — required before the physical inventory can be closed"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In as Approver",
      "action": "Sign in to Oracle Fusion as the user assigned to approve physical inventory adjustments.",
      "test_data": "${APPROVER}",
      "expected_result": "The approver signs in successfully and lands on the home page.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Inventory Management",
      "action": "Navigate to the Inventory Management work area used to review the completed physical inventory and its pending adjustments.",
      "test_data": "",
      "expected_result": "The Inventory Management work area opens and physical inventory adjustment functions are available.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Review the Variance Report",
      "action": "Open the variance report generated for the completed physical inventory and review each resulting adjustment.",
      "test_data": "${PHYSICAL_INVENTORY_NAME}",
      "expected_result": "The variance report lists every adjustment resulting from the count, with variance and tolerance comparison presented accurately, without a fixed dollar or quantity value being assumed by the test.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the report, filtering by physical inventory name and reviewing each variance line."
    },
    {
      "step_number": 4,
      "step_name": "Approve or Reject Each Adjustment",
      "action": "Approve or reject each pending adjustment individually or in bulk, as applicable to the scenario.",
      "test_data": "${ITEM} / ${VARIANCE_QUANTITY}",
      "expected_result": "Each decision is accepted by Oracle Fusion without unexpected errors, and is routed to the correct approver based on ${APPROVAL_TOLERANCE}.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Provide Justification Where Required",
      "action": "Enter approval or rejection justification if Oracle Fusion requires it for the adjustment.",
      "test_data": "",
      "expected_result": "Justification is accepted where required, or the step is skipped where not required by configuration.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit the Decisions",
      "action": "Submit the approval or rejection decisions for processing.",
      "test_data": "",
      "expected_result": "The decisions are submitted successfully and each adjustment status updates accordingly.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Close the Physical Inventory",
      "action": "Once all adjustments have been processed and every tag is accounted for, close the physical inventory.",
      "test_data": "${PHYSICAL_INVENTORY_NAME}",
      "expected_result": "The physical inventory closes successfully only when every tag has been counted or voided and every adjustment has been actioned; closure is blocked otherwise.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify On-Hand and Accounting Impact",
      "action": "Confirm the on-hand quantity and accounting impact of the approved adjustments, and confirm the physical inventory status is closed.",
      "test_data": "${ACCOUNT}",
      "expected_result": "Approved adjustments post correctly to on-hand quantity and accounting, and the physical inventory shows a closed status with a complete audit trail.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — the test does not stop merely because the approve, submit or close actions were accepted successfully."
    }
  ],
  "expected_results": [
    "Adjustments resulting from the completed physical inventory route correctly to the configured approver based on ${APPROVAL_TOLERANCE} and variance magnitude.",
    "An approver within their configured authority can approve adjustments individually or in bulk.",
    "An approver can override the default account on an adjustment where permitted.",
    "Multi-level approval routing is enforced where configured.",
    "An approved adjustment posts correctly to on-hand quantity and accounting.",
    "The physical inventory cannot be closed while unresolved variances or unaccounted tags remain.",
    "Approval history and audit trail are captured and retained against each adjustment.",
    "Users without the appropriate role or authority cannot approve adjustments or close the physical inventory."
  ],
  "validation_checkpoints": [
    "Adjustment is correctly routed to the appropriate approver based on ${APPROVAL_TOLERANCE} and variance magnitude, not a hard-coded threshold.",
    "Approved adjustments post to on-hand and accounting correctly.",
    "The physical inventory cannot close until all tags are accounted for.",
    "Approval history and audit trail are recorded against each adjustment."
  ]
}