Script TRTCRMPE: Calling script for CRM module EP

CLLOBJ: Definition of the OBJect for a campaign call

This entry point is located within the call distribution matrix of the call campaign assistant. You can use it to define a customized objective for each call generated by this assistant.

For example, the 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 display it on the call to be made.

When the call objective is defined via this entry point, the CLLCMGOMP parameter has no effect on the relevant call.

This entry point is linked to the 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 as: 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 created by the distribution matrix.

The [F] class for the call to be created is partially entered.

The sequence 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 been created physically in the database yet.

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 blank before each call to the entry point, must be entered with the complete text to be displayed for the call to be carried out. The maximum size of the text is dependent on the size of the clob type defined for the HD5 data type.
• 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 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 column means that the content matches the context.

OMMXML: XML additions specific to a mass-mailing

This entry point is located inside the generation of an XML type mass-mailing. You can use it to complete the XML document generation with the information excluded from the capacities of the standard XML mass-mailing setup.

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 recording end tag is written. The tag associated with the field is 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 column means that the content matches the context.

MGCDEDIT: Specific report definition to print the data of a target

This entry point is located before the printing to view or extract data for a target. You can use it to customize the reports being 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 printing starts.

Available variables and masks

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

Use this entry point to take the entire responsibility for the content of the different browsers of the selection panel making up 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 a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose, such as currbox, FILGAUCHE, FILGAUSUP, and so on.
• GSRECTRNUM: Entry transaction currently used.

Open tables

In the table below, the Significant content column means that the content matches the context.

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

Use this entry point 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 overlooked.

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, you need to give it a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose, such as currbox, FILGAUCHE, FILGAUSUP, and so on.
• GSRECTRNUM: Entry transaction currently used.

Open tables

In the table below, the Significant content column means that the content matches the context.

MAINITNFLT: Total management of the selection panel of a service response

Use this entry point to take the entire responsibility for the content of the different browsers of the selection panel making up the service response 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 service response 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 a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose, such as currbox, FILGAUCHE, FILGAUSUP, and so on.
• GITNCTRNUM: Entry transaction currently used.

Open tables

In the table below, the Significant content column means that the content matches the context.

ITNFLT: Complex filter on the additional browsers for the service responses

Use this entry point 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 overlooked.

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 service response 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 give it a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose, such as currbox, FILGAUCHE, FILGAUSUP, and so on.
• GITNCTRNUM: Entry transaction currently used.

Open tables

In the table below, the Significant content column means that the content matches the context.

MAINMACFLT: Total control of the selection panel for a customer installed base

Use this entry point to take the entire responsibility for the content of the different browsers of the selection panel making up 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 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 a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose, such as currbox, FILGAUCHE, FILGAUSUP, and so on.
• GMACCTRNUM: Entry transaction currently used.

Open tables

In the table below, the Significant content column means that the content matches the context.

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

Use this entry point 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 overlooked.

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 give it a positive value. The content of the different selection panels is defined by using the usual supervisor variables provided for this purpose, such as currbox, FILGAUCHE, FILGAUSUP, and so on.
• GMACCTRNUM: Entry transaction currently being used.

Open tables

In the table below, the Significant content column means that the content matches the context.

AUTINVCFIL: Add selection criteria for contracts to be invoiced

Use this entry point to insert additional logic during the definition of the selection criteria for the contracts to be invoiced.

You can use it 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 to 250 characters. To ensure that everything is operational during the evaluation, FILSUP is initialized to the string 1=1 if these variables have not been loaded by the entry point. Completing the info in the entry point is enough.

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 column indicates that the content matches the context. 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

Use this entry point to insert additional logic during the definition of the selection criteria for the service requests to be invoiced.

You can use it 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 to 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 enough to complete it in the entry point.

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 column means that the content matches the context.

FEEDHDI: Change or addition to the billable service request lines

Use this entry point when a service request is closed and any billable consumption lines are generated.

You can use it to change some of these lines or even 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 column means that the content matches the context.

RVACON: Revaluation of a service contract according to a formula

Use this entry point to carry out the revaluations of the service contracts that are not based on the evolution of an index.

