2370724 - FAQ of Argentina's Electronic Invoice RG2904 (Domestic Scenario)

Symptom

This SAP KBA aims to clarify questions about the implementation and use of the Argentina's Electronic Invoice RG2904 solution that support the legal requirement Resolución General 2904/2010 from AFIP (national tax authority from Argentina). We intend to maintain this SAP KBA updated with new SAP Notes and other future changes regarding the AEI solution. The current SAP's AEI solution is divided in three parts (RG2485, RG2904 and RG2758), which are different general resolutions from AFIP. This SAP KBA is specific for AEI RG2904 solution only. For AEI RG2485 solution, check the SAP KBA 2370680. For AEI RG2758 solution, check the SAP KBA 2370720.

Topic A - Basic processes
Topic B - SAP Notes
Topic C - Common issues
Topic D - PI/XI settings
Topic E - Previous solution

AFIP legal requirement Factura Electrónica: http://www.afip.gob.ar/fe
SAP Help of Localization Argentina: https://goo.gl/jn5Swm
Last update: 10/JAN/2017. New SAP Notes and topic C5.

A - Basic processes and setup of AEI solution

AEI RG2904 solution supports the national legal requirement AFIP Resolución General 2904/2010. Every official document with print character A and B must contain a CAE number (Comprobantes Electrónicos Emitidos) and ODN (Official Document Number) before sending to customers. AEI RG2904 solution is only used for domestic scenario of sales in Argentina, it sends document header and line item information to AFIP, and its main include is LJ1AEF02. The communication of AEI solution happens between ERP and PI systems and AFIP systems, and then the AEI documents are sent to AFIP for CAE approval. In order to install the AEI RG2904 solution, implement the SAP Note 1537823 and follow its instructions in the content of description and attachments. The processes explained below are valid for all three parts of AEI solution (RG2485, RG2904 and RG2758). In case you do not know which is the AFIP RG that you are currently using, check the log of an AEI document in the AEI Monitor (transaction J1AMONITOR or J1AEXPMONITOR), or check table J_1A_RFC_DEST. 

A1 - SD scenario:

When a SD billing document is created, a validation is run to check if it is applicable for AEI solution, based in the country and the Branch details of table J_1ASNR. If the SD billing document is applicable, then an entry for this document is created in the table J_1ACAE with status 'New', and the AEI document is created. The validations performed while saving the SD billing document are to check the mandatory fields for table J_1ACAE. In case of errors, an information is shown in the SD programs and other details in the AEI Monitor J1AMONITOR.

Once the AEI document is in table J_1ACAE, the user can send it to AFIP via AEI Monitor J1AMONITOR or scheduling a background job. If the validation fails before sending AEI document to AFIP, its status is updated to 'Validation Error'. Once the error is corrected in the SD billing document, user is able to reprocess the AEI document in the AEI Monitor J1AMONITOR.

Once the SD billing document is correct, AEI solution preassigns an ODN in the field Reference, sets status 'Sent to AFIP' and assigns a RFC lock. The RFC lock prevents the next authorization to take place before the current one is finished. When the AEI document is approved by AFIP, a CAE number (Comprobantes Electrónicos Emitidos) is assigned, the status is changed to 'Approved' and the ODN is updated with a complete format in the table J_1ACAE.

After this process above, the SD billing document is transferred to FI side, creating the FI accounting document. This procedure is automatically if the billing type has been configured to automatically transfer to FI side. In case the AEI document is rejected by AFIP, its status is changed to 'Rejected' and the rejection code is filled in the table J_1A_WS_REJ and the same pre assigned ODN is reused for other AEI document. Notice that the SD billing document can be saved in SD side, but it cannot be transferred to FI side before it is authorized by AFIP. And once the AEI document is authorized, the SD billing document and AEI document cannot be cancelled anymore.

A2 - FI scenario:

When a FI accounting document is created, a validation is run to check if it is applicable for AEI solution, based in the country and the Branch details of table J_1ASNR and handled via substitution. If the FI accounting document is applicable, then an entry for the document is created in the table J_1ACAE with status 'New'. The validations performed while saving the FI accounting document are to check the mandatory fields for table J_1ACAE. In case of errors, an information is shown in the FI programs and other details in the AEI Monitor J1AMONITOR.

