JMS file to idoc

Hi,
where in I will get the file is read using JMS adapter,here I have a problem with the content of the flat file as shown below
<?xml version="1.0" encoding="ISO-8859-1"?>
<MessageHeader>
<RecipientId>SAP.TEST</RecipientId>
<RecipientSapSystemId>xxxxx</RecipientSapSystemId>
<RecipientIdQualifier> Application</RecipientIdQualifier>
<SenderId>aaaaa</SenderId>
<SenderIdQualifier>yyyyyyy</SenderIdQualifier>
<ApplicationId>zzzzzz</ApplicationId>
<ApplicationIdQualifier> Application</ApplicationIdQualifier>
<DateSpecifier>iii</DateSpecifier>
<DateFormatSpecifier>YYYYMMDD</DateFormatSpecifier>
<Date>20110208</Date>
<TimeFormatSpecifier>HHMMSS</TimeFormatSpecifier>
<Time>154126</Time><AuthorizationId>sunny</AuthorizationId>
<MessageKeyData>???</MessageKeyData>
</MessageHeader>
TID00702751
TTE007027512011-02-08-15.41.00.000000K210164   450003280000032700001173490003906
TO100011734                                                   AJL
TO200004004700000000326007600000720800005057000
Thanks in advance
Edited by: SWATHIP on Feb 24, 2011 7:03 AM

I think, your mmeta data file i.e. message type is in complete as it has only header so JMS adpater is not able to convert the entir message into XML.
/Adi

Similar Messages

File to idocs - sequence of inbound processing

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

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

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

Logical System in file 2 idoc

Hi
I am developing an scenario of file to idoc.
My problem is, when it is generating the idoc in target system, the Parner Number in control record is filling with the logical system name given when creating the business system.
I tried changing the logical system name with actual partner number which I want but giving an error ' The selected integration server already has a business system with logical name "pidclnt001". Select a different integration server or change the logical name. '
Can anybody advice me, is it not possible to create two scenarios to send same Idoc to same system ?
Regards,
Shylesh

Hi Shylesh !
You need to enable the header mapping option in your receiver agreement to overwrite the Logical System name that is sent to the R/3 destination system...which now is the Logical System name linked to your sender system (info is in SLD if is a business SYSTEM or in the Adapter Specific identifier attributes if it is a business SERVICE)
You cannot have more than 1 business service/system with the same Logical System name...but you can overwrite the sender logical system name that arrives to the destination R/3 system using the header mapping section of the receiver agreement as noted above.
Regards,
Matias.

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

File to Idoc OR File to AbapProxy

Hello,
Let me expose my problem.
In fact, I need to integrate new Goods Movements sent by a non-Sap system to ECC system.
To do that, the non-sap system sends a file.
Then, I need to generate from this file an Idoc (MBGMCR), fill this Idoc with some extra data (from Ecc tables) and then to integrate it into ECC.
The question here is to find the best solution (according to performance and feasibility) to do that using PI (7.0).
We are hesitating between two scenarios:
1- File to Abap Proxy
We get the data sent by an abap proxy, and then we complete it with the necessary extra data from ECC tables in order to create complete the Idoc segments.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Even, using PI will be a waste of performance/time (due to mappingu2026)
2- File to IDOC
This alternative looks more interesting (at least in the PI way).
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
For example, the file contains Orders headers and I need to generate Goods Movements for the materials contained in the orders. So I need to access Orders posts, to retrieve the materials data.
Is there a way to retrieve simple information in PI using ECC data?
Any other suggestion/comment is welcome.
(Any other scenario is also welcome)
Thanks you in advance.
Saber L.
SAP PI consultant.
Edited by: LMS LMS on Nov 7, 2008 10:24 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM
Edited by: LMS LMS on Nov 7, 2008 10:25 AM

ABAP proxy would improve performance in terms of providing adapterless communication.
In this case, I canu2019t see the need of SAP PI because we could have just basically read the file directly with ECC.
Making a direct connection would increase point to point connectivity across the organization whose reduction is one of the reason why XI is used.
If ur communication is async and u have the idoc structure ready, then u may proceed with Idocs.
But this scenario may lead to the following problem: there are a lot of fields not filled by the data coming from the non-sap system (even whole segments).
If you want to prevent the node from getting generated, simply disable it in mapping.
I hope u have seen this
Choose the Right Adapter to integrate with SAP systems
Regards,
Prateek

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

Error in file to idoc scenerio

hi
in file to idoc scenario
i got error in sxmb_moni
in status it is showing recording,
in Q.status it is showing stop symbol.
waiting for suggestions.

Hi Sandeep,
Have a look at queue problms here
/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
Some additional help
Q.Status is "Queue stopped"
queue status is stopped
Regards,
Prateek

Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

Weblogic Server 9.2 - JMS File Store not working as expected.

