No transfer of data executing a mapping

hi guys,
plz help me out! i try to transfer a simple filled table from the design schema to the target schema. there are no errors or warnings deploying the mapping. NOW: every time i execute the mapping it says that the mapping was completed successfully, BUT the problem is it doesnt insert the data from the source table to the target table. the target table is empty.
my question:
- do i have to change/set the system privileges to sysdba or sysoper for the runtime schemas to solve this problem ?
- is it maybe a connection problem between the dw and source module ?
- what could it else be ?
appreciate any idea, thx!
greetings
s8472

i think i know now what is the problem:
althought the owb user's guide tells on page 3-5, that a connector is automatically created as you place sources on the mapping canvas, the missing connector was the problem of the "no transfer" of the data.
so i created a connector from the oracle_dw-module_location to the oracle_source-module_location. after that dont forget to deploy the connection inside of the deployment manager. now the mapping executes and transfer the data completely.
greetings
s8472

Similar Messages

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

How can I transfer binary data from a database to another database?

Hi all.
I want to transfer binary data from a MS SQL Server 2000 to anohter SQL Server 2000.
I created JDBC(table) to JDBC(stored procedure) scenario,and
I uploaded a JPG image file to the sender table using the java program I developed.
The JPG data was transfered to receiver,but the transfered data was broken.
I can't not open the file correctly.
Can XI transfer binary data using JDBC adapter?
The sender table structure is following.
column (data type)
id (int 4)
binary (binary 8000)
flag (int 4)
The receiver stored procedure parameter is following.
parameter (data type)
id (smallint)
binary (binary 8000)
flag (smallint)
Regards.
Yuuki

Hi,
Can XI transfer binary data using JDBC adapter?
Ans: Yes
Supported JDBC Types
http://help.sap.com/saphelp_nw04s/helpdata/en/16/9dc9ac8bc72a48b80e639abaa2e497/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
Mapping JDBC types to Java types
http://help.sap.com/saphelp_nw04/helpdata/en/7d/79dfa72d1049bc963f4f272bb1638e/frameset.htm
Regards,
Prateek

Execute owb mapping as a whole instead of giving step by step or skip

Hi friends,
I need a help from you.. Actually i am working with owb 10.2 and db 10.2. I am able to do all the process successfully like debugging, reinitializing and entering the data into the table.
The thing is while debugging,i have to give step or skip to execute the mapping. Now i wanted to run the mapping as a whole,that is,once if i give debug,all the process must execute automatically and data must enter into the table. I need to avoid step or skip process.
how to achieve that?? pls help me out..
Thanks in advance,
Bharath.
Edited by: user11342336 on Aug 10, 2009 12:06 AM

user11342336 wrote:
Thank you very much for ur reply.
and one more thing, consider, i have two or three mapping to be executed one by one.i.e one after another.
say for an example,i have three stages. stage1,stage2 and stage3. all are inter-related and execute one stage by one.
My job is to debug the stage1 alone. once it finished executing the stage1,it should automatically debug stage 2 and stage 3. and the data must enter into the table in all the stage.
how to achieve this??
Thanks much,
Bharath.Any reason you can't debug them one at a time? Ideally, if you successfully execute stage1, you should have the intermediate data in some table. Resume debugging on stage2 from there.

Getting an error while transfer the data SAP XI to SAP R/3

Hello Everyone,
I am getting an error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
when i was transfing the data to SAP R/3.
But i found the error In SM59 , TCP IP connections ,
AI_DIRECTORY_JCOSERVER , AI_RUNTIME_JCOSERVER and SAPSLDAPI are failed to connect.
ERROR program AI_DIRECTORY_SXI not registered
LOCATION SAP-Gateway on host starxi / sapgw00
DETAIL TP AI_DIRECTORY_SXI not registered
COMPONENT SAP-Gateway
COUNTER 15736
MODULE gwr3cpic.c
LINE 1621
RETURN CODE 679
SUBRC 0
RELEASE 640
TIME Sun Oct 12 16:23:18 2008
VERSION 2
How to register these program?
Can any one please help me.
Thanks
Subash.

Hi,
Check this XI Configuration guide:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089dcc97
Also check this thread on XI installation and post-installation:
Re: XI INSTALLATION and POSTINSTALLATION
Regards,
Subhasha

How to execute a mapping based on an event

Hi
I am on OWB 10.2.0.3. and Oracle 10.2.0.2. I have a mapping which is fine, deploys well, I can execute using the control manager.
I also created a schedule module in OWB, created a schedule for a specific date and time and also an interval, configured the mapping to this schedule. The mapping gets executed successfully at the scheduled time.
The requirement is this mapping needs to be executed by an external process (oracle but a different application in a different machine). The team owning this process is ready to insert a record in a table. Which I want to sense and execute this mapping.
I already have created a procedure so that this mapping can also be run from pl/sql. I can create an after-insert trigger in this table so call this procedure, but that will make the whole think synchronous and the external process will have to wait for this mapping to complete to proceed further which is not acceptable by them.
Is there a way I can check for the record in this table and exec the mapping from OWB?
Can somebody please help and provide me pointers how I can schedule a mapping based on an event (insertion of the record) without (preferably) or with Oracle Workflow.
Thanks a lot in advance!
Maruthi

