Issue in Data transfers using ALE for E-Recruiting standalone system

Dear Experts,
We have an issue in data transfers using ALE. We are having standalone system where E-Recruiting is maintaind seperately and the version is EHP5.
When we configured iDoc in Sandbox and its working fine. But when it comes to Dev and Quality servers this is not working fine.
we have created iDocs using the following filters.
For Object P: Infotypes 0000, 0001, 0002, 0003, 0006, 0024, 0105.
For Objects O,S: 1032, Subtype: 0010
For Object: 1001, Subtype: A003, A008, A012, B007
For Object O: 1001, Subtype: A002, B002, B003, B012, Tyoe of related object: O,S
For Objects: C, O, S, Subtype: 1000, 1002, 1028
For Object:C, Subtype: 1001, Subtype: A007
When we do the data transfers in Sandbox using PFAL it is transferring the data properly.
But when we do the same iin Dev and Quality servers we are not able to do it and gettign 52, 51 errors.
Here we are facing a strange issue. For some Users when we transfer data it is transferring data but with 52 error messgae.
For some users I am getting 51 error where i could not transfer any data.
For some users, when we tranfer O, S, and P related data is moving but getting mostly 52 error and all the relationships are not moving here for O,S and properly. But P related CP, BP and NA are getting created successfully.
It is happening only in Dev and Quality server and that too some users are able to get transferred but not all.
Where will be the issue? How can we resolve this?
Any help will be appreciable.
Thank you in advance.

Hi Sekhar,
Have a look over these threads.
Errors in ALE data transfer to E-Recruiting.
http://scn.sap.com/thread/1535402
BR,
RAM.

Similar Messages

Slow data transfere using card reader for PE8 on Win7 machine

I just migrated (reinstall) my PE8 on a new PC (from old WINXP SP2 to a high end WIN7 64 bit) .
I have a ordinary card reader (USB 2.0) for my SD,SDHC, and XD cards.
Everything works excellent on the new machine except for the data transfere rate. When collecting pictures, or videos for that matter, with PE8 Organizer. What takes minutes in my old XP machine takes hours (hours for real) in the new machine.
Since PE8 is a 32 bit app I have also tried on the new machine to change the compatibility for C:\Program Files (x86)\Adobe\Elements Organize\PhotoDownloader.exe. I tested with running PhotoDownloader.exe just as on the old box winXP SP2 and SP3. But it made no difference.
I also looked in performance monitor. Nothing of interest. I had lots and lots of power left.
So..
Now I'm stuck. Both on the problem cause search. Or finding a solution. Anyone got any good ideas to make progress.

My main overall objective is to look at the pictures and films. Not work with them as a hobby as such. (even if it is quite fun, but very time consuming. And time I do not have)
0. The vast majority of files are .mts and .jpg
1. Step one is to get them into PE8 organizer.
2. Batch organizing jobs like renaming, tagging, minor quick enanhcement etc
3. Some hands on changes or add ons like back ground musik.
in short
¬ 70 % are trivial at level. Using mainly the Auto stuff. Want to being in control picturens and films and making them more viewable by removing junk and pain just adding minor enhancement.
¬ 25 % at low-medium level
¬ 5 % at medium level
I hope this answer your question. My question is, do you have any idea how to solve the issue?

Anyone else having an issue with TCP connections using iCloud for Windows?

