IDOC failure in R/3 Inbound processing

Hi
I was able to successfully generate XML files from Syndicator, but when it comes for processing in R/3 side it get fails all the time with the IDOC err msg : "IDoc included in IDoc packet containing an error: transfer it separate ".
Kindly adivce how to solve the same.
thanks in adv
Alexander

Hi Ravi
Let me explain in detail.
From R/3 to MDM --> All materials in one XML file.
while from MDM to R/3 --> 3 diiferent IDOC am able to
see, one for each material in Inbound Processing.
kindly advice me how to fix the same.
thanks
Alexander

Similar Messages

How many types of inbound process r there

how many types of inbound process r there for a inbound idoc?

Hi,
Creating an Inbound Process Code
The inbound process code, that is, its attributes, indicates how an inbound IDoc is processed. A process code has the following attributes:
·        Processing type (for example, should the inbound function module be called immediately, or should a workflow or work item be started?);
Standard: "ALE, function module called directly"
·        Name of inbound function module;
·        Error processing attributes (objects and events; see the section on objects, and so on, for error handling);
·        Application object type used for ALE links;
¡        the object type created or changed by the inbound function module. Example: An inbound ORDERS IDoc, containing a customeru2019s purchase order, creates a customer order in the receiving SAP System. Here the application object type is BUS2032, the object type for customer orders in the BOR (Business Object Repository).
·        The application event to be triggered (dealt with in the section on advanced techniques) is not generally used.
For an example, have a look at the process code MATM used for material master data.
Reward If Helpfull,
Naresh

Park inbound EDI Invoices on iDoc failure from a workflow?

Hello all,
We have seen note 501524 that talks about parking inbound invoices by default.
Our situation is this. We are expanding our use of EDI for inbound invoices. As such we would like to automate the validations steps as much as possible. To date with our limited use we have set up a workflow to notify on idoc failures and then a few agents have access to BD87 to make the idoc right and reprocess. We don't want to continue this process.
Our preference would be to continue to allow the iDoc to fail, the workflow fires but at this point we communicate the failure to the appropriate person and park the invoice.
Does this sound like a reasonable approach?
Can we even park a red lighted iDoc?
Once parked can the invoice be dealt with without using BD87?
Has anyone ever tried this?
Thanks,
Doug

Hi Ralph,
In my opinion, you must have a PO Number for Invoice if you want to use standard functionality. You will probably need to create IDOC using an ABAP program which reads this file and search for PO based on the information available to you. I also notice that you are missing material number as well, how do you match the item number in the PO ?
I don't see a way aroung without writing an ABAP program to handle this logic, but you can still use IDOC ( which comes with the standard processing logic and that is a big advantage ) so that you need to write only the PO matching logic.
or if you are not inclined to write a separate program for uploading file into SAP and formatting IDOC, you can write your own process code (FM)for INVOICE01. Inside this process code (FM), you can put your PO matching logic and then call standard FM (process code). This is what I usually do.
Cheers,
Sanjeev
Cheers,
Sanjeev

IDoc Inbound Processing for CREMDM & DEBMDM

Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.

Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh

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

File to idocs - sequence of inbound processing

Hi everybody,
we have a file to (2) idocs scenario. In XI we map the received data of vendors into two idocs (adrmas and cremas). After building the idocs we send them in that sequence to the reveiver systems (recommended). The problem is that in the receiver system very often the idoc cremas wants to be processed before adrmas is ready. This leads to the error "vendor xy is blocked by user sapale". Especially for massprocessing I get a lot of these error-messages in bd87. As workaround I processed all the error-idocs by the report rbdmani2. (First step adrmas - second step cremas) But then I face missing data in some cases in table lfa1 - which seems to me that the sequence of 1. adrmas and 2. cremas was not correct processed.
Is there a possibility for inbound processing with the rule process adrmas - wait until ready - process the associated cremas and so on?
I checked the sap-help article for seralisation - but we could not achieve a better result by queing the outgoing messages in the xi.
Thanks very much.
With kind regards
Jörg

You have to get a solution based on the following concepts
1. Do not use BPM it is not efficient
2. Understand what is the difference between an IDOC in received state and processed state. Received state mean IDOC is saved into IDOC table. Processed state mean IDOC processed into the business system.
3. You can ASK BASIS guy to turn on the immediate IDOC processing option in SAP system,so that SAP process the IDOC as soon as it arrive in IDOC table. This is not efficient, in case if your SAP system has to process SAP online client request and SAP document (inbound and outbound) same time.
4. Understand the concept of standard based integration, mean integration system provide the option to business parties to provide the successfull message transfer.
Based on all these points I recomend you to follow the steps below.
1. Extract each record from the input files into two idocs.
2. Send the first IDOC to the receiving system
3. Send the second IDOC to a ESB storage such as DATABASE, JMS Queue, MQ Series Q (if you have available) or even to another File.
4. Develop an RFC module to check the status of the IDOC being send to the receiving system. Status here mean whether the IDOC data processed into the business system. You can do this lookup using a custom RFC lookup using the attribute connecting the first IDOC record with second IDOC.
5. Process the records (second IDOC) from the intermediate storage using the RFC lookup into the business system updates its status as ready to deliver.
6. Using another process such as FILE to IDOC or JMS to IDOC or JDBC to IDOC send each record which are ready to process from intermediate storage to the receiving system.
7. Create a report using FILE or JMS, JDBC adaptor module to keep track of these three stage processing, so that in case an inconsistency happed you will have an auditing trace available.
This is the standard based integration approach.
ABAP guys, BASIS guys they may not get it when then repair a BMW in local auto workshop, cuz I had to fight with them 4 years ago to make it happen in Verizon supply chain project where I had to accomplish the same concept in SAME IDOCS you mentioned here.
BPM, turning on immediate processing of IDOCS etc will end up in buying another 16 CPU hardware and BASIS guys or ABAP guys running BAD record IDOC processing report for 350.00 hr consulting FEES.
SAP is a good company and XI is a good product, as long as it is being used as per right usage.

