TRTCRMPE processing: Call processing for the CRM module EPs

CLLOBJ: Definition of the OBJect for a call generated by call campaigns

This entry point intervenes within the distribution matrix for the calls from the call campaign assistant. It is used to define a personalized objective for each call generated by this assistant.

For example, this latter is particularly useful within the framework of a call campaign for unpaid reminders. The entry point can then calculate the amount remaining due for each correspondent to be contacted and to make them appear on the call to be carried out.

When the definition of the call objective is carried out via this entry point, the CLLCMGOMP parameter has no effect for the call in question.

This entry point is linked to miscellaneous table 456. A specific entry point must match each record in this miscellaneous table. The name of the operational entry point for a record in the miscellaneous table where the code is A1 is displayed in the form : CLLOBJ_A1.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called for each telephone call being created by the distribution matrix. The [F] class for the call to be created is partially entered. The chrono number for the call has already been calculated and is available in the following two variables: [F:CLL]CLLNUM or SZCLLNUM. The call has not yet been created physically in the database.

Available variables and masks

IFULOBJBYPE: This variable is tested for each call. It is always initialized to zero before each call to the entry point. If its value remains null, the objective of the call is defined according to the value of the CLLCMGOMP parameter. If its value is positive, the call objective will then be loaded with the content of the CLBCLLFULOBJ clob variable.

CLBCLLFULOBJ: This variable initialized to empty before each call to the entry point must be filled with the complete text to be displayed for the call to be carried out. The maximum size of the text is conditioned by the size of the clob type defined on the data type HD5.

SZSUMUP: This variable of 235 characters can contain a summary or a complete text entered in the CLBCLLFULOBJ variable.

GSZOPGNUM: This information variable contains the code for the call campaign being created via the assistant.

SZBPRNUM: This information variable contains the code for the business partner to be called.

SZCCNNUM: This information variable contains the code for the contact to be called.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

OMMXML: XML additions specific to a mass-mailing

This entry point intervenes within the generation of an XML type mass-mailing. It is used to complete the XML document during the generation with the information excluded from the capacities of the standard setup of the XML mass-mailings.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called for each recipient of the mailing just before the write to the end of record tag (tag associated for the field : Object XML).

Available variables and masks

SZBULLTOFILL: Variable of 250 characters that forms the write buffer. Once checked, its content can be written in the XML file via a line of code such as :

Wrseq SZBUFFTOFILL Using [FXML]

SZOPGNUM: Information variable containing the code for the mass-mailing being generated.

SZMXL: Information variable containing the code of the XML mass-mailing setup used for the generation.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

MGCDEDIT: Specific/custom report definition for the printing of data for a targe

This entry point intervenes before the printing to view or to extract the data for a target. It is used to personalize the reports used.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called after the generation of the data for the target, before the start of the printing.

Available variables and masks

MAINSREFLT: Total consideration of the selection panel for a service request

This entry point is used to take the entire responsibility on the content of the different browsers of the selection panel forming the Service request object.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called at the start of the FILGAUCHE action for the Service request object.

Available variables and masks

IMAINSREPEFLT: This variable is initialized to zero before each call to the entry point. If the entry point must take responsibility for the selection panel content, it must be assigned with a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose. (currbox, FILGAUCHE, FILGAUSUP...)

GSRECTRNUM: Entry transaction currently being used.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

SREFLT: Complex filter on the additional browsers for the service requests

This entry point is used to take the entire responsibility for the content of the browsers of the additional selection panels defined by the entry transaction being used. When this entry point is active, the filters carried by the entry transaction are ignored.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called from within the FILGAUCHE action of the Service request object but only for the additional browsers.

Available variables and masks

ISREPEFLT: This variable is initialized to zero before each call to the entry point. If the entry point must take responsibility for the content of the additional browsers, it is necessary to assign a positive value to it. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose. (currbox, FILGAUCHE, FILGAUSUP...)

GSRECTRNUM: Entry transaction currently being used.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

MAINITNFLT: Total consideration of an intervention selection panel

This entry point is used to take the entire responsibility for the content of the different browsers of the selection panel forming the Interventions object.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called at the very start of the FILGAUCHE action of the Interventions object.

