URGENT : TAS Interface - BOM SO create a IDOC Automatically

Hi,
We have a situation where I am not able to configure the system to trigger an IDOC automatically.
1. Unable assign load IDs to the exploded BOM items in SO. I have added the material / sales org / plant to make it TAS relevant. Yet I am getting the message that the item is not TAS relevant. Adding to this the same configuration is working if the item is not a BOM.
2. When we create a SO in both the above cases I would like the SO to automatically have the output type and medium as ALE and the Logical system to be populated. So when the Order is saved an IDOC will be triggered to an external Logical system. Currently i have to manually enter the output type , and still even the IDOC isnot triggered. I have configured the Output type(OIOR) to the IDOC Include.
Any help to fill in any missing configuration would be helpful. Please feel free to ask questions, as this is on HIGH PRIORITY.
Thanks and Regards,
Arnab

>
Abir Banerjee wrote:
> Check this BADI. See if it helps.
> BAdI for Processing Inbound Licenses
>
> Path: SPRO->SAP GTS->General Settings->BADI For SAP GTS->BAdI for Processing Inbound Licenses
Abir,
Thanks for the response, All my license information is coming from the 3rd party, so I don't need any sort of logic or manipulation on GTS side. All i have to do is blindly create a license, so BADI doesn't help me.
All I need is a function module/ BAPI that can accept the licence information as input and create a license.
Also I'm looking to see if there is any standard Idoc to hold the licence data (Like orders04 for sales order...)
Thanks for your time
-Amit.

Similar Messages

Create inbound idocs

how to create interface programs to create inbound idocs and outbound xml file generation to the external server?
any clues pls..
Regards,
swathi.

Follow the following steps :->
1) Create a fn module to post the Idoc.
2) Define input method for inbound fn module. You have to check dialog Allowed . (t.code BD51)
3) Assign fn module to logical message (t code BD57).
4) Create Process code (t.code WE42).
( Now this process code you can use while creating partner profile t.code we20 ).
Reward Points if useful.
Regards,
Monica

How to create an IDOC ? Urgent!

Hi ...can anyone tell me the steps and process of creating an IDOC?
or can email to [email protected]
very urgent...THANKS IN ADVANCE.
Suryaa

Hi SUrya,
Go the below links:
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
Also check this links for additional information.
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
Regards
Srini

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

Urgent: Creating ALE IDOC for SALES ORDER

hi
please tell me <b>step by step procedure to create ALE IDOC for SALES ORDER?</b>
reward for sure
regards
ravish

Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards

Multiple document numbers not created while creating multiple idocs.

Hi Experts,
we have developed one the interface file to idoc, whenever invoice number change it will create a multiple idocs.
but i am facing some issue with context handling, can you suggest the suitable mapping / UDF for the below issue.
Our customized idoc structure has header and line items and both are in not same level-its parent child structure.
in our sample file there are three different invoice number and as per the requirement its creating three idocs and corresponding headers but not line item details.
all line item details creating in 1st idoc itself and 2nd and 3rd idoc has only header items no line items. but tried fix with graphical mapping context handling for this problem but not resolved. please advise.
Regards,
Krushi.

hi Hareesh,
thank you for your quick response.
after the File Adapter FCC, below is the inbound payload, first four feilds we mapped to header and rest for line items.
<SettlementDetails>
<row>
<PaymentType>CHECK</PaymentType>
<Filler></Filler>
<Currency>IN</Currency>
<Filler1></Filler1>
<Invoice>100410-133MT5-MH</Invoice>
<Filler2></Filler2>
<SettlementMethod>4</SettlementMethod>
<Filler3></Filler3>
<PreferredTradingPartnerIdentifier>MT</PreferredTradingPartnerIdentifier>
<Filler4></Filler4>
<FinalPayAmount>12.00</FinalPayAmount>
<Filler5></Filler5>
<ProductIDUnformatted>55111064001</ProductIDUnformatted>
<Filler6></Filler6>
<Filler7></Filler7>
<Filler8></Filler8>
<PaytoPreferredTradingPartnerIdentifier>MT</PaytoPreferredTradingPartnerIdentifier>
<ClaimType>ORIG</ClaimType>
<CMSRecordID>FFSU</CMSRecordID>
</row>
</SettlementDetails>
multiple settlement details will be there.
regards,
krushi.

Creating multiple idocs in ABAP mapping

