/SAPAPO/OM_PLAN_VERSION_CHANGE - Create/Change/Delete Planning Versions in liveCache

ABAP Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Functionality

The pegging areas specified in table IT_PLAN_VERSION are created/changed/deleted. The operation to be performed depends on the data in the METHOD field in T_PLANV_VERSION:

• If METHOD = GC_NEW:
  The plan version with key CLIENT, SIMVERSION is created. Whether loggingand/or ATP time series update is active for this plan version depends on the RECORDING or ATP_UPDATE fields. However, both of these features can only be activated for an active plan version (SIMVERSION='000').

• If METHOD=GC_CHANGE:
  For existing plan versions with key CLIENT, SIMVERSION, the RECORDING and ATP_UPDATE parameters are reset. However, these two features can only be switched off.
  Note: It is not possible to switch them back on again subsequently!

• If METHOD = GC_DELETE:
  The pegging area with key CLIENT, SIMVERSION is deleted. All liveCache objects belonging to this plan version are also deleted.

ET_RC contains return codes for plan versions with processing errors.

NOTE: For technical reasons, a COMMIT WORK is set against the liveCache at the start of this functionmodule. Furthermore, this function module cannot be rolled back. This means that any changes made here are immediately stored in the liveCache by autocommit.

Example

Notes

Further information

Parameters

ET_RC
IT_PLAN_VERSION
IV_AFTER_INIT_LC
IV_DONT_SET_NETCHG_FLAG
IV_WRITE_LOG

Exceptions

LC_APPL_ERROR
LC_COM_ERROR
LC_CONNECT_FAILED

Function Group

APO/SAPLOM_CORE

Addresses (Business Address Services)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.


Length: 1749 Date: 20120525 Time: 045541     triton ( 75 ms )