Estrutura de envio do ECC para XML 2.0

Bom dia, pessoal estava olhando function J_1B_NF_MAP_TO_XML que faz o mapeamento do ECC para XML e percebi que o mesmo não tem nenhum comentário sobre a NF-e 2.00 somente 1.10 como no código abaixo, será que ficou faltando alguma OSS, ja fiz a conferências das principais OSS e elas foram aplicadas., obrigado
ones are read.                                         "V1.10
read NFe customizing for branch                        "V1.10
PERFORM read_nfe_customizing3 USING   wk_header-bukrs "V1.10
                                        wk_header-branch "V1.10
                                        wk_header-model "V1.10
                               CHANGING ls_cust3.        "V1.10
lv_xmlvers = ls_cust3-version.                         "V1.10
                                                       "V1.10
if ls_cust3 is initial.                                "V1.10
Att,
Marcelo

Aconselho a navegar pelos forms que preenchem as estruturas e dar uma olhada você mesmo. Não sei de cabeça quais campos sao do standard e quais são preenchidos pela BAdI.
Por exemplo, navegue nos forms block_h > block_h1, vc vai achar coisas do tipo:
* quantity in base unit or alternate unit from reference documents ?
* H13
* with XML version 2.0 the QTRIB field has type DEC 15 with 4 decimals
IF xmlh-version >= 2.                              "V2.0
    xmli-qtrib_v20 = wk_item-menge.                  "V2.0
ELSE.                                              "V2.0
    xmli-qtrib = wk_item-menge.
ENDIF.                                             "V2.0*
* H14
* with XML version 2.0 the QCOM field has type DEC 15 with 4 decimals
IF xmlh-version >= 2.                              "V2.0
    xmli-qcom_v20 = wk_item-menge.                   "V2.0
ELSE.                                              "V2.0
    xmli-qcom   = wk_item-menge.
ENDIF.                                             "V2.0
* with XML version 2.0 the VUNCOM field has type DEC 21 with 10 decimals
IF xmlh-version >= 2.                              "V2.0
    xmli-vuncom_v20 = wk_item-nfpri.                 "V2.0
ELSE.                                              "V2.0
    xmli-vuncom = wk_item-nfpri.              "xNFe
ENDIF.                                             "V2.0
Abs,
Henrique.

Similar Messages

Validador GRC SP17 não está funcionando corretamente para XML 3.10

Caros,
Recentemente subimos o SP17 no GRC (SAPK-90017INSLLNFE) e também implementamos as notas para nota versão do XML 3.10 no ERP (1933985 - NF-e new layout 3.10 e seus pré-requisitos).
O XML está sendo gerado corretamente, mas nos casos em que alguma informação não é preenchida corretamente e deveria parar no validador do GRC, isto não ocorre. Exemplo tag F_NRO (house number) vazia, não para no validador do GRC.
Antes do upgrade do support package e na versão XML 2.0, o validador funcionava corretamente.
Aparentemente as configurações de NF-e outboud na IMG do GRC estão corretas e as tabelas /XNFE/XMLVALID e /XNFE/NFEVALID estão preenchidas corretamente também.
Alguém está passando pelo mesmo problema?
Obrigada.

Oi Cristiane,
Qual status da NFe no monitor do GRC 3.10
http://<host>:<port>/sap/bc/webdynpro/xnfe/nfe_outb_monitor ?
Dei uma olhada no código da RFC /XNFE/OUTNFE_CREATE chamada pelo ERP para 3.10. Aparentemente somente a visão de CNPJ tem relevância para erro de validação quando o campo validação está preenchido.
(SPRO - Nota Fiscal Eletrônica - Saída - Atualizar resposta do sistema para nºs próprios ID fiscal)
Outro ponto que você pode avaliar e que tem relevância é a função /XNFE/GET_XMLVERSION que reflete as configurações:
SPRO - Nota Fiscal Eletrônica - Saída:
- NF-e: atualizar sistemas das autoridades conectados
- NF-e: atualizar versão dos tipos de mensagem
E que talvez o caminho lógico, seja o que está errado... o que tenho visto muito.
Veja se lhe ajuda na análise...
Obrigado,
Bruno

GRC 10.0 / PI 7.3 - Envio de Notas para no BATCH_nfeRecepcaoLote_OB

Bom dia, pessoal, tudo bem:
Estou tendo um problema.
Configurei os cenários no Integration Directory > Integration Builder.
BATSR_WebAS_Outbound_BatchStatusRequest
CANCR_WebAS_Outbound_CancellationRequest
NFESC_WebAS_Outbound_NFeStatusCheck
SIGN_WebAS_Outbound_ExternalSignature
SKIPR_WebAS_Outbound_SkippingRequest
SRVSC_WebAS_Outbound_BatchProcess
SRVSC_WebAS_Outbound_ServiceStatusCheck
O SRVSC_WebAS_Outbound_ServiceStatusCheck está funcionando corretamente, ja conseguimos obter o status de serviço na SEFAZ.
Quando mandamos uma NF-e, ela fica com a engrenagem no monitor sap (J1BNFE), No Monitor WEB, indica Stat.processo: 4 - Incluído no Lote.
No SXMB_MONI, é acionado o BATCH, incluido com sucesso.
@DFQProcessed successfully@ @8QQErro indefinido @ 01.12.2011 09:42:40 01.12.2011 09:42:42 CQ1CLNT230 http://sap.com/xi/NFE/006 BATCH_nfeRecepcaoLote_OB
Porém, para aí. Este erro Indefinido (bolinha verde com uma Interrogação) que aparece, não conseguimos localizar.
O que poderia ser?
Desde já, muito obrigado.
Att.,
Fábio Cirino.

