Inbound IDOC Failure with WE19

Hi , we are testing a standard IDOC CONF21(inbound) with the test tool WE19.
We have created a FILE port in WE21
We have created a partner relationship in WE21 with inbound parameters (process code CON2)
In WE19 we have populated oly sender and logical message type, plus the segment data. When we try th IDOC in WE19 we have an error in the control record: (partner profile not available)
IDoc 0000000000001027 Current status: 56
        Control record Direction: Inbound Sender: LS/ /IDOCTEST
        Data records Total number: 000001
            E1CONF2 Segment: 000001 CC2 confirmation structure
        Status records
            56 IDoc with errors added
    Message: EDI: Partner profile inbound not available
Is there anyone who can help me for this problem ?
Tanks and Regards,
Riccardo.

Yes we have created a partner profile in WE20.
This is the check log, it seems to be correct...
     Partner profile IDOCTEST /LS
     Header entry (table EDPP1)
     Correct partner status
     Recipient of notifications exists
     Entries for inbound processing (table EDP21)
     Entry IDOCTEST /LS/ /CONF21 /
     Process code (inbound) exists

Similar Messages

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

Inbound idoc failure(vendor invoice not posted)

Hi All,
we have two SAP systems. SAP A and SAP B.
SAP A is the vendor for SAP B system we have created a sales order/delivery/out bound invoice in SAP A system.The sales order has BOM material with main item and sub items. We have the same material master data and BOM master data in system A and system B since we are following split architecture.
The outbound invoice(with main and sub item) in system A has generated an outbound idoc and the idoc has gone to SAP
system B. There are the usual segments like E1EDP01 for main item and another E1EDp01 for the sub itmes in the outbound
idoc.The message type is INVOIC and basic type INVOIC02 with no extension.
In system B, the inbound idoc (coming from system A) has failed giving the error message "higher level items not allowed". The
segment E1EDP01 for sub item is highlighted in red ! basically the inbound idoc in sap system B is posting a vendor
invoice since the inbound idoc in B is calling the FM IDOC_INPUT_INVOIC_MRM... I think this is doing vendor invoice
verification.
I have checked in system A, all is ok and the outbound idoc is ok but the issue is in sap system B, the inbound idoc has failed
with message "higher level items not allowed". The segment E1EDP01 for sub item is highlighted in red in inbound idoc in
system B. The segments are the same for inbound idoc in B and outbound idoc in A.
Can someone pls tell what is wrong in system B.(config or data issue) as we are managing both systems.
regds

Hi,
I am not sure if we can send both main and sub items thorugh inbound invocie idoc to create vendor invoice.
you can try to post the idoc by removing main items from the IDoc in WE19.
one more thing you should aware is you are not allowed to to create two E1EDP01 segements for the same PO item(E1EDP02).
check this as well.
Regds,

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
          EXPORTING
            pernr                          = ins_objects-objid       "#EC DOM_EQUAL
            actio                           = 'INS'
            tclas                           = tclas
            dialog_mode               = dial_mode
            luw_mode                  = '0'
            no_existence_check = $cross
            no_enqueue              = $cross
          IMPORTING
            return1                       = return
            hr_return                    = hr_return
          TABLES
            proposed_values    = proposed_values.
        REFRESH proposed_values.
     IF hr_return-msgty = 'E'.                           "note 984409
      CLEAR protocol_error.
      protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
      READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
                                       infty = hr_return-infty
                                       subty = hr_return-subty.
      protocol_error-segnum = t_hrobjinfty-segnum.
      protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
     protocol_error-msgty = hr_return-msgty.
      protocol_error-msgid = hr_return-msgid.
      protocol_error-msgno = hr_return-msgno.
      protocol_error-msgv1 = hr_return-msgv1.
      protocol_error-msgv2 = hr_return-msgv2.
      protocol_error-msgv3 = hr_return-msgv3.
      protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
Thanks!

Inbound IDOC FM with BAPI

Hi Everyone,
I need some information about posting an application using inbound IDOC with BAPI. I need to write a FM for
Inbound IDOC with BAPI to post it. Can some one give me direction as where to start as I am new to BAPI.
Thanks in advance.
Regards,
vicky

Hi Vicky,
Please take a look at this link which will show step by step on how to setup inbound proscessing.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Also check this links for sample codes.
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
Hope this will help.
Regards,
Ferry Lianto
Message was edited by: Ferry Lianto