Available variables and masks

IMAINITNPEFLT: This variable is initialized to zero before each call to the entry point. If the entry point must take responsibility for the selection panel content, it must be assigned with a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose. (currbox, FILGAUCHE, FILGAUSUP...)

GITNCTRNUM: Entry transaction currently being used.

 Open tables

In the table below, the significant content flag indicates that the content matches the context.

ITNFLT: Complex filter on the additional browsers for the interventions

This entry point is used to take the entire responsibility for the content of the browsers of the additional selection panels defined by the entry transaction being used. When this entry point is active, the filters carried by the entry transaction are ignored.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called within the FILGAUCHE action of the Interventions object but only for the additional browsers.

Available variables and masks

IITNPEFLT: This variable is initialized to zero before each call to the entry point. If the entry point must take responsibility for the content of the additional browsers, it is necessary to assign a positive value to it. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose. (currbox, FILGAUCHE, FILGAUSUP...)

GITNCTRNUM: Entry transaction currently being used.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

MAINMACFLT: Total consideration of the selection panel for a customer installed

This entry point is used to take the entire responsibility for the content of the different browsers of the selection panel forming the Customer installed base object.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called at the very start of the FILGAUCHE action of the Customer installed base object.

If this entry point is activated, the counting of the installed base records and for the physical quantity of the filtered installed base must be carried out by the entry point.

Available variables and masks

IMAINMACPEFLT: This variable is initialized to zero before each call to the entry point. If the entry point must take responsibility for the selection panel content, it must be assigned with a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose. (currbox, FILGAUCHE, FILGAUSUP...)

GMACCTRNUM: Entry transaction currently being used.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

MACFLT: Complex filter on the additional browsers for the customer installed bas

This entry point is used to take the entire responsibility for the content of the browsers of the additional selection panels defined by the entry transaction being used. When this entry point is active, the filters carried by the entry transaction are ignored.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called within the FILGAUCHE action of the Customer installed base object but only for the additional browsers.

Available variables and masks

IMACPEFLT: This variable is initialized to zero before each call to the entry point. If the entry point must take responsibility for the content of the additional browsers, it is necessary to assign a positive value to it. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose. (currbox, FILGAUCHE, FILGAUSUP...)

GMACCTRNUM: Entry transaction currently being used.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

AUTINVCFIL: Add selection criteria for contracts to be invoiced

This entry point is used to insert additional logic during the definition of the selection criteria for the contracts to be invoiced.

It is used to add additional filters on these contracts.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is an open log file.

Call context

This entry point is called during the selection criteria definition.

Available variables and masks

The selection mask for contracts [M :DIA] (SAUTINVC) is still available.

The standard criteria are loaded in the CRITERE variable.

The FILSUP variable has been created to add these additional criteria.

This variable is sized at 250 characters. To ensure operations during the evaluation, FILSUP is initialized to the string "1=1" if these variables have not been loaded by the entry point.

It is sufficient to complete it in the entry point.

For example: Add an additional filter on the customer that must start with "CLI".

FILSUP -= ‘ & CONBPC >= "CLI"’

FILSUP is evaluated at the same time as CRITERE during the filter on the CONTSERV file. The criteria must relate to the fields in the CONTSERV file.

Open tables

In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…). It is usually the case for the file containing the header, but not for the file containing the lines…

AUTINVSFIL: Add selection criteria for requests to be invoiced

This entry point is used to insert additional logic during the definition of the selection criteria for the service requests to be invoiced.

It is used to add additional filters on these requests.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is an open log file.

Call context

This entry point is called during the selection criteria definition.

Available variables and masks

The selection mask for requests [M :DIA] (SAUTINVS) is still available.

The standard criteria are loaded in the CRITERE variable.

The FILSUP variable has been created to add these additional criteria.

This variable is sized at 250 characters. To ensure operations during the evaluation, FILSUP is initialized to the string "1=1" if these variables have not been loaded by the entry point.

It is sufficient to complete it in the entry point.

For example: Add an additional filter on the customer that must start with "CLI".

FILSUP -= ‘ & SREBPC >= "CLI"’

FILSUP is evaluated at the same time as CRITERE during the filter on the SERREQUEST file. The criteria must relate to the fields in the SERREQUEST file.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

