VF01 - Não é possível gravar nota fiscal.

[Former Member]

Bom dia Pessoal,

Após a configuração de um cenários de vendas. Os documentos de faturamentos passaram a não gravar mais.

Já desfizemos todas as configurações no customizing.

A mensagem que aparece:

SAPSQL_ARRAY_INSERT_DUPREC

PROGRAMA CL_J_1BEFD=======CP, Include CL_J_1BEFD======CU: Erro sintaxe linha 33.

Implementation missing for method 'CONSTRUCTOR'...

Prog. J_1BEFD_MAIN: erro sintaxe linha 000135

INCLUDE report 'J_1BEFD_BLOCK_0_AUX' not found.

Nós de SD não conseguimos descobrir onde pode ser, recentemente aplicamos as notas do EFD. Mas porque as notas de EFD influenciariam na VF01?

Toda ajuda é bem vinda, estamos sem os ambientes de homologação.

[Former Member]

Bom dia Fernando e Henrique.

Fico feliz em dizer que a aplicação das 5 notas acima mencionada resolveram meu problema.

Obrigado por todo o suporte que me foi dado.

Uma boa semana a todos.

[henrique_pinto]

Aparentemente as notas nao foram completamente aplicadas (talvez falte passo manual?).

A dependencia eu chutaria que deve ser em algum tipo de tratamento que foi inserido para que o doc faturamento esteja "SPED ready".

Abs,

Henrique.

[Former Member]

Tem algum modo de verificar se foi uma configuração manual, ou uma inserção ABAP que está interferindo no programa.

Pelo que eu pude ver esses programas são todos do EFD/PIS..COFINS, mas não consigo afirmar.

Basis fez tudo o que pode, mas também em vão. Acho que vou precisar chamar um ABAP para ver se descobre algo. O que você acha?

[henrique_pinto]

No caso, ele está reclamando que o include J_1BEFD_BLOCK_0_AUX não existe.

Você pode buscar por objetos no http://service.sap.com/notes.

Jogando o nome desse include no campo de search desse site, ele aponta pra 2 notas:

1295626

1443881

Analisando as notas, a primeira delas é a que cria o objeto.

Peça pra um ABAP revisar os passos manuais de implementacao dessa nota, alem de todas as outras notas de SPED que foram aplicadas. Se vc aplica SNOTE sem fazer os passos manuais de uma nota, está fadado a ter problemas de sintaxe como esse.

Abs,

Henrique.

[former_member182114]

Bom dia Jefferson,

Você está tendo um dump na VF01?

E este dump é no programa J_1BEFD_MAIN?

Até onde sei estes programas não são ligados.

O J_1BEFD_MAIN é o report de extração do sped fiscal (EFD) executado mensalmente.

Verifique se o dump que encontrou é disparado SEMPRE que roda a VF01.

Veja no dump o call stack, pilha dos programas que foram chamados anteriormente ao ponto dump.

Atenciosamente, Fernando Da Ró

[Former Member]

Boa tarde,

Henrique Agradeço a sua ajuda.

Fernando,

Alguma nota ou outra customização feita, está dando o seguinte problema.

Name of runtime error SAPSQL_ARRAY_INSERT_DUPREC

Exception CX_SY_OPEN_SQL_DB

e junto com ele o erro comentado no inicio deste Thread.

Mas já vi que são coisas separadas, como em SD desfizemos todas as configuração, e transportamos a resquest sobreescrevendo as antigas.

Mesmo assim nosso erros continuavam.

Bom estou tratando somente do erro no

analisando pela SM13

Chave AT 6D3E8DE094DEF1F783B600221988CB28

Mandante 300

Usuário 983

Data 02.06.2011 Hora 14:33:59

Idioma PT

Conta

Report SAPLV60A

Transação VF01

Chv.enfil. 20110602143330190000010100SRVSAPQADEV.....................

Contexto :P:

Info (50) = VB_WITH_ENQUEUE, VB_ENQUEUES_RELEASED,

Rc-AT 9

Status Atualização cancelada

Serv.AT SRVSAPQADEV_DEV_00

ClntAtlz. SRVSAPQADEV_DEV_00

FusoHorár.local BRAZIL

Time-Offset 1

Info erro Classe: 00 Nº: 671

Processador ABAP: SAPSQL_ARRAY_INSERT_DUPREC

Report LV60UF0V Linha 505

No dump aparece o seguinte.

Análise do erro

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "VBUK_BEARBEITEN" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)

Análise do erro

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "VBUK_BEARBEITEN" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)

Notas p/eliminação de erros

Use an ABAP/4 Open SQL array insert only if you are sure that none of

the records passed already exists in the database.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"

"SAPLV60U" or "LV60UF0V"

"VBUK_BEARBEITEN"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"VBUK_BEARBEITEN" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Linha Txt.fonte

475 stru LIKE vbuk,

476 END OF da_xvbuki.

477 DATA: BEGIN OF da_xvbuku OCCURS 20,

478 stru LIKE vbuk,

479 END OF da_xvbuku.

480 * Positionen anlegen oder ändern

481 LOOP AT xvbuk.