This entry point is generally called when a service contract open item is invoiced. 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 the A1 record is: RVACON_A1.

Context and operating mode

Transaction

The revaluation of the service contracts is used in many different contexts. Some revaluations are run within a transaction while others take place outside of any transaction. It is therefore recommended 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 per Mathematical formula type revaluation of the basis of the annual fee for a service contract that 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 revaluated contract.

Open tables

In the table below, the Significant content column means that the content matches the context.

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

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

If this entry point is activated, it must run all the controls related to the revaluations and automatic renewals of 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 column means 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 is used each time a service request is created or modified or even when the batch server analyzes 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 done. If the entry point returns 0, the escalation will not be done.
• SZSRENUM: This variable contains the code for the escalated service request.

Open tables

In the table below, the Significant content column indicates that the content matches 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 10 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 column indicates that the content is in phase with the context.

SAVEUDE: Management of the specific fields when deleting requests

Use this entry point to take control of the additional specific or custom fields during the recording of a service request deletion tracking. The impacted fields were added to the UDDDELSRE table. The entry point has to make sure that the fields are qualified when they are deleted.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is no open log file.

Call context

The entry point is called right before the deletion entry is written 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 column means that the content matches the context.

LOADUDE: Management of specific fields when displaying request deletions

Use this entry point to display the additional specific or custom fields in the inquiry window for the tracking of the service request deletions. The impacted fields have been added to the UDDDELSRE table. The entry point must guarantee that these fields are loaded in the UDD7 screen.

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 fully accessible.

Open tables

In the table below, the Significant content column means that the content matches the context.

MACMCC: Specific aggregation for the installed base inquiry

This entry point is located in the inquiry of the aggregated installed base.

You can use it to aggregate this inquiry on the basis of the additional specific or 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 when an aggregation is requested on the basis of a non-standard field.

If required, the entry point must guarantee that this inquiry is fully loaded.

Available variables and masks

The MCC1 mask is fully accessible.

The aggregation field can be accessed in the [M:MCC1]FIE variable.

Open tables

In the table below, the Significant content column means that the content matches the context.

CUSRUL: Customized integration rule for customer installed base

Use this entry point to create the integration rules for the specific customer installed base.

This entry point is run when the integration component of the base (MACRULE, TRTMACRULE script) is called with an action code equal to 7. In that 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 adxlog variable.

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 scripts.

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 column means that the content matches the context.

CRMTRS: Entry transactions for the Customer support module

This entry point is located in the SUBCRMTRS script (entry transaction management). It generates a CRMTRS action.

This action allows the management of the specific fields at the display and entry levels.

All the entry transactions in the Customer support are impacted by this entry point, that is to say those of the workbench, the service requests, the service responses and 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 no transaction in progress for the RAZCRE, LIENS and APRES_MODIF actions

Log file

There is no open log file.

Different call cases

The entry point is called during the management of the entry transaction setup for:

• The workbench
• The service requests
• The service responses
• The customer installed base

It is also called for the GOBJET following actions:

• RAZCRE in creation mode, initialization of the screen fields.
• INICRE before the record is written, loading of the file fields.
• CREATION after the record is written, intervention in the field parameters before the generation of the entry screens.
• LIENS after the record is read, interventions on the screen fields after each record is read.
• INIMOD before the record is rewritten, loading of the file fields.
• MODIF after the record is rewritten, intervention on the screen fields before the generation of the entry screens.
• APRES_MODIF after each field is entered, intervention on the screen fields.
• EXEBOUT after a button at the bottom of the screen is used. Only the Validation button is important. In this case, the REP variable needs to be 1. This is an alphanumeric number.

Available variables and masks

The following variables are loaded when calling the CRMTRS action:

• PACTION: GOBJET action at the origin of the call, such as RAZCRE, INICRE, CREATION, LIENS, INIMOD, MODIF, APRES_MODIF, EXEBOUT.
• PVERSION: Numeric value of the X3 version number used, for example GVERSION = 1.2.4  PVERSION = 124.
• FJL: Type of transaction currently managed.
• MFROM: Code for the entry screen.

Open tables

In the table below, the Significant content column means 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 screen and script generation are open. They must not be modified in the entry point.

