Posting Data Issue with IDOC Type : COND_A03

Friends,
I'm posting the data from Middleware(Message Broker) to SAP using the IDOC Type : COND_A03 with Message Type : COND_A.
For this IDOC,I'm populating the below Segment's data.
Segement :E1KOMG:
Fields:
KVEWE,KOTABNR,KAPPL ,KSCHL,VAKEY ,KONDA,MATNR .
Segement :E1KONH:
Fields:
KNUMH,DATAB,DATBI
Segement :E1KONP:
Fields:
KSCHL,STFKZ,KSTBM,KSTBW,KRECH ,KBETR,KONWA,KPEIN,KUMZA,KUMNE,MXWRT,GKWRT,ZAEHK_IND ,KBRUE,VALTG,
VALDT,ANZAUF,MIKBAS,MXKBAS,KOMXWRT,KLF_STG,KLF_KAL
Problem:  In SAP, IDOC's are processing successfully with status 53 and updating the tables : KONH,KONP  successfully.
But Table A957 which is passing against KOTABNR field is not pupulating with the Materials passing.
Can anyone please guide me why the Materials are not populating in the table : A957.
Regards,
Sreeram

Hi,
I guess there might be some issue with VAKEY population.
All the key fields in A957 should be concated properly while populating VAKEY. (Leading zeros must be prefixed to the material)
Regards,
Ganga

