Activation of BC_SETs
- Soporte Techedge BPLUS ES
The activation of the BC_SETs is mandatory along with the installation process of the version via software component. Without this activation, some functionalities of the product may not work.
The BC_SETs that are provided with version 1.0 and 1.1 are as follows:
Version | SP level | BCset with custom without client | BCset with custom with client |
|---|---|---|---|
100_700 | 0000 | /EDGE/TB_BCSET_SIN_MNDT_1 | /EDGE/TB_BCSET_CON_MNDT_1 |
100_700 | 0001 | /EDGE/TB_BCSET_SIN_MNDT_2 | /EDGE/TB_BCSET_CON_MNDT_2 |
100_700 | 0002 | /EDGE/TB_BCSET_SIN_MNDT_3 | /EDGE/TB_BCSET_CON_MNDT_3 |
100_700 | 0003 | /EDGE/TB_BCSET_SIN_MNDT_4 | /EDGE/TB_BCSET_CON_MNDT_4 |
100_700 | 0004 | /EDGE/TB_BCSET_SIN_MNDT_5 | /EDGE/TB_BCSET_CON_MNDT_5 |
100_700 | 0005 | /EDGE/TB_BCSET_SIN_MNDT_6 | /EDGE/TB_BCSET_CON_MNDT_6 |
100_700 | 0006 | /EDGE/TB_BCSET_SIN_MNDT_7 | /EDGE/TB_BCSET_CON_MNDT_7 |
100_700 | 0007 | /EDGE/TB_BCSET_SIN_MNDT_8 | /EDGE/TB_BCSET_CON_MNDT_8 |
Before activating the bc_set of the level of SP 0002, the bc_set of the product b + Alarms must be activated
BC_SET activation
To activate the BC_SET use transaction SCPR20.
Activate in the same order in which they appear in the previous table, activating first those for WITHOUT CONTROLLER and secondly those for WITH CONTROLLER.
For each of the BCset, perform the following steps for activation:
1 - Check the consistency of the BCset
2 - Once the consistency has been checked, press the icon to activate it:
3 - Customizing or workbench orders will be required to store the table content.
BC_SETs are only activated in the development environment. For the custo to reach the rest of the environments, the transport orders generated when activating the BC_SETs under development will be transported.
4 - We click on continue:
In some cases it is possible that errors may appear when activating, in these cases we will have to reactivate the BCset, this is because there are entries that are dependent on others that are in the same BCset.
List of objects by BCset
BCset | Objetos Customizing | Objetos Workbench |
|---|---|---|
/EDGE/TB_BCSET_SIN_MNDT_1 | ||
/EDGE/TB_BCSET_CON_MNDT_1 |
| |
/EDGE/TB_BCSET_SIN_MNDT_2 |
|
|
/EDGE/TB_BCSET_CON_MNDT_2 |
|
|
/EDGE/TB_BCSET_SIN_MNDT_3 |
|
|
/EDGE/TB_BCSET_CON_MNDT_3 |
|
|
/EDGE/TB_BCSET_SIN_MNDT_4 |
|
|
/EDGE/TB_BCSET_CON_MNDT_4 |
|
|
/EDGE/TB_BCSET_SIN_MNDT_5 |
|
|
/EDGE/TB_BCSET_CON_MNDT_5 |
|
|
/EDGE/TB_BCSET_SIN_MNDT_6 |
| |
/EDGE/TB_BCSET_CON_MNDT_6 |
| |
/EDGE/TB_BCSET_SIN_MNDT_7 |
| |
/EDGE/TB_BCSET_CON_MNDT_7 |
| |
/EDGE/TB_BCSET_SIN_MNDT_8 |
| |
/EDGE/TB_BCSET_CON_MNDT_8 |
|
Detected errors
/EDGE/TB_BCSET_SIN_MNDT_1
These errors will appear but if it is activated again they should not appear
/EDGE/TB_BCSET_CON_MNDT_1
If these errors appear about PNG, it means that the PNG document type does not exist in the archivelink settings.
We must create it.
To create the png we have to go to the transaction spro-> SAPNetWeaver -> Application server → Base Service → ArchiveLink → Base Customizing → Treat document types.
We will save this entry.
We activate the BC_SET again and the errors will disappear.
/EDGE/TB_BCSET_SIN_MNDT_3
/EDGE/TB_BCSET_CON_MNDT_3
You will get these errors but if you re-activate it you should not get them
/EDGE/TB_BCSET_SIN_MNDT_4
These errors will appear but can be ignored
/EDGE/TB_BCSET_SIN_MNDT_5
These errors will appear but can be ignored.
/EDGE/TB_BCSET_SIN_MNDT_6
These errors will appear but can be ignored.
/EDGE/TB_BCSET_SIN_MNDT_7
These errors will appear but can be ignored.
/EDGE/TB_BCSET_SIN_MNDT_8
These errors will appear but can be ignored.
/EDGE/TB_BCSET_CON_MNDT_8
These errors will appear but it must be activated again.
After the second activation it should look like this, these errors can be ignored:
Avvale 2024