MACAUTO: Field population on auto creation / modification of an installed base

Use this entry point on the automatic creation of an installed base.

You can use it to enter the fields that are 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 the mode of an installed base is in creation (C) or modification (M).
• 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 column means that the content matches the context.

AOBEXP: HTML / XML generation setup of the OBJects in CRM

Use this entry point to customize the XML and HTML extractions for the main objects components of the CRM module.

All the following objects can be the subject of an extraction in the HTML or XML format using various sub-programs provided to that effect:

• Business partners
  
• Appointments
  
• Telephone calls
  
• Tasks
  
• Projects
  
• Service requests
  
• Service responses
  
• Solutions

The EASYCRMXML sub-program for the SUBAOBXML script is used to carry out the XML extraction with the code given as a 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, or an execution context.

The EASYCRMLXML sub-program of the SUBAOBXML script is used to carry out the XML extraction for all the records from a selection filter given as a 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 mentioned for AOBINXML.

The AOBINHTML sub-program for the SUBAOBHTML script is used to carry out the HTML extraction with the code given as a 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 useful in the case of an HTML extraction type. It is used to define the format of the generated document. If the document must be read using a terminal on a smaller screen such as a mobile phone, it must then take the value: PALM. If the document must be read on a terminal with a high resolution display such as a PC, it must then take the value: PC.
• SZPECONTEXT: This variable can be used to indicate a particular extraction context each time the XML or HTML extraction sub-program is called. This context can be tested with this 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 script 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.
  
• 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.
  
• 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.
  
• 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.
  
• 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.
  

Open tables

In the table below, the Significant content column indicates that the content matches the context.

XMLTAG: Set up tags generated by the XML extraction of OBJects in CRM

Similarly to the AOBEXP entry point, XMLTAG is used to customize the XML extractions of the database objects in the CRM module. However, this entry point is applied to XML extractions only because it is only used 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 modify its name to: MONDOCUMENT. This type of customization 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 impacts the XML type extractions. 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 column indicates that the content matches the context.

LSTBPRCRM9: Acceptance or not of an element from the BP list in CRM9

Use this entry point before the display of a business partner in the list after criteria are entered in the 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 column means that the content matches the context.

CONCHGMOD: Modify the reference contract created from product record

When a service contract is created using a sales order, the reference contract is recovered from the product record. Use this entry point after recovering this information 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 in the [F:ITM]TPLCONSRV field, the ZSITMTPL variable takes its value. It can be changed directly after being recovered from the product.

Open tables

In the table below, the Significant content column means that the content matches the context.

CONCONFAC: EP for specific headings in service contract invoicing

Use this entry point to load specific sections when invoicing a service contract.

Context and operating mode

Transaction

There is a creation of a sales invoice.

Log file

There is no open log file.

Different call cases

This entry point is called when creating 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 sections

Open tables

In the table below, the Significant content column means that the content matches the context.

CONMODCONAMT: EP to modify a service contract from an order

Use this entry point to modify a service contract from an order, immediately after the amount recalculation (CONAMT) in order to be able to act on it.

Context and operating mode

Transaction

There is a modification of an order.

Log file

There is no open log file.

Different call cases

This entry point is called when 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 sections.

Open tables

In the table below, the Significant content column means that the content matches the context.

CONSERAUT: Act on the reference contract read from the product

Use this entry point 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 obtained from the product record.

Available variables and masks

The SZTPLCONGUA variable contains the value of a warranty contract specified on the product, in the [F:ITM]TPLCONGUA field. Its value can be modified.

Open tables

In the table below, the Significant content column means that the content matches the context.

RENCONSER: Service contract renewal

Use this entry point 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 populated with the new values of the service contract, but it has not been rewritten 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:

• Warranty contract renewal (CONCAT = 1).
• Renewal of a contract other than a warranty contract, but not invoiced. It is processed in the same way as the warranty contract (CONCAT <> 1 and NEXINVDAT = [0/0/0]).
• Renewal of a contract other than a warranty contract, 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 populated, but not written yet. You can modify specific sections at this level, where appropriate.

You can also populate another table.

When exiting an entry point, 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 occurs in the standard section, when the rewriting process of the renewed contract ends successfully.

