4.5. ICOs Configuration

For each source system we will have to create 4 different scenarios.

• Invoice signature

• QR code generation

• Sending LROE (Foral de Bizkaia)

• Sending TicketBAI (Foral de Araba and Gipuzkoa)

To do so, it will be necessary to create an ICO for each of these scenarios. For the unification of all DIR objects, the use of integration scenarios is recommended.

• |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

 Auxiliary scenario for QR calculation, JSON header calculation, 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

Note: BS_XXXX will be the SAP system from which the functional process is performed. Normally it will follow the nomenclature of a Business System BS_<SID><MANAGER> (examples: BS_OSD001 or BS_NWD100).