Bom dia Ricardo / Pedro,
O IP e IS importados são do 006, já eliminei o cache do Adapter e fiz Full e CPA cache refresh.
O report XNFE/PROCESS_REPORTS está com a variante configurada com o intervalo de 00:00:05 e Considerar aviso de recebimento, também já testei com outros intervalos.
Ao executar o report /XNFE/GET_ACKNOWLEDGMENT manualmente é gerado uma exceção na consulta do registro da tabela /XNFE/ACKNOWLEDG (CX_AI_SYSTEM_FAULT) e atribuído o status 71 como retorno.
A SAPNote 1373738 já não se aplica ao nosso ambiente que está no SP 08, já implementei as Notas 1849533 e 1857701.
Quando faço um restart da instância J2EE (SMICM) recebo o retorno do ack do PI.
Essa instalação do PI 7.31 dual stack exige alguma configuração adicional para ccBPM ?

ENVIO DE CORREO CON XML DE LA FACTURA ELECTRONICA

HOLA CHICOS, BUEN DIA,
Alguno de ustedes sabe como puedo configurar que el xml que se genera de factura electronica en SAP se envie una copia al correo del cliente?
Agradezco de antemano su apoyo.
SALUDOS
NANCY

HOLA MAURICIO,
Yo estoy utilizando la factura electronica nativa de SAPB1 que genera un xml. Estoy trabajando con 8.81pl07
saludos.

Flash builder paras XML

Hello guys.
Now I have been trying for last 10 days to make this happen but not even one tutorial is working online..
Not even one script i tried is working.
I can make it work with xml feed but I can't make it work as full fetch feed.
Now I have one application online built by conduit mobile
Link to download app
Now I want to create this type of feed in my application with flash builder.
Can any one please explain how, maybe create tutorial ??
Thank you so much ..

Hello guys.
Now I have been trying for last 10 days to make this happen but not even one tutorial is working online..
Not even one script i tried is working.
I can make it work with xml feed but I can't make it work as full fetch feed.
Now I have one application online built by conduit mobile
Link to download app
Now I want to create this type of feed in my application with flash builder.
Can any one please explain how, maybe create tutorial ??
Thank you so much ..

Cenário de envio de XML (B2B)

Olá Henrique.
Estou implementando a solução SAP GRC/NFe e configurando o envio de XML aos clientes através do cenário NTB2B_WebAS_Outbound_B2B_NFe.
Observei que a documentação indica a criação de um communication channel para cada cliente, porém gostaria de configurar um único mail receiver onde o endereço de e-mail seja flexível.
Para isso, necessito enviar do ECC para o GRC o campo e-mail do cliente e que o GRC transmita este campo na mensagem NTB2B_procNFe_OB.
Existe esta possibilidade prevista no GRC?
Se não, como ficam os desenvolvimentos no PI? Como a criação de novo Interface Mapping, ou, até mesmo de um novo BPM?
Obrigado,
Dorval Neto.

Olá Dorval,
nao é preciso desenvolver um BPM.
É possível sim fazer isso dinamicamente (através de alguns simples desenvolvimentos), até mesmo utilizando a interface standard NTB2B_WebAS_Outbound_B2B_NFe (que é chamada por default pelo proxy após a autorizacao da NFE). Para isso, existem 2 métodos:
1. alimentacao do dynamic configuration de Mail (procure sobre "dynamic configuration" ou "adapter specific message attributes" no forum de XI q vc vai ter varios retornos);
2. mapping do XML de NFE p/ a estrutura de Mail Package (procure tb por "mail package" no forum do XI).
Em ambos os casos, vc precisa definir um novo message mapping que irá ser utilizado nesse cenario:
No caso 1, vc precisa de um message mapping "fake" (onde ambas estruturas fonte e destino sao o mesmo message type, no caso o message type da interface NTB2B_WebAS_Outbound_B2B_NFe). No campo que contém o CNPJ nessa estrutura, vc pode fazer por exemplo um Lookup no mapping para chamar uma RFC que retorna o email a ser utilizado a partir do CNPJ (vc pode desenvolver essa RFC no proprio R/3 e chama-la a partir do lookup, passando um communication channel que aponte o R/3). Procure por "lookup api" ou "rfc lookup" no forum do XI. Uma vez retornado o email, vc pode entao alimentar o dynamic configuration do campo To do Mail adapter com esse valor.
No caso 2, o mapping vai de fato preencher o Mail Package.
Vc precisa, da mesma maneira anterior, fazer o RFC Lookup para pegar o valor do email, mas em vez de preencher um dynamic configuration, vc preenche direto na estrutura destino do mapping (q tem os campos subject, to, cc etc.). O campo content vc alimenta a partir do campo xmlString da estrura de origem.
Depois de criados os mappings, vc precisa tb criar um interface mapping para coloca-lo dentro.
No caso 1, alem do mapping dummy q vc criou, o interface mapping precisa ter o java mapping standard q vem no interface mapping standard dessa interface.
No caso 2, o interface mapping soh precisa do mapping q alimenta o mail package.
Para o configuration, vc pode configurar todo o cenario standard. Daí depois de configurado, vc vai no Interface Determination e troca o interface mapping standard pelo interface mapping q vc criou acima.
Ainda, para evitar duplicar/recriar objetos, vc pode incluir uma dependencia do seu Software Component Version ao SWCV SLL-NFE 1.0. Daí, vc pode incluir os objetos standard nos seus proprios objetos. Ainda, alguns objetos vc nao precisa nem criar (como o interface mapping), bastando modificar os objetos "standard" q aparecem dentro do nó "Basis" do seu SWCV (é como se ele automaticamente criasse versoes Z dos objetos standard, q vc pode modificar a vontade; esses objetos tem o mesmo nome e namespace dos standard, mas o SWCV é o seu, nao o SLL-NFE 1.0).
Eu até comecei a escrever um blog a respeito disso tudo, mas nao cheguei a terminar.
Se conseguir, eu publico.
Abracos,
Henrique.
PS: em anexo segue um exemplo de codigo que pode ser utilizado na UDF para recuperar o email. No caso, ele nao preenche dynamic configuration, soh retorna o email (o codigo para preencher o dynamic config está na 3a referencia abaixo).
Referencias:
- Mail Adapter help: http://help.sap.com/saphelp_nw70/helpdata/EN/6b/4493404f673028e10000000a1550b0/frameset.htm
- Javadoc da Lookup API: http://help.sap.com/javadocs/NW04S/current/pi/index.html (package com.sap.aii.mapping.lookup)
- Dynamic Configuration: http://help.sap.com/saphelp_nw70/helpdata/EN/43/03612cdecc6e76e10000000a422035/frameset.htm
- Modifying XI Objects: http://help.sap.com/saphelp_nw70/helpdata/EN/ab/3adb41083f6024e10000000a1550b0/frameset.htm

