IDOCs - IDOC type ORDERS05 with message type MSGCHG

Hi,
I'm in my first IDOC project and I'm facing a problem. I need to change sales orders with EDI messages, so I've decided to use message type ORDCHG and IDOC type ORDERS05. I'm filling segments E1EDK01, E1EDP01 and E1EDP19. In header the action is '003' to indicate I'm going to change items, and in item the action is '002' - change. I'm not changing all items of the order, so I only fill item segments for the item I want to change.
The problem is the F.M. IDOC_INPUT_ORDCHG looks to use batch input technique to update the order and the BDCDATA contents does not look good. And I receive a message saying VBAP-PSTYV is not an input field. I'm not entering the contents of PSTYV in segment E1EDP01.
Does anyone have any idea of what can be the reason for this problem ? For the error, and for the fact of the contents of BDCDATA do not look good.
And any idea of how to solve it.
And does anyone knows if the batch input technique is mandatory, or is there any way to avoid it like forcing the standard to use a BAPI ?
I'll really apreciate any possible help, because i'm without any idea about how to solve problem.
Thanks in advance,
Paulo Sousa

If you go to SE11 and enter VBAP then finf the field PSTYV, double click on the field and see if the !fixed Value. ex" field is ticked, if it is this means that SAP is trying to get a value for this field from a fixed set of values.
You could try using WE19 to mess around with the IDOC in error and process the document as a standard inbound IDOB.  See here https://websmp105.sap-ag.de/~sapidb/011000358700002529571998E/default4.htm for some field entry examples
Hope this helps,
Conor.