Hi,
my scenario is source message (JDBC) to target message (idoc).
There can be multiple idocs (unbounded).
I am using ABAP mapping to create the Idoc XML structure. For this i use function module IDX_IDOC_TO_XML.
The idoc is getting created but the problem occurs in case of generating multiple idoc instances.
I changed the idoc occurence to unbounded & used the new idoc external definition in the interface mapping.
I also call the IDX_IDOC_TO_XML & create the output stream factory in a loop (per idoc ).
However only 1 idoc gets generated every time.
Can someone suggest how to create the multiple idocs.
Regards
Prasenjit

Hi Prasenjit,
In order to generate multiple idoc first of all you need to change the target structure with multiple occurence...that you have already done...
Now while generating XML in abap mapping you have to make sure you have element idoc(with its content) repeating for your "N" number of idocs...
can you please copy paste your final xml generated...
Nilesh

** Interface Mapping - No Objects Found - IDoc is receiver

Hi Friends,
In our scenario, sender is File & receiver is IDoc. For each record in file, we need to created one IDoc. IDoc is CREMAS.CREMAS05. For this as usual we exported XSD and changed the occurrence of IDOC node as minOccurs="0" maxOccurs="unbounded" (as explained in Michael Blog - 2762) and did the message mapping successfully.
While create Interface Mapping, (Message interface (OB) for File, no message interface for IDoc, we directly use CREMAS.CREMAS05 in the target interface) and 'Read Interfaces' and select the Message Mapping option' it shows 'No Objects Found'. What could be the problem ?
Note that earlier it was working fine (Some times ago), now it is showing this error 'No Objects Found". I am very confused why this error is coming.
Kindly help me friends, to solve this.
Kind regards,
Jegathees P.

Friends,
Thanks for all your reply. When we click Read messages button automaticlly our source message (type) and target message (type) will be selected. Then, we select Mapping Program which is suitable for the Source & Target Message. When we do like this, it is showing the error 'No Objects Found'.
I want to check with you Is this due to what reason ? (Because, earlier it was working fine)
Eventhough we select 'Any' to 'Any' and select the mapping, save. After that If we do consistency check , it will show an warning message about the namespace issue.

Creating custome idocs

hi all
I am XI consultant
i want to send IDOC to XI server using ALE..but the IDOC is not present ....the master data is stored in standard sap tables but for them idoc is not present ...so i want to create custom idoc and using change pointer i can send it across ...is this a write approach...? Also please give me the procedure for the above approach as i dont have idea about how to create custome idoc and send it using change pointer
thanks
Sheetal

Hi
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
Reward points if useful
Regards
Anji

Creating outbound IDOC for EDI

HI All,
I have to create an IDOC for EDI. Can anyone tell be the function module to create an IDOC for EDI. I know MASTER_IDOC_DESTRIBUTE, but it is only used for ALE.
Can anyone help me in this.
Thanks.
Shweta

Dudes:
It sounds to me like all of you guys need some training and some understanding of the basics.
MASTER_IDOC_DESTRIBUTE is called by the standard IDoc interface after an IDoc has been built and is ready to be kicked out the door. It provides all the services needed to write the idoc to the database and send it out through the partner profile and file or tRFC port. It's used both for ALE and EDI IDocs.
I cover the processing flow extensively in my new book from SAP Press "Architecting EDI with SAP IDocs". The book is available from:
http://www.sappress.com/product.cfm?account=&product=H3003
I also cover these topics in my IT Toolbox blog at:
http://it.toolbox.com/blogs/ehadzipetros
And my SDN blog at:
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417600)ID1280983950DB11991735787968519403End?blog=/pub/u/252038725
Good luck. ejh,

How to do configuration to create outbound idoc using message control

The objective is to create outbound idoc based on some selection criteria using message control approach.The interface will be triggered when there is goods receipt via MIGO transaction.............Now based on the material document number from NAST table i am going to fetch data and do further processing inside the function module i am going to create.later idocs will be created via program RSNASTED.How we do the configuration to set up this whole operation?

Please go thru:
1) message control
2) http://help.sap.com/saphelp_di46c2/helpdata/EN/c8/19878343b111d1896f0000e8322d00/content.htm
Regards
Shital

How to create an idoc layout file *.ido

Hello,
I'm want to create an IDOC layout file (*.ido) from a specific idoc (ORDERS05 or another).
How can i do that.
Thanks and regards

It's not the solution. I want an description of the layout of an idoc in a specific format. In this case an *.ido format. I have an conversion program (TIE portal) where i have to import it for interfacing.

API or interface table to create releases for a blanket purchase agreement

