mass processing function for production/process orders - set deletion flag

[#1]

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.

[dejoy]

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,

[sven_schneider2]

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

[dejoy]

Hello Sven,

yes you are right as its intended for archiving but i used it once for the same purpose though i have not tried to reset,so i am not aware about the issue you might face in resetting.

     If i found any reference to 260/270,will update here.

Regards,

[sven_schneider2]

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":

• in COAC(COA5) you need archive/delete rights with C_AFKO_ATY, ACTVT=06
  
  
• in COR2/COOSPI you need only C_AFKO_ATY, ACTVT=02 (only set deletion flag possible)
  This is the same for COHVPI and mass processing functions 260/270 or corresponding BAPI's
  BAPI_PROCORD_SET_DELETION_FLAG / BAPI_PROCORD_SET_DEL_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