Processing inbound Idoc ORDERS03 with status 51

Dear ALL
While processing inbound idoc with message type ORDERS03 i am getting a status 51 with below erros
I have maintained the data under VOE2 & VOE4 but not got the solution. We are on SAP ECC6 Version
Customer 1100 is customers purchase organization
Partner no 1109 is customers plant
VKORG, VTWEG, SPART cannot be determined for customer 0000001100 , vendor REN15D
Message no. VG204
Terms of payment in IDoc E1EDK18 have been transferred: Check data
Message no. VG202
Partner number 1109 for customer 0000001100 , partner function WE does not exist.
Message no. VG140
Regards
Arun

Hi,
Vendor 100002 is not maintained in your system. Maintain the same or use some other vendor which is there in your system.
You should be able to post the document.
Regards,
Lalit Kabra

Email on Idoc Failure with Status 56 64 68 69 70

We have standard inbound idoc processing for Basic Type : DELVRY01 and Message Type : DESADV using the function module IDOC_INPUT_DESADV1.
We currently have a requirement to send an email, when any of these type of Idocs fail with status 56, 64, 68, 69 and 70.
Where would be best place to provide this solution to send an email to a particular user when the Idoc fails with the above status?

Hello Saleem,
One approach would be to consider workflow based on object type IDOCAPPL. The start condition for the workflow could be the triggering of the event errorProcessCompleted. You could filter further by status and your message type (DESADV ) to only start the workflow for the errors that you mentioned. The workflow could then send an email.
You will need to verify the details for your own scenario.
Good luck,
Greg Kern

How to solve the INFREC Idoc failure with message type

Hi,
Please let me know how can we solve the INFREC Idoc with the message type" Not possible to set tax code without tax calculation schema"
Pl suggest me how to tackle this Idoc failure.
Regards
Raj

Hi,
An\ybody..please suggest.. It is very urgent..
Regards
Raj

Workflow for inbound idoc failures

Hi Gurus,
Can anybody please point me to a place where i can start to see how i can setup workflow to notify users via SBWP whenver there is an inbound idoc error happens. We want to derive the standard functionality to its fullest even before thinking of putting any custom code. I'm specifically looking for hte order acknowledgemetns and shiipping notifications errors of idocs coming from the vendor
Thanks
anusha
Edited by: anusha vemulapati on Jul 2, 2011 4:43 PM