Once the AEI document is in table J_1ACAE, the user can send it to AFIP via AEI Monitor J1AMONITOR or scheduling a background job. If the validation fails before sending AEI document to AFIP, its status is updated to 'Validation Error'. Once the error is corrected in the FI accounting document, user is able to reprocess the AEI document in the AEI Monitor J1AMONITOR.

Once the FI accounting document is correct, AEI solution preassigns an ODN in the field Reference, sets status 'Sent to AFIP' and assigns a RFC lock. The RFC lock prevents the next authorization to take place before the current one is finished. When the AEI document is approved by AFIP, a CAE number is assigned, the status is changed to 'Approved' and an ODN is filled in the table J_1ACAE.

In case the AEI document is rejected by AFIP, its status is changed to 'Rejected' and the rejection code is filled in the table J_1A_WS_REJ. Notice that the FI accounting document is posted without an ODN, and only after the AFIP approval the ODN is filled in the field Reference. A FI accounting document without ODN can be cancelled, in case it is rejected and the problem cannot be solved, but once the AEI document is authorized, the FI accounting document cannot be cancelled anymore.

A3 - Contingency:

In case AFIP systems are down and the requests are not processed, the users can switch a Company Code and Branch to contingency and these details are in the attachments of the main SAP Notes of each part of AEI solution. If a Branch is in contingency, it is substituted in the SD billing document for a Contingency Branch (also known as Manual Branch), which is read from table J_1ASNR. In case of FI accounting document, if a Branch is set in contingency mode, then a pop-up is given to the user where it is possible to choose to switch to a Contingency Branch or not. When the SD and/or FI document is created with Contingency Branch, the ODN generated is stored in the original document and in the AEI document. This information is also stored in the table J_1ACONTINGENCY with ODN and Branch details. Notice that the table J_1ACON is to manage the contingency maintained at Company Code and Branch level, and it stores the details whether a Branch is in contingency or not.

A4 - Communication:

The AEI solution is adapted to be used with PI system and the steps are given in attachments of the main SAP Note 1537823 of AEI RG2904 solution. This is applicable for PI 7.0 and higher releases and the Java environment to be used must be of version 1.4 or higher. If user wants to have their own communication server, use BAPI BAPI_AR_WS_DOMESTIC.

A5 - AEI Monitor:

The tool to monitoring the AEI documents is accessed via transaction J1AMONITOR for AEI RG2485 and AEI RG2904 solutions (and J1AEXPMONITOR in AEI RG2758 solution). The AEI Monitor J1AMONITOR displays the status of the AEI documents and the user is able to process them through AFIP or via Contingency. For more details about how to use the AEI Monitor J1AMONITOR, check the attachment AEI_MONITOR.PDF.

A6 - Customizing:

The procedures to perform the customizing of the AEI solution are described in the attached file AEI_RG2904_SETUP.PDF. Also, review the instructions informed in the Description content and attachments of the main SAP Note 1537823 of AEI RG2904 solution.

A7 - Cash Discount:

For every Cash Discount, a separate credit memo must be posted. Without the automatic discount document generation, the user would have to post this credit memo manually before posting a payment. When posting a payment all Cash Discount amounts would have to be deactivated or deleted. The Cash Discount amount is determined during the payment transaction and when the payment is posted, an additional line item in the payment document is generated which represents a posting on the vendor/customer account. Also in a new document, the Cash Discount credit memo is posted together with and cleared by the payment document. Refer to SAP Notes 1666334, 1741608, 1769771, 1770259, 1791284, 2011669, 2038139, 2087624, 2225577 and 2262013.

B - SAP Notes of AEI RG2904

All SAP Notes for ERP system are only valid for SAP_APPL versions from 600 to 618 releases and for some specific S4CORE or SAP_FIN versions. In case the transaction SNOTE informs you that a specific SAP Note is obsolete for your system version, disregard the SAP Note but review its textual content and attachments. Check if you followed all the manual instructions and if you implemented the last version of SAP Notes. Notice that some SAP Notes have manual pre and post implementation steps in the description content or in their attachments. The list has SAP Notes to be used in the installation of the AEI RG2904 solution, correction issues and manual instructions. Notice that some SAP Notes are just valid for specific versions.

