Process of inbound idoc

Hi,
can any one pls let me know the steps we should fallow in an inbound idoc processing.
I have the messagte type , basic type, process code and i have to create partner profile , pls let me know what are the steps to be fallowed
thanks,
Deepak

Hi,
U need to update the Purchase Order based on the idoc.
The Process Code for this development is: ORDR,
Basic IDOC Type: ORDERS05
Function Module: IDOC_INPUT_ORDRSP,
Message type: ORDRSP.
Enhancement: MM06E001
Customer Enhancement: EXIT_SAPLEINM_008
The logic should be written in the Include ZXM06U20.
LOOP AT idoc_data.
CASE idoc_data-segnam.
WHEN 'E1EDP01'.
Move Structure ACKNOW_PO info to Confirmations.
ENDCASE.
ENDLOOP.
Regards
Kannaiah

Similar Messages

Processes in Inbound IDoc posting

Hi guys,
I'm new with IDocs, and I have an object which requires Inbound IDoc posting..
Can you give me the possible steps/processes including the tcodes on how can I solve this object?
Please also include FMs that I might possibly used during my development.
I highly appreciate all your swift responses. Thanks!

Hi Mel,
You can use FM IDOC_INBOUND_WRITE_TO_DB to create an inbound IDoc.
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
    EXPORTING
      PI_STATUS_MESSAGE       = I_EDIDS
    IMPORTING
      PE_IDOC_NUMBER          = DOCNUM
      PE_STATE_OF_PROCESSING = STPROC
      PE_INBOUND_PROCESS_DATA = I_TEDE2
    TABLES
      T_DATA_RECORDS          = I_EDIDD
    CHANGING
      PC_CONTROL_RECORD       = I_EDIDC
    EXCEPTIONS
      IDOC_NOT_SAVED          = 1
      OTHERS                  = 2.
Regards,
Chandra Sekhar

Problem with processing edited inbound idoc

hi
i am editing an inbound idoc as a result it goes to status 69.
Then to process this IDoc through program 'RBDAPP01', i am changing the status of the idoc to 64 through IDOC_STATUS_WRITE_TO_DATABASE'.
But after that when i am calling transaction for RBDAPP01 passing the idoc number it gives me a message 'IDoc is still being processed' and the status is 64.
Any help on the same is highly appreciated.
Thanks.

Hi Anand,
If you have custom program written, please add FM <b>DEQUEUE_ALL</b> at the end of FM IDOC_STATUS_WRITE_TO_DATABASE. This will prevent overflow of the lock table for large number of IDOCs prior to call program RBDAPP01.
If you run manually via SE37, please ensure you are completely out from FM IDOC_STATUS_WRITE_TO_DATABASE. Then you can run program RBDAPP01. Please use program RC1_IDOC_SET_STATUS to convert IDoc status.
Hope this will help.
Regards,
Ferry Lianto
Please reward point if helpful

Sequential processing of inbound idoc

Hi experts
Does anyone know whether the inbound idoc processing is sequential (one by one) if the partner profile is maintained to be triggered immediately? Can this be done instead of using an external program for processing?
thanks in advance!

By sequential do you mean in the order that were received for a particular message type? If this is the type, you need to enable qRFC processing in WE20.

Error while processing INVOIC01 inbound idoc in R/3

Hello @ all,
in XI I'm mapping a XML-file to an INVOIC01 idoc and then sending it to an R/3.
While processing the idoc in the R/3 it is passed to the application and brings the following error:
A company code cannot be determined for LS 0000001111
As solution the system advices to send the company in segment E1EDK14 and ORGID field and the value "011" used as the qualifier, what I allmost did.
And btw. in my case 1111 is not LS but LF.
So has anyone an idea what the problem could be, or how to solve it?
P.S.: To determine the company code for LS 0000001111 in Financial Accounting customizing is not possible, because it is a training system without admin rights I'm working with.
Thankx.

Hi Krishna,
The middleware user is locking the order so the document has not distributed through the system properly.
Try looking at the inbound queue (transaction SMQ2) and outbound queue (SMQ1) for errors. Also look at the BDocs in error (SMW01).
When CRM sends an order to R/3 it waits for a confirmation to be returned, looks like the problem is here, maybe in your delta downloads not being set correctly.
Cheers
Andrew

Validations and sutitutions while processing an inbound IDoc message

Hi all.
I have got the next question for gurus:
FI sustitutions and validations are processed while creating a new FI documento via IDoc? I'm using the message type FIDCC2 I can't sustitute any field.
Could you help me, please?
Thank you in advance.

Thank you for your answer, but we need to use the FI validations and substitutions because we want to perform the same checks and substitutions done while a FI document is created via FB01.
Do you have any other idea?
Regards.
Edited by: Arévalo David on Feb 2, 2009 8:18 AM

Inbound Idocs: Queue Processing (non-stop queue?)

Hi everyone!
I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
I'm using PI 7.0 SP30.
Thank you in advance!

First, this is not serialization, it's the queuing design EOIO... they are not the same.
So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
Basically the serialization is not a good fit for these requirements.
Here is one solution:
1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
4- There is standard report that you have to schedule and restart the queues
5- Reprocess the IDOCs from steps 2
The enemy of EOIO design is the user locks in the target system...
Cheers,
Fouad

