Transfer of data in screen programming

Hi All,
Can u clarify how data is transfered in screen programming. as we dont write any write statement in screen programming.
i know that it will compare the screen field names with abap variables. so can anyone clarify in this point.
if i was right or wrong can any one make me clear how data is going to transfer.
Thanks
T.Ramana Prasad

*& Module pool       ZBHMOD2                                           *
REPORT ZBHMOD2.
DATA: OKCODE1 TYPE SY-UCOMM,
      OKCODE2 TYPE SY-UCOMM,
      ENAME(10) TYPE C,
      DNAME(10) TYPE C.
MODULE STATUS_1000 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'TIT1'.
ENDMODULE.                 " STATUS_1000 OUTPUT
MODULE STATUS_1001 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'TIT2'.
ENDMODULE.                 " STATUS_1001 OUTPUT
MODULE USER_COMMAND_1000 INPUT.
CASE OKCODE1.
WHEN 'BACK'.
SET SCREEN '0'.
WHEN 'NEXT'.
DNAME = ENAME.
SET SCREEN '1001'.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_1000 INPUT
MODULE USER_COMMAND_1001 INPUT.
CASE OKCODE2.
WHEN 'BACK'.
SET SCREEN '1000'.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_1001 INPUT
FORM ON_CTMENU_FORM USING ZDEMO1 TYPE REF TO CL_CTMENU.
CALL METHOD ZDEMO1->LOAD_GUI_STATUS
EXPORTING
      PROGRAM = 'ZDEMO1'
      STATUS = 'ZDEMO1'
      MENU = ZDEMO1.
ENDFORM.                    " ON_CTMENU_FORM
FLOW LOGIC:
PROCESS BEFORE OUTPUT.
MODULE STATUS_1000.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_1000.
PROCESS BEFORE OUTPUT.
MODULE STATUS_1001.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_1001.
hi,
this is a simple program to move dat from screen to screen.
regards,
bharat.

Similar Messages

Screen Exit - Enhancement MM06E005 - Transfer input data back to program

I have implemented enhancement MM06E005 to create a subscreen on the PO header. I have created the screen and I see it on the POs tcodes (ME2#n). However, I can't figure out how to "save" the data that the user inputs. By save I mean bringing the data back to the calling program (tcode). When the PO is saved the input data goes away; it is there until the save. I realize that I am missing something but I can't figure how where/how to transfer the data in the FMs EXIT_SAPMM06E_007 and/or EXIT_SAPMM06E_008.
I have read the SAP documentation but that isn't much help. I also have a book from SAP on modifications/enhancements (from an SAP course) and that isn't of any help either.
Any ideas?
Regards,
Davis

Hello,
i think you can found an answer to your question in the thread below :
[MM06E005 functional exit;
Particularly, the post of Padmam is saying : "You incorporate your customer fields for the Document Header in the INCLUDE CI_EKKODB (in table EKKO)."
Have you add the customer fields (those displayed in the subscreen you create) in the include CI_EKKODB ?
Cordialement,
Chaouki.

Transfer Payload data to Screen

Dear All
I have to retrieve a perticular value of a field (say MATNR) from an IDOC MATMAS which is in XI.
I know that this value is stored in the payload of the message. By searching I have found that the payload is stored in SXMSCLUP TABLE.
How can I retrieve this value and display it to the screen of my report program screen?
Edited by: Sourabh Nirmal on Sep 24, 2008 1:24 PM

Hi
I found the answer for my query...
1) the data that we try to upload in InfoPackage should be in form of XML.
2) their should right objects in InfoObject ... same as XML
Thanx
Shivanjali

Need to transfer value from BADI to program/smartform

Hi Guys,
I have to add 3 fields from Infotype/table PA0041 to the smartform generated by this Program "Employer Statement (RPLERCC0)". I have implemented a BADI and written my code in the method get_output_strucuture. But how will I transfer my data to the program/smartform. If anyone has worked in the same then please provide your suggestions.
Thanks in Advance.
Manoj

Hi,
Do an export/import.
* In the Badi
EXPORT ZQTY
              ZMATNR
     to memory id 'ZTEST'.
