Idoc posting in SAP

Hi Gurus,
Im working on file to RFC scenario.
According to the business requirement, I have split the file or message and for each message RFC is called to post the idoc in the SAP system.
If the batch file contains 3 messages, the batch is getting split but teh order is not getting maintained...
The first message should be processed first and the idoc should get posted in SAP.
The second message should be processed after teh first one and the idoc should get posted in SAP.
The third message should be processed after the second one..
But in reality teh first message is processed first and idoc got posted.
The third message is processed next and second message is processed after the third message.
I checked the box Maintain Order At Runtime in PI interface determination.But this did not serve the purpose.
Can you please provide any solution to maintain the order while sending the RFC-xml messages from PI to SAP.
Thanks,
Jay
Edited by: j r saithala on Sep 29, 2011 3:24 PM
Edited by: j r saithala on Sep 29, 2011 3:47 PM

Hi,
So to understand the requirement, you need to maintain order for the messages received from the legacy and send it in sequence to SAP. You are using RFC adapter instead of the IDOC adapter in the receiver side.
If you click on the maintain order at runtime in the Interface determination, SAP does create a serialize queue. But ideally we should have a dedicated queue scenario which will be better performance & design wise.
Design
1. Sender file adapter communication channel should be set as EOIO ( input the queue name ) so the receiver QOS also changes to EOIO. You need to use IDOC adapter on the receiver side.
2. IDOC Receiver adapter you use the queue processing which will help your requirement.
Regards,
Indranil

Similar Messages

SAP MDM == PI== SAP ECC, IDOC posting

Hi,
We are integrating SAP ECC 6.0 with SAp MDM 7.1 SP04 using PI 7.1 as a interface. Scenario is SAP MDM ==>PI==> SAp ECC. I would be creating record in ECC and will be posted in SAp ECC through PI. We will be creating Basic Data (MARA), Plant level data (MARC), Sales Level data (MVKE), and Valuation level Data (MBEW) in MDM. IDOC used is MATMAS05.
Plant level data (MARC) will activate various views in Material master like Purchasing, Sales plant general data, MRP views and accounting views...right
I donu2019t want to activate MRP view but need plant level data i.e. Plant and profit center to populate in MARC table. Means same Material Type but some Materials donu2019t have MRP view activated and some may have alongwith other plant related views.
I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory. (Which means it is activating MRP view)
Do we have separate IDOC for MDM integration?? Do I need to enhance IDOC??
Warm regards,
Rc
NOTE - This is possible while manual creation as will as through BAPI.

Hi,
Have you checked MDM71_Material_Content.pdf page no 20.
3.3.2 Business Scenario: MDM710_Outbound.
You also need MDM PI content to install and run this Scenario..
Hope it helps if you go through MDM71_Material_Content.pdf
As you said, I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory
Try passing any constant through PI Message Mapping to inbound IDOC (Receiving System, ECC)
Thanks and Regards,
Mandeep Saini

What triggers idoc posting in outbound message from sap ?

Do change or create events can be used to trigger Posting to IDOC? Have any body used idoc for outbound message sending from SAP?

Hi Reddy,
Posting IDoc Packets
Two groups of function modules are used to post IDocs:
· Function modules which process IDocs in mass. These transfer packets of IDocs for which individual IDocs are updated in the same Logical Unit of Work (LUW).
· Function modules which process one IDoc per call.
· INPUTTYP contains the code for posting function modules.
To display the function module's INPUTTYP on the ALE Development screen, choose IDoc ® Inbound Processing ® Function Module® Maintain Attributes (BD51).
INPUTTYP can contain the following values:
· "0", for function modules which process IDocs in packets.
"1" and "2" for function modules which process one IDoc per call:
If you post the IDocs immediately, the SAP sending system determines the packet size. ALE inbound processing can recognize if the posting function module allows packet processing and if so, passes the IDoc packet to it. If not, the IDoc packet is split into individual IDocs.
If IDocs are posted in the background, you can specify the size of the IDocs to be generated in the program RBDAPP01.
If you use function modules that can process IDocs in mass, the database load is reduced.
If you group IDocs into packets, this may also be practical for function modules that post inbound IDocs one at a time, because the ALE layer calls the function module several times in the same dialog process, thereby reducing the administrative load on the SAP system.
If program RBDAPP01 carries out the background processing, as a guide, you should use a packet size of between 20 and 100 IDocs.
Packet processing and parallelism complement one another. Packet processing and parallelism complement each other, although in some situations they may compete with each other. If the size of the packet is too big, this may mean that not all the available dialog processes are being used.
Scheduling IDoc Posting
There are two ways of posting IDocs in ALE inbound processing:
·        Immediate processing:
Upon receipt inbound IDocs are immediately released for posting. ALE inbound processing splits the IDoc packets into individual IDocs.
·        Background processing
Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.
The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.
Perform the following steps:
1.       Set-up background processing (IDoc/ALE area menu):
IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Profiles (WE20)
Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.
2.       Schedule posting (ALE customizing):
Transaction SALE ® Set-Up System Monitoring ®
         Posting IDocs in Recipient System ®Schedule
