Erro durante aplicação da Nota 1933895

[Former Member]

Bom dia a todos,

Estamos finalizando a aplicação da nota 1933895 e todas as suas dependências em um cliente com ECC 6.0 EhP5 SP06! Peripécias à parte no volume de notas aplicadas (já ultrapassam 200), finalmente chegamos no pote de ouro no fim do arco-íris: a SAP Note 1933895. Seguimos os passos informados na Nota, importamos o arquivo SAR listado na SAP Note 1976416, e iniciamos as correções solicitadas no arquivo Pre_ChangedObjects_ImpSteps1933985.pdf. No item 2.3.3 deste manual, temos a alteração da tabela J_1BNFIMPORT_DI:

2.3.3 J_1BNFIMPORT_DI

- Execute transaction SE11;

- Select "Database table" radio button;

- Enter " J_1BNFIMPORT_DI" in the proper field;

- Choose "Change" pushbutton;

- Select “Fields” tab;

- Enter the following fields in the end of the list:

Field	Data Element
TRANSPORT_MODE	J_1BNFE_IMP_TRANSPORT_MODE
MARITIME_FREIGHT	J_1BNFE_IMP_MARITIME_FREIGHT
INTERMEDIATE_MODE	J_1BNFE_IMP_INTERMEDIATE_MODE
CNPJ	J_1BNFE_IMP_CNPJ
REGIO	J_1BNFE_IMP_REGION

- Save and activate the changes.

O problema é que no nosso sistema, o tamanho máximo para o nome de um campo é 16 caracteres, e "INTERMEDIATE_MODE" possui 17 caracteres. Assim, quando incluímos o campo, o nome do mesmo fica "INTERMEDIATE_MOD", e não conseguimos passar deste ponto na aplicação da Nota. Nos campos das estruturas anteriores, J_1BDYIMPORT_DI e BAPI_J_1BNFIMPORT_DI, o nome pôde ser informado sem nenhum problema.

Já estamos abrindo chamado na SAP, porém sabemos que a resposta não será rápida, e precisamos finalizar a aplicação desta nota para poder liberar o ambiente para um teste regional (LatAm).

Alguém mais teve este problema, ou sabe a solução para o mesmo?

Obrigado a todos!

[Former Member · Accepted solution]

Boa tarde a todos,

Apenas uma informação: a Nota SAP correta é a 1933985. Efeitos de ter aplicado mais de 200 Notas no sistema.

At.

Andre Monteiro

[Former Member · Accepted solution]

Olá Andre,

Estamos com o mesmo problema em nossa implementação e acabamos de abrir chamado na SAP. Você conseguiu resolver o problema e terminar de aplicar a nota?

Grata,

Lucimara

[Former Member · Accepted solution]

Olá, Lucimara,

Tivemos um retorno da SAP, que copio abaixo para te orientar e aos demais que tiverem o mesmo problema.

Thank you for contacting SAP Active Global Support. Please note that now it is possible to create fields up to 30 bytes lenght. You can check SAP Note 1680583. Also, all this info is described on the following link:

http://scn.sap.com/community/abap/blog/2013/11/02/data-dictionary-supports-field-s-name-up-to-30-byt...

Let me know if you have any further question or if you still have issues with that.

Aplicamos a nota informada, e conseguimos completar a aplicação da nota 1933985.

At.

[deborauchoa]

Bom dia Pessoal,

Estamos realizando a aplicação da nota 1933985 e o SAP nos mostrou alguns erros. Os pré requisitos foram aplicados corretamente, alguém tem alguma pista ou já viu isso?

Muito obrigado

Att

[Renan_Correa]

Oi Débora,

     Bad News! Faltam pré-requisitos ou passos manuais. A dica mais válida é procurar pelo nome do objeto faltante ( no caso de campos desconhecidos ) no service marketplace e identificar qual a nota que cria ele, depois determinar se a nota foi aplicada e se os passos manuais foram corretamente executados.

att,

Renan

[RJSA]

