4.5. Configuración de ICOs

Por cada sistema origen que tengamos habrá que crear 4 escenarios diferentes.

Firma de factura
Generación de código QR
Envío LROE (Foral de Bizkaia)
Envío TicketBAI (Foral de Araba y Gipuzkoa)

Para ello será necesario crear un ICO por cada uno de estos escenarios. Para la unificación de todos los objetos del DIR se recomienda el uso de escenarios de integración.

|BS_XXXX|SI_OS_FirmaFactura||
- Inbound Processing
  - Communication Channel: CC_S_ABAP_PROXY
- Receiver
  - Receiver Determination: Standard
  - Communication Component: BC_PI
- Receiver Interfaces
  - Name: SI_IS_FirmaFactura
  - Namespace: urn:techedgegroup.com:ticketbai:comun
  - OM: N/A
- Outbound Processing
  - Communication Channel: CC_R_AAPP_FirmaOrquestador

|BS_XXXX|SI_OS_GenerarQR||
- Inbound Processing
  - Communication Channel: CC_S_ABAP_PROXY
- Receiver
  - Receiver Determination: Standard
  - Communication Component: BC_PI
- Receiver Interfaces
  - Name: SI_IS_GenerarQR
  - Namespace: urn:techedgegroup.com:ticketbai:comun
  - OM: OM_TICKETBAIQR_TO_QRResponse
- Outbound Processing
  - Communication Channel: CC_R_SOAP_CallDumyFlow

|BS_XXXX|SI_OS_EnvioLROE||
- Inbound Processing
  - Communication Channel: CC_S_ABAP_PROXY
- Receiver
  - Receiver Determination: Standard
  - Communication Component: BC_TICKETBAI
- Receiver Interfaces
  - Name: SI_IS_EnvioLROE
  - Namespace: urn:techedgegroup.com:ticketbai:comun
  - OM: OM_TICKETBAIDTO_TO_LROEORQ
- Outbound Processing
  - Communication Channel: CC_R_AAPP_EnvioLROE

|BS_XXXX|SI_OS_EnvioTBAI||
- Inbound Processing
  - Communication Channel: CC_S_ABAP_PROXY
- Receiver
  - Receiver Determination: Standard
  - Communication Component: BC_TBAI
- Receiver Interfaces
  - Name: SI_IS_EnvioTBAI
  - Namespace: urn:techedgegroup.com:ticketbai:comun
  - OM: N/A
- Outbound Processing
  - Communication Channel: CC_R_AAPP_EnvioTBAI

Escenario auxiliar para calculo de QR, calculo de cabeceras JSON, etc.

|BS_XXXX|SI_OS_DUMMY||
- Inbound Processing
  - Communication Channel: CC_S_SOAP_DUMMY
- Receiver
  - Receiver Determination: Standard
  - Communication Component: BC_PI
- Receiver Interfaces
  - Name: SI_IS_DUMMY
  - Namespace: urn:techedgegroup.com:ticketbai:comun
  - OM: N/A
- Outbound Processing
  - Communication Channel: CC_R_SOAP_DUMMY

Nota: BS_XXXX será el sistema SAP desde donde se realiza el proceso funcional. Normalmente seguirá la nomenclatura de un Business System BS_<SID><MANDANTE> (ejemplos: BS_OSD001 ó BS_NWD100).