Comparación de páginas

Installation files

In this release two new support packages are released:

...

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

Image Removed

Image AddedPrerequisites

It is necessary to have the Concilia License component installed: 1.1.2.1 Installation of Concilia LicensesLicense 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.

...

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 by procedure as a Software Components to see where to download the files.

...

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

Image Modified

Image Modified

Image Modified

Once they have been loaded, press 

Then select the TESII component.

The SPs to be installed will appear in green.

Image Modified

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

...

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

Finally check that they have been installed correctly:

Image Modified

BC_SETs activation

...

• /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, you need table SCPRSTAM needs to be set up table SCPRSTAM. This table is client-independent, so it makes no difference in which client you set it up. It is only set for one client.

This customizing can be done using t-code SM30→Maintain→ New entries.

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

...

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  Image Modified 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.

In this consistency check the BC_SET /EDGE/SII_BC_SET_SP5_SIN_MANDANT, may give an error.

Image Added

This is due to the SAP version of this table. In product, the records in this table are defined by the key fields:

• PROCESS
• VERSION
• PROCESS_STEP

Image Added

However, in different versions the key fields may have a non-key field as a second field:

Image Added

This causes problems when entering BC_SET entries in this table.

If this is the case, and this error occurs in this BC_SET, proceed as follows.

Activate the BC_SET despite the error so that all other tables in this BC_SET are recorded in the system. 

Then, enter the following entries manually in the view of the SM30 EDOPROCSTEPVERV:

Image Added

Insert these table entries into the transport request (workbench) that the BC_SET generates so that they are transported to all other environments.

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

Press OK as many times as necessary. 

During activation, the process will request a transport request.

...

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

If the error occurred earlier in table EDOPROCSTEPV, you will see the next error in the log.

Image Added

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

...

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, we add an entry in the task as follows:

...

• /EDGE/SII_ERRCOD
• EDOMAPCLASSDETV
• EDOSTATUSV

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.

...

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 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.25. New mapping classes.

Manual actions after activation of BC_SETs

After activating the BC_SET it is necessary to check table /EDGE/SII_PRIORI. In a BC_SET, new entries are added for this table, but old entries that are now unusable are not deleted. To solve this problem, all entries that have no value in the "VersionXML" field (if any) must be deleted from this table. Thus, the only entries that must remain in this table are the following:

Image Added

This process must be performed in all work environments so that the table is aligned and with the same records in all environments.