Fonction SAP CACS00_SAMPLE_PRC_1099 - Context Postprocessing of a Commission Case

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
IFLG_MASS_PROCESS BOOLEAN_FLG C 1 Mass Processing? (See Documentation)
IFLG_SIMULATION CACSSIMULATION C 1 Process should be carried out in simulation mode
I_APPL_VERSION CACSGENVERSION N 6 Version of Generated Application
I_CASE CACS00_CAS u 586 Reported Commission Case (See Documentation)
I_DOC_HEAD CACS00_DOCHD u 547 Resulting Document Header

Paramètre Reférence Long. Facultatif Description
I_ACTIVITY CACS00_ACT 92 Reported Activities for Case
I_BUNDLE CACS00_BDL 181 Rebundling Order for Triggering Subobjects
I_DOC_ACTIVITY CACS00_DOCACT 42 X Commission Document: Activities
I_DOC_INVESTIGATION CACS00_DOCINV 77 X Participant in Commission Document
I_DOC_OBJECTDATA CACS00_DOCOBJ 109 X Commission Document: Object Data
I_DOC_PARTICIPATION CACS00_DOCPAR 38 X Participation of Commission Document
I_DOC_RELATIONS CACS00_DOCREL 78 X Commission Document: Relationships Between Participants
I_DOC_REMDETAIL CACS00_DOCDT 113 Comn: Detail Items for Remuneration Rows
I_DOC_REMUNERATION CACS00_DOCRE 368 Determined Remuneration for ComnDoc
I_DOC_SETTLEMENT CACS00_DOCSE 202 Determined Due Dates for Settlement
I_DOC_VALUATION CACS00_DOCVA 138 Determined Valuations for ComnDoc
I_INVESTIGATION CACS00_INV 100 Reported Participants in Participation
I_LINES CACS00_LIN 207 Reported Variances (Special Commission) for Case
I_OBJECTDATA CACS00_OBJ 140 Reported Object Descriptions for Activities
I_PARTICIPATION CACS00_PAR 32 Reported Participation(s) in Case
I_RELATIONS CACS00_REL 71 Reported Relationships Between Participants


DEFINE &TEXT& = 'Context Postprocessing of a Commission Case'
DEFINE &EVENT& = 'CACS1099'
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
* Convert parameter to types of MESSAGE module
sy-msgv1 = E_TRI_METH_TARGET.
* Allow message navigation with this query
IF 1 = 0.
MESSAGE e484(cacsib)
WITH E_TRI_METH_TARGET.
ENDIF. " SE91
* Write message to log file
CALL FUNCTION 'MESSAGE_STORE_WITH_DISPLAY'
EXPORTING
arbgb = 'CACSIB'
msgty = 'E'
msgv1 = sy-msgv1
txtnr = '484'.
ENDIF.
INCLUDE ISIS_HELP_PORTAL_TOOLS_BTE OBJECT DOKU ID TX