on 09-23-2013 10:27 PM
With SAP ERP 6.0 EHP3 and activating business function LOG_PP_MIS you get new functions for mass processing of production-/process-orders.
In compound with Transaction CISL you can change list types and correspondig mass processing functions.
There are two new undocumented mass processing functions for production-/process orders with list type order header PPIOH000 (transaction COHV/COHVPI):
260 Set Deletion Flag
270 Set Deletion Indicator
At least "260 set deletion flag" function seems to be working.(I could only test this)
Before activating of business function LOG_PP_MIS these two mass processing functions were explicitly inactivated in function module CO_WORK_REGISTERED_FUNCTIONS_S.
(look for constants cowrk_c_fct_delflag or cowrk_c_fct_delind / comment "also delete functions which are not supported in COHV yet")
Does anyone know whether these functions were officially released or where they are documented?
Otherwise we would have to implement a class with BAPI_PROCORD_SET_DELETION_FLAG with integration into the navigation profile of COVH / COHVPI.
That's what I wanted to avoid, if there is already a standard implementation.
Hello Sven and Dee,
any News on this Topic? what are your experiences? Do you use the functionalities?
regards
and thanks
Horst
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here the answer from SAP Enterprise Support :
The mass processing functions
- Set deletion indicator
- Set deletion flag
are implemented at least since ECC 6.0. In
addition the BAPIs for the process orders support these 2 functions as well.
With the business function LOG_PP_MIS available in ERP 6.0 EhP3 it is possible to
activate COISL (change list types). With this transaction you can select the two
functions also for mass processing in COHVPI. So, these functions are
officially released and supported.
Unfortunately, this is not yet documented
(in the official documentation nor in the release note). -> We will do this
in the nearer future.
If you need an official note, we could
update an FAQ note asap.
Sven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your fast reply!
So, I guess that you activated LOG_PP_MIS (see also note 1819470) , changed PPIOH000 in COISL and restricted access to those new functions? If so, then how?
Thanks again
regards
Horst
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Horst,
hope I understand your question?
First activate BF LOG_PP_MIS.
(In SFW5 check, that there are no activation error. If so, resolve them.)
We have then add function "260 Set deletion flag" in COISL.
Restrict access to these functions --> see my posts above or FM-documentation to the corresponding BAPI in SE37. (use authority object C_AFKO_ATY in your PFCG role)
Hello Sven,
Its good to know that these functions provided in LOG_PP_MIS but i also did not find any documentation or release info.
you can use t-code CO78 as another option to flag deletion.Here choose first option"deletion flag/deletion indicator" only and flag collectively.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello dee,
yes, but CO78(COA1)/COAC(COA5) or report PPARCHP1/PRARCHP1 are not really intended for production planner or production staff.
This transactions/reports are something for an archive administrator in conjunction with an archive concept.
And if you accidentally marked "set deletion indicator" here, there is normaly no way back. (see note 191216)
In addition, with activating BF LOG_PP_MIS and transaction COISL (typo above
) you can only customize "260 Set Deletion Flag" for mass processing transactions COHV/COHVPI.
The same as in COR2.
But my initial question was:
Does anyone know whether these functions were officially released or where they are documented?
Or in other words, can I use this function safely?
Regards Sven
Hello dee,
thanks for your replies.
But there is a further reason, why we can't use these archive functions.
Authority makes the difference for functions "set deletion flag/indicator":
Our "normal" users don't have archive/delete rights to C_AFKO_ATY (or generelly to S_ARCHIVE).
This applies to all SARA related archive objects.
Sven
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 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.