How to process inbound failed IDOCS

Hi Guys,
Actually in outbound idocs are created with one comapny code, but in inbound idocs are failed with company code is not availabe i.e, menas outbound company code is not availabe in inbound side.
inbound is production system not allowing our new company code
Is there any technique to post the failed idocs due to company code in inbound side

outbound is production system, idocs created in outbound and transfered to inbound , but the problem is after idocs are came to inbound we will try to post with <b>another company code</b> not with existed company code in IDOC

Similar Messages

How To Process Inbound Shipment IDOC of IS-OIL ?

Hi Expert,
We are on 4.7E IS-OIL. We have one requirement thru which we are getting the Shipment IDOC from SCM system which is coming to R/3. The IDOC Message Type Which is Flowing From SCM To R/3 is OILSH1 & Basic Type is OILSHI01.
I want to Know how to Process this IDOC as InBound IDOC in R/3 & create the Shipment Doucment from it in R/3.
What is the Process Code & Function Module I should use.
Kindly give me the Step By Step Settings if Possible. like Partner Profile etc.
Regards,
Umesh

Hi,
Idocs Works on tRFC Queues.
Check this Report to Process Inbound Idocs with Specified Status.
RBDAPP01
Regards
Seshagiri

How to process the Received Idoc in SAP R/3 ? What to be done ?

Hi All
I am working for file to Idoc scenario.....
Idoc received into SAP R/3 but how to process the Idoc data ?
Such it will store in SAP R/3 DB.....
Clearly
How to Process the received idoc data into SAP R/3 ? (this is for inbound idoc)
I hope any one can help me on the processing steps ?
Waiting for valuable inputs form experts
Regards
Rakesh

rakesh
chec <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc</a>
normally, based on the idoc types it will get processed. if it is an idoc with master record it will create appropriate master records or if it based for a transaction it will create one.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098</a>

How to process inbound idoc in R/3 with status 75 - idoc received via qRFC?

Hi gurus,
we are using EOIO for source to R/3, and all the idocs a received in r/3 with this status. But they can't be processed from BD87. How to process these?
Thanks,
Olian
Edited by: Olian Saludew on Sep 11, 2008 11:44 AM

Hi,
Idocs Works on tRFC Queues.
Check this Report to Process Inbound Idocs with Specified Status.
RBDAPP01
Regards
Seshagiri

How to process inbound process code by populating its value

hi friends,
we have created a inbound process code for ticket creation and actualisation, for process an inbound idoc and we need to test by populating values to it
As i am a newbie to IDOC processing please help me in this regards by giving step by step
thanks in advance
S.Janagar

answered

Steps in Inbound Processing in ALE IDOC

Hi all,
Could anyone explain the steps to be followed in inbound processing in ALE Idoc.
I know we have to create a FM n then call that in a program. But still the detail steps are not clear.
An example will be really helpful.
Thanx

Hi
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Anji

How to track the Inbound child IDOcs in PI 7.4 Single stack

Hi Friends,
I would like to know the procedure of tracking the Inbound child IDocs in PI 7.4 Single stack.
Here is the detailed description.
Say we are getting the data from third party system and the message may have multiple IDOcs in it. The message has processed successfully from PI and reached to the target system(ERP). So, now my question is how to track the IDOc count with in that message.
Please suggest on the same.
Thanks in Advance,
Venkateswarlu.

Hi Hareesh,
Thanks for your inputs. According to the link IDOC Status, Tracking in SAP PI/PO Single Stack I am thinking the required funcionality is not there in PO 7.4, but still i would like to have little more clarity before moving further.
I will explain what what was happening in PI 7.11 so that you can understand what i am looking for in PO 7.4.
We will get the data from third party system in xml format, we had to search for the messages based on interface name and time range within SXMB_MONI. After getting the result(say the output is 100 messages), we will download the values of "Outbound Reference" field(which is a key to find the child messages for messages resulting in an Interface Collection). Below is the snap of Outbound Reference field for your reference.
Now we will go to the table IDXRCVPOR in SE16(within PI) and put the values of Outbound Reference field in Text 24 and execute. Here we will get all the child messages.
Now please let me know if this kind of scenario is possible in PO 7.4.
Thanks,
Venkat.

How to create Inbound Idoc from XML file-Need help urgently

Hi,
can any one tell how to create inbound Idoc from XML file.
we have xml file in application server Ex. /usr/INT/SMS/PAYTEXT.xml' we want to generate inbound idoc from this file.we are successfully able to generate outbound XML file from outbound Idoc by using the XML port. But not able to generate idoc from XML file by using we19 or we16.
Please let me know the process to trigger inbound Idoc with out using XI and any other components.
Thanks in advance
Dora Reddy

Hi .. Did either of you get a result on this?
My question is the same really .. I am testing with WE19 and it seems SAP cannot accept an XML inbound file as standard.
I see lots of mention of using a Function Module.
Am I correct in saying therefore that ABAP development is required to create a program to run the FM and process the idoc?
Or is there something tht can be done with Standard SAP?
Thanks
Lee

