Versiones comparadas

Clave

  • Se ha añadido esta línea.
  • Se ha eliminado esta línea.
  • El formato se ha cambiado.

This extension point contains 2 BAdIs:

...

  1. BADI /EDGE/BADI_TB_CREA-> Contains the /EDGE/IF_BADI_TB_CREA interface which has these methods

...

These methods can modify the creation conditions.

The product uses these tables for the creation of annotations and for the self-invoice flow:

...

It is interesting to implement these BAdI methods when you want to modify these flows. For example, create annotations from a Z table instead of the /EDGE/TC_TB_COPR table (DETERMINE) or change the standard auto invoice flows for your own ones (DETERMINE_AUTO, DETERMINE_CLI_PRO).

...

  1. :

...

Only the methods CHANGE_CREATION and CHANGE_ANULATIONS_RECTIFIES have default implementations.

These implementations are located in the /EDGE/CL_BADI_TB_CREA reservation class.

  1. DETERMINE: Modifies creation conditions, for example changing the standard annotation configuration to retrieve data from a Z table.

  2. DETERMINE_AUTO: Modifies the creation conditions of the self invoice flows. It will be necessary when you want to create an auto-invoice for a flow that has not been defined in the standard.

  3. DETERMINE_CLI_PRO: It modifies the conditions for the creation of self-invoice flows replacing the transactions /EDGE/TC_TB_TB_HA_P and /EDGE/TC_TB_TB_HA_C.

  4. DETERMINE_PRIORIDAD: It is necessary to implement it when you want to change the order of priorities established by the standard detailed in : Settings for creating annotations .

  5. CHANGE_CREACION: It is used to add additional conditions that determine whether the flow is generated or not. Its default implementation means that if the document arrives with an empty BSET table, the b+ TicketBAI flow is not generated.

  6. CHANGE_ELECTRONIC_INVOICE: It is used when you want to change the conditions of the electronic invoice in the channel class /EDGE/CL_TB_CHANNEL_GEN.

  7. CHANGE_ANNOUNCEMENTS_RECTIFICA: Modifies if the rectifications/cancellations go through the b+ TicketBAI flow. Its default implementation means that rectifications and cancellations prior to 2022 do not enter the flow.

Image Added

2. BADI /EDGE/BADI_TB_CREA_BAJAS-> Contains the interface /EDGE/IF_BADI_TB_CREA_BAJAS interface which has this method with default implementation that retrieves the canceled voided document.

Image Modified

It would be necessary to implement this BAdI when obtaining the canceled document is obtained overridden by other than the standard logic (see logic in the /EDGE/IF_BADI_TB_CREA_BAJAS ~ GET_DOC_CANCELLED method of the /EDGE/CL_BADI_TB_CREA_BAJAS reservation class of reservation).

...