Open tables

In the table below, the Significant content column means that the content matches the context.

MSKCRECON: Modification of an auto created service contract

Use this entry point before saving a service contract created automatically.

Context and operating mode

Transaction

There is no transaction in process.

Log file

There is no open log file.

Different call cases

This entry point is called during the automatic creation of a service contract, before it is rewritten.

The [F:CON] class is not populated yet. All the information remains in the [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 the [M:CONx] classes of the window are entered to be saved.

Open tables

In the table below, the Significant content column means that the content matches the context.

CREMACCOU: Modify the standard sequence number of the customer base

Use this entry point to act 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 on invoice management when selecting an open item of a service contract.

Available variables and masks

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

Open tables

In the table below, the Significant content column means that the content matches the context.

BPRAINCRM9: Adding extra selection criteria in CRM9

Use this entry point to enter the standard selection criteria for the transaction FUNCRM9: Identify.

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 either when elaborating the set of conditions to be applied to BPs, or during the creation of the conditions to be applied to contacts.

Available variables and masks

The [M:CRM9]TYPESEARCH screen field takes the BPR or AIN value to detect one case or the other.

Example of use of the entry point:

  If [M:CRM9]TYPESEARCH = "BPR" Then

                If [M:CRM9]TELBPR <> "" Then

                SZWHERE(ILIGNEWHERE) =  SZAND + " (pat([F:BPA]TEL, '"+

                &                                     [M:CRM9]TELBPR+"*') <> 0)"

                ILIGNEWHERE = ILIGNEWHERE + 1

                SZAND = " AND "

                Endif

                #

                If [M:CRM9]NAFBPR <> "" Then

                SZWHERE(ILIGNEWHERE) =  SZAND + " (pat([F:BPR]NAF, '"+

                &                                     [M:CRM9]NAFBPR+"*') <> 0)"

                ILIGNEWHERE = ILIGNEWHERE + 1

                SZAND = " AND "

                Endif

                Elsif [M:CRM9]TYPESEARCH = "AIN" Then

                If [M:CRM9]TELAIN <> "" Then

                SZWHERE(ILIGNEWHERE) =  SZAND + " (pat([F:AIN]CNTETS,'"+

                [M:CRM9]TELAIN+"*') <> 0)"

                ILIGNEWHERE = ILIGNEWHERE + 1

                SZAND = " AND "

                Endif

                #

                If [M:CRM9]FAXAIN <> "" Then

                SZWHERE(ILIGNEWHERE) =  SZAND + " (pat([F:AIN]CNTFAX, '"+

                &                                     [M:CRM9]FAXAIN+"*') <> 0)"

                ILIGNEWHERE = ILIGNEWHERE + 1

                SZAND = " AND "

                Endif

            Endif

The size of the SZWHERE variable is 20 lines. The first lines are used by the standard criteria.

Open tables

In the table below, the Significant content column means that the content matches the context.

SRETRSWIN: Act before window validation during transaction progress

When validating a transaction, Use this entry point in a window before it is saved and validated.

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 when the [F:AWI] class of the window generated by the transaction setup is populated, but before it is written. You can modify it. For example, you can hide one or several tabs.

Available variables and masks

Open tables

In the table below, the Significant content column means that the content matches the context.

MAIAUTO1: Enter the machine installation data

When saving the Customer base and more specifically updating the history of installations, use this entry point to enter information to be saved in the MACITN table: machine installations.

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 before saving each customer base installation line.

The [F:MAI] class is completely populated at the level of the standard sections.

Available variables and masks

All the screens in the OMAC window are available.

When calling this entry point, the script starts a loop on [M:MAC4].

The current index is in ZI.

If an error occurs in the specific code, set GERR to 1 (GERR = 1) and load the error message in GMESSAGE.

Open tables

In the table below, the Significant content column means that the content matches the context, given the situation variables.

MAIAUTO2: Enter the machine installation data

When creating the Customer base duplicate and more specifically when updating the history of installations, use this entry point to enter information to be saved in the MACITN table: machine installations.

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 before saving each customer base installation line.

The [F:MAID] class is already completely loaded at the standard section level when performing a copy.

The [F:MAIV] class is already completely loaded at the standard section level when performing a creation.

Available variables and masks

The SZCMMAIAUTO variable is populated by:

• [MAID] if the entry point is called during a copy
• [MAIV] if the entry point is called during a creation.

Open tables

In the table below, the Significant content column indicates that the content is consistent with the context, given the situation variables.

MACWAUTO: Add info to customer base creation class [M:MACW]

When a Customer base is created automatically, use this entry point to provide standard information loaded in the [M:MACW] work class.

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 after the [M:MACW] class has been populated with the proper standard values.

The available call context is defined with the content of the SZMACWCNT variable. It can be specified in the SZMACWPRE variable.

Available variables and masks

The SZMACWCNT variable contains the name of the script (context) of the call:

• TRTVENLIVV
• TRTVENFACV
• SUBSRL
• SUBSRH
• SUBSIHA
• SUBSRS

When the SZMACWCNT variable is equal to SUBSRH, the context can be specified using the SZMACWPRE variable. The variable can have the following values:

• (empty)
• DOC
• MOD

When the SZMACWCNT variable is equal to SUBSRS or SUBSRH, the context can be specified using the SZMACWPRE variable. The variable can have the following values:

• (empty)
• MOD

When the SZMACWCNT variable is equal to TRTVENLIVV or TRTVENFACV, the SZMACWPRE variable remains empty.

Open tables

MACAUTOYES: Bypassing a customer base automatic creation

Use this entry point 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.

Log file

There is no open log file.

Call context

This entry point is called after the standard controls authorizing the automatic creation of a customer base have been completed. It is used to bypass these controls and the automatic creation process.

Available variables and masks

The IMACAUTOYES variable is automatically set to 1.

To bypass the creation of a customer base, the variable must be set to 0.

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

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

Open tables

CRMAGD: Add info to loading filters of the CRM planning calendar

Use this entry point to enter the various filters used in the CRM calendar.

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 after standard filters have been applied, but before safety filters, such as applying roles.

A context variable (SZCNTCRMAGD) is used to know the stage in the script.

Available variables and masks

The SZCNTCRMAGD variable takes various values and is used to know the current stage of the script.

The values are:

• FILTDIM: Used to act on the size of the filtering variable (SZWHERE).
• AGDBAP: Filter on appointments displayed in the planning calendar.
• AGDCLL: Filter on calls displayed in the planning calendar.
• AGDTSK: Filter on tasks displayed in the planning calendar.
• OPPOR: Filter on projects displayed in the Projects tab.
• BAPPOINT: Filter on appointments displayed in the Appointments tab.
• PHONECALL: Filter on calls displayed in the Calls tab.
• TASK: Filter on tasks displayed in the Tasks tab.
• INFBAP: Filter on information related to appointments displayed in the Information tab.
• INFCLL: Filter on information related to calls displayed in the Information tab.
• INFTSK: Filter on information related to tasks displayed in the Information tab.
• INFOPP: Filter on information related to projects displayed in the Information tab.
• INFCON: Filter on information related to contracts displayed in the Information tab.
• OPPCLL: Filter on marketing campaigns displayed in the Marketing campaigns tab.
• PHONING: Filter on call campaigns displayed in the Marketing campaigns tab.

Except for FILTDIM, all other values are used to apply conditions that complement the standard ones. They are all used in the same way, with respect to the current search.

The principle is as follows:

SZWHERE(ILIGNEWHERE) = SZAND - "<Specific conditions> "
                ILIGNEWHERE += 1
            SZAND = " AND "

The entry point is triggered after standard conditions have been loaded. Therefore, conditions can be completely questioned. Must-have conditions are also applied and cannot be questioned, such as the implementation of roles.

The SZWHERE variable is declared as follows: Local Char SZWHERE(250)(IFILTDIM)

IFILTDIM is 20 by default.

Given the additional conditions, this value can be insufficient.

The FILTDIM context is used to increase the value of IFILTDIM.

For example: IFILTDIM = 50

This leads to declaring SZWHERE with 50 lines instead of 20.

Open tables

HDKAGD: Add info to loading filters of the Customer support plan

Use this entry point to complete the various filters used in the customer support calendar.

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 after standard filters have been applied, but before safety filters, such as applying roles.

A context variable (SZCNTHDKAGD) is used to know the stage in the script.

Available variables and masks

The SZCNTHDKAGD variable takes various values and is used to know the stage in the script.

The values are:

• FILTDIM: Used to intervene on the size of the filtering variable (SZWHERE).
• SERREQUEST: Filter on service requests displayed in the Service request tab.
• AGDITN: Filter on responses displayed in the planning calendar.
• INFITN: Filter on information related to service responses displayed in the Information tab.

Except for FILTDIM, all other values are used to apply conditions that complement the standard ones. They are all used in the same way, with respect to the current search.

The principle is as follows:

SZWHERE(ILIGNEWHERE) = SZAND - "<Specific conditions> "
                ILIGNEWHERE += 1
            SZAND = " AND "

The entry point is triggered after standard conditions have been loaded. Therefore, conditions can be completely questioned. Must-have conditions are also applied and cannot be questioned, such as the implementation of roles.

The SZWHERE variable is declared as follows: Local Char SZWHERE(250)(IFILTDIM)

IFILTDIM is 20 by default.

Given the additional conditions, this value can be insufficient.

The FILTDIM context is used to increase the value of IFILTDIM.

For example: IFILTDIM = 50

This leads to declaring SZWHERE with 50 lines instead of 20.

Open tables

SRELOADCPN: Intervene in the LOADCPN loop

This entry point is called in the loading loop of the SRE7 screen to load specific sections.

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 in the loading loop of the LOADCPN subprogram of the SUBSREB1 script. It is used to load specific sections.

The ILINCPN variable contains the current line of the table being loaded.

The screen is abbreviated as [SRE7].

Open tables

In the table below, the Significant content column means that the content matches the context.

SRESAVECPN: Intervene in the SAVECPN loop

This entry point is called in the saving loop of the SRE7 screen to load specific sections.

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 in the loading loop of the LOADCPN subprogram of the SUBSREB1 script. It is used to load specific sections.

The ITER variable contains the current line of the table being loaded.

The screen is abbreviated as [SRE7].

Open tables

In the table below, the Significant content column means that the content matches the context.

DUPLIMAC: Add info to the copy of a base on additional tables

When copying a Customer base, use this entry point to fully perform the update of standard tables with specific tables.

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 when all standard tables have been updated and before the transaction has been validated.

It is then possible to add specific tables to this duplication.

Available variables and masks

The INOERROR variable is used to specify if the script has run properly:

• INOERROR = 1: It is then possible to validate the transaction.
• INOERROR = 1: It is possible to validate the transaction.

Open tables

In the table below, the Significant content column indicates that the content is consistent with the context, given the situation variables.

SRELOADMAC: Intervene in the LOADMAC loop

This entry point is called in the loading loop of the SRE7 screen to load specific sections.

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 in the loading loop of the LOADMAC subprogram of the SUBSREB1 script. It is used to load specific sections.

The ILINDEB variable contains the current line of the table being loaded.

The screen is abbreviated as [SRE7].

Open tables

In the table below, the Significant content column means that the content matches the context.

SRESAVEMAC: Intervene in the SAVEMAC loop

This entry point is called in the saving loop of the SRE7 screen to load specific sections.

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 in the loading loop of the SAVEMAC subprogram of the SUBSREB1 script. It is used to load specific sections.

The ITER variable contains the current line of the table being loaded.

The screen is abbreviated as [SRE7].

Open tables

In the table below, the Significant content column means that the content matches the context.

CMATRTECRAN/CMATRTGENFEN/CMAONGLET/CMABLOCS/CMACOLFIX/CMACHAMPS: Intervene at any stage of a customer installed base record

Set of entry points:

• CMATRTECRAN
• CMATRTGENFEN
• CMAONGLET
• CMABLOCS
• CMACOLFIX
• CMACHAMPS

Use these entry points to intervene at any stage of an entry transaction validation for a customer installed base record.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is no open log file.

Call context

These entry points are called during the different validation stages of an entry transaction for the Customer base (GESMAC) record.

Open tables

HBP1FILLHST: Add elements to the history

Use this entry point to add items to the prospect/customer history (SAIHBP1 action).

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 when all the standard events have been generated in the HISTOCRM work table.

It is then possible to add other events by applying the following template:

  If ITODO Then
                Filter [TSK] Where [F:TSK]TSKCMP = GSZBPRNUM and [F:TSK]TSKDON <> 2 Order By [F:TSK]TSKDAT Asc
                Else
                Filter [TSK] Where [F:TSK]TSKCMP = GSZBPRNUM and [F:TSK]TSKDON = 2 Order By [F:TSK]TSKDAT Desc
                Endif
                Call DEBTRANS From GLOCK
                Trbegin [HST]
                ICOUNTLNS = 0
                For [TSK] Hint Key TSK2
                If ICOUNTLNS >= dim([M:HBP1]TYPCLA) Then
                Break
                Endif
                [F:HST]CLSNUM = 0
                If ITODO Then
                [F:HST]DON = 1
                Else
                [F:HST]DON = 2
                Endif
                [F:HST]SSS = GIDENT
                [F:HST]RECNUM = [F:TSK]TSKNUM
                [F:HST]RECDAT = [F:TSK]TSKDAT
                [F:HST]RECHOU = [F:TSK]CREHOU
                [F:HST]RECTYP = "TSK"
                Write [HST]
                If fstat Then
                ITRB = 1
                Break
                Endif
                ICOUNTLNS += 1
                Next
                Filter [TSK]
                #If an entry has failed. Complete stop.
                If ITRB Then
                GMESSAGE = mess(348,196,1) #Error upon loading history.
                GERR = 1
                Rollback
                End
                Else
                Commit
            Endif

Open tables

In the table below, the Significant content column means that the content matches the context.

HBP1LOADHBP: Add elements to the history

Use this entry point to display non-standard elements in the prospect/customer history (SAIHBP1 action) or to complete the standard information with additional data.

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 each time HISTOCRM is read after the standard records have been processed.

It is then possible to add specific information to the data displayed in the table. The current index is contained in I.

If the data read in HISTOCRM is not standard, it can be considered in the table display.

Open tables

In the table below, the Significant content column means that the content matches the context.

ADDHEADER: Add headers to CSV files during mass-mailing

Use this entry point to add headers to the CSV generated during the mass-mailing process.

This entry point is dependent on the WRITEMRE entry point.

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 during mass-mailing when adding column headers to the CSV file in the [F:MRE] table.

It is not necessary to use it, because the name of the specific column in [F:MRE] is displayed in the current targeting criteria.

This entry point operates jointly with the WRITEMRE entry point.

Available variables and masks

Open tables

WRITEMRE: Complete the values of the CSV files during mass-mailing

Use this entry point to complete the values of the CSV file generated during the mass-mailing process.

This entry point is dependent on the ADDHEADER entry point.

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 during mass-mailing before writing in [F:MRE] to complete the loading of the specific sections.

It is used after all standard sections have been loaded, and before using the Write [F:MRE] command.

The actual creation of the CSV file is performed using the MRECSV export template.

It needs to be modified to add new sections.

This entry point works jointly with the ADDHEADER entry point.

Available variables and masks

Open tables

GETREPBPR: Assign specific representatives in call campaign

Use this entry point to assign additional and specific representatives to a call campaign where standard representatives already exist. It cannot be more than 2 representatives.

Context and operating mode

Transaction

There is no transaction in process.

Log file

There is no open log file.

Call context

This entry point is called during a campaign call, when assigning representatives.

It is called before assigning representatives and it is used to list the additional fields that need to be tested. These additional fields are tested after the two standard fields if no call is assigned to them.

Its use is based on two variables:

• INBREPSPE: Integer-type variable which includes the number of additional fields to be tested. The first additional field is set to index 0.
• SFIEREPSPE: Character tables used to specify the list of fields in the [F:BPC] class to be tested. The value is given as [F:BPC]REP3.

Example

INBREPSPE += 1

SFIEREPSPE(INBREPSPE) = [F:BPC]REP3

Available variables and masks

Open tables

ITNFORCEHOU: Force the start time and intervention duration

Use this entry point to force the start time and duration of the intervention.

Context and operating mode

Transaction

There is no transaction in process.

Log file

There is no open log file.

Call context

This entry point is called in the $RAZCRE label of an intervention.

It is called before the start time and duration have been assigned default values. It is used to take over this default functioning.

Its use is based on two variables:

• IPEFORCEHOU: Integer type variable.

When it is set to zero, it specifies that the standard functioning should be run. Any other value means that the standard functioning is not run.

In this case, this whole phase of the standard process should be considered by the entry point:

  If IPEFORCEHOU = 0 Then
                If SZNVGCOD = "1" Then
                #Intervention to plan
                [M:ITN0]DON = 1
                [M:ITN1]DAT = date$ + 1
                [M:ITN1]HOU = "0900"
                Elsif SZNVGCOD = "2" Then
                #Intervention completed
                [M:ITN0]DON = 2
                [M:ITN1]DAT = date$
                [M:ITN1]HOU = left$(time$, 2) + mid$(time$, 4, 2)
                Endif
                #Default planner
                Call SETDEFPLN([M:ITN1]DAT, [M:ITN1]HOU, [M:ITN8]HOUSVCPLN, [M:ITN8]MNTSVCPLN) From SUBITNB2
            Endif

CRITCON: Add additional criteria on contract selection

Use this entry point to add additional criteria to the selection of a valid contract to cover a service request.

Context and operating mode

Transaction

There is no transaction in process.

Log file

There is no open log file.

Call context

This entry point is called in the following subprograms of the TRTCOVER script:

• CHKNBCON
• CHECKCON
• CHECKPIT
• RECHKNBCON

It is used to add more filter conditions on [F:CON] service contracts in order to add further detail and complement the contract retained to cover the service requests, according to the requirements.

Available variables and masks

• SSPESPCALLER: It contains the name of the calling subprogram, among the 4 mentioned above. This allows the calling context to be known and the behavior to be adapted, if needed.
• SSPECRITCON: It allows the specific code to include any necessary additional filters. These filters must relate to the [F:CON] service contract table.

This is a sized variable that is 250 characters long (0..10).

If the first line is empty, the filter is automatically populated with (1=1), so that only the standard criteria are applied.

LOAD_ITN: Loading of specific fields in [M:MAC4]

Use this entry point to load specific fields in the [M:MAC4] screen in the LOAD_ITN subprogram of the SUBMACB script.

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 in the LOAD_ITN subprogram of the SUBMACB script.

It is used to load specific fields in this MAC4 screen.

Available variables and masks

I:MAC4 is a grid. I is the number of the current line.

[F:MAI] is the current F class to load MAC4.

GESMAILOAD: Loading of specific fields in [M:MACW]

Use this entry point to load specific fields in the [M:MACW] screen in the GESMAI subprogram of the SUBMACC script.

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 in the GESMAI sub-program of the SUBMACC script.

It is used to load specific fields in this MACW screen.

Available variables and masks

[M:MAC7] is the current M class to load MACW.

MNGWAR_CHECKCON: Deactivate default contract service search

Context and operating method

Transaction

There is a transaction in progress.

Log file

No trace file is open.

Code context

During TRTMACRULE, the automated installed base process, existing contracts are checked whether to generate or not a service contract.

Use this entry point to deactivate this default behavior.

This entry point is called and ISKIP_CON is set to 1 by default.

If you need to deactivate control and go out of the loop, ISKIP_CON must be set to 0.

Available variables and masks

$MNGWAR label is called in different places.

The following variables are used to identify the relevant case:

• IRULEORI
• SZRULEVCRORI
• DRULEDAT
• SZCRECONCXT

Open tables

NOCHKITNDISP: Deactivate availability check on Service response

Context and operating method

Transaction

There is no transaction in progress.

Log file

There is no open trace file.

Code context

This entry point is called at the beginning of the CHKITNDISP label in SUBTINB3.

Use this entry point to deactivate the availability check of a user.

It is called in $VERIF_CRE and $VERIF_MOD, from the GESITN function.

The INOCHKITNDISP variable defaults to 0. Then, the process is done and the employee availability is checked.

Any other value deactivates this control so the user is accepted in any cases.

Available variables and masks

The OITN window screens are available.

Open tables