Hello,
We person customized programme for Production orders confirmation. It uses BAPI_PRODORDCONF_CREATE_TT.
I deliberation determination is immoderate known issue, erstwhile sometimes entries are stuck successful CO1P owed to posting successful update mode. As advised, to debar CO1P entries BAPI_GOODSMVT_CREATE tin beryllium used.
But unluckily for america it is not an option.
>> The process we have:
1. Users corroborate Production orders done customized tool
2. Background occupation for CORUPROC is tally each 5 minutes
>> The problems we have:
1. Sometimes during confirmation users disregard the information that Goods receipt did not happen. They spot that thing happened and station it 1 much time. Later CO1P is processed and we person situation, that Goods receipt were duplicated.
2. Sometimes erstwhile idiosyncratic is moving with peculiar Production bid and astatine the aforesaid clip the occupation CORUPROC is processed utilizing the aforesaid order. It leads to receiving introduction successful CO16N with mistake "User locks the order" which tin beryllium processed lone manually.
>> So the question is however it is amended to debar the issues? If we tin not re-design the program, astir apt we tin adhd cheque giving to idiosyncratic the restricting message.
1. I'm not definite successful which infinitesimal entries spell to CO1P. Is it imaginable during confirmation to drawback it and amusement to idiosyncratic the message, benignant of: "Goods receipt is stuck successful CO1P..." ?
2. If constituent 1 is possible, is it imaginable to separate CO1P introduction from entries COGI and CO16N?
3. If it is not imaginable to drawback CO1P introduction during confirmation. Probably aft confirmation, hold a fewer seconds and past cheque AFFW array and springiness the connection if entries are found? But however to separate CO1P introduction from entries COGI and CO16N?
4. Any different options oregon hints? Maybe I request to deliberation successful different direction.
Thanks.