1537823 AEI RG2904 Argentina Electronic Invoice Web Service for Domestic Scenario
1628348 Get Last ODN functionality not working
1639996 Issue with buidling XML data of the FI accounting documents
1640613 XML archiving not working for multiple document
1647385 BAPI Request and response
1669798 Wrong ODN generation for new fiscal year
1671045 Error code 519 due to incorrect unit price
1674372 Wrong amounts sent in request XML
1695567 Issue with unit of measure UoM validation
1728257 Corrections to hardcoding of VAT percentage
1732274 Issue with building XML data for FI documents
1741608 Cash Discount year different from invoice
1758980 Error code 130 due to wrong tax amount in XML
1762169 External date format for issuing date
1762239 Tax amount is not included in document amount
1767610 Wrong tax details sent in request XML
1769152 Corrections to populate header level amounts (SAP Note valid for SAP_APPL 603)
1769512 Partial Rebate Settlements Rejected by AFIP
1770259 Cash Discount branch different and error 'Respective payment reference is not present in J_1ACAE'
1773894 Enhancing values for tax number type
1783904 Correction to VAT amount population
1783981 Non-taxable amount not populated in request XML
1787628 Check on tax and SD billing document amounts
1788373 Update log if FI accounting document reference is not initial
1789421 Condition classes addition to calculate amounts
1790013 Documents rejected when BOM items are invoiced
1791284 Integrating Cash Discount (If SAP Note 1666334 is applied, there is no need to apply this SAP Note)
1791370 Problem with Get last ODN and Contingency
1796869 Archiving Solution for request and response XML
1802117 Unable to reverse an accounting document
1803831 Credit or Debit memo reference not populated
1804976 Unable to process credit and debit memo
1805271 Wrong VAT rate code is populated in request XML
1811089 Invoice rejected due to VAT difference
1812045 Rejection of non taxable accounting documents
1842867 Get Last ODN did not reset RFC sent lock
1844256 Not updating observations in J_1A_WS_REJ table
1847759 Not populating tax details due to rounding
1855046 Free Goods scenario error with zero value
1875999 Item array is not filling for FI accounting documents with manual taxes in XML
1893339 SD billing documents getting rounding error in total amount
1923806 FI accounting document rejected by AFIP when other taxes exist
1927252 Credit or Debit Memo reference modification
1930722 Differentiation between VAT and Perception with same percentage based on Tax Class
1945190 Total exempted amount is not populated in request XML for credit memo
1953825 Get Last ODN did not reset CAE status for first document of a Web Service branch
1958057 Wrong VAT perception ID is reported to AFIP
1959854 Validation error 'Error while checking the integrated data' is reported from SD billing document
1959998 Duplicate message in the message log of J1AMONITOR for Get Last ODN
1962816 Reporting VAT perception details in XML to AFIP in case of minimum amount
1962849 Docs with non local currency rejected (SAP Note not relevant as process is no longer supported by AFIP)
1967880 Tax number is filled from table KNA1 for one time customer
1970029 Wrong amounts for billing doc in request XML
1970562 Documents are rejected from AFIP with error code 501 due to billing quantity is less than 1
1970852 The documents are rejected due to incorrect amounts in request XML
1973608 Request XML item array data is not populated for additional taxes
1973748 Populating wrong item VAT details due to rounding error
1980160 Issues with request XML amounts for official document class 06/07
1987414 Rebate credit notes with negative values in item are not processed to AFIP
1988020 FI documents with other taxes without VAT
1990693 Free Goods scenario error with zero value
1994613 Invoice rejected due to VAT difference
1997703 Incorrect unit price and vat amount for FI accounting documents
2011669 Cash discount with VAT and tax
2013309 Incorrect material code and UOM in XML for rebate documents
2019152 Wrong VAT Rate Code determined for exempt item or non taxable item
2020923 Unable to process credit memo with zero quantity and zero amount
2027509 Corrections to SAP Note 1728257
2028535 Manual VAT adjustment for accounting documents autorizarAjusteIVA
2037083 System failure when using the Get Last ODN
2038139 FI accounting cash discount document rejected by AFIP
2046532 Rounding off difference in invoice total document amount
2052200 FI documents with non taxable amount are rejected
2057475 Check on tax and document amounts
2057494 Not populating tax details due to rounding
2057578 Wrong amounts for SD billing document in request XML
2057604 Issues with request XML amounts for official document class 06/07
2057606 Corrections to SAP Note 1728257
2057609 Free Goods scenario error with zero value
2057672 Documents rejected when BOM items are invoiced
2057743 Free Goods scenario error with zero value
2057750 Invoice rejected due to VAT difference
2059310 Syntax error in implementing SAP Note 1767610
2060139 Wrong branch determined for rebate agreement
2064579 Corrections to archiving SAP Note 1796869
2066754 Rounding issue in function J_1A_WS_ROUND_HALF_EVEN
2067115 AFIP new validations as per web service developer manual version
2082577 CUIT not filled for one time customer
2087624 Perception taxes are not added in XML for cash discount documents
2100099 Problem with Get Last ODN and Contingency
2100148 Get Last ODN did not reset RFC sent lock
2114056 Archiving Solution for AutorizarAjusteIVA request and response XML
2128562 Corrections to archiving SAP Note 1796869
2133442 Billing documents are rejected by AFIP with error code 517
2148108 Rounding error in item total VAT amount of SD billing documents
2155992 Corrections due to change in length of official document type
2156662 Partner functions are not populated for delivery related billing
2159044 Free Goods with zero net value documents are not processing
2162840 Total SD billing document amount calculated in request XML is zero
2210522 Documents are not sent to AFIP due to validation error
2224511 Error code 511
2262013 AFIP rejection for payment reference
2271301 Rounding difference in invoice document amount before sending documents to AFIP
2301183 Difference in calculated total amount and document total amount
2350439 Header conditions incorrectly impacting on XML total amount
2351937 Rejection of Accounting Documents with Non-Taxation Amounts