Hi Anusha,
The simplest way is to link the partner profile to a specific user ID. This is done in trs WE20 - you have the link to the WF recipient both generally for the partner (on the initial screen of WE20 when the partner has been selected) and specifically for the different message types - double-click on the inbound message type and choose the tab "Post processing - permitted agent".
You link the partner profile to a specific user by choosing the user type = "US" (user") and then specifying the user name below it. If you want several users to receive the same WF, you can link the partner profile to another user type, e.g. O = Organisational unit. Then you link the users to the organisational unit in trs PPOME.
As far as I remember, the WF for IDoc's in error is activated in the standard system, i.e. the setting above shall be sufficient.
BR
Raf

Inbound IDoc error with status 51 : No unique SA could be determined

Hello,
when I would like to create AAU by EDI info;
ORDERS05, DELORD type
how can I set mandatory item for AAU?
Please help
Edited by: Hiroko Numano on Apr 9, 2008 7:13 AM

Hi,
Vendor 100002 is not maintained in your system. Maintain the same or use some other vendor which is there in your system.
You should be able to post the document.
Regards,
Lalit Kabra

Goods receipt against process order with inbound idoc

Hi Experts,
We need to post good receipt against process order with movement type 101 and for By-product 531.
Can we use inbound idoc-WMMBID02,with message type WMMBXY to achieve this functionality?
Or please advise if we can achieve this from any other Idoc type.
We are getting below field values for external system
1. process order number
2.plant
3.material
4.quantity in unit of entry
5.unit of measure
6.storage location
7. movement type
8.Batch
Kindly advise how can we achieve this.
Best Regards
CS

261 and 262 are two different movement types INDEPENDENT of each other. I definitely know for the fact that SAP allows you to create a 262 without a 261. if you were to restrict it... you can disable access through a tcode for that mov. type 262 and ask users to use MBST to cancel any material documents created via 261 movt type.. that would ensure a smooth process

Inbound IDoc w/message ORDERS - issues with error processing

We are using inbound IDoc ORDERS05 with message type ORDERS to create the sales orders in SAP. In WE20 we have the following settings:
- partner type LS (= Sales Org VKORG)
- process code ORDE
- trigger by background program
- post-processing agent of type US (user) with a user ID.
We create IDocs through an ABAP program and use RBDAPP01 to post the IDocs. When there is an application error in the IDoc posting we expect the designated user to receive a workflow item in the SAP Inbox, but for some reason this is not happening.
I did some research and went through all the possible settings for workflow, task, etc. and everything seems to be set up correctly. When debugging RBDAPP01 I have noticed that it calls FM APPLICATION_IDOC_POST_IMMEDIAT, which, in turn, calls IDOC_START_INBOUND. If IDOC_START_INBOUND returns SY-SUBRC = 1 then the workflow item is sent correctly to the designated user, exactly as we want. But for some reason it returns 0 (I changed it to 1 in the debugger).
It seems that IDOC_START_INBOUND reads TEDE2 records (TEVE2-EVCODE = ORDE) and sy-subrc = 1 is only possible when EDIVR2 is 1,2,3 or 4. In our case TEDE2-EDIVR2 = 6. It seems that TEDE2 is maintained in the transaction WE42. However, I tried to change the settings there but it affects the IDoc processing in whole (IDoc gets some odd status and doesn't get processed as before). I've also tried to use process code ORDE_BY_WORKFLOW in WE20 with the same "success".
What do we need to do to get a workflow item for the errors that happen in the application layer when IDoc is posted? Is it even possible with this message type?
Any ideas would be appreciated.

Hi,
Can you please share how do you overcome the problem, so that it can be helpful for others.

Rejection of PO item with reason 06 - IDoc failure

Hi,
There is an IDoc failure with message: Rejection of PO item with reason 06.
The user(supplier) wants to reject first line item of the Subcontracting PO and add a new line item instead with the right data.
Please suggest.
Regards,
Akash Prekar

Hi Dirk,
You can actually use the BADI BBP_CREATE_PO_BACK to change the flag value before filling the PO Craetion BAPI interface parameters
Sangeeta

Inbound idoc pordcr101 status 51 "enter purchase org"

in the we19 standard inbound for idoc pordcr101 i see the following
EDIDC with the partner/port info
E1PORDCR1
E1BPMEPOHEADER
    comp_code 300
    doc_type "NB"
    vendor 58121
    purch_ord 3000
    purch_group 000
E1BPMEPOHEADERX
    'X' next to respective fields
E1BPMEPOITEM
     po_item 00010
     Material scw1212
     Plant    3000
     qty       1000
E1BPMEPOITEMX
     'X' next to respective fields
Each time i run the inbound idoc pordcr101 in we19 with the above i get
enter purch org
i am really really stuck because i am entering purchase org but for some reason it does not know about it
what am i missing
HELP
I deleted the unused segments

no successful idocs in we19 up to this point
i was told
E1BPMEPOHEADERX 'X' next to respective fields this is used to indicate which fields are being input.
so i am using both
it is purch_org not purch_ord

Prevent the Output Message when creating PO from inbound IDOC

Hi SAP Gurus,
In my project, I have to create PO from inbound IDOC (PORDCR) with a specific Document Type ('099').
Requirement: These PO should not generate the output message while the others (Doc Type # '099') do.
I have the Z fuction module which call BAPI_PO_CREATE for posting IDOC and it works fine.
In the existing system, there are some set up that trigger the output message type for PO (output NEU) when using ME21 or ME22, as a result my PO created with output message.
Can you please advise if there are some way (User Exit?) that prevent the output message in this scenario (specific PO Type) without touching the current Condition setup?
I'm new in MM and really need help!
Thanks,
Elaine.

Hi Vinod,
I really appreciate your anwer. I'm going to explore this with my functional consultant.
Just like to have more questions:
1. Is it easier if we change the existing condition table instead of creating a new routine?
2. There are two forms for routine 101 (FORM KOBEV_101 and FORM KOBED_101). Can you explain to me why we need 2 here for what purpose of each form.
3. In the debug mode by using WE19 to post inbound IDOC, I change the SY-SUBRC = 4 and PO created without output message. Is it the right direction? Anything else I need to pay attention to?
Thanks again.
Regards,
Elaine.

Inbound IDOC Failure with WE19

Similar Messages

Maybe you are looking for