File to IDOC mapping - Message Type WMMBXY

Hi
   I am working on FILE to IDOC Scenario. I have records like the following in my file:
301 ABC455559 03.11.2009 02u0391B13 01     OBAF515150 G378378 15 PC   20090311 MIGO
301 ABC455560 03.11.2009 02u0391B13 01     OBMN515040 437482 50 PC   20090311 MIGO
Using an ABAP Program I added DTL in front of every record as I have to convert text file to XML mapping.
DTL 301 ABC455559 03.11.2009 02u0391B13 01     OBAF515150 G378378 15 PC   20090311 MIGO
DTL 301 ABC455560 03.11.2009 02u0391B13 01     OBMN515040 437482 50 PC   20090311 MIGO
When I did this my mapping is fine from source side. For the above two records there are two records created in xml format. But only one record is created at target side. I changed message type WMMBXY to unbounded in the external message but still only one idoc is created.
Please let me know if anyone faced the same issue.
Thanks
Naga

1..Please mapping ur sorce node (has occurance 0..unbound) with target node.
2...change occurance in message tag in mapping for IDOC message
3...change occurance in message mapping for IDOC message
Regards,
Manisha

Similar Messages

  • How outbound idoc of message type WMMBXY is created? any program or FM name

    Hello Gurus,
    How outbound idoc of message type WMMBXY is created? any program or FM name??
    basic type : WMMBID01... i checked the idoc in my system, it does not have any process code....
    also, i checked the exit : EXIT_SAPLMBMB_001. It has some code but nothing to fill the segments...
    BR,
    Ks

    got the answer in : WMMBXY and WMMBID02

  • IDOC message type WMMBXY not including Serial numbers in GR material documents when created with reference to an Inbound delivery

    Hello,
    We currently have an inbound ALE process (message type WMMBXY and basic type WMMBID02) to post GR's against inbound delivery. If the inbound delivery item is maintained with serial numbers, we want those serial numbers to be pulled into the goods movement material document (and stored in SER03).
    Currently segment E1MBXYJ is maintained with the inbound delivery number in field VLIEF_AVIS and Inbound delivery item number in field
    VBELP_AVIS. In segment E1MBXYI, no purchase order is assigned and the fields EBELN and EBELP are blank. The movement indicator (KZBEW) has the value 'B'.
    Even after making the above settings, the serial number(s) maintained on the Inbound delivery item do not get saved to the material document.I did look at OSS note 833603 (Solution for 2 - GR for Inbound delivery) and we have followed the same settings. This works when there is no serial number in the Inbound delivery. However if we have serial numbers, the IDOC posts successfully, however the material documents in MB03 do not have any serial numbers copied over from the Inbound delivery where the serial numbers are definitely assigned.
    Any help you can provide is greatly appreciated!
    Thanks,
    Ashvin
    P.S
    If we manually create the GR via MIGO, the serial numbers are automatically applied to the GR material document. This is what we want to accomplish via the above IDoc process.

    Hi
    Try with enhancement MWMIDO08. See note 833603 - EDI: Goods receipt for stock transport order for further information.
    I hope this helps you
    Regards
    Eduardo

  • IDOC - message type WMMBXY(Stock transfer from quality to unrestricted)

    Hi Gurus,
    I have IDOC problem.
    Inbound message type WMMBXY(Stock transfer from quality to unrestricted), The status if I check in WM02 of Doc is "51-Application document not posted"
    Error Message ""Required function
    MB_CREATE_GOODS_MOVEMENT is not being processed".
    Please Help.
    Prashant

    Hi
    The Idoc whcile Posting using Message type WMMBXY calls the Function module L_IDOC_INPUT_WMMBXY & in turn this calls the function module MB_CREATE_GOODS_MOVEMENT.
    This function is not getting executed.
    Please check if the Movemnt type used is not active for WM movemnts.
    If you have used previously this movemnt type & now it is not working. Please take hlep of ABAPer  for debugging & finding the Root cause
    Thanks & Regards
    Kishore

  • To map batch number to serial number for inbound message type WMMBXY

    Hi Gurus,
    Can anybody guid me how to map batch number to serial number for goods receipt inbound EDI 861 message type WMMBXY  .
    And can tell me how to assign serial number in Purchase Order for serialized product for perticuler Batch number.

    hi dsk,
    thanks for your earliar reply,
    actually iam working on sapscript there i want to add batch number ,but i am not able to clear my doubt from where i get this.
    how can i map batch number with corresponding to PO num ber, '
    in the report i used structure vbplp with field charg"(batch num).
    also i want to know from which table i can get customer part number and Po number .
    how can i add batch num ,..
    from which table or with which field i can compare itr to get .
    sunny

  • RFC error "No authorization to send IDOCs with message type ..."

    Hi all,
    I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
    I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
    I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
    Any suggestions?
    Regards,
    Liesel

    Hi Liesel,
    The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
    Please check if the user id/Password that you have given has all the authorization.
    Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
    There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
    Regards,
    Abhy Thomas

  • Error : No authorization to send IDocs with message type MATMAS

    Hi All,
    My scenario is FILE-XI-IDOC.
    I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
    When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
    Do I need to give any authorizations on XI side or on R/3 side?
    If so, what is the authorization required?
    I could not find the note :837595.

    <i>You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
    This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
    Solution
    In transaction PFCG, extend the role of the logon user by adding the following authorizations:
    Authorization object S_RFC
          Field name RFC_TYPE value FUGR
          Field name RFC_NAME value EDIMEXT, SDTX
          Field name ACTVT    value 16
    Authorization object S_IDOCDEFT
          Field name ACTVT  value 03
          Field name EDI_CIM value ' '
          Field name EDI_DOC value TXTRAW01
          Field name EDI_TCD value WE30
    Authorization object S_CTS_ADMI
          Field name CTS_ADMFCT  value TABL
    Authorization object S_TABU_DIS
          Field name ACTVT      value 03
          Field name DICBERCLS  value</i>
    from the note mentioned above.
    Regards
    Bhavesh

  • Issue: "No Authorization to send Idocs with message type Orders" - IDX5

    Hi All,
       I am working on a File to IDoc(Orders.Orders05) scenario. The sender is PI Server and the receiver is the SAP ISR system. A technical system has been created in PI SLD for the ISR system and a Business system is added to that. The logical system created in ISR system using Tcode BD54 is added to the business system in PI. A new RFC destination is created in PI system to connect to the ISR system.
      On the ISR system Partner profile is created using TCode we20 with the same logical system name already created using Tcode BD54.
    When sxi_monitor is executed on the PI system, It shows checked flag on the Inbound side and Red flag on the Outbound side. And when idx5 is executed, it shows the new Idoc number and when it is double clicked, it shows the Status Text as
    "No Authorization to send IDocs with message type Orders".
    All authorizations have been provided on the Sender side.
    Please let me know if any authorization need to be provided on the ISR system or Is this an error on any settings.
    Thanks in Advance.
    Stalin S.

    Hi,
    Check this Thread which deals with the Authorization Issue
    RFC Adapter
    And also check this how to check whether u have sufficient authorization to send the Idocs or not
    To test the Authorization check
    Double click the RFC Destination that u have created in XI towards R/3 in SM59
    Select UtilitiesTestAuthorization test
    By this you can come to know whether your user is having the propper authorization or not
    REgards
    Seshagiri

  • Goods issue - Message type WMMBXY

    Hello,
    I am using message type WMMBXY and process code WMMB for generating idoc. I need to do goods issue using above setting. Is it possible to do goods issue using message type WMMBXY and process code WMMB?

    Mark,
    The messages
    Delivery has not yet been put away / picked (completely)
    Delivery has not yet been completely processed by WM
    are displayed when you try to do PGI on a WM-relevant delivery that has not been picked completely. I'm not sure what the pick order but we have the SAP system with and without WM and in WM we use "transfer orders" (transaction LT03) to pick the deliveries. In this case the picked quantity field is grayed out in VL02N and it's being updated when a TO has been created. TO also have to be confirmed (LT12, I think), so in our case the reason for such error messages would be that TO is either missing or not confirmed.
    We are successfully using SHPCON with PIC and PGI but only in our non-WM SAP system. In the one with WM I was unable to use IDocs to pick the deliveries due to the strict customer requirememts. So we use BDC (I even wasn't able to find an FM for that) to create and confirm TOs and then use only the PGI SHPCON IDoc.
    I have a feeling that you might need either a different or an additional IDoc for WM to pick the deliveries successfully. Take a look at the WM... IDocs, maybe you need the one that creates the transfer orders or something. Also with DELVRY01 IDoc you can use message type WHSCON, maybe it would work differently (although I didn't notice any difference in our case).
    If there is no IDoc for "pick orders" you might have to create your own ABAP program to run between the PIC and PGI IDocs to perform the missing step.
    Good luck!

  • Error while trying to post inbound idoc of message type COND_A

    Hi,
    I am getting error while trying to post inbound idoc of message type COND_A.
    If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
    and if providing value in above fields then dump is coming.
    How to solve ?
    Plz do reply
    Thanks
    Mohit

    I do not see any reason why you would need to use COND_A04  if COND_A01 is working.
    What if you could get COND_A04 to post and you would face the same result as in COND_A01?
    If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
    For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
    fixed a situation where the vendor number was not validated.

  • Creation of IDOC with message type INVOIC01

    Hi All,
    I am trying to create a new IDOC with message type INVOIC01.
    When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
    However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
    The client wants me to create IDOCs with basic type INVOIC01.
    Can anyone please help?
    Thanks in advance.
    regards
    Nagarajan

    Hi Nagaraj!
    I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
    Thank You,
    Natalija

  • Diff bet IDOC and Message Types.

    What are the difference between IDOC and Message types.
    Diff between MATMAS01 ,MATMAS02 and MATMAS03

    IDOCs:
    - IDOC is an Intermediate Document. It is simply a data container used to exchange information between any two processes  that can understand the syntax and semantics of the data.
    An IDOC is created as a result of executing an Outbound ALE or EDI process.
    In an inbound ALE or EDI process, an IDOC serves as input to create an application document. When an IDOC is created in the system , an unique number(16 Digits) is assigned to it.IDOC will wait until the Remote System is Active.
    Basic Idoc Type: Basic Idoc type defines the structure and format of the business document
    that is to be exchanged between  two systems. Basic Idoc type can refer to an SAP provided
    basic IDOC type or a customer developed basic IDOC type.
    - A basic IDOC type has the following characteristics:
    Name : A basic Idoc type can be assigned upto a thirty character name.
    List of permitted segments: The segments make up the IDOC structure.
    Hierarchy of segments : The hierarchy of segments specifies the physical sequence and any parent - child relationship in the segments.
    Mandatory Vs Optional Segments : When used in the IDOC type, each segment has an attribute that defines whether the segment  is option or mandatory. Minimum/Maximum range for each segment: It defines the maximum and minimum number of timesa data record corresponding to a segment cn exist in an IDOC.
    -Segments : A segment defines the format and structure of a data record. Segments are reusable componets. A segment consists of various fields that represent data in data record.
    IDOC Record Types:
    1. Control Record : The control record contains all of the control information about an IDOC, this information basically includes the IDOC number, sender and receiver information, and information such as the message type it represents and the IDOC type. 
    - there is only one control record per IDOC.
    - The stucture of the control record is the same for all the IDOCs and is defined by SAP.
    - The structure of the control record is defined by the data dictionary structure EDI_DC40. The control record is stored in the EDIDC table.
    2. Data Record : Data records contain the application data. A data record has two sections
    Administrative Section and a Data section.
    - The Administrative section cotain the segment name, client, IDOC number, segment number, hierarchy level information.
    - The Data section of a data record is a stram of 1000 bytes where the actual data resides.
    - The data record is defined by the data dictionary structure EDI_DD40.
    - Data records for IDOCs stored in the EDID4 table.
    3. Status Record : Status records are attaced to an IDOC throughout the process as the IDOC achieves different milestones or encounters an error. At every milestone a statu code, date and time are assigned.
    - Status codes 01 to 49 are reserved for OUtbound process, 50 and above are reserved for inbound processes.
    <u><b>IDOC TYPE IS AN INSTANCE OF IDOC</b></u>
    Message Type: Identifies what type of information transformed between logical systems or partners.Message type is not   a   local object type , it is transportable.
    For different applicatons we have different MESSAGETYPE.
    example:
    <u>APPLICATION</u>                <u>  MESSAGETYPE</u>
    MATERIAL MASTER                       MATMAS
    VENDOR MASTER                          CREMAS
    CUSTOMER MASTER                      DEBMAS
    MATMAS01, MATMAS02, MATMAS03, MATMAS04, MATMAS05 are all MESSAGETYPES  ... FOR NEW VERSIONS LIKE SAP 4.7EE, SAP ECC5.0....we have to use MATMAS05 message type. for older versions like SAP R/3 we have to use MATMAS01.
    REWARD ME IF THIS IS HELPFUL

  • Batches not getting updated by incoming idoc DELVRY03 (message type SHPCON)

    Hi
        I am using incoming idoc DELVRY03 (message type SHPCON) to update delivery document.I am using field E1EDL24-CHARG to pass batch data.
          However batch number is not getting updated in delivery document. I have verified aspects like batch number is valid etc.
         While updating batch number thru incoming idoc, do I need to supply some other data?
    Please help.
    TIA
    Koustav

    Hi Biswas,
    I think batches are determined automatically in the deliveries while creation and thats the reason it is not getting the batch number in the delivery, if there is no automatic batch dertermination then it will update the valid batch number
    also please check the batch determination procedure and the batch master in MSC2N and availability of materials for that particular batch
    regards,
    Santsoh

  • Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

    Hello All,
    I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
    Br,
    Sri

    Hi !
    Becaus alle this happens in beckgound, things are a bit difficult but solvable....
    What you should do is a "Authority trace" ... as follows....:
      - Go to the ST01
      - Mark "Authorisation Check"
      - Swich the trace on for your Workflow user
      - Execute the Workflow until the error uccurs
      - Go back to the ST01
      - Press the "Analyze" button and see what error occurs
    Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
    Regards
    rainer
    Some Reward poins would be nice if that helped....

  • IDOC of message type EUPEXR

    hi all,
    When I run RFFOEDI to gereate IDOCS, IDOCS of message type EUPEXR and PAYEXT are generated.
    I need to pass a value in a field in the control record for the IDOC of message type EUPEXR but in FM : FI_EDI_EUPEXR_IDCREF01_OUT  ( which is uesd to generate this IDOC ), control record is filled and before passing this control record to MASTER_IDOC_DISTRIBUTE, I could not find any exit to change its control record.
    Please help.
    Thanks and Regards
    Gurpreet Singh

    Hi Ferry,
    System checks for the IDOC version and then calls the EXIT if the versions are different .Following is the code snippet that ensures the above thing in include LBD11F0T :
      Change IDOC version if target <> current version.
      IF  F_EXCEPTION-MSGTY IS INITIAL
        AND (    F_IDOC_CONTROL-IDOCTP <> TARGET_IDOCTP
              OR F_IDOC_CONTROL-CIMTYP <> TARGET_CIMTYP ).
        PERFORM CHANGE_IDOC_VERSION TABLES   T_IDOC_DATA
                                    USING    TARGET_IDOCTP
                                             TARGET_CIMTYP
                                    CHANGING F_IDOC_CONTROL
                                             CHANGED_FLAG
                                             F_EXCEPTION.
      ENDIF.                               "End of  if subrc = 0
    Have you tested it ? Pls suggest if I am wrong somewhere.
    Thanks and Regards
    Gurpreet Singh

Maybe you are looking for