C - Common Issues of AEI RG2904

C1 - Difference in the cents due to different currencies: As informed in the consulting SAP Note 2117220, minor variation of amounts in foreign currencies and ARS/PES (Argentine Peso) are expected when comparing the AEI document with the FI accounting document, and there is not legal problem with this minor differences.

C2 - Credit or debit documents rejected: The user cannot send to AFIP the credit or debit documents using AEI Monitor J1AMONITOR because the VAT amount and net amount are different. You may face these rejections 'The total document amount calculated in request XML is [amount]' and 'Actual document amount as per the system is [amount]. Please check the document to avoid this rounding error'. Check if the SAP Notes 1791284, 1923806, 1962849, 1973748, 2087624, 2133442, 2013309, 2162840, 2224511, 2262013, 2271301 and 2301183 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C3 - Rejection 'Error while checking the integrated data': You also may face the rejections 'The total document amount calculated in request XML is [amount]', 'Error al verificar los datos integrados', 'Importe documento real por sistema es [amount]. Verifique documento para evitar error de redondeo', 'Importe documento total calculado en XML solicitud es [amount]', 'Actual document amount as per the system is [amount]. Please check the document to avoid this rounding error' and 'Error while validating the built data'. Check if the SAP Notes 2148108, 2148108, 2052200, 2162840, 2271301, 2301183,2204138, 2106912, 2330298 and 2335924 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C4 - Rejection 'Item discount amount should be less than or equal to (item unit price * selling quantity)': The rejection is shown in the AEI Monitor J1AMONITOR, because the discount amount is greater than the item amount. Check if the SAP Notes 2087624, 2133442, 2159044, 2210522, 2301183 and 2350439 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C5 - Rejections Code 110 and Code 116: You also may face the rejections 'El Importe Gravado debe ser igual (dentro del margen de error permitido) a la sumatoria de importes de los ítems menos la sumato' and 'El Importe Total debe ser igual a la sumatoria de Importes de Items y el Importe de Otros Tributos'. Check if the SAP Notes 2351937, 1762239, 1783981, 1788373, 1803831, 1812045, 1875999, 1970852,1973608, 1988020, 1997703, 2025304 and 2052200 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B. Also, in case of Cash Discount scenario, do not generate the FI accounting document via FB70. The supported scenario advises to create credit memos at the collection moment via F-28.

C6 - Documents with non local currency rejected: Check if the SAP Note 1962849 is already implemented in your system. In case this SAP Note is already applied in your system, review the list of the topic B.

C7 - Rejection 'Code 102. El número de comprobante informado debe ser mayor en 1 al último informado para igual punto de venta y tipo de comprobante': In the AEI Monitor J1AMONITOR use the functionality Get Last ODN. The functionality Get Last ODN searches for the entries in the table J_1ACAE which has the field RFC_SENT_LOCK set as X and the field CAE_STATUS as I (Send to AFIP). In case you face issues with the Get Last ODN, check if the SAP Notes 1537823, 1842867, 1973608, 1953825, 1959998 and 2100148 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C8 - Rejection 'Issuing date should not exceed 5 days to the posting date': Since the day was already exceed the maximum of five days to the posting date, the rejection occurs. This is the system standard behavior and it is according to AFIP requirements.

