Collect mode BPM for Flat IDoc

Hi Experts,
I am working on development of a BPM which should use flat IDocs as input collect them and then send them as output as a single file. XI is able to collect the IDocs only if they are XMLIZED. Can you please give me some idea by which i can collect flat Idocs in XI ???
If it is not possible to collect Flat IDoc in XI, can we collect all the Flat IDocs in R/3 and then send them as one IDoc to XI using ABAP code or any other method.
I am using Java mapping in my scenario.
Please guide.
Grewal.

Hi Grewal,
it is not impossible, but is is a lot of work to to.
You need as a inputstructure an element that contains the whole IDOC.
Sample Source Message Type<YourMessageType>
<root>
<IDOC_Content> //1..unbounded
</IDOC_Content> //1..unbounded
<root>
<YourMessageType>
Your target message-Type is the IDOC
Now you need a UDFs that extracts the single values out of <IDOC_Content> an map them to the target IDOC-fields. This will be a lot of work.
Regards Mario

Similar Messages

IDOCs (Multiple Types) Collection in BPM---string index out of range

Hi
I am following this weblog
IDOCs (Multiple Types) Collection in BPM
1.
In Step 4
Below mapping is for N:1 transformation. (Here input will be having three different types of Abstract IDOCs and target will be having Abstract Target File type)
(iv) MM_ISU_UKGAS_NOM_to_NOM_ABS"
when I tried to 3 idoc as sender and My Message Type as the receiver
I am getting the following error message
String index out of range: 0
so how can I do this message Mapping
2.
and in Step 3.
I have just mapped
Source Idoc 1 with Source Idoc 1
Source Idoc 2 with Source Idoc 2
Source Idoc 3 with Source Idoc 3
is it right way ?
thanks
manian
Edited by: manian on Dec 8, 2008 10:49 AM

Manian,
Multiline option should be on for receiver message .
Mapping seems to be o.k.
Regards,

Error in IDOCs (Multiple Types) Collection in BPM

Hi
I am following this scenario
IDOCs (Multiple Types) Collection in BPM
But in BPM i am getting the following error (Pls check this link)
http://www.flickr.com/photos/33169400@N05/3095091883/
where should I have to check for the errors
thanks
mainan
Edited by: manian on Dec 9, 2008 10:45 AM

The source message should be a single line container variable and the target should be a multiline container variable.
VJ

Upload Flat-IDocs via WE16 fails - where is log-file for this upload