Hi,
Before I asked this question, I did wait to see if any related questions came up, but none did, so I submit it now.
On my admittedly older laptop running Windows 7 64b Home, I've run into difficulties with the iCloud for Windows app to the extent that I had to uninstall it.
It would that, as my laptop was running, in the background, iCloudServices.exe would endlessly iterate TCP connections, which, while not actively sending or receiving any data, after some hours would number over 100 instances, taking up resources, and grinding my laptop's WiFi connection to a grindingly slow pace. I ended up, within the app, turning off everything, iCloud Drive and Photos, (I never used bookmarks), but still this would continue to occur.
I contacted Apple Support, explaining what was going on, and they stated they only dealt with IOS and gave me a Microsoft Support number. When I called Microsoft support, I came more and more to the realization that the issue was specifically with the iCloud for Windows app, as that was the only software that was endlessly creating and not closing TCP connections as it was. How was Microsoft supposed to solve an issue with Apple code?
So I called Apple back, whereupon they insisted it was a Microsoft issue. I explained other cloud services installed on the same computer were not having the same issue, it was unique to ICloudServices.exe. They stated they only dealt with IOS. I stated I purchased an iPad Air less than 7 months ago, and was trying to run iCloud in support of that. They again stated they only dealt with IOS, and suggested I again try Microsoft. I asked them if it was reasonable to expect Microsoft to solve issues with Apple code? They said regardless, there was zero support offered for anything having to do with Windows, and all I could do was uninstall the app, which I did, though that did not feel very satisfactory to me. My thinking is, if Apple writes a Windows app in support of their hardware, they should offer support for it.
Anyway, I was just wondering, is this an issue unique to me? or have others experienced a similar issue? I found this issue by opening the Windows Resource Monitor, looking under the Networking tab, and scrolling through the TCP Connections section to find 100+ concurrent iCloudServices.exe instances listed, whereas even Chrome, with multiple tabs and extensions, topped out at around 20.
My one month old Desktop, DYI, sports a solid Asus 1150 MoBo, i7-4790k cpu, 16GB Ram, and an EVGA GTX 970 video card. I list some specs only to illustrate this computer has no hardware issues in comparison to my long in tooth laptop. On this desktop, running Win 8.1 Pro 64b, at least as many, identifiably Apple, background service TCP connections are created even compared to Chrome, regardless of many tabs being open, many extensions, and even some related apps. Adobe does not even come close, though I run the full CC subscription. On this new computer, running Windows 8.1 Pro 64b, there are currently over 50 TCP connections and loopbacks that do not identify themselves, with just a - for the Image, and PID. With the experience on my laptop, I wonder how many of these are generated by Apple software, if not specifically iCloud software?
The frustrating aspect of these connections is they seem in no way active, While the Chrome and Adobe connections can be seen to be transferring data, as long as I am not running iTunes, or so have my iPad actually plugged in, it seems 99% of the time these iCloudServices.exe connections are just taking up ports, neither sending nor receiving any data discernable to me under the Processes with Network Activity, or Network Activity lists, both displayed in the same window as the TCP Connections in the Windows Resource Monitor.
Though I am fairly ignorant as regards coding, it seems as if there is no call to close a connection, very specifically, iCloudServices.exe, when it is no longer needed, and the next time a connection is needed, a new one is opened, rather than accessing the one previously opened. The only other reason I could imagine this might be occurring is if my Norton Internet Security software might mask and/or block the port after a certain time of inactivity.
Anyone out there have any ideas or advice about this? Thanks in advance.

Thanks jared,
I'm still dealing with this issue through Apple. Some time after I posted this, I contacted Apple again. They did start a case up for me, as I was experiencing the same behavior on two different machines, with two different versions of Windows.
So far it remains unsolved. I've logged iClouds for Windows on my desktop, which is brand new, then logged for awhile after completely uninstalling Norton Security Suite, depending on the Microsoft security for some time, and finally logged after I uninstalled iCloud for Windows, restarted, installed a clean download, and connected using a completely different test account, which Apple set up for me. None of this made any difference. Looking at the logs, it seems every 10 minutes, iCloudServices.exe creates a new TCP connection to confirm I'm using less than 5GB on iCloud, (which I am by a good margin, using less than 2GB), it seems this connection is not closed, and when the next iteration rolls around 10 minutes later, a new TCP connection is created. I come very close to having 6 TCP connections created per hour, until I restart my computer. This works out to... 6 x 24 = 144/day.
Perhaps the article you posted will shed some further light on this. I'm thinking seeing the state of the connection through netstats, at the least, could help.
For the last week, I've been putting a hold on further logging, as Apple wants me to create a new user account on one of my computers, install iCloud for Windows there, and log it running in the other account. This however basically means I cannot use my computer for a fair number of hours, and I've been busy enough with work the past week that I haven't the time or energy to afford to set this up and run it. I've had need of my computers too much for the past week.

Data transfer using ALE/IDOC into XML.

Dear All,
I have to transfer FI document data (FB01) from the sap system ,convert it into XML and dump it in 1 of the file servers.I want to do this using ALE/IDOC.Is it possible to do the same and how.Similarly i want to do the same for Vendor and Customer master i.e sending the data in XML format.
Kindly Suggest how do i go about doin the same..Its very urgent.Please help.
Thanks & Regards,
Lailu Philip.