C9 - Rejection 'Payment reference of document is not approved': Also, the errors 'The respective payment reference is not present in J_1ACAE' and 'Error while checking the integrated data'. User is sending a document to AFIP and you receive this rejection when it has the same document of reference in different exercises (fiscal year). Check if the SAP Note 2262013 is already implemented in your system. In case this SAP Notes are already applied in your system, review the list of the topic B.

C10 - Rejection 'The official document type is not defined as from AFIP': In order to correct this issue, check if the SAP Note 2153090 is already implemented in your system. Read the content of the SAP Note in order to confirm if there are prerequisites and manual steps. In case this SAP Note is already applied in your system, review the list of the topic B.

C11 - AEI RG2904 solution in S/4HANA: The Argentina's Electronic Invoice solution is supported in SAP S/4HANA On Premise 1511. For more details, check the links below:

Feature Scope Description of SAP S/4HANA: https://goo.gl/ohGq6RLocalization Best Practices SAP S/4HANA: https://goo.gl/0n0wMRSAP Help of Localization Argentina: https://goo.gl/jn5Swm

C12 - Intercompany scenario: You se standard SD customizing with intercompany invoices. The FI accounting document is default determined by the solution, but the AEI document does not appear in the AEI Monitor J1AMONITOR. The intercompany scenarios are out of the scope of Localization Argentina. If you want this functionality, you can submit the idea to ASUG Argentina, that is the channel to request such kind of change, or check it with Custom Development Team.

C13 - Law 'Liquidación de Tabaco Verde' in AEI RG2904 solution: This AFIP legal requirement is valid for tobacco providers companies in Argentina. This requisite is not be covered by Localization Argentina as it is an industry specific legislation and it is not in the scope of Argentina's Electronic Invoice solution. Submit the idea to ASUG Argentina, that is the channel to request such kind of change, or check it with Custom Development Team.

C14 - Unable to reverse a FI accounting document: There can be multiple FI accounting documents with the same document number, but belonging to different fiscal years. When the user tries to reverse the latest document which is not yet approved, the user receives an error 'Documents with CAE number cannot be modified' J_1A_WS_CAE008 from function J_1A_WS_POST_BTE_UPDATE_1030. Check if the SAP Notes 1802117, 1855435 and 1949572 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C15 - Rejection 'Se rechaza documento; ver mensajes de error a continuación': Also, the error 'Cód. 520 Descripción Ítem 4: Si informa el Código de Producto/Servicio deberá también informar las Unidades de Referencia'. Check if the SAP Notes 1945190, 1980160 and 2262013 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C16 - Rejection 'Cód. 514 Descripción Ítem 1: El Importe IVA del ítem no debe informarse para Tipos de Comprobante B (6, 7 u 8)': About the tag <importIVA>, there is a specific customization given in PI. If the value of VAT/IVA is zero, then it will not send any value in this tag. Check the customization in your PI system. If the VAT/IVA condition is 05, the amount will not be filled in the tag <import IVA>, due to data type initial value, zero is sent to PI system. In PI system, we have customization in these cases. Based on this scenario, we have given the PI customization not to inform the VAT/IVA amount to AFIP. Review the PI documentation of the SAP Note 1537823.

C17 - Rejection 'Communication failure while calling BAPI': Also the error 'System failure' and 'Call to messaging system failed'. Check if the SAP Notes 1630478, 1647385, 1949572, 1973608 and 2250734are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C18 - Message 'Last ODN approved by AFIP is not the same with table J_1ACAE. Do you wish to update ODN in table J1ACAE?': Also the other messages 'Último ODN aprobado por AFIP no es coherente con la referencia en la tabla J_1ACAE. Desea actualizar ODN en tabla J_1ACAE?', 'No hay doc.disponibles p.actualiz.números ODN'. In order to correct the situation, check if the SAP Notes 1819381,1953825 and 2037083 are already implemented in your system. In case these SAP Notes are already applied in your system, review the list of the topic B.

