Posting a idoc

Hi,
I am working on SAP CRM .Currently i used the XI system to read a XML file file using a file adapter and posting the information as a inbound idoc in the CRM system using the idoc adapter.
Can the same functionality be achieved without using XI? Can the XML document be read by a ABAP program and can the information be used to create a idoc without making use of XI.
Regards,
Shambavi

Hi,
For File to IDOC,
in R/3
1.create rfc connection using sm59
2.create Logical sys using bd54
3.create port using we21
4.create partner profile using we20
in xi
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
How ToConvert an IDoc-XML structure to a flat file and vice versa in XI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
********Please award with points,if useful

Similar Messages

Error while posting the IDoc for Customer Invoice.

hi,
I m posting Customer Invoice through LSMW using IDocs.
Basic type is FIDCCP02 and message is FIDCC2.
While posting the Idoc I m getting error as:
'Document or line item does not exist for invoice reference'.
I m not getting the error why it is asking for invoice reference because
in FB01 it is not asking for any reference or anything.
Even in f-22 also it is not asking for the same.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-Umesh

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Error while posting Invoice IDOC (The difference is too large for clearing)

Hi All,
While posting Invoice IDOC to Remittance Advice IDOC get fails with status 51 & message ' The difference is too large for clearing'.
Please suggest any solution or reason to fail IDOC.
Thanks & Regards,
Ajay
Moderator message: please search for information and try to find out yourself before asking, this will be a functional problem anyway that should be asked in the appropriate forum, e.g. ERP Financials.
locked by: Thomas Zloch on Aug 20, 2010 1:59 PM

Pls check the tolerance amounts limits:
SPRO--- F/A --AR/AP -
Business transactions -Open item clearing--- Clearing differance---- Define / Assign tolerance groups for emp -
Where you need to change the limits of max amounts with the %
Let me know for any info.
Regards
Suresh

Non-po invoice posting using IDOC into LIV module

Hi,
does anyone know if idoc interface is available for posting non-po invoice as an LIV invoice into MM module. what I found that I can post the idoc to FI module directly using message code - FI.
Thanks.

Hi
I Got your name from this site.I would be very thankful if you can help me here.I am designing a EDI based invoice LIV.Is it possible to post some charges which are without PO reference but are coming in Vendor Invoices.Is it possible to post these kind of charges with EDI message INOIC01 or we have to post through FI posting.If possible through EDI in which segment of IDOC we will enter these charges with amt.Also is it possible to post credit memo also with EDI
Thanks
Sanjeev

Error while trying to post inbound idoc of message type COND_A

Hi,
I am getting error while trying to post inbound idoc of message type COND_A.
If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
and if providing value in above fields then dump is coming.
How to solve ?
Plz do reply
Thanks
Mohit

I do not see any reason why you would need to use COND_A04 if COND_A01 is working.
What if you could get COND_A04 to post and you would face the same result as in COND_A01?
If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
fixed a situation where the vendor number was not validated.

Error while posting the IDOC. Status message '56'

Hi,
I have a requirement where I will post an IDOC which inturn will split the original IDOC into child IDOCs based on the store value.
I am trying to post the IDOC in WE19. So, the Original IDOC is posted successfully with status '53'. Whereas, the child IDOCS finished with error. The status of the message is '56' and the error says 'EDI: Partner profile not available'. Could someone tell me what could be the reason for this..?
Actually, the IDOC was created by the Functional Consultant. So, should the partner profile creation also done by them or do we need to do anything to solve this problem.? Could someone answer me this question. Thanks in advance.
Best Regards,
Paddu.

It looks like the control data for the child segment is not getting populated. you have to find the code which populated the control data and see if it is doing what it should.

Error while posting the Idoc 'Update error, transaction VA01'