Débora, boa tarde!

Passei pelos mesmos problemas que você está relatando. O que ocorre é que a SAP liberou a informação dos pré-requisitos da nota 1933895 dentro das notas guidelines da 310, ou seja, não estão listados dentro da nota principal 1933895.

Por exemplo, a nota que cria a estrutura J_1BNFE_ORGDATA e a estrutura J_1BNFE_ORGDATA_TAB é a nota 1547262 - NF-e Incoming Automation: Pre-requisites in ERP.

Veja as notas Guide:

2057942 - [3.10] Guideline for NF-e layout 3.10 implementation in ERP and SAP NFE

2056762 - [3.10] Guidelines for NF-e layout 3.10 SAP Notes installation

Abraços,

Rafael Sá

[deborauchoa]

Rafael,

Verifiquei a nota 1547262, porém essa nota é de Incoming Automation. Não temos essa solução implementada aqui no cliente. Se eu aplicar essa nota o snote vai exigir todos os pré requisitos do incoming automation e o cliente não tem interesse nesse processo no momento. Existe uma forma de contingência pra correção desse erro?

Obrigada pela resposta.

Att

Débora.

[Former Member]

Débora, boa tarde,

Aqui no cliente, tivemos que aplicar todas as notas que eram pré-requisitos, mesmo não tendo aqui automação de entrada. Não havia outra alternativa. Aplicamos notas de automação, CT-e (outro cenário que não é usado) e inclusive notas de MIRO, Pedido, J1BTAX, etc.

O cliente aqui tem ECC 6.00, EhP5 SP06, e aplicamos as seguintes notas como pré-requisitos da 1933985 (posteriormente, durante o projeto, aplicamos mais correções):

1514723 - NF-e: Conversion routine for field NCM - missing for XML 2.0

1555267 - MIRO/MIR4: Runtime error SAPSQL_ARRAY_INSERT_DUPREC

1568361 - NF-e incoming - Subcontracting

1573580 - NF-e: Automation of incoming NF-e special scenarios

1574311 - MIRO: wrong distribution for multi account assignment POs

1590506 - CPE: Problems when processing invoices

1596057 - MIRO: Balance is not updated

1610354 - NF-e: Request cancellation/skipping automatically

1612648 - NF-e: Iss. Type, Proc. Date and Time not copied (STO)

1615299 - RTP & Subcontracting component shipment

1616520 - NF-e Prerequ. for Future delivery in incoming automation II

1616521 - NF-e incoming - Returnable Packaging Goods Receipt

1616778 - NF-e: NT2011/004 Import Tax included in NF Totals

1623340 - NF-e: After re-sending an NF-e entrada, other base is zero

1623794 - BAPI: Invoice for canceled service entry sheet

1623830 - SOA downport I: New IVTYP and encapsulation of EDI logic

1625819 - NF-e: Field <IEST> is not filled with correct partner

1626304 - NF-e Incoming Automation: Returnable packaging process

1628192 - NF-e incoming - prerequisites

1628621 - NF-e: Enhancements for NF-e Incoming

1630899 - NF-e prerequisites for future delivery invoice III

1631695 - NF-e Currency conversion of additional costs

1632930 - Check of taxgroups with zero taxamount

1635729 - NF-e Incoming future delivery wrong conversion at validate

1636750 - Maintenance of incoming automation process attributes

1637762 - Prerequisites for future delivery invoice IV

1638531 - Difference in PIS- and COFINS-taxes

1639222 - NF-e incoming - prerequisites

1640055 - NF-e: 'Cancel Source Doc.' fails when NF-e not numbered

1640258 - MIRO: ABAP runtime error DYNPRO_FIELD_CONVERSION

1640464 - Corrections of PO Search for Subcontracting

1641790 - The system does not save changes to CPE formulas

1641823 - NF-e incoming: Future Delivery and RTP corrections

1642097 - Syntax error in individual include files

1642423 - IPI base not correct by factor 100

