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.
With the latest product version available (1.7.5), new BC_SETs are released that must be activated regardless of the type of installation. These BC_SETs contain table information that the prodcut needs to work properly. The BC_SETs are as follows:
- /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 has to be activated in every available client because the information it contains is client-dependent.
/EDGE/SII_BC_SET_SP6_SIN_MANDANT: It only needs to be activated in one client since its tables are not client-dependent.
/EDGE/SII_BC_SET_SP6_CON_MANDANT: It has to be activated in every available client because the information it contains is client-dependent.
The order to activate these BC_SETs is as follows:
- /EDGE/SII_BC_SET_SA_SIN_SIN_MANDT (if applicable)
- /EDGE/SII_BC_SET_SA_CON_MANDT (if applicable)
- /EDGE/SII_BC_SET_SP5_SIN_MANDANT
- /EDGE/SII_BC_SET_SP5_CON_MANDANT
/EDGE/SII_BC_SET_SP6_SIN_MANDANT
/EDGE/SII_BC_SET_SP6_CON_MANDANT
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.
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):
- 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
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. 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.
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_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./EDGE/SII_BC_SET_SP5_SIN_MANDANT
During BC_SET /EDGE/SII_BC_SET_SP5_SIN_MANDANT activation, you may get an error when checking or activating.
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
However, in different versions the key fields may have a non-key field as a 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 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:
| Proc. edoc. | Process Description | Ver. | Process Step | Proc. Step Description |
|---|---|---|---|---|
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | ||
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | ACCEPT | Accept Batch |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | ACCEPT_ERR | Accept Batch with errors |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | CORR_LOTE | Correct Batch |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | CREATE | Create Batch |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | DIS | Discard batch ECC |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | DISMW_DIS | Discard batch MW+ECC |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | ERROR_MW | Error in MW process |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | GENXML_SEN | Generate XML and send to MW |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | MAP_ERROR | Mapping error |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | REJECT | Reject Batch |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | REPROC_MW | Reprocessing Middleware |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | RESEND | MW Forwarding Request |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | SACAR_INT | Remove eDocs from eDocs Batch |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | TIME_OUT | Time Out Error |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | VXML_DISMW | Cancel XML&discard Batch MW+EC |
| /EDGE/SIIL | Sistema Información Imp. Lotes | 2 | VXML_TCORR | Cancel XML and technical corre |
Insert these table entries into the transport request (workbench) that the BC_SET generates so that they are transported to all other environments.
Finally, if the log is checked, you will get the following errors:
During the process you will request a transport request.
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
EDGE/SII_BC_SET_SP5_CON_MANDANT
During the activation of the BC_SET EDGE/SII_BC_SET_SP5_CON_MANDANT, 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
|
/EDGE/SII_BC_SET_SP6_SIN_MANDANT
During BC_SET /EDGE/SII_BC_SET_SP6_SIN_MANDANT activation, a Workbench transport request is requested.
To check that it has been activated successfully, you must check that the following tables appear in the generated transport request:
- /EDGE/SII_CO_015
- /EDGE/SII_MP_000
- /EDGE/SII_MP_010
- /EDGE/SII_MP_014
- EDOPROCSTEPV
- EDOTYPEV
- TDDAT
- TMENU01
- TMENU01R
- TTREES
- V_FILENACI
- V_ARC_USR
/EDGE/SII_BC_SET_SP6_CON_MANDANT
During activation of BC_SET /EDGE/SII_BC_SET_SP6_CON_MANDANT, a customizing transport request is requested.
To check that it has been activated successfully, you should check that the following table appears in the generated transfer order:
- /EDGE/SII_ERRCOD
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.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.
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.2. New mapping classes.
If this installation process is being performed for the first time on a system that had nothing installed from the B+ SII, you need to activate BC_SET /EDGE/SII_BC_SET_ERR_AEAT. If this is the case, another BC_SET, /EDGE/SII_BC_CLASES_MAPEO, has also been created, containing all the standard records from table EDOMAPCLASSDETV with the standard mapping classes used in the product for both versions (1.0 and 1.1), which must be activated.
These two BC_SETs are client-dependent and must be activated, as a result, in all available clients.
Important: The BC_SET /EDGE/SII_BC_CLASES_MAPEO must not be activated in an installation process where the system already had the B+ SII installed. Activating this BC_SET will replace the entries in this table with the standard product entries. If this table has never been modified manually, and the mapping classes set are standard, then there is no risk of losing data and you can activate BC_SET. If, on the other hand, Z mapping classes have been created and set in this table, this BC_SET MUST NOT BE ACTIVATED. If you want to add new entries, you must enter them manually using the documentation in this table: 2.1.6.3. Mapping class customizing per batch And for the foral mapping classes: 2.2.7. Mapping Classes for batches File
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:
This process must be performed in all work environments so that the table is aligned and with the same records in all environments.
- After activating the BC_SETs, it is also necessary to set up table /EDGE/SII_INTERM manually. To do this, go to transaction SM30, enter the name /EDGE/SII_INTERM, press update, press new entries and enter the following entries:
Tipo de eDocument | Descripción de tipo |
|---|---|
/EDGE/BI | Investment Goods Investment Goods Cancel Investment Goods Cancel Inv.Id Charge on Issued Invoice Issued Invoice Issued Invoice Cancel Issued Invoice Cancel Inv.Id Received Invoice Received Invoice Cancel Received Invoice Cancel Inv.Id Intra-Community Operations Intra-Community Op. Cancel Intra-Commun. Op. Canc. Inv.Id Collect on Received Invoice Cadastral Ref. Cadastral Ref. Cancel |
HELP: To easily enter these entries, copy each column of the upper table and paste it into the notepad or any other application of this type to remove the formatting. Then copy them from there and paste them into the corresponding column. Another option is to copy them from the attached text file below.
The table should be finally like this:
FICA records are only required if this module is used in the SII. These do not need to be entered manually as they are incorporated in the corresponding transport request for FICA.