* in the report program
IMPORT ZQTY
             ZMATNR
from memory id 'ZTEST'.
FREE MEMORY ID 'ZTEST'.
Best regards,
Prashant

Phone screen is blank, I need to transfer all data

My phone (Accolade LG-VX5600) got broken at the hinge, and now my screen is blank.
I need to transfer ALL data to a new phone, but in the mean time I want to transfer everything to my computer. I downloaded LG pc sync which enabled downloading my contacts and calendar reminders. Now I'm looking for a way to do the same with my photos and text messages. BitPim does not support my model.
I'd prefer to do it for free.

I can understand your desire to transfer your photos and text messages to your PC, malpa. You won't be able to transfer your messages to your PC, but you can forward them individually to an email address. All you'll to do is enter the email address where you would usually enter the wireless number.
Your device does not offer mass storage. You can transfer your pictures using your text message application. Attach the picture to a text message forward it to an email address. I hope this helps you save your precious memories. Have a great day.
ChaunceyM_VZW
Follow us on twitter @VZWSupport

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

Taking data from one program to fill in pdf form

I'm pretty new to this and I am not even sure this would be possible. I've created a fillable .pdf form and I was wondering if there is a way to transfer information from one software program into it's correct fields on the fillable form. For example, the person's contact information is seen on the screen from on program, but not in any structure to just copy and paste, and I would like to somehow very quickly autopopulate/transfer it to the form?

There's no way to do that with JS. What you can do is export the data to a
plain-text file and then use JS to import that file and populate the
fields. If you're not using Acrobat X it would also be possible to do it in
a smoother way using a local DB, but that is also much more complex to
implement.
For a more automated solution you will need to use a plugin or stand-alone
application. You can ask at the Acrobat SDK forum about those.

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.

The "infallible" backup system crashes and burns; how to transfer the data?

