SAP Function CACS00_SAMPLE_PRC_1100 - Additional Data from PD-Org

Parameter Reference Type Length Default Optional Text
I_APPL CACSAPPL C 6 Commission Application Identification
I_CASE_PREV CACS00_CAS u 586 Commission Case
I_DOC_HEAD_PREV CACS00_DOCHD u 547 Commission Document Header
I_META_CASE CACS00_S_CASM u 642 Commission Case (Meta Object)
I_TRI_METH_TARGET CACS00_S_CASM-TRI_METH_TARGET C 1 Processing Target of Triggering Method

Parameter Reference Type Length Text
E_TRI_METH_TARGET CACS00_S_CASM-TRI_METH_TARGET C 1 Processing Target of Triggering Method

Parameter Reference Length Optional Text
C_META_INVESTIGATION CACS00_S_INVM 188 Commission Case Participant (Meta Object)
C_META_PARTICIPATION CACS00_S_PARM 58 Commission Case Participation (Meta Object)
I_META_ACTIVITY CACS00_S_ACTM 130 Commission Activities (Meta Object)
I_META_LINES CACS00_S_LINM 248 Alternative Commission (Meta Object)
I_META_OBJECTDATA CACS00_S_OBJM 140 Commission Object Data (Meta Object)


DEFINE &TEXT& = 'Additional Data from PD-Org'
DEFINE &EVENT& = 'CACS1100'
DEFINE &TYPE& = 'PRC'
INCLUDE CACS_BTE_DOCUMENTATION_PRC01 OBJECT DOKU ID TX

Issuing Messages / Documentation of Error
You should document the occurrence of an error as described in the Example below.
Abap_icon_exclstatus_version is only changed if an error is found. thefield must not be reset, otherwise the error documentation of theprevious process steps is destroyed.
If an error occurs, it is absolutely necessary to write an error messagein the log of the process (this error message has the same function asthe parameter FLG_ERROR that exists in previous releases).
To find out whether an error message has already been issued in theprocess, the static method LOG_HAS_ERROR_MSG( ) of class CL_CACS_BAL_STcan be used. This method returns TRUE if a message of type A or E iswritten to the process log. If no log handle is specified at callup, thecurrent default handle CACS_BUFFERLOG that is buffered in function groupCACS_BUFFERLOG is examined. A query of the process status then lookslike this: IF CL_CACS_BAL_ST=>LOG_HAS_ERROR_MSG( ) = TRUE.
Likewise, the static method LOG_HAS_ABEND_MSG( ) can be used for queriesof message type A.

Example
INCLUDE CACS_GLOBDEF. " <(><<)>= Include CS constants
IF <(><<)>error situation exists>.
* Tell process that error exists, i.e. object is set to pending
* Select object line
c_meta_participation-status_version = statusvers_inconsistent.
* Convert parameter to types of MESSAGE module
sy-msgv1 = i_tri_meth_target.
sy-msgv2 = c_meta_participation-status_version.
* Allow message navigation with this query
IF 1 = 0.
MESSAGE e484(cacsib)
WITH i_tri_meth_target.
c_meta_participation-status_version.
ENDIF. " SE91
* Write message to log file
CALL FUNCTION 'MESSAGE_STORE_WITH_DISPLAY'
EXPORTING
arbgb = 'CACSIB'
msgty = 'E'
msgv1 = sy-msgv1
msgv2 = sy-msgv2
txtnr = '484'.
ENDIF.
INCLUDE ISIS_HELP_PORTAL_TOOLS_BTE OBJECT DOKU ID TX

Description
A technical construction to encapsulate a complete commissionapplication, including its master data and transaction data.
The following belongs to the context of commissions:
o Interfaces of commission system
o Rules (definition and attributes)
o Business partner role
o Master data administration
o Ledger/account (also for pending contracts)
o Reporting system

Description
The structure contains the historical data for the commission case.

Description
The structure contains the historical data for the commission casedocument header.

Description
The structure contains the relevant data for the commission case.

Description
The table contains the participants for the commission case.

Description
The table contains the participations of the the commission case.

Description
The table contains the commission case activities of the commissioncase.

Description
The table contains the different commissions of the commission case.

Description
The table contains the object data of the commission case.