FEEDHDI: Change or addition to the billable service request lines

This entry point intervenes at the time of the closing of a service request and any generation of billable consumption lines. It is notably used to change certain of these lines or even to add other additional elements to be invoiced.

Context and operating mode

Transaction

There is no transaction in progress. The generation of the consumption lines is completely finished and confirmed.

Log file

There is no open log file.

Call context

This entry point is called once after all the consumption lines have been generated and aggregated.

Available variables and masks

SZSRENUM: Information variable containing the code for the service request currently being closed.

 Open tables

In the table below, the significant content flag indicates that the content matches the context.

RVACON: Re-evaluation of a service contract according to the formula

This entry point is used to carry out the re-evaluations of the service contract that are not based on the evolution of an index. This entry point is generally called on the invoicing of an open item in the service contract. This field is linked to miscellaneous table 427. A specific entry point must match each record in this miscellaneous table.

For example, the true operation name of the entry point associated with record A1 will be : RVACON_A1.

Context and operating mode

Transaction

The re-evaluation of the service contracts intervenes in many different contexts. Certain re-evaluations are executed within a transaction while others take place outside of any transaction. It is therefore advisable to always test for the presence of a transaction by using the adxlog variable.

Log file

There is no open log file.

Call context

This entry point is called once a re-evaluation (of the Mathematical formula type) of the basis of the annual fee for a service contract is detected as necessary by the system.

Available variables and masks

IRVACONPRI: This variable must contain the new basis for the annual fee calculated by the entry point for the re-evaluated contract.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

SIHCON: Calculation of the amount for a service contract open item in an invoice

This entry point is used to take control of the calculation of the amount for a service contract open item at the time of its invoicing.

This entry point is activated, this latter must then take in hand all the controls related to the re-evaluations and automatic renewals for the invoiced contract.

Context and operating mode

Transaction

This entry point is called from a number of different contexts. It is therefore advisable to always test for the presence of a transaction by using the adxlog variable.

Log file

There is no open log file except in automatic invoicing.

Call context

This entry point is called during the initialization of each invoice line related to the service contract open item.

Available variables and masks

IPEONLY: This variable is used to activate the control of the open item calculation by the entry point. Before each call to the entry point, this variable is initialized to zero. If a positive value is assigned to it, it activates the execution of the entry point.

IPRIX: The result of the open item amount calculation by the entry point must be returned in this variable.

IOLDCONAMT: This variable contains the basis of the annual fees for the contract currently being invoiced.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

ESCCND: Execution conditions for the escalations

This entry point is associated with miscellaneous table 454 that is used to describe all the execution conditions for the different escalations defined in the application.

Its operational name is made up of its identifier followed by the code for the associated miscellaneous table. For example, for a miscellaneous table code A1, the associated entry point is ESCCND_A1.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called each time it is necessary to control if an escalation must be executed. This control intervenes at each creation or modification of a service request or even during an analysis by the batch server for all the active service requests.

Available variables and masks

IEXECESC: Variable that is used to indicate the result of the evaluation of the condition by the entry point. It the entry point returns 1, the escalation will be executed. If the entry point returns 0, the escalation will not be executed.

SZSRENUM: This variable contains the code for the escalated service request.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

ESCACT: Execution of an escalation action

This entry point associated with miscellaneous table 455 is used to describe all the actions executed by the different escalations defined in the application.

Its operational name is made up of its identifier followed by the code for the associated miscellaneous table. For example, for a miscellaneous table code A1, the associated entry point is ESCACT_A1.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called each time one of the execution conditions for the escalation is fulfilled. This entry point can be called up to ten times under different names for a single escalation.

Available variables and masks

SZSRENUM: This variable contains the code for the escalated service request.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

SAVEUDE: Management of the specific/custom fields when deleting requests

This entry point is used to take control of the additional specific/custom fields during the recording of a service request deletion tracking. The fields in question have been added to the UDDDELSRE table. Their checks at the time of the deletion must be assured by the entry point.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is no open log file.

Call context

The call to the entry point takes place just before the write of the deletion entry in the UDDDELSRE table.

Available variables and masks

