Isu Contract Table in Sap Crm

Delivery class: A – Application table with master and transaction data Display/maintenance via SM30: Yes, but with restrictions Extension Category i: Can be extended (character type or numeric) For more information about this category and other SAP improvement categories Billing and billing module, explain the process that starts with invoicing and ends with invoice printing. (Source) Here is the standard documentation available and some details about the fields that make up this table. For more information about SAP EVER_CRMQ table and the data it contains, you can view relevant transactions such as SE11, SE80, or SE16. Also see the Comments section below to see or add related articles and sample screenshots. The billing cycle in ISU view begins with the creation of meter reading orders (MROs) and ends with the creation of the respective invoices (also known as printing documents). (Source) The IS-U master data model can be divided into two main groups EVER_CRMQ – ISU Contract CRM-Entry Queue EVER_AUDIT – IS-U Audit Flags for Contracts EVER_ARCH – Contract with Time Slices for Archiving EVERX – IS-U Contract: Indicator for Obsolete Data EVERU – IS-U Contract: Move-in/out Fields EVERTRAGINFO – Contract Environment “All master data used for the actual provision of services, are grouped under Technical Data. Planning groups the subdivision of the service area into portions (billing units) and meter reading units in the system and generates appointments for the following functions: EVER_CRMQ is a standard SAP table used to store ISU-Contract CRM input queue data and available in R/3 SAP Systems based on version and version level. For example, a device or meter installed at a customer`s site. (Source: SAP IS-U Data Model) Device Management manages technical data, installations, meter readings and equipment inspection. .