482 vbuk = xvbuk.

483 CASE xvbuk-updkz.

484 WHEN updkz_new.

485 beleg = vbuk-vbeln.

486 * CHECK: BELEG-NR NE 0.

487 IF beleg-id = '$'.

488 CHECK: beleg-nr NE 0.

489 PERFORM vbrk_belegnummer_ermitteln.

490 vbuk-vbeln = xvbrk-vbeln.

491 xvbuk-vbeln = xvbrk-vbeln.

492 MODIFY xvbuk.

493 ENDIF.

494 da_xvbuki = xvbuk.

495 APPEND da_xvbuki.

496 WHEN updkz_update.

497 da_xvbuku = xvbuk.

498 APPEND da_xvbuku.

499 ENDCASE.

500 ENDLOOP.

501 UPDATE vbuk FROM TABLE da_xvbuku.

502 IF sy-subrc > 0.

503 MESSAGE a101 WITH 'VBUK' sy-subrc da_xvbuku-stru-vbeln.

504 ENDIF.

>>>>> INSERT vbuk FROM TABLE da_xvbuki.

506 IF sy-subrc > 0.

507 MESSAGE a100 WITH 'VBUK' sy-subrc da_xvbuki-stru-vbeln.

508 ENDIF.

509

510 ENDFORM. "VBUK_BEARBEITEN

511 *eject

512

513 *----

---

*

514 * FORM VBUP_BEARBEITEN *

515 *----

---

*

516 * Die Tabelle VBUP wird geaendert *

517 *----

---

*

518 FORM vbup_bearbeiten.

519

520 xvbrk_tabix = 0.

521 DATA: BEGIN OF da_xvbupi OCCURS 1,

522 stru LIKE vbup,

523 END OF da_xvbupi.

524 DATA: BEGIN OF da_xvbupu OCCURS 100,

Já achei 5 notas em um outro post que o você ajudou a resolver com este mesmo problema, estou aplicando as notas para ver se dará certo são elas:

1430774 NF Writer:one-time data updated in header and partner tables

1429335 NF BAPI: update to store partners address in NF database

1422287 MR8M: 8B 109 Type of partner not found with doc type 4 or 7

1417805 Nota Fiscal: partner information records NFe only

1391905 MR8M: Partner type not found

Estou com os dedos Cruzados para darem certo.

Post a resposta em seguida.

att

[Former Member]

Desculpem a mensagem acima ficou muito grande,

vou dividi-la para ficar melhor visualizado.

Boa tarde,

Henrique Agradeço a sua ajuda.

Fernando,

Alguma nota ou outra customização feita, está dando o seguinte problema.

Name of runtime error SAPSQL_ARRAY_INSERT_DUPREC

Exception CX_SY_OPEN_SQL_DB

e junto com ele o erro comentado no inicio deste Thread.

Mas já vi que são coisas separadas, como em SD desfizemos todas as configuração, e transportamos a resquest sobreescrevendo as antigas.

Mesmo assim nosso erros continuavam.

Bom estou tratando somente do erro no

analisando pela SM13

Chave AT 6D3E8DE094DEF1F783B600221988CB28

Mandante 300

Usuário 983

Data 02.06.2011 Hora 14:33:59

Idioma PT

Conta

Report SAPLV60A

Transação VF01

Chv.enfil. 20110602143330190000010100SRVSAPQADEV.....................

Contexto :P:

Info (50) = VB_WITH_ENQUEUE, VB_ENQUEUES_RELEASED,

Rc-AT 9

Status Atualização cancelada

Serv.AT SRVSAPQADEV_DEV_00

ClntAtlz. SRVSAPQADEV_DEV_00

FusoHorár.local BRAZIL

Time-Offset 1

Info erro Classe: 00 Nº: 671

Processador ABAP: SAPSQL_ARRAY_INSERT_DUPREC

Report LV60UF0V Linha 505

[Former Member]

no Dump está assim.

No dump aparece o seguinte.

Análise do erro

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "VBUK_BEARBEITEN" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)

Análise do erro

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "VBUK_BEARBEITEN" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)

Notas p/eliminação de erros

Use an ABAP/4 Open SQL array insert only if you are sure that none of

the records passed already exists in the database.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"

"SAPLV60U" or "LV60UF0V"

"VBUK_BEARBEITEN"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"VBUK_BEARBEITEN" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

[Former Member]

Já achei 5 notas em um outro post que o você ajudou a resolver com este mesmo problema, estou aplicando as notas para ver se dará certo são elas:

1430774 NF Writer:one-time data updated in header and partner tables

1429335 NF BAPI: update to store partners address in NF database

1422287 MR8M: 8B 109 Type of partner not found with doc type 4 or 7

1417805 Nota Fiscal: partner information records NFe only

1391905 MR8M: Partner type not found

Estou com os dedos Cruzados para darem certo.

Post a resposta em seguida.

att

[Former Member]

Boa tarde,

infelizmente após a aplicação das notas, continuamos com o mesmo problema.

Abrimos um chamado na SAP para tentar solucionar nosso problema. Se alguém tiver mais sugestões será bem vinda.

att

Jefferson Souza