In continuation:
Example Purchasing & Selling scenario
We will develop a custom IDoc to carry the billing number from the Service Receivers system to the Service Providers system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
Requirements
Working ALE environment - See ALE Basis Configuration Guide;
ALE scenario design together with the business requirement;
Development access; and
ALE configuration access.
NOTES:
1. All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
2. This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
3. Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
2. OUTBOUND PROCESSING
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
We will create the IDoc of the following structure:
ZINVRV01
Purchasing and Selling - Invoice receipt reversal
Z1INVRV P&S - Segment 1
Segment fields
LIFNR Vendor account number
XBLNR Reference document number
Figure 3: IDoc type ZINVRV01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
2.4.1. Example code
The code displayed below does the following:
populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
populates the control record info with the message type and IDoc type; and
calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
Data declaration statements
DATA: C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
Z1INVRV LIKE Z1INVRV,
C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
IDOC_CONTROL LIKE EDIDC,
T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR. Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR. Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME. Segment name
IDOC_DATA-SDATA = Z1INVRV. Segment data
APPEND IDOC_DATA. Populate IDoc internal table
Move the control data info required for the distribution
IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
Call the distribute function with the required parameters
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = IDOC_CONTROL
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_CONTROL
MASTER_IDOC_DATA = IDOC_DATA
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
Figure 4: Outbound processing example code
NOTE:
For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
3. INBOUND PROCESSING
3.1. Create Function Module
This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
Example parameters
Import parameters Reference field Opt Y/N
INPUT_METHOD BDWFAP_PAR-INPUTMETHD N
MASS_PROCESSING BDWFAP_PAR-MASS_PROC N
Export Parameters Reference field Opt Y/N
WORKFLOW_RESULT BDWFAP_PAR-RESULT N
APPLICATION_VARIABLE BDWFAP_PAR-APPL_VAR N
IN_UPDATE_TASK BDWFAP_PAR-UPDATETASK N
CALL_TRANSACTION_DONE BDWFAP_PAR-CALLTRANS N
Table Parameters Reference field Optional Y/N
IDOC_CONTRL EDIDC
IDOC_DATA EDIDD
IDOC_STATUS BDIDOCSTAT
RETURN_VARIABLES BDWFRETVAR
SERIALIZATION_INFO BDI_SER
Exceptions
WRONG_FUNCTION_CALLED
Example code
The code displayed below does the following:
populates a BDC table with the IDoc info;
calls the transaction via a BDC call; and
updates the IDoc status according to the BDC error status.
EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
Declaration of local variables
DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
*-Loop through the IDOCs
LOOP AT IDOC_CONTRL.
*---Loop through the data for the IDOC
LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
CASE IDOC_DATA-SEGNAM.
WHEN C_SEGNAM.
Here we get the info from the idoc table
IT_Z1INVRV = IDOC_DATA-SDATA.
ENDCASE.
PERFORM REV_INV.
ENDLOOP.
PERFORM UPDATE_IDOC_STATUS.
ENDLOOP.
FORM REV_INV "Reverse invoice form
Local variables & constants
DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'. "BDC transaction code
Now we can build the bdc table to call the reversal transaction start of screen 109
CLEAR BDC_TAB.
BDC_TAB-PROGRAM = 'SAPMV60A'.
BDC_TAB-DYNPRO = '109'.
BDC_TAB-DYNBEGIN = 'X'.
APPEND BDC_TAB.
Document number
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
BDC_TAB-FVAL = IT_Z1INVRV-XBLNR. "Billing document number
APPEND BDC_TAB.
OK Code for screen 109
CLEAR BDC_TAB.
BDC_TAB-FNAM = 'BDC_OKCODE'.
BDC_TAB-FVAL = 'SICH'.
APPEND BDC_TAB.
Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale. The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
Store the return code for use in another form (status update)
RETURN_CODE = SY-SUBRC.
Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
IF SY-SUBRC NE 0.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = 'ZINVRV'
USER = C_ALE_USER
KEEP = 'X'.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = C_TCODE
TABLES
DYNPROTAB = BDC_TAB.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
ELSE. "No problems
C_EXISTS = 'N'.
Select from the billing document table to get sales doc number
SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
Select from the sales document table to get user status number
SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
POSNR = VBRP-AUPOS.
Select from the status table to change the user status to pending
SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
STAT LIKE C_USER_STATUS.
IF JEST-STAT = C_US_PENDING. "User status is pending
JEST-INACT = C_UNCHECKED. "Make pending the active status
UPDATE JEST.
C_EXISTS = 'Y'. "I.E. An entry is already in table
ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
JEST-INACT = C_CHECKED. "Make everything else inactive
UPDATE JEST.
ENDIF.
ENDSELECT.
IF C_EXISTS = 'N'. "I.E. Pending has never been a status before
JEST-OBJNR = VBAP-OBJNR.
JEST-STAT = C_US_PENDING.
JEST-INACT = C_UNCHECKED. "Make pending the active status
INSERT JEST.
ENDIF.
ENDSELECT. "Select from VBRP (Billing document table)
ENDIF.
ENDFORM. " REV_INV
FORM UPDATE_IDOC_STATUS.
Now we check the CALL TRANSACTION return code and set IDOC status
CLEAR IDOC_STATUS.
IF RETURN_CODE = 0.
WORKFLOW_RESULT = '0'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '53'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ELSE.
WORKFLOW_RESULT = '99999'.
IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
IDOC_STATUS-STATUS = '51'.
IDOC_STATUS-UNAME = SY-UNAME.
IDOC_STATUS-REPID = SY-REPID.
IDOC_STATUS-MSGTY = SY-MSGTY.
IDOC_STATUS-MSGID = SY-MSGID.
IDOC_STATUS-MSGNO = SY-MSGNO.
IDOC_STATUS-MSGV1 = SY-MSGV1.
IDOC_STATUS-MSGV2 = SY-MSGV2.
IDOC_STATUS-MSGV3 = SY-MSGV3.
IDOC_STATUS-MSGV4 = SY-MSGV4.
RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.
RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
APPEND RETURN_VARIABLES.
ENDIF.
APPEND IDOC_STATUS.
ENDFORM. " UPDATE_IDOC_STATUS
Figure 5: Inbound processing example code
3.1.1. Debugging inbound FM
Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
3.2. Maintain ALE attributes
The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
3.2.1. Link Message Type to Function Module (WE57) Client independent
To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
Select an entry (EG. IDOC_INPUT_ORDERS) and copy
Type in module name Z_IDOC_INPUT_ZINVRV
Type in basic IDoc type as ZINVRV01
Type in message type as ZINVRV
Type object type as IDOCINVOIC (Invoice document) - Used for workflow
Direction should be set to 2 for inbound
Enter and save
3.2.2. Define FM settings (BD51) Client independent
Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
Click on New entries
Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
Enter 0 for mass processing in the output column
Save and Exit
3.2.3. Maintain process codes (WE42) Client dependent
A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
To maintain the process code follow these steps:
Log on to the appropriate receiving system client
Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
Choose Inbound with ALE service
Choose Processing with function module
Click on Processing with function module and choose create icon
Click on New Entries
Type in process code ZINR and give it a description and save
Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
Enter your process code ZINR
Enter your function module Z_IDOC_INPUT_ZINVRV
NOTE: The next 6 steps are used in workflow error handling.
Enter IDPKFIDCMT in object type
Enter MASSINPUTFINISHED in End event
Enter IDOCINVOIC in IDoc object type
Enter INPUTERROROCCURREDFI in IDoc start event
Enter INPUTFINISHEDFI in IDoc End event
Enter IDOCINVOIC in Application object type
You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
To set up the workflow area please consult the Workflow config guide.
3.3. Create inbound partner profile
For each message type you need to maintain the inbound partner profiles.
3.3.1. Maintain receiving system partner profile (WE20) Client dependent
To maintain inbound partner profiles read the document ALE configuration procedure:
Add the message type ZINVRV with process code ZINR.
Enter the output mode (background, immediately) for inbound processing and NO message code.
Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
3.4. Test
Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.
Hope this will help you,
If you want me to explain more, you can give me your email id.
Reward with points incase you are satisfied.
Regards,
Sushama