Envio do XML

Olá pessoal.
Estamos pensando em fazer o envio automático do XML para os clientes, no momento do retorno aprovado da NFe.
Gostaria de saber se alguém já fez isso, e se tem alguma dica / receita de bolo sobre o assunto.
Vamos ver se o que eu tenho em mente está correto.
Pensei em fazer uma nova interface, que ao receber o retorno da NFe com status de aprovada, leia o email do cliente e faça este envio através de email.
Pelo que andamos pesquisando, a SAP ainda não tem isso standard, correto?!
Obrigado.

Bom Dia
A solução standard ... possibilita isso é só configurar os scenarios B2B:
NTB2B_WebAS_Outbound_B2B_NFe
CTB2B_WebAS_Outbound_B2B_Cancellation
existem alguns links que poderam te ajudar
1 - Para maiores informações acesse:
https://wiki.sdn.sap.com/wiki/display/profile/Henrique+Pinto
2 - Using SAP PI Lookup API and Dynamic Configuration in SAP GRC NFE Outbound B2B Interface for Dynamic E-mail Determination
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/00a7ba12-e7cd-2b10-d589-e52b11346f77
Edited by: Ronaldo de Moraes on Sep 16, 2009 5:25 PM

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

SAP ECC Interface w/ IDOC-XML using TCP/IP, HTTP, or FTP to 3rd-Party Syst.

I am trying to understand if the following interface options can occur (without the use of SAP PI or any other middleware):
Option 1A: Can I process an SAP ECC outbound IDoc in XML using TCP/IP to a non-SAP 3rd party system? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 1B: Can I process an SAP ECC inbound XML-IDOC from a non-SAP calling system that used TCP/IP? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 2A: Can I process an SAP ECC outbound IDOC in XML using HTTP to a non-SAP 3rd-party system? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 2B: Can I process an SAP ECC inbound XML-IDOC from a non-SAP calling system that used HTTP? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 3A: Can I process an SAP ECC outbound IDOC in XML using FTP to a non-SAP 3rd-party system? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 3B: Can I process an SAP ECC inbound XML-IDOC from a non-SAP calling system that used FTP? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?