GSZUDDDELSRENUM: This variable contains the service request code currently being deleted.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

LOADUDE: Management of the specific/custom fields when displaying the request de

This entry point is used to display the additional specific/custom fields in the inquiry window for the tracking of the service request deletions. The fields in question have been added to the UDDDELSRE table. Their loading in the UDD7 screen must be assured by the entry point.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called for each deletion tracking record corresponding to the selection criteria for the selection of the inquiry window.

Available variables and masks

the UDD7 mask is accessible in its totality.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

MACMCC: Specific/custom aggregation for the installed base inquiry

This entry point intervenes in the aggregated installed base inquiry.

It is used to aggregate this inquiry on the basis of the additional specific/custom fields.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called once an aggregation is requested on the basis of a non standard field. If required, the entry point must ensure to totally load it in this inquiry.

Available variables and masks

The MCC1 mask is accessible in its totality.

The aggregation field is accessible in the variable [M:MCC1]FIE.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

CUSRUL: Personalized integration rule for the customer installed base

This entry point is used to create the integration rules for the specific customer installed base. This entry point is executed when the integration component of the base (MACRULE, TRTMACRULE processing) is called with an action code equal to 7. In this case, the integration of the installed base and of service contracts is the only purpose of the entry point.

Context and operating mode

Transaction

This entry point is called from a number of different contexts. It is therefore advisable to always test for the presence of a transaction by using the variable: adxlog.

Log file

There is no open log file.

Call context

This entry point is never called as standard. It can only be called by additional specific processings.

Available variables and masks

The MACW mask contains all the information that is used to carry out the integration.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

CRMTRS: Entry transactions for the Customer support module

This entry point located in the SUBCRMTRS processing (entry transaction management) generates a "CRMTRS" action .

This action aims at giving the possibility to intervene in the specific field management at the display level as well as the entry level.

All the entry transactions in the Customer support are concerned by this entry point, that is to say those of the workbench, the service requests, the interventions, the customer installed base.

Context and operating mode

Transaction

There is a transaction in progress for the INICRE, CREATION, INIMOD and MODIF actions.

There is not transaction in progress for the RAZCRE, LIENS and APRES_MODIF actions

Log file

There is no open log file.

Different call cases

The call is made during the management of the entry transaction setup:

- for the workbench

- for the service requests

- for the service responses

- for the customer installed base

and this for the following actions for GOBJET:

- RAZCRE in creation mode, initialization of the screen fields

- INICRE before the write of the entry, loading of the file fields

- CREATION  after the write of the entry, intervention in the field parameters before the generation of the entry screens

- LIENS  after each read of the entry, interventions on the screen fields after each read of the entry

- INIMOD  before the re-write of the record, loading of the file fields.

- MODIF  after the re-write of the entry, intervention on the screen fields before the generation of the entry screens

- APRES_MODIF  after entry of each field, intervention on the screen fields

- EXEBOUT  after use of a button at the bottom of the screen. Only the "Validation" button is of interest, in this case the REP variable needs to be "1" (warning this is an alphanumeric number).

Available variables and masks

The following variables are loaded at the time of the call to the "CRMTRS" action.

PACTION,

Action GOBJET at the origin of the call (RAZCRE, INICRE, CREATION, LIENS, INIMOD, MODIF, APRES_MODIF, EXEBOUT).

PVERSION,

Numeric value of the X3 version number used (e.g. GVERSION=1.2.4  PVERSION=124).

FJL,

Type of transaction currently being managed.

MFROM,

Code for the entry screen

Open tables

In the table below, the significant content flag indicates that the content matches the context.

Miscellaneous remarks

The AWINDOW, AWINPAR, AMSK, AMSKZON, AMSKACT tables, as well as all the tables required for the management of the screen generation and processings are open but must not be modified in the entry point.

MACAUTO: Loading of the fields in automatic creation/modification of an installe

This entry point is used upon automatic creation of an installed base.

It is used to enter the fields specific to the installed base management: 

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called right before the record is written in the MACHINES table.

Available variables and masks

SZPEMAC_ACTION : mentions if in creation ("C") or modification ("M") mode of an installed base

SZPEMAC_ORIGINE : specifies the context  (local menu 2971)

The F :MACV  class contains the information that is going to be written.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

