Error : ACRD 'CNPJ invalido - Entrega'
Ao tentar atualizar o Cadastro do PN o sistema indica um endereço que
não existe com o CNPJ invalido.
Temos algumas validações nas procedure para preenchimento de alguns
campos.
O usuário não esta utilizando Add-On.
Tivemos apenas a reclamação deste registro até o momento.
Qualquer dúvida estou a disposição.
Estamos utlizando validações como por exemplo:
Não permitir inserir o cadastro de PN com os campos em branco:
Tipo de Endereço, Bairro, Cep, CNPJ em branco ou duplicado.
Para este tipo de cadastro não passa por autorizações ou aprovações.
Qualquer dúvida estou a disposição.
Grata,
Vikas
Não entendi bem... Voce esta tendo este erro ou esta explicando este erro?
A Sap não permite que voce preencha dados por procedures no Business One. A tabela ACRD é a tabela de log de Parceiros de Negócios. Este erro geralmente é acompanhado pela perda do Suporte pela SAP...
Similar Messages
-
Como obter o CNPJ do PN se o endereço de entrega padrão é de outra empresa?
Pessoal,
Preciso gerar um relatório com as seguintes informações dos Clientes:
Código, Razão, Endereço (Tipo, Rua/Caixa, Complemento, Bairro, ...), CNPJ e Inscrição Estadual;
Porém verifiquei que as identificações fiscais (CNPJ, IE, ..) que ficam armazenadas na aba Contabil e Fiscal -> aba Imposto do cadastro de PN dependem do Endereço de Entrega Padrão.
Ou seja, se o PN tem como Endereço de Entrega Padrão uma outra empresa ou filial com outro CNPJ e IE, o CNPJ da aba Imposto será o desta empresa cadastrada no enderço de entrega padrão.
Desta forma, como poderei acessar real o CNPJ do PN ?
No aguardo,
Paulo GarciaOi Paulo
Para um relatório envolvendo esse volume de tabelas eu vejo somente 2 opções:
1. Criar uma query que agrege todos esses campos para obter a informação desejada.
2. Na versão já em Ramp-Up SAP Business One 8.8 existe disponível para download o Crystal Reports For SAP Business One e permite mais facilmente a criação de relatórios complexos.
Paulo Calado
SAP Business One Forums Team -
CNPJ obrigatorio na Tag entrega mas o recebedor é pessoa fisica
Bom dia
Estou com algumas notas que estao parando no validador do GRC
Minha nota tem endereço de entrega, entao preencho no XML os dados de entrega.
Mas o endereço de entrega é uma pessoa fisica e o validador esta exigindo CNPJ valido, mas nao tenho CNPJ neste caso.
Minha venda é uma venda feita em site de internet, onde uma pessoa compra (emissor pessoa fisica) e manda entregar na casa de outra pessoa (recebedor - tambem pessoa fisica)
Na TAG de emissor tenho CNPJ ou CPF a serem preenchidos mas na tag de entrega nao tenho campo CPF, so CNPJ e esta obrigatório. Mas o cliente de entrega nao tem CNPJ
Como posso validar esta nota?
Obrigada
Renata HoppBom dia Renata,
Olhei os manuais e pelo atual layout 1.10 é o que você comentou mesmo, só seria possível preencher CNPJ e é obrigatório, porém no esquema XSD ele consta como opcional ?!?!?
Faça um teste, no GRC vá na SM30 visão /xnfe/nfevalid (regras do validador) e procure o registro para o field G_CNPJ então altere os conteúdos abaixo:
Minimum Lenght (MIN_LENGTH) de 14 para 0
Not Init. (NO_INIT_FLD) de X para vazio
Se funcionar, abre um chamado no componente SLL-NFE para modificar no standard.
ATENÇÃO: Esta tabela é mantida pela SAP e atualizada por nota ou sobreescrita nos support packages.
No layout 2.0, disponibilizado em homologação pela Sefaz esta semana e sem previsão oficial da SAP de atendê-lo, este problema foi corrigido, além de existir a tag CPF tem também o CNPJ passa a ser opcional.
Atenciosamente, Fernando Da Ró -
Erro 8B260 (Processo de Entrega Futura)
Bom dia, Pessoal!
Estou com um problema no processo de devolução de entrega futura.
Realizei a entrada da nota de fatura normalmente atraves da MIRO e da nota de remessa atraves da MIGO (mov 801).
O fornecedor nos enviou as notas de Fatura e Remessa como de entrada pois ele ainda não tem a obrigação legal da NFE, porém a empresa aonde estou já está obrigada a utilizar a NFE e ao realizar a devolução o sistema não encontra a referencia da nota de remessa. A mensagem de erro é a 8B 260 (NOTA FISCAL DE REFERÊNCIA XXXXX NÃO FOI ENCONTRADA)
O pedido está somente com a opção de parceiro FO o processo já foi criado sem a opção de parceiro "FM" (Fornecedor da Mercadoria).
As Notas Abaixos já estão aplicadas:
NF:
1055401 Subcontracting Returns doesn't find reference Nota Fiscal
NF-e:
1175538 NF-e Reference between NF and NF-e
1238765 NF-e: Returns for Subcontracting - Error 8B287
1257933 NF-e: Reference NF not found by return for subcontracting
1288925 NF-e: References between NF-e and non NF-e
1356952 NF-e: Returns for Subcontracting - Error 8B260
Estive debugando a função J_1B_NF_DOCUMENT_SELECT_2 e o que pode verificar é que como o processo de fatura/remessa é gerado atraves de uma nota de entrada ele armazena as informações J_1BNFDOC-NFNUM porem ao realizar a devolução, como a empresa que estou é obrigada a emitir a NFE a função realiza a busca no campo J_1BNFDOC-NFENUM com o numero da nota de remessa (NFNUM) por este motivo não é encontrado a nota de referencia e o erro é apresentado.
Eu procurei por alguma nota que pudesse corrigir meu problema porém não encontrei nenhuma aplicavél, alguem tem alguma ideia de como resolver este problema?
Obrigado
GustavoOlá xará,
tudo certo?
Esse erro provavelmente está ocorrendo porque existem múltiplos parceiros atribuídos ao Pedido de Compras.
No procesos de entrega futura, contudo, o sistema comporta somente a utilização de um parceiro, do contrário o processo é interpretado como sendo uma operação triangular.
Abraços -
NF-e Rejeitada com 542 - Rejeição: CNPJ do Transportador inválido.
Olá,
Estamos iniciando a operação com XML versao 2.00. e nos deparamos com um problema de rejeição que na versão 1.10 não acontece
Quando o transportador é Pessoa Jurídica está funcionando.
Porém, quando o transportador é PESSOA FISICA, a NF-e é rejeitada com o motivo 542 - Rejeição: CNPJ do Transportador invalido.
A rejeição está correta, pois no transportador tem um CPF e não um CNPJ.
Fiz um debug no ERP, até o momento que que o perform CALL_XI (function J_1B_NF_MAP_TO_XML) é executado e confirmei que os campos XMLH-T1_CNPJ e XMLH-T1_CPF estão preenchidos corretamente, exemplo:
XMLH-T1_CNPJ = 00000000000000
XMLH-T1_CPF = 86399845653
Ao analisar o XML assinado e enviado à SEFAZ, no GRC (SXMB_MONI), constatei que no bloco dos dados referente ao transportador, o tag não aparece.
Alguém já passou por esta situação?Claudemir,
estranho que esse erro nao acontecia antes, pq esse codigo foi um dos poucos pontos em que nao mudou nada pro layout 2.00 em relacao ao 1.10, no GRC:
IF NOT is_nfe_header-t1_cnpj IS INITIAL.
ls_nfe_transp-transporta-choice-cnpj = is_nfe_header-t1_cnpj.
ls_nfe_transp-transporta-choice-selection = 'CNPJ'.
ELSE.
ls_nfe_transp-transporta-choice-cpf = is_nfe_header-t1_cpf.
ls_nfe_transp-transporta-choice-selection = 'CPF'.
ENDIF.
Talvez no ERP tenha mudado a maneira de passar os parametros, e daí agora tao jogando zeros no CNPJ qdo esse é vazio?
De qq maneira, a solucao é via chamado.
Eu sugeriria abrir chamado no SLL-NFE e solicitar que implementassem pro CNPJ/CPF do transportador a mesma lógica que há no CNPJ/CPF do destinatário, mas sem o tratamento de vir vazio, pois o CNPJ do transportador nao aceita vazio, ao contrario do CNPJ do destinatario. Seria algo assim:
IF NOT is_nfe_header-t1_cnpj = '00000000000000' AND " RS 20081008
is_nfe_header-1_cnpj NE ''. " RS 20081008
ls_nfe_transp-transporta-choice-selection = 'CNPJ'.
ls_nfe_transp-transporta-choice-cnpj = is_nfe_header-t1_cnpj.
ls_nfe_transp-transporta-choice-cpf = ''.
ELSE.
ls_nfe_transp-transporta-choice-selection = 'CPF'.
ls_nfe_transp-transporta-choice-cnpj = ''.
ls_nfe_transp-transporta-choice-cpf = is_nfe_header-t1_cpf.
ENDIF.
Abs,
Henrique. -
Entrega futura - Não contabiliza PIS e COFINS na MIGO
Bom dia a todos,
Estou tendo dificuldades de lançar os impostos PIS e COFINS na MIGO para o cenário de entrega futura com o tipo de movimento 801/802.
Eu já fiz todas as configurações disponibilizadas no forum e inclusive abri um chamado na SAP que orientou a aplicação das mesmas notas, conforme descrito abaixo :
Eu estou achando que o problema está na configuração da OMJJ para o movimento 801/802, pois não vejo registros/configurações na pasta "modificação de conta", e acredito que para o sistema identificar a string WE01 talvez precise destas configs ...
Alguém saberia me dizer se para os tipos de movimentos brasileiros 800-899 é normal que não exista registros na pasta "modificação de conta" ?
Apenas como informativo :
- Na MIRO contabiliza corretamente e gera os impostos no livro corretamente;
- Na MIGO não gera contabilização dos impostos porém na Nota Fiscal os impostos são calculados e destacados corretamente (ICMS, IPI, PIS e
COFINS);
- Não utilizo PIS e COFINS no preço (TAXBRA);
- O principal documento que segui foi o "PIS-COFINS_not_incl_on_net_price" mencionado na nota 1697517;
- Também já analisei as notas 844630 e 679372;
Se alguém já passou por este problema e puder me ajudar eu agradeceria bastante.
/Flavio Marcilio
Resposta SAP:
Hi Flavio,
Thank you for contacting SAP Active Global Support.
Unfortunately PIS and COFINS calculation is still not covered for
future delivery in MIGO. However there is a workaround, but only for
TAXBRA. This you can read on note 1697517. Please check the text below
that was taken from that specific note:
Solution
To enable PIS/COFINS posting at MIGO you should do the customizing
described on article of this link: (
http://scn.sap.com/docs/DOC-5727 )
That said, for you to be able to to use this kind of functionality, it
is necessary to follow the steps on the link above. Just applying note
1697517 won't solve the issue. Please, review all your steps in order
to check if all requisites on the link are applied.
The requested in the message refers to a consulting issue instead of a
bug or error.Olá Cláudio.
Não existe solução standard para configuração envolvendo PIS e COFINS para processos de consignação.
Pode-se tentar atender o cenário customizando PIS e COFINS na mesma linha do ICMS para consignação, mas isto necessita de uma avaliação específica por parte dos seus consultores para determinar esta possibilidade.
A solução oficial da SAP está descrita na nota #852302.
Atenciosamente,
Felipe Silveira -
Error 70 - Código do status 225: Rejeição: Falha no Schema XML da Nfe.
Bom dia grupo!
Nós estamos atualmente recebendo a seguinte mensagem de erro da SEFAZ relacionado aos batches que nós enviamos: Error status 70 "Error from the authorities" and Código do status (Status Code) 225: Rejeição: Falha no Schema XML da Nfe.
Nossa configuração é 46C com muitos OSS notes aplicados (veja abaixo)
Nós estamos realmente parados neste momento e não temos nem ideia de onde começar.
Atenciosamente,
Marc de Ruijter
OSS notes for NF-e phase 2
989115 Nota Fiscal Electronica (NF-e) - Overview Note
852302 Implementation Overview ISS 2004 - Legal Change MP135/LC116
759965 New Condition Formulas for MP-135 and ISS 2004
747607 Basic Customizing for MP135 and ISS legal change Brazil
980214 DDIC changes: PIS / Cofins Tax Law and Tax Situation
981123 PIS / Cofins Tax Law and Tax Situation
981687 NFe: For Services in Muncipio Sao Paulo
934846 Syntax error: TYPE-POOL 'SXRT' is unknown
979881 Message S 000 in NF writer when mandatory fields not filled
980213 Nota Fiscal Electronica (NF-e) of SEFAZ - Phase 2
1037070 NF-e of SEFAZ - Phase 2, Enhancement 01
1014600 No output found for the Nota Fiscal
1052575 NF-e of SEFAZ - Phase 2 / DDIC changes after shipment
1043688 NF-e of SEFAZ - Phase 2, Enhancement 02
1062468 NF-e: Multiple volume structure for XML file
1062251 NF-e: Extension of BADI Interface FILL_HAEDER
1070261 NF-e of SEFAZ - Phase 2, Enhancement 03
1094041 NF-e of SEFAZ - Phase 2, Enhancement 04
1000130 Public System for Digital Bookkeeping (SPED) - Overview Note
1008306 SD: Manual changes of CFOP for services when ISS tax applies
998194 Missing ISS Tax Situation in the Nota Fiscal
1047606 SD/Brazil: Using of error log during Nota Fiscal creation
120449 SD-Brazil Exchange variance error in Nota Fiscal
92383 LSA:BR:SD: Tax laws in return nota fiscal
689157 Nota Fiscal Split and number of Packages
987882 ISS Tax Law (field J_1BTAXLW3) not copied from sales order
989965 CFOP redermination in the delivery document not working
909835 Message 8B 679 raised during the delivery process
337554 SD: No. of packages in Nota Fiscal
533046 Repair order inconsistent to object list
920330 Error when changing the tax codes in a sales order
998195 PIS/COFINS/ISS Tax Law and Tax Situation in SD
104606 EDI/IDoc: Mapping IDoc types to ANSI X12
1094041 NF-e of SEFAZ - Phase 2, Enhancement 04
1105588 J_1BLFZF: Runtime error OBJECTS_OBJREF_NOT_ASSIGNED
OSS notes for XML ver 1.1 and NF-e phase 3
1065334 NF-e: Extension of BADI Interface FILL_ITEM with tax table
1068615 NF-e: Extension of BADI Interface with SD document flow
1079826 NF-e: BAdI Interface Enhancement for NF Messages
1069919 NF-e: Partner in Block E should always be main partner
1090279 NF-e monitor: automatic refresh upon user actions
1093252 NF-e: ICMS tax situation in XML File and DANFE
1113127 NFe: New XML Layout - Version 1.10
1114348 NF-e - xNFe integration - backend
1122294 Send/resend NF-e: fill VBFA for BAdI item method
1124075 NF-e: Serie not taken from Contingency NF-Type
1144194 NF-e: Cancellation/Skipping Reason
Bug Fix notes for NF-e BAPI.
1049946 NF-e: Adaption of Nota Fiscal Bapis
1147934 NFe: Random number should not be generated for incoming NFes
1150733 NFe: Randon number and check digit not cleared
1154995 NF-e: NF BAPI - enhancement for NF-e processing
1158622 NF-e: NF BAPI - no input of random number possible
Bug Fix notes for Contingency process
1158612 NF-e: Wrong partner in Block-E for Entrada
1240212 NF-e: One time Vendor data not transferred to XML file
1255450 NF-e: Jurisdiction code for one time vendor / customer
1257030 NF-e: Country Name for one time vendor / customer
1069018 Cancellation of incoming NFe shows error J1B_NFE 003
1070077 NF-e: Protocol number and document status for Denied NF-e
1145148 NFe: Cancellation for Contingency NFes
1152263 NF-e monitor: wrong action status '7' for C-NF-e
1146914 NFe: Synchronous call to messaging system from backend
1149356 NFe: Dump when NFe is cancelled with MIGO
1152081 NFe: Dump when NFe is cancelled with VL09
1153533 NFe: Dump when NFe in contingency is cancelled with VL09
1156116 NF-e: Contingency by stock transfers
1160107 NF-e: Cancellation of contingency NF-e with DOCSTA = 1 or 2
1161347 NF-e: Cancellation of Contingency NF-e - correction
1238648 NF-e monitor: req. action '3' (send) wrong for swtch. NF-e
1165953 NF-e: Numbering Gaps
1244326 NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP
1245425 NF-e monitor: required process step - contingency
1252567 NF-e: Resend of NF-e - rejected or with validation error
1266344 NF-e: Action Indicator for NF-e with validation error
1254565 NF-e: Synchronization of RFC call between ERP and xNFe
1053626 MIRO: wrong document reference in nota fiscal
1073259 NF-e: Transfers - Outgoing NF-e No. not taken by Incoming
1153874 NF-e: GR for future delivery takes wrong NF-e number
1174946 NF-e: Serie not considered for duplicate NF-e number in MIRO
Miscellaneous bug fix notes
1175538 NF-e: Reference between NF and NF-e
1244881 NF-e: Mixed scenario in MIRO shows error 8B219
1257422 MIRO: Error 8B 219 by posting of reference invoices
1150843 NFe: Text for cancel reason not transferred to XML file
Bug Fix Notes Group 2
1059699 NF-e: Reference between NF and NF-e
1139062 NF-e incoming: Posted via J1B1N -> Wrong Document Status
1144199 NF-e: SD Billing and Contingency
1145089 NF-e: Cancellation despite rejected cancel request
1149787 NF-e: Wrong status-code text in NF-e history
1151112 NF-e: cancellation-reason text gets lost (pre req of 1150172)
1150172 NF-e monitor: selection leads to dump
1068379 Creation of Billing document issues an error 8B 145 (pre req of 1145089)
1152842 NF-e: cancellation reason does not work
1154700 NF-e: Random number & check digit not stored in active table
1073145 PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
1082527 Missing PIS / COFINS Tax Laws for Transfers (pre req for 1155231)
997868 VL02N: CFOP, tax laws not copied from delivery (error 8B148) u2013 (pre req of 1155231)
1155231 PIS/COFINS tax law in NF/NF-e by split valuated material
1155424 NF-e monitor: Menu -> "Check MS Connection" does not work
1159177 NF-e: FUNC J_1B_NFE_SET_STATUS_IN_BACKEND set as Rem.Enabl
1161951 NF-e monitor: "Resend" functionality.
1162232 NF-e: switch to contingency not possible after MSS Update
1162512 NF-e: cancellation reason not initial at first-time call.
1162629 NF-e: creation date gets deleted from NF-e data-base table
1164283 NF-e: SCS '5' - upon authr.to cancel system does not cancel
1165155 NF-e Monitor: BACK (F3) leads to cancellation
1165360 NF-e Monitor: new selection parameter - creation user
1168394 NF-e: Reference document not taken from Nota Fiscal header
1168798 NF-e: User decision for used NF-Type for Material Movements
1171383 NF Writer: Copy NF-e that was switched to contingency.
799445 Nota Fiscal creation: Consideration of local dates (pre req of 1171383)
1104003 NF-Writer: Serie not taken from Reference NF (pre req of 1171383)
1156037 NF-e: NF-Writer allow reference with different NF-types (pre req of 1171383)
1175759 NF-e: central contingency per business place - correction
1239598 NF-e: Random number and check digits are lost in NF writer.
1163888 NF-e: Random Number includes spaces (pre req of 1239598)
1245425 NF-e monitor: required process step u2013 contingency. u2013 applied in bug fix notes no need to apply.
1246700 NF-e: Wrong reference for NF entradas.
1257688 NF-e: Update termination with error J1B_NFE 021
1258021 NF-e: Dump by creation of NF header text for XML file
1258974 NF-e: Monitor report aborts with DBIF_RSQL_INVALID_RSQL
1265172 NF-e - Decouple RFC from DB Update
1285851 NF-e: Cancellation of none authorized documents
1288925 NF-e: References between NF-e and non NF-e
1272677 NF-e: Cancellation for Material Document with serial number (pre req for 1288925)
1247602 NF-e: Cancellation of material documents with serial numbers
1163104 NF-e: Cancel Material documents with initial cancel reason
1293944 NF-e: Cancellation of material documents with batch classes.
1267128 NF-e: Cancellation goods movement with MVT 844 not possible (pre req for 1293944)
1300000 NF-e: Decouple - Contingency
1314856 NF-e: Decouple - Contingency in J1BNFE and VF01 & VF04
1321837 F-e: Cancel of material documents not possible
1092028 NF-e: Protocol number in NF-header overwritten (pre req for 1265172)
1114283 NF-e: cancellation - document status cleared in J_1BNFDOC (pre req for 1265172)
1234053 Local time / local date in NF header and NF-e XML (pre req for 1265172)
1288994 NF-e: Decupling note 1265172 causes error for incoming NF-e (pre req for 1300000)
1297042 NF-e: NF-e number missed in access key after decoupling (pre req for 1300000)
1087535 RFFOBR_A,U:Doc.no should be filled with 9 digits in DME file Applied OSS note 1087535 to the object Z_RFFORIY1 which was copied from RFFORIY1
1097455 NFE: Bank files should accommodate Doc. Numbers with 9 digits
304961 Wrong boleto check digit with carteira data (pre req of 1097455) - Not relevant
336117 Include due date factor in Boleto barcode for A/R (pre req of 1097455) - Not relevant
705726 ITAU: Boleto has negative interest value (pre req of 1097455) - Not relevant
846297 Func Mod - BOLETO_DATA not printing correct nosso numero (pre req of 1097455) - Not relevant
852782 BOLETO_DATA - Corrections of note 846297 for Bredesco only (pre req of 1097455) - Not relevant
1227478 Dump in payment run (F110) when XBLNR is empty
1138278 NFe: Field PREDBC not filled in XML interface structure (pre req of 1149585)
1149585 NFe: CST field required in XML file for taxes not in NFe
1053855 VL02N raises error 8B 053 "Branch not foundu201D
1165696 RFEBBU00: Error in batch input due to changes in Nota Fiscal
1180402 NF-e: BADI methods FILL_HEADER and FILL_ITEM
1180672 NF-e: Gap numbering check doesnu2019t consider the series
1225338 RFEBBU00: Additional changes to the note 1165696
1241922 NF-e: Report J_1BNFECHECKNUMBERRANGES xNFe adaption
1244326 NF-e: Numbering gaps - Status update in table J_1BNFENUMGAP (Applied using other Kintana)
1270813 NF-e: Year not included in the XML file
1247264 NF-e: Error in RFC to /XNFE/NFE_CREATE after note 1241922 (pre req for 1274200)
1274200 NF-e: Numbering gaps report sends SERIE with spaces
1276185 NF-e: Numbering gaps report sends SERIE with spaces
1294917 NF-e: Gap numbering check - several corrections
1324538 Missing address for OT Customer in J_1B_NFE_CREATE_TXT_FILE
1331432 NF-e: Numbering gaps report detects gaps for initial series
1332167 NF-e: Rep. J_1BNFECHECKNUMBERRANGES aborts with error DC 006
1092341 RFFOBR_A,RFFOBR_D: Performance problem while rebate calcula
1237089 RFEBBU10:While uploading ITAU Bank returnfile- Error(F5 170)
1051314 Check Digit missing from Boleto number (pre req for 1306966)
1306966 J_1BBR30:XREF3 is not updated correctly with Boletofrom bank
1005924 RFFOBR_A-The DME file does not include Rebate for ITAU (pre req for 1287633)
1287633 RFFOBR_A: Discount amount not calculated correctly
1234054 NF-e: function J_1B_NFE_MS_REQUESTS_DATA is not RFC enabled
1297534 NFe cancellation problems in GRC
1243964 NF-e: Adaption of xNFe interface of function NFE/NFE_SKIP
1165746 NF-e: Cancel - Error log not updated
1327465 The program /xnfe/update_erp_status is not updating R/3
1326691 BAdI for controlling the RFC call of external systems
1333136 Prevent simultaneous click on buttons in NF-e monitor
1333742 NF-e got the status 218
1354192 Validation rules: correction for fields TPLACA and T_UF1
1373175 Lock object for /XNFE/NFE_CREATE to prevent double transm
1376500 BAPIRET2 to provide the detailed information to ERP
1267455 Not possible to create different DOCREF per item using BAPI (pre req for 1373321)
1373321 BAPI_J_1B_NF_CREATEFROMDATA: DOCREF from Header go to item
1328583 NF-Writer posting of NF/NFe when mandatory fields not filled
1338166 NF-e: Random number and check digit lost after note 1328583
1259918 NF-e: RFC calls for request for cancellation or skip
1152140 NF-e: backend allows inconsistent new SCS (pre-req for 1298283)
1162852 NF-e: Inbound errors missed in error log of Monitor Report (pre-req for 1298283)
1163056 NF-e: Problems with printing via BADI method CALL_RSNAST00 (pre-req for 1298283)
1276438 NF-e: Parallel Phase not identified in messaging system (pre-req for 1298283)
1296515 NF-e: J1BNFE reset rejected NF-e after skipping request (pre-req for 1298283)
1297823 NF-e: Cancelled NF-e shows wrong action indicator (pre-req for 1298283)
1298283 NF-e: Skip for NF-e with validation error
1362969 NF-e: check cancellation for billing documents
1368159 NF-e: cancellation of invoices via original application only
1370933 NF-e: Accept Rejection to Cancel - wrong status in monitor
1376324 NF-e: Skip for NF-e with validation error
1140579 NFe: Field length conflicts from backend interface to XML
1357713 NF-e: Cancel of incoming NF-es does not update active table.
1173018 NF-e: Field control for Random Number and Check Digit (pre-req for 1366320)
1321517 NF-e: MIRO Credit Memos for NF-e shows error 8B 020 (pre-req for 1366320)
1366320 NF-e MIRO:Save is allowed without mandatory fields filled for NFe
1375066 NF-e: J_1BNFECHECKNUMBERRANGES ends too early, wrong subrc
1375894 NF-e: J1BNFE authority check for company code
1377879 NF-e: Report J_BNFECALLRFC aborts with message A098
1379062 NF-e: posting GR after cancellation leads to wrong NF-e
1357777 Cancel billing document without Nota Fiscal cancellation
1380861 NF-e Resend(proc.stat.07) with Signature error impossible
1362025 Error while sending Bacen Code EX with 0 on begining
1249819 NF-e: Field MODFRETE filled incorrectlyBom dia Marc de Ruijter,
Não dá para ler sua thread, mas imagino que seu validador esteja desligado.
No GRC vá em SPRO --> SAP GRC Nota Fiscal Electronica --> Configure System Response for Each Tax Number (CNPJ)
Para ligar/desligar o Validador basta clicar no check box na coluna Validation.
Observação: Para correto funcionamento do GRC deve-se sempre utilizar o validador ligado.
Após isto refaça seu teste, é provável que você receba um erro de validação para a NF-e. Veja em GRC Web monitor -> NFe Detailed View -> Validation History.
Atenciosamente,
Fernando Da Ró -
NF de Saída a partir de Várias NF de entrega
Pessoal, Boa Noite!!!
Tenho o seguinte cenário tenho um cliente que tem varias filiais e eu vendi algumas impressoras para ele.
Ele pediu para enviar para essas filiais e faturar pela matriz. Fiz 7 NFs de entrega cada uma com o cnpj da filial de destino com o CFOP correto de envio.
Agora quero fazer a NF de venda e preciso linkar com essas notas de entrega para não dar baixa no meu estoque novamente.
Alguem sabe como posso fazer isso??
Obrigado
RodrigoBoa tarde Rodrigo,
Para linkar a NF de saída com as várias entregas, é só fazer a cópia a partir da tela de NF de saída.
Entre na NF de saída, coloque o código do cliente e mande copiar das Entregas, nesse momento usando o botão Ctrl você pode selecionar quantas entregas quiser e o próprio B1 faz a soma dos valores totais. -
I developed a Report which proces an XML document based on the following schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://palaciohierro.com.mx/mde/ebre"
xmlns="http://palaciohierro.com.mx/mde/ebre"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:phtypes="http://palaciohierro.com.mx/mde/phtypes"
elementFormDefault="qualified">
<xsd:import namespace="http://palaciohierro.com.mx/mde/phtypes"
schemaLocation="http://serreg2.palaciohierro.com.mx:8888/mdews/schema/services-types.xsd"/>
<xsd:annotation>
<xsd:documentation xml:lang="es">
Esquema de respuesta de busqueda de eventos para la Mesa de Eventos Web
Copyright 2002 palaciodehierro.com.mx. Todos los derechos reservados.
</xsd:documentation>
</xsd:annotation>
<xsd:element name="evento-busqueda-respuesta">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="erType">
<xsd:attributeGroup ref="phtypes:servicioIdGroup"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:unique name="id_busqueda">
<xsd:selector xpath="busqueda"/>
<xsd:field xpath="@id_busqueda"/>
</xsd:unique>
</xsd:element>
<xsd:complexType name="erType">
<xsd:annotation>
<xsd:documentation>respuesta de busqueda de eventos</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="busqueda" type="busquedaType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="busquedaType">
<xsd:annotation>
<xsd:documentation>evento</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="evento" type="eventoType" minOccurs="0"/>
</xsd:sequence>
<xsd:attribute name="id_busqueda" type="phtypes:identifierType" use="required"/>
<xsd:attribute name="encontrado" type="xsd:boolean" use="optional" default="true"/>
<xsd:attribute name="comentario" type="phtypes:comentarioType" use="optional"/>
</xsd:complexType>
<xsd:complexType name="eventoType">
<xsd:annotation>
<xsd:documentation>datos del evento</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="organizador" type="organizadorType" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="entrega" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="domicilioType">
<xsd:sequence>
<xsd:element name="persona" type="phtypes:personaType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id_evento" type="phtypes:identifierType" use="required"/>
<xsd:attribute name="numero" type="phtypes:identifierType" use="optional"/>
<xsd:attribute name="envoltura" type="xsd:string" use="optional"/>
<xsd:attribute name="usuario" type="xsd:string" use="required"/>
<xsd:attribute name="tipo_evento" type="xsd:string" use="required"/>
<xsd:attribute name="tipo_cliente" type="xsd:string" use="required"/>
<xsd:attribute name="tienda" type="xsd:positiveInteger" use="required"/>
<xsd:attribute name="plan" type="xsd:string" use="optional"/>
<xsd:attribute name="fecha_evento" type="xsd:date" use="required"/>
<xsd:attribute name="fecha_registro" type="xsd:date" use="required"/>
<xsd:attribute name="fecha_lista" type="xsd:date" use="optional"/>
<xsd:attribute name="fecha_cierre" type="xsd:date" use="optional"/>
<xsd:attribute name="estado" type="phtypes:estadoEventoType" use="optional"/>
<xsd:attribute name="com_general" type="xsd:string" use="optional"/>
<xsd:attribute name="com_envio" type="xsd:string" use="optional"/>
<xsd:attribute name="NIP" type="xsd:string" use="optional"/>
<xsd:attribute name="VIP" type="xsd:boolean" use="optional" default="false"/>
</xsd:complexType>
<xsd:complexType name="organizadorType">
<xsd:annotation>
<xsd:documentation>datos del organizador</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="phtypes:personaType">
<xsd:attribute name="id_participante" type="phtypes:identifierType" use="required"/>
<xsd:attribute name="tipo" type="xsd:string" use="required"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="entregaType">
<xsd:annotation>
<xsd:documentation>domicilio de entrega de regalos</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="domicilio" type="domicilioType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="tipo" type="xsd:string" use="required"/>
<xsd:attribute name="nombre" type="xsd:string" use="required"/>
</xsd:complexType>
<xsd:complexType name="domicilioType">
<xsd:annotation>
<xsd:documentation>datos del domicilio</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="phtypes:domicilioType">
<xsd:attribute name="id_domicilio" type="phtypes:identifierType" use="required"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
after setting both the schema and the XML document I want the Report to be based on, I get the following error:
ERROR 63001: Invalid stream in the URL address of the data definition http://myserver:8888/myapp/evento-estadocuenta-respuesta.xsd eventoType.
Are there any restrictions on the schema that the XML Reports PDS can process?
Where could I find documentation on this isssues?
Thanks,
FedroIndeed, I have found that no xsd includes and complex types will work. There's a faint mention of this in the Report's Realease Notes, but nothing complete and thorough.
I have found that only the simpliest XML schemas with no custom types and (only a few elements of simple types will work). And also, a simple File-Row-column XML layout will work.
It seems to me that the XML PDS is still a newborn, and a lot of work still needs to be done to be practical and useful... long way to get something like FOP.
Well, the whole idea of having a web service which will feed XML docs to both parties and Report's services will have to stay in the oven a little longer (or may be not so little).
Thanks anyway,
Fedro -
Error in PSA with special characters
Hello,
I'm having a problem with sprecial characters in PRD system.
This happen with standard extractor for Confirmations in SRM module, 0BBP_TD_CONF_1.
I have 5 records with error in PSA. The field that have the error is 0bbp_delref and it has the text: GUIA ENTREGA Nº2.
The error message says that field OBBP_DELREF has special characters that are not supported by BW.
The field is char 16 and in spro I have the characters:
QWERTYUIOPASDFGHJKLǪNºZXCVBM/~^´`* '()"#$%&!?.-0123456789«»<>
In QUA, I created confirmations with this text and it worked fine and the characters in SPRO are the same.
Any idea?
Thanks and best regards,
MariaHi Maria,
There will be no issue with update rules as the issue is with Data..
ALL_CAPITAL should resolve your issue, .otherwise try individually executing those spl characters in RSKC..
have you tried in SPRO...
Check in this table RSALLOWEDCHAR in SE11 and find what all characters allowed(permitted) in PRD system...
please go through the above mentioned blog once
Thanks,
Sudhakar. -
Hello,
I'm trying to upload a CSV file with the next format but i receive the following error in the slg1 transaction of SRM.
Error in the CSV file in the following line:
tent;;;;;;;;;;;;;;;
The CSV file format is this:
SAP CATALOG CSV 2.0 <;> update;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Defaults;ES;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
1. catalog export for /CCM/MASTER_CATALOG by user XE06241 at 08.10.2008 12:13:31 (CET)
Model;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
1. Catalog;CatalogID;CatalogType;Catalog Characteristic(s);Catalog short text(s);;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Catalog;IMP_CAT_PROVEEDORES;2;cat_prov;{ES-ES}IMP_CAT_PROVEEDORES;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Content;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
#;Texto materal;Activo;Divisa;GLG Responsable;Nombre Proveedor;Texto pedido;Unidad;U.M.B. Maestro de materiales;Posición de contrato;Número de contrato;Plazo de entrega;Texto largo de material;Unidad de medida del pedido;Grupo de artículos;URL;Tipo de objeto MIME;Código del fabricante;núm. material del fabricante;ID de Proveedor;ID del material;Material del proveedor;Núm. anterior del material;Descripción breve del material;Texto adicional;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;Vista;
ItemValuation;Comment;ACTIVO;WAERS;GLGRESPONSABLE;NAME1;TEXTOPEDIDO;UNIDAD;/CCM/BASE_UOM;/CCM/CONTRACT_ITEM_ID;/CCM/CONTRACT_ID;/CCM/LEAD_TIME;/CCM/LONG_DESCRIPTION;/CCM/ORDER_UNIT;/CCM/PRODUCT_GROUP;/CCM/PICTURE#/CCM/URL;/CCM/PICTURE#/CCM/MIME_TYPE;/CCM/MNFCTR_ID;/CCM/MNFCTR_PART_NO;/CCM/SUPPLIER_ID;/CCM/PRODUCT_ID;/CCM/SUPPLIER_PART_NO;CODIGOANTIGUO;SHORT_DESCRIPTION;TEXTOADICIONAL;T_DAR_S;T_DAR_N;T_DAR_E;T_DAR_NW;T_DAR_CAN;T_DAR_CEN;T_DAR_CAT;S_BCL;S_FACTORING;FINANZIA_RED;FINANZIA_SSCC;FINANZIA_UNOE;NAVIDAD;INSTITUCIONAL;SSCC;OPERACIONES;ORGANIZACION;ALMACEN;RED;INMUEBLES;
000000000000000112;Prueba Catálogo;TRUE;EUR;INMUEBLES;PROVEEDOR000726;Texto pedido de este material y ocupa las 2 líneas que me permite la tr.;Unidad;Unidad;00010;4610000045;005;Este texto pertenece al texto de datos básicos del material, que debe ser leído por el proceso para ser incluído en el campos del fichero LONG_DESCRIP;Unidad;110100500;
REDCARPETAUBICACION.GIF;GIF;0020000060;9017829237282939373987393873987375610917;0010000782;000000000000000112;21789123784973849734893748934789347;123456789012345678;Prueba Catálogo;GRANO FINO, CALIDAD ALTA;FALSE;FALSE;FALSE;TRUE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;FALSE;You might be best to open a support incident about this so you can work directly with an engineer on this. Infoview is using the Java SDK, its possible there is an issue with the .NET SDK that needs to be looked at.
-
Error using Message Transform Bean in SimplePlain2XML in file sender
Hi guys.
Im using Message Transform Bean to convert from file to xml in file sender.
My structure look like this:
ROW (1..n)
>TRANSPORTES (1)
>ENTREGAS (1..n)
And I have configured the module like this:
AF_Modules/MessageTransformBean - transform
transform - Transform.Class - com.sap.aii.messaging.adapter.Conversion
transform - xml.ENTREGAS.endSeparator - 'nl'
transform - xml.ENTREGAS.fieldFixedLengths - 1,30
transform - xml.ENTREGAS.fieldNames - TIPO,NUM_ENTREGA
transform - xml.ENTREGAS.keyFieldValue - E
transform - xml.TRANSPORTES.endSeparator - 'nl'
transform - xml.TRANSPORTES.fieldFixedLengths - 1,30
transform - xml.TRANSPORTES.fieldNames - TIPO,NUM_TRANSPORTE
transform - xml.TRANSPORTES.keyFieldValue - T
transform - xml.conversionType - SimplePlain2XML
transform - xml.documentName - MPrueba_Zip
transform - xml.documentNamespace - http:/XXXXXX.es/XXXX/sap/prueba
transform - xml.keyFieldName - TIPO
transform - xml.processFieldNames - fromConfiguration
transform - xml.recordsetName - row
transform - xml.recordsetStructure - TRANSPORTES,1,ENTREGAS,*
Im getting this error and I don´t know why:
Error: com.sap.aii.messaging.adapter.trans.TransformException: Transformer Conversion3.0.5227 Error initializing Class: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.fieldFixedLengths' or 'xml.fieldSeparator' is missing (4409) Parameter 'xml.fieldNames' is missing (4403) ; nested exception caused by: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.fieldFixedLengths' or 'xml.fieldSeparator' is missing (4409) Parameter 'xml.fieldNames' is missing (4403)
Why am i doing wrong?????
Thanks a lot!!!Hi
For Complex conversion you have to use xml.conversionType as "StructPlain2XML"
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
Regards
Ramg -
Vendor search with CNPJ number
Hello all,
We are in SAP SRM 5.0 Server 550 system with ECS.
Recently we went live with Brazil, now there is a requirement that the users while creating SC want to select vendors based on CNPJ number (Legal tax number - In vendor master is Tax number 1 ).
So the vendor search criteria should include CNPJ field. Can you suggest possible ways of achieving this.
CNPJ number is getting replicated in SRM.
Rgds,
MadhanSorry for the delay in responding to your question. I talked to one of our search experts and he told me that most part numbers are searchable, as long as you are in the library that contains the part number. Alternatively, you can search for docs based on their part number n the Oracle Store.
Each book that is published using the standard Oracle procedures goes into a directory hierarchy on download.oracle.com. In your example, the URL for the table of contents would be:
http://download.oracle.com/docs/html/A75388_03/toc.htm
However, that URL gives a "page not found" error. So I suspect that the book either was published so long ago that it wasn't transferred over to the download server. -
Hi All,
I need to configure CNPJ number for the new plant, I have a doubt on this, CNPJ number have following format ,
12.345.678./0001-96 and these digits represent three distinct elements:
12.345.678. - The first eight digits refer to the company registration number assigned to the company by the tax authorities.
*Its Configured *
0001 - The next four digits comprise the business place.
Its Configured *
96 - The last two digits refer to the check digits, which the system uses to perform automatic checks when you create a customer or vendor master record, to ensure that no invalid numbers are stored in the system.
where to configure this ???
Thanks & Regards,
PKDear Experts,
During Serial Number profile in Serializing Procedure i have maintained the following settings, will it be fine:
MMSL Maintain goods receipt and issue doc. 03 02
SDLS Maintain delivery 03 02
SDRE Maintain returns delivery 03 02
But during MIGO. it is giving an error - " No new number can be entered for material". Also do we have to create serial numbers first before MIGO?? I tried that IQ01, i filled only plant it says " Stock control active".
I think i m missing some config settings
Plz guide
Thanks
DM
Edited by: Deepak M on May 15, 2008 4:26 PM -
Error on Creating New Business Partner
Hi All,
We have client who are using SAP Business One 2007 A (8.00.181) SP:00 PL: 49; they have been using the system for more than three years perfectly good .Now they have started to face a problem of Creating new Business Partners and System is recurring with an error message that u201CThis entry is already exist on the following tables u2018Business Partnersu2019 (OCRD) (ODBC u2013 2085) [Message 131 u2013 183]u201D while there is no such kind of record exist on the system. So can any one help on this problem?
Best Regards,Hi.........
Please check OCRD and ACRD table.
OCRD table is for whether the Business Partner Master is already present or not.
And ACRD is for whether the Business Partner Created and Deleted from OCRD and logs manitained in ACRD.......
Please check you get some Clue........
Regards,
Rahul
Maybe you are looking for
-
Report Builder 3.0 Expression i am not able to make it work on Oracle DB Table
Hi, I am newbie to SSRS Report Builder 3.0 so please be patient with me. I am trying to create a report to query Remedy Ticketing System and it uses Oracle Database installed on a Unix OS...My end objective is to do some calculation on the ticket met
-
Do I have to previously open a pdf to launch the batch OCR tool?
In Acrobat X, I could launch the batch recognize text tool as a wizard from the basic menu you have when opening Acrobat without any file open. Now with XI, I first have to open whatever PDF then go to tools and choose recognize then more than one fi
-
4.4.4 has a wakelock issue after playing audio files or podcasts
phone wont deep sleep after done playing media. which in turns drains the battery faster. The only way to get deep sleep back is to restart device didnt have this problem in 4.4.2
-
My ichat is not working with AIM
I bought my macbook in march and have never been able to get my aim to work. It logs in but none of my contacts are ever shown as anything but offline and grayed out. I did check into my aim from my AOL email and it's the same way on there. I have se
-
Boot media and Active Directory Boundaries
I am using a active directory site as a boundary. It works fine for deployments etc to machines that are already on the domain. When I however boot with bootable media it does not get any task sequence's and seems like it cant find the management poi