Creating an Inbound IDoc PORDCR

Hi Gurus,
I am working on generating an inbound idoc for creating purchase order using Message type PORDCR03, which I successfully did create. But my requirement is that I have to populate REF_1 (your reference) field in E1BPEKKOA segment.
I tried giving a reference PO number in that field using we19 and created PO with an IDoc. But the field is still not populating.
Please advice on how to get this field with values.
Thanks,
Shreya

Hi Shreya,
At the time of doing the inbound processing, do it in bebug mode, put a breakpoint on FM BAPI_PO_CREATE. This fm will be called internally for creating the PO. Then you can easily understand what is happening.
Again you are using right field but don't know what is happening.
Regards,
Amitava

Similar Messages

How to create a inbound IDOC from flat file in Application server

HI All
Our requirement is to create the Inbound idocs from a flat file from application server with in R/3
Could any body please let me know the steps required for this.
Thanks
Malli

1. Read the file using OPEN DATASET and read and fill up the segment info and fill the EDIDC header data
and then call function
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
    TABLES
      IDOC_CONTROL       = i_edidc
      IDOC_DATA          = i_edid4.
a®

How to create an inbound Idoc from an inbound IDoc in same client

How to create an inbound Idoc from an inbound IDoc in same client
Idoc will come from XI as an inbound idoc to SAP, now I have to read this inbound Idoc and split it into Several Inbound Idocs and now needs to be posted in the same client.
please let me know the procedure..
Thanks in advance,
Sagar

Hi Sagar,
Develop a cusom Z-Inbound function module, configure the Z-FM to trigger when idoc is recieved from XI. In your Z-Inbound function module split the idoc (Recieved from XI) into respective Idocs and Using MASTER_IDOC_DISTRIBUTE post the IDOCs into the same system.
Thanks & Regards

NO MATERIALs in the Sales order created through inbound idoc file

hi,
i have maintained the customer material number as well the SAP Material number in the tcode VD51,but still the inbound
idoc type ORDERS03 is posting the application document(Sales order) without the materials.
for instance,
I have cust.material as CUSTMAT1 in the idoc file.
I have maintained the CUSTMAT1 as cust material and 1001 as material no in VD51.
After posting the inbound idoc file using RSEINB00 prg,the idoc is created and i can see the CUSTMAT1 in the material segment field
The Sales order is created successfully ,but without the materials.
i need the application document has to be posted with materialsm,can any one help me to solve this issue.?
Thanks

Hi ganesh ram
In order to determine the Material Number with you custom material then you needs to have some configurations.
Check with your Functional consultant to add the Access sequence for determining the Material Number with you custom material
In Sale order processes...
Thanks
Ramesh

Create an INBOUND IDOC