1643930 - Wrong PIS and COFINS base for resale returns scenario

1645822 - NF-e: Creation of In. Deliv. fails when BAdI not implemented

1645907 - VF04: performance enhancement

1648937 - MIR4: Error message F5 165

1649321 - Fiscal Workplace: Moving average price negative

1651021 - Wrong tax calculation with PIS and COFINS pauta

1652103 - Batch Split in Inbound Delivery

1653000 - NF-e incoming - automation of special scenarios (II)

1653567 - NF-e: Cancel synch. of skipped NF-e posted in contingency

1653630 - NF-e Batch Split in Inbound Delivery prerequisite part

1654179 - NF-e incoming - Subcontracting corrections

1654777 - BR: Data Upload from MS Excel for NF Writer

1655561 - NF-e: Incoming error during simualtion

1655760 - MIR4: Error message M8_2 205

1660188 - MIRO:Termination message M8424 for multiple account assgmt

1660436 - MIRO: Pricing for CPE conditions

1661701 - MIRO: Security retention is not adjusted

1661957 - MIRO ends in system error/incorrect call

1663592 - NF-e incoming - Consignment Invoice

1663667 - NF-e incoming - Future Delivery and RTP corrections

1665479 - MIR4: No price determination during direct posting

1667732 - Maintain tax rates with 4 decimals for SPED (Pauta Unit)

1671302 - Fill XML field IEST only if tax situation 10,30,60,70,or 90

1673222 - Maintain PIS and COFINS tax rates with 4 dec. more robust

1673991 - NF-e incoming - prerequisites

1674815 - Pauta Rate and Subtrib Base Reduction despite not active tax

1674817 - NF: Unit and Number of Units is empty for Pauta Conditions

1678446 - MIRO: Invoice is incorrectly locked

1678676 - 4-dec Phase 1 (4): 4DEC-Unit of measure is copied

1679459 - Errors in Condition Migration

1681509 - Error CPE 304 despite successfully evaluated formula

1683506 - NF-e: Mandatory field check doesn't work for random number

1683835 - PIS/COF Rates w/ 4 Dec. Places in MM/SD: Prerequisites

1685187 - OT partner: Missing NF-e region for OT account partners

1690193 - NF-e Check routine for batch-input and background simulation

1690348 - STO: OT partner address from delivery not transferred to NF

1698528 - FSTST_ACCESS_CHECK: Table without validity period-short dump

1699985 - PIS/COF Rates w/ 4 Dec. Places in MM/SD: Classical Tax Calc.

1699986 - PIS/COF Rates w/ 4 Dec. Places in MM/SD: Customizing Views

1700574 - MIRO: You cannot complete condition changes

1703810 - CT-e Legal Change: Extension of Features

1704412 - CT-e: follow up changes provided by the note 1661137

1704465 - NFe Dump CALL_FUNCTION_NOT_FOUND when posting goods movement

1704822 - Documento Auxiliar do Conhecimento de Transporte Eletrônico

1705016 - NF-e: Cancel of Stock Transport with ext. delivery no. fails

1705322 - BR: Wrong UoM when uploading data from MS Excel

1708107 - CT-e Legal Change: Total Values and Ship To Jur. Code

1710983 - NF-e: Purchase Order Number and Item not filled in XML

1711453 - Posting PIS and COFINS with incoming automation

1713435 - PIS/COF Rates w/ 4 Dec. Places in MM/SD: NF Writer & XML Map

1713458 - PIS/COF Rates w/ 4 Dec. Places in MM/SD: Cond. Based Taxes

1714116 - PIS/COF Rates w/ 4 Dec. Places in MM/SD: 4DEC Reports

1714749 - CT-e LC: Extension of Tax Calculation Features

1715926 - NF-e: Update SD/FI with NF-e number in J_1B_NFE_SET_NUMBER

1716892 - Rounding difference in ICMS tax baseamount

1717837 - Flexible PIS and COFINS Base for FI/MM Tax Codes