Hi Gurus,
When an inbound Idoc for sales order is trying to post we are getting the error 'Update error, transaction VA01'.
Aslo following are the details of the error:
Update error, transaction VA01
Message no. 00377
Diagnosis
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
Update information
Return code: 009
Text : Error during insert table FPLTC (RC= 1, Key= )
Procedure
Pleas analyse your Batch-Input data.
You can also examine your posting data using the transaction SM13.
Can somebody let me know what would be the cause.
Also the we are trying to post the Idoc with a Id which is having maximum Authorization.

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Not able to Post multiple IDOCS

Hi All,
I am getting my output from XSLT mapping like below:
<?xml version="1.0" encoding="UTF-8" ?>
<ZORDERS5>
+ <IDOC BEGIN="1">
+ <IDOC BEGIN="1">
</ZORDERS5>
But in the SAP R/3 it is able to post only the last IDOC (which is second IDOC in this case). I want to post all the IDOCS. What could be the problem?
Edited by: sreinivas prak on May 13, 2008 11:12 AM

Hi Srinivas,
Post multiple IDOCS
There are two Message Mappings involved in the whole scenario. First mapping is N:1 Mapping which will be used in BPM and second Mapping is 1:1 Mapping:
1. First Message Mapping  N: 1 Mapping between IDoc (occurrence 0...unbounded in Messages tab) to IDoc with changed occurrence of its top node (IDOC) as 0...unbounded.
Check these Blogs:
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter
/people/prasadbabu.nemalikanti3/blog/2006/02/24/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-1
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on May 13, 2008 11:21 AM

Error 'Maximum number of sessions reached' while posting an idoc

Hi,
i got one requirement that when ever user enters so many materials with different quantities and version id's and when he executes,it has to post the idocs using FM .but if the number of records increases,iam getting error that 'maximum number of internal sessions exceeded' how can i avoid this for successfful posting.To avoid this i called the FM in background .If i call the FM in background it is not at all posting even one idoc also.Can anybody please help on this .
Thanks & Regards
Roopa

Hi,
i got one requirement that when ever user enters so many materials with different quantities and version id's and when he executes,it has to post the idocs using FM .but if the number of records increases,iam getting error that 'maximum number of internal sessions exceeded' how can i avoid this for successfful posting.To avoid this i called the FM in background .If i call the FM in background it is not at all posting even one idoc also.Can anybody please help on this .
Thanks & Regards
Roopa

Help required in posting inbound idocs

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

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

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Problem with Posting Sender IDOC

Hi,
I am Integrating SAP R/3 with a web browser Using SAP XI
Sender : SAP R/3 -
> IDOC Adapter
Receiver : Web Browser----->Soap Adapter
In SAP R/3 I am doing for " PM Module"
for Transaction IE02 ( Change Equipment),
This Transaction is Used to change any details of that Equipment.
I Identified the Standard IDOC which is created by using BAPI
"EQUIPMENT_CHANGE.EQUIPMENT_CHANGE01"
I configured ALE at Sender and configured Soap Adapter at receiver side.
My Query is,
Now I want to Post the IDOC , For the Above IDOC How should i send.
( For Example for Matrerial MATMAS for Posting IDOC it has transaction BD12)
But for Posting My IDOC wat will be the transaction and How should I post it.
Points will be awarded for the answer.
My Email ID is : [email protected]
Regards,
Jayasimha Jangam

Hi Jayasimha,
You should do the following configurations to post an IDoc from R/3 to XI.
Once check wheather these configurations are done.
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

Posting multiple idocs without BPM

Hi all,
We have a JDBC->XI->Idoc scenario.
We would like to post "n" idocs to SAP for the "n" records fetched from database.
Due to performance issues we are not using BPM.
Is there any other way to post multiple idocs without using BPM.
rgds
Prashant

HI,
As suggested by others, it is possible without BPM.
For this, you need to alter the Idoc Schema i.e change the occurence of the idoc in the idoc schema. Then import this xsd as a External Definition into Repository..then mapping etc ..
Regards,
Moorthy

Error in posting the Idoc....