After five years of exemplary, error-free service, my old Powerbook G4 1Ghz finally crashed during a backup to an external hard drive. I just bought a new Macbook Pro (arrived September 16th) and want to transfer the data from the old Pro to the new Pro. Herein lies the complex problem, and Migration Assistant and a firewire cable won't solve it.
When the old Pro died, I was maintaining what I believed to be an infallible backup system (ha). I did nightly backups to two different external hard drives; one was a USB LACIE drive, the other a firewire LACIE drive. I used Carbon Copy Cloner to do a merge contents backup on the USB drive and a file-level bootable clone to the firewire drive. Surely nothing could go wrong. Oh, one only needs to think of the Titanic and say, “Something did.”
The old Pro could only backup to the USB drive when using an express card that added USB 2.0 connections (the old Pros have USB 1.1 and they’re too slow). But whenever the express card was plugged into my old Pro and it fell asleep without my first powering the card off, the computer crashed. This was no problem; I just powered off the card before putting it to sleep and ignored the fact that the computer on rare occasion acted buggy with the USB express card plugged in. Well, on the fateful night in question, the computer did its backup to the USB drive and then fell asleep while it was still plugged in (this is what its energy saver told it to do, unfortunately). When I tried to turn the computer back on, a black box appeared in the upper left hand corner with a bunch of random-seeming white text and the concluding message, “Waiting for remote debugger.” The computer was frozen and a cold reboot was the only option.
My old Pro would never be the same again.
I tried to boot it up. Sometimes it did so, but then would suddenly show a red screen and crash. It kept crashing, sometimes just powering off immediately. So I brought out good old Disk Warrior, booted up with that, repaired permissions, repaired disk, and rebuilt the directory. I also booted up with the Tiger OS X install CD and fixed permissions that way just for good measure. The computer then started up fine. I thought I was back to normal! Celebration time! Not. The USB drive that I had backed up to would not mount anymore. So I, seeing that the computer appeared to be back to normal, just plugged in second external hard drive--the firewire--and began the bootable clone. It delved into making the clone without a hitch and I went off to work happy and content that I would have an up-to-date backup soon.
Lo and behold, when I came back from work, the backup to the firewire drive hung midway through. It had done nothing but wiped the entire drive and copied about 500 mb of data to it before freezing. I tried again several times and, believe it or not, only got vastly improved results when the offending express card was actually plugged into the computer. By this mysterious and probably risky method, I was able to get some data off. But only about 1/10 of the whole. The old Pro always would crash before more than 5 gigs of data or so can be transferred.
Starting from around that time, the offending old Pro began to exhibit hideous popping, gurgling, grating, clicking, swiping, and other sounds from the left hand side of the computer—where I imagine the hard drive is. These sounds can be quite loud and sometimes even sound like tempered UFO tones beamed down to the computer. Sometimes they aren’t present at all and the computer acts fine, until a certain file or folder is accessed, and then they start again and the computer hangs, going from fine to disastrous in an instant.
I took out the offending express card and launched it away and took the USB drive and put it on another computer. It still would not mount. I finally got it to unlock (it’s a fingerprint-access safe drive) and ran Disk Warrior on it and was able to get as much data off it as I could. But it appears that a huge chunk of data was simply missing from the drive, whether from Disk Warrior having to delete data when it rebuilt the directory or from damage when the computer died while backing up to this drive, I don’t know.
So now I went from a supposedly infallible backup system of two rotating external hard drives to potentially losing 5 years of utterly critical work!
I tried starting up the old Pro in target disk mode with my new Pro. At first, this appeared to have very promising results because there was no grating or popping sounds from my old Pro when I did this. I began a data transfer with glee. But no luck; the old Pro always eventually hangs and the new Pro doesn’t even recognize it (the icon for the old Pro disappears as if I unmounted it).
Sometimes the Old Pro can still boot up and seem to act fine; it can sit like that indefinitely, I'd guess; but if the disk is actually read and written to enough, it always fails. I am using it as little as possible now (i.e. not at all) so as not to exacerbate the problem any more than it already has been.
Two quick notes that might further explain the situation: two weeks before the crash happened, I used iDefrag to defragment the drive. The night before the crash happened, I did a lot of work on my computer while on a bumpy trip on the Long Island Railroad. The computer acted fine throughout all this, but perhaps the bumpiness or the defragmentation contributed to this problem.
I must get the data off. This dead/dying hard drive doesn’t just contain mere photos and music libraries and nifty applications. I’m talking completed and incomplete novel manuscripts, lecture notes, lesson plans, published and to-be-published articles, a massive thesis, and much more totaling literally thousands upon thousands of pages and representing more than 5 years of graduate and professional research and work. For me, the stakes are critically high. Thank you for reading this Hero's Journey of a post.

Good news!
Imagine a Venn diagram with four interlapping circles. The circles are:
1. Catastrophically exploded hard drive
2. Catastrophically annihilated external hard drive used for incremental backups
3. Catastrophically wiped cleaned external hard drive used for bootable clones
4. Email, CD, and iPod backups
With a little shake, rattle and roll and other craziness you do with a hard drive with failed bearings, I got #1 working briefly, thank goodness.
With Disk Warrior and figuring out how to surpass a fingerprint-activated security feature, I got #2 working in a limited fashion.
With some workarounds, I got some use out of #3.
#4 just is.
The interlap of these 4 things produced about 95-99% or so of my data, including all critical items. It was a disorganized mess I just spent two days organizing, but I am back up and running without having to use expensive data backup services. I am slightly bothered by that slight bit of missing data, but from what I can tell, it amounts to nothing more than a brief sketch of a lesson plan, a song or two from the iTunes store, and maybe a handful of attachments. Nothing to spend big bucks recovering, in other words.
Now I will substitute my "infallible" backup system with a new one:
1. Time capsule/time machine
2. Complete online backups with Mozy
3. Occasional bootable clones to the external hard drive I have that didn't get damaged.
I think this will be the ticket!
Thank you all.

How do I transfer my data to my new macbook pro using an external hard drive?

I've already set up my new MacBook Pro is my issue. It asked me if I'd like to "Migrate" my stuff or use an external hard drive etc but at the time I didn't transfer my data from my old MacBook yet. I was going to manually do it later as I had to wait for my External hard drive to back my old Mac up. Now it's that time and I have no idea how to do it. I believe I've researched best of my ability.
I feel like I'm asking a pretty dumb question. If I were to just drag all my programs out like my Adobe Suite on to my new macbook pro would that work? I feel like that's just too easy and incorrect. Please and thank you.

