BAdI CALL BEFORE DACTE RECEIPT x BAdI CALL AFTER DACTE RECEIPT

The following BAdIs (Incoming) are available for SAP Nota Fiscal Eletrônica (NFE):

• BAdI: Step Implementation before/after DACTE
  You can implement a BAdI that is used within the business process Customer-Specific Business Process with DACTE (technical name: CTEFLXBL) to trigger transactions in the integrated ERP system.
• BAdI: Determine Business Process for CT-e
  You can implement a BAdI that carries out a customer-specific business process determination.
• BAdI: Determination of Logical System
  You can implement a BAdI that determines the logical system for the ERP system.
• BAdI: Provide LES Documents in ERP
  You can implement a BAdI that is used in the business process CT-e for Inbound NF-e with LES (technical name CTEINBLE). LES is the abbreviation for Logistic Execution System.

Note

For more information, see the documentation for the BAdIs in Customizing under  Nota Fiscal Eletrônica Inbound Business Add-Ins for Inbound CT-es . 

CT-e Flexible Process

 In addition to the processes included in the standard shipment of SAP Nota Fiscal Eletrônica (SAP NFE), SAP NFE also offers a flexible process that can trigger customer-specific actions in the ERP system. Two new steps have been added to the CT-e Flexible Process (technical name CTEFLXBL) to allow you to call your own actions, events, or processes in the ERP system:

• BAdI Call Before DACTE Receipt (CTEBBEFD): You carry out this BAdI-based step before the arrival of goods and the corresponding DACTE.
• BAdI Call After DACTE Receipt (CTEBAFTD): You carry out this BAdI-based step after the arrival of goods and the corresponding DACTE.

Process

CT-e Flexible Process (CTEFLXBL)

This process consists of the following steps:

1. CTESIGNA (Auto)
   Check Business Partner's Signature
2. CTEAUTHO (Auto)
   Check Authorization After CT-e Receipt
3. CTEBBEFD (Auto)
   BAdI Call Before DACTE Receipt
4. RECDACTE
   Enter DACTE
5. CTEAUTHG (Auto)
   Check Authorization After DACTE Receipt
6. CTEBAFTD (Auto)
   BAdI Call After DACTE Receipt
7. DARNOTIF (Auto)
   Notification about Received DACTE

CTE Flexible Process contains the following technical steps:

Steps 1–2: Check Business Partner's Signature; Check Authorization after CT-e Receipt

Step 1: Check Business Partner's Signature

(Technical name: CTESIGNA)

The system checks if the signature is OK.

• Signature OK: The CT-e has passed the signature check and can proceed to the next processing step. For more information, see the documentation in Customizing under  Nota Fiscal Eletrônica Signature .
• Signature Not OK: The user can manually reject the CT-e and notify the vendor.

Step 2: Check Authorization after CT-e Receipt

(Technical name: CTEAUTHO)

The system checks the CT-e's authorization status received from the SEFAZ tax authority's Web service. This communication is carried out using an asynchronous call.

• XML Authorized: The authorization check was successful and the CT-e can proceed to the next processing step.
• XML Not Authorized: The user can manually reject the CT-e and notify the vendor.

Step 3: BAdI Call before DACTE Receipt;

Step 3: BAdI Call Before DACTE Receipt

(Technical name: CTEBBEFD)

You can implement this BAdI-based step according to your requirements. For more information, see the documentation in Customizing under  Nota Fiscal Eletrônica Incoming Business Add-Ins for Incoming CT-esBAdI: Step Implementation before/after DACTE .

Steps 4–6: Enter DACTE; Check Authorization After DACTE Receipt; BAdI Call After DACTE Receipt

The vendor sends goods together with a DACTE to your company, and the goods and DACTE arrive.

Step 4: Goods Arrived, Enter DACTE

(Technical name: RECDACTE)

The NF-e fiscal clerk notifies the vendor that the XML has been accepted, and then sets this process step to OK or Not OK. If the status is OK, the system automatically continues with the next step.

Step 5: Check Authorization After DACTE Receipt

(Technical name: CTEAUTHG)

The system automatically checks the authorization status of the XML via the SEFAZ tax authority's Web service.

Step 6: BAdI Call After DACTE Receipt

(Technical name: CTEBAFTD)

You can implement this BAdI-based step according to your requirements. For more information, see the documentation in Customizing under  Nota Fiscal Eletrônica Incoming Business Add-Ins for Incoming CT-esBAdI: Step Implementation before/after DACTE .

Step 7: Notification about Received DACTE;

(Technical name: DARNOTIF)

Source: BAdIs for Inbound CT-es

Source: CT-e Flexible Process

Source: Business Process Determination for CT-es