Thanks Detlef,
The problem I have is the trigger will make it actually synchronous with the process that inserts the record in the table.
Even if I define the trigger as AUTONOMIUS_TRANSACTION, both the process will not parellel. setting this I can have commits and rollbacks in triggers but they will be synchronous. I want this mapping to run asynchronously so that the main process inserts the record and continues with the rest of the process while the mapping can be executed independently.
For this reason I am looking for something which will allow me to do this without a trigger on the table.
As mentioned in your refereed post, I can use CDC, but not sure how good is CDC and will this be an overkill to implement and use CDC for this purpose. Any simpler solution available?
Any inputs please?
Thanks once again!
Regards,
Maruthi

Getting an error in while transfer the data to SAP

Hello Everyone,
I am getting an error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
when i was transfing the data to SAP R/3.
But i found the error In SM59 , TCP IP connections ,
AI_DIRECTORY_JCOSERVER , AI_RUNTIME_JCOSERVER and SAPSLDAPI are failed to connect.
ERROR program AI_DIRECTORY_SXI not registered
LOCATION SAP-Gateway on host starxi / sapgw00
DETAIL TP AI_DIRECTORY_SXI not registered
COMPONENT SAP-Gateway
COUNTER 15736
MODULE gwr3cpic.c
LINE 1621
RETURN CODE 679
SUBRC 0
RELEASE 640
TIME Sun Oct 12 16:23:18 2008
VERSION 2
How to register these program?
Can any one please help me.
Thanks
Subash.

Did you create the entry for this in the J2EE visual admin -> Cluster -> Server -> Services -> JCo RFC Provider ?

Process flow failes when executing a mapping by error ......

hi all,
When we executes a mapping through owb normally it works fine.
But the same when executes throgh a process flow it get falies with the f/w error.
*"Set based mode not supported ORA-06512"*
The operating mode is "set based fali over to row based"
In the mapping we are doing some transforamtion and putting the data in a flat file.
Please help in this reagrd.
Regards
ashok

Hi,
change in processflow configuration property OPERATING_MODE for this mapping to ROW_BASED or ROW_BASED_TARGET_ONLY
Hope this helps!

How we can view convert data after XSLT mapping & before Graphical mapp

Hello Friends,
Currently i am working on XI standard content. In this client need some customization.
In interface mapping, XSLT mapping on 1st position & Graphical mapping on 2nd position.
As per my understanding 1st XSLT mapping will be exected then Graphical mapping.
Can I see or check convert data from XSLT mapping.
I want to check data between XSLT mapping & Graphical mapping.
Kindly help me out.
Regards,
Narendra

>
Narendra GSTIT wrote:
> I dont want to test standalone XSL Code.
>
> The data which I get from Source interface and after XSLT mapping I want to check this that my XSLT code is going well or not.
>
> i.e. check for proper input & get proper output.
You have ro do standalone testing of the XSLT mapping.....Interface Mapping or Interface Determination will give you output message which will be that of message mapping (the last mapping)
What is the issue in testing the XSLT mapping alone?...may be in Stylus Studio.
Just ensure that XSLT mapping produces proper output and then this output message of XSLT is the input to your Message Mapping.....once the entire Interface mapping gets executed then it would mean that all the included mapping programs work fine.
Regards,
Abhishek.

TDMS HCM data transfer - no data transferred to receiver and no errors

Hi,
I am experiencing problems with a "Package for HCM Personnel Dev. PD & PA Receiver " for my client who has approximately 800 employees.
I have no errors in any of the phases, and I can see the TDMS SEND and RECEIVER jobs executing during the data transfer. However, the data transfer phase executes for approximately 1-2 minutes but when I check the tables in the RECEIVER the tables (such as HRP1001) are empty.
There are 42 tables selected, and CNVHCM_TR_TAB contains 1533 entries.
Below is a sample from the 'Transfer Selection Criteria' phase:
Transfer Target - System ECR / Client 210
The Transfer Program ran in PA Delete Mode
The Transfer Program ran in PD Delete Mode
Object Type: C // Total number: 5
Object Type: O // Total number: 5
Object Type: P // Total number: 28
Object Type: S // Total number: 31
Table HRITABNR - Time(ms) 10 - Entries 3
Table HRP1000 - Time(ms) 57 - Entries 65
Table HRP1001 - Time(ms) 39 - Entries 158
Table HRP1007 - Time(ms) 38 - Entries 5
Table HRP1018 - Time(ms) 39 - Entries 3
Table HRT1018 - Time(ms) 17 - Entries 3
Table PA0000 - Time(ms) 53 - Entries 47
Table PA0001 - Time(ms) 83 - Entries 76
So I would reasonably assume that if there are no errors anywhere in the Sender, Receiver or the Central system - that table HRP1001 would contain an extra 158 entries or PA0001 would contain 76 entries. This is not the case PA0001 is empty and HRP1001 contains the same number of rows as before the Data Transfer executed.
Has anyone come across this situation before, or got suggestions on troubleshooting the cause of no data transfer when all the phases are green.
Any assistance is appreciated. Regards,, Sheryl.

