Once the product has been installed using a software component, it is necessary to activate a few BC_SETs that allows to configure the tables used in b+ SII with the necessary data.
If this installation is being done on a system where the b+ SII product is being installed for the first time, i.e. the system does not have this product installed using another procedure, these two BC_SETs need to be activated:
- /EDGE/SII_BC_SET_SA_SIN_MANDT: It only needs to be activated in one client since its tables are not client-dependent.
- /EDGE/SII_BC_SET_SA_CON_MANDT: It has to be activated in every available client because the information it contains is client-dependent.
Important: If the product is being upgraded to a new version, or if this process is being performed to change the installation procedure to Software Component after the initial installation was performed using transport request, THESE TWO BC_SETs MUST NOT BE ACTIVATED.
If the installation of this product is being done for the first time in the system, it will be necessary to activate all the BC_SETs available so far. The BC_SETs are as follows:
- Activation of BC_SETs release 1.7.4
- Activation of BC_SETs release 1.7.5
- Activation of BC_SETs release 1.7.6
- Activation BC_SETs version 1.7.7
- BC_SETs activation release 1.7.8.
- Activation of BC_SETs release 1.7.9
- Activation BC_SETs version 1.7.9.1
- Activation BC_SETs version 1.8.0
- Activation BC_SETs version 1.8.1 BC_SETs version 1.8.1
If, on the other hand, the product is being upgraded to installation by Software Component, the BC_SETs of the applicable versions must be activated:
- If the product version 1.7.4 has not been previously installed in the system by means of transport orders, activate the BC_SETs of this version: Activation of BC_SETs release 1.7.4
- If product version 1.7.5 has not been previously installed in the system via transport orders, activate the BC_SETs of this version: Activation of BC_SETs release 1.7.5
- If the product version 1.7.6 has not been previously installed in the system by means of transport orders, activate the BC_SETs of this version: Activation of BC_SETs release 1.7.6
- If the product version 1.7.7 has not been previously installed in the system by means of transport orders, activate the BC_SETs of this version: Activation BC_SETs version 1.7.7
- If product version 1.7.8 has not been previously installed in the system by means of transport orders, activate the BC_SETs of this version: BC_SETs activation release 1.7.8.
- If product version 1.7.9 has not been previously installed in the system by means of transport orders, activate the BC_SETs of this version: Activation of BC_SETs release 1.7.9
- If product version 1.7.9.1 has not been previously installed in the system by means of transport orders, activate the BC_SETs of this version: Activation BC_SETs version 1.7.9.1
If version 1.8.0 of the product has not been previously installed in the system through transfer orders, activate the BC_SETs of this version: Activation BC_SETs version 1.8.0.
If version 1.8.1 of the product has not been previously installed in the system through transfer orders, activate the BC_SETs of this version: Activation BC_SETs version 1.8.1.
The order of activation of these BC_SETs will be as quoted in this guide. So the order would be as follows:
- /EDGE/SII_BC_SET_SA_SIN_MANDT (if activation is needed)
- /EDGE/SII_BC_SET_SA_CON_MANDT (if activation is needed)
- /EDGE/SII_BC_SET_SP5_SIN_MANDANT (if activation is needed)
- /EDGE/SII_BC_SET_SP5_CON_MANDANT (if activation is needed)
/EDGE/SII_BC_SET_SP6_SIN_MANDANT (if activation is needed)
/EDGE/SII_BC_SET_SP6_CON_MANDANT (if activation is needed)
/EDGE/SIICNC_BC_SET_SP7_CON_MDNT (if activation is needed)
/EDGE/SII_BC_SET_SP7_SIN_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP7_CON_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP8_SIN_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP8_CON_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP9_SIN_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP9_CON_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP10_SIN_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP10_CON_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP11_CON_MDNT (if activation is needed)
- /EDGE/SII_BC_SET_SP12_CON_MDNT
- /EDGE/SII_BC_SET_SP13_SIN_MDNT
- /EDGE/SII_BC_SET_SP13_CON_MDNT
Before activating them, you need to configure the SCPRSTAM table. This table is independent of the client, so it does not matter in which client to configure it. It is only set for one client.
To configure this table go to transaction SM30→Update→ New Entries.
In this table you have to enter 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
- /EDGE/SII_MIDDLE
- /EDGE/SII_INTERM
- /EDGE/SIITINTERM
- /EDGE/SII_PRO_SR
Activation example for a BC_SET
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.
- Field REF_PROCESS of set CE /EDGE/SII_BC_SET_SA_SIN_MANDT is not an integral part of table/view EDOP.
They can be ignored as this fields are 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.
Note: This process must be repeated for each BC_SET that needs to be activated. Note that some of them are client-dependent, so they must be activated in all the available clients.
Notes for each BC_SET activation
/EDGE/SII_BC_SET_SA_SIN_MANDT
During activation of BC_SET /EDGE/SII_BC_SET_SA_SIN_MANDT, the process will request a transport request.
To check that it has been activated successfully, the following tables must appear in the generated transport request:
- /EDGE/SII_MP_000
- /EDGE/SII_MP_005
- /EDGE/SII_MP_014
- /EDGE/SII_PRIORI
- BALOBJ
- EDOCOUNTRYTCH
- EDOFILETYPEV
- EDOPROCESSV
- EDOSRCTYPEV
- EDOTYPEV
- TBE11
- TMENU01
- TMENU01R
- TTREES
- TTXOB
- TVIMF
- V_TVIMF
- /EDGE/SII_CS001
- /EDGE/SII_CS002
- EDOPROCSTAFLAGV
- EDOPROCSTEPV
- TBE31
- TMENU01T
- TTXID
- V_BALSUB
- EDOPROCSTEPVERV
- EDOPROCFLAGASGV
/EDGE/SII_BC_SET_SA_CON_MANDT
During activation of BC_SET /EDGE/SII_BC_SET_SA_CON_MANDT, the next pop-up can appear:
Click on "Copy values" with no data in Company Code field.
Afterwards, the process will ask for two transport requests (Workbench and Custo.).
To check that it has been activated successfully, the following tables must appear in the generated transport request (Custo):
- /EDGE/SII_AL_010
- /EDGE/SII_AL_015
- /EDGE/SII_ERRCOD
- /EDGE/SII_MP_002
- /EDGE/SII_VAL_01
- EDOSTATUSV
The Workbench request will be empty.
|
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.