C19 - Rejections 'Could not determine quantity', 'Could not determine item text', 'Could not determine reference 3' and 'Error while checking the integrated data': To resolve these errors, use the BADI BADI_AEI_WS_DOC_CHANGE that is provided initially via SAP Note 1537823. Check the attachments ERP_BEFORE_CODE(600_OR_ABOVE).ZIP > 2_MANUAL_ACTIVITY_BEFORE_CODE.DOCX and review the Section 3 in the page 19. Implement the BADI BADI_AEI_WS_DOC_CHANGE with a Z implementation and write the custom logic in the Z implementation to fill the following values for each line item of the invoice (Quantity, Material and Material Description). Also, review all the instructions informed in the pages 11 to 18 of the attachment SETUP_AEI_WS_DOMESTIC.ZIP from that SAP Note.

D - PI system with AEI solution

D1 - Customizing details:

In case you face issues with PI system and AFIP, we suggest you to check the instructions of SAP Notes 1630478, 1647385, 2000581 and 2335190, and the attachments related to PI customizing from SAP Note 1537823. These contents introduce the technical flow involving this mapping. It makes easier to understand the checkpoints that are proposed afterwards. Also, in the ERP, go to AEI Monitor J1AMONITOR with any Company Code and then execute. In the next screen, select one document and click in 'Check RFC Connection'. This calls BAPI_AR_WS_CONN_TEST, which communicates with PI through a RFC sender channel. In PI, the Mapping MM_Request_FEDummy is initiated. In this mapping, BAPI_AR_WS_LOOKUP_TOKEN_SIGN is called by communication channel CC_Rcvr_RFC_Lookup_TokenSign.

This BAPI uses the value of the following three variants CUIT_COMP_CODE, WS_SERVICE and GEN_TIME to see if there is an already valid token and sign in ERP. Notice that Token and Sign given by AFIP webService(WSAA) has a validity of 12 hours. Once there is one, it is saved in table J_1A_WS_TKN_SIGN during those 12 hours. PI uses the same token and sign without the need to consult WSAA. When there is no valid token and sign (because 12 hours expired or because table is empty), BAPI returns an N as answer to PI, like the following below. When it happens, PI calls WSAA to get a token and sign through a SOAP receiver channel CC_Rcvr_SOAP_WSAA. Once it gets them, it saves them in the ERP, using the same BAPI.

<?xml version="1.0" encoding="UTF-8"?>
<rfc:BAPI_AR_WS_LOOKUP_TOKEN_SIGN.Response
xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<RETURN>N </RETURN><RET_SIGN></RET_SIGN><RET_TOKEN></RET_TOKEN>
</rfc:BAPI_AR_WS_LOOKUP_TOKEN_SIGN.Response>

Check the following points to narrow down the problem:

D1.1 - Keystore entries for each Company Code are entered exactly the same between the NWA keystore view and FixValues in the mapping.

D1.2 - Certificate chain for WSAA are not expired, and imported into the TrustedCAs in a completely right order. Refer to the following question in the attachment PI_FAQ.ZIP in SAP Note 1537823.

D1.3 - Application user (default as PIAFUSER) is assigned with role SAP_XI_ADMINISTRATOR_J2EE, which makes sure the accessibility to the keystore views. A useful try may be to move the Certificate entries to TrustedCAs, and also replace the Constant for keystore view with TrustedCAs in the mapping.

D1.4 - If problem still occurs, try to collect the inspector trace on receiver channel CC_Rcvr_SOAP_WSAA according to SAP Note 1514898.

D2 - AFIP certificate renewal:

In order to renew the certificates from AFIP, access your PI system, go to transaction SXMB_IFR in the ABAP Stack of the PI and navigate to the ESR tools. Then logon to 'Netweaver Administrator (NWA)', navigate to Configuration Management > Certificates and Keys. In this screen you should use the Import button.

D3 - Error 'Could not parse XMBMessage':

The following error is shown in the AEI Monitor J1AMONITOR 'Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System. Error The message status was set to FAIL'. Go to the transaction SXMB_ADM > Integrationn Engine Configuration and check if your server is configured as hub with the same URL or not. More details in the following link: https://scn.sap.com/thread/1353221

D4 - Problem 'Error while getting token and sign from WSAA':

This situation happens in PI system and it generates issues in the statuses of AEI documents in AEI Monitor J1AMONITOR. In case you have your AFIP certificates in the Key Storage View 'WSAA_Certificates', move these certificates to the 'TrustedCAs' store and retest your scenario.

F - Previous AEI solution