Hi
I need to know if Oracle provides a standard API or interface table to create releases for a blanket purchase agreement.
I tried using the release_num field in PO_HEADERS_INTERFACE, PO_LINES_INTERFACE. But this is not working.
I'm able to create the blanket purchase agreement using the open interfaces, but not the releases.
Regards,
Alister

Hi Alister,
You can't create a release of a BPA through API, there is no such APIs provided by oracle.
Where as you can create a BPA by using API. You need to dump/poplulate data in PO_headers_interface & PO_Lines_intreface table.. Then use Purchasing Documents Open Interface API to create a BPA.
Regards,
S.P DASH

How to create Inbound Idocs in a ABAP program? Any function Module?

Hello Experts,
My requirement is : I have sales order data which I extracted from third party system in my internal tables. In the same box I need to create inbound Idocs and then consequently create sales orders.
I have used the function module IDOC_INBOUND_WRITE_TO_DB to create inbound Idocs from Sales Orders data in internal tables. I have populated all the data records with correct PSGNUM and HLEVEL values. My plan is to create inbound idocs with this function module and send those to IDOC_INPUT_ORDERS function module which creates Sales Orders.
If a sales order in the internal table in ABAP program contains only one item, then I am getting correct idocs. But if more than one item exists for a sales order then the line item segments which got repeated in Idoc are having PSGNUM and HLEVEL values as zero when I checked in WE02. As a result the hierarchy from the second item segment is getting disturbed and getting the status 60.
I populated T_EDIDD with data records from IDOC_INBOUND_WRITE_TO_DB.
To the function module IDOC_INPUT_ORDERS, T_EDIDC and T_EDIDD are the input. I observed that in T_EDIDD also the PSGNUM and HLEVEL values are blank.
I am getting Status 60 with message 'EDI: Syntax error in IDoc (segment cannot be identified)' for idocs which have more than one item.
I need to extract sales data from third party and create inbound idocs and create sales orders in one ABAP program only. I need to display corresponding Idoc numbers for the corresponding third party sales order number in a listoutput.
Can anybody please provide inputs?
Regards.

Hi Anjali,
Thanks for the response.
I have passed the PSGNUM and HLEVEL values while populating the data records. Then I sent the data records and control record information to the function module IDOC_INBOUND_WRITE_TO_DB. Inside this function module there is code to clear the PSGNUM values and HLEVEL values.
for compatibility: clear administration data of data records
           perform data_records_wipe
                                  tables
                                      t_data_records.
FORM DATA_RECORDS_WIPE
                  TABLES
                      T_DATA_RECORDS_IN STRUCTURE EDIDD.
LOOP AT T_DATA_RECORDS_IN.
    CLEAR: T_DATA_RECORDS_IN-MANDT,
           T_DATA_RECORDS_IN-DOCNUM,
           T_DATA_RECORDS_IN-SEGNUM,
           T_DATA_RECORDS_IN-PSGNUM,
           T_DATA_RECORDS_IN-HLEVEL.
    modify t_data_records_in.
ENDLOOP.
ENDFORM.                               " DATA_RECORDS_WIPE
This is the code which is clearing all the PSGNUM and HLEVEL values. After coming out of this function module we are getting the error idocs created with disturbed hierarchy.
I need to create INBOUND Idocs with the data in ABAP program.
Please let me know if any inputs? Is there any function module existing to create Inbound Idocs inside an ABAP program?
Regards

How to create an IDoc just with the updated data.

Hello I have a question regarding IDocs.
In case I updated an existing material.
Is there a transaction where I can put a matnr in, that reads the change pointer table and creates an IDOC with just the updated fields for an existing material.
Like the transaction BD21, for example. But there I just have the possibility to enter a message type and not a material number.
If there is no standard transaction. What steps do I have to do to achieve this goal?
Kind regards,
Tobias

thanks a lot for your fast answers. but I want to decide weather I want to create a idoc that includes all data for a material (using transaction bd10) or create an idoc that includes just the updated data.
The program logic should be the following:
Select all materials in the change pointer table (that have been changed or new created).
Check what value has been changed.
If it is value YSAPSYSTEMXX (extension of mara) then create a idoc with all data for the material.
If not YSAPSYSTEMXX has been changed create an idoc that includes just the updated data.
For Idocs that include all material data I would use sap standard transaction BD10 and batch-input.
For Idoc that should only include the changed/updated data I am searching for a corresponding transaction.
Kind regards,
Tobias

URGENT : TAS Interface - BOM SO create a IDOC Automatically

Similar Messages

Maybe you are looking for