<b>PO number duplication Issue that you are facing has following options to solve:</b>
Options:
I) At config level we can bring about a change and we can generate a warning message.
Process:
In standard config of Sales doc type we have “Check Purch Order no” field.
This has to be changed from blank to “A” to generate a “Warning Message”. (Set up in incompletion log)
In this case user will still be in a position to save the order because it is just a warning message.
Feasibility:
As most of the orders are generated through IDOC’s these days, this will NOT work and IDOC’s can be reprocessed to reach status 53.
Options:
II) In Standard program of VA01, we need to use a user exit.
Process:
Program running in the background of VA01 t-code is: SAPMV45A
Under this standard SAP program we have another main program: SAPLXVVA
Under this we have 3 user exits, out of which one will be responsible for processing the PO numbers in orders
User Exit available is:<b> ZXVVAU09</b>
This will check the PO number in the sales booking screen for the first time. VA01 - Create with reference to another order and PO number.
Once again it will check the PO number in the main screen of sales order (VA01 - Create without reference) once we key in the PO number, it validates and returns to the item level.
So we can have user exit ZXVVAU09 modified in such a way that it stops processing the order by giving an ERROR.
Feasibility:
This can be done using the user exit ZXVVAU09 provided we get the complete business process of customer and match it with this code, types of orders they use and restrict this to specific sales org only. This will not have an impact on other sales organizations.
Feel free to revert with questions
Regards,
Syed Nasir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.