Baixe manual configuração cte inbound e outras Esquemas em PDF para Sistemas Operacionais, somente na Docsity!
MANUAL DE CONFIGURAÇÃO CT-e INBOUND
- 1- CT-e Inbound............................................................................................................................ Sumário
- 2- Processing Inbound CT-es........................................................................................................
- 3- Business Process Determination for CT-es...............................................................................
- 4- Process Settings and Customizing (Inbound)............................................................................
- 5- CT-e Basic Process....................................................................................................................
- 6- CT-e Cancellation Process.......................................................................................................
- 7- CT-e Flexible Process..............................................................................................................
- 8- BAdIs for Inbound CT-es.........................................................................................................
- 9- CT-e Fiscal Workplace............................................................................................................
- 10- CT-e for NF-e Inbound with LES (Logistic Execution System)................................................
- 11- CT-e for NF-e Outbound with LES (Logistic Execution System).............................................
- 12- CT-e for NF-e Inbound with TM (Trade Management).........................................................
- 13- CT-e for NF-e Outbound with TM (Trade Management)......................................................
- 14- Events for CT-e.....................................................................................................................
1- CT-e Inbound
O CT-e de entrada do SAP Nota Fiscal Eletrônica tem o seguinte escopo: Gerenciar e automatizar a recepção de facturas electrónicas recebidas de fornecedores:
- CT-e - recepção / validação de faturas de frete de entrada O CT-e de entrada do SAP Nota Fiscal Eletrônica é composto dos seguintes tópicos:
2- Processing Inbound CT-es
Identificação de Processos de Negócios Você deve identificar o processo de negócio correta para cada CT-e individual antes de processamento. Pré-processamento Passo 1: Receber o CT-e
**- O fornecedor envia uma CT-e via XML para a empresa.
- O sistema recebe a entrada CT-e do fornecedor via PI, verifica se o CT-e é relevante para a empresa, e salva-lo ao banco de dados. Preprocessing Step 2: Identify the Correct Business Process** The business process is identified. For more information, see: Business Process Determination for CT-es. You can control the process determination with the Business Add-In Determine Business Process for CT-e in Customizing: Nota Fiscal Eletrônica Inbound Business Add-Ins for Inbound CT-es BAdI: Determine Business Process for CT-e. For a detailed description of business processes, see: CT-e Basic Process CT-e Cancellation Process CT-e Flexible Process CT-e for NF-e Inbound with LES (Logistic Execution System) CT-e for NF-e Outbound with LES (Logistic Execution System) CT-e for NF-e Inbound with TM (Trade Management) CT-e for NF-e Outbound with TM (Trade Management)
3- Business Process
Determination for CT-es
You have maintained a logical system for each ERP system (see the corresponding Customizing activity). Activities Define the assignment of the recipient’s CNPJ number to the corresponding ERP system. Example o Recipient's CNPJ 1234567890 o Logical System ABCCLNT If an NF-e is received for CNPJ number 1234567890, system ABCCLNT400 is determined. NF-e: Maintain Business Process Determination for Inbound NF-es Use In this Customizing activity, you assign specific business processes to incoming NF-es for further processing. The business processes are determined based on the CFOP codes that are assigned to the NF-e items. If the CFOP code does not enable identification of a unique business process, the NF-e is not assigned. Requirements Every CFOP code that is to be used must be assigned a business process. Wildcard entries are not supported. This means if a value such as * or blank is entered for the CFOP code, the business process is not determined. Activities Enter the CFOP codes you want to use to determine business processes and assign the corresponding business processes to them. For more information, see the documentation in Customizing under Nota Fiscal Eletronica Inbound Maintain Business Process Determination for Incoming NF-es. Maintain Control Parameter for Process Flow Use In this Customizing activity, you perform certain steps to further process an incoming document (NF-e, CT-e, or Event). These process steps are determined from the business process to which the NF-e was assigned based on the CFOP codes of its items (This is only true for NF-es; for CT-es and events, the CFOP code is not used for business process determination). The process flow for this business process is contained in table /XNFE/PROCFLOW. You can determine how the process flow is handled, dependent upon the sender's and/or recipient's CNPJ number in the incoming document. The Control Settings field lets you control the processing of a process step. It has the following options: o Manual = The process step is not processed automatically during the process. The automatic process stops at this process step. The user performs this step manually. o Automatic = The process step is performed automatically during the process - that is, without user interaction. If processing is successful, the step status is set to OK and the process is continued. o You can use the following options in the Inactive field to deactivate a process step:
o " " = The process step is active and can be executed automatically or manually, depending on the settings in the Control Settings field. o "X" = The process step is deactivated: The process step is not carried out, but the status of this step is set to OK and the process continues to the next step. Requirements You can maintain a blank entry for CNPJ codes. The system uses the following search sequence to determine the valid entry: o Search with both CNPJ numbers to find an entry o Search with the recipient's CNPJ number to find an entry o Search with the sender's CNPJ number to find an entry o Search with two blank CNPJ numbers to find an entry Make sure that at least the generic entry (blank CNPJ field) is present for each process step. Standard settings Steps that are essential to the process flow cannot be deactivated. Activities Define the process type and process step that you want to influence. Enter the CNPJ numbers in accordance with the criteria listed before, taking the search sequence into account. Define the suitable control options. NF-e: Maintain Assignment of Item Category to CFOP Code Use In this Customizing activity, you can maintain the assignment of item categories to CFOP codes. This assignment is relevant for determining the correct business process. The item categories represent the meanings of the CFOP codes. They have different priorities in the determination of the business processes. If an NF- e contains both main items and other item categories, then only the main items are used to determine the business process. Activities Maintain the assignment of item categories to CFOP codes. If no entry is created for a CFOP code, then the item category for that CFOP code is Blank, which means it is a main item. Example In subcontracting cases, the NF-e can contain a final product (= main item) and the subcontracting components (= symbolic return). To determine the correct business process, the entries must be maintained for the final product and the subcontracting components, to enable assignment of the corresponding item categories: CFOP Item Category 5124 Main Item 5902 Symbolic return of subcontracting component Define Control Parameters for Process Steps Use In this Customizing activity, you can define various activities for a specific process step. These process steps are determined from the business process to
If the service taker with CNPJ 74.544.297/0004-35 acts as goods sender (TOMA = 0), then process type B is determined for the incoming CT-e. If a service taker with a differing CNPJ acts as goods receiver (TOMA = 3), then process type A is determined for the incoming CT-e. Control Parameters for Process-Independent Actions Use In this Customizing activity, you can define parameters for process-independent actions. You can define the parameters depending on your own tax number (CNPJ). The available action can be selected with the corresponding parameter. Various values are available for the parameter. Requirements If no value is defined for an own tax number and an action, the system automatically uses a default value. Likewise, the system also uses the standard settings when the Value field is blank for a given activity. Activities Define the action you want to influence. You can limit your selection by the tax number (CNPJ). You can define a blank entry for the CNPJ codes. The system always searches an entry with the CNPJ number first. If none is found, the system searches an entry with a blank CNPJ number. Example If an NF-e or CT-e is received more than once, you can choose the following values: Exception; Visible as an application error in PI This is the default setting. The corresponding XML message is displayed in the PI message monitor with an application error. Ignore; Entry in history table. The corresponding XML message is displayed in the PI message monitor as successfully processed. Only an entry in the document history indicates that the document was received several times. If an NF-e is received with a receiver-CNPJ that is not maintained in Customizing as an own CNPJ, you can choose the following values: Book in NF-e without assigning a business process Exception; Visible as an application error in PI NF-e: Define Reasons for Rejection; Assign to Events Use In this Customizing activity, you specify the reasons for rejecting processing for incoming NF-es. Only the texts defined in this activity can be selected as reasons for rejection. If vendor notification is active (in the rejection case), the selected rejection text can be sent to the business partner as part of an e-mail. Activities Enter the abbreviation for a rejection and enter a descriptive text. Example Rejection Rejection Text AUTHORIZ The NF-e is not authorized SIGNATUR The signature is not valid CT-e: Define Reasons for Rejection Use
In this Customizing activity, you specify the reasons for rejecting the processing of inbound CT-es. Only the texts defined in this activity can be selected as reasons for rejection. The selected rejection text can be sent to the business partner as part of an e-mail. Activities Enter the abbreviation for a rejection and enter a descriptive text. Example Rejection Rejection Text AUTHORIZ The NF-e is not authorized SIGNATUR The signature is not valid Maintain Mail Sender Parameters for Own Tax Numbers Use In this Customizing activity, you assign an e-mail address to incoming NF-es for your own tax number (CNPJ). This e-mail address is used as the sender address for e-mail communication. If you do not define this entry, the system tries to use the e-mail address of the currently active user. You can enter the e-mail text with the rejection in the Rejection Text Name field. You can enter the e-mail text with the acceptance in the Acceptance Text Name field. You can maintain these texts using transaction code SO10; the text ID must be NFE. You can use the following fields from structure /XNFE/NFE_COM_TEXT to create the texts: o NFEID - Access key o TYPE - NF-e type o FINNFE - Issue function o CNPJ_EMIT - CNPJ number of the NF-e issuer o C_XNOME - Company name of the NF-e issuer o CNPJ_DEST - CNPJ/CPF number of the NF-e recipient o E_XNOME - Company name of the NF-e recipient o SERIE - Series o NNF - NF-e number o NOTIFICATION - Rejection text Activities Enter a valid e-mail address as sender address for your tax number. Optional: Use transaction code SO10 to enter a user-defined rejection text for your tax number. Example Your tax number Sender mail address Rejection text name Acceptance text name 74544297000435 John.Q.Public@SAP.COM NFE_REJECTION_TEXT NFE_ACCEPTANCE_TEXT Maintain Communication Parameters for Partner Tax Numbers Use In this Customizing activity, you define the communication parameters for a business partner. The business partner tax number must be entered. Optional: You can also enter your own tax number and link it with the business partner tax number. The recipient e-mail address determines where notifications are sent during e-mail communication. If no recipient e-mail address is entered for a business partner tax number, then e-mail notification is not possible for that business partner.
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 process stops. 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.
6- CT-e Cancellation Process
You use the CT-e cancellation process to cancel a CT-e (technical name: CTECANCL). The cancellation process consists of the following steps: Check Business Partner's Signature
The process type is Check Business Partner's Signature (technical name: CTESIGNA), the corresponding cancel process type is Cancellation of CT-e, general process (technical name: CTECANCL). Check Authorization After Cancellation CT-e The process type is Check Authorization After Cancellation CT-e (technical name: CTEAUTHC), the corresponding cancel process type is Cancellation of CT- e (technical name: CTECANCL).
Process
If a canceled CT-e arrives, the system carries out the following steps. If the automatic process fails, then the user can manually carry out individual follow-on actions in the workplace. Assign Business Process Cancellation of CT-e (technical name: CTECANCL Step: Check Business Partner's Signature (technical name: CTESIGNA) Check if this step was carried out correctly: o If yes, proceed to the next check. o If No, then the step is not OK and either the user or the system can decide what happens with this CT-e: o Cancellation rejected: Go back to original process and continue there. o Cancellation accepted: The CT-e is canceled and the processing finished.
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-es BAdI: 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.
Actions in Step 7: The sender is notified that the DACTE has been received.
8- BAdIs for Inbound CT-es
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.
9- CT-e Fiscal Workplace
A transport service provider can issue a freight document called conhecimento de transporte eletrônica (CT-e). The CT-e Fiscal Workplace is where the fiscal clerk processes incoming CT-es.
Queries
Today The Today query lists all CT-es received today with their main header data and the status information. Overview The Overview query lists all CT-es with their main header data and the status information.
List
Based on your selection criteria, the CT-e Fiscal Workplace displays a list of CT-es and their processing status. The following status icons are used: Process Completed; CT-e Processed Successfully. This icon represents the following statuses: o 99 -> Process Completed; Document Successfully Processed o 98 -> Document Manually Closed Process completed; CT-e rejected. This icon represents status 89. The CT-e processing finished with a rejection by the user with no option to continue processing. Process Waiting for Asynchronous Reply. This icon represents status 11. Technical Error in preceding Process Step. This icon represents the following statuses: o 02 -> Error in last process step o 03 -> Technical error in last process step To correct the error, go to the status overview and check the problem description in the last activity. After correcting the problem, you can continue the process either by using the corresponding step-specific user interface or with the action Continue Process. Process waiting for user action. This icon represents status 01. The process stopped for the user to carry out necessary actions on the corresponding step-specific user interface.
For setting the current process step to OK, despite the fact that the process step was not carried out successfully. o End CT-e Manually For ending the CT-e processing in the NFE system without carrying out any further steps. o Reject CT-e To reject the CT-e and to stop further processing in the NFE system. o Send Notification To send a notification to your business partner.
CT-e Details
You can display the details by choosing a CT-e's Access Key, or by selecting the corresponding line and choosing Display Details. The details view displays the entire content of the XML in several tabs and grouped according to the tags in the XML.
Navigation
You can access the CT-e Fiscal Workplace in SAP NFE via one of the following options: You can call up the specific menu Fiscal Workplace from the user role /XNFE/ WP_NFE_IN_FISCAL(Menu: NF-e Inbound Fiscal Workplace). You can access this option from the user role by choosing Fiscal Workplace: Inbound Messages CT-e.
10- CT-e for NF-e Inbound with
LES (Logistic Execution
System)
The following scenario is used as an example to illustrate this process: The goods receiver pays for the transport together with the delivery, the inbound CT-es and NF-es are posted in the system.
Example
- The truck arrives and the driver hands over all the documents.
- The DACTE and DANFEs are scanned. The inbound CT-e is processed in the goods receiver system according to the process CT-e for NF-e Inbound with LES (CTEINBLE).
- Finally the invoice receipt for the CT-e is posted.
Process
CT-e for NF-e Inbound with LES (CTEINBLE) This process consists of the following steps:
- CTESIGNA Validate Signature of Business Partner
- CTEAUTHO Check Authorization After CT-e Receipt
- CTEILVAL Validation
- CTEILFCD Provide LES Documents Through BAdI
- CTEILIVS Invoice Simulation
- RECDACTE Enter DACTE
- CTEAUTHG