AOBEXP: Setup of the HTML and XML generation of the OBJects in the CRM module

This entry point is used to personalize the XML and HTML extractions for the principal objects components of the CRM module.

In fact, all the following objects can be the object of an extraction in the HTML or XML format using various sub-programs planned for this effect.
A/P - A/R Accounting
Appointment
Telephone calls
Tasks
Projects
Service requests
Service responses
Solutions

The EASYCRMXML sub-program for the SUBAOBXML processing is used to carry out the XML extraction where the code is given in parameter. A more sophisticated version of this sub-program is available under the name : AOBINXML. This is used to intervene on the name of the generated file, any transformation sheets, an execution context.

The EASYCRMLXML sub-program of the SUBAOBXML processing is used to carry out the XML extraction for all the records from a selection filter given in parameter.
A more sophisticated version of this sub-program is available under the name : AOBLISTXML. It is used for the same functional additions as those evoked for AOBINXML.

The AOBINHTML sub-program for the SUBAOBHTML processing is used to carry out the HTML extraction where the code is given in parameter.

Each of these sub-programs call to the AOBEXP entry point to authorize a specific setup for the content of these extractions.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called at the end of the standard definition of the extraction for each table involved. Any modification of the standard proposition can therefore be applied within this entry point.

Available variables and masks

SZSCREENTYPE: This variable is only of use in the case of an HTML extraction type. In fact, it is used to define the format of the generated document. If the document must be read using a terminal where the size is reduced (Mobile phone, Pocket PC...), it must then take the value : PALM. If the document must be read on a terminal with a high resolution display (PC, printer...), it must then take the value : PC.

SZPECONTEXT: It is possible to indicate a particular extraction context for each call to the XML or HTML extraction sub-program.
This context can be tested with the SZPECONTEXT variable in order to deliver the different parameters.

SZAOBEXPTAB: This variable contains the name of the table currently being extracted and for which the extraction characteristics can be modified.

IDISPLAYXXX: This variable is used to deactivate the processing of a table linked to the entity that is being extracted. A value equal to 1 authorizes the extraction of all the records associated with the selected entity. A value equal to 0 deactivates any information extraction from this table.
XXX: Represents the abbreviation of the table currently being extracted.

SZFIEXXX: This grid contains the list of the fields forming the table being processed. This grid is sized according to the number of fields forming the entity being extracted. For each field in this grid, the context information is available at the same level of index in the different variables that follow.
XXX: Represents the abbreviation of the table currently being extracted.

SZTAGXXX: This variable contains the XML tag in which the value of a field will be extracted.
By default, the XML tag is named: Abbreviation of the table + Name of the field in the table.
XXX: Represents the abbreviation of the table currently being extracted.

SZLABELXXX: This variable contains the label associated with the field in the current language.
XXX: Represents the abbreviation of the table currently being extracted.

IHIDEXXX: This variable determines the extraction of a field for the table currently being processed. A null value is used to ignore this field during the extraction. A positive value is used to extract the content of the field in the generated file.
XXX: Represents the abbreviation of the table currently being extracted.

ISORTXXX: This variable determines the order in which the fields will be extracted in the generated file. When this variable is modified by the entry point, it is recommended to verify the absence of multiple entries for the order numbers within the process.
XXX: Represents the abbreviation of the table currently being extracted.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

XMLTAG: Setup of the XML tags generated by the XML extraction of the OBJects in

Just like the entry point AOBEXP, XMLTAG is used to personalize the XML extractions of the database objects in the CRM module. However, this entry point is applied to XML extractions only because its only goal is to modify the tags in the generated document.
For example, the XML tag that makes up the root of a standard document standard is called XROOT. XMLTAG is used to modifier its name to : MONDOCUMENT.
This type of personalization can be applied to all the component nodes that make up the document.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point only concerns the extractions of the type XML. It is called once at the very start of the extraction process.

Available variables and masks

SZXROOT: This variable contains the name of the XML tag representing the root of the generated document.
By default, its value is equal to: XROOT.

SZXUTILITY: This variable contains the name of the XML tag corresponding to the container of the information elements present once at the start of the generated document.
By default, its value is equal to: XUTILITY.