Similar Messages

  • How to get the IDOC name attached with message type (IDoc at receiver end)

    Hello Friends,
    I have configured the Order Confirmation Idoc.And the port used is XML_HTTP. in this port generally the idocs are sent to a java servlet.
    So there the idocs are being created with name  :- Idoc_no.XML
    but i need to get the IDoc name prefixed or attached with the message type name, that the particular idoc uses.
    waiting for your replies .
    thanks,
    jeevan

    Hi Jeevan,
    I am sorry for the confusion, the solution i provided is used when we go for XML FILe port. But when we go for XML HTTP port, this option is not available in SAP. So we need to check with the target system, whether there is any option available to read the file contents before saving , so that we can save the idoc with the required file name .
    With my knowledge i assume why this option is not there for XML HTTP port is when we use XML HTTP port the idoc will be converted into XML and will be transported over HTTP protocol to an remote system which may be any type like XI, Java Servlet, Business connector, .Net etc. So in that case all the systems may not support the file name what we propose from the SAP. This is my assumption.
    Please go through the help provided by SAP for XML Port types
    http://help.sap.com/saphelp_nw04/helpdata/en/21/e9c975eb1911d6b2ea00508b6b8a93/frameset.htm
    Please check with the Java guys who are working at the target end, whehter they may help you to resolve.
    Thanks & Regards
    Vijayanand Poreddy

  • Idoc ORDERS05 with Custom Message Type

    We want to use a Z message type for idoc type ORDERS05 to be able to separate a particular group of partners from other partners using ORDERS/ORDERS05.
    The goal with our Z message type is to use the standard function IDOC_OUTPUT_ORDERS. The only problem I see is that this function checks the message type in form READ_SERVICE_PACKAGE. It would ignore this code since my message type is a Z and it's checking for message type ORDERS. 
    I was thinking of using a Z wrap-around function to perform the same code in form READ_SERVICE_PACKAGE if the message type is my Z message type.
    I want to avoid creating a Z copy of IDOC_OUTPUT_ORDERS and all if the includes!!!
    Any suggestions?

    Hello Bruce,
    The function module is associated with the process code.
    Why do you need a new message type?
    Regards,
    Samir.

  • 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

  • Error in idoc of basic type artmas05 - status 51 with Message no. MG537

    Hi all,
         I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
    *The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required
    field; it does not contain an entry
    *The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry        
    *The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    *You have not fully maintained the tax classifications
    *The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
    It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
    Thanks in advance,
    Revathi.

    Hi,
    Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
    The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
    The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
    The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
    The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
    Regards,
    Gowri.S

  • 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

  • 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.

  • 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

  • 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 generation with Message Type HRMD_A with filter on Personnel Area

    Hello All,
    We are facing an issue in generating IDoc using the standard message type HRMD_A.
    When we have no filters on the Distribution Model, the IDoc is generated through RBDMIDOC. When we use the filter on BUKRS, it generates the IDoc but gives an error status "Cross-system company code XXXX does not exist". I know to how resolve this issue. But, we tried to filter the changes with Personnel Area this time. So I have used the field PERS_AREA in BD59 with segment type E1PLOGI. When I run the standard report RBDMIDOC it gives the message "No data selected for distribution".
    I have checked the field name PERS_AREA from table TBD10, and it is mapped to T500P-PERSA. Change pointers are triggered and stored in BDCP2. Request experts to suggest what could be wrong with this.
    Thanks,
    Anil

    Hello Michele,
    If you have added BUKRS in BD59 for the message type, you will see Company Code (not filter1) in your filter criterion in BD64.
    Have you included the following code in FILTER_VALUES_SET method of the BADI implementation.
      CHECK OTYPE = 'P '.
      SELECT * FROM PA0001
               INTO PA0001 WHERE PERNR =  OBJID
                           AND   BEGDA <= SY-DATUM
                           AND   ENDDA >= SY-DATUM.
    record is valid today, no authorization check
        EXIT.
      ENDSELECT.
      IF SY-SUBRC = 0.
        FILTER1 = PA0001-BUKRS.   ELSE.
        CLEAR FILTER1.
      ENDIF.
    Lastly, just make sure the record you are testing for has your desired company code PGPB.
    Regards,
    Anil

  • Outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON

    Hi Friends
    I am trying to pack outbound delivery with Inbound IDOC DELVRY06 with Message type SHPCON.
    But IDOC has error Specification of destination HU missing.
    Could you please help us to resolve the issue to Pack the outbound delivery with the  IDOC.
    Thanks
    SR

    HI Ian Kehoe
    Sorry for delay in reply
    Thanks you very much
    I solved that problem .
    Could you please advice  test data for IDOC  DELVRY06 packing hierarchy (multi level packing) to pack SAP outbound delivery.
    Thanks
    Ravi

  • No authorization to send IDocs with message type R

    I'm in the process of installing some business content for a 3.5 prototype.  When trying to load some master data I get the following error in the transactional RFC in the source system.
    "No authorization to send IDocs with message type R"
    Any clues to what may be causing this?
    Any help appreciated.
    thanks
    Mike

    Hi Michael,
    the suggestion for SAP_ALL was just for testing purposes in order to see whether it works then. If security is an issue you should reduce the authorization to the ones really needed (see note).
    Another security option is to make the background user a system user and not a dialog user.
    Regards, Klaus

  • 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

  • ORDERS05 Idoc Type Extension

    Hello,
    I am extending the segment E2EDKA3 in ORDERS05. Please let me know any user exit or any other way to populate the values in the extended segments.
    I am adding these fields: VBPA-KUNNR,VBPA-ADRNR,VBPA-XCPDK & VBPA-ADRNP                         .
    Thanks in advance,
    Suresh

    Hi Suresh,
    Go through this info ucan able to do.
    Enhancement of IDoc Type
    Usually enhancement takes place when the content in IDocs provided by SAP are not sufficient for the business process. IDoc extension can take place whenever dictionary table has a new structure appended required by the business process. 
    In brief IDoc extension takes place when extra fields are required for the business process.
    Let us take a scenario and understand the process of IDoc extension.
    In this scenario say visitor is different from the actual customer who has came to the sales office in behalf of the customer to obtain the quotation or inquiry etc. Or an authorized agent qualified by the actual customer to order for items. So a field by name NAMEVI (Visitor) is added to Customer master data. As there is no provision given by SAP to handle this, we need to extend an IDoc. 
    The standard message type and IDoc type provided by SAP are DEBMAS and DEBMAS05. 
    Consider the data in the table below for extending the IDoc. These details can be understood in different sections in the process of extending it. 
    Basic IDoc type      DEBMAS05
    Version      4.7
    IDoc extension      DEBMASEXT
    Custom segment      Z1KNA1
    Fields in Custom Segment      Visitor
    Parent of Custom Segment      E1KNA11
    Outbound process
    Step1. Customize kna1 table by appending a structure provided by SAP (ZAKNA1) 
    Component                Component Type
    VISITOR                     NAMEVI
    Step2: Write a module pool program to update some existing customers to add data  for Visitor. 
    Step3: Create a custom segment
    Transaction Code: WE31
    Segment type: Z1KNA11   Click  (create). Provide short text 
    Field Name                Data element
    VISITOR                NAMEVI
    Save 
    Step4: Create IDoc extension
    Transaction      WE30
    Object Name      DEBMASEXT
    Choose Extension
    Click   and it leads to next screen.
    Linked basic type: DEBMAS05
    Provide description and enter
    Observe all the segments to be copied into your IDoc extension from linked basic
    type.
    Select E1KNA11 and click  (create segment) to obtain a popup window
    Provide the required values and observe child segment Z1KNA11 to be added to
    parent segment E1KNA11. 
    Step5: Release segment and IDoc extension
    Transaction: WE31
    Segment type: Z1KNA11
    Path: Edit à Set release
    Step6: Assign Basic type to extension / messages
    Transaction: WE82
    Click  , then 
    Select DEBMAS message type against DEBMAS06 basic type
    Click   provide the information
    Message Type      Basic Type      Extension      Version
    DEBMAS      DEBMAS06      DEBMASEXT           4.7
    Delete the earlier one from which it was copied.
    Save. 
    Observe the result as follows
    Step 7: Check and Transport IDoc extension
    Transaction: WE30
    Object name: DEBMASEXT
    Path: Development object à Check
    Ensure that there are no errors or warnings
    Now transport
    Path: Development à Transport 
    Step8: Find suitable user exit for writing code to support IDoc extension
    Transaction: SE84.
    Click Enhancements
    In short text provide customer
    Find suitable enhancement to be VSV00001 
                             Alternative way
    Transaction: SMOD
    Click F4 help for Enhancement
    Path: F4help à SAP Applications à Logistics general à Logistics Basic Data à
    Business partners à Vendor Master.
    Find the enhancement as VSV00002, which is an approximate user exit.
    Now search for different extensions like VSV00001. Then see for its components.
    Identify the appropriate user exit to be ‘EXIT_SAPLVV01_001’ (Create Export of
    Additional Customer Master Segments). This user exit can be used in outbound ALE
    process, meant for filling the data into custom segments. 
    You have to identify here another user exit as ‘EXIT_SAPLVV02_001’, which is
    helpful for inbound ALE process. This user exit can be used to read the segments
    and post it to Application repository. 
    Step9: Develop a project to encapsulate enhancements and components.
    Transaction: CMOD.
    Enhancement: custex and click Create to provide attributes.
    Click Enhancement Assignments.
    Provide VSV00001, short text and save.
    From the initial screen of the transaction, select components and click change.
    Find 4 components to be added.
    Activate them.
    Select user exit EXIT_SAPLVV01_001 for outbound process and double click it. It leads to function builder.
    Double click on provided include program ZXVSVU01 and press enter.
    Now, write supporting code for IDoc extension, i.e., populating custom segments in IDoc.
    Check the code and activate.  
    Code in ZXVSVU01
    *& Include           ZXVSVU01                                         *
    *In this scenario, the E1KNA11 has been extended to accommodate
    *User-defined fields in the customer table kna1. The name of the
    *extended
    *segment is z1kna11. There is one custom field: visitor
    *Data declarations
    DATA: kna1m like e1kna1m,
          kna11 like e1kna11,
          z1kna11 like z1kna11,
          w_kna1 like kna1. 
    make sure you are processing correct message type
    check message_type eq 'DEBMAS'.
    make sure data is added after the correct segment
    check segment_name eq 'E1KNA1M'.
    since customer number is not passed in this user exit, you need to go
    through the data records to find the customer number
    loop at idoc_data.
      case idoc_data-segnam.
         when 'E1KNA1M'.
           move idoc_data-sdata to kna1m.
         when 'E1KNA11'.
           move idoc_data-sdata to kna11.
      endcase.                             " case idoc_data-segname.
    endloop.                               " loop at idoc_data. 
    select data from the user-defined fields in kna11.
    select single *
      from kna1                            " Customer master table
      into w_kna1
    where kunnr = kna1m-kunnr.
    if sy-subrc eq 0.
    set the idoc extension name for control record
      idoc_cimtype = 'DEBMASEX'.
    clear custom fields from kna1 to extended segment
      clear z1kna11.
    copy custom fields from kna1 to extended segment 
    move-corresponding w_kna1 to z1kna11. " field name must be same
    condense all fields of extended segment
      condense: z1kna11-visitor.
    populate segment name in the data record, copy data contents into it 
    and append the data record to existing data records in
      move 'Z1KNA11' TO IDOC_data-segnam.    " administrative section
      move z1kna11 to idoc_data-sdata.       " data section 
      append idoc_data.
    endif.                                 " if sy-subrc eq 0.
    Step 10: 
    Define Logical System
    Assign client to Logical System
    Maintain RFC Destination
    Maintain Customer Distribution Model
    Generate Partner Profiles
    Distribute Customer Distribution Model
    INBOUND PROCESS
    Step 11: Append the custom structure to the table KNA1 similar to the process done
            in outbound process.
    Step 12.
    Define Logical System
    Assign client to Logical System
    Generate Partner Profiles
    Step 13. Execute the transaction to ‘Send Customers’ from Outbound system.
    Step 14. Now in the Inbound system, create the project in the similar way as done at
            outbound side.
    In the user exit EXIT_SAPLVV02_001, find include ‘ZXVSVU02’. Write the code to
    support IDoc extension.
    Code in ZXVSVU02
    *&  Include           ZXVSVU02                                         *
    data: kna1m like e1kna1m,
          kna11 like e1kna11,
          z1kna11 like z1kna11.
    data fs_kna1 type kna1.
    message i000(0) with 'INBOUND PROCESS CALLED'.
    LOOP AT IDOC_data.
      case idoc_data-segnam.
        when 'E1KNA1M'.
          kna1m = idoc_data-sdata.
        when 'E1KNA11'.
          kna11 = idoc_data-sdata.
        when 'Z1KNA11'.
          z1kna11 = idoc_data-sdata.
          select single *
            from kna1
            into fs_kna1
           where kunnr = kna1m-kunnr.
          if sy-subrc eq 0.
            update kna1
               set visitor = z1kna11-visitor
             where kunnr = kna1m-kunnr.
          else.
            idoc_status-docnum = idoc_control-docnum.
            idoc_status-status = '51'.
            idoc_status-msgty = 'E'.
            idoc_status-msgid = 'ZE'.
            idoc_status-msgno = '005'.
            idoc_status-msgv1 = kna1m-kunnr.
         append idoc_status.
          endif.                           " if sy-subrc eq 0.
      endcase.                             " case idoc_data-segnam.
    endloop.                               " LOOP AT IDOC_data.
    Step 15. Assign FM to extension/Message type
    Transaction:      WE57
    Path: Change à New Entries
    Select ‘IDOC_INPUT_DEBITOR’ against DEBMAS06 basic type, to fill extra
    information as shown below.
    Function Module          Basic Type     Message Type          Extension
    IDOC_INPUT_DEBITOR     DEBMAS06     DEBMAS          DEBMASEXT
    Step 16. Execute the transaction to ‘Get Customers’.
    And observe that records with extra data are saved in database.
    Rewards some points.
    Rgds,
    P.Nag

Maybe you are looking for