You can also process the IDocs manually by passing them to the posting function module. In ALE Administration choose Monitoring ®Status Monitor (BD87), select the IDocs and then select Process.
Regards,
Kumar.

Idoc not posted in sap system

Hi All,
i have configured the file to idoc and idoc to idoc scenario.
in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the port that is idoc comming from sap system.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space of the idoc ,which is not to our operational mapping created in IR.
Regards,
reddy

in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the
port that is idoc comming from sap system.
In Message Mapping enable the EDI_DC40 segment and then give value to the SNDPOR/ RCVPOR ....once done in receiver IDOC channel check the Apply Control Record from Payload....Michal has written a blog on EDI_DC40 segment check it once.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space
of the idoc ,which is not to our operational mapping created in IR.
This behavior is correct....IDOC will refer to its own namespace and not to the one created in IR.....and this should not cause any issue while assigning mapping in Interface Determination....if it is causing an error then you have not selected the objects properly.
Regards,
Abhishek.

IDOC generation in SAP R/3

Hi,
I want to know how to generate the IDOC for MATMAS??
Regards
suman

Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
Create File Port (WE21) for outbound file.
Maintain Distribution Model (BD64) for sender ->receiver system.
Create Partner Profile (WE20) for logical system.
You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
Create File Port (WE21) for inbound file.
Maintain Distribution Model (BD64) for receiver -> sender system.
Create Partner Profile (WE20) for logical system.
You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
links that will help you
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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
cheers
sharad
Edited by: sharad narayan on Apr 16, 2008 1:23 PM

Reg : Idoc Transfer From SAP R/3 to Gentran

Hi Floks /
Any body can transfer SAP R/3 idoc to external Sterling Gentran intgration suite . what are process steps required to sending and what are the transaction codes are available in Gentran and Sap .
can u please help me out.
thanks
suresh

HI,
See the below links
In Gentran
XI with Gentran
XI vs Gentran for EDI
SAP ECC 5.0 Upgrade questions with Gentran, BDC, screens
Gentran EDI ?
Interuppting/debugging response from Gentran
Gentran and XI 3.0 question
Interuppting/debugging response from Gentran
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d53af8ca-0801-0010-08b0-dce9e02130a8
In R3 IDocs
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm - Collection of IDoc to Single File
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
File-XI-IDoc Scenario - File to Idoc
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
see the below links to get more details about IDocs
ALE/ IDOC/ XML
Troubleshooting of ALE Process - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Please check this online document for ALE and IDoc.
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
serialization /people/alessandro.guarneri/blog/2006/11/26/content-based-serialization-dynamic-queue-name-in-xi
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.henrikfrank.dk/abapexamples/IDOC/gl_postings2.htm
http://searchsap.techtarget.com/ sDefinition/0,,sid21_gci852485,00.html - 45k - Cached - Similar pages
Process codes in IDOC
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b806743d711d1893e0000e8323c4f/frameset.htm
http://edi.stylusstudio.com/msg04418.htm
Check this link to find out the difference b/w ALE,IDOC and BAPI
http://www.sap-img.com/abap/ale-bapi.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
---Split messages :
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
Regards
Chilla

Issue in Idoc Posting

Hi Guru's,
I am facing an issue during the consumption values upload in forecasting view thru LSMW (BAPI) with Idoc, issue is that at the end of the upload i am getting status of Idoc posting is 53 which is Application Document Posted, but i found some of the the materials for which consumption values were not uploaded but Idoc posting status is showing 53 and getting massage:Material number XYZ1234 in version already exists.
Kindly give ur expert opinion on the above mentioned issue.
With Regards.

