Dúvidas XML 2.0 - Dois ECCs

Estou em um cliente com o seguinte landscacpe:
SAP_ECC_1 <-->
                                GRC/PI (7.0) <--> SEFAZ
SAP_ECC_2 <-->             
Sendo que tenho dois ECCs e apenas uma máquina GRC/PI.
Considerações:
Para o SAP_ECC_1 foram aplicadas todas as notas referente a versão XML 2.0;
Para o GRC/PI foram aplicados SLL-NFE SP15, SLL-NFE-JWS SP11 e XI content 15, mais as notas pós SLL-NFE SP15.
Para o SAP_ECC_2 não foi aplicado nenhuma nota referente a versão XML 2.0.
Datas de Go-live (XML 2.0):
SAP_ECC_1 -> 15/11/2010;
SAP_ECC_2 -> 15/12/2010;
A questão é:
Verificando a </XNFE/NFE_CREATE> da versão 1.0 e da 2.0 observei que foram criados novos parâmetros.
Quando o SAP_ECC_1 entrar em produção (emitindo NFe 2.0) o SAP_ECC_2 (continuará emitindo NFe 1.0) e com o
ambiente sem nenhuma nota aplicada referente a XML 2.0.
Posso ter algum problema?
Obrigado,
Al.

Al,
os parametros novos sao de fato opcionais e especificos para o layout 2.00, com excecao do IV_VERSION.
Porém, a lógica dentro da /XNFE/NFE_CREATE considera que, se este parametro nao for preenchido, o valor default a ser considerado é o "005a", justamente para permitir a retrocompatibilidade.
*   define the government version
    IF iv_version =  gc_govvers-vers_006.
      lv_govvers = gc_govvers-vers_006.
    ELSE.
      lv_govvers = gc_govvers-vers_005.
    ENDIF.
Abs,
Henrique.

