IDOC PPCC2PRETEVENT is not working

Hi Experts,
I wanted to use the IDOC "PPCC2PRETEVENT" for posting the confirmation of a process order. I have done all the settings in WE20 and BD64. IDOC is getting generated and the status is 53. But no confirmation is getting updated. Even if there is no data passed to this IDOC also, the status is 53.
Have any body come across such a case?. Please let me know how to solve it.
Thanks & Regards
Prathib

Dear Prathib,
Status 53 mean, their was no problem to send the data to system and store the data in table AFRP0. This data need to be processed later to see confirmations.
First please check transaction CI41, flag 'immediate Update' is this flag set or not?
If yes the system should process the records in AFRP0 normaly automatically. Please check CO16N, maybe their was a problem while processing? You should find records here then.
If the flags is NOT set
You need to process this data in table AFRP0 now by using report CORUPROC1 or transaction CO1L. If an error occur while processing the data then the record is stored in CO16N, so you need to check CO16N here too.
Hope this help.
BR Sabine

Similar Messages

  • RBDMANI2 for IDOCs in error not working in Background..

    Dear All,
        We have an ALE-IDOC scenario in which our IDOC gets posted in the destination system with status 51 as per business reqt. We schedule a job in the background using program RBDMANI2 which is used to manually reprocess IDOCS in error.
        This background job was working fine in the 4,7 R/3 Server, but we have upgarded the receiving system to ECC 6.0. Now the problem is dat when we try to reprocess the IDOC using this job, the IDOC are not processing further.. It ideally is supposed to do further processing as per the code writen.
      We tried debugging the code(RBDMANI2) in background. But, its not helping.
    Kindly advise.
    Regards,
    Santosh Reddy.

    On primary research I found that there is a call to this FM 'SAPGUI_PROGRESS_INDICATOR' .
    In that FM see line 12.
    IF SY-BATCH <> SPACE.
              EXIT.    "do nothing in batch
           ENDIF.
    May be this is the cause of your error.
    Rhea.

  • Inter-Company Billing via idoc FI & MM Not Working in Tandem

    Hi,
    Difficult choice where to post this as it crosses so many disciplines...hope there is someone who can help.
    My problem is this:
    We have an inter-company situation configured in our system, one company code supplies stock to another, the receiving company code is billed via an idoc and a FI doc is posted. This is all well and good, it works fine as a PO is involved and it is using the MM variant of EDI processing.
    Now we wish to also use Cross Company Selling - this is where NO po is involved, simply the plant in the different company code satisfies the sales order.
    All works up to the point of the EDI posting. It is set to work with the FI variant but the idoc does not process due to the error message: Enter document number from number range 51 for year 2009.
    I understand what the message means: in the MM scenario the FI doc is created using the MM doc no for the vendor invoice receipt.
    In the cross company sale FI scenario, there is no MM vendor invoice receipt so FI can't get it's doc No.
    What am I missing?
    Should I be creating a different FI doc in this process - maybe one that automatically assigns a No?
    If so how does the EDI process decide which doc to create?
    Any help gratefully received.
    Regards
    Guy

    Hi Guy,
    What i understood is that you are trying to clear manually. I suggest you to create a BDC from F-30 transaction which clears intercompany Billing Invoice (from the selling plant) and post an Debit on account of the other company plant.
    Thanks
    Rajjanikanth

  • File to idoc scenario error - not working yet :(

    Hello! I'm trying to make changes in business partner record in CRM using idoc CRMXIF_PARTNER_SAVE_M01
    I have an error 56 EDI: Partner profile not available.
    In Control record in we02 transaction, I have right Partner number for Recipient information - logical system name like CRM has in SLD.  But there is no Port.
    In Sender information I have right Partner number, like my filesystem business system has in SLD and have a port SAPP1D - but  I have nowhere entered it!
    And one more little question. In we20 transaction am entering inbound parameters for partner:
    CRMXIF_PARTNER_SAVE
    CRMXIF_PARTNER_SAVE_M
    1) Is this right inbound parameters for my idoc?
    2) What Process code should I use ?

    Hi,
    in XI in IDX1 transaction, maintain a port for CRM system specifying the CRM port and the client and the RFC destination from XI to CRM system.......moreover if you are using apply control record values from payload option in reciver IDOC comm channel, then in the IDOC control record in msg mapping map the sender port to CRM port, partner number as logical system of CRM ie C2DCLNT100 and partner type as LS..........then when you will re-run your scenario, your IDOC will have CRM port also in the control record..........
    in CRM system your WE20 for LS for XI should have as an inbound parameter your IDOC - which i think you have already done.........
    One more thing - put everything in uppercase letters everywhere in msg mapping in control record data, in we20 setting etc.
    Regards,
    Rajeev Gupta

  • IDOC is not working

    Hi,
    We have 2 company codes and for the intercompany trade we are using IDOC to send invoices between the companies - it works perfect. Now we have added a third company code and the IDOC functionality does not work for intercompany trade involving the new company. All about pricing, requirements, PO, delivery etc. works without problems but the IDOC process does not start when we create the invoice - so i don't even have error to trace. I have created OBCA, OBCB, OBCD and OBCE and of course WE20.
    A tip for the missing link will be really appreciated - thanks in advance
    yu

    With reference to this issue, please review note 106142 which has good     
    information on this behaviour.                                             
    Transaction OBCA is not really a customizing function since the table    
    as the partner numbers in the key, and these are master data, at        
    east in case of vendors (partner type LI). Thus, table T076B should not 
    ransport relevant. But there's been a couple of bugs in the lower       
    releases (note 106142) and they're fixed in release 4.70 and higher.     
    Similarly the tables like T076S as well as view V_T076S depend on master  
    data (like vendor master data), the standard settings of these tables     
    do not implicate transport requests.                                      
    Within note 106142 incorrect table settings in lower releases were        
    corrected to avoid the transport of these tables.                         
    If you nevertheless want to transport changes of these tables you have         
    to undo the change of the recording routine in transaction se54.               
    For these tables change it back to Standard Recording Routine and save         
    the changes. Please do NOT generate the view.                                                                               
    But please keep in mind that this setting represents a modification            
    and possible problems due to this setting are not supported by SAP.                                                                               
    tr. SE54 ->                                                                    
    Table/View: T076M                                                              
    select the radio-button 'Generated objects' ->                                 
    select the button 'Create/change' ->                                           
    frame 'Dialog data transport details' ->                                       
    'Recording routing' -> please, select option 'Standard recording               
    routing' and save your settings.                                               
    PLEASE, DO NOT REGENERATE THE VIEW !!!!                                                                               
    Further details which may be helpful:                                          
    You have to change                                                             
    the view T076M for the transaction OBCD                                        
    the view V_T076S for the transaction OBCE,                                     
    the view V_T076K for the transaction OBCC,                                     
    the view V_T076B for the transaction OBCA,                                     
    the view V_T076I for the transaction OBCB.                                                                               
    Please also review the SAP notes.                                         
    356483     Customizing: Current settings in the test system                    
    135028     Transfer IMG activity to current setting      
    106142     EDI: Customizing tables T076B, T076I,...      
    Regards
    Vijayesh V V

  • IDoc string field to JDBC date field - Not working

    Hello everyone,
    Once again I must ask you something that is keeping me..
    I had a interface type RFC ASync to JDBC SQL Server, it was working fine. Then, I was asked to change to a type iDoc ASync to JDBC SQL Server.
    At first, it was not a problem, just manual work. But them, I am getting an error.
    In the RFC, I had a date field, that was directly related to the date field on the JDBC destination, so the mapping was pretty much straight forward. The SQL INSERT command was working fine on this cenario.
    Now, in iDoc, this field was automatically converted to a string, and somehow, PI is not understanding that string has to be mapped to a date field in the JDBC.
    Is there any 'workaround' for me to do this?
    Thanks!
    Ricardo Sancio Lóra
    Brazil

    The issue here is that somehow, the same SQL insert command that was working, does not work anymore.
    This is the SQL command took from RWB log monitor:
    INSERT INTO  aniversariantes_sap (matricula, nome, nascimento, unidade) VALUES (00000070, 'Ricardo Lora', '19851216', 00000000)
    If I run this query on my DB it works.
    But, in PI, it's not, here is the error:
    Could not execute statement for table/stored proc. "aniversariantes_sap" (structure "ANIVERSARIANTES_SAP") due to com.microsoft.sqlserver.jdbc.SQLServerException: Syntax error converting datetime from character string.
    I´ve tried cast() and convert() using mapping 'habilities', but also, does not work. Work if I run in the DB, but not if PI runs it.
    Wierd..
    Ricardo

  • Multiple occurence not working for extended idocs

    hai friends
    iam doing file to idoc senario in that multiple occurence is not working for Z segments.
    it is extented idoc .
    in taht multilpe segments are not creating only one segment is creating
    what is the problem
    pls help me
    with regards
    srikanth vipparla

    Hi Srikanth,
    You should map the node of the target side(the one which you want to occur multple times) to the node of the source side based upon which the target side node has to occur multiple times. For example lets say our source and target side structures are like this:
    <Source>
                  <Element1>
                  <Element2>
                  <Element3>
    </Source>
    <Target>
                  <Element1>
                  <Element2>
                  <Element3>
    </Target>
    Now if you want Target to occur n times if  Source node occurs n times, you should map Target node to the Source node. Even in case you want that Element1 of target side should occur as many times as many times you have Element1 of Source side, you should do the same.
    Thanks and Regards,
    Sanjeev.
    PS: Reward points if helpful.

  • Multiple IDOCs pattern not working

    Hello, When I tried Multiple IDOC to single file pattern, it is not working as expected. Everytime when a idoc reaches XI, it is going to a seperate BPM queue and not collecting the IDOCs, any idea??

    Yes, I have refered. I have done exaclty the same thing as in SAP Pattern for collecting multiple idocs to single file. Everything is working fine in BPM too.  But the problem is whenever the idoc hits XI, it is going to a seperate BPM queue instead of a same queue. So single message for each BPM and BPM waits for 3 minutes (mentioned in BPM) and times out. But my need is all the IDOCs should come to a single BPM queue and BPM needs to collect all the IDOCs and send it as a single file.

  • Message Listener Not Working

    Hi,
    We are using MII 12.0.2 (88). We have connected with SAP ECC and we are receivng iDoc mesg from SAP and processing thru message listener and processing rule editors.
    This connection was successful and we are able to recive all iDoc but suddenly on this is not working as only one type of iDoc are getting. But in SAP all are showing as Successful in WE02 tranx. We have checked in SM58 and other queues also. But in MII we didnt receive any iDoc except particular iDoc.
    We are seeing this error in log  "Could not save IDoc messages to the database"
    and location as "com.sap.xmii.databuffer.server.JCoIDOCServer".
    What is the problem and how to solve it.
    Regards,
    Senthil
    Edited by: senthil kumar on Jun 7, 2011 5:08 PM

    Hi Senthil,
    Did you mean that you were receiving a variety of IDocs before and now you only receive one type? 
    Or did you just try a new type and fail? 
    Check to make sure the Partner Profile's Outbound Parameters and the Distribution Model both are set properly for the IDoc types.
    Regards,
    Mike

  • Partner function not working when creating PO with ref to PReq

    Partner function is not working when creating a Purchase Order with ref to a Purchase Requistion, Partner functions maintained in the vendor master are VN, OA & PI.
    But OA & PI are not appearing in the PO header partner tab when created with ref to PR.
    however it works when i create the PO directly ( without the PR ref )
    I am using the same material & Plant for both manual PO & PR to PO.
    Any idea what could be wrong .
    I have maintained the settings for schema groups for vendor master & purchasing doc in the partner determination.
    Thanks
    Dkmurthy

    Hi,
    I have also an issue that seems similar to one you are discussing.
    When we use ME59N and create a PO with ref. from a PR (created from a sales order), the message determination works well, it reads the condition set in MN04 (condition records for messages), and creates a message (with output type for EDI , medium: 6, and partner function LS: Logical system). Message is created and idoc is sent.
    When we try with ME21N, ME21 and we create the PO with ref. to the same PR, either by entering manually the PR in the document overview of ME21N or by selecting the PR (without entering the PR number), i.e with date, the message is not created in the PO.
    Company code is assigned to purchase organization, and so is purchase organization to plant.
    Any idea why there is no automatic message determination in the case of the transaction: ME21N
    Note: If I try ME21N, and enter the output type and partner, manually, I receive a warning message
    VN006 (Partner XXXX does not exist for partner function LS). If I accept this warning message, then message is saved- idoc is sent. However I can not overcome the warning message, if it plays any role, because I can not assign partner function LS to the vendor.Then I receive message CZ 327 (Can not use this partner role).
    Any input is wellcome.

  • Extraction of certain master data not working

    Hi, we are on BI7 and some of the BC masterdata extractions are not working correctly.  Some masterdata working fine, consequently communication between systems working, but some master data fields e.g. 0co_area, 0chrt_accts and more are not working fine.  Get this on 3.x and new datasources.
    The data does get pulled through but the upload just never goes green, and keeps running.  If one look at the batch jobs (SM37) in the appropriate source system, it keeps on going until it is manually stopped. 
    I am only experiencing this problem with data pulled through from the production system - I am pulling it through to my testing and production box, but fails in both, where all other ECC systems are fine.
    In the monitor there is a warning and the following is the details of the monitor: 
    Overall status: Missing Messages or warnings
       Requests (messages):  Everything OK  (green)       Data request arranged  (green)
           Confirmed with:  OK (green)
       Extraction (messages): Missing messages (yellow)
           Data request received (green)
           Data selection scheduled (green)
           Missing message:  Number of sent records (yellow)
           Missing message: Selection completed (yellow)
       Transfer (IDocs and TRFC): Missing messages or warnings (yellow)
           Request IDoc: Application document posted (green)
           Info IDoc 1 : Application document posted (green)
           Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n (yellow)
           Info IDoc 2 : Application document posted (green)
       Processing (data packet) : Everyting OK (green)
           Inboun Processing (32 records) : No errors (green)
           Update PSA (32 records posted) : No errors (green)
           Processing end : No errors (green)

    Thanks, for the responses.  The appropriate Idocs work fine with transaction BD87. I looked in SM58 earlier during the course of the day and there was no error, just checked again (8PM) and found some entries with error texts for BW background user - 6 errors within 10 seconds.  Something to do with 'ERROR REQU... PG# IN 1' - do not have authorisation at this moment to check the specific requests, but not sure if the master data extractions would have caused these.
    In the job log for the problematic jobs, only 1 IDoc get created, unlike the other succesful ones that have 3 IDocs (not sure if this means anything)

  • ESS is not working properly after upgrade from 4.7 to ECC6.0

    ESS Scenario in 4.7
    4.7 Scenario:
    The IMG configuration u201CWork and Life Eventsu201D is done to map them with the PZM3 service (Home Page) to get them as different folders/links on the home page as given below:
    List of Services used to set up ESS:
    Sl.No     Functionality     Service/EWT/URL Name     Standard/ Customized     Type
    1     Home Page     PZM3                                          Standard                 Service
    2     Inbox                     BWSP                                          Standard                 Service
    3     Calendar                     BWCA                                          Standard                 Service
    4     Whou2019s Who     PZ01                                          Standard                 Service
    5     CPF Display     http://192.168.0.2:7070/omcpf             NA                                  URL
    6     Payslip Display     ZPAYSLIP_USER                          Customized                Service
    7     Section 80C     PZ88                                          Standard                EWT
    8     Section 80                     PZ80                                          Standard                EWT
    9     Form 16                     HRESSIN_F16                          Standard                EWT
    10     Address                     PZ02                                             Standard                EWT
    11     Bank Information     PZ03                                          Standard                Service
    12     Open Appraisals     Not Available                           NA                                 Service
    13     Emergency Address     PZ05                                           Standard                 EWT
    14     Family/Dependents     PZ12                                           Standard                 EWT
    15     Personal Data     PZ13                                               Standard                  EWT
    16     Previous Employers     PZ28                                           Standard                 EWT
    17     Apply Leave     WS20000081                           Standard               Service
    18     Leave Overview     WS01000109                           Standard              Service
    19     Leave Balance     PZ09                                             Standard              Service
    20     Loan Application     ZLOAN                                          Customized              Service
    ECC6.0 Scenario:
    In ECC6.0, flow based services are no more supported by ECC6.0 and Dynpro based services are supported.PZM3 (Home Page) is a flow based service.
    There is no replacement provided for PZM3 service, so the IMG configuration is not possible for u201CWork and Life Eventsu201D.
    OSS ticket raised, but no solution for IMG u201CWork and Lifeu201D events.
    List of Services would be used to set up ESS:
    Sl.No     Functionality     Service/EWT/URL Name     Standard/ Customized    Type
    1     Home Page     PZM3                                       Standard                           service
    1)this service is not available
    2)SAP does not provide any replacement.
    3)PZM3 is not supported in Integrated ITS. No direct solution proposed.
    4)Given reference of few notes.
    5) A dynpro (module pool screen) based IAC needs to be created and links need to be provided on that screen. Generated HTML page is modified  to access the services via URL or by OKCODE.
    Screenshot attached below.
    2           Whou2019s Who                 PZ01                                      Standard                             Service
    1)this service Available
    2)Not Working properly.
    3) The problem may be because of the dependency with SAP Query. Either Query is missing in the new system or not having the proper authorization. Needs to be debugged and finalized.
    7     Section 80C     PZ88      Standard     EWT     Available               
    8     Section 80      PZ80     Standard     EWT     Available               
    9     Form 16                HRESSIN_F16     Standard     EWT     Available               
    10     Address                PZ02     Standard     EWT     Available     Only EWT Available.          Service needs to be created to access the EWT.
    11     Bank Information     PZ03     Standard     Service     Available     EWT Available.           Service needs to be created to access the EWT.
    12     Open Appraisals     Not Available     NA     Service          EWT Available.           Service needs to be created to access the EWT.
    13     Emergency Address     PZ05     Standard     EWT     Available     EWT Available.           Service needs to be created to access the EWT.
    14     Family/Dependents     PZ12     Standard     EWT          EWT Available.           Service needs to be created to access the EWT.
    15     Personal Data     PZ13     Standard     EWT          EWT Available.           Service needs to be created to access the EWT.
    16     Previous Employers     PZ28     Standard     EWT          Service Available          
    17     Apply Leave     WS20000081     Standard     Service     Available, but not working                                                                               No solution is proposed yet.
    18     Leave Overview     WS01000109     Standard     Service     Available, but not working               No solution is proposed yet.
    19     Leave Balance     PZ09     Standard     Service     Available, but not working               No solution is proposed yet.

    Ya ramakrishna,
    Even easier is for you to send us the mail ID of your client. We will do the work, then send them an idoc of message type INVOICE and for you a post card of course.
    Please do the needfull,
    Julius

  • Variable Substitution not working when using ABAP mapping

    Hi all,
    I am doing an IDoc to File scenario.
    Due to some complex mapping requirements, i had to use ABAP mapping for IDoc to File ( IDoc : SHPMNT05)
    There is also one more requirement where in i need to generate the receiver filename dynamically
    i.e the filename is of the form :     
        GW-XYZ-DD/MM/YYYY.csv
    Where
    XYZ is the Shipment number (E1EDT20- TKNUM)
    DD/MM/YYYY is the IDOC creation date in ECC (EDIDC-CREDAT)
    so i used the variable substitution option in receiver file adapter.
    But its not working.
    Is there any limitation for using the variable Substitution, doesnt variable substitution work in case of ABAP mapping?
    Regards,
    Loveena.

    Hi,
      u written ABAP mapping program to get the file name in the required format ,
    is it rt?
    when u test it at message mapping(including ABAP map program)
    u get the the required format of file name in the one of target filed.
    if that was fine, please check the variable substituiton parameters at receiver file adapter.
    i mean, are u maintain variable name and refernece.
    u have to specify the payload information.
    warm regards
    mahesh.

  • Flex Time with variable tempo not working correctly.

    Hey,
    Has anyone else noticed that Flex Time doesn't work as intended if you have variable tempo?
    To clarify, I recorded a band playing their song and then figured out their various natural tempo changes and adjusted the Global Tempo Track accordingly.
    Then, the drummer recorded his part to a click on that track, obviously keeping with the natural tempo changes that the band played to.
    Quantization of MIDI works just fine, as in, it matches the increases and decreases in tempo.
    However, attempting to quantize an audio track using Flex Time does not work properly.
    I was just wondering if there is something that I'm doing wrong or if this is a known bug.
    Thanks,
    William

    Thank you for your answers!
    But there are several Problems using a dummy field in an IDOC structure. We have got a naming convension so that we can't create an IDOC-like structure named ORDRSP.ORDERS05.
    But perhaps I am thinking to complex and there is an easier way to add a dummy field to an IDOC structure.
    Could you perhaps also suggest a solution for that dummy field problem?
    Many thanks and kind regards,
    Steven

  • IDocs in WEOUTQUEUE not processed

    Hi all,
    I have a problem with IDocs' serialization. I want to send IDocs of specific message types via IDoc outbound queue (trans. WEOUTQUEUE) .At sender system side in outbound partner profile (WE20) I configured IDoc to be send by Queue Processing with rule "constant:ediqueue". IDocs arrive to queue in WEOUTQUEUE, and here the problems begin:
    1. Processed messages stay in queue - why?
    2. If I send 1 IDoc it's not sended automatically, I have to activate queue in order to process it. It ried to use report RSEOUT00,but it only shows how many IDocs ready for processing and doesn't send them - how can I configure automatic processing of Idocs in queue?
    3. If I send (with WE19) more then 1 IDoc at once, thay are automatically processed, but in XI in SXMB_MONI i see that they are processed by random QRFCs and are not serialized.
    Can anyone please help me to work it out?
    Thanks!
    Anna.

    We are having a similair issue.  I have IDocs outbound from R/3 to XI.  The Idocs are setup as "Queue Processing" with "Transfer IDoc Immed" option in the WE20 partner profile for EOIO processing.  I usually have no problem all day long but every night right after midnight all the Idocs remain in a status 30.  I have to use WEOUTQUEUE to activate the que or BD87 to release them.  Once I do this, all IDocs moved along successfuly except every once in awhile during the middle of the day they go into a status 30 and remain there.  I did notice the difference between the Idocs that work and the others that get stuck is the there are 2 entries for status 30 when viewing the IDocs in WE02.  Here is what they look like.  IS this simialiar to your issue?
    03 - qRFC used to send IDoc to SAP system  (I get this once I releaqse them manualy)
    30 - blank
    30 - Receiver exists , No filters , No conversion , No version change
    01 - blank

Maybe you are looking for