Ir al final de los metadatos
Ir al inicio de los metadatos

Estás viendo una versión antigua de esta página. Ve a la versión actual.

Comparar con el actual View Version History

« Anterior Versión 11 Siguiente »

Installation files

In this release two new support packages are released:

  • SP5 for TESII Component → TESII_100_700_SP5.sar
  • SP4 for TESIICNC Component → TESIICNC_100_700_SP4.sar

These files can be downloaded from the customer portal in the installation section, version 1.7.4, using software components:

Prerequisites

It is necessary to have the License component installed: 1.1.2.1 Installation of License Component BPCORE. It is enough to have the component installed to carry out the installation, it is not necessary to wait for the activation of the license.

To install SP5 for TESII, TESII Software Component has to be installed up to SP4. If you do not have the latest SP installed, download them from the customer portal and place them in the installation queue along with the new SP5 for TESII.

To install SP4 for TESIICNC, TESIICNC Software Component needs to be installed up to SP3. Otherwise, download the necessary SPs and add them to the installation queue together with SP4 for TESIICNC.

If some SPs need to be added to the prior to the SPs that are released in this version, check section Installable files from : 1.1.2.3 ECC Installation procedure as a Software Components to see where to download the files.


Installation task

Installation for SP5 TESII and SP4 TESIICNC.

Log in the system in EN, Client 000.

T-code SPAM.

Load both files for the installation, SP5 for TESII and SP4 for TESIICNC. (If it is necessary, load the previous SPs as indicated in the prerequisites).

Once they have been loaded, press 

Then select the TESII component.

The SPs to be installed will appear in green.

Press the green check and in the next pop up, press NO.

Press the release icon.

Select the installation in the background.

If the SPAU and SPDD are skipped during this process, make the necessary adjustments.

Once the process is finished, click on the queue confirmation icon.

Finally check that they have been installed correctly:

BC_SETs activation

Once the support packages have been installed, two BC_SETs that are released in this version need to be activated to have the necessary setting.

The BC_SETs to be activated are the following:

  • /EDGE/SII_BC_SET_SP5_SIN_MANDANT: It only needs to be activated in one client since its tables are not client-dependent.

  • /EDGE/SII_BC_SET_SP5_CON_MANDANT: It needs to be activated it in every available client because the data it contains is client-dependent.

Before activating them, table SCPRSTAM needs to be set up. This table is client-independent, so it makes no difference in which client you set it up. It is only set for one client.

In this table, the next entries for the following tables must be added (in case they are not customised already):

  • EDOCOUNTRYTCH
  • EDOFILETYPE
  • EDOFILETYPEV
  • EDOFILETYPET
  • EDOSRCTYPE
  • EDOSRCTYPET
  • TBE31
  • TMENU01
  • TTREES
  • TVIMF
  • /EDGE/SII_PAR_MW
  • /EDGE/SII_CS001
  • /EDGE/SII_CS002
  • /EDGE/SII_MP_000
  • /EDGE/SII_MP_005
  • /EDGE/SII_PRIORI
  • /EDGE/SII_MPT014
  • /EDGE/SII_MP_014
  • /EDGE/SII_VAL_01
  • /EDGE/SII_CO_015
  • /EDGE/SII_MPT010
  • /EDGE/SII_MP_010

The order to activate these two BC_SETs is as follows:

First activate /EDGE/SII_BC_SET_SP5_SIN_MANDANT and then /EDGE/SII_BC_SET_SP5_CON_MANDANT.

To activate a BC_SET go to t-code SCPR20. Enter the name of BC_SET: /EDGE/SII_BC_SET_SP5_SIN_MANDANT.

Click on the   Consistency Check icon and check that no errors occur.

This Warning may appear: Field TABNAME of set CE /EDGE/SII_BC_SET_SP5_SIN_MANDANT is not an integral part of table/view EDOTYPE. It can be ignored as this field is irrelevant in the information provided from the product for this table.

Once the consistency has been checked, click on the icon to activate it.

Press OK as many times as necessary. 

During activation, the process will request a transport request.

This way the BC_SET would be activated.

It may be that after activation is complete, a message appears with information about the activation:

Termination with warnings

To see these warnings press the log icon:

The same warnings appear as when the performance of the BC_SET consistency was done.

To check that it has been activated successfully, the transport request can be checked. The following tables must appear in the generated transport request:

  • /EDGE/SII_MP_000
  • /EDGE/SII_MP_005
  • /EDGE/SII_PRIORI
  • BALOBJ
  • EDOPROCSTEPV
  • EDOTYPEV
  • /EDGE/SII_CS002 
  • EDOPROCSTEPVERV
  • V_BALSUB

Due to a failure in the properties of table /EDGE/SII_MP_010, it is not automatically introduced in the transport request and must be added manually. To do this, add an entry in the task as follows:

R3TR TABU /EDGE/SII_MP_010

Press the key icon and add the follow information:


Repeat this process for BC_SET /EDGE/SII_BC_SET_SP5_CON_MANDANT in all available clients.

During the activation of this BC_SET, two transport request will be requested (Workbench and Cust.) To check that the BC_SET has been activated correctly, check that the following tables have been entered in the Workbench request:

  • /EDGE/SII_CO_015
  • TVIMF
  • V_TVIMF

and in the Customizing request:

  • /EDGE/SII_ERRCOD
  • EDOMAPCLASSDETV
  • EDOSTATUSV

(info.) This BC_SET must be activated in all clients, but the only transport requests that need to be transported to other environments are those that are created when you first activate the BC_SET in a client. The Workbench transport request that is generated will have to be transported to the corresponding environments in a single client. On the other hand, the Customizing transport request must be transported to all other environments in all clients.

(info.) If during the activation of the BC_SETs in the development environment in other clients, any transport request is generated, those transport requests can be ignored.

In the last BC_SET, /EDGE/SII_BC_SET_SP5_CON_MANDANT, the entries for the new error messages defined by the AEAT for the new version of XML are incorporated in the table /EDGE/SII_ERRCOD. It only contains the new messages generated for this version and some changes made to some messages.

In addition, another BC_SET is available to activate, /EDGE/SII_BC_SET_ERR_AEAT, which contains all existing records for this table that are set in the B+ SII product. That is, all error codes that are used in the product. The activation of this BC_SET is neither mandatory nor necessary if all the error codes in the table already exist. It may also be that these error messages associated with the AEAT codes have been modified in some client by creating specific Z messages for each project.

This means that, if this table has been modified manually, activating this BC_SET will replace the existing entries, setting the ones defined by product. It is, therefore, only advisable to activate this BC_SET if this table has not been customized in the system, some error messages are missing and this table needs to be filled with all the possible records existing in the product as standard.

On the other hand, the BC_SET /EDGE/SII_BC_SET_SP5_CON_MANDANT available in this version, also contains entries from table EDOMAPCLASSDETV. The entries contained in this BC_SET are new entries that have been created for this version.

These entries correspond to those with the value 2 in the version field of this table:

These entries identify the mapping classes to be used for the new version of XML with the new mappings 1.1. If these (standard) classes have been replaced for Z classes in the past, this table will have to be adjusted with the new classes of version 2 to fit the existing ones in version 1 of this table. For more information about this functionality, please visit the page 18.5. New mapping classes.

  • Sin etiquetas

Avvale 2024