Queries with date functions using PreparedStatement for multiple DB

I am developing application that uses DB independant queries. I am using preparedstatement to process the queries. I need to use date functions for query selection criteria.
for eg.
selecting the list of employees who had joined in the last 15 days
selecting list of employees who had joined between two dates etc.
where Date Joined field is a Timestamp value. To extract date no DB specific function can be used.
If I use setMonth, setYear etc.. to set params in the pstmt the query becomes complex in the above case. Can any one throw some light on how to do the above in preparedstatement or any other better alternative.
Tx a lot

Hi,
I did not mean that way. I presume that there is a timestamp value (may be a date too) column in the table. Then based upon your requirement (say before 15 days) pass the value as date (or time stamp) in the query as a parameter.
String qry = "select * from myTable where join_date <= ?";
stmt.setDate(1,myDate); // this is where you will have to manipulate the value to suit your DB timestamp or date value; you will have compatibility issues with util.Date and sql.Date so use Calendar class to satisfy.Feel free to mail me if you need further clarifications to [email protected]
Cheers,
Sekar

How to transfer the transactional dat a using ale

hi to all abap gurus
i heard that we can transfer the transactional data ( like so data , po data ) using message control technique by ale technology . . can u please give all steps in message control technique with one exapmle . i searched in the forum but i did not get answer . pls points will be rewrared for good answers. if u want to give links pls give exact links .