Hi,
I am facing a problem at the server startup possibly due to huge size of the JMS File Store created.
My question is that our application receives messages via MDB (container managed),
Even after successfully processing the message, the message which is logged in the File Store is not deleted.
How can i make sure that a message which is successfully processed is not logged in the file store?
(considering container managed transactions do not require acknowledgement-mode set in the descriptor, altough i have it specified)
Find the the stack trace on the server log below:
####<Dec 10, 2008 11:45:30 AM CST> <Error> <JMS> <xlqwls01> <ACSServer1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tu
ning)'> <<WLS Kernel>> <> <> <1228931130485> <BEA-040123> <Failed to start JMS Server "SDBJMSServer1" due to weblogic.jms.common.JMSException: web
logic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery.
weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery
at weblogic.jms.backend.BackEnd.open(BackEnd.java:963)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.messaging.kernel.KernelException: Unexpected store exception in messaging kernel recovery
at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:839)
at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.store.PersistentStoreException: [Store:280020]There was an error while reading from the log file
at weblogic.store.io.file.Heap.read(Heap.java:648)
at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Error reading from file, No such file or directory, errno=2
at weblogic.store.io.file.direct.DirectIONative.read(Native Method)
at weblogic.store.io.file.direct.DirectFileChannel.read(DirectFileChannel.java:133)
at weblogic.store.io.file.StoreFile.read(StoreFile.java:281)
at weblogic.store.io.file.Heap.read(Heap.java:646)
at weblogic.store.io.file.FileStoreIO.readInternal(FileStoreIO.java:224)
at weblogic.store.io.file.FileStoreIO.access$000(FileStoreIO.java:31)
at weblogic.store.io.file.FileStoreIO$Cursor.nextInternal(FileStoreIO.java:573)
at weblogic.store.io.file.FileStoreIO$Cursor.next(FileStoreIO.java:547)
at weblogic.store.internal.PersistentStoreConnectionImpl$CursorImpl.next(PersistentStoreConnectionImpl.java:266)
at weblogic.messaging.kernel.internal.PersistenceImpl.recoverHeaders(PersistenceImpl.java:1148)
at weblogic.messaging.kernel.internal.PersistenceImpl.recover(PersistenceImpl.java:814)
at weblogic.messaging.kernel.internal.KernelImpl.open(KernelImpl.java:235)
at weblogic.jms.backend.BackEnd.open(BackEnd.java:961)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:180)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:589)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:450)
at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:430)
at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Edited by: user5823244 on Dec 14, 2008 2:59 AM

Hi,
It seems there are two problems going on here:
(1) Forceful shutdowns should not (must not) normally corrupt the file store. There may be a bug in WL, or it may be the admin is arbitrarily deleting some file store files while leaving others in place (not supported).
(2) "Even after successfully processing the message, the message which is logged in the File Store is not deleted."
This is a strong indicator that there's an application error and the message is not actually getting deleted. The file store size is proportional to the number of current messages (successfully processing/acknowledging/committing a received message frees space for new messages), and is not proportional to the number of successfully processed messages.
I think it's likely that the application isn't actually successfully processing the message but is instead receiving a message somehow and is either:
(A) throwing an exception from within an XA-or-non-XA-MDB or auto-ack-onMessage() and somehow forcing the message into a state where its not being redelivered for reprocessing
(B) specifying a transacted session and failing to call session.commit()
(C) specifying an XA transaction capable receive and failing to call commit
(D) specifying a "client acknowledge" mode and failing to call acknowledge .
For evidence, check the console statistics for the destination after "successfully processing" all sent messages: the value of "current" + "pending" should be zero once all processing completes, the value of "received (aka total)" should match the sent message count. If the "current" + "pending" value is non-zero, then this is an indication there are messages that were not successfully processed.
Tom Barnes
WebLogic Server Messaging Developer Team

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

File to IDOC

Hi,
While working with File to IDOC, How can we know what are the mandatory fields that need to mapped?
Regards
Krishna.

Hi,
I want to know the mandatory fields before I import the IDOC into XI, so that I can mention those fields in my source structure.
So, how can I know that?
Regards
Krishna.

How to handle the control records in case of file to idoc scenario.

Hi All,
can you please clarify me how to handle the control records in case of file to idoc scenario.

Hi,
In File to Idoc scenario even though you selected apply control record values from payload and you are not getting those correct values which you have provided in the mapping.
Also check the checkboxes Take sender from payload and Take receiver from payload along with the Apply control record values from payload checkbox
Regards
Seshagiri

Help needed in a file to idoc scenario

Hi all,
The scenario is file to Idoc via XI. The problem here is the input file might contain both the PO create and PO change in the same file.
Assume the first record is PO create and When we post this via XI there could be a delay for creating the PO in the SAP.
Meanwhile even if the second record (say that's the PO change for the first PO create record) gets processed parallely there could be a possibility of error saying that PO is not created.
How do we handle this in XI??.. If we use Queue Processing in IDoc adapter it'll guarantee only the delivery order and not the processing order if I'm right?.
Please guide.

Saravanan - IDoc preocessing can be handled by serialization. This will guarantee also the order of processing.
<br/>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/frameset.htm" target="n">SAP Help - IDoc serialization in XI</a>
<br/>
<br/>
Peter

JMS file to idoc

Similar Messages

Maybe you are looking for