1720361 - PIS pauta rate not taken for TAXBRJ when not 4DEC

1722320 - BR: Upload from MS Excel not possible without material no.

1723841 - Enhance NF-e Monitor with print functionality

1724215 - Wrong tax calculation with PIS and COFINS pauta

1725176 - MIGO: comparison of delivery notes is lead. zeros dependent

1726599 - CFOP field is disabled for NF model 7

1726904 - Field <iest> for ICMS SubTrib is not filled correctly

1731451 - CT-e: Timestamp, Street & House.No. missing when RFC space

1732638 - Sub.Trib. surcharge rate not filled in outgoing XML

1732696 - NF-e incoming: ICOR condition balance error

1735417 - Value Determination correction for CT-e ICMS ST

1737011 - NF-e: Take over price elements from incoming XML

1740282 - Correction flexible PIS/COFINS base for classical tax calc.

1740963 - NF-e: Number Skip Report doesn't update last checked number

1742578 - NF-e incoming prerequisites (Multi accounting)

1743242 - Set Payment flag <ForPag> in XML for CT-E to 'To be Paid'

1743464 - Internal correction of function module design

1744595 - BR: Batch input for tab page 'Import Documents'

1746113 - NF-e: Wrong NF Reference in XML for Return to vendor

1746223 - Flexible PIS/COFINS base - Code Adjustment

1746671 - CT-e: SVC Server Determination

1746690 - NF-e incoming: Subcontracting Components are condensed

1751747 - Subsequent Adjustment for Subcontracting is not working

1754198 - Prereq. Multiple XML-items for the same Purchase Order Item

1755123 - PIS&Cofins Pauta w. 4decimal places - BASERED2 is filled

1755777 - CT-e Legal Change: Jur. Code and Ship-to Determination

1758473 - NF-e: Automatic Creation of NF-e in contingency process

1761307 - BAdI for import Outgoing CT-e Data

1761607 - CT-e: Issuing City Name, City Code, and Region empty

1763565 - CT-e: Enable function cancel prior to authorization

1766209 - CT-e: new CT-e Tax Calculation determination for Incoming

1767815 - NF-e: Auth. to Cancel manually created NF-e in C.P.A. fails

1768622 - Defaults / exception handling for nota fiscal item types

1771066 - CT-e LC: ICMS Exempt and ICMS Other Base

1772654 - Printing Nota Fiscal aborts in Nota Fiscal Writer

1773766 - New BAPI_CTE_J_1B_NF_CREATFROMDATA

1776434 - CT-e: CFOP determination and first digit check

1777253 - Issue in Program J_BNFECALLRFC with NF-e Number in SD/FI

1777925 - Some (ICMS, IPI) tax rates are displayed by a factor of 10

1779115 - Rounding difference in ICMS-/IPI-tax data

1779143 - CT-e: Enable automatic sending of cancellation request

1779216 - NF-e: CT-e reference filled incorrectly into NF-e reference

1779526 - Field <IEST> is empty for ICMS Subtrib due to tax region

1779693 - CT-e: Badi to check active server

1781245 - CT-e: TPAMB not filled

1781257 - <motDesICMS> should be filled only when <vICMS> is not empty

1781930 - NF-e with subseq. document - contingency process not allowed

1782182 - CT-e: CL_TAX_CALC_BR Code Changes

1782267 - CT-e LC: Wrong data in CT-e Tab for annulment documents

1782618 - FSTST_ACCESS_CHECK displays pricing procedure ZBVO;incorrect

1791864 - Error when activating a change with abap_true/false in J1BB

1792089 - Condition Value Formulas 342 and 343 only shipped via SP

1792546 - Check NF-e XML Values vs. NF-e Net Values incl. Tax

1792935 - CT-e: Incoming Complementary ICMS

1798662 - NF-e: Copy Protocol Information only for NF-e without Form

1799591 - NF Writer - Mandatory IPI law for Conhecimento

1799663 - Addition of missing DDIC for CT-e related BAPI