Hi ,
here is the configuration.
MESSAGE CONTROL (USING EDI / ALE)
For Purchase order (Message control using EDI and message type ORDERS) STEPS
Settings to be done in the Sending system
From NACE
Choose Application EF ( Purchase order), press on condition record
Output type NEU Purchase order / double click ;choose Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11) execute. Key in the data (vendor vendor11, name name1, partner function - VN, Partner Vendor11,Medium 6 (EDI), time 4(send immediately), language EN).
Press on output types , choose NEU Purchase order, double click, Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time send immediately, Transmission medium EDI, Partner function VN)
Create RFC destination from SM59 (ZNARA_ALE_EDI).
Create a port from ZNARA_ALE.
Create partner profile vendor11 under LI and not LS. PARTNER NUMBER SHOULD BE SAME AS THAT OF VENDOR SET IN THE CONDITION TYPE.
In the outbond parameters of the partner profile Vendor11 key in the data (Reciever port -> ZNARA_ALE,
Basic type ORDERS05, Message type ORDERS ) Go to the message control and key in the data (Application EF, Message type NEU, Process code ME10, Transfer immediately )
Create a purchase order from ME21 with data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11). System will generate an outbond Idoc automatically which can be seen from WE02.
For Purchase order (Message control using ALE and Message type ORDERS) - STEPS
To transfer the idoc from Client 555 to 500
Settings do be done in 555.
From NACE
Choose Application EF Purchase order, press on condition record
Output type NEU Purchase order / double click ;choose Purchasing output determination:Doc type/purc org/vendor . Key in the data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11) execute. Key in the data (vendor vendor11, name name1, partner function - VN, Partner Vendor11,Medium A (ALE), time 4(send immediately), language EN).
Press on output types , choose NEU Purchase order, double click, Access sequence 0001(doctype/purcorg/vendor) tick mark the access to condition, go to default values (dispatch time send immediately, Transmission medium ALE, Partner function VN)
From SALE create two logical systems and assign them to the respective clients (ZALERECV_N 500, ZALESEND_N 555).
From SM59 create RFC destination with the same name as that of the receiving logical system (ZALERECV_N).
From BD 64(distribution model), create a model view with Technical name ZNARA_PO (message type ORDERS, Sender ZALESEND_N, Receiver ZALERECV_N). Generate partner profiles. Distribute.
Note that partner profile will be generated under LS.
Settings do be done in 500.
From NACE create two logical systems and assign them to the respective clients (ZALERECV_N 500, ZALESEND_N 555).
From BD 64(distribution model), keep the cursor on Technical name ZNARA_PO. Generate partner profiles. Note that partner profile will be generated under LS. Change the process code to ORDE in the inbond parameters .
Now in client 555, Create a purchase order from ME21 with data (Purchasing doc type NB, Purc organisation 0001, Venor vendor11). System will generate an outbond Idoc automatically which can be seen from WE02. The purchase order details will be updated in 555 thru the inbond idoc.
IMP data for message control in Sales order creation.
Partner profile to be created under KU.
Outbond parameters in the partner profile (Message type ORDRSP, Basic type ORDERS02, partner profile - SP) In Message control (Application V1, Message type BA00, Process code SD10)
Notes:
Check the entries in the NAST table to see whether outbond idoc has been created successfully or not
If you have choosen collect idocs in the partner profile, use trans code BD87 to process them
Table EDP13 - Partner Profile: Outbound (technical parameters)
Table EDP21 - Partner Profile: Inbond (technical parameters)
Please reward if useful.