A little clarification might help you... explain 'BOX'. Do you mean an SAP Instance? SAP Instance/Client? Or ??

Starting new database LUW inside ABAP during IDoc posting

Hi all,
During posting of an inbound IDoc, I am trying to update my Z-table in user-exit. I want to do it regardless of the result of IDoc posting. The problem is: if IDoc posted successfully - table is updated because COMMIT WORK is called at the end of the posting, however, if IDoc not posted - ROLLBACK WORK is called and table is not updated. So, my aim now is to commit the update of Z-table in any case, but it is the only thing that should be committed - no other prior update FMu2019s should be committed.
I'm aware about the following thread
http://forums.sdn.sap.com/thread.jspa?threadID=1884700
Author of this thread says that he solved a problem by means of RFC and STARTING NEW TASK. But ABAP help says
that starting asynchronous RFC triggers immediately a database commit in the calling program (which is unacceptable because all prior update FMu2019s will be committed ). I've checked and it is really the case.
From my point of view SET UPDATE TASK LOCAL with COMMIT WORK should work in such kind of tasks, but in case of IDoc processing the whole process runs in a local update (see SET UPDATE TASK LOCAL in FM 'IDOC_INPUT'), so writing once again SET UPDATE TASK LOCAL has no effect.
I tested SUBMIT statement as well. It had no effect and then I found out from ABAP help that SUBMIT ... AND RETURN starts new SAP LUW, but NOT a DB LUW. That is if I update my Z-table in the program called by SUBMIT - all ROLLBACK statements still affect my Z-table update.
Is there any simple solution? Please suggest.
Thanks in advance!

Hello,
Try SUBMIT VIA JOB.....
Sample Code
call function 'JOB_OPEN'
exporting
jobname = name
importing
jobcount = number
exceptions
cant_create_job = 1
invalid_job_data = 2
jobname_missing = 3
others = 4.
if sy-subrc = 0.
submit z_idoc_create_process_order and return
via job name number number
with p_aufnr = it_header1-aufnr
with p_werks = it_header1-werks
with p_autyp = c_autyp
with p_auart = it_header1-auart
with p_dispo = it_header1-dispo
with p_opt = c_opt
with p_mestyp = c_mestyp.
if sy-subrc = 0.
call function 'JOB_CLOSE'
exporting
jobcount = number
jobname = name
strtimmed = 'X'
exceptions
cant_start_immediate = 1
invalid_startdate = 2
jobname_missing = 3
job_close_failed = 4
job_nosteps = 5
job_notex = 6
lock_failed = 7
others = 8.
if sy-subrc 0.
endif.

/SAPTRX/IDOC_INPUT_EVMSTA IDoc posting only works for single BAPI call

Although the settings and code imply that the function /SAPTRX/IDOC_INPUT_EVMSTA can handle multiple events in a single IDoc the fact is that the code does not have a refresh statement on the BAPI internal tables with the loop through the IDoc control record. This means that we end up posting multiple events for the the same event during Idoc posting.
Is SAP going to fix this situation? PS: The same applies with the EHPOST Idoc function module.
Thank you
Kevin

Dear,
I just debugged my Z-function, after adding all input parameters as in the standard BAPI function.
All parameters seems to be passed correctly except from the table parameters from
CLASS_OBJECTS
So all I_parameters are passed :
{ZBAPI_CLASS_GET_CLASSIFICATION.I_LANGU_INT} = "EN" and
{ZBAPI_CLASS_GET_CLASSIFICATION.I_LANGU_ISO} = "EN" and
{ZBAPI_CLASS_GET_CLASSIFICATION.I_KEY_DATE} = Date (2011, 08, 05) and
{ZBAPI_CLASS_GET_CLASSIFICATION.I_CLASSNUM} = "DSWTEST" and
{ZBAPI_CLASS_GET_CLASSIFICATION.I_CLASSTYPE} = "001" and
{ZBAPI_CLASS_GET_CLASSIFICATION.I_CHARACTS_OF_CLASS_ONLY.BAPIFLAG} = ""
but the table parameters aren't coming through:
{ZBAPI_CLASS_GET_CLASSIFICATION.T_CLASS_OBJECTS.OBJECT_TYPE} = "MARA" and
{ZBAPI_CLASS_GET_CLASSIFICATION.T_CLASS_OBJECTS.OBJECT_KEY} = "000000000000000085" and
these are 'blanco' in the function.
also after the function is executed and all data is retrieved, when passing the data back to Crystal reports, once again, the table result isn't passed to Crystal Reports.
please advise