Similar Messages

  • The meta data for the IDoc type "LOIPRO01" is unavailable

    Hello,
    i'm trying to send idocs via rfc from SAP ERP ECC 6.0 to SAP MII 12.06, but we always get errors like:
    The meta data for the IDOC type LOIPRO01 is unavailable
    I've checked the parameters on MII side of the IDOC Listener:
    Servername  MII_JCI33 
    server Properties 
    gwhost H33-I0.rz.k-plus-s.net 
    gwserv sapgw02 
    progid MII_JCI33 
    trace 1 
    params   
    snc_myname   
    snc_qop   
    snc_lib   
    unicode 1 
    max_startup_delay   
    Client Properties 
    client 303 
    user RFC-I33 
    alias_user   
    passwd   
    lang en 
    sysnr 02 
    ashost h33-i0.rz.k-plus-s.net 
    mshost H33-I0.rz.k-plus-s.net 
    gwhost H33-I0.rz.k-plus-s.net 
    gwserv sapgw02 
    r3name H33 
    group   
    tpname MII_JCI33 
    tphost H33-I0.rz.k-plus-s.net 
    type 3 
    trace 1 
    codepage 1 
    There is no saprouter between ERP and MII as in the thread from Christoph Mertins in November 2008. The user rfc-i33 on the ERP has SAP_ALL permissions.
    Has anyone an idea ?
    Kind Regards,
    Thomas Strecker

    Thomas,
    There is a link for a basic IDoc installation that may help.
    [IDocListener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
    One other issue that has occurred to cause problems is registering the program in Visual Administrator.  If you registered the ProgID in Visual Administrator, there will now be two ProgIDs registered (MII does self registration with the RFC Destination upon starting the server).  Delete the registration in VA, if you did it.
    If there are other error messages available, please post them.
    Good luck,
    Mike
    I also just remembered, if you have two ProgIDs that are the same, running on two separate MII instances, you may run into a problem.  Not sure it will have the same symptoms or error messages, but something else to check with (especially when migrating from dev to prod).
    Edited by: Michael Appleby on Feb 10, 2009 5:02 PM

  • The meta data for the IDoc type "MATMAS05" is unavailable

    Dear Gurus:
    I need  help in completing small test that I am doing to send MATMAS IDOC to xMII.
    I have done:
    1.     RFC connection SM69 and tested ok
    2.             xMII IDOC Listner config with my SAP client
    3.     Connection appears in –smgw ok (in logon client screen)
    4.     Completed Distribution channel and we20,we21
    All above looks in place when I send one IDOC (BD10) it remains in 03 even after I run RBDMOIND. Besides IDOC is not appearing in C:\Lighthammer\JCO\Output.
    On tRFC I see error “The meta data for the IDoc type "MATMAS05" is unavailable.”
    Note that
    a) I am NOT using transaction on routing tab
    b) xMII version 11.5
    c) I used "How to send IDOC ...." Version 2 PDF that is available on web (thanks to Bimal)
    d) I looked at other two posts which has to do with LOIPRO message type and with JCO issue
    Please help.
    Thanks
    Jay

    Jay,
    What version of ERP are you using, perhaps this note will help: 770239
    Also the SAP Help has some suggestions as well...<a href="http://help.sap.com/saphelp_nw04/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/content.htm">Click Here</a>
    -Sam
    null

  • Add new bank account in master data client with idoc DEBMAS.

    Hi friends,
    I have an issue.
    I am trying to add new bank account in master data client with idoc DEBMAS.
    But when I submit, then just overwrite the bank data but not add.
    I try playing with MSGFN code with value '009' or '004' but nothing done.
    Someone has met this issue ?
    Thanks for your answers.

    Thanks,
    But what do you mean ? where can I find this path , in img ?
    Fields->Set Qualified Update ->Append Option
    I think we have to use another idoc :
    BUPA_C_BANKDETAIL_ADD01 SAP BP,  BAPI: Add Bank Details
    I'll try...

  • Data transfer with IDoc

    Hi All,
    Can any one please explain me about "Data transfer with IDoc".

    Dear Prasad,
    Using the IDoc option , you will not have a staging in BW like PSA were you can do corrections if required,
    We can use IDOC option when we are very sure that data we are loading is error free,
    and in older versions we are forced to use only IDOC option when doing hierarchy loads and its ruled out now,
    Data transfer with IDoc
    The data is packed into IDocs by the source system and sent to the Business Information Warehouse. In BW your data is saved persistently and intransparently in the IDoc store. From there the IDocs can be updated in the IDocs manually or automatically.
    It is used for hierarchies load Limitations with IDoc is:
    transfer structure must not have more than 1000 Bytes in the character format.
    If it is a critical data we can use IDocs it can't be modified here. In case the load fails we need to load data from source system.
    http://help.sap.com/saphelp_nw04/helpdata/en/7d/724d3caa70ea6fe10000000a114084/frameset.htm
    Hope this helps u..
    Best Regards,
    VVenkat.
    Edited by: Venkata Narayana Jakkampudi on Dec 23, 2008 12:03 PM

  • Does SAP or Oracle have an issue with these type of processors?

    Does SAP or Oracle have an issue with these type of processors?
    Intel Xeon X5260 & E5450    vs    Intel Itanium       PROCESSORS
    I want a Sales / Marketing URL link or white papers that talks about processor recommendations.
    SAP GUI  7.20

    > Does SAP or Oracle have an issue with these type of processors?
    >
    > Intel Xeon X5260 & E5450    vs    Intel Itanium       PROCESSORS
    >
    > I want a Sales / Marketing URL link or white papers that talks about processor recommendations.
    SAP does neither "recommend" nor "deny" any processors.
    If you check http://service.sap.com/benchmarks then you get a lot of machines with different CPUs/operating ssytems and database combinations.
    Choose the one that suits best for you.
    Markus

  • Issue with Message Type Triggering during Inbound Delivery Creation

    Hi Experts,
    Hi Experts, 
    Currently we are facing issue with message type triggering during inbound delivery creation:
    In NACE transaction for Inbound delivery we have 3 custom output types:
    Pricing Procedure Used is standard one -> E10001
    Z140  Inbound Delivery Create  (This should get triggered when IB delivery is created)
    Z141  Inbound Delivery Change (This should get triggered when IB Delivery is changed)
    Z142  Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
    At present if i check delivery in  VL33 -> Extras -> Delivery Output
    Both  Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
    Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
    Thanks

    Hi,
    There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
    Thanks,

  • Post Goods Issue with BAPI with reference to BOM

    Hi All,
    I want to post Goods Issue with BAPI / FM with reference to BOM.
    The requirement is like to replicate what we can do with MB1A with reference to BOM with BAPI / FM.
    Please give ur suggestions.
    Thanks in advance.
    Chintan.

    https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_forums_rm&query=kanban&adv=false&sortby=cm_rnd_rankvalue&sortmode=true&searchmode=similar&similardocsuri=/forumsrm/1_category/42_category/50_forum/34196_thread/322837_message

  • Posting goods issue using Message type SHPCON and idoc type DELVRY03

    Hi SAP Gurus,
    I am using message type SHPCON and idoc type DELVRY01 with processing code DELV to post goods issue for a delivery note.
    I tried to simulate the inbound entry via WE19. The scenario should be posting goods issue based on the delivery order.
    In some cases, quantity issued is less than the quantity in the DO. For this, I need to change the delv quantity in the DO via VL02N before I select Post goods issue button. This will change at the same time post the goods issue.
    What I have filled up are the fields:
    E1EDL20-VBELN = DO num
    E1EDL20-VSTEL = Plant
    E1EDL18-QUALF = "PGI"
    E1EDTH13-QUALF = "006"
    E1EDTH13-NTANF = date today
    E1EDL24-POSNR = 000010
    E1EDL24-MATNR = material num
    E1EDL24-WERKS = delv plant
    E1EDL24-LGORT = sloc
    E1EDL24-LFIMG = updated quantity
    But everytime I simulate using WE19, the entire quantity in the DO is not changed at all. The goods issue quantity posted is still the original DO quantity.
    May I know how to do this? Thanks.

    Put value in E1EDL24-LGMNG for qty to pgi.

  • IDOC status 64 not converting to 53, while trying to post GR with IDOC type MBGMCR02

    Hi All,
    We are having a issue while posting GR for an inbound delivery using IDOC type MBGMCR02. We are using FM BAPI_IDOC_INPUT1 for the same (taken from the process code BAPI). The IDOC is getting generated, but with status 64. And here it is throwing a dump Messge type "X".
    How can we get this IDOC processed to next stage / get status 53. The IDOC is failing to get status 53, while updating the delivery document flow information.
    We took the ref' of note # 833603, to post the GR.
    Any help is highly appreciated.
    Regards,
    Simadri

    Thanks Sudeesh for replying my question.
    I just found one note 1993787 which resolved my isssue and was released recently on 2nd may
    Thanks,
    Simadri

  • How to revert stock in quality stock after qty issued with movemt type 704

    Hi Experts,
    User issued qty from quality stock to cost centre trough T-Code MI10. Inspection lot against the issue qty has status u201CREL CALC SPCO PRII CROK QLCHu201D This lot has been generated through mov  101 against PO (GR). After doing GR qty posted in quality stock. By mistake user has issued qty from quality stock to cost centre trough T-Code MI10. For same movement type was 704.
    Now they want same qty back in quality stock also they want to do UD for the same. How to get back this stock in quality stock?
    Awaiting for your expert reply.
    Thanks and Regards,
    Sandy

    hi Sandy,
    Quickest and easiest option without lot of configuration and process change for your scneario will be ,
    The transaction code is MB0A.
    The steps for executing the above trancode is as follows.
    Inputs:-
    Posting date : UD date.
    Movement type : 102
    Enter relevant plant, storage location, vendor and the material code
    The purchase order/sch.agreement for the given vendor-matl-plant combination will be displayed.
    Select the correct PO and click adopt selected.
    The material with quantities to be reversed will appear in various line items. Select the correct quantity for which the reversal to be made.
    Click adopt + details
    Enter storage location
    Remove "X" in the stocktype field
    Save.
    Material document will be generated.
    The correct material could be inwarded again and correct usage decision can be taken  against this lot.  
    Get approval from Materials and  Finance guys.   As long as your accounting documents nurlifies each other  ,  you should be good to go.
    If not  you have to use the same proess   witht twiests , with other movement types for which you have activated  inspection type.
    Hope this helps
    Cheers
    Rav

  • GR document and posting date issue for initial stock upload are overidden

    Hi all
    Loading initial stock into the system using standard idoc message type MBGMCR and basic type MBGMCR02.
    We are trying to post the intial stock upload with posting and document dates in past with this idoc. The Idoc is accepted with these dates but while posting the system is overiding these dates and posting the document with system date. Any clue as to what is happening?
    Regards,
    Amit

    Hi Jurgen
    I am aware about the posting being possible till the last period.
    But the system over-riding the posting and document dates in the IDoc even if I chose previos day's date in the current period. The dates in the IDoc are correct to be in the past. The IDoc is accepted by the system with the document and posting dates in the past.
    But dates in the document after posting are system dates. Very unsual. Please let me know the reasons.
    Thanks for the reply.
    Cheers,
    Amit

  • ECC6.0 upgrade issue with IDoc release

    Hi experts,
    we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
    In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
    We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
    has any one faces such situation in the past? if yes, please throw some light.
    Thanks in advance.

    Hello,
    Iam new to SAP. Thar’s why i can’t understand well to do upgrade,
    Then i found out some notes from internet about Upgrade : ‘‘ SAP Note Number 857904  (upgrade from Release 6.’ To 7.0)’’.
    In that notes,
    Actually i would like to know about some key words (for example : ASSIGNING, REPLACE, TRANSFER…. )  which how to work in the Release 7.0
    Always i have some objets in 4.6C. 
    Ex 01: ’’READ DATASET p_dataset INTO wa_record’’
    Ex 02 :  ’’ TRANSFER i_crhu TO p_crhd ’’
    LOOP AT i_crhd.
    *disable controls in crhd
        PERFORM f_disable_crhd.
        TRANSFER i_crhd TO p_crhd.
        IF sy-subrc NE 0.
          MESSAGE a045.        "Error when transfering data to error file
        ENDIF.
    ENDLOOP.
      CLEAR i_crhd.
      CLOSE DATASET p_crhd.
      IF sy-subrc NE 0.
        MESSAGE a039.                      "Error at close dataset
      ENDIF.
      OPEN DATASET v_crhd FOR OUTPUT IN TEXT MODE.
    And then i have some FM (ex : WS_UPLOAD , WS_DOWNLOAD)
    So I have changed the code for WS_UPLOAD by GUI_UPLOAD
                                  and WS_DOWNLOAD by GUI_DOWNLOAD
    now my problem is to know about some key word which how to work in ECC6 (for example ASSIGNING, REPLACE, TRANSFER…. )
    thanks in advance
    Rathy

  • Could not trace the issue with IDOC to file

    Hi All,
        We are facing issue with missing idoc data in the file, There were 20 idocs got generated (msg type - PAYEXT) from the payment run but only 15 of them written to the file, in the Outbound partner profiles we are using file port to create file. Noticed that all idocs were showing the same status (03) and The IDoc was written to file & file location.
       When we checked the file and found that 5 idocs data was not written to the file, but surpricingly status was showing that it was written to file. Can any one give clue / similar experience ... on this. Not sure how to track the issue ... i checked SMQ1, but nothing was locked.
    Thanks
    Satya

    Hi Kumar,
    As Jose mentioned please check the occurrence of the 6th file. It should be 0..unbounded. Also if you do this it will pass the mapping but you will get the error for the 6th file in sxmb_moni, because it would be an empty root message only. This is a known issue and I dont think we have a solution for this. But one workaround would be to create a custom mapping exception so that you have that exception in sxmb_moni when the message fails and if you have alerts then you will have this mapping exception in your alert.
    Regards,
    ---Satish

  • Error M7044 posting goos issue (VL02N) - valuation type

    Hello!
    We have a delivery (for a consignment fill-up) which we want to post goods issue.
    But when i try to post goods issue i get the error "choose a valuation type" - M0744
    But the item line has a valuation type "EIGEN"
    Checking the material data - Accounting 1 for valuation type "EIGEN" all seems OK too...
    I don't know what i shall do, to solve the problem.
    Thanks in advance
    Markus

    Hello Jürgen,
    i checked and i have batch number and valuation type for material 215778 / batch 0.

Maybe you are looking for