Hi,
we are using ERP2005 and we wanna upload large Flat-IDocs (exported by a customer, > 100MB) via WE16.
Now we are getting the error "...error in converting while reading file ..." (a translation of the german error message
Is there a log file for this upload process?
regards
Wolfgang Hummel

The following Oracle Forms objects did not generate successfully: gl forms/ZHS GLXJEENT.fmxadpatch log will tell you worker which was processing this fmb.....mark that worker number.....in same directory find ad*worker_num*.log and see that log file.
You can find adworker,adpatch,adworker log at:-
Application Tier-- adpatch log - $APPL_TOP/admin/<SID>/log/
Thanks,
JD

How to print Individual mode and Collective Mode for Goods Receipt

Hi Friends,
Right now I am working on Smartforms on MIGO transaction.
My Client requirement is that all items that have been received should be printed on one form in
Collective mode.More specifically in the transaction MIGO only the items checked OK should print on
the form. It Should also allow the user to print Items in Individul mode.
Could anybody please specify on what basis( fileds ), I will be able to segregate the items.
how can I write the select stament so that when the user selects collective mode and accordingly
should print. same for individual mode.
Kindly help me.
Regards,
Xavier.P

In MIGO tcode you strcture like GOHEAD-XNAPR and GOHEAD-WEVER
if you check GOHEAD-XNAPR = X and select GOHEAD-WEVER Individual mode and Collective mode.....

BPM in an IDoc--EDI scenario

This is the BPM i have encountered with.
The parameters for the steps are :
1. Start: One Queue
1. Loop: Condition: CO_endloop value: not = true
2. Parallel: End condition; necessary branches : value: 1
3. Fork Start.
4. Receive: message: Collect message; use correlation: Correlation
5. Append : target: Collectmessagelist; operation: Append
6. loop parameter1: target:Co_endloop;expression:False
7. Wait:duration: 2mins;
8. loop parameter2: target:co_endloop;expression:True
9. Applymapping: source and target messages defined.
10. Send New message: mode:asynchcronous.
11. Stop: One queue.
The graphical definition looks like this:
.................................-> wait(15 minutes) > loop2>
Start--> loop --> Parallel(Fork).....................Parallel Fork END --> loop END --> append >send>Stop
.................................--> receive -->append --> loop1 --->
Kindly show me how this works.
Is it a good flow;Please inform if u can come up with a more reduced BPM for the said requirement.
If we have a similar kind of bpm for another interface,with another branch to add in the parallel node specifying the number or cardinality function(specifying number of idocs to be collected along with the wait condition). how can we do it ?
Please explain.
If there are any reference materials in any blogs for the same then please post in reply.

Hi Abhisek,
I just understand from your question that you are using BPM for collecting number of input msgs ( may be Idocs) for a particular time period. Please confirm.
I cant tell u the exact flow of the BPM since you have just mentioned the steps which are not very clear.
Can u just be clear what are the steps inside Parallel(Fork) block. i.e, how many branches u have and what does each branch have??
One more simpler way for collecting IDocs for a particular time is:
You can just create an infinite loop for collecting IDOCs and use a control step as a deadline handler..the deadline handler can be used to raise or throw an exception and end the infinite loop.
Since I cant add a screenshot here, I can forward a screenshot of a sample BPM to ur mail ID.
If u can explain more clearly about your BPM steps, I can try to explain you the flow.
Hope it will be helpful

Which all configurations you need to do in R/3 for an Idoc to file scenario

which all configurations you need to do in R/3 for an Idoc to file scenario?
Rgds
Ruchitha

Hi ruchitha thakur ,
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
Integration Builder
Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1
The following web-sites give u step-by-step solution to configure R/3 :
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
Step by Step Procedure of IDOC to File Scenario using BPM
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/main&
cheers!
gyanaraj
****Pls reward points if u find this useful

One file for multiple IDOCs

Hi,
Need help on IDOC files created on application server.
For IDOCs of EDI type generally one file is created on application server for one idoc. Is there any way to create a common file for multiple IDOCs that are created in a batch job?
Thanking in anticipation
Sudhir Bhate

Hi Sudhir;
Yes, it is a setting on the outbound parameters of the partner profile. In the section for "output mode," select "Collect IDocs." This link to help.sap.com describes the procedure:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b812a43d711d1893e0000e8323c4f/content.htm
Cheers,
John

BPM SA Bridge Idoc Message ID

Hi Experts
I have BPM where i receive some message. Scenerio is sync. So i BPM first i open sync to async bridge. In BPM i send idoc to ERP end after this step i do transformation with source abstract interface releted to idoc message target respode to sync request.
My purpose is to recieve message id of idoc that has been send in this BPM. in transformation i receive message id of abstract interface with naturaly has diffrent id than idoc.
Any idea ?
Regards
M.

Bhavesh,
I have reached a step further in my Mapping.
I have defined a Mapping between File1_ABS and File2_IN (get Message ID)
Second Mapping is between File2_ABS and File2_IN
for Scenario : N:2 Transformation
N IDoc collected (Receive) -> Transform(2 files) -> Send1(File1_ABS)
-> Send2(File2_ABS)
I am struck at the Scenario. How do i define Receiver Agreement, Interface determination and Receiver determination?
Kindly Advice.
Thanks,
Gowri

Improve Triggering Time for outbound IDOCs

Hi,
We have a requirement where in we have to transfer some material master data from Production system to a Testing system.
We schedule a background job for BD10 in the Production system which generates IDOCs for the material data.
Similarly, after we get this IDOC in the Testing system, we run RBDAPP01 to process the IDOCs.
Now the problem is, the IDOCs are getting generated in the Production system quickly and we can see the status of the IDOCs as 03 which means IDOCs
are sent from the production system. But it takes too long for us to see the IDOC in the testing system.
( We sent some 50000 IDOCs from Production System and after 6 hours, we can see only 20,000 IDOCs in the Testing system. )
Any idea how we can reduce this time? Is there any background program scheduled for the IDOCs to be sent from one system to another, where in we can change the frequency ?
After changing the output mode in the partner profile from TRANSFER IDOC IMME to COLLECT IDOCS , and increasing the packet size, we see some improvement.
But can it be improved further?
Any pointers to this is highly appreciated.
Regards,
Suganya

Hi,
One thing you cand do is use the Parallem Proc option of the program RBDAPP01 This way the IDocs will be processsed parallelly instead of sequentially. Take a look at the documentation of the program for parallel proc. And remember with parallel processing, large packet sizes lowers the level of parallel processing.
I hope you are specifying the the message type in the selection screen on the program RBDAPP01so that it processes only MATMAS messages.
Hope this helps
regards,
Advait

BPM for Weblogic configuration is failed

1, I install BPM for Weblogic.
2, I create a domain for weblogic using config tool and start it.
3, I create a new directory.
However, the configuration is failed.
The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
The log is as follows:
For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear, to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear, to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at weblogic.WLST.main(WLST.java:29)
Exiting WebLogic Scripting Tool.
<Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
Do you want to cancel this wizard?

Hi,
Thanks for your reply. I change the file and reconfigure the BPM for weblogic. However, it is still failed in 70-72%.
-------------------log message-------------------------------
TO_MSG PATH=/root/bea/wlserver_10.3/server/bin:/root/bea/modules/org.apache.ant_1.6.5/bin:/root/bea/jrockit_160_05/jre/bin:/root/bea/jrockit_160_05/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
TO_MSG
TO_MSG Your environment has been set.
TO_MSG
TO_MSG CLASSPATH=/root/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/jrockit_160_05/lib/tools.jar:/root/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/root/bea/wlserver_10.3/server/lib/weblogic.jar:/root/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/root/bea/wlserver_10.3/server/lib/webservices.jar:/root/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/root/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/root/OraBPMwlHome/lib/fuego.boot.jar:/root/OraBPMwlHome/bin/./:/root/OraBPMwlHome/bin/./lax.jar::/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar
TO_MSG
TO_MSG Initializing WebLogic Scripting Tool (WLST) ...
TO_MSG
TO_MSG Welcome to WebLogic Server Administration Scripting Shell
TO_MSG
TO_MSG Type help() for help on available commands
TO_MSG
TO_MSG Starting server BPMServer
TO_MSG Please see the server log files for startup messages available at /root/weblogic3/bpm
TO_MSG Starting weblogic server ...
TO_MSG WLST-WLS-1249792014056: [WARN ] -XX:MaxPermSize=256m is not a valid VM option. Ignoring
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ26￥ﾈﾆ58￧ﾧﾒ CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00￧ﾧﾒ CST> <Info> <Management> <BEA-140013> </root/weblogic3/bpm/config/config.xml not found>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00￧ﾧﾒ CST> <Info> <Management> <BEA-141254> <Generating new domain directory in /root/weblogic3/bpm>
TO_MSG .....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ12￧ﾧﾒ CST> <Info> <Management> <BEA-141255> <Domain generation completed in 12,326 milliseconds.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ13￧ﾧﾒ CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15￧ﾧﾒ CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ16￧ﾧﾒ CST> <Notice> <Log Management> <BEA-170019> <The server log file /root/weblogic3/bpm/servers/BPMServer/logs/BPMServer.log is opened. All server side log events will be written to this file.>
TO_MSG ...WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ24￧ﾧﾒ CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
TO_MSG ....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34￧ﾧﾒ CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "BPMServer" for domain "bpm" running in Development Mode>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36￧ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
TO_MSG Server started successfully.
TO_MSG Started Server. Trying to connect to the server ...
TO_MSG Connecting to t3://localhost.localdomain:7001 with userid weblogic ...
TO_MSG Successfully connected to Admin Server 'BPMServer' that belongs to domain 'bpm'.
TO_MSG
TO_MSG Warning: An insecure protocol was used to connect to the
TO_MSG server. To ensure on-the-wire security, the SSL port or
TO_MSG Admin port should be used instead.
TO_MSG
TO_MSG Location changed to edit tree. This is a writable tree with
TO_MSG DomainMBean as the root. To make changes you will need to start
TO_MSG an edit session via startEdit().
TO_MSG
TO_MSG For more help, use help(edit)
TO_MSG
TO_MSG Starting an edit session ...
TO_MSG Started edit session, please be sure to save and activate your
TO_MSG changes once you are done.
TO_MSG creating mbean of type JMSServer ...
TO_MSG creating mbean of type JMSSystemResource ...
TO_MSG creating mbean of type SubDeployment ...
TO_MSG creating mbean of type Queue ...
TO_MSG creating mbean of type Topic ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type Server ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Realm ...
TO_MSG creating mbean of type RoleMapper ...
TO_MSG creating mbean of type CredentialMapper ...
TO_MSG creating mbean of type CertPathProvider ...
TO_MSG creating mbean of type Authorizer ...
TO_MSG creating mbean of type Adjudicator ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG setting attributes for mbean type JMSServer
TO_MSG setting attributes for mbean type JMSSystemResource
TO_MSG setting attributes for mbean type SubDeployment
TO_MSG setting attributes for mbean type Queue
TO_MSG setting attributes for mbean type Topic
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type Server
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type DefaultIdentityAsserter
TO_MSG setting attributes for mbean type SecurityConfiguration
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type EmbeddedLDAP
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type Domain
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type JDBCXAParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG Saving all your changes ...
TO_MSG Saved all your changes successfully.
TO_MSG Your edit session is not stopped, you can continue your edits.
TO_MSG Activating all your changes, this may take a while ...
TO_MSG The edit lock associated with this edit session is released
TO_MSG once the activation is completed.
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute InternalAppsDeployOnDemandEnabled on weblogic.management.configuration.DomainMBeanImpl@fffe8220([bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@1759a12([bpm]/Log[bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute ListenAddress on weblogic.management.configuration.ServerMBeanImpl@2ddd7637([bpm]/Servers[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@2df105fa([bpm]/Servers[BPMServer]/Log[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.WebServerLogMBeanImpl@2df106e5([bpm]/Servers[BPMServer]/WebServer[BPMServer]/WebServerLog[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53￧ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG
TO_MSG The following non-dynamic attribute(s) have been changed on MBeans
TO_MSG that require server re-start:
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Log,Server=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Server
TO_MSG Attributes changed : ListenAddress
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Log
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Domain
TO_MSG Attributes changed : InternalAppsDeployOnDemandEnabled, ProductionModeEnabled
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=WebServerLog,Server=BPMServer,WebServer=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG Activation completed
TO_MSG Creating a user ...
TO_MSG
TO_MSG Created user successfully
TO_MSG Deploying application from /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ01￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ08￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear], to BPMServer .>
TO_MSG .................Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ29￥ﾈﾆ48￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 08-workspace-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ30￥ﾈﾆ45￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 09-feeds-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ00￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 06-workspaceadmin-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ31￧ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 07-papiws-wls103-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear], to BPMServer .>
TO_MSG ..WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48￧ﾧﾒ CST> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "weblogic.servlet.internal.WebAppServletContext@30302d0 - appName: '07-papiws-wls103-XAFDIDS.ear', name: 'papiws', context-path: '/papiws', spec-version: '2.5'" to "/root/weblogic3/bpm/servers/BPMServer/tmp/_WL_user/07-papiws-wls103-XAFDIDS.ear/f0r1c0/papiws.war".>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48￧ﾧﾒ CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249792304208' for task '5'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'papiws''
TO_MSG WLST-WLS-1249792014056: weblogic.application.ModuleException: Failed to load webapp: 'papiws'
TO_MSG WLST-WLS-1249792014056:      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: java.io.IOException: Error opening file
TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.open(Native Method)
TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:117)
TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:133)
TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
TO_MSG WLST-WLS-1249792014056:      at weblogic.application.io.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:290)
TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: >
TO_MSG WLST-WLS-1249792014056: java.io.FileNotFoundException: /root/weblogic3/bpm/config/config.xml (Too many open files)
TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.open(Native Method)
TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.Fil

What are the settings for datasource and infopackage for flat file loading

hI
Im trying to load the data from flat file to DSO . can anyone tel me what are the settings for datasource and infopackage for flat file loading .
pls let me know
regards
kumar

Loading of transaction data in BI 7.0:step by step guide on how to load data from a flatfile into the BI 7 system
Uploading of Transaction data
Log on to your SAP
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( Transaction data )
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to create ODS( Data store object ) or Cube.
Specify name fro the ODS or cube and click create
From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
Click Activate.
Right click on ODS or Cube and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used.
Loading of master data in BI 7.0:
For Uploading of master data in BI 7.0
Log on to your SAP
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( master data attributes, text, hierarchies)
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to select Insert Characteristics as info provider
Select required info object ( Ex : Employee ID)
Under that info object select attributes
Right click on attributes and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.

How to Configure logical path and how to retrieve physical path for an IDOC

Hi ,
I want to configure logical path for an IDOC,
and then I need to retrieve Physical path from this logical path
using a FM (eg. FILE_GET_NAME).
How to configure the logical path for an idoc ?
Regards ,
Harshit Rungta

Using Logical Files in ABAP Programs
To create a physical file name from a logical file name in your ABAP programs, use the function module FILE_GET_NAME. To insert the function module call in your program, choose Edit ® Insert statement from the ABAP Editor screen. A dialog box appears. Select Call Function and enter FILE_GET_NAME. The parameters of this function module are listed below.
Import parameters
Parameters
Function
CLIENT
The maintenance tables for the logical files and paths are client-dependent. Therefore, the desired client can be imported. The current client is stored in the system field SY-MANDT.
LOGICAL_FILENAME
Enter the logical file name in upper case letters that you want to convert.
OPERATING_SYSTEM
You can import any operating system that is contained in the list in Transaction SF04 (see Assigning Operating Systems to Syntax Groups). The physical file name will be created according to the syntax group to which the operating system is linked. The default parameter is the value of the system field
SY-OPSYS.
PARAMETER_1
PARAMETER_2
If you specify these import parameters, the reserved words in the physical path names will be replaced by the imported values.
USE_PRESENTATION
_SERVER
With this flag you can decide whether to import the operating system of the presentation server instead of the operating system imported by the parameter OPERATING_SYSTEM.
WITH_FILE_EXTENSION
If you set this flag unequal to SPACE, the file format defined for the logical file name is appended to the physical file name.
Export Parameters
Parameters
Function
EMERGENCY_FLAG
If this parameter is unequal to SPACE, no physical name is defined in the logical path. An emergency physical name was created from table FILENAME and profile parameter DIR_GLOBAL.
FILE_FORMAT
This parameter is the file format defined for the logical file name. You can use this parameter, for example, to decide in which mode the file should be opened.
FILE_NAME
This parameter is the physical file name that you can use with the ABAP statements for working with files.
Exception Parameters
Parameters
Function
FILE_NOT_FOUND
This exception is raised if the logical file is not defined.
OTHERS
This exception is raised if other errors occur.
Suppose the logical file MYTEMP and the logical path TMP_SUB are defined as in the preceding topics and we have the following program:
DATA: FLAG,
      FORMAT(3),
      FNAME(60).
WRITE SY-OPSYS.
CALL FUNCTION 'FILE_GET_NAME'
     EXPORTING
          LOGICAL_FILENAME        = 'MYTEMP'
          OPERATING_SYSTEM        = SY-OPSYS
          PARAMETER_1             = '01'
     IMPORTING
          EMERGENCY_FLAG          = FLAG
          FILE_FORMAT             = FORMAT
          FILE_NAME               = FNAME
     EXCEPTIONS
          FILE_NOT_FOUND          = 1
          OTHERS                  = 2.
IF SY-SUBRC = 0.
WRITE: / 'Flag      :', FLAG,
         / 'Format    :', FORMAT,
         / 'Phys. Name:', FNAME.
ENDIF.
The output appears as follows:
HP-UX
FLAG :
FORMAT : BIN
Phys. Name: /tmp/TEST01
In this example, the R/3 System is running under the operating system HP-UX, which is member of the syntax group UNIX. The logical file name MYTEMP with the logical path TMP_SUB is converted into a physical file name /tmp/TEST01 as defined for the syntax group UNIX. The field FNAME can be used in the further flow of the program to work with file TEST01 in directory /tmp.
Suppose we have a logical file name EMPTY with the physical file name TEST, connected to a logical path that has no specification of a physical path. If you replace the EXPORTING parameter 'MYTEMP' with 'EMPTY' in the above example, the output appears as follows:
HP-UX
FLAG : X
FORMAT :
Phys. Name: /usr/sap/S11/SYS/global/TEST
The system created an emergency file name, whose path depends on the installation of the current R/3 System.

How IE works for flat file

Hi all:
As we all know that, when IE gets a idoc's service name from SLD, then use it with idoc's message type and Idoc type to do receiver determniation, what about flat file ? how can we know its Service name and interface name if there is only a flat file on FTP? how IE works for Flat file ?
Couldn't thank you more

Hi,
For any idoc scenarious, you would use business systems rather than business service which is stored in SLD. So the IE would fetch it from SLD at runtime.
For file based scenarious also, you can create business system as type third party and use the same.
Is that answer your question?
Regards
Krish

Get IDoc-number from flat IDoc using dynamic configuration

Dear experts
In an IDoc2File scenario I have added the IDoc-number to dynamic configuration using the folling code in an UDF:
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","DOCNUM");
conf.put(FileName, a);
The information is stored in the SOAP message
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="DOCNUM">0000000000012345</SAP:Record>
</SAP:DynamicConfiguration>
Can anybody tell me how I can access this information in the "variable substitution" section of the CC? Perhaps something like "message:docnum"?
Additional information:
Taking the IDoc-number from the payload using e.g. "payload:ORDERS05,1,IDOC,1,EDI_DC40,1,DOCNUM,1" does not work, since the XML-IDoc has been converted to an flat-IDoc.
Thanks in advance for any good ideas
Markus

Dear Rodrigo and Sarvesh
Thanks for your help so far! I applied your hints and now it is working fine.
But now I have the following additional questions
1.) My message mapping only maps the input IDoc to an output IDoc of the same type and structure. The MM is only required to process the UDF. Is there another, better solution to achieve my requirement that the IDoc-number shall be part of the filename?
2.) In the CC you have the possibility to use temporary files (section "Processing", Option "Put File" = "Use Temporary File". I think this will not work with the given solution, will it?
To possibly help somebody else or clarify the mechanism once again, I wrote down how my solution now looks like.
My UDF in the message-mapping looks like this
- Input = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- Outpt = DOCNUM of IDoc, e.g. ORDERS05/IDOC/EDIDC/DOCNUM
- UDF:
public String putDynamicConfiguration(String docnum, Container container) throws StreamTransformationException{
try
     DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
     DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
     String filename = "Prefix_" + docnum + ".txt";
     conf.put(key, filename);
     return docnum;
catch (Exception e)
     return docnum;
In the CC the settings are now as follows
File Name Scheme = . -> only a dot or something else, because this field is obligatory, even if it is not used in this case.
Variable substitution (...)
    Enable -> unchecked
Adapter-Specific Message Attributes
    Use Adapter-Specific Message Attributes -> checked
    Fail If Adapter-Specific Message Attributes Missing -> checked
    File Name -> checked
    Directory, File Type, Temporary Name Scheme for Target File Name -> unchecked
When I send an IDoc to PI and view the Adapte-Engine Version of the message (the SOAP-document, not the payload) I can find the Filename:
<SAP:DynamicConfiguration SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">Prefix_0000000000012345.txt</SAP:Record>
</SAP:DynamicConfiguration>

Collect mode BPM for Flat IDoc

Similar Messages

Maybe you are looking for