Hi Experts,
When I post the Idoc from the external system to the SAP,I am getting the
error as application document not posted and status code as 52.so what I need
to do to overcome this error,please help me over this issue.
Regards,
Kiran.

Hi,
you have to check the idoc in debugg mode and pull it out the reason why i has 52 and you know how to debug inbound - go to we19 and here give any existing idoc no and press F8 and enter into screen, in that select 'INBOUND FUNCTION MODULE' select give ur standard F.M name and select the background mode.
or thre way is goto BD87 make the correct the error idoc manually.
--Use Tcode BD87 to check for IDocs that are not been processed and reactivate.
u can find here if any data wrong or missing.
Reward if useful
Regards,
Vijay

How to post an Idoc (INVOICE02) for non-po Invoice (MIRO transaction)

Hi,
I want to Post an Idoc for non-po vendor Invoice through MIRO transaction. I want to use INVOICE02 basic type. In the line item we need to enter G/L account , Cost center and line item amount. But I am not able to enter the same in the INVOICE02 Idoc. It will be nice if you please let me know how to post non-po Idoc through MIRO transaction.
Thanks
Rama
Edited by: Rama Sengupta on Nov 25, 2009 3:57 PM

Hi Raja,
Check this out.
Inbound IDocs are triggered by either external systems (edi, wms etc) or can be triggered by inhouse applications in SAP to post a application document.
1. EDI_DATA_INCOMING can create a IDoc from a file on the OS layer. It just needs a IDoc flat file containing control and data records, it will create an Idoc from it if the control record successfully matches a inbound partner profile parameters.
2. IDOC_INBOUND_ASYNCHRONOUS can be triggered by external/internal programs to creae IDoc withing SAP, whereas IDOC_INBOUND_SYNCHRONOUS can be used by inhouse SAP programs to create inbound Idoc.
3. WE19 can create and post an existing inbound Idoc to application
Hope this resolves your query.
Reward all the helpful answers.
Regards

Error oocuring after posting the IDOC

Hi
i am getting a error in a scenario
the scenario is Idoc to file. when we post the IDoc, its getting posted successfully. but the pipiline is getting failed at the inbound message when monitoring in SXMB_MONI.
i am getting the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIAdapter</SAP:Category><SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/>
<SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server
</SAP:Stack><SAP:Retry>N</SAP:Retry></SAP:Error>
all the experts help me out in solving this issue

Hi Deepika,
their might be some problems with ur ALE settings.
Here is a detail of the steps to be followed.
Do verify whether u have done the steps or repeat the steps as stated:
Steps for ALE settings:-
Steps for XI
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the R3 system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto IDX1.
 Create a new port.
 Give the port name.
 Give the client number for the R3 system.
 Select the created Rfc Destination.
Step 3)
 Goto IDX2
 Create a new Meta data.
 Give the Idoc type.
 Select the created port.
Steps for R3.
Step 1)
 Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the XI system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
Step 2)
 Goto WE21.
 Create a port under transactional RFC.(R3->XI)
 Designate the RFC destination created in prev step.
Step 3)
 Goto SALE.
 Basic settings->Logical Systems->Define logical system.
 Create two logical systems(one for XI and the other for R3)
 Basic settings->Logical Systems->Assign logical system.
 Assign the R3 logical system to respective client.
Step 4)
 Goto WE20.
 Partner type LS.
 Create two partner profile(one for XI the other for R3).
 Give the outbound or inbound message type based on the direction.
Step 5)
 Goto WE19
 Give the basic type and execute.
 fill in the required fields.
 Goto IDOC->edit control records.
 Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
 Click outbound processing.
Step 6)
 Go to SM58
 if there are any messages then there is some error in execution.
 Goto WE02.
 Check the status of the IDOC.
 Goto WE47.
 TO decode the status code.
Step 7)
 Not mandatory.
 Goto BD64.
 Click on Create model view.
 Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)

Posting a idoc

Similar Messages

Maybe you are looking for