I have the need after a sales order is created via the BAPI to add a characteristic that will hold the sales order number. I do not need to know how to do this without causing a commit issue, suffice it to say that we know how to handle that and have been since 2008 and that is not where I need the help.
Where I need the help is what function module or method do I call given that I have a sales order line with a filled in CUOBJ field in VBAP that I can then "force set" (my term) a custom characteristic that would hold the order number. We can get this to work via VA01 because it creates the line first and then the other stuff and the order line information is already available. However, when run via the BAPI, it's all done at once and then there is a large COMMIT at the end so doing what works with VA01 will not help here.
So what I'm looking for ideally is a function module that takes in a an order number (VBAP-VBELN) and object ID (VBAP-CUBOJ) value and the name of the characteristic and then takes the order number and stores it as a value for that characteristic. The characteristic will just be a stand-alone one and will not be part of any logic that determines what to do, our functional people wanted it this way so they could gather all the config attributes later on.
I did search the CU package but there is a lot there and I'm not that familiar with it and I did search the community before posing this question.
Even if the solution requires another call to either commit the change or to cause a reconfig that would be acceptable. In the case of the reconfig I would need to know the name of that as well.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.