SZXTITLE: This variable contains the name of the XML tag storing the name of the extracted entity in the current language.
By default, its value is equal to: XTITLE.

SZXRECORD: This variable contains the name of the XML tag representing each record in the generated document. Each of these records can correspond to the entity extracted or to one of its linked tables.
By default, its value is equal to: XRECORD.

SZXAOB: This variable contains the name of the XML tag representing the abbreviation of the table from where the record being extracted comes from.
By default, its value is equal to: XAOB.

SZXAOBTITLE: This variable contains the name of the XML tag storing the name of the table from where the record being extracted comes from.
By default, its value is equal to: XAOBTITLE.

SZXAOBNUM: This variable contains the name of the XML tag that stores the identifier for the record. If the record is at a level greater than zero, the identifiers for each level are concatenated.
By default, its value is equal to: XAOBNUM.

SZXLEVEL: This variable contains the name of the XML tag representing the level of the record in the hierarchy of linked tables. Level 0 corresponds to the requested entity.
By default, its value is equal to: XLEVEL.

SZXPARENTAOB: This variable contains the name of the XML tag that stores the abbreviation of the parent table for the record in the hierarchy of the linked tables.
By default, its value is equal to: XPARENTAOB.

SZXPARENTNUM: This variable contains the name of the XML tag that stores the identifier for the parent record.
By default, its value is equal to: XPARENTNUM.

SZXAOBDATA: This variable contains the name of the XML tag that represents each field in the table that is currently being extracted.
By default, its value is equal to: XAOBDATA.

SZXSORT: This variable contains the name of the tag attribute XAOBDATA representing the order number of the extracted fields.
By default, its value is equal to: XSORT.

SZXLABEL: This variable contains the name of the XML tag representing the label for each extracted field in the current language.
By default, its value is equal to: XLABEL.

SZXFIELD: This variable contains the name of the XML tag that stores the content of an extracted field.
By default, its value is equal to: XFIELD.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

LSTBPRCRM9: Acceptance or not of an element from the business partner list in CR

This entry point is used to intervene before the display of a business partner in the list after entry of a criterion (identification screen).  It is used to display or not the current business partner.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Call context

This entry point is called for each business partner in the list.

Available variables and masks

ILSTBPROK: Variable indicating if it is necessary to include the business partner in the list (value 0 to exclude).

Open tables

In the table below, the significant content flag indicates that the content matches the context.

CONCHGMOD: Modifying the reference contract created from the product record

When a service contract is created using a sales order, the reference contract is recovered from the product record. This entry point is used to intervene after recovering this information and to modify it.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point is called upon creating a service contract when the reference contract has been created from the product record.

Available variables and masks

When a service contract is specified on the product ([F:ITM]TPLCONSRV field) the ZSITMTPL variable takes its value. It can be changed right after being recovered from the product.

Open tables

In the table below, the significant content flag indicates that the content matches the context.

Table	Significant content	Table Title
CONTSERV	Yes	Service contracts
CONTTEMPL	Yes	Service contract template
ITMMASTER	Yes	Product

CONCONFAC: EP for specific sections in service contract invoicing

Entry point used to load specific sections when invoicing a service contract.

Context and operating mode

Transaction

Creation of a sales invoice

Log file

There is no open log file.

Different call cases

This entry point is called upon creating an invoice linked to a service contract.

Available variables and masks

The [F:CON] file has been loaded.The program makes it possible to affect specific sections.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

Table	Significant content	Table Title
CONTSERV	Yes	Service contracts
CONTAMT	Yes	Annual bases
CONTIDX	Yes	Index values
CONTREW	Yes	Contract renewal

CONMODCONAMT: EP in modification of service contract from an order

Entry point for modifying a service contract from an oder, just after the amount recalculation (CONAMT) in order to be able to apply actions to it.

Context and operating mode

Transaction

Modification of an order

Log file

There is no open log file

Different call cases

This entry point is called upon modifying an invoice linked to a service contract.

Available variables and masks

The [F:CON] file has been populated.The program is used to assign specific headings

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

Table	Significant content	Table title
CONTSERV	Yes	Service contracts
CONTAMT	Yes	Annual bases
CONTIDX	Yes	Index values
CONTREW	Yes	Contract renewal