Hi guys,
I need to create an idoc on the system.data is coming from the thrid pary as ascii format and kept on the application layer.i can pick up the data on the application layer`, and use the FM, IDOC_INBOUND_SINGLE to create an idoc. i have even created segments and new idoc type.
my question is how to map the data i am picking from application server, to the FM.I have idea that i should use the edidd, edidc structures for this,
but i am not able to get an idea how to code.....
pls help in this matter for which i would be greatful...

Hi,
Hi, I assume the inbound setting are alreay in place (eg:WE82, BD51, WE57,...)
Here is the sample code to assign idoc data into your internal table:-
DATA: fs_emhdr LIKE Z1EMHDR,
i_emhdr like Z1EMHDR occurs 0 with header line.
LOOP AT IDOC_CONTRL. " data from EDIDC
LOOP AT IDOC_DATA WHERE " data from EDIDC
DOCNUM EQ IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN 'Z1EMHDR' " idoc segment
fs_emhdr = IDOC_DATA-SDATA.
MOVE-CORRESPONDING fs_emhdr
TO i_emhdr.
append i_emhdr.
WHEN ....... " for others segment
ENDCASE.
ENDLOOP.
ENDLOOP.
Reward points if found helpful....
Cheers,
Venkoji Babu.

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.

Creating Delivery based on the Inbound IDOC received.

Hi all,
I have a requirement where in, Outbound Delivery for Sales order is to be created based on the inbound IDOC received from a third party. The standard idoc type DELIVERY03, requires the Delivery Number for updating the order but it cannot create a delivery number.
Can any one suggest which IDOC type can be used for this or if there is any alternative solution?

Hi,
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.
Check the following link:
http://www.sapbrain.com/TUTORIALS/TECHNICAL/IDOC_tutorial.html
<b>Reward points</b>
Regards

INBOUND IDOC not updating the basic data field which is created newly

Hi,
i am creating an inbound IDOC for material master creation in that in basic data1 i have created 2 custom field in general data 1 is updating and another is not updating with the value in iDOC.
User exits codes are fine. but data is not updating.
can some one help hw to resolve this..
regards,
thanigai

Hi,
Are you Debug the function module in Process code of IDOC and use COMMIT WORK in that Function module.

Creating inbound idocs in the same system

Hi
Could you please let me know the Steps i should follow to get the following req done?
Iam creating INBOUND IDOCS from flat file ...so my sending and recieving systems are same...
In WE20 i have setup the logical system and assigned inbound parameters with message type and proces code.
Iam using IDOC_INBOUND_ASYNCHRONOUS to create the inbound IDOCS but iam getting the error
EDI: Partner profile inbound not available
It looks like iam missing some settings here..
Please let me know what checks i need to make sure to get rid of this error and post the idoc.
Thanks
Govi

Hi,
You need to create the partner profile in WE21 - Type Port.
You need to give the directory name and the inbound file name. Just do the access test available to check if the file is accessible.
Also create the process code in WE42 and maintain the processing FM.
Hope this helps you
Regards
Shiva

Creating Inbound IDoc Using LSMW

How to create the inbound IDoc using LSMWu2026
For example
Input is Flat filesu2026.
I created custom IDoc with header and items
Structure looks
Header 1
Item 1
Item 2
Header 2
Item 3
Item 4
Header 3
Item 4
Item 5
u2026u2026.
u2026u2026.
u2026u2026..
Do I need to create different flat files (item level & Header level) as input while creating IDoc using LSMW ??
Can some one guide me on thisu2026with best way to create IDoc using LSMW with flat fileu2026.
Ramesh

can you please help me ... how input file to LSMS looks ..Sample file is helpful...
My Structure
E1EDK01    < Header Data
E1EDK14    < Header Data
E1EDK14    < Header Data
E1J3K03     < Header Data
E1EDK05    < Header Data
E1EDK05    < Header Data
E1EDKA1    < Header Data
E1EDKA1    < Header Data
E1J3P01      < Header Data
     E1J3AIM     < Item Data
     E1EDP20     < Item Data
E1J3P01      < Header Data
     E1J3AIM       < Item Data
     E1EDP20      < Item Data
Header had 3 segement E1EDK14   E1EDK05 & E1EDKA1 repeating twice.... i am facing prolem with this
What Structure format i used for above segement in LSMW and what file format i should use..for input to LSMW...
Edited by: Ramesh on Mar 25, 2009 1:26 AM
Edited by: Ramesh on Mar 25, 2009 1:41 AM
Edited by: Ramesh on Mar 25, 2009 1:44 AM

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

How to create inbound idoc and FM

Dear All,
How to create custom inbound idoc, the program and FM.
Can anyone send me step by step process to create it, steps in FM and Coding.
I have created for outbound and its working fine.
Plz reply ASAP.
Regards,
Arun.

Hi Arun,
1) Create segment (WE31)
2) Create IDOC Types (WE30)
3) Create message type (WE81)
4) Link message type with basic type (WE82)
5) Create FM (SE37)
here in the source code part of the function module you have to loop into the data records table of the idoc. then loop into the status recod table to update the status of the idoc(Posted/Postedwitherrors/errors).
6) Create Process Code (Inbound - WE41/ Outbound - WE42)
7) Link FM and process code (WE57)
go to WE19 to test it.
Edited by: Chinna guntur on Sep 2, 2008 9:17 AM

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Inbound IDOC using XML

Hi,
I need to create an Inbound IDOC using Function modules using an XML file as Input.
I am using mySAP ERP 2004(WAS 6.4).
IDOC type : HRMD_A05
Message Type : HRMD.
I am using the FM's in an ABAP report for testing, reading the data from the XML File using the FM GUI_UPLOAD .
I tried using the FM <b>IDOC_INBOUND_XML_VIA_HTTP</b>,with import parameters XML_STREAM, CONTENT_LENGTH, CONTENT_TYPE, REMOTE_ADDR.(ALL Type Strings)
This FM creates the IDOC successfully but i do not get the status record for the IDOC as there are no export parameters or tables where i can get the value.
I am trying using the FM <b>IDOC_INBOUND_XML_SOAP_HTTP</b>,with import Parameters as <b>XML_STREAM type XSTRING</b>,and there is the export parameter ASSIGN ,type IDOC_ASSIGN_TAB and i was wondering if this could return the status.
I used the same XML and used the FM "SCMS_STRING_TO_XSTRING", to convert the file input string into XSTRING.
On executing this i get the exception,"NO DATA RECEIVED" .
Can anybody Please Tell me
1)How to get the status of an IDOC if i use the FM IDOC_INBOUND_XML_VIA_HTTP ?
2)How to use the FM IDOC_INBOUND_XML_SOAP_HTTP ?
3)Is there any other way to create an IDOC with XML input?
Thanks,
regards,
Siddhartha Jain

HI Nagarajan,
I had checked the first link mentioned by you and activated the required service from Transacttion SICF,but still it didn't help.
The second link points to the IDOC Adaptor for XI,guess it won't help as i'm not using XI.
I want to pass XML data read from file and call a FM which creates and posts and IDOC into R/3 and returns the IDOC Number and Status.
For this i found the FM's IDOC_INBOUND_XML_SOAP_HTTP and IDOC_INBOUND_XML_VIA_HTTP.
The FM IDOC_INBOUND_XML_VIA_HTTP accepts xml as string and posts IDOC succesully,but i do not get the status and IDOC Number.
The IDOC_INBOUND_XML_SOAP_HTTP accepts xml as xstring,so i used the FM SCMS_STRING_TO_XSTRING to convert the same xml string to xstring and pass it to the FM.But it gives an error 'NO DATA RECEIVED'.
If i make few changes to the XML doc,to include SOAP envelope ,like
<?xml version="1.0" encoding="UTF-8"?><HRMD_A05>.......</HRMD_A05>
to
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><IDOC BEGIN="1">.......</IDOC></soap-env:Body></soap-env:Envelope>
I get the error,the tag <IDOC BEGIN="1"> not found ,the IDOC XML should be of format <IDOC BEGIN="1"> <IDOC>.
Can anybody please help on what to do/how to proceed.
Thanks,
Regards,
Siddhartha

Message type is not populating in the Inbound idoc control record

Hi,
I have created an Inbound Idoc function module and have done the necessary Idoc settings. But, while testing in WE19, I observed that control record is not getting populated with message type and it is dumping.
The settings which I have done in WEDI as follows:
1. Created Idoc segments with necessary fields and released
2. Created Idoc type for the segment type
3. Created message type
4. Assigned message type to basic type
5. In the inbound processing settings,
filled the ALE attributes with the Idoc function module name and input value '0'
6. Assigned FM to basic type and message type
7. Created process code and assigned the process code to message type
Please let me know, the reason for the message type not populating in the control record. Useful answers will be surely rewarded.
Best Regards,
Mallika

Hi,
Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
Thanks
Rahul

Creating an Inbound IDoc PORDCR

Similar Messages

Maybe you are looking for