3 hours ago
I need technical support; a technical analysis that would answer the following question: Is there any BAdI I could use to properly select the production version when creating a Purchase Requisition (PR) via the BAPI_PR_CREATE BAPI, and then later during the conversion to a Purchase Order (PO) via BAPI_PO_CREATE1?
This is a special scenario in which the user has a single PIR, but several production versions, which they define in transaction CMPDS1.
For the creation of the PR, I managed to use the BAdI MD_MODIFY_PRODVERS, where I select the appropriate version, and the created PR has the version I require. Unfortunately, further down the line - during the conversion of the PR to a PO - this BAPI is also called within the flow, but it is too late, and changing the version there does not work (because, unfortunately, the original flow takes the version automatically from the PIR, whereas I want a different version than the one in the PIR). The change made at this enhancement stage does not take effect. The converted PO ends up, unfortunately, with the version from the PIR (even though, for example, the PR from which it was converted has a different version — the one I previously forced via the BAdI MD_MODIFY_PRODVERS).
Is there any other way to force a version different from the one in the PIR?
Previously, I did this using an implicit enhancement in the FORM COMEX_FUELLEN within the function module ME_SEARCH_VERID_PO. Unfortunately, I would like to achieve this using a standard BAdI rather than an implicit enhancement.
Request clarification before answering.
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.