GRC Inbound - setar step POASSIGN manualmente

Bom dia Pessoal,
Preciso de uma ajuda, alguém sabe se é possível setar o step POASSIGN do GRC Inbound para Definido como OK manualmente?
Pergunto isso porque a solução aqui do projeto é que alguns passos do processo que o GRC faz sejam feitos por um desenvolvimento ABAP no ECC,que irá gerar uma série de workflows para áreas responsáveis em caso de erro..
Exatamente isso:
Para compras normais:
1.SIGNATUR (Auto)
Checagem da assinatura  (EXECUTADO PELO GRC)
2.AUTHORIZ (Auto)
Checagem da autorização na SEFAZ (EXECUTADO PELO GRC)
3.NPURVALD (Auto)
Validação de processo normal (EXECUTADO PELO GRC)
4.POASSIGN (Auto) (NESSE MOMENTO HÁ INTEGRAÇÃO ENTRE GRCxECC PARA QUE O STEP SEJA EXECUTADO PELO DESENVOLVIMENTO ABAP NO ECC)
Associação do pedido ao XML
5.NFESIMUL (TAMBÉM EXECUTADO PELO DESENVOLVIMENTO ABAP NO ECC)
Simulação da nota
6.DELCREAT (Auto) (TAMBÉM EXECUTADO PELO DESENVOLVIMENTO ABAP NO ECC E APÓS OK, RETORNA UM STATUS AO GRC QUE OS 3 PASSOS FORAM EXECUTADOS COM SUCESSO, NESSE MOMENTO  OS 3 PASSOS POASSIGN, NFESIMUL E DELCREAT DEVEM SER SETADOS OK MANUALMENTE NO GRC PARA DAR SEGUIMENTO NO PROCESSO, PORÉM LOGO NO PRIMEIRO PASSO POASSIGN JA NÃO FOI POSSIVEL SETA-LO, APARENTEMENTE ELE OBRIGA QUE ENTRE COM UM NR. DE PEDIDO PARA A ATRIBUIÇÃO, É ISSO MESMO?)
Pensei em usar o processo flexível FLEXPR01, porém afetaria os passos do monitor logístico que estão contemplados no processo normal,(GRCONFQU,.GRFICHCK e GRMMCHCK)
Há alguma outra saída?
Obrigado pela ajuda,
DANIEL

Olá Eduardo,
Desculpe pela demora em dar um feedback.
Atualizando a questão, acabamos por adotar o processo Flexível mesmo, deixando a parte de verificações de quantidade a cargo do sistema ABAP aqui da integração.
Respondendo suas perguntas
porque destes desenvolvimentos?
O cliente decidiu adquirir uma ferramenta desenvolvida em ABAP que irá controlar os passos que citei e gerar Workflows para as áreas responsáveis em caso de erros, esse seria o motivo principal dessa solução.
O que vocês irão fazer? Como irão fazer?
Iremos utilizar como ponto da integração as BADIs flexíveis, método before_danfe para o momento de atrib. de pedido até a geração da inbound delivery. e método after_danfe após a entrada da chave de acesso até a geração da MIRO
Obrigado pela ajuda,
Daniel