CONSERAUT: Intervene on the reference contract read on the product

This entry point is used to perform actions on the reference contract from the specified product.

Context and operating mode

Transaction

There is no transaction in progress

Log file

There is no open log file.

Different call cases

This entry point is called upon creating a customer base when the warranty contract has been created from the product record.

Available variables and masks

The SZTPLCONGUA variable contains the value a warranty contract specified on the product (field [F:ITM]TPLCONGUA); its value can be modified.

Open tables

In the table below, the significant content flag indicates that the content is in line with the context.

Table	Significant content	Table title
CONTTEMPL	Yes	Service contract template
ITMMASTER	Yes	Product

RENCONSER: Service contract renewal

This entry point is used to intervene before a service contract is rewritten during its renewal.

Context and operating mode

Transaction

There is a transaction in progress.The [F:CON] class is loaded with the new values of the service contract, but its rewriting did not occur yet.

Log file

There is no open log file.

Different call cases

This entry point is called during the renewal of a service contract.

Three renewal cases can occur:

1.      Warranty contract renewal (CONCAT = 1),

2.Renewal of a contract other than warranty, but not invoiced ( processed in the same way as the warranty contract) (CONCAT > 1 and NEXINVDAT = [ 0/0/ 0]),

3.Renewal of a contract other than warranty, but invoiced (CONCAT > 1 and < > NEXINVDAT [ 0/0/ 0]).

They all lead to this entry point.

Available variables and masks

The [F:CON] class is loaded, but not written yet. It is therefore possible, where appropriate, to make changes to specific sections at this level.

It is also possible to load another table.

In entry point return, the content of GERR is tested. The rewrite of the renewed service contract only occurs if GERR<>1. A possible "Rollback" must be supported in the entry point. The "Commit" will occur in the standard section, when the rewriting process of the renewed contract ended successfully.

Open tables

In the table below, the significant content flag indicates that the content is in line with the context.

Table	Significant content	Table title
CONTSERV	Yes	Service contract

MSKCRECON: Modification of an automatically-created service contract

This entry point is used to intervene before saving a service contract created automatically.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point, during the automatic creation of a service contract, before its rewriting.

The [F:CON] class is not loaded yet. All the information remains in [M:CONx] classes.

The action that follows this entry point is "VERIF_CRE".

Available variables and masks

The [F:CON] class is not loaded yet.

All [M:CONx] classes of the window are entered to be saved.

Open tables

In the table below, the significant content flag indicates that the content is in line with the context.

Table	Significant content	Table title
CONTSERV	No	Service contract

CREMACCOU: Modify the standard sequence number of the customer base created via

This entry point is used to intervene on the standard sequence number of the customer base obtained during the validation of deliveries.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

This entry point is called in invoice management at the time of selecting an open item in a service contract:

Available variables and masks

The SZCOUNTER variable contains the value of standard sequence number.It can be modified.

Open tables

In the table below, the significant content flag indicates that the content is in phase with the context.

Table	Significant content	Table Title
MACHINE	No	Customer base
ITMMASTER	Yes	Product
BPARTNER	Yes	Business partner
BPADDRESS	Yes	Addresses
TABCUR	Yes	Currency table
FACILITY	Yes	Sites

MACAUTOYES: Bypassing a customer base automatic creation

This entry point is used to bypass the standard functional controls linked to the automatic creation of a customer base.

Context and operating mode

Transaction

There is one transaction in progress.

There is no log file.

This entry point is called after the completion of the standard controls authorizing the automatic creation of the customer base.It is used to counter and bypass the automatic creation.

Available variables and masks

The IMACAUTOYES variable is automatically set to 1.

To bypass the creation of the customer base, the variable must be set to 0 (zero).

For those products that are not managed with serial numbers, if the IMACAUTOYES variable is set to 2, the installed base record will be automatically split. This will create as many different records with a quantity equal to 1. A value different from 2 will be dealt with as a standard case (variable set to 1).

For those products that are managed with serial numbers, value 0 will be the only one to be tested to bypass the management of the installed base. Any other value will not be used and the standard behavior will be applied (one installed base record with a quantity equal to 1 per serial number).

Open tables