Kontakt

Ansicht
Dokumentation

CRMV_EOP_APPLOBJ - Define Handler Class for Application Objects

CRMV_EOP_APPLOBJ - Define Handler Class for Application Objects

Vendor Master (General Section)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you define handler classes for application objects.

The classes define which application objects are included in the End of Purpose Check (EoP).

SAP delivers the standard application object 1Order Application for Service.

You can define the start of the retention date for the application object 1Order Applicationunder Define Start of Retention Date. All other business transactions inherit this setting unless otherwise defined in that Customizing activity.

You can create your own application object implementation for the EoP check to suit your business needs.

To implement your own handler class, make the following settings:

  1. Inherit the class CL_CRM_EOP_CHECK or directly implement the interface IF_CRM_EOP_DET. The class CL_CRM_EOP_CHECK already provides an implementation for some interface methods. If they apply to your business needs, you can reuse them.
  2. Implement the interface methods if necessary:
    1. IF_CRM_EOP_DET~DETERMINE_ILM_OBJECT
Given a business transaction GUID, this method determines the corresponding ILM object.
  1. IF_CRM_EOP_DET~DETERMINE_OBJECT_TYPE
Given a business transaction GUID, this method determines the corresponding (generic) object type that corresponds to the (generic) object types defined under Define Available Application Objects.
  1. IF_CRM_EOP_DET~DETERMINE_TRANSACTION_TYPE
Given a business transaction GUID, this method determines the corresponding transaction type (process type).
  1. IF_CRM_EOP_DET~GET_PARTNERS_OF_TRANSACTION
Given a business transaction header GUID, an indicator that shows whether the related business transaction is completed. This method determines all business partners that are related to the business transaction at both header and item level.
  1. IF_CRM_EOP_DET~GET_HI_GUIDS_OF_PARTNERS
This method is the opposite of GET_PARTNERS_OF_TRANSACTION since it determines all business transactions (headers and items) to which the business partners specified are related.
  1. IF_CRM_EOP_DET~DETERMINE_OPEN_TRANSACTIONS
This method determines for each of the given business partners whether or not there are open transactions left (business transactions that do not have status completed).
  1. IF_CRM_EOP_DET~DETERMINE_END_OF_BUSINESS
This method determines the start of retention for the given business transaction header as well as for the related items.
  1. IF_CRM_EOP_DET~CHECK_TRANSACTION_IS_COMPLETED
For a given business transaction header GUID, this method checks whether the header is completed and also if each item is completed.
  1. IF_CRM_EOP_DET~DETERMINE_HEADER_GUIDS
This method determines all business transactions that were created in the given date interval.
  1. IF_CRM_EOP_DET~DETERMINE_CONDITION_FIELDS
Given a business transaction GUID, this method fills a table of ILM condition fields with values from the business transaction.
  1. IF_CRM_EOP_DET~DETERMINE_ALL_OBJ_WITH_OPENTRX
This method determines all business transactions that are not completed for all given partners.






rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4272 Date: 20240523 Time: 151915     sap01-206 ( 62 ms )