HT3625 I don't have a "Use audio for:" menu in my system preferences

When I go to system preferences and try to follow all of the directions in the article, there isn't any menu or anything that says "Use audio for:" when I'm on the input tab of the sound preferences. How can I get my MBP use the audio input instead of detecting it as an audio output?

malcolm007,
Here is a pin description of the 4 pin connector, there impedence and shunting that needs to be taken into consideration, not to mention the response curve that this is optomized for,ie:headset mic response. There could be potential damaged cause by incorrect matching and shunting (shorting certain pins to ground) you might consider calling Apple and see what their response is. You can even try experimenting at your own risk, I myself can make no recomendation and would advise against it as you could risk damaging your device. I found no data that would allow an informed decision on my part. The audio quality would most likely be sub par for a music type of application anyways, as it is most likey optomized for the headset mic as prviously mentioned.
USB interfaces are cheap and most sound good and will definatly provide a safe and flexible way to get in.
IMHO
http://www.speechrecsolutions.com/assets/iPad_and_microphones.pdf

Amount of data transferred using PXI

Hi,
I'm new to XI, anyone can advise how to check amount of data has been transfered in the XI server?
Regards
CL

If you want to monitor the time taken for a data which is being send or recieved in PI server,use Performance monitoring tool in PI.

Data not updating in table ,data transfered using DTW

Hi Everybody,
I had transfered data using DTW, it shows that data imported,but it not updated, that means it not shows in database.
So please so me any solution to this.
Regards,
Srinivas

Hi suda,
I am giving he detailes of the BusinessObject
BusinessObject =oUserLanguages
template=oUserLanguages.csv
i had copied the oUserLanguage.csv file and entered data into it and saved it(comma deliminated)
steps:
1.i had selected oUserlanguage object from list.
2.i had selected source file (oUserLanguage.csv )
3.the data properly matched and data is displayed when source tab is pressed. and ields are properly matched.
4.three check boxes are checked.
5.i had seen the message you are sucessfully specified required information for imporing data
6.in lost step it shows like below
Total: 2 business object(s)
2 business object(s) imported successfully
0 business object(s) not imported
0 business object(s) updated successfully
0 business object(s) not updated
7.in log files status shows succeeded
But I had cheked the languages , the data imported not shown.
Regards
srinivas

Data Transfer Using ALE/IDOC

Dear All,
          I have to implement an ALE\IDOC scenario and i am totally new to this.I have a web based software from where i need to pull data into SAP.
           The moment billing takes place in my web based software i have to pull the required data and generate an accounting document number in SAP using transactions FB01 er FB60 and FB70 depending on vendor or customer Invoice which means i need to have my vendor and customer master data in place before this.The IDOC which i would be using is FIDCCP01.My question is:
The web based software can generate both an XML and EDI file into a domain from where SAP can fetch it. Now,
1. If they can generate an EDI file which format should it be in?
2.If EDI file generation is possible through that web based software its structure should be exactly the same as my IDOC structure right?
3. What would then be the process on SAP side to pick that   EDI file data?
4. Does the transaction WE16 help in picking up an XML file format or an EDI format and convert it automatically into an IDOC and how do we go about it?
5. Now when this idoc is going to generate accounting documents against those billing documents if the customer or vendor does not exist is there a way by which i can first create this vendor\customer in the master and then continue using some other abap tool?
6. Could an email be generated automatically when teh document is posted?
I know these are a lot of questions but i really need an answer to this.
If u have an answer my alternate email id is [email protected]
Awaiting your reply shortly.
Thanks & Regards,
Lailu Philip.

1. XML Format
2. Message type INVOIC01 or INVOIC02 format
3. You need to write a Z program to read data from that path and use FM IDOC_XML_FROM_FILE to convert that XML file to IDOC.
4. Use transaction we60 with above message type it will all help you need. we16 is for testing it could not be used for a solution.
5. In your Z program check before the XML is ubmitted for processing whether the customer exist by select on KNA1 if not use FM BAPI_CUSTOMER_CREATE to create and same for vendor.
6. You need to implement workflow for this.....
Reward points it this helps

Format Date TextField using Locale for international apps

