Summary:
Before a cost update is sent to Impulse or the GDL, the Xvantage Global Cost Engine (GCE) performs several validations based on the rules provided by the business. Below are some validation scenarios a typical cost request goes through.
Question: What validations does the Xvantage Global Cost Engine (GCE) perform before a cost update is sent to Impulse or the GDL?
Answer:
Ingestor - Once an XCM sends and stores all the cost update changes on GDL, the GCE Ingestor retrieves the relevant VPN-level information from GDL and passes it to the Rules Engine in the form of Json for further processing.
XRE - Once a VPN is ingested into GCE, the XRE (Rules Engine) runs all applicable business rules configured at both VPN and SKU levels. The system performs VPN-level checks initially. If SKUs exist under that VPN, each one undergoes SKU-level validation. The Rules Engine returns the validation results for each VPN/SKU to the Ingestor, and the Ingestor saves these results along with the associated data in the database.
UI -The UI fetches the data, and the validation results from the DB and displays them on the Cost Exceptions screen. The following are the file level and VPN level statuses that we sow on the UI for exceptions:
File Level statuses with definition:
Needs review - Has updates or exceptions that needs to be addressed.
Processing - Changes have been submitted and are currently processing.
Completed - All processed, approved, with no updates or exceptions. Cost updates have been published
Cancelled - The file is cancelled.
Inactive - If the file is overwritten.
Processed - All processed, approved, with no updates or exceptions. Cost updates have NOT yet been published
VPN Level statuses with definition:
Needs approval – The update has an exception that must be handled manually by the user.
Approved – The update is approved and will be published on the effective date.
Integrator - When the cost update flow is for a Non-transactional SKU, the integrator picks the cost update and stores it in GDL. While for a transactional SKU, the cost updates are sent to the Impulse at SKU level for further validation. All based on the response from Impulse; we display statuses to notify the user on their next steps.
SKU level statuses with definition:
Processing - Update is currently being processed.
Pending - Update is in queue to be processed.
Needs review - Rejected in ERP; review and respond accordingly.
Needs manual review - Accepted in ERP; requires manual cost change. Contact your approver.
Completed – The updates are successfully published.