Similar Messages

  • [GRC Inbound]Criação da remessa atualizar a identificacao do transporte

    Bom dia a todos!
    Gostaria de pedir, por favor, se alguém já precisou atualizar a identificação do transporte (LIKP-TRAID) na criação da remessa a partir do GRC Inbound utilizando a tag <placa> do xml de entrada (layout 3.10), se sim, há alguma BADi que permite isso?
    Eu implementei a BADi 'Determination of Custom UI for Logistics Workplace for Inbound NF-es' conforme SAP note 2038967. No entanto, nesse momento a ordem de fornecimento já está criada e eu preciso  que seja atribuído a placa do veiculo na criação da remessa, porque o veiculo precisa da ordem de descarga (impressa automaticamente) que segue o veiculo até o ponto de descarga e nesse doc. é obrigatório a placa.
    Obrigada.
    Patrícia

    Boa tarde Patricia,
    Pelo standard não tem como, já que a informação da placa não é repassada para o ECC no momento da criação da Inbound Delivery no ECC. O que pode ser feito é:
    Cenário 1: Você criaria a Inbound Delivery antes da execução do step DELCREAT do GRC (via implicit enhancement-point no começo da função /XNFE/PROCSTEP_NFE_DELCREAT c/ uma chamada RFC p/ o ECC, fazendo a criação via BAPI/FM), já com os dados da placa (TRAID), como se fosse um processo externo criando a Delivery e implementaria a BAdI J_1BNFE_IN método INBOUND_DELIV_SEARCH, para indicar que neste passo a Delivery já foi criada e que o número dela é X;
    Cenário 2: Você implementaria um implicit enhancement point na função /XNFE/PROCSTEP_NFE_DELCREAT, no final do módulo de função, chamando uma RFC Z do ECC, que seria a responsável por fazer a atualização da Inbound Delivery com o TRAID. Como não achei BAPI que fizesse a atualização da inbound delivery com os campos necessários, sugiro ou utilizar um BATCH INPUT ou o não recomendado update na likp.
    []'s
    JN

  • U00EFu00BBu00BF  -these chars why they are appearing the inbound message step in moni

    when i am testing the file-to-proxy scenario, by placing a proper xml file in the outbound directory,
    it is failing in the xml-validation step.
    in the moni, when i see the payload of the the Inbound Message step, i see
    <?xml version="1.0" encoding="utf-8"?>
    Invalid at the top level of the document. Error processing resource 'file:///C:/Documents and Settings/i053295/Local Settin...
    <?xml version="1.0" encoding="utf-8"?>
    My question is: why the chars  are getting appeared in the inbound message, but i checked the actual input xml file, opened in notepad, editplus etc, it does not contain those chars.

    Hi,
    Try to open the input file with textpad or wordpad.You can find the space or some etc char in the file.
    Thanks.
    Regards,
    Indira D

  • ALE Inbound Cofiguration Steps needed

    Hi friends,
    kindly send me ALE Inbound Configuration Steps with all the Mandatory settings that need to be done
    Thanks in Advance
    Ganesh

    Outbound:
    Step 1. Application document is created when transaction is saved.
    2. Message control is invoked.
    3. Messages are processed by system.
    4. Messages are Edited (if desired).
    5. Output (ALE / EDI) is checked
    6. Validate against Message control record from Partner Profile
    7. Application Document is saved.
    8. Entry NAST table is created for every selected output program
    along with Medium & Timing.
    9. Check for Process Immediately .
    If (yes)
    Determine Processing Program from TNAPR Table.
    ELSE
    Execute RSNASTED Program.
    10. Read Partner Profile to determine Process Code.
    11. Process Code points to the Function Module & Invoked.
    12. IDoc is generated.
    13. Check for ALE Request.
    if (Yes)
    Perform Filters, Conversions, Version Changes etc.
    Else.
    IDoc is stored in DATABASE.
    INBOUND:
    Step 1. EDI Subsystem creates an IDoc file from EDI Messages
    2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
    3. Data in Control Record is validate against the Partner Profile.
    4. IDoc is generated in Database and syntax check is carried out.
    5. IDoc file is deleted once file read.
    6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
    7. Check for Process Immediately.
    If NO
    Execute RBDAPP01 Program
    Else
    Read Process Code from Partner Profile
    Process Code Points to Function Module
    Application Document Posted.
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Reward points for useful Answers

  • GRC system validation steps

    Hi, Please check and provide GRC system validation steps in serial. I am looking for the serial steps which we need to follow while validating GRC system after applying support packs or upgrade etc. Appreciate your feedback. Thanks & Regards, Koteswara Rao.

    Hello Gurus,
    I too am looking for similar information so I am posting my question in the same thread.
    I was going through the GRC 5.3 sizing guide for figuring out the hardware requirement for RAR. We wanted to go with the expert sizing of RAR. Expert sizing takes into account the factors such as no.of users, roles and violations. I thought we can easily figure out the no.of roles and no.of users but how do I estimate "Number of SOD Violations"? Please advice..
    @ Sanjay,
    I will just outline of what we did so far..hope this might help you
    Here at our company, we started off by 1) buying the GRC access control suite, 2) deciding what components within GRC will be implemented first. 3) systems (ECC, BI, etc) in scope
    4) System landscape (Dev and Test will be on one box, Prod will be on another box)
    5) Sizing based on systems in scope
    6) Decide whether to install on existing Solman or install on a new box...(bcos all that GRC 5.3 needs is NW04s Java stack)
    7) Buy hardware based on sizing, Install NW
    and so on...
    Thanks in advance for your input...
    regards,
    Venkateswara Rao

  • GRC Inbound - Base de cálculo PIS/COFINS

    Boa tarde!
    Como existe uma tolerância mínima entre o XML do fornecedor e o pedido de compra de R$ 0,02, os usuários solicitaram que este limite fosse alterado para R$ 10,00 (além das tolerâncias que já estão cadastradas na OMR6). Criamos um enhancement para buscar estes dados através de uma variável.
    O problema ocorreu no lançamento da fatura, que utilizou como base de cálculo para PIS/COFINS os valores do pedido de compra e não do XML, gerando um lançamento com bases divergentes entre os impostos (para ICMS e IPI buscou corretamente do XML).
    Eu verifiquei em outro post que os dados do XML para PIS/COFINS são descartados, mas gostaríamos que a base de cálculo fosse a mesma do XML e as taxas fossem do pedido de compra.
    Alguém já passou por este problema?
    Muito obrigada!
    Cristiane

    Olá Helio!
    Na pricing a condição que representa o valor do icms é a ICM3. No nosso cenário também temos a incidência do IPI, e o cálculo da base do ICMS é:
    Valor produtos + Frete + IPI, ou seja, para esse cenário, não podemos utilizar esta condição para determinar o nível do PIS e COFINS.
    Alterei o nível da condição para uma outra linha, que tem o valor correto que precisamos, porém ainda assim, ele continua utilizando a base 107,00 (preço + frete).   Na linha do Cofins, a pricing utiliza fórmula base standard 801 e na linha do  Pis a fórmula base, também standard é a 803. 
    O que está determinando a base das condições PIS e COFINS são estas fórmulas e não a configuração do nível. Se retirar esta fórmula da certo Porém como é fórmula standard, não gostaria de fazer isso. Sabe se tem alguma nota que corrja este problema?
    Tks,
    Kelem

  • CTE Inbound com LES (CTEINBLE)

    Oi pessoal.
    Estou tentando ativar o processo de entrada de CT-E com LES para compras (Processo CT-E inbound CTEINBLE).
    Ao verificar a documentação da SAP no step 4 - Provide LES Documents Through BAdI (Technical name: CTEILFCD) é mencionado que ao final dessa etapa o sistema reque uma
    folha de registro de serviço para o frete.
    Porém, para processos de compra utilizando custo complementar de aquisição, o LES não gera pedido de compra de frete nem folha de serviço. A MIRO do frete deve ser feita no próprio pedido de compra de mercadoria.
    Alguém já ativou esse processo do CT-E inbound? Funciona com custo complementar de aquisição?
    Obrigado, abraços.
    Documentação da SAP mencionada:
    http://help.sap.com/saphelp_nfe10/helpdata/en/19/627f51fdbe9302e10000000a44538d/content.htm?frameset=/en/19/627f51fdbe9302e10000000a44538d/frameset.htm&current_toc=/en/51/5b7271095c4fe1b3c1cc9f4b7d13c3/plain.htm&node_id=181&show_children=true#jump181

    Bom dia Bernardo,
    Evite postar em threads já respondidas, é muita mais claro se sua questão é iniciada por você.
    Se quiser chamar atenção de outra pessoa você pode usar o Claudia Wada por exemplo mas evite fazer a pergunta a uma pessoa específica, tem tantos colegas com conhecimento para responder.
    Separei a questão de GRC Inbound com LES - Validação de CNPJ do tomador de frete - CTEOUTLE em uma nova, favor acompanhá-la.
    Atenciosamente, Fernando Da Rós
    Message was edited by: Fernando Ros

  • Inbound function module !

    How to analyze an inbound idoc function module  ?

    Hi,
    You may put a break point in the inbound FM, and use transaction WE19 to debug your inbound FM step by step.
    Hope it helps,
    Chang

  • Unable to see a column of a table in portal for a particular User

    Hi,
    A particular user is unable to see a particular column of a table in the portal . The application is developed in Webdynpro ABAP. The table contains two columns. Both the columns contain text type fields. What appears to the user is that the left column has disappeared and the right hand column has shifted to the left.
    This is occuring for a particular user only. We have checked in our development and quality systems but we are unable to replicate the issue. Please help.
    Thanks and regards,
    Satya.

    Hi Vikas.
    You can use BAPI in LSMW to craete Material or You can use direct input method. Both methods as follows below:
    Using BAPI in LSMW:
    First maintain IDOC Inbound Processing steps by giving PORT and Partner Type and Partner Numberby clicking 'settings' icon in menu path in LSMW Screen.
    Adn then execute LSMW and maintain the values as below in the first step.
    BusinessObject Method(BAPI)
    Business Object       BUS1001006                      Standard material
    Method                     SAVEDATA                        Create and change materia
    Message Type         MATMAS_BAPI                   Create and change materia
    Basic Type               MATMAS_BAPI03               Create and Change Materia.
    For the selecting of views, you can maintain fields for all views(From Basic view to costing view) in your excel and populate with 'X' in respective fields for activating views.
    In the 6th step (Maintain field mapping and conversion rules). you can map those fields for views which you want to activate since we have all views are in the standard structure.
    Using Direct Input Method:
    Standard Batch/Direct Input
    Object                      0020                                             Material master
    Method                     0000
    Program Name          RMDATIND
    Program Type           D                                                  Direct Input
    For the selecting of views, you can maintain fields for all views(From Basic view to costing view) in your excel and populate with 'X' in respective fields for activating views.
    In the 6th step (Maintain field mapping and conversion rules). you can map those fields for views which you want to activate since we have all views are in the standard structure.

  • Issue in Iodc- abap proxy scenario

    Hi all
    I have a idoc to abap proxy scenario. The issue is ,
    when we send the idoc to client A of target system, it works ifne.
    But when we send the saem mesage to Client B, we find a error message in sxmb_moni of Target system. the mesage is Application_fault.
    Is it because of any error in XI configuration or somethin else.

    hi all
    thanks for all your responses.
    I forgot to mention that based on a particualr field value in the idoc , it will be routed to eihter Client 100 or 200 .
    I gave the conditions in Receiver Determination.
    Same Server Proxy  is used in both the target business sytems.
    I have done all the Configuration Steps ,( Created two separate business systems also )
    Also I have checked wiht all the system settings to be made in the target system B.
    When i trigger the idoc to Client 100, it goes to XI and then reaches  Client 100 of System B
    without any problem. I get the desired result from proxy code.
    When i send the saem idoc to Client 200, it reaches the target system and routed to client 200. But getting this error message in
    the Call Inbound PRoxy step. (from sxmb_moni)
    <SAP:Category>Application</SAP:Category>
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
    Since it reaches the target system correctly, i guess there is nothing wrong in the XI configuration side.
    But if its Application fault, how come the same data is processed successfully in one client whereas it thorws error in another.

  • SAP R/3 -- PI -- Oracle DB SYNC (JDBC)

    What is the best approach to handle the following request:
    We need to develop a synchonous call that will pass information from SAP R/3 through PI to an Oracle database can return the data.
    For instance, we want to pass a material number from SAP R./3, and have all the related information stored in the Oracle DB returned immediately.
    The data stored in Oracle will be retrieved via a JDBC connection.   If possible can you provide an example....thx

    >> Just a simple query, no updating is required.
    >>>  select f1 f2 f3....from ms_tbl where part = inbound-part
    Then you dont need sql stored procedure . We can easily handle at pi side.
    Step 1) create data type for proxy as per your need
    Step 2)  Create the data type for  jdbc request side as similar below ...
    <stmt>
        <Customers action="SQL_QUERY">
          <access> SELECT f1,f2,f3 from ms_tbl  WHERE PART ='$KEYFIELD$';</access>
          <key>
              <KEYFIELD>inbound-part</KEYFIELD>
          </key>
        </Customers>
      </stmt>
    Note: use constant to populate values for action and access field in mapping area.
    Step 3)
    create data type for the  jdbc response side as below
    <stmt_response>
    <row>
    <f1>
    <f2>
    <f3>
    </row>
    </stmt_response>
    Step 4)
    Then create Proxy response data type
    Step 5) create message types and Service Interface.(outbound synchronous and inbound synchronous)
    step 6)first map: Map step 1 messg type with step2 mesg type
    step 7) second map:  Map step 3 mesg type to step 4 mesg type
    Integration Directory: configure Jdbc reciever. Rest are all same.
    That's  it.
    Please follow this link ...
    Jdbc structure :
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
    Jdbc configure (comm channel)
    http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm

  • ERROR in  XI TO BI INTEGRATION

    Hi all
    i am doing XI to BI configuration as per given in "HOW TO GUIDE" of SAP
    my scenario is JDBC(SQL) to     BI (ABAP proxy)
    i am picking data from SQL datbase table and sending to BI
    source structure is as follows:
    DT_Sender
         DATA              1:unbounded
              Currency     1:1
               Material      1:1
    Target structure RFC
    /BIC/CCUSTDATA
            DATA             0:unbounded
                Currency    1:1
                Material      1:1
    if i send the data through testing tool in RWB then it goes successful in XI and data come in BI
    if i send the data from database table using JDBC adapter then it went  succesful in XI and data replicates but while i check in BI side through SXMB_MONI it shows chequered flag but while checking paylaod inside the message it does not replicate the data
    any body plz give your inputs how the data can come coorectly in BI message payload
    Thanks
    sandeep sharma

    Hi All
    as per suggested by Vijaya
    i have switched on logging by putting parameter 1
    now i can see in the sxmb_moni following pipelinesteps
    Inbound Message ( CENTRAL )
    Receiver Identification
    Interface Determination
    Receiver Grouping
    Message Branch According to Receiver List
    Request Message Mapping
    Technical Routing
    calladapter
    response
    i can see payload in each step which is fine, starting from inbound message step to Message Branch According to Receiver List step,
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:MT_Sender xmlns:ns0="http://groupsoft.in/XIBITEST">
    - <row>
      <CURRENCY>dgs</CURRENCY>
      <MATERIAL>sxdfgs</MATERIAL>
      <STATUS />
      </row>
      </ns0:MT_Sender>
    while in the next step Request Message Mapping i can see in the payload
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:_-BIC_-CFCUSTDATA xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
      <DATA />
      </ns1:_-BIC_-CFCUSTDATA>
    that means my data is not reflecting on the receiver side
    source structure is as follows:
    MT_Sender       1:1
    row            1:unbounded
        Currency    1:1
        Material    1:1
    Target structure RFC
    /BIC/CCUSTDATA      1:1
        DATA            1:1
          item          0:unbounded
             Currency   1:1
             Material   1:1
    can anybody suggest me in this regards what change should i do to reflect accurate data in receiver side
    Thanks
    sandeep

  • XI to BW scenario

    Hi all,
    I have to make a scenario that pushes data from Xi to BW. I have found one PDF that includes all the steps. My question is before following these steps do we need to make some changes in our SLD or what are the prerequisites to onfigure such a scenario as the same is not very clear in the PDF.
    Regards...

    Note the steps below:
    Step 1.Logon to the BI server and type transaction code SM59, then go to HTTP to           R/3 Connections and check the RFC Destination for XI system and test the connection .It should give status: ok.
    Step 2.Goto Transaction RZ70 and give the host and system gateway id and exexcute the transaction, so that it will automatically create the Technical System for BW system in SLD.
    Step 3.Define Business System for BW System in SLD and assign it to above defined Technical system. So, now we have Receiver system for the target.
    Now we are ready for the configuration in Repository and Builder
    Define the namespace in a software component version and save it.
    Integration Repository
    Step 1.Create Source Data structure which is termed as Data Type in XI.
    Step 2. Create Target Data Structure
    Here in order to simply the scenario we have taken same structure as target structure so message mapping is one to one.
    Step 3. Create Message Types
    Step 4. Create Sender Message Interface
               This message Interface is Outbound Asynchronous
    Step 5. Create Receiver Message Interface (Inbound Asynchronous)
    Step 6. Create Message Mapping between Sender structure and Receiver Structure
    Step 7. Create Interface Mapping to call the message mapping at runtime
    Now, Integration Repository part has been finished.
    Do Configuraion in ID.
    REgards,
    Anurag garg

  • Problem in Extended Idoc

    Hi All,
    I have Extended ORDERS05 for adding custom fields for inbound process,
    Steps i have fallowed to create Extend Idoc:
    1,Created new segment with all Z-fields and released,
    2,Created Extension Idoc with reference standard Idoc ORDER05, and added custom segment under standard segment E1EDP01,
    released Extend Idoc,
    am able to see all Z-fields in Z-segment,
    but my problem is am unable to see any standard fields under any standard segment in my Extended Idoc?
    why am not able to see all standard fileds?
    Regards
    suresh.d

    Hi,
    Are you checking in WE30 or in WE02?
    In WE30 you cans ee only Segment names.
    Give the segment name in SE11 and then see if you are able to see the fields.
    Regards,
    Sravan

  • Confirmation Control Process Flow

    My Dear Gurus,
    I want to know the actual confirmation control process in material manangement. Becoz of one of my client having the following scenerios.
    PO is created only by PR reference with confirmation tab enabling in po. Once he created the PO again he come back to change mode in PO and enable the confimation control (0001) and the confirmation category as AB.
    Once the vendor is received the PO and the delivery date is accepted by vendor and he manually over phone tell the final delivery date.
    So our client wants to update the final delivery date given by vendor.
    My question is either he need to do *the inbound delivery through VL31N* then only do the MIGO (GR) or directly without doing VL31N do the MIGO transaction.
    Kindly xplain process flow for the above case.
    Regards,
    Vimal

    You can define and do the required confirmation control key under
    SPRO -- > Materials Management --> Purchasing --> Confirmation .
    Confirmation control Key "AB"  is  refers to Order Acknowledgement.
    Based on configuration under " Set up Confirmation Control " system decides whether only Order Acknowledgement is required or subsequent operation is required prior to GR.
    Suppose " Inbound Delivery is required" then one need to do Inbound delivery under VL31N.
    Then GR. You can remove the inbound delivery steps by making blank key  under Confirmation tab.

Maybe you are looking for