Argentina's AEI J1ACAE solution (also known as Facturador Plus) is not supported and enhanced since 2012 and no legal updates are developed anymore for it. This solution is outdated and it was replaced by AFIP's RG2485, RG2904 and RG2758 laws. Review the main SAP Notes 1659814, 1558532 and 1537823. The new solutions bring process automation to make the invoicing faster and precise. SAP recommendation is to migrate to the new solutions. New legal changes and requirements will be updated only in the new solutions of AEI (RG2485, RG2904 and RG2758). If you need help with the previous AEI J1ACAE solution, request a consulting service.

Read more...

Keywords

J_1A_WS_DOMESTIC, EXCHANGE_RATE, VBRK, BL001, BKPF-XMWST, BKPF, XMWST, RG2904, RG 2904, 2904, Argentina, FOREIGN_TO_LOCAL_CURR_AMT, field, sucursal, sociedade, J1ACAE, J1_ACAE, J1A_CAE, REBZJ, BSEG-ZTERM, BSEG, ZTERM, SOAP Foult, SOAP, Foult, J_1A_WS_AEI_BILLING_CHECK, Function BAPI_AR_WS_CONN_TEST not found, fm BAPI_AR_WS_CONN_TEST not found, domestic, domestico, pesos, pessos, ars, pes, factura, factura electronica, eletronica, eletrónica, electronic, eletronic, cliente eventual, argent, argentine, argentinean, J_1A_WS_BRANCH_DETERMINATION, law, laws, requisite, requisites, J_1A_WS_AEI_UPDATE_TASK, aduana, J_1A_WS_BUILD_BILLING_DATA, 8A137, F-22, J_1A_WS_CAE001, Tierra del Fuego, Land of Fire, S4HANA, SAP/4HANA, on-premisse, on premise, Administración Federal de Ingresos Públicos, RECE, faturador,  xmlToString, jar, wsaaClass, LJ1AETOP, J_1A_WS_MONITOR_FORMROUTINE, J1AWS_BG, J1AWS_ARCH, J1AWS_APP, J1AWS_PRES, J_1A_WS_MONITOR, J_1A_WS_REMOTE_CALL, token & Sign, token and sign, Argentinean, Argentinian, J_1A_WS_EXPORT_MONITOR_FORM, RV_INVOICE_DOCUMENT_ADD, J_1A_WS_EXP_REMOTE_CALL, J_1A_WS_EXPORT_MONITOR_LOG, J_1A_WS_EXPORT_MONITOR_MOD_PAI, BADI_SD_BILLING_ITEM AEI_WS_BILLING_CHK, BADI_SD_BILLING, AEI_WS_BILLING_CHECK, INVOICE_DOCUMENT_CHECK, VBRK_VBRP_DATA_TRANSFER, J_1A_WS_POST_BTE_CHEC_1025, J_1A_WS_POST_BTE_UPDATE_1030, SAPLJ1AE, J_1ACON, J_1ACONT, J_1A_AFIP, J_1A_ARCH, J_1BBRANCV, J_1A_ODN, J_1A_WS_BUILD_CASH_DISC_DATA, J_1A_WS_UPD_CASH_DISC, J_1A_WS_REJ, J_1A_RFC_DEST, J_1A_WS_TKN_SIGN,  J_1A_WS_BRANCH, J_1ASNR, J_1A_CURCODE, J_1A_UOMCODE, BAPI_AR_WS_LOOKUP_TOKEN_SIGN, KTOSL, J_1AUOMCODE, TRIBUTOS, ALICIVA, IMPORTEOTROSTRIBUTOS, DATA_RETRIEVAL_SD, DATA_RETRIEVAL_FI, DATA_RETRIVAL_FI, TOT_DOC_AMOUNT, TOT_TAX_AMOUNT, STCD1, SETTLEMENT, REBATE AGREEMENT, KOAID, UNIT_PRICE, WA_J_1A_WS_DOMESTIC-CUST_CUIT, DATA_RETRIEVAL_SD, LT_KONV, WA_ITEM_AMT-DISCOUNT_AMOUNT, GET_ITEM_DETAILS, J_1A_WS_CAE008, J_1A_WS_CAE 008, PERMISO, EXISTENTE, PERMISO_EXISTENTE, rg 2904 LJ1AEF02. , KBA , XX-CSC-AR-LO , Logistics

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required). 

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.

Fonte: https://apps.support.sap.com/sap/support/knowledge/preview/en/2370724