How to post Freight Charge in INbound INVOIC Idoc? (MM Invoice Verif)

Hi Folks,
Would like to post an inbound invoice(810) IDoc that has multiple line items that may or may not have variances(quantity, price, etc.). MM Logistics Invoice verification is the process used for posting our invoices for raw materials. We would like for the line item variances to continue to post to the PPV account. Our problem is freight. Freight in this instance is in the header of the IDOC(segment E1EDK05). For example, we create a purchase order with 3 line items for $100.00 each totaling $300.00 for the purchase order. We receive an EDI Invoice for $345.00 which contains a $45.00 charge in the header for freight. We would like for the freight to be posted to the appropriate account. Currently the $45.00 difference in P/O total and Invoice total is being posted to the PPV account. Your helpis appreciated!
What if Freight charge is populated as Line item in the inbound invoic idoc. Will the inbound program allow this kind of posting??
Throw some light experts.
Thanks,
Matt
Edited by: Creasy Matthew on Aug 16, 2009 6:25 PM
Edited by: Creasy Matthew on Aug 16, 2009 6:25 PM

Yes, you can include the freight cost in line item as well but that would not be advisable. Why don't you include Fright Cost in your pricing procedure ??? Do check the following link
How to account freight in purchase order

EDI-How does the Inbound File process work?

Hi
How does the Inbound process work in EDI
When a file is put in the Inbound EDI directory of the App server how does the system start the process?
Which programs are called/triggered?
How does the Inbound process work?
Please be brief and precise.

Hi
Check the links
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points if useful
Regards
Anji

Can anyone pls tell how to process idoc manually ??

hi experts ,
my process chain got failed at INFOPACKAGE STEP ITSELF which updating data from r/3 to cube via dso ... and in IP monitor screen it is showing that "SOME IDOC PROBLEM "
i went to to BD87 and checked for idocs status ..my outbound idoc has problem .... its saying that "error passing data to port "
and on drilling down, it is showing error msg like """code page couldn't find page for receiving system """"".. (with red status )
,if i process these idocs manually ,will it resolve the issue ?? can any one pls tell me how does this error looks like ???
and can you please tell me how to process IDOC MANUALLY ??
IS IT LIKE "SELECTING IDOC --> RIGHT CLIK --> PROCESS" ??????
please help with your suggestions
HELP FULL ANSWERS WILL BE REWARDED WITH POINTS ..
Thanks in advance ....
Harry

1. Status 02 to 03 : RBDAGAIN / Tcode BD83 > Calls IDOC_PROCESS_ERROR function module.
2. Status 30 to 03 : RSEOUT00
3. Status 29 : Problem in ALE settings
You can refer this link for more details : http://goo.gl/p5XPl
See status of record and process below programs using submit report by passing Idoc number
Program RBDMANI2 for status 51 & 52
Program RBDAPP01 for status 64 ,66
Program RBDAGAIE for status 32 and 69 (Edited IDocs)
Program RBDSYNER for status 26
Program RSEOUT00 for status 30
Re-process IDocs failing in 29 status, use program RBDAGAIN.
+ Attention : Use these tcodes with extreme caution+

Inbound Custom IDoc Processing

Hi,
I've created an Inbound Custom IDoc, Created the ABAP function module to post it to the application, configured workflow and IDoc processing. All my setup appears fine as I can create IDocs from our AS400 subsystem and trigger a successful posting via the IDoc test tool.
Having got this working I now want to automate the posting.
At present I create the IDoc's on our Legacy AS400 System and FTP them onto the SAP Application Server which runs on a Windows 2003 platform.
How do I get SAP to process each of my waiting Idoc's?
Any examples appreciated....

Hi
For CUSTOM IDOC inbound processing
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Check out this sample Function Module on the inbound system
FUNCTION Z_IDOC_INPUT_EMPREP.
""Local interface:
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Database Tables
TABLES: ZAK_EMPLIST.
Include programs
INCLUDE MBDCONWF.
Data Declarations
*--- Employee Header -IDOC
DATA: FS_EMPHDR_DATA LIKE Z1R_SEG1.
*--- Employee Details -IDOC
DATA: FS_EMPDET_DATA LIKE Z1R_SEG2.
*--- Employee Header - application data
DATA: FS_APP_EMPHDR LIKE ZAK_EMPLIST.
*--- Employee Details - application data
DATA: FS_APP_EMPDET LIKE ZAK_EMPLIST.
Program Logic
*---Initialize Work Flow Result
WORKFLOW_RESULT = C_WF_RESULT_OK.
LOOP AT IDOC_CONTRL.
*--- Check whether the correct message was passed to us
IF IDOC_CONTRL-MESTYP NE 'ZR_MSG'.
      RAISE WRONG_FUNCTION_CALLED.