Hi Poonam,
The reason why there is no extra PA* tables above is that this was just a short snapshot of the tables, those tables are included.
I have selected the following for the Data Transfer:
Plan Version = 01
Object Type = O
Object ID = 500383 (Contracts)
Objects Status = All Existing
Evaluation Path = BSSORG
Status Vector = 1
PD Selection tab:
Use Current PD Selections - ticked
Transfer PD Infotypes - 0000 to 9402 - ticked
All other PD values unticked
PD Delete and Target options:
Delete target area - ticked
Target plan version = 01, and transfer 1:1 without change chosen
Root options:
Without new root - chosen
PA Selections
Use current PA selections - ticked
Transfer Master Data - Infotypes 0000 to 9402 - ticked
Transfer Cluster Data - ticked
Transfer Central Person - ticked
Partial cut-off date - 01.07.2011
PA Delete and Target Options
Delete Target Area - ticked
Target PERNR Options - Target range - 700000 to 99999999, maximum number range= 99999, transfer 1:1 without change (chosen)
When I choose CONFIRM ONLINE the only warning messages I receive in the log file is (there are no error messages):
No CP Object Type records will be transferred from the sender system
Table PA3xxxx / PERNI is not registered as being released
Table HRPxxxx / PERNI is not registered as being released
Table PA09xx / PERNI is not registered as being released
Hi Toribio,
When I run the test with PD and PA Authorisation with granularity 04 I get no messages on the next screen. All users have SAP_ALL. SAP_NEW, SAP_TDMS_MASTER, SAP_TDMS_HCM_MASTER plus extra specific HR authorisations for PA and PY.
Thankyou both for your assistance, hopefully we can get to the bottom of this problem.
Regards,
Sheryl.

Transfer Rules: How does the mapping work?

Transfer Rules: How does the mapping work?
Is there a document out there that explains the following or can someone help clarify it for me. I have some confusion on what is really going on.
When I create an InfoSource (IS_Test) as a Flexible update and then Assign DataSource (DS_Test) and I respond Yes, to the message DataSource assignment DS_Test to InfoSource IS_Test Save
a) Under Transfer_Structure/Transfer_Rules in the InfoSource
1) the Transfer Rules tab, what are the fields found in the right column (Assigned InfObjct-field)? And where do the fields you enter in the left column (Communication Str/Transfer rules) eventually go?
2) the DataSource /Trans. Structure tab, can I always assume that all the fields in the right column (DataSource) came from DS_Test? The left column (Transfer Structure), in my test was exactly the same as on the right. Where do these fields eventually go?
b) Under Communication_Struct., in the InfoSource
3. the right column (ISource Fileds) where from those InfoObjects. if I am now creating my InfoSource. Where did they come from?
4. The left column is Communication Structure, which at this point has no InfoObjects, if I move a couple of InfoObjects from the right to the left, where do these Objects in the left eventually go?
5. what is the relationship between the Communication Structure in 4 and 1? Or any relationship between a) and b) as a whole?
Thanks.