1801131 - Wrong tax law values in a service nota fiscal

1803009 - Renewal of Screen Controls in Nota Fiscal Writer

1809117 - NF-e: Cancellation Event status stuck when timestamp empty

1810694 - NF-e: Cancellation Synchr. fails after Validation Error

1812415 - CT-e switch class improvements

1813441 - NF-e reference is missing in CT-e outbound

1814052 - Table types for CT-e resources

1814431 - NF-e: Cancel material document with serial number

1814483 - No messages when Nota Fiscal is created without taxes

1815707 - MIRO: Wrong tax law values in a nota fiscal

1817072 - Nota Fiscal: Delivery of NBS

1818586 - Pauta Base: DDIC Changes

1818634 - Pauta Base: Condition-Based Tax Calculation

1818637 - Pauta Base: NF Writer, Bapi, XML Mapping

1822661 - OT Partner: Jurisdiction code not considered when issuing PO

1826651 - STO: ICMS wrongly calculated for Full/Partial return from ZF

1831696 - Technical Pre-Requisite for Function Group J1BC

1832764 - NF Writer: Reference document year wrongly assigned

1835980 - Customizable message has incorrect message type

1836258 - NF-e: Search Help for Conting.Reas. not language dependent

1838557 - NF-e Event out: Protocol number not provided

1838582 - Stock Transfer - Missing NFe-Number for inbound delivery

1839027 - Wrong Comp. ICMS base/amount value using PIS/COFINS Pauta

1840188 - NF Writer: structures missing in mandatory field check

1840963 - [Material origin] Fix of issues from note 1816560

1842924 - Nota fiscal header create: Code re-arrangement

1844619 - NF-e: Storing Additional Data - BAdI, derived fields, texts

1844621 - NF-e: Storing Additional Data - Obj.Services & NF Writer

1846669 - ME22N: Wrong ICMS value for material origin using TAXBRJ

1847110 - Techn.Pre-requisites in Nota Fiscal for Further Enhancements

1849186 - Not able to cancel a NFe through nota fiscal monitor

1849741 - Material origin: Enhancements to Sched. Agrm. and Contract

1851184 - BAPI_J_1B_NF_GETDETAIL does not return the data for import

1853104 - NFS-e municipal document, processing date and time

1856625 - Master Data - Screen

1859126 - NF-e: Storing Additional Data - Enhancement of NF Writer

1860360 - NF-e: Storing Additional Data - application generated NFs

1860362 - NF-e: Storing Additional Data - outbound NF-e & Reports

1860433 - NF-e: Storing Additional Data for DANFE & Reporting

1864545 - NF number maintenance in NF Writer

1864860 - System is not validating J_1BAL values when saving MIRO

1865657 - NF-e: Update MM/FI with NF-e number - Credit Memos

1868824 - Change documents for nota fiscal import document information

1869063 - NF-e: send obsCont, obsFisco, procRef to GRC

1870338 - Dump when setting item tax field as mandatory

1872953 - Change documents for new fields/tables in fiscal document

1873005 - Change Documents for CT-e Data in the Financial Document

1873181 - MIRO: Invoice amount with reference to blocked stock items

1873294 - Master Data - DDics

1874485 - Material Origin: STO - Enhancement fo NF-e

1877404 - NF-e: Enhancements NF Writer screen controls

1882947 - NF-e: Storing Additional Data - Corrections for NF Writer

1883364 - NF-e: Enhancement of BAdI for Additional NF Data

1883752 - Fill new master data fields into NF document (CNAE, CRT, ..)

1884155 - NF-e: mapping of new fields overwrites values set in BAdI

1885164 - NF: Renewal of Nota Fiscal consistency checks

1885307 - Prerequisite for note 1883872 Mat. origin with incom. autom.

1885909 - Enhancement NF Writer screen control- Corrections

1889990 - NF-e: Update MM/FI with NF-e number - Credit Memos

1892279 - NF-e: additional fields - corrections for applic.gen. NF-es