ENDIF.
*--- Clear application buffers before reading a new record
CLEAR   FS_APP_EMPDET.
CLEAR   FS_APP_EMPHDR.
REFRESH FS_APP_EMPDET.
REFRESH FS_APP_EMPDET.
*--- Process all records and pass them on to application buffers
    LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_CONTRL-DOCNUM.
      CASE IDOC_DATA-SEGNAM.
        WHEN 'Z1R_SEG1'.            " Employee Header
          FS_EMPHDR_DATA = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING FS_EMPHDR_DATA TO FS_APP_EMPHDR.
        WHEN 'Z1R_SEG2'.            " Employee Details
          FS_EMPDET_DATA = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING FS_EMPDET_DATA TO FS_APP_EMPDET.
      ENDCASE.
    ENDLOOP.
*--- If data is ok
SELECT * FROM ZAK_EMPLIST WHERE ENUMBER = FS_APP_EMPHDR.
    IF SY-SUBRC NE 0.
      INSERT INTO ZAK_EMPLIST VALUES FS_APP_EMPHDR.
      INSERT INTO ZAK_EMPLIST VALUES FS_APP_EMPDET.
    ELSE.
      UPDATE ZAK_EMPLIST FROM FS_APP_EMPHDR.
      UPDATE ZAK_EMPLIST FROM FS_APP_EMPDET.
    ENDIF.
ENDSELECT.
IF SY-SUBRC EQ 0.
*--- Populate Return variables for success
      RETURN_VARIABLES-WF_PARAM    = 'Processed_IDOCs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      RETURN_VARIABLES-WF_PARAM    = 'Appl_Objects'.
      RETURN_VARIABLES-DOC_NUMBER = FS_APP_EMPHDR-ENUMBER.
      APPEND RETURN_VARIABLES.
*--- Add Status Reocrds indicating success
      IDOC_STATUS-DOCNUM           = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS           = '53'.
      IDOC_STATUS-MSGTY            = 'I'.
      IDOC_STATUS-MSGID            = 'ZE'.
      IDOC_STATUS-MSGNO            = '006'.
      IDOC_STATUS-MSGV1            = FS_APP_EMPHDR-ENUMBER.
      APPEND IDOC_STATUS.
ELSE.
      WORKFLOW_RESULT              = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM    = 'Error IDOCs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
*--- Add status record indicating failure in updating
      IDOC_STATUS-DOCNUM           = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS           = '51'.
      IDOC_STATUS-MSGTY            = 'E'.
      IDOC_STATUS-MSGID            = 'ZE'.
      IDOC_STATUS-MSGNO            = '007'.
      IDOC_STATUS-MSGV1            = FS_APP_EMPHDR-ENUMBER.
      APPEND IDOC_STATUS.
    ENDIF.
ENDLOOP.
ENDFUNCTION.
Good Luck and reward me for the same
Thanks
Ashok

Inbound processing of INVOIC IDOC without PO number and item check

Hi All,
I'm processing an Inbound INVOIC IDOC to create an Intercompany Vendor Invoice against a Purchase order but wish to do process this based on the delivery note number rather than the PO number. The INVOIC IDOC will not contain a reference to the Purchase order and thus the need to process it based on the delivery note number which will be referenced in the Purchase order Goods receipt.
However, when processing the Inbound INVOIC IDOC it is validating that the number in IDOC segment E1EDP02 with QUALF 001 is the purchase order number. In this scenario it won't be and therefore it errors. The delivery note number is in IDOC segment E1EDP02 with QUALF 016.
Could someone please tell me if there is a standard way that we can have this Inbound INVOIC IDOC processing using only the delivery note?. If I manual process in the MIRO transaction I can process an Invoice based on the dleivery note in the Goods receipt so would expect I should be able to do so also with the IDOC processing.
I have noticed that IDOC segment E1EDP19 with QUALF 003 is not being populated and therefore according to the SAP help the IDOC segment E1EDP19 with QUALF 002 holding the Vendor material number is checked. Could this have something to do with it not being able to process the Invoice using only the delivery note number reference?.
Thanks in advance,
Michael

Hi Karen,
According to Note 103051 - EDI: Multiple reference to same purchase order item.
Module IDOC_INPUT_INVOIC_MRM (only as of Release 4.0) for the logistics invoice verification can distinguish different goods receipts by means of the delivery note number. For this purpose, GR-related invoice verification must be active. Please check the note.
Thank you,
Shyam

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

How to assign function module with process code in IDOC ?

how to assign function module with process code in IDOC ? and what code i have to write in that function module for custom IDOC ?
helpful answer will be rewarded?

Hi,
First goto transaction we42 -->editing mode --> new entries -->give name of your process code and description --> processing with alv service and function module -->then press enter -->after that enter the name of the function module you want to associate from the drop down and save it.
Thats the way to assign function module with process code.
In that process code we will have the Function modules and Bapi's which will take the data which we are sending through IDOC and then process it.
for example: i am triggering the IDOC for every purchase order created then this process code in the receiver system will take the data which i have enetered in the sender system to create the purchase order and process it and creates the same purchase order in the receiver's system.
Reward if helpful.
with regards,
Syed

How to process inbound failed IDOCS

Similar Messages

Maybe you are looking for