SAP VA41/42 Discount Workflow
Budget: ₹400 – ₹750 INR
I need a small but reliable SAP-SD workflow that sits on transactions VA41 and VA42. The logic is simple:
• If the user saves the quotation or contract without touching the existing price condition types, it should post straight through—no approvals—then automatically create the follow-on billing document.
• If any discount is entered (the fixed-amount discount condition type that already exists in our pricing procedure), the standard SAP Business Workflow must start. The workflow should route to the person defined in the corresponding approval path and send that individual an SAP inbox / Fiori notification the moment their step becomes active.
• Once the final approver releases the document, the system must create the invoice automatically with no further manual steps.
I will provide the existing condition type, organisational data and basic approval matrix. What I expect back is:
– A configured workflow template transported to QA (include object type enhancements or ABAP classes if you choose that route).
– Unit-test evidence covering the two scenarios above.
– A short hand-over note describing where the logic lives, how to tweak approvers, and any new authorisations required.
If you have solid SAP Business Workflow or ABAP OO experience and can keep the solution clean—ideally no hard-coding—I’d like to hear your approach and timeline.
• If the user saves the quotation or contract without touching the existing price condition types, it should post straight through—no approvals—then automatically create the follow-on billing document.
• If any discount is entered (the fixed-amount discount condition type that already exists in our pricing procedure), the standard SAP Business Workflow must start. The workflow should route to the person defined in the corresponding approval path and send that individual an SAP inbox / Fiori notification the moment their step becomes active.
• Once the final approver releases the document, the system must create the invoice automatically with no further manual steps.
I will provide the existing condition type, organisational data and basic approval matrix. What I expect back is:
– A configured workflow template transported to QA (include object type enhancements or ABAP classes if you choose that route).
– Unit-test evidence covering the two scenarios above.
– A short hand-over note describing where the logic lives, how to tweak approvers, and any new authorisations required.
If you have solid SAP Business Workflow or ABAP OO experience and can keep the solution clean—ideally no hard-coding—I’d like to hear your approach and timeline.