Similar Messages

  • XML File-- XI-- SAP ECC Scenario

    Hi guys,
    We have the following scenario in XI XML File>XI>SAP ECC, and we need to call a BAPI at R/3 side. Which do you think is the best way to implement this, either calling the BAPI directly from XI or using an Inbound Server Proxy ?
    Thank you.

    Hi,
        Addition to the above ensure that the BAPI Commit is called ....
    or expose the BAPI as the RFC so that the commit and rollback operations can take place in the RFC itself...
    Keep the above options during the design..n implementation...
    Recommended is RFC call rather than proxy when standards are available n  volume of the data is less..
    HTH
    Rajesh

  • IDOC_XML_FROM_FILE Error while loading XML as IDOC to ECC 6.0

    I have successfully converted IDOC to XML file.
    Getting Error while converting XML back to IDOC in ECC 6.0 using function: IDOC_XML_FROM_FILE
    Segment EDI_DS40 is not defined.....I am really not sure about the error as this idoc was previously posted to the same ECC 6.0...
    Exception       SEGMENT_ERROR
    Message ID:          EA                         Message number:           721
    Message:
    The segment EDI_DS40 is not defined.
    Secondly is there a way to load XML file via WE19?
    Tx
    Salman

    Thanks alot Oliver for taking a stab...
    I created the XML file from within SAP by using the functionailty of this function module:-
    IDOC_XML_TRANSFORM
    I created my ZIDOC_XML_TRANSFORM and just added file download facility in that the rest is the same as the orignal function.
    Is there any way for me to supress generation of ED_DS40 segements in the XML file??

  • XML-IDOC inbound for ECC 6.0

    Hi,
    in a ECC 6.0 only landscape we would like to process XML-IDOC in inbound. For outbound we have already create a XML-IDOC port... but I don't be able to find it for inbound.
    How can I do it ?
    Regards.
    Ganimede Dignan.

    Hi,
    it's quite simple, if you have a system base on NW 2004s or newer you have all that you need but take in mind XML-IDOC it's not a Free XML .... it's an XML structure as an IDOC.
    In WE21 TCODE you can set-up and "XML File" port or and "XML Http" port.
    In anyway you can parser each XML by ABAP custom code.
    read olso some of my old notes....
    IDOC_INBOUND_FROM_FILE => called within report RSEINB00
    IDOC_XML_FROM_FILE         => not called by any report (on release 4.6c)
    I have used fm IDOC_XML_FROM_FILE already many times to manually transfer XML-IDocs from one SAP system to another.
    Given the fact that report RSEINB00 is quite simple (see below) you could create your ZRSEINB00 for processing XML IDocs.
    The reports can be scheduled in background to process the inbound IDocs continuously.
    REPORT RSEINB00 MESSAGE-ID E0.
    * EDI inbound processing (main program to be scheduled)
    * This program processes one file with one ore more intermediate
    * documents.  When an error occurs, a message will be send via workflow
    * processing.
    * The index of the last successfully processed record of the file is
    * always written to the table EDFI2.
    * If the program is startet again for this file, the table EDFI2 will
    * be interpreted and the processing will start at the next record.
    * PARAMETERS
    PARAMETERS:
    * directory + name of file that has to be processed
      P_FILE  LIKE  EDI_PATH-PTHNAM  DEFAULT '/usr/sap/.../SYS/global/...'.
    * DATA
    DATA:
      G_MESSAGE_FIELDS LIKE EDIMESSAGE.
    * MAIN PROGRAM
    START-OF-SELECTION.
    * do inbound processing from file
      CALL FUNCTION 'IDOC_INBOUND_FROM_FILE'
           EXPORTING
                FILE_NAME            = P_FILE
           EXCEPTIONS
                FILE_OPEN_FAILED     = 1
                MARKER_TO_BE_DELETED = 2
                READ_FILE_FAILED     = 3
                IDOC_NOT_STORED      = 4
                FILE_DELETE_FAILED   = 5
                MARKER_MODIFY_FAILED = 6
                EVENT_CREATE_FAILED  = 7
                FIRST_RECORD_INVALID = 8
                INVALID_RECORD       = 9
                OTHERS               = 10.
      IF SY-SUBRC  0.
    * fill message fields for exception handling from system fields
        MOVE-CORRESPONDING SY TO G_MESSAGE_FIELDS.
    * error handling using the 3.0 business workflow
        CALL FUNCTION 'IDOC_ERROR_WORKFLOW_START'
             EXPORTING
                  DOCNUM                  = 0
                  EVENTCODE               = 'EDIM'
                  MESS                    = G_MESSAGE_FIELDS
             EXCEPTIONS
                  NO_ENTRY_IN_TEDE5       = 0
                  ERROR_IN_START_WORKFLOW = 0
                  OTHERS                  = 0.
    * do not care for exceptions here
        COMMIT WORK.
    * abend message for RFC
        MESSAGE ID     G_MESSAGE_FIELDS-MSGID
                TYPE   'A'
                NUMBER G_MESSAGE_FIELDS-MSGNO
                WITH   G_MESSAGE_FIELDS-MSGV1 G_MESSAGE_FIELDS-MSGV2
                       G_MESSAGE_FIELDS-MSGV3 G_MESSAGE_FIELDS-MSGV4.
      ENDIF.
    * end of report
    there are some function modules to accomplish this.
    IDOCS_OUTPUT_IN_XML_FORMAT
    IDOCS_OUTPUT_VIA_XML_HTTP
    for inbound processing,
    IDOC_INBOUND_XML_SOAP_HTTP
    IDOC_INBOUND_XML_VIA_HTTP
    IDOC_XML_FROM_FILE
    IDOC Adaptor,
    IDX_IDOC_TO_XML
    Extended table maintenance, to display IDOC in XML format with XSL,
    IDOC_XML_DISPLAY
    IDOC_XML_TRANSFORM

  • XSD and XML to integrate sap ecc system using PI 7.3

    Hi ,
    Please tell me
    1.how to integrate using PI 7.3 XML and XSD to sap ecc to post cost centre idocs .
    2.how to post standard cost centre idocs using PI 7.3 to third party system ,please througn some light on these scenarios

    >.how to post standard cost centre idocs using PI 7.3 to third party system ,please througn some light on these scenarios
    You first need to talk to third party system about their tecnologies handling.  If the sender system ecc sends idoc to PI then PI can convert the idoc to xml file or idoc to webservice or so.
    Example idoc to file is one possible option.

  • Output type for XML in ECC - XI conversion?

    Hi,
    I ahve few queries regarding the PO o/p sent from ECC for XML output type...
    I header XML is supported in ECC from EHP4..is this true?
    If PO from ECC need to be sent out via XML,the output configuration for ECC PO's need to be changed also?
    Also if PO o/p needs to be sent EDI or XML,my understanding is XI will be mandatory for PO to be sent to supplier system.Can you pls confirm.
    Also when we say PO is sent via EDI(idoc) or XML,is there any difference in the data format/way in which data is sent to XI?If there any conversion happening on XI based on output type EDI or XML?
    On ECC side,is XML one of the output type or we just ALE and EDI?

    Hi,
       Check this help.
    http://help.sap.com/saphelp_srm30/helpdata/en/91/41faf2c220e84c9002a4ae4cc1906a/content.htm
    Best Regards,
    Ravi

  • REUSE_ALV_GRID_DISPLAY Download to XML

    I'm trying to export an ALV report into XML format from our ECC 6 system.  From the export->spreadsheet option, I selected the 2003 XML spreadsheet format; however, when Excel 2010 starts up, it displayed a "Problem During Load" pop up box with the text "Table" in it.  I  recently upgraded to Office 2010.
    G

    Looks like I need to load the latest SAP GUI to correct the problem.

  • SAP IDOC to IDOC.xml

    Hello All,
    I have a scenario where I need to pass IDOC.xml from SAP to Legacy system: we need to pass Customer Master and Material Master to the same server.. I am using same File CC to send the IDOC.xml file to the location....
    Is it possible to send the name of the file with respec to IDOC type? Suppose if MATERIAL is sending then Material.xml and if Customer then Customer.xml
    How can I achieve it?? I am not using any ESA objects as I am just passing message from SAP IDOC to Legacy IDOC.xml.
    Thanks
    Rajeev

    Hi,
    I configured what you mentioend... But I am getting test.xml as I used a dummy interface name and name space as I didnt used any ESA (IR) objects.... I am jsut passing the ECC IDOC.xml to IDOC.xml to legacy applicaiton...
    MATMAS01 released from ECC to sap pi.... SAP PI will pass this IDOC to Legacy applicaiton as MATMAS01.xml
    DEBMAS01 released from ECC to sap pi.... SAP PI will pass this IDOC to Legacy applicaiton as DEDMAS01.xml
    As I am not using any transformations and the format target system needed is idoc.xml .. I am using ID objects to forward the IDOC.xml files..
    Please let me know is there any way to dynamically change the file name?
    Thanks
    Rajeev

  • Types of attachments that can be sent in an email from SAP ECC 6.0

    Hi,
      We are redesigning a legacy application in ECC 6.0. The requirement is to send various types of files such as .txt, .csv and .xml files as attachments in email to various business users. The emails should be sent from ECC 6.0 to various external users.
      The question here is whether we will be able send attachments of any type such as .txt OR .csv OR .xml in an email. If possible, what is the procedure to achieve that ?
    Regards,
    Mukund
    Edited by: Mukund Gorla on Aug 23, 2008 12:13 AM

    Hi Mukund,
    You can send email with the attachements like TXT, CSV, PDF, XLS, XML... from ECC 6.0
    Have a look at the demo programs given by SAP
    BCS_EXAMPLE_1
    BCS_EXAMPLE_2
    BCS_EXAMPLE_3
    BCS_EXAMPLE_4
    BCS_EXAMPLE_5
    BCS_EXAMPLE_6
    Regards,
    Trikanth

  • How to get XML data of IDOC

    Hello ABAP gurus
    I am an SAP PI consultant working on some IDOCs.
    I am able to see the payload (in XML format)  sent via IDOC adapter.
    This is being sent to our backend system (ECC 6.0). I would like to know if there is any way that I can see this IDOC in XML format  on the ECC side so that I can compare it with the XML data that I see on PI side.
    After checking old postings on SDN, I have tried tables like EDIDC, EDISYN and EDID4. I even tried IDOC transactions like WE02, WE60 etc.,  But couldn't see the XML data.
    Any suggestions or comments will be highly appreciated.
    Thanks
    Ram

    Hi
    Check SXMB_MONI in ECC if you find the message. I am not sure but you can have a look.
    Regards
    Vinit

  • Comment vider ma bibiotheque de photo et les albums photos sur iphone 4

    Bonjour
    j ai un iphone 4. et j ai mis à jour la dernièere version  du logiciel IOS.
    mon iphone est plein  et je n ai quasiment plus d espace libre donc il ne peut pas faire de synchronisation  et importerde mes derniers achats.
    je dois donc liberer de l espace . j ai déjà vider toute ma pelicule et il ne me reste plus que 8 photos dessus. toutefois  j ai une grosse  bibliothèque de photos qui apparais sous formes d albums et je ne peux pas la retirer ou transferer directement sur mon ordinateur pour vider l iphone.
    ma question donc est: comment proceder pour vider ma bibliothèque de photos et tous les albums.
    Par ailleurs je souhaite aussi vider ma musique  comment dois je m y prendre svp .
    je vous remercie par avance
    keltycia.

    Hi millene,
    Est-ce que vous avez récupérer votre données de iPhone?   Je pense vous etês très malchanceux, parce que votre problème est si compliqué.  Je vous conseil chercher la solution sur google.   Avant, j'ai reconu un aussi question pour supprimés des message de mon android. Et j'ai cherchée sur google et récupérer mes données à temps. Ok, je vous consiel quelque logiciel que google recommandé:
    http://www.ipubsoft.fr/idevice-tips/how-to-recover-deleted-sms-from-iphone.html
    www.apwersoft.fr/recuperation-de-donnees-iphone
    http://fr.copytran.net/support/comment-transferer-contacts-ancien-iphone-a-iphon e-5s/

  • DIMP ON ECC EHP4

    Hi Experts
    I had done a EHP4 upgrade of our ERP 6.0 and during the upgrade just took few components like APPL and HR which are now at 604.
    But now we have a new requirement where in we need to implement DIMP 604.
    How do I go about this?
    Warm Regards
    Madhav

    Hello,
    There is ECC DIMP 604 (a software component ) and Discrete Industry and Mill Products (a technical usage).
    If you want to use EHPI to update Discrete Industries and Mill Products, you will be updating to 604 the following software components:
    EA-APPL 604
    ECC-DIMP 604
    SAP APPL 6.04
    I guess that your EA-APPL and SAP_APPL are already at 604, so if  you use Maintenance Optimizer, select option 'Enhancement Package install',  choose Discrete Industry and Mill Products as technical usageand there you would generate the needed XML, to update only ECC-DIMP to 604.
    Sunny knows more about the upgrade tools to use after that than I do, I would have thought  EHPI could  be used, but it also makes sense to use SAINT.
    I hope this information helps.
    Best regards,
    Miguel Ariñ

  • Inbound Moeda Estrangeira GRC-NF-e 10

    Pessoal, boa tarde!
    A empresa que estou realizando a implantação do GRC NF-e 10  trabalha com entrada de mercadoria com moeda estrangeira.
    Quando determino no pedido de compra a taxa de câmbio fixada para o valor da moeda o sistema não respeita esta instrução.
    Esta correto afirmar que para todas as entradas em moeda estrangeira será necessário cadastrar a taxa de conversão na OB08.
    Pergunto isso porque se tenho dois pedidos com taxas diferentes e realizo a entrada no mesmo dia será necessário modificar a instrução da conversão constantemente.
    Alguém já passou por esta situação e consegue me instruir como realizo este processo?
    Atenciosamente
    Ândrea Lopes

    Felipe,
    também tive o mesmo problema do lado do NTB2B_procNFe_OB. Tentei de várias formas transformar o XML para ficar aderente ao cliente, porém o PI sempre alterava o XML (possivelmente devido ao encoding).
    Vi muitos posts sobre o tema, mas ainda quando era o GRC NF-e 1.0, com a assinatura no Java. Para o GRC 10.0 não funciona, pois quando o xml chega no PI, o mesmo já está assinado, portanto não se pode alterar nada.
    A solução foi para nesses casos específicos enviar o xml através do ECC mesmo.
    Mas para o NFB2B_procNFe_IB ainda sem solução.
    Abs.
    Rodrigo.

  • Problema assinatura - Status 20 - Versão 006

    Bom dia pessoALL,
    Já verifiquei os respectivos links abaixo e não consegui solucionar o meu problema :
    O cenário aqui é:
    ECC (NDE) 005A / ECC (NED) 006  < -- > GRC < -- > PI < -- > SEFAZ
    São dois ECC´s apontados para um ambiente GRC/PI.
    Estamos no SP 15 e última versão dos outros respectivos SP´s (ABA/BASIS...)
    Já realizei a configuração em todo ambiente de GRC para suportar os dois tipos (005a - 1.0 / 006 - 2.0), tanto a  abap / java.
    Qual está sendo o problema, quando faço a emissão de uma NFe do ambiente NED (versão 2.0 - 006)  as notas travam em status do processo 1 e status de erro 20: Assinador digital não acessível.
    Quando é emitido uma NF´e em ambiente NDE (versão 1.0 - 005a) o fluxo acontece normalmente.
    Fiz uma pesquisa e fiz um check nas seguintes transações: sproxy , sldcheck , bd54, bd97 , sxmb_adm... estão ok.
    Já entendi que as notas não estão saindo do GRC para o integration (conexão abap proxy).
    Reliz um check na configuração toda, está tudo ok.
    Não sei como atuar diante da situação. Alguem teria alguma luz ? O que verificar ? O que refazer ?
    Atenciosamente,
    Ricardo

    Bom dia Ricardo,
    Veja esta thread NF-e pré-validação erro - XML 2.00 - /XNFE/VERSION 0006, na resposta do dia Aug 13, 2010 4:45 PM.
    Após o SP15 tem algumas correções a serem feitas.
    Especificamente para este caso é a SAP Note 1498700.
    Atenciosamente, Fernando Da Ró

  • SAP GRC NF-e 10.0: Erro na interface NFB2B_procNFe_IB (contendo CDATA)

    Olá a todos.
    Poderiam por gentileza me ajudar com a questão abaixo?
    Estou com o seguinte problema na interface NFB2B_procNFe_IB do SAP GRC NF-e 10.0 (Support Package 15):
    Recebemos uma série de XML's de montadoras de automóveis que contém informações adicionais nas tags <infAdProd> e <infCpl>, como por exemplo:
      <infAdProd>VLR. PIS R$ 6,81 VLR. COFINS R$ 31,44<![CDATA[<ID ITEM=005115/><PED=4500159772/> <UM=PC/>]]></infAdProd>
    Porém ao inserir essa mensagem na interface NFB2B_procNFe_IB, a interface interpreta da seguinte forma:
        <infAdProd>VLR. PIS R$ 6,81 VLR. COFINS R$ 31,44
          <![CDATA[
            <ID ITEM=005115/>
            <PED=4500159772/>
            <UM=PC/>]]>
            </infAdProd>
    Sendo assim, ocorre o erro abaixo:
    <nm:ExchangeFaultDataExt xmlns:nm="http://sap.com/xi/NFE/common" xmlns:prx="urn:sap.com:proxy:NED:/1SAI/TAS8DFA2846CCAA9B6570C6:702">
      <faultText>Erro durante a transformação: Fim de elemento '{http://www.portalfiscal.inf.br/nfe}infAdProd' esperado programa: /1SAI/SAS6F90159886715E7C4560 caminho: nfeProc(1)NFe(1)infNFe(1)det(4)infAdProd(3)ID(1)</faultText>
      </nm:ExchangeFaultDataExt>
    Sei que temos algumas opções como:
    1. Alterar o XML no mapping do PI; (Funcionaria com mensagens processadas através do PI, mas não conseguiria inserir um XML manualmente via SE80)
    2. Alterar o XML no ABAP ao executar a classe /XNFE/CL_006NFB2B_PROC_NFE_IB; (Fazer algum replace nesses caracteres "<" e ">" por "&lt;" "&gt;"
    Mas como fazer isso sem danificar a assinatura do XML que já está assinado e autorizado na SEFAZ?
    Existe alguma nota SAP para corrigir esse problema?
    Agradeço desde já a atenção.
    Rodrigo Costa.

    Felipe,
    também tive o mesmo problema do lado do NTB2B_procNFe_OB. Tentei de várias formas transformar o XML para ficar aderente ao cliente, porém o PI sempre alterava o XML (possivelmente devido ao encoding).
    Vi muitos posts sobre o tema, mas ainda quando era o GRC NF-e 1.0, com a assinatura no Java. Para o GRC 10.0 não funciona, pois quando o xml chega no PI, o mesmo já está assinado, portanto não se pode alterar nada.
    A solução foi para nesses casos específicos enviar o xml através do ECC mesmo.
    Mas para o NFB2B_procNFe_IB ainda sem solução.
    Abs.
    Rodrigo.

Maybe you are looking for