Hello Kirk ,
The answers for your question are:
Option 1A: Yes you can .you can use TCP/IP but you must have a middleware component for that such as BC/JCO .
Please see the link : [http://help.sap.com/saphelp_nw04/helpdata/EN/09/c88442a07b0e53e10000000a155106/frameset.htm]
Option 1B: See the link above.
Option 2A: You can use ABAP code :
[http://help.sap.com/saphelp_nw04/helpdata/EN/e5/4d3514c11411d4ad310000e83539c3/frameset.htm]
Option 2B: [http://help.sap.com/saphelp_nw04/helpdata/EN/90/4f3c2ec3c511d6b2b400508b6b8a93/frameset.htm]
Option 3A: Only with ABAP code :[Reg: FTP Connection;
Option 3B: See the link of Option 3A.
Good Luck,
Boaz
Edited by: Boaz Ornan on Feb 21, 2010 4:33 PM

Problemas no recebimento de XML via E-mail caracteres especiais Valid ***.

Boa tarde
Mestres
Este problema descrito abaixo só acontece qnd recebo XML com caracteres especiais entre as tags Enter, Tabs, Espaço....
que representam 30% dos XML recebidos via E-MAIL
Estou tendo problemas quando tenho a Assinatura Digital verificada pelo Serviço disponibilizado pelo Visual Administrador(Verify)
Hoje recebo um XML por e-mail...resgato a string do XML no Kpro (GRC) e envio para esse serviço de Validação de Assinatura o mesmo Invalida a Assinatura
Quando o mesmo é submetido ao validador do governo Programa Visualizado NF-e 3.5 e ao serviço SEFAZ RS http://www.sefaz.rs.gov.br/ASP/AAE_ROOT/NFE/SAT-WEB-NFE-VAL_1.asp a assinatura é dada como Valida
Bom ...o senhores devem estar se perguntando será que esse arquivo não esta sendo corrompido na transferencia do mesmo para o Kpro ou no envio da msg para o serviço de validação de assinatura..., por esse motivo executei alguns ciclos de teste..:
1 - Baixei o arquivo original para minha máquina e executei a validação usando o programa do governo
Visualizador NFe 3.5 / serviço SEFAZ RS - Assinatura Válida
2 - Executei a Interface através do PI enviando uma MSG contendo a string do xml NFe resgatada no Kpro... para esse
Serviço disponibilizado pelo Visual Administrador(SAP) as java - Assinatura Invalida
3 - Baixei o Payload da MSG da interface de Validação da ***. Digital pela transação SXI_MONITOR Ajustei o xml editando em um bloco de notas (trocando os caracteres <> para maio e menor)
Visualizador NFe 3.5 / serviço SEFAZ RS - Assinatura Válida
4 - Criei um programa abap ler a string do XML no Kpro (GRC) e baixar ..local
Visualizador NFe 3.5 / serviço SEFAZ RS - Assinatura Válida
5 - Executei a Interface através do PI enviando uma MSG contendo a string do xml ...local ..teste executado através da transação SPROXY
- Assinatura Invalida
em qual serviço estará o Problema?
Alguém já enfrentou esse problema ou esta enfrentando?...pois esse tipo de problema parece ser muito comum pois nem toda empresa tem SAP ....e o problema é que o SEFAZ aceita e valida esses XMLs...!
pois estou pensando em seguir parte desta sugestão
agradeço desde já ....!
Edited by: Ronaldo de Moraes on Oct 21, 2009 3:05 AM

Ronaldo,
claramente há algum problema com a codificacao do arquivo.
Abra o xml no Notepad e verifique que na tag Signature, há varias quebras de linha, incluindo caracteres nao reconhecidos (representados como um retangulo).
Ainda, como vc está testando o servico verify?
Vc fez uma interface XI? Porque não há interface PI standard p/ o serviço verify.
Ainda, como vc chamou essa interface? Pela tela de teste do Runtime Workbench?
O próprio ctrl+c que vc dá no conteúdo pode estar corrompendo os dados.
O fato de vc estar utilizando um browser para o teste poderia corroborar isso.
Faça o seguinte teste:
1. Através do XMLSpy, criar uma SOAP Request p/ a interface verify (menu SOAP -> Create New SOAP Request)
2. a tag Send SOAP Request). Aqui deu válida;
4.2. abra o .xml que vc quer testar no notepad, copie a tag Send SOAP Request). Aqui deu inválida.
Ou seja, dependendo da maneira que vc trata o conteudo (aplicacao onde vc abre o .xml, ctrl+c etc) vai haver uma modificacao da codificacao.
Nao vejo muita maneira de garantir que funcione sempre a nao ser removendo esses caracteres, conforme definido pela propria SEFAZ.
Att,
Henrique.

Migração TAXBRJ para TAXBRA

Olá pessoal.
Estamos em projeto de migração de TAXBRJ para TAXBRA e atualização do ECC para 6.0.4
Com relação as ordens de venda em aberto, gostaria de saber se existe alguma forma de converter para a nova price ou teremos que lançar tudo novamente.
Att.
Leticia.

Oi Leticia
Não tem como converter. Você terá que criar novos documentos.
Em uma apresentação recente da SAP foi apresentado que é possível fazer uma migração parcial. Neste caso você pode definir a determinação da sua pricing somente para determinados tipos de documentos de vendas.
Eu particularmente não conheço nem ouvi falar de alguma empresa que tenha feito isso.
Abraço
Eduardo Chagas

Timeout error in ECC "INTERNAL.CLIENT_RECEIVE_FAILED Error while receiving by HTTP (error code: 402 , error text: ICM_HTTP_TIMEOUT)"

Dear Experts,
I am very critical situation due to this timeout error in ECC, please help me as much as you can. Go-live date is very near, but I am not getting any clue why this error is occurring. our ECC system is EHP 4, and PI is dual stack 7.4
My scenario is synchronous ABAP proxy to HTTP_AAE. request is triggering from ECC via proxy and reaching to third party (bank) through PI, I am reviving the response back in PI from bank. But from PI to ECC the response is not reaching. So in ECC after the defined Timeout limit its getting timed out.
I have tried everything by increasing the timeout in ECC more than 15 minutes in HTTP_TIMEOUT under SXMB_adm in ECC, but nothing worked, even if I am increasing for half an hour then also its getting timeout after half an hour.
response from bank to PI is coming within 30 to 40 seconds, but PI is not sending the response back to ECC.
This is classical scenario, and I have checked the trace via SXMB_Moni in PI as well as in ECC, in ECC its showing the timeout error, but in PI i did not see any trace for this error.
I have read many thread on SCN for the same error, and everywhere it has been suggested to increase the timeout, and I have tired that, it didn't help me.
All ABAP proxy configuration has been done as follows.
RFC destinations in ECC
LCRSAPRFC(TCP/IP)
SAPSLDAPI ((TCP/IP))
G type destination to path "/sap/xi/engine?type=entry"
G type destination SAP_PROXY_ESR to path "/rep"
All the destination connection test is working fine.
but i have a doubt on G type destination(AAE_XDJ) to path "/sap/xi/engine?type=entry" which is returns the status code 500 with message "Empty HTTP request received", is it ok with 500 ?
Configuration in ECC Integration Engine configuration is as follows
Questions
How the message gets pushed to ECC from PI, once the message received in PI, I believe by G type RFC destination on path "/sap/xi/engine?type=entry" , please clarify.
How to trace this, if message is not getting pushed to ECC, I mean I have checked the trace in PI XSMB_MONI, but didn't get anything for this error. In ECC SXMB_moni only I am able to the timeout error.
Please expert help me as soon as you can, this error really effecting me badly in front of management
Thanks,
Farhan

Hi Hareesh,
I configured the scenario based on ICO, and again I received the same timeout error in ECC.
I am really sick with this error, and I have raised the OSS message to SAP. Meanwhile I just want to double check my entire configuration with you. Please see the below configuration (for classical) for ABAP proxy to HTTP_AAE, and let me know if anything is wrong.
Request structure (ECC->PI->Bank)
<?xml version='1.0' ?>
<PaymentInfoMessage>
<PaymentInfoRequest>
<CompanyCode>Partner01</CompanyCode>
<BankCode>BSFRSARI</BankCode>
<StartDate>2006-07-09T00:00:00</StartDate>
<EndDate>2006-07-09T00:00:00</EndDate>
<TransactionType>940</TransactionType>
</PaymentInfoRequest>
</PaymentInfoMessage>
Response Structure (Bank->PI->ECC)
<?xml version="1.0"?>
<PaymentInfoMessageResponse>
<PaymentInfoResponse>
    <TransactionType>940</TransactionType>
    <SequenceNum>1</SequenceNum>
    <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
    <ProcessStatus>1</ProcessStatus>
    <Comment>No Comment</Comment>
    <TransactionData>:20:MT940-1007200601
:25:3210000079901
:28C:190/0001
</TransactionData>
    <CompanyCode>PARTNER01</CompanyCode>
</PaymentInfoResponse>
<StatusCode>OK</StatusCode>
<StatusDetail>OK</StatusDetail>
<ResponseItemCount>2</ResponseItemCount>
</PaymentInfoMessageResponse>
ESR Configuration
Please see the below screenshot for ESR config. I have created 4 data types, 4 message types, 2 Service interface (synchronous), 2 mapping and one operation mapping.
I just want to clarify about selecting the Request and response message type in inbound and outbound service interface.
<?xml version='1.0' ?>
<PaymentInfoMessage>
<PaymentInfoRequest>
<CompanyCode>Partner01</CompanyCode>
<BankCode>BSFRSARI</BankCode>
<StartDate>2006-07-09T00:00:00</StartDate>
<EndDate>2006-07-09T00:00:00</EndDate>
<TransactionType>940</TransactionType>
</PaymentInfoRequest>
</PaymentInfoMessage>
Response Structure (Bank->PI->ECC)
<?xml version="1.0"?>
<PaymentInfoMessageResponse>
<PaymentInfoResponse>
    <TransactionType>940</TransactionType>
    <SequenceNum>1</SequenceNum>
    <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
    <ProcessStatus>1</ProcessStatus>
    <Comment>No Comment</Comment>
    <TransactionData>:20:MT940-1007200601
:25:3210000079901
:28C:190/0001
</TransactionData>
    <CompanyCode>PARTNER01</CompanyCode>
</PaymentInfoResponse>
<StatusCode>OK</StatusCode>
<StatusDetail>OK</StatusDetail>
<ResponseItemCount>2</ResponseItemCount>
</PaymentInfoMessageResponse>
ESR Configuration
I have simply created 2 data types for requests(ECC->PI->Bank) and did one to one mapping. Similarly for response(Bank->PI->ECC) 2 data types, one to one mapping for this as well.
But I just want to clarify about selecting the Request and response message type in inbound and outbound service interface. please explain me this for synchronous interface.
Please see the below structure from ESR and inbound and Outbound service and let me know if the selection of Request and response message types is correct or not.
OutBound service interface
Inbound service interface
Thanks,
Farhan

KEY and KEYREFs support on XML DB

First of all, sorry for my english but I am a spanish researcher who have not been abroad too much :-).
I�m trying to use XML DB to store XML documents that represents UML models and the way I've choosed to map relationships in my schema is using KEY and KEYREFs. The fact is that It seems to me that XML DB does not use them whem it creates the different objects that results on the schema's load. Does XMLDB support the definitons of KEYs and KEYREFs in the schema?? If so, how does it do?? Defining constraints oon the objects created?? I suppose no, because the KEYs and KEYREFs are defined on 'complexTypes' and the Oracle's constraints goes to tables (not to object types).
I'm worling with the next schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns="Kybele/MetaModel_Schema_All" targetNamespace="Kybele/MetaModel_Schema_All" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">



<xsd:element name="MetaModel" xdb:defaultTable="MMALL_METAMODELS_TABLE">
<xsd:complexType xdb:SQLType="MMALL_METAMODELS_TYPE">
<xsd:sequence>
<xsd:element name="ModelElements" type="ModelElement" maxOccurs="unbounded"/>
<xsd:element name="Dependencies" type="Dependency" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>



<xsd:key name="Dependency_PK">
<xsd:selector xpath="Dependencies"/>
<xsd:field xpath="Nombre"/>
</xsd:key>
<xsd:key name="ModelElement_PK">
<xsd:selector xpath="ModelElements"/>
<xsd:field xpath="Nombre"/>
</xsd:key>
<xsd:keyref name="Requirement_FK" refer="Dependency_PK">
<xsd:selector xpath="ModelElements"/>
<xsd:field xpath="requirement"/>
</xsd:keyref>
<xsd:keyref name="Provision_FK" refer="Dependency_PK">
<xsd:selector xpath="ModelElements"/>
<xsd:field xpath="provision"/>
</xsd:keyref>
<xsd:keyref name="Client_FK" refer="ModelElement_PK">
<xsd:selector xpath="Dependencies"/>
<xsd:field xpath="client"/>
</xsd:keyref>
<xsd:keyref name="Supplier_FK" refer="ModelElement_PK">
<xsd:selector xpath="Dependencies"/>
<xsd:field xpath="supplier"/>
</xsd:keyref>

<xsd:key name="Generalization_PK">
<xsd:selector xpath="Generalization"/>
<xsd:field xpath="Nombre"/>
</xsd:key>
<xsd:key name="GeneralizableElement_PK">
<xsd:selector xpath="GeneralizableElement"/>
<xsd:field xpath="Nombre"/>
</xsd:key>
<xsd:keyref name="Subtype_FK" refer="GeneralizableElement_PK">
<xsd:selector xpath="Generalization"/>
<xsd:field xpath="subtype"/>
</xsd:keyref>
<xsd:keyref name="Type_FK" refer="GeneralizableElement_PK">
<xsd:selector xpath="Generalization"/>
<xsd:field xpath="type"/>
</xsd:keyref>
<xsd:keyref name="Generalization_FK" refer="GeneralizableElement_PK">
<xsd:selector xpath="GeneralizableElement"/>
<xsd:field xpath="generalization"/>
</xsd:keyref>
<xsd:keyref name="Specilization_FK" refer="GeneralizableElement_PK">
<xsd:selector xpath="GeneralizableElement"/>
<xsd:field xpath="specialization"/>
</xsd:keyref>

<xsd:key name="Classifier_PK">
<xsd:selector xpath="Classifier"/>
<xsd:field xpath="Nombre"/>
</xsd:key>
<xsd:key name="AssociationEnd_PK">
<xsd:selector xpath="AssociationEnd"/>
<xsd:field xpath="Nombre"/>
</xsd:key>
<xsd:keyref name="AssociationEnd_FK" refer="AssociationEnd_PK">
<xsd:selector xpath="Classifier"/>
<xsd:field xpath="associationEnd"/>
</xsd:keyref>
<xsd:keyref name="Participant_FK" refer="AssociationEnd_PK">
<xsd:selector xpath="Classifier"/>
<xsd:field xpath="participant"/>
</xsd:keyref>
<xsd:keyref name="AssociationEnd_Type_FK" refer="Classifier_PK">
<xsd:selector xpath="AssociationEnd"/>
<xsd:field xpath="type"/>
</xsd:keyref>
<xsd:keyref name="AssociationEnd_Specification_FK" refer="Classifier_PK">
<xsd:selector xpath="AssociationEnd"/>
<xsd:field xpath="specification"/>
</xsd:keyref>

<xsd:keyref name="AttributeCompose_FK" refer="AssociationEnd_PK">
<xsd:selector xpath="Attribute"/>
<xsd:field xpath="associationEnd_member"/>
</xsd:keyref>

<xsd:keyref name="AssociationEndCompose_FK" refer="Association_PK">
<xsd:selector xpath="Association"/>
<xsd:field xpath="Association_member"/>
</xsd:keyref>
</xsd:element>


<xsd:simpleType name="AggregationType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="none"/>
<xsd:enumeration value="aggregate"/>
<xsd:enumeration value="composite"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="ScopeType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="instance"/>
<xsd:enumeration value="classifier"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="MultiplicityType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="0..1"/>
<xsd:enumeration value="1..1"/>
<xsd:enumeration value="0..N"/>
<xsd:enumeration value="1..N"/>
</xsd:restriction>
</xsd:simpleType>

<xsd:simpleType name="ChangeableType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="none"/>
<xsd:enumeration value="frozen"/>
<xsd:enumeration value="add_only"/>
</xsd:restriction>
</xsd:simpleType>


<xsd:complexType name="ModelElement" xdb:SQLType="MMALL_ModelElement_Type">
<xsd:sequence>
<xsd:element name="nombre" type="xsd:string"/>

<xsd:element name="requirement" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="provision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="Dependency" xdb:SQLType="MMALL_Dependency_Type">
<xsd:complexContent>
<xsd:extension base="ModelElement">
<xsd:sequence>
<xsd:element name="description" type="xsd:string"/>

<xsd:element name="client" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="supplier" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="Generalization" xdb:SQLType="MMALL_Generalization_Type">
<xsd:complexContent>
<xsd:extension base="ModelElement">
<xsd:sequence>
<xsd:element name="discriminator" type="xsd:string"/>

<xsd:element name="subtype" type="xsd:string"/>
<xsd:element name="supertype" type="xsd:string"/>

</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="NameSpace" xdb:SQLType="MMALL_NameSpace_Type">
<xsd:complexContent>
<xsd:extension base="ModelElement"/>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="GeneralizableElement" xdb:SQLType="MMALL_GeneralizableElement_Type">
<xsd:complexContent>
<xsd:extension base="NameSpace">
<xsd:sequence>
<xsd:element name="isRoot" type="xsd:boolean"/>
<xsd:element name="isLeaf" type="xsd:boolean"/>
<xsd:element name="isAbstract" type="xsd:boolean"/>

<xsd:element name="generalization" type="xsd:string"/>
<xsd:element name="specification" type="xsd:string"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="AssociationEnd" xdb:SQLType="MMALL_ASSOCIATIONEND_TYPE">
<xsd:complexContent>
<xsd:extension base="ModelElement">
<xsd:sequence>
<xsd:element name="IsNavigable" type="xsd:boolean"/>
<xsd:element name="IsOrdered" type="xsd:boolean"/>
<xsd:element name="Aggregation" type="AggregationType"/>
<xsd:element name="Multiplicity" type="MultiplicityType" minOccurs="0"/>
<xsd:element name="Changeable" type="ChangeableType"/>
<xsd:element name="TargetScope" type="ScopeType"/>

<xsd:element name="Qualifier" type="Attribute" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Association_member" type="xsd:string"/>
<xsd:element name="Type" type="xsd:string"/>
<xsd:element name="Specification" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="Classifier" xdb:SQLType="MMALL_CLASSIFIER_TYPE">
<xsd:complexContent>
<xsd:restriction base="GeneralizableElement">
<xsd:sequence>

<xsd:element name="AssociationEnd" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="Participant" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="Class" xdb:SQLType="MMALL_CLASS_TYPE">
<xsd:complexContent>
<xsd:extension base="Classifier"/>
</xsd:complexContent>
</xsd:complexType>

<xsd:complexType name="Attribute" xdb:SQLType="MMALL_ATTRIBUTE_TYPE">
<xsd:sequence>
<xsd:element name="associationEnd_member" type="xsd:string" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="Association" xdb:SQLType="MMALL_ASSOCIATION_TYPE">
<xsd:complexContent>
<xsd:restriction base="GeneralizableElement">
<xsd:sequence>
<xsd:element name="connection" type="AssociationEnd" minOccurs="2" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
and when I try to load it into XMLDB it fails:
SQL> @registerSchema oe oe /home/OE/Metamodel_Schema_All.xsd "http://kybele.escet.urjc.es/ejemplos/x
ml_schema/Metamodel_Schema_All.xsd"
SQL> set echo on
SQL> connect &1/&[email protected]
Conectado.
SQL> alter session set events='31098 trace name context forever';
Sesi�n modificada.
SQL> begin
2 dbms_xmlschema.registeruri(
3 '&4',
4 '&3',
5 TRUE,TRUE,FALSE,TRUE);
6 end;
7 /
antiguo 3: '&4',
nuevo 3: 'http://kybele.escet.urjc.es/ejemplos/xml_schema/Metamodel_Schema_All.xsd',
antiguo 4: '&3',
nuevo 4: '/home/OE/Metamodel_Schema_All.xsd',
begin
ERROR en l�nea 1:
ORA-31154: invalid XML document
ORA-19202: Se ha producido un error en el procesamiento
LPX-00217: invalid character 0 (\u0000) de XML
ORA-06512: en "XDB.DBMS_XMLSCHEMA_INT", l�nea 0
ORA-06512: en "XDB.DBMS_XMLSCHEMA", l�nea 166
ORA-06512: en l�nea 2
it says.
I have done several attempts, deleting and including just some of the KEYs/KEYREFs in the schema and it seems to me that the problem is that it let me include so much keys as I want but it fails when the number of KEYREFs that I include increase.
Help!!!
Thanks on advance for spare your time helping us.

Looks like known bug 2831302 fixed in (forthcoming) 10g release. In the mean time I would simply comment the key/keyref out of the schema

KEY and KEYREF support in Oracle XML DB

First of all, sorry for my english but I am a spanish researcher who have not been abroad too much :-).
I�m trying to use XML DB to store XML documents that represents UML models and the way I've choosed to map relationships in my schema is using KEY and KEYREFs. The fact is that It seems to me that XML DB does not use them whem it creates the different objects that results on the schema's load. Does XMLDB support the definitons of KEYs and KEYREFs in the schema?? If so, how does it do?? Defining constraints oon the objects created?? I suppose no, because the KEYs and KEYREFs are defined on 'complexTypes' and the Oracle's constraints goes to tables (not to object types).
I'm worling with the next schema:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns="Kybele/MetaModel_Schema_All" targetNamespace="Kybele/MetaModel_Schema_All" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
     
     
     
     <xsd:element name="MetaModel" xdb:defaultTable="MMALL_METAMODELS_TABLE">
          <xsd:complexType xdb:SQLType="MMALL_METAMODELS_TYPE">
               <xsd:sequence>
                    <xsd:element name="ModelElements" type="ModelElement" maxOccurs="unbounded"/>
                    <xsd:element name="Dependencies" type="Dependency" maxOccurs="unbounded"/>
               </xsd:sequence>
          </xsd:complexType>
     
     
          
          <xsd:key name="Dependency_PK">
               <xsd:selector xpath="Dependencies"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:key name="ModelElement_PK">
               <xsd:selector xpath="ModelElements"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:keyref name="Requirement_FK" refer="Dependency_PK">
               <xsd:selector xpath="ModelElements"/>
               <xsd:field xpath="requirement"/>
          </xsd:keyref>
          <xsd:keyref name="Provision_FK" refer="Dependency_PK">
               <xsd:selector xpath="ModelElements"/>
               <xsd:field xpath="provision"/>
          </xsd:keyref>
          <xsd:keyref name="Client_FK" refer="ModelElement_PK">
               <xsd:selector xpath="Dependencies"/>
               <xsd:field xpath="client"/>
          </xsd:keyref>
          <xsd:keyref name="Supplier_FK" refer="ModelElement_PK">
               <xsd:selector xpath="Dependencies"/>
               <xsd:field xpath="supplier"/>
          </xsd:keyref>
          
          <xsd:key name="Generalization_PK">
               <xsd:selector xpath="Generalization"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:key name="GeneralizableElement_PK">
               <xsd:selector xpath="GeneralizableElement"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:keyref name="Subtype_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="Generalization"/>
               <xsd:field xpath="subtype"/>
          </xsd:keyref>
          <xsd:keyref name="Type_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="Generalization"/>
               <xsd:field xpath="type"/>
          </xsd:keyref>
          <xsd:keyref name="Generalization_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="GeneralizableElement"/>
               <xsd:field xpath="generalization"/>
          </xsd:keyref>
          <xsd:keyref name="Specilization_FK" refer="GeneralizableElement_PK">
               <xsd:selector xpath="GeneralizableElement"/>
               <xsd:field xpath="specialization"/>
          </xsd:keyref>
          
          <xsd:key name="Classifier_PK">
               <xsd:selector xpath="Classifier"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:key name="AssociationEnd_PK">
               <xsd:selector xpath="AssociationEnd"/>
               <xsd:field xpath="Nombre"/>
          </xsd:key>
          <xsd:keyref name="AssociationEnd_FK" refer="AssociationEnd_PK">
               <xsd:selector xpath="Classifier"/>
               <xsd:field xpath="associationEnd"/>
          </xsd:keyref>
          <xsd:keyref name="Participant_FK" refer="AssociationEnd_PK">
               <xsd:selector xpath="Classifier"/>
               <xsd:field xpath="participant"/>
          </xsd:keyref>
          <xsd:keyref name="AssociationEnd_Type_FK" refer="Classifier_PK">
               <xsd:selector xpath="AssociationEnd"/>
               <xsd:field xpath="type"/>
          </xsd:keyref>
          <xsd:keyref name="AssociationEnd_Specification_FK" refer="Classifier_PK">
               <xsd:selector xpath="AssociationEnd"/>
               <xsd:field xpath="specification"/>
          </xsd:keyref>
          
          <xsd:keyref name="AttributeCompose_FK" refer="AssociationEnd_PK">
               <xsd:selector xpath="Attribute"/>
               <xsd:field xpath="associationEnd_member"/>
          </xsd:keyref>
          
          <xsd:keyref name="AssociationEndCompose_FK" refer="Association_PK">
               <xsd:selector xpath="Association"/>
               <xsd:field xpath="Association_member"/>
          </xsd:keyref>
     </xsd:element>
     
     
     <xsd:simpleType name="AggregationType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="none"/>
               <xsd:enumeration value="aggregate"/>
               <xsd:enumeration value="composite"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="ScopeType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="instance"/>
               <xsd:enumeration value="classifier"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="MultiplicityType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="0..1"/>
               <xsd:enumeration value="1..1"/>
               <xsd:enumeration value="0..N"/>
               <xsd:enumeration value="1..N"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     <xsd:simpleType name="ChangeableType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="none"/>
               <xsd:enumeration value="frozen"/>
               <xsd:enumeration value="add_only"/>
          </xsd:restriction>
     </xsd:simpleType>
     
     
     <xsd:complexType name="ModelElement" xdb:SQLType="MMALL_ModelElement_Type">
          <xsd:sequence>
               <xsd:element name="nombre" type="xsd:string"/>
               
               <xsd:element name="requirement" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
               <xsd:element name="provision" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="Dependency" xdb:SQLType="MMALL_Dependency_Type">
          <xsd:complexContent>
               <xsd:extension base="ModelElement">
                    <xsd:sequence>
                         <xsd:element name="description" type="xsd:string"/>
                         
                         <xsd:element name="client" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                         <xsd:element name="supplier" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:extension>
          </xsd:complexContent>
     </xsd:complexType>
     
     <xsd:complexType name="Generalization" xdb:SQLType="MMALL_Generalization_Type">
          <xsd:complexContent>
               <xsd:extension base="ModelElement">
                    <xsd:sequence>
                         <xsd:element name="discriminator" type="xsd:string"/>
                         
                         <xsd:element name="subtype" type="xsd:string"/>
                         <xsd:element name="supertype" type="xsd:string"/>
                         
                    </xsd:sequence>
               </xsd:extension>
          </xsd:complexContent>
     </xsd:complexType>
     
     <xsd:complexType name="NameSpace" xdb:SQLType="MMALL_NameSpace_Type">
          <xsd:complexContent>
               <xsd:extension base="ModelElement"/>
          </xsd:complexContent>
     </xsd:complexType>
     
     <xsd:complexType name="GeneralizableElement" xdb:SQLType="MMALL_GeneralizableElement_Type">
          <xsd:complexContent>
               <xsd:extension base="NameSpace">
                    <xsd:sequence>
                         <xsd:element name="isRoot" type="xsd:boolean"/>
                         <xsd:element name="isLeaf" type="xsd:boolean"/>
                         <xsd:element name="isAbstract" type="xsd:boolean"/>
                         
                         <xsd:element name="generalization" type="xsd:string"/>
                         <xsd:element name="specification" type="xsd:string"/>
                    </xsd:sequence>
               </xsd:extension>
          </xsd:complexContent>
     </xsd:complexType>
     
     <xsd:complexType name="AssociationEnd" xdb:SQLType="MMALL_ASSOCIATIONEND_TYPE">
     <xsd:complexContent>
          <xsd:extension base="ModelElement">
               <xsd:sequence>
                    <xsd:element name="IsNavigable" type="xsd:boolean"/>
                    <xsd:element name="IsOrdered" type="xsd:boolean"/>
                    <xsd:element name="Aggregation" type="AggregationType"/>
                    <xsd:element name="Multiplicity" type="MultiplicityType" minOccurs="0"/>
                    <xsd:element name="Changeable" type="ChangeableType"/>
                    <xsd:element name="TargetScope" type="ScopeType"/>
                    
                    <xsd:element name="Qualifier" type="Attribute" minOccurs="0" maxOccurs="unbounded"/>
                    <xsd:element name="Association_member" type="xsd:string"/>
                    <xsd:element name="Type" type="xsd:string"/>
                    <xsd:element name="Specification" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
               </xsd:sequence>
          </xsd:extension>
     </xsd:complexContent>
     </xsd:complexType>
     
     <xsd:complexType name="Classifier" xdb:SQLType="MMALL_CLASSIFIER_TYPE">
          <xsd:complexContent>
               <xsd:restriction base="GeneralizableElement">
                    <xsd:sequence>
                         
                         <xsd:element name="AssociationEnd" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                         <xsd:element name="Participant" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:restriction>
          </xsd:complexContent>
     </xsd:complexType>
     
     <xsd:complexType name="Class" xdb:SQLType="MMALL_CLASS_TYPE">
          <xsd:complexContent>
               <xsd:extension base="Classifier"/>
          </xsd:complexContent>
     </xsd:complexType>
     
     <xsd:complexType name="Attribute" xdb:SQLType="MMALL_ATTRIBUTE_TYPE">
          <xsd:sequence>
               <xsd:element name="associationEnd_member" type="xsd:string" minOccurs="0" maxOccurs="1"/>
          </xsd:sequence>
     </xsd:complexType>
     
     <xsd:complexType name="Association" xdb:SQLType="MMALL_ASSOCIATION_TYPE">
          <xsd:complexContent>
               <xsd:restriction base="GeneralizableElement">
                    <xsd:sequence>
                         <xsd:element name="connection" type="AssociationEnd" minOccurs="2" maxOccurs="unbounded"/>
                    </xsd:sequence>
               </xsd:restriction>
          </xsd:complexContent>
     </xsd:complexType>