Hi Caud,
As Ashish pointed out, communication structure contains fields (infoobjects) that suppose to go to data targets. Which IO in CS to which IO in the data target will go (and what transformation of data may occur) is determined in URs of the data target.
The transfer structure is the structure in which the data is transported from the source system into BW:
http://help.sap.com/saphelp_bw33/helpdata/en/3f/0e503c3c0d563de10000000a114084/frameset.htm
In Transfer_Structure/Transfer_Rules in the IS, DataSource /Trans. Structure tab, right part shows fields in the Datasource, the left part fields in the transfer structure. There is also a transfer structure in R/3 for a given DS. Transfer structure in BW is created identical to the TS in R/3 during TRs activation.
During data load data are transferred 1:1 from TS in R/3 to TS in BW.
TS in BW corresponds to the PSA table structure.
How data from PSA are transferred to the CS is determined in TRs.
The 3rd column (Field) (Transfer Rules tab, right part (Assigned InfObjct-field)), contains field names of the DS (TS); and the 1st column shows IO in the CS to which the DS field will go. So, its a mapping DS filed -> CS field.
The left part (Communication str./Transfer rules) is always identical to the CS content. But the 4th column (Tp) shows possible data transformation during transfer from PSA to CS. If this column contains a yellow triangle then there is no transformation (Value of DS field will go to value of CS field). If there is a red cross, it means that no data for this CS field is supplied from a DS. You can click on this yellow triangle and choose: 1). Another field from a DS; 2). Constant; 3). ABAP routine; 4). Formula. So, here you can determine the data transformation. Moreover, there is a possibility to create a start routine (blank sheet icon at the top).
And finally, here are the answers on your questions:
Q:
a) Under Transfer_Structure/Transfer_Rules in the InfoSource
1) the Transfer Rules tab, what are the fields found in the right column (Assigned InfObjct-field)? And where do the fields you enter in the left column (Communication Str/Transfer rules) eventually go?
A: Right part shows a mapping between DS and CS fields. Left part shows CS fields and data transformation (TRs) during data transfer from TS (PSA) to the CS. These are fields in the CS that will go to data target and which are fed from a TS (DS).
Q: 2) the DataSource /Trans. Structure tab, can I always assume that all the fields in the right column (DataSource) came from DS_Test?
A: Yes, you are right.
Q: The left column (Transfer Structure), in my test was exactly the same as on the right. Where do these fields eventually go?
A: As I described, left and right parts are identical. These fields will go to CS.
Q: b) Under Communication_Struct., in the InfoSource
3. the right column (ISource Fileds) where from those InfoObjects. if I am now creating my InfoSource. Where did they come from?
A: these are fields from an IS template, the name of this template you can see above this right part. Actually, during IS (CS) creation you can choose different templates and choose fields from them transferring them into the left part.
Q: 4. The left column is Communication Structure, which at this point has no InfoObjects, if I move a couple of InfoObjects from the right to the left, where do these Objects in the left eventually go?
A: these are fields of CS (left part) and as I said before they will go to data target.
Q: 5. what is the relationship between the Communication Structure in 4 and 1? Or any relationship between a) and b) as a whole?
A: CS in 4 just shows IOs that will be transferred to data target. CS in 1 also shows how values for CS IOs are to be fed and transformed.
Best regards,
Eugene
Message was edited by: Eugene Khusainov

Error on "External Payment Collectors: Transfer Payment Data"

Dear FI-CA gurus
On the program ""External Payment Collectors: Transfer Payment Data"
(RFKK_CVSPAY_CONFIRM),
when I ticked the simulation flag, it seemed the file upload
is done successfully.
However, when I ticked-off the simulation flag, I got error message
">0 015 Formal error in table FKKOPK: Item 0002 is incomplete".
I created the test file from program "rfkk_cvspay_confirm_test".
Did I miss something??
Y.Kaneko

Hi, Doug.
By not ejecting the drive before disconnecting it, the partition map was corrupted. Short of professional data recovery, you've covered everything and then some in my "Data Recovery" FAQ. If DR-II and TTP can't recover the data, then you're left with professional data recovery, per my FAQ.
I presume you don't have backups of the contents on the LaCie. After you recover from this incident, I suggest you implement a comprehensive Backup and Recovery solution addressing all of your drives. For advice on the backup and recovery solution I employ, see my "Backup and Recovery" FAQ.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Transfer forms data to excel

Hello Guys,
I have emp block in my form that when executes query displays all records. I want to transfer this data to excel sheet. Column names of the block needs to be the heading of excel sheet.
Please give me an idea how to do so.
Regards,
Imran

Follow it:
Re: How export data to Excel
Regards

Error in transfer applicant data to PA30

Hi Friends
When i am transfer applicant data to PA30,
the error message come " maintain applicant activity error"
i had check all the configuration and maintain
also check all the post on the SDN related to transfer applicant data.
but still i am facing problem.
can anybody tell me how come out from this issue
thanks and regards,
urvashi chaudhari

Hi Uravashi,
Please goto transaction code PB 60 and check if the activities are maintained for an applicant. Delete all unwanted entries and again execute an action "Prepare for Hiring". In this step, after saving the first screen, one more pop up comes for applicant activity. If you have any specific activity then specify it here or simply click on enter.
Once this is done execute the transaction code PBA7 to transfer the applicant data to PA.
You have mentioned something about PA30 in ur last message. I hope it was a typo error.
Thanks!
Best Regards,
Chetan Shriraj Wahane

Error while executing a mapping

Hi All
I'm getting the following error message when i'm executing a mapping :
ORA-12801: error signaled in parallel query server P013 ORA-01722: invalid number
Any advice or help is greatly appreciated.
Thanks

Thanks Nawneet
I got the error from the runtime browser where you can view the errors, and i dont see any debug options in there except the error message.
Thanks again

No transfer of data executing a mapping

Similar Messages

Maybe you are looking for