1894089 - Pre-Implementation Objects II

1895460 - Material Origin: some scenarios with TAXBRJ and ME22N

1896201 - MIRO: Fixed condition results in incorrect difference amount

1897850 - NFe: add FCI number to NF item (NT 2013/006)

1901342 - Material Origin: STO - Fix changed value after Goods Issue

1903638 - Brazilian fields filled incorrectly in the CBT determination

1904511 - MIRO: Balance divergence after applying SAP Note 1839027

1910518 - BAPI_J_1B_NF_CREATEFROMDATA: Improvement of Message Handling

1914193 - NF-e: add FCI number to BAPI/BADI of Nota Fiscal Item

1920785 - CT-e: Adding Issuer's CNPJ and IE to DACTE (NT 2013.011)

1923423 - Nota Fiscal: only two tax lines are displayed on the tax scr

1933746 - NF-e Total Values of Service and Material

1933985 - NF-e new layout 3.10

1934958 - Material Origin: Correction of note 1875160

1934959 - Material Origin: STO - Performance Improvement

1939148 - NF: Error "Duplicated partner" when Posting Goods Issue

1939893 - Implementation of Nota Fiscal de Ajuste

1951532 - Nota Fiscal: scroll through items not consistent

1958816 - Error CONVT_NO_NUMBER when posting Goods Receipt

1965381 - Contingency: Changes in active server status check fuctional

1970414 - MIRO: Incorrect invoice value via CPE price determination

1977491 - NFe tax rounding issue (IPI and ICMS)

1977764 - NF-e 3.10 Incoming Automation

1980784 - NF-e new layout 3.10 - Enhancement Note 01

1983836 - NF-e new layout 3.10 - Enhancement Note 02

1993209 - IPI Return for the NF-e layout 3.10

1996598 - NF-E: XML tag MODBCST wrongly informed for Sub.Trib.scenario

1997896 - NF Writer: Tab NF-e Data Doc. Status

2000511 - SVC Contingency error J1B_NFE 107.

2004264 - Authorization error related to ICMS ST base total value

2008167 - NF-e 3.10: Mapping Issues

2020500 - NF-e Total Values of Service and Material

2023027 - Wrong region version attribution

2026540 - Message e047 is raised when MarFreight is 0,00.

At.

Andre Monteiro

[RJSA]

Débora, bom dia!

Realmente não existe outra alternativa, inclusive essas notas estão listadas nas notas guide referente ao layout 3.10. Tendo ou não os cenários de Incoming, CT-e, FCI, entre outros, é necessário a aplicação de todas as notas e seus pré requisitos listados no guideline 3.10. Infelizmente.

Abraços,

Rafael Sá

[Former Member]

Boa tarde a todos,

Fiz algumas pesquisas adicionais, porém sem sucesso. Tirando uma alternativa descrita abaixo, não é possível criar campos em tabelas cujo nome tenha mais de 16 caracteres, conforme cita o artigo http://help.sap.com/saphelp_nw70/helpdata/en/cf/21eb6e446011d189700000e8322d00/content.htm:

On the Fields tab page, enter the table fields. Perform the following steps for each table field:

Enter a name for the table field in the column Fields. The field name may only contain letters, digits and underlining, and it must begin with a letter. A field name may not be longer than 16 characters.

A única forma que talvez permita a criação de campos com mais de 16 caracteres é a descrita na SAP Note 660239:

Never use this workaround as the 'default' for 'new entries' to enable long field names in the case of PSA tables. It is only provided so that you can continue to use your existing transfer rules even if the maximum field name length is exceeded. You can also use it to enable long field names for other reasons. In this context, explicit reference is made to the potential conflict described above.

Porém, no ambiente do cliente a implementação desta nota está fora de questão.

O time de Basis do cliente fica na Índia, e estamos passando todas estas informações para a abertura do chamado por parte deles. Se alguém tiver conseguido implementar esta nota com sucesso, gostaria de saber como este passo foi feito.

Muito obrigado!