</xsd:schema>
and when I try to load it into XMLDB it fails:
SQL> @registerSchema oe oe /home/OE/Metamodel_Schema_All.xsd "http://kybele.escet.urjc.es/ejemplos/x
ml_schema/Metamodel_Schema_All.xsd"
SQL> set echo on
SQL> connect &1/&[email protected]
Conectado.
SQL> alter session set events='31098 trace name context forever';
Sesi�n modificada.
SQL> begin
2 dbms_xmlschema.registeruri(
3 '&4',
4 '&3',
5 TRUE,TRUE,FALSE,TRUE);
6 end;
7 /
antiguo 3: '&4',
nuevo 3: 'http://kybele.escet.urjc.es/ejemplos/xml_schema/Metamodel_Schema_All.xsd',
antiguo 4: '&3',
nuevo 4: '/home/OE/Metamodel_Schema_All.xsd',
begin
ERROR en l�nea 1:
ORA-31154: invalid XML document
ORA-19202: Se ha producido un error en el procesamiento
LPX-00217: invalid character 0 (\u0000) de XML
ORA-06512: en "XDB.DBMS_XMLSCHEMA_INT", l�nea 0
ORA-06512: en "XDB.DBMS_XMLSCHEMA", l�nea 166
ORA-06512: en l�nea 2
it says.
I have done several attempts, deleting and including just some of the KEYs/KEYREFs in the schema and it seems to me that the problem is that it let me include so much keys as I want but it fails when the number of KEYREFs that I include increase.
Help!!!
Thanks on advance for spare your time helping us.

Please post this message at:
Forums Home » Oracle Technology Network (OTN) » Products » Database » XML DB

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

Estrutura de envio do ECC para XML 2.0

Similar Messages

Maybe you are looking for