Problem to Integrate IDOC type J3AGRI

hello experts,
When trying to modify an existing Grid with IDocs, the IDoc inbound processing raises message with id 8J number 406 and text 'Grid old and new dimensions don't match' (Function Group J3A0 Text Symbol 639), though the IDoc has the same dimensions as the existing Grid in the system.
please i need a help.
thank you in advance.

Ok Mady,
then just reward this good response
PS: for IDOC exchange, this is the only message type changed by switching < 4.5B to >= 4.5B.
New message types can be added for contract distribution (BLAORD, COND_A, BLAREL).
Rgds
Christophe

Similar Messages

  • Problem in Idoc type

    Hi Experts,
    I am facing one strange issue in idocs.
    I am having a scenario where for particular LS i have assigned HRMD_A06 basic type and ZHRMD_A06 extension in partner profile.
    and i am trying to implement badi HRALE00OUTBOUND_IDOC.
    in this badi at runtime wrong message type is getting picked up at the runtime(checked in debugging). But at the end it displays proper basic type.
    so for me it is getting difficult to write logic in this badi.
    Please guide is there any particular setting apart from partner profile where we assign message type to LS.

    Hi,
    In problem in idoc type , that below link will helpful to you.
    Try this link,
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/technology/sap/18/
    Regards,
    Sekhar

  • Message type idoc type problems

    Hi,
    I'm facing a problem in idocs. I'm sending idocs with message type ORDRSP and idoc type ORDERS05, but for some reason in SAP, the idoc is always picking up a different message type ORDERS and the partner profile part is failing because my partner profile is set up for ORDRSP message type. Is there any setting or transaction that sets a default message type for an idoc type in SAP.
    Regards,
    Vijay

    Hi vihay,
    yes for the message type ordrsp the basic type is orders05.
    u r telling ur geeting problem in inbound idoc?
    if that is the case then u have to use in we20 inbound parameters and give the processcode(ORDE) there instead of basictype .CHECK the same and get back to me if any quries
    Regards,
    Nagaraj

  • ALE: setting up reduced IDoc type for use in 4.7 and ERP 2005 problem

    I need to set up a reduced HRMD_A message type and then use it to send HR data from a 4.7 system to an ERP 2005 system.
    To define the reduced type in both systems I use transaction BD53 (Idoc reduction maintenance).
    The problem is that the transaction offers HRMD_A06 as the basic type on a 4.7 system and HRMD_A07 on ERP 2005. Thus i cannot  set up identical definitions.
    I suppose I should  'step back' to A06 at the ERP 2005 system somehow, but where to look for?..
    Thank you in advance!

    The table is maintained with BD69 - Assignment of message type to IDOC type.
    In my case I added one line with values:
    Message type: {my reduced message type}
    Basic type: HRMD_A06
    Extension: {my HRMD_A06 extension}
    Also it looks like there is another (better?) way of making the assignment. It is done with WE82, described in sap help here http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b7db043d711d1893e0000e8323c4f/frameset.htm and also discussed in this topic.
    SAP ERP Human Capital Management (SAP ERP HCM)

  • Problems with PORDCR101/2 IDOC Type

    Hi All,
    I am new to SDN so not sure of the protocol so please bear with me.
    I am trying to use IDOC type PORDCR101 to create purchase orders.
    In the segment E1BPMEPOHEADER I have mapped the the DOC_TYPE to NB (with the corresponding E1BPMEPOHEADERX set to X)
    But I am still getting a strange error message
    Document type ZU not allowed with doc. category F (Please check input)
    ZU is a bespoke requestion that exists in the system, but nowhere is this mapped. The standard NB Purchase order type exists in the system.
    If anybody can shed some light, I can provide the complete mapping if this is useful.
    thanks
    Shashi

    Hi G.Ganesh Kumar,
    The partner profile in WE20 the Partner Type is set correctly, the inbound parameters have message type PORDCR1 set correctly with the BAPI process code.
    I have no problem generating the idoc, I get the error 51 with the above description when the idoc tries to post.
    Shashi

  • Mapping problem for IDOC Type DESADV

    Dear all
    I need to change Segment E1EDP07 in the message type DESADV.
    I should concatenate VBELN and VGPOS into BSTNK.
    I tried to do this with BD79 (Rules for Data Converting). This seems not to work as I can get only 1 sender Field.
    So I tried to use the userexit EXIT_SAPLBD11_001, but it seems that this is not used. I have set a break-point for debugging and treated the IDOC with RSNAT00 without any stop.
    Do you have any ideas how I can do this?
    Herbert

    >
    Herbert Schlup wrote:
    > I have 2 entries for my DWSADV01
    >
    > 1 with FM IDOC_INPUT_DESADV and the other with IDOC_INPUT_DESADV1
    With the first one, you cannot do much, as there is no user exit in it. But in the second one, there is a user exit when the idoc data is parsed the exit name is EXIT_SAPLV55K_004 and is called in the subroutine  DESADV_IDOC_PARSE in the function.
    But please note that the function IDOC_INPUT_DESADV1 is used with process code DELS for message type DESADV and Idoc type DELVRY01 and IDOC_INPUT_DESADV  is used with process code DESA and message type DESADV with IDoc type DESADV01.  So you might be using IDOC_INPUT_DESADV  function and unfortunately there are no user exits to handle your requirement.
    My advice would be to check with the source system or the middleware to define the mapping of these fields according to your requirement. But if that is not possible, then you need to first check which message type and IDoc type you are receiving and proceed accordingly
    KR,
    Advait

  • IDX2 Communication Error - Problem with only 1 IDoc Type

    Trying to import metadata via IDX2.  All IDoc types have imported succesfully, except DELVRY03. 
    I get a message saying "Communication Error" Message #: IDOC_METADATA407.
    I have tried DELVRY01 and it imports fine.  But, DELVRY02 and DELVRY03 both give the "Communication Error" messages.
    Any ideas why this one particular type will not import?  Settings/logon have not changed.
    Thanks

    FYI, Update... I think I may be on to something here...
    All checks in WE30 return okay.
    I debugged the IDX2 program, error is occuring in the 'IDOCTYPE_READ_COMPLETE' function call.  It is returning with message: 'Structure of segment E1EDD10 is unknown'.  Did search on this in OSS and found note #491264 -- Output of IDoc DELVRY02/DELVRY03 does not work
    Symptom
    You want to display IDoc DELVRYnn (nn = 02,03), SHPMNTnn (nn = 03,04,05), or PLNSHPnn (nn = 01) via the IDoc documentation transactions. The sys
    Comment: This relates only to the display of the IDOC structure. The IDocs work for the data exchange.
    Still working through the note to see if this will fix the issue, but I just tried to import in SHPMNT03 and I get the same error.
    Thanks.

  • WMMBID02 idoc type for 313 movement

    Hi,
    I want to integrate two step movement (313-315) in a third party system to SAP. Now we are using WMMBID02 idoc type for stock transfers but when I tested movement type 313 I got an error  ""you have entered a movement type that has not been defined for this transaction/event.
    Does it mean that WMMBID02 idoc type is not used for 313 stock movement?
    Which idoc type should we use?
    Thank you

    Hi,
    Problem is happening becuase of Transaction code used in IDOC header segment, try checking the tcode used and whether its valid for the mvt 313 (u can check this in transaction code OMJJ),
    if i can guess it right, u should try using MIGO  in your idoc, if it doesn't work try using MB1B,
    IF you are in version 4.6c or below, then MB1B will work (MIGO is allowed for transfers only after 4.7 and above)
    hope this helps
    Reg
    Dheeraj

  • RSAR238 : IDoc type for source system T90CLNT090 is not available

    Hi all,
    I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
    1. Error:
    R7I028
    Object could not be activated
    2. Error:
    RSAR238
    IDoc type for source system T90CLNT090 is not available
    Error when creating the export datasource and dependent objects
    Kindly help me with this error.
    Thanks and regards,
    Dhanapal

    Hi,
    Check the same in SDN..
    Object ZDUMMY could not be activatedMessage no. R7I028
    Re: DSO Activation problem
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
    http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
    Thanks
    Reddy

  • IDoc type could not be determined for the IDoc

    I am trying to Post the payment run through the transaction F110.
    In the payment run log i get the following message:
    "IDoc type could not be determined for the IDoc"
    But in fact the IDoc is generated and it is displayed in We05.
    I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
    Has anybody Idea about why this error is coming and how i can resolve this?
    This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
    Would appreciate if anyone can please help on the same.
    Thanks & Regards,
    Narayanan

    Hi,
    If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
    still if you are having any problem
    Check in the below path:
    IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
    2. Assign Release Approval Procedure for Release for Payment
    3. Define Users with Authorization to Payment Release
    Thanks
    Chandra

  • Modify BP in CRM using Idoc type BUPA_INBOUND_MAIN_SAVE_M03

    Hi,
    I want to modify(add) a new role to an existing BP in CRM.
    I am using the Idoc type BUPA_INBOUND_MAIN_SAVE_M03 for the same.
    The problem that I am facing is that even though I am wanting to modify the BP, whenever this IDoc is posted the existing roles (seen in table BUT100) for the BP get deleted and the  new role is added through the interface.
    Please can anyone assist me as what is going missing in the filling the segments.
    Regards,
    Taher
    the segment structure is as below.
    BUPA_INBOUND_MAIN_SAVE_M03
    E101BUS_EI_EXTERN             
      E101BUS_EI_HEADER
            E101BUS_EI_INSTANCE
        E101BUS_EI_CENTRAL_DATA
            E101BUS_EI_ROLES
                E101BUS_EI_BUPA_ROLES
                    E101BUS_EI_ROLE_DATA
                    E101BUS_EI_ROLE_DATA_X

    Hi,
    I figured out the solution to this.
    Get the existing roles for the BP using the FM BAPI_BUPA_ROLES_GET.
    Append the existing roles along with the new role that is required to be added.
    the task type should be I (Insert).
    When the Idoc is posted the existing roles do not get overwritten and the new role is added.
    Regards,
    taher

  • Problem in  Outbound IDOC from SAP R/3

    Hi,
    I am working on to send an IDOC from SAP R/3 to XI.
    I configured all necessary things as follows:
    1. Created for XI in sender system -- RFC dest, PORT and a partner profile with an outbound parameters and reciever port as XI port.
    2. created for sender system in XI -- RFC dest, PORT(as SAP<SID>) in IDX1 and assigned an idoc type(coming from sender system) to the port.
    Now I am trying to push the IDOC from sender system using Test IDOC transaction and gets success message as data is passed to port.
    My problem is I am not able to see any message in SM58 of XI server.
    Could anyone help me out?
    Thanks In Advance.
    Yaseen.

    Yasseen,
    you hardly see the idocs in Xi in sm58. Try sxmb_moni.
    If you see anything there try sm58 on the sending R/3. There you see if you have connection problems (eg authorization in XI or missing receiver determinitions).
    Hope it hellps,
    helge

  • XI Problem: File to Idoc Scenario - IDOC_INBOUND_ASYNCHRONOUS

    Hi,
       I'm having problems with inbound IDOCS in R/3. The idocs from XI are sent as tRFC using the FM IDOC_INBOUND_ASYNCHRONOUS and this is a problem because i have like 200 or 300 idocs to be sent at the same time and each IDOC takes like 5 minutes to process, hence the system crash due the amount of simultaneous logins (error message ThISend: ThRollout ).
    I need to fix this problem using some kind of serialization and the use of the function module IDOC_INBOUND_IN_QUEUE.
    Does anyone know how to achieve this?.
    The scenario configuration in XI and R/3 is as follows:  (PI 7.0 SP15) - (R/3 SAP ECC 6.0)
    File to Idoc.
    Sender CC->
    File content conversion
    Exactly once in order
    Receiver CC->
    IDOC protocol
    Queue Processing
    R/3 Partner profile config.
    Message type BOMMAT
    Trigger immediately
    Thanks.

    Hi,
    You have to split the messages in the sender file adapter, by using the parameter "Recordsets per Message".
    I hope that it will solve your problem. Please see the below link, it might be useful to you.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
    Regards,
    Rajesh

  • Port &1 segment defn &2 in IDoc type &3 CIM type &4 do not exist

    Hello,
    I've a question. We would send an standard IDOC from the 4.6C System to our SAP Xi 3.0. I customized the XI with TA IDX1 and IDX2. If we trigger the IDOC to XI I get the follow error message back:
    Port SAPQ73 segment defn E2EDL20002 in IDoc type DELVRY03 CIM type &4 do not exist.
    The IDOC Vers. is 4.6. In another system with IDOC Vers. 6.20 isn't a problem. So I think its a problem of the IDOC Version, or? So I checked the forum about this topic but I didn't find anything. So, I hope you can help me. Kind Regards Stephan

    Hello,
    I have exactly the same issue... We're currently upgrading our SAP system 4.7 to ECC6.0. We're also upgraded the system to an unicode system.
    Before those change, the interface between SAP and Xi worked well. Since the upgrade, those idocs don't pass any more and get the same error message than Stephan.
    I've checked the authorization of the RFC user and he has SAP_ALL and SAP_NEW. Partner profile, RFC connection, port and distribution model didn't changed.
    Do someone have an idea why this can appear ?
    Thanks in advance.

  • Want to add multiple idoc type with single message type.

    Hi Gurus,
    I have a problem. I want to add multiple idoc type with single message type in WE20.
    How we can do this in WE20 or is there any other way to do that?
    Please help me.
    Thanks in advance.
    Srimanta.

    hi,
    basically in partner profile i.e. in we20 , we add details to the receiver / sender port that we have created using we21.
    so what exactly we do in that is that we first use the message type for those idocs that we have created.
    now based on those message type we create a process code. now this is the reason why you cannot apply several message types with the same name in we20... as process code is unque for each message type.
    so thats why you can only assign the same message name to several idocs in we82 and then in we20 define the process code for that message type.
    it will solve your problem.
    hope this will help you!!!
    Thanks & regards,
    punit raval.

Maybe you are looking for