Process Inbound IDoc WPUWBW

Hi experts,
I am quite new in SAP, and I am finding a lot of problems trying to make probably the easiest things.
My problem is this:
I am trying to process an inbound IDoc type WPUWBW, and it has status 53, but when I try to view it in the workbench, the system does not recognize the IDoc as good movement type and I can not find the way to insert in one field of the IDoc via we19 transaction the transaction type.How can I make it?And in which field can I insert the transaction type??
Thank you very much in advance!
Best regards,
Ander

Hi Praveen,
First of all thank you very much for your help.
My problem continues, because I am not able to find the field inside the WPUWBW IDoc to insert the transaction type, in my case 1502. But I can find the field to introduce the goods movements type, in my case 7004 in E1WPG02 segment, movement type line.
Thank you very much.
I wait your reply.
Best regards,
Ander

Inbound IDOCs - Process

Thru our Middleware we are going to receive IDOCs (Invoices, ASN etc) from our Suppliers.
We have to develop the programs, workflow and other objects on the R/3 side to receive this IDOCS and then to poste them into the appropriate tables.
What are all the steps that I need to follow to process the Inbound IDOCS. If there is any step by step guide available? Please help me.
Thank you.

Hi Mohan,
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
For example, consider the FM "IDOC_INPUT_MATERIAL" . the only thing you are concerned most is, importing input method,mass processing , exporting work flow result and tables idoc_control, idoc_data and idoc_status. Rest you can leave (for basic processing and posting ).
In the FM,
1) write a subroutine to initialize organizational data.
2) Interpret idoc.
3) check for idoc segments and raise exception if any error occurs, otherwise post the data using the BDC or BAPI.
4) Read the status message and change the idoc_status according to the status message.
Hope this will be helpful for you.
Regards,
Vicky
PS: AWard points if helpful

How to create the INBOUND Function Module for INBOUND IDOCs

Hi Friends,
Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
which are recieved from XI Server ?
I am working in SAP-ISU
Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
We have a Standard INBOUND FUNCTION MODULE
IDOC_INPUT_ISU_MR_UPLOAD
which Uploads the Meter Reading Results.
I copied the Same function Module into ZIDOC_INPUT_
and working on it.
Can any one suggest me, whether i am going in correct way or not.
In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
Can I Use the Same BAPI
BAPI_MTRREADDOC_UPLOAD
to Update the below fields,
EABL-SERNR
EABL-ZWNUMMER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS
EABL-ADATTATS
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Kindly Suggest me,
Thanks in Advance,
Ganesh

Hello Ganesh
I think you are going completely astray with you z-function module for IDoc processing.
If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
EABL-SERNR => BAPIEABLU-SERIALNO
EABL-ZWNUMMER =>REGISTER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS => ACTUALMRTIME
EABL-ADATTATS => ACTUALMRDATE
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
- BAPI_TE_EABL
- BAPI_TE_EOSB
Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
Regards
Uwe

Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L

Hello all,
I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc.
So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
During the development and testing phase in the Sandbox system this works.
However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
I was wondering if there are any ideas why this could have happened?
Oh ... I also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
Well I hope to hear from you.
Regards
Edited by: Rob Burbank on Dec 6, 2011 1:03 PM

Hi,
Check in t.code CMOD whether project is active or not (Activate the Project)
BR,
Vijay

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Help required in posting inbound idocs

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

How to get the inbound idoc for the newly created inbound Idoc FM

Hi,
I have created a new function module to process the Inbound idoc. I need to have a idoc to check my function module, whether it is working fine or not. How I can get the data. Do I need to have the idoc from the partner ? Please help me ASAP.
Thanks,
sreenivas.

Hi Sreenivas,
Go to WE19 and get any of the your present idoc with the idoc type
then go to BD20...execute the same idoc...and there you can create the IDoc, and process the same with the Inbound function module tab..( give the FM you are using as the process code.)
from there you can do the debugging aswell of that FM
Thanks

Message variant is missing in INBOUND IDOC.

hi,
Any one can help on this issue?
The sender has confirmed that message variant was filled in outgoing file.
However, When we received this Inbound IDOC, the message variant is blank.
I still am confused by two questions:
1. The function module which insert record into table EDIDC and EDIDD, is same as the function module which post this IDOC to sap module(normally we maintained it in WE57)
2. We normally need to maintained in WE57, but also need create one processing code, what is relationship between WE57 and processing code(WE42)

Hi,
Message Type/Message Variant needs to be maintained in WE20 ( Partner Profiles). In case of inbound IDOC ( receiving the data other systems) Data processing/posting will happens via function module. the function module will attach to the process code.
Process Code : The IDoc interface uses the process code to find the business process which controls the conversion of the IDoc into the SAP document.
The Process code will assign to the function module in WE42, the same function module will assign to the Message type and Idoc type in WE57
In a short summary, The Function module required to post the Idoc/update the data in SAP. However the Function module should process specific to the Message type and Idoc type only. It means the settings is required to identrify the correct function module to process the Inbound Idocs.
Whenever there is a problem with ALE setting the message 64 will trigger, it means the IDOC is ready to transfer to the application ( process through FM ).
Thanks,
Kiran.

Process of inbound idoc

Similar Messages

Maybe you are looking for