Hello there...
I am developing an application and I want it to be easily converted to different languages.
In Brazil, we use the date like dd/MM/yyyy. In the USA, it is MM/dd/yyyy.
My question is: how can I get the text from a text field and convert it to a Calendar using a Locale (or the default Locale)? I don't want something like
SimpleDateFormat formatter = new SimpleDateFormat("dd/MM/yyyy");
I would like something like:
SimpleDateFormat formatter = new SimpleDateFormat(locale);
The constructor SimpleDateFormat () without arguments says it builds the parser based on the Locale, but I get a ParseException. I must always specify some parse mask.
The second issue is the deprecation of a lot of things in java.util.Date. So, I would like to use a Calendar object to store the date, and without the warnings I get when I use date.getMonth() for example.
My code is something like this:
String text = dateField.getText();
SimpleDateFormat formatter = new SimpleDateFormat("dd/MM/yyyy");
Date date = null;
try {
date = formatter.parse(text);
} catch (ParseException ex) {
ex.printStackTrace();
Calendar calendar = null;
if (data != null) {
calendar = new GregorianCalendar();
calendar.set(Calendar.DAY_OF_MONTH, date.getDate());
calendar.set(Calendar.MONTH, date.getMonth());
calendar.set(Calendar.YEAR, date.getYear());
Thanks for helping!
(Sorry the not so good english :) )

My question is: how can I get the text from a text
field and convert it to a Calendar using a Locale (or
the default Locale)? I don't want something like Have you tried DateFormat.getDateInstance(int style, Locale aLocale)?
And then is your second question just how to go from a parsed date to a Calendar?
Calendar calendar = new GregorianCalendar():
if (date != null)
calendar.setTime(date);

Anyone having issues with data when using iphone 4 on straight talk?

ok. so i have a straight talk micro sim card purchased for installing in an iphone 4. i have found ways to get the data and mms to work perfectly using a method i found on sinfuliphone.com without jailbreaking. its been working great for last couple months. now my data is not working at all but i can still do mms msgs. was wondering if anyone else had this issue and any suggestions.

Since Straight Talk customer service was no help at all by telling me to call apple instead of trying to help me, this is what I did to fix the issue! I am not saying it will work for you but it worked for me so what do you have to lose! First of all, I have a At&t iphone!
The first thing I did was remove the Straight Talk APN Profile that was installed or remove any one there! Because of what I read in the Straight Talk website which was:::
For iPhone customers who activated using anAT&T compatible SIM card, there is NO need to program APN settings as this will be done automatically.
Ok, here is what I did after that: First I removed the SIM card from the phone, then I rebooted the phone, then I reset network settings, then put the SIM card back in and BAM, I had 3G once again!
Please keep in mind I am no expert, It was just by chance that this worked for me! And all of this with no APN Profile what so ever! Good Luck,,,,Dano

Issues with Motion in Using Compressor for a PAL DVD

I am new to DVD Studio Pro and Compressor and am trying to create a DVD of a 50 minute PAL project that I made using FCP. I have found a couple tutorials on how to export my project using compressor to be compatible with DSP via pre sets (DVD: Best Quality 4:3) and actually manipulating the controls myself. I have found in using both techniques that during any scene with motion, the edges of the moving actor become blurred and grainy. The tutorials that I checked out I assume (since they were from the US) were for NTSC projects, is there any other considerations that I should make in compressing a PAL project, which might contribute to this graininess? Any ideas?
Any help would be much appreciated. I have included my settings from Compressor below.
Thanks.
Name: MPEG-2 6.2Mbps 2-pass 4:3
Description: Fits up to 90 minutes of video with Dolby Digital audio at 192 Kbps or 60 minutes with AIFF audio on a DVD-5
File Extension: m2v
Estimated file size: 273.48 MB
Type: MPEG-2 video elementary stream
Video Encoder
Format: M2V
Width: 720
Height: 576
Pixel aspect ratio: PAL CCIR 601
Crop: None
Frame rate: 25
Frame Controls: Off
Aspect ratio: 4:3
Field dominance: Bottom first
Average data rate: 6.2 (Mbps)
2 Pass VBR enabled
Maximum data rate: 7.7 (Mbps)
High quality
Best motion estimation
Closed GOP Size: 12, Structure: IBBP
DVD Studio Pro meta-data enabled

The general concepts are the same in terms of maintaining quality throughout the work process in terms of Codecs, exports etc.
As to the motion areas, compression markers in FCP can help in problem areas. What you should do is grab some of the problems sections and drop markers in there and encode them. Some of the frame controls can help, depending on source footage. What was the original material and cpautred/edited? Sometimes things in there can also give quality hits.
Lastly some things (like real black outfits on light backgrounds) can cause some edging issues which can take some work to clean up as much as possible...

Error Importing data into switching data source using cim for CRS Oracle Commerce 11

Hi All,
I am getting the below error while importing data into the switching data source for oracle commerce 11 with CRS.
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339319
atg.cim.database.ImportDataTask
4 Data Import: Repository: /atg/commerce/locations/LocationRepository Path: /CIM/tmp/import/switchingA-import3.xml Module: Store.EStore,Store.EStore.International state:error
**** info
Fri Apr 17 12:18:59 IST 2015
1429253339321
atg.cim.util.AdminDatabaseUtils
The administrative tables have not been initialized. Unable to update the administrator password for this datasource.
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.database.ImportDataTask
1 of 8 data imports had errors. Please check C:\OracleCommerce\ATG\ATG11.0\CIM\log/cim.log for more details.
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
atg.cim.StepException: StartSqlRepositoryTemplateStep:Error Executing Step
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:112)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:99)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:254)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:86)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:111)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.startCimFlow(Launcher.java:361)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.main(Launcher.java:110)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
Caused by :atg.cim.StepException: StartSqlRepositoryTemplateStep:Error Executing Template
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:158)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:99)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:254)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:86)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:111)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.startCimFlow(Launcher.java:361)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.main(Launcher.java:110)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
Caused by (#2):atg.cim.CommandException: Error Executing Template
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:93)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:99)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:254)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:86)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:111)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.startCimFlow(Launcher.java:361)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.main(Launcher.java:110)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
Caused by (#3):atg.cim.RunnerException: Error processing Steps.
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:173)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:99)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:254)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:86)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:111)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.startCimFlow(Launcher.java:361)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.main(Launcher.java:110)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
Caused by (#4):atg.cim.StepException: switchingAImportStep:Error Executing Step
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:123)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:99)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:254)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:86)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:111)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.startCimFlow(Launcher.java:361)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.main(Launcher.java:110)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
Caused by (#5):atg.cim.StepException: switchingAImportStep:Error Executing Pre Navigation Validation
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.ui.text.TextDisplay.processStep(TextDisplay.java:377)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.ui.UIDispatchImpl.processStep(UIDispatchImpl.java:109)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:239)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:99)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:254)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:86)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:111)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.startCimFlow(Launcher.java:361)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.Launcher.main(Launcher.java:110)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
Caused by (#6):atg.cim.ValidatorExecutionException: AlwaysTrueValidator:Error Executing Validator Commands
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.executeValidations(StepExecutor.java:363)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.ui.text.TextDisplay.processStep(TextDisplay.java:375)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.ui.UIDispatchImpl.processStep(UIDispatchImpl.java:109)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:239)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:166)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:195)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processStep(StepExecutor.java:155)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:105)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.runner.Runner.run(Runner.java:170)
**** Error
Fri Apr 17 12:18:59 IST 2015
1429253339322
atg.cim.step.StepExecutor
at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:90)
**** Error

Hi,
I think I faced the same issue when I trying to import data for international(multiple currency support) version of CRS/Motorprise and that time I just switched to use only English version import as last time I concluded was that there is some encoding issue in oracle database.
Please check once you are using right version of oracle db which are supported by ATG 11.
Hope this will help.

Issue: Sending material master using ALE-IDOC.

Hi all,
I am sending the material master data from one server to another.All the fields getting transported along with creator(field ERNAM) of the material.When viewed from WE05 the field is having the same data as original creator of the material in sending system.But when i view data in receiving system for field MARA-ERNAM the field is having the USER NAME giver in RFC-DESTINATION.can anybody guide so that the creator from IDOC is updated in database and not the creator given in RFC
destination.
Thank you.
Edited by: sanu debu on Jun 30, 2009 9:35 AM

Hi,
Hope you are using some middleware to transfer the Idoc to other system, check the mapping details from the middleware side whethere the field mapped correclty.

Issue in Data transfers using ALE for E-Recruiting standalone system

Similar Messages

Maybe you are looking for