Update idoc data into sap

Hi All,
I had an requirement where the inbound idoc contains data i want to upload that data into sap. How to update the value that is coming in the Idoc to our SAP system. so that the data has to reflect in database tables.
Regards,
Karthik
Moderator message: please search for available information/documentation/how-to guides.
Edited by: Thomas Zloch on Apr 5, 2011 2:14 PM

Hi Madhu,
Check this link
Re: What about receiving?
Post ur query in this forum .U might get possible solutions for ur requirement.
[SAP Netweaver Mobile|SAP for Mobile;
Regards,
Lakshman.

IDOCS: Inbound non-SAP system

Hi
The outbound idocs works fine. I want to create an inbound goods receipt/movement idoc.
Should i rather write RFC to update the SAP system from a non-SAP system ?

Hi,
Your first query...
Should i rather write RFC to update the SAP system from a non-SAP system ?
Always prefer using idocs for posting before BAPI / RFC fucntion module.
As you have mentioned outbound idocs are working fine..which means you are able to create idocs from non-sap system..right? If so you can use same idoc type for posting.
Your second query's answer...
Check out following code for calling BAPI_GOODSMVT_CREATE
You need to code to call function module /BAPI in your posting program as follows..
append the data into the corresponding internal tables and work-area, check for the IMPORT and TABLES parameter in the function module BAPI_GOODSMVT_CREATE.
a.     GOODSMVT_HEADER-DOC_DATE = SYST-DATM
b.     GOODSMVT_HEADER -PSTNG_DATE = RECEIPT_DATE (Input File)
c.     GOODSMVT_HEADER - HEADER_TXT = BATCH ID (Input File)
d.     GOODSMVT_HEADER - GR_GI_SLIP_NO = GOODS_INWARD_NO (Input File)
e.     GOODSMVT_ITEM-MOVE_TYPE = Constant 101
f.     GOODSMVT_ITEM-PO_NUMBER = PURCHASE_ORDER_NO (Input File)
g.     GOODSMVT_ITEM -PO_ITEM = PURCHASE_ORDER_LINE_NO (Input File)
h.     GOODSMVT_ITEM PLANT = From Selection Screen (WERKS)
i.     GOODSMVT_ITEM STGE_LOC = From Selection Screen (LGORT)
j.     GOODSMVT_ITEM -ENTRY_QNT = QUANTITY_RETURNED (Input File)
k.     GOODSMVT_ITEM -NO_MORE_GR = COMPLETE_INDICATOR (Input File). Value X if status = X else space.
6.     Call the function module BAPI_GOODSMVT_CREATE.
7.     Use function module BAPI_TRANSACTION_COMMIT to do the commit work.
append the data into the corresponding internal tables and work-area, check for the IMPORT and TABLES parameter in the function module BAPI_GOODSMVT_CREATE.
a.     GOODSMVT_HEADER-DOC_DATE = SYST-DATM
b.     GOODSMVT_HEADER -PSTNG_DATE = RECEIPT_DATE (Input File)
c.     GOODSMVT_HEADER - HEADER_TXT = BATCH ID (Input File)
d.     GOODSMVT_HEADER - GR_GI_SLIP_NO = GOODS_INWARD_NO (Input File)
e.     GOODSMVT_ITEM-MOVE_TYPE = Constant 101
f.     GOODSMVT_ITEM-PO_NUMBER = PURCHASE_ORDER_NO (Input File)
g.     GOODSMVT_ITEM -PO_ITEM = PURCHASE_ORDER_LINE_NO (Input File)
h.     GOODSMVT_ITEM PLANT = From Selection Screen (WERKS)
i.     GOODSMVT_ITEM STGE_LOC = From Selection Screen (LGORT)
j.     GOODSMVT_ITEM -ENTRY_QNT = QUANTITY_RETURNED (Input File)
k.     GOODSMVT_ITEM -NO_MORE_GR = COMPLETE_INDICATOR (Input File). Value X if status = X else space.
6.     Call the function module BAPI_GOODSMVT_CREATE.
7.     Use function module BAPI_TRANSACTION_COMMIT to do the commit work.
Hope this will help you.
Cheers,
Nilesh

How to trigger IDOC'S from SAP

Hi All,
How to trigger IDOC's from SAP(ECC 6)..where can we check this in mii 11.5 weather it is fail/success
Thanks,
Abhi

You can trigger LOIPRO, LOIPLO and a few others manually from POIT (SAP Txn). Master Data related to orders can be triggered from POIM. Depending on which IDocs you which to generate, there are other transactions to trigger different IDocs.
You can also use Triggers from MII to generate IDocs in SAP using CLOI_DOWNLOAD_TRIGGER_MDAT (POIM equivalent) and CLOI_DOWNLOAD_TRIGGER_TRANS (POIT equivalent).
There is also a rather nice post which detailed the process of using change pointers to automate the IDoc generation and download, but I am having trouble finding it. Will continue to look and will post link when I find it.
Regards,
Mike
I couldn't find the post I was looking for, but there is an informative note 390635 which may help.
Edited by: Michael Appleby on May 5, 2009 1:29 PM

IDOC posted with error

Hi
working on File2 IDOC scenario..my idoc posted .. but that is red and green in SXMB_MONI... where should I check for correct the problem?

I am getting error like this :(SXMB_MONI)
<?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="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please help me

Collecting or time based inbound idoc posting

Dear All,
We have need of posting idoc's in a specific time interval in SAP ECC system. Please help us.
requirement is We are pushing idocs to ECC , but the idoc should get process only between 3 Pm to 6 PM.
Kindly help us.
Regards
Pradeep P N

hello pradeep,
Schedule a Background job whenever you get the IDOC in to SAP .Run the Job at specific time.
We had a similar scenario where we had to post it after 24 hours.
sample code ......
start_time = "when ever you want".
WRITE docnum TO name.
SHIFT name LEFT DELETING LEADING '0'.
CONCATENATE 'POST_IDOC_' name INTO name.
CONDENSE name.
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobname          = name
    IMPORTING
      jobcount         = number
    EXCEPTIONS
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      OTHERS           = 4.
IF sy-subrc = 0.
Fill idoc number
    r_docnum-low = docnum.
    r_docnum-sign = 'I'.
    r_docnum-option = 'EQ'.
    APPEND r_docnum.
Fille message type
    r_mestyp-low = mestyp.
    r_mestyp-sign = 'I'.
    r_mestyp-option = 'EQ'.
    APPEND r_mestyp.
Manual processing of IDOCS
    SUBMIT rbdmani2 WITH so_docnu IN r_docnum
                     WITH so_mesty IN r_mestyp
                     WITH p_output = ''
                     WITH p_wodial = 'X'
                      VIA JOB name NUMBER number
                      AND RETURN.
    IF sy-subrc = 0.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount             = number
          jobname              = name
          sdlstrtdt            = start_date
          sdlstrttm            = start_time
        EXCEPTIONS
          cant_start_immediate = 1
          invalid_startdate    = 2
          jobname_missing      = 3
          job_close_failed     = 4
          job_nosteps          = 5
          job_notex            = 6
          lock_failed          = 7
          OTHERS               = 8.
      IF sy-subrc <> 0.
      ENDIF.
    ENDIF.
ENDIF.
ENDFORM.                    " POST_IDOC_DAYS_LATER
Thanks,
Pradeep.

IDOC POsting Error: Transition no. OBJ_SYS is blocked by another user

Hi Experts,
I m sending the XML from a third party system into SAP using XI as middleware for IDOC posting (FB01).
I m getting an error <b>Transition no. <xx> is blocked by another user</b> while sending intercompany and cash applications. SAP is unable to process such XML directly.
But if i login to SAP and mannually post the IDOC, it is getting posted successfully.
Any idea what may be the cause?
Useful answers will be rewarded for sure.
Regards
DhanyaR Nair

Hi Dhanya,
        In your inbound idoc processing program, pls do use the lock mechanism for the FI document which you are processing and if it cannot be locked then keep it on wait for sometime and check for the same.
        If its a standard program check whether it can be done in XI.
      When SAP is locking the transaction it will be unlocked after the commit work and hence its happening.
The reason why you may not be getting this in individual processing is that you are doing the same thru a single session. And the lock if am not wrong is happening in table level and not in record level.
Cheers
JK

Idoc posting in SAP

Similar Messages

Maybe you are looking for