The Adobe suite can be downloaded free, you dont have to copy it at all, under standard CS6 Adobe rules, if you own the suite, you get 2 computers "activated at any one time" Make sure, if youre not using the older computer, you deactivate the software under the HELP menu in Adobe.
format the new drive in disk utility ......APPLICATIONS.....UTILITIES.....DISK UTILITIES.......select the external drive and format (if its new and empty!!!) under the ERASE button with Mac OSX extended journaled
copy all your important stuff from older computer , pics, files, documents, personal anything.
most of you apps, i ASSUME you bought in the (other than Adobe software, or Office suite, etc etc,..... obviously) in the MAC APP store, so you can reload them on the new computer without copying them , makes things very easy......just open APP STORE, and download what you already bought.
really the only important things , is copy all important work files, documents, pictures, personal ABC...XYZ...... obviously.
the migration is about emails, contacts, etc etc etc, also data, just because you passed it by at the time doesnt mean you still cant do it, go to the SEARCH at menu at top and type in MIGRATION ASSISTANT to do it again , since you passed it by at first .
the only thing you NEED / SHOULD copy is all your personal stuff........Applications need to be reinstall from either ONLINE download,.......or from the MAC APP STORE,........ you cant just copy the apps over (in most cases) and toss them onto the new computer
Nahh, there are no dumb questions, just dumb mistakes because you DIDNT ask any questions, and we all make those here and there.

Transfer of data from one iTunes account to another

My son has been using my iTunes account for games. Got him a 5th gen iPod touch. Can I transfer his data from my iTunes acct to a brand new iTunes account ? He is so ovewhelmed that he will lose his data .

Have you looked at the Family sharing program?
http://www.apple.com/ios/whats-new/family-sharing/

I have a mid year 2007 24 inch iMac and will be purchasing a new 27 inch Retina iMac, what is the easiest way to transfer the data and files from my old machine to the new one?

I have a mid year 2007 24 inch iMac and will be purchasing a new 27 inch Retina iMac, what is the easiest way to transfer the data and files from my old machine to the new one?

Following up on this thread,
I have a new iMac on the way and my current is from 2008, never had a problem but I am sure there are internal issues that I would prefer not to transfer.
I have no issues other then the slowness in certain programs and that is the main reason to buy a new one.
Programs like numbers and pages seem to take a longer time to open after I update to Yosemite.
I only use 272GB of 500 GB, my memory is 4GB and I am upgrading to 8Gb and bought the 4.0 processor.
Question:
Is there a way to manually transfer items or would that be a waste of time in that if there are issues they could be anywhere and would transfer anyway?

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

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

Error in LSMW for MM41 - "No batch input data for screen SAPLMGMW 0100"

I'm trying to create an LSMW for MM41 to create new Retail articles en Mass. This will be used to only create the Basic view as other LSMW's already exist to maintain the other views. I've created the Recording and setup the LSMW already. My data is read correctly from the source file. When I execute the batch session it fails with the following error - "No batch input data for screen SAPLMGMW 0100".
I assume the fields in MM41 screen are not setup for batch processing. Could someone with more knowledge or experience in SAP Retail please confirm my assumption and explain where this is setup or provide an alternative to creating new articles en Mass via MM41? The direct input method is more suited for MM01 and not MM41.
Regards
Fawaaz

Hi Guys,
Thanks so much for all the prompt responses. My issue is now resolved.
The issue, I'm sure, was my default settings in the MM41 screen which the recording probably took into account or the batch program didn't like. I deleted my recording and created a new one but before I started the recording, I went into the MM41 screen and removed all default values AND view selections. I made my Basic view selection constant in my recording and also in my field mapping. My LSMW for MM41 is now working perfectly.
Just to answer some of the questions above, my LSMW was Reading and Converting the data in my source file fine. When I display the Read and Converted data, it shows the data fields in the correct place.
Thanks again.
Regards
Fawaaz

Transfer of data in screen programming

Similar Messages

Maybe you are looking for