Error In inbound Processing IDoc

Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
Thanks

Hi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN     005
SPRAS     E
MAKTX     MANATA2000 TEST ALE
SPRAS_ISO     EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

User Exit for Inbound Process - Changing IDOC control record

Hi,
I want to utilize the identification field (under details tab) of the IDOC Control Record. What is the suitable user exit for inbound process that i can use to change the IDOC control record?

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

Idoc inbound processing? from non-sap system?

Hi experts,
I'm confused with some functions below:
IDOC_INBOUND_SYNCHRONOUS
INBOUND_IDOC_PROCESS
IDOC_INBOUND_SINGLE
IDOC_INBOUND_ASYNCHRONOUS
can you tell me what are the differences? when to use them?
for sap outbound processing, we can only call function master_idoc_distribute to generate idoc or use message control to trigger outbound idoc. no other options, correct?
for sap inbound processing, if we use message control for automatical posting, we have process code which read the inbound idoc file and do the sap posting. when to use those functions above?
does the middlewares like seeburger, GIS call those functions to generate idocs at SAP side?
in what scenarios can we use those functions? read directly non-sap file into sap internal table then call the functions to create inbound idoc? how about the posting? call inbound processe code function after the functions above?
in case the interface between sap and legacy system is using above functions to build inbound idoc in sap and sap use process code for inbound posing, sap can monitor all inbound process using idoc, but how can the legacy system mornitor the interface?
Thanks.
Legend.
Edited by: legend li on Dec 21, 2010 4:58 PM
Edited by: legend li on Dec 21, 2010 5:40 PM

Hi Christophe,
Awesome!!!!!! it worked, You are the best.
I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
Can you kindly share the IDoc data to be passed in...along with respective segments and fields:
Segment                                                 Field
E101CRMXIF_BUSTRANS     OBJECT_TASK
E101CRMXIF_BUSTRANS     PROCESS_TYPE
E101CRMXIF_BUSTRANS     POSTING_DATE
E101CRMXIF_PARTNER                          PARTNER_NO
E101CRMXIF_PARTNER                RELATION_PARTNER_NO
E101CRMXIF_ORGMAN         SALES_ORG
E101CRMXIF_ORGMAN          DIS_CHANNEL
E101CRMXIF_ORGMAN         DIVISION
E101CRMXIF_SALES             PO_NUMBER_SOLD
E101CRMXIF_SALES            YOUR_REF_SOLD
E101CRMXIF_SALES            PO_NUMBER_SHIP
E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
E101CRMXIF_SCHEDLIN_I     ORDER_QTY
Thanks a ton in advance .
Vijay

IDOC DEBMDM and inbound process code

Hi ya.
Do you know if there is a standard inbound process code for IDOC DEBMDM in R3?
Regards
Agnieszka

I can not make it working at the moment. I am getting message: IDOC_INPUT_DEBITOR_MDM called up.
I can not find an error in my config at the moment.
Function module IDOC_INPUT_DEBITOR_MDM is assigned to message type DEBMDM and IDOC DEBMDM06.
Any clues ?

LSMW idoc Inbound Processing settings

Hi,
We have done LSMW with BAPI method to create Bank master.
In Idoc Inbound Processing settings -
We created partner type as 'B' i.e, for BANK
While creating Partner Number it is not allowing to create Partner Number. The error is "Enter a permissible partner number"
Please let me know what would be the problem.
Regards,
Hari
Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AM

Hi,
Use patner type as US only and LSMW as Patner number.
this will surely solve your problem .
plz do this way :
The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
Port: LSMW
Name: Legacy System Migration Workbench
Version: 3 (IDoc record types SAP Release 4.x)
Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
SAP recommends:
Port: assigned by the system
Version: 3 (IDoc record types SAP Release 4.x)
RFC destination: Name of R/3 System
Name of port: Legacy System Migration Workbench.
Then the partner type should be defined or selected. SAP recommends:
Partner type: "US" (User)
As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
Partner type: Create US
Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine: READ_USER
Short description: any.
Finally a partner number should be defined or selected. SAP recommends:
Partner number: LSMW
Partner type: US
Partner status: A (active)
Type: US
Language: DE or EN
Person in charge: Your user ID.
Activate IDoc inbound processing
reference : help.sap
thanx.
Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM

Plant missing in the inbound processing of IDOC ORDERS?

Hi gurus,
We are using IDOC ORDERS to create sales order in the inbound processing of R3 4.7 system, finally we found the sales order was created succesfully in VA03, but the plant(WERKS) and storage location(LGORT) couldn't be seen even the idoc has relevant value.
Have you met this case? Any help will be appreciated. Thanks.

Hi Himanshu,
Thans for your reply. I gave the field E1EDP01-WERKS the relevant value, but in VA03 we couldn't see the plant value when the idoc status was 53. When we debug it in WE19, we found the plant value probably wasn't assigned.
Any ideas?

Idoc verification in inbound process

Hi,
in outbound process.. the idoc posting is fine..
mean.. the message : the data passed to port ok .
it is sd to mm realated..(functional side)..
question is .. how to see idoc status in the inbound process ??
regards,

Hi,
You can check the Idoc status using the transactions WE02 OR WE05.
When the Inbound Idoc is created then the status will be 64(IDoc ready to be transferred to application) then after you process the Idoc then the status will change to 53(Application document posted).
Thanks,
Srinivas

IDOC failure in R/3 Inbound processing

Similar Messages

Maybe you are looking for