| Advertencia | ||
|---|---|---|
| ||
The activation of BC_SETs is mandatory along with the process of installing the version using the software component. Without this activation some product features may not work |
...
To set up this table, go to transaction SM30→Refresh→ New entries.
In this table, you must make entries for the following tables:
- 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:
...
This is due to the SAP version of this table. In product, the records in this table are marked by the key fields:
- PROCESS
- VERSION
- PROCESS_STEP
However, in different versions the key fields may have a non-key field as the second field:
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 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:
Put these table entries into the transfer order (workbench) that BC_SET generates so that they are transported to all other environments.
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 transfer order.
This way 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 view these warnings click on the log icon:
The same warnings appear as when you performed the BC_SET consistency.
If the error occurred earlier in table EDOPROCSTEPV, you can display the error in the log.
To check that it has been activated successfully, you must check that the following tables appear in the generated transfer order:
- /EDGE/SII_MP_000
- /EDGE/SII_MP_005
- /EDGE/SII_MP_010
- /EDGE/SII_PRIORI
- BALOBJ
- EDOPROCSTEPV
- EDOTYPEV
- /EDGE/SII_CS002
- EDOPROCSTEPVERV (if it did not work with BC_SET, enter the manually added entries in the transfer order)
- V_BALSUB
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 transfer orders will be requested. One will be from Workbench and one from Cust. To check that it has been activated correctly, check that the following tables have been entered in the Workbench command:
- /EDGE/SII_CO_015
- TVIMF
- V_TVIMF
and in Custo's order:
| Info | ||
|---|---|---|
| ||
This BC_SET must be activated in all clients, but the only orders required to transport to other environments are those that are created when you first activate BC_SET in a client. The Workbench order that is generated will have to be transported to the corresponding environments in a single client. On the other hand, the order you generate from Customizing must be transported to all other environments in all clients. If, when you activate BC_SET in other development clients, transfer orders are generated, these orders can be ignored. |
In the latter BC_SET, /EDGE/SII_BC_SET_SP5_CON_MANDANT, the entries with the new error messages generated by the AEAT for the new version of XML are incorporated. These entries are in table /EDGE/SII_ERRCOD. It only contains the new messages generated for this version and any changes to an existing one.
In addition, another BC_SET is offered, /EDGE/SII_BC_SET_ERR_AEAT, which contains all existing product records for this table. 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 are already available. It may also be that these error messages associated with the AEAT codes have been modified in some client by creating more specific Z messages for each project.
This means that, if you have changed this table manually, activating this BC_SET will "crush" the existing entries, leaving the ones defined by product active. It is therefore only advisable to activate this BC_SET if this table has not been customized in the system and if you do not have all the error messages available and want to fill the table 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. If you have Z classes, you will have to adjust 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.3. New book of additional properties
Manual actions after activation of BC_SETs
After activation the BC_SET it is necessary to check the /EDGE/SII_PRIORI table. In BC_SETs, new entries are added for this table byt olf entries that are now unusable are not deleted. To solve this problem, all entries that have no value in the "ReleaseXML" fiel (if any) must be deleted from this table. The only entries that must remain in this table are the following